Understand multidisciplinary engineering design, how to coordinate disciplines and interfaces, which deliverables to require, and how to procure an integrated engineering solution.

Check it out!

A multidisciplinary engineering design is one in which two or more technical disciplines must be developed in a coordinated manner to produce a single, coherent, buildable solution. The value of the multidisciplinary approach is not simply placing electrical, civil, structural, HVAC, telecommunications, electronic security, automation, or other specialties under the same contract. It lies in treating the interfaces among those disciplines as part of the design itself.

In simple projects, each discipline may have few dependencies. In complex facilities, renovations, modernization programs, critical environments, and brownfield projects, one team’s decision changes assumptions for several others: electrical loads affect switchboards and generators; equipment changes cooling requirements; cable routes compete for space with piping and HVAC; automation depends on points and protocols from other systems; electronic security depends on infrastructure, networks, and power; architecture and civil works constrain all of these solutions.

For this reason, multidisciplinary design is not synonymous with a “package containing several designs.” It is an integrated process of requirements, engineering, coordination, interdisciplinary design coordination, review, and interface control until the complete solution can be procured, built, tested, and handed over without material contradictions among disciplines.

What Characterizes a Multidisciplinary Engineering Design

Multidisciplinarity exists when a decision cannot be made correctly by looking at only one specialty. The project needs a common architecture and formal mechanisms for integrating contributions from different professionals.

Typical examples include:

  • corporate and public buildings with electrical, data, HVAC, security, and automation systems;
  • data centers and technical facilities where power, cooling, telecommunications, detection, security, and physical infrastructure are interdependent;
  • industrial facilities involving electrical systems, instrumentation, controls, mechanical systems, utilities, and safety;
  • retrofits in occupied buildings, where the existing condition strongly constrains the solution;
  • technology infrastructure modernization across multiple sites;
  • mission-critical projects in which availability and continuity must be addressed across disciplines.

In these cases, BIM-based engineering design can add a digital layer for coordination and information management. BIM, however, is not a prerequisite for multidisciplinary engineering. Disciplines can be coordinated effectively in 2D or hybrid workflows; the core issue is integration of requirements, decisions, and interfaces.

A typical coordination structure connects project requirements to engineering coordination, distributes them across electrical, civil/architectural, HVAC, telecommunications/network, security, and automation disciplines, and then reconverges those disciplines through coordinated interfaces into an integrated, buildable design.

Multidisciplinarity, Coordination, and Design Coordination Are Different

The concepts are related but not equivalent.

Multidisciplinarity describes the presence and interdependence of several disciplines within the project. Design coordination is the function that organizes decisions, responsibilities, information, schedules, and interfaces among those disciplines. Interdisciplinary coordination or design compatibility review is the verification activity used to identify physical, functional, or documentary conflicts and confirm that the designs can coexist and be built together.

Concept Main question
Multidisciplinary design Which disciplines must contribute to one integrated solution?
Design coordination Who integrates decisions, responsibilities, information, and interfaces?
Interdisciplinary coordination Are the designs coherent with each other and buildable together?
Design Review Does the solution meet requirements, standards, performance objectives, and design criteria?

The content on Engineering Design Coordination explores governance among teams in greater depth. BIM Design Coordination addresses the specific process of identifying and resolving interferences among disciplines.

Design Should Begin with Requirements, Not Drawings

When each discipline begins from its own assumptions, conflicts appear late. A structured requirements program creates a common baseline for performance, capacity, interfaces, and constraints before discipline-specific design begins.

When every discipline receives only a generic request to “prepare its design,” each team tends to develop a locally correct solution that may not be coherent with the overall project.

Integration starts before drawing production. The team must consolidate what the asset or facility must accomplish: capacity, users, loads, availability, constraints, expansion, spaces, performance levels, external interfaces, standards, operations, maintenance, and acceptance criteria.

The Engineering Requirements and Needs Program can provide the structured input for this phase. It reduces the risk that different designers adopt incompatible assumptions about the same problem.

Cross-Cutting Requirements Must Reach Every Discipline

Some requirements belong to the project as a whole rather than to one discipline. Examples include:

  • continuity of operations during construction;
  • minimum infrastructure availability;
  • future growth;
  • energy efficiency;
  • people and asset safety and security;
  • maintenance access;
  • equipment standardization;
  • interoperability;
  • redundancy;
  • documentation and identification;
  • testing and commissioning requirements.

If these criteria are distributed in a fragmented manner, each specialty may partially satisfy the demand while the overall solution fails.

Existing-Condition Surveys Are Critical in Brownfield Projects

In existing facilities, coordination without a reliable survey means coordinating assumptions. Site Surveys and engineering surveys reduce uncertainty about actual routes, capacities, technical spaces, and interfaces.

In existing buildings and operating facilities, multidisciplinarity becomes even more sensitive because the new solution must coexist with assets, structures, and systems already in service. One survey error can contaminate several disciplines at once.

Before renovation or modernization design begins, the project may require a Site Survey and an Engineering Existing-Conditions Survey. The purpose is not merely to “measure the building,” but to capture conditions that affect design: available capacities, routes, technical spaces, switchboards, shafts, networks, connection points, interferences, existing equipment, apparent condition, documentation, and access constraints.

Lack of this information leads to one of the most expensive multidisciplinary design problems: each discipline designs against a different assumed reality.

How to Define the Required Disciplines

There is no universal list of disciplines that every multidisciplinary project must include. The composition should derive from the need, facility characteristics, and identified interfaces.

An initial assessment can consider:

  1. which functions the facility or project must provide;
  2. which systems will be installed, renovated, or retained;
  3. which existing systems will be affected;
  4. which standards and authorities apply;
  5. which systems depend on power, networks, cooling, or physical infrastructure;
  6. which disciplines require their own calculations or sizing;
  7. which approvals and permits will be required;
  8. which systems must integrate during operation.

In an electronic security modernization, for example, the apparent core may be CCTV and access control, yet the project may also require telecommunications, structured cabling, electrical systems, pathways, architecture, technical-room HVAC, UPS, servers, integration, and cybersecurity. Procuring only the “main” discipline can leave interfaces without a defined technical owner.

Interface Matrix: The Document That Eliminates Gray Areas

In projects with several disciplines, many failures do not clearly belong to one team. They originate at boundaries. An interface matrix turns those boundaries into explicit responsibilities.

A useful matrix can record:

Interface Origin Destination Information/deliverable Responsible party Required date
Equipment loads Special systems Electrical Power and duty cycle Systems discipline Before electrical sizing
Heat dissipation IT/security HVAC Thermal load Systems discipline Before thermal calculations
Cable pathways Telecommunications Civil/architecture Routes and occupancy Telecommunications Before coordination review
Automation points HVAC/electrical Automation I/O and signal list Originating discipline Before programming
Technical space All disciplines Architecture Area, access, maintainability Coordination Before layout freeze

This mechanism is valuable because it makes visible who depends on whom and when. Coordination stops reacting only to conflicts already drawn and starts managing production of the information needed by downstream disciplines.

Technical Coordination Is Not a Coordination Meeting

Meetings are only one instrument. Engineering coordination means managing decisions and information that cross discipline boundaries.

The coordinator should control, among other matters:

  • common assumptions;
  • responsibility matrix;
  • interfaces;
  • deliverable schedule;
  • status of input information;
  • open items and RFIs;
  • review comments;
  • requirements changes;
  • technical decisions;
  • document revisions;
  • maturity of each package;
  • criteria for releasing each stage.

Coordination must also distinguish geometric conflicts from functional conflicts. Two pipes may not physically clash and still leave equipment without maintenance access. A rack may fit in a room and still exceed available electrical or thermal capacity. A system may operate independently and still lack the interface required for automation or supervisory control.

For this reason, multidisciplinary design requires engineering analysis beyond clash detection.

BIM Improves Coordination but Does Not Replace Engineering

BIM increases the ability to coordinate information and visualize interfaces, but results depend on clearly defined requirements, responsibilities, and approval processes. Modeling without governance does not resolve multidisciplinary decisions.

ISO 19650 establishes principles and processes for information management throughout the asset life cycle and, during delivery, provides a structured process for organizing and exchanging project information. This is particularly valuable in environments involving many actors, models, and documents.

In Brazil, the national BIM strategy also encourages collaborative adoption of BIM processes and technologies. For Brazilian public procurement, Law 14,133/2021 provides for preferential adoption of BIM or similar integrated technologies and processes when appropriate to the object.

A federated model, however, does not automatically resolve engineering decisions. BIM may reveal that a cable tray crosses an HVAC duct, but it does not determine which system should move, which alternative is technically superior, what maintainability impacts exist, or which party owns the revision. Those remain coordinated engineering decisions.

BIM-based engineering design is most effective when information requirements, responsibilities, levels of development, and approval workflows are defined from the outset rather than when finished drawings are merely converted into 3D models.

Which Deliverables Should a Multidisciplinary Design Produce?

Deliverables depend on the design stage and disciplines, but the package must make it possible to understand not only individual components but also the integration of the complete project.

Typical deliverables may include:

  • discipline-specific and integrated design narratives;
  • design calculations;
  • plans, sections, details, and diagrams;
  • technical specifications;
  • equipment and material schedules;
  • point and signal lists;
  • architecture and integration diagrams;
  • interface matrix;
  • requirements matrix;
  • BIM models, when applicable;
  • coordination reports;
  • technical review reports;
  • quantity takeoffs and cost estimates;
  • testing and acceptance criteria;
  • documentation required for permits and approvals.

Detailed Engineering Design addresses the required level of definition when the solution must be ready for execution.

A Set of Drawings Is Not Necessarily a Coordinated Design

Having drawings from every discipline can create a false sense of completeness. Maturity must be assessed by checking consistency across documents.

Useful checks include:

  • are equipment loads correctly reflected in the electrical design?
  • does cooling capacity include the specified equipment?
  • do pathways have adequate space and occupancy?
  • do layouts preserve maintenance and replacement access?
  • do network and power points match equipment positions?
  • do diagrams correspond to floor plans?
  • do quantity takeoffs reflect the latest revision?
  • are specifications consistent with narratives and drawings?
  • are redundancy requirements reflected in every affected discipline?

These checks reduce the probability of discovering incompatibilities only during construction.

Interdisciplinary Coordination Should Be Continuous, Not Final

When coordination is left until the end, disciplines have already invested significant effort in consolidated solutions, and any change generates cascading rework. An incremental process is more effective.

One possible sequence is:

  1. freeze the minimum requirements and assumptions for the stage;
  2. develop discipline concepts;
  3. review high-impact interfaces;
  4. consolidate layouts and technical spaces;
  5. develop calculations and sizing;
  6. perform intermediate coordination reviews;
  7. review requirements and constructability;
  8. close the package for the next stage;
  9. record remaining open items and responsible parties.

BIM coordination should operate as part of this development cycle rather than as a geometric audit performed after every decision has already been frozen.

How to Control Changes Across Several Disciplines

In multidisciplinary design, a change is rarely local. If equipment power changes, it may affect circuits, switchboards, UPS, generators, heat dissipation, and infrastructure. If equipment location changes, it may affect pathways, civil works, architecture, networks, and maintenance access.

Change control should answer four questions:

  • what changed?
  • why did it change?
  • which disciplines are affected?
  • which documents and calculations must be revised?

Every significant decision should remain traceable. Without that traceability, some disciplines incorporate the change while others continue designing against the previous revision.

Requirements, Evidence, and Acceptance Criteria Management and Process, Workflow, and Technical Approval Management can provide this governance in more complex projects.

How to Procure a Multidisciplinary Engineering Design

The procurement scope should make clear that the object is production of one integrated solution, not the administrative sum of independent disciplines. The scope should establish coordination, interfaces, responsibilities, and review criteria.

Points that deserve explicit definition include:

  • included and excluded disciplines;
  • expected design stage;
  • input documents provided by the Owner;
  • surveys included in the scope;
  • applicable standards and references;
  • responsible professional engineers;
  • overall design coordination;
  • interface matrix;
  • review and interdisciplinary coordination methodology;
  • common information-sharing environment;
  • native and interoperable file formats;
  • comment and revision cycles;
  • technical meetings and formal decisions;
  • acceptance criteria for each deliverable;
  • quantity takeoffs, cost estimates, and complementary documentation.

If BIM is required, uses, information requirements, naming standards, model structure, responsibilities, and deliverables should also be defined. Simply requiring “a BIM design” is insufficient to define the service.

How to Evaluate Engineering Design Proposals

Lowest price alone does not show whether a team can coordinate a complex object. The technical proposal should demonstrate understanding of multidisciplinarity and the integration method.

Useful evaluation points include:

  • experience with projects having comparable interfaces;
  • team composition and seniority;
  • formal technical coordination responsibility;
  • survey and assumption-validation methodology;
  • interface management method;
  • design review and QA/QC procedure;
  • collaboration tools;
  • interdisciplinary coordination strategy;
  • change management approach;
  • clarity of deliverables;
  • technical hours and effort consistent with complexity.

Technical Procurement Support and Engineering Bid Evaluation can support the Owner when methodologies and teams must be compared rather than only formal qualification documents.

Main Failures in Multidisciplinary Design

Failure Typical effect
Disciplines start with different assumptions Structural inconsistencies and rework
No defined coordinator Ownerless decisions and recurring open items
Insufficient existing-condition survey Designs incompatible with field conditions
No interface matrix Gaps between scopes
Coordination performed only at the end High volume of late revisions
Changes without impact analysis Documents at contradictory revisions
BIM used only for 3D modeling Attractive model but weak engineering integration
Vague acceptance criteria Difficulty approving or rejecting deliverables
No integrated design document set Contradictions among narratives, schedules, and drawings

These failures show why coordination should be procured as an explicit technical activity with its own responsibilities and deliverables.

When Engineering Consulting Adds the Most Value

The need for independent support increases when the Owner manages many sites, must consolidate corporate standards, faces poorly documented existing facilities, coordinates several designers, or intends to procure a complex technical package.

Engineering consulting can act before design by structuring the demand and requirements; during development by coordinating interfaces and performing Design Reviews; before procurement by checking design and cost-estimate maturity; and during implementation by monitoring changes, quality, testing, and acceptance.

This approach is consistent with engineering consulting applied to the Owner’s technical decisions: protect the Owner’s decision-making throughout the life cycle rather than merely produce isolated documents.

Final Considerations

Multidisciplinary engineering design is a system of interdependent decisions. Final quality depends less on the number of contracted disciplines than on the ability to make them share requirements, information, spaces, assumptions, interfaces, and acceptance criteria.

A technically coordinated project begins with clear requirements, understands existing conditions, defines responsibilities, controls interfaces, coordinates disciplines progressively, and maintains change traceability. BIM can strengthen this process, particularly for information management and spatial coordination, but it does not replace engineering analysis or governance among specialists.

For the Owner, the central question should not be only “which designs do I need to procure?” but also “who will be responsible for ensuring that all these designs form one buildable solution?” This integration responsibility is what distinguishes a true multidisciplinary design from a collection of separately delivered disciplines.

When the Owner needs to integrate several specialties, review solutions, and preserve decision traceability, engineering consulting can provide an independent layer of coordination, review, and governance.

Technical References

[1] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including BIM — Information management — Part 1: Concepts and principles. Available at: https://www.iso.org/standard/68078.html

[2] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 19650-2:2018 — Organization and digitization of information about buildings and civil engineering works, including BIM — Information management — Part 2: Delivery phase of the assets. Available at: https://www.iso.org/standard/68080.html

[3] BRAZIL. Decree No. 11,888 of January 22, 2024. National Strategy for Dissemination of Building Information Modelling in Brazil — BIM BR Strategy. Available at: https://www.planalto.gov.br/ccivil_03/_ato2023-2026/2024/decreto/d11888.htm

[4] BRAZIL. Law No. 14,133 of April 1, 2021. Public Procurement and Administrative Contracts Law. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm

Frequently Asked Questions

What is a multidisciplinary engineering design?

It is a design in which several technical disciplines must be developed and coordinated as parts of one solution, sharing requirements, assumptions, interfaces, information, and acceptance criteria.

Does multidisciplinary design have to use BIM?

No. Multidisciplinarity is a characteristic of discipline integration. BIM can improve spatial coordination, collaboration, and information management, but multidisciplinary designs can also be developed in 2D or hybrid workflows when technical coordination is effective.

What is the difference between design coordination and interdisciplinary coordination?

Design coordination is the broader process of organizing decisions, responsibilities, schedules, information, and interfaces. Interdisciplinary coordination is a specific verification activity used to identify physical, functional, and documentary conflicts among designs.

Who should coordinate a multidisciplinary design?

There should be formal technical coordination responsibility held by a professional or team with a system-wide view of the project and authority to manage interfaces, open items, revisions, and decisions among disciplines.

Which disciplines belong in a multidisciplinary design?

It depends on the object. They may include civil, architecture, structural, electrical, lightning protection, HVAC, plumbing, telecommunications, cabling, electronic security, automation, networks, fire protection, and any other specialties required by the project outcome.

How can an Owner determine whether the multidisciplinary design is ready for procurement?

In addition to checking completeness within each discipline, the Owner should assess cross-document consistency, interfaces, coordination, quantity takeoffs, requirements, acceptance criteria, cost estimates, and open items. Readiness must be evaluated as an integrated whole, not document by document.

Additional Technical Materials

Related Solutions

Related Services

Key Content on the Topic

Related Technical Content