Monitoring access is the ability for authorized people or systems to view the performance, status, and operational data of EV charging infrastructure through a CPMS (charger management platform), dashboard, or API. It defines who can see what data (sites, chargers, sessions, meters, alarms) and how they can access it (web portal, mobile app, integrations).
Why monitoring access matters
Proper monitoring access improves uptime, accountability, and operational efficiency:
– Enables faster fault detection and response, improving uptime and reducing MTTR
– Allows installers and service teams to verify commissioning and diagnose issues remotely
– Supports site owners with visibility into utilization, energy use, and revenue performance
– Reduces unnecessary site visits by resolving issues through remote troubleshooting
– Protects sensitive data by limiting access to the minimum needed for each role
What monitoring access typically includes
Monitoring access can cover different levels of visibility and control:
– Charger status (available, charging, faulted, offline) and live alerts
– Session monitoring (start/stop time, kWh delivered, user identifier, tariff applied)
– Metering and energy data (site totals, sub-metering, MID metering where applicable)
– Fault and event logs (alarms, error codes, connectivity drops, protective trips)
– Performance KPIs (utilization, success rate, availability, response times)
– Optional control actions depending on permission level (remote restart, unlock connector, firmware update)
Typical roles and permission levels
Monitoring access is usually managed with role-based permissions:
– Site owner / property manager: high-level dashboards, utilization, energy, reports
– CPO operations team: full network monitoring, alerts, session control, tariff management
– Installer / commissioning partner: limited access for setup, diagnostics, and handover checks
– Service and maintenance provider: fault logs, remote tests, limited control actions
– Finance / accounting: billing exports, settlement reports, invoice and receipt data
– IT / security: audit logs, integration access, cybersecurity monitoring
How monitoring access is provided
Common access methods include:
– CPMS web portal accounts with role-based permissions
– API access with keys or OAuth for integrations (BI tools, ERP, ticketing systems)
– Alerting integrations (email, SMS, Slack, service desk tickets)
– Read-only links or reports for stakeholders who do not need direct CPMS access
Security and governance considerations
Monitoring access should be governed like any other critical system:
– Use least-privilege permissions and segregate duties (operations vs finance vs admin)
– Require strong authentication (MFA) and secure credential management
– Maintain audit logs of logins, configuration changes, and remote commands
– Define data retention and privacy rules for user/session data
– Limit third-party access to specific sites and time windows when needed
Common issues and pitfalls
– Too many admins increases risk of misconfiguration and unauthorized actions
– No audit trail makes accountability and incident investigation difficult
– Sharing logins instead of individual accounts weakens security and traceability
– Overly restricted access slows down maintenance and increases downtime
– Inconsistent data visibility across roaming partners can create reporting gaps
Related glossary terms
CPMS
Monitoring module
Uptime
Mean Time To Repair (MTTR)
OCPP
Incident response plan
Role-based access control (RBAC)
Data minimization
Remote diagnostics
Firmware updates