modules
Recipe, Run and Process Execution
Keep the approved recipe, actual machine program, physical run and resulting material history connected.
A recipe revision reaches one line while another line is still finishing the previous version. MAXACOR keeps the instruction, parameters, equipment state, material and resulting output tied to the run that actually used them. MES and enterprise systems retain business production records; equipment controllers retain local execution.
When it matters
A recipe revision reaches one line while another line is still finishing the previous version. MAXACOR keeps the instruction, parameters, equipment state, material and resulting output tied to the run that actually used them.
data Viz
data View
section: module-scene
Section 1
col Title: Recipe and Execution Context
col Cont: A batch starts only after the current recipe, equipment and material context agree. Teams can prove which instructions governed each output.
Section 2
col Title: Execution Run
col Cont: A run pauses after partial production and resumes without losing the units already transformed. Run status reflects physical evidence rather than a workflow terminal.
Section 3
col Title: Process Deviation
col Cont: An operator adjusts a parameter to protect the batch during a disturbance. The deviation, authority, evidence and downstream review remain attached to the resulting material.
Recipe, Run and Process Execution
data View: maxacor-recipe-run-execution:submodules
Recipe and Execution Context
desc: Connect recipe, parameters, materials, tooling and approved configuration to the physical run.
link: /sub-modules/maxacor-recipe-context
Execution Run
desc: Follow one physical run from admission through work, interruption, completion and evidence closure.
link: /sub-modules/maxacor-execution-run
Process Deviation
desc: Capture departures from the approved process and connect them to affected output.
link: /sub-modules/maxacor-process-deviation
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.
Execution Run
action: Follow one physical run from admission through work, interruption, completion and evidence closure.
mechanism: A run pauses after partial production and resumes without losing the units already transformed.
workflow role: A run pauses after partial production and resumes without losing the units already transformed.
operational outcome: Run status reflects physical evidence rather than a workflow terminal.
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
MAXACOR does not replace MES business ownership.
Process Deviation
action: Capture departures from the approved process and connect them to affected output.
mechanism: An operator adjusts a parameter to protect the batch during a disturbance.
workflow role: An operator adjusts a parameter to protect the batch during a disturbance.
operational outcome: The deviation, authority, evidence and downstream review remain attached to the resulting material.
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
A deviation record is not automatic quality acceptance.