Sequence Enterprise EVM needs a baseline-change ledger

Freeze the measurement contract for each period

Octave's official page presents Sequence Enterprise, formerly EcoSys, across project controls and project management, planning, scheduling, estimating, earned value, budgeting, forecasting, and portfolio work. Those statements establish documented product scope. They do not establish that a buyer's work breakdown, budgets, schedule, progress rules, actual costs, or performance measures are complete or contractually authoritative. Before reading a variance, the project team needs an approved measurement contract for the reporting period.

Record the project and control-account hierarchy, work packages, scope version, performance-measurement baseline, budget basis, schedule baseline, calendars, data date, planned-value time phasing, earned-value technique, percent-complete rule, actual-cost source, accrual treatment, currency and accounting period, responsible manager, and approval time. Preserve the units and cutoffs used to derive planned value, earned value, and actual cost. A dashboard date alone cannot show that the three measures refer to the same scope and period.

Keep approved change separate from measured performance

A baseline can change for authorized scope, budget, schedule, replanning, correction, or other governed reasons. Each change needs an identifier, origin, affected control accounts and activities, prior and proposed values, reason, commercial or governance status, approval authority, effective reporting period, and links to the supporting project records. Pending exposure should remain visible without being silently incorporated into the approved baseline. Historical reported periods should not be rewritten merely to make current variance look smaller.

Use a baseline-change ledger that shows the sequence from proposal through approval and implementation. Reconcile the approved change to the schedule, cost system, contract or funding record, forecast, and reporting cube. When a correction addresses an error rather than authorized scope, label it accordingly and preserve both the erroneous and corrected calculation. Earned value can support control only when users can distinguish performance against an approved plan from a change to the plan itself.

Reconcile source systems before calculating variance

Project-controls platforms often connect schedule, cost, procurement, time, field, and finance records. The system boundary matters. Preserve source-system identifiers, extraction times, accounting periods, schedule versions, cost-code and work-breakdown mappings, currency conversions, late actuals, accruals, transfers, rejected records, and manual adjustments. A formula can be correct while its inputs describe different periods or scopes. A green performance indicator cannot resolve that mismatch.

For every published reporting period, retain a reproducible input snapshot and calculation version. Reconcile totals and exceptions back to the authoritative sources, and name which system owns schedule status, commitments, actual cost, approved budget, progress, and funding. Lock the period after approval under a defined reopening process. If a late invoice or corrected progress record arrives, show the effect as a traceable restatement or current-period adjustment under the organization's policy rather than overwriting prior evidence.

Test one change across two reporting periods

A buyer demonstration should establish an approved baseline, load schedule progress and actual costs for one period, and reproduce the planned, earned, actual, schedule-variance, and cost-variance values from exported evidence. Then introduce an unapproved scope change, an approved change effective next period, a late actual cost, a corrected progress quantity, and a mapping error. Inspect which values remain in the baseline, which appear only as exposure, how history is retained, and who can approve or reopen the period.

Contractor Systems Index reviewed the exact registered Hexagon EcoSys URL and its current official Octave destination on September 23, 2026. The page supports the stated product identity and project-controls, planning, earned-value, budgeting, and forecasting positioning. It does not disclose a buyer's configuration, source-system authority, baseline quality, earned-value method, change approvals, data completeness, calculation accuracy, contract effect, schedule or cost outcome, or implementation performance.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Contractor Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.