MarketEvaluationPoint

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.

Tracks the lifecycle of the metering installation at a usage point with respect to readiness for billing via advanced metering infrastructure reads.

True if as a result of an inspection or otherwise, there is a reason to suspect that a previous billing may have been performed with erroneous data. Value should be reset once this potential discrepancy has been resolved.

All configuration events created for this usage point.

A code used to specify the connection category, e.g., low voltage or low pressure, where the usage point is defined.

State of the usage point with respect to connection to the network.

Customer agreement regulating this service delivery point.

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.

The diagram objects that are associated with the domain object.

Is an indication of how the usage point is physically connected or disconnected.

All end device controls sending commands to this usage point.

All end device events reported for this usage point.

All end devices at this usage point.

All equipment connecting this usage point to the electrical grid.

Estimated load.

True if grounded.

Dataset containing the data objects.

If true, this usage point is a service delivery point, i.e., a usage point where the ownership of the service changes hands.

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 company's 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.

All meter readings obtained from this usage point.

Meter read schedule that applies to the usage point

All meter service work tasks at this usage point.

All metrology requirements for this usage point.

If true, minimal or zero usage is expected at this usage point for situations such as premises vacancy, logical or physical disconnect. It is used for readings validation and estimation.

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.

All names of this identified object.

Nominal service voltage.

All outages at this Usage Point

Outage region in which this usage point is located.

Phase code. Number of wires and specific nominal phases can be deduced from enumeration literal values. For example, ABCN is three-phase, four-wire, s12n (splitSecondary12N) is single-phase, three-wire, and s1n and s2n are single-phase, two-wire.

Number of potential phases the Usage Point supports, typically 0, 1 or 3.

Quantitative information about the maximum physical capacity of the connection for the usage point.

The planned outage notification for the specified Usage Point.

All pricing structures applicable to this service delivery point (with prepayment meter running as a stand-alone device, with no CustomerAgreement or Customer).

The single CIM data object in the appropriate dataset context.

Current flow that this usage point is configured to deliver.

Active power that this usage point is configured to deliver.

Cycle day on which the meter for this usage point will normally be read. Usually correlated with the billing cycle.

Identifier of the route to which this usage point is assigned for purposes of meter reading. Typically used to configure hand held meter reading systems prior to collection of reads.

All registers for quantities metered at this Usage Point.

Service category delivered by this usage point.

Remarks about this usage point, for example the reason for it being rated with a non-nominal priority.

Service location where the service delivered by this usage point is consumed.

All multipliers applied at this usage point.

Priority of service for this usage point. Note that usage points at the same service location can have different priorities.

ServiceSupplier (utility) utilising this usage point to deliver a service.

Data objects registered.

All groups to which this usage point belongs.

Location of this usage point.