Institutional Inquiry Framework

UMIP is the registry framework and operating platform that issues and manages Persistent Infrastructure Identities (PIIDs) for physical infrastructure assets. Through the UMIP registry, infrastructure assets are assigned a stable digital identity that allows lifecycle information such as design records, construction documentation, inspections, maintenance activities, and risk events to remain connected to the same asset across time, ownership changes, and multiple software systems.

A Persistent Infrastructure Identity (PIID) is a globally unique digital identifier assigned to a physical infrastructure asset. Similar to how Vehicle Identification Numbers (VINs) uniquely identify automobiles throughout their lifecycle, a PIID provides infrastructure assets with a stable identity that allows lifecycle records, documentation, and system data to remain linked to the same physical asset over time.

PIIDs enable infrastructure information to remain connected across design, construction, operations, insurance, and asset management systems, improving lifecycle continuity and governance for the built environment.

No. A Persistent Infrastructure Identity (PIID) is designed to remain permanently associated with the infrastructure asset or zone to which it is issued. Once assigned through the UMIP registry, the PIID remains constant for the lifetime of the asset.

While ownership, operational systems, or asset attributes may change over time, the PIID remains the stable reference point that allows lifecycle records, documentation, and system data to remain connected to the same physical infrastructure.

This persistence ensures long-term continuity of infrastructure records across ownership transitions, system migrations, and operational changes.

No. Once a Persistent Infrastructure Identity (PIID) is issued to a specific infrastructure asset or defined zone, it remains permanently associated with that asset. A PIID cannot be reassigned to a different asset, even if the original asset changes ownership, undergoes significant modification, or transitions between operational systems.

This permanence ensures that lifecycle records remain consistently tied to the same physical infrastructure asset over time.

A UMIP Zone is a defined portion of an infrastructure asset that can be individually identified and tracked within the UMIP registry. Zones allow large or complex assets—such as buildings, facilities, or infrastructure systems to be organized into identifiable areas or systems where work, inspections, maintenance, and lifecycle events occur.

By assigning Persistent Infrastructure Identities (PIIDs) to specific zones such as structural components, mechanical systems, equipment areas, or operational sections—lifecycle records remain tied to the exact portion of infrastructure where activity takes place.

This structure enables infrastructure assets to maintain both asset-level identity and system-level traceability, supporting clearer lifecycle records, maintenance history, and risk documentation over time.

An infrastructure asset is typically assigned a primary PIID that represents the asset as a whole. However, complex assets may also include additional PIIDs assigned to defined portions of the asset through the UMIP Zone framework.

This allows major systems, structural components, or operational sections of an asset to maintain their own persistent identity while remaining linked to the primary asset identity. As a result, lifecycle events such as inspections, maintenance activities, repairs, or upgrades can be recorded at both the overall asset level and the specific system or zone where the activity occurred.

This hierarchical identity structure enables more precise lifecycle tracking and clearer infrastructure governance over time.

Yes. The UMIP registry maintains the identity record and lifecycle registry associated with each Persistent Infrastructure Identity (PIID). Infrastructure stakeholders including owners, contractors, inspectors, insurers, and asset managers can upload documents, reports, and lifecycle records directly to the registry.

These records become part of the asset’s persistent infrastructure history. Over time, the registry may contain design documentation, construction records, inspection reports, maintenance activities, repair logs, risk documentation, and other lifecycle information associated with the asset.

External systems may also continue to manage operational data within their own platforms while referencing the PIID as the asset’s stable identity. By connecting records to the same PIID, information from multiple sources can remain linked to the same infrastructure asset across its lifecycle.

This architecture allows infrastructure assets to maintain a persistent digital identity and a continuously growing lifecycle record, supporting clearer asset governance, operational transparency, and long-term infrastructure stewardship.

No. UMIP is designed to complement existing industry systems rather than replace them.

The UMIP registry provides the persistent identity layer for infrastructure assets through the issuance of Persistent Infrastructure Identities (PIIDs). These identifiers allow information generated by different systems such as design platforms, construction management tools, inspection systems, facility management software, and insurance platforms to remain connected to the same physical asset over time.

Organizations may continue using the systems they already rely on to manage operations, documentation, and workflows. By referencing the same PIID, those systems can associate their records with a consistent infrastructure identity while maintaining control of their own operational data.

This approach enables lifecycle continuity across multiple systems while preserving the tools and platforms already used throughout the built environment.

Infrastructure assets generate information across many systems throughout their lifecycle, including design platforms, construction management tools, inspection records, maintenance logs, and insurance documentation. However, these systems often use different identifiers for the same asset, making it difficult to maintain a continuous and reliable record over time.

Persistent Infrastructure Identity provides a stable digital identity for infrastructure assets that remains consistent across systems, ownership changes, and operational transitions. By linking lifecycle records to a single, persistent identifier, infrastructure stakeholders can maintain clearer asset histories, improve governance and documentation continuity, and reduce the operational inefficiencies caused by fragmented records.

This continuity supports more transparent asset management, more reliable lifecycle data, and better long-term stewardship of infrastructure systems.

UMIP is designed for organizations and stakeholders involved in the design, construction, ownership, operation, and risk management of infrastructure assets.

This includes architects, engineers, contractors, property owners, asset managers, facility operators, insurers, inspectors, and other professionals responsible for managing infrastructure systems over their lifecycle.

By providing a persistent identity for infrastructure assets through Persistent Infrastructure Identities (PIIDs), UMIP allows these stakeholders to maintain clearer lifecycle records, documentation continuity, and system-level traceability as assets evolve over time.

The framework supports collaboration across multiple organizations and systems while ensuring that infrastructure information remains consistently linked to the same physical asset.

Infrastructure assets generate large volumes of information throughout their lifecycle, including design documentation, construction records, inspection reports, maintenance activities, and insurance documentation. However, these records are often stored across multiple systems that use different identifiers for the same asset.

As infrastructure changes ownership, undergoes repairs, or moves between operational systems, this fragmentation can lead to incomplete records, lost documentation, and reduced lifecycle continuity.

UMIP addresses this challenge by providing a persistent digital identity for infrastructure assets through Persistent Infrastructure Identities (PIIDs). By linking lifecycle information to a stable identifier, infrastructure records can remain connected to the same physical asset over time, improving documentation continuity, asset governance, and long-term infrastructure management.

UMIP is designed to support a wide range of systems used throughout the infrastructure lifecycle. This includes platforms used for design, construction management, inspection and compliance, facility operations, maintenance tracking, asset management, and risk documentation.

By referencing Persistent Infrastructure Identities (PIIDs), these systems can associate their records with a consistent infrastructure identity while continuing to operate within their own software environments. This allows information generated by different tools and organizations to remain connected to the same physical asset over time.

Through this approach, UMIP enables lifecycle continuity across multiple systems while supporting interoperability throughout the built environment.

Insurance and reinsurance organizations rely on accurate infrastructure records to evaluate risk, manage policies, and assess claims. However, infrastructure data is often fragmented across multiple systems and stakeholders, making it difficult to maintain consistent asset histories over time.

UMIP supports insurance and reinsurance environments by providing a persistent identity for infrastructure assets through Persistent Infrastructure Identities (PIIDs). By linking inspection records, maintenance documentation, system upgrades, and claims-related information to a stable identifier, insurers and reinsurers can maintain clearer infrastructure histories associated with the assets they evaluate.

This continuity helps support more transparent risk assessment, improved documentation during underwriting and claims processes, and stronger lifecycle visibility for infrastructure assets.

UMIP pilot programs are designed to evaluate how Persistent Infrastructure Identities (PIIDs) can support lifecycle continuity for infrastructure assets within real operational environments. Pilots typically involve assigning PIIDs to selected infrastructure assets and recording relevant lifecycle information such as documentation, inspections, maintenance activities, and system updates within the UMIP registry.

Participating organizations continue using their existing operational systems while associating asset records with the assigned PIIDs. This allows stakeholders to evaluate how persistent identity can connect records across systems and organizations while maintaining continuity for the underlying asset.

Pilot programs may include collaboration with asset owners, contractors, facility operators, insurers, and other infrastructure stakeholders to explore how persistent infrastructure identity can support documentation continuity, asset governance, and lifecycle transparency.

UMIP pilot participation is currently coordinated through structured pilot programs with organizations involved in the design, construction, ownership, operation, and risk management of infrastructure assets.

These pilots are intended to evaluate how Persistent Infrastructure Identities (PIIDs) function within real-world infrastructure environments and how lifecycle information can be recorded and maintained through the UMIP registry.

Organizations interested in participating in future pilot programs are encouraged to contact UMIP to learn more about current initiatives and potential opportunities for collaboration.

Organizations can engage with UMIP through pilot programs, research collaborations, and infrastructure identity initiatives involving Persistent Infrastructure Identities (PIIDs). These engagements allow organizations to explore how persistent infrastructure identity can support lifecycle documentation, asset governance, and operational continuity across infrastructure systems.

UMIP works with stakeholders across the built environment including infrastructure owners, engineering and construction organizations, facility operators, insurers, and asset managers to evaluate how persistent identity can be integrated into existing workflows and systems.

Organizations interested in learning more about collaboration opportunities are encouraged to contact UMIP to discuss potential engagement.

UMIP operates a registry and technology framework that supports the issuance and management of Persistent Infrastructure Identities (PIIDs) for infrastructure assets. While the registry is supported by software systems, UMIP is designed primarily as an infrastructure identity layer rather than a traditional software application.

Through the UMIP registry, infrastructure assets can be assigned persistent digital identities and associated lifecycle records including documentation, inspections, maintenance history, and system updates can be recorded over time.

Organizations may interact with the UMIP registry directly or through integrations with the systems they already use throughout the infrastructure lifecycle. This approach allows UMIP to support interoperability across the built environment while maintaining a stable identity framework for infrastructure assets.

Yes. The framework is designed for multi asset and institutional environments, including portfolio level deployment strategies.

The UMIP registry is operated and maintained by UMIP Inc., which oversees the issuance and management of Persistent Infrastructure Identities (PIIDs) and the operation of the infrastructure identity registry.

The framework is designed to provide a neutral and consistent identity layer for infrastructure assets, allowing lifecycle information to remain associated with the same asset across multiple systems and stakeholders over time.

As the framework evolves, UMIP works with organizations across the built environment including asset owners, engineering and construction firms, insurers, facility operators, and other infrastructure stakeholders to support responsible development of the registry and its associated standards.

A PIID record may include identity metadata and lifecycle information associated with the infrastructure asset. This can include documentation such as design records, construction documentation, inspection reports, maintenance logs, repair history, and other operational or risk-related records.

By linking these records to a persistent identity, infrastructure stakeholders can maintain a continuous record of asset activity and documentation throughout the lifecycle of the asset.

Yes. Large infrastructure sites such as campuses, industrial facilities, or complex buildings may contain multiple assets and systems. In these cases, a primary PIID may represent the overall asset, while additional PIIDs can be assigned to defined portions of the asset through the UMIP Zone framework.

This hierarchical structure allows infrastructure assets to maintain both asset-level identity and system-level traceability across the lifecycle of the asset.

A Persistent Infrastructure Identity (PIID) is issued through the UMIP registry. During issuance, the infrastructure asset or defined asset zone is recorded within the registry and assigned a globally unique identifier.

The issuance process establishes the asset’s identity record within the registry, allowing lifecycle documentation, inspections, maintenance records, and other operational information to be associated with the asset over time.

Yes. Each PIID issued through the UMIP registry can be verified through the registry system. Verification allows stakeholders to confirm the existence of the identifier and review associated identity records and lifecycle documentation where access permissions allow.

This verification capability supports transparency and helps ensure that infrastructure records remain associated with the correct physical asset.

Yes. UMIP is designed to support interoperability with systems used throughout the infrastructure lifecycle. Design platforms, construction management systems, inspection tools, facility management software, and insurance systems can reference PIIDs to associate their records with the same infrastructure asset.

This approach allows organizations to continue using their existing tools while maintaining continuity of infrastructure identity across systems.