By GlobalITN · 17 November 2026

What information is needed to scope rack and stack in a Singapore data centre?

To scope rack and stack accurately, give the provider the equipment list, the rack and position for each device, the power and patching plan, the site access arrangements and the evidence you need at handover. These details let the engineer check tools, accessories and dependencies before the visit. The agreed scope and site conditions determine what can be completed.

Illustration of Equipment and work pack, Rack installation, using scope equipment and workflow composition

The equipment list

List every item to be installed, with:

  • make, model and quantity
  • rack units and depth
  • rail kit or mounting method
  • power supplies and power cable type
  • serial numbers, if you want them recorded at install

Note anything still in transit and who receives deliveries at the data centre. Most Singapore colocation facilities have their own loading-bay and goods-receiving rules.

Illustration of Every delivered item, Model, serial and owner, using inventory equipment and workflow composition

The rack elevation

Provide a rack elevation showing which unit each device occupies, plus blanking panels, cable managers and shelves. If the rack already has equipment, include a current photo or elevation so the engineer can see the free space and existing cabling.

Check depth and weight. Deep servers or storage may not fit a shallow rack, and heavy devices should go low in the rack.

Illustration of Assigned rack units, Free space and cabling, using rackelevation equipment and workflow composition

Power

State the power feeds available to the rack (A and B feeds where redundant), the PDU type and the outlets each device should use. Devices with dual power supplies should normally be connected to separate feeds. Confirm the rack’s power budget can take the new load before the visit.

Illustration of Feed A, Feed B, Verify outlets and rack power budget, using power equipment and workflow composition

Patching and labelling

Provide a patching schedule: each port on each device, the cable type and length, and the destination port. Include cross-connects, uplinks to your switches and links to carrier equipment.

Agree a labelling standard for cables and devices. Labels that match your documentation save time on every future visit.

Add a service or VLAN reference where relevant, and name who will enable a switch port if that work is outside the installer’s scope. Record unavailable ports, unconnected cables and temporary connections. A photograph supports the cable schedule but does not replace endpoint records.

Illustration of Source ports, Destination mapping, using patching equipment and workflow composition

Access and site rules

  • Data centre name, hall, cage and rack ID
  • Access request process and who approves it
  • Named engineer details the facility needs in advance
  • Working hours, escort rules and photography rules
  • Delivery reference numbers

Missing access approval is a common reason for a wasted visit.

Illustration of Visit approval, Escort and entry, Site rules, using siteaccess equipment and workflow composition

Configuration and testing

Decide who configures the equipment. Some customers pre-stage configuration remotely; others want the engineer to power on and connect the device so the remote team can take over. State the tests that confirm success, such as power-on status, link lights, console access or a remote team confirming reachability.

Use a numbered installation sequence and stop if the equipment, rack elevation, port labels or power arrangement differs from the approved plan. Record each test’s expected result, actual result, tester, time and status. Mark an unperformed test as not tested, not passed. A failed test does not expand the installer’s authority.

Illustration of Power and links, Remote acceptance, using test equipment and workflow composition

Handover

Ask for:

  • photos of the rack front and rear (where the facility permits)
  • the updated rack elevation and patching record
  • serial numbers of installed equipment
  • a list of anything outstanding and who owns it

Packaging removal is often forgotten; say whether the engineer should take it away.

Identify the revision or date of the final elevation and cable schedule, any approved deviations, removed parts and remaining dependencies on another team. The operations owner should review the pack before job closure. Physical installation sign-off does not establish that an application, monitoring or wider service is ready.

Illustration of Records and permitted photos, Completed tests, using handover equipment and workflow composition

How GlobalITN helps

GlobalITN has supported Singapore businesses since 2013, supplying and renewing Cisco Meraki and Fortinet licences and hardware, with our own engineers across Singapore, Hong Kong, Australia and Vietnam for survey, deployment and on-the-ground support. Our engineers carry out rack and stack, cabling and device installation in Singapore data centres, working to your elevation and patching plan.

See our guide to what smart hands services should include and how to choose an APAC IT deployment partner, our Meraki and FortiGate deployment services, or send your equipment list through our Get a quote / talk to an engineer.

Frequently asked questions

Can you work from our existing documentation?

Yes. An elevation and patching schedule in any clear format is enough to plan the job.

Do you configure the equipment?

That is agreed per job. The engineer can install and connect only, or carry out configuration against an approved plan.

What if the equipment does not fit?

The engineer stops and contacts your named lead. Agree in advance who can approve changes on the day.

Can you handle deliveries?

Deliveries are arranged through the facility’s goods-receiving process. Provide delivery references when you book.