SVC-03 / Hardware Implementation
Hardware Implementation
Specification, procurement, install and commissioning of the physical layer.
The situation this addresses
The model works on a laptop. It has to work in a warehouse, on a factory floor, in a room with one power circuit and a network nobody has audited since the fit-out.
How we approach it
In order.
- 01Survey the site: power, cooling, network, physical access, and who is on site at 2am.
- 02Specify to the workload, not to a vendor’s data sheet.
- 03Procure, stage and burn in before anything goes near the rack.
- 04Commission against a written test plan and hand over the results.
What this looks like in practice
This is the part most AI suppliers subcontract or simply decline. It is also where projects die: the model is fine, the integration is fine, and the whole thing stalls because the only free power circuit in the room is already carrying the compressor, or because the network drop the plan assumed does not exist.
So we survey first, physically. Power draw and what else is on the breaker. Ambient temperature at the hottest hour, not the average. Where the cable can actually run, and who is allowed to open the cabinet at 2am when it stops. Those answers change the specification more often than the workload does.
Specified to the workload
A data sheet describes a device under conditions that are not your site. We size to the job — inference throughput you actually need, headroom for the version of the model you will want in eighteen months, and a failure mode that degrades rather than stops. Where a cheaper box does the job, we say so; the margin on hardware is not why we are in the room.
Staged before it ships
Equipment is built, configured and burned in on the bench before it goes near your site. Install day should be install day, not first-boot day.
Commissioned against a written plan
You get the test plan before we run it, the results after, and an as-built pack that reflects what is actually in the rack rather than what was drawn six weeks earlier. Plus a spares list, because lead times are the thing that hurts.
Hardware trackWhat you end up with
Three things you can point at when it is finished.
SVC-03-01
Site survey, bill of materials and rack elevation
SVC-03-02
Install, cabling, network and power configuration
SVC-03-03
Commissioning test results and a handover pack
- Site survey
- Power, cooling, network, physical access and out-of-hours cover
- Specification
- Sized to the workload, with headroom, not to a vendor data sheet
- Procurement
- Bill of materials issued for your sign-off before anything is ordered
- Staging
- Built, configured and burned in on the bench before dispatch
- Install
- Cabling, network and power configuration on site
- Commissioning
- Run against a test plan you receive before we run it
- Handover
- As-built documentation, test results and a spares list
- Typical duration
- 3–10 weeks; procurement lead times usually dominate
- Engagement shape
- Standalone install, or the physical layer of a larger build.
- Indicative duration
- 3–10 weeks; procurement lead times usually dominate. Confirmed in writing after the discovery call, not before.
What usually sits next to it
Rarely bought alone.
SVC-02
Technology Consultancy
Architecture, audits and roadmaps — before you commit budget to a build.
Read the service detail
SVC-04
AI Solutions
Models, RAG pipelines and decision systems wired into real business data.
Read the service detail
SVC-01
Software Development
Custom web and backend systems built to your operations, not to a template.
Read the service detail
Next step
Bring us the process, not the specification.
A discovery call is 45 minutes. You get a written summary of what we heard and what we would do about it, whether or not you go further with us.