S24 DEE
Unified Mission Workbench
Activation + Ops Graph Assembly Builder Mission Consequence Explorer
Single-page stakeholder workflow

Activate systems → define assembly → evaluate feasible mission consequences

This mockup keeps everything on one continuous page. The first section captures which systems are online and shows a mission operations graph, the middle section is the assembly-builder workspace, and the final section is the mission consequence explorer that surfaces DES-generated scenario options.

1. Activate Systems + Mission Operations Graph
The user is not hard-coding the event sequence here. They are activating available assets, setting high-level operational constraints, and defining the mission configuration that the DES can use to generate feasible sequences.
Activate Systems
Active Systems
5
Assets currently available to the DES
Network Edges
8
Potential operational interactions
Feasible Plans
3
Dummy DES outputs ready for screening
Mission Score
78
Composite cost / throughput / risk proxy
Mission Operations Graph
Active logistics or production node Surface support / crew node Transport or transfer path
Graph updates when systems are turned on or off. This is the stakeholder-facing systems view that constrains what the DES is allowed to sequence downstream.
2. Assembly Builder
This section keeps the assembly tree + editable part metadata layout from your uploaded Assembly Builder structure, but reformats it into the single-page flow beneath the activation section. The original file uses a left tree / right form composition with tree rendering, import, metadata fields, and preview actions. fileciteturn1file0 fileciteturn1file3
Assembly Tree
Select a node to edit or create a new child.
Part / Assembly Metadata
Selected path: /LSP1Assembly
Identity
Dimensions
Transform — Position
Transform — Orientation
Units
Custom Attributes
Actions
✓ Assembly metadata saved and ready to feed downstream logic.
SysML Preview
package LSP1 {
  part LSP1Assembly {
    attribute geometry = "assets/geom/lsp1_assembly_geom.usda";
    attribute materialRef = "Aluminum_2219_T87";
  }
}
This page is wired with dummy data, but it is structured so that your actual DES outputs could replace the scenario array and metrics without changing the user flow.
Mission Workbench
3. Mission Consequence Explorer
Mission Consequence Explorer — DES Mockup

Mission Consequence Explorer

Interactive mockup for a DES-driven lunar infrastructure dashboard with real-time parameter perturbation.

Scenario: ISRU Processing Plant
Mode: Consequence Explorer
Baseline vs Modified
Mission Time t = 6 hr
Rover unload Plant active Threshold Transport Power spike

Coupled Mission State Network

Node color = health/utilization. Edge thickness = current flow magnitude. This is what the stakeholder “feels” when a parameter changes.
● healthy ● constrained ● bottleneck
Regolith Rover Load: 4000 kg ISRU Plant LOX: 10.1 kg Solar + Power 100 kW available LOX Rover Idle LZ / Depot 0 kg stored Habitat 5 kW Comms 2 kW Charge Station 20 kW
At the current parameter set, the rover is supplying enough regolith to keep the plant active with low starvation risk. Increasing discharge rate will likely steepen LOX growth, increase plant energy consumption, and move threshold-triggered transport earlier in the mission.

LOX Stored vs Time

Shows whether the parameter change increases cumulative oxygen availability.

Power Demand vs Time

Shows secondary energy consequences from plant and rover-side changes.

Rover Battery vs Time

Shows mobility margin and charging stress as throughput is increased.

Regolith Buffer / Delivery

Shows whether the plant is starved, balanced, or oversupplied.

Show baseline overlay
This mockup uses dummy consequence propagation to illustrate the stakeholder experience. In the real system, these updates should be driven by a DES rerun or a surrogate model.