MFG-RB01-P01 | Cell and task boundary briefing
Concept training procedure draft · D1 · 29 October 2026
For the inert browser model only. Not an approved operating SOP. No physical work, production release or certification is authorised.
Equipment: MFG-RB01
Model: 1.0.0-concept
Source basis: Original authored concept; no approved customer/OEM SOP supplied.

01. Confirm equipment and task identity.
Evidence: MFG-RB01 · Robot task development cell. Record draft D1 and model 1.0.0-concept.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

02. Confirm the inert training boundary.
Evidence: For the inert browser model only. Not an approved operating SOP. No physical work, production release or certification is authorised.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

03. Locate ROBOT-BASE, SHOULDER and ELBOW.
Evidence: Identify the articulated concept without assigning a real robot model.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

04. Locate WRIST and both gripper jaws.
Evidence: Keep end-effector geometry separate from the arm.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

05. Identify PICK-NEST and PLACE-NEST.
Evidence: Record the intended task start and end contexts.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

06. Locate WORKPIECE-01.
Evidence: Its illustrative size does not establish gripping compatibility.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

07. Inspect the boundary posts and CELL-STOP prop.
Evidence: They are nonfunctional visuals, not a validated safeguarding system.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

08. List the absent control and sensing interfaces.
Evidence: No robot controller, live sensor or safe motion programme is connected.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

09. Define who owns hardware qualification.
Evidence: A qualified integrator and site task owner must approve real testing.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

10. Hold any claim of task transfer.
Evidence: This model does not prove autonomous execution or cross-hardware reuse.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

11. Prepare the evidence record.
Evidence: Record observations, source revisions, holds, recovery and missing physical evidence; do not invent a result.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.

12. Request qualified review before reuse.
Evidence: Keep this draft unapproved until the task owner accepts the sources, geometry, criteria, permissions and revision.
HOLD if: Identity, source applicability or required evidence is missing or inconsistent.