Technologies
EV Fleet Charging Platform
EZFleet is an electric fleet charging platform that helps companies manage EV charging across public, workplace, and home charging scenarios. The platform supports fleet managers and drivers with access to charging locations, charging activity visibility, operational reports, driver management, and centralized billing workflows.
Yellow! GNU / Matrix Rom provided ongoing software development, production support, investigation, debugging, and platform improvement services for EZFleet, working across the mobile app, admin platform, backend services, database layer, cloud infrastructure, and OCPI-related charging data flows.
EV charging platform support
We supported the technical operation of a complex EV mobility platform where charging sessions, CPO data, driver accounts, charging tokens, app behavior, and administrative reporting all need to work reliably together.
Our work included investigation and fixes across:
Mobile app behavior on iOS and Android
Charging station map and location display
Driver and fleet manager login flows
Admin platform usability
Driver, organization, tag, chip, and token management
Transaction exports and operational reporting
OCPI session and CDR data reconciliation
AWS, PostgreSQL, logging, staging, and production deployment flows
Key areas of contribution
Mobile app reliability and usability
We investigated and addressed issues affecting the driver-facing application, including platform-specific behavior on iOS, map loading, station visibility, filtering, connector information, transaction display, no-internet handling, app stability, and charging-screen behavior.
This included diagnosing cases where the application behaved differently on iOS and Android, improving error handling, and helping the app remain usable even when external data or assets were incomplete.
Admin platform improvements
We worked on the operational back office used by administrators and fleet managers. This included improvements around organization search, sorting, driver exports, transaction exports, fleet manager login, user and driver creation flows, organization selection, validation messages, and management of active/inactive users.
These improvements helped reduce manual support effort and made daily fleet operations easier to manage.
Driver, tag, chip, and token management
A significant part of the support work focused on the lifecycle of drivers and charging identifiers: creating drivers, assigning tags, moving tags between organizations, disabling or reactivating tags, preventing incorrect assignments, and investigating cases where tags or chips appeared in the wrong account or disappeared from the expected company view.
The goal was to make driver and charging-token operations safer, more traceable, and less prone to manual correction.
OCPI, sessions, CDRs, and charging transaction diagnostics
We investigated complex charging-data discrepancies between CPO reports, OCPI broker data, session records, CDR records, and EZFleet’s own transaction tables.
This work included:
Comparing CPO-provided reports with OCPI receiver data
Identifying missing or incomplete sessions
Checking whether CDRs were received or absent
Building diagnostic SQL views and queries
Analyzing corrupt, incomplete, zero-cost, and non-completed sessions
Separating EZFleet-side issues from upstream CPO or OCPI broker data gaps
This helped clarify whether a reporting issue originated inside EZFleet, in the OCPI broker, or from data not being sent by a charging provider.
Reporting and export functionality
We implemented and investigated export flows for operational data, including drivers, transactions, transaction history, and date-range based reporting.
This supported finance, operations, reconciliation, and customer service workflows where fleet managers need accurate data rather than manual database extraction.
Backend, AWS, database, and deployment support
We supported the backend and infrastructure side of the platform, including AWS-based diagnostics, CloudWatch log analysis, PostgreSQL queries, deployment investigation, staging and production release support, logging improvements, and deployment-stack refactoring.
This helped stabilize delivery and gave the team better visibility into what happens when charging, session, driver, or tag operations fail.
Technical scope
The work touched multiple layers of the platform:
Mobile application support for iOS and Android
Admin web platform
Backend APIs and serverless functions
AWS cloud services and logs
PostgreSQL data analysis and diagnostics
OCPI-related session, CDR, location, and transaction flows
Fleet manager and driver identity flows
Tag, chip, and token lifecycle management
Reporting and export features
Staging, production deployment, QA, and sanity testing
Business value
Our support helped EZFleet operate and improve a live EV fleet charging platform while handling real production issues, customer-reported defects, data inconsistencies, and new operational requirements.
The engagement combined development, troubleshooting, data analysis, cloud support, QA, and production release assistance — the kind of practical technical support needed by platforms that connect mobile apps, fleet operations, charging providers, and financial reporting.
Why it matters
EV charging platforms are not simple CRUD applications. They depend on real-time data, external charging networks, OCPI integrations, session and CDR consistency, driver identity, mobile reliability, and accurate financial reporting.
For companies operating in eMobility, Yellow! GNU can provide the software engineering and technical support needed to keep such systems working, improving, and scaling.
Services provided
Software development
Mobile app troubleshooting
Backend development and debugging
OCPI data-flow investigation
PostgreSQL analysis
AWS log and infrastructure diagnostics
Admin platform improvements
Driver and token management support
Reporting and export functionality
QA, staging, production support
Ongoing technical support
Domains
EV fleet charging · eMSP platforms · OCPI · CPO integrations · Mobile apps · Admin platforms · Fleet operations · Charging transactions · Session and CDR reconciliation