Geometry & clickable intelligence
Inspect duct, VAV boxes, diffusers, risers, equipment, hierarchy, and linked construction activities.
This version keeps the new field-to-cash / claim-payment story and restores the polished Cockpit v1 “Floor Section & Spine” story as a second guided narrative. Both stories launch the same live RC8 engine.
Artemis Construction turns one representative commercial HVAC 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.
The guided demo loads four representative bulletin claims against the live activity model — each one traceable to quantities, cost codes, and the payment-application register.
12 terminal units added after the fit-out replan. Loaded as a sample claim pending backup against activity 0520-VAV.
2,400 LB of duct rerouted around an as-built beam discovered above the ceiling. Partially approved against 0410-DUCT.
Load recalculation drove a 1-EA chiller upsizing. Loaded as a disputed sample claim against 0510-SET.
Controls scope growth of 60 additional points. Pending backup against 0720-DDC.
This second story preserves the strongest language and feel from the attached Cockpit v1 file: the floor-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, site context, and control engines remain the source of truth.
The Bridge takes a single commercial HVAC 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.
Floor section, plenum, duct mains, VAV boxes, diffusers, riser shafts, and brass accents create a subject-specific story rather than a generic dashboard.
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.
BIM, QTO, project controls, field, commercial/claims, standards/QA, and executives all receive the same source model in their own working language.
The narrative is the front door. Launch buttons open the actual model, site context, schedule/cashflow, actuals/claims, Mechanical Standards Lens, control room, and capture studio.
This section imports Cockpit v1’s best decision layer into RC8.2, but points it at the active RC8 geometry and estimate engine. Scenario, building type, and existing-conditions 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.
| Code | Activity | Value |
|---|
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.
One model is translated into the professional dialect each team needs, while the controls remain connected across disciplines.
Inspect duct, VAV boxes, diffusers, risers, equipment, hierarchy, and linked construction activities.
Synchronize the activity register, Gantt sequence, PV/EV/AC curves, CPI/SPI, EAC, variance, and cash.
Load deterministic sample scenarios or import source-tagged daily production and cost records.
Map L/M/C/S/E/R cost codes, payment applications, approvals, retainage, payment status, and cash gaps.
Trace representative mechanical-standard assumptions into geometry, quantities, formulas, controls, and public-safe limitations.
Read cost, production, cash, variance, risk, opportunity, reconciliation, and warnings beside the live model.
The Bridge reduces re-keying and version drift by letting each role read a shared source through the controls they already understand.
Geometry, hierarchy, zones, quantities, selection, and linked activities.
Activity windows, sequence logic, PV/EV/AC, CPI/SPI, forecast, and variance.
Zone, floor, quantity, crew, inspection, notes, and actual cost.
SOV rates, payment applications, retainage, lag, and cash exposure.
Representative standards logic, assumptions, checks, and limitations.
Decision gate, warnings, ownership, risk, cash, forecast, and reconciliation.
Move directly from the narrative into the operational proof point. The underlying RC8 actuals/claims, QTO, EVM, site context, and cashflow engines remain the source of every live number.
Place a persistent question mark on the selected element or choose an exact visible model point.
Eight guided capture presets for LinkedIn, printable storytelling, model-canvas export, and the narrated app demo.
Press Demo to auto-walk through the screenshot deck while the model, executive charts, and captions tell the 60-second story.
Representative Midtown Manhattan mechanical geometry stays connected to quantity, schedule, field production, ERP cost, payment applications, cashflow, and executive action.
Purpose: make this public demo unmistakably about a realistic commercial HVAC mechanical system. Artemis Construction is using representative ASHRAE / SMACNA / IMC-style mechanical 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.
| Item | Public demo treatment | Reason |
|---|---|---|
| Mechanical standards | Representative standard-family logic, not official design approval. | Shows method without implying agency certification. |
| Geometry | Parametric and quantity-driven; not survey control or sealed design. | Good for demonstration, estimation logic and workflow design. |
| Quantities | Derived from model assumptions and visible formulas. | Useful for QTO/SOV templates, subject to contract reconciliation. |
| ERP / CMiC bridge | Demonstrates L/M/C/S/E/R mapping and exports. | Shows how field/project models can communicate with ERP structures. |
| Risk / opportunity | Scenario and randomized trend simulation. | Executive visibility; not a replacement for project controls judgment. |
Activity register, Gantt storytelling, construction-front playback, and cash/EVM status stay synchronized to the same working-day clock.
Trace the Midtown Manhattan model through daily completion, actual cost, earned value, payment application, approval, retainage, payment lag, and executive control response.
Office tower site anchor at 40.7549, −73.9840, near Bryant Park. Esri World Imagery provides recognizable, token-free satellite context (Esri World Street Map is available as the streets layer) while the Artemis Construction model remains the independent source for demonstration geometry, quantities, controls, schedule, and cashflow.
| Layer | Purpose | Regression guard |
|---|---|---|
| 3D model | Geometry/QTO/selection | Never depends on satellite tiles |
| Esri World Imagery | Midtown satellite context | Default Leaflet layer with attribution; tile errors fall back to the schematic |
| Site anchor | Building footprint and zone context | Fallback schematic if map fails |
| GeoJSON export | Site point and demonstration asset points | Separate, labeled contextual export |
An Artemis Construction 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.
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.
Artemis Construction 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.
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.
| Frequency | Action | Why it matters |
|---|---|---|
| Daily | Update field log quantities, labor hours, equipment hours, material/subcontract costs. | Keeps EVM and forecast meaningful. |
| Daily | Record notes for delays, inspections, weather, concealed-condition conflicts, and design holds. | Creates claim/reconciliation traceability. |
| Weekly | Export schedule, cashflow, QTO, field log, and JSON snapshot. | Creates versioned backup and review package. |
| Weekly | Run Geometry QA and formula audit before sharing. | Prevents presenting stale assumptions. |
| Monthly | Reconcile billing revenue, actual cost, projected cost, retainage, and cash received. | Aligns model with PM forecast and payment reality. |
Validates that the guided scenario controls, actuals/claims studio, narrative cockpit, and source-of-truth engine are still synchronized.
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.
Commissioning panel loading…
Runtime, DOM, feature-preservation, capture, sequence, and public-boundary checks.
This guided tour explains the app as a presentation tool, estimator/QTO aid, 4D/5D simulator, and geometry QA dashboard.
3DQTOCMiC Cost CodesEVMCashflowSatellite ContextUse Iso/Profile/Plan/Fit, then choose Construction cutaway, Full ductwork, Piping only, or Completed condition. Keep HUD and legend visible while teaching; use Clean mode for screenshots.
Show duct family, SMACNA pressure class, plenum/ceiling access, hanger/seismic, VAV box layout, diffuser count, and Geometry QA. Emphasize which parameters are standard-based, lookup-based, assumed, or placeholders.
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.
Use Schedule & Cashflow, EVM & Forecast, and Field Log. Demonstrate how actuals change earned value, projected final cost, margin, and net cash position.
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.
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.
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.