RUN-1191 has no RUN fixture in this wireframe — showing scenario A (RUN-1190). Gate 5 object view →
RUN-1190
Print complete · bed occupiedplate 3 of 3Cloud synchronized · 0 min oldFinished on the bed at 08:12. Clearing it is what makes U1-05 available.
- JOBJOB-203
- →
- PARTHEX-OS-01 · Outer Shell
- →
- VARIANTHEX-OS-01-V1
- →
- FILEFILE-0117-v2
- →
- MACHINEU1-05
Pieces Collected
bed blocked- collect
- 1 · count
- 2 · outcome
- → action queue
4 Outer Shell pieces were planned on this bed. One touch means: collected and accepted for the planned count.
Nothing is inferred from the machine. Good enters stock only after this step; until then the 4 pieces are UNKNOWN and U1-05 is NOT available.
Execution
Idlebed: Awaiting RemovalProduction counts · this run
awaiting humanProduced is written only from a human count or a validated object-level signal. Scrap is material lost (PCY); Unproduced is capacity never realised; UNKNOWN is neither — and never zero.
Objects · 4 on the plate
Object ManifestObject identity comes from the file's Object Manifest. Outcome per object is human input at collection; the run never infers it from progress. Open Print File →
Run timeline
append-only- 04:02Run started · JOB-203 · plate 3 of 3 · U1-05
- 04:03Material reserved · PLA Signal Orange · 86 g · SP-0132
- 08:12Print complete · G-code finished · 312 layers
- 08:12Bed occupied · 4 objects reported on the bed · machine NOT available
- 08:12Action created · ACT-4471 · Awaiting Removal
- —Pieces Collected · waiting for a human