EUMED Metering Ontology

• time period ^op
• values interval ^op

Kind of accumulation behaviour for read or measured values from individual end points.

Kind of aggregation for read or measured values from multiple end points.

Kind of commodity being measured.

Monetary currencies. ISO 4217 standard including 3-character currency code.

Organisation receiving services from service supplier.

• has kind ^op
• owns meter ^op

Kind of customer.

TBA

• accumulation kind ^c
• aggregate kind ^c
• commodity kind ^c
• currency ^c
• customer kind ^c
• flow direction kind ^c
• macro period kind ^c
• eme:MeasurementKind ^c
• measuring period kind ^c
• phase code ^c
• unit multiplier ^c
• unit symbol ^c

TBA

• customer ^c
• interval block ^c
• interval reading ^c
• meter ^c
• meter reading ^c
• meter reading set ^c
• name ^c
• name type ^c
• name type authority ^c
• reading quality ^c
• reading type ^c
• usage point ^c
• usage point location ^c

Kind of flow direction for reading/measured values proper to some commodities such as, for example, energy, power, demand.

Time sequence of readings of the same reading type. Contained interval readings may need conversion through the application of an offset and a scalar defined in associated pending.

• eme:hasReadingType ^op
• is composed of interval readings ^op

• is composed of interval blocks ^op
• is part of interval block ^op
• is used by interval block ^op

Data captured at regular intervals of time. Interval data could be captured as incremental data, absolute data, or relative data. The source for the data is usually a tariff quantity or an engineering quantity. Data is typically captured in time-tagged, uniform, fixed-length intervals of 5 min, 10 min, 15 min, 30 min, or 60 min. Note: Interval Data is sometimes also called "Interval Data Readings" (IDR).

• eme:hasReadingQuality ^op
• time period ^op
• is part of interval block ^op
• time stamp ^dp
• value ^dp

• applies to interval reading ^op
• is composed of interval readings ^op

Kind of macro period for calculations on read or measured values.

Kind of period for reading or measuring values

Physical asset that performs the metering role of the usage point. Used for measuring consumption and detection of events.

• is owned by customer ^op
• provides meter readings ^op
• install code ^dp

• is provided by meter ^op
• owns meter ^op

Set of values obtained from the meter.

• values interval ^op
• is composed of interval blocks ^op
• is provided by meter ^op
• is obtained by usage point ^op

• has meter readings ^op
• is composed of meter readings ^op
• provides meter readings ^op

encapsulates a set of Meter Readings (container of measured values), Usage Points (points related to the measurements) and Reading Types (characterization of the kind of the measured values).

• is composed of meter readings ^op
• is composed of reading types ^op
• is composed of usage points ^op

The Name class provides the means to define any number of human readable names for an object. A name is not to be used for defining inter-object relationships. For inter-object relationships instead use the object identification 'mRID'.

• has name as reading type ^op
• has name as usage point ^op

Type of name. Possible values for attribute 'name' are implementation dependent but standard profiles may specify types. An enterprise may have multiple IT systems each having its own local name for the same object, e.g. a planning system may have different names from an EMS. An object may also have different names within the same IT system, e.g. localName as defined in CIM version 14. The definition from CIM14 is: The localName is a human readable name of the object. It is a free text name local to a node in a naming hierarchy similar to a file directory structure. A power system related naming hierarchy may be: Substation, VoltageLevel, Equipment etc. Children of the same parent in such a hierarchy have names that typically are unique among them.

Authority responsible for creation and management of names of a given type; typically an organization or an enterprise system.

An unordered enumeration of phase identifiers. Allows designation of phases for both transmission and distribution equipment, circuits and loads. The enumeration, by itself, does not describe how the phases are connected together or connected to ground. Ground is not explicitly denoted as a phase. Residential and small commercial loads are often served from single-phase, or split-phase, secondary circuits. For the example of s12N, phases 1 and 2 refer to hot wires that are 180 degrees out of phase, while N refers to the neutral wire. Through single-phase transformer connections, these secondary circuits may be served from one or two of the primary phases A, B, and C. For three-phase loads, use the A, B, C phase codes instead of s12N. The integer values are from IEC 61968-9 to support revenue metering applications.

Quality of a specific reading value or interval reading value. Note that more than one quality may be applicable to a given reading. Typically not used unless problems or unusual conditions occur (i.e., quality for each reading is assumed to be good unless stated otherwise in associated reading quality type). It can also be used with the corresponding reading quality type to indicate that the validation has been performed and succeeded.

• applies to interval reading ^op
• comment ^dp

Detailed description for a type of a reading value. Values in attributes allow for the creation of recommended codes to be used for identifying reading value types as follows: ..................

• has accumulation ^op
• eme:hasAggregate ^op
• has commodity ^op
• has currency ^op
• has flow direction ^op
• has macro period ^op
• has measurement kind ^op
• eme:hasMeasuringPeriod ^op
• has multiplier ^op
• has name as reading type ^op
• has phases ^op
• has unit ^op
• is used by interval block ^op
• consumption tier ^dp
• cpp ^dp
• rational number ^dp
• reading interharmonic ^dp
• tou ^dp

• eme:hasReadingType ^op
• is composed of reading types ^op

The unit multipliers defined for the CIM. When applied to unit symbols, the unit symbol is treated as a derived unit. Regardless of the contents of the unit symbol text, the unit symbol shall be treated as if it were a single-character unit symbol. Unit symbols should not contain multipliers, and it should be left to the multiplier to define the multiple for an entire data type.

For example, if a unit symbol is "m2Pers" and the multiplier is "k", then the value is k(m**2/s), and the multiplier applies to the entire final value, not to any individual part of the value. This can be conceptualized by substituting a derived unit symbol for the unit type. If one imagines that the symbol "Þ" represents the derived unit "m2Pers", then applying the multiplier "k" can be conceptualized simply as "kÞ".

For example, the SI unit for mass is "kg" and not "g". If the unit symbol is defined as "kg", then the multiplier is applied to "kg" as a whole and does not replace the "k" in front of the "g". In this case, the multiplier of "m" would be used with the unit symbol of "kg" to represent one gram. As a text string, this violates the instructions in IEC 80000-1. However, because the unit symbol in CIM is treated as a derived unit instead of as an SI unit, it makes more sense to conceptualize the "kg" as if it were replaced by one of the proposed replacements for the SI mass symbol. If one imagines that the "kg" were replaced by a symbol "Þ", then it is easier to conceptualize the multiplier "m" as creating the proper unit "mÞ", and not the forbidden unit "mkg".

The derived units defined for usage in the CIM. In some cases, the derived unit is equal to an SI unit. Whenever possible, the standard derived symbol is used instead of the formula for the derived unit. For example, the unit symbol Farad is defined as "F" instead of "CPerV". In cases where a standard symbol does not exist for a derived unit, the formula for the unit is used as the unit symbol. For example, density does not have a standard symbol and so it is represented as "kgPerm3". With the exception of the "kg", which is an SI unit, the unit symbols do not contain multipliers and therefore represent the base derived unit to which a multiplier can be applied as a whole. Every unit symbol is treated as an unparseable text as if it were a single-letter symbol. The meaning of each unit symbol is defined by the accompanying descriptive text and not by the text contents of the unit symbol. To allow the widest possible range of serializations without requiring special character handling, several substitutions are made which deviate from the format described in IEC 80000-1. The division symbol "/" is replaced by the letters "Per". Exponents are written in plain text after the unit as "m3" instead of being formatted as "m" with a superscript of 3 or introducing a symbol as in "m^3". The degree symbol "°" is replaced with the letters "deg". Any clarification of the meaning for a substitution is included in the description for the unit symbol. Non-SI units are included in list of unit symbols to allow sources of data to be correctly labelled with their non-SI units (for example, a GPS sensor that is reporting numbers that represent feet instead of meters). This allows software to use the unit symbol information correctly convert and scale the raw data of those sources into SI-based units. The integer values are used for harmonization with IEC 61850.

Logical or physical point in the network to which readings or events may be attributed. Used at the place where a physical or virtual meter may be located; however, it is not required that a meter be present.

• has meter readings ^op
• has name as usage point ^op
• locates usage point ^op
• usage point usage point location ^op

• is composed of usage points ^op
• is obtained by usage point ^op

Location of an individual usage point.

• locates usage point ^op
• usage point usage point location ^op

Reading value to which this quality applies.

Accumulation behaviour of a reading over time, usually 'measuringPeriod', to be used with individual endpoints (as opposed to 'macroPeriod' and 'aggregate' that are used to describe aggregations of data from individual endpoints).

• Salient attribute of the reading data aggregated from individual endpoints. This is mainly used to define a mathematical operation carried out over 'macroPeriod', but may also be used to describe an attribute of the data when the 'macroPeriod' is not defined.

• has aggregate

Commodity being measured.

Metering-specific currency.

Flow direction for a reading where the direction of flow of the commodity is important (for electricity measurements this includes current, energy, power, and demand).

Kind of customer.

Time period of interest that reflects how the reading is viewed or captured over a long period of time.

Identifies "what" is being measured, as refinement of 'commodity'. When combined with 'unit', it provides detail to the unit of measure. For example, 'energy' with a unit of measure of 'kWh' indicates to the user that active energy is being measured, while with 'kVAh' or 'kVArh', it indicates apparent energy and reactive energy, respectively. 'power' can be combined in a similar way with various power units of measure: Distortion power ('distortionVoltAmperes') with 'kVA' is different from 'power' with 'kVA'.

• Time attribute inherent or fundamental to the reading value (as opposed to 'macroPeriod' that supplies an "adjective" to describe aspects of a time period with regard to the measurement). It refers to the way the value was originally measured and not to the frequency at which it is reported or presented. For example, an hourly interval of consumption data would have value 'hourly' as an attribute. However in the case of an hourly sampled voltage value, the meterReadings schema would carry the 'hourly' interval size information. It is common for meters to report demand in a form that is measured over the course of a portion of an hour, while enterprise applications however commonly assume the demand (in kW or kVAr) normalised to 1 hour. The system that receives readings directly from the meter therefore shall perform this transformation before publishing readings for use by the other enterprise systems. The scalar used is chosen based on the block size (not any sub-interval size).

• has measuring period

All meter readings obtained from this usage point.

Metering-specific multiplier.

All names of this reading type.

All names of this usage point.

Type of this name.

Authority responsible for managing names of this type.

Metering-specific phase code.

• has reading qualities

• All qualities of this reading.

• Type information for interval reading values contained in this block.

• has reading type

Start and end of the period for those readings whose type has a time attribute such as 'billing', seasonal' or 'forTheSpecifiedPeriod'.

Metering-specific unit.

All usage points at this location.

Date and time interval of the data items contained within this meter reading.

All interval blocks contained in this meter reading.

Interval reading contained in this block.

TBA

TBA

TBA

Location of this usage point.

• TBA

• is meter reading as part of meter reading set

Customer owning this end device.

Interval block containing this interval reading.

Meter providing this reading.

TBA

Usage point from which this meter reading (set of values) has been obtained.

All blocks containing interval reading values with this type information.

All end devices of this customer.

All meter readings provided by this meter.

Elaboration on the quality code.

In case of common flat-rate pricing for power, in which all purchases are at a given rate, 'consumptionTier'=0. Otherwise, the value indicates the consumption tier, which can be used in conjunction with TOU or CPP pricing. Consumption tier pricing refers to the method of billing in which a certain "block" of energy is purchased/sold at one price, after which the next block of energy is purchased at another price, and so on, all throughout a defined period. At the start of the defined period, consumption is initially zero, and any usage is measured against the first consumption tier ('consumptionTier'=1). If this block of energy is consumed before the end of the period, energy consumption moves to be reconed against the second consumption tier ('consumptionTier'=2), and so on. At the end of the defined period, the consumption accumulator is reset, and usage within the 'consumptionTier'=1 restarts.

Critical peak period (CPP) bucket the reading value is attributed to. Value 0 means not applicable. Even though CPP is usually considered a specialised form of time of use 'tou', this attribute is defined explicitly for flexibility.

(if applicable) Reference to geographical information source, often external to the utility.

Installation code.

Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.

The name is any free human readable and possibly non unique text naming the object.

Rational number = 'numerator' over 'denominator'.

Interharmonics are represented as a rational number 'numerator' over 'denominator', and harmonics are represented using the same mechanism and identified by 'denominator'=1.

The time when the value was last updated.

Time of use (TOU) bucket the reading value is attributed to. A value of “0” means that TOU is not applicable to this measurement.

Value of interval reading.