Airport modernization projects depend on accurate models, but airports are difficult environments to model. They combine active passenger areas, dense building systems, security requirements, operational workflows, and phased construction in spaces that often cannot stop functioning while renovation work moves forward.
That makes the connection between real field conditions and project models especially important. When airport teams design, coordinate, or renovate using outdated information, small gaps can quickly become larger issues for construction, operations, maintenance, or future upgrades.
Hexagon Multivista helps airport teams address that challenge through Hexagon Multivista Create services, which can turn captured conditions into models, documentation, and deliverables that support design, VDC, construction, handover, and long-term facility planning.
As Malena Maceri, Architect and Project Manager, Hexagon Multivista, explains:
“What changes most in airport projects is the number of stakeholders involved. Modeling, coordinating, and documenting may follow familiar methods, but the coordination challenge is much greater because so many more people and requirements are part of the process.”
Airport modeling is not only a technical exercise
At a basic level, modeling an airport may use many of the same tools and standards as modeling other AECO projects. Teams still need accurate geometry, clear documentation, coordinated systems, and reliable outputs that different stakeholders can use.
The difference is the environment around that work.
Airport projects often involve owners, airport operations teams, design teams, consultants, general contractors, trades, safety stakeholders, security authorities, and public agencies. Decisions may need to account for construction requirements, passenger circulation, airline operations, restricted access, emergency egress, maintenance needs, and future operational upgrades.
That changes the pressure on the model. The model is not only a design or coordination artifact. It becomes a shared reference point that helps different teams align around what exists, what is changing, what needs to be protected, and what must remain operational.
Dense systems make current information essential
Airports are dense, system-heavy buildings. Mechanical, electrical, and plumbing (MEP) systems may share space with fire protection, communications, security infrastructure, baggage handling, passenger circulation, concessions, back-of-house operations, and maintenance access.
Those systems do not exist independently. A change in one area can affect another. A ceiling condition may influence routing. A passenger flow requirement may affect layout. A baggage handling path may affect structure, access, and coordination. A security or life safety requirement may limit what can be moved, removed, or redesigned.
Maceri describes the coordination burden this way:
“In airports, there are many more things living inside the same space: MEP, security, baggage handling, and the flow of people. The level of coordination is much higher. The way we model or document may not change completely, but the team has to pay much closer attention to every factor involved.”
That attention matters because airport spaces leave less room for assumptions. When teams rely on incomplete or outdated drawings, they may plan around conditions that no longer exist. A duct may be shown in one place and installed in another. A pipe may have shifted during a previous renovation. A corridor may carry more operational importance than a plan alone suggests.
For project teams, that creates risk. The model may look complete, but if it is disconnected from current field conditions, it can support decisions that do not match the building.
Why models need to reflect real conditions
In airport modernization, the cost of outdated information is not limited to rework. It can affect access, sequencing, coordination, safety, operations, and long-term maintainability.
If a team is renovating a restaurant, expanding a concourse, reconfiguring a mechanical room, or upgrading passenger-facing spaces, they need to understand what is actually installed around the work area. That includes visible conditions and hidden systems that influence what can be moved, reused, protected, or redesigned.
Maceri emphasizes that this connection between field conditions and models is especially important in airports:
“The model has to reflect reality. If you need to redesign anything, from a restaurant to a machine room, you need to know where every pipe and system is located. In an airport, you are working with different risk factors, so the model needs to be extremely accurate.”
That does not mean a model can eliminate every field challenge. Construction is dynamic, and conditions may continue to change after documentation is produced. But a model based on current, captured conditions gives teams a stronger starting point than historical drawings or isolated reports.
It also helps reduce the need to rediscover the same information repeatedly. When stakeholders can use a model to review how a space is organized, where systems are located, or how a new intervention may fit, they can make decisions with more context before sending teams back into hard-to-access areas.
From existing conditions to phased renovation
Airport modernization often happens in phases. Teams may need to preserve passenger movement while renovating check-in areas, concourses, gates, retail spaces, back-of-house areas, or building systems. Temporary configurations may be needed so the airport can keep operating while permanent work is underway.
That creates a modeling challenge. Existing conditions, demolition phases, temporary work, and future conditions may all need to be understood together. A model that starts from captured conditions can help teams organize those phases more clearly.
For example, when Create teams receive a model of existing conditions, they can help adjust and develop that model so teams can understand what exists, what will be demolished, and what the renovated condition is expected to become. That gives project teams a more complete view of the transformation, rather than forcing them to rely on disconnected drawings or separate reports.
This is where the connection between Capture services and Create services for airport modernization becomes valuable. Capture services help document what is there. Create services to help turn that information into usable models and documentation for design, coordination, construction, and handover.
What the JFK Terminal One case study shows
The JFK Terminal One case study shows why keeping models close to field conditions matters at airport scale. On one of the largest aviation redevelopment projects in the United States, the project team needed accurate monthly as-built models while construction was still underway.
The case study focuses on automated as-built delivery through Hexagon Multivista Analyze services, but the lesson applies directly to Create conversations as well: airport teams need documentation and models that reflect what is actually installed, not just what was planned.
At JFK Terminal One, reality capture helped support monthly as-built model delivery while construction continued. That helped the project team keep documentation closer to installed conditions, support coordination, and reduce the gap between field progress and project records.
For airport modernization teams, that is the broader point. Models become more valuable when they stay connected to reality.
Helping stakeholders align beyond plans and reports
Airport projects involve many teams that may not all use information the same way. Owners may need confidence in scope, risk, and long-term asset value. General contractors may need constructible information for sequencing and trade coordination. Architects and consultants may need visual and spatial context for design decisions. Trades may need clarity around installation conditions. Airport operations teams may need to understand how changes affect passengers, access, maintenance, or future upgrades.
A coordinated model can help bring those groups closer to the same view of the project.
Maceri explains the difference between isolated documentation and a coordinated 3D model this way:
“Having the model helps a lot with decision-making. It is very different to work only from a plan or a report than to have the full 3D view, where you can understand how a machine room is organized or how an element will fit. In an airport, that value is even greater.”
That shared view can make conversations more practical. Instead of discussing a condition only through a 2D drawing, an email thread, or a written report, teams can look at the modeled context and understand how decisions affect adjacent systems and spaces.
This is especially useful when stakeholders are not all on site at the same time. A model can help teams review options, identify constraints, and align next steps before field access is required.
Long-term value for handover and future upgrades
Airport models should not only support construction. They should also support what happens after construction.
When models and documentation reflect real conditions, they can become part of a stronger handover record. Facilities and operations teams can use that record to understand where systems are located, how spaces are configured, and what information may be needed for future maintenance, renovations, or upgrades.
That long-term value matters because airports are never truly finished. They are continuously adapted to support passenger demand, new technologies, security requirements, retail changes, airline needs, and operational improvements.
If the final model is incomplete or disconnected from the field, future teams may need to spend time rediscovering conditions before every new project. If the model is accurate and maintained, it can help those teams move faster and reduce uncertainty.
The value is not only in creating a model. It is in creating a model that the next team can trust.
Conclusion
Airport modernization depends on decisions that are informed by real conditions. In dense, operationally sensitive environments, outdated drawings and incomplete documentation can create coordination risk, slow reviews, and make future maintenance harder.
Hexagon Multivista Create services help teams turn captured field information into models and documentation that support design, coordination, construction, handover, and future planning. When those models stay close to what is actually installed, stakeholders can align around a clearer understanding of the airport environment.
For airport owners and project teams, that is the real opportunity: not just creating a model for construction, but creating a reliable record that can support the airport throughout its lifecycle.
Ready to see how Create services can support your airport modernization project? Book a free 30-minute consultation with our team to discuss modeling, documentation, VDC, handover, and how current field information can support better project decisions.