Synthetic live rebuildRC8.3 source protectedUtility Intelligence Bridge · Executive Field Claims

One parametric model. Six disciplines. One source of truth for utility contractors.

Artemis turns a utility corridor into an operating language for contractors: geometry becomes quantity, quantity becomes schedule, cost, labor, and cash, field completion becomes earned value, and approved work becomes claims, payment exposure, and executive action.

Open Live Workbench Contractor Pathway Compare RC8.4 Catalog Entry

Animated Source-Model Feed

One source object

Synthetic utility object

Pipe run · trench · manhole set · restoration zone

Data custody packet

Same source object, translated without losing the review trail.

01 · BIM / 3D

Geometry, stationing, trench, pipe, structures, and selectable work objects.

02 · QTO

LF, CY, SY, tons, structures, restoration, bedding, concrete, and support.

03 · Cost codes

Labor, material, equipment, subcontract, indirect, and review-coded budgets.

04 · EVM / forecast

PV, EV, AC, CPI, SPI, EAC, variance, and forecast-method confidence.

05 · Field actuals

Daily quantities, crew hours, equipment, weather, inspections, and notes.

06 · Executive / standards

Assumption basis, reconciliation, cashflow signal, risk, and action register.

The motion means custody, not decoration: geometry becomes quantity; quantity becomes schedule, cost, actuals, earned value, claim, payment, cash, and action.

Model corridor

Synthetic utility corridor

Stationed pipe, trench, structures, restoration, and access zones.

Bid / SOV basis

Index 100

Representative value index only; not payment certification.

Construction duration

410-day baseline

Demo sequence for work-package review and executive action.

Control data mode

Browser-local

Deterministic sample records, no external systems or API keys.

Public/private gate

Sanitized rebuild

No raw HTML, GIS coordinates, agency labels, or private records.

What it is not

Not a publication of the private RC8.3 HTML, GIS context, coordinates, or source paths.
Not live ERP, schedule, BIM, GIS, accounting, or document-control write-back.
Not an unmanaged bot that changes systems of record without review gates.

Progression

From public narrative to field-claims command workbench

This page highlights the RC8.3 utility demo as the next step in the Artemis progression: the public site keeps the raw source private while exposing the extended functionality as a sanitized, native route.

App shell v0.1

Foundation

Reusable Artemis navigation, proof cards, and executive page language.

Established public-safe presentation discipline before deeper workbench exposure.

Construction workbench

Synthetic live pattern

KPI panels, forecast comparison, risk register, controls matrix, and audit notes.

Proved the public route could show project controls without raw private records.

Utility bridge narrative

Model-to-money story

Utility work-package chain from geometry and quantities to commercial exposure.

Separated public narrative from private GIS, HTML, and agency-specific logic.

RC8.3 field claims hardening

Extended contractor demo

Actuals, claims, retainage, payment lag, cash timing, and executive action.

Turns the utility demo into a field-to-cash command workbench for contractors.

Source-Model Feed

The chain of custody is the product

The contractor value is not a prettier model. The value is knowing how one utility object changes quantity, code, schedule, actuals, earned value, claim approval, payment lag, cash, and action.

Model

Quantity

Cost code

Schedule

Actuals

Earned value

Claim

Payment

Cash

Action

Launch Bay

A controlled demo path for contractor executives

The route follows the RC8.3 demonstration order while keeping everything public-safe and deterministic.

Explore the model feed

See one source object translated into operating disciplines.

Jump to section

Run sample actuals

Switch field performance, cost, schedule, and payment modes.

Jump to section

Run claim/payment lag

Trace field quantity through claim approval and cash receipt.

Jump to section

Open control room

Review current condition, consequence, owner, and next action.

Jump to section

Live Application Shell

Run the field-claims scenario without private data

The workbench demonstrates scenario recomputation and record reconciliation through synthetic, source-tagged sample records. It shows the operating shape of a private pilot without claiming live enterprise integration.

Cockpit Decision Deck

Scenario controls for contractor review

Change the mode, ground condition, or water table. The sample bridge recomputes cost basis, schedule duration, labor hours, earned-value signals, and claim-to-cash exposure from deterministic representative records.

Actuals & claims mode

Ground

Water table

Real-Deal Detection Layer

Payment Lag / Claim Risk

Cash timing watch

Bottleneck

Approved work and cash are not moving at the same speed as earned field value.

Executive action

Separate entitlement, approval, retainage, and payment timing this period.

Operating truth

The project may be producing value while approval and payment timing starve cash.

Cost basis

Index 108

P50 exposure +10; P80 exposure +25.

Revenue / SOV

Index 113

Representative SOV index only; no payment certification.

Schedule duration

429 days

CPI 1.01 · SPI 1.00.

Labor hours

30,350

Soil ground · Wet water table.

L/M/C/S/E Composition

Cost-code concentration

Labor34%

Material28%

Equipment17%

Subcontract14%

Indirect11%

ERP / CMiC-Style Codes

Top exposure locations

U-310

Pipe installation

Concentration32%

U-220

Trench support

Concentration19%

U-255

Dewatering

Concentration20%

U-610

Surface restoration

Concentration12%

Actuals & Claims Studio

Field report to claim approval to cash receipt

These are source-tagged representative records. They show the custody chain a contractor needs to keep visible before field completion, entitlement, approval, retainage, and cash timing get mixed together.

Field completion

81%

Accepted representative quantity for the review period.

FR-SYN-108 · stationed segment sample · source-tagged

Claim / approval

79% / 66%

Claimed quantity compared with approved quantity.

CL-SYN-022 · pay-item sample · retainage 10%

Cash receipt

44%

Payment lag sample: 38 days.

PMT-SYN-019 · demo payment state · not certification

Field quantity vs claim quantity

Claimed quantity stays tied to accepted field quantity before approval review.

Approved quantity vs cash received

Approval is ahead of payment; cash timing needs executive action.

Actuals freshness

Sample actuals are current for the representative review period.

Executive Control Room

Current condition, consequence, and owner

Earned field value81%

Claimed quantity79%

Approved quantity66%

Cash received44%

Action Register

Who owns the next move?

Owner: Contract admin + finance
Action: Separate entitlement, approval, retainage, and payment timing this period.
Forecast note: Scenario recomputes from representative source-tagged sample records.
Exposure range: P50 +10 · P80 +25 index points.

Capability Matrix

One bridge, six contractor disciplines

Each discipline keeps its own professional dialect, but Artemis keeps the source chain connected so leadership can find the governing constraint.

Estimating

Did the quantity or production basis move?

Cost-code concentration, unit-rate pressure, and bid-to-forecast movement.

Field operations

What is the governing constraint?

Access, crew, equipment, inspection, weather, rework, or sequence owner.

Project controls

Is the schedule and earned-value story current?

PV / EV / AC relationship, CPI/SPI signal, EAC trend, and freshness warning.

Contract administration

Does claimed work reconcile to accepted field quantity?

Claim quantity, approved quantity, retainage, payment status, and support gap.

Finance

Is the project earning value but waiting on cash?

Approval lag, payment lag, net-due signal, retainage exposure, and cash action.

Executive leadership

What changed and who owns the next move?

Operating condition, consequence, confidence, owner, deadline, and action register.

Role Translation

The same truth in the language each team uses

Artemis should not flatten contractor work into one generic dashboard. The workbench translates the same source object into field, estimating, controls, contract, finance, and executive language.

Superintendent

Production, blockers, crews, weather, access, and inspections.

What field condition is driving the forecast and claim posture?

Estimator

LF, CY, structures, unit rates, labor hours, and productivity factors.

Which quantity or production assumption changed the cost basis?

Project manager

Schedule movement, change exposure, owner decisions, and action owners.

Which issue needs intervention before it becomes a permanent variance?

Contract administrator

Pay items, claimed quantity, approved quantity, retainage, and backup.

Which claim line lacks the field support or approval state needed for cash?

CFO / executive

Earned value, approved work, payment lag, net due, and cash timing.

Is the project operationally healthy but commercially starved for cash?

Schema Bridge

Minimum path from demo to private pilot

The public page names the source structures without publishing private records. A private implementation can map these fields to approved schedule, ERP, field, BIM, GIS, and document-control interfaces.

Field completion reports

report idreport datework day / shiftweathercrew / foremanactivity codesegment / station rangecompleted quantity / unitrework percentinspection statusinspector notesource

Actual cost records

cost record idcost dateactivity codesegmentcost categoryquantity / unithours / rateamount indexvendor or crewsource documentsource

Claim / payment records

claim idperiod start / endclaim datepay itemactivity codeclaimed quantityapproved quantitybilling unit rate indexretainagenet-due signalpayment status / dateowner notesource

RC8.3 QA / Regression Status

Public release checks for the sanitized rebuild

The strongest demo is useful only if the public boundary is clean. These checks are visible so the contractor audience understands what is proven and what remains private-pilot scope.

Pass

Raw-source boundary

The public route is rebuilt from sanitized narrative and TypeScript data only.

Pass

Sample-data posture

All records are deterministic, representative, source-tagged samples.

Pass

System-of-record gate

The page describes approved interfaces and review gates, not silent write-back.

Pass

Contract limitation

Visible copy says this is not payment certification, agency approval, or legal advice.

Related Proof

Where this demo sits in Artemis

The field-claims route extends the existing Utility Intelligence Bridge, the reusable workbench shell, and the forecast exposure control pattern.

Synthetic liveRC8.4 progression

Utility Dual Story Cockpit

A public-safe RC8.4 route for utility contractors with two guided narratives: Field Claims operational proof and Cockpit Classic Section & Spine.

Dual-story selectorSection & Spine narrativeField claims proof

The public page is a native sanitized rebuild. Raw RC8.4 HTML, exact corridor/GIS context, agency/project identifiers, protected formulas, and private records remain unpublished.

Open proof page

Public narrativeInfrastructure proof

Utility Intelligence Bridge

A public-safe executive story for utility and heavy-civil programs: model context, field production, cost exposure, and forecast logic in one bridge.

Design packagesUtility geometryField production

This public page is narrative only. Real program workbenches stay private until rebuilt with synthetic or approved data.

Open proof page

Synthetic liveReusable system

Artemis Workbench Shell

The reusable Artemis workbench pattern: executive KPIs, source-labeled assumptions, forecast comparisons, registers, and CTA surfaces.

KPI panelsForecast chartRisk register

The live workbench uses synthetic sample data only and does not include raw private demos.

Open proof page

Private Pilot Gate

Start with one utility scope, one forecast period, and one claims review.

Artemis should read approved project structures, reconcile source-tagged records, propose reviewed outputs, and write back only through explicit review gates.

Request a Utility Contractor Pilot Back to Utility Bridge Proof Library

Approved interfaces onlySynthetic public dataHuman review gate