Difference between revisions of "User:Milan Wölke"

From wiki.railML.org
Jump to: navigation, search
m (Erzeuge Benutzerseite mit der Biographie des neuen Benutzers.)
 
Line 1: Line 1:
July 2010 – present
 
Project Manager
 
PSI Transcom GmbH, Berlin
 
 Requirement Analysis, Design, Implementation, Testing and Commissioning of projects providing passenger information systems to public transportation companies in Germany, Switzerland and Malaysia (C#.NET, ASP.NET, VB.NET, Java)
 
 Specification of implementation tasks and management of the project team
 
 Communication with sub/main contractors and the customer project teams
 
  
May 2009 – July 2010
+
# '''railML® 3 use cases im timetable-Schema '''
Technical Project Manager
 
PSI Logistics GmbH, Berlin
 
 Requirement Analysis, Design, Implementation, Testing and Commissioning of customer projects providing control systems for transport optimization in Germany (Java)
 
 Specification of implementation tasks and management of the project team
 
 Communication with the customers project team
 
  
Jan 2007 – April 2009
 
Senior Software Developer
 
PSI Logistics GmbH, Berlin
 
 Design and implementation of features of a SOA-based transport management system (Java)
 
 Design and implementation of the underlying JEE-framework (Java)
 
 Setup and administration of the used development environment (nightly builds,
 
automated unit testing, code coverage) (Ant, Junit, Clover)
 
 Guidance/mentoring of co-workers at implementing features
 
 Enhancement of existing systems (C)
 
 Implementation of unit tests (Perl)
 
  
Apr 2004 – Jan 2007
 
Specialist for traffic and logistics systems
 
PSI Transportation GmbH, Berlin
 
 Enhancement of the system created as part of my Diplomarbeit in cooperation with several providers of passenger information systems (C/C++)
 
 Deployment of the system with several projects in Germany and the Netherlands
 
 Design and implementation of interface processes for external system integration (EAI) (C#.NET, Java, C++)
 
 Enhancement and service of existing legacy systems (C/C++)
 
  
Dec 2003 – Apr 2004
+
'''Use case / Anwendungsfall / Scénario d’utilisation: '''
Projects as freelancer for PSI Transportation GmbH, Berlin
+
 
 Enhancement and deployment of the system created as part of my Diplomarbeit (C/C++)
+
 
 Implementation of a system used to search any online freight market (Perl)
+
 
 +
Passenger information at stations/Fahrgastinformation am Bahnhof
 +
 
 +
 
 +
 
 +
'''Description / Beschreibung / Description '''
 +
 
 +
 
 +
 
 +
This use case describes the exchange of data between a system for providing passenger information at a railway station and a timetable planning system. The PIS allows for display of the current schedule including information about the current state of operation such as delays, cancelation or additional trains. In order to do so the schedule as published to the passenger for the current day of operation is necessary. The completeness of this timetable information limits the accuracy of the information available to the passenger by means of the PIS. The mandatory data can be limited to the services run on the current operation day, including all stops of a train with the according arrival and departure times. Additional information for can be provided to model blocks of services (can be used to increase accuracy of forecast information), planned interconnection with other services, planned construction sites with impact on the services, etc.
 +
 
 +
 
 +
 
 +
'''Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces '''
 +
 
 +
 
 +
 
 +
A PIS is a pure railML consumer.
 +
 
 +
 
 +
 
 +
Mandatory information imported from timetable system includes:
 +
 
 +
* <train>
 +
* <trainPart>
 +
* <category>
 +
* <ocp>
 +
 
 +
 
 +
 
 +
 
 +
 
 +
Optionally imported information includes:
 +
 
 +
* <track>
 +
* <formation>
 +
* <annotation>/<annotationRef>
 +
* <rostering>
 +
* <connection> (in order to provide and manage connection information for internal or external services)
 +
* <statistics>
 +
 
 +
 
 +
 
 +
If the topology is not imported from railML it is assumed that it is imported from a different source including an appropriate mapping to the ocp’s imported from railML.
 +
 
 +
 
 +
 
 +
'''Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML® '''
 +
 
 +
Mandatory: infrastructure
 +
 
 +
Optionally: rolling stock
 +
 
 +
 
 +
 
 +
'''Characterizing Data / Charakterisierung der Daten / Caractérisation des données '''
 +
 
 +
 
 +
 
 +
This section serves to specify the required data regarding certain aspects.
 +
 
 +
 
 +
 
 +
How often do the data change (update)?
 +
 
 +
yearly
 +
 
 +
regular changes
 +
 
 +
daily
 +
 
 +
 
 +
 
 +
How big are the data fragments to be exchanged (complexity)?
 +
 
 +
Huge - whole data set
 +
 
 +
 
 +
 
 +
Which views are represented by the data (focus)?
 +
 
 +
Mid term planning (eg. for yearly timetable disposition)  
 +
 
 +
Short term planning (eg. for trackworks)
 +
 
 +
Passenger information
 +
 
 +
 
 +
 
 +
Which specific timetable data do you expect to receive/send (elements)?
 +
 
 +
{| class="prettytable"
 +
|-
 +
|
 +
Element
 +
 
 +
|
 +
Mandatory
 +
 
 +
|
 +
Remarks
 +
 
 +
|-
 +
|
 +
Infrastructure/operationControlPoints/ocp
 +
 
 +
|
 +
X
 +
 
 +
|
 +
Used for referencing with the PIS topology
 +
 
 +
|-
 +
|
 +
Timetable/timetablePeriods/timetablePeriod
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/operatingPeriods/operatingPeriod
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/categories/category
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/annotations/annotation
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/formationTT
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/operatingPeriodRef
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/times
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/connections
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/connections/connection
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/connections/connection/annotationRef
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/statistics
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/sectionTT/runTimes
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription/stopTimes
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/ocpsTT/stopDescription/annotationRef
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trainParts/trainPart/annotationRef
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trains/train
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trains/train/trainPartSequence
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/trains/train/trainPartSequence/trainPartRef
 +
 
 +
|
 +
X
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/rosterings/rostering/blockParts/blockPart
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/rosterings/rostering/blocks/block
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|-
 +
|
 +
Timetable/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef
 +
 
 +
|
 +
 
 +
 
 +
|
 +
 
 +
 
 +
|}
 +
 
 +
 
 +
Mit Blick auf den Usecase Fahrgastinformation im Fahrzeug sollte <annotation> u. U. erweitert werden, um das Zielsystem der Sonderinformation zu bestimmen.
 +
Ausserdem sollte m. E. nach im rostering der Übergangstyp hinterlegt werden. Das hat Einfluss auf die Prognoseberechnung, sowie die berechnung von Via Zieltexten.

Revision as of 17:46, 16 March 2015

  1. railML® 3 use cases im timetable-Schema


Use case / Anwendungsfall / Scénario d’utilisation:


Passenger information at stations/Fahrgastinformation am Bahnhof


Description / Beschreibung / Description


This use case describes the exchange of data between a system for providing passenger information at a railway station and a timetable planning system. The PIS allows for display of the current schedule including information about the current state of operation such as delays, cancelation or additional trains. In order to do so the schedule as published to the passenger for the current day of operation is necessary. The completeness of this timetable information limits the accuracy of the information available to the passenger by means of the PIS. The mandatory data can be limited to the services run on the current operation day, including all stops of a train with the according arrival and departure times. Additional information for can be provided to model blocks of services (can be used to increase accuracy of forecast information), planned interconnection with other services, planned construction sites with impact on the services, etc.


Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces


A PIS is a pure railML consumer.


Mandatory information imported from timetable system includes:

  • <train>
  • <trainPart>
  • <category>
  • <ocp>



Optionally imported information includes:

  • <track>
  • <formation>
  • <annotation>/<annotationRef>
  • <rostering>
  • <connection> (in order to provide and manage connection information for internal or external services)
  • <statistics>


If the topology is not imported from railML it is assumed that it is imported from a different source including an appropriate mapping to the ocp’s imported from railML.


Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML®

Mandatory: infrastructure

Optionally: rolling stock


Characterizing Data / Charakterisierung der Daten / Caractérisation des données


This section serves to specify the required data regarding certain aspects.


How often do the data change (update)?

yearly

regular changes

daily


How big are the data fragments to be exchanged (complexity)?

Huge - whole data set


Which views are represented by the data (focus)?

Mid term planning (eg. for yearly timetable disposition)

Short term planning (eg. for trackworks)

Passenger information


Which specific timetable data do you expect to receive/send (elements)?

Element

Mandatory

Remarks

Infrastructure/operationControlPoints/ocp

X

Used for referencing with the PIS topology

Timetable/timetablePeriods/timetablePeriod

X


Timetable/operatingPeriods/operatingPeriod

X


Timetable/categories/category



Timetable/annotations/annotation



Timetable/trainParts/trainPart/formationTT



Timetable/trainParts/trainPart/operatingPeriodRef

X


Timetable/trainParts/trainPart/ocpsTT

X


Timetable/trainParts/trainPart/ocpsTT/times

X


Timetable/trainParts/trainPart/ocpsTT/connections



Timetable/trainParts/trainPart/ocpsTT/connections/connection



Timetable/trainParts/trainPart/ocpsTT/connections/connection/annotationRef



Timetable/trainParts/trainPart/ocpsTT/statistics



Timetable/trainParts/trainPart/ocpsTT/sectionTT/runTimes



Timetable/trainParts/trainPart/ocpsTT/stopDescription



Timetable/trainParts/trainPart/ocpsTT/stopDescription/stopTimes



Timetable/trainParts/trainPart/ocpsTT/stopDescription/annotationRef



Timetable/trainParts/trainPart/annotationRef



Timetable/trains/train

X


Timetable/trains/train/trainPartSequence

X


Timetable/trains/train/trainPartSequence/trainPartRef

X


Timetable/rosterings/rostering/blockParts/blockPart



Timetable/rosterings/rostering/blocks/block



Timetable/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef




Mit Blick auf den Usecase Fahrgastinformation im Fahrzeug sollte <annotation> u. U. erweitert werden, um das Zielsystem der Sonderinformation zu bestimmen. Ausserdem sollte m. E. nach im rostering der Übergangstyp hinterlegt werden. Das hat Einfluss auf die Prognoseberechnung, sowie die berechnung von Via Zieltexten.