plan specification

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

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

SubClass Of: information content entity

Class Hierarchy

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

Direct subclasses:

• business model
• commercial service specification
• encoded algorithm
• inspection plan
• maintenance strategy
• material handling plan
• packaging plan specification
• process plan
• production plan
• shipment plan specification
• supply chain plan specification
• warehousing plan specification

Definition

information content entity that has action specifications and objective specifications as parts

Explanatory Notes

When concretized, plan specification may be realized in a process where participants take the prescribed actions to achieve the prescribed process objectives. In other words, a plan specification is concretized in a ‘planned process’ that it ‘prescribes’

Examples

• a manufacturer’s sales plan; process plan for producing a part; a schedule for routine maintenance and inspection of a machine; a work order to build 100 of a particular kind component for today.

Synonyms

• process design
• process specification
• work instruction

Adapted From

• http://purl.obolibrary.org/obo/IAO_0000104

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

InformationContentEntity(x) ∧ ∃a∃o∃p(ActionSpecification(a) ∧ ObjectiveSpecification(o) ∧ PlannedProcess(p) ∧ continuantPartOfAtAllTimes(a,x) ∧ continuantPartOfAtAllTimes(o,x) ∧ prescribes(x,p)) → PlanSpecification(x)

Semi-Formal Natural Language Axioms

if x is an ‘information content entity’ that ‘prescribes’ some ‘planned process’ and x ‘has continuant part at all times’ some ‘action specification’ and some ‘objective specification’ then x is a ‘plan specification’

Description Logic

constr:PlanSpecification ⊑ constr:InformationContentEntity

constr:PlanSpecification ⊑ ∃ bfo:has_continuant_part_at_all_times .constr:ActionSpecification

constr:PlanSpecification ⊑ ∃ bfo:has_continuant_part_at_all_times .constr:ObjectiveSpecification

constr:InformationContentEntity ⊓ ∃ bfo:has_continuant_part_at_all_times .constr:ActionSpecification ⊓ ∃ bfo:has_continuant_part_at_all_times .constr:ObjectiveSpecification ⊓ ∃ constr:prescribes .constr:PlannedProcess ⊑ constr:PlanSpecification

SubClassOf: constr:InformationContentEntity

SubClassOf: bfo:has_continuant_part_at_all_times some constr:ActionSpecification

SubClassOf: bfo:has_continuant_part_at_all_times some constr:ObjectiveSpecification

constr:InformationContentEntity and bfo:has_continuant_part_at_all_times some constr:ActionSpecification and bfo:has_continuant_part_at_all_times some constr:ObjectiveSpecification and constr:prescribes some constr:PlannedProcess SubClassOf: constr:PlanSpecification