Skip to content

Operator Information Module

Jump to bottom Edit New page
Tjalle Groen edited this page Sep 29, 2020 · 3 revisions

Operational Information

As a summary of the data exchanged provided by the TOMP-API calls, Fig. 4 shows an overview of the data sets’ blocks and units exchanged between the TOs and MPs.

The operator information endpoint should contain all necessary information about the operator, this information can be summarized in the following categories :

  • Regions
  • Stations
  • Available assets
  • Alerts
  • Calendar / opening hours
  • General information
  • Pricing plans, these are extended with TOMP objects (to represent conditions like max fares, scales etc)

Operational view of the API
Fig. 4: Data exchange overview of TOMP-API

Blueprint for an Application Programming Interface from Transport Operator to MaaS Provider (TOMP-API) – Version Dragonfly 1

TOMP-API1

Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations

Blueprint index

Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications

Blueprint appendices

A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API

Clone this wiki locally