Computer integrated systems design, seated one blade at a time
Kunming Fanbi E-commerce Co., Ltd. is a computer integrated systems design studio working from a bench room at Unit 2, Room 705, Building 3, Zhicheng Homeland, Fengning Subdistrict, Wuhua District, Kunming - 650000, China (CN). We take a system the way a technician takes a fan deck: seat every blade, check the balance, and feel the draft before the unit is declared ready. See the full service deck Every engagement ends with a written run sheet, not a slide deck.
Open a bench slotThe motor swap window opens on the first working Monday of each month, and the bench holds an extra chair for every client who wants to sit through the swap and watch the new drive settle into the frame.
Each round is a fixed piece of work with a named owner, a start rule and a finish rule. The list below is the same list our bench crew reads from every morning, unchanged since the room opened.
The first round of any integrated system design is the blade set desk, where we lay out every functional module of the client estate and give it a seat, a purpose and an owner. Nothing moves forward until the set is complete and nobody is holding a spare blade that belongs to another system.
Ledger fan rounds are our scheduled walk of the whole stack, read from oldest record to newest, so that drift in one layer cannot hide behind a healthy reading in another. The round produces a short written ledger entry that names what changed and who signed off on it.
A draft band week is a dedicated block where the bench tunes airflow through a system: cache behaviour, queue depth, message size and the pace of background jobs. We target the draft, not the peak, because a system that moves air comfortably at idle is the system that survives a hot afternoon.
Motor swap days replace the drive behind a workload without stopping the desk that depends on it, using a staged handover and a rollback seat that stays open for the whole window. Our crew writes the swap sheet before the first component is unclipped and reads it back to the client after the last.
Balance run sessions are load tests built around the way a client actually works, with the ratio between read and write, burst and lull set from real telemetry rather than a vendor chart. We report vibration in the system the way a technician reports vibration in a fan frame: small numbers, plainly stated.
Wiring check evenings are quiet after-hours reviews of interfaces, credentials, certificates and the small joins between services that nobody notices until one of them loosens. Every check ends with a diagram update and a list of joins due for another inspection in the coming quarter.
An integrated computer system earns trust only when it is quiet in the ordinary hours. Our office sits above a busy street in the Wuhua District, and the desk fans in the room taught the crew an early lesson: a fan with one loose blade rattles all night, and no amount of polish on the grille hides it. We build systems the same way. We seat each blade, meaning each module of the client estate, inside a frame that can carry it without stress.
The bench room at Unit 2, Room 705, Building 3, Zhicheng Homeland holds six work bays, a shared test rack and a wall of printed run ledgers that goes back to the first engagement. Clients are welcome to sit at the spare chair during motor swap days and wiring check evenings, because a system that cannot be watched by its owner is a system that cannot be trusted.
Every design deliverable leaves the room with a fan sheet: the seated module list, the balance readings, the draft band target and the wiring diagram revision. The fan sheet is short on purpose. It fits on one page and it names the person who checked each line. When a client calls a year later, the crew pulls the sheet and the conversation starts from the last known good balance.
We serve small manufacturers, logistics operators, research groups and professional service firms, and we never take an engagement we cannot finish with the bench crew we have. Capacity is published, slots are booked ahead, and the bench closes for maintenance every quarter, which is the one week the crew spends tuning its own systems rather than someone else.
Four stages, each with a written gate, so that nobody at the bench or on the client side is guessing about the state of the work.
We inventory the estate, write the seated module list and agree on which systems are in scope for the first cycle. The blade set desk produces the page that every later round will reference, and the client signs it together with the bench lead.
Through ledger fan rounds and balance run sessions we read the system under real conditions and record the readings that matter. Any reading that drifts outside its band gets a named owner and a date, and nothing is quietly absorbed into the next report.
Draft band weeks tune the airflow and motor swap days move the drive components into their new positions. We test the draft after every swap and we keep the old configuration documented until the new one has run clean for a full cycle.
Wiring check evenings end the cycle with a review of interfaces and joins, a fresh diagram revision and a handover note. The client keeps the fan sheet, the bench keeps the ledger, and the next cycle starts from a known balance rather than from memory.
Computer integrated systems design covers a wide field, from control rooms to commerce platforms to research instrument networks. We stay inside the part of that field where careful bench work makes the difference: the joins between systems, the airflow between services, and the balance of a stack under steady load.
We map the modules, the data paths and the contracts between them, then build the integration layer in stages that each pass a balance run before the next begins. No big bang cutover, no undocumented bridges.
Draft band tuning sets the airflow of a system so that ordinary days feel effortless. We tune cache, queue and batch windows against real telemetry, and we publish the target bands in the fan sheet.
Motor swap days move platforms, databases and runtime engines without freezing the desk. The swap sheet lists every step, every dependency and the exact point at which a rollback would be called.
Ledger fan rounds and wiring check evenings keep the design honest after launch. We read the system the way the crew reads a fan deck, one row at a time, and we record what we find.
The Fanbi bench room was fitted out by the crew itself. Six work bays face a shared test rack, the walls carry printed run ledgers instead of posters, and a long shelf holds the desk fans that gave the room its grammar. Each fan on the shelf was chosen for a quality we wanted to copy in our systems work: a broad blade for low-speed efficiency, a copper hub for quiet bearings, a tight cage for safety at high speed.
Cables run through cable trays that anyone can trace with a finger from the rack to the wall, and every tray is labelled at both ends. The room has no door on the client side of the bench, which means a visiting client can walk from the reception chair to the rack without asking permission. If a system is too tangled for its owner to follow, we consider that a design fault and fix it before we fix anything else.
Ready to seat the first blade?
Send a short note about your estate and the bench lead will answer with the next open slot. We reply to every enquiry within two working days, and we will say plainly if the work does not fit our bench.
Contact the bench