Typical sequence

Getting Started

The usual path from scoped review to continuous monitoring when it is actually needed.

Start with Verify

For most teams, the first step is a defined review of one asset or site so everyone is working from the same baseline.

Best for: first engagement

Add monitoring only if justified

Horizon is usually considered only after the baseline is clear and the operating case is strong enough to support continuous coverage.

Best for: monitored fleets or restricted operating environments
1

Verify Review

Start with one site, one dataset, and a defined question set.

  1. Confirm fit: We review the asset type and available data.
  2. Submit data: We provide the secure path for the agreed review scope.
  3. Run the review: Typical turnaround is five business days from clean receipt.
  4. Decide next step: Use the report to close the issue, monitor internally, or consider a larger deployment.
Typical use: baseline, diligence, or issue clarification
2

Expansion Paths

If the review shows a persistent operating need, the next step is to scope monitoring around the site rather than force a larger rollout.

  1. Horizon: For BESS operators who need ongoing monitoring and a deployment model shaped around the site.
  2. Choose the right boundary: Managed, on-premise, or isolated deployment is decided from the site requirements rather than sold as a separate front-door product.
  3. Expand carefully: Roll out site by site only when the evidence supports it.