Airports and Aviation
Persistent structure identity for the physical infrastructure supporting aviation.
Airports operate through complex networks of terminals, hangars, cargo facilities, maintenance buildings, operations facilities, parking structures, administrative buildings, emergency facilities, engineering environments, GIS, facilities platforms, capital programs, and enterprise technology.
Those environments can reference the same physical structures differently.
PIID™ gives each qualifying physical structure a persistent identity that can remain consistent across systems, operators, capital programs, renovations, ownership relationships, and decades of airport evolution.
Airport and Aviation Infrastructure
The airport is the location. PIID™ identifies the structures within it.
PIID™ gives each qualifying physical structure a persistent identity that can remain consistent across systems, operators, capital programs, renovations, ownership relationships, and decades of airport evolution.
The Aviation Infrastructure Identity Problem
One airport. Many structures.Many references.
Airport infrastructure can be represented through:
Airport codes.
Terminal names.
Building numbers.
Addresses.
Parcel identifiers.
Coordinates.
GIS objects.
Facility identifiers.
Engineering references.
Construction project numbers.
Maintenance systems.
Property systems.
Insurance records.
Digital models.
Enterprise system keys.
Each reference can serve an important purpose.
But none necessarily establishes one persistent identity for the physical structure itself.
PIID™ provides that persistent structure reference.
Different systems. Same physical structure. One persistent identity.
- Airport code
- Terminal name
- Facility no.
- GIS
- CMMS
- Property
The Airport Is Not the Structure
Airport identity and structure identity solve different problems.
An airport code identifies the airport.
A terminal name identifies a facility within the airport environment.
An address identifies location.
A parcel identifies land.
A GIS object provides spatial representation.
A facilities system may assign an internal building number.
PIID™ persistently identifies the qualifying physical structure itself.
Those existing references remain useful.
PIID™ provides the identity capable of connecting supported representations of the same structure across systems and time.
Airport context above. Persistent structure identity underneath.
Multi Structure Airport Environments
An airport is a network of physical structures.
A major airport can include:
Passenger terminals.
Concourses.
Hangars.
Cargo facilities.
Maintenance buildings.
Operations facilities.
Administrative buildings.
Parking structures.
Rental car facilities.
Fire and emergency facilities.
Storage buildings.
Other qualifying permanent structures.
A single airport identifier cannot distinguish every physical structure within that environment.
PIID™ allows each qualifying structure to maintain its own persistent identity.
AIRPORT
Structure 01 — Passenger Terminal
PIID™
Structure 02 — Hangar
PIID™
Structure 03 — Cargo Facility
PIID™
Structure 04 — Maintenance Building
PIID™
Structure 05 — Parking Structure
PIID™
- GIS
- CMMS
- BIM
- Engineering
- Property
- Energy
- Insurance
- Emergency Management
- Digital Twin
- Enterprise Systems
AIRPORT
Structure 01 — Passenger Terminal
PIID™
Structure 02 — Hangar
PIID™
Structure 03 — Cargo Facility
PIID™
Structure 04 — Maintenance Building
PIID™
Structure 05 — Parking Structure
PIID™
GIS
CMMS
BIM
Engineering
Property
Energy
Insurance
Emergency Management
Digital Twin
Enterprise Systems
One airport. Many structures. Persistent identity for each qualifying asset.
UMIP Structure Schedule™
Document the physical structure inventory of the airport.
UMIP Structure Schedule™ is being developed to document qualifying structures associated with a property through PIID™, location, geometry, and parcel relationship.
For airports, Structure Schedule™ can create clearer structure level context across large and complex physical environments.
This can support:
Facilities management.
Capital planning.
Engineering.
Property administration.
Insurance.
Risk review.
Emergency management.
GIS.
Construction.
Portfolio management.
Infrastructure planning.
Know what structures exist. Know where they are. Know which structure is being referenced.
Coming Soon
In development
PIID Resolve™
Resolve fragmented airport references to persistent structure identity.
PIID Resolve™ identifies, validates, and resolves supported references to the physical structure.
Supported inputs:
Normalized Address
Parcel
PIID™
Coordinates
Geometry
Supported Source Reference
Airport authorities, operators, technology providers, engineering organizations, and enterprise systems can use PIID Resolve™ to reconcile different representations of the same physical structure around one persistent identity.
Submit a reference. Resolve the structure. Return persistent identity.
PIID Resolve™Passenger Terminals
Terminal systems change.The physical terminal remains.
Passenger terminals can remain operational through generations of:
Airline relationships.
Technology platforms.
Security systems.
Passenger processing systems.
Retail environments.
Facilities platforms.
Renovation programs.
Expansion projects.
Digital systems.
The physical structure remains the constant underneath those changes.
PIID™ provides persistent structure identity capable of continuing through them.
Operations evolve. Terminal identity persists.
Hangars and Maintenance Facilities
Identify the facility independently of the aircraft inside it.
Aviation facilities may contain aircraft, equipment, tools, maintenance systems, and operational assets with their own identifiers.
PIID™ does not replace aircraft registration, equipment identifiers, maintenance asset numbers, or operational references.
It identifies the qualifying physical structure itself.
Aircraft keep their identifiers. PIID™ identifies the structure.
Cargo and Logistics Facilities
Cargo moves.The physical infrastructure remains.
Airport cargo environments can change continuously.
Carriers change.
Shipments change.
Tenants change.
Technology changes.
Operating systems change.
The cargo facility remains.
PIID™ provides persistent identity for the physical structure beneath those changing relationships.
The cargo moves. Structure identity persists.
Facilities Management
Persistent identity beneath airport operations.
Airports rely on extensive facilities environments.
CMMS.
Enterprise asset management.
Building management systems.
Work order platforms.
Inspection systems.
Engineering systems.
GIS.
Energy platforms.
Property systems.
Digital twins.
Enterprise applications.
Those systems can retain their existing identifiers.
PIID™ provides a persistent reference to the physical structure they share.
Different operating systems. Same physical facility. One persistent identity.
Asset Management and CMMS
The maintenance platform can change.The structure identity should not.
Airport facilities can remain operational through generations of maintenance technology.
A CMMS may be replaced. Asset hierarchies may be migrated. Building codes may change. New facilities platforms may be introduced.
PIID™ provides an identity independent of the maintenance system currently responsible for the structure.
A legacy platform can reference PIID™.
A replacement platform can reference the same PIID™.
Migrate the system. Preserve the structure reference.
Maintenance Continuity
Decades of maintenance.One physical structure.
Airport buildings can accumulate extensive histories of:
Maintenance.
Inspections.
Roof work.
Mechanical upgrades.
Electrical improvements.
Interior renovations.
Life safety projects.
Capital repairs.
Energy projects.
Modernization.
Different organizations and systems can manage that activity over time.
PIID™ provides the persistent structure identity around which supported maintenance context can remain connected.
The work changes the facility. The identity carries forward.
Capital Programs
Airport infrastructure is continually evolving.
Airports undergo major cycles of:
Expansion.
Renovation.
Terminal modernization.
Concourse development.
Facility replacement.
Technology upgrades.
Parking development.
Cargo expansion.
Maintenance improvements.
Passenger facility improvements.
Each program can introduce new systems, project numbers, engineering records, contractors, models, and documentation.
PIID™ provides persistent structure identity beneath those programs.
New program. Same physical structure. Same persistent identity.
Architecture, Engineering and Construction
Carry structure identity from project delivery into permanent airport operations.
Airport infrastructure projects generate extensive architectural, engineering, construction, and digital information.
The project eventually ends. The design team leaves. The contractor leaves. The project platform may be retired. The structure remains.
PIID™ provides a persistent structure identity capable of continuing beyond construction and into long term facilities operations.
The project ends. The structure continues. Its identity should too.
CAD, BIM and Digital Delivery
Give every aviation model a reference to the physical structure it represents.
Airport facilities may be represented through multiple generations of CAD, BIM, engineering models, and digital delivery environments.
Those models can change.
PIID™ identifies the actual physical structure beneath them.
This allows supported BIM environments, GIS systems, facilities platforms, digital twins, and future project systems to reference the same physical structure.
The model represents the facility. PIID™ identifies the facility itself.
Engineering Continuity
Different engineering disciplines.Same physical infrastructure.
Airport facilities may involve:
Structural engineering.
Civil engineering.
Mechanical engineering.
Electrical engineering.
Environmental engineering.
Energy engineering.
Transportation engineering.
Facility engineering.
Each discipline may use different systems and project references.
PIID™ provides a common persistent structure identity around which supported engineering context can coordinate.
Different disciplines. Same structure. Persistent identity between them.
Airport GIS
Connect airport geography to persistent structure identity.
Airports depend heavily on geospatial information.
Coordinates.
Building footprints.
Imagery.
Parcels.
Facility maps.
GIS objects.
Site relationships.
Those references establish spatial context.
PIID™ establishes persistent structure identity.
PIID Resolve™ can reconcile supported spatial references to structure identity.
Location tells you where. PIID™ tells you which structure.
Property and Facility Administration
Give airport property systems a persistent structure reference.
Airport property environments can include facilities operated by airport authorities, airlines, concessionaires, logistics companies, maintenance organizations, rental car operators, and other entities.
Occupancy and operating relationships can change.
The physical structure remains.
PIID™ provides persistent identity underneath those changing relationships.
The operator can change. The structure identity does not need to.
Tenant and Operator Transitions
New operator.Same physical facility.
Airport structures can pass between:
Airlines.
Cargo operators.
Maintenance providers.
Concessionaires.
Service organizations.
Airport authorities.
Other operators.
Each transition can introduce new systems and internal identifiers.
PIID™ provides a persistent reference to the structure itself.
Operating relationships change. Structure identity persists.
Energy and Utilities
Aviation depends on complex physical infrastructure systems.
Airport facilities depend on:
Electrical service.
Water.
Heating.
Cooling.
Backup generation.
Energy systems.
Communications infrastructure.
Other building services.
Those systems may maintain their own accounts, service points, operational references, and facility identifiers.
PIID™ complements those systems with persistent structure identity.
The service relationship can change. The structure identity remains.
Airport Resilience
Maintain structure identity through disruption and recovery.
Airports are critical transportation infrastructure.
Storms, fire, infrastructure failures, flooding, and other disruptions can involve:
Airport authorities.
Facilities teams.
Airlines.
Engineers.
Utilities.
Emergency responders.
Government agencies.
Insurers.
Contractors.
Recovery teams.
PIID™ provides a persistent structure reference capable of remaining consistent through preparedness, disruption, assessment, repair, and recovery.
Before the event. During the event. After the event. Same structure identity.
Emergency Management
Response depends on knowing exactly which physical structure is being referenced.
Large airports contain many structures with different functions, access requirements, occupancy patterns, and risk profiles.
PIID™ provides persistent structure identity.
UMIP Structure Schedule™ can provide clearer structure level inventory across complex airport properties.
Know which structure. Know where it is. Maintain the same reference through the event.
Fire and Emergency Facilities
Emergency facilities are part of the infrastructure network.
Airport fire, rescue, operations, and emergency support facilities can interact with multiple airport systems.
PIID™ provides persistent structure identity for qualifying facilities within that environment.
The purpose is not to replace operational emergency systems.
It is to give supported systems a consistent reference to the same physical structure.
Different emergency systems. Same facility reference.
Insurance and Risk
Resolve aviation facility risk to the correct physical structure.
Airports contain structures with significantly different uses, construction characteristics, values, occupancies, and risk profiles.
Insurance and risk environments may analyze:
Property exposure.
Catastrophe risk.
Fire.
Flood.
Storm.
Business interruption.
Physical damage.
Facility resilience.
PIID™ provides persistent structure identity beneath supported risk workflows.
Structure Schedule™ can provide clearer structure context across multi structure airport environments.
Know which structure carries the risk. Persistently.
Security System Context
Facility identity and security identity solve different problems.
Airports operate sophisticated security and access environments.
Those systems should continue using the identifiers and controls required for their specialized functions.
PIID™ does not replace security credentials, access controls, passenger identity, employee identity, or operational security systems.
PIID™ identifies the qualifying physical structure.
Security systems control access. PIID™ identifies the structure.
Digital Twins and Simulation
Give every digital airport representation a persistent physical reference.
Airport operators can increasingly use:
Digital twins.
Engineering models.
Operational simulations.
Capacity models.
Energy simulations.
Facility analytics.
Planning environments.
Those representations can evolve.
The physical structures remain.
PIID™ identifies the structure beneath the digital representation.
Lifecycle™ provides continuity through time.
Digital representations change. Physical asset identity should persist.
Capacity and Facility Planning
Many future scenarios.One physical structure.
Airport planning can involve:
Passenger growth.
Terminal expansion.
Facility modernization.
Cargo growth.
Parking expansion.
Tenant changes.
Operational changes.
Capital improvements.
Infrastructure renewal.
PIID™ gives supported planning environments a consistent physical structure reference as future scenarios are evaluated.
The scenario changes. The physical structure reference remains.
Lifecycle Continuity
Aviation facilities can serve generations.
A terminal, hangar, cargo building, or airport support structure may remain operational through decades of:
Renovation.
Maintenance.
Operator changes.
Technology upgrades.
Capital programs.
Engineering projects.
Energy modernization.
Insurance events.
Facilities system migrations.
Lifecycle™ provides the framework through which supported records, events, relationships, and history can remain connected around the same PIID™.
The airport evolves. The structure identity carries forward.
Lifecycle™Artificial Intelligence
Aviation AI needs persistent physical infrastructure context.
Artificial intelligence can increasingly interact with:
Facilities information.
Maintenance records.
Engineering documents.
GIS.
Energy information.
Digital twins.
Risk models.
Property information.
Infrastructure analytics.
PIID™ provides a persistent physical structure reference across supported information.
Lifecycle™ provides continuity through time.
Persistent identity creates persistent machine context.
Smart Airport Infrastructure
A smarter airport begins with knowing which physical structure every system is talking about.
Airports are becoming increasingly connected through:
Sensors.
Building systems.
Facilities technology.
Energy platforms.
GIS.
Digital twins.
Automation.
Enterprise systems.
Artificial intelligence.
More connected systems increase the importance of consistent physical structure identity.
PIID™ provides that persistent reference.
More connected infrastructure requires clearer identity.
Portfolio Management
Persistent identity across airport infrastructure portfolios.
Airport authorities, aviation companies, infrastructure owners, investors, operators, and government organizations can manage portfolios containing many physical structures.
PIID™ provides persistent structure identity across supported environments.
This can support:
Portfolio normalization.
Structure reconciliation.
Facilities operations.
Capital planning.
Risk analysis.
Insurance.
Engineering.
Energy analysis.
Property management.
Infrastructure intelligence.
Many facilities. One persistent structure reference framework.
Cross System Interoperability
The airport does not need one database.
GIS can remain GIS.
CMMS can remain CMMS.
BIM can remain BIM.
Property systems can retain their role.
Engineering applications can retain their role.
Energy platforms can retain their role.
Digital twins can remain digital twins.
Enterprise applications can retain their own records.
PIID™ provides a persistent structure reference through which supported environments can reference the same physical asset.
Different systems retain their role. Identity becomes the connection point.
Data Control
Connection does not require centralization.
UMIP does not require airport authorities, airlines, operators, engineering firms, technology providers, insurers, or data partners to move all underlying infrastructure information into one central repository.
Existing systems can remain.
Existing identifiers can remain.
Source records can remain within the environments responsible for them.
PIID™ provides the persistent structure reference through which supported information can coordinate.
Persistent identity without mandatory data centralization.
System Independence
Airport structures can outlive the technology platforms around them.
A terminal or aviation facility may remain operational much longer than the systems used to manage it.
CMMS platforms change.
GIS platforms change.
Engineering software changes.
BIM environments change.
Enterprise systems change.
PIID™ provides a structure identity independent of any single software platform or technology provider.
Platforms are replaceable. Physical structure identity should persist.
Enterprise Delivery
Built for integration into aviation infrastructure systems.
PIID Resolve™ is designed for structured enterprise integration.
Supported JSON responses:
PIID™
Verification Context
Registry Context
Structure Context
Building Geometry
Property Context
Supported Source References
Integration environments:
Airport facilities platforms.
CMMS.
EAM.
GIS.
Engineering systems.
BIM.
Property systems.
Energy platforms.
Risk applications.
Digital twins.
Enterprise data platforms.
Artificial intelligence.
Supported file based delivery can also accommodate applicable enterprise exchange workflows.
API delivered. Machine readable. Built for integration at scale.
Technology Providers
Add persistent structure identity to aviation technology.
Aviation, facilities, geospatial, engineering, property, risk, and infrastructure technology companies can integrate PIID™ as a persistent structure reference within existing products.
PIID™ can complement internal facility identifiers without replacing them.
This can provide continuity across supported:
Facilities platforms.
Airport systems.
GIS.
Engineering environments.
Risk platforms.
Digital twins.
Property applications.
Energy systems.
Enterprise technology.
Give aviation technology a persistent reference to the physical infrastructure itself.
Built on UMIP
Persistent identity beneath airport and aviation infrastructure.
PIID™
Provides persistent identity for each qualifying physical structure.
PIID Resolve™
Resolves supported aviation facility, spatial, property, and source references to persistent structure identity.
Lifecycle™
Maintains continuity around structure identity through time.
UMIP Registry™
Maintains persistent infrastructure identity and supported registry context.
UMIP Structure Schedule™
Documents qualifying structures across complex airport properties.
Coming Soon
In development
Governed by GIIS™
Persistent aviation infrastructure identity requires consistent rules.
Airport infrastructure spans airport authorities, operators, airlines, engineering firms, government organizations, facilities teams, technology providers, insurers, utilities, and generations of physical asset life.
GIIS™ establishes the governance framework supporting consistent Persistent Infrastructure Identity across those environments.
PIID™ provides the structure identity.
GIIS™ provides the governance foundation supporting its continuity.
Identity establishes the reference. Governance protects its continuity.
At Scale
Persistent identity for aviation infrastructure at national scale.
- 189M+PIIDs Registered Across the United States
Airports will continue becoming more connected, automated, digitally managed, and intelligent.
The physical structures beneath those environments still require persistent identity capable of continuing through generations of technological, organizational, and operational change.
Structure Identity → Aviation Interoperability → Lifecycle Continuity → Infrastructure Intelligence
Airport and Aviation Infrastructure
Flights change. Operators change. Technology changes.The physical infrastructure remains.
Airlines change.
Passenger systems change.
Cargo moves.
Tenants change.
Capital programs transform the airport.
Facilities systems are replaced.
Digital models evolve.
The physical structures remain.
PIID™ gives qualifying airport and aviation infrastructure a persistent identity capable of continuing across the systems, organizations, and programs responsible for it.
Flights change. Operators change. Technology changes. The physical infrastructure remains.
The airport is the location. PIID™ identifies the structures within it.
Related
Resolve physical structures to persistent infrastructure identities. PIID Resolve™ identifies, validates, and resolves structures from addresses, parcels, coordinates, geometry, and supported source records.
Establishes how supported records, attributes, events, relationships, and history remain connected to that identity through time.
Identify and organize the permanent structures associated with a property, with each qualifying structure referenced through its own PIID™.