Brownfield Industrial Extension: 20,000 m² Inside an Operating Facility

Adding 20,000 m² to an existing 245,000 m² production facility is not an isolated building exercise. It is an integration project inside a much larger operational environment. New systems must connect with existing utilities, production requirements, access routes, safety provisions, equipment spaces, and maintenance strategies without losing control of the interfaces between them.

TEBIN supported this European brownfield industrial extension through an integrated Building Information Modeling workflow. The delivery included 8 coordinated BIM models and more than 800 drawings developed for basic and tender design. Mechanical, electrical, plumbing, and fire protection information was managed within the same digital process, allowing the team to coordinate geometry, calculations, quantities, and documentation across several locations.

Why brownfield extensions are different

A greenfield project begins with a site and a new design basis. A brownfield extension begins with an existing facility that already has physical constraints, utility networks, operating rules, and established production logic. The extension must connect to that environment rather than overwrite it.

Each new decision can affect an existing condition. A mechanical route may require a structural opening, compete with a cable route, cross a fire compartment, or reduce maintenance access. New electrical demand must be considered against the available distribution strategy. Drainage and water connections depend on existing levels, capacities, and connection points. Equipment placement influences ventilation, power, controls, supports, and replacement access at the same time.

This makes interface management central to the design. The project team needs a reliable way to see how disciplines and existing conditions interact, record open decisions, and keep documentation aligned as the design develops.

Scope of the coordinated design and engineering work

The project scope covered heating, ventilation, and air conditioning systems together with air-exchange calculations; fluid systems; water supply and sewerage networks; electrical load schedules; lighting analysis; cable sizing; and fire-fighting system coordination. Equipment spaces, primary service routes, access zones, and connections between systems were developed as shared coordination subjects.

These workstreams could not be treated as independent layers. Airflow requirements influence duct dimensions and plant space. Electrical loads influence distribution equipment and cable containment. Water and sewerage routes depend on levels and structural penetrations. Fire protection requirements interact with architecture, ventilation, electrical supply, and operational safety. Coordinating these relationships while the design is still developing is more useful than identifying them after separate discipline packages are complete.

The design was produced across several locations, which increased the importance of consistent model structure, exchange rules, naming, review cycles, and issue communication. A shared digital workflow gave distributed teams the same current design context and reduced reliance on disconnected files or decisions held in individual communication threads.

Eight BIM models as one coordination environment

The 8 discipline models were brought together as a federated multidisciplinary model. Federation allowed each discipline to retain responsibility for its own information while giving the project team a combined view for coordination and review.

The coordinated environment was used to examine service routes, equipment locations, access requirements, and discipline interfaces. Geometric clash detection was one part of the process, but coordination also required engineering judgement. A route can be free of direct clashes and still be difficult to install or maintain. Reviews therefore needed to consider usable space, sequence, access, and the relationships between systems, not geometry alone.

The model also provided a common reference for discussions across locations. Instead of reviewing discipline decisions only through separate drawings, teams could examine the same interface in context, assign responsibility, and carry the agreed resolution back into the relevant model and documentation.

From coordinated models to 800+ drawings

More than 800 drawings were developed from the coordinated workflow. The quantity matters, but consistency matters more. On a large industrial project, drawings, models, schedules, calculations, and bills of quantities must describe the same design.

Basic and tender design packages were developed from the same model-based information. This supported alignment between plans, sections, equipment layouts, service routes, and schedules as the documentation set grew. Bills of quantities were extracted from coordinated models, reducing the need to rebuild quantity information manually in a separate process.

Model-based extraction does not make quantities automatically correct. Model elements still need suitable classification, parameters, and quality checks. The value comes from maintaining a traceable relationship between the designed object and the reported quantity, so revisions can be reviewed against the current coordinated information.

What made the workflow useful

For this project, BIM was not used only to visualise the extension. It served as the shared infrastructure connecting distributed design teams, multidisciplinary interfaces, project reviews, quantities, and a large documentation package.

The workflow created a consistent place to coordinate decisions before they were issued across hundreds of drawings. It also made the design easier to review as one industrial system rather than as a stack of unrelated discipline outputs.

Coordinating across locations and regulatory frameworks

Producing the design across several locations added a layer of complexity beyond the technical coordination already described. Distributed teams working across different time zones and working cultures meant that a decision made by one discipline group had to reach every other affected team reliably and quickly — a feedback loop that is forgiving on a single-site project and far less forgiving when the next discipline review happens the following morning in a different time zone. That is precisely why consistent model structure, exchange rules, and issue communication mattered as much as the engineering itself: without them, the distance between teams would have slowed the coordination the federated model was built to speed up.

Regulatory compliance added a second layer specific to industrial brownfield work of this kind. An existing operating facility carries established safety, fire, and process standards that a new extension has to integrate with, on top of whatever code framework applies to the new construction itself. Understanding which standards govern the existing facility's systems, and how the new scope has to interface with them, has to happen before detailed design starts — not as a check applied to a finished design.

A practical lesson for brownfield delivery

Large brownfield extensions demand disciplined information management because the new scope is always connected to something that already exists. Existing constraints must be understood, assumptions must remain visible, and changes must be reviewed across every affected discipline.

The practical lesson from this 20,000 m² extension is straightforward: model federation is most valuable when it supports real design and engineering decisions. Eight models and more than 800 drawings become manageable when they are produced through one coordinated workflow, with interfaces treated as part of the design rather than problems left for construction. The same coordination discipline that resolves a clash between two systems is what keeps a distributed, cross-location team working from one current design — distance and disciplines are both interfaces, and both have to be managed the same way.