TL;DR
-
MEP coordination in schematic design organizes a building’s mechanical, electrical, and plumbing systems relative to the architecture, establishing the equipment spaces, routing strategies, and spatial relationships that every later phase builds on.
-
Technology belongs in that framework from the first coordination meeting, since telecommunications room locations, equipment room placement, and the backbone cabling pathway all get decided during SD.
-
A technology consultant’s SD deliverables, including T-layer documents, room plans, and a requirements list for the MEP scope, let conflicts surface where they cost a drawing revision rather than a change order.
-
Architectural firms get the most value when the technology consultant joins before schematic design begins, because an engagement that starts at DD inherits decisions already made without technology in mind.
MEP coordination during schematic design establishes the framework that all other coordination work builds on. It's the phase where mechanical, electrical, and plumbing systems are first organized relative to the building's architecture – establishing equipment spaces, primary routing strategies, and the spatial relationships between building systems that will govern coordination through design development and into the construction documents.
When technology requirements are part of that framework from the start, they get built into the design instead of retrofitted, and that starts with what gets decided at schematic design.
What’s Established at Schematic Design?
Schematic design is where the primary infrastructure decisions are made. For technology systems, those decisions include:
- Telecommunications Room Locations: Where the floor-level distribution hubs sit on each floor, sized and positioned to stay within the maximum horizontal cable run distance from the devices they serve.
- Equipment Room Placement: Where the main technology equipment room sits relative to the building's power and mechanical systems, with enough space for the rack count and active equipment the project requires.
- Backbone Cabling Pathway: How the low-voltage infrastructure runs vertically through the building, through riser shafts and core penetrations coordinated with the structural and mechanical design.
None of these decisions should be made in isolation. Telecommunications room locations affect the architectural floor plan, equipment room sizing affects the MEP power and mechanical scope, and backbone cabling pathway strategy affects the structural core design and the MEP shaft allocation.
Engaging a technology consultant during SD, before the architectural and MEP decisions are made without them, helps eliminate expensive reworks later.
How Does Technology Coordination Fit Into the SD Process?
During schematic design, the technology consultant works alongside the architect and MEP engineers to establish the technology program: what systems the project requires, where they're located, and what physical requirements they have.
The technology consultant's SD deliverables typically include:
- T-layer documents describing all systems and infrastructure requirements
- Preliminary telecommunications room location plan
- Equipment room sizing recommendation
- Backbone cabling pathway strategy
- List of technology-related requirements for the MEP engineering scope
Those deliverables feed directly into the SD coordination set, which means any conflicts between technology requirements and other building systems are identified and resolved at the SD level – where they cost a drawing revision rather than a change order.
What Happens When Technology Is Missing From SD Coordination?
When technology isn't part of the SD coordination process, the architectural and MEP decisions get made without technology requirements factored in. For example, equipment rooms may get sized for the generic minimum rather than the actual technology load, or riser shafts get allocated to mechanical and electrical without reserving space for low-voltage backbone cabling.
Those decisions become the constraints within which the technology consultant has to operate during design development. Correcting an undersized equipment room at DD means negotiating with the architect for additional floor area. Adding a backbone cabling pathway to a riser shaft that wasn't designed for it means coordinating with structural on new penetrations.
While issues like this aren’t insurmountable, they’re more expensive and time-consuming than establishing the right requirements during SD.
What's Locked In When Schematic Design Ends?
Schematic design closes with a set of decisions that become progressively harder to reopen. The floor plan and core layout are approved by the owner, which fixes where telecommunications rooms and the main equipment room can realistically sit. Riser shaft allocations are divided among the mechanical, electrical, plumbing, and technology scopes, which caps how much vertical pathway the low-voltage backbone will ever have. Floor-to-floor heights and preliminary ceiling depths are set, which constrains the cable tray and conduit routing available above ceilings for the rest of the project.
Each of these carries directly into design development as a given rather than a question. A project that enters DD with technology requirements already reflected in the floor plan, shaft allocation, and ceiling strategy spends that phase refining the design. A project that enters DD without them spends it negotiating for space that other scopes already claimed, which is why the SD coordination window matters more for technology than any phase that follows.
Schematic Design FAQs
What is the role of MEP coordination in schematic design?
MEP coordination in schematic design establishes how the mechanical, electrical, and plumbing systems will share the building before any of them are designed in detail. The phase sets equipment room locations, primary routing strategies, and the spatial relationships between systems and the architecture, creating the framework that design development and the construction documents refine. Decisions made here govern every later phase, which is why SD coordination quality shows up directly in how smoothly a project runs.
What is the role of a technology consultant in schematic design?
A technology consultant’s role in schematic design is establishing the project’s technology program alongside the architect and MEP engineers: which systems the building requires, where they live, and what physical requirements they carry. Their SD deliverables typically include T-layer documents, a preliminary telecommunications room plan, an equipment room sizing recommendation, a backbone cabling pathway strategy, and a list of technology requirements for the MEP engineering scope, all of which feed the SD coordination set.
What does a technology consultant for architects deliver during SD?
A technology consultant for architects delivers the documents that let the rest of the design team plan around real technology requirements: T-layer documentation describing every system and its infrastructure needs, telecommunications room locations sized against cable run limits, an equipment room recommendation with power and cooling implications, and the backbone pathway strategy for the building core. Those deliverables give the architect concrete inputs for the floor plan and give the MEP engineer a defined scope to coordinate against.
How early in a building project should a technology consultant be engaged?
The strongest engagements begin before schematic design starts, so the technology consultant participates in the first coordination meeting rather than reacting to its outcomes. Equipment spaces, shaft allocations, and pathway strategies are all established during SD, and each one is expensive to revisit afterward. An engagement that begins at design development can still add value, but it operates inside constraints that were set without technology requirements on the table.
What technology decisions get locked in during schematic design?
Schematic design locks in the decisions with the longest consequences: telecommunications room and main equipment room locations, the centralized or distributed architecture those rooms support, riser shaft allocation for the low-voltage backbone, and the ceiling depths that determine available pathway space. Changing any of them later means renegotiating approved floor plans or coordinating new structural penetrations, which is why these items anchor the SD portion of any technology coordination effort.
When To Engage a Technology Consultant for SD Coordination
Architectural firms should engage a technology consultant before schematic design begins, so they're part of the design team from the first coordination meeting. An engagement that starts at DD – after the floor plan and primary equipment spaces are established – is starting after the decisions that most affect technology coordination have already been made.
TMC brings vendor-neutral technology expertise to that first coordination meeting, so the architect and MEP engineer have the right requirements in front of them from the start. Reach out today to learn more about how we can support your next technology-intensive building project.
