The logical data model of the Oracle Utilities Data Model defines the business entities and their relationships and provides an understanding of the business and data requirements for the Oracle Utilities Data Model data warehouse.
This chapter includes the following sections:
The following describes the main entities related to some major or typical subject areas in Oracle Utilities Data Model:
Note:
The entity-relationship figures of the major reference entities in those subject areas are available with the Oracle Utilities Data Model IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Utilities Data Model patch sets, go to My Oracle Support at https://support.oracle.com.
Entities of Subject Area: Account
This subject area contains major classes relevant to account and their relationships. This section lists the entities associated with the subject area Account.
Account
Account Accounting Cycle History
Account Assignment
Account Assignment Reason
Account Assignment Type
Account Balance Adjustment
Account Balance Bucket
Account Balance Group
Account Balance Impact
Account Balance Type
Account Billing Cycle History
Account Billing Frequency History
Account Billing Occurrence
Account Billing Period History
Account Management History
Account Payment
Account Payment Method Status
Account Payment Method Status Reason
Account Payment Method Status Type
Account Preferred Invoice Delivery
Account Preferred Payment Method
Account Profile
Account Role Type
Account Segment
Account Segment Assignment History
Account Segmentation Model
Account Status History
Account Status Reason
Account Status Type
Account Type
Accounting Cycle
Address Location
Bank Direct Debit Channel
Billing Cycle
Billing Frequency
Billing Occurrence Type
Billing Period
Credit Category
Currency
Customer
Customer Account Assignment
Event Invoice Delivery
Invoice
Invoice Delivery Type
Language
Organization Business Unit
Party
Party Account Assignment
Payment Method Type
Segment Criteria
Segment Type
Unit Of Measure
Entities of Subject Area: Account Balance
Account
Account Adjustment Reason
Account Balance Adjustment
Account Balance Adjustment Type
Account Balance Bucket
Account Balance Group
Account Balance History
Account Balance Type
Entities of Subject Area: Account Credit Limit
Account
Account Credit Limit
Credit Category
Currency
Debt Aging Band
Payment Aging Class
Product Subscription
Entities of Subject Area: Agreement
Account
Account Agreement Relationship
Agreement
Agreement Approval
Agreement Assignment
Agreement Assignment Reason
Agreement Assignment Type
Agreement Document
Agreement Item
Agreement Status
Agreement Status Type
Agreement Type
Customer
Customer Account Assignment
Customer Document
Customer Order
Document Type
Installment Agreement
Invoice
Invoice Payment Term Type
Party Agreement Relationship
Promotion
This subject area contains the core information that support asset management applications that deal with the physical and lifecycle aspects of various network resources.
Activity Record
Asset
Asset Activity Record Assignment
Asset Container
Asset Function
Asset Info
Asset Location
Asset Model
Asset Model Catalog
Asset Model Catalog Item
Asset Organization Role
Asset Organization Role Assignment
Asset Owner
Asset PSR Assignment
Asset Type
Asset User
Bushing
Com Media
Com Module
Compatible Unit
Compatible Unit Procedure Assignment
Configuration Event
Customer
End Device
End Device FunctionFACTS DeviceFinancial Info
Joint
Manufacturer
Measurement
Operation Tag
Pole
Power System Resource
Procedure
Procedure Asset Assignment
Product Asset Model
Product Asset Model Function Assignment
Scheduled Event
Scheduled Event Asset Assignment
Seal
Streetlight
Structure
Structure Support
Tower
Underground Structure
Work Asset
Work Task
Work Task Asset Assignment
Entities of Subject Area: Asset Information Classes
Asset Info
Busbar Section Info
Composite Switch Info
Current Transformer Info
End Device Info
Fault Indicator Info
Potential Transformer Info
Power Transformer Info
Protection Equipment Info
Shunt Compensator Info
Surge Arrester Info
Switch Info
Tap Changer Info
Transformer End Info
Transformer Tank Info
Wire Info
Wire Spacing Info
Entities of Subject Area: Billing
Account
Account Billing Cycle History
Account Billing Frequency History
Account Billing Occurrence
Account Billing Period History
Account Payment
Account Preferred Payment Method
Account Refund
Billing Cycle
Billing Frequency
Billing Period
Currency
Employee
Employee Job Role Assignment
Event Invoice Delivery
Invoice
Invoice Adjustment
Invoice Adjustment Quota
Invoice Delivery Format
Invoice Delivery Type
Invoice Discount
Invoice Discount Reason
Invoice Discount Type
Invoice Item
Invoice Item Detail
Invoice Item Detail Type
Invoice Item Relationship
Invoice Item Type
Invoice Payment Assignment
Invoice Payment Term
Invoice Status History
Invoice Status Type
Job Role
Language
Organization Business Unit
Price Event
Price Type
Tax Category
Unit Of Measure
Entities of Subject Area: Business Events
This subject area provides the common base for business events.
Account Event Type
Address Location
Campaign Channel
Channel
Event
Event Account
Event Assignment
Event Assignment Reason
Event Assignment Type
Event Category
Event Class
Event Employee Payroll
Event Equipment Instance
Event Geography
Event Invoice Delivery
Event Loyalty Program
Event Party Assignment
Event Party Interaction
Event Party Profile
Event Party Role
Event Reason
Event Reason Category
Event Resolution
Event Response Reason
Event Result
Event Status
Event Status Reason
Event Status Type
Event Type
GL Account
Invoice
Invoice Delivery Type
Loyalty Program Event Type
Organization Business Unit
Party
Party Event Type
Entities of Subject Area: Business Interaction
This subject area provides the common base for business interaction as an arrangement, contract, communication, or joint activity.
Account
Account Business Interaction Role
Appointment
Appointment Type
Base Work
Business Interaction
Business Interaction Assignment
Business Interaction Assignment Type
Business Interaction Item
Business Interaction Item Price
Business Interaction Location Assignment
Business Interaction Role
Business Interaction Status History
Business Interaction Status Reason
Business Interaction Status Type
Business Interaction Type
Business Interaction Version
Customer
Customer Account Assignment
Party
Party Business Interaction Role
Product Subscription
Purchase Order
Purchase Order Line Item
Resource Order
Resource Order Item
Service
Service Order
Service Order Line Item
Work Order
Work Task
Entities of Subject Area: Channel
This subject area identifies all the channels through which customers interact with the utility company for campaign, promotion, sales, or services purposes.
Bank Direct Debit Channel
Campaign Channel
Campaign Channel Type
Channel
Channel Type
Event
Event Party Interaction
Interaction Channel
Party
Payment Channel
Sales Channel
Entities of Subject Area: Connectivity Model
This subject area provides connectivity information among power systems resources through connectivity node.
AC Line Segment
ACDC Terminal
Base Voltage
Breaker
Clamp
Conducting Equipment
Connectivity Node
Connectivity Node Container
Cut
DC Conducting Equipment
DC Line Segment
Energy Consumer
Equipment
Equipment Container
Generating Unit
Jumper
Jumper Action
Measurement
Operational Limit Set
Operational Restriction
Outage
PSR Type
Power System Resource
Power System Resource Location
Power Transformer
Power Transformer End
Protected Switch
Recloser
Regulating Cond Eq
Substation
Switch
Switch Action
Switch Phase
Switch Switching Operation Assignment
Switching Operation
Synchrocheck Relay
Terminal
Topological Node
Transformer Tank
Usage Point
Usage Point Equipment Assignment
Entities of Subject Area: Cost
This subject area contains major classes relevant to cost which might incurred from any operation or event which can be tracked at certain level.
Account
Accounting Item Category
Cost
Cost Reason
Cost Subtype
Cost Type
GL Account
Party
Party Cost Assignment
Project
Project Element
Entities of Subject Area: Generation Curve Schedule Model
A multi-purpose curve or functional relationship between an independent variable (X-axis) and dependent (Y-axis) variables.
Basic Interval Schedule
Curve
Curve Data
Irregular Interval Schedule
Irregular Time Point
Regular Interval Schedule
Regular Time Point
This subject area contains the core information that supports customer management.
Account
Account Payment
Address Location
Agreement
Agreement Usage Point Assignment
Baring Reason
Black List History
Calendar Month
Credit Score Provider
Customer
Customer Account Assignment
Customer Group
Customer Group Assignment
Customer Individual
Customer Mining
Customer Occasion
Customer Occasion Type
Customer Organization
Customer Restricted Info
Customer Revenue Band
Customer Revenue Band Assignment
Customer SIC Assignment
Customer Score
Customer Segment
Customer Segmentation Model
Customer Source
Customer Type
Derived Value
Education
External Credit Profile
External Credit Profile Assignment
External Organization Type
Gender
Household
Initiative Result Type
Interaction Type
Invoice
Job
Language
Marital Status
Nationality
Party
Party Promotion Response
Party Status Change Reason
Party Status History
Promotion
Prospect
SOC Job
SOC Job Category
SOC Job Group
Segment Criteria
Unit Of Measure
Usage Point
Value Type
Entities of Subject Area: Customer Account and Agreement
This subject area presents a simplified view on the relationship between customer, account, and agreement.
Account
Account Type
Agree Item Pricing Struct Assignment
Agreement
Agreement Item
Agreement Type
Agreement Usage Point Assignment
Customer
Customer Account Assignment
Customer Type
Pricing Structure
Usage Point
Entities of Subject Area: Demand Response Program
Agreement
Customer
Customer Mining
DR Prog End Device Grp Assignment
DR Program Agreement Assignment
Demand Response Program
End Device Group
Usage Point Group
Entities of Subject Area: Employee
Business Unit Job Role
Employee
Employee Actual Labor Hourly
Employee Cost
Employee Designation
Employee Job Role Assignment
Employee Job Role Type
Employee Language Capability
Employee Restricted Info
Employee Schedule
Employee Training Record
Employee Type
Job Role
Organization Business Unit
Party
Entities of Subject Area: End Device Control
This subject area contains core information on end device control (or an end device group) to perform a specified action.
End Device
End Device Control
End Device Control Type
End Device Ctrl Primary Device Timing
End Device Ctrl Secondary Device Timing
End Device End Device Ctrl Assignment
End Device End Device Grp Assignment
End Device Group
Meter
Usage Point
Usage Point Group
Usage Point Grp End Device Ctrl Assignment
Entities of Subject Area: End Device Event
This subject area contains core information on end device event detected by a device function associated with end device.
End Device
End Device End Device Ctrl Assignment
End Device Event
End Device Event Detail
End Device Event Type
End Device Group
Meter
Meter Reading
Usage Point
Entities of Subject Area: Financial
This subject area contains the major classes on financial part of the utility business. Tariff and Pricing Structure are included and linked to Invoice and Agreement, respectively.
Account
Agree Item Pricing Struct Assignment
Agreement
Agreement Item
Cost
GL Account
GL Journal Entry
GL Ledger
GL Ledger Account Assignment
Invoice
Invoice Item
Invoice Item Detail
Invoice Item Detail Type
Pricing Structure
Pricing Structure Tariff Assignment
Tariff
Tariff Profile
Tariff Tariff Profile Assignment
Entities of Subject Area: Generating Unit
Air Compressor
CAES Plant
Cogeneration Plant
Combined Cycle Plant
Curve
Gen Unit Op Cost Curve
Gen Unit Op Schedule
Generating Unit
Generating Unit Rotating Machine Assignment
Gross To Net Active Power Curve
Hydro Generating Unit
Nuclear Generating Unit
Power System Resource
Regular Interval Schedule
Rotating Machine
Steam Sendout Schedule
Synchronous Machine
Thermal Generating Unit
Wind Generating Unit
Entities of Subject Area: Line Model
This area includes major classes relevant to the transmission line model to support network operation.
AC Line Segment
Conducting Equipment
Conductor
Equipment
Equipment Container
Line
Per Length Impedance
Per Length Phase Impedance
Per Length Sequence Impedance
Phase Impedance Data
Power System Resource
Series Compensator
Sub Geographical Region
Entities of Subject Area: Load Model
Conducting Equipment
Conform Load
Conform Load Group
Conform Load Schedule
Day Type
Energy Area
Energy Consumer
Equipment
Equipment Container
Load Area
Load Group
Load Response Characteristic
Non Conform Load
Non Conform Load Group
Non Conform Load Schedule
Season
Season Day Type Schedule
Station Supply
Sub Load Area
Substation
This subject area provides modeling of the energy consumers and the system load as curves and associated curve data. Special circumstances such as seasons and day types are also included.
Entities of Subject Area: Location
Address Location
Asset
Asset Location
Geography Building
Geography City
Geography Complex
Geography Country
Geography County
Geography Demographic Group
Geography Demography Attribute
Geography Demography Value
Geography Entity
Geography Entity Assignment
Geography Entity Hier Level Assignment
Geography Hierarchy
Geography Hierarchy Level
Geography Level
Geography Region
Geography State
Geography Street
Geography Sub Region
Geography World
Location
Measurement Location
Power System Resource
Power System Resource Location
Usage Point
Usage Point Location
Work Location
Zone
Entities of Subject Area: Meter Asset
This subject area presents meter from asset perspective.
Asset
Asset Container
Asset Info
Asset Model
Asset Type
End Device
End Device Function
Manufacturer
Meter
Meter Register Assignment
Product Asset Model
Reading Channel
Reading Type
Register
Entities of Subject Area: Device Event and Measurement
This subject area contains the basic information on meter events and reading.
Activity Record
Asset
Asset Container
Base Reading
End Device
End Device Function
Final Reading
Initial Reading
Measurement Value
Meter
Meter Reading
Meter Register Assignment
Reading Channel
Reading Type
Register
Entities of Subject Area: Meter Reading
Agreement
Base Reading
End Device
Final Reading
Identified Object
Initial Reading
Invoice Item
Invoice Item Detail
Measurement Value
Meter
Meter Reading
Reading Quality
Reading Quality Type
Reading Reason Kind ENUM
Reading Type
Service Quantity
Usage Point
Usage Read Cycle
Entities of Subject Area: Meter Reading and Events
This subject area contains core information on end device event detected by a device function associated with end device.
Activity Record
Asset
Asset Activity Record Assignment
Asset Container
Base Reading
End Device
End Device Domain
End Device Event
End Device Event Detail
End Device Event Or Action
End Device Event Type
End Device Sub Domain
Final Reading
Initial Reading
Meter
Meter Reading
Reading Quality
Reading Quality Type
Reading Type
Entities of Subject Area: Meter Reading and Control Overview
Agreement
Agreement Usage Point Assignment
Base Reading
Campaign
Customer Facing Service
DR Prog End Device Grp Assignment
DR Program Agreement Assignment
Demand Response Program
Electricity Service
End Device
End Device Control
End Device Control Type
End Device End Device Ctrl Assignment
End Device End Device Grp Assignment
End Device Event
End Device Event Detail
End Device Event Type
End Device Function
End Device Function Kind ENUM
End Device Group
End Device Grp End Device Ctrl Assignment
Final Reading
Initial Reading
Measurement Value
Meter
Meter Reading
Promotion
Reading Quality
Reading Quality Type
Reading Type
Service
Usage Point
Usage Point End Device Ctrl Assignment
Usage Point Group
Usage Point Grp End Device Ctrl Assignment
Usage Point Location
Usage Read Cycle
Entities of Subject Area: Meter Reading Register and Channel
This subject area contains the core information on meter reading, register, and reading channel.
Com Function
Connect Disconnect Function
End Device
End Device Function
Meter
Meter Reading
Meter Register Assignment
Reading Channel
Reading Channel Identifier
Reading Type
Register
Simple End Device Function
Entities of Subject Area: Meter Reading Type
Consumption Tier
Critical Peak Period
Currency
Energy Flow Direction
Interharmonics
Measurement Kind
Phase
Reading Accumulation Behavior
Reading Data Qualifier
Reading Time Attribute
Reading Time Period
Reading Type
Time Of Use
Unit Multiplier
Unit Of Measure
Utility Commodity
Entities of Subject Area: Network Operation
AC Line Segment
AC Line Segment Phase
Active Power Limit
Apparent Power Limit
Asset
Asset PSR Assignment
Clamp
Clearance Action
Clearance Document
Conducting Equipment
Conductor
Connect Disconnect Function
Current Limit
Cut
Cut Action
End Device Function
Equipment
Generic Action
Incident
Jumper
Jumper Action
Operating Participant
Operating Share
Operation Tag
Operational Limit
Operational Limit Set
Operational Restriction
Outage
Outage Schedule
Power System Resource
Safety Document
Switch
Switch Action
Switch Connect Disconnect Func Assignment
Switch Phase
Switch Switching Operation Assignment
Switching Activity
Switching Activity Safety Doc Assignment
Switching Operation
Switching Plan
Switching Step
Switching Step Group
Tag Action
Voltage Limit
Work Task
Work Task Asset Assignment
Entities of Subject Area: Outage Management
Conducting Equipment
Customer
Customer Outage Notification Assignment
End Device
Equipment
Fault
Incident
Incident Work Assignment
Meter
Outage
Outage Code
Outage Notification
Outage Plan
Outage Record
Outage Record Code Assignment
Outage Report
Outage Schedule
Outage Step
Outage Step Code Assignment
Phase Connected Fault
Planned Outage
Switch
Switch Action
Switching Plan
Trouble Ticket
Usage Point
Work Order
Party Organization Business Unit
Address Location
Call Center
Call Center Service Capability
Cost Center
Language
Market Area
Market Area Level
Organization Area
Organization Banner
Organization Business Entity
Organization Business Unit
Organization Business Unit Type
Organization Chain
Organization Company
Organization Corporate
Organization District
Organization Hierarchy
Organization Hierarchy Level
Organization Hierarchy Level Assignment
Organization Hierarchy Version
Organization Level
Organization Level Attribute Value
Organization Level Attributes
Organization Market Data
Organization Region
Organization Service Website
Organization Warehouse
Organizational Demography Value
Service Coverage Area
Service Coverage Geo Detail
Virtual Team
Entities of Subject Area: Payment
Account
Account Balance History
Account Balance Impact
Account Balance Type
Account Payment
Account Payment Balance Impact
Account Payment Method Status
Account Payment Method Status Type
Account Preferred Payment Method
Account Refund
Account Refund Reason
Agree Item Pricing Struct Assignment
Agreement
Agreement Item
Bank Direct Debit Channel
Currency
Customer
Customer Account Assignment
Debt Collection
Employee
Event
Invoice
Invoice Adjustment
Invoice Payment Assignment
Invoice Payment Term
Invoice Payment Term Type
Organization Business Unit
Party Account Assignment
Party Account Assignment Type
Payment Method Type
Payment Transaction Type
Pricing Structure
Entities of Subject Area: Premise and Node
This subject area contains the core information on service location (premise) and its relationships such as the ones with usage point and end device.
Address Location
Asset
Asset Container
Asset Location
Connectivity Node
Connectivity Node Container
End Device
Equipment
Equipment Container
Power System Resource
Service Location
Service Location Identifier
Usage Point
Usage Point Equipment Assignment
Usage Point Location
Entities of Subject Area: Pricing Structure
This subject area contains the core information on pricing structure such as tariff and relation to agreement class.
Agree Item Pricing Struct Assignment
Agreement
Agreement Item
Consumption Tariff Interval
Demand Tariff Interval
Pricing Structure
Pricing Structure Tariff Assignment
Rate
Service Category
Service Type
Tariff
Tariff Profile
Tariff Tariff Profile Assignment
Time Tariff Interval
Entities of Subject Area: Promotion and Campaign
Campaign
Campaign Channel
Campaign Channel Assignment
Campaign Channel Type
Campaign Characteristic
Campaign Characteristic Value
Campaign Management History
Campaign Message
Campaign Message Creative
Campaign Message Depiction
Campaign Relationship
Campaign Status
Campaign Term Value
Campaign Type
Contact List
Contact List Change Reason
Contact List Recurrence Type
Customer Segment
Event Party Interaction
Geography Entity
Initiative Type
Market Area
Market Segment
Market Segment Inclusion
Media Object
Media Object Assignment
Media Object Type
Organization Business Unit
Party
Party Contact List Participation
Party Contact List Role
Party Management Role
Party Market Segment Assignment
Party Promotion Response
Product Offering
Promotion
Promotion Cluster Usage
Promotion Contact List Utilization
Promotion Management History
Promotion Message Rendering
Promotion Product Offering Assignment
Promotion Relationship
Promotion Result Type
Promotion Sales Channel Assignment
Promotion Term Type
Promotion Term Value
Promotion Type
Proposal
Proposal Relationship
Prospect
Prospect Priority Type
Prospect Quality Score Type
Prospect Quality Score Value
Prospect Reject Reason
Publication
Sales Channel
Source System
Source System Type
Target Account
Target Agreement
Target Geography Area
Target Type
Entities of Subject Area: Regulating Equipment Model
The diagram shows all classes related to equipment regulation and reactive power compensation.
Control
Frequency Converter
Regulating Cond Eq
Regulating Control
Regulation Schedule
Rotating Machine
Shunt Compensator
Static Var Compensator
Synchronous Machine
Tap Changer
Tap Changer Control
Tap Schedule
Terminal
Entities of Subject Area: SCADA
This subject area contains entities to model information used by Supervisory Control and Data Acquisition (SCADA) applications.
Communication Link
Control
Identified Object
Measurement Value
Power System Resource
Remote Control
Remote Point
Remote Source
Remote Unit
Remote Unit Communication Link Assignment
Entities of Subject Area: Schedule Model
This area covers schedules relevant to wires model.
Basic Interval Schedule
Day Type
Regular Interval Schedule
Regular Time Point
Regulating Control
Regulation Schedule
\Season
Season Day Type Schedule
Switch
Switch Schedule
Tap Changer
Tap Schedule
Entities of Subject Area: Substation Feeder and Transformer
Connectivity Node Container
Equipment
Equipment Container
Feeder
Feeder Substation Assignment
Power System Resource
Substation
Transformer Feeder Assignment
Transformer Tank
Usage Point
Usage Point Transformer Assignment
Entities of Subject Area: Switching Equipment Model
This area covers switching equipment inheritance structure.
Breaker
Disconnector
Fuse
Ground Disconnector
Ground Switch
Jumper
Load Break Switch
Protected Switch
Recloser
Sectionaliser
Switch
Entities of Subject Area: Tap Changer Model
This area covers major classes related for the transformer tap model.
Phase Tap Changer
Phase Tap Changer Asymmetrical
Phase Tap Changer Linear
Phase Tap Changer Non Linear
Phase Tap Changer Symmetrical
Phase Tap Changer Tabular
Phase Tap Changer Tabular Point
Power Transformer
Power Transformer End
Ratio Tap Changer
Ratio Tap Changer Tabular
Ratio Tap Changer Tabular Point
Regulating Control
Regulation Schedule
Tap Changer
Tap Schedule
Transformer End
Entities of Subject Area: Transformer Model
Base Voltage
Conducting Equipment
Power Transformer
Power Transformer End
Terminal
Transformer Core Admittance
Transformer End
Transformer Mesh Impedance
Transformer Star Impedance
Transformer Tank End
Entities of Subject Area: Usage Point, Agreement, Account, Customer, and Premise
Account
Agreement
Agreement Usage Point Assignment
Customer
Customer Account Assignment
Service Location
Usage Point
Entities of Subject Area: Usage Point and End Device
Agreement
Asset
Asset Container
Asset Status
Asset Type
Com Function
Connect Disconnect Function
End Device
End Device Event Type
Lifecycle Date
Market Role
Meter
Meter Identifier
Meter Reading
Meter Status
Reading Type
Service Category
Service Supplier
Status
Usage Point
Usage Read Cycle
Entities of Subject Area: Voltage Control Model
Busbar Section
Connector
Power System Resource
Regulation Schedule
Season Day Type Schedule
Voltage Control Zone
Entities of Subject Area: Weather Model
Activity Record
Address Location
Asset
Asset Activity Record Assignment
Asset Container
Atmospheric Pressure
Cloud Information
End Device
Flood Information
Meter
Precipitation
Sea Condition
Spot Temperature
Usage Point
Weather Alert
Weather Forecast
Weather Information
Weather Location
Wind Information
Entities of Subject Area: Work Management
Base Work
Business Case
Crew
Crew Work Task Assignment
Incident
Incident Work Assignment
Meter Service Work
Outage Record
Project
Tool
Vehicle
Work Asset
Work Billing Info
Work Cost Detail
Work Cost Summary
Work Flow Step
Work Location
Work Order
Work Status Entry
Work Task
Work Time Schedule
The business area lists contain a list of subject areas that the business area contains.
Note:
The notion of a business area is not strict. That is, some business areas are overlapping. Thus, a logical entity can belong to, or be needed in several business areas. Some logical entities are not explicitly listed because they either only represent a relationship between tables, are not critically important to any business area, or are simply lookup entities. For more information, see About Business Areas and Subject Areas in Oracle Utilities Data Model.
This section lists the business areas in Oracle Utilities Data Model:
Note:
The subject area figures showing complete diagrams with attributes and entities are available with the Oracle Utilities Data Model IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Utilities Data Model patch sets, go to My Oracle Support at https://support.oracle.com.
Business Area: Account Management
This business area contains information to support utility customers with the tracking, status, and plans with matters such as service requests, service agreements, monthly billing, reported trouble, planned outages, outage history, and so on.
Subject Area: Account
Subject Area: Account Balance
Subject Area: Account Credit Limit
Subject Area: Agreement
Subject Area: Billing
Subject Area: Cost
Subject Area: Location
Subject Area: Payment
Subject Area: Pricing Structure
Subject Area: Promotion and Campaign
Business Area: Asset Management
This business area is mainly on the information management for network data sets, assets, and asset catalogs.
Subject Area: Asset
Subject Area: Asset Information Classes
Subject Area: Agreement
Business Area: Customer Management
This business area includes customer service, trouble management, and point of sale related information within the utility enterprise.
Subject Area: Channel
Subject Area: Business Interaction
Subject Area: Customer
Subject Area: Customer Account and Agreement
Subject Area: Demand Response Program
Subject Area: Financial
Subject Area: Premise and Node
Subject Area: Usage Point, Agreement, Account, Customer, and Premise
Subject Area: Usage Point and End Device
Business Area: Meter Reading and Control
This business area focuses on meter reading, event, and control information within the utility enterprise.
Subject Area: Meter Event and Reading
Subject Area: Business Interaction
Subject Area: End Device Control
Subject Area: End Device Event
Subject Area: Meter Reading and Control Overview
Subject Area: Meter Reading and Events
Subject Area: Meter Reading
Subject Area: Meter Reading Register and Channel
Subject Area: Meter Reading Type
Business Area: Network Operation
This business area provides the information on network operation for both distribution and transmission within utility industry such as supervising main substation topology, control equipment status, handling network connectivity, and loading conditions. It also makes it possible to locate and supervise the location of field crews.
Subject Area: Business Interaction
Subject Area: Connectivity Model
Subject Area: Curve Schedule
Subject Area: Generating Unit
Subject Area: Line Model
Subject Area: Load Model
Subject Area: Network Operation
Subject Area: Phase Model
Subject Area: Regulating Equipment Model
Subject Area: SCADA
Subject Area: Schedule Model
Subject Area: Switching Equipment Model
Subject Area: Substation, Feeder, and Transformer Hierarchy Model
Subject Area: Tap Changer Model
Subject Area: Transformer Model
Subject Area: Voltage Control Model
Business Area: Outage Management
This business area supports the utilities to identify disruptions in the system, to carry out restoration switching actions and to provide customers with notification of disruptions detected.
Business Area: Weather Model
This is a weather model to support utility operation.
Table 2-1 Utilities Data Model Entities A-H
| Entity Name | Type | Description |
|---|---|---|
|
|
Reference |
A wire or combination of wires, with consistent electrical characteristics, building a single electrical system, used to carry alternating current between points in the power system. For symmetrical, transposed 3ph lines, it is sufficient to use attributes of the line segment, which describe impedances and admittances for the entire length of the segment. Additionally impedances can be computed by using length and associated per length impedances. |
|
|
Reference |
Represents a single wire of an alternating current line segment. |
|
|
Reference |
Acceptance test for assets. |
|
|
Reference |
The account tracks the financial interactions of a customer with the utility. It is normally generated by a contract between the utility and customer. One customer may have multiple accounts. |
|
|
Base |
Billing cycle status history for accounts. |
|
|
Lookup |
The reason why the adjustment was put on the customer account. |
|
|
Reference |
The association history from account the contract. |
|
|
Derived |
Account arrears month derived. |
|
|
Reference |
This entity keeps relationship between accounts. For example: parent account and child account. |
|
|
Lookup |
Explain why two accounts are related. |
|
|
Lookup |
The type of relationship between two accounts. For example, a corporation account can have several affiliated accounts. |
|
|
Base |
Add the adjustment to customer account Account/Receivable. The credit is positive values. |
|
|
Lookup |
The categories of adjustment applied to a customer account. |
|
|
Base |
Balance of customer account which may be used in prepaid business. |
|
|
Reference |
The balance group concept allows one account have multiple balance groups, which applies to different groups of services. This is optional entity. |
|
|
Base |
Balance history of account subjected to the primary currency. The balance value was classified by the balance type. The adjusted, due, received, used amounts in the same period are also captured. |
|
|
Base |
The account balance change details, because of a specific event, such as an account payment. |
|
|
Derived |
Derived fact table on account balance by month. It aggregates over customer/account level. |
|
|
Lookup |
Type of account balance. For example: water, gas, kwh usage. |
|
|
Reference |
Billing cycle status history for accounts. |
|
|
Reference |
Billing Frequency history for accounts. |
|
|
Base |
Each billing occurrence happened to the account. The billing occurrence might be triggered by billing cycle or some other events like account termination. In each billing occurrence, there may be multiple invoices generated. |
|
|
Reference |
Billing period history for accounts. |
|
|
Reference |
The Business Interaction Role which can be assigned by a Customer Account. |
|
|
Base |
The credit limit on the customer, which is imposed on the account basis. |
|
|
Base |
Account Debt |
|
|
Derived |
The summarized daily debt status for each account. The account is deemed as in debt status when and only when there is a ''debt collection'' record to indicate the collection. |
|
|
Lookup |
This entity keeps all categories of account event type. |
|
|
Base |
Sub type of Party Account assignment. The Account management history tracks the management relationship from employee to the accounts, including Account Creation (through sales channel), and Accounts update/termination. |
|
|
Base |
The payments table records details of each allocation of money from a receipt made by a Party to a specific account. It is the receipt of a single sum of money from a party as a credit against an outstanding balance for the provision and/or supply of products or services. |
|
|
Base |
The account balance impact originated from account payments. |
|
|
Derived |
Daily aggregation of payments made by all customers. Derive from Account Payment. The difference between this entity and payment aging drvd, is that this one aggregates based on payment transactions, while the payment aging aggregates based on invoices, which is payment due. |
|
|
Base |
Status history of each account preferred payment method. For example:
For Direct Debit Status, it defines current and original payment status of account, and maybe changed or terminated according to contract. |
|
|
Derived |
Current status of the payment methods for each account. The information helps tracking the progress of direct debit applications and thus in processing the application as soon as possible. Derived from Account Payment Method Status. Direct debit status fact gives information about the current direct debit accounts and also the status of the new applications for the direct debit. Status can be accepted, rejected or pending. |
|
|
Lookup |
This entity will be used to keep why the status is changed. For example: reject reason could be not sufficient balance. |
|
|
Lookup |
Lookup for types of account Payment Method Status. For example: Active, Inactive, payment rejected. Postpaid customers can pay their bills using the direct debit facility wherein they if they have their bank accounts in certain banks (listed with the company for Direct Debit), monthly bill can be directly deducted from the bank account of the customer. |
|
|
Reference |
The preferred invoice delivery type history for account. This also include the billing address location information specific for an account. |
|
|
Reference |
This entity contains preferred payment methods for the accounts. |
|
|
Reference |
To record more details about the account. To be customized. This is currently a placeholder. |
|
|
Base |
The recharge made into the customer account. |
|
|
Base |
The customer refund is the money transferred back to customer account, which is normally based on invoice adjustment made. |
|
|
Lookup |
The reason why refund may occur. For example:
|
|
|
Lookup |
The type of ACCOUNT ROLEs. For example, primary account, secondary account, and so on. This can build a secondary classification system other than account type. |
|
|
Reference |
The segments identifying distinct groupings of accounts with similar characteristics. Those segments are typically generated from the data mining analysis. |
|
|
Reference |
Assign account segment to each account. |
|
|
Reference |
Used to cluster the account. |
|
|
Base |
The history of account status change, including disconnect, reconnect, and so on. |
|
|
Derived |
The status change information about all accounts at every day. Derived from Account Status History. |
|
|
Lookup |
The reason why the account reaches its status at the time. |
|
|
Lookup |
This level broadly classifies the status into categories such as Connected and Disconnected customer accounts. |
|
|
Lookup |
Type of account. |
|
|
Reference |
Accounting cycle is internal billing cycle, which calculate the usage amount and update account balance for accounting G/L purpose. |
|
|
Lookup |
A specific account code that can be associated with an incurred Cost. For example: Operations, Staffing, Supplies. |
|
|
Base |
Accumulator represents a accumulated (counted) measurement. For example, an energy value. |
|
|
Reference |
Limit values for Accumulator measurements. |
|
|
Reference |
Specifies a set of Limits that are associated with an Accumulator measurement. |
|
|
Reference |
Accumulator limit set assignment. |
|
|
Base |
Accumulator Value represents an accumulated (counted) Measurement Value. |
|
|
Reference |
An electrical connection point (AC or DC) to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes. |
|
|
Reference |
Limit on active power flow. |
|
|
Base |
Records activity for an entity at a point in time; activity may be for an event that has already occurred or for a planned activity. |
|
|
Reference |
Keeps all addresses. It has levels as country, state, city, address and so on. |
|
|
Reference |
Pricing structure assigned to an agree item. |
|
|
Reference |
Legal agreement between a Service Provider and an account. (its not for changed contract only) |
|
|
Base |
Approval to the contract from operator's authorized employee if the contract requires higher level approval or review. |
|
|
Base |
Contracts are related to each other for various reasons, like one new contract to replace existing one. |
|
|
Lookup |
Lookup for reasons of why two contracts are related. |
|
|
Lookup |
Lookup for types of the assignment between two contracts. |
|
|
Reference |
The document provided by customer when contract was signed. For example:
|
|
|
Reference |
Detail items for the contract between customer and utility. Each item may use a different service or product. |
|
|
Base |
The status history of the contract. |
|
|
Lookup |
Lookup type of all possible contract status. For example: 1. Newly created for new account 2. Renewed automatically. 3. Terminated. |
|
|
Lookup |
The type of Contracts. |
|
|
Reference |
Agreement that a usage point has. |
|
|
Reference |
Combustion turbine air compressor which is an integral part of a compressed air energy storage (CAES) plant. |
|
|
Lookup |
Lifecycle states of the metering installation at a usage point with respect to readiness for billing through advanced metering infrastructure reads. |
|
|
Base |
Analog represents an analog measurement. |
|
|
Reference |
Limit values for analog measurements. |
|
|
Reference |
An Analog Limit Set specifies a set of limits that are associated with an analog measurement. |
|
|
Reference |
Analog limit set assignment. |
|
|
Base |
Analog value represents an analog measurement Value. |
|
|
Lookup |
Kind of anchor. |
|
|
Reference |
The SIC code used in Australia and New Zealand. |
|
|
Reference |
Apparent power limit. |
|
|
Base |
The appointment between two parties to define a future time conducting businesses. For example the customer visit appointment, between sales representative and the customer, and support appointment between the customer and the engineer. In the appointment, the parties involved are tracked in Party Business Interaction Role'. The Business Interaction Date inherited should contain the date when the appointment was created, and appointed date is ''appointment start date". |
|
|
Lookup |
Captures the appointment types. For example:
|
|
|
Reference |
Tangible resource of the utility, including power system equipment, various end devices, cabinets, buildings, and so on. For electrical network equipment, the role of the asset is defined through Power System Resource and its subclasses, defined mainly in the Wires model (refer to IEC61970-301 and model package IEC61970::Wires). Asset description places emphasis on the physical characteristics of the equipment fulfilling that role. |
|
|
Reference |
Activity record of an asset. |
|
|
Base |
The valuation history of the asset. |
|
|
Base |
The condition history of an asset, as inspected by internal employee or contractors. Those are more important for vehicles or buildings. |
|
|
Reference |
Asset that is aggregation of other assets such as conductors, transformers, switchgear, land, fences, buildings, equipment, vehicles, and so on. |
|
|
Reference |
Function performed by an asset. |
|
|
Reference |
Set of attributes of an asset, representing typical data-sheet information of a physical device that can be instantiated and shared in different data exchange contexts:- as attributes of an asset instance (installed or in stock), as attributes of an asset model (product by a manufacturer), as attributes of a type asset (generic type of an asset as used in designs/extension planning). |
|
|
Reference |
Location of an asset. |
|
|
Reference |
Model of an asset, either a product of a specific manufacturer or a generic asset model or material item. Data-sheet characteristics are available through the associated Asset Info subclass and can be shared with asset or power system resource instances. |
|
|
Reference |
Catalog of available types of products and materials that are used to build or install, maintain or operate an Asset. Each catalog item is for a specific product (Asset Model) available from a specific supplier. |
|
|
Reference |
Provides pricing and other relevant information about a specific manufacturer's product (that is, Asset Model), and its price from a given supplier. A single Asset Model may be available from multiple suppliers. A manufacturer and supplier are both types of organization, which the association is inherited from Document. |
|
|
Lookup |
Usage for an asset model. |
|
|
Reference |
Role an organization plays with respect to asset. |
|
|
Reference |
Organization role of an asset such as owner, operator and so on. |
|
|
Reference |
Owner of the asset. |
|
|
Reference |
Power System Resource assigned to an asset. |
|
|
Reference |
Current status information relevant to an entity. |
|
|
Lookup |
Type of Asset. |
|
|
Reference |
Organization that is a user of the asset. |
|
|
Reference |
This is a super class of assignment tables. |
|
|
Base |
Atmospheric Pressure |
|
|
Reference |
Keep information of banks. |
|
|
Reference |
Subtype to the payment channel, which tracks various bank channels where customer can pay by direct debt method. Customers can go to the bank and pay the bill by cash in the bank. This is allowed only through specific banks. |
|
|
Lookup |
Lookup defining reasons a customer may be banned from using a service. |
|
|
Base |
Common representation for reading values. A reading value may have multiple qualities, as produced by various systems ('ReadingQuality.source'). |
|
|
Reference |
Defines a system base voltage which is referenced. |
|
|
Reference |
Common representation for work and work tasks. |
|
|
Reference |
Schedule of values at points in time. |
|
|
Reference |
The Bill Cycles table documents each billing cycle. Typically it's per month (Billing cycle). Sometimes customer may be billed at different date inside the billing cycle. For example:
For example:
|
|
|
Reference |
The billing frequency specifies the number of billing periods that comprise the billing cycle. |
|
|
Lookup |
Specifies the type of billing occurrence, which could be classified by triggering type. For example,
|
|
|
Lookup |
The billing period specifies the unit to be used to calculate the billing cycle (such as day or month). |
|
|
Base |
To keep track of black listed customers. Those records might be because of late payment, default, or fraud. |
|
|
Reference |
A mechanical switching device capable of making, carrying, and breaking currents under normal circuit conditions and also making, carrying for a specified time, and breaking currents under specified abnormal circuit conditions. For example, those of short circuit. |
|
|
Reference |
A Conductor, or group of Conductors, with negligible impedance, that serve to connect other conducting equipment within a single substation. Voltage measurements are typically obtained from VoltageTransformers that are connected to busbar sections. A bus bar section may have many physical terminals but for analysis is modeled with exactly one logical terminal. |
|
|
Reference |
Busbar section data. |
|
|
Reference |
Bushing asset. |
|
|
Lookup |
Insulation kind for bushings. |
|
|
Reference |
Business justification for capital expenditures, usually addressing operations and maintenance costs as well. |
|
|
Reference |
Specifies information relating to a fortnight in a Business Calendar. |
|
|
Reference |
Specifies information relating to half year in a Business Calendar. |
|
|
Base |
An abstracted entity to provide the common base for customer order and contract. A Business Interaction is an arrangement, contract, communication or joint activity between one or more Party Roles, ResourceRoles, or CustomerAccounts. A Business Interaction may consist of one or more Business Interaction Items. A Business Interaction Item may refer to a Product, Service, Resource, or one of their specifications. A Business Interaction is further defined by one or more Places. One Business Interaction may reference another Business Interaction and one Business Interaction Item may reference another Business Interaction Item on the same or different Business Interaction. There are five types of Business Interactions: Requests, Responses, Notifications, Agreements, and Instructions. |
|
|
Reference |
Defines the relationship between two Business Interactions. |
|
|
Lookup |
Business interaction assignment type, such as subordinate business interaction, and so on. |
|
|
Base |
The detail items included in the Business Interaction. The purpose for the Business Interaction is expressed in terms of a Product Type, Service Type or may refer to a Product or Service. |
|
|
Base |
The actual price charged to the Business Interaction Item. |
|
|
Reference |
The Business Interaction Role which can be assigned to an address. For example:
|
|
|
Base |
The roles which can be played by Party or other Business Interaction elements like Resource, and so on. |
|
|
Base |
The status history of a Business Interaction. For example:
Both current status and historical status should be captured and they can be differentiated by effective to date. |
|
|
Lookup |
The reason to explain why a Business Interaction has had a change in status. |
|
|
Lookup |
Lookup for available business interaction status types and descriptions. For example: Active Closed. |
|
|
Lookup |
Business interaction type, such as Customer Order, Contract, and so on. |
|
|
Reference |
Specifies the ability to distinguish between different instances of Business Interaction. |
|
|
Lookup |
The legal status of the company. The value might be Public Company, Private. |
|
|
Reference |
Specifies information relating to a month in a Business Calendar. |
|
|
Reference |
Specifies information relating to a quarter in a Business Calendar. |
|
|
Reference |
Capture the specific job role for an organization. |
|
|
Reference |
Specifies information relating to a week in a Business Calendar. |
|
|
Reference |
Specifies information relating to a year in a Business Calendar. |
|
|
Reference |
Compressed air energy storage plant. |
|
|
Reference |
Captures information relating to a fortnight in a Normal Calendar. |
|
|
Reference |
Captures information relating to half year in a Normal Calendar. |
|
|
Reference |
Captures information relating to a month in a Normal Calendar. |
|
|
Reference |
Captures information relating to a quarter in a Normal Calendar. |
|
|
Reference |
Captures information relating to a week in a Normal Calendar. |
|
|
Reference |
Specifies information relating to a year in a Normal Calendar. |
|
|
Reference |
The utility may have multiple call centers in different locations, for different timezone or language purpose. |
|
|
Reference |
All the possible agents with whom the customer can make a contact. For example: IVR, Human Agent and so on. |
|
|
Lookup |
Lookup table that further characterizes the type of cases from the call center. It helps in splitting a given case type in various sub-types. For example, ''outage''. |
|
|
Lookup |
Further classify the call center case sub type. In order to serve the customer properly call center has organized approach. Customer complaints called as cases are classified using three level classification structures. All the cases are broadly classified into Call Center Case Type. |
|
|
Lookup |
Lookup for types of call center cases. For example:
|
|
|
Reference |
Assigns the languages, products, or geographical areas which the call center can serve to the call center. |
|
|
Reference |
A campaign is a concentrated effort to enhance the image of the enterprise, in order to retain, acquire or consolidate customers. |
|
|
Reference |
The campaign channel is used for Campaign, or by which customer can know the product. A channel can be a specific news group (/media company) which issues newspaper, TV channel and so on. A piece of newspaper of a block/slot on the paper is a publication/media object. It can be categorized by Campaign Channel Type. |
|
|
Reference |
The assignment to define which campaign is launched at which Campaign Channel. |
|
|
Lookup |
This entity keeps the channel type, which is used to Campaign. For example:
|
|
|
Reference |
A characteristic quality or distinctive feature of a Campaign. The characteristic can be take on a discrete value, such as number of press releases, can take on a range of values. For example, number of prospects reached 50,000 - 100,000), or can be derived from a formula (for example, number of brokerage house pickups = sum of all brokerage house instance characteristics). |
|
|
Reference |
A number or text that can be assigned to a Campaign Characteristic. |
|
|
Reference |
The customer documents provided during campaign activities. |
|
|
Reference |
The history of campaign party role about management of a Campaign. The party here can be not only the sales or marketing employee at the utility, it can also be campaign partner. |
|
|
Reference |
Holds details about the execution message used in a Campaign. |
|
|
Base |
Information about the creative content of the message. |
|
|
Reference |
Details about how the execution message is depicted for a Campaign. This dimension table holds details about how the execution message is depicted, for a Campaign. |
|
|
Reference |
Defines the relationship between two Campaigns. For example, to replace/upgrade, to enhance, and so on. |
|
|
Lookup |
This entity keeps strategy or business objective of the Campaign. |
|
|
Reference |
The term value for a given Campaign. |
|
|
Lookup |
This entity keeps types of Campaigns. For example: a targeted promotion (to specific individuals, account or group of accounts), a mass market promotion (to a massive audience usually through radio, television and newspaper). |
|
|
Reference |
Identifies all the channels through which customers interact with the provider for sales or services purposes. Each channel by itself is also a Party, and Channel provide another way to group parties with same functionality to the service provider. In current model, for most of channels, the analytical hierarchy should be: Party (with internal levels) |
|
|
Lookup |
Channel Type is used to classify the channels according to their functionalities. For example: 1. Sales Channel 2. Payment Channel 3. Debt collection channel 4. Loyalty Program Channel (where to join/change/redeem loyalty program). |
|
|
Lookup |
Kind of charge. |
|
|
Reference |
A Clamp is a galvanic connection at a line segment where other equipment is connected. A Clamp does not cut the line segment. A Clamp is Conducting Equipment and has one Terminal with an associated Connectivity Node. Any other Conducting Equipment can be connected to the Clamp Connectivity Node. |
|
|
Reference |
Action on cut as a switching step. |
|
|
Lookup |
Kind of action on cut or jumper. |
|
|
Reference |
Safety document used to authorize work on conducting equipment in the field. Tagged equipment is not available for commercial service. |
|
|
Base |
Cloud Information. |
|
|
Reference |
A set of thermal generating units for the production of electrical energy and process steam (usually from the output of the steam turbines). The steam sendout is typically used for industrial purposes or for municipal heating and cooling. |
|
|
Reference |
Subtype of Party, who collects customer debt on behalf of the operator under some financial agreements. |
|
|
Lookup |
Kind of communication direction. |
|
|
Reference |
Com Function |
|
|
Reference |
Communication media such as fiber optic cable, power-line, telephone, and so on. |
|
|
Reference |
An asset having communications capabilities that can be paired with a meter or other end device to provide the device with communication ability, through associated communication function. An end device that has communications capabilities through embedded hardware can use that function directly (without the communication module), or combine embedded communication function with additional communication functions provided through an external communication module. |
|
|
Lookup |
Kind of communication technology. |
|
|
Reference |
A set of combustion turbines and steam turbines where the exhaust heat from the combustion turbines is recovered to make steam for the steam turbines, resulting in greater overall plant efficiency. |
|
|
Base |
A command is a discrete control used for supervisory control. |
|
|
Reference |
The connection to remote units is through one or more communication links. Redundant links may exist. The CommunicationLink class inherit Power System Resource. The intention is to allow CommunicationLinks to have Measurements. These Measurements can be used to model link status as operational, out of service, unit failure and so on. |
|
|
Reference |
A pre-planned job model containing labor, material, and accounting requirements for standardized job planning. |
|
|
Reference |
Compatible Unit Procedure Assignment |
|
|
Reference |
Properties of a composite switch. |
|
|
Lookup |
Kind of composite switch. |
|
|
Reference |
Protection equipment assigned to a conducting equipment. |
|
|
Reference |
The parts of the AC power system that are designed to carry current or that are conductively connected through terminals. |
|
|
Reference |
Combination of conducting material with consistent electrical characteristics, building a single electrical system, used to carry current between points in the power system. |
|
|
Base |
Used to report details on creation, change or deletion of an entity or its configuration. |
|
|
Reference |
Conform load represent loads that follow a daily load change pattern where the pattern can be used to scale the load with a system load. |
|
|
Reference |
A group of loads conforming to an allocation pattern. |
|
|
Reference |
A curve of load versus time (X-axis) showing the active power values (Y1-axis) and reactive power (Y2-axis) for each unit of the period covered. This curve represents a typical pattern of load over the time period for a given day type and season. |
|
|
Reference |
A function that will disconnect and reconnect the customer's load under defined conditions. |
|
|
Reference |
Connectivity nodes are points where terminals of AC conducting equipment are connected together with zero impedance. |
|
|
Reference |
A base class for all objects that may contain connectivity nodes or topological nodes. |
|
|
Reference |
A Conductor, or group of Conductors, with negligible impedance, that serve to connect other conducting equipment within a single substation and are modelled with a single logical terminal. |
|
|
Reference |
One of a sequence of intervals defined in terms of consumption quantity of a service such as electricity, water, gas, and so on. It is typically used in association with Tariff Profile to define the steps or blocks in a step tariff structure, where startValue simultaneously defines the entry value of this step and the closing value of the previous step. Where consumption is >= startValue it falls within this interval and where consumption is < startValue it falls within the previous interval. |
|
|
Reference |
Tier define by consumption amount. |
|
|
Reference |
Lists of potential and existing customer for Campaigns. Contact Lists can be created from marketing activity (running certain models), or obtained from another Organization. |
|
|
Lookup |
Lookup of possible reasons for changing the Contact List. When contact list is changed, the SCD2 columns will capture the change and provide reason for change. |
|
|
Lookup |
A categorization of the recurrence of a Contact List. For example:
|
|
|
Lookup |
Describes the various roles a contact individual may play in the relationship with the operator. |
|
|
Base |
Control is used for supervisory/device control. It represents control outputs that are used to change the state in a process. For example, close or open breaker, a set point value or a raise lower command. |
|
|
Lookup |
Specifies the type of Control. For example:
The ControlType.name shall be unique among all specified types and describe the type. The ControlType.aliasName is meant to be used for localization. |
|
|
Lookup |
Method of cooling a machine. |
|
|
Lookup |
Kind of corporate standard. |
|
|
Base |
Define the cost might incurred from any operation or event which is trackable at certain level. |
|
|
Reference |
To categorize the different cost charges inside the utility for different purpose. Organization can own multiple cost center for different project/product operation. |
|
|
Lookup |
Lookup of all possible reasons why the cost occurred. For example, natural disaster, operator error, and so on. |
|
|
Lookup |
Further classify cost type. For example, For ''cost to customer'', subtype could be acquire cost, retention cost, and so on. For ''cost to employee'', subtype could be salary, and so on. For ''cost to channel'', subtype could be damage, new equipment, repairing fee. |
|
|
Lookup |
Lookup for types of costs. For example, the cost is to the customer, channel, or to the employee. |
|
|
Reference |
Category based on customer credit. |
|
|
Reference |
Credit score provider provide reference financial rating scores for each customers to the service provider. It is also called Credit rating agency. |
|
|
Reference |
Group of people with specific skills, tools, and vehicles. |
|
|
Reference |
Crew Member |
|
|
Reference |
Custom description of the type of crew. This may be used to determine the type of work the crew can be assigned to. For example:
|
|
|
Reference |
Work task assigned to a crew. |
|
|
Reference |
Critical peak period usually associated with a peak pricing. |
|
|
Lookup |
The currencies represented by ISO currency codes. |
|
|
Lookup |
Monetary currencies. |
|
|
Base |
Exchange rate against the primary currency, as determined by exchange rate type and value date. |
|
|
Reference |
To define currency usage in different area. |
|
|
Reference |
Operational limit on current. |
|
|
Reference |
A device that checks current flow values in any direction or designated direction. |
|
|
Reference |
Properties of current transformer asset. |
|
|
Reference |
A multi-purpose curve or functional relationship between an independent variable (X-axis) and dependent (Y-axis) variables. |
|
|
Base |
Multi-purpose data points for defining a curve. The use of this generic class is discouraged if a more specific class can be used to specify the x and y axis values along with their specific data types. |
|
|
Lookup |
Style or shape of curve. |
|
|
Reference |
All the customers, including individual and organization customers. A customer is generally defined as a party using one or more services from the operator. |
|
|
Reference |
To define relationship between customer and account including the history on the relationship. |
|
|
Reference |
Various customer proof document provided for customer order, contract, and so on. |
|
|
Reference |
This is the base class for defining Customer Facing Services. A Customer Facing Service is an abstraction that defines the characteristics and behavior of a particular Service as seen by the Customer or other appropriate Party Role. This means that this Party Role purchases, leases, uses and/or is otherwise directly aware of this type of Service. This is in direct contrast to ElementFacingServices, which support CustomerFacingServices but are not seen or purchased directly by the Customer. Customer Facing Service is visible to the customer, therefore can be purchased to be a subscription. |
|
|
Lookup |
The lookup code for grouping the customers based on any criteria defined by the service operator. |
|
|
Reference |
A grouping of the customers based on any criteria defined by the service operator. |
|
|
Reference |
Subtype of Customer (and Party), which contains details of individuals as opposed to organizations. |
|
|
Lookup |
Customer kind (meant for enumerated list). |
|
|
Derived |
The result measures from mining analysis. |
|
|
Reference |
It stores an event celebrated or observed by a customer. For example:
|
|
|
Lookup |
A categorization of Customer Occasions. |
|
|
Base |
Captures information about orders placed by customers. |
|
|
Reference |
The document provided while submitted customer order. |
|
|
Base |
Captures information about each item in the customer order. |
|
|
Reference |
Subtype of Customer (and Party), which contains details of organizations as opposed to individuals. An organization can also consist of one individual only (for example, ''independent''). |
|
|
Reference |
To define which customers an outage notification sends to. |
|
|
Reference |
It captures the restricted information for the customer or prospects - typically personal information used in segmentation. (income level, and so on). |
|
|
Lookup |
Customer classification in its income/revenue term. For example: Customer with income/revenue of $10000/Month, or 1Billion/Year (organizational). This is not to be confused with ''ARPU Band'', which bins the customer revenue (monthly payment as an example) to the operator. |
|
|
Reference |
To determine revenue band of customer. Customer's revenue band may drift month by month. |
|
|
Reference |
Scores or Score ranges that may be assigned to a customer based on credit, behavior, or other criteria. For example: 1,2,3,4,5 or 1~10,1 1~20. Customer score can be rated based on the Customer Behavior, Credit, or another criteria. |
|
|
Reference |
The Segments table holds details of customer segments identified by business analysis activities, like Data Mining. A segment identifies distinct groupings of customers or accounts with similar characteristics. The segments are typically used in marketing Campaigns. |
|
|
Reference |
The segmentation model used to profile the customers. For example,
|
|
|
Reference |
To keep track of how the customer is related to the SIC/NASIC, and also keep the history. One Organization may operate in multiple business area. For individual customer, this indicate the job he is taking. |
|
|
Reference |
How the customer came in touch to the sales team. For example:
Very important for campaign planning and management. |
|
|
Lookup |
This level identifies or groups customers such as residential or corporate. |
|
|
Reference |
Customer Work Assignment |
|
|
Reference |
A cut separates a line segment into two parts. The cut appears as a switch inserted between these two parts and connects them together. As the cut is normally open there is no galvanic connection between the two line segment parts. But it is possible to close the cut to get galvanic connection. The cut terminals are oriented towards the line segment terminals with the same sequence number. Hence the cut terminal with sequence number equal to 1 is oriented to the line segment's terminal with sequence number equal to 1. The cut terminals also act as connection points for jumpers and other equipment. For example, a mobile generator. To enable this, connectivity nodes are placed at the cut terminals. Once the connectivity nodes are in place any conducting equipment can be connected at them. |
|
|
Reference |
Action on cut as a switching step. |
|
|
Lookup |
Kind of action on cut or jumper. |
|
|
Reference |
Calendar day in the day dimension. |
|
|
Lookup |
Group of similar days. For example it could be used to represent weekdays, weekend, or holidays. |
|
|
Reference |
The parts of the DC power system that are designed to carry current or that are conductively connected through terminals. |
|
|
Reference |
A wire or combination of wires not insulated from one another, with consistent electrical characteristics, used to carry direct current between points in the DC region of the power system. |
|
|
Lookup |
Ranges of time used to group debt based on the age of the debt. For example:
Postpaid customers are billed on a monthly basis for the usage of services in the month. At the end of the billing month for the customer an invoice is sent to the customer for which customer is supposed to pay by payment due date. |
|
|
Base |
A special type of interaction to collect defaulted payment from customer by the in-house debt collector. |
|
|
Base |
The assignment of debt collection case to external debt collection agency. Currently the status of the collection is tracked inside the assignment. If detailed status history is required, another 2 ''Status History + Status Type'' entities could be created. |
|
|
Base |
Normally the collection assignment are sent to collector in a batch. |
|
|
Reference |
Demand response program. |
|
|
Reference |
One of a sequence of time intervals defined in terms of real time. It is typically used in association with Tariff Profile to define the intervals in a time of use tariff structure, where startDateTime simultaneously determines the starting point of this interval and the ending point of the previous interval. |
|
|
Reference |
A feature or quality used to make recognizable or to define somebody or something, such as age, income, education, revenue, and so forth. |
|
|
Reference |
A sub-level group or category further qualifying a set of data (Profile Group) collected about a customer to assist in marketing efforts. For example:
|
|
|
Reference |
The domain of classifications used to group profile information about a Party. For example:
|
|
|
Reference |
This entity stores the derived value of the customer. These value could have multiple value types or value measures. |
|
|
Lookup |
Lookup for various reason the direct debit payment become the current status. For example:
|
|
|
Reference |
A manually operated or motor operated mechanical switching device used for changing the connections in a circuit, or for isolating a circuit or equipment from a source of power. It is required to open or close circuits when negligible current is broken or made. |
|
|
Base |
Discrete represents a discrete Measurement. That is, a Measurement representing discrete values. For example, a Breaker position. |
|
|
Base |
DiscreteValue represents a discrete Measurement Value. |
|
|
Reference |
Parent class for different groupings of information collected and managed as a part of a business process. It will frequently contain references to other objects, such as assets, people and power system resources. |
|
|
Base |
Current status information relevant to an entity. |
|
|
Lookup |
All types of the documents customer may provide to service provider for identification. For example: 1. Driver License Photocopy. 2. Address certification. 3. Bank Card photocopy. |
|
|
Lookup |
The group of document types of which customer may provide to service provider for identification. For example Mandatory Document, Legal Requirement, Income Proof Document, and so on. For example: 1. Driver License Photocopy. 2. Address certification. 3. Bank Card photocopy. |
|
|
Reference |
Assigns different document types into different document type groups. |
|
|
Reference |
End device group assigned to a demand response program. |
|
|
Reference |
Agreement related to a demand response program. |
|
|
Derived |
Derived table on demand response program resulted load reduction by region by day. |
|
|
Lookup |
The education level of the customer. |
|
|
Reference |
Electricity service |
|
|
Reference |
Employee of the utility. Sub entity of party individual. |
|
|
Base |
The actual shifts the hourly employees have worked in, including break time. |
|
|
Base |
Subtype of cost, which occurs to employee. For example, salary and bonus for employee. |
|
|
Lookup |
The various designations present in an organization for the employees. For example, Consultant, Engineer and so on. |
|
|
Reference |
Keep the relationship between employee and job role. |
|
|
Lookup |
Delegate, primary role, or secondary role. |
|
|
Reference |
The languages the employee can serve, especially for call center agent and sales representatives. |
|
|
Reference |
It captures the restricted information for the employee. |
|
|
Reference |
This entity stores the planned schedule for an employee, which consists of the store, job role and shift the employee is planned to be working for. |
|
|
Base |
A record that a particular employee has been trained in performing a particular Task. |
|
|
Lookup |
This lookup describes types of Employee. Possible values can be PartTime, Contractual, Full Time and so on. |
|
|
Reference |
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, and so on. 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 (for example, water, gas, electricity). Some devices may use an optical port that conforms to the ANSI C12.18 standard for communications. |
|
|
Reference |
End Device Capability |
|
|
Base |
Instructs an end device (or an end device group) to perform a specified action. |
|
|
Reference |
Detailed description for a control produced by an end device. Values in attributes allow for creation of recommended codes to be used for identifying end device controls as follows: <type>.<domain>.<subDomain>.<eventOrAction>. |
|
|
Base |
Timing for the control actions of end devices. |
|
|
Base |
Timing for the control actions of end devices. |
|
|
Lookup |
End Device Domain |
|
|
Reference |
To define relationship between End Device and End Device Ctrl and the history of the relationship. |
|
|
Reference |
To define relationship between End Device and End Device Group and the history of the relationship. |
|
|
Base |
Event detected by a device function associated with end device. |
|
|
Derived |
Derived table on end device event by customer by day. |
|
|
Aggregate |
Aggregate fact table on end device event by customer by month. |
|
|
Derived |
Derived table on end device event by device by day. |
|
|
Aggregate |
Aggregate fact table on end device event by device by month. |
|
|
Reference |
Name-value pair, specific to end device events. |
|
|
Lookup |
End device event or action. |
|
|
Lookup |
Detailed description for an event produced by an end device. Values in attributes allow for creation of recommended codes to be used for identifying end device events as follows: <type>.<domain>.<subDomain>.<eventOrAction>. |
|
|
Reference |
Function performed by an end device such as a meter, communication equipment, controllers, and so on. |
|
|
Lookup |
Type of end device function. |
|
|
Reference |
Abstraction for management of group communications within a two-way Automated Meter Reading (AMR) system or the data for a group of related end devices. Commands can be issued to all of the end devices that belong to the group using a defined group address and the underlying AMR communication infrastructure. |
|
|
Reference |
End device control capability assigned to an end device group. |
|
|
Reference |
End device data. |
|
|
Lookup |
End device sub domain. |
|
|
Lookup |
End device type. |
|
|
Reference |
The class describes an area having energy production or consumption. |
|
|
Reference |
Generic user of energy - a point of consumption on the power system model. |
|
|
Reference |
A single phase of an energy consumer. |
|
|
Lookup |
Energy Flow Direction |
|
|
Reference |
The parts of a power system that are physical devices, electronic or mechanical. |
|
|
Reference |
A modeling construct to provide a root class for containing equipment. |
|
|
Base |
This entity keeps track of all interactions with Service Provider. Event can occur related to a provider (for example, equipment down, service disruption) or a customer(for example, service order, paying bill). It will be used to track customer behavior, in order to make special campaigns or analyze cost of customers. Normally the event incurs some cost and may generate revenue for the operator. |
|
|
Base |
The events occurring to account. For example:
|
|
|
Base |
This entity relates events to other Events. The Event Relationship reason describes why a relationship exist between two events. |
|
|
Lookup |
Lookup of all possible reasons why a relationship exists between two Events. Such as premise, result in. |
|
|
Lookup |
Lookup of all types of relationship between two Events. |
|
|
Lookup |
Root category of all Event Types, it's used to distinguish different events. |
|
|
Base |
The chat history between the service representative and the customer. It shares the pk from event, as event code. |
|
|
Base |
The chat history details between the service representative and the customer. Each chat message is saved as one record. |
|
|
Lookup |
A classification for the types of Events that can occur. For example:
|
|
|
Base |
The payroll made to employee, except sales commission. |
|
|
Base |
A sub-type of event, it keeps all events, occurred for a specific Equipment. |
|
|
Base |
A subtype entity of Event, it keeps all events, which occurred for a specified Geographic Area which may affect the Business. For example:
|
|
|
Base |
The delivery of Invoice to customer. For example: 1. Printed letter 2. Email 3. Duplicate Printed Letter on request |
|
|
Base |
Events associated with each event or transaction on customer loyalty program. For example: Customer earn Loyalty points Bonus points are awarded to the customer Points are redeemed by Customer. This entity may be better named as ''event account balance change''. |
|
|
Base |
This entity relates parties with events. A Party can have many events; and an event can involve many parties. |
|
|
Base |
The Party Interactions table records all interactions or communications with the customer. The interactions include: - outages - inbound and outbound telemarketing - direct mail, SMS, email - service calls - complaints - Debt collection. |
|
|
Base |
Sub type of Event Party Interaction, which represents all phone call interactions from the customer with details information including: holding, queuing, interaction time, run by the Automated Voice Response. |
|
|
Base |
Sub type of Event Party Interaction, which represents the email interaction from customers. |
|
|
Base |
When multiple threads are discussed in a single interaction event, this line item lists the involved threads and other information including accounts, subscriptions, and so on. This is also the M:M relationship between the interaction thread and the event. |
|
|
Base |
Sub Type of Event Party Interaction, which represents the interaction with customer through letter. |
|
|
Base |
Tracks multiple employees who participate in a same interaction with a customer. |
|
|
Base |
Subtype of Interaction event, to record all the visits to the stores (for sales or supports). Some shops equipped with Queuing machine can track customers queue Time, No Show, and so on. |
|
|
Base |
The Party Event table track all changes to party information. For example:
|
|
|
Lookup |
The code for the role that a Party has with an Event. For example: customer who reported the event, customer affected by event, party who caused the event. |
|
|
Lookup |
The reason that an event occurred and their descriptions. For example as account suspension because of arrearage. |
|
|
Lookup |
Provide an higher category for event reasons applied to each sub event entity. |
|
|
Lookup |
The domain of results that may occur in the resolution of an Event. |
|
|
Lookup |
A reason for a particular response obtained for an event. |
|
|
Lookup |
Lookup for the description of a result or any events. For example:
|
|
|
Base |
Describes the event status such as completed, pending, in progress, suspended, canceled, abandoned. |
|
|
Lookup |
This entity describes the reason for the event status. For example, if the event status is rejected, the event status reason will describe the reason the event was rejected. Reasons include insufficient funds, card reported as stolen, and so on. |
|
|
Lookup |
This entity describes the event status such as completed, pending, in progress, suspended, canceled, abandoned, and so on. |
|
|
Lookup |
This entity keeps all types of events under each category: For example: 1. In Loyalty Program event 1.1 Points Accumulation. 1.2 Redemption. 2 Account Suspension (because of late payment, and so on). |
|
|
Base |
The event of customer registering at website to apply for service. The potential customer can register at website to apply for service. The call center then call them to confirm the order. Before the order was generated, the application form info (date, and so on) was saved in web registration with pointer to Party and Initiate. |
|
|
Base |
Subtype of Customer Interaction event, to track the customer visit on service provider website. This Web Visit Event contains the customer visit Session, and details of visited pages are in Interaction Navigation History. |
|
|
Reference |
A source of information that helps define a credit worthiness of the customer. |
|
|
Reference |
To indicate which external agency/institute provided the credit profile for the given customer. |
|
|
Reference |
Represents the source from which the Demographic Information or customer information is obtained. |
|
|
Lookup |
Type of the external organization. |
|
|
Reference |
FACTS device asset. |
|
|
Lookup |
Type of FACTS device. |
|
|
Reference |
Abnormal condition causing current flow through conducting equipment, such as caused by equipment failure or short circuits from objects not typically modeled. For example, a tree falling on a line. |
|
|
Reference |
Parameters of fault indicator asset. |
|
|
Lookup |
Type of resetting the fault indicators. |
|
|
Reference |
Substation feeder. |
|
|
Reference |
Substation a feeder is connected. |
|
|
Base |
Value measured by a meter or other asset, or calculated by a system. Each Reading is associated with a specific Reading Type. |
|
|
Reference |
Various current financial properties associated with a particular asset. Historical properties may be determined by Activity Records associated with the asset. |
|
|
Reference |
Quarter level in the fiscal calendar. |
|
|
Reference |
Year level in the fiscal calendar. |
|
|
Reference |
An abstracted entity to provide common structure for all type of characteristics. All various type of characteristics may be applicable to the subject, including product, service, network element, and so on. This is a flexible way to define addition attributes for those entities with complex features. |
|
|
Reference |
Possible values that a characteristic may take, including predefined choices, or free numeric values. |
|
|
Base |
Flood Information |
|
|
Reference |
A device to convert from one frequency to another (for example, frequency F1 to F2) comprises a pair of FrequencyConverter instances. One converts from F1 to DC, the other converts the DC to F2. |
|
|
Reference |
An overcurrent protective device with a circuit opening fusible part that is heated and severed by the passage of overcurrent through it. A fuse is considered a switching device because it breaks current. |
|
|
Reference |
Input pin for a special protection scheme gate. |
|
|
Reference |
Relationship between unit operating cost (Y-axis) and unit output active power (X-axis). The operating cost curve for thermal units is derived from heat input and fuel costs. The operating cost curve for hydro units is derived from water flow rates and equivalent water costs. |
|
|
Reference |
The generating unit's Operator-approved current operating schedule (or plan), typically produced with the aid of unit commitment type analyses. The X-axis represents absolute time. The Y1-axis represents the status (0=off-line and unavailable: 1=available: 2=must run: 3=must run at fixed power value: and so on.). The Y2-axis represents the must run fixed power value where required. |
|
|
Lookup |
Gender lookup table, male or female. |
|
|
Reference |
A single or set of synchronous machines for converting mechanical power into alternating-current power. For example, individual machines within a set may be defined for scheduling purposes while a single control signal is derived for the set. In this case there would be a GeneratingUnit for each member of the set and an additional GeneratingUnit corresponding to the set. |
|
|
Reference |
Generating unit rotating machine assignment. |
|
|
Lookup |
Unit control modes. |
|
|
Lookup |
The source of controls for a generating unit. |
|
|
Lookup |
Operating mode for secondary generator control. |
|
|
Reference |
An arbitrary switching step. |
|
|
Reference |
Building level in Geography Hierarchy. This is commonly used in urban areas where the service operator can server many customers in the same building. |
|
|
Reference |
City level in Geography Hierarchy. |
|
|
Reference |
Complex level in Geography Hierarchy. Complex include the complexes (a few building forming enclosed area) in the city, Universities, or industrial parks, and so on. Neighborhood is also named as ''Community'' or ''complex''. A complex consists of several buildings in the urban area. |
|
|
Reference |
Country level in Geography Hierarchy. |
|
|
Reference |
County level in Geography Hierarchy. County may be at different levels in different countries. In this model, the county is defined as a level below the city, which is close to ''District''. |
|
|
Reference |
A classification for a Geo-Demographic Profile attribute. Groups include: Population Characteristics, Urban/Rural, Gender, Race, Ethnic Background, Age. |
|
|
Reference |
A classification for a Geography Profile Group. For example: for the profile group race: Percent White, Percent Black, Percent Native American, Percent Pacific Islander/Asian, Percent Persons Of Hispani. |
|
|
Reference |
This entity stores the value of the Gwo demography Profile. For example: Population the value (ex 102977) will be stored here). |
|
|
Reference |
This describes the various physical geography entities that can be created. For example Geo Entities could be Sales Region North, State, country, city, street, building, and so on. |
|
|
Reference |
This entity defines the Geo entity name to a Hierarchy level and also defined the parent child relationship. Thus we link a hierarchy level to a physical geography entity. |
|
|
Reference |
Geography Entity Hierarchy Level Assignment |
|
|
Reference |
This stores the details of a Geographical hierarchy, like you might have Geo sales hierarchy, Geo customer hierarchy, Geo purchase hierarchy and so on. |
|
|
Reference |
Captures the geographical hierarchy along with the levels. |
|
|
Reference |
Assign the geography entity to the right level in the hierarchy. |
|
|
Reference |
This entity stores all the geographical levels as required by the analytics. Level definitions could be as simple as Level 1, level 2 or could be Geo 1, Geo 2 and so on. |
|
|
Reference |
This stores the attributes at a specific geographical level. |
|
|
Reference |
This entity stores the various Geography Level Attributes. For example, in a Sales hierarchy you have North sales region and you want to store the population of that region. It can stored here in this entity. |
|
|
Reference |
Region level in Geography Hierarchy. |
|
|
Reference |
State level in Geography Hierarchy. |
|
|
Reference |
City level in Geography Hierarchy. |
|
|
Reference |
Sub region level in Geography Hierarchy. |
|
|
Reference |
World level in Geography Hierarchy. |
|
|
Reference |
The GL accounts are defined to track financial status from a specific angle. All GL Journals are posted to various GL Accounts to reflect financial impact of each business transaction. Each account are defined by certain codes and flags, including whether the account is enabled, whether detail posting or detail budgeting is allowed, and others. Segment values are stored in the SEGMENT columns. Each Segment column links the GL Account to the corresponding GL Segment record. Moreover, the SEGMENT columns that are used are not guaranteed to be in any order. Summary accounts have SUMMARY_FLAG = 'Y' and TEMPLATE_ID not NULL. Detail accounts have SUMMARY_FLAG = 'N' and TEMPLATE_ID NULL. |
|
|
Reference |
Defines the relationship between two GL Accounts to form an Account Hierarchy. It stores lists of the detail accounts associated with each summary account. |
|
|
Reference |
Defines different types of GL Account, including Cash, Bank, Equipment, and so on. |
|
|
Lookup |
General Ledger Account type. For example:
|
|
|
Base |
GL Balance stores actual, budget, and encumbrance balances for detail and summary accounts. This table stores ledger currency, foreign currency, and statistical balances for each accounting period that has ever been opened. ACTUAL_FLAG is either 'A', 'B', or 'E' for actual, budget, or encumbrance balances, respectively. |
|
|
Reference |
Subtype of GL Segment which links GL Account to a specific Cost Center. |
|
|
Base |
Defines the relationship between GL Journal Entry Lines and Subledger journal entry Lines. It stores individual transactions from subledgers that have been summarized into General Ledger journal entry lines. |
|
|
Base |
GL Journal Entry Header stores journal entries. There is a one-to-many relationship between journal entry batches and journal entries. Each record includes the associated batch ID, the journal entry name and description, and other information about the journal entry. This table corresponds to the Journals window of the Enter Journals form. STATUS is 'U' for unposted and 'P' for posted. Other status indicate that an error condition was found. CONVERSION_FLAG equal to 'N' indicates that you manually changed a converted amount in the Journal Entry Lines zone of a foreign currency journal entry. In this case, the posting program does not re-convert your foreign amounts. This can happen only if your user profile option MULTIPLE_RATES_PER_JE is 'Yes'. BALANCING_SEGMENT_VALUE is null if there is only one balancing segment value in your journal entry. If there is more than one, BALANCING_SEGMENT_VALUE is the greatest balancing segment value in your journal entry. |
|
|
Base |
GL Journal Entry Batch stores journal entry batches. Each row includes the batch name, description, status, running total debits and credits, and other information. This table corresponds to the Batch window of the Enter Journals form. STATUS is 'U' for unposted, 'P' for posted, 'S' for selected, 'I' for in the process of being posted. Other values of status indicate an error condition. STATUS_VERIFIED is 'N' when you create or modify an unposted journal entry batch. The posting program changes STATUS_VERIFIED to 'I' when posting is in process and 'Y' after posting is complete. |
|
|
Lookup |
GL_JE_CATEGORIES_TL stores journal entry categories. Each row includes the category name and description. Each journal entry in your General Ledger application is assigned a journal entry category to identify its purpose. For example, Purchase Invoices, Receiving, and so on. |
|
|
Base |
GL Journal Entry Line stores the journal entry lines to track changes to each GL Account made by a certain GL Journal Entry. There is a one-to-many relationship between journal entries and journal entry lines. Each row in this table stores the associated journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal line. STATUS is 'U' for unposted or 'P' for posted. |
|
|
Reference |
GL Ledger stores information about the ledgers and the ledger sets defined in the Financial system. Each row includes the ledger or ledger set name, short name, description, ledger currency, calendar, period type, chart of accounts, and other information. A GL Ledger is defined by 4C, chart of accounts(COA), functional currency, accounting calendar, and Accounting method. |
|
|
Reference |
Assign the GL accounts to Ledgers to form the Chart Of Account (COA). |
|
|
Reference |
Assigns the GL Account to corresponding Organization Business Unit. |
|
|
Reference |
GL Period stores information about the accounting periods you define using the Accounting Calendar form. Each row includes the start date and end date of the period, the period type, the fiscal year, the period number, and other information. |
|
|
Reference |
Assigns the GL Account to corresponding Product. |
|
|
Reference |
Assigns the GL Account to corresponding Projects. |
|
|
Reference |
Each GL Account consists of a few independent segments, which are determined by Financial System setup. |
|
|
Lookup |
Type of GL Segment. For example, Project, Account, Project, and so on. |
|
|
Reference |
GL Subledger is the subsidiary ledger, and stores original business transaction information that varies depending on the application. It includes at least a row for each application, who may feed financial journal entries into GL application. |
|
|
Base |
GL Subledger Journal Entry stores subledger journal entries. The subledger Journal Ledger record the transaction at original level, that is, each invoice, or each Purchase Order should have one entry in subledger journal entry. |
|
|
Base |
GL Subledger Journal Entry Line stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger. The GL Subledger Journal Entry Line breaks down the subledger JE into different GL Accounts. |
|
|
Reference |
Relationship between the generating unit's gross active power output on the X-axis (measured at the terminals of the machine(s)) and the generating unit's net active power output on the Y-axis (based on utility-defined measurements at the power station). Station service loads, when modeled, should be treated as non-conforming bus loads. There may be more than one curve, depending on the auxiliary equipment that is in service. |
|
|
Reference |
A manually operated or motor operated mechanical switching device used for isolating a circuit or equipment from ground. |
|
|
Reference |
A switch used to connect to ground. These are not normally carry power, but are important for fault analysis, unbalanced analysis, or for grounding considerations. |
|
|
Reference |
Headend system to collect meter data and send to utility through AMI (Advanced Metering Infrastructure). |
|
|
Reference |
This table contains information at the hour level. |
|
|
Reference |
Assign time of use to an hour. |
|
|
Reference |
Captures household information which the individual customer may belong to. Operator may recognize household by customer's shared address and then generate this data according to the customer's demographic value. |
|
|
Lookup |
Specifies the capability of the hydro generating unit to convert energy as a generator or pump. |
|
|
Reference |
A generating unit whose prime mover is a hydraulic turbine. For example: Francis, Pelton, Kaplan. |
Table 2-2 Utilities Data Model Entities I-P
| Entity Name | Type | Description |
|---|---|---|
|
|
Reference |
This is a root class to provide common identification for all classes needing identification and naming attributes. |
|
|
Base |
Description of a problem in the field that may be reported in a trouble ticket or come from another source. It may have to do with an outage. |
|
|
Reference |
To define relationship between Work and Incident including the history of the relationship. |
|
|
Reference |
Individual demography value, the detailed information and its value collected about customers. For example age will have Demography group as AGE, Attribute as various bands and value as 15 years which will be stored in this entity. |
|
|
Base |
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. Interval Data is sometimes also called "Interval Data Readings" (IDR). |
|
|
Lookup |
Lookup for all possible result of initiatives. |
|
|
Lookup |
The lookup for different types of Initiatives. |
|
|
Reference |
The installment payment scheme for customer bills. |
|
|
Base |
Describes the pre-defined answers(Choices) for the Initiative Questions table. The Initiative Answers table is only used if the questions have answers in the multiple-choice format. |
|
|
Reference |
Keep channels which is used for interacting between provider and customer. For example, call center, online business system, counter. |
|
|
Lookup |
A reference table that documents whether the primary intent of an initiative is for inbound or outbound communications. |
|
|
Base |
The history of customer navigation path in each interaction call, or web visit. For example, in IVR call, customer may go through Welcome, then (1) Outages, then (1) Account balance query. Those actions are realized as three records here. |
|
|
Reference |
Interaction Navigation Item tracks all the possible places where customer may go to in the IVR or Web service context. |
|
|
Lookup |
The different priorities which can be assigned to each party interaction. |
|
|
Base |
Tracks the responses provided by the customer to the questions asked as part of the communication with the customer. |
|
|
Lookup |
Interaction reason table is to track why the interaction happened. For example:
|
|
|
Lookup |
Type of response received from customer interaction. For example: Showed Interest without Decision, Offer accepted, Never call again, and so on. |
|
|
Lookup |
Interaction Status is a reference table the documents the various states an interaction with a customer may be in. For example:
|
|
|
Base |
Interaction Transfer History |
|
|
Lookup |
The reason that an interaction is transferred from one agent to another one. For example, wrong routing, Another Business Interactions, to supervisor, and so on. |
|
|
Lookup |
Interaction Types s a reference table that describes the different types of interaction between the company and a customer. For example: 1. eMail 2. Call Center Inbound 2.1 Call center inbound complain 2.2 Call center inbound query 3. Call Center Outbound 3.1 Call Center outbound service quality survey 4. Walk-In 5. Letter. |
|
|
Lookup |
Interharmonics are represented as a rational number with a numerator and a denominator. |
|
|
Base |
The Invoices table documents each invoice issued to each account. An invoice represents the request for payment for goods and services during a specified period. |
|
|
Base |
This is to record all adjustment made on the invoices. In current design, Adjustment ID & Invoices code serve the primary, therefore, 1 adjustment could make change to multiple invoices. |
|
|
Reference |
Invoice adjustment quota are assigned to employee according to their job role and levels. |
|
|
Lookup |
The format specification (including header, font, and so on) of each invoice delivered to the customer. |
|
|
Lookup |
Type of delivery of Invoice to customer. For example: 1. Printed letter 2. Email 3. Duplicate Printed Letter on request. |
|
|
Base |
This is to track all discount applied to the invoices. It's on the invoice level. For example, if you want to reward all your customers who pay by credit card, you can create the payment discount for all invoices belonging to those customers. |
|
|
Lookup |
The reason why the discount was put on the invoice. |
|
|
Lookup |
The categories of discounts applied to a Customer Invoices. |
|
|
Base |
Invoice Item holds all components that appear on the invoice. |
|
|
Base |
Provide additional information for specific Invoice Item. |
|
|
Lookup |
Specify the type to the charge detail. |
|
|
Base |
Defines the relationship between Invoice Items. |
|
|
Lookup |
Invoice Detail Types is a reference table that describes the different types of information available in the Invoice Details table. |
|
|
Base |
To indicate which payment reconcile which invoice. |
|
|
Base |
Payment Terms of each invoices. For example: payment days and late payment fee, and so on. The late payment fee might be calculated according to invoice value and payment date. |
|
|
Lookup |
The term for payment. It maybe be by the time aspect. For example Monthly, and with how to calculate the penalty for defaults for month/year. |
|
|
Base |
Status history for an invoice. For example, the invoice may experience status change from open to closed, or from open to extended. |
|
|
Lookup |
Type of invoice status. For example
|
|
|
Base |
The Tax item applied to the Invoice. |
|
|
Lookup |
Type of invoice according to invoice generation process. For example: 1. Summary Invoice for hierarchical account. 2. Standard Invoice. 3. Trial Billing Invoice. |
|
|
Reference |
The schedule has time points where the time between them varies. |
|
|
Reference |
Time points for a schedule where the time between the points varies. |
|
|
Lookup |
The IVR Menu Item, which can be used to construct the whole IVR navigation system. Each IVR menu item represent a group or a specific business function. |
|
|
Reference |
The type of occupation that customer is currently taking, which is the principal activity customer do to earn money. |
|
|
Reference |
The job role. |
|
|
Reference |
Joint connects two or more cables. It includes the portion of cable under wipes, welds, or other seals. |
|
|
Lookup |
Configuration type for joints. |
|
|
Lookup |
Fill type for Joint. |
|
|
Base |
Cross-Reference from Subledger Journal Entry Line to Invoice Item. |
|
|
Reference |
A short section of Conductor with negligible impedance which can be manually removed and replaced if the circuit is de-energized. Zero-impedance branches can potentially be modeled by other equipment types. |
|
|
Reference |
Action on jumper as a switching step. |
|
|
Lookup |
Speaking or written language. |
|
|
Lookup |
Type of Letter send to customer according to the content and purpose. For example:
|
|
|
Reference |
Dates for lifecycle events of an asset. |
|
|
Reference |
Specifies one limit value for a Measurement. A Measurement typically has several limits that are kept together by the LimitSet class. The actual meaning and use of a Limit instance (that is, if it is an alarm or warning limit or if it is a high or low limit) is not captured in the Limit class. However the name of a Limit instance may indicate both meaning and use. |
|
|
Reference |
Specifies a set of Limits that are associated with a Measurement. A Measurement may have several LimitSets corresponding to seasonal or other changing conditions. The condition is captured in the name and description attributes. The same LimitSet may be used for several Measurements. In particular percentage limits are used this way. |
|
|
Reference |
Contains equipment beyond a substation belonging to a power transmission line. |
|
|
Reference |
The class is the root or first level in a hierarchical structure for grouping of loads for load flow load scaling. |
|
|
Reference |
A mechanical switching device capable of making, carrying, and breaking currents under normal operating conditions. |
|
|
Reference |
The class is the third level in a hierarchical structure for grouping of loads for load flow load scaling. |
|
|
Reference |
Models the characteristic response of the load demand due to changes in system conditions such as voltage and frequency. This is not related to demand response. If LoadResponseCharacteristic.exponentModel is True, the voltage exponents are specified and used as to calculate: Active power component = Pnominal * (Voltage/cim:BaseVoltage.nominalVoltage) ** cim:LoadResponseCharacteristic.pVoltageExponent Reactive power component = Qnominal * (Voltage/cim:BaseVoltage.nominalVoltage)** cim:LoadResponseCharacteristic.qVoltageExponent Where * means "multiply" and ** is "raised to power of". |
|
|
Reference |
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 position points (coordinates) in a given coordinate system. |
|
|
Reference |
The Loyalty Programs table identifies the marketing loyalty programs that a customer may be a member of. |
|
|
Lookup |
The Loyalty Program Event Types table is a reference table that describes the categories of events that can be applied against a Party and loyalty program. |
|
|
Reference |
Organization that maintains assets. |
|
|
Reference |
Organization that manufactures asset products. |
|
|
Lookup |
Marital Status |
|
|
Reference |
Market Area denotes a geographic area for which resident demographic data is available. |
|
|
Reference |
Level of classification inside the market areas. This classification can be based on, 1. Community: This represented as the one set of demographic attributes as described in the demography entity. 2. Geographic 3. User defined. |
|
|
Reference |
Defines the customer document requirements of each service or product market plan. |
|
|
Reference |
Market Role |
|
|
Reference |
A market segment is identified to group certain common areas where business can be conducted. For example, a group of persons, a specific geographical area, and so on. Customer Segment and Marketing Segment: The market segments are defined according to manual marketing analysis, or external marketing source, while the Customer Segments are normally generated from Mining activities on existing customer base. |
|
|
Reference |
The inclusion relationship between two market segments. |
|
|
Base |
A Measurement represents any measured, calculated or non-measured non-calculated quantity. Any piece of equipment may contain Measurements. For example, a substation may have temperature measurements and door open indications, a transformer may have oil temperature and tank pressure measurements, a bay may contain a number of power flow measurements and a Breaker may contain a switch status measurement. The PSR - Measurement association is intended to capture this use of Measurement and is included in the naming hierarchy based on Equipment Container. The naming hierarchy typically has Measurements as leafs. For example, Substation-VoltageLevel-Bay-Switch-Measurement. Some Measurement represent quantities related to a particular sensor location in the network. For example, a voltage transformer (PT) at a busbar or a current transformer (CT) at the bar between a breaker and an isolator. The sensing position is not captured in the PSR - Measurement association. Instead it is captured by the Measurement - Terminal association that is used to define the sensing location in the network topology. The location is defined by the connection of the Terminal to Conducting Equipment. If both a Terminal and PSR are associated, and the PSR is of Conducting Equipment, the associated Terminal should belong to that ConductingEquipment instance. When the sensor location is needed both Measurement-PSR and Measurement-Terminal are used. The Measurement-Terminal association is never used alone. |
|
|
Lookup |
Kind of measurements. |
|
|
Reference |
Location a measurement is made. |
|
|
Base |
The current state for a measurement. A state value is an instance of a measurement from a specific source. Measurements can be associated with many state values, each representing a different source for the measurement. |
|
|
Reference |
Measurement value quality defined by its attributes. |
|
|
Reference |
Measurement Value Source describes the alternative sources updating a Measurement Value. User conventions for how to use the Measurement Value Source attributes are described in the introduction to IEC 61970-301. |
|
|
Reference |
This is any object the campaign message may appear on. Like a Page in the newspaper, or a time slot in the TV broadcasting. |
|
|
Reference |
Build the Media Object into a hierarchy, with certain levels. |
|
|
Lookup |
Type of the media object. For example:
|
|
|
Reference |
Physical asset that performs the metering role of the usage point. Used for measuring consumption and detection of events. |
|
|
Reference |
Identifiers a meter may have. |
|
|
Base |
Set of values obtained from the meter. |
|
|
Derived |
Derived fact table on daily meter reading. |
|
|
Derived |
Derived fact table on hourly meter reading. |
|
|
Aggregate |
Aggregate fact table on meter reading by month. |
|
|
Aggregate |
Aggregate fact table on tine of use meter reading by month. |
|
|
Reference |
Meter Register Assignment. |
|
|
Reference |
Work involving meters. |
|
|
Lookup |
Lookup for status. For example:
|
|
|
Reference |
The North American Industry Classification System (NAICS) has replaced the U.S. Standard Industrial Classification (SIC) system. This is an example for NAICS classification for banking: 52 Finance and Insurance 521 Monetary Authorities - Central Bank. |
|
|
Lookup |
Nationality |
|
|
Reference |
Non conform load represent loads that do not follow a daily load change pattern and changes are not correlated with the daily load change pattern. |
|
|
Reference |
Loads that do not follow a daily and seasonal load variation pattern. |
|
|
Reference |
An active power (Y1-axis) and reactive power (Y2-axis) schedule (curves) versus time (X-axis) for non-conforming loads. For example, large industrial load or power station service (where modeled). |
|
|
Reference |
A nuclear generating unit. |
|
|
Reference |
An operator of multiple power system resource objects. Multiple operating participants may operate the same power system resource object. This can be used for modeling jointly owned units where each owner operates as a contractual share. |
|
|
Reference |
Specifies the operations contract relationship between a power system resource and a contract participant. |
|
|
Reference |
Operation Tag |
|
|
Reference |
A value associated with a specific kind of limit. |
|
|
Reference |
A set of limits associated with equipment. Sets of limits might apply to a specific temperature, or season. For example, a set of limits may contain different severities of limit levels that would apply to the same equipment. The set may contain limits of different types such as apparent power and current limits or high and low voltage limits that are logically applied together as a set. |
|
|
Reference |
A document that can be associated with a conducting equipment to describe any sort of restrictions compared with the original manufacturer's specification or with the usual operational practice. For example, temporary maximum loadings, maximum switching current, do not operate if bus couplers are open, and so on. |
|
|
Reference |
Oracle Geometry is a super entity to all geographical entities, with SDO_GEOMETRY attribute as defined in Oracle Database 11g. |
|
|
Reference |
Areas within an organization chain. |
|
|
Reference |
The name of company, organization, or subsidiary that is recognizable to the consumer or the name of the store as it appears on the catalog, web channel, or brick and mortar store. Holds the information about different organization banners under which product or service are sold. |
|
|
Reference |
Any logical entity that is recognized as a part of the enterprise for business analysis and transactions. Classification for a business entity can include company, operation unit, store, or warehouse. Business Entity in an Organization represent any logical entity that is recognized as an enterprise for Business analysis and transactions. Possible classifications for a Business Entity can include, Company, Operation Units, Stores, Warehouse and so on. |
|
|
Reference |
A business unit of the organization that delivers a limited range of specific services through any sales channel. For example: retail or distribution. |
|
|
Lookup |
Type of Organization Business Unit. For example: 1. Call center 2. Branch Office. 3. Warehouse |
|
|
Reference |
Organization hierarchy level within an organization company and is the parent of one or more organization areas. |
|
|
Reference |
Organization hierarchy level within an organization corporate and is the parent of one or more organization chains. |
|
|
Reference |
Highest level of organization hierarchy and is the parent of one or more organization companies. |
|
|
Reference |
Organization hierarchy level within organization corporate. |
|
|
Reference |
User defined. Master list of all of the hierarchies in an organization. |
|
|
Reference |
The association table for the hierarchies and levels. |
|
|
Reference |
Assignment of Hierarchy Levels to organization hierarchy. Assignment table for Hierarchy levels to the Business Entities. |
|
|
Reference |
Version of organization hierarchy. The version table for the hierarchies. |
|
|
Reference |
List of all the business levels inside the organization. |
|
|
Reference |
Attributes of a business entity. |
|
|
Reference |
Attributes assigned to an organization level. Attributes applicable only to the corresponding level in the organization. Possible values that can be stored in this entity can be, Regional Language. |
|
|
Reference |
Publicly available and statistical information regarding the internal or external parties, such as DUNS number and number of employees. Market related information about an Organization. In LDM the Organization Market Data entity has the SIC code and DUNS number. Duns Numbers are specific to Organizations where as SIC codes are for Industry sectors. |
|
|
Reference |
Organization hierarchy level within an organization area and is the parent of one or more organization districts. Holds region within a company, chain area. |
|
|
Reference |
Identifies a way in which an organization may participate in the utility enterprise (for example, customer, manufacturer, and so on). |
|
|
Reference |
Sub-type of the organization business unit, it collects all information on (normally public) website managed by the operator. A website owned/commissioned by the organization from where product/services can be purchased and supported. |
|
|
Reference |
The location at which un-deployed assets are maintained. A place in which goods or merchandise are stored; a storehouse. |
|
|
Reference |
User defined attribute definitions and corresponding values regarding demographic statistics as related to an organization business unit. This entity stores the detailed information and its value collected about organizations. |
|
|
Reference |
Individual party associated with a party organization other than those defined such as Customer or Employee. For example, the contact person of a vendor, the chairman of a dealer. |
|
|
Base |
Document describing details of an active or planned outage in a part of the electrical network. A non-planned outage may be created upon:-a breaker trip, a fault indicator status change, a meter event indicating customer outage, a reception of one or more customer trouble calls, or an operator command, reflecting information obtained from the field crew. Outage restoration may be performed using a switching plan which complements the outage information with detailed switching activities, including the relationship to the crew and work. A planned outage may be created upon: a request for service, maintenance or construction work in the field, or an operator-defined outage for what-if/contingency network analysis. The associated outage plan defines operational restrictions and atomic switch actions to define the changes that, after applied, would result in a total or partial equipment outage as required for network analysis. |
|
|
Derived |
Derived fact table on outage by day. |
|
|
Aggregate |
Aggregate fact table on outage by month. |
|
|
Derived |
Derived fact table on outage by usage point. |
|
|
Reference |
Classification of outage types. Multiple outage codes may apply to a given outage or outage step. The primary overall outage type is recorded in 'OutageRecord.outageType'. There may be more than one classification per outage step and/or per outage record. Example codes/subcodes include: weather/ice, weather/lightning, wildlife/squirrel, wildlife/bird, burned/overload, burned/weather, wire down/accident, wire down/tree, wire down/vandalism, and so on. The typical outage code is in the inherited association to Name. The code is described in the inherited "description" attribute. |
|
|
Reference |
A document containing information to be sent to customers notifying that an outage will take place. This generates mailing lists for customers. |
|
|
Reference |
Document containing operational restrictions and atomic switch actions to define the changes in the network that, after applied, would result in a total or partial equipment outage, as required for network analysis. |
|
|
Base |
Document describing details of an outage in part of the electrical network, typically produced by a SCADA system following a breaker trip, or within a trouble call system by grouping customer calls. It has an associated outage step for each supply point. Primary cause of the outage is captured in 'type'. In some countries all outage restoration is performed using a switching schedule which complements the outage record and records the crew and any planned work. In other systems, it may be acceptable to manage outages including new work tasks without switching schedules. The relationship between OutageRecord and ErpPerson and Crew is inherited as each is a type of Document. |
|
|
Reference |
Outage Record Code Assignment. |
|
|
Reference |
Document with statistics of an outage. |
|
|
Reference |
The period that a piece of equipment is out of service. For example: for maintenance or testing; including the equipment's active power rating while under maintenance. The X-axis represents absolute time and the Y-axis represents the equipment's available rating while out of service. |
|
|
Reference |
Holds an outage start and end time for each supply point of an outage record. The supply point for a given step is the associated Power System Resource instance. |
|
|
Reference |
Code assigned to an outage step. |
|
|
Reference |
Usage points involved in an outage including history. |
|
|
Reference |
Assigns costs of a given promotion to a Partner or Party participating in the promotion. The service provider may partner with another Service Provider or with sales partner to do joint promotion jointly. |
|
|
Reference |
A party is a real person, organization, branch, subsidiary, legal entity, holding company, and so on. Any real thing that you would want to put a name to is a party. The attributes of a party are universal. In other words, they are independent of your selling (or ultimately buying) relationship with the party. A party is not necessarily a customer. It can represent prospects as well as parts of an organization's hierarchy (branches, head offices, corporate conglomerates) that may not necessarily have a billing relationship with the company. Any party that has an active account can be considered a customer. Historical information concerning the party is available in the Parties History table. |
|
|
Reference |
This entity keeps relationship between party and account. For example: 1. A party owns the account. It does not have to be the customer. Then this assignment tracks the owning party of the account. 2. A party is a warrantor of an account. 3. A party is responsible for payment of the account. |
|
|
Lookup |
Lookup for type of relationship between Party and Account. Depending on type of party, the relationship can be: Customer owns the account multiple customers may share the same account. |
|
|
Reference |
Associates one or more Addresses with a party. Captures history of the names and addresses associated with a party or customers. |
|
|
Reference |
Assignment of a Party to a Contract. For example, 1. A contract belongs to a party, for example, Customer Own the Contract. 2. The commission of Sales agent over signed contract will also be 1 relationship here. |
|
|
Reference |
Association of a Party with one or more other Parties. The relationships may include those among customers or between customer and the utility. |
|
|
Lookup |
Lookup for valid reasons parties may be associated with each other. For example: Cooptation (customer brings in a new customer) Financial Responsibility Hierarchical relationship in the organization contractual agreement. |
|
|
Lookup |
Describe the type of the party relationship. For example: 1. father & son 2. organizational hierarchy, subsidiary. 3. Customer referral. One customer might refer another party to join certain services to gain some bonus points. 4. Warrantor to Warrantee. |
|
|
Reference |
The Business Interaction Role which can be assigned by a Party. |
|
|
Reference |
Contact information for a party. For example, email, cell phone number. |
|
|
Lookup |
Keep the type of contact information. For example,
|
|
|
Lookup |
Relationship between party and Contact List. For example, a party belongs to a contact list. |
|
|
Lookup |
The role of the party in a Contact List. |
|
|
Base |
Assignment of cost items to a Party. One party may incur multiple costs. For example, for a customer acquisition the customer might be given discounts or rebates. Cost might be assigned to multiple parties. For example, for operational cost several organizations may share the same expense on a promotion or Campaign. |
|
|
Reference |
Defines individual and organization demography value for a given party demographic profile. |
|
|
Lookup |
Lookup for valid event types that may be assigned to a party profile for the various event types that may be actioned against a party. |
|
|
Reference |
Assigns a party to one or more geography entities. Depending on type of party, relationship might be: 1. Some customer belongs to some country, visited (roamed or not) other countries. 2. Organization's HQ is located at a city. 3. External operation has business at some country. |
|
|
Base |
Grouping of multiple related contact events regarding the common purpose with a party into a single thread. For example, If customer makes multiple calls to complain about same issue, those calls are grouped into single thread. The status history of a thread (service request) is in Business Interaction Status History. The party interaction thread status can also be tracked through each ''Party interaction Event''. For example:
|
|
|
Base |
The relationship between a Party Interaction Thread and the involved subscriptions. |
|
|
Lookup |
The type of Party Interaction Thread. For example:
|
|
|
Reference |
Keeps the language capability score for each Party. |
|
|
Lookup |
|
|
|
Lookup |
The type of relationship between the Party and the address. For example, office location, Primary Living location, Product Installation Address, and so on. |
|
|
Lookup |
This entity keep all roles which a Party plays in a Campaign. such as management or potential customer. |
|
|
Reference |
Assign a Party to its belonging market segment. |
|
|
Reference |
Party project participation describe the roles of each Party in the project. |
|
|
Base |
Response of a Party to a promotion. For example, positive responses: The customer accepted the offer. The customer modified their usage. The customer changed a specified behavior. For example moved from payment by check to an electronic payment option. |
|
|
Lookup |
Lookup for Roles a Party may be assigned in an Event. For example:
|
|
|
Reference |
Assigns party roles that the Party acted as to the Party. Party roles are X-X relationship and it may change due to contract change and so on. |
|
|
Reference |
Status history of the each Role that a Party has taken. Historical information tracked along the whole lifecycle of the Party in the system. |
|
|
Lookup |
Higher level of Party Status. For example:
|
|
|
Lookup |
Lookup for valid reasons that may be assigned for a Party Status change. For example: hire, transfer, new customer. |
|
|
Base |
Keep track of current party status history, regarding to what Operator may be interested. Historical information captured for all lifetime of the customer/dealer/... This information may be calculated from internal data, like payment, or obtained from external source, like credit rating agent. |
|
|
Lookup |
Status type of the Party. For example: 1. In category of Customer Status, Values may include Active, Inactive, Defaulted, New Customer, VIP customer, Black Listed, and so on. 2. In category of Prospect Status, Values may include New Prospect, Contacted No interests, Interested, Purchased, Rejected, and so on. |
|
|
Lookup |
Lookup for party type that classifies involved parties according to their inherent characteristics and structure. For example:
|
|
|
Lookup |
The classification of accounts according to payment delay history. For example: 0-10 days, 11-20 days, and so on. Postpaid customers are billed on a monthly basis for the usage of services in the month. At the end of the billing month for the customer an invoice is sent to the customer for which customer is supposed to pay by payment due date. |
|
|
Reference |
Channel which customer used to pay for the services. For example, For POS, payment channel could be POS001, POS002, and so on. For cash, payment channel could be STORE001, STORE002,which means paying by cash in the one store. |
|
|
Lookup |
Customers can pay their bills, deposits, other charges by different modes of payment. For example:
|
|
|
Lookup |
Lookup for type codes and description of Transaction Types associated with the Account Payment The payment maybe for Periodically Invoice, Installation Fee, Pre-deposit to the account Late Pay Penalty Payment. Regular Monthly Refund / Void. The payment type like Manual Cash In, direct debit are tracked in Payment Method Type. |
|
|
Reference |
Common type for per-length impedance electrical catalogs. |
|
|
Reference |
Impedance and admittance parameters per unit length for n-wire unbalanced lines, in matrix form. |
|
|
Reference |
Sequence impedance and admittance parameters per unit length, for transposed lines of 1, 2, or 3 phases. For 1-phase lines, define x=x0=xself. For 2-phase lines, define x=xs-xm and x0=xs+xm. |
|
|
Lookup |
Phase such as ABC phase, A phase and so on. |
|
|
Lookup |
Enumeration of phase identifiers. Allows designation of phases for both transmission and distribution equipment, circuits and loads. Residential and small commercial loads are often served from single-phase, or split-phase, secondary circuits. For 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. |
|
|
Reference |
Fault connection among Phases. |
|
|
Lookup |
The type of fault connection among Phases. |
|
|
Reference |
Triplet of resistance, reactance, and susceptance matrix element values. |
|
|
Lookup |
The configuration of Phase connections for a single terminal device such as a load or capacitor. |
|
|
Reference |
A transformer phase shifting tap model that controls the phase angle difference across the power transformer and potentially the active power flow through the power transformer. This phase tap model may also impact the voltage magnitude. |
|
|
Reference |
Describes the tap model for an asymmetrical phase shifting transformer in which the difference voltage vector adds to the primary side voltage. The angle between the primary side voltage and the difference voltage is named the winding connection angle. The phase shift depends on both the difference voltage magnitude and the winding connection angle. |
|
|
Reference |
Describes a tap changer with a linear relation between the tap step and the phase angle difference across the transformer. This is a mathematical model that is an approximation of a real Phase Tap Changer. |
|
|
Reference |
The non-linear Phase Tap Changer describes the non-linear behavior of a Phase Tap Changer. This is a base class for the symmetrical and asymmetrical Phase Tap Changer models. The details of these models can be found in the IEC 61970-301 document. |
|
|
Reference |
Describes a symmetrical phase shifting transformer tap model in which the secondary side voltage magnitude is the same as at the primary side. The difference voltage magnitude is the base in an equal-sided triangle where the sides corresponds to the primary and secondary voltages. The phase angle difference corresponds to the top angle and can be expressed as twice the arctangent of half the total difference voltage. |
|
|
Reference |
Describes a tabular curve for how the phase angle difference and impedance varies with the tap step. |
|
|
Reference |
Describes each tap step in the Phase Tap Changer Tabular curve. |
|
|
Reference |
Input pin that maps to a network voltage for RAS. |
|
|
Reference |
Planned outage involves network operations which will affect the supply of power to customers. The list of Power System Resources for the Planned Outage may be the same or a superset of the ones per Outage Step. |
|
|
Lookup |
Kind of planned outage. |
|
|
Reference |
Pole asset. |
|
|
Lookup |
Kind of base for poles. |
|
|
Lookup |
Preservative kind for poles. |
|
|
Lookup |
Kind of treatment for poles. |
|
|
Lookup |
Type of postal service type available to the carrier. For example: 1. First-class 2. Registered mail 3. Regular Mail 4. Postal Card. |
|
|
Reference |
Postal Code, Zip Code, or similar geographical designation. |
|
|
Reference |
Properties of potential transformer asset. |
|
|
Reference |
An area or zone of the power system which is used for load shedding purposes. |
|
|
Reference |
A power system resource can be an item of equipment such as a switch, an equipment container containing many individual items of equipment such as a substation, or an organizational entity such as sub-control area. Power system resources can have measurements associated. |
|
|
Reference |
Location of a Power System Resource. |
|
|
Reference |
An electrical device consisting of two or more coupled windings, with or without a magnetic core, for introducing mutual coupling between electric circuits. Transformers can be used to control voltage and phase shift (active power flow). A power transformer may be composed of separate transformer tanks that need not be identical. A power transformer can be modeled with or without tanks and is intended for use in both balanced and unbalanced representations. A power transformer typically has two terminals, but may have one (grounding), three or more terminals. The inherited association Conducting Equipment. Base Voltage should not be used. The association from Transformer End to Base Voltage should be used instead. |
|
|
Reference |
A Power Transformer End is associated with each Terminal of a Power Transformer. The impedance values r, r0, x, and x0 of a PowerTransformerEnd represents a star equivalent as follows 1) for a two Terminal PowerTransformer the high voltage Power Transformer End has non zero values on r, r0, x, and x0 while the low voltage PowerTransformerEnd has zero values for r, r0, x, and x0. 2) for a three Terminal PowerTransformer the three Power Transformer Ends represents a star equivalent with each leg in the star represented by r, r0, x, and x0 values. 3) for a Power Transformer with more than three Terminals the Power Transformer End impedance values cannot be used. Instead use the TransformerMeshImpedance or split the transformer into multiple Power Transformers. |
|
|
Reference |
Set of power transformer data, from an equipment library. |
|
|
Base |
Precipitation such as rain and snow. |
|
|
Base |
Type of event which may trigger a billing process. For example, event of customer using a product over its quota. |
|
|
Lookup |
Lookup for type codes and descriptions for utility services and products. |
|
|
Reference |
Grouping of pricing components and prices used in the creation of customer charges and the eligibility criteria under which these terms may be offered to a customer. The reasons for grouping include state, customer classification, site characteristics, classification (that is, fee price structure, deposit price structure, electric service price structure, and so on) and accounting requirements. |
|
|
Reference |
Pricing Structure Tariff Assignment |
|
|
Reference |
Priority definition. |
|
|
Reference |
Documented procedure for various types of Work or Work Tasks. One or more procedures guide a compatible unit, a standard way of performing a unit of work. The type of procedure is defined in Procedure.type. For example, when type=Inspection, this procedure coupled with Schedule and other information provides the key items of an inspection plan. Another type of Procedure is a Diagnosis. Each specific value and setting to be used in a procedure is intended to be described in an instance of UserAttribute. A maintenance ticket, a type of Work, is generated whenever maintenance is determined to be needed as a result of an inspection or diagnosis. |
|
|
Reference |
Asset assigned to a procedure. |
|
|
Lookup |
Kind of procedure. |
|
|
Reference |
Asset model by a specific manufacturer. |
|
|
Reference |
Function assigned to a product asset model. |
|
|
Reference |
Defines how a utility service or product is brought to market. |
|
|
Reference |
The record of customer using a product (or product package). Customer subscription is the basis of billing. One subscription may be based on contract. |
|
|
Reference |
The business activities (Tasks) may be categorized into a specific Project according to their common purpose. [20110407] Current design focus more on financial side. |
|
|
Reference |
The business activity which may happen to the utility. It is the super type of project and tasks. |
|
|
Reference |
The promotion reflects the tactics an operator undertakes to generate increased incremental sales or usage volume for specific product within a promotional event. Promotions are frequently communicated as part of a marketing campaign to ensure that awareness is generated with the target audience. |
|
|
Base |
Assigns a particular customer segment (cluster) to a given promotion or list of promotions. The customer segments are generated by certain analytical application (including Oracle Mining) and this assignment tracks the usage of customer segment in the promotion. |
|
|
Base |
This entity keeps relationship between a Contact List and a Campaign. Contact list can be used to do a campaign to some customers, who have the same characters. |
|
|
Base |
A history of campaign party role about management of a campaign episode. |
|
|
Reference |
Details regarding each campaign message broadcast through a media object. For example, if channel is a newspaper, then media object will be the page and the picture. For a TV advertisement, how frequently it broadcast, how long time in each broadcast. |
|
|
Reference |
Associates product market plans to a promotion, typically, when a given market plan will be offered by the promotion only during a certain period. |
|
|
Reference |
Defines the relationship between two promotions. |
|
|
Lookup |
Lookup for the prospect reaction to a specific promotion during a sales campaign. For example:
|
|
|
Reference |
The allocation of promotion resource/actions onto each sales channel. The efficiency of promotion can be evaluated by comparing the promoted sales volume with the promotion cost. |
|
|
Lookup |
Lookup for codes and descriptions of Promotion Term. For example:
|
|
|
Lookup |
Assigns promotion term type to a promotion with a value corresponding to the Term Type. For example:
|
|
|
Lookup |
Lookup for the type of promotion. Direct marketing by Phonecall, Direct marketing by mail, Media Broadcast by TV, Direct marketing by Phonecall. |
|
|
Reference |
The proposals made available to prospects in the promotion. It could be a upsell offer like selling a new product, or a retention program. |
|
|
Reference |
The relationship between two proposals. |
|
|
Reference |
An individual, collection of individuals, company, or public institution who has not purchased services, but who may in the future. A prospect may also be a customer of one product (already purchased) that does not currently purchase another product (may purchase). |
|
|
Lookup |
The different priorities which can be assigned to the prospect and prospect interests. |
|
|
Lookup |
Lookup for type of quality scores which can be applied to prospects. For example:
|
|
|
Reference |
The quality score value assigned to each prospect under different type of criteria. |
|
|
Lookup |
The reason to explain why an offer or proposal is rejected by the prospect. |
|
|
Reference |
A Protected Switch is a switching device that can be operated by Protection Equipment. |
|
|
Reference |
An electrical device designed to respond to input conditions in a prescribed manner and after specified conditions are met to cause contact operation or similar abrupt change in associated electric control circuits, or simply to display the detected condition. Protection equipment are associated with conducting equipment and usually operate circuit breakers. |
|
|
Reference |
Properties of protection equipment asset. |
|
|
Lookup |
Classifying instances of the same class. For example, overhead and underground AC Line Segments. This classification mechanism is intended to provide flexibility outside the scope of this standard, that is, provide customization that is non standard. |
|
|
Reference |
Publication to which the media object used in campaign belongs. It includes the journals, TV media, newspapers, and so on. |
|
|
Lookup |
Lookup for code and description describing the type of publication. |
|
|
Base |
All the purchase orders that are raised on suppliers by the purchasing unit of a business organization (purchasing organization). The types of purchase orders can be many and would typically include one-time, regular, blanket, release and so on. It inherit PK from Business Interaction. |
|
|
Base |
Holds Purchase order line Item information. |
Table 2-3 Utilities Data Model Entities Q-Z
| Entity Name | Type | Description |
|---|---|---|
|
|
Reference |
Quality flags in this class are as defined in IEC 61850, except for estimatorReplaced, which has been included in this class for convenience. |
|
|
Reference |
A charge element associated with other entities such as tariff structures, auxiliary agreements or other charge elements. The total charge amount applicable to this instance of charge is the sum of fixed and variable portion. |
|
|
Reference |
A tap changer that changes the voltage ratio impacting the voltage magnitude but not the phase angle across the transformer. |
|
|
Reference |
Describes a curve for how the voltage magnitude and impedance varies with the tap step. |
|
|
Reference |
Describes each tap step in the ratio tap changer tabular curve. |
|
|
Reference |
Rational number with a numerator and a denominator. |
|
|
Lookup |
Meter reading accumulation behavior such as accumulative and delta. |
|
|
Reference |
Reading Channel. |
|
|
Reference |
ID of a reading channel. |
|
|
Lookup |
A reading is viewed in the aggregate such as average, maximum, minimum and so on. |
|
|
Base |
Quality of a specific reading value or interval reading value. More than one quality may be applicable to a given reading. Typically not used unless problems or unusual conditions occur (that is, 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. |
|
|
Lookup |
Detailed description for a quality of a reading value, produced by an end device or a system. Values in attributes allow for creation of recommended codes to be used for identifying reading value quality codes as follows: <systemId>.<category>.<subCategory>. |
|
|
Lookup |
Reading quality type category. |
|
|
Lookup |
Provides an identification of the system which has declared the issue with the data. |
|
|
Lookup |
Reading quality type sub category. |
|
|
Lookup |
Reason for the reading being taken. |
|
|
Lookup |
Reading time attribute such as hourly read and 15 minute read. |
|
|
Lookup |
Reading time period such as daily and monthly. |
|
|
Reference |
Detailed description for a type of a reading value. |
|
|
Reference |
Pole-mounted fault interrupter with built-in phase and ground relays, current transformer (CT), and supplemental controls. |
|
|
Reference |
Meter register. |
|
|
Reference |
The schedule has time points where the time between them is constant. |
|
|
Reference |
Time point for a schedule where the time between the consecutive points is constant. |
|
|
Reference |
A type of conducting equipment that can regulate a quantity (that is, voltage or flow) at a specific point in the network. |
|
|
Reference |
Specifies a set of equipment that works together to control a power system quantity such as voltage or flow. |
|
|
Lookup |
The kind of regulation model. For example
|
|
|
Reference |
A pre-established pattern over time for a controlled variable. For example, busbar voltage. |
|
|
Derived |
Derived fact table on utility reliability indices by city by month. |
|
|
Derived |
Derived fact table on utility reliability indices by feeder by month. |
|
|
Reference |
Details of remote connect and disconnect function. |
|
|
Reference |
Remote controls are outputs that are sent by the remote unit to actuators in the process. |
|
|
Reference |
For a RTU remote points correspond to telemetered values or control outputs. Other units (for example, control centers) usually also contain calculated values. |
|
|
Reference |
Remote sources are state variables that are telemetered or calculated within the remote unit. |
|
|
Reference |
A remote unit can be a RTU, IED, substation control system, control center and so on. The communication with the remote unit can be through various standard protocols (for example, IEC 61870, IEC 61850) or non standard protocols (for example, DNP, RP570 and so on.). A remote unit contain remote data points that might be telemetered, collected or calculated. The RemoteUnit class inherit Power System Resource. The intention is to allow RemotUnits to have Measurements. These Measurements can be used to model unit status as operational, out of service, unit failure and so on. |
|
|
Reference |
Remote unit communication link assignment. |
|
|
Lookup |
Type of remote unit. |
|
|
Base |
The service order can be translated into resource order to determine how it can be fulfilled. A type of Request that represents a Service Order's services decomposed into the elements on which the services will be provisioned. |
|
|
Base |
The purpose for the Resource Order expressed in terms of an equipment order. |
|
|
Lookup |
Accounting classification of the type of revenue collected for the customer agreement, typically used to break down accounts for revenue accounting. |
|
|
Reference |
A rotating machine which may be used as a generator or motor. |
|
|
Reference |
Document restricting or authorizing works on electrical equipment (for example a permit to work, sanction for test, limitation of access, or certificate of isolation), defined based upon organizational practices. |
|
|
Reference |
Channel through which the utility uses to communicate with other parties for sales purposes. The external sales channel should roll up to an internal legal subsidiary organization business unit. |
|
|
Reference |
Abstracted entity to provide SCD2 capability for all its children. |
|
|
Base |
Signifies an event to trigger one or more activities, such as reading a meter, recalculating a bill, requesting work, when generating units must be scheduled for maintenance, when a transformer is scheduled to be refurbished, and so on. |
|
|
Reference |
Asset assigned to a scheduled event. |
|
|
Reference |
A list of specific groupings of questions or statements that will be presented to individuals during a Survey. |
|
|
Reference |
Initiative Questions documents the questions that will be asked of the customer as part of the initiative. |
|
|
Base |
Sea Condition |
|
|
Reference |
Physically controls access to AssetContainers. |
|
|
Lookup |
Kind of seal condition. |
|
|
Lookup |
Kind of seal. |
|
|
Lookup |
This dimension table holds seasons and their attributes. Seasons are arbitrary periods of time around which some retailers organize their buying and selling patterns. Each day should fall within no more than one season. |
|
|
Reference |
A time schedule covering a 24 hour period, with curve data for a specific type of season and day. |
|
|
Reference |
Automatic switch that will lock open to isolate a faulted section. It may, or may not, have load breaking capability. Its primary purpose is to provide fault sectionalising at locations where the fault current is either too high, or too low, for proper coordination of fuses. |
|
|
Reference |
Minimum and Maximum scores for each segment associated with an account segment or customer segment. |
|
|
Lookup |
Lookup for type codes and descriptions used to define account segmentation model or customer segmentation model. |
|
|
Reference |
A Series Compensator is a series capacitor or reactor or an AC transmission line without charging susceptance. It is a two terminal device. |
|
|
Reference |
Service is an internal technical presentation of available services or products to the customer. |
|
|
Lookup |
Category of Service, sample values: Customer facing service, Resource facing service, Composite service. |
|
|
Reference |
Service coverage area defines the coverage area of a given Service Spec. The geographic area covered by service provider with certain product combination. Service areas are defined so that service providers can determine the demographic / psychographic / population data the geography served by the network. |
|
|
Reference |
The detail about service territory a utility covers. |
|
|
Reference |
A real estate location, commonly referred to as premise. |
|
|
Reference |
ID assigned to a service location. |
|
|
Base |
A type of Request that represents a Customer Order's products decomposed into the services through which the products are realized. |
|
|
Base |
The purpose for the Service Order expressed in terms of a Service Specification or a Service. |
|
|
Reference |
Set of values obtained from the meter. |
|
|
Reference |
Organization that provides services to customers. |
|
|
Lookup |
Type of Service. Sample value should be from subtype of customer facing service, resource facing service and composite service. |
|
|
Base |
A Set Point is an analog control used for supervisory control. |
|
|
Lookup |
Type of rotor, used by short circuit applications. |
|
|
Reference |
A shunt capacitor or reactor or switchable bank of shunt capacitors or reactors. A section of a shunt compensator is an individual capacitor or reactor. A negative value for reactivePerSection indicates that the compensator is a reactor. ShuntCompensator is a single terminal device. Ground is implied. |
|
|
Reference |
Properties of shunt capacitor, shunt reactor or switchable bank of shunt capacitor or reactor assets. |
|
|
Reference |
Single phase of a multi-phase shunt compensator when its attributes might be different per phase. |
|
|
Reference |
Assigns one industry to another one in Standard Industrial Classification (SIC). How 2 industries are related. For example, the Petroleum Industry and Automobile, the Mining and the Steal. This might be too difficult for Communication Service Provider to capture. <to be further considered>. |
|
|
Lookup |
Lookup for reason code and description as to why two industries were assigned together in Standard Industrial Classification (SIC). |
|
|
Lookup |
Standard Industrial Classification (SIC). |
|
|
Reference |
Simple end device function distinguished by 'kind'. Use this class for instances that cannot be represented by another end device function specializations. |
|
|
Lookup |
Enumeration of single phase identifiers. Allows designation of single phases for both transmission and distribution equipment, circuits and loads. |
|
|
Reference |
The most detailed level of job code from Standard Occupational Classification (SOC) System. For example: 15-1041 Computer Support Specialists 15-1011 Computer and Information Scientists, Research 15-1021 Computer Programmers. |
|
|
Reference |
The 2nd level of job code from Standard Occupational Classification (SOC) System. |
|
|
Reference |
The top level of job code from Standard Occupational Classification (SOC) System. |
|
|
Lookup |
Source gives information related to the origin of a value. |
|
|
Reference |
System of Record from which Oracle Utilities Data Model data was loaded. For example, AMI system, CRM system, and so on. |
|
|
Reference |
Track Key of the Party (customer or employee) in the originating source system. This key can be used back to track information back to source management system. The party can consolidate different people from different source systems, like CRM, Billing, into a unique one. Therefore, the multiple keys for the same unique party is saved here. |
|
|
Lookup |
Lookup for type code and description used to describe source system. For example: Competitor Customer Listing Third-Party Purchased Mailing List Government Roll Tax List. |
|
|
Base |
Spot Temperature |
|
|
Reference |
A facility for providing variable and controllable shunt reactive power. The SVC typically consists of a stepdown transformer, filter, thyristor-controlled reactor, and thyristor-switched capacitor arms. The SVC may operate in fixed MVar output mode or in voltage control mode. When in voltage control mode, the output of the SVC will be proportional to the deviation of voltage at the controlled bus from the voltage setpoint. The SVC characteristic slope defines the proportion. If the voltage at the controlled bus is equal to the voltage setpoint, the SVC MVar output is zero. |
|
|
Reference |
Station supply with load derived from the station output. |
|
|
Reference |
Current status information relevant to an entity. |
|
|
Reference |
The cogeneration plant's steam sendout schedule in volume per time unit. |
|
|
Reference |
Streetlight asset. |
|
|
Lookup |
Kind of lamp for the streetlight. |
|
|
Base |
String Measurement represents a measurement with values of type string. |
|
|
Base |
String Measurement Value represents a measurement value of type string. |
|
|
Reference |
Construction holding assets such as Conductors, transformers, switchgear, and so on. Where applicable, number of Conductors can be derived from the number of associated wire spacing instances. |
|
|
Lookup |
Kind of material used for structures. |
|
|
Reference |
Support for structure assets. |
|
|
Lookup |
Kind of structure support. |
|
|
Reference |
A subset of a geographical region of a power system network model. |
|
|
Reference |
The class is the second level in a hierarchical structure for grouping of loads for load flow load scaling. |
|
|
Reference |
A collection of equipment for purposes other than generation or utilization, through which electric energy in bulk is passed for switching or modifying its characteristics. |
|
|
Reference |
Properties of surge arrester. |
|
|
Reference |
A survey is a subtype to the Promotion. An initiation of a survey on a Party is implemented as an Event Party Interaction. The response from a survey is in Interaction Question Response. |
|
|
Lookup |
Static VAr Compensator control mode. |
|
|
Reference |
A generic device designed to close, or open, or both, one or more electric circuits. |
|
|
Reference |
Action on switch as a switching step. |
|
|
Lookup |
Kind of action on switch. |
|
|
Reference |
Connect disconnect func a switch has, including history. |
|
|
Reference |
Switch data. |
|
|
Reference |
Single phase of a multi-phase switch when its attributes might be different per phase. |
|
|
Reference |
A schedule of switch positions. |
|
|
Lookup |
Possible states for a switch. |
|
|
Reference |
Switching operation assigned to a switching. |
|
|
Reference |
Activity within the switching plan. |
|
|
Reference |
Safety document assigned to a switching activity. |
|
|
Reference |
A Switching Operation is used to define individual switch operations for an Outage Schedule. This OutageSchedule may be associated with another item of Substation such as a Transformer, Line, or Generator; or with the Switch itself as a Power System Resourcee. A Switch may be referenced by many Outage Schedules. |
|
|
Reference |
Switching Plan |
|
|
Reference |
Atomic switching step; can be part of a switching step group, or of the switching plan. |
|
|
Reference |
A logical step, grouping atomic switching steps that are important to distinguish when they may change topology (for example, placing a jumper between two cuts). |
|
|
Reference |
A device that operates when two AC circuits are within the desired limits of frequency, phase angle, and voltage, to permit or to cause the paralleling of these two circuits. Used to prevent the paralleling of non-synchronous topological islands. |
|
|
Reference |
An electromechanical device that operates with shaft rotating synchronously with the network. It is a single machine operating either as a generator or synchronous condenser or pump. |
|
|
Lookup |
Synchronous machine type. |
|
|
Lookup |
Synchronous machine operating mode. |
|
|
Reference |
Action on operation tag as a switching step. |
|
|
Lookup |
Kind of action on tag. |
|
|
Reference |
Mechanism for changing transformer winding tap positions. |
|
|
Reference |
Describes behavior specific to tap changers. For example, how the voltage at the end of a line varies with the load level and compensation of the voltage drop by tap adjustment. |
|
|
Reference |
Tap changer data. |
|
|
Reference |
A pre-established pattern over time for a tap step. |
|
|
Reference |
The customer accounts included in a specific campaign cell. |
|
|
Reference |
The Contracts included in a specific promotion. |
|
|
Reference |
The geography information included in a specific campaign cell. |
|
|
Reference |
The market segments included in a specific campaign. |
|
|
Lookup |
Indicates the type of targets in a specific Promotion: For example:
|
|
|
Reference |
Document, approved by the responsible regulatory agency, listing the terms and conditions, including a schedule of prices, under which utility services will be provided. It has a unique number within the state or province. For rate schedules it is frequently allocated by the affiliated Public utilities commission (PUC). |
|
|
Reference |
A schedule of charges; structure associated with Tariff that allows the definition of complex tariff structures such as step and time of use when used in conjunction with Time Tariff Interval and Charge. Inherited 'status. value' is defined for the utility's business rules. For example: active, inactive, and so on. |
|
|
Reference |
A profile assigned to a tariff, including history. |
|
|
Reference |
The specific tasks inside a project. |
|
|
Lookup |
A government authority that levies sales taxes and on whose behalf the store collects these sales taxes. For example National, State, Province, City, County, Other. |
|
|
Lookup |
The tax categories which may be applied to invoices items. |
|
|
Reference |
An AC electrical connection point to a piece of conducting equipment. Terminals are connected at physical connection points called connectivity nodes. |
|
|
Reference |
A generating unit whose prime mover could be a steam turbine, combustion turbine, or diesel engine. |
|
|
Lookup |
Time Of Use. |
|
|
Reference |
Description of anything that changes through time. Time schedule is used to perform a single-valued function of time. Use inherited 'type' attribute to give additional information on this schedule, such as: periodic (hourly, daily, weekly, monthly, and so on.), day of the month, by date, calendar (specific times and dates). |
|
|
Reference |
Time period. |
|
|
Reference |
One of a sequence of time intervals defined in terms of real time. It is typically used in association with Tariff Profile to define the intervals in a time of use tariff structure, where startDateTime simultaneously determines the starting point of this interval and the ending point of the previous interval. |
|
|
Reference |
Tool asset. |
|
|
Reference |
For a detailed substation model a topological node is a set of connectivity nodes that, in the current network state, are connected together through any type of closed switches, including jumpers. Topological nodes change as the current network state changes (that is, switches, breakers, and so on. change state). For a planning model, switch statuses are not used to form topological nodes. Instead they are manually created or deleted in a model builder tool. Topological nodes maintained this way are also called "busses". |
|
|
Reference |
Tower asset. Dimensions of the Tower are specified in associated DimensionsInfo class. When used for planning purposes, a transmission tower carrying two 3-phase circuits will have 2 instances of Connection, each of which will have 3 MountingPoint instances, one for each phase all with coordinates relative to a common origin on the tower. (It may also have a 3rd Connection with a single MountingPoint for the Neutral line). |
|
|
Lookup |
Kind of tower construction. |
|
|
Lookup |
Control modes for a transformer. |
|
|
Reference |
The transformer core admittance. Used to specify the core admittance of a transformer in a manner that can be shared among power transformers. |
|
|
Reference |
A conducting connection point of a power transformer. It corresponds to a physical transformer winding terminal. In earlier CIM versions, the Transformer Winding class served a similar purpose, but this class is more flexible because it associates to terminal but is not a specialization of Conducting Equipment. |
|
|
Reference |
Transformer End Info |
|
|
Reference |
A feeder that a transformer connects including history. |
|
|
Reference |
Transformer mesh impedance (Delta-model) between transformer ends. The typical case is that this class describes the impedance between two transformer ends pair-wise, that is, the cardinalities at both transformer end associations are 1. But in cases where two or more transformer ends are modeled the cardinalities are larger than 1. |
|
|
Reference |
Transformer star impedance (Pi-model) that accurately reflects impedance for transformers with 2 or 3 windings. For transformers with four or more windings, you must use Transformer Mesh Impedance. For transmission networks use Power Transformer End impedances (r, r0, x, x0, b, b0, g and g0). |
|
|
Reference |
An assembly of two or more coupled windings that transform electrical power between voltage levels. These windings are bound on a common core and place in the same tank. Transformer tank can be used to model both single-phase and 3-phase transformers. |
|
|
Reference |
Transformer tank end represents an individual winding for unbalanced models or for transformer tanks connected into a bank (and bank is modeled with the Power Transformer). |
|
|
Reference |
Set of transformer tank data, from an equipment library. |
|
|
Lookup |
Kind of trouble reporting. |
|
|
Reference |
Trouble Ticket |
|
|
Reference |
Underground Structure |
|
|
Lookup |
Kind of underground structure. |
|
|
Lookup |
Multiplier of a unit, such as kilo. |
|
|
Lookup |
The unit multipliers defined for the CIM. |
|
|
Lookup |
This table stores and describes all possible measurement units valid for the data within the system. For example: valid units of measure are inch, kilowatt-hour, days, cubic centimeters. |
|
|
Lookup |
The units defined for usage in the CIM. |
|
|
Reference |
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. |
|
|
Lookup |
State of the usage point with respect to connection to the network. |
|
|
Reference |
End device ctrl assigned to usage point. |
|
|
Reference |
Equipment linked to a usage point. |
|
|
Reference |
Abstraction for management of group communications within a two-way AMR system or the data for a group of related usage points. Commands can be issued to all of the usage points that belong to a usage point group using a defined group address and the underlying AMR communication infrastructure. |
|
|
Reference |
Group a usage point assigned. |
|
|
Reference |
DR program a usage point group assigned. |
|
|
Reference |
End device ctrl capability a usage point group has or assigned, including history. |
|
|
Reference |
Location of an individual usage point. |
|
|
Reference |
Transformer a usage point connected, including history. |
|
|
Reference |
Meter read cycle. |
|
|
Lookup |
Utility Commodity |
|
|
Lookup |
Validity for Measurement Value. |
|
|
Reference |
Describes the translation of a set of values into a name and is intended to facilitate custom translations. Each Value Alias Set has a name, description and so on. A specific Measurement may represent a discrete state like Open, Closed, Intermediate and so on. This requires a translation from the Measurement Value. value number to a string. For example,
Each Value To Alias member in Value Alias Set. Value describe a mapping for one particular value to a name. |
|
|
Reference |
Describes the translation of one particular value into a name. For example, 1 as "Open". |
|
|
Lookup |
Value type describes the type of value. Value type could be time or money. |
|
|
Base |
Validation, estimation, and editing (VEE) exception. |
|
|
Lookup |
Validation, estimation, and editing (VEE) exception types. |
|
|
Lookup |
Validation, estimation, and editing (VEE) groups. |
|
|
Lookup |
Validation, estimation, and editing (VEE) rules. |
|
|
Reference |
The vehicles owned and used by the operators to fulfill its business requirement. |
|
|
Reference |
Any vendor utilized by the enterprise. |
|
|
Reference |
Vendor Item |
|
|
Reference |
The virtual team beside department hierarchy formed for specific purpose. For example: 1. Sales Team A, B, C 2. Customer Support Team A, B, C 3. Project team. 4. Strategic Account management team including sales and support. |
|
|
Reference |
An area of the power system network which is defined for secondary voltage control purposes. A voltage control zone consists of a collection of substations with a designated bus bar section whose voltage will be controlled. |
|
|
Reference |
Operational limit applied to voltage. |
|
|
Lookup |
Weather Alert |
|
|
Lookup |
Weather Forecast |
|
|
Lookup |
Weather Information |
|
|
Lookup |
Location where weather information collected. |
|
|
Reference |
A web page on service operator website. It may present a product, or take customer service request. |
|
|
Lookup |
Type of fuel. |
|
|
Reference |
A wind driven generating unit. |
|
|
Base |
Information on a work. |
|
|
Lookup |
Winding connection type. |
|
|
Reference |
Wire data that can be specified per line segment phase, or for the line segment as a whole in case its phases all have the same wire characteristics. |
|
|
Lookup |
Kind of wire insulation. |
|
|
Lookup |
Kind of wire material. |
|
|
Reference |
Wire spacing data that associates multiple wire positions with the line segment, and allows to calculate line segment impedances. Number of phases can be derived from the number of associated wire positions whose phase is not neutral. |
|
|
Lookup |
Kind of wire usage. |
|
|
Reference |
Asset used to perform work. |
|
|
Reference |
Billing information for work performed for the customer. The history of Work Billing Info, Invoices, and Payments is to be maintained in associated Activity Records. |
|
|
Reference |
A collection of all of the individual cost items collected from multiple sources. |
|
|
Base |
A roll up by cost type for the entire cost of a work order. For example, total labor. |
|
|
Reference |
Shadow class for Document, to isolate subclassing from this package. If any subclass gets normative and needs inheritance, it will inherit directly from Document. |
|
|
Reference |
A pre-defined set of work steps for a given type of work. |
|
|
Reference |
Shadow class for Identified Object, to isolate subclassing from this package. If any subclass gets normative and needs inheritance, it will inherit directly from Identified Object. |
|
|
Lookup |
Kind of work. |
|
|
Reference |
Information about a particular location for various forms of work. |
|
|
Reference |
Document used to request, initiate, track and record work. |
|
|
Reference |
A type of Activity Record that records information about the status of an item, such as a Work or Work Task, at a point in time. |
|
|
Lookup |
Kind of status, specific to work. |
|
|
Reference |
Work Task. |
|
|
Reference |
Asset assigned to a work task including the history. |
|
|
Lookup |
Work task kind. |
|
|
Reference |
Time schedule of a work. |
|
|
Lookup |
Kind of work schedule. |
|
|
Reference |
Area divided off from other areas. It may be part of the electrical network, a land area where special restrictions apply, weather areas, and so on. For weather, it is an area where a set of relatively homogenous weather measurements apply. |
|
|
Lookup |
Kind of zone. |