ProSig InfoMail 09/2012

Transcription

1 New features for enhanced design capabilities within the context of Deutschen Bahn s PlanPro standardization project Visit us at the InnoTrans Fair in Berlin, September Welcome to our hall 25 / stand 310 1

2 Ladies and Gentlemen, Dear ProSig Users, We ve kept busy these last years by gradually expanding our ProSig application system to meet the latest demands posed by all the global networks out there. As a result, we ve made great strides in further improving major applications like ProjectManager, ObjectEditor, TableExporter and SmartDriver. Owing to further across-the-board improvements in our communication process, it is our privilege today to share with you a development, which is bound to significantly impact both our work in the years to come: ProSig Extended Planning Unit (EPU) for PlanPro Data Interface of Deutsche Bahn Germany s national railway company Deutsche Bahn (DB) started the project PlanPro to create the basis for electronic data interchange with all systems and corporations involved in its planning process for electronic interlocking technology (see also PlanPro item in Signal+Draht Issue 9/2012 ). Recently, the project resulted in the first viable basis in that direction. It serves to define and document all relevant (LST) objects like switches, signals, axle counters, as well as complex structural assemblies like track topology, track clearance sectors, pre-set railway routes and rail lateral protection, in full detail right down to all their elemental characteristics. ProSig team members were there to accompany the project right from the beginning by assisting Deutsche Bahn in creating said basis for the data interface. ProSig is a fully compliant data supplier that comes with features making the documentation of complex data and structural plans easy for you to create and easy for others to understand. In the following months PlanPro data interface will be evaluated in a series of pilot projects, also to prepare ProSig EPU for broad use within the DB network. In addition to the proven functions in ProSig, EPU generally serves the following tasks: Database-supported project tasks Import of track layout and automatic generation of track topology Automatic calculation of signal locations and overlap lengths Automatic generation of track clearance sectors Easy inserting, positioning and editing of all LST objects Interactive creation of platforms, railroad crossings, key locks and block posts System-supported definitions of pre-set railway routes and rail lateral protection Convenient ETCS Level 1 and Level 2 planning LST object cabling for all standard interlocking systems Data export to signal tables (PT1 and ETCS) and to PlanPro data interface 2

3 Visit this year s InnoTrans expo, where we present our developments for the very first time: Add to that a special presentation on the topic "ProSig EPU - Extended Planning Unit" at our booth (no. 310 in Hall 25) at 10:00 am on Thursday, Sept. 20, 2012, to which we invite you cordially. Enclosed you ll find documentation highlighting the present state of our developments we included to give you an initial idea of the PlanPro and EPU projects. Your ProSig Team 3

4 EPU Essentials Here we introduce you to the essential functions of EPU as applied in the course of regular project work. On many levels, EPU presents an extension of ProSig rather than a fully separate module. It features independent functions with new dialogs as well as extensions of pre-integrated functions. In this context, the following descriptions vary accordingly between actual EPU functions and wellknown ProSig functions. ProSig Project Management Fig. #1: The Project Manager serves to keep all project plans in organizational and data-specific order. The Project Manager serves to create a database project in usual fashion (see Fig. #1). Changes to one project plan automatically lead to updates of any other plans pertaining to the project. This ensures data consistency within the individual ProSig database projects, saving users the burden of manually updating any outdated plans. Database projects provide the systematic basis for the EPU functions, as all data and data models required for a database project are stored in the EPU project database for future reference. 4

5 Track Layout and Track Topology Starting any ProSig project requires track layouts. Users can apply the GND Track Layout function to automatically import track layouts to their ProSig drawings from the DB-GIS (Geographical Information System) of Deutsche Bahn. They can also create track layouts in their plans by applying familiar functions like Track Construction, Switches and Crossings. Users furthermore rely on the Track Topology function for verification and automatic import of their complete track layouts to a node/edge model of possible routes ; i.e., track topology (see Fig. #2). Track topology is the primary ingredient for any planning and planning support in ProSig. Fig. #2: Track layout transforming from a ProSig drawing into track topology in ProSig data model Control charts for track topology are created in the form of polylines on a separate layer in the layout plan, using a special color for highlighting (see Fig. #3). Node points appear at switches and crossings in track topology, like the double -slip switch and four rail junctions shown in Fig. #4. Fig. #3: Control chart for track topology in layout plan Fig. #4: Double-slip switch with four rail junctions 5

6 In addition to track layouts, users can also import the following information from DB-GIS: GND Kilometrage, GND Gradient and GND Superelevation. Aforesaid information is also fed into the ProSig data model and, where appropriate, updated via the corresponding functions: Kilometrage, Gradient (see Fig. #5) and Superelevation. Users can further import data from the Deutsche Bahn list of local speed limits (VzG) for the automatic creation of maximum-speed ranges and for ETCS planning support. The Speed function serves to verify and, if needed, adjust data users create from the VzG. Fig. #5: Editor for controlling, creating and adjusting gradient ranges Signal Planning The actual process of integrating signals in drawings carries over unchanged with the Signal Generator. However, it now adds automatic activation of a new feature called Gradient-based Location Identification (GLI), which applies imported gradient ranges (see above) and signal parameters (e.g., maximum speed and overlap length) to precisely calculate the proper location for signals or actual overlap lengths, displaying the results to users as shown in Fig. #6. Fig. #6: Display of automatically calculated actual overlap lengths 50m, 100m and 200m 6

7 The scope of PlanPro and EPU opens a host of additional characteristics and conditions to detailed editing. Helping to visualize their complex layouts are the detailed display options of the separate SignalEditor (see Fig. #7). Users can arrange a variety of views (e.g., Standard, PlanPro, SignalTable 1) to display only essential characteristics as needed. Notably SignalTable 1 viewing mode, which displays data identically to (PT1) SignalTable 1, facilitating the process of table exports, as shown in the foreground of Fig. #7. Fig. #7: SignalEditor with different viewing options (e.g., SignalTable 1) for editing signals Track Clearance Sectors Among the subdivisions (under the track topology) of any rail network are track clearance sectors. They are defined as usual by inserting and positioning track clearance sensor units in drawings using the Axle Counter, Insulated joints and Relevant Range functions, among others. Based on the positioned and labeled track clearance sensor units (see Fig. #8), the Track Clearance Sectors function automatically generates corresponding sectors with an extra layer for control displays in the drawing (see Fig. #9). 7

8 Fig. #9: Control display for track clearance sectors in layout plan. Fig. #8: Defining track clearance sectors based on axle counters, for example Planning Additional LST Elements The process of integrating symbols for signal-relevant elements in plans carries over unchanged using the corresponding insert functions. Within the framework of PlanPro and EPU, special insert and editor functions support layouts of a more complex nature. Track magnet/pzb control Track clearance sensor units such as axle counters and track circuits; see above Balises for ETCS, among others Key lock logically connected to locked element via EPU Key Locks function Areas for close operation logically connecting elements included within them via EPU Close Operations function Level crossings featuring LST-relevant components and conditions Platforms for interactive construction (see Fig. #10) Fig. #10: Interactive construction design with platform shown in white, block post shown in green and block section shown in magenta 8

9 Block systems featuring block sections for interactive definition as area objects in layout plans (see Fig. #10 on right) and block posts with characteristics assigned via special editor (see Fig. #11) Fig. #11: Block post editor/generator Parameter drawings, created and assigned to LST elements (see Fig. #12) Fig. #12: The Parameter Drawing Editor serves to define all parameter drawings required for a project Railway Routes & Rail Lateral Protection The central requirement to ProSig within the scope of EPU involves the planning of railway routes and rail lateral protection. This encompasses a multitude of technical aspects associated with interlocking systems. Confronting these complex challenges involved implementing a Railway Route/Rail Lateral Protection Editor in ProSig (see Fig. #13) to support the following range of functions: 9

10 Defining routes o Choosing route start (start signal, in particular) and end points in ProSig drawings o Displaying all possible combinations of start and end points o Validating said combinations based on track topology (automatic route search along track topology) with result display: valid, invalid, present o Integration of selected routes in ProSig project o Zoom and highlight options for routes in drawings o Editing of route characteristics Defining overlap lengths accordingly Combing routes with overlap lengths and thereby defining railway routes Defining rail lateral protection o Choosing object (switch, in particular) requiring rail lateral protection o Requesting rail lateral protection; i.e., generating rail lateral protection object o Automatic search for rail lateral protection object (automatic search for rail lateral protection along track topology) o Zoom and highlight options for rail lateral protection in drawings, as shown in the foreground of Fig. #13 o Editing of rail lateral protection characteristics Fig. #13: The Railway Route/Rail Lateral Protection Editor serves to support complex planning tasks Equipment Planning for ETCS Levels 1 and 2 The European standardization of equipment and control systems in the field of control command and signaling technology requires special ETCS Level 1 and ETCS Level 2 support modules in ProSig. At this stage, ETCS technology is not included in PlanPro data modeling, although its incorporation is planned in the next expansion phase of the data interface. 10

11 The ETCS Level 1 module currently supports the control command application ZBS of Berlin s S-Bahn railway with the following functions: o Interactive insert of equipment (especially balises) o Distance measurement within a meter between data points (balises) via interactive track topology positioning o Interactive assignment of data points to LEU signals (signals, whose present readouts can be read by data points) o Interactive definition of data point links o Creating and editing of data point links telegrams o Creating and editing of reduced-speed areas o Automatic calculation of areas of protection based on gradient range (see above) o Data export to relevant Excel tables The ETCS Level 2 module differs from its Level 1 sibling in that it does not require trackside signals. Irrespective thereof, Deutsche Bahn relies on an integrative signal layout plan (SLP) in its ETCS Level 2 planning, as well as on all other PT1 provisions. As a result, the Level 2 module supports the following functions: o Interactive insert and positioning of equipment (similar to Level 1) o Import and automatic assignment of data point addresses o Import and editing of relevant gradient and maximum-speed ranges (see Fig. #14 on right) o Editing of further ETCS characteristics o Automatic extrapolation of SLP to ETCS layout plan o Automatic position alignment of elements in ETCS layout plan to those in SLP based on track topology o Automatic generation of ETCS rail edge descriptions (see Fig. #14 on left) o Automatic graphic creation of gradient and maximum-speed ranges in ETCS layout plan (see Fig. #14 at bottom) o Automatic creation, administration and export of ETCS title blocks o Data export to relevant Excel tables 11

12 Fig. #14: Results of ETCS L2 planning: ETCS layout plan, maximum-speed and gradient ranges Bild Cabling for LST Objects The cabling of LST objects (e.g., signals) carries over unchanged using the Cable Layout Plan function. This chiefly involves objects that are located along cable routes and connected to the interlocking system through cable cabinets. In addition to determining the quantity of cable types being used, there are functions for objects to be - logically assigned (e.g., signal ESTW) - provided with data links (control) - connected to run off electricity (power supply) Within the scope of PlanPro, users can display and edit all cabling data using the Outside Element Controls function (see Fig. #15). 12

13 Fig. #15: Dialog concept for the supply of elements with energy and data Export to Signal Tables Together with the signal plans, the system of signal tables forms the central planning outcome of PT1 created with the aid of ProSig. Once all the PlanPro-relevant objects and information have been configured within the scope of a ProSig database project, their data is ready to automatically load in the PT1 tables as well (see Fig. #16). Fig. #16: Automatic export of project data to export preview (above) and to train route table 13

14 Export to PlanPro Data Interface The activities described above conclude by exporting the full range of LST data to the PlanPro data interface as well. Fig. #17 shows the systems currently involved in the process: ProSig LST planning software by IVV (DB standard software since 1998) BEST ESTW operation simulation software by Funkwerk IT (also used as training system for train dispatchers at DB) Project engineering systems of interlocking system manufacturers (incl. Siemens, Thales, Bombardier Transportation, Scheidt & Bachmann and Funkwerk) LST database of Deutsche Bahn, currently being implemented The interface file comes in standard XML format (see Fig. #18) with a series of schemes (XSD) and additional specific regulations (incl. Schematron) to secure its form and contents. Fig. 17: Systems currently involved in data exchange via PlanPro data interface 14

15 Fig. #18: View of a tiny fraction of the PlanPro data being exported by ProSig Contact and Support If you have any questions or feedback, feel free to contact us: Phone.: Fax: prosig.support@ivv-gmbh.de For further information please visit our homepage 15