Powered shell
The building foundation for your fit-out.
Bring your preferred fit-out and equipment strategy to a dedicated building with clearly defined campus and infrastructure interfaces.
Delivered condition
Understand the shell before planning the fit-out.
Powered shell can describe different delivered conditions. The useful question is exactly what will be complete, energized, tested, and handed over. ARX's proposed scope defines the building and infrastructure interfaces that support the customer-led work.
Scope
What the shell scope should define.
| Scope area | What to define |
|---|---|
| Base building | Structure, envelope, access, loading, and other agreed building provisions. |
| Power interface | Delivery point, capacity basis, protection, metering, and remaining electrical work. |
| Mechanical interface | Agreed cooling provisions, connection points, and customer fit-out responsibilities. |
| Connectivity | Campus pathways, entry arrangements, and service demarcations. |
| Acceptance | Tests, records, defects process, and conditions for transfer. |
| Operations | Who maintains each system before, during, and after fit-out. |
Coordination
Coordinate both delivery programs.
The campus works and customer fit-out must meet at the same technical boundary. Align design information, long-lead items, access dates, testing, and construction interfaces early enough to support the intended deployment.
Campus services
Pair physical control with selected campus services.
Connectivity coordination, access processes, and operating support can be evaluated alongside the shell. Services are defined for the project rather than assumed to accompany the building.
Define the shell and your fit-out boundary.
Email our team with your fit-out approach, building size, power requirement, and the work your team plans to deliver.
Or email info@arxdatacenters.com