New pages
Jump to navigation
Jump to search
- 07:31, 26 October 2022 Damage Management Service (hist | edit) [753 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == The handling of a damaged wagon or loco is not harmonized. The continuation in the train run and the repair steps including the new status are not digitally supported and sometimes carried out in a highly individual way. == Target == All RUs use the standardized digital supported process to inform about the impact of the damage and the responsible for the resources updates the status of the repair p...")
- 07:31, 26 October 2022 Data Management (hist | edit) [12,440 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual situation == Today the data management is heterogeneous and platform/community dependent. Therefor the data quality is impacted (media breaks, other business/technical models). Some of the providing technical services has a long lifetime and are bound to be renovated to meet today's service standards and enable a further evolution. == Target == # Legacy Service renovation To overcome the restrictions and threa...")
- 07:30, 26 October 2022 Platform Services (hist | edit) [3,622 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual situation == The today's platform landscape is scattered. A lot of the communication is based on bilateral agreements. The communication patterns are diverse and heterogenous. SmallRU's can't participate because of the complexity and the technical prerequisites. The resulting coverage is low. border|center|800px == Target == To overcome the difficulties in digital communication the...")
- 07:29, 26 October 2022 Train ETA Service (hist | edit) [5,754 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == The current ETA quality is not sufficient (e.g. different ETA solutions / initiative depending on products and created from different sources) and does not cover the entire transport route. == Target == # ETA is provided for all rail freight products on train <s>both on train and shipment level</s> (e.g. block trains, SWL, intermodal etc.) easily accessible via the digital platform, also serving as...")
- 07:28, 26 October 2022 Train Service Harmonization (hist | edit) [10,575 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == No/little digital support for all RUs in the train service planning. Information exchange is mostly handed bilaterally and manually. == Target == # All RUs use a cooperation service to setup, manage, update and reference the train service planning. This can happen by system interface, or # web portal to exchange Train Service Information. This process starts with the initial (yearly) train service p...")
- 07:28, 26 October 2022 Telematic Data Sharing (hist | edit) [5,233 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == Wagon Keepers are currently equipping their fleets with telematics and sensors to ease internal use cases (i.e. mileage, customer service, internal processes). No common solution exist on how to exchange telematic data. == Target == # Creating a platform using the existing interfaces of the RFF DP ecosystem to transmit telematic data between partners to create transparency and a fully digitalized jo...")
- 07:27, 26 October 2022 Digital Train Composition (hist | edit) [6,205 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == Different train composition message is used in RU/RU versus RU/IM communication. Variants are defined per IM network in messages due to national speciticas. This results in * specific adaptors for each network the large RU is operating in. * Time consuming and error prone solution for small RUs as they queue in manually the necessary data. == Target == # The basic idea is to use a standardized train...")
- 07:27, 26 October 2022 Digital Consignment Note (hist | edit) [4,045 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == Creation and handover of consignment notes (CNs) often a manual and cumbersome process. Documents’ check on paper between small and large RUs and ports, terminals. == Target == # All RUs use 100% standardized digital consignment notes (CNs) that are available via API to partner RUs. # Creation and handover of CNs can be done by mobile user-friendly interfaces - especially for small RUs. # DP Rail p...")
- 07:26, 26 October 2022 Digital Train Handover (hist | edit) [4,196 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == Non-standardized Business to Authorities communication and fragmented bilateral RU-RU, RU-IM, IM-IM communication leading to long, inefficient handover processes at border crossings == Target == # Automated workflow providing all relevant information digitally to the required stakeholders including authorities (Customs / Dangerous Goods / Waste), integrating standardized handover processes and servi...")
- 07:25, 26 October 2022 Digital Train Operations (hist | edit) [10,163 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Description = == Actual Situation == Gaps and ambiguities for operational trains, delays in information forwarding inhibits a safe and looking ahead operation. No/little integration of small RUs in the train processing. Information on first and last mile mostly handed over manually. == Target == # Integration & Quality: Operational train events are aggregated, completed and distributed among the involved parties. The log record is wri...")
- 07:24, 26 October 2022 Phase3 Iteration1 (hist | edit) [4,614 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 22.1 = The iteration lasts from 25.January to 15.February. = Topics = * MS POC status * MARS * CEF Call * Project Setup * ARCH Blueprint * RFF pilot: UC TDS and GEOmodel == CEF Call Status == # CEF Call application status RFF DP becomes DP-RAIL # Project setup ## Organisation ### Product teams -> Workpackages ### Platform team ### Infrastructure & Data Mgmt ### Digital delivery...")
- 07:23, 26 October 2022 Phase3 Iteration2 (hist | edit) [2,859 bytes] Sfr (talk | contribs) (Created page with " Category:RFF no public data = Iteration 22.2 = The iteration lasts from 15.February to 8.March. = Topics = * DP Rail organisation * DAC Migration * MARS * ProcessMap * WP Dossier == DP Rail organisation == File:DP-RAIL-Contribution RFF IT Fullteam Folien 0-19.pdf == MARS status == File:MARS Fullteam 20220308.pdf == DAC Migration == File:20220218 DAC migration 1st workshop IT v3.pdf == ProcessMap == The base for our project setup is the overall...")
- 07:22, 26 October 2022 Phase3 Iteration3 (hist | edit) [4,418 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 22.3 = The iteration lasts from 8.March to 29.March. = Topics = * DP Rail topics * DAC Migration * MARS * ProcessMap * WP Dossier == DP Rail topics == In DP Rail the following topics are treated. # Train Service Harmonization # Digital Consignment Note # Digital Train Composition # Telematic Data Sharing # Digital Train Operations # Train ETA Service # D...")
- 07:21, 26 October 2022 Phase3 Iteration4 (hist | edit) [4,096 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 22.4 = The iteration lasts from 29.March to 10.May. = Topics = * DP Rail topics * WP Dossier * ARCH blueprint = DP Rail topics = In DP Rail the following topics are treated. # Train Service Harmonization # Digital Consignment Note # Digital Train Composition # Telematic Data Sharing # Digital Train Operations # Train ETA Service # [[Digital Train Handover]...")
- 07:21, 26 October 2022 Phase3 Iteration5 (hist | edit) [679 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 22.5 = The iteration lasts from 10.May to 31.May. = Topics = * DP Rail topics * WP Organisation * ARCH toolchain * MARS release = DP Rail topics = In DP Rail the following topics are treated. # Train Service Harmonization # Digital Consignment Note # Digital Train Composition # Telematic Data Sharing # Digital Train Operations # Train ETA Service # Digita...")
- 07:20, 26 October 2022 Phase3 Iteration6 (hist | edit) [2,577 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 31.6 = The iteration lasts from 31.May to 21.June. = Topics = * DP Rail topics * WP1 - train harmonization * DP-RAIL work package ws series * MARS status and demo * Planning 2022 * WP leader introduction == WP1 Digital Train Operation == We had in the last full team meeting a session with the architects before starting the WS sessions with the business specialists. * presentation...")
- 07:19, 26 October 2022 Phase3 Iteration7 (hist | edit) [2,268 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> = Iteration 22.7 = The iteration lasts from 21.June to 12.July. = Topics = * WP workshops status * Planning 2022 = DP Rail topics = In DP Rail the following topics are treated: # Digital Train Operations Initial Workshop on 8.June √ # Digital Train Handover Initial Workshop on 9.June √ # Digital Consignment Note Initial Workshop on 5.July √ # Digital Train Composition Initial Workshop on 30.June √ # [...")
- 07:18, 26 October 2022 Phase3 Iteration8 (hist | edit) [883 bytes] Sfr (talk | contribs) (Created page with "<accesscontrol>Department</accesscontrol> Category:RFF no public data = Iteration 22.8 = The iteration lasts from 12.July to 23.August. = Topics = * Planning DP-RAIL ** 2022 ** 2023, next phase * MARS presentation ** status ** planning = Planning = The planning of the next steps is in progress. * What topics to tackle? ** How to organize, ** what to combine, ** what to advance, what to start slower? * How to organize? ** Community ** Governance ** Prepare for t...")
- 07:17, 26 October 2022 Phase3 Iteration9 (hist | edit) [1,011 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Iteration 22.9 = The iteration lasts from 23.August to 27.September. = Topics = * Status DP Rail * Outlook Q4 2022 * Presentation MARS MVP = Status DP Rail = border|center|800px see details on consortium slides == Presentation Innotrans 21.Sept == Presentation on InnoTrans 21.September, slides are on RFF Sharepoint: https://xrail.sharepoint.com/:p:/s/RFFDigitalplatforms/EaSysLuf3L1PuHF...")
- 07:09, 26 October 2022 Phase3 Iteration10 (hist | edit) [2,829 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data = Iteration 22.10 = The iteration lasts from 27.September to 15.November. = Topics = * Summary ARCH 2022 * CEF Call 2023 preparation * RNE alignment * Planning 2023 = Summary ARCH 2022 = * Summary ARCH 2022 documentation ** Finalize documentation ** Upload to DP Rail wiki * CEF Call 2023 participation = CEF Call 2023 = The call was published in September. [https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportu...")
- 10:01, 29 August 2022 Facade A (hist | edit) [406 bytes] Sfr (talk | contribs) (Created page with "Category:RFF no public data * Train Service Planning: PCS by RNE * Consignment Note: Reception MARS by RFF * Train Preparation: Organisation MARS by RFF * Train Operation...")