CustomerBillingInfo
The creation of the monthly customer billing statements is the method employed to notify Customers of charges, adjustments and credits applied to their account for Services and Products. The actuall billing occurs through an ErpInvoice. The CustomerBillingInfo includes information from the payment, collection, meter reading, installed meter, service, site, customer, customer account, customer agreement, services and pricing subject areas. Each component price shows up as a separate line item on the ErpInvoice. The Customer Billing Statement may include collection and account messages, marketing/civic event messages and bill inserts. One Customer Billing Statement is produced for all Agreements under a CustomerAccount per billing cycle date defined in 'CustomerAccount.billingCycle'. The history of CustomerBillingInfo, Invoices and Payments is to be maintained in associated ActivityRecords.
Type |
Class |
|---|---|
URI |
|
CIM standard (perspective) |
IEC61968 (Enterprise) |
Slots
| Name | Cardinality | Type | Description |
|---|---|---|---|
1 |
Dataset containing the data objects. |
||
0..1 |
n/a |
||
0..1 |
Business date designated for the billing run which produced this CustomerBillingInfo. |
||
0..1 |
Calculated date upon which a customer billing amount is due, used in the invoicing process to determine when a Customer's Payment is delinquent. It takes into consideration the regulatory criteria and the Customer's requested due date. In the absence of a Customer requested due date, the due date is typically calculated from the regulated number of days and the 'billingDate'. |
||
0..1 |
Kind of bill customer receives. |
||
0..1 |
Amount of the last payment received from the customer. It is retained in the Customer Billing system, although the details of each payment are tracked in the ERP system. |
||
0..1 |
Date of the last payment received from the customer. It is retained in the Customer Billing system, although the details of each payment are tracked in the ERP system. |
||
0..1 |
Outstanding balance on the CustomerAccount as of the statement date. |
||
0..1 |
Monthly amortized amount due during each billing cycle for the CustomerAccount balance for which the Payment Plan is set-up. |
||
0..1 |
Type of payment plan. |
||
0..* |
n/a |
||
0..1 |
Approver of this document. |
||
0..1 |
Author of this document. |
||
0..1 |
Editor of this document. |
||
0..1 |
Issuer of this document. |
||
0..1 |
The single CIM data object in the appropriate dataset context. |
||
0..1 |
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. |
||
0..1 |
Name of the author of this document. |
||
0..1 |
Free text comment. |
||
0..1 |
Date and time that this document was created. |
||
0..1 |
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. |
||
0..1 |
Status of this document. For status of subject matter this document represents (e.g., Agreement, Work), use 'status' attribute. Example values for 'docStatus.status' are draft, approved, cancelled, etc. |
||
0..1 |
Electronic address. |
||
0..1 |
Date and time this document was last modified. Documents may potentially be modified many times during their lifetime. |
||
0..1 |
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. |
||
0..1 |
The name is any free human readable and possibly non unique text naming the object. |
||
0..1 |
Revision number for this document. |
||
0..1 |
Status of subject matter (e.g., Agreement, Work) this document represents. For status of the document itself, use 'docStatus' attribute. |
||
0..1 |
Document subject. |
||
0..1 |
Document title. |
||
0..1 |
Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.). |
||
0..* |
The activity record for a document |
||
0..* |
All configuration events created for this document. |
||
0..* |
The diagram objects that are associated with the domain object. |
||
0..* |
All names of this identified object. |
||
0..* |
Data objects registered. |
ActivityRecord
The activity record for a document
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
aliasName
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.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
authorName
Name of the author of this document.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
billingDate
Business date designated for the billing run which produced this CustomerBillingInfo.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
ConfigurationEvents
All configuration events created for this document.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
createdDateTime
Date and time that this document was created.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
description
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.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
DiagramObjects
The diagram objects that are associated with the domain object.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
docStatus
Status of this document. For status of subject matter this document represents (e.g., Agreement, Work), use 'status' attribute. Example values for 'docStatus.status' are draft, approved, cancelled, etc.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
dueDate
Calculated date upon which a customer billing amount is due, used in the invoicing process to determine when a Customer's Payment is delinquent. It takes into consideration the regulatory criteria and the Customer's requested due date. In the absence of a Customer requested due date, the due date is typically calculated from the regulated number of days and the 'billingDate'.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
electronicAddress
Electronic address.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
InstanceSet
Dataset containing the data objects.
URI |
|
|---|---|
Cardinality |
1 |
Type |
|
Inherited from |
lastModifiedDateTime
Date and time this document was last modified. Documents may potentially be modified many times during their lifetime.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
lastPaymentAmt
Amount of the last payment received from the customer. It is retained in the Customer Billing system, although the details of each payment are tracked in the ERP system.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
lastPaymentDate
Date of the last payment received from the customer. It is retained in the Customer Billing system, although the details of each payment are tracked in the ERP system.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
mRID
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.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
name
The name is any free human readable and possibly non unique text naming the object.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
Names
All names of this identified object.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
outBalance
Outstanding balance on the CustomerAccount as of the statement date.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
PropertiesCIMDataObject
The single CIM data object in the appropriate dataset context.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
pymtPlanAmt
Monthly amortized amount due during each billing cycle for the CustomerAccount balance for which the Payment Plan is set-up.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
revisionNumber
Revision number for this document.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
status
Status of subject matter (e.g., Agreement, Work) this document represents. For status of the document itself, use 'docStatus' attribute.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |