Sentinel Integration Assurance Programme
The Sentinel programme gives manufacturers and integration partners a structured way to document and verify evidence capability—without confusing observability with electrical safety.
What it is for
Operators need to know more than whether a charger connects. They need to understand which signals are available, where they came from, what scope has been verified, how recently it was reviewed, and what limitations remain.
The programme documents that evidence consistently across manufacturers and integration paths.
Improve firmware evidence readinessWhat it is not
A Sentinel verification status is not electrical safety certification, regulatory approval, type approval, a warranty, or a judgement about overall charger quality. It does not replace manufacturer documentation, applicable standards, local protection systems, qualified inspection, or statutory obligations.
Verification status
Verification status describes the governance state of a hardware profile. It remains separate from the Sentinel evidence level, which describes how much useful evidence the integration exposes.
The manufacturer and model identity is published, but no verified capability is inferred from the listing alone.
Public manufacturer or Open Charge Alliance evidence documents the protocol route, but no Sentinel capability level has been assigned yet.
AmpNexus has verified the published integration, evidence scope and limitations against the programme criteria.
A material firmware, hardware, API or mapping change requires the public profile to be reviewed again.
Sentinel evidence level
Evidence levels describe operational depth. Verification status shows whether the public profile is listed, manufacturer documented, AmpNexus verified or due for review. A published badge combines the two, for example “AmpNexus verified — Observed”.
These levels describe verified evidence depth for third-party integrations. They do not rate electrical safety, product quality or standards compliance.
01
Baseline operational evidence is available through a verified integration, with known limitations made visible.
02
Additional verified signals or context extend the baseline view.
03
A deeper supported integration provides documented mappings, provenance, and a broader evidence set.
04
A verified evidence interface supports the Sentinel Confidence framework.
Review criteria
The programme follows the capability from source documentation through mapping and test evidence into the public profile. Credentials, private keys and live customer telemetry move only through an approved secure exchange after initial triage.
Programme governance
Every verification outcome applies only to the stated model, firmware, configuration and integration route.
Operators can inspect capabilities, provenance, limitations, review date and enhancement opportunities behind the status.
Material firmware, hardware, API or mapping changes move the profile back into review until the evidence is confirmed.
Manufacturers and operators can report outdated or incorrect profile information for governed review.
Verification journey
The review follows the evidence from initial scope through technical verification, profile publication and ongoing change control.
Define the manufacturer, model, variant, firmware, configuration, protocol, API, and integration under review.
Collect approved documentation, mapping information, test results, and capability limitations.
Verify that public capability assertions match the defined scope and evidence.
Prepare the hardware profile with provenance, dates, unknowns, and limitations.
Apply the programme criteria and governance process to the defined scope.
Reassess after material firmware, hardware, API, mapping, or programme changes.
FAQ
No. It verifies the stated integration and observability evidence. It is not electrical safety certification, regulatory approval, type approval or a replacement for device protection.
No. A protocol version alone does not establish which capabilities are implemented, configured, accessible, timely, or verified.
The manufacturer or integration partner starts an integration review, confirms model, firmware and configuration scope, provides the applicable mappings and test access, and resolves the known gaps recorded on the profile. AmpNexus then publishes the verified capability scope and evidence level.
No. Confidence Ready is a third-party evidence level. PlugStream Native is a separate native-device category with a direct relationship to PlugStream firmware and device-originated evidence.
No. Verification depends on the evidence supplied, technical scope, test outcome and programme review decision.
Timing depends on the number of models, firmware variants, integration routes and evidence sources included in the review.
Share verified model, firmware, protocol, signal, and integration information so operators can see what your chargers can evidence—and where the boundaries are.
