Difference between revisions of "Capacity Optimization"

From RFF Wiki
Jump to: navigation, search
Line 1: Line 1:
  
 
== Description ==
 
== Description ==
 +
The RU needs to plan initially and replan later the train service together with the involved partners.
 +
Today it is a long, labour intensive and highly specific manual planning process. The digital data exchange is crucial for the efficiency and quality of the partner communication in future.
 +
The communication encompasses
 +
* Train service planning
 +
* Path requests,
 +
* Local service provider e.g. Last/First mile, yield management, shunting capacity​
  
Train-slot management, capacity requests, hand-over + service provider, yield management, shunting capacity​
+
== Use Case ==
 +
=== RU plans Train Service ===
 +
The RU needs to plan the Train Service together with his partners. This involves
 +
* the RU partners,  
 +
* the Local Service partners,
 +
* the yield managers.
 +
To be able to carry out this planning efficiently the RU needs to communicate electronically with his partners.
  
an overarching capability for an improved production workflows combining several use cases of data exchange on Train-slot management, capacity requests / bookings , hand-over, first / last mile service provider, yield management, shunting capacity​, etc. to ensure smooth processes and remove redundancies (waiting, handover-checks, border-crossing, send back) supported by IT workflows for data exchange, platform services or marketplace.
+
=== RU replans Train Service ===
 +
The RU needs to replan the Train Service with his partners. This involves
 +
* the RU partners,  
 +
* the Local Service partners,
 +
* the yield managers.  
 +
To be able to manage this change efficiently the RU needs to communicate electronically with his partners.
  
== Use Case ==
+
=== RU asks for a new Path ===
 +
The RU needs to hava a new Path. In the process of replanning the RU detects that the capacity of the booked Paths no longer fits to the transport needs and he needs another Path.
 +
The RU must manage this additional capacity efficiently in terms of resources and time. A system interface communication and a short term answer (e.g. in 10 min) from the IM planning system is expected.
 +
 
 +
=== RU changes booked Path ===
 +
The RU needs to change a booked Path. In the process of replanning the RU detects that the booked path no longer fits to the transport needs. This can be
 +
* in its timetable,
 +
* in its route and
 +
* in its technical parameter.
 +
The RU must manage this change efficiently in terms of resources and time. A system interface communication and a short term answer (e.g. in 10 min) from the IM planning system is expected.
  
 
== Preconditions ==
 
== Preconditions ==
Line 14: Line 40:
 
== Dependencies ==
 
== Dependencies ==
 
This service provides the basic (inhouse) information to ask or offer free capacity in the SM13 [[Share Free Capacity]] service.
 
This service provides the basic (inhouse) information to ask or offer free capacity in the SM13 [[Share Free Capacity]] service.
 +
This service depends on
 +
* SM_05 [Train Harmonzation Service]
 +
* SM_06 [End-To-End Path Planning/Ordering]
 +
* SM_07 End-To-End Transport Planning
 +
services as basis.
  
 
== Planned Steps ==
 
== Planned Steps ==
  
 
== Evaluation ==
 
== Evaluation ==

Revision as of 09:12, 16 June 2021

Description

The RU needs to plan initially and replan later the train service together with the involved partners. Today it is a long, labour intensive and highly specific manual planning process. The digital data exchange is crucial for the efficiency and quality of the partner communication in future. The communication encompasses

  • Train service planning
  • Path requests,
  • Local service provider e.g. Last/First mile, yield management, shunting capacity​

Use Case

RU plans Train Service

The RU needs to plan the Train Service together with his partners. This involves

  • the RU partners,
  • the Local Service partners,
  • the yield managers.

To be able to carry out this planning efficiently the RU needs to communicate electronically with his partners.

RU replans Train Service

The RU needs to replan the Train Service with his partners. This involves

  • the RU partners,
  • the Local Service partners,
  • the yield managers.

To be able to manage this change efficiently the RU needs to communicate electronically with his partners.

RU asks for a new Path

The RU needs to hava a new Path. In the process of replanning the RU detects that the capacity of the booked Paths no longer fits to the transport needs and he needs another Path. The RU must manage this additional capacity efficiently in terms of resources and time. A system interface communication and a short term answer (e.g. in 10 min) from the IM planning system is expected.

RU changes booked Path

The RU needs to change a booked Path. In the process of replanning the RU detects that the booked path no longer fits to the transport needs. This can be

  • in its timetable,
  • in its route and
  • in its technical parameter.

The RU must manage this change efficiently in terms of resources and time. A system interface communication and a short term answer (e.g. in 10 min) from the IM planning system is expected.

Preconditions

Basic Services

Dependencies

This service provides the basic (inhouse) information to ask or offer free capacity in the SM13 Share Free Capacity service. This service depends on

  • SM_05 [Train Harmonzation Service]
  • SM_06 [End-To-End Path Planning/Ordering]
  • SM_07 End-To-End Transport Planning

services as basis.

Planned Steps

Evaluation