Scoped hardware profile
A public manufacturer and model record with the applicable firmware, configuration and integration boundary.
For manufacturers
Make your charger’s evidence easier to use—and harder to misread.
Work with AmpNexus to document model, firmware, protocol, telemetry, and integration capabilities for a clearer mixed-estate evidence profile.
Why documented capability matters
Operators cannot use evidence they cannot interpret
The same field can carry different meaning across implementations. A signal may exist for one firmware version and not another. A vendor API may provide context that the configured OCPP route does not.
Clear documentation helps operators understand what is available, how it should be interpreted, where it applies, and what remains unknown. It also reduces the risk that incomplete telemetry is mistaken for poor charger health—or that missing evidence is overlooked entirely.
Integration path
From discovery to ongoing evidence review
Each stage keeps technical scope, evidence ownership, known limitations and change history attached to the integration.
- 01
Discover
Identify the applicable models, variants, firmware, protocols, APIs, and available evidence.
- 02
Map
Agree canonical meaning while preserving source semantics, units, timestamps, quality, and provenance.
- 03
Verify
Review the evidence and test the integration against the stated technical scope.
- 04
Explain
Document verified capabilities, limitations, unknowns, and applicability in a public-safe profile.
- 05
Publish
Release the approved profile, evidence level and verification status with their scope attached.
- 06
Maintain
Review changes in firmware, hardware, APIs, mappings, and capability over time.
What to prepare
Bring evidence at the level where it changes
Use the manufacturer integration contact route to begin the review. Do not submit credentials, private keys, live customer telemetry, personal data, or security-sensitive implementation details through an unapproved channel.
- Manufacturer and verified model identifiers.
- Variants and configuration boundaries.
- Applicable firmware versions or ranges.
- OCPP versions, profiles, and implemented messages or fields.
- Approved vendor API documentation and access process.
- Signal definitions, units, timing, quality, and known limitations.
- Relevant fault, warning, state, metering, thermal, and protection evidence.
- Change history, technical owner, and public-safe supporting documents.
What the review produces
Leave with a usable profile, not just a badge
The review produces an operator-facing record that stays useful after publication and can be maintained as the product changes.
Capability matrix
A field-level view of observable evidence, source, cadence, provenance and verification state.
Evidence and verification status
An operator-facing Sentinel evidence level paired with the profile's documented review status.
Limitations and next steps
Known gaps, operational impact and the firmware, API or mapping work that can unlock richer evidence.
What operators see
A profile that shows scope, not just a badge
The hardware profile records which capabilities have been verified, the integration path, model and firmware applicability, evidence source, last review date, and known gaps.
The evidence level and verification status summarise integration assurance, while the underlying evidence and limitations remain visible. Neither is electrical safety certification.
Explore the hardware directoryProgramme relationship
Verification follows the evidence
The Sentinel Integration Assurance Programme makes verified integration depth easier to understand. Participation does not guarantee AmpNexus verification, and verification does not certify electrical safety, standards compliance, or overall product quality.
Review the programmeFAQ
Manufacturer questions
Does submitting information guarantee AmpNexus verification?
No. Publication and programme status depend on the approved verification and review process.
Can information be scoped to specific firmware or configurations?
Yes. Capability should be recorded at the level where it can be verified and should not be generalised beyond that scope.
How are updates handled?
The process records evidence ownership and review dates so profiles can be updated when hardware, firmware, APIs or mappings change.
Is the programme an electrical safety certification?
No. It concerns integration and observability evidence only.
Make your hardware easier to understand in the field
Share verified model, firmware, protocol, signal, and integration information so operators can see what your chargers can evidence—and where the boundaries are.