Difference between revisions of "Facilities on location"
(Created page with " == Description == The service provides information about facilities, restrictions and capabilities of a location. == Use Case == == Preconditions == === Basic Services ==...") |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | == Description == | ||
| − | + | The smart service provides information about | |
| + | * facilities, | ||
| + | * restrictions and | ||
| + | * capabilities | ||
| + | of a location and the connecting segment. Operated by IMs or private, for passenger of freight. | ||
| − | + | Easy to fill with content and should be easily accessible either via APIs or web. Connection to other location data bases creating only one common interface for location handling be it IM / data interchange or physical details of a location. Geofencing of locations to support seamless track & trace solutions. | |
== Use Case == | == Use Case == | ||
| + | |||
| + | * Source for new / existing railway customers to investigate if possible to transport to a certain location | ||
| + | * To create transparency of existing locations for RUs | ||
== Preconditions == | == Preconditions == | ||
| + | Available data and sufficient data quality | ||
| − | + | == Basic Services == | |
| + | SM08 [[Siding Everywhere]] | ||
== Dependencies == | == Dependencies == | ||
| + | |||
| + | Existing location databases as | ||
| + | * CRD | ||
| + | * Rail facilities portal, | ||
| + | * RINF, | ||
| + | * DIUM | ||
| + | * Geo editor | ||
| + | |||
| + | A potential solution is described at [[GEO Model]] | ||
== Planned Steps == | == Planned Steps == | ||
== Evaluation == | == Evaluation == | ||
| + | |||
| + | * Michel Thuering commented 20 Apr 2021 12:32 | ||
| + | I consider SM_17 Facilties on location to be sensible with a view to uniform data collection. As SBB Cargo, the business value is not yet clear to me, as today this task is guaranteed by the infrastructure manager. As a company, I therefore do not yet have a return on investment - no simplification of processes, less administrative effort or a gain in time, do I? | ||
| + | * Frank Kschonsak on 25 June | ||
| + | Information provided should be applicable for the creation of the TSI OPE Route Book (see Guide for the application of TSI OPE – In accordance with Article 19(3) of Regulation (EU) 2016/796, Annex 3 - 3.2 Route book). | ||
Latest revision as of 13:32, 27 August 2021
Contents
Description
The smart service provides information about
- facilities,
- restrictions and
- capabilities
of a location and the connecting segment. Operated by IMs or private, for passenger of freight.
Easy to fill with content and should be easily accessible either via APIs or web. Connection to other location data bases creating only one common interface for location handling be it IM / data interchange or physical details of a location. Geofencing of locations to support seamless track & trace solutions.
Use Case
- Source for new / existing railway customers to investigate if possible to transport to a certain location
- To create transparency of existing locations for RUs
Preconditions
Available data and sufficient data quality
Basic Services
SM08 Siding Everywhere
Dependencies
Existing location databases as
- CRD
- Rail facilities portal,
- RINF,
- DIUM
- Geo editor
A potential solution is described at GEO Model
Planned Steps
Evaluation
- Michel Thuering commented 20 Apr 2021 12:32
I consider SM_17 Facilties on location to be sensible with a view to uniform data collection. As SBB Cargo, the business value is not yet clear to me, as today this task is guaranteed by the infrastructure manager. As a company, I therefore do not yet have a return on investment - no simplification of processes, less administrative effort or a gain in time, do I?
- Frank Kschonsak on 25 June
Information provided should be applicable for the creation of the TSI OPE Route Book (see Guide for the application of TSI OPE – In accordance with Article 19(3) of Regulation (EU) 2016/796, Annex 3 - 3.2 Route book).
