Recurring intelligence layer

Your site decision should not go stale the day the report is delivered.

ORBIT Portfolio Monitor keeps a governed watch on the evidence behind large-load infrastructure decisions. When a permit, utility milestone, water allocation, wastewater limit, tariff, schedule assumption or linked source changes, ORBIT creates a traceable change signal tied back to the affected site, constraint and prediction history.

Why recurring monitoring exists

The constraint map changes after the screen.

Large-load projects move through utility studies, permit actions, design changes, construction sequencing and operating evidence. A decision that was defensible three months ago can become stale when one dependency moves.

Official sourcepermit, utility, tariff, capacity or operating evidence
Change eventnew, changed, superseded, expired or contradicted
Portfolio signalwhich monitored site and decision is affected
Human reviewacknowledge, dismiss, require action or resolve
Decision versionpreserve what changed and why
System of record behavior

Changes are events. Decisions become versions. Neither is silently rewritten.

ORBIT's monitoring architecture is designed to preserve an auditable history. A source change creates a new event. The resulting alert is append-only. Human review is recorded separately. If the recommendation changes, Decision Memory creates a new version linked to the evidence that triggered review while the prior version remains inspectable.

Portfolio-scoped

One customer can maintain multiple sites and multiple monitored decision scopes under one portfolio.

Evidence-linked

Alerts inherit the official source and affected Atlas or Prediction Ledger references so the reason for a re-screen remains inspectable.

Versioned decisions

Decision Memory preserves the recommendation, rationale, effective date, linked alerts and evidence snapshot of each version.

Annual ORBIT

From one-time screen to recurring decision intelligence.

The commercial path is designed around a bounded diagnostic first, then recurring monitoring only where the customer has a live reason to keep the decision current.

1 · Initial screen

Establish the cross-resource baseline, evidence register, constraint map and testable predictions.

2 · Monitoring scope

Select the sites, jurisdictions, evidence domains and open predictions whose changes can affect the decision.

3 · Change-driven decision versioning

When material evidence changes, review the signal, determine whether the decision basis moved, and preserve the new recommendation as another version rather than rewriting the prior record.

Explore Decision Memory →
What compounds

Decision history becomes an operating asset.

Switching cost

The customer accumulates site evidence, decision versions, predictions, source changes and verified outcomes in one governed history.

Calibration data

Changes and outcomes can later show which assumptions were stable, which constraints moved, and which predictions were well calibrated.

Portfolio intelligence

Repeated patterns across sites can reveal which jurisdictions, resource domains and project phases most often create schedule or capacity risk.

Commercial scope

Annual / Portfolio ORBIT

Pricing depends on site count, monitored domains, source complexity, update cadence, integrations and professional-review requirements. The product is intended to replace stale one-off decision files with a continuously governed evidence and decision record.