Glossary

Data evaluation and analytics SW from HaslerRail related to railway operations data recording based on an on-board recording unit.

The deployment of the EVA+ application on a web server

An event recorder is an event-driven recording unit. The TELOC® is an event Recorder.

Juridical Recording Unit (according to ERTMS/ETCS SubSet-027)

DRU: Data Recording Unit (according to specific requirements

Hasler Rail event Recorder. Can be configured as a JRU.

A railway vehicle such as a train, locomotive, EMU, etc.

Equipment installed on a vehicle with the purpose of collecting/recording data. Depending on the configuration of the vehicle there could be more than one recorder (e.g. DRU and a JRU).

A fleet is a set of vehicles (set number is 1 … n).

A Fleet can be divided into several sub-fleets according to certain characteristics (vehicle class, vehicle typ, etc.). A vehicle can be an element of several sub-fleets.

Train Operating Company, train operator and/or train owner (e.g. SBB, SNCF, SNCB).

A rolling stock operating company (ROSCO) owns and maintains railway engines and carriages which are leased to train operating companies (TOC) who actually operate the trains (e.g. Angel Trains, Railpool, MRCE).

The owner of a vehicle.

Body responsible for system integration. Often an integrator is the train manufacturer such as Bombardier, Alstom or Siemens.

Moveable railway asset equals to vehicle. 

Owning and/or operating a railway infrastructure.

A user interface (or view) in EVA+ is a graphical interface provided to the user, allowing him/her to operate the application.

A business scenario refers to a specific process relevant for the core business for user of EVA+. E.g. brakes check at the start of a mission.

A unique ID needed to identify the data source, composed of vehicle id, recorder serial number and recorder configuration. If the origin parameter changes a new data stream is created.

Data recorded in a recorder. Teloc Raw data can be in the following format: ETCS, GUM, Legacy, T1000 or T2200.

Interpreting the data (that EVA+ receives from a Recorder).

An event is one occurrence of an event type and contains measures (previously known as kpi’s) and dimensions (previously known as parameters).

It is the core element to make analysis across multiple vehicles, fleets and sub-fleets. Its purpose is to aggregate data and reduce its amount in order to perform faster analysis.

(Example: Emergency brake of vehicle 12 at 21:23 on the 12.11.2015)

=> What is the aim of an event: Indicate a particularly interesting combination of recorded signals (defined together with a customer) in time related to a vehicle/recorder and additional signals (like for example location).

events are calculated based on the data extracted (and fragmented) from a recorder.

An event Type is a

1. Combined signal condition (Boolean and/or arithmetic). Example: digin1 = true.
2. A time event type such as day, month or year which is triggered by the time (local time of the event recorder)

An event type is defined in an event generator for each TELOC® configuration.

An event type can have a duration restriction (the condition has to be true for a minimal or maximal duration).

Example: (Emergency brake of vehicle 12 with config 5 and issue 23)

An event generator contains the event type definitions for a specific TELOC® configuration and signature.

As additional information to an event, it is possible to configure the recording of other signals (“additional signals”) when the event condition is met.

It is possible to map a signal (analog, digital) or record (ETCS Message, OPM Record) or a mathematical/logic function of one (or more) signal(s) to an abstract name that can be used as a signal reference in an event definition. With this process a new signal is created and therefore defined as an “artificial signal” (previously known as “special signal”). 

Event without duration e.g. an ETCS message, it only has a timestamp but no start and stop time.

Dimensions and measures are the physical aspects of data aggregation.

Dimensions allow data analysis from various perspectives. For example, time dimension could show you the breakdown of sales by year, quarter, month, day and hour. Product dimension could help you see which products bring in the most revenue. Supplier dimension could help you choose those business partners who always deliver their goods on time. Customer dimension could help you pick the strategic set of consumers to whom you'd like to extend your very special offers.

A measure is a numerical property of a fact describing a quantitative attribute on which calculations (e.g. aggregations) can be made. Examples of measures include dollars of sales, number of credit hours, store profit percentage, dollars of operating expenses, number of past-due accounts and so forth.

Railway-specific example

Dimensions: time dimension could show the breakdown of travelled miles by year, month, day and hour. Vehicle dimension could help seeing which vehicle will need maintenance next, by showing the amount of a certain type of event for each vehicle. Driver dimension could help seeing the efficiency of each driver (relating to energy wasted for being outside the braking curve).

Measures: brake pressure, speed, duration of an event, distance of an event

An event contains default dimensions: Timestamp of the event start, source id (vehicle id, TELOC® serial number), event type, classification (previous known as alert), position and error.

Events can contain custom dimensions, which have to be defined in the event generator. A dimension can be made out of a signal value at the start of the event or a measure (e.g. DriverID).

There is a dimension table for each dimension. This table contains the dimension values (automatically populated over time or added manually in advance) and manually added attributes.

Example: the user adds names to the custom dimension driverID.

The purpose of the dimension table is to perform slice/pivot operations on events.

Example:  

Driver dimension table:

A measure can be any metric which can be extracted out of TELOC® data;

A measure has a key and a value (e.g. avgSpeed, 50 ) and is assigned to an event.

Measures are:

• Average of a signal over the time of the event
• Maximum signal value during an event
• Count of a signal condition
• Duration of a signal condition
• Distance of a signal condition

Events contain the default measures “duration” and “distance”.

Custom measures can be appended to every event type.

Key Performance Indicator. In EVA+ (till now) this term refers to a data aggregator (e.g. max, count, average or last value of a signal).

Configuration file containing the KPI definitions for a specific TELOC® configuration.

Signals (messages) as defined in the ERTMS/ETCS specifications (TSI CCS Annex A www.era.europa.eu/Core-Activities/ERTMS/Pages/Current-Legal-Reference.aspx).

A user with administrator rights on EVA+. This user can perform actions like adding and removing user, data and vehicles.

Data that cannot be parsed by EVA+. This can be due to missing parameters in the configuration (e.g. ETCS data that are recorded and sent to EVA+, but for which the syntax is not yet implemented).

A template is a saved query to the event database, which can be applied by user, dashboards and reports.

Analytics views: 

• EVENT ANALYTICS: Event analytics is a specific view that allows displaying and analyzing events in form of a pivot tables, hence aggregated events along a certain criteria (e.g. event types, fleet/vehicles, drivers, regions, etc) and then draw the corresponding event occurrences along a time axis.
• STATISTIC ANALYTICS: Statistics Analytics shall visualize data in bar graphs to allow a fast and accurate overview over a huge amount of aggregated data. The bar is configurable by the user, the data displayed is configurable.
• ALERT ANALYTICS: The Alert Analytics view provides a tabular view of incoming ‘alerts’. An alert is an ordinary event occurrence that requires special attention by the user and for that reason is displayed within the alert analytics view.
• INDICATOR ANALYTICS: The indicator analytics view provides a tabular view of incoming ‘indicators’. An indicator is an ordinary kpi.
• SIGNAL ANALYTICS: The signal analytics view displays the set of selected signals in a graphical way and / or tabular view. The view allows scrolling through the signal time line, zooming in and out, and for complex signals (e.g. structured messages) the user can also inspect the details for each data point. By adding markers the user can define reference points in order e.g. to measure distances and compare signal levels.
• VEHICLE POSITION: The vehicle location view provides a map with the last known position of the vehicles.
• EVENT POSITION: The event position view provides a map with the position where specific events occurred.

Tools:

• DATA IMPORT: This view allows to import data files
• DATA EXPLORER: This view allows to see if there are data in a specific time range
• DATA SAFE: This view shows the list and status of the imported data
• REPORT CONFIGURATION: This view is needed to configure the report settings
• REPORT LIST: This is the list of the automatically generated reports

Customer specific view, composed by one or more widgets.

Configurable part of the dashboard showing information coming from the other views.

Configurable document including information coming from one or more views. It is possible to configure its content and its automatic generation settings.

By means of this view it is possible to configure the fleet tree and to assign events to each vehicle/fleet/sub-fleet.

The basic view for the event is a list of all events, with all the available dimensions and measures as a column.

Example: