Section 00Line 02
Line of work 02
Build and integration
A pallet of boxes is not a delivery. What leaves our bench is a rack that has been assembled, brought to a defined firmware level, configured, run under load and written down.
Section 01Scope
What a build includes
Mechanical
- Rail kits, mounting, blanking panels
- Power distribution and redundant feeds
- Structured cabling with a documented port map
- Labelling to your naming scheme, both ends of every cable
Firmware and BIOS
- A single baseline across the batch, recorded by version
- Power profile, boot order, virtualisation and security settings
- Out-of-band management addressed and hardened
- Known-bad releases avoided, with the reason recorded
Configuration
- RAID or software-defined layout as specified
- Operating system or hypervisor image, or bare metal for your own provisioning
- Network configuration to your VLAN and addressing plan
- Credentials handed over separately from the hardware
Test
- Burn-in under CPU, memory, storage and network load
- Memory and storage error counters read before and after
- Power draw measured per node at load
- Failures replaced before delivery, not after
Section 02Handover
The as-built document
Every build is delivered with a document that records, per unit: serial number, exact configuration as shipped, firmware versions, management address, rack position, cable map and the burn-in result. It is the document you will want in eighteen months when a node misbehaves and nobody remembers what was in it.
The same document is what makes a warranty claim or an insurance claim straightforward, and it is what we use ourselves when you order the next batch and want it identical.