AmpNexus

Sentinel Confidence

Confidence begins with knowing what you can see.

A charger can appear healthy when evidence is sparse, delayed, stale, or internally inconsistent. Sentinel Confidence shows what supports the conclusion—and what does not.

Sentinel estate intelligence

Health

Understand what the available evidence says about operational condition.

State · change · trends

Observability

See the coverage, freshness and provenance behind the operational view.

Coverage · freshness · provenance

Evidence stays attached to findings, so teams can see what changed and why it matters.

The evidence story

“Available” can be a fact. It is not the whole evidence story.

Two chargers can report the same top-level status while exposing very different supporting evidence. One may provide recent measurements, detailed faults, and clear state transitions. The other may provide a single status message with no independent context.

A useful monitoring system should not make those situations look equally certain. Sentinel Confidence starts by separating what the evidence suggests from how much credible evidence is available.

Health and Observability

Two measures, two different questions

A health view is useful only when the evidence behind it is clear. Sentinel keeps the operational conclusion and the quality of its evidence separate.

Operational view

Health

What does the available evidence suggest about this charger?

Health summarises what the available, relevant evidence suggests about an asset’s operational condition. A responsible health view should show when it was evaluated, link to the evidence behind it, and remain inconclusive when the evidence is insufficient.

Built from relevant state, event, measurement and trend evidence.

Evidence view

Observability

How much credible evidence is available to support that view?

Observability describes the coverage, freshness, provenance, and usefulness of the evidence available for evaluation. It makes gaps visible instead of allowing “no reported fault” to become “healthy.”

Built from coverage, freshness, provenance, usefulness and corroboration.

Health describes the conclusion. Observability describes the evidence available to support it.

Explainability

A conclusion should be able to show its working

Sentinel attaches an evidence trace to material findings so the operator can see which inputs supported the view, which conflicted, which were missing or stale, and when the evaluation occurred.

Explainable findings

Why Sentinel surfaced this

Material findings keep the operational context and evidence needed to support investigation.

Finding
What changed or requires attention.
Evaluated at
When Sentinel evaluated the available evidence.
Evidence freshness
How recent the supporting inputs are.
Supporting evidence
The signals and events that support the finding.
Conflicting evidence
Inputs that weaken or challenge the conclusion.
Missing or stale evidence
Known gaps that affect confidence in the view.
Source and integration path
Where the evidence originated and how it reached Sentinel.
Applicable scope
The relevant model, firmware, configuration and operating context.
What remains uncertain
The questions the available evidence cannot answer.
Suggested investigation
A clear operational next step for the team.

Observability inputs

More data is not automatically better evidence

Observability considers whether evidence is available, recent, attributable and useful for the question being asked.

Coverage

Are the relevant capabilities available for the question being asked?

Freshness

Is the evidence recent enough to support the displayed conclusion?

Provenance

Can Sentinel identify the source, integration path, mapping, units, and applicable context?

Usefulness

Does the signal carry enough meaning, timing, and quality to contribute to the evaluation?

Corroboration

Is there sufficiently independent evidence to support or challenge the same conclusion?

Gaps and contradictions

Are missing, stale, unsupported, or conflicting inputs represented honestly?

Third-party assurance

A clearer view of what each integration can evidence

These levels describe verified evidence depth for third-party integrations. They do not rate electrical safety, product quality or standards compliance.

  1. 01

    Observed

    Baseline operational evidence is available through a verified integration, with known limitations made visible.

  2. 02

    Enhanced

    Additional verified signals or context extend the baseline view.

  3. 03

    Integrated

    A deeper supported integration provides documented mappings, provenance, and a broader evidence set.

  4. 04

    Confidence Ready

    A verified evidence interface supports the Sentinel Confidence framework.

FAQ

Sentinel Confidence questions

What is Sentinel Confidence?

Sentinel Confidence shows both what operational evidence suggests and how much credible evidence supports that view.

What is the difference between Health and Observability?

Health describes the operational conclusion supported by available evidence. Observability describes the coverage, freshness, provenance, and usefulness of the evidence available to support that conclusion.

Is Observability an electrical safety score?

No. It describes evidence available to a monitoring system. It does not certify electrical safety, replace device protection, or approve a charger for use.

Can a charger be healthy with low Observability?

The charger may be operating normally, but Sentinel should not present a strong health conclusion when evidence is insufficient. Low observability describes uncertainty in the view, not proof of a fault.

Does OCPP support guarantee full Observability?

No. Signal availability varies by OCPP version, implementation, model, firmware, configuration, and integration. Capabilities must be verified.

How does Sentinel handle missing or stale evidence?

Sentinel treats missing and stale evidence as explicit conditions so uncertainty remains visible in the operational view.

Is PlugStream Native the highest assurance level?

No. PlugStream Native is a separate native-device category, not a fifth rung in the third-party assurance ladder.

Find out what your estate can actually evidence

Start with the chargers, integrations, and signals already in your estate. We will help you map what is visible, where evidence is limited, and which questions need a better data source.