Optimize Asset Utilization
Description
The focus for this smart service is on digital specification of assets and its components, both software and hardware. This data can be provided by the manufacturer and the keeper/manager for this asset. It includes the evolvement of the asset (lifecycle) and its usage data.
The asset can be a
- Movable
- Locomotive
- Wagon
- Intermodal Unit
- Immovable
- Location (facility, point, station, yard)
- Section (segment, route)
The technical data of an asset includes the technical specification of:
- the type of asset
- the modification and enhancement of the individual instance
- additional features of the individual instance
- the actual restrictions and limitations of the individual instance
It covers both the hardware and software features of the asset.
Use Case
RU retrieves technical asset data digitally
The RU retrieves digitally the necessary technical data for the asset. The retrieval for the wagon asset is described here: Rolling Stock Retrieval Workflow
RU provides usage data to keeper digitally
When using an asset the RU sends the data digitally to the keeper.
Asset usage
The RU sends the usage data of an asset to the maintaining keeper. Wagon Performance Workflow
Asset faulty technical data
The RU also sends any faulty technical asset data to the keeper as input for correction.
Asset damage
The RU reports any damage that he detects during a technical check back to the keeper. Wagon Damage Workflow
Asset Keeper maintains the technical data digitally
The asset keeper updates and maintains actively the technical data of the asset.
Preconditions
- Standardized digital asset specification (legal)
- Legally binding to digital representation (legal)
Basic Services
Dependencies
This topic depends on the bottom up capabilities
Location
- #1 CRD Location
- #2 CRD
- #5 CRD
- #6 CRD
Wagon
- #36
- #39
- #42
- #43
- #44
- #45
- #46
- #105
The topic is linked to the Damage Information smart service. The second one covers a part of this extensive service.
Planned Steps
Evaluation
This used to be uses cases in the “VDV” project (“elektr. Lok- und Zugakte”); collecting all relevant operational data for the vehicles for the moment “train is running” or “will be running”. Assumption is, that all stakeholders deliver current data, like the temporary “owner” of a loco feeds the “platform” with the latest error-codes or workshop/maintenance repairs. Discussions so far showed, that the business model for this is difficult to establish so it can be guaranteed, that the information-pool is valid. Another problem is, that only parts of master data is currently online in certain databases like “RSRD2”. Some data in RSRD2 is already available, but apparently unfortunately wrong.
