Description of content

This Data Store shall be used within the Manage Public Transport Operations Area.  It shall contain the historical average value indicators for Public Transport vehicles in the fleet.

The data in the Store shall be structured in the following way for the static data about each PT Vehicle:
- type (characters)
- vehicle ID (number)
- passenger capacity (number)

The data in the Store shall be structured in the following way for the real-time data about each PT Vehicle:
- date (date string)
- time (numbers defining hours, minutes and seconds)
- location (characters and/or numbers, e.g. GPS/Galileo data)
- service ID (number)
- real-time status indicators (numbers and/or characters)
- alarm present (number or character indicating YES or NO)
- number of passengers currently on-board (number)
- passenger alarm raised (number or character indicating YES or NO)
- passenger alarm acknowledged (number or character indicating YES or NO)
- message sent to driver (number or character indicating YES or NO)
- message text sent to driver (text string)
- message received from driver (number or character indicating YES or NO)
- message text received from driver (text string)
- internal video from PT Vehicle (video file)
- scheduling for PT services

It shall be possible for the information to be stored in such a way that it can be retrieved by route, by service, by type of vehicle etc. as needed.  For each of the above categories as minimum the stored data shall be archived classified by type of day with the needed level of detail (working days, holidays, school days, off school days, rainy days, sunny days, traffic restriction days, etc).  The level of detail shall be coherent with the detailed specification of the system: e.g. average travel time can be as detailed as calculated for every few meters of road along the route or distinguishing between characteristic stretches of road, or just between two terminals.

The entries in the Data Store shall also include the exact description of the time, place and whatever else is needed to identify the scenario to which the set of data is referred to.

Stored data shall be constantly updated with new measurements available and previously smoothed and validated.  It shall be possible for the time slots used to store the data to vary according to the needs.

The information that is archived shall also be filtered taking into account presence of exceptional events during the day and the actual operating service scheme.

Diagrams

The Diagram(s) below is (are) the Diagram(s) where you can find the Datastore

DFD 4 Manage Public Transport Operations

DFD 4.1 Monitor PT fleet

DFD 4.2 Plan PT Service

DFD 4.4 Control PT Fleet

Input dataflows

mpto_consolidated_vehicle_data

mpto_control_actions

mpto_PT_vehicle_static_data_for_historic_use

Output dataflows

mpto_historical_vehicle_data

mpto_recorded_data

mpto_typical_travel_times