Start a data center value-chain map with what the expansion must deliver, not a list of companies.
This hypothetical example separates IT equipment, facility systems and network connections from the work of designing, installing and operating them—and leaves unverified contracts blank.
Data center fundamentals series
What does the hypothetical expansion need to deliver?
A useful value-chain map starts with outcomes: run an application, store its data and connect it to users. It then separates the IT equipment and facility systems that make those outcomes possible from the work needed to design, install and operate them. That classification does not identify a supplier or contract partner.
Suppose an organization wants to add computing and storage for a new application in a server room it already operates, while securing a connection to an external network. This is a hypothetical request, not a real project.
The first questions concern the application and its storage needs, the endpoints and distances of its connections, and initial and future loads. Without those answers, server counts, electrical capacity and link speeds remain unknown.
The Fiber Optic Association — The FOA Reference For Fiber Optics - Fiber Optic Network Design
U.S. Department of Energy — Best Practices Guide for Energy-Efficient Data Center Design
IBM — What Is a Data Center? | IBM
What belongs in each row of the map?
The table is a worked classification of that request, not a standard purchasing sequence. “Unconfirmed” means that the example supplies neither an assigned party nor a document establishing its responsibility.
Run the application and retain data
- Related elements
- Servers, storage and internal network
- Design, installation or operating work
- Choose a configuration; establish deployment and management responsibilities
- Party and evidence to confirm
- IT design and operating parties; scope of work
- Still unknown
- Equipment counts, storage configuration and capacity
Supply power
- Related elements
- Incoming supply and distribution; backup source, UPS or PDU where needed
- Design, installation or operating work
- Check whether existing infrastructure can serve the added load and which equipment needs UPS protection
- Party and evidence to confirm
- Electrical design and installation parties; design documents
- Still unknown
- Load, capacity and protection scope
Remove added heat
- Related elements
- Airflow and cooling systems
- Design, installation or operating work
- Assess initial and future loads and the suitability of existing airflow
- Party and evidence to confirm
- Facility design and operating parties; design documents
- Still unknown
- Heat load, cooling capacity and method
Connect systems and users
- Related elements
- Internal network and building entrance to an external network
- Design, installation or operating work
- Define endpoints, distance, speed and transmission equipment; coordinate the connection
- Party and evidence to confirm
- Network designer and external connection provider; scope of work
- Still unknown
- Link count, speed, cable type and interfaces
Complete and accept installation
- Related elements
- Cable routes and terminations if fiber installation is in scope
- Design, installation or operating work
- Record the route and connections; plan tests and capture acceptance results
- Party and evidence to confirm
- Installer; test plan and acceptance documents
- Still unknown
- Installation scope and link-specific tests
Keep the service operating
- Related elements
- IT and facility systems; connection records where applicable
- Design, installation or operating work
- Assign maintenance, monitoring, change and incident responsibilities
- Party and evidence to confirm
- Operating parties; contract and operating records
- Still unknown
- Division of continuing responsibilities
The unresolved column matters as much as the equipment column: it prevents a plausible component list from being mistaken for an approved design or an awarded contract.
Which equipment choices does the request leave open?
For IT, distinguish servers that run the application, storage for its data and the network that connects systems and users. Storage need not mean drives attached to servers. Direct-attached storage (DAS), network-attached storage (NAS) and a storage area network (SAN) are different configurations that can coexist; the request does not select one.
For facility power, keep the supply and distribution path separate from the IT equipment it serves. Backup sources, uninterruptible power supplies (UPSs) and power distribution units (PDUs) may be relevant, but the design must establish which loads need UPS protection and whether the existing path has capacity.
Cooling likewise requires an assessment of added heat and airflow, not an automatic choice of technology. Direct liquid cooling transfers heat to fluid near its source; some liquid-cooled approaches still need air cooling for remaining heat. Nothing in this example establishes that liquid cooling will be installed.
Finally, distinguish connections among servers and storage inside the facility from the connection through the building entrance toward an external network. As the Fiber Optic Association’s design guidance explains, communications requirements, distance and transmission equipment inform cable choices. Without defined endpoints and requirements, neither a fiber type nor an external connection provider can be assigned here.
Why map design, acceptance and operations separately?
An equipment list does not say who will turn requirements into an installable design. If a fiber connection is part of the project, its design may involve choosing a route and transmission equipment, coordinating with facility and electrical personnel, and checking whether permissions or inspections are needed. Those are tasks to allocate, not evidence that one firm performs them all.
Nor is delivery of components the same as acceptance of an installed link. For fiber work within scope, route and termination records, a test plan agreed during design, and results incorporated into acceptance documentation form a distinct deliverable. The particular tests depend on the link and agreed scope.
After acceptance, maintenance, monitoring, changes and incident response still need owners; fiber records and restoration plans may also need upkeep. Do not assume that the installer becomes the operator.
Can the map identify the companies that benefit?
Not from this example alone. It begins with a self-operated server room, but a different service model would change what must be assigned. Colocation provides space, power, cooling and network connectivity for customer-owned IT; whether management services are included needs checking.
In a managed arrangement, a provider can administer dedicated leased servers, storage and networking equipment. Cloud services instead provide access to shared IT resources over the internet. These models do not imply identical ownership, deployment or operating responsibilities.
Knowing what a UPS, storage system or network link does is not evidence of who supplied it, who contracted for it or whose revenue it generated. When applying the map to an actual project, use design documents, the scope and contract, and the chosen ownership model to fill in the responsible parties and acceptance and operating duties.
Until then, blank company fields are useful: they show precisely which claims still need verification.
The Fiber Optic Association — The FOA Reference For Fiber Optics - Data Centers -
Sources
Related reading
