|
|
| Line 1: |
Line 1: |
| {{UseCase|IS|2.3|title=Maintenance Planning|RS=1|abbr=MAPL}} | | {{mirror}} |
| | |
| {{UC title}}
| |
| Maintenance Planning; {{Deu|Wartungsplanung}}; {{Fra|nom descriptif en Francais}}
| |
| | |
| {{UC description}}
| |
| The application focuses the transfer of infrastructure data from an asset management source system (e.g. DfA in Switzerland) to the maintenance planning system of the infrastructure manager.
| |
| | |
| {{UC flows}}
| |
| The data flow is one-directional: It goes from the (central) asset management source data base to the maintenance planning system of the infrastructure manager.
| |
| There are two types of data flows:
| |
| * Initial full transfer (realized outside the defined interface, done only once)
| |
| * Delta transfer of updated elements
| |
| | |
| [[file:Data_Flows_for_Mainteanance_Planning_use_case.png|800px|Figure 1: Data flows for maintenance planning use case]]
| |
| | |
| {{UC interference}}
| |
| * rolling stock
| |
| | |
| {{UC data}}
| |
| This section serves to specify the required data regarding certain aspects.
| |
| | |
| {{UC update}}
| |
| * monthly
| |
| | |
| {{UC complexity}}
| |
| * tiny
| |
| | |
| {{UC focus}}
| |
| * Signaling
| |
| * Construction
| |
| * Geodasy (coordinates)
| |
| | |
| {{UC elements|IS}}
| |
| * Topology:
| |
| ** Lines
| |
| ** Operational points
| |
| ** tracks
| |
| * Asset types:
| |
| ** Trackbed (“Fahrbahn”)
| |
| ** Railway electrification system (“Bahnstrom”)
| |
| ** Signaling (interlockings, signals, signalling components)
| |
| ** Bridges, tunnels
| |
| ** Walls, sewing systems
| |
| ** Station building infrastructure
| |
| ** Platforms
| |
| ** Telecommunication infrastructure
| |
| * Special railway vehicles:
| |
| ** Maintenance railway vehicles
| |
Revision as of 17:49, 24 November 2019