This guide gives an overview of the steps required to create a new Local Actor on the Sweden data exchange.


Prerequisites

Before a Local Actor can be created, the organisation needs to be registered and a FreshDesk account is required to create support desk tickets. See the Quick Start Guide for details.


An organisation is also required to be registered as a "CS1 Issuer" under EN ISO 14816 in order to be able to publish data on the exchange. The registration ID forms part of the publisher ID of the Local Actor. For more information, please see https://www.itsstandards.eu/registries/how-to-become-registered/. Registration under EN ISO 14816 is not required to consume data.


A temporary publisher ID may be issued while you complete the registration process. This temporary publisher ID is to be used only for testing purposes where data is published and consumed by the same organisation. Please submit a support ticket from the Support Home Page to request a temporary publisher ID. 


Terminology

Local Actor

Participant organisations may develop one or several C-ITS systems that publish or consume data on the Sweden exchange. Each system that connects to the data exchange is referred to as a “Local Actor”.

One security certificate is registered per Local Actor.


Capability

A capability refers to a data set that is published by one Local Actor and consumed by one or more other Local Actors.

A single Local Actor can publish or consume multiple capabilities.


Permission

Access and rights for the Sweden data exchange are arranged by Monotch.


Steps for Creating a Local Actor

One security certificate is required per Local Actor. A Certificate Signing Request (CSR) is required to register a new security certificate.


  1. Generate a CSR, see the Knowledge Base article "Generating a Certificate Signing Request" for details.
  2. Download and fill out the “New Local Actor” form attached to this article.
  3. Create a new FreshDesk support ticket by clicking on “New Support Ticket” on the Support Home Page. Choose ticket type "onboarding".
  4. Attach the New Local Actor form and the CSR to the support ticket. Please note: attach only the CSR, do not send the private key.
  5. Monotch will sign and return the security certificate in a response to the support ticket.
  6. Registration of the new security certificate will be displayed in the data exchange dashboard.


Next step

Once a Local Actor has been created, capabilities can be consumed and produced. See the Knowledge Base article “Consuming and Producing Capabilities” for more details.