sub-modules
Recipe and Execution Context
Connect recipe, parameters, materials, tooling and approved configuration to the physical run.
A batch starts only after the current recipe, equipment and material context agree. Teams can prove which instructions governed each output.
What changes
A batch starts only after the current recipe, equipment and material context agree. Teams can prove which instructions governed each output.
data Viz
data View
section: operating-scene
Operational boundary
- What it does
- Connect recipe, parameters, materials, tooling and approved configuration to the physical run.
- What the team gains
- Teams can prove which instructions governed each output.
- What it does not own
- Recipe approval does not directly command equipment.
- section
- operational-boundary
Recipe and Execution Context
action: Connect recipe, parameters, materials, tooling and approved configuration to the physical run.
mechanism: A batch starts only after the current recipe, equipment and material context agree.
workflow role: A batch starts only after the current recipe, equipment and material context agree.
operational outcome: Teams can prove which instructions governed each output.
maturity: specified
evidence: MAXACOR Part 9, §§12–19.
Section 1
Operations team
Section 2
Engineering team
Section 1
Qualified physical state
Section 2
Current work context
Section 1
Evidence-bearing operational disposition
Section 1
Recipe approval does not directly command equipment.