Asset Management and CMMS
Persistent structure identity for the systems that operate the built world.
Computerized Maintenance Management Systems, enterprise asset management platforms, facilities applications, and operational technology help organizations manage the physical environments they depend on.
Work orders change.
Equipment changes.
Vendors change.
Software changes.
Ownership changes.
The physical structure remains.
Asset Management and CMMS
The CMMS can change. The structure identity should not.
PIID™ gives each qualifying structure a persistent identity that can remain consistent across maintenance, inspections, facilities operations, capital planning, system migrations, and decades of asset life.
The asset identity problem
Operational systems know the work.They do not always share the same structure identity.
Asset management environments already contain extensive identifiers.
Site IDs.
Building numbers.
Location codes.
Asset IDs.
Equipment tags.
Work order numbers.
Portfolio IDs.
Internal property keys.
Vendor identifiers.
Those references are valuable inside the systems that created them.
But they are not necessarily designed to persist with the physical structure across software platforms, operators, owners, organizations, or time.
PIID™ provides a persistent identity for the qualifying physical structure itself.
Operational identifiers describe the asset within a system. PIID™ identifies the structure across systems.
- Site code
- Building code
- Work order
- CMMS ID
Structure identity, not equipment identity
PIID™ complements the asset hierarchy.
A facility contains many assets.
HVAC equipment.
Electrical systems.
Pumps.
Elevators.
Roofing systems.
Fire protection equipment.
Mechanical components.
Production equipment.
Building systems.
Those assets should continue using the equipment identifiers, serial numbers, tags, and classifications required by their operational systems.
PIID™ serves a different role.
It persistently identifies the qualifying physical structure that provides context for those assets.
Equipment keeps its identifiers. PIID™ identifies the structure.
The structure as the persistent context
Every operational record happens somewhere.
A work order occurs at a structure.
An inspection concerns a structure.
A capital project affects a structure.
A maintenance record belongs within a structure context.
A facility manager operates a structure.
A digital twin represents a structure.
A risk assessment evaluates a structure.
PIID™ gives those workflows a persistent physical reference capable of continuing beyond the software currently managing them.
The structure becomes the persistent context around operations.
CMMS continuity
Preserve structure identity across generations of maintenance technology.
Organizations change CMMS platforms.
Databases are migrated.
Properties are acquired.
Facilities teams reorganize.
Naming conventions evolve.
Building numbers are reassigned.
Data is imported from legacy systems.
The physical structure may remain the same throughout every transition.
PIID™ provides a structure reference that can remain consistent across those changes.
Systems migrate. Structure identity persists.
PIID Resolve™
Resolve operational references to the physical structure.
PIID Resolve™ identifies, validates, and resolves supported references to persistent infrastructure identity.
Supported inputs can include:
Normalized Address
Parcel
PIID™
Coordinates
Geometry
Supported Source Reference
Asset management platforms can use PIID Resolve™ to reconcile supported site references, property records, spatial references, and enterprise identifiers to the same physical structure.
Submit a reference. Resolve the structure. Return persistent identity.
PIID Resolve™Asset hierarchies
Give the building hierarchy a persistent root.
Many asset management systems organize information through hierarchies.
Portfolio.
Property.
Site.
Building.
Floor.
Space.
System.
Equipment.
Component.
PIID™ can provide a persistent structure level reference within that hierarchy.
The operational platform can continue managing equipment and component relationships while PIID™ maintains a consistent identity for the physical structure.
A persistent structure reference strengthens the hierarchy around it.
Multi structure properties
One facility can contain many physical structures.
Campuses and complex properties can contain numerous qualifying structures.
Hospitals.
Universities.
Industrial sites.
Government complexes.
Corporate campuses.
Multifamily properties.
Distribution centers.
Research facilities.
Manufacturing sites.
A single address, site code, or parcel may represent the entire property.
PIID™ allows each qualifying physical structure to maintain its own identity.
One property. Many structures. Persistent identity for each qualifying asset.
UMIP Structure Schedule™
Document every qualifying structure within the property.
UMIP Structure Schedule™ is being developed to provide a documented inventory of qualifying structures associated with a property.
Each structure can be referenced through its PIID™, location, geometry, and relationship to the parcel.
For asset management and CMMS environments, Structure Schedule™ can establish a clearer structure inventory before operational assets, systems, work orders, and records are organized underneath it.
Know what structures exist. Know where they are. Know which structure is being operated.
Coming Soon
In development
Work order continuity
The work order ends.The structure remains.
Work orders are temporary operational records.
A structure may accumulate thousands of them across decades.
Different platforms may manage those work orders at different times.
PIID™ provides a persistent structure reference through which supported maintenance activity can retain consistent physical context.
Many work orders. One physical structure. One persistent identity.
Maintenance history
Maintenance history becomes more useful when the physical asset stays consistently identified.
A structure may experience decades of:
Preventive maintenance.
Corrective maintenance.
Inspections.
Repairs.
System replacements.
Roof work.
Mechanical upgrades.
Electrical improvements.
Safety work.
Renovations.
Capital projects.
Lifecycle™ provides the framework through which supported records and events can remain connected around the same persistent structure identity through time.
Maintenance changes the asset. Persistent identity keeps the context connected.
Lifecycle™Inspections
Keep inspection history connected to the structure inspected.
Facilities and asset environments can involve many forms of inspection.
Building condition assessments.
Safety inspections.
Fire inspections.
Roof inspections.
Mechanical inspections.
Electrical inspections.
Regulatory inspections.
Insurance inspections.
Engineering assessments.
PIID™ provides a persistent structure identity around which supported inspection references can remain organized.
Different inspections. Same physical structure. Persistent identity between them.
Capital planning
Long term investment needs long term asset identity.
Capital plans can extend across years or decades.
A physical structure may undergo:
Major repairs.
Roof replacement.
Mechanical upgrades.
Electrical modernization.
Energy improvements.
Accessibility projects.
Structural work.
Expansion.
Renovation.
Technology upgrades.
PIID™ provides a persistent structure reference capable of continuing across those capital programs.
Capital projects change. The structure identity carries forward.
Facility handoff
Operational identity should survive changes in responsibility.
Facilities change hands.
Property managers change.
Service providers change.
Owners change.
Maintenance teams change.
Contractors change.
Software changes.
Without persistent structure identity, each transition can create another opportunity for records and references to fragment.
PIID™ provides a consistent reference to the physical structure underneath those organizational changes.
Responsibility can transfer without resetting the identity of the asset.
Portfolio management
One persistent structure reference across the portfolio.
Large organizations may operate hundreds or thousands of structures assembled through different systems, acquisitions, regions, owners, and technology environments.
PIID™ provides persistent structure identity across supported portfolios.
This can support:
Portfolio Normalization
Structure Reconciliation
Property Alignment
Capital Planning
Maintenance Analytics
Risk Analysis
Facilities Operations
System Migration
Enterprise Reporting
One portfolio. Many structures. Persistent identity at the structure level.
Acquisitions and divestitures
Ownership changes should not reset physical asset identity.
When properties are acquired, operational systems frequently need to reconcile inherited data.
Building names may differ.
Site numbers may change.
Internal identifiers may be replaced.
Legacy systems may use different hierarchies.
PIID™ remains associated with the physical structure.
That persistent reference can provide stronger continuity as the property moves between owners and technology environments.
New owner. New systems. Same physical structure.
System migration
Move the application without losing the structure reference.
CMMS and EAM migrations can require organizations to reconcile years of asset and location information.
PIID™ provides a persistent structure reference that can exist independently of the platform being migrated.
The source CMMS can reference PIID™.
The destination CMMS can reference the same PIID™.
The surrounding operational data can change systems without requiring the physical structure to receive a new identity.
Migrate the system. Preserve the structure reference.
GIS and mapping
Connect operational assets to persistent spatial context.
Asset management environments often integrate with GIS and mapping systems.
PIID Resolve™ can reconcile supported spatial references to persistent structure identity.
Together, they create stronger continuity among:
CMMS
GIS
Property Context
Building Geometry
Physical Structure
PIID™
Location tells you where. PIID™ tells you which structure.
GIS, Mapping and Geospatial IntelligenceCAD, BIM and digital delivery
Connect project information to the structure operations inherit.
Design and construction environments create detailed information before the asset enters long term operation.
CAD and BIM systems may maintain project specific identifiers and model references.
Facilities teams may later operate within entirely different systems.
PIID™ provides a persistent structure identity capable of connecting supported project and operational environments to the same physical asset.
The project ends. Operations continue. Structure identity carries forward.
CAD, BIM and Digital DeliveryDigital twins and simulation
Give the operational model a persistent physical reference.
Digital twins increasingly combine building geometry, operational information, maintenance records, sensors, analytics, and simulation.
The digital representation can evolve.
The underlying physical structure remains.
PIID™ provides a persistent structure identity beneath the digital twin.
Lifecycle™ provides continuity through time.
Digital representations change. Physical asset identity should persist.
Digital Twins and SimulationArtificial intelligence
AI needs stable physical asset context.
AI is increasingly entering maintenance, facilities, reliability, operations, capital planning, and enterprise asset management.
AI systems may analyze:
Work orders.
Maintenance history.
Inspection reports.
Energy information.
Building systems.
Images.
Documents.
Risk data.
Digital twins.
Enterprise records.
PIID™ provides a persistent structure identity around which supported information can coordinate.
Persistent identity creates persistent machine context.
AI agents and automation
Automated systems should know which physical structure they are acting on.
AI agents and automated workflows can increasingly move between systems and act on infrastructure information.
Those workflows become more reliable when the physical structure maintains a consistent identity.
A maintenance agent.
A capital planning workflow.
A risk model.
A facilities assistant.
An inspection application.
An enterprise integration.
Each can reference the same PIID™ for the physical structure.
Automation moves faster when identity does not need to be rebuilt every time.
Energy and building performance
Connect performance information to the persistent structure.
Facilities teams increasingly manage energy consumption, efficiency, electrification, building performance, sustainability, resilience, and distributed energy.
Those systems may maintain different site and building references from the CMMS.
PIID™ provides a persistent physical structure reference through which supported energy and operational environments can coordinate.
Performance changes. Structure identity persists.
Insurance and risk
Connect facilities context to the structure carrying the risk.
Asset management and CMMS environments can contain valuable operational context about the physical structure.
Insurance and risk environments may describe the same asset through different references.
PIID™ provides a persistent structure identity capable of serving as a common reference across supported facilities, property, risk, and insurance workflows.
Different workflows. Same physical asset.
Lifecycle continuity
The structure can outlive every operating system around it.
A physical structure may remain in service for fifty years or more.
During that time, it may experience multiple:
Owners.
Operators.
CMMS platforms.
Facilities teams.
Capital programs.
Renovations.
Insurance relationships.
Technology migrations.
Service providers.
Lifecycle™ provides the framework through which supported records, relationships, and events can remain connected around the same persistent PIID™ through those changes.
The operating environment changes. The structure identity persists.
Lifecycle™Cross system interoperability
Facilities technology does not need another silo.
CMMS.
EAM.
GIS.
BIM.
Digital twins.
Energy systems.
Risk platforms.
Document systems.
Enterprise data platforms.
AI.
These systems serve different purposes.
They do not need to become one application.
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 operational data.
UMIP does not require CMMS providers, facilities teams, enterprise customers, or data partners to move all underlying operational information into a central repository.
Existing systems can remain.
Existing identifiers can remain.
Operational records can remain within the platforms responsible for them.
PIID™ provides the persistent structure reference through which supported systems can coordinate.
Connection does not require centralization.
CMMS and EAM providers
Add persistent physical structure identity to the platforms customers already use.
CMMS and enterprise asset management providers can integrate PIID™ as a persistent structure reference within existing applications.
PIID™ can complement platform specific site, location, and building identifiers without replacing them.
This can support continuity across:
Customer Implementations
Portfolio Environments
System Migrations
Acquisitions
GIS Integrations
BIM Integrations
Digital Twins
Data Platforms
AI Workflows
Enterprise Applications
Give the operating system a structure identity that exists beyond the operating system.
Enterprise delivery
Built for direct integration.
PIID Resolve™ is designed for integration into asset management, facilities, geospatial, digital twin, analytics, and enterprise technology environments.
Supported structured 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 facilities and asset operations.
PIID™
Provides persistent identity for each qualifying physical structure.
PIID Resolve™
Resolves supported operational, property, and spatial 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 structure identity requires consistent rules.
Asset management environments span organizations, properties, software platforms, service providers, ownership transitions, 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 enterprise systems operate around.
- 189M+PIIDs Registered Across the United States
Facilities operations are becoming more connected, automated, data driven, and intelligent.
As operational systems become more sophisticated, the need for a persistent physical structure reference becomes more important.
Structure Identity → Operational Interoperability → Lifecycle Continuity → Connected Asset Intelligence
Asset Management and CMMS
The system manages the work.PIID™ identifies the structure.
CMMS platforms will change.
Asset hierarchies will change.
Maintenance programs will change.
Operators will change.
Technology will change.
The physical structure remains.
PIID™ provides a persistent identity capable of continuing across the systems and organizations responsible for operating it.
The CMMS can change. The structure identity should not.
Related
Resolve physical structures to persistent infrastructure identities. PIID Resolve™ identifies, validates, and resolves structures from addresses, parcels, coordinates, geometry, and supported source records.