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.
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.
Verify Review
Start with one site, one dataset, and a defined question set.
- Confirm fit: We review the asset type and available data.
- Submit data: We provide the secure path for the agreed review scope.
- Run the review: Typical turnaround is five business days from clean receipt.
- Decide next step: Use the report to close the issue, monitor internally, or consider a larger deployment.
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.
- Horizon: For BESS operators who need ongoing monitoring and a deployment model shaped around the site.
- 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.
- Expand carefully: Roll out site by site only when the evidence supports it.
Scope first
Defined review scope
Boundary, telemetry window, and mandate question are pinned down before conclusions move.
Encrypted handling
Protected review workflow
Review traffic and operating data are handled with encrypted transfer and controlled access.
Customer boundary
Customer-controlled deployment
Managed, private, and isolated deployment paths are available when the environment requires them.
Direct accountability
Principal sign-off
Technical accountability stays close to the method rather than disappearing into a generic workflow.