Very engaged and professional team with tons of industry knowledge and hands on experience in the e-mobility sector.
Radosław Dobrołęcki, Co-Founder at Ave Mobility
We provide:
Tech development & support
to help eMobility Service Providers and Charge Point Operators fully benefit from the services they offer
Top-notch modules
ready-to-integrate components, boosting the integration with Open Standards, to unlock e-mobility opportunities
eMobility experience
documented successes on both sides of the market eMobility Service Providers and Charge Point Operators
IT expertise
we have extensive domain knowledge in the tech aspects of the e-mobility world
What we can do to boost your eMobility growth?
1
Conduct seamless integration with Open Standards
We can offer ready-to-integrate components that will boost the adaptation process, or integrate your system with the selected Standard.
2
Connect your ideas with the best technology
We know the code, eMobility forecasts, and most performing technologies, that support the green, integrated world.
3
Conduct workshops
To verify your product, identify areas for improvement or help you better understand users’ interactions and meet their expectations.
4
Support your growth with the best tech knowledge and expertise
Whether you are an eMobility Service Provider or Charge Point Operator, we have experience and domain knowledge on both sides.
5
Nourish your business opportunities
Recent updates and most desired features are something we always keep in mind. Staying up-to-date will drive your business ahead.
For eMobility Service Providers
Whether you are an aspiring eMSP looking for opportunities to grow or a senior explorer, you might need a keen eye to draw a bigger picture. With technical knowledge, norms requirements, and possibilities driven by the best software solutions, we can help you expand your business. We can partner your company by establishing and supporting:
The road to achieving eRoaming
Sky-rocking user experience
Open, user-friendly network
The discovery of functional requirements
Platform development
Learn more
For Charge Point Operators
A secure, stable, and accessible charging infrastructure provides maximum efficiency. We partner Charge Point Operators with the most performing tech solutions, recent updates in generally accepted standards, eMobility experience, and domain knowledge. We can help you unlock opportunities by:
Secure charging infrastructure
Core platform: CDR processing, charging station management
Payment, billing, and settlement solutions
Customized infrastructure
Integration with open standards
Learn more
Interested in smooth and simple integration?
Fill the contact form and we will reach you as soon as possible
1
OCPI Gateway
Anti Corruption Layer between any CPO/eMSP system and any OCPI partner (hub and p2p partners)
Read more
2
OCPP Gateway
OCPP server allowing connection to the charge point via OCPP 1.6 or 2.0.1 protocol.
Read more
3
OCPP Virtual Charge Point
Software Charge Point for e2e testing and monitoring of the CPO platform based on OCPP 2.0.1.
Read more
4
White-label EMSP Application
Mobile app for EV drivers with a developed web application allowing e-mobility providers for its seamless management
Read more
5
CPO Platform
Customizable CPO platform sold on proprietary licensing and ready to run in client’s infrastructure or supported by Solidstudio.
Read more
About the most commonly used standards in the industry
OCPP - Open Charge Point Protocol
An application protocol for communication between charging stations and a central management system. It is available for free, international, open-source, vendor-independent standard.
OICP - Open InterCharge Protocol
Developed by Hubject, is an implemented communication standard between eMSP and CPO systems via the Hubject platform.
OCPI - Open Charge Point Interface
Designed for information exchange about charge points between CPOs and eMSPs to facilitate scalable and automated EV roaming.
ISO15118
An international standard for bi-directional digital communications between electric vehicles and the charging station.
Components created through experience - what we have learned and how we can nourish eMobility development?
Creating a valid data model from the beginning
Late changes to the data model are time-consuming. MVP or initial versions of the software cover every basis needed. When the system does not require a sophisticated model of the charging infrastructure it may be enough to shape the whole charge point as a flat structure. Upon this simple model, more features can be built, till your range grows, and a need to open the platform using some open standard comes up.
This action requires developing mapping between the internal model and the one introduced by the standard. If the existing model does not support concepts (e.g. Location and EVSE) and does not follow general standards, when it comes to the format of IDs, it may require plenty of work to perform such mapping.
Observation:
While working for one of our partners, mapping their existing codebase to make it available for open standards, took several months for a team of developers. In fact, if the model would match the standard from the beginning, the integration would require just a simple action, and full integration would be possible within a few weeks.
Lesson learned:
The time for full integration can be significantly reduced (from a few months to a few weeks) thanks to the implementation of ready-made code linking the standard and the platform.
Creating an efficient architecture of the system from the start
Some aspects of system architecture are specific to the domain.
For example:
- deciding which processes are synchronous and which are asynchronous
- the decision whether or not some data must be immutable
Observation:
General concepts, but taking into account these limitations from the very beginning helps to avoid making wrong decisions when designing and developing the e-mobility platform.
Knowing the details of adopted standards to customer needs
OCPI is defined as an open standard. In theory, everyone ought to introduce this standard in the same way.
Observation:
OCPI is not always the norm. Hub Gireve, for example, extends this standard. Some components exist and are not part of the OCPI documentation. Some OCPI partners require a certain sequence of specific actions that are actually not part of the standard. It is worth knowing this upfront when designing the CPO/eMSP end system.
Bringing the domain knowledge
Having the domain knowledge within the development team allows participating in specific direct business conversations about e-mobility. We are familiar with general concepts, e-mobility background (CPO, eMSP/EMP, EVSE, eMI3 ID, OCPI, OICP, OCPP), different market approaches (public/private/fleet charge points), so we can immediately proceed directly with the specific business issues that are to be solved, rather than technical details (we already know them).
Observation:
We have learned that getting to know a specific area takes time, but once explored, it allows us to catch common parts. The observations turned into concrete solutions are an improvement for the future.
What else can we offer?
For more information fill the contact form or visit our blog to find more of our publications from the eMobility world
