recipe procedural element

IRI: https://spec.industrialontologies.org/ontology/construct/RecipeProceduralElement

Defined In: https://spec.industrialontologies.org/ontology/biopharma/Recipe/

SubClass Of: plan specification

Class Hierarchy

owl:Thing › bfo:entity › bfo:continuant › bfo:generically dependent continuant › information content entity › plan specification › recipe procedural element

Direct subclasses:

• recipe operation
• recipe phase
• recipe procedure
• recipe unit procedure

Definition

plan specification that prescribes some planned process that is part of a batch run and is equipment specific or manufacturing capability specific

Explanatory Notes

1) From ISA-88 (1995) part 1 section 3, a building block for procedural control that is defined by the procedural control model. 2) From ISA-88 (2010) part 1 section 5, a procedural element is any part of a recipe or control strategy that defines a set of activities or actions, potentially including decision logic, which guides the execution of a manufacturing process.

Usage Notes

1) A recipe procedural element must not be included in general recipes, site recipes, or recipe process elements, as it is intended to represent equipment-specific or manufacturing capability-specific instructions. This restriction is formally captured by the axiom: ‘continuant part of at some time’ only (not (‘general recipe’ or ‘recipe process element’ or ‘site recipe’)). 2) While a recipe procedural element may be included in one or more control recipes or master recipes, there is no axiomatic requirement for such inclusion, allowing for flexible reuse and recombination across different contexts. When associating a recipe procedural element with a control or master recipe, the ‘continuant part of at some time’ relation (or an appropriate subproperty) should be used.

Examples

• recipe operation; recipe phase; recipe procedure; recipe unit procedure

Primitive Class

This class is declared primitive and it does not have necessary and sufficient condiftions defined.

Primitive Rationale

This term is expected to remain primitive, as it is challenging to define a set of OWL-compatible necessary and sufficient conditions that in all cases reliably distinguish a recipe procedural element from a recipe process element.

Formal Axioms

First-Order Logic Axioms

RecipeProceduralElement(x) → PlanSpecification(x) ∧ ∀y(continuantPartOfAtSomeTime(x, y) → ¬(GeneralRecipe(y) ∨ RecipeProcessElement(y) ∨ SiteRecipe(y))) ∧ ∃z (prescribes(x, z) ∧ PlannedProcess(z) ∧ ∃w (occurrentPartOf(z, w) ∧ BatchRun(w)))

Semi-Formal Natural Language Axioms

if x is a ‘recipe procedural element’, then x is a ‘plan specification’, x is not a continuant part at any time of a ‘general recipe’, ‘recipe process element’, or ‘site recipe’, and x ‘prescribes’ some ‘planned process’ that is an ‘occurrent part of’ some ‘batch run’

Description Logic

constr:RecipeProceduralElement ⊑ constr:PlanSpecification

constr:RecipeProceduralElement ⊑ ∀ bfo:continuant_part_of .¬ constr:GeneralRecipe ⊔ constr:RecipeProcessElement ⊔ constr:SiteRecipe

constr:RecipeProceduralElement ⊑ ∃ constr:prescribes .(constr:PlannedProcess ⊓ ∃ bfo:occurrent_part_of .constr:BatchRun)

constr:RecipeProceduralElement ⊓ constr:RecipeProcessElement ⊑ ⊥

SubClassOf: constr:PlanSpecification

SubClassOf: bfo:continuant_part_of only not (constr:GeneralRecipe or constr:RecipeProcessElement or constr:SiteRecipe)

SubClassOf: constr:prescribes some (constr:PlannedProcess and bfo:occurrent_part_of some constr:BatchRun)

constr:RecipeProceduralElement DisjointWith: constr:RecipeProcessElement