Mixed Site Strategy
Support static, dynamic, and hybrid site patterns inside one network-facing language.
Property chargers and public chargers together
No forced one-flow policy
Cleaner rollout decisions
CPO teams do not just need dashboards. They need charging flows that fit real site behavior, remote actions that feel intentional, and session state that stays legible when support pressure rises.
Site-specific flow choices, mixed charger behavior, payment edge cases, and support requests are all normal in network operations. The UI should make that variation understandable instead of multiplying screens.
Support static, dynamic, and hybrid site patterns inside one network-facing language.
Property chargers and public chargers together
No forced one-flow policy
Cleaner rollout decisions
Show what is happening now, what happened just before, and what the operator can do next.
Session-linked logs
Clear state transitions
Support-ready evidence
Make remote actions explicit and contextual so operators do not second-guess intervention timing.
Remote start intent
Remote stop context
Machine state beside operator action
Keep the public charging path tight and understandable even as backend complexity grows.
Charge hub route
Static and manual flows
Consistent mobile-facing language