A documented, execution-ready Phase I plan
The Phase I plan is a six-month hardware-calibration effort. The linked Mobient digital twin has matured into an execution-readiness toolchain that structures that plan end to end: passive-target design, bench calibration, active-surface, thermal, and sensor-timing validation, runtime proof, and DSE-ready evidence.
This does not replace bench validation. It gives the Phase I team a structured path that reduces the ambiguity, planning overhead, and rework risk that usually consume the early hours of the effort.
The current toolchain now supports
Deterministic Replay Viewer
Scenario-level DSE admission, refusal, active surface authority, coil thermal mapping, and A/B reproducibility – demonstrated through byte-identical replay.
RSL Forge
Passive footwear, SLED rail, and coupon geometry design over the Mobient coil grid, with approximate pre-calibration scoring for force distribution, center of pressure, moment, shear capacity, cogging, heat-risk, manufacturability, and DSE compatibility.
RSL CalBench
The measured-truth loop: Forge profile → physical coupon test → imported measurements → predicted-vs-measured residuals → calibration fit → DSE authorization status.
Mobient ScenarioDeck
Population, mission, and safety-gate coverage for calibrated RSL profiles: consumes a Forge profile + CalBench calibration + DSE authorization and evaluates coverage across people, cargo, mission cases, and faults – with an exportable RSL Coverage Certificate.
Mobient CoilBench
Active-side calibration of the coil surface: force vs current vs gap fits (with saturation + temperature terms), per-coil outlier maps, and the H01/H23 RowFeed Auditor against the 190 A per-feed budget – emitting a hashed CoilCalibrationPack + DSE force-adapter bundle.
Mobient ThermalBench
The measured-thermal-truth workbench: ingest coolant, PCM, coil / driver / baseplate, and surface temperatures; fit thermal response, define coolant-valid and PCM-limited envelopes, and export a DSE thermal derate pack – with per-coil RC, multi-tile route, vacuum and station-coolant checks, and a sealed crew-contact surface-compliance package.
Mobient StackGuard
The 2.5D mechanical package, release, and build / commissioning-handoff workbench: a baseplate feature registry, z-stack / clearance / ligament checks, requirements and evidence traceability, CAD / vendor review, a drawing release book, a build traveler, as-built configuration, commissioning records, and a static Digital Twin Configuration Seed + Build Handoff Bundle – not CAD / PLM / MES / certification authority; service / admin-twin state is future scope.
Mobient TripWire
Temporal / causal sequence validation: did the runtime steps happen in the only safe order, on valid evidence, inside the timing budget (12 ms Trip→Full-Hold, 2 ms dead-man), before actuation? A 20-invariant simulation / replay / shadow validator, not a live firmware gatekeeper.
Mobient SenseWindow
Sensor-timing planning and trace auditing: when a Hall / capacitive / current / FOD reading can be trusted relative to PWM switching (the quiet window), raw→used traceability, and known-clear freshness – exporting the sensor evidence TripWire's contracts consume.
Mobient CalibrationPack Compiler
The publishing layer: assembles, validates, hashes, and publishes the other tools' outputs into a versioned CalibrationPack v1 + DSE adapter bundle + RunManifest fragment, with a status ladder and authority precedence; sample-only data can never reach DSE_READY.
Together, these tools turn Phase I from an open-ended discovery effort into a structured calibration workflow. The core Phase I work is still physical: build coupons, run bench tests, collect measurements, fit calibration data, and update the hardware-truth profiles. What is already in place is the surrounding structure: the test matrix, the data pathway, and the authorization logic are documented and ready, not invented at kickoff.
Hours protected across the Phase I scope
The Phase I scope spans mechanical, electromagnetic, thermal, sensor-timing, and integration work. Across all of it, the toolchain replaces open-ended setup with ready-to-run protocols, data formats, and authorization logic, so award-period hours go to bench work rather than to inventing the test matrix, the data pathway, and the calibration path.
| Phase I workstream | Toolchain support | Est. hours protected |
|---|---|---|
| Mechanical fixture definition | Forge coupon / rail / boot geometry, pose sweeps, test protocols | 40–70 |
| EM calibration planning | CalBench residuals, fit constants, validity envelopes | 30–60 |
| Thermal calibration planning | ThermalBench coolant / PCM / surface protocols, derate pack + DSE thermal-governor constants | 35–60 |
| Mechanical package + build / commissioning handoff | StackGuard 2.5D package / clearance checks, drawing release book, build traveler, as-built + commissioning records, digital twin configuration seed | 45–80 |
| PI integration / coordination | Shared schemas, profiles, dashboards, status ladder | 60–100 |
| Bench test execution | Protocols, import templates, predicted-vs-measured views | 25–50 |
| Digital-twin integration | RSLProfile → CalibrationFit → DSE authorization records | 40–70 |
| Total execution overhead structured up front, before the bench work begins | ~260–460 hrs | |
Across the Phase I scope, that is roughly 260–460 team-hours of execution overhead structured up front – without reducing the need for physical bench validation.
The toolchain is approximate / pre-calibration: it does not certify hardware or replace bench validation. RSL Forge scoring and RSL CalBench fits are engineering estimates calibrated to the deterministic twin; DSE authorization is only granted inside a measured validity envelope. Sample data shown in the tools is synthetic and labeled as such.