If Your PMIS Isn’t Asset-Centric, You’re Solving the Wrong Problem
Why capital program leaders need to start thinking about asset outcomes before the first project begins
by Jack Dempsey June 2026 - 7 minute read
Most organizations implement a Project Management Information System (PMIS) to improve project delivery: better schedules, better cost control, better reporting. Those are important goals. But they miss a more important question…
What happens to the asset after the project is complete?
If your PMIS strategy does not start with an asset-centric lifecycle perspective, you may improve project execution while unintentionally making long-term asset management more difficult. And for organizations responsible for large portfolios, that can have consequences measured in decades and billions of dollars.
The uncomfortable truth is this: Capital programs are historically optimized to deliver projects, not to deliver asset outcomes. That distinction matters more than most owners realize.
Asset Management Is About Outcomes
One of the phrases I’ve often used is simple but powerful:
“Better asset management leads to better outcomes.”
Those outcomes vary from organization to organization, but they generally fall into four categories:
- Mission performance – infrastructure enables the organization to deliver its core mission.
- Financial performance – investments are optimized for lifecycle value, not just initial cost.
- Risk management – infrastructure is resilient, reliable, and prepared for disruptions.
- Sustainability – assets support long-term environmental and operational goals.
Modern asset management systems such as defined by ISO 55001 formalize this idea: infrastructure assets should be managed in a way that balances performance, risk, and cost to achieve organizational objectives.
But that balance becomes much harder when asset data is fragmented across disconnected systems and organizational silos. And that fragmentation almost always begins during capital project delivery.
The Industry’s Blind Spot: The Handover Gap
Most organizations treat project delivery and asset operations as separate domains. Projects are managed in one set of tools and processes. Operations are managed in another. The connection between them — asset data handover — is often treated as an afterthought.
The result is predictable. Consider a common scenario we’ve seen repeatedly across large infrastructure portfolios:
A new facility is completed and ready to open. But the building systems — HVAC, electrical, security, etc. must be managed through a computerized maintenance management system (CMMS). That system requires structured asset data: equipment lists, locations, maintenance procedures, warranty information, and more.
Unfortunately, that information was not collected in a usable format during project delivery.
So, before the building can operate, the organization must:
- recreate the asset inventory
- audit and validate equipment data
- populate the CMMS database
- reconcile discrepancies between drawings, models, and reality
This process can take months.
In extreme cases, buildings sit idle while teams manually reconstruct the asset database that should have been created during construction.
The cost of that delay is rarely attributed to the capital program. But it is a direct consequence of how projects were delivered.
Managing Assets vs. Asset Management
Another source of confusion comes from the difference between managing assets and asset management. They sound similar, but they are fundamentally different.
Managing assets is what you do to assets. It focuses on the lifecycle of individual assets:
maintaining equipment, replacing components, scheduling inspections.
Asset management is what you do with assets, in contrast, it focuses on organizational outcomes:
how infrastructure investments support mission performance, financial goals, and risk tolerance.
This distinction is critical. Lifecycle maintenance decisions affect capital planning.
Capital investments affect operational risk. Operational performance affects mission readiness and financial outcomes. When these domains are disconnected, organizations make decisions that optimize locally but fail globally. The goal of an asset-centric lifecycle strategy is to connect these perspectives.
Why Capital Programs Must Become Asset-Centric
For decades, capital programs have been structured around delivering projects. But the value of infrastructure is not created at project completion. It is created over the entire lifecycle of the asset. That lifecycle can span 30, 50, or even 100 years.
If asset data is not captured and structured correctly during design and construction, organizations will struggle with: incomplete asset inventories, inconsistent equipment hierarchies, unreliable lifecycle cost forecasts, disconnected capital and maintenance planning, and poor visibility into asset performance
These problems compound over time. Eventually organizations find themselves trying to answer strategic questions without reliable data. Without a strong asset data foundation, those decisions about replacement of aging assets, risks associated with an asset portfolio, or planning and prioritizing capital spend all become guesswork.
A Different Approach: Asset-Centric Project Delivery
An asset-centric approach changes how organizations think about capital programs. Instead of asking, “How do we deliver this project?”, Owners begin by asking, “How will this asset perform across its entire lifecycle—and how does this generate value for the organization?”
That shift changes the role of project systems. A PMIS should not simply track project workflows. It should help ensure that every capital project contributes to the long-term asset strategy by:
- capturing structured asset data during delivery
- linking project information to the asset inventory
- supporting asset data handover to operations systems
- enabling lifecycle performance analysis
This requires integration across the systems that manage asset information throughout the lifecycle, including:
- PMIS platforms used for capital delivery
- CMMS systems used for maintenance and operations
- BIM and digital engineering environments
- GIS platforms managing location and spatial data
- ERP systems supporting financial planning
When these systems are connected through an asset-centric data architecture, organizations can begin to manage infrastructure portfolios strategically rather than reactively.
The Technology Opportunity
Today, most technology platforms in the built environment still operate within narrow domains. Some systems focus on project delivery. Others focus on facility operations. Very few bridge the two effectively. That gap creates an opportunity for a new generation of platforms capable of supporting true lifecycle asset management. Platforms like Kahua are beginning to move in this direction.
Kahua’s asset-centric data architecture allows project delivery processes to be structured around the assets being created or modified. This makes it possible to capture the information needed for long-term asset management during project execution, rather than reconstructing it later. By connecting project data with asset inventories and operational systems, this approach can:
- support lifecycle thinking during capital planning
- bridge project delivery and asset data handover
- enable more strategic asset management decision-making
Over time, this foundation could evolve into the basis for next-generation Asset Management Systems (AMS) that integrate capital planning, project delivery, operations, and performance analytics on an enterprise level. But technology alone is not the solution. The real transformation comes from how organizations think about infrastructure.
A Call to Owners
If you are evaluating a new PMIS or modernizing your capital program systems, there is one question worth asking early:
Does this system help us manage projects, or does it help us manage assets?
The difference is profound. Organizations that continue to separate capital delivery from asset management will struggle with fragmented data, inefficient decision making, and missed opportunities to optimize their infrastructure portfolios.
Those that adopt an asset-centric lifecycle strategy can unlock something far more powerful: infrastructure that actively supports organizational success.
And that journey begins with the systems and processes used to deliver projects today.
Interested in learning more? Join ICAC and be part of the solution! theicac.org/join