List of Participant IDs (PID) and known implementations
Purpose and responsibility
Purpose of table below is for BoB-participants to get information about:
Interoperability possibility. It could however indicate that there is an implementation but it is not publicly accesible.
The implementation status of participants implementations
Participant organisation and contact information
Responsibility
The information accuracy within the list is each participant's responsibility.
Contact help.samtrafiken.se to help us keep it up-to-date.
Participant implementation status list
Color coding - Implementation status Implementation status color indication for Development and Production requires publication of endpoints to Participant Metadata test or production (interoperability aspect) | ||
Planned | Development | Production |
Definitions: S (server) = A service that implements an API and responds to requests to the specified API. E.g. an authentication service or a ticket service. C (client) = A service/system that makes requests to a server using a specified API. E.g. a validation device or a metadata manager client. Note: If a client has an authentication service it still counts as only client | ||
PID | Organisation Name | Type of participant | Contact Information | Authentication | Device | Inspection | Participant Metadata | Product | Ticket | Validation | Booking | Traveller | Token | Comments |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | BoB, testservices. | Administrator | S | S | S | S | S | S | S | S | S | Test environment for BoB |
| ||
10 | Skånetrafiken | Operator | CS | CS | CS | CS | CS | CS | CS | CS | Ticketing system (singapore) |
| |||
11 | SL (Region Stockholm) | Operator | CS | CS | CS | C | CS | CS | CS | Ticketing system (TAP) |
| ||||
12 | SilverRail Technologies AB | CS | S | C | CS | CS | Adapters for BoB interface |
| |||||||
14 | Västtrafik AB | Operator | CS | CS | CS | C | CS | CS | CS |
| |||||
15 | Merresor AB | Reseller | Client? |
| |||||||||||
16 | Samtrafiken AB | Administrator | CS | BoB Connect |
| ||||||||||
20 | SJ AB | Reseller | CS | CS | CS | CS | CS | BoB interfaces for old ticketing system |
| ||||||
21 | Infospread AB | Supplier |
| CS | CS | CS | C | CS | C | CS | Client (App) | ||||
22 | Hallandstrafiken AB | Operator | CS | CS | CS | CS | CS | CS | CS | CS | CS | Ticketing system (BoBcat core - Lynx) |
| ||
23 | Länstrafiken Kronoberg | Operator | CS | CS | CS | CS | CS | CS | CS | CS | CS | Ticketing system (BoBcat core - Lynx) |
| ||
24 | Jönköpings länstrafik | Operator | CS | CS | CS | CS | CS | CS | CS | CS | CS | Ticketing system (BoBcat core - Lynx) |
| ||
25 | Kalmar länstrafik | Operator | CS | CS | CS | CS | CS | CS | CS | CS | CS | Ticketing system (BoBcat core - Lynx) |
| ||
26 | UL (Region Uppsala) | Operator | CS | CS | S | CS | CS | CS | CS | Ticketing system (BoBcat core - Ulla-Bella) |
| ||||
27 | Mälardalstrafik Aktiebolag | Operator | CS | CS | C | CS | CS | Adapters for ticketing system (Ridango) |
| ||||||
28 | Sörmlandstrafiken | Operator | CS | CS | C | S | S | Adapters for ticketing system (Ridango) |
| ||||||
29 | Länstrafiken Norrbotten | Operator |
| Project for new ticketing system started |
| ||||||||||
30 | Länstrafiken i Västerbotten | Operator |
|