CAD, BIM, common data environments, and digital delivery platforms have transformed how infrastructure is designed, coordinated, constructed, and handed over.
But the digital representation is not the physical asset.
Models change.
Files change.
Project identifiers change.
Software changes.
Ownership changes.
The completed structure remains.
CAD, BIM and Digital Delivery
The model can change. The physical structure identity should not.
PIID™ gives each qualifying physical structure a persistent identity that can continue beyond the project, beyond the model, and through the operating life of the asset.
The model identity problem
The project has identifiers.The physical structure needs identity.
CAD and BIM environments already contain sophisticated references.
Project numbers.
Model identifiers.
Drawing numbers.
Building designations.
Spatial references.
Object identifiers.
File names.
Internal system keys.
Client identifiers.
Those references are essential within the environments that created them.
But they are not necessarily designed to remain with the physical structure for the life of the asset.
Once the project ends, the environment changes.
Design teams leave.
Construction teams demobilize.
Files transfer.
Owners take control.
Facilities systems take over.
New software is introduced.
The physical structure remains.
PIID™ provides persistent identity for the structure beyond the project environment.
- Design model
- Const. model
- Project no.
- File ID
Model versus physical asset
The model represents the structure.PIID™ identifies the structure itself.
A BIM model can represent a building in extraordinary detail.
A CAD drawing can describe its design.
A digital twin can represent its current operating state.
A simulation can model future conditions.
PIID™ serves a different role.
It identifies the qualifying physical structure represented by those environments.
Model
Digital representation.
Drawing
Technical documentation.
Digital Twin
Operational or analytical representation.
PIID™
Persistent identity of the physical structure itself.
Representation changes. Physical identity persists.
Structure identity, not object identity
PIID™ does not replace BIM object identifiers.
A BIM environment may contain thousands or millions of modeled objects.
Doors.
Windows.
Walls.
Mechanical systems.
Electrical systems.
Equipment.
Components.
Spaces.
Assemblies.
Those elements should continue using the identifiers and classifications required by the design, construction, and operating systems responsible for them.
PIID™ serves a different purpose.
It persistently identifies the qualifying physical structure that provides context for those objects.
BIM identifies what exists within the model. PIID™ identifies the physical structure the model represents.
From design to physical asset
Carry identity beyond project delivery.
A structure begins as an idea.
Then a design.
Then a coordinated model.
Then a construction project.
Eventually, it becomes a physical asset expected to operate for decades.
PIID™ creates a persistent reference capable of continuing across that transition.
Design → Construction → Commissioning → Operation → Improvement → Lifecycle Continuity
The project environment can end.
The structure identity continues.
PIID Resolve™
Resolve project and spatial references to persistent structure identity.
PIID Resolve™ identifies, validates, and resolves supported references to the physical structure.
Supported inputs can include:
Normalized Address
Parcel
PIID™
Coordinates
Geometry
Supported Source Reference
This gives design, construction, owner, and enterprise systems a way to reconcile supported project and property references to the same physical structure.
Submit a reference. Resolve the structure. Return persistent identity.
PIID Resolve™Digital delivery
The deliverable should carry forward into the life of the asset.
Digital delivery increasingly creates rich information during design and construction.
Models.
Drawings.
Specifications.
Schedules.
Reports.
Commissioning information.
Closeout documentation.
Asset information.
The challenge begins when those deliverables leave the project environment.
PIID™ provides a persistent structure reference capable of continuing into ownership and operations.
Digital delivery should end with more than files. It should preserve the identity of the physical asset those files describe.
The handoff problem
Handoff should transfer information without breaking asset identity.
Project handoff is one of the most important transitions in the infrastructure lifecycle.
The design team completes its work.
The contractor closes the project.
The owner receives documentation.
Facilities teams inherit the structure.
Operational systems begin managing it.
At each transition, identifiers and systems can change.
PIID™ provides a persistent reference to the physical structure underneath those changes.
Handoff should transfer responsibility, not reset the identity of the asset.
As built continuity
The final model is still only one representation in a much longer lifecycle.
As built information can provide important context at project completion.
But the structure does not remain frozen at handoff.
It will be maintained.
Renovated.
Repaired.
Expanded.
Inspected.
Reconfigured.
Retrofitted.
Repositioned.
Transferred.
PIID™ allows future systems and records to continue referencing the same physical structure even as the digital representation evolves.
The as built model captures a moment. Persistent identity continues through time.
Common data environments
Collaboration environments can change while structure identity remains.
Common data environments help teams coordinate project information across disciplines and organizations.
But the platform supporting that collaboration may not remain in place for the life of the structure.
PIID™ provides an identity reference independent of the project collaboration environment.
The common data environment can reference PIID™.
The owner platform can reference PIID™.
The facilities environment can reference PIID™.
A future digital twin can reference the same PIID™.
The collaboration environment is temporary. The structure identity is persistent.
Multi structure projects
One model environment can represent many physical structures.
Large projects can include multiple qualifying structures.
Campuses.
Industrial properties.
Multifamily developments.
Institutional facilities.
Government complexes.
Mixed use properties.
Corporate campuses.
Large commercial developments.
A project number or site model may represent the entire environment.
PIID™ gives each qualifying structure its own persistent identity.
One project. Many structures. Persistent identity for each qualifying asset.
UMIP Structure Schedule™
Document the physical structures delivered by the project.
UMIP Structure Schedule™ is being developed to document each qualifying structure associated with a property through PIID™, location, geometry, and parcel relationship.
For CAD, BIM, and digital delivery workflows, Structure Schedule™ can create a clear bridge between project level representations and the permanent structures actually delivered.
One property. Every qualifying structure. Clearly identified.
Coming Soon
In development
Owner handoff
Give the owner an identity that survives the project team.
Owners often receive large amounts of information at project completion.
The value of that information depends partly on whether it can remain associated with the correct physical structure after the project environment is gone.
PIID™ gives the owner a persistent structure reference that can continue into:
Facilities management.
Asset management.
Insurance.
Finance.
Energy management.
Capital planning.
Risk.
Future construction.
Digital twins.
Enterprise systems.
The owner inherits the structure. The identity should already be established.
Asset management and CMMS
Connect project delivery to the systems that operate the structure.
Once the project is complete, operational responsibility frequently moves into asset management, CMMS, EAM, and facilities environments.
Those systems may have no relationship to the software used during design and construction.
PIID™ provides a persistent structure identity capable of bridging those environments.
The BIM environment can reference PIID™.
The CMMS can reference the same PIID™.
The facilities system can reference it.
The digital twin can reference it.
The software changes. The physical structure reference remains.
Asset Management and CMMSFacilities management
Carry design context into decades of operation.
Facilities teams operate physical structures long after the original project team is gone.
Maintenance.
Inspections.
Repairs.
Capital planning.
Energy.
Safety.
Operations.
Renovations.
Lifecycle™ provides the framework through which supported records, relationships, and events can remain connected around the same persistent structure identity.
Design begins the structure story. Operations continue it. PIID™ keeps the identity constant.
Lifecycle™Facilities ManagementRenovation and future projects
Every future project should recognize the structure that already exists.
A physical structure can undergo many projects during its life.
Renovation.
Expansion.
Modernization.
Energy retrofit.
Roof replacement.
Structural work.
Interior reconfiguration.
System upgrades.
Every project can create a new model environment and new project identifiers.
PIID™ provides a persistent reference to the structure underneath all of them.
New project. New model. Same physical structure. Same persistent identity.
Digital twins and simulation
Give every future representation a persistent physical reference.
Digital twins and simulations increasingly build on information created during design and construction.
But the digital twin is still a representation of the physical asset.
PIID™ identifies the physical structure underneath it.
Lifecycle™ provides continuity through time.
Digital representations change. Physical asset identity should persist.
Digital Twins and SimulationGIS, Mapping and Geospatial Intelligence
Connect model geometry to the broader spatial environment.
CAD and BIM environments describe structures at extraordinary levels of detail.
GIS and mapping systems place those structures within broader geographic context.
PIID™ provides a persistent structure identity capable of connecting supported representations across those environments.
PIID Resolve™ can reconcile supported spatial references to persistent structure identity.
BIM describes the asset. GIS locates the asset. PIID™ persistently identifies the asset.
GIS, Mapping and Geospatial IntelligenceArchitecture, Engineering and Surveying
Carry identity across disciplines.
Architecture, engineering, and surveying create different but complementary representations of the same physical environment.
Survey establishes spatial context.
Architecture defines design intent.
Engineering defines technical systems and performance.
PIID™ gives supported disciplines a persistent structure reference that can continue beyond the individual project.
Different disciplines. Same physical structure. One persistent identity.
Architecture, Engineering and SurveyingConstruction
The construction project is only one stage of asset life.
Construction transforms the model into the physical structure.
Once completed, the structure enters a lifecycle that can continue for generations.
PIID™ establishes a persistent physical asset reference capable of continuing beyond construction.
The project ends. The structure continues. Its identity should too.
ConstructionDocument continuity
Documents become more useful when the structure remains consistently identified.
A structure can accumulate decades of:
Plans.
Drawings.
Specifications.
Reports.
Inspections.
Renovation documents.
Engineering studies.
Commissioning records.
Maintenance information.
Future models.
Lifecycle™ provides a framework through which supported information can remain associated with the same physical structure.
Persistent identity is foundational. Storage is optional.
Lifecycle™Model federation and interoperability
Different models should still know when they represent the same physical structure.
A project may involve multiple models from multiple disciplines and providers.
Those models can retain their own internal identifiers.
PIID™ provides a persistent physical structure reference outside those model specific environments.
This creates another interoperability point among supported:
Architectural models.
Engineering models.
Construction environments.
GIS platforms.
Owner systems.
Facilities platforms.
Digital twins.
Enterprise applications.
Different models. Same physical structure. One persistent reference.
System migration
Migrate the platform without resetting physical asset identity.
Technology environments evolve.
Software versions change.
Platforms consolidate.
File formats evolve.
Organizations adopt new tools.
Legacy systems are retired.
PIID™ provides a physical structure identity independent of those technology transitions.
A legacy model can reference PIID™.
A new platform can reference the same PIID™.
The structure does not need to receive a new identity because the software changed.
Migrate the technology. Preserve the structure reference.
Artificial intelligence
AI needs persistent context for the physical asset behind the model.
Artificial intelligence is increasingly being used across design, engineering, construction, document analysis, facilities, simulation, and digital twins.
AI systems can process enormous amounts of information.
But they still need to know when different records, models, and systems describe the same physical structure.
PIID™ provides persistent structure identity.
Lifecycle™ provides continuity through time.
Persistent identity creates persistent machine context.
AI and generative design
More models increase the need for persistent physical identity.
AI can generate new designs, alternatives, scenarios, models, analyses, and recommendations.
The number of digital representations surrounding infrastructure will continue increasing.
That makes the distinction between representation and physical asset even more important.
PIID™ provides the persistent identity of the actual structure.
More digital representations should not create more physical asset ambiguity.
Cross system interoperability
The built environment does not need one software platform.
CAD.
BIM.
GIS.
CMMS.
EAM.
Digital twins.
Project management.
Common data environments.
Document management.
Owner systems.
Enterprise platforms.
AI.
Each serves a different purpose.
They do not need to become one system.
PIID™ gives supported environments a persistent reference to the same physical structure.
Different systems retain their role. Identity becomes the connection point.
Data control
Persistent identity does not require centralizing project data.
UMIP does not require design firms, engineering firms, contractors, owners, BIM providers, or technology companies to move their underlying models, files, or data into a central repository.
Organizations retain their systems.
Providers retain their models.
Existing identifiers can remain.
Project data can remain within the environments responsible for it.
PIID™ provides the persistent structure reference through which supported information can coordinate.
Connection does not require centralization.
CAD and BIM technology providers
Add persistent physical identity to the platforms customers already use.
CAD, BIM, common data environment, and digital delivery providers can integrate PIID™ as a persistent physical structure reference within their existing platforms.
PIID™ can complement model specific and project specific identifiers without replacing them.
This can support continuity across:
Design
Engineering
Construction
Commissioning
Owner Handoff
Facilities Operations
System Migration
Digital Twins
GIS Integration
Artificial Intelligence
Give the model a reference to the physical structure that exists beyond the model.
Enterprise delivery
Built for direct integration.
PIID Resolve™ is designed for structured integration into design, construction, geospatial, owner, facilities, and enterprise technology environments.
Supported JSON responses can provide:
PIID™
Verification Context
Registry Context
Structure Context
Building Geometry
Property Context
Supported Source References
Supported file based JSON delivery can also accommodate applicable enterprise exchange workflows.
API delivered. Machine readable. Built for integration at scale.
Built on UMIP
Persistent identity beneath the digital representation.
PIID™
Provides persistent identity for each qualifying physical structure.
PIID Resolve™
Resolves supported project, spatial, and property 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 within complex properties.
Coming Soon
In development
Governed by GIIS™
Persistent physical identity requires consistent rules.
CAD and BIM environments span organizations, disciplines, projects, owners, software platforms, jurisdictions, and decades 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 the structures digital systems represent.
- 189M+PIIDs Registered Across the United States
The built environment is becoming increasingly digital.
More models.
More platforms.
More automation.
More digital twins.
More AI.
More data.
As digital representations multiply, the need for persistent identity of the physical asset becomes more important.
Design → Model → Construct → PIID™ → Operate → Improve → Persist
CAD, BIM and Digital Delivery
Build the model. Deliver the project.Preserve the identity of the physical asset.
The drawing can change.
The model can change.
The project team can change.
The software can change.
The owner can change.
The physical structure remains.
PIID™ gives that structure a persistent identity capable of continuing from design and construction into ownership, operations, future projects, digital twins, enterprise systems, and decades of change.
The model represents the structure. PIID™ identifies the structure itself.
Related
Resolve physical structures to persistent infrastructure identities. PIID Resolve™ identifies, validates, and resolves structures from addresses, parcels, coordinates, geometry, and supported source records.
