OEO Ontology

Overview / Open Energy Ontology / Class - plan specification
Label: plan specification
Definition:
A directive information entity with action specifications and objective specifications as parts, and that may be concretized as a realizable entity that, if realized, is realized in a process in which the bearer tries to achieve the objectives by taking the actions specified.

Sub classes:
algorithm
view
Definition:
A plan specification which describes the inputs and output of mathematical functions as well as workflow of execution for achieving an predefined objective. Algorithms are realized usually by means of implementation as computer programs for execution by automata.

climate neutrality criterion
view
Definition:
A climate neutrality criterion is a plan specification that intends to describe a state in which human activities result in no net effect on the climate system.

dispatch assignment
view
Definition:
Dispatch assignment is a plan specification that refers to resource planning at a power plant (usually by the plant’s operator).

merit order
view
Definition:
A merit order is a plan specification that describes the dispatch ranking of power plants (electrical generation) based on ascending order of price.

methodology
view
Definition:
A methodology is a plan specification that describes processes that are part of a study.

policy
view
Definition:
A policy is a plan specification that is a deliberate system of principles, rules and guidelines, adopted by an organisation to guide decision making with respect to particular situations and implemented to achieve stated goals.

programming language
view
Definition:
A language in which source code is written that is intended to be executed/run by a software interpreter. Programming languages are ways to write instructions that specify what to do, and sometimes, how to do it.

software
view
Definition:
Software is a plan specification composed of a series of instructions that can be interpreted by or directly executed by a processing unit.


study design
view
Definition:
A plan specification comprised of protocols (which may specify how and what kinds of data will be gathered) that are executed as part of an investigation and is realized during a study design execution.

sufficiency
view
Definition:
Sufficiency is a plan specification for reducing, in absolute terms, the consumption and production of end-use products and services through changes in social practices in order to comply with environmental sustainability while ensuring an adequate social foundation for all people.

sustainability criterion
view
Definition:
A sustainability criterion is a plan specification that intends to meet the needs of the present without compromising the ability of future generations to meet their own environmental, economic and social needs.

technology
view
Definition:
A technology is a plan specification that describes how to combine artificial objects or other material entities and processes in a specific way.

Back to the super classes:
directive information entity
view
Definition:
An information content entity whose concretizations indicate to their bearer how to realize them in a process.

Editor note:
2009-03-16: provenance: a term realizable information entity was proposed for OBI (OBI_0000337) , edited by the PlanAndPlannedProcess branch. Original definition was "is the specification of a process that can be concretized and realized by an actor" with alternative term "instruction".It has been subsequently moved to IAO where the objective for which the original term was defined was satisfied with the definitionof this, different, term.

Editor note:
2013-05-30 Alan Ruttenberg: What differentiates a directive information entity from an information concretization is that it can have concretizations that are either qualities or realizable entities. The concretizations that are realizable entities are created when an individual chooses to take up the direction, i.e. has the intention to (try to) realize it.

Editor note:
8/6/2009 Alan Ruttenberg: Changed label from "information entity about a realizable" after discussions at ICBO

Editor note:
Werner pushed back on calling it realizable information entity as it isn't realizable. However this name isn't right either. An example would be a recipe. The realizable entity would be a plan, but the information entity isn't about the plan, it, once concretized, *is* the plan. -Alan