Documentation

Procedures for every hardware handoff.

Use these guides to prepare, ship, connect, operate, and remove customer-owned hardware at Helixrack LLC.

Before you ship

Approval applies to the exact machine.

Start with the manufacturer, model, rack height, expected power, power-supply configuration, network needs, and anything non-standard about the chassis.

  • Confirm the chassis height, depth, weight, rails, and airflow direction.
  • Provide expected and peak power draw, input requirements, and PSU count.
  • Describe GPU, storage, network, or cable requirements that affect fit.
  • Wait for written approval and the current receiving label before shipping.

Receiving

Protect the server and preserve its identity.

Use a rigid box or pallet appropriate for the server's weight. Immobilize rails and loose components, protect drive bays and rack ears, and place the approved shipment reference on the outer package.

Current published process

Delivery confirmation

The exact label, receiving window, shipment reference, and condition-record scope are confirmed in writing for the approved delivery.

Review receiving and intake

Going live

Inspection first, credentials last.

Installation timing and test scope depend on the approved configuration, shipment condition, facility fit, and written handoff. The quote or intake approval identifies any committed target.

Inspect

Identity and condition

Chassis condition, expected components, rail fit, power supplies, and management access are checked against intake.

Test

Agreed checks

The approved scope identifies which condition, power, management, storage, memory, or load checks will be performed before handoff.

Handoff

Access and network

You receive the approved network details, facility assignment, service start, and secure remote-management handoff defined for the deployment.

Open the network handoff guide and sample record

Ready for a fit check?

Send the exact hardware details before arranging delivery.

Send server specs