Service Catalogue · Suzhou Fort Desk
The six sheets of the fort desk
Wall sheets, watch runs and client letters run from the Suzhou fort desk of SuZhou RongZhai E-Commerce Co., Ltd., where every engagement is posted as a sheet on the wall rail and read in order. Each service below can be taken on its own or as part of a full desk cycle, and each one leaves a written record behind.
Wall Sheet Bays
A wall sheet bay is the master record of an engagement. It names every subsystem, every interface and every external dependency that a computer integrated system must carry, and it fixes the acceptance line before any hardware is ordered or any code is committed. The desk draws the bay as a single page so that a director, an operator and an engineer can all read it without translation. Nothing is assumed; anything unverified is marked as a question for the next discovery sitting.
The bay stays open for the life of the engagement. Changes do not arrive as chat messages or verbal agreements; they arrive as signed watch notes that amend the sheet and are dated in the bundle. When a client later asks why a decision was made, the answer is already on the wall.
Watch Note Runs
A watch note run is a scheduled sequence of short written observations. Each note records what the desk saw, what it means for the wall sheet and what the next watch should test. Notes are kept to a single screen wherever possible, because a note that runs long is a note that nobody reads. Runs are filed by date so that the client, the build floor and any auditor can follow the system up close.
Most engagements take a weekly run during active build and a monthly run during steady operation. The rhythm can be raised for a migration or a peak season, and it can be lowered once the system settles, but it is never stopped without a closing note that says why.
Client Letter Desks
The client letter desk is where the practice states its promises in plain language. A letter confirms what will be built, what it will cost, what it will not do and who is responsible for each part. Letters are written before work begins, countersigned by both sides and stored as the first page of the wall sheet bundle, so that the original intent is never lost behind later detail.
The desk also uses letters for difficult conversations: a scope disagreement, a missed window or a change of direction. Writing it down is not a formality. It is the practice that keeps a long systems project from drifting into a dispute that nobody intended.
Battlement Windows
A battlement window is a staged view of the system at an agreed moment. The desk prepares a short demonstration and a written note that lists what is finished, what is open and which decisions the client must take before the next window opens. The client brings the people who will actually operate the system, not only the people who signed the letter.
Windows are held at the natural seams of an integrated build: after the interface map, after the first working slice, after the load test and before handover. Each window closes with decisions written into the wall sheet the same day, so that the next window starts from a settled page rather than from a memory.
Signal Review Rounds
A signal review round gives either side a formal route to raise a concern about risk, quality or scope drift. A signal is not a complaint and not an escalation; it is a written flag that says something needs a decision soon. The desk answers every signal within three working days, and the answer is filed in the watch note run whether the outcome is agreement, a change or a reasoned refusal.
Rounds are held at fixed points through the engagement and on request when a concern cannot wait. The value of the round is that it happens before the problem reaches the shipping door, when the cost of a change is still measured in hours rather than in weeks.
Tower Sittings
A tower sitting is a short leadership review held off the build floor. The desk brings the wall sheet, the watch notes and the current signal list, and the client brings the business goal the system was built to serve. The question is not whether the build is on schedule but whether the system still points at the goal it was raised for.
Sittings are held quarterly for long engagements and once at the end of a short one. They are documented in a single page of decisions and are deliberately kept separate from the day to day watch, so that the conversation stays strategic and does not dissolve into ticket detail.