Airport modernization is not only a construction challenge. It is a coordination challenge that unfolds inside active, security-controlled, passenger-facing environments where operations cannot simply pause while work moves forward.
That is why airport teams need more than captured site data, and they need more than models alone. They need a connected path from real field visibility to usable models, documentation, and project insight. Hexagon Multivista helps airport teams support that connection through Capture and Create services.
The JFK Terminal One case study shows that same principle in practice. Reality capture only became scalable project information because it supported a repeatable monthly as-built model process, giving the team documentation that could keep pace with active construction instead of waiting until the end of the project.
The shows why that connection matters at scale. On one of the largest aviation redevelopment projects in the United States, reality capture helped support a repeatable approach to monthly as-built model delivery while construction continued.
Airports keep operating while they change
Airport projects are different because the building remains active while teams plan, capture, coordinate, renovate, and build. People continue moving through terminals. Restricted areas remain controlled. Security processes stay in place. Operations teams need continuity, even while construction teams need access.
As Maria Emilia Quadri, Architect and Program Manager, Hexagon Multivista, explains:
“In airports, the biggest difference is operational security. From the reality capture side, accessing each area requires a high level of logistics, permits, and coordination, and the airport cannot simply stop functioning while that happens.”
That operational reality affects every step that follows. Capture teams may need to work around passenger flow, boarding areas, ceiling access, security approvals, construction activity, and restricted zones. Create teams may then need to turn that captured information into models that support coordination across many systems and stakeholders.
If those steps are disconnected, project teams can lose time. Capture may document the field, but the information may not become usable quickly enough. Models may support coordination, but they may not reflect what is currently installed. Reports may summarize progress, but they may not give teams enough spatial context to make confident decisions.
The value comes from keeping those pieces connected.
Site visibility must become project information
Reliable capture gives airport teams a record of real conditions, but airport capture rarely happens in one clean sequence. Access may be granted in separate areas, at different times, and under different operational constraints. That makes consistency critical.
María Emilia describes the challenge this way:
“When access happens in separate sections, the challenge is making sure everything comes together coherently afterward. If the team needs an existing conditions record, it must be precise, even if the capture had to happen in parts.”
That is where early alignment between Capture and Create becomes important. Before field teams begin documenting conditions, project stakeholders should understand what the captured information needs to support. Is the goal existing conditions documentation? Renovation planning? As-built modeling? Phased construction coordination? Handover preparation?
The answer affects what needs to be captured, how it should be organized, and how the downstream model or documentation will be used.
When airport teams align those needs early, captured data has a better chance of becoming useful project information. Photos, scans, and field records can support more than visual references. They can become the foundation for models, documentation, coordination reviews, and facility management.
Models must reflect the airport as it is
Create services help airport teams translate captured conditions into models and documentation that different stakeholders can use. But in airport modernization, the model needs to stay close to real conditions because the environment is dense, active, and heavy.
Airport projects bring together MEP systems, fire protection, communications, security infrastructure, baggage handling, passenger circulation, concessions, maintenance areas, and operational workflows. A change in one area can affect many others.
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.”
That stakeholder complexity raises the importance of current, usable models. Airport owners, general contractors, architects, consultants, trades, airport operations teams, and authorities may all look at the same project from different priorities. A coordinated model can help those teams move beyond isolated drawings, reports, or verbal updates and work from a more shared understanding of the space.
The model becomes more than a technical deliverable. It becomes a coordination tool.
Outdated information creates downstream risk
When teams design or coordinate from outdated drawings, they may be planning around conditions that no longer exist. A duct may be shown in the wrong location. A pipe may have shifted during earlier work. A ceiling condition may be more constrained than expected. A corridor may need to support a higher passenger volume than the existing documentation suggests.
In a less complex building, that can create coordination friction. In an airport, it can affect safety, access, sequencing, operations, maintenance, and future upgrades.
Malena puts it directly:
“The model must 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.”
This is why Capture and Create services should not be treated as separate moments in the project lifecycle. Capture helps establish what is real. Create helps make that reality usable for decisions. When those services are aligned, airport teams can reduce the gap between what is documented, what is modeled, and what is actually happening in the field.
What JFK Terminal One shows at scale
The JFK Terminal One case study is a strong example of why airport documentation needs to keep pace with construction.
The project team needed accurate monthly as-built models while construction was still underway. Traditional approaches would have required extensive manual modeling effort and would likely have trailed behind field conditions. Instead, reality capture supported a more repeatable process for automated as-built model delivery.
For airport teams, the broader lesson is not only about monthly as-builts. It is about keeping field conditions, models, and documentation closer together while the project is still moving.
That matters because airport construction does not wait for a perfect documentation window. Design changes, installation progress, access constraints, and stakeholder needs continue to evolve. A connected approach helps project teams respond with information that is more current, more visual, and more useful for coordination.
A lifecycle record, not just a construction deliverable
The value of connected site visibility and usable models does not end at construction.
Airport facilities need to keep adapting after a project is complete. Passenger volumes change. Security requirements evolve. Retail and concessions shift. Building systems need maintenance. Future renovations and operational upgrades require reliable information about what exists and where it is located.
When captured conditions and models are organized with the lifecycle in mind, handover becomes stronger. Future teams can start from a more reliable record instead of rediscovering existing conditions each time a new project begins.
For airport owners and delivery teams, that is the strategic value: a connected record that supports construction today and better decisions tomorrow.
Conclusion
Airport modernization depends on coordination across active operations, restricted areas, dense systems, and many stakeholders. Capture services help teams document real conditions. Create services help turn those conditions into usable models and documentation. Together, they help project teams keep site visibility connected to the decisions that depend on it.
The JFK Terminal One case study shows what that can look like on a major aviation project, where reality capture helped support monthly as-built model delivery while construction continued.
For airport teams, the takeaway is simple: visibility is valuable, but connected visibility is what helps teams plan, coordinate, build, hand over, and prepare for what comes next.
Ready to connect site visibility, models, and documentation on your airport modernization project? Book a free 30-minute consultation with our team to discuss how a connected project record can support decisions from construction through handover.