Systems drawn before they are built. SPEC

Computer integrated systems design sits at the seam between the people who specify a system and the people who build it. On one side are operations leads describing what they need on a busy Tuesday morning. On the other side are vendors selling a platform, a switch, a licence tier or an integration layer. In the middle sits a gap, usually a few pages wide, where most of the cost of a project quietly accumulates.

Hartvigsen Roberts Technologies LLC fills that gap with drafting. Our desk does not resell hardware, does not earn commission from vendors and does not run builds. That independence is the point. When we draw a system, the drawing answers to the client, and the client alone decides which members to load and which to leave out.

Spec Sheet Bays in daily use

A number of client engagements begin with a single overflowing inbox: old network diagrams, half finished licences, a spreadsheet showing a switch that was decommissioned two years ago. The first task is to build a spec sheet bay that collects every fact about that system into one controlled folder. Each bay holds the hardware model, the firmware baseline, the network path, the software dependency and the named owner. Over the life of a project, the bay becomes the single source of truth that stops a build team from implementing a design that only half exists.

Truss Drawing Runs and the shape of a system

A truss drawing run takes those facts and arranges them as a structure. Members are the components carrying load, joints are the contracts between them, and gussets are the agreements keeping the joint from buckling. Drawing the stack as a truss makes dependency visible. A design with a long unsupported member in the middle of the run is obvious at a glance, and a second support can be designed before the build team discovers the weak point under real traffic.

Integration Letter Desks and the written handoff

Integration letters are the documents that change hands at the boundaries between vendors. Most projects already produce more mail than anyone reads, so the desk writes each letter in plain sentences: who agreed to which interface, on what date, under which condition, and who owns the consequence if it slips. The letters live alongside the drawing, and every one is written twice over the course of a project so a change in vendor terms cannot disappear into a thread. You can review the full letter workflow on the integration letter desks section of the services page.

Design Windows, Load Review Rounds and Draft Sittings

Once the drawing exists, the work moves into scheduled design windows. A design window is a reserved block of drafting time that the client books in advance, and it always ends with a marked drawing. Load review rounds then test that drawing against real pressure, with findings written as short numbered notes so the client can act on each one. The sequence closes with a draft sitting in which the client and the desk edit the drawing together, leaving a signed sheet that carries authority into the build phase.

Who the desk suits

The practice works well for mid sized organisations bringing several vendors into one system, for operations teams inheriting an undocumented estate, and for build teams that want a defensible design before they commit staff. It is a poor fit for a client who wants an on call engineer or a monthly managed service. The desk sells drawings and review time, and every deliverable is a document rather than a subscription.