A Profile of the IEC Common Information Model for Smart Grids, developed by the Cerise-SG project.
Current status information relevant to an entity.
This package contains the information classes that support distribution management in general.
The IEC 61968 subpackages of the CIM are developed, standardized and maintained by IEC TC57 Working Group 14: interfaces for distribution management (WG14). Currently, normative parts of the model support the needs of information exchange defined in IEC 61968-3, IEC 61968-4, IEC 61968-9 and in IEC 61968-13.
Function performed by an end device such as a meter, communication equipment, controllers, etc.
This package contains the core information classes that support end device applications with specialized classes for metering and premise are network devices, and remote reading functions. These classes are generally associated with the point where a service is delivered to the customer.
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).
Street details, in the context of address.
Asset container that performs one or more end device functions. One type of end device is a meter which can perform metering, load management, connect/disconnect, accounting functions, etc. Some end devices, such as ones monitoring and controlling air conditioner, refrigerator, pool pumps may be connected to a meter. All end devices may have communication capability defined by the associated communication function(s). An end device may be owned by a consumer, a service provider, utility or otherwise. There may be a related end device function that identifies a sensor or control point within a metering application or communications systems (e.g., water, gas, electricity). Some devices may use an optical port that conforms to the ANSI C12.18 standard for communications.
Lifecycle states of the metering installation at a usage point with respect to readiness for billing via advanced metering infrastructure reads.
Detailed description for a type of a reading value. Values in attributes allow for creation of recommended codes to be used for identifying reading value types as follows: <macroPeriod>.<aggregate>.<measuringPeriod>.<accumulation>.<flowDirection>.<commodity>.<measurementKind>.<interharmonic.numerator>.<interharmonic.denominator>.<argument.numerator>.<argument.denominator>.<tou>.<cpp>.<consumptionTier>.<phases>.<multiplier>.<unit>.<currency>.
Common representation for reading values. Note that a reading value may have multiple qualities, as produced by various systems ('ReadingQuality.source').
This is a root class to provide common identification for all classes needing identification and naming attributes.
Contains the core PowerSystemResource and ConductingEquipment entities shared by all applications plus common collections of those entities. Not all applications require all the Core entities. This package does not depend on any other package except the Domain package, but most of the other packages have associations and generalizations that depend on it.
This package contains the core information classes that support customer billing applications.
Category of service provided to the customer.
General purpose street address information.
Set of spatial coordinates that determine a point, defined in coordinate system specified in 'Location.CoordinateSystem'. Use a single position point instance to desribe a point-oriented location. Use a sequence of position points to describe a line-oriented object (physical location of non-point oriented objects like cables or lines), or area of an object (like a substation or a geographical zone - in this case, have first and last position point with the same values).
This package is an extension of the Metering package and contains the information classes that support specialised applications such as prepayment metering. These classes are generally associated with the collection and control of revenue from the customer for a delivered service.
The place, scene, or point of something where someone or something has been, is, and/or will be at a given moment in time. It can be defined with one or more postition points (coordinates) in a given coordinate system.
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.
Simple end device function distinguished by 'kind'. Use this class for instances that cannot be represented by another end device function specialisations.
Physical asset that performs the metering role of the usage point. Used for measuring consumption and detection of events.
Agreement between the customer and the service supplier to pay for service at a specific service location. It records certain billing information about the type of service provided at the service location and is used during charge creation to determine the type of service.
Specific value measured by a meter or other asset, or calculated by a system. Each Reading is associated with a specific ReadingType.
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.
Organisation that provides services to customers.
Identifies a way in which an organisation may participate in the utility enterprise (e.g., customer, manufacturer, etc).
Organisation receiving services from service supplier.
Town details, in the context of address.
Interval between two date and time points.
The domain package define primitive datatypes that are used by classes in other packages. Stereotypes are used to describe the datatypes. The following stereotypes are defined: <<enumeration>> A list of permissible constant values. <<Primitive>> The most basic data types used to compose all other data types. <<CIMDatatype>> A datatype that contains a value attribute, an optional unit of measure and a unit multiplier. The unit and multiplier may be specified as a static variable initialized to the allowed value. <<Compound>> A composite of Primitive, enumeration, CIMDatatype or othe Compound classes, as long as the Compound classes do not recurse.
Coordinate system used to describe position points of this location.
Meter reading containing this interval block.
All meter readings provided by this meter.
Interval reading contained in this block.
Usage point from which this meter reading (set of values) has been obtained.
All reading values contained within this meter reading.
ServiceSupplier (Utility) utilising this usage point to deliver a service.
Type information for this reading value.
All end device functions this end device performs.
All meter readings (sets of values) containing this reading value.
All meter readings obtained from this usage point.
Service supplier for this customer agreement.
Tracks the lifecycle of the metering installation at a usage point with respect to readiness for billing via advanced metering infrastructure reads.
All blocks containing this interval reading.
All locations described with position points in this coordinate system.
Location described by this position point.
Customer agreement regulating this service delivery point.
Sequence of position points describing this location, expressed in coordinate system 'Location.CoordinateSystem'.
Secondary address of the location. For example, PO Box address may have different ZIP code than that in the 'mainAddress'.
Service category delivered by this usage point.
Date and time interval of the data items contained within this meter reading.
Usage point to which this end device belongs.
(could be deprecated in the future) Customer agreement for this meter reading.
Start and end of the period for those readings whose type has a time attribute such as 'billing', seasonal' or 'forTheSpecifiedPeriod'.
Type information for interval reading values contained in this block.
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'.
If true, this usage point is virtual, i.e., no physical location exists in the network where a meter could be located to collect the meter readings. For example, one may define a virtual usage point to serve as an aggregation of usage for all of a companies premises distributed widely across the distribution territory. Otherwise, the usage point is physical, i.e., there is a logical point in the network where a meter could be located to collect meter readings.
The name is any free human readable and possibly non unique text naming the object.
Main (local) part of this telephone number.
Designator of the specific location on the street.
Unique transaction reference prefix number issued to an entity by the International Standards Organisation for the purpose of tagging onto electronic financial transactions, as defined in ISO/IEC 7812-1 and ISO/IEC 7812-2.
(if applicable) Utilities often make use of external reference systems, such as those of the town-planner's department or surveyor general's mapping system, that allocate global reference codes to streets.
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
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).
If true, there is no physical device. As an example, a virtual meter can be defined to aggregate the consumption for two or more physical meters. Otherwise, this is a physical hardware device.
System that originally supplied the reading (e.g., customer, AMI system, handheld reading system, another enterprise system, etc.).
Suffix to the street name. For example: North, South, East, West.
Master resource identifier issued by a model authority. The mRID must semantically be a UUID as specified in RFC 4122. The mRID is globally unique. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
Additional address information, for example a mailstop.
Status value at 'dateTime'; prior status changes may have been kept in instances of activity records associated with the object to which this status applies.
True if this street is within the legal geographical boundaries of the specified town (default).
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 sytem that receives readings directly from the meter therefore must 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).
Pertinent information regarding the current 'value', as free form text.
Classification by utility's corporate standards and practices, relative to the location itself (e.g., geographical, functional accounting, etc., not a given property that happens to exist at that location).
(if applicable) Extension for this telephone number.
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.
Town section. For example, it is common for there to be 36 sections per township.
Date and time for which status 'value' applies.
If true, this usage point is a service delivery point, i.e., a usage point where the ownership of the service changes hands.
A Uniform Resource Name (URN) for the coordinate reference system (crs) used to define 'Location.PositionPoints'. An example would be the European Petroleum Survey Group (EPSG) code for a coordinate reference system, defined in URN under the Open Geospatial Consortium (OGC) namespace as: urn:ogc :def:uom:EPSG::XXXX, where XXXX is an EPSG code (a full list of codes can be found at the EPSG Registry website http://www.epsg-registry.org/). To define the coordinate system as being WGS84 (latitude, longitude) using an EPSG OGC, this attribute would be urn:ogc:def:uom:EPSG::4236. A profile should limit this code to a set of allowed URNs agreed to by all sending and receiving parties.
Meter form designation per ANSI C12.10 or other applicable standard. An alphanumeric designation denoting the circuit arrangement for which the meter is applicable and its specific terminal arrangement.
Prefix to the street name. For example: North, South, East, West.
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time.
(if applicable) In certain cases the physical location of the place of interest does not have a direct point of entry from the street, but may be located inside a larger structure such as a building, complex, office block, apartment, etc.
User ID needed to log in, which can be for an individual person, an organisation, a location, etc.
Zero-relative sequence number of this point within a series of points.
Reason code or explanation for why an object went to the current status 'value'.
(if applicable) Reference to geographical information source, often external to the utility.
Type of street. Examples include: street, circle, boulevard, avenue, road, drive, etc.
Residential streetlight or other related customer.
Detection and monitoring of reverse flow.
Usage point is equipped with a non AMI capable meter.
Usage point is equipped with an AMI capable meter having communications capability.
Usage point is equipped with an AMI capable meter; however, the AMI functionality has been disabled or is not being used.
Usage point is equipped with an AMI capable meter that is functioning and communicating with the AMI network.
Presentation of metered values to a user or another system (always a function of a meter, but might not be supported by a load control unit).
Meter kh (watthour) constant. The number of watthours that must be applied to the meter to cause one disk revolution for an electromechanical meter or the number of watthours represented by one increment pulse for an electronic meter.
Potential transformer ratio used to convert associated quantities to real measurements.
Reporting historical power interruption data.
Usage point is equipped with an AMI capable meter that is not yet currently equipped with a communications module.
Support for one or more relays that may be programmable in the meter (and tied to TOU, time pulse, load control or other functions).
Usage point is equipped with an operating AMI capable meter and accuracy has been certified for billing purposes.
Current transformer ratio used to convert associated quantities to real measurements.
Entity that delivers the service to the customer.
Register multiplier. The number to multiply the register reading by in order to get kWh.
Usage point is not currently equipped with a meter.
Autonomous application of daylight savings time (DST).
Rates (e.g. tax, charge, toll, duty, tariff, etc.) service.
Entity that sells the service, but does not deliver to the customer; applies to the deregulated markets.