Model evidence at a glance
Verified for Sentinel's OCPP operational-evidence baseline, with model-specific enhanced telemetry kept separate until an additional mapping is approved.
This profile verifies the stated Sentinel integration scope. It is not electrical safety certification, regulatory approval, a warranty or a claim that every optional signal is available on every unit.
AmpNexus verified: AmpNexus has verified the published integration and capability scope shown on this profile.
Hardware evidence scorecard
CIRCONTROL eVolve Post Single Phase
Certification, integration and observable signals are assessed separately.
- OCPP certificationNot evidenced
- AmpNexus integrationVerified
- Operational stateVerified
- ConnectivityVerified
- Charging sessionsVerified
- EnergyVerified
- VoltageNot evidenced
- CurrentNot evidenced
- PowerNot evidenced
- TemperatureNot evidenced
- RCD diagnosticsNot evidenced
- Contactor feedbackNot evidenced
- Fault / reset evidencePartial
- Vendor APINot evidenced
- Sentinel assurance
- Observed
- Observability coverage
- 5 / 12
Coverage counts signal areas with published verified or partial evidence. It is not a charger health score.
Evidence flow
From charger to Sentinel
Charger
CIRCONTROL
eVolve Post Single Phase
ACAmpNexus verified
Device evidence
OCPP operational baseline
Sentinel
Published evidence lanes
Identity◐
State✓
Meter✓
Events✓
- Meaning
- Timestamps
- Provenance
- Limitations
Scope
- Model
- eVolve Post Single Phase
- Variant or configuration
- AmpNexus OCPP connection with status, transaction and meter-value reporting enabled
- Firmware
- Connected portfolio firmware identified during onboarding and boot evidence
- Geography or network context
- UK connected estates
- Evidence last reviewed
- 2026-08-09
- Mapping and integration scope
- 1 integration record
Integration paths
OCPP
OCPP operational baseline
Connected units using the AmpNexus OCPP path with the required messages enabled.
- Mapping version
- sentinel-ocpp-baseline-v1
- Last verified
- 2026-08-09
Integration limitations
- Optional and vendor-specific telemetry depends on firmware, configuration and documented mappings.
- A protocol connection does not by itself establish access to thermal, contactor, CP/PP or RCD evidence.
Capability evidence
- Verified
Availability and state
Connector operational state
- Integration source
- circontrol-evolve-post-single-phase-ocpp-baseline
- Availability conditions
- Available while the charge point is connected and sending OCPP status events.
- Units or meaning
- Available, Preparing, Charging, Suspended, Finishing, Unavailable and Faulted states are retained with timestamps.
- Freshness or cadence
- Event driven
- Evidence source
- AmpNexus OCPP core and Sentinel device-health implementation
- Last verified
- 2026-08-09
Sentinel keeps the source state and timestamp attached to the normalised operational view.
- Verified
Connectivity
Connection and heartbeat evidence
- Integration source
- circontrol-evolve-post-single-phase-ocpp-baseline
- Availability conditions
- Available for active AmpNexus OCPP connections.
- Units or meaning
- Connect, disconnect and heartbeat timing with the applicable charge-point identity.
- Freshness or cadence
- Connection event and configured heartbeat cadence
- Evidence source
- AmpNexus OCPP core and Sentinel device-health implementation
- Last verified
- 2026-08-09
- Verified
Sessions and metering
Charging sessions and energy
- Integration source
- circontrol-evolve-post-single-phase-ocpp-baseline
- Availability conditions
- Available when transaction and meter-value messages are enabled by the charger configuration.
- Units or meaning
- Session state, timestamps and reported energy retain their source units and mapping context.
- Freshness or cadence
- Transaction events and configured meter-value cadence
- Evidence source
- AmpNexus OCPP core and Sentinel device-health implementation
- Last verified
- 2026-08-09
- Verified
Faults and incidents
Reported fault and incident evidence
- Integration source
- circontrol-evolve-post-single-phase-ocpp-baseline
- Availability conditions
- Available when the charger reports a faulted connector state or supported device-health event.
- Units or meaning
- Source status, error context, classification and evidence confidence.
- Freshness or cadence
- Event driven
- Evidence source
- AmpNexus OCPP core and Sentinel device-health implementation
- Last verified
- 2026-08-09
- Partially verified
Device identity
Firmware identity
- Integration source
- circontrol-evolve-post-single-phase-ocpp-baseline
- Availability conditions
- Available when firmware identity is supplied through boot or inventory evidence.
- Units or meaning
- Manufacturer-reported firmware version string.
- Freshness or cadence
- At boot and during applicable inventory refreshes
- Evidence source
- AmpNexus OCPP core and Sentinel device-health implementation
- Last verified
- 2026-08-09
A firmware string establishes identity context; it does not prove that every optional capability is enabled.
Evidence boundary
What is not yet evidenced
- No model-specific temperature source is included in the published OCPP baseline profile.
- Contactor command/output, CP/PP and RCD evidence require an approved manufacturer mapping or vendor API where the standard integration does not expose them.
- Optional device-specific fault fields remain scoped to the firmware and configuration that emits them.
How to improve this profile
Expose and verify more evidence
- Provide a manufacturer-maintained firmware and capability matrix.
- Document approved vendor API or OCPP DataTransfer fields for model-specific telemetry.
- Verify thermal, protection, contactor and control-pilot evidence for a higher Sentinel evidence level.
Evidence sources and review
- AmpNexus portfolio hardware inventory
- AmpNexus OCPP core and Sentinel device-health implementation