Phase 0 · Baseline inventory and legal mapCatalog scenes, extensions, APIs, data, models, licenses, GPU assumptions, and operational dependencies. Freeze representative workloads before redesign begins.Exit: every retained feature has an owner, baseline trace, acceptance metric, and migration disposition.
Phase 1 · Contracts and coordinate disciplineDefine ISAM, dynamics, sensor, control, time, and evidence contracts. Fix SI units, handedness, frame naming, quaternion order, and timestamp semantics.Exit: contract tests run against adapters without loading a renderer or physics engine.
Phase 2 · Asset compiler and semantic round tripImport OpenUSD, URDF/SDF, glTF, CAD/IFC, AAS, and OPC UA references into ISAM, then export required exchange formats.Exit: zero loss of safety-critical joints, frames, limits, mass properties, sensor calibration, and identity.
Phase 3 · Browser engineering runtimeDeliver Three.js rendering, scene inspection, timeline, state replay, simple Ammo.js physics, and WASM kinematics.Exit: target scenes meet frame-time, memory, pose-accuracy, and usability budgets on reference browsers.
Phase 4 · Native dynamics and planning workersImplement the dynamics ABI, actuator/contact extensions, MoveIt 2 planning bridge, native SIMD/GPU workers, and backend capability registry.Exit: canonical physics suites and task trajectories pass differential tolerances.
Phase 5 · Virtual sensor and data factoryAdd calibrated camera, depth, LiDAR, IMU, force/torque, encoder, tactile, domain randomization, and typed annotations.Exit: sensor distributions and downstream perception KPIs meet hardware-derived limits.
Phase 6 · Policy, control, and HILConnect ROS 2, behavior runtime, planner, policy packages, real controllers, fieldbus timing, and safety monitors.Exit: shadow and HIL runs preserve control deadlines, interlocks, fault response, and task success.
Phase 7 · Parallel operation and selective retirementRun incumbent and open stacks on the same scenario set, sign evidence manifests, migrate teams and CI, then retire only capabilities that pass.Exit: two release cycles without a severity-one regression and with approved rollback evidence.
阶段 0 · 基线盘点与法律边界清点场景、扩展、API、数据、模型、许可证、GPU 假设和生产依赖。在重构前冻结代表性工作负载。退出:每项保留能力都有负责人、基线轨迹、验收指标和迁移处置。
阶段 1 · 契约与坐标纪律定义 ISAM、动力学、传感器、控制、时间和证据契约,固定 SI 单位、手性、坐标命名、四元数顺序和时间戳语义。退出:无需加载渲染器或物理引擎即可对适配器执行契约测试。
阶段 2 · 资产编译器与语义往返把 OpenUSD、URDF/SDF、glTF、CAD/IFC、AAS 和 OPC UA 引用导入 ISAM,再导出所需交换格式。退出:安全相关关节、坐标、限位、质量属性、传感器校准和身份零丢失。
阶段 3 · 浏览器工程运行时交付 Three.js 渲染、场景检查、时间线、状态回放、基础 Ammo.js 物理和 WASM 运动学。退出:目标场景在参考浏览器达到帧时、内存、位姿精度和可用性预算。
阶段 4 · 原生动力学与规划节点实现动力学 ABI、执行器/接触扩展、MoveIt 2 规划桥、原生 SIMD/GPU 节点和后端能力注册表。退出:规范物理测试集和任务轨迹通过差分容差。
阶段 5 · 虚拟传感器与数据工厂加入已标定相机、深度、LiDAR、IMU、力/力矩、编码器、触觉、域随机化和类型化标注。退出:传感器分布和下游感知 KPI 达到真实硬件推导的限制。
阶段 6 · 策略、控制与硬件在环接入 ROS 2、行为运行时、规划器、策略包、真实控制器、现场总线时序和安全监视器。退出:影子与 HIL 运行保持控制截止时间、联锁、故障响应和任务成功率。
阶段 7 · 并行运行与选择性退役让现有栈与开放栈运行相同场景,签署证据清单,迁移团队与 CI,只退役已经通过验收的能力。退出:连续两个发布周期无一级回归,并具有获批的回滚证据。