Service schedule · Waltham Cross floor

Six ways to hold hardware here. RACK

DSH LIMITED keeps a compact schedule because every line is delivered by the same floor team at 24 Felstead Road, Waltham Cross - EN8 7HB, United Kingdom (GB). A single-tenant metal lease is the smallest unit we let, a private rack suite is the largest, and the four services in between exist to keep a tenancy steady after it is live. Each is described below as a working order rather than a product badge.

Ask for the written schedule →

Book a floor walkthrough →

The order rail

Six services, each with its own working terms

Read the rail from top to bottom. The order of the lines is also the order in which a tenancy usually grows: a lease first, a suite later, then the supporting services that keep both steady.

Delivery D

Single-Tenant Metal Leases

A metal lease means one client, one physical chassis, one set of disks and one network port, with no shared hypervisor between tenants. Before delivery we agree the processor class, the memory shape, the disk arrangement and the uplink speed. The unit is then racked into a bay, labelled with the client account, and cabled into the loom with each strand recorded in the patch ledger. Leases are billed on a fixed monthly cycle with a documented refresh point so that aging hardware does not quietly become a client problem. If a workload outgrows the unit, the conversation is about a second lease or a move into a private suite, not about squeezing a shared host.

Enclosure S

Private Rack Suites

A suite is a locked half rack or full rack inside the cold aisle, let as a unit. The client receives dedicated power circuits, a dedicated switching position and a patch loom that belongs to the suite alone. Because the enclosure is private, growth happens inside the client own cage rather than through a migration. We agree a cable plan before the first unit is mounted, and we keep spare bay positions free inside the suite so a swap can happen without removing anything permanent. Suites suit clients who expect to add two or three machines a year and would rather not renegotiate space each time.

Labour H

Remote Hands Windows

A remote hands window puts one of our engineers at the client rack for a booked period, normally one to four hours. The client submits a task sheet in advance: reseat a cable, replace a drive caddy, connect a console cable, check airflow at the aisle face, photograph a label. The engineer works from that sheet and writes back a short account of what was found and what changed. Anything outside the sheet is reported rather than improvised. Windows are booked against the rack, not against a person, so continuity is kept even when a different engineer attends the second visit.

Addressing L

IP Block Assignments

Every lease or suite receives an IPv4 allocation sized to its role and an IPv6 block as standard. Reverse records are maintained by the floor team, which means a mail server or a monitoring probe can be reached by name without a second request. We keep the justification note for each block on file, so a later growth request does not have to be reconstructed from scratch. Blocks can be reassigned between machines inside a client suite when a machine is retired, and we document the change on the ticket that authorised it.

Traffic R

Bandwidth Burst Plans

A committed rate sets the floor of what the link will carry, and a burst ceiling sets the headroom above it. The pair means a launch week can pass without an unplanned invoice, while the ordinary month still bills against a predictable commitment. Traffic graphs are kept readable by the floor team and reviewed with the client before a ceiling is changed. If a workload becomes consistently bursty, we would rather discuss a larger committed rate than let the client pay overage in silence. Plans are attached to the suite or the lease, whichever carries the uplink.

Parts B

Hardware Swap Visits

When a component fails, the swap visit is the service that gets the machine healthy again. The client ships or delivers the replacement, our engineer books it in at the door, matches it to the open ticket, performs the swap at the rack and returns the failed unit under the same ticket number. Common parts such as drive caddies, power supplies and network modules are held in spare crates on site, which shortens the gap between a failure and a working machine. Clients who wish to attend can book a supervised window and watch the work at their own rack.

DSH LIMITED opens its next rack handover window on the Waltham Cross floor, and every service on this page is carried out by the same small team that keeps the aisle clear.

Process overview

How a service request moves through the floor

A request begins with a scope call, and the outcome of that call is a written schedule. The schedule names the unit, the circuits, the addressing plan, the burst ceiling and the handover date. Nothing is racked before the schedule is agreed, because a machine installed without a written plan is a machine nobody can audit later.

Once agreed, the floor team reserves a bay, prepares the labelling and stages any parts the job needs. The unit is mounted, cabled into the loom, powered on an independent circuit and checked at the aisle face. The check covers more than whether the machine boots: the front clearance, the cable labels and the patch ledger entry are all verified before the handover is declared ready.

After handover, the tenancy enters its steady state. Remote hands windows and swap visits are booked against the rack, addressing changes are documented on the ticket that authorised them, and bandwidth ceilings are reviewed at the point a client expects traffic to change. The client keeps the written trail, and so do we.

Working terms

What each service asks of the client

Metal leaseConfirmed specification
Rack suiteAgreed cable plan
Hands windowTask sheet in advance
Address blockJustification note
Burst planReviewed ceiling
Swap visitMatching replacement part

None of these asks is heavy. They exist so that the floor can act quickly on the day a client needs something, without a second round of questions while a machine sits down.

Small print, plainly

Boundaries we keep

Remote hands windows cover physical work at the rack. They do not include application support, operating system administration or debugging inside the client stack. If a task sheet strays into that territory, the engineer will say so before starting, and the work is returned to the client rather than attempted without authority.

Swap visits assume that the replacement part has been supplied and that the failed part is due back to the client. If a client asks us to dispose of hardware, that request is handled as a separate documented task with its own signed note.

Private rack suites are let with the understanding that the suite interior belongs to the client and the surrounding row belongs to the floor. That division keeps airflow honest and keeps every visit short. A client who wants to mount extra rail hardware inside a suite can do so, but the change is recorded so that a later engineer is not surprised by it.

Addressing and bandwidth plans are governed by the Terms of Service. The service page explains how each works; the legal page explains the obligations that attach to them.

Tell us which line of the schedule you need

Write down the compute shape, the traffic profile and the date you want the machine live. We will reply with the schedule and a handover window that matches.

Contact the floor team