Project Background
An industrial park needed to manage charging devices across several parking areas. Device status, orders, faults, and maintenance records were distributed in different backends, making it hard for operators to understand device availability, fault causes, and station performance.
Applicable Scenarios
This case is suitable for New Energy projects that need to unify offline processes, device data, user operations, and management reports. If an enterprise already has partial systems, the project can start from high-frequency workflows or critical devices and then expand gradually.
Client Requirements
- Manage stations, charging piles, connectors, users, orders, and maintenance staff.
- View online status, charging status, fault codes, and utilization rate in real time.
- Send alerts for offline devices, charging exceptions, fault codes, and order anomalies.
- Build a closed loop from alert to dispatch, handling, and review.
Technical Solution
The project was designed around device access, operation management, and maintenance closure. It unified device status, order data, and fault information to help operators move from problem discovery to closed-loop handling.
- Built station, device, connector, and operation account management modules.
- Integrated charging pile protocols or vendor APIs for status, fault, and order data.
- Configured fault levels, alert rules, and work order workflows.
- Generated reports on station utilization, orders, device faults, and maintenance efficiency.
System Functions
- Station map, device list, real-time status, fault code explanation, and operation logs.
- Order query, user records, charging details, and operation statistics.
- Alert center, work order dispatch, processing records, and review analysis.
- Reserved APIs for payment, parking, membership, or third-party operation platforms.
Data and Security Design
- Define permissions for administrators, business users, maintenance staff, and external collaborators.
- Keep operation logs for important business actions to support tracing, audit, and review.
- Use authentication, parameter validation, and clear error responses for external APIs.
- Support backup, export, and conditional query for important data to simplify long-term maintenance.
Implementation Process
The team first validated device protocols and vendor APIs, then built station and device archives. Before launch, the focus was order consistency, status update frequency, fault code parsing, alert de-duplication, and work order flow.
Acceptance Focus
- Core workflows can run through creation, processing, query, and archive.
- Key data fields match the client's business definitions and report results can be reviewed.
- Mobile, backend, and API data remain consistent with clear exception messages.
- Deployment, account permissions, operation instructions, and maintenance methods are delivered clearly.
Delivery Results
- Charging devices from multiple stations can be managed in one platform.
- Fault handling changed from passive feedback to alert-driven work order closure.
- Operators can analyze usage by station, device, and time period.
- The platform reserved interfaces for payment, parking linkage, and membership systems.
Project Boundary
This is an anonymized industry case focused on project type, technical route, and delivery method. Real implementation should be evaluated against the client's existing systems, devices, workflows, permissions, and maintenance conditions.
Reusable Experience
Charging pile projects should confirm device protocols, vendor APIs, payment flow, and maintenance responsibility early. For operation teams, online rate, order accuracy, and alert closure are more important than dashboards alone.
Related Services
FAQ
Can different brands of charging piles be connected?
They can be evaluated, but protocols, open APIs, and data fields must be confirmed for each brand.
Must payment be included in the first version?
No. Device monitoring and maintenance can be launched first, with payment added later.
How can repeated fault alerts be reduced?
Alert levels, duration, recovery status, and de-duplication rules can reduce invalid notifications.
Online
Phone
WeChat
Top