Scope a deployment that connects your own network, telemetry, and commercial systems, and reads them beside the live public market — with your internal state and public evidence kept clearly apart.
Historians, GIS, and commercial platforms scoped source by source, inside a boundary you define.
Your topology, telemetry, and work state carried into modeled map, network, and Radar surfaces.
Private state and live public evidence on one board, each source and timestamp kept labeled.
The current prototype demonstrates a synthetic distribution feeder across map, network, and Radar. A deployment adds the validated source boundary and governed data access required for your systems. The grid agent stays beside every surface.
A deployment can place topology, assets, telemetry, and work state on the same geographic surface as the public market.
Grid agent on this surface
The prototype carries the selected asset, geographic focus, and modeled cursor into the question.
A modeled feeder, redrawn as a one-line: source, switches, and downstream share, laid out automatically from topology rather than hand-drawn.
Grid agent on this surface
Carry the selected branch, switch state, and topology context into an illustrative investigation.
Bring private operating signals and public context onto one board, keeping each source and timestamp explicit when their clocks differ.
Grid agent on this surface
Ask from the operating frame while private and public sources remain separately labeled.
Connection patterns are designed and validated source by source: identity, freshness, permissions, and operational ownership are part of the engagement.
Operational historians
Network & GIS
Commercial
Custom connectors
Operational historians
Scope telemetry, availability, and asset state from a PI System.
Network & GIS
Scope topology, conductors, switches, substations, and service territory.
Commercial
Scope positions, awards, schedules, settlements, and portfolio context.
Custom connectors
SCADA, EMS/ADMS, trade capture, and internal databases via scoped connectors.
Named systems illustrate common source classes; connector availability is confirmed during scoping. Public feeds remain source-attributed and separate from private state.
A Private Grid is designed as more than a view. Connectors, models, and recurring analyses are defined around the deployment boundary, the systems of record, and the review path your team requires.
Scope how private feeds enter the deployment boundary, how credentials are held, and how freshness and ownership are validated.
Define asset studies or storage programs around your existing models, private inputs, and the live public market.
Recurring reconstructions, checks, and reports can be designed as scoped private workloads with reviewable outputs.
Scoped
Boundary
Defined per deployment
Scope
Example BESS fleet
Inputs
Proposed telemetry + market
Output
Reviewable variance
Delivery pattern
Deployment-scoped
The agreed design keeps private inputs inside the deployment boundary while public market evidence remains attributed and independently inspectable.
Define where private data is processed, stored, and separated from public market evidence.
Scope identity-provider, role, and asset-access requirements with the deployment.
Keep source credentials inside the agreed boundary, with ownership and rotation made explicit.
Set retention, residency, and operating controls around the organization's requirements.
A scoped engagement, not a self-serve toggle — most first deployments start with one market, a small private-data boundary, and one decision that matters.
Scope how service territory, DER, and outage context should sit beside the wholesale market your load and generation clear into.
See the solution02Define how fleet telemetry and dispatch should be reviewed against the prices, constraints, and weather that shaped the opportunity.
See the solution03Scope the private positions, schedules, or settlement context that should be reviewed beside the live nodal market.
See the solutionTell us the market, the systems you'd connect, and the decision you're trying to support. We scope the deployment before we quote it — these are operating systems, not seats.