UC:IS:MaintenancePlanning: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
No edit summary |
(Standardization) |
||
| Line 1: | Line 1: | ||
{{UseCase|IS|2.3|title=Maintenance Planning}} | |||
{{UC title}} | |||
Maintenance Planning; {{Deu|Wartungsplanung}}; {{Fra|nom descriptif en Francais}} | 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. | 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. | 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: | There are two types of data flows: | ||
| Line 18: | Line 15: | ||
[[Datei:Data_Flows_for_Mainteanance_Planning_use_case.png|Figure 1: Data flows for maintenance planning use case]] | [[Datei:Data_Flows_for_Mainteanance_Planning_use_case.png|Figure 1: Data flows for maintenance planning use case]] | ||
{{interference}} | |||
* rolling stock | * rolling stock | ||
{{UC data}} | |||
This section serves to specify the required data regarding certain aspects. | This section serves to specify the required data regarding certain aspects. | ||
{{UC update}} | |||
* monthly | * monthly | ||
{{UC complexity}} | |||
* tiny | * tiny | ||
{{UC focus}} | |||
* Signaling | * Signaling | ||
* Construction | * Construction | ||
* Geodasy (coordinates) | * Geodasy (coordinates) | ||
{{UC elements}} | |||
* Topology: | * Topology: | ||
** Lines | ** Lines | ||
Revision as of 18:09, 23 June 2016
| Maintenance Planning Subschema: Infrastructure | ||
| ||
| For general information on use cases see UC:Use cases |
Use case / Anwendungsfall
Maintenance Planning; Wartungsplanung;
Description / Beschreibung
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.
Data Flows and Interfaces / Datenflüsse und Schnittstellen
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
Figure 1: Data flows for maintenance planning use case
- rolling stock
Characterizing Data / Charakterisierung der Daten
This section serves to specify the required data regarding certain aspects.
How often do the data change (update)?
- monthly
How big are the data fragments to be exchanged (complexity)?
- tiny
Which views are represented by the data (focus)?
- Signaling
- Construction
- Geodasy (coordinates)
Which specific data do you expect to receive/send (elements)?
- 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