PlannedProcess(x) ↔ Process(x) ∧ ∃s(PlanSpecification(s) ∧ prescribes(s,x)) every instance of 'planned process' is defined as exactly an instance of 'process' that is 'prescribed by' some 'plan specification'

https://spec.industrialontologies.org/ontology/core/Core/PlannedProcess

http://purl.obolibrary.org/obo/OBI_0000011

unexpected failure events; unexpected malfunctioning of a machine; safety occurrence (that lacks explicit plan specifications);

PlannedProcess(x) ↔ Process(x) ∧ ∃s(PlanSpecification(s) ∧ prescribes(s,x))

every instance of 'planned process' is defined as exactly an instance of 'process' that is 'prescribed by' some 'plan specification'

1. 'Planned' is here functioning as a specifier, rather than as a modifier analogous to 'cancelled' or 'averted'. Therefore, to say that a process is planned is not to say that it has not yet taken place. Rather, it is to say that it is (was or will have been) protocol-driven, instruction-driven, command-driven, or software-driven, or in some combination thereof. 2. 'Planned' means 'protocol driven'. Protocols may be written, spoken, or simply thought – as when upon waking up, we plan, for instance, what to eat for breakfast.

PlannedProcess(x) ↔ Process(x) ∧ ∃s(PlanSpecification(s) ∧ prescribes(s,x))

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

iof-core:PlannedProcess

iof:PlannedProcess

PlannedProcess

every instance of 'planned process' is defined as exactly an instance of 'process' that is 'prescribed by' some 'plan specification'

http://purl.obolibrary.org/obo/BFO_0000015

https://github.com/Mat-O-Lab/MSEO/raw/main/domain/util/readable_bfo_iris.ttl/Process