output objective specification

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

Defined In: https://spec.industrialontologies.org/ontology/core/Core/

SubClass Of: objective specification

Class Hierarchy

owl:Thing › bfo:entity › bfo:continuant › bfo:generically dependent continuant › information content entity › objective specification › output objective specification

Direct subclasses:

Definition

objective specification that prescribes the entities to be produced or modified in a planned process or the attributes they must posses to serve as valid outputs

Explanatory Notes

As a subclass of objective specification, the output specification defines the intended results of a planned process. As such it should exclude waste and unintended products (e.g., byproducts or impurities generated during synthesis) that are not part of the process objective.

Examples

  • A specification stating that the chromatography step must yield purified monoclonal antibody at a purity > 98% and recovery > 85%; An analytical procedure specification requiring a quantified measurement of total protein concentration with CV < 5% across replicates; A fill-finish procedure output specification requiring that each vial is filled with 1.0 mL ± 0.05 mL of formulated drug product and passes visual inspection; A machining operation output objective specification stating that the finished shaft must have diameter 25.00 mm ± 0.01 mm and surface roughness Ra ≤ 0.8 µm; A parcel fulfillment output objective specification requiring that each sealed carton has total mass 10.0 kg ± 0.1 kg and contains the correct item count per packing list; A data processing step output objective specification requiring that the generated report contains the specified summary fields and that all numeric values are rounded to the required precision.

Counter-Examples

  • A specification about waste collected after cleaning, e.g., “The waste stream from CIP must be neutralized before disposal.”; A specification limiting the number of rejected vials during inspection (this constrains process acceptability, not what is intended to be produced); A specification stating that the equipment must be cleaned and verified as clean before the procedure is considered complete (a completion criterion/post-condition, not an output objective for a product); A specification requiring that the process log and electronic batch record are reviewed and approved after execution (a documentation/release post-condition, not an output objective for the produced entity).

Primitive Class

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

Primitive Rationale

See the general discussion and rationale provided for informational entities under ‘information content entity’.

Formal Axioms

First-Order Logic Axioms 

OutputObjectiveSpecification(x) → ObjectiveSpecification(x) ∧ ∀y(prescribes(x,y) → ((Continuant(y) ∧ ∃p(isSpecifiedOutputOf(y,p) ∧ PlannedProcess(p))) ∨ (SpecificallyDependentContinuant(y) ∧ ∃z(specificallyDependsOn(y,z) ∧ Continuant(z) ∧∃p (isSpecifiedOutputOf(z,p) ∧ PlannedProcess(p))))))

Semi-Formal Natural Language Axioms

if x is an ‘output objective specification’ then x is an ‘objective specification’ and whenever x ‘prescribes’ some y that y mustbe either a ‘continuant’ that ‘is specified output of’ some ‘planned process’ or a ‘specifically dependent continuant’ that ‘specifically depends on’ some ‘continuant’ that ‘is specified output of’ some ‘planned process’

Description Logic

constr:OutputObjectiveSpecification ⊑ constr:ObjectiveSpecification

constr:OutputObjectiveSpecification ⊑ ∀ constr:prescribes .((bfo:continuant ⊓ ∃ constr:isSpecifiedOutputOf .constr:PlannedProcess) ⊔ (bfo:specifically_dependent_continuant ⊓ ∃ bfo:specifically_depends_on .(bfo:continuant ⊓ ∃ constr:isSpecifiedOutputOf .constr:PlannedProcess)))

SubClassOf: constr:ObjectiveSpecification

SubClassOf: constr:prescribes only ((bfo:continuant and constr:isSpecifiedOutputOf some constr:PlannedProcess) or (bfo:specifically_dependent_continuant and bfo:specifically_depends_on some (bfo:continuant and constr:isSpecifiedOutputOf some constr:PlannedProcess)))