WELCOME TO THE HUBJECT ONBOARDING GUIDE
As an EMP, you benefit through higher customer satisfaction as your EV driver members will have access to public charging infrastructure across networks and around the world with intercharge. Your customers will be able to identify available charging station on your app or by the recognizable intercharge logo. By connecting to the intercharge network, your customers will be able to use every charging station of all participating CPOs you connect with as an EMP via eRoaming.
Once you are onboarded to the HBS (Hubject Brokering System) you will be part of the largest open eMobility marketplace, and an open seamless charging network from which everyone ultimately profits.
This guide was created for you as an EMP (Emobility Service Provider) and provides the details you need to onboard to the Hubject eRoaming platform.
An integrated ticketing system serves as the communication interface between you and Hubject. For the Onboarding process, please submit tickets using the standardized ticket forms as directed in the Onboarding Guide. If you have further questions you can use the blue “Support” button in the lower right corner of the screen.
All major steps of the Onboarding process are explained in the guide.
There are two different ways to be connected to the Hubject platform as an EMP.
The Offline EMP has no real-time connection for authorization to the Hubject platform. This means that authentication data for authorization MUST be sent and stored on the Hubject platform with eRoamingPushAuthenticationData. The HBS authorizes charging sessions locally on the platform. There can however be a real-time connection for pulling dynamic POI data. Furthermore, the CDRs, as a result of each charging session, are not directly forwarded to the EMP but are also stored on the HBS. The EMP than can download this CDRs in line with its demands via the eRoamingGetChargeDetailRecords.
The Online EMP is fully connected to the Hubject platform via a real-time interface. This means that authorization requests are forwarded to the EMP’s system. To ensure an online authorization, the EMP MUST implement the holistic authorization Web service. Furthermore, the CDRs, as a result of each charging session, are directly forwarded to the EMP’s system. The CPO MUST therefore implement the eRoamingChargeDetailRecord.
Let's get started:
- Read all information providedin order
- Use the onboarding project checklist provided in 0.2 to track the Onboarding steps
- Please do not skip any step as you will need to send information through preconfigured ticket forms step
- At the end of each article, you are directed to the next step (You can also use the navigation sidebar on the left)
- If you have any questions or require further information to complete a step, please contact us using the blue “Support” key in the bottom right corner
In addition, the Onboarding FAQs provide useful answers to key questions.
The next article provides you with an overview of the different phases of the onboarding process and checklist.