Meter Data Management Table Setup Sequence
This section provides the suggested order for the setup of Meter Data Management administrative data.
Sequence |
Entity |
Description |
1 |
Quantities measured and recorded by the system (CCF, KWH, KW, etc.). |
|
1 |
Used to further distinguish between measured quantities that have identical UOM/TOU combinations. |
|
1 |
Modifiers for a given unit of measure that indicate a period of time during which a quantity has been used (On- Peak, Off-Peak, etc.). |
|
1 |
Centrally stored sets of values for use in validation rules, bill determinants calculations, and other processes. |
|
1 |
Defines jurisdictions or regulatory environments in which a Service Point participates. |
|
1 |
Defines the schedule for manual meter reading of devices at Service Points in that cycle |
|
1 |
Define the dates on which devices are scheduled to be read for a given measurement cycle. |
|
1 |
Defines messages sent to external systems. |
|
1 |
Defines types of schedules that can be referenced by different processes and objects. |
|
2 |
Defines External Systems with which Oracle Utilities Meter Data Management should be able to communicate. |
|
3 |
External entities that serve various roles relative to the application (head-end systems, billing systems, market participants, outage management systems, etc.). |
|
3 |
Defines properties of a class of entities (businesses, persons). |
|
4 |
Defines properties common to a specific type of activity. |
|
4 |
Define properties common to a specific type of communication. |
|
4 |
Defines specific types of tasks performed by external users (self-service meter reads, self-service outage notifications, etc.) |
|
4 |
Defines information common to dynamic options of a specific type. |
|
4 |
Individual companies that makes devices. Manufacturers also reference models. |
|
4 |
Defines properties common to VEE Exceptions of a specific type. |
|
5 |
Collections of VEE Rules that are applied to initial measurement data. |
|
6 |
Standard and custom VEE Rules that perform checking and/or manipulation of initial measurement data. |
|
7 |
Dictates whether a VEE Rule can execute based on a set of defined criteria. |
|
8 |
Defines the most important properties of a measuring component. |
|
8 |
Defines details by which measuring component data can be compared to determine the days that most closely resemble a specific day being evaluated. |
|
9 |
Defines properties of Device Configurations of a given type. |
|
10 |
Defines information about a class of devices. When setting up Device Types, device type codes should match corresponding asset type codes in Operational Device Management (see Operational Device Management Table Setup Sequence). |
|
11 |
Defines specific types of points at which service is delivered. |
|
11 |
Defines types of quantities that can be stored for a service point. |
|
12 |
Used to limit the set of Time Of Uses that are usable in a TOU schedule. |
|
13 |
Schedules used for TOU map data generation. |
|
14 |
Define important properties of TOU maps of a given type. |
|
15 |
Defines properties common to Usage Transaction Exceptions of a specific type. |
|
15 |
Collections of usage calculation rules that are applied to measurement data to calculate bill determinants for usage subscriptions. |
|
16 |
Defines rules that perform calculations on measurement data to generate bill determinants and other values used by external systems. |
|
17 |
Dictates whether a usage calculation rule can execute based on a set of defined criteria. |
|
18 |
Defines collections of properties common to a set of Usage Subscriptions. |
|
19 |
Defines the source of data for dynamic aggregation, such as measurement data from usage subscriptions linked to a service point, badged or unbadged items, or measuring component sets |
|
19 |
Define the most important properties of a measuring component used with dynamic aggregation. |
|
19 |
Measuring Component Set |
Define the dimensions and criteria by which dynamic aggregation will be performed. |
19 |
Define the ordering of a series of related aggregations based on a set of configured measuring component Sets. |
|
20 |
Control various behaviors for external applications, head end systems, and market participants within the system such as which message is sent, how an external value is translated, among others. |
|
20 |
Configuration that applies to series of modules that acts as a central point of configuration rather than embedding repetitive configuration throughout a set of algorithms. |
|
20 |
Information Lifecycle Management (ILM) is designed to address data management issues, with a combination of processes and policies so that the appropriate solution can be applied to each phase of the data's lifecycle. |
|
20 |
Defines the extract parameters, the bucket configurations and configuration snapshots used for extracting data for Oracle Utilities Analytics |