1

These are options that can be set to impact system processing. Typically these have wide ranging impact across several modules (e.g., multi-time zone support)

1

Your organization's country.

1

Your organization's native currency.

1

Controls how dates, times, and numbers displayed.

1

The language to use for this implementation.

1

Your organization's base time zone.

1

The work calendar for your organization, which identifies your public holidays.

2

Control various global aspects of the system.

2

Used to associate users with To Do entries.

2

Used to define types of To Do Entries.

3

Defines a user's user groups, data access roles, portal preferences, default values, and To Do roles.

3

A group of users who have the same degree of security access.

3

Defines specific types of service for which usage can be recorded and captured (electric, gas, steam, etc.).

4

Delineates between different operating companies within a large conglomerate of utilities.

4

Quantities measured and recorded by the system (CCF, KWH, KW, etc.).

4

Used to further distinguish between measured quantities that have identical UOM/TOU combinations.

4

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.).

4

Centrally stored sets of values for use in validation rules, bill determinants calculations, and other processes.

4

Defines jurisdictions or regulatory environments in which a Service Point participates.

4

Defines the schedule for manual meter reading of devices at Service Points in that cycle

4

Define the dates on which devices are scheduled to be read for a given measurement cycle.

4

Defines messages sent to external systems.

4

Defines types of schedules that can be referenced by different processes and objects.

5

Defines External Systems with which Oracle Utilities Meter Data Management should be able to communicate.

6

External entities that serve various roles relative to the application (head-end systems, billing systems, market participants, outage management systems, etc.).

6

Defines properties of a class of entities (businesses, persons).

7

Defines properties common to a specific type of activity.

7

Define properties common to a specific type of communication.

7

Defines specific types of tasks performed by external users (self-service meter reads, self-service outage notifications, etc.)

7

Defines information common to dynamic options of a specific type.

7

Individual companies that makes devices. Manufacturers also reference models.

7

Defines properties common to VEE Exceptions of a specific type.

8

Collections of VEE Rules that are applied to initial measurement data.

9

Standard and custom VEE Rules that perform checking and/or manipulation of initial measurement data.

10

Dictates whether a VEE Rule can execute based on a set of defined criteria.

11

Defines the most important properties of a measuring component.

11

Defines details by which measuring component data can be compared to determine the days that most closely resemble a specific day being evaluated.

12

Defines properties of Device Configurations of a given type.

13

Defines information about a class of devices.

14

Defines specific types of points at which service is delivered.

14

Defines types of quantities that can be stored for a service point.

14

Defines types of quantities that can be stored for a usage subscription.

15

Used to limit the set of Time Of Uses that are usable in a TOU schedule.

16

Schedules used for TOU map data generation.

17

Define important properties of TOU maps of a given type.

18

Defines properties common to Usage Transaction Exceptions of a specific type.

18

Collections of usage calculation rules that are applied to measurement data to calculate bill determinants for Usage Subscriptions.

19

Defines rules that perform calculations on measurement data to generate bill determinants and other values used by external systems.

20

Dictates whether a usage calculation rule can execute based on a set of defined criteria.

21

Defines collections of properties common to a set of Usage Subscriptions.

22

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

22

Define the most important properties of a measuring component used with dynamic aggregation.

22

Define the dimensions and criteria by which dynamic aggregation will be performed.

22

Define the ordering of a series of related aggregations based on a set of configured measuring component Sets.

23

Defines collections of properties defining a class of settlement subscriptions.

23

Defines the “lowest common denominator set” of dynamic aggregation dimensions.

23

Defines collections of settlement calculation rules that are used to perform settlement calculations, including calculating service point quantities, totaling consumption and usage for settlement units, application of losses, and allocation of unaccounted for energy (UFE).

23

Defines rules that perform settlement calculations, including calculating service point quantities, totaling consumption and usage for settlement units, application of losses, and allocation of unaccounted for energy (UFE).

23

Defines specific types of end-customer settlement accounts.

23

Defines specific types of market contracts used in settlement processing.

23

Defines the highest level grouping for a set of market products that will be processed together.

23

Define types of products used in settlement processing.

23

Define types of attribute data snapshots used in settlement processing.

23

Define types of measurement data snapshots used in settlement processing.

24

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.

24

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.

24

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.

24

Defines the extract parameters, the bucket configurations and configuration snapshots used for extracting data for Oracle Utilities Analytics