Oracle Utilities Work and Asset Management WAM is best-in-class Work and Asset Management solution, with pre-built integration with other Oracle utility applications, Comprehensive asset management solution for fixed, linear and smart devices throughout the lifecycle of assets. Asset condition monitoring, risk management and planning functionalities tailor-made for utilities’ assets. Compliant with all well-known industry best practices, for e.g., ISO 55000 and PAS 55.  Enhanced user experience through support for new age digital technologies such as mobile and analytics.

• Logging in to the Oracle Utilities application environment

• Explore Application Viewer:

1. Navigate to Admin Menu—A—Application Viewer to launch the Application Viewer.
2. Once in the Application Viewer, toggle the tree view to Physical by clicking the icon with the Physical label. The Application Viewer will list all the physical tables.
3. Navigate to Admin Menu—T—Table to open the table search.
4. Click the search icon.
5. Compare the search results with the tables in Application Viewer.
6. Click the W1_ASSET table in the Application Viewer.
7. In the application, enter the table name W1_ASSET in the table search and click the Refresh bar.
8. Select the W1_ASSET table and compare the table metadata, such as fields, with what is in the Application Viewer.

• These are setups and configurations: Mapping to an Identifier Type – Mapping to a Characteristic Type – Mapping to XML
  Location – Location and Organization Type – Contacts – Locations – Manufacturer Specifications – Specification Business Object – Asset – Service History – Assessment – Assessment Classes – Measurement – Approval Processing – Approval Profiles – Approval Requests – Work Order and Activity – Work Order Requirements – Approved Work Orders – Template Work Orders – Completion Events – Preventive Maintenance – Maintenance Schedules and Triggers – Maintenance Specifications and Algorithms – Scheduling – Inventory – Inventory Processes – Purchasing – Taxing Data – Financials – Lifecycle Business Objects – Warranty – Material Disposition.
• Maintenance Objects: Most objects are made up of several tables and the term maintenance object (MO) to reference the group of tables that hold an object’s physical data.

• Business Objects: Business Objects are Logical Views of Maintenance Objects. BOs are much more than visual definitions of objects.BO-specific business rules without coding in Java. Populate and retrieve effective-dated attributes without complicated joins to effective-dated table. Set up default values for BO attributes. Extend objects without the need for new tables and columns. Enable the generation of HTML that reflects each element’s data type. Allow external systems to communicate with our system in a more natural way (rather than in a third normal form way).
  
• BO Elements and Validation Rules: A BO’s elements are defined in their schema. BO schemas are XML documents. Schema Configuration is used To Implement Simple Rules. The various validation-oriented attributes that can be defined in a BO’s schema:
• Validation Rules: Validation algorithms are on a BO if you need more sophisticated validation than can be defined using the schema attributes. Validation algorithms are executed after the MO processing (e.g., core validation rules).
• Other Types of BO Rules: Pre-processing rules are triggered from the BO layer only. Other rules are triggered from the MO layer whether called via a business object or directly Therefore, the MO needs to determine the processed instance’s BO before executing its rules.
• Business Object Lifecycle: Plug-in algorithms can be linked to a BO. For example, you can develop validation plug-ins to
  validate the elements on different types of customers.
• Oracle Utilities Application Framework script: There are three types of scripts:
  • Plug-in scripts: These run on the server and are plugged into the BO or MO on the algorithm tab or in the algorithm section of a lifecycle. They get their inputs/outputs from their BO’s schema
  • Service scripts: These run on the server and can be considered a stand-alone script to be called from other scripts. They have their own schema
  • BPA scripts: These run on the client and are used to guide a user through a business process; for example, adding a person or a paycheck.

• Plug-in scripts and service scripts are developed for server-based business rules and functions.
• –These types of scripts run on the application server (this is why the term “server script” is used to refer to both types of scripts).
• Business Process Assistant (BPA) scripts are developed for client-based functions. These types of scripts run on the client’s browser. No client software is installed, these scripts are executed in the client browser.
• Portals and Zones: Portals can be easily changed and extended by an implementation team (object maintenance transactions cannot be changed without significant effort). Portals are meant to maintain BOs, whereas object maintenance transactions maintain MOs (which are, by
  definition, generic). Virtually Everything Is Configurable. There are common features of zones and most of the features are controlled by metadata (naturally). Zones can be constructed using BOs (Business Objects), BS’s (Business Services), and SS’s (Service Scripts). The zone is the ONLY place where you can code SQL. You can write efficient SQL in a world of XML schemas. Therefore, you use the programs and drivers associated with the MOs to access the database to add, modify, and delete rows in the database. All of this takes place in the framework, behind the scenes.