A traffic signal may be physically intact, connected to a control center and visible on a digital map yet still remain non-functional for months.
The problem may not be the sensor, network or software.
The maintenance contract may have expired. The vendor may be waiting for payment. Spare parts may not be covered. The service-level agreement may have no active owner.
Yet most digital twins would continue displaying the signal as an asset with a location, specification and operational status.
They would show what the asset is.
They would not show whether the institutional and commercial arrangements needed to keep it operational are still alive.
That is a serious gap.
Physical assets depend on contractual infrastructure
Infrastructure does not operate through technology alone.
A smart traffic system, water network, solar plant, airport, data center or industrial facility relies on a chain of commitments:
- Equipment warranties
- Annual maintenance contracts
- Software licenses
- Connectivity subscriptions
- Cloud services
- Calibration schedules
- Cybersecurity certificates
- Spare-parts agreements
- Performance guarantees
- Insurance coverage
- Regulatory approvals
- Utility-supply commitments
- Vendor response obligations
These are not administrative attachments to the asset.
They are part of its operating system.
When one of these commitments expires or becomes disputed, the physical asset may remain in place while its operational reliability begins to decline.
A digital twin that tracks sensor readings but ignores these dependencies sees only part of the asset’s condition.
An asset can be technically healthy and operationally exposed
Consider a pump in an urban water network.
Its current vibration and temperature readings may be within acceptable limits. From a condition-monitoring perspective, the pump appears healthy.
But what if:
- Its warranty expired last month?
- The maintenance contractor has not been renewed?
- The required replacement bearing is unavailable locally?
- The remote-monitoring license will expire in ten days?
- The vendor’s response-time commitment is under dispute?
- The maintenance budget has not been released?
The pump is functioning, but its operational resilience is weakening.
This is a different type of risk. It cannot be identified through IoT telemetry alone.
The same issue appears across smart infrastructure.
A surveillance camera may be working while its cybersecurity certificate has lapsed. A solar inverter may be reporting normally while its service provider has withdrawn support. A building-management system may remain online while its software license is approaching expiry. A public EV charger may be installed but unavailable because the payment gateway agreement has failed.
The asset state and the contract state must therefore be evaluated together.
The twin needs a commitment layer
Most digital twins organize information around three broad layers:
- The physical asset
- Its current data and behavior
- The analytical or simulation model
A decision-ready twin requires another layer: the commitments that determine who must act, under what conditions and within what time.
This commitment layer should connect every critical contract or obligation to the relevant asset, location, service and responsible organization.
A practical record could include:
Commitment → affected asset → responsible party → validity period → performance obligation → monitoring evidence → current status → escalation path
For an annual maintenance contract, the twin should know:
- Which assets are covered
- When the contract begins and ends
- What preventive maintenance is required
- Which fault classes are included
- The permitted response and restoration times
- Who validates completed work
- What evidence the vendor must submit
- What happens when the obligation is missed
This turns the contract from a stored PDF into an operational control.
Move from document storage to contract intelligence
Many organizations already keep contracts in ERP, procurement or document-management systems.
The problem is that these records are rarely connected to live asset conditions.
The maintenance team may see the fault but not the commercial obligation. Procurement may see the contract date but not the asset failure. Finance may see an unpaid invoice but not understand that it is delaying restoration of a critical service. Management may see an availability dashboard without seeing which failures have crossed contractual thresholds.
A digital twin can connect these separated views.
When an asset reports a fault, the platform should determine:
- Whether the asset is under warranty or maintenance coverage
- Which organization is responsible
- Which service level applies
- When the response clock started
- Whether acknowledgement, attendance and restoration targets were met
- What evidence confirms completion
- Whether payment, penalty or escalation conditions were triggered
This is where the twin begins supporting accountability rather than merely visibility.
Contract status should change operational decisions
Tracking contract dates is useful, but the real value comes when contract status changes the next action.
For example:
- A fault on a covered asset should automatically enter the vendor workflow.
- A fault outside coverage should trigger an internal maintenance or procurement route.
- A license approaching expiry should be escalated before service interruption.
- Repeated SLA failures should affect vendor performance scoring.
- An unapproved change should prevent contract closure.
- Missing restoration evidence should keep the incident open.
- A disputed obligation should be visible as an operational risk, not hidden in email correspondence.
The twin should also distinguish between different confidence levels.
A vendor may report that work is complete. The asset may still be offline. A technician may upload a photograph, but the timestamp or asset identity may not match. A sensor may show recovery, while field acceptance is still pending.
Closure should therefore require an evidence chain:
Fault detected → obligation identified → work assigned → action recorded → condition verified → authorized acceptance → contract outcome updated
This makes contractual performance measurable against the actual state of the asset.
The commercial consequences extend beyond maintenance
A contract-aware twin can improve several business functions.
For asset owners, it can expose upcoming coverage gaps before they become failures.
For operations teams, it clarifies responsibility and reduces time lost between departments and vendors.
For procurement, it provides evidence for renewals, renegotiations and supplier evaluation.
For finance, it connects payments and penalties to verified performance.
For regulators and public agencies, it creates an auditable record of whether essential infrastructure is being maintained as promised.
For investors and insurers, it provides a more realistic view of operational risk. Two physically similar assets may carry very different risk profiles because one has active maintenance, parts availability and response coverage while the other does not.
Lifecycle cost and resilience cannot be understood from asset condition alone.
Start with the contracts that can stop operations
Not every agreement needs to enter the twin immediately.
The first priority should be commitments whose failure can interrupt service, compromise safety or weaken compliance.
A focused implementation could begin with:
- Annual maintenance contracts
- Critical equipment warranties
- Software and connectivity licenses
- Statutory inspection and certification
- Cybersecurity and firmware support
- Spare-parts availability
- Emergency-response agreements
The initial objective is simple: identify which assets become operationally exposed when a commitment expires, fails or remains unresolved.
From there, the organization can introduce alerts, workflows, evidence requirements and performance analytics.
A living asset needs living obligations
Infrastructure owners often invest heavily in mapping assets, connecting sensors and building dashboards. But an accurate model of the physical system is not enough.
The asset remains operational because multiple organizations continue to fulfil multiple commitments.
Those commitments have owners, deadlines, conditions, dependencies and consequences. They can weaken even when the asset still appears healthy.
A digital twin should therefore answer more than:
What is happening to the asset?
It should also answer:
Who is obligated to keep it working, is that obligation still active, and what evidence shows that it is being fulfilled?
The next generation of digital twins will not only model physical systems.
They will make the agreements surrounding those systems operational, measurable and visible.
Because an asset is not truly alive when its model is current.
It is alive when the responsibilities that sustain it remain active.