DIVA 4 and EFA 10 - Paradigm Change at the VVS

More documents

Recommendations

Info

6 mdv news II/2011 Figure 4: Display of a current route network map in DIVA Web Figure 7: Finished mini timetable PDF file
Figure 5: Selection options for route option map Figure 8: Run script overview Figure 9: DMS overview shows the conversion of day-specific timetables EFA 10 mdv news II/2011 - 7 In using DIVA4, the VVS also committed to switching from EFA9 to EFA10. Due to the more efficient data supply, more efficient integration of real-time data through incremental conversion in DIVA4 and more efficient processing of real-time data by EFA10 the switch to EFA10 was desired and implemented. Data supply from DIVA4 to EFA10 has been made more convenient. In the past, data supply occurred in separate, individual processes. DIVA4 uses scripts in DIVAWeb to make the supply of data to EFA10 simpler (see figure 8). The conversion is essentially performed using 3 scripts: - Copy network version - Conversion - Export network version By copying a network version, a database that is intended for release to EFA is transferred to another, separate network version. On the basis of this procedure, data is prepared for conversion for use in EFA10. Network versions can also be exported so that the data is available for use in external systems. All three procedures can be displayed and analyzed in the DMS (Data Management System) (see figure 9). Additional process steps have been integrated into the script for EFA Conversion, two of which are data preparation for the EFA Location Server and generation of elevation data. The script can be upgraded and customized. When the process is run, all data required for data supply to EFA are generated. A very important functionality at the VVS is the use of real-time. One of the big advantages of DIVA4 and EFA10 is the ability to quickly integrate day-specific timetable data from AVM systems to EFA. Complete conversion is no longer required for this process. Instead, the day-specific data are integrated into an intermediate format from which the EFA10 data are subsequently compiled. At the VVS there are now 3 connected AVM systems: - DB (Deutsche Bahn or German Rail) - AVM-Light (3 transport authorities Dannenmann, Kappus and OVR-WRG) - SSB (Stuttgarter Straßenbahn or Tram) The DB data of the VVS already contain the trip IDs to determine delay messages. Dayspecific data with trip IDs are received by the SSB and AVM Light and subsequently integrated to the EFA10 system. The DMS is used to view and analyze these processes (see figure 10). The integration of day-specific data and the processing of EFA10 data only take a few
Page 1 and 2: DIVA 4 and EFA 10 - Paradigm Change
Page 3 and 4: DIVA 4 and EFA 10 - Paradigm Change
Page 5: Maps One of the development goals o
Page 9 and 10: In order to continually improve per
Page 11 and 12: ductive trip to the start of anothe
Page 13 and 14: Stuttgart Tram Strike Strike - no b
Page 15 and 16: mdv news II/2011 - 15 Adorf (Erzgeb

DIVA 4 and EFA 10 - Paradigm Change at the VVS

Create successful ePaper yourself

Delete template?

Save as template?