Utility Intelligence BridgeArtemis · RC8.4 Dual Story Hardened
RC8.4 startup story selector

Choose the narrative path

This version keeps the new field-to-cash / claim-payment story and restores the polished Cockpit v1 “Section & Spine” story as a second guided narrative. Both stories launch the same live RC8 engine.

East 10th Street · Avenue A to Avenue B · East Village

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

Artemis turns one representative sewer utility model into a shared operational language. Geometry becomes quantity; quantity becomes schedule and cost; field completion becomes earned value; approved work becomes cashflow and executive action.

Activities 15 Corridor 740 LF GIS context East Village Deployment single-file + fallback
DATUM EL. 100.00 0+00 1+00 2+00 3+00 4+00 5+00 6+00 7+00 8+00 9+00 10+00 PARAMETRIC 3D MODEL SOURCE BIM / 3D receives model geometry and constructible sequence.BIM / 3DGEOMETRY QTO reads the same geometry as quantities and takeoff drivers.QTOQUANTITIES Cost codes translate quantities into CMiC-style L/M/C/S/E cost structure.COST CODESCMIC EVM reads plan, earned value, actual cost, CPI, SPI, and forecast.EVMFORECAST Field actuals close the loop through daily quantities, crew hours, and actual costs.FIELDACTUALS DEP / Executive view reads standards, cash, risk, and action gates from the same source.DEP / EXECSTANDARDS A SECTION A–A · STA 5+00 PAVEMENT BACKFILL STONE BEDDING 36–48" RCP SUB-GRADE / INVERT SHEETING
Data spine / flowDiscipline station BackfillStone beddingRCP pipeAnimated packets show the source model feeding six disciplines →
New in RC8.2: the narrative hero now includes the animated source-model feed, showing BIM/3D, QTO, cost codes, EVM, field actuals, and DEP/executive standards all reading one parametric utility model.
Model corridor740 LF736 ft GIS alignment
Bid / SOV value$0live from estimate engine
Construction duration0 wdworking-day sequence
Control data modePlanCPI 1.00 · SPI 1.00
Public control gateControlledchecks remain live below
Cockpit Classic Story · Section & Spine

The original polished cockpit narrative, now inside the full RC8 engine

This second story preserves the strongest language and feel from the attached Cockpit v1 file: the trench-section visual identity, the data spine, the six-discipline bridge, the live estimate preview, and the human-in-the-loop AI synthesis story. It is a narrative layer only — the RC8 actuals/claims, QTO, EVM, GIS, and control engines remain the source of truth.

ESCR · SANDRESM1 · Reach K / East Village Utility Intelligence

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

The Bridge takes a single sub-grade utility model and lets every team read it in their own language: BIM sees geometry, project controls sees cost codes and earned value, field operations sees daily quantities, commercial sees claimed / approved / paid work, QA sees standards, and executives see decisions.

Change the model once; every discipline updates downstream. No re-keying, no parallel workbook drift, no story disconnected from the engine.

Disciplines 6Activities 15Corridor 740 LFMode live RC8
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 rather than a generic dashboard.

02 · Live Engine

Numbers are not decorative

The cockpit section reads the active RC8 estimate engine: 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 all receive the same source model in their own working language.

04 · Launch Bay

Story becomes operation

The narrative is the front door. Launch buttons open the actual model, GIS, schedule/cashflow, actuals/claims, DEP Standards Lens, control room, and capture studio.

01ArchitectureDefine model, schema, estimate logic, and single-file app structure.
02Edge casesStress-test quantities, cost codes, scenarios, and public-safe boundaries.
03Spatial designRefine 3D/4D/GIS logic and the trench-section visual language.
04Field realismPressure-check productivity, crew logic, actuals, claims, and payment lag.
05QA hardeningVerify syntax, DOM hooks, scenario buttons, exports, and no-regression checks.
RC8.4 dual-story rule: Cockpit Classic explains the vision; Field Claims proves the operating loop. Both point to the same live workbench.
Live capability · Cockpit v1 graft

The estimate engine, risk register, and CMiC bridge computing in the narrative

This section imports Cockpit v1’s best decision layer into RC8.2, but points it at the active RC8 geometry and estimate engine. Scenario, ground, and water-table selections update the underlying live application controls, then redraw the cost basis, SOV value, duration, labor hours, L/M/C/S/E split, top CMiC-style codes, and P50/P80 risk envelope.

Live RC8 engineCockpit decision deck · model-to-controls proofBASE · Soil · Dry
Cost basis—direct + indirect
Revenue / SOV—markup bridge
Schedule—working days
Labor hours—all activity crews

Cost composition · L / M / C / S / E

Monte Carlo · P50 / P80 risk envelope

Top CMiC-style cost codes by value

CodeActivityValue
Field loopDaily production can update EV and actual cost the same day.
Commercial loopApproved quantities, retainage, payment lag, and cash exposure remain connected.
QA loopDEP-style assumptions stay visible beside geometry, QTO, and controls.
The connected project-controls lifecycle

From sub-grade geometry to executive action

The narrative is not a separate marketing calculation. Each launch point opens the corresponding live RC8 engine, using the same geometry, quantities, schedule clock, cost categories, actuals, claims, and control checks.

01Model geometryPipe, trench, structures, stationing, and constructible envelopes.
02Quantity takeoffLF, CY, SF, SY, tons, structures, concrete, and restoration.
03Construction sequenceActivity register, moving fronts, Gantt, and playback day.
04Field completionDaily quantity, station, segment, inspection, and source record.
05Actual costLabor, material, consumable, subcontract, and equipment.
06Earned valuePV, EV, AC, CPI, SPI, EAC, and activity forecast.
07Payment applicationClaimed and approved measured quantity by pay item.
08Approval & retainageApproved amount, held retainage, pending backup, and disputes.
09Cashflow impactPaid net due, payment lag, funding need, and cash gap.
10Executive actionWarnings, ownership, reconciliation, and decision gates.
What the Bridge carries

Every capability mapped to the discipline that owns it

One model is translated into the professional dialect each team needs, while the controls remain connected across disciplines.

01 · MODEL / BIM

Geometry & clickable intelligence

BIM / VDC Coordinator

Inspect pipe, trench, manholes, catch basins, restoration, hierarchy, and linked construction activities.

Live proof: 740 LF · 4 segments
02 · PROJECT CONTROLS

Schedule, EVM & forecast

Project Controls Manager

Synchronize the activity register, Gantt sequence, PV/EV/AC curves, CPI/SPI, EAC, variance, and cash.

Live proof: 15 activities · 41 wd
03 · FIELD

Completion reports & actual cost

Field Engineer / Superintendent

Load deterministic sample scenarios or import source-tagged daily production and cost records.

Live proof: Plan mode · import ready
04 · COMMERCIAL

ERP, SOV, claims & cash

Commercial / Finance Team

Map L/M/C/S/E/R cost codes, payment applications, approvals, retainage, payment status, and cash gaps.

Live proof: CMiC-style bridge
05 · STANDARDS / QA

DEP Standards Lens & boundaries

Industry Expert / QA Reviewer

Trace representative sewer-standard assumptions into geometry, quantities, formulas, controls, and public-safe limitations.

Live proof: RCP · MH · CB · trench
06 · EXECUTIVE

Control Room & action register

Project Executive / PM

Read cost, production, cash, variance, risk, opportunity, reconciliation, and warnings beside the live model.

Live proof: live decision gate
Who reads the model

The same truth, in six professional dialects

The Bridge reduces re-keying and version drift by letting each role read a shared source through the controls they already understand.

BIM / VDC

“Show me what the object is.”

Geometry, hierarchy, stationing, quantities, selection, and linked activities.

Project Controls

“Show me when and at what performance.”

Activity windows, sequence logic, PV/EV/AC, CPI/SPI, forecast, and variance.

Field Operations

“Show me what was completed today.”

Segment, station, quantity, crew, weather, inspection, notes, and actual cost.

Commercial / Finance

“Show me what is earned, claimed, approved, and paid.”

SOV rates, payment applications, retainage, lag, and cash exposure.

DEP / QA Lens

“Show me the basis and the boundary.”

Representative standards logic, assumptions, checks, and limitations.

Executive Leadership

“Show me what needs action.”

Decision gate, warnings, ownership, risk, cash, forecast, and reconciliation.

Open the live systems

Launch bay

Move directly from the narrative into the operational proof point. The underlying RC8 actuals/claims, QTO, EVM, GIS, and cashflow engines remain the source of every live number.

Public-safe boundary: Representative demonstration only. Not sealed design, not survey control, not official agency approval, not payment certification, and not a substitute for contract reconciliation. Sample actuals and payment applications are clearly source-tagged demonstration records.
Artemis DEP Sewer Utility Intelligence Bridge RC8.4 Dual Story + Field Claims Hardened East Village GIS · Dual Story · Cockpit Classic · Guided Field Claims · Claims-to-Cashflow
PUBLIC
Artemis
DEP Sewer Standards Lens · RC8 · East Village GIS · 2026

Model Status

Trench depth—
Excavation—
Concrete—
Rebar—
Bid value—
Forecast margin—
Control assurance is evaluating live project data.
Question placement is active: click a visible model element · Esc cancels

Model Questions

Place a persistent question mark on the selected element or choose an exact visible model point.

Select an element or enter a question, then choose how to place it.
Coordination note only: model questions are local planning annotations, not formal RFIs, sealed design comments, agency direction, or contract records.
Segment detail view: closer chainage review with selected segment, compact UI, and preserved QTO/cost/schedule logic.
DEP Sewer Utility Standards LensSample RCP/VCP/manhole/catch-basin system · geometry-driven QTO · executive risk/cashflow bridge
Artemis DEP Sewer Executive Control Room
DEP Sewer Utility System / Standards · Field-to-ERP · Geometry-to-Cashflow · Risk/Opportunity · Variance · Dynamic Trends
Standards basis: representative DEP sewer sheet families for pipe, structures, bedding/cradle, trench, CB, MH and restoration logic.
Executive lens: standard-driven quantities flow into ERP codes, schedule, cashflow, variance, risk and opportunity trends.

Cash Flow

Cost Variance

Production Trend

Risk / Opportunity

Forecast Range

DEP standards → App: pipe families, manholes, catch basins, bedding/cradle, trench support, restoration.
Field → App: production, labor, equipment, material, subcontract, notes.
App ↔ ERP: cost codes, L/M/C/S/E/R, SOV and quantity completion support.
App → Executives: cashflow, variance, forecast margin, risk/opportunity exposure.
Dynamic controls: scenario simulation, randomized trends, no-regression handoff.
Representative demonstration only. Not sealed design, not survey control, not official agency approval, not payment certification, and not a substitute for contract reconciliation.

RC7 Publication Capture Studio

Eight guided capture presets for LinkedIn, printable storytelling, model-canvas export, and the narrated app demo.

Current capture message
Hero
Open a preset to stage the app for a polished LinkedIn capture.
Full-app capture: use the staged preset with the browser or operating-system screenshot command. Canvas PNG exports the live 3D model only; browser security prevents a dependency-free full-DOM screenshot in this single-file build.
Artemis DEP Sewer Utility Intelligence BridgeScreenshot ModeRepresentative demonstration only. Not sealed design, survey control, agency approval, or payment certification.
RC7 Video Demo Autopilot00:00 elapsed · 01:00 remaining
Artemis DEP Sewer Utility Intelligence Bridge

Press Demo to auto-walk through the screenshot deck while the model, executive charts, and captions tell the 60-second story.

Legend
Excavation  Sheeting
Bedding  Cradle  Pipe
Manhole  Catch basin  House conn
Backfill  Pavement  Selection / active front
Day 1 / —
—

Selected Element

—
Total Sewer System
Click an element · double-click = parent group · triple-click = grandparent

Quantities — Est / Actual / Projected

Cost & Billing — Est / Actual / Projected

Clickable Element Intelligence

Select a model element to see linked construction activities, schedule windows, completion, and control actions.

Model Hierarchy

Keyboard

↑Parent group ↓First child / detail ← →Cycle siblings EscClear selection SpacePlay / pause simulation , .Step −1 / +1 day [ ]Speed down / up RToggle reverse POpen DEP Standards Lens QOpen Model Questions 1 2 3Iso / Profile / Plan camera
Dashboard
Controls & Alerts
DEP Standards Lens
ERP Cost Codes
Crosstab
Schedule & Cashflow
EVM & Forecast
Actuals & Claims
Risk
Formulas & Exports
Satellite / GIS
Presentation Guide
Offline QA / Fallback
Handoff / Regression
The Section & The Spine

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

Representative East Village sewer geometry stays connected to quantity, schedule, field production, ERP cost, payment applications, cashflow, and executive action.

01Geometry & GIS
02QTO & Schedule
03Field & Actual Cost
04Claim & Approval
05Cash & Action

Quantity takeoff

Current decision gate
EVALUATING
Cross-checking schedule, cost, cash, geometry, field data, risk, and governance controls.

Independent checks and balances

Control discipline: acknowledgement records that a condition has been reviewed; it does not clear the condition. Decision gates change only when live project data resolves the underlying exception. Thresholds are demonstration controls and require project-specific governance before production use.

DEP Sewer Utility Standards Lens

Purpose: make this public demo unmistakably about a realistic sewer utility system. Artemis is using representative DEP-style sewer standard families as the sample domain, then showing how standard-driven geometry can feed quantity takeoff, ERP cost codes, field production, schedule, cashflow, variance, risk, opportunity, and executive reporting.

Pipe families
RCP · VCP · HE-RCP
Pipe family and size selections drive outside envelope, trench geometry, bedding/cradle/encasement factors, LF quantities, and cost-code mapping.
Structures
Manholes · Catch Basins
Manhole and catch-basin families define structure count, excavation allowances, concrete, risers, leads, and inspection/sequence logic.
Pipe zone
Bedding · Cradle · Encasement
The demo treats pipe-zone assumptions as geometry drivers so users can trace how standard details become QTO and cost categories.
Open cut / support
Trench · Sheeting · OSHA
Depth, width, soil, groundwater, support system, and open-trench buffer drive excavation, sheeting, disposal, production, and risk signals.
Restoration
Backfill · Pavement · Surface
Backfill, pavement area, asphalt tonnage, and restoration quantities connect the utility model to completion and billing templates.
Commercial bridge
QTO → ERP → Cashflow
Standard-driven quantities become L/M/C/S/E/R cost-code rows, SOV support, production curves, cashflow, variance and forecast signals.

Standards-to-controls flow

1. Standards basisRepresentative DEP sewer details define pipe/structure families, pipe-zone logic, excavation/restoration assumptions and QA boundaries.
2. GeometryThe model converts selected utility standards into station-based 3D geometry: pipe, trench, MH, CB, leads, backfill and pavement.
3. QuantityGeometry drives LF, CY, SF, SY, TON, EA and structure quantities with formula audit visibility.
4. ERP bridgeQuantities are organized into labor, material, consumable, subcontract, equipment and revenue/billing categories.
5. Field bridgeDaily production and actual cost records update earned value, productivity, billing progress and project forecast signals.
6. Executive lensCashflow, variance, risk, opportunity and forecast range move with the same construction simulation and quantity logic.

DEP sewer utility demo boundaries

ItemPublic demo treatmentReason
DEP standardsRepresentative standard-family logic, not official design approval.Shows method without implying agency certification.
GeometryParametric and quantity-driven; not survey control or sealed design.Good for demonstration, estimation logic and workflow design.
QuantitiesDerived from model assumptions and visible formulas.Useful for QTO/SOV templates, subject to contract reconciliation.
ERP / CMiC bridgeDemonstrates L/M/C/S/E/R mapping and exports.Shows how field/project models can communicate with ERP structures.
Risk / opportunityScenario and randomized trend simulation.Executive visibility; not a replacement for project controls judgment.
Public-safe disclaimer: Representative demonstration only. Not sealed design, not survey control, not official agency approval, not payment certification, and not a substitute for contract reconciliation.

Category roll-up

Schedule of Values — billing unit prices

Cumulative curves sampled at period ends

DEP-Style Open-Cut Construction Sequence

Activity register, Gantt storytelling, construction-front playback, and cash/EVM status stay synchronized to the same working-day clock.

Planned activity window Complete through selected day Playback day Click any bar to inspect its activity and linked model element.

Activity register — construction, controls, and element links

Activity forecast (EAC / ETC / TCPI)

Actuals & Claims Demo Studio

Field production to approved cash

Trace the East Village model through daily completion, actual cost, earned value, payment application, approval, retainage, payment lag, and executive control response.

Plan-based demo activeLoad sample actuals to activate CPI/SPI and claim/payment analytics.
RC8.4 guided path: select a scenario, review field reports, actual cost, claims/payment, reconciliation, and the control register. Demo records remain representative only; they are not payment certification or agency approval.
Representative demonstration dataSample field completion reportsSample actuals Sample payment applicationNot payment certificationNot official agency approvalNot contract reconciliation
Legacy field-actual record editor and compatibility import

East Village Demonstration Corridor

East 10th Street from Avenue A to Avenue B, directly across from Tompkins Square Park. OpenStreetMap provides recognizable, token-free street and landmark context while the Artemis model remains the independent source for demonstration geometry, quantities, controls, schedule, and cashflow.

East VillageManhattan context
E 10 StAvenue A to Avenue B
~735 ftCoordinate distance
OpenStreetMapRecommended basemap
Evaluating geospatial alignment...
The map layer is optional. Use OpenStreetMap, enter a separate provider/token, or use the schematic alignment fallback.
Demo sewer alignmentStartManholeCatch basinEnd

Real-world context controls

Safe architecture: the basemap is a geospatial presentation layer, not a model dependency. The 3D model, QTO, cost codes, field log, schedule, cashflow, and project controls continue to run if Leaflet, tiles, or internet access are unavailable.
LayerPurposeRegression guard
3D modelGeometry/QTO/selectionNever depends on satellite tiles
OpenStreetMapEast Village streets and landmarksDefault Leaflet layer with attribution
AlignmentStationed start/end, MH, and CB contextFallback schematic if map fails
GeoJSON exportLine and demonstration asset pointsSeparate, labeled contextual export

Demonstration talking points

  • Orient the audience at East 10th Street beside Tompkins Square Park.
  • Show the same coordinate alignment in the map overlay, GIS tab, 3D model, stationing, and GeoJSON export.
  • Use manhole and catch-basin markers to connect real-world context to clickable model intelligence.
  • Explain that street context improves communication but does not certify utility location, survey control, or design.
  • Export GeoJSON for a QGIS handoff demonstration, then reconcile against authoritative project records.

What it is

An Artemis Field-to-ERP and Geometry-to-Cashflow demonstration system showing how controlled construction geometry can connect field production, quantities, cost codes, ERP-style structures, schedule, EVM, cashflow, risk, opportunity, variance, and executive decision support.

What it is not

Not sealed design, not survey control, not official agency approval, not a BIM replacement, not payment certification, and not an automatic pay estimate without contract reconciliation.

Best demo flow

  • Open with DEP Standards Lens, then Executive Control Room.
  • Fit model and show labels.
  • Select a pipe, manhole, trench, or restoration family.
  • Show QTO → cost codes → schedule → cashflow.
  • Finish with Geometry QA and known assumptions.

Benefits

  • Connects design geometry to cost and revenue.
  • Turns field logs into EVM signals.
  • Makes CMiC-style L/M/C/S/E/R coding visible.
  • Supports executive presentation and estimator review.

LinkedIn message

Artemis builds custom AI-assisted intelligence bridges between real operations and management systems. This construction demonstration shows how field reality, geometry, quantity, ERP logic, cashflow, risk, opportunity, variance, and trends can speak the same language.

Artemis program names

  • Field-to-ERP Bridge: field progress, labor, equipment, material, and revenue logic structured for management systems.
  • Geometry-to-Cashflow System: geometry and quantities connected to cost, billing, cash position, and forecast variance.
  • Field-to-Finance Intelligence: operational reality translated into commercial visibility.
  • Dynamic Controls Bridge: risk, opportunity, variance, and trends monitored as conditions change.

Executive control room

RC4 adds side-by-side live 3D model review and synchronized cashflow, production, cost variance, risk/opportunity, and forecast range charts for executive review, screenshot capture, and narrated LinkedIn video.

Pro tips

  • Use Clean mode for screenshots.
  • Use Field Log before EVM conclusions.
  • Use formula audit before presenting numbers.
  • Keep satellite as context unless georeferenced and verified.

Pitfalls

  • Do not treat schematic piles or utility envelopes as engineered design.
  • Do not mix assumed quantities with actuals without labeling source.
  • Do not let basemap imagery imply survey accuracy.
  • Do not overwrite baseline without a regression checklist.

Daily / weekly maintenance workflow

FrequencyActionWhy it matters
DailyUpdate field log quantities, labor hours, equipment hours, material/subcontract costs.Keeps EVM and forecast meaningful.
DailyRecord notes for delays, inspections, weather, utility conflicts, and design holds.Creates claim/reconciliation traceability.
WeeklyExport schedule, cashflow, QTO, field log, and JSON snapshot.Creates versioned backup and review package.
WeeklyRun Geometry QA and formula audit before sharing.Prevents presenting stale assumptions.
MonthlyReconcile billing revenue, actual cost, projected cost, retainage, and cash received.Aligns model with PM forecast and payment reality.
Offline fallback is initializing…
Excavation Pipe Cradle Manhole Catch basin Sheeting / active

Selected fallback element

Click a fallback element to test simplified hit detection.

Runtime reliability checks

v1.4 lessons carried forward

Reliability purpose: this tab proves the app still has a native, dependency-light model sanity layer if Three.js, Chart.js, Leaflet, CDN access, or satellite tiles fail. It is not the official design model.

RC8.4 Dual Story + Field Claims Hardening Check

Validates that the guided scenario controls, actuals/claims studio, narrative cockpit, and source-of-truth engine are still synchronized.

Best augmentation strategy

Method: keep v2.7/v2.8 as the base, add isolated reliability patches, and use v1.4/v2.3 only as references. Do not merge old files wholesale.

Upload manifest

Claude prompt

Codex vs regular chat

Regular chat best for architecture, prompt design, reviewing screenshots, and deciding what to upload.

Codex best for editing the actual HTML, running checks, comparing diffs, and making repeatable no-regression changes across versions.

RC7 QA Status

Runtime, DOM, feature-preservation, capture, sequence, and public-boundary checks.

DEP Sewer Workbench Tutorial

This guided tour explains the app as a presentation tool, estimator/QTO aid, 4D/5D simulator, and geometry QA dashboard.

3DQTOCMiC Cost CodesEVMCashflowSatellite Context

1. Start with the model

Use Iso/Profile/Plan/Fit, then choose Construction cutaway, Full trench, Pipe only, or Completed condition. Keep HUD and legend visible while teaching; use Clean mode for screenshots.

2. Explain geometry and assumptions

Show pipe family, pipe size, cover, trench/support, manhole spacing, CB/house connections, and Geometry QA. Emphasize which parameters are standard-based, lookup-based, assumed, or placeholders.

3. Connect geometry to money

Move from QTO to ERP Cost Codes and Crosstab. Explain L/M/C/S/E/R suffixes: labor, material, consumable, subcontract, equipment, and revenue/billing.

4. Show 4D/5D workflow

Use Schedule & Cashflow, EVM & Forecast, and Field Log. Demonstrate how actuals change earned value, projected final cost, margin, and net cash position.

5. Use satellite responsibly

Satellite imagery is context only unless the model is properly georeferenced against survey/control. It should support presentation and orientation, not certify dimensions or pay quantities.

Offline QA and fallback discipline

Use the Offline QA tab to confirm dependency status, simplified fallback geometry, element indexing, and CSV-pack exports. This helps prove enhancements did not break presentation reliability.

Closeout discipline

Export QTO, schedule, cashflow, formula audit, and JSON snapshot weekly. Keep a version log and never overwrite a working baseline without syntax and UI regression checks.