Digital Asset Table Setup Sequence
The table below provides the suggested order for the setup of administrative data used with Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Digital Asset Management.
Entity |
Description |
|
---|---|---|
1 |
Feature Configuration |
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 |
Country |
Your organization's country. |
1 |
Currency |
Your organization's native currency. |
1 |
Display Profile |
Controls how dates, times, and numbers displayed. |
1 |
Language |
The language to use for this implementation. |
1 |
Time Zone |
Your organization's base time zone. |
1 |
Work Calendar |
The work calendar for your organization, which identifies your public holidays. |
2 |
Installation Options |
Control various global aspects of the system. |
2 |
To Do Role |
Used to associate users with To Do entries. |
2 |
To Do Type |
Used to define types of To Do Entries. |
3 |
User |
Defines a user's user groups, data access roles, portal preferences, default values, and To Do roles. |
3 |
User Group |
A group of users who have the same degree of security access. |
3 |
Service Type |
Defines specific types of service for which usage can be recorded and captured (electric, gas, steam, etc.). |
4 |
Division |
Delineates between different operating companies within a large conglomerate of utilities. |
4 |
Outbound Message |
Defines messages sent to external systems. |
5 |
External System |
Defines External Systems with which Oracle Utilities Meter Data Management should be able to communicate. |
6 |
Head End Systems |
External entities that serve various roles relative to the application (head-end systems, outage management systems, etc.). |
6 |
External Applications |
External entities that serve various roles relative to the application (head-end systems, outage management systems, etc.). |
6 |
Program Subscription Contact Type |
Defines properties of a class of entities (businesses, persons). |
7 |
Activity Type |
Defines properties common to a specific type of activity. |
7 |
Communication Type |
Define properties common to a specific type of communication. |
7 |
Service Task Type |
Defines specific types of enrollment and unenrollment processes |
7 |
Program Type |
Defines information common to dynamic options of a specific type. |
7 |
Manufacturer |
Individual companies that makes devices. Manufacturers also reference models. |
8 |
Controllable Asset Type |
Defines information about a class of controllable assets. |
9 |
Controllable Device Type |
Defines information about a class of controllable devices. |
10 |
Device Location Type |
Defines specific types of locations at which devices are installed. |
10 |
Metered Service Point Type |
Defines specific types of points where services are provided. |
11 |
Program Calculation Group |
Collections of program calculation rules used to calculate device control scores. |
12 |
Program Calculation Rule |
Defines rules that calculate device control scores |
13 |
Metered Service Type |
Defines collections of properties common to a set of metered service records |
13 |
Program Subscription Type |
Defines collections of properties common to a set of Program Subscriptions. |
14 |
Program Rules |
Defines specific rules and parameters used by programs and program calculation rules. |
14 |
Program Initiatives |
Defines criteria used to determine if customers are eligible to participate in programs. |
14 |
Customer Questions |
Defines specific information related to a customer or their service. |
15 |
Processing Methods |
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. |
16 |
Master Configuration |
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. |
17 |
Information Lifecycle Management |
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. |