RC8.4 synthetic rebuildRaw source protectedUtility Intelligence Bridge · Dual Story Cockpit

Two guided stories. One field-to-cash workbench for utility contractors.

RC8.4 keeps the operational field-claims proof and restores the polished Cockpit Classic story as a second narrative path. Both stories lead to the same controlled source chain: model, quantity, schedule, cost, actuals, claims, payment, cash, and executive action.

Choose Story Path Open Live Cockpit Compare RC8.3

Cockpit Classic · Section & Spine

Trench logic becomes operating logic

Surface restoration

Public-facing work zone and restoration exposure.

Backfill

Production quantity, compaction basis, schedule driver.

Pipe + bedding

Core installed asset, quantity basis, cost-code anchor.

Trench support

Safety, support, productivity, and risk envelope.

Datum / station spine

The review line tying model, activity, claim, and cash together.

This is a rebuilt diagram concept. It does not include source geometry, GIS coordinates, private styles, protected formulas, or raw source code from the attached HTML.

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 sealed design, survey control, agency approval, legal advice, or payment certification.
Not an iframe around the private single-file app.
Not live ERP, BIM, GIS, accounting, schedule, or document-control write-back.

RC8.4 Startup Selector

Choose the narrative path

The attached version’s strongest addition is a dual-story front door. Field Claims proves the operating loop; Cockpit Classic explains the model-to-controls vision.

Story 1 · Operational proof

Field completion -> actual cost -> claim/payment lag -> executive action

The contractor operating story: model geometry becomes field reports, actual cost records, earned value, claims, approvals, retainage, payment lag, and action gates.

Open Field Claims Story

Story 2 · Cockpit classic

One parametric model. Six disciplines. One source of truth.

The restored Cockpit Classic story: Section & Spine visual identity, discipline dialects, live engine preview, synthesis pipeline, and launch bay language.

Open Cockpit Story

Progression

RC8.4 extends the field-claims route without replacing it

The public site now has a comparison path: RC8.3 for the direct field-to-cash command workbench and RC8.4 for the dual-story cockpit wrapper around the same operating proof.

RC8.3

Field Claims Hardened

Made the field-to-cash loop explicit: actuals, cost records, claims, approvals, retainage, payment lag, cash exposure, and executive action.

RC8.4

Dual Story Cockpit

Adds a startup selector so the audience can choose between operational proof and the polished Cockpit Classic narrative.

Public route

Sanitized website layer

Publishes the narrative structure and synthetic workbench behavior without raw HTML, exact coordinates, private formulas, or source records.

Story 1 · Operational Proof

Field completion becomes earned value; approved work becomes cash exposure

This path is built for contractor leadership: show how the same source record moves from installed quantity to actual cost, claim, approval, payment lag, cash, and action.

Model

Quantity

Cost code

Schedule

Actuals

Earned value

Claim

Payment

Cash

Action

Story 2 · Cockpit Classic

Section & Spine turns the model into six professional dialects

This story restores the strongest Cockpit Classic idea from RC8.4: the visual identity comes from utility construction itself, while the same source model feeds every discipline.

01 · The Spine

Visual identity from the trench

Sub-grade section, datum, station chainage, gravity profile, bedding, pipe, backfill, and brass survey accents create a subject-specific story instead of a generic dashboard.

02 · Live Engine

Numbers are not decorative

The cockpit reads the active estimate logic: cost basis, revenue/SOV, duration, labor hours, L/M/C/S/E split, top cost codes, and risk envelope.

03 · Six Dialects

One truth, six professional readings

BIM, QTO, project controls, field, commercial/claims, standards/QA, and executives receive the same source model in their working language.

04 · Launch Bay

Story becomes operation

Narrative buttons launch model, schedule/cashflow, actuals/claims, standards lens, control room, and capture-ready executive views.

Synthesis Pipeline

From classic story to hardened operating proof

The dual-story version is not just a different opening screen. It adds a disciplined path for explaining, stress-testing, and hardening the public/private bridge.

Source model

A generic utility corridor object anchors geometry, quantities, activities, and record custody.

Edge cases

Stress-test quantities, cost codes, scenarios, payment timing, and public-safe boundaries.

Spatial design

Refine 3D/4D/GIS language without publishing raw coordinates, map dependencies, or private source context.

Field realism

Pressure-check productivity, crew logic, actuals, claims, approval status, and payment lag.

QA hardening

Verify route hooks, scenario buttons, sample exports, disclaimers, and no-regression checks.

Launch Bay

Both stories launch the same controlled workbench

The public route keeps the RC8.4 launch behavior as website navigation: every action goes to a reviewable, synthetic route section.

Live cockpit

Run scenario, ground, and water-table choices against synthetic cost and schedule signals.

Launch

Actuals & Claims

Load the payment-lag posture and trace field completion through claims, approval, and cash receipt.

Launch

Control room

Read current condition, consequence, action owner, and forecast confidence from one source chain.

Launch

Program catalog

Review the source-to-public migration rule and the no-raw-HTML publication boundary.

Launch

Live Cockpit

Run the synthetic RC8 operating proof

Use the same public-safe workbench as the RC8.3 field-claims page. The difference is the RC8.4 narrative wrapper: choose the operational proof or Cockpit Classic path, then land on the same source chain.

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.

Discipline Translation

The dual-story cockpit still speaks to every owner

The Cockpit Classic story explains the vision; the Field Claims story proves the operational chain. Both are useful only if every discipline can read the same source truth.

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?

Capability Map

RC8.4 is a story selector, not a data fork

Each capability still maps to the same source custody chain. The selector changes how the room enters the demo, not which truth the system uses.

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.

Publication QA

What changed for RC8.4 and what stayed private

These checks are visible because the public page must prove the boundary as clearly as it proves the product story.

Raw RC8.4 HTML is not embedded, iframe-wrapped, copied, or shipped.

Exact source coordinates, agency/project identifiers, and private GIS context are excluded.

All visible metrics are deterministic representative indices, not payment certification.

No live ERP, schedule, BIM, GIS, accounting, or document-control write-back is claimed.

Related Proof

Compare the utility progression

The proof cards let reviewers compare the broader Utility Bridge, the RC8.3 Field Claims workbench, and the RC8.4 Dual Story cockpit.

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

Synthetic liveContractor controls

Utility Field Claims Command Workbench

A public-safe RC8.3 rebuild for utility contractors: one source model feeding quantity, cost code, schedule, actuals, claims, payment lag, cashflow exposure, and executive action.

Synthetic utility corridorField completion recordsActual cost records

The live page is a sanitized native rebuild with deterministic sample records. It does not publish raw RC8.3 HTML, private GIS context, agency identifiers, protected formulas, or live system write-back.

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

Private Pilot Gate

Use RC8.4 when the room needs both the executive story and the field-to-cash proof.

The right pilot starts with approved source structures, representative mappings, explicit review gates, and no silent overwrite of systems of record.

Request a Utility Contractor Pilot Compare RC8.3 Utility Bridge

Synthetic dataNative routeReview gatesNo payment certification