Infrastructure asset data and handover register
The facility's location, equipment and maintenance data are prepared for the operator. Documents of the transfer, shortcomings and what has already been accepted are visible.
The operator's need for information is not tied to the property actually installed, its changes and the course of its reception. The data transmitted is not suitable for the maintenance register or part of the property has to be re-adjusted on the spot.
How the solution works
- The operator determines the required asset structure, data used and acceptance criteria.
- The design candidates are linked to the actual installation of the facility and its approved changes.
- The submission of data is checked against a specific type of asset and the necessary proof.
- The defect is returned to the responsible participant, and the accepted volume is transferred to the operational register.
- A subsequent change preserves the property's history and updates the communications required for maintenance.
Key challenges
- No operational data is available
Solution capabilities
Operational information needs
Data is collected that is needed for identification, maintenance and applicable responsibility; design attributes are not moved solely because of their abundance.
Property Structure and Facility Codes
The object is linked to an equipment, section or other operating unit while maintaining the difference between the project and the actual property.
Evidence of actual transmission
The technical feature and location have an approved source; the target unit is not automatically considered to be mounted.
The course of the shortcomings and reception
The dataset is checked by the designated employee, notes the shortcomings and confirms which part of it is suitable for transfer to the asset operator.
History of Documents and Changes
Instruction, guarantee basis and asset correction remain linked to the right unit and validity.
Business context
- No operational data is available
- The operator's need for information is not tied to the property actually installed, its changes and the course of its reception. The data transmitted is not suitable for the maintenance register or part of the property has to be re-adjusted on the spot.
- The operator receives a history of the object prepared for use
- The value of a completed infrastructure object also depends on its proper maintenance. Linked asset codes, locations and documents allow verification of the completeness of the transfer. It is easier for the customer to accept the result and for the contractor to identify and complete the remaining agreed upon submissions.
Core features
- Operational information needs
- Property Structure and Facility Codes
- Evidence of actual transmission
- The course of the shortcomings and reception
- History of Documents and Changes
Key integrations
- Project Information Environment
- The technical basis, actual changes and transfer documents have been approved.
- Geographic Property Data
- Location, stretch of the operational unit and its connection to infrastructure.
- Existing Assets and Oversight Framework
- The structure, the necessary properties and the answer to a successful transfer or defect are accepted.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Re-creation of asset data after transmission
6–25%Decreasing
This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.
Active work on asset structure and technical information recovery is measured for a comparable group of objects.
Improper Submissions of Property Data
5–25%Decreasing
This illustrative scenario assumes that 20-50% of missed actions can be identified through task and deadline tracking. That share is assumed to fall by 25-50%. Company data is needed to verify both the addressable share and the resulting change.
Resubmissions due to inappropriate content or connection are counted, separately from the legally pending installation.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- The object has been transferred, but the maintainer is re-creating the equipment list from drawings and folders.
- The design product features remained in the register, although another approved unit was actually installed during construction.
Implementation requirements
The operator determines what property data is required for maintenance and other actions after the transfer. Relationships of design elements to actual facilities, documentation requirements and acceptance rules are combined with the property register used.
Further development options
- Transfer of additional asset classes according to their specific operational needs
- Marking an object locally when it facilitates its reliable recognition