This ontology describes the openADR protocol based on the documentation provided by the openADR Profile B
A spatial representation for a given feature.
Exists if the subject SpatialObject spatially contains the object SpatialObject
Relationship between a VE, Resource or Asset with the Group of targets associated
Relation between a target and its components
Relation between a target and the asset it contains
Relation between a target and the resource it contains
Relation between a target and the VEN it contains
Relation between an event and its metadata
Relation between an entity and its service area target
This is the time interval between sampled data in a report request
Relation between an entity and its group target
Relation between a report and the load control state to enable a VEN to report on its load control state that corresponds to a LOAD_CONTROL signal that might be sent to a VEN.
Relation between a report and its payload
Relation between a signal and its payload
Relationship between a signal and its signal type
Relation between an entity and its target
Link between a report and the measurement included in the payload
Relation between an entity and its signal
Relation between the report and its subject
Relation between an entity an its active period
Linked between a report and the properties it measure
Link between a signal and the interval where it is active
Relation between a payload and its descriptor
Relationship between a schedule and a target
Relation between Opt and the planification of a target
Relation between the node and an object it receives
Relation between a target and its availability
Relation between a report and its metadata
Relationship between the node and the report it requests
Relation between a node and an object it requires
A link between a node and the objects it sends
A link between a node and the event it sends
A link between a node and the opt it sends
A link between a node and the report it sends
relation between the report and its specification
Indicates the likely variability of the prediction and the error of a reading
A statistical probability that a reported data point is accurate
Number which is incremented each time an event is modified.
The priority of the event in relation to other events (The lower the number higher the priority. A value of zero (0) indicates no priority, which is the lowest priority by default).
Metadata about the Readings, such as mean or derived
A scaling factor for the base unit of measure for a report
Attribute to determine whether or not data is sampled as it changes
Attribute to indicate if a response is required to acknowledge the object
Attribute to indicate if the event is for testing purposes
The starting time for the activity, data, or state change
This class represents the top-level feature type. This class is equivalent to GFI_Feature defined in ISO 19156:2011, and it is superclass of all feature types
The class represents the top-level geometry type. This class is equivalent to the UML class GM_Object defined in ISO 19107, and it is superclass of all geometry types.
The class spatial-object represents everything that can have a spatial representation. It is superclass of feature and geometry.
A point, typically described using a coordinate system relative to Earth, such as WGS84.
Anything with spatial extent, i.e. size, shape, or position. e.g. people, places, bowling balls, as well as abstract areas like cubes
Duration of a temporal extent expressed as a number scaled by a temporal unit
A temporal entity with zero extent or duration
A temporal entity with non-zero extent or duration, for which the value of the beginning and end are different
A unit of measure is a definite magnitude of a quantity, defined and adopted by convention and/or by law. It is used as a standard for measurement of the same quantity, where any other value of the quantity can be expressed as a simple multiple of the unit of measure. For example, length is a quantity; the metre is a unit of length that represents a definite predetermined length. When we say 10 metre (or 10 m), we actually mean 10 times the definite predetermined length called "metre".
This is the amount of energy from a resource that was bid into a program
Signal that represents the price that was bid by the resource
This is the amount of load that was bid by a resource into a program
Signal that represents the amount of load that was bid by a resource into a program
This is the price that was bid by the resource
This is the delta amount of energy that should be contained in a storage resource from where it currently is.
This is the percentage of full charge that the storage resource should be at.
This is used to either charge or discharge a certain amount of energy from a storage resource until its charge state reaches a certain level.
Signal used to dispatch storage resources
These reports are used to report actual data that may be measured or calculated.
OpenADR 2.0 Demand Response Specification Profile B
This is the demand charge expressed in absolute terms
This is a multiplier to the existing demand charge
This is a delta change to the existing demand charge
This is the cost of electricity expressed in absolute terms
This is a multiplier to the existing cost of electricity
This is a delta change to the existing price of electricity
This is the cost of energy expressed in absolute terms
This is a multiplier to the existing cost of energy
This is a delta change to the existing price of energy
An event is a notification from the utility to demand side resources requesting load shed starting at a specific time, over a specified duration, and may include targeting information designating specific resources that should participate in the event
OpenADR 2.0 Demand Response Program Implementation Guide
Part of the OpenADR event object that describes metadata about the event, such as program name and event priority
This is usage history that can be transmitted using the well known GREEN BUTTON standard payloads
This is a type of data report in which the history of the data point values is logged and can be subsequently requested
These are logs of usage data that are typically logged by VEN’s and can be queried by the VTN
OASIS Energy Market Information Exchange (eMIX) standard
This is an instruction for the load controller to operate at a level that is some percentage of its maximum load consumption capacity. This can be mapped to specific load controllers to do things like duty cycling. Note that 1.0 refers to 100% consumption. In the case of simple ON/OFF type devices then 0 = OFF and 1 = ON.
Discrete integer levels that are relative to normal operations where 0 is normal operations. There is no requirement to link the setpoints to specific load consumption values, but the intention is that the higher the setpoint the less load is consumed. Note that these are controller set points that can be mapped at the VEN side to something as simple as thermostat temperature set point offsets.
Percentage change from normal operations. The percentage does not refer to specific load consumptions values, but to load control operation levels. The lower the percentage the less load is consumed.
Load controller set points. There is no requirement to link the setpoints to specific load consumption values. Note that these are generic controller set points and can be mapped at the VEN side to something as simple as specific thermostat temperature set points.
Signal for to set the load control to values that are relative to the load controller and its output capacity.
The LoadControlState attributes are meant to mirror the LOAD_CONTROL signal attributes meaning that for each LOAD_CONTROL signal type there is a corresponding attribute in the LoadControlState of a report.
This is used to dispatch loads to some offset from an agreed upon baseline. Note that the baseline may be the current power consumption.
This is used to specify the load in terms of discrete levels.
This is used to dispatch loads as some multiple of power against some agreed upon baseline. Note that the baseline may be the current power consumption.
This is used to dispatch loads to a specific amount
Instructions are used to set the load values that can be expressed in terms of the desired load
The metadata report can contain a specification for one or more type of reports, each report having its own set of report descriptors and specifications
Element that interacts with resources in the environment
The expected response from the demand side resource owner upon receipt of an event.
Report sent from a VEN to a VTN to report the energy consumption or the status of Resources connected to the VEN
Part of the OpenADR report object that describes the data included in the descriptor report
Part of the OpenADR report object that includes the data sent to a node
Part of the OpenADR report object that describes metadata about the report
Part of the OpenADR report object that describes the status of the descriptor report
Part of the OpenADR report object that includes the status of the payload report
Entity that is enrolled in the DR Programs and is capable of delivering some sort of change to their load profile in response to receiving a DR signal from a VTN.
The average number of samples obtained in one second
The Service Area expresses locations or geographic regions relevant to price communication
OASIS Energy Market Information Exchange (EMIX)
The actionable information contained in an event such as electricity pricing or specific levels of load shed requested that typically trigger some preprogrammed load shed behavior by the recipient of the event.
Interval of time where a signal is active
The term telemetry in the context of OpenADR refers to data that is reported periodically in real time
This is usage data that is periodically reported from the VEN to the VTN in real time
This is the status of a resource, which may be periodically reported from the VEN to the VTN
This is the OpenADR Virtual End Node that is used to interact with the VTN
This is the OpenADR Virtual Top Node that is used to interact with the Resources enrolled in the DR Programs.