Difference between revisions of "Facilities on location"
(→Evaluation) |
|||
| Line 21: | Line 21: | ||
== 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? | ||
Revision as of 13:28, 4 May 2021
Contents
Description
The smart service provides information about facilities, restrictions and capabilities of a location. 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
Dependencies
Existing location databases as CRD, Rail facilities portal, RINF, DIUM, Geo editor
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?
