Enlarge image:

1. optiSMS
open telematics interface – Standardized Message Structure

Definition, design and development of a standardized interface- and data-protocol (air-interface) for the bidirectional data communication between an communication server (CS) and mobile units (MU).

2. optiXML
open telematics interface - eXtensible Markup Language

Definition, design and development of a standardized interface- and data-protocol (back-end-interface) for the bidirectional data communication between an communication server (CS) and back-end-applications (e.g. ERP, etc.)

Situation in the Future – Technical Challenges to solve

• Heterogeneous System:
  - Different operators
  - Different vendors of
  o mobile units (MU)
  o communication servers (CS)
  - Different needs and features on freight cars and locomotives
  - Different limitations from the hardware
• Extendability
  - For new needs and features
  - Concurrent deployment not possible!
  o Dynamic extendability required
  o “Simple” versioning not adequate

Solution: Generic Protocol

• Communication settings
• Reporting and query
• Configurable mobile unit (MU) behavior
  – Event
  – Action
  – Modes
• Configurable periphery as a bridge between “real” and generic world

Goals

• Mind the semantic gap: protocol as precise as possible
• Support of future needs: Extendability
• A subset of the generic protocol shall be adequate for all use-cases

Benefits

• Operator
  – Interoperability (heterogeneous system)
  – Internally
  – Externally with other operators
  – Enables second source for mobile units (MU)
• Vendors
  – Short learning curve
  – New markets
  – Usable for other application fields (e.g. container, asset tracking, etc.)
  – Return on Investment (ROI)

Costs

• Modification of current communication server (CS) and application server (AS)
  Adaptation of the use-cases