Oracle Utilities Work and Asset Management

Transcription

1 Oracle Utilities Work and Asset Management User Guide Release E May 2015

2 Oracle Utilities Work and Asset Management User Guide Release E May 2015 Documentation build: :27:29 [WAM2_ ] Copyright 2012, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. 2

3 Contents Getting Started About Oracle Utilities Work and Asset Management About the Home Page Understanding the User Interface Menus and Navigation Standard Actions for Data Maintenance...15 Viewing and Adding Log Entries Searches, Saved Searches and Bookmarks Searching Data Using the 360 Degree Search...16 About 360 Degree View About 360 Degree Search...17 Approvals Understanding Approvals About Approval Requests and Approvals...18 About Approval Profiles...20 About the Approval Dashboard Working with Approval Administration Defining an Approval Profile...21 Setting Default Approval Profile for a Record Type...21 Working with Approvals...21 Reviewing a Record Before Approving Approving a Record in the Approval Dashboard Approving a Record on the Approval Request Routing/Submitting a Record for Approval Reviewing Documents Requiring your Approval Decision Disable Notifications for an Approver...23 Assets Understanding Asset Management...24 About Assets About Asset Types About Components About Asset Locations About Asset Location Types About Bill of Materials...27 About Service History About Service History Types...29 About Condition Assessment Questions...29 About Condition Assessment About Condition Assessment Classes About Specifications...30 About Firmware About Operational Readings (Measurements) About Measurement Types (Operational Readings)...32 About Measurement Unit of Measurement About Warranty About Warranty Terms About Material Disposition About Mass Asset Disposition Update About Replication About Asset Configurations About Asset and Component Configuration Types...35 About Asset and Component Configuration Reports...35 About Shapes...36 Working with Asset Administration...36 Defining Measurement Unit of Measurement (UOM)...36 Defining a Measurement Type (Operational Reading)...36 Defining Condition Assessment Questions...36 Defining Service History Types

4 Defining a Condition Assessment...37 Defining a Condition Assessment Class Defining Asset Location Types...37 Defining Asset Types...38 Defining Component Types Defining a Shape Defining Asset Configuration Types Working with Assets, Components, Service History and Asset Related Objects Working with Assets Creating an Asset Location...39 Creating an Asset Manually Entering Service History Manually Performing Asset Maintenance Performing an Asset Inspection Scheduling an Asset Inspection Reviewing Asset Statistics...41 Reviewing Asset Type Statistics Rejecting Assets Retiring Assets...42 Updating the Disposition of a Single Asset Update the Disposition of a Group of Assets Working with Components...43 Creating Components Manually Storing a Component after Receipt Attaching a Component to an Asset...43 Detaching a Component from an Asset...44 Creating a BOM Part...44 Working with Vehicles...44 Entering a Vehicle as an Asset Entering a Vehicle as a Storage Location Working with Specifications Defining Specifications Adding or Updating Firmware Versions Working with Operational Readings (Measurements) Entering Operational Readings (Measurements) Using Operational Reading (Measurement) Quick Entry...46 Importing Operational Data from a File Working with Warranties and Warranty Terms Defining a Warranty Term...47 Entering a Warranty Entering a Warranty from an Asset Working with Asset Configurations and Configuration Reports Creating an Asset Configuration Creating an Asset Configuration Report Creating Work to Correct or Maintain Asset Configurations...49 Inventory...50 Understanding Inventory About Storage Locations About Storage Location Types...51 About Stock Items...51 About Stock Item Details...52 About Commodity Codes About Material Request and Issue About Material Request Templates...53 About Material Returns...54 About Physical Inventory About Inventory Adjustments...54 About Stock Transfers About Receiving About Returns About Material Disposition About Batch Stock Reorder and Reorder Review...56 Working with Inventory Administration...57 Working with Storage Locations

5 Defining a Storage Location Type Creating a Storage Location Linking a Contact to a Storage Location Entering a Vehicle as a Storage Location Defining a Commodity Code...58 Working with Inventory...59 Working with Stock Items Entering a Stock Item...59 Adding a Stock Item to a Storeroom (Stock Item Details)...59 Reviewing Stores...60 Reviewing and Approving Items for Reorder (Reorder Review)...60 Processing a Stock Transfer...61 Performing a Physical Inventory Working with Material Requests, Issue and Returns Creating a Material Request (Checkout Request) Issuing Stock (Material Issue) Creating a Material Request Template Processing a Material Return (Returning Stock Items)...63 Working with Purchasing Receipts and Returns Record Receipt/Delivery for a Purchase Order (Processing a Receipt) Processing a Purchasing Return...64 Purchasing Understanding Purchasing About Buyers...65 About Purchase Commodities About Manufacturers...66 About Vendors About Capability Types About Payment Terms...67 About FOB (Freight on Board or Free on Board)...67 About Purchase Requisitions...67 About Purchase Orders About Expedite Purchase Order About Blanket Contracts About Blanket Contract Access Lists...69 Working with Purchasing Administration...69 Defining a Buyer Defining a Purchase Commodity Defining a Capability Type Defining a Vendor Payment Term...70 Defining a FOB (Freight on Board or Free on Board) Working with Purchasing...70 Working with Vendors and Manufacturers Defining a Manufacturer Creating a Vendor Adding a Vendor Location...71 Defining a Vendor's Payment Terms Adding Capabilities to a Vendor Viewing Vendor Purchase Order History Viewing Open Requisitions with a Vendor...72 Working with Purchase Requisitions and Purchase Orders...72 Creating a Purchase Requisition Manually Adding Line Items to a Purchase Requisition...72 Creating a Purchase Order from a Purchase Requisition Creating a Blanket Contract from a Purchase Requisition Creating a Purchase Order Manually...73 Adding Line Items to a Purchase Order Updating an Approved Purchase Order...74 Issuing a Purchase Order Creating a Change Order...75 Creating an Expedite Order Working with Blanket Contracts...75 Defining a Blanket Contract Access List...75 Granting User Access to a Blanket Contract

6 Creating a Blanket Contract...76 Adding Line Items to a Blanket Contract...76 Re-sequencing Line Items on a Blanket Contract Creating a Purchase Requisition from a Blanket Contract Creating a Purchase Order from a Blanket Contract...77 Reviewing the Activity for a Blanket Contract...78 Creating a Blanket Contract Revision...78 Resource Management Understanding Resource Management...79 About Hierarchies...79 About Organizations...79 About Organization Types...80 About Contacts...80 About Contact Types...80 About Resource Types About Documents (Attachments, Standard Notes and URL Attachments) About Document Types...82 About Service Classes...82 About Service Areas About Employees About Employee Types About Employee Unavailability About Employee Unavailability Types About Resource Unit of Measurement About Crews...83 About Crew Types...83 About Crew Shifts...84 About Crew Shift Types...84 About Shift Plan Templates About Crafts About Equipment...85 About Other Resources About Other Direct Charges Working with Resource Management Administration Defining a Resource Unit of Measurement (UOM) Defining Organization Types...86 Defining a Service Class Defining a Service Area...86 Defining a Contact Type...86 Defining a Document Type...87 Defining an Employee Type Defining an Employee Unavailability Type Defining a Crew Type...87 Defining a Crew Shift Type Working with Resource Management Working with Contacts Creating a Contact Linking a Contact to a Storage Location Working with Organizations Creating an Organization Linking an Organization to a Location Working with Documents Creating a Document Adding an Attachment, Note or URL to a Record Viewing Documents Replacing a Document File...90 Deleting Documents from Records Working with Common Attachments Creating a Common Attachment from the Attachment Portal Viewing Common Attachments Editing Common Attachments...91 Replacing an Common Attachment File Deleting Common Attachments...92 Working with Employees

7 Creating an Employee...92 Enter and Track Employee Training Information Entering Employee Unavailability Create an Employee Leave Request...93 Working with Work Resources, Crews and Crew Shifts Entering Equipment Entering an Other Resource Creating a Crew Adding Workers to a Crew...94 Creating a Craft Adding an Hourly Rate to a Craft Defining a Secondary Craft...95 Creating a Shift Plan Template...95 Subscribing a Crew to a Common Shift Weekly Template...95 Creating a Daily Crew Shift...96 Creating a Weekly Crew Shift...96 Reviewing a Crew Shift Schedule...96 Work Management Understanding Work Management...97 About Planners and Maintenance Managers About Work Requests...98 About Work Orders About Template Work Orders About Activities About Activity Types About Activity Resource Requirements About Scheduling About Projects About Timesheets About Preventive Maintenance About Reliability Centered Maintenance (RCM) About Completion Events About Completion Event Types About Inbound Communication Working with Work Management Administration Defining a Maintenance Manager Defining a Planner Defining an Activity Type Defining Completion Event Types Defining Time Periods Defining a Labor Earning Type Defining an Overtime Type Defining a Project Category Working with Work Management Working with Work Requests Creating a Work Request Manually Creating a Work Order or Activity from a Work Request Finding Duplicate Work Requests Working with Work Orders and Activities Creating a Work Order Creating a Template Work Order Creating a Purchase Requisition from a Work Order Creating an Activity Generating Activities in Batch Processing Adding an Activity to a Work Order on the Work Order Adding Resource Requirements to an Activity Processing and Completing Activities Manually Creating Completion Events Manually Creating an Inbound Communication Working with Projects Creating a Project Viewing Subproject Information Working with Preventive Maintenance Creating a Maintenance Schedule

8 Creating a Maintenance Trigger Financials Understanding Financials About Financial Transactions About Accounting Calendars About Currency About Colors About Cost Category About Cost Centers About Expense Codes About Business Units About Factors and Factor Values About Tax Rate Schedules About Distribution Codes Working with Financials Creating an Accounting Calendar Defining Currency Defining a Color Defining a Cost Category Defining a Cost Center Reviewing Cost Center Statistics Deactivating a Cost Center Defining an Expense Code Deactivating an Expense Code Defining a Business Unit Defining a Factor Defining a Tax Rate Schedule Defining a Distribution Code Reviewing a Financial Transaction General Administrative Functionality About Access Control About Statistics Understanding Communications Administration About Communication Types Defining Communication Types Business Objects/ s Approval Object s Approval Profile Definitions Approval Request Definitions Asset Management Object s Asset Object s Asset Type Definitions Component Type Definitions Asset Definitions Component Definitions Shape Definitions Asset Location Type Definitions Asset Location Definitions Bill of Material Definitions Service History Object s Condition Assessment Question Definitions Service History Type Definitions Condition Assessment Definitions Condition Assessment Class Definitions Service History Definitions Specification Object s Specification Definitions Child Specification Definitions Operational Reading (Measurement) Object s Measurement Type (Operational Readings) Definitions Operational Reading (Measurement) Definitions Measurement Unit of Measurement Definitions Warranty Object s

9 Warranty Term Definitions Warranty Definitions Asset Configuration Object s Asset Configuration Type Definitions Asset Configuration Definitions Configuration Report Definitions Inventory Object s Material Request, Issue and Return Object s Material Request Template Definitions Material Request Header Definitions Material Request Line Definitions Material Issue Line Definitions Material Return Header Definitions Material Return Line Definitions Physical Inventory Object s Physical Inventory Definitions Inventory Adjustment Definitions Receipt Object s Receipt Definitions Receipt Line Definitions Return Line Definitions Reorder Review Definitions Stock Item Detail Definitions Storage Location Object s Storage Location Type Definitions Storage Location Definitions Commodity Code Definitions Purchasing Object s Buyer Definitions Vendor Object s Vendor Definitions Vendor Location Definitions Capability Type Definitions Payment Term Definitions Free on Board Definitions Purchase Order Object s Purchase Requisition Header Definitions Purchase Requisition Line Item Definitions Purchase Order Header Definitions Purchase Order Line Item Definitions Expedite Purchase Order Definitions Blanket Contract Object s Blanket Contract Definitions Blanket Contract Line Definitions Blanket Contract Access List Definitions Manufacturer Definitions Purchase Commodity Definitions Resource Management Object s Organization Object s Organization Type Definitions Organization Definitions Resource Type Definitions Contact Object s Contact Type Definitions Contact Definitions Crew Object s Crew Type Definitions Crew Definitions Crew Shift Object s Crew Shift Type Definitions Crew Shift Definitions Shift Plan Template Definitions Document Object s Document Type Definitions

10 Document Definitions Employee Object s Employee Type Definitions Employee Definitions Employee Unavailability Type Definitions Employee Unavailability Definitions Other Direct Charge Object s Other Direct Charge Definitions Other Direct Charges Detail Definitions Service Object s Service Area Definitions Service Class Definitions Resource Unit of Measurement Definitions Work Management Object s Work Order Object s Work Request Definitions Work Order Definitions Template Work Order Definitions Activity Object s Activity Type Definitions Activity Definitions Template Activity Definitions Template Activity Resource Definitions Completion Event Type Definitions Completion Event Definitions Inbound Communication Definitions Communication Type Definitions Project Object s Project Category Definitions Project Definitions Material Disposition Definitions Timekeeping Object s Time Period Definitions Labor Earning Type Definitions Overtime Type Definitions Timesheet Definitions Timesheet Detail Definitions Preventive Maintenance Object s Preventive Maintenance Calendar Definitions Preventive Maintenance Schedule Definitions Preventive Maintenance Trigger Definitions Failure Profile Definitions Financial Object s Accounting Calendar Definitions Business Unit Definitions Commodity Code Definitions Cost Category Definitions Color Definitions Cost Center Definitions Distribution Code Definitions Expense Code Definitions Factor Object s Factor Definitions Factor Value Definitions Financial Transaction Definitions Tax Rate Schedule Definitions General Administrative Object s Statistics Definitions

11 Chapter 1 Getting Started This guide provides information on working with the functionality in Oracle Utilities Work and Asset Management. This guide and the Oracle Utilities Work and Asset Management section of the online help contain the same contents. The Getting Started section provides information on the business processes supported by the application, about the home page and on understanding the user interface. About Oracle Utilities Work and Asset Management Oracle Utilities Work and Asset Management provides functionality to handle large volumes of assets and to manage the receipt, installation, maintenance, tracking and removal of those assets. The system also manages approval processing, tracks purchasing transactions, manages inventory and resources, and tracks costs, accounting and financial transactions. The system handles the following main functional areas: Home Page: The home page provides a comprehensive dashboard where you can access information you need to review and complete your work. For example, the Main tab can be configured to display your key work areas; crews or buyers that you monitor, approval summary, your bookmarks or saved searches, and so on. Additional tabs provide easy access to information and KPIs that approvers, planners, executives and others can use to review organizational functions and complete their work. Approval Processing: One of the ways that the system simplifies and speeds up work is by routing records when they require approval. Approval requests use approval profiles to determine the properties and requirements for the approval. Approvers can use the Approval Dashboard to manage the approvals that require their attention. Assets: Asset management provides functionality to track the purchase, repair and maintenance of assets and asset components using general work management processing, preventive maintenance techniques, purchasing processing and inventory tracking. The system also allows organizations to record asset measurements and perform asset inspections in addition to the standard maintenance that is performed on assets. Inventory: Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. As inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available. Purchasing: Purchasing functions can be used to plan, initiate, and process purchases and purchasing contracts. The system also manages vendors, designated buyers, and stock items. Oracle Utilities Work and Asset Management User Guide 11

12 Resource Management: Resources encompass any object that contributes to the running of your organization. This includes crews and crew shifts, employees, equipment, contacts, documents, standard notes and attachments, and so on. Work Management: Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked, as applicable to your business processes. The system also allows organizations to set up preventive and predictive maintenance cycles including reliability centered maintenance. Accounting and Financial Transactions: The system tracks transactions that incur costs including purchasing and procurement costs, inventory and stocking costs, and the costs associated with the labor, equipment and materials that are incurred when completing work. About the Home Page The Oracle Utilities Work and Asset Management home page provides a comprehensive dashboard where you can access all of the information you need to review and complete your work. The home page can be configured as the first page launched when you log in to the application. This can serve as your personal web page where you configure system elements that you use most frequently. Zones are added to the home page by adding options to Portal Preferences under your User Profile. Using profile preferences, you can also personalize the arrangement of the zones and whether or not they are initially collapsed or open when the home page opens. Refer to the Oracle Utilities Application Framework online help for more information on using portal preferences. In general, click on any link, pie chart, or graph to open details about that item. The Go To icon,, at the front of some items opens the corresponding tab with the related information populated. For example, if you click the symbol in front of a storeroom in the My Storage Locations section on the Main tab, the system opens the Inventory tab with that Storeroom ID populated. Click Refresh to update and display the graphs. The base package home page can include the following tabs and zones: Main: The Main tab displays general system information and any custom zones provided by your implementation (such as company news). Click the Add link in any zone to add the related information. The My Buyer, My Storage Locations, and My Crews zones do not automatically include the records. For example, if the logged in user is a buyer, he or she must still add their own buyer to the zone, if they want to include their own buyer in the zone. As examples, the Main tab might include the following: Approval Summary: Provides a pie chart indicating the percentage of record types the logged in user has in their approval queue. Approval information can also be accessed via the Approval tab on the home page or directly in the Approval Dashboard. Crew Membership: Indicates any crew shifts in pending, planned or active status where the logged on user is a member. My Buyer: A list of buyers that are of interest to the logged on user. For example, if a supervisor wants to keep an eye on the buyers in his or her group, they can be added here. My Crews: A list of crews that are of interest to the logged on user. A crew supervisor can add crews, for example, to have access to an easy list where he or she can click through to view the crew schedule or further details about the crew. My Storage Locations: A list of storage locations that are of interest to the logged on user. A planner or inventory manager, for example, can add locations here to monitor specific locations. Open Work Requests by Criticality: Displays a graph representing ALL work requests that are in approved status and that have a criticality. Criticality is defined on the asset location, so if a work request does not reference an asset with a location, it does not display in this zone. Planner Weekly Planned WO Summary: Displays a graph representing work orders, by planner, by week, by owning organization. The number on the left represents the number of work orders in planning status. Oracle Utilities Work and Asset Management User Guide 12

13 Alerts, Saved Searches, Bookmarks and Favorites: Custom configuration by your implementation also allows you to add other zones which are not delivered in the base package to display on the home page. Refer to the Oracle Utilities Application Framework guides under Approvals: The Approvals tab provides the same information and functionality as the Approval Dashboard. Refer to the About the Approval Dashboard section for more information. Work: The Work tab can display statistics about work requests and work orders. Some of the work zones might include a link to the Statistics portal. Authorized users can edit some of the details displayed in the zones using this portal. The base package Work tab zones include: Active Activity Count by Planner: Provides a count of activities in active state by planner. Active Activity Count by Crew: Provides a count of activities in active status, by crew and owning organization, where there is a crew on the schedule. Emergency Work Orders: Provides a count of all emergency work orders in any status based on created date. A typical usage is to show how many emergency work orders are created each day, week or month. Emergency Work Order Trend: Provides a count of all emergency work orders. The created period ranges and the priority minimum are set in Master Configuration. Planned WO Count by Planner: Provides a count of all work orders in planning status, filtered by organization and planner. Weekly Planned WO Count by Planner: Provides a count of all work orders in planning status, by week, filtered by organization and planner. Completed WO Count by Planner: Provides a count of all completed work orders, by planner and organization. Weekly Completed WO Count by Planner: Provides a count of all completed work orders, by week, filtered by planner and organization. Completed WO Count by Crew: A count of all completed work orders by crew and organization. This only includes scheduled work orders. Planned WO Count by Crew: A count of all planned work orders, by crew and organization. This only includes scheduled work orders. Weekly Completed WO Count by Crew: A count of all completed work orders by crew and organization, by week. This only includes scheduled work orders. Weekly Planned WO Count by Crew: A count of all planned work orders with a scheduled crew. Open Work Requests: A count of all work requests in approved status. This zone shows all work requests, regardless of the role of the logged in user. Open Work Requests by Criticality: A count of all work requests that are in approved status and that have a criticality. Criticality is defined on the asset location, so if a work request does not reference an asset with a location, it does not display in this zone. Inventory: The Inventory tab provides information about stock items by storeroom. You must enter a storeroom and click Refresh to display the zones. The base package Inventory tab zones include: Overstocked Stock Items by Commodity Category: A count of stock items that have stock quantities which are above the maximum quantity indicated in the stock item details record. The stock item detail must also include commodity categories to be represented in this zone. Below Reorder Point Stock Item Overstocked Stock Items by Commodity Category: A count of stock items that have stock quantities which are below the maximum quantity indicated in the stock item details record. The stock item detail must also include commodity categories to be represented in this zone. Purchasing: The Purchasing tab can display purchasing statistics by buyer. You must select a buyer and click Refresh to display the zones. The base package Purchasing tab zones include: Buyer Open Purchase Requisition Count: A count of open requisitions by status. Oracle Utilities Work and Asset Management User Guide 13

14 Buyer Expedited Purchase Order Count: A count of expedited purchase orders. Labels and data ranges are defined in Master Configuration. A typical usage for this zone is to show which expedited purchase orders are at or nearing their expedite date. Blanket Contract Count by Limit Used: A count of blanket contracts per percentage of usage against the limit, buy buyer. The limit ranges are set in Master Configuration. Expiring Blanket Contract Count: A count of blanket contracts that are about to expire in x amount of time, by buyer. The time frames are set in Master Configuration Understanding the User Interface For information about the main application toolbar, menu system, user setup and security, and user interface standards, refer to the "System Wide Standards" topic in the "Oracle Utilities Application Framework" online help. This section provides high level information about menus, navigation and the Oracle Utilities Work and Asset Management specific menus. Menus and Navigation This topic describes the menus and general rules for navigating the system. Menus are highly configurable, so the options that appear may vary based on your user profile and your system configuration. System Menus By default, the system provides two menus: The Admin menu: Provides access to functions used for setup and administration. Only users who have administrative privileges will be able to see or access this menu. The main user functionality Menu: Provides access to all other functions. The options displayed on each menu are based on the settings defined in your user profile. Your user profile also controls your access to different portals and dashboard zones. NOTE: Refer to the "Oracle Utilities Application Framework" online help under Framework Business Process > System- Wide Standards > Page Components > Characteristics Common to All Pages > The Application Toolbar for more detailed information about working with menus and other navigational functions. Access to Different Applications The menu system provides access to both Oracle Utilities Application Framework functions and Oracle Utilities Work and Asset Management functions. If you have additional Oracle applications installed, the menu system will provide access to functions for that application as well. Oracle Utilities Application Framework functions are described in the online help of the same name. Likewise, topics related to Oracle Utilities Work and Asset Management are listed in the help contents panel under the appropriate heading. Oracle Utilities Work and Asset Management User Guide 14

15 Standard Actions for Data Maintenance This section provides information on basic steps for performing standard actions on data maintained from the Main or Admin Menu. The system displays buttons for all valid actions, based on the object's current status, your user privileges, and your system's configuration. Use these buttons and actions to complete functions such as creating a new record, editing records, searching, deleting, duplicating, bookmarking, changing status and routing records for approval, and so on. NOTE: Refer to the "Oracle Utilities Application Framework" online help under Framework Business Process > System-Wide Standards > Page Components > Characteristics Common to All Pages > Page Title Area > Page Actions Toolbar > Bookmark Button for more detailed information about working with standard actions. Viewing and Adding Log Entries Use the Log tab to view or add log entries for the current object. The log displays a list of user and system actions associated with an object, such as when it was created, last updated, or transitioned to different status. For each log entry, the system displays the date and time the action occurred, the user/system that initiated the action, the type of action, and related object, if any. To create a new log entry, click the Add Log Entry link in the zone title, then enter log entry details and click Save. Your user ID is saved with the log entry. Searches, Saved Searches and Bookmarks Most portals include a search screen where you can find applicable records according to various criteria. The system can search for an item matching your criteria based on multiple methods including using wildcards. You can also sort the search columns, as needed. Searching by Status Note that when you search by status, the statuses that are available are dependent on other fields that are selected. For example, if searching for an activity, ALL possible statuses are available for search if there is no activity type selected. However, if you select an activity type, the status search is limited to the statuses that apply for that activity type. This filtering helps users to avoid having to sort through irrelevant statuses in their search query. This applies for all record types. Save Search Options You have the ability to save searches from any portal search screen by accessing options on the Explorer Zone menu. Click the Explorer Zone Menu icon to list available tools. From this list you have options such as: saving your current search opening a saved search after it is saved setting or removing a search as your default search when you open the portal adding or removing a search to/from your favorites NOTE: Beyond searching, the explorer zone also allows you to export a search to excel, print, filter, and so on. Oracle Utilities Work and Asset Management User Guide 15

16 Refer to the "Oracle Utilities Application Framework" online help under Framework Business Process > Configurable User Interface Features > Configurable Zone Information > Explorer Zones > Explorer Zone Menu for more detailed information about working with these useful system tools and others. Bookmarks Click the Bookmark button on most pages to save the current page and context to the bookmarks list which appears in your Dashboard. After clicking the Bookmark button, you are prompted to provide a name for the bookmark. After saving, it is visible in the Bookmarks Zone on the dashboard, allowing you to return to the same screen. For example, if you are looking at a specific purchase order, the bookmark can go directly back to that record. Likewise, you can create a bookmark from a search results screen to return there with one click. NOTE: Bookmarks can be managed from your User Profile record. Refer to the Oracle Utilities Application Framework online help under Framework Business Process > System-Wide Standards > Page Components > Characteristics Common to All Pages > Page Title Area > Page Actions Toolbar > Bookmark Button for more detailed information about working with bookmarks. Follow links in this topic to learn more about bookmarks in your User Profile and other information. Searching Data Using the 360 Degree Search Use this procedure to search for data using the 360 Degree Search portal. 1. Select Main Menu > 360 Search. 2. Select a Query Option and enter your search criteria. 3. Click Refresh. 4. Click the link for the option you want to view. The corresponding portal opens for the object you selected. About 360 Degree View The 360 Degree View feature allows users to view data for assets, components, contacts and locations from a single set of portals. The 360 Degree View has a separate portal for each type of object: Asset Information Asset ID Asset Specification Asset Location Information Storage Location Information Location ID Contact Name Once you select one object, the 360 Degree View provides related information so that you have full visibility into all information about that object. For example, if you select Asset Information and search on an asset type, the resulting view portal shows the components, service history, activity history, and location information for assets of that asset type. Oracle Utilities Work and Asset Management User Guide 16

17 About 360 Degree Search The 360 Degree Search feature allows users to search for assets, components, specifications, locations and contacts. Users can also search on other identifiers or characteristics as defined by your organization. Selecting a Query Option changes the search fields to present different options. From the search results list, you can navigate to the selected portal to view data for the object. Oracle Utilities Work and Asset Management User Guide 17

18 Chapter 2 Approvals The following sections provide information on concepts related to approval processing. Understanding Approvals One of the ways that the system simplifies and speeds up work is by routing records when they require approval. Approval requests use approval profiles to determine the properties and requirements for the approval. Approvers can use the Approval Dashboard to manage the approvals that require their attention. This section describes how various processes work together to manage approvals throughout the system. Please refer to the Working with Approvals section for procedural tasks related to these concepts. About Approval Requests and Approvals Records within the system, such as purchase orders or work requests, often require an authorized person to provide approval for the purchase or work. Approval requests are used to route the request for approval to the appropriate individuals with the authority to approve or reject the request. Basic approval processing requires that the person creating or managing a record that requires approval must create an approval request. This is done by clicking the Submit for Approval button on the record when it is in pending approval status and selecting the appropriate approval profile for the document. Once a record is submitted for approval, the request is ed to approvers, sent to their To Do List, or both. Most users only need to know which Approval Profile to choose when they submit a record for approval. This selection will depend on your business processes and how your approval profiles are configured. For example, when a user submits an approval request for a timesheet, he or she should only see approval profiles available for a timesheet. The Approval Request shows the related document, the person who submitted it and when, who has approved it so far, and which roles still need to provide an approval decision. Oracle Utilities Work and Asset Management User Guide 18

19 The Approval Profile indicated on the approval request identifies the people who need to approve the record and their role. Sometimes there are multiple approvers needed, depending on how the approval profile is set up and your business practices. Often records will have a set of approval profiles which are defined for all records of that type. For example, when a new work request is routed for approval, the options for approval profile are limited to those defined for work requests. Approvers can access information about approvals that require their attention using the Approval Dashboard. The person submitting the record for approval can check the status of the approval from a zone on their home page or by checking the individual record. The requestor is notified via when the record has been approved or if the request times out. Most approvers also have access to the Approval Request Action zone on the side Dashboard. You can also record and submit your decision here. Access to this zone is controlled by your Portal Preferences in your user profile. The Log tab on the record being approved indicates who approved the record and when. Refer to the Approval Request Definitions section or the Approval Profile Definitions section for more information and field definitions. Approval Routing As mentioned, an approval profile includes approval types and dollar limits that control which approvers can and are required to approve a record. When the approval request is submitted, the system sends notification to all users indicated on the approval profile (approvers) by , their To Do List or both depending on the system settings for notifications. The notification is sent to approvers associated with the To Do Roles on the approval profile in the sequence defined on the profile (the approval path). The approval request moves along the route/hierarchy based on the roles of the approvers and their approval decisions. For example: One Standard Role: If the approval profile consists of one To Do Role with mandatory or standard approval type, the users with that role receive the approval notification and any one of them can approve the request as long as the To Do Role has authority for the needed dollar amount. Multiple Roles/All Standard: If the approval profile consists of multiple To Do Role s and all are standard, any To Do Role can approve the request as long as they have the authority for the needed dollar limit. Mix of Mandatory and Standard Roles: If the approval profile consists of multiple To Do Roles with a mix of mandatory and standard, the users with mandatory must approve the request even if the standard approvers have authority based on the dollar limit or other factors. In other words, the mandatory approval role must take an action by agreeing or rejecting the request. Request Time-out: If approvers do not respond to the request within the time allotted by the time-out threshold, the system sends another notification to the approvers. If they still do not take action, the request moves to the next approval role, as applicable and the next role receives notification. One Approver with Multiple Roles: If one approver has multiple To Do Role s on one approval profile for the request, the system prompts that person to indicate which role he or she is approving. For example, approver Jon is in both the Supervisor and Manager To Do Role s. When an approval request comes in and Jon approves the request, a selection box opens to allow him to choose in which To Do Role he is approving the request. If Jon selects multiple approval requests to approve at once in the Approval Dashboard he may receive a warning that he needs to specify an Acting To Do Role before selecting an action. This means you must pick a role from the Acting To Do Role drop down and click Search to let the system know which role you are using to approve the requests. Insufficient Approval Amount: If an approval request comes in for a record with a higher dollar amount than anyone on the approval path is authorized to approve, the requestor is notified that no one on the approval profile has sufficient authority. The requestor must choose a different approval profile and resubmit. One Standard Role: If an approver rejects the approval request, the request terminates and additional approvers on the approval path are not notified. The requestor is notified that the request has been rejected. Any approver in the route can Oracle Utilities Work and Asset Management User Guide 19

20 reject and terminate the approval process regardless of their approval authority or limit amount. However, this does not apply for notification only approvers. Not Authorized to Approve: Some roles might be set as not authorized to approve but they still appear on the approval path. These approvers receive notification of the request and can approve or reject, but their decision is simply recorded for the next approver on the approval path to be aware of their decision. This setting is only applicable for an approval profile that is for no amount. If this type of approver rejects the request, the same processing applies as described for one standard role. About Approval Profiles Approval profiles are used to define the approval hierarchy within your organization. Based on To Do Roles, approval profiles define: the types of documents the role can approve the working calendar to use when determining approval time lines and when to send alerts dollar amount maximums that the role is authorized to approve An approval profile can have one or many To Do Roles, and it is possible for an approver to be assigned to more than one To Do Role in the same approval profile. Depending on the notification setting designated on the approval profile, the approver receives an and/or an alert in their To Do List. Note: Individual approvers can choose to modify their notification settings for approvals. Navigate to the User portal and access the Characteristic tab to set the Approval Profile Override setting to disable notifications for approval requests. When this is set, the approver does not receive any s and must rely on the approval dashboard or alerts. Refer to the Approval Profile Definitions section for more information and field definitions. Refer to the configuration guide for information on how approvals are set up for various document types. About the Approval Dashboard The approval dashboard provides a summary of approval requests that have been sent to the broad list of approvers with a breakdown of the approval profiles. This overview provides approvers with a simple summary of the records requiring their attention. The summary list includes the counts of approval requests that have been sent out to any approvers that are not Notification Only and shows the current approvers and the mandatory future approvers. The list is broken down by document type and approval profile. It is possible to filter the list by current or future approvers using the Queue field. The filter is used to distinguish current and future approval requests which may require the attention of the approver. For example, if an approver is about to go on vacation, he or she may want to take action on an approval request early. In this case the list can be filtered by future approval requests where this approver is not necessarily next in the approval route. This is a way for the approver to obtain a preview of requests that are coming from the route. Broadcasting an individual line opens a zone where the approver can check off records and choose a button to make their approval decision (approve or reject). The approver can also click the link to open the approval request itself, and to open the individual record. Note that the dashboard contents are specific to the logged in user, so one person may see a different list than another depending upon their approval authority. Oracle Utilities Work and Asset Management User Guide 20

21 Approval Request Dashboard Zone The system also includes a zone in the side dashboard which highlights any new approval requests that require the logged in user s attention. The User can approve or reject the request in this dashboard, if desired. Working with Approval Administration The following sections provide information on tasks associated to creating and maintaining the administrative records needed for approvals. Defining an Approval Profile Navigate to the Approval Profile portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: Work calendars and related document types must be created in order to reference them on the approval profile. You must also have the necessary approval related To Do Types defined to determine which To Do Types are responsible for profile that you are creating. Establish the approval hierarchy for the profile by entering To Do Roles, approval types, notification methods and amount limits for each To Do Role. Refer to the Approval Profile Definitions section for more information and field definitions. Refer to the configuration guide for information on how approvals are set up for various document types. Setting Default Approval Profile for a Record Type Your organization should configure your system with the To Do Types, To Do Roles, and Approval Profiles in combination so that when a user selects the Submit for Approval option, the list of possible approval profiles is limited to a finite selection of approvers based on the type of document they are trying to approve. Refer to the configuration guide for more information. Working with Approvals The following sections provide information on tasks associated to working with approvals and approval processing. Refer to the Understanding Approvals section for a conceptual overview of this functional area or to the Approval Object s sections for more information and field definitions. Reviewing a Record Before Approving Use this procedure to review the requesting document prior to recording an approval decision. 1. From the approval dashboard, broadcast the details for the record group requiring approval. A new zone opens at the bottom of the screen with options to approve or reject the record. Approvers can record their decision for multiple requests by selecting the check boxes and clicking the appropriate button. Oracle Utilities Work and Asset Management User Guide 21

22 2. Click the link to open the Approval Request to further review the information. Here, you can also choose buttons in the Record Actions section to record your approval decision. 3. Click the link in the Requesting Document field to open the actual record in need of approval. Here you can review the complete document information, search for possible duplicates (for Work Requests), or edit the record if you have the proper authority within the system. Most approvers also have access to the Approval Request Action zone on the Dashboard. You can also record and submit your decision here. Access to this zone is controlled by your Portal Preferences in your user profile. Approving a Record in the Approval Dashboard Approvers can record their approval decision from the Approval Dashboard, on the Approval Request or on the record itself. Use this procedure to approve the record from the approval dashboard. 1. From the approval dashboard, broadcast the details for the record group requiring approval. A new zone opens at the bottom of the screen with options to approve or reject the record. 2. Click one of the decision buttons to record your approval or rejection of the record. You can also record your decision for multiple requests by selecting the check boxes and clicking the appropriate button. If you have authority on multiple To Do Roles, and you select multiple approval requests to approve at once, you may receive a warning that you need to specify an Acting To Do Role before selecting an action. This means you must pick a role from the Acting To Do Role drop down and click Search to let the system know which role you are using to approve the requests. You also have the option to click the link to the approval request to review it further. Most approvers also have access to the Approval Request Action zone on the Dashboard. You can also record and submit your decision here. Access to this zone is controlled by your Portal Preferences in your user profile. Approving a Record on the Approval Request Approvers can record their approval decision from the Approval Dashboard, on the Approval Request or on the record itself. Use this procedure to approve the record from the approval request. 1. From the approval dashboard, broadcast the details for the record group requiring approval. A new zone opens at the bottom of the screen with options to approve or reject the record. 2. Click the link to the approval request to further review the information. 3. Click one of the decision buttons to record your approval or rejection of the record. The approval decision is recorded and a notification is sent to the initiator of the request. You also have the option of navigating to the requesting document to review it further. Click the link next to the Requesting Document field on the approval request. Most approvers also have access to the Approval Request Action zone on the Dashboard. You can also record and submit your decision here. Access to this zone is controlled by your Portal Preferences in your user profile. Routing/Submitting a Record for Approval Use this procedure to submit a record for approval. Prerequisites: The record requiring approval must be created and in Created or Planning status. Oracle Utilities Work and Asset Management User Guide 22

23 1. Search for and select the appropriate record requiring approval. 2. Click the Submit for Approval button. 3. Enter or search and select the appropriate approval profile and Save. The system begins approval processing by sending alerts to the approvers and updating the status of the record to Pending Approval. You can check on the status of the approval in the Approval Dashboard. Reviewing Documents Requiring your Approval Decision Use this procedure to review approvals that require your attention. You can review the documents that require your review and approval decision using the Approval Dashboard, or, depending on your business practices and system settings, in your To Do List. Approval requests might also be sent directly to the address indicated in your user profile. Disable Notifications for an Approver Individual approvers can use this procedure to disable notifications for approval requests. Prerequisites: Your system approval processing must be configured so that you receive alerts for this procedure to be relevant. 1. Navigate to user Preferences under your username (at the top of the application window). You can also navigate to the User portal under the Admin menu if you have access. 2. Navigate to the Characteristics tab. 3. Add Approval Profile Override under Characteristic Type. 4. Add Disable under Characteristic Value and Save. You will no longer receive approval notifications for ANY approval requests in your . To enable alerts again, delete the characteristic. Oracle Utilities Work and Asset Management User Guide 23

24 Chapter 3 Assets The following sections provide information on concepts related to managing assets and components. Understanding Asset Management The Oracle Utilities Work and Asset Management system provides functionality to track the purchase, repair and maintenance of assets and asset components using general work management processing, preventive maintenance techniques, purchasing processing and inventory tracking. Assets and components are related in that a component is an asset that is installed on another asset. Service history is used to track and record the work that is done on assets and components. Specifications are used to define attributes needed to provide information about assets. Assessments can be configured to manage inspections and condition ratings for assets. The system tracks warranty information for assets. Measurement data for assets can be recorded and maintained to track asset reliability and performance. Work orders and activities track maintenance and repairs for assets, and can be set up on templates to establish regular schedules for preventive maintenance. This section describes how various processes work together to manage assets throughout the system. Please refer to the Working with Assets, Components, Service History and Asset Related Objects section for procedural tasks related to these concepts. Oracle Utilities Work and Asset Management User Guide 24

25 About Assets An asset is an object in an infrastructure, such as a smart meter, poles, pipes, transformer or any other material item owned or managed by an organization. Assets typically require tracking, inspection, service or work history. Your system may be configured with any number of asset fields depending upon your business requirements. The Asset Type defines whether or not costs are tracked for the asset. Types of Assets Assets are typically classified as: In/Out Service: In/Out of service assets are typically stationary, such as a pole or pipe. They stay in service until they fail and are then removed from service rather than being repaired or tracked. This type of asset will be recorded at an asset location with a disposition such as in service or out of service. Tracked: Tracked assets have their status and location carefully monitored and recorded as they move in and out of service or go for maintenance or repair. This type of asset will be tracked at a location with a disposition such as in receipt, in stores, in repair, retired or rejected. If the tracked asset is installed, or put in service, it will be related to an asset location. Tracked assets utilize more statuses and a status reason to more carefully track the asset as it moves from receipt to retirement. Within these classifications, several different types of assets can be managed for your organization. These include: Plant Assets: Stationary structures such as buildings, factories, or other facilities. Fleet Assets: Vehicles including cars, trucks, and equipment such as bulldozers or forklifts. IT Assets: Technology equipment such as phones, computers and laptops, monitors. OT Assets Operational technology assets such as smart meters and manual meters. Linear Assets: Assets that can be connected with each other such as pipes or telephone poles. Infrastructure Assets: Assets that makeup general infrastructure such as roads and parking lots. Beyond these general types, your organization might also manage: Communication Relays: Communication relays transmit messages between various points to facilitate communication between units. These typically use the same fields and statuses as meters. Communication Components: Communication components are devices that can be attached to an analog meter to connect the meter to the smart communication grid. These use the same fields and statuses as smart meters with the exception that they are never installed directly at a location, but are instead attached to another asset. Refer to the Asset Definitions section for more information and field definitions. Asset Hierarchy Assets typically exist within a structured relationship based on the relationship between the asset and its locations and organizations, or nodes. The hierarchy is represented in a nested format on the Tree View tab of asset locations, storage locations, organizations and assets. This view displays which assets are in a location, which assets are attached to other assets, and where assets belong within organizations. Clicking the broadcast icon next to any element within the tree displays a list of assets and components related to that element in the hierarchy. Clicking the actual link for an element navigates to the associated record for the element. Oracle Utilities Work and Asset Management User Guide 25

26 Asset Type Statistics Average costs for assets, grouped by asset type, are displayed graphically on the Asset Type record. Depending on your settings, this information is also available in the Home Page portal. Linear Assets An asset may be discrete, such as a building, a vehicle or an equipment item, or it may be linear, such as a sewer line, a road or a power line. Linear assets are defined in the system by designating an asset location where the linear assets are connected as well as by specifying connected to points to show the connections between linear assets. The Tree View of any asset or location in the system will show the other related assets with a visual indication of their relationships. Refer to the configuration guide for information on setting up linear assets. About Asset Types Asset types define the attributes for assets of a certain type. This includes determining information such as whether or not costs are tracked for assets of the type, the valid location types and service history types for the assets, and whether or not such assets can have attached components. Average cost statistics are displayed graphically on the Asset Type record. Refer to the Asset Type Definitions section for more information and field definitions. About Components Components are devices or other objects that are attached to another device, usually an asset. One of the most common examples of components are the electronic reading devices (ERTs) that are often attached to analog meters. However, a component can be any asset attached to another asset. Since they are always attached to another device, components cannot be installed at a location. However, they may be received, tracked, maintained and inspected like any other device. Given this, activities and work orders can be created to perform these tasks on components. Detaching components involves either moving the component to a new asset or transferring to a storage location. The process within the system is to search for and select the component and then "detach" it from the asset where it currently resides. Refer to the Component Definitions section for more information and field definitions. About Asset Locations Asset locations define the physical location where assets are installed. Valid asset locations might include service points, other locations for in service assets, or any other location as defined by your organization. For example, a service point is the address where a meter is located. This type of location typically contains just one active asset and no stored assets. Note that an asset location is the physical location where assets or components can be installed, whereas storage locations are for receipt, storage, repair, retirement, transport (on vehicles) and other dispositions. Asset locations can be defined in hierarchies with parent and child locations. For example, a campus might be defined with one parent location with the buildings on the campus defined as child locations to that parent. The parent can define attributes or identifiers common to all child locations, however specific location information must be defined on each location individually. Oracle Utilities Work and Asset Management User Guide 26

27 A child location cannot be in active status if the parent location is inactive. It is also not possible to make a location inactive if it has associated assets or child locations. Refer to the Asset Location Definitions section for more information and field definitions. Also refer to the About Storage Locations section for information about physical locations where assets or components are stored. About Asset Location Types Asset location types define the details of asset or component locations of a certain type. Valid asset locations might be service points, other locations for installed assets, or any other location as defined by your organization. Refer to the Asset Location Type Definitions section for more information and field definitions. About Bill of Materials A Bill of Material (BOM) is a parts list containing a hierarchy of component parts that make up a piece of equipment or asset. Your organization can build parts lists for assets, components and fleet assets (vehicles). Bills of materials are used to simplify identifying materials when planning work. A bill of materials can be a great advantage for maintenance personnel when they are planning or working on a work order. The bill of materials can be used to easily find the stock items related to component parts of the assets that need to be worked on. This relieves planners from doing extensive research to find the correct related stocked and non-stocked items needed. Bills of materials can be multilevel, with a list of components and lists of parts for the components, lists of parts that make up the parts, and so on. The level of detail you build into them depends on your organization's resources and needs. A Bill of Materials is similar to a Named Specification in that the same Bill of Material can be created as one source for specific criteria needed to maintain the asset, which is then referenced on many assets. Bills of materials are classified in the following ways: General Stock Item Part Defines a general piece of stock or equipment. A generic stock item BOM is automatically generated by the system when a stock item is created. Manufacturer Part Defines a general piece of stock or equipment with the manufacturer identified. A manufacturer part BOM is automatically generated by the system when a stock item is created with a Manufacturer/Model specified. Assembly Only Part Defines a piece of stock or equipment that requires assemblies. For parts requiring assemblies, your organization must update the BOM to specify which parts make up the stock item. A given stock item may have several different BOM assemblies that are unrelated to the manufacturer. For example, a sludge pump might have one assembly when a Johnson manufacturer motor is used, and a different assembly when a Mercury manufacturer motor is used. In this case the stock item would have Assembly Only BOM Part assemblies for which a parent part is needed. Independent Part Defines a generic part which is not a stock item, but can be composed of many parts. For example, a truck would be defined as an asset, not a stock item, but might reference a BOM with independent parts. These must be created manually. Refer to the Bill of Material Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 27

28 About Service History Use service history to enter relevant information regarding service or maintenance on assets. Typically it is used to record inspection feedback, pass/fail details, downtime, parts failure information, maintenance or service logs, or other information regarding service on the asset. Types of service history might include: Asset downtime Failure details Asset maintenance Visual inspection Detailed inspection Smart meter test Battery replacement... and so on. Service history can be manually created or is automatically generated as the result of completion events being processed for activities. If the service history type has any schedule defined, a set schedule may also be established to create regular service history for repeated tasks such as inspection or regular maintenance. Service history types linked to asset types control which service history can be created for assets. Refer to the Service History Definitions section for more information and field definitions. Inspections and Condition Assessments Assessment functionality is used to determine asset condition. Your organization defined inspection criteria to address typical inspection points, concerns, issues, or checklists that must be completed to properly assess an asset. This is based on the kind of asset, the kind of inspection, and so on. Assessments and inspections are conducted using service history which includes questions and answers. A field technician or other worker assesses the asset and enters answers to predefined questions on the service history record. Answers are typically chosen from a set of pre-defined values that are configured when the questions are designed for the assessment. About Condition Assessment and About Condition Assessment Classes are used to bundle the various kinds of inspections that are available for an asset. All of the data that is collected is used to calculate a final condition score. Condition scores are on a 1 5 scale where 1 is Very Good and 5 is Very Poor. Scores also have an associated confidence level which is a percentage which drops as the input data ages. This is based on the premise that the older the data, the less reliable it is. There are three kinds of inspections that can be performed: General Weighted(grading on a 1-5 scale): The condition of the asset is based on a general assessment of potential defects using a weighted scale of 1-5. Each potential defect is assigned a weight value based on the impact to the service level. A potential defect that has significant impact on the service level will have a higher weight value than a potential defect with minimal impact on the service level. A like new asset would exhibit none of the potential defects and be awarded the minimum points resulting in a rating of 1. A severely broken asset would exhibit the highest severity of each potential defect and would be awarded the maximum points resulting in a rating of 5. Deficiency (noting various defects on the asset, which can be summed): The condition of the asset is based on accumulated defect points. As with the general weighted method, each potential defect is assigned a weight value based on the impact to service level. Then each defect is broken down into specific severity levels with a point value assigned to each. The more severe the nature of the defect, the higher the associated point value. Normally, the point scale is a Oracle Utilities Work and Asset Management User Guide 28

29 range of 1-10, allowing for at least 10 different definitions or levels of severity. Unlike the general weighted method, each defect and severity identified during inspection is accumulated for the final deficiency score. That is, if there are 5 defects with a severity of 2 points each, then the deficiency score for the asset would be 10. A like new asset would exhibit none of the potential defects and be awarded a deficiency score of 0 (i.e., absolutely no defects were noted). A severely broken asset would exhibit the highest severity of each potential defect, probably numerous times, and would be awarded a higher deficiency score. Percent of New(maps a percent value to the 1-5 scale): The condition of the asset is based on passing or failing characteristics of a new asset. A like new asset would pass all characteristics and be awarded the maximum points resulting in a 100% rating. A severely broken asset would fail all characteristics of a new asset and be awarded zero points resulting in a 0% rating. You can recalculate a condition rating by navigating to the inspection type service history for an asset and clicking the Compute Score button. You may have to reopen the service history first. About Service History Types Service history types define the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement and so on. Refer to the Service History Type Definitions section for more information and field definitions. About Condition Assessment Questions Questions and related answers can be entered to define inspection templates which guide asset inspections. Questions are associated to service history types which are then associated to asset types. When it comes time to complete an inspection, the previously defined set of questions and answers guides the process for inspectors as the complete the inspection out in the field. Answers may be presented as a checkbox, multiple choice, or freeform text. Refer to the Condition Assessment Question Definitions section for more information and field definitions. About Condition Assessment Condition assessments are used with asset assessment/condition rating functionality. They group assessment service history types (i.e. inspection types) and to factor in asset aging factors to comprise a weighted combination of elements that affect how condition ratings are calculated. The aging factors that are defined for each condition assessment set up the parameters for calculating the confidence rating for inspections related to the assessment. Confidence rating is a percentage score attributed to an inspection. Note that the older the data, the lower the percentage because the less reliable the inspection data. The confidence rating is shown on the related asset record. Refer to the Condition Assessment Definitions section for more information and field definitions. About Condition Assessment Classes Assessment classes are sets of condition assessments, and are necessary for asset assessment/condition rating functionality. They are used to manage assets according to a set of inspection criteria and are used to define an inspection rating system for inspections. The purpose of this rating system is to measure the deterioration of the assets and the effect of the deterioration on the service levels that are expected of the asset. Inspections are performed to assess the asset's current physical condition via a scoring method that grades the asset based on severity and number of deficiencies found. The results of the inspection program are used to determine the residual life (i.e. Oracle Utilities Work and Asset Management User Guide 29

30 effective remaining life) of an asset and to support the review of preventative maintenance activities to ensure optimization of the asset's life. Please note the following with respect to assessment classes: Assessment classes are associated to assets on the asset type. Assessment classes are formed by a grouping of condition assessments. The total of all weights must equal 1. The Assessment Class Summary Information section displays a pie chart to represent the percentage of assets by score and a cluster chart to show the number of inspections, per type, per month (for the most recent months). Please refer to the Condition Assessment Class Definitions section for more information and field definitions. About Specifications A specification is contains the manufacturer, model, and other information about a set of assets. Specifications may also contain written procedures, careful handling instructions for hazardous or delicate materials, or any other set of attributes needed to provide information about a set of assets. Please note the following with regard to specifications: Specifications often include an attachment which supports the specification definition or provides the actual specification from the manufacturer. A specification may also include default in service and out of service maintenance schedules for assets or components linked to the specification. When the specification is associated with the asset or component, the related maintenance schedule becomes in effect for the asset or component. Please refer to the Specification Definitions section for more information and field definitions. About Firmware Firmware is software that is embedded in a piece of hardware. Devices such as smart meters, a network cards, or routers all have software that is programmed into special memory contained in the hardware itself. Manufacturers often release regular firmware updates to keep their hardware compatible with new connections, to improve performance, or to add additional features. After a firmware is released from the vendor, new firmware may need to be tested and validated then either approved or rejected for roll out. The system provides the needed functionality to support validating and updating firmware versions as needed. Associating Firmware and Firmware Versions to Assets In most business processes, firmware and firmware version is entered as part of the manufacturer settings when assets are created. This information appears in the Settings section on the asset. Also during asset creation, a basic business process would associate an asset specification to the asset to keep track of detailed manufacturer information which might also include the firmware. Attached, as a child to that specification, would be another specification that indicates the firmware versions that are available. As firmware versions change the child specification is updated with new versions. These versions can then be tested and accepted or rejected using the lifecycle functionality on the specification. Next, work orders and/or activities can be created to update the firmware version on the assets that are associated with those specifications. For example, your business process might require that you create an Asset Criteria Generator type work order to create a list of assets based on firmware as the selection attribute. The system would then apply the updates made via the work order to any assets that meet that criteria (i.e. that have that firmware type or version). Firmware Management You can use the system to manage firmware in the following ways: Oracle Utilities Work and Asset Management User Guide 30

31 Create firmware groupings: Record firmware versions into groupings or "families" on specifications so that related versions can be easily managed together. Add firmware to assets: Use peer specifications to associate assets to these firmware groups. Review firmware: Review firmware distribution and status in the Firmware Deployment and Firmware Version Dispositions zones on specifications. Document firmware: Manage related release notes or manufacturer information by creating attachments directly on the specification. Test firmware: Track testing and roll out of new firmware versions including the ability to approve or reject firmware version deployments. Update firmware: Create work orders and/or activities to update firmware versions on assets. Reject firmware versions: After testing, set the firmware version to an inactive status to indicate that the firmware version cannot be used for assets. The Configurations portal manages asset to component to firmware configurations that determine which versions are valid for which assets. Configuration Reports can be used to obtain details about the configurations and verify that the correct versions are in use. Firmware on Specifications The Firmware Deployment section on specifications provides statistics on the number of assets that are on each version of the firmware that is applicable to the specification. Click the pie chart for a version to see the number of assets on that versions grouped by the asset state. The Firmware Versions section lists the firmware that has been added via the specification. Use the Add Firmware Version link in the zone to add a new version. Click on one of the listed versions to open a screen with more details about the firmware. This screen can also be used to add attachments for the specific firmware version. For example, you might attach the release notes that were delivered with the firmware release. On this screen, the Firmware Version Dispositions section lists the assets that use the firmware version indicated, if any. Firmware Version Lifecycle Statuses for firmware version updates can be managed on the specification by selecting the actions in the Record Actions section. Valid statuses include: Active Statuses created under testing approved Intermittent Statuses deprecated quarantined Inactive Statuses rejected obsolete If the firmware version is in an intermittent status, assets or components can reference that version. In general, these statuses are for documentation purposes. for example, an organization might use the Deprecated status to indicate that they do not want to roll out new meters on that version any longer, however, existing meters that are on that version are still valid. No assets or components can have the version associated if the version is in one of the inactive statuses. Oracle Utilities Work and Asset Management User Guide 31

32 This functionality works in conjunction with the valid configurations that can be set up for the asset or component. If the firmware version is placed in an inactive status, yet it is referenced as part of a configuration, the configuration will become invalid. Refer to About Configurations for more information. About Operational Readings (Measurements) Measurements manage the asset operational and runtime data which is collected and tracked for assets. Asset measurements might include mileage, hours of uptime, number of start-stops, and so on. Since they almost entirely depend on the usage of the related asset, readings cannot be calculated or predicted accurately by the system. Instead, readings must be collected and entered into the system, either manually by a user or imported as the result of activity completion. Data readings that fall outside of expected limits or thresholds trigger alerts which go to the person responsible, who can then initiate the appropriate work to repair the measurement device or asset. Refer to the Operational Reading (Measurement) Definitions section for more information and field definitions. Operational Reading Activities The taking of measurements can be effectively managed by setting up the appropriate work orders or activities to track and schedule the work. This type of scheduling can be even more stringently managed using maintenance triggers and schedules. Asset records display any related measurement activities in the Measurements zone. Operational Reading Quick Entry Reading quick entry provides an easy way for users to enter asset readings. This tool can be used to enter multiple readings from a spreadsheet. Operational Reading Alert Review Reading alert review provides users with an easy dashboard to review alerts related to asset measurements. Generally an alert is triggered when an asset reading falls outside of an established threshold. Users can select the appropriate measurement type to see a list of measurements of that type that are in error. This list is sorted by the most recent errors first. The Asset portal displays a similar zone on relevant assets that have had measurements taken. This zone also includes an Add link where users can enter a measurement directly on the Asset record. Select appropriate assets (usually assets that have readings in error) and click the Make Valid button which automatically moves the status of the reading from an error to a valid state. Measurement Activity zone This zone displays a listing of activities related to a measurement. This provides visibility into maintenance planning activities that are triggered by measurement alerts. For example, your system configuration might trigger an alert if an out of range measurement is entered. This zone also includes an Evaluate button which, when clicked, moves the measurement to the next state where the measurement ranges will be evaluated, such as valid or error. About Measurement Types (Operational Readings) Measurement types define the units to use for a particular measurement and establish the values needed to support the evaluation of measurements such as upper and lower reading thresholds, maximum reading value, and so on. Asset measurements, or operational data, might include mileage, hours of uptime, number of start-stops, and so on. Only one measurement type can be created for each type of unit of measurement. Each asset is assigned a list of valid measurement types to regulate the types of measurements take for that asset. Oracle Utilities Work and Asset Management User Guide 32

33 Typically measurement types would be metered reads or gauge reads. Gauge reads are usually compared to a threshold or valid range of values. For example, tire pressure for a typical truck tire should be between 34 and 36 psi. These would be defined as the lower limit and upper limit for the measurement type. Refer to the Measurement Type (Operational Readings) Definitions section for more information and field definitions. About Measurement Unit of Measurement Measurement unit of measurements (UOM) establish the types of units that can be used to measure assets. Each UOM identifies a definite magnitude of a measurement reading taken for an asset. This might include tire pressure (psi), temperature ratings (degrees), and so on. Refer to the Measurement Unit of Measurement Definitions section for more information and field definitions. About Warranty A warranty is a written guarantee issued to your organization promising to repair or replace a damaged item within a specified period of time or usage limit. The Warranty portal manages the warranties held for assets or other purchased items for your organization. Refer to the Warranty Definitions section for more information and field definitions. About Warranty Terms Warranty terms hold the duration, term, value or usage limit of assets or items that are under warranty. The warranty term also specifies the specification and/or vendor that a warranty claim can be issued to when needed. Warranty terms can be defined as calendar warranties (such as number of years) or runtime warranty terms (such as number of miles). When a warranty term is created and set to Active status, it can be associated with assets. Once warranties have been created referencing the term, the Warranty section displays a list of the applicable warranties. Refer to the Warranty Term Definitions section for more information and field definitions. About Material Disposition Material disposition is a process designed to track repairable assets/stock items. The process tracks the asset or component from when it is removed from service to where it is either retired, scrapped or repaired and returned to availability for reuse. The portal is accessed under the Work Management menu. Material disposition processing involves creating a work order to remove then replace a broken asset or component. The asset must be flagged as repairable. In creating the work order and related activities, the resource requirements must indicate that a replacement asset must be checked out from a storeroom to replace the broken one. In order to fulfill these requirements, users must create a material request and material issue for the asset. A Material Disposition record is created as a result of these material requirements being fulfilled, and the replacement asset and the broken asset are added on the material disposition as line items. Note that new records are not created directly in the Material Disposition portal. They must be generated automatically by this processing. The person responsible for material disposition should navigate to the Material Disposition portal to complete the steps within the system to remove the broken asset and move it to a pending disposition status while moving the replacement asset to an installed status. This is done using the Complete Exchange option. When completing the complete exchange process, the system prompts for information such as the actions to perform on the assets, status reason, new storage location as applicable, and dispositioning dates and times. Oracle Utilities Work and Asset Management User Guide 33

34 The actual assets should also be swapped as applicable toward completing the initial work order and activity. Your business process may then require that you create a follow up work order to repair the broken asset using the Create Work Order action from within the Material Disposition portal. You can review the costs and other statistics related to the replacement and repair of assets by reviewing the actual Asset record in the Cost Information section. Refer to the Material Disposition Definitions section for more information and field definitions. About Mass Asset Disposition Update The Mass Asset Disposition Update portal allows you to select assets by asset type, current disposition state or other common criteria to change the status and location of multiple assets at one time. Asset disposition indicates where the asset is and what is being done to the asset. Mass Asset Disposition is aimed at moving many assets of the same type from one storage location to another storage location. In a mass disposition task, the target is always a single location. For example, if a pallet of meters has been received in the receiving storeroom, mass disposition can be used to move this batch of assets to a storage location. Once the appropriate assets are retrieved and selected, click the Change Disposition button to execute the change in one quick step. Refer to the Asset Definitions section for more information and field definitions. About Replication As devices and other assets are received in large quantities, the Asset Replication portal allows for the receipt, inspection, storage and other processing of these assets in batches. This is only available with Oracle Utilities Operational Device Management. Using asset replication functionality your organization can complete processes such as: Replicating assets in the same lot/pallet Selecting assets for testing or inspection Mass updating asset disposition such as rejecting or accepting a lot or pallet This processing creates new asset IDs, badge numbers and serial numbers for assets based on general information that is entered related to each batch. When a new replication event is created it is tied to a replication activity type to determine default settings and attributes for the replication. The actual asset information can be entered manually or uploaded via a CSV file. Assets can then be moved between locations, or dispositioned using Mass Asset Disposition Update. About Asset Configurations A single asset or component can have many parameters and only certain combinations of parameter values that are allowed. Multiple assets and/or components may work together as a group with only certain combinations of settings that are allowed or supported. Configurations document and manage the valid set ups for assets/and components. This includes a specification for each asset or component in the configuration as well as the valid value for each parameter, such as the firmware version of each asset. Configuration reports can be generated to provide a summary of any currently installed configurations. These reports show whether the configuration in an installation is valid or invalid, they show the identifiers and values being used, and they display all of the assets/components and other elements that make up the installed configuration. Oracle Utilities Work and Asset Management User Guide 34

35 If a configuration is found to be invalid or in need of reconfiguration, work orders can be created based on configuration criteria. Configuration functionality can also be tied in with specifications to manage firmware version testing and upgrades. Configuration Statuses Configurations also allow you to indicate a status for a particular status. Applicable statuses include: Pending Under Testing Rejected Approved Deprecated Obsolete Use actions in the Record Actions section to transition the configuration to the appropriate status. Refer to the Asset Configuration Definitions section for more information and field definitions. About Asset and Component Configuration Types Configuration types define the information required for various asset configurations with other assets, components, firmware, and other aspects of a functioning configured system. Configurations are referenced on specifications which are then referenced on assets and components to indicate the best way that these entities can work with the other entities that they are connected to in the field. In general configuration classes define the types of connections that are being configured. The generic classes that are available include: Single Asset Asset/Component Asset to Asset Asset/Component to Asset Asset to Asset/Component Asset/Component to Asset/Component Refer to the Asset Configuration Type Definitions section for more information and field definitions. About Asset and Component Configuration Reports Configuration reports provide a summary of any currently installed configurations. These reports show whether the configuration in an installation is valid or invalid, they show the identifiers and values being used, and they display all of the assets/components and other elements that make up the installed configuration. Batch processing and the setting of the Reporting Mode field on a report determines when a configuration report is generated after it is submitted. If a report is set to generate one time, the report status is set to Pending after it is generated and it will not be updated again until a user manually submits the report. If the report is set to recur, the report is updated every time batch processing runs. If the configuration is invalid, the configuration column is blank in the report results. Navigate to the configuration itself to review the set up. A button next to each configuration also allows you to generate a work order to correct, reconfigure, or otherwise maintain any of the configurations. Refer to the Configuration Report Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 35

36 About Shapes Use the Shape portal to define circles or lines used to draw linear assets. For example, a manhole would be represented as a circle, whereas a pipe would be represented as a line. Shapes can specify an outline color, fill color, width, and a radius (for circles). A zone on the asset location graphically displays the relationships between linear assets. Refer to the Shape Definitions section for more information and field definitions. Working with Asset Administration The following sections provide information on tasks associated with creating and maintaining the administrative records needed for asset related functionality. Defining Measurement Unit of Measurement (UOM) Navigate to the Unit of Measure Measurements portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Measurement Unit of Measurement Definitions section for more information and field definitions. Defining a Measurement Type (Operational Reading) Navigate to the Measurement Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the measurement type record: Note: This list does not represent required fields. Measurement Unit of Measure Refer to the Measurement Type (Operational Readings) Definitions section for more information and field definitions. Defining Condition Assessment Questions Navigate to the Condition Assessment Question portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Condition Assessment Question Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 36

37 Defining Service History Types Navigate to the Service History Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the service history type record: Note: This list does not represent required fields. Questions Refer to the Service History Type Definitions section for more information and field definitions. Defining a Condition Assessment Navigate to the Condition Assessment portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the condition assessment record: Note: This list does not represent required fields. Service History Type Service history type defines the questions and answers used when completing an inspection. Set up the condition assessment to define which service history types are valid for the condition assessment. This will then be referenced on the condition assessment class to provide the comprehensive criteria for an inspection. Refer to the Condition Assessment Definitions section for more information and field definitions. Defining a Condition Assessment Class Navigate to the Condition Assessment Class portal under Admin, select Add mode, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the assessment class record: Note: This list does not represent required fields. Condition Assessment A condition assessment class may consist of one or many condition assessments which define the comprehensive criteria for a type of inspection. Refer to the Condition Assessment Class Definitions section for more information and field definitions. Defining Asset Location Types Navigate to the Asset Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the asset location type record: Note: This list does not necessarily represent required fields. Parent Location or Organization Type (as applicable) Refer to the Asset Location Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 37

38 Defining Asset Types Navigate to the Asset Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the asset type record: Note: This list does not represent required fields. Assessment Class Asset Location Type Service History Type Failure Profile Refer to the Asset Type Definitions section for more information and field definitions. Defining Component Types Use this procedure to define component types. Prerequisites: The following are referenced by the asset type record: Note: This list does not represent required fields. Assessment Class Asset Location Type Storage Location Service History Type 1. Navigate to the Asset Type portal under the Admin menu and select Add. 2. Complete the required fields according to your business practices and Save Valid Location Types where the component can be received, stored, installed, repaired, and so on. Valid Attached to Asset Types to indicate the asset types where the component can be attached/installed. Valid Service History Types which define the types of service that can be performed on components of this type. You can now create components based on the component type. Refer to the Component Type Definitions section for more information and field definitions. Defining a Shape Navigate to the Shape portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The actual shapes must be preconfigured in the Managed Content portal. If you need to specify a fill color or outline color, these must already be defined by the Color portal. Refer to the Shape Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 38

39 Defining Asset Configuration Types Navigate to the Configuration Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Asset Configuration Type Definitions section for more information and field definitions. Working with Assets, Components, Service History and Asset Related Objects The following sections provide information on tasks associated to working with assets and asset related objects. Refer to the Understanding Asset Management section for a conceptual overview of this functional area or to the Asset Management Object s sections for more information and field definitions. Working with Assets The following sections provide information on tasks associated with creating and updating assets. Creating an Asset Location Navigate to the Asset Location portal under Asset Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the asset location record: Note: This list does not represent required fields. Asset Location Type Parent Location/Organization (as applicable) Enter a parent location or organization to establish the position of your new location in the location hierarchy. Work Request Approval Profile (as applicable) Contact (as applicable) Service Area (as applicable) Cost Center RCM System Backlog Group Make sure that the Location Disposition is set to Active if you want to make the location available for reference on other records. Additional information typically includes an address and additional info to define the location. The criticality section captures information which defines the importance of the location in terms of the potential impact of having issues or problems at that location. For example, a hospital might have a high criticality rating since losing power there might result in deaths of patients. A city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Oracle Utilities Work and Asset Management User Guide 39

40 Refer to the Asset Location Definitions section for more information and field definitions. Creating an Asset Manually Use this procedure to manually create a single asset in the system. Prerequisites: The following are referenced by the asset record: Note: This list does not represent required fields. Asset Type (with referenced in receipt storage location) Storage Location Specification Vendor (as applicable) Measurement Type (as applicable) Employee Maintenance Manager Planner Cost Center Service Area Defining an asset involves selecting an asset type then defining asset attributes. While this procedure describes the creation of a single asset, it is also possible to create multiple assets at one time in Oracle Utilities Operational Device Management using asset replication.. Please refer to the Asset Definitions section for more information and field definitions. Entering Service History Manually Use this procedure to create service history for an asset or component. Service history might also be created automatically as the result of a completion event for an activity. 1. Navigate to the Service History portal under Asset Management and select Add. 2. Enter the ID for the asset that you are creating service history for and select a service history type. This list is limited by the service history types that are valid for the asset ID. Service history type determines the basic attributes that should be included on the service history such as category, whether the service is for inspection or maintenance, or any other criteria. It also sets a service schedule, if applicable. 3. Click OK. 4. Enter the effective date and time for the service history. This value can be set in the past if you are recording a service that occurred prior to the current date. 5. Enter the ID for the associated activity, if applicable. 6. Enter any comments, as applicable. 7. Enter any downtime details, as applicable. 8. Click Save. Refer to the Service History Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 40

41 Performing Asset Maintenance Performing asset maintenance involves creating a work order and/or activity for the maintenance the needs to be performed and seeing the work order processing through to completion. Performing an Asset Inspection Performing an asset inspection involves creating an inspection type service history against the asset and answering the questions for the inspection according to how they are configured for your organization. In some cases, the inspection process might be managed by work order processing which may be set up in a preventive maintenance or RCM system. When the inspection is completed, the answers are used to compute the total inspection points. The calculation is generally sum (answer points * question weight), but varies depending if the service history type. The total inspection points are then normalized to an overall grade or score. The condition rating and confidence rating are also calculated and the asset is updated with the appropriate values. Scheduling an Asset Inspection Scheduling an asset inspection involves creating an activity configured with an inspection service history type. The activity can then be scheduled via regular scheduled activity processing. When the inspection is completed, the answers are used to compute the total inspection points. The calculation is generally sum (answer points * question weight), but varies depending if the service history type. The total inspection points are then normalized to an overall grade or score. The condition rating and confidence rating are also calculated and the asset is updated with the appropriate values. Reviewing Asset Statistics Review asset statistics by navigating to the Asset portal and viewing the statistics section. Information is organized into logical groupings, such as Cost Information by Service Class. Reviewing Asset Type Statistics Review cost information by asset type by navigating to the Asset Type portal and reviewing the Statistics section. Information is organized into logical groupings, such as cost information or count of assets and activities, by asset type. Rejecting Assets Use this procedure to reject assets. You can only reject tracked assets that are in one of the following states: In Receipt, or In Repair. 1. Navigate to the Asset portal in Search mode. 2. Search for and select the appropriate asset. 3. Click the Reject button. The asset is archived in Rejected status and cannot be dispositioned any further. Oracle Utilities Work and Asset Management User Guide 41

42 Retiring Assets Use this procedure to retire assets. You can only retire tracked assets that are in one of the following states: In Store, or In Repair. 1. Navigate to the Asset portal in Search mode. 2. Search for and select the appropriate asset. 3. Click the Retire button. The system updates the status of the asset as retired. Updating the Disposition of a Single Asset Use this procedure to update the status and location of an asset. 1. Navigate to the Asset portal in Search mode. 2. Search for and select the appropriate asset in display mode 3. Click Change Location in the Record Actions section. To take the asset out of service, click the Out of Service button. 4. Update the effective date and time and enter the new location for the asset. The available locations depend upon the asset type and the current disposition of the asset. 5. Click Save. Note the change in the information in the Asset Disposition Details section. The new disposition status and location are indicated. Update the Disposition of a Group of Assets Use this procedure to change the status and location for a batch of assets. 1. Navigate to the Mass Asset Disposition Update portal in Search mode. 2. Search for assets according to the appropriate criteria. Options include selecting all assets that are in a certain state, all assets of a certain condition or assets by physical location. You can also select from characteristics or other identifiers. You can create combinations of criteria such as all assets of a certain type and that are in a particular status. 3. Select individual assets or check the box at the top of the column to select all assets. 4. Click Change Disposition to begin the disposition change. A pop-up window opens where you select the effective date and the new status and location for the assets. 5. Enter the date that the status and location change should occur. This defaults to the current date and time, however, you can set this to past date depending on how the assets need to be handled. 6. Enter the appropriate location where the assets will go when they are dispositioned. 7. Click OK. Oracle Utilities Work and Asset Management User Guide 42

43 The assets are moved to the new status and location, and the disposition log on the individual asset records is updated with the change. Working with Components The following sections provide information on tasks associated with creating and updating components. Creating Components Manually Use this procedure to manually create a component. Prerequisites: The following are referenced by the component record: Note: This list does not represent required fields. Asset Type Select an asset type that defines a component. Storage Location Specification Vendor (as applicable) Measurement Type (as applicable) Defining a component involves selecting a component type asset type and then indicating the asset where the component is attached. 1. Navigate to the Asset portal under Asset Management and select Add. 2. Complete the required fields according to your business practices and Save. Next you can attach the component to an asset. Please refer to the Component Definitions section for more information and field definitions. Storing a Component after Receipt Use this procedure to change the disposition of a component after it has been received (entered into the system). This step usually needs to be completed before a tracked component can be installed on an asset. 1. Navigate to the Asset portal in Search mode. 2. Search for and select the appropriate component. 3. Click Store in the Record Actions section. A window opens where you select the effective date and the storage location for the component. For in/out service components you choose an asset location. For tracked components, you choose a storage location. 4. Click Save. The Asset Disposition Detail section and the Disposition History zone are updated with the status and location for the component. Attaching a Component to an Asset Use this procedure to attach an existing component to an asset. 1. Navigate to the Asset portal in Search mode. Oracle Utilities Work and Asset Management User Guide 43

44 2. Search for and select the appropriate component. 3. Click Attach in the Record Actions section. The option to attach the component is generally not available unless the component is in the necessary interim disposition. If the current disposition is in receipt, you must first store the component in a valid location where it can be attached to an asset. A window opens where you select the effective date and the Asset ID where the component is to be attached. 4. Click Save. The Asset Disposition Detail section and the Disposition History zone are updated with the status and location for the component. Detaching a Component from an Asset Use this procedure to detach a component from an asset. 1. Navigate to the Asset portal in Search mode. 2. Search for and select the appropriate component. 3. Click Change Location in the Record Actions section. A window opens where you select the effective date and the location where the component is to be stored when it is removed from the asset. For in/out service components you choose an asset location. For tracked components, you choose a storage location. 4. Click Save. The Asset Disposition Detail section and the Disposition History zone are updated with the status and location for the component. Creating a BOM Part Whenever you create a general stock item, a corresponding BOM part is automatically created. If a stock item is created referencing a manufacturer, a manufacturer BOM is automatically created. Navigate to the BOM Part portal under Asset Management to search for BOM items. Refer to the Bill of Material Definitions section for more information and field definitions. Working with Vehicles The following sections provide information on tasks associated to working with vehicles. Entering a Vehicle as an Asset Use this procedure to create a vehicle record within the system. Vehicles are considered fleet assets in Oracle Utilities Work and Asset Management. They are considered storage locations on Oracle Utilities Operational Device Management. Prerequisites: The following are referenced by the fleet asset record: Note: This list does not represent required fields. Asset Type (with referenced in receipt storage location) Asset Location Specification Oracle Utilities Work and Asset Management User Guide 44

45 BOM ID (as applicable) Vendor (as applicable) Measurement Type (as applicable) Employee ID (responsible party) Badge Number Serial Number Vehicle Identification Number License Number Defining an vehicle involves selecting an asset type then defining attributes of a vehicle. While this procedure describes the creation of a single fleet asset, it is also possible to create multiple assets at one time in Oracle Utilities Operational Device Management using asset replication. Please refer to the Asset Definitions section for more information and field definitions. Entering a Vehicle as a Storage Location Use this procedure to create a vehicle record within the system. Vehicles are mainly considered storage locations in Oracle Utilities Operational Device Management, and can be considered as both fleet assets and storage locations in Oracle Utilities Work and Asset Management. Please refer to the configuration guide for information on how vehicles should be set up. Prerequisites: The following are referenced by the vehicle record: Note: This list does not represent required fields. Storage Location Type Organization (as applicable) Contacts (as applicable) Make sure that the Location Disposition is set to Active if you want to make the vehicle available for reference on other records. Refer to the Storage Location Definitions section for more information and field definitions. Working with Specifications The following sections provide information on tasks associated to working with specifications. Defining Specifications Navigate to the Specification portal under Asset Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the asset location record: Note: This list does not represent required fields. Asset Type Manufacturer BOM ID Maintenance Schedule Oracle Utilities Work and Asset Management User Guide 45

46 Refer to the Specification Definitions section for more information and field definitions. Adding or Updating Firmware Versions Use this procedure to add new firmware versions or update existing firmware versions in the system. These can then be tested, approved or added to work records to be updated on assets. A specification for the firmware must exist within the system 1. Navigate to the Specification portal in Edit mode. 2. Search for and select the appropriate specification. 3. Click the Add Firmware Version link in the Firmware Versions section. 4. Confirm the firmware listed then enter the version, date, release note if any, and any other information as required by your business practices. 5. Click Save. Refer to the Specification Definitions section for more information and field definitions. Working with Operational Readings (Measurements) The following sections provide information on tasks associated to working with measurements including measurement types, measurement alerts and measurement quick entry. Entering Operational Readings (Measurements) Navigate to the Operational Reading portal under Asset Management, select Add, complete the required fields according to your business practices and Save. Use the Operational Reading Quick Entry portal to enter multiple readings from a spreadsheet. Prerequisites: The following are referenced by the measurement: Note: This list does not represent required fields. Measurement Type Asset ID Refer to the Operational Reading (Measurement) Definitions section for more information and field definitions. Using Operational Reading (Measurement) Quick Entry Use this procedure to enter a measurement using the Operational Reading Quick Entry tool. Prerequisites: The following are referenced by the measurement: Note: This list does not represent required fields. Measurement Quick Entry Activity Type Work Order ID Asset ID Badge Number Measurement UOM Oracle Utilities Work and Asset Management User Guide 46

47 This process is generally used when a measurement work order is already created and the measurement is being entered as the follow-up measurement activity. 1. Navigate to the Operational Reading Quick Entry portal 2. Select the Measurement Quick Entry Activity Type. 3. Enter or search for and select the appropriate Work Order ID. 4. Enter the measurement in the provided fields and Save. Measurements can also be uploaded using a prepared CSV file with the following columns: Sequence Asset ID Badge Reading Date Time Measurement UOM Current Value Selecting Download To CSV File opens a blank spreadsheet with the appropriate columns. Importing Operational Data from a File Use this procedure to import measurements from a spreadsheet. 1. Navigate to the Operational Reading Quick Entry portal under Asset Management. 2. Select the Measurement Quick Entry Activity Type. 3. Enter or search for and select the appropriate Work Order ID. 4. Click the CSV File To Upload link. Measurements can be uploaded using a prepared CSV file with the following columns: Sequence Asset ID Badge Reading Date Time Measurement UOM Current Value Selecting Download To CSV File opens a blank spreadsheet with the appropriate columns. Working with Warranties and Warranty Terms The following sections provide information on tasks associated to working with warranties and warranty terms. Defining a Warranty Term Navigate to the Warranty Term portal under Asset Management, select Add, complete the required fields according to your business practices and Save. Terms are entered in the Warranty Term portal under Asset Management. Oracle Utilities Work and Asset Management User Guide 47

48 Prerequisites: The following are referenced by the warranty term: Note: This list does not represent required fields. Specification (as applicable) Vendor Warranty terms are defined as calendar based (such as a number of months or years) or runtime based (such as number of miles). Refer to the Warranty Term Definitions section for more information and field definitions. Entering a Warranty Navigate to the Warranty portal under Asset Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the warranty: Note: This list does not represent required fields. Warranty Term Asset ID If creating a runtime warranty, you will need to provide the initial measurement for the asset. For example, if the runtime is a certain number of miles for a vehicle, you would enter a starting odometer reading. This reading must be validated against an actual asset reading that has been entered into the Measurement portal for the asset. A warranty can also be created from the warranty term that it references or from the asset that the warranty affects. Refer to the Warranty Definitions section for more information and field definitions. Entering a Warranty from an Asset Use this process to enter a warranty directly on the Asset record. 1. Navigate to the appropriate Asset record in Edit mode. 2. Click the Add link in the Asset Warranty zone. 3. Complete the required fields according to your business requirements and Save. Working with Asset Configurations and Configuration Reports The following sections provide information on tasks associated to working with configurations and configuration reports. Creating an Asset Configuration Use this procedure to create a configuration. 1. Navigate to the Asset Configuration portal under Configuration Report and select Add. 2. Select a configuration type and click Ok. The configuration type sets the default fields that need to be filled in. 3. Fill in required information as needed and click Save. Oracle Utilities Work and Asset Management User Guide 48

49 Enter a useful description for the configuration then use the Configuration Detail section to indicate the specifics of the configuration. This will include information on assets and components along with their characteristics and identifiers as defined by your organization. The specification that is chosen for the asset and/or component will determine the main firmware and other information for the configuration. Add any related attachments in the Configuration Common Attachments section. Refer to the Asset Configuration Definitions section for more information and field definitions. Creating an Asset Configuration Report Use this procedure to create a configuration report. 1. Navigate to the Configuration Report portal under Configuration Report and select Add. 2. Select a configuration report type and click Ok. The configuration report type sets the default fields that need to be filled in. 3. Fill in required information as needed and click Save. Enter a useful description for the configuration report and select a Reporting Mode. The reporting mode determines whether this is a recurring report, or a one time report. Use the Report Criteria section to indicate the specifics of the assets, components, identifiers and characteristics that should determine filtering for the report. 4. After the report is created, click the Submit button to finalize the report. In most business practices you will wait for batch processing to run to generate the report. The report record includes a Generate Report action, however; it is recommended that this is not used for typical processing. Refer to the Configuration Report Definitions section for more information and field definitions. Creating Work to Correct or Maintain Asset Configurations Use this procedure to create a work order from a configuration report. 1. Generate a configuration report. 2. In the Report Results section, click the Create Work Order button next to the configuration that needs attention. The system creates a work order with applicable information filled in. Finish creating and processing the work order according to your usual business practices. Oracle Utilities Work and Asset Management User Guide 49

50 Chapter 4 Inventory The following sections provide information on concepts related to managing inventory. Understanding Inventory Inventory is tracked, ordered, and received from vendors and allocated in the Inventory system. As inventory is allocated to work, the system passes this information back to the Work Management system so that maintenance managers and crews know that their parts are available. As inventory falls and reorder becomes necessary, the Inventory system passes this information to the Purchasing system so that purchases of new inventory can be carried out. Using reorder review, the system can be configured to automatically reorder stock items or notify a specified user when the quantities reach predetermined reorder points. Each time inventory quantity is changed, the system generates a transaction record, and you have access to this information through related logs and historical information zones. Managing inventory means balancing the need to order new items against the available supply, maintaining an optimum inventory stock level, and stocking and ordering items for upcoming work and safety requirements. This section describes how various processes work together to manage inventory throughout the system. Please refer to the Working with Inventory section for procedural tasks related to these concepts. About Storage Locations Storage locations define the physical location where assets or components are stored. Quantities are not tracked for storage locations. Valid storage locations might be storerooms, warehouses, receiving docks, retirement locations, real estate, vehicles, or any other location as defined by your organization. Note that storage locations are for receipt, storage, repair, retirement, transport (on vehicles) and other dispositioning, whereas asset locations are the physical location where assets or components can be installed. Example storage locations include: Oracle Utilities Work and Asset Management User Guide 50

51 A storeroom or repair shop is a location where assets are physically stored. This type of location can be composed of a simple description ( Central Storage or Repair ) but might also have address information. A real estate location is typically an address or a building name. Vehicles or "fleet assets" may be considered as storage locations within the system. If the asset is in transit and on a vehicle it is considered stored on that vehicle. A truck that contains assets in storage will have a location with a single active asset and many stored assets. Refer to the Storage Location Definitions section for more information and field definitions. Storage locations can be defined in hierarchies with parent and child locations. The parent can define attributes or identifiers common to all child locations, however specific location information must be defined on each location individually. A child location cannot be in active status if the parent location is inactive. It is also not possible to make a location inactive if it has associated assets or child locations. Also refer to the About Asset Locations section for information about physical locations where assets are installed. About Storage Location Types Storage location types define the details of storage locations of a certain type. Valid locations might be storerooms, warehouses, receiving docks, or any other location as defined by your organization. Refer to the Storage Location Type Definitions section for more information and field definitions. About Stock Items Stock items are defined as material resources that are held in storerooms and issued to activities that require the materials to be completed. The stock item record determines whether or not the type of stock can be purchased, repaired, tracked, and so on. The stock item record can also provide a list of vendors and manufacturers who provide the item as well as appropriate alternative stock, as applicable. Only stock items in active status can be purchased or entered as a material requirement on an activity. When they are entered in the system, stock items are categorized in some of the following ways: General: General stock items are created with the trackable and lot managed flags set to false on the stock item record. Trackable: Trackable stock items merit being individually identified and followed from initial receipt on-site through complete usage. These are typically large, expensive or specialized assets or materials which are inspected when they are received into inventory, repaired if they break, can be installed on other assets, and are otherwise carefully dispositioned in the system. These types of items are controlled by the following rules: created with the trackable flag set to true and the lot managed flag set to false on the stock item record can be repairable cannot be expensed at receipt cannot be designated as direct purchase items when configured for reorder review, trackable items have a safety stock flag Lot Managed: Lot managed items are also tracked in a special way in the system. These types of items are fabricated, sold, and delivered in lots or batches of the item. This is significant when there are qualities or details about the item that might vary between lots. If this item is lot managed, the system tracks a lot number with any transaction that changes the quantity of the item for the storeroom. Since each received lot also has its inventory tracked independently, lot managed item details all have child" stock item details for each lot that is received. This means a master stock item detail that is classified as "lot managed" on its stock item detail with many lot" stock item details (one for every lot that is received). When an activity references lot managed items as a resource requirement, the master stock item detail is Oracle Utilities Work and Asset Management User Guide 51

52 referenced. Lots only become relevant when material is issued from or received into inventory. This means the material issue for lot managed stock items reference a lot stock item detail, but the planned activity references the master stock item detail. These types of items are controlled by the following rules: created with the trackable flag set to false and the lot managed flag set to true on the stock item record cannot be expensed at receipt cannot be designated as direct purchase items When a stock item is maintained in the inventory of a storeroom, a corresponding Stock Item Detail record must be created. Stock item details define how the stock item is managed in the storeroom and contain storeroom-specific information for the stock item such as pricing, reorder information, unit of issue, unit of purchase, expense code, and so on. One stock item might be stored in multiple storerooms. When it is needed, stock transfers can be used to move items between storerooms. For example, an organization might have a central storeroom from which satellite storerooms request stock. Please refer to the Resource Type Definitions section for more information and field definitions. About Stock Item Details Stock Item Detail records define how a stock item is managed in the storeroom and manage and track quantities for stock items. Each record contains storeroom-specific information for the stock item such as pricing, reorder information, unit of issue, unit of purchase, expense code, and so on. Every stock item that is to be maintained in the inventory of a storeroom must have a corresponding Stock Item Details record. The Stock Item Inventory section provides a graphical representation of what is in stock with lines representing maximum quantity and reorder quantity. Use the filters to change the display on the chart. This chart can be changed to show projected inventory (taking into account pending purchases and pending activities), or historical inventory (showing actual inventory use and receipts). Refer to the Stock Item Detail Definitions section for more information and field definitions. About Commodity Codes Commodity Codes are an alternate way to describe stock items which can be helpful when you need to locate a specific stock code because they form a logical segmented code for a stock item. Codes are segmented by commodity category, name, type, and composition. The Stock Item portal can be searched by commodity code where you can filter by a variety of criteria. Commodity codes cannot be created directly. Instead they are constructed as a combination of the following: Commodity Category Commodity Category is the most general description of the item. A sample category code might be M for a piece of mechanical equipment. Commodity Name For each category, there is a unique list of Commodity Names. A sample commodity name for mechanical equipment might be a Check Valve. Commodity Type For each category and name combination, there is a unique list of Commodity Types. A sample commodity type for a check valve might be a high-pressure pneumatic check valve. Commodity Composition For each category/name/type combination, there is a unique list of Commodity Compositions. The composition code is used to indicate the primary material in the item (e.g. titanium alloy). These attributes must be created in sequence within the commodity code hierarchy itself. Please refer to the Commodity Code Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 52

53 About Material Request and Issue Material requests, or checkout requests, manage the process of specifying the need to issue stock items from a storeroom. When an activity needs stock items, a material request can be created. The request includes a list of all the items that the activity needs from the storeroom with the stock code, the storeroom and the needed quantity specified. By simply processing the request, the inventory count is not affected. The following processing must be completed: Create the material request Add line items for the stock items to be issued Line items can be added manually or from a material request template. Prepare the material request for issue Issue the materials Materials may be issued fully or partially Refer to the Material Request Line Definitions section for more information and field definitions. About Material Issue Material issue, or stock checkout, manages the process of pulling out and releasing stock items from a storeroom. Material issue processing occurs as follows: The person from the issuing storeroom can verify availability within the system then release (issue) the items. The material issue is processed via the originating Material Request record. The system calculates the inventory count to decrease it accordingly. Issued items are to be charged to the activity. It is also possible to issue materials without relationship to an activity. In this case, the user must provide the accounting information that will be charged for the materials. Refer to the Material Issue Line Definitions section for more information and field definitions. About Material Request Templates A material template is a collection of stock items that is used to easily populate a material request. For example, a template could exist for office supplies that contains the collection of office supply stock items that the user can add to the request. Likewise, you might have a template to request all of the items on a bill of materials. Each storeroom can have multiple templates. The stock items referenced in the template must exist at the storeroom. Only stock items in inventory (both Lot Managed and Not-Lot Managed) and tracked assets can be specified on a template. The stock items must have a stock item detail at the storeroom. Direct purchase stock items cannot be referenced on a material request template. If populated, an override expense code is populated on the request / return line. If this value is blank, the expense code defined on the stock item detail (or stock item) will be populated on the line instead. A default count can be included on the template to indicate the default request quantity of the stock item. For example, your organization might always request the same amount of the stock item. This can be specified on the template. After a material request is created, the line items can be added by referencing the template then selecting items from a picklist. Refer to the Material Request Template Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 53

54 About Material Returns Material returns manage the process of returning to the storeroom excess stock items that were previously issued. Material return processing occurs as follows: A material return is created by navigating to the related material request and clicking the Return button for the relevant line item. This can also be done by creating a new record in the Material Return portal which references the originating material request Warehouse personnel checks the quality of the stock item being returned. If it is in good condition, the item is accepted and returned to the storeroom. The system calculates the inventory count to increase it accordingly. Returned items are credited back to an account or work order activity. Refer to the Material Return Header Definitions section or the Material Return Line Definitions section for more information and field definitions. About Physical Inventory Physical inventory is an auditing procedure within Inventory Management which your organization can use to ensure that the physical quantities of items, materials and stock that are housed in your storage locations are actually stocked per what is recorded within the system. This basically allows your organization to verify the accuracy of your inventory quantities and values. If actual counts are found to be out of sync with system inventory counts, they can be reconciled based on pre-defined tolerance thresholds. Refer to the Physical Inventory Definitions section for more information and field definitions. About Inventory Adjustments Inventory adjustments can be used to adjust inventory counts or price of stock items. When inventory is adjusted, stock transactions are created to adjust the price and quantity of the items being adjusted. Trackable assets are adjusted different in that the unit price is directly adjusted and financial transactions are created if the total inventory value is changed (based on the relative price/quantity adjustment). Refer to the Inventory Adjustment Definitions section for more information and field definitions. About Stock Transfers Stock transfers are used to move stock from one storeroom to another; essentially one store room is ordering stock from another. The ordering storeroom is considered as the receiving storeroom, and the source storeroom is considered as the issuing storeroom. Only items with the same stock type can be transferred. Refer to the Material Request Line Definitions section, the Material Issue Line Definitions section, or the Material Return Line Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 54

55 About Receiving The receiving process is used to track inventory that is received as the result of a purchase order by recording basic information such as the quantity received, receiving location, packing slip details, carrier, and so on. When items are delivered to your organization, they must be added into the system inventory by creating a receiving record then accepting the items. The receiving process tracks delivery items through several distinct steps from the time they arrive until they are placed in a storeroom. The steps in the process allow for the actual receipt, inspection of items and acceptance. The process steps include: Record the delivery of items create a receipt record which holds basic delivery information. This step does not include details about the items. Match items to the purchase order review items on the purchase order and select, from a pick list, the items that were delivered. Items are counted and compared to what was ordered then placed in receipt. Items can also be received without a purchase order reference. Receive and accept the items complete the acceptance process to record the items into the appropriate storeroom. The system adjusts inventory quantities for the items accordingly. Depending on your system configuration and business practices, the system may also include taxes and other incidental costs for the items at the time of receipt. (alternate) Return the items As needed, return items for replacement or credit. When returns are processed, the appropriate costing and inventory adjustments are made to account for the credit. Quick Receive Your organization may not require a multi-step processing to receive items into your inventory. In these cases, the system includes a feature to receive and accept the items in one step. This feature is only available if it is enabled in your system implementation. If the stock item has Accept on Receipt set as yes, one-step receiving is allowed. Forced Complete In some cases, the quantity ordered on the purchase order may never be fulfilled. For example, if your organization ordered a quantity of 10 of items that were discontinued and the vendor only had 5 to send to fulfill the order. The system provides the ability to receive the five items then to force the system to consider the order complete. This processing flags the system that the line item receipt quantity is complete so that the purchase order does not stay open. After receiving partial items, select the Force Complete action on the Receipt record. Completing this action marks the purchase order line item as Fully Received and transitions it to the Closed state. Refer to the Receipt Definitions section or the Receipt Line Definitions for more information and field definitions. About Returns Returns track inventory that must be returned to a vendor. Returns are tracked in relationship to the purchase order for the original receipt of the items. Note that this processing is different from a material return in that the items are being returned to an outside vendor rather than adjusting quantities in internal storerooms. Refer to the Return Line Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 55

56 About Material Disposition Material disposition is a process designed to track repairable assets/stock items. The process tracks the asset or component from when it is removed from service to where it is either retired, scrapped or repaired and returned to availability for reuse. The portal is accessed under the Work Management menu. Material disposition processing involves creating a work order to remove then replace a broken asset or component. The asset must be flagged as repairable. In creating the work order and related activities, the resource requirements must indicate that a replacement asset must be checked out from a storeroom to replace the broken one. In order to fulfill these requirements, users must create a material request and material issue for the asset. A Material Disposition record is created as a result of these material requirements being fulfilled, and the replacement asset and the broken asset are added on the material disposition as line items. Note that new records are not created directly in the Material Disposition portal. They must be generated automatically by this processing. The person responsible for material disposition should navigate to the Material Disposition portal to complete the steps within the system to remove the broken asset and move it to a pending disposition status while moving the replacement asset to an installed status. This is done using the Complete Exchange option. When completing the complete exchange process, the system prompts for information such as the actions to perform on the assets, status reason, new storage location as applicable, and dispositioning dates and times. The actual assets should also be swapped as applicable toward completing the initial work order and activity. Your business process may then require that you create a follow up work order to repair the broken asset using the Create Work Order action from within the Material Disposition portal. You can review the costs and other statistics related to the replacement and repair of assets by reviewing the actual Asset record in the Cost Information section. Refer to the Material Disposition Definitions section for more information and field definitions. About Batch Stock Reorder and Reorder Review The system can be configured to automatically monitor and respond when inventory levels for stock items fall below set reorder points. Batch stock reorder monitors all storeroom stock items that are set up for reorder processing then processes any items that have reached the reorder point and creates Reorder Review for further processing. Reorder Review records cannot be created manually, they must be created by the batch stock reorder process. When the inventory for a stock item falls below the reorder point, the system creates this Reorder Review record. Reorder Review records include the quantity that batch processing has determined must be ordered to increase the current inventory to the maximum level, along with other information from the Storeroom record. Once the Reorder Review records are approved by a reviewer, batch processing completes the processing by generating the appropriate purchasing document (Purchase Order or Purchase Requisition). The batch process groups items with the same vendor, buyer, storeroom, type of purchasing document, and blanket contract before calling the process which creates the purchasing document. Batch processing helps avoid the possibility of creating multiple purchasing records to the same vendor an unnecessary cost. Reorder Review Mass Approval The Reorder Review Mass Approval portal is used to approve multiple reorder review items. Authorized approvers can place a check in front of one or many items and approve. From the Reorder Review record reviewers can click the Approve Reorder Items link and the mass approval screen opens. Oracle Utilities Work and Asset Management User Guide 56

57 Reorder Review vs. Automatic Reorder Note that automatic reorder (with reorder review), is different from automatic approval for reorder review. The auto reorder setting on the Stock Item Detail record can be set to monitory inventory quantity and automatically create a reorder review record when the reorder point is reached. Automatic approval (or, more accurately, Reorder Review Approval Required) is a setting on the Storeroom record which indicates whether or not the created reorder review records are automatically approved. Please refer to the configuration guide for more information on these settings. Refer to the Reorder Review Definitions section for more information and field definitions. Working with Inventory Administration The following sections provide information on tasks associated to creating and maintaining the administrative records needed for inventory management. Working with Storage Locations The following sections provide information on tasks associated to working with storage locations. Defining a Storage Location Type Navigate to the Storage Location Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the storage location type record: Note: This list does not necessarily represent required fields. Parent Location (as applicable) Organization (as applicable) The Location BO field indicates the business object to use when creating storage locations of this type. You can also enter a parent location or organization to establish the position of storage locations of this type in the location hierarchy. Storage location type is referenced when creating storage locations. Refer to the Storage Location Type Definitions section for more information. Creating a Storage Location Navigate to the Storage Location portal under Inventory, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the storage location record: Note: This list does not represent required fields. Storage Location Type Organization (as applicable) Contacts (as applicable) Make sure that the Location Disposition is set to Active if you want to make the location available for reference on other records. Oracle Utilities Work and Asset Management User Guide 57

58 You can also enter a parent location or organization to establish the position this storage location in the location hierarchy. This might be defaulted from the storage location type. Refer to the Storage Location Definitions section for more information. Linking a Contact to a Storage Location When a new storage location is created, a contact can be entered to link the location to the contact. This is used for reporting and to provide a point of contact if needed when referencing the location. Entering a Vehicle as a Storage Location Use this procedure to create a vehicle record within the system. Vehicles are mainly considered storage locations in Oracle Utilities Operational Device Management, and can be considered as both fleet assets and storage locations in Oracle Utilities Work and Asset Management. Please refer to the configuration guide for information on how vehicles should be set up. Prerequisites: The following are referenced by the vehicle record: Note: This list does not represent required fields. Storage Location Type Organization (as applicable) Contacts (as applicable) Make sure that the Location Disposition is set to Active if you want to make the vehicle available for reference on other records. Refer to the Storage Location Definitions section for more information and field definitions. Defining a Commodity Code Use this procedure to create a commodity code with the four levels of category, name, type and composition. Prerequisites: It is a good idea to have a detailed spreadsheet or plan for creating commodity codes for your organization. 1. Navigate to the Commodity Code portal. 2. Select the Add Category link. 3. Create the Commodity Category with a description. 4. Create a Commodity Name as needed and Save. It is recommended that you create one name at a time. If you need to create additional names, create them after completing this process through the commodity composition for each name. 5. From the hierarchy tree, select the Expand icon next to the Category you just created. 6. Select one of the commodity names just created and click the Edit button. 7. Enter a Commodity Type as needed and Save. It is recommended that you create one type at a time. If you need to create additional types, create them after completing this process through the commodity composition for each name and type. 8. From the hierarchy tree, select the Expand icon next to the Category you just created then expand the full hierarchy down to the Type. Oracle Utilities Work and Asset Management User Guide 58

59 9. Select the Type you just created and click the Edit button. 10. Enter Commodity Compositions as needed and Save. This is the last level of the hierarchy, so you can create as many as you need for each category, name, and type. Refer to the Commodity Code Definitions section for more information and field definitions. Working with Inventory The following sections provide information on tasks associated to working with inventory. Refer to the Understanding Inventory section for a conceptual overview of this functional area. Working with Stock Items The following sections provide information on tasks associated to working with stock items. Entering a Stock Item Use this procedure to manually enter a stock item into the system. Prerequisites: The following are referenced by the stock item record: Note: This list does not represent required fields. Resource UOM Usage Expense Code Inventory Expense Code Purchase Commodity Commodity Code Vendor Location set at least one vendor location to Primary Manufacturer The process of creating a stock item is the similar whether you are creating regular stock, a direct purchase item, a lot managed item, a tracked item, or a stock item that is expensed at receipt. Refer to the Resource Type Definitions section under Stock Item Resource Type for more information about the various fields that define each type of stock item. You must activate the stock item for it to be made available. Add the stock item to a storeroom by creating a Stock Item Details record for it. Adding a Stock Item to a Storeroom (Stock Item Details) Use this procedure to manually add a stock item to a storeroom. Prerequisites: The following are referenced by the stock item record: Note: This list does not represent required fields. Stock Item Storage Location Cost Center Oracle Utilities Work and Asset Management User Guide 59

60 Buyer Vendor Bin Information 1. Navigate to the Stock Item Details portal under Inventory and select Add. 2. Enter or search for and select the name of the stock item. 3. Enter or search for and select the record number for the storeroom (storage location). The storeroom where the stock item is stored must have already been defined as a storage location. 4. Select the Stock Item Detail Class according to the classification for the item. Storerooms might be classified as direct purchase, expensed at receipt, inventory, and so on. 5. Click OK. 6. Complete the remaining information according to your business practices. Note: Use the Reorder Information fields to set up automatic reorder for the stock item, as needed. 7. Activate the stock item detail record so that the stock item is considered available for work or ordering. Refer to the Stock Item Detail Definitions section for more information and field definitions. Reviewing Stores Use this procedure to review the recorded inventory for a stock item. 1. Navigate to the Stock Item portal under Inventory and select Search. 2. Search for and select the appropriate stock item. 3. Review the Stock Item Availability section for inventory quantity, on demand quantity, in receipt quantity, and so on. A color code will also indicate whether or not there are sufficient quantities of the item or if the item is under-stocked or over stocked. This information is also available on the Reorder Review record for a stock item in the Stock Item Availability section. Reviewing and Approving Items for Reorder (Reorder Review) Use this procedure to review and approve items that have been set for automatic reorder. 1. Navigate to the Reorder Review portal under Inventory. 2. Search for and select Reorder Review records. Search by a specific buyer, vendor, stock item, status and so on. Searching for items in Created status yields a list of all pending reorder review records. 3. Click the link to the Reorder Review record to view details about the reorder. The record provides information such as the reorder details, the stock item being reordered, vendor information, as applicable, and so on. 4. Click the Approve button to approve the reorder and initiate the creation of the follow up purchasing record. Alternately, you can click the Approve Reorder Items link under Additional Processes to launch the Mass Approval tool and approve multiple items at once. You also have the option to select the Initiate Stock Transfer link to create a stock transfer to replenish the items. This is used when there is more of the item in an alternate storeroom and this stock can be used for replenishment. Oracle Utilities Work and Asset Management User Guide 60

61 Processing a Stock Transfer Use this procedure to complete a stock transfer. Only items with the same stock type can be transferred. 1. Navigate to the Stock Transfer portal under Inventory and select Add. 2. Complete the required fields according to your business practices. 3. You must specify the source and destination storerooms. 4. Click Save. 5. Using the Stock Request Quick Add zone, add request lines for each stock item being transferred. 6. To initiate the transfer of each stock item, click the Ready for Issue button. 7. Click the Issue button next to each item in the Open Request Lines zone. You have the option to fully or partially issue the items. Selecting the issue options creates issue lines in the Issued Lines zone. 8. Click the Issue button for the overall record to transition all of the issued items to Ready for Receipt. As a result of the issue, receive options are made available for each of the stock item line items. 9. Navigate to the Stock Transfer Receipt tab. 10. Receive the stock items (into the receiving storeroom) using the appropriate buttons next to each stock item. The receipt will automatically be completed once all the stock items are received. Performing a Physical Inventory Navigate to the Physical Inventory portal under Inventory, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the physical inventory record: Note: This list does not represent required fields. Storeroom Stock Codes Vendor Processing for performing a physical inventory count includes the following: 1. Create the physical inventory header according to your business practices and Save. Enter a value for Items to Create to indicate the number of items to count. For example, you have 100 different stock items in inventory, but you only want to count 20 of them. This is not the quantity for each item, but rather, the number of individual items slated for counting. The physical inventory is initiated in Created status. 2. Create the list of items to be counted by clicking the Generate Count List button. This action generates the physical inventory count masters. If needed, you can regenerate the count at this stage. For example, you might edit the criteria used to originally generate the count lines. The lines would have to be regenrated after the update. 3. Record the counts. Oracle Utilities Work and Asset Management User Guide 61

62 This step varies depending on if this is a first count or a subsequent count and whether or not the physical count is equal to the system count. 4. Review the count lines and adjust inventory as needed. Only authorized people can generate the inventory adjustment. If the person doing the count is not authorized, the line stays in a Review Needed state. An authorized user must then click the Adjust Inventory button for the counts to be updated and the corresponding financial transaction created. Note that counts for lot-managed items and tracked assets are handled differently. A dialog opens after the adjust inventory action is selected, and there are options to either save the count in progress or finish the count. Refer to the Physical Inventory Definitions section for more information and field definitions. Working with Material Requests, Issue and Returns The following sections provide information on tasks associated to working with material requests, material issue, and material return. Creating a Material Request (Checkout Request) Navigate to the Material Request portal under Inventory, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the material request record: Note: This list does not represent required fields. Storeroom Activity After creating the request, add line items either manually or via a material request template. Refer to the Material Request Header Definitions section or the Material Request Line Definitions section for more information and field definitions. Issuing Stock (Material Issue) Use this procedure to issue requested material items. 1. Navigate to the Material Issue Line portal under Inventory and select Search. 2. Search for and select the appropriate material request. Search for items in the Ready for Issue state. 3. Verify the information on the material issue and click the Issue button next to each individual line item. Items can also be partially issued or, where allowed, you can issue substitute items. Refer to the Material Issue Line Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 62

63 Creating a Material Request Template Navigate to the Material Request Template portal under Inventory, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the material request template record: Note: This list does not represent required fields. Storeroom Stock Item Detail Expense Code Refer to the Material Request Template Definitions section for more information and field definitions. Processing a Material Return (Returning Stock Items) Use this procedure to return unused stock items into inventory. 1. Navigate to the Material Request portal under Inventory and select Search. In rare cases where items are being returned unrelated to a previous issue transaction, you can navigate directly to the Material Return portal and create a new record. 2. Search for and select the appropriate material request. 3. Click the Return button next to each individual line item. A return can be initiated as a follow up to a receipt. Alternately, the return might be initiated without a referenced receipt. Please refer to the Material Return Header Definitions section or the Material Return Line Definitions section for more information and field definitions. Working with Purchasing Receipts and Returns The following sections provide information on tasks associated to working with purchasing receipts and returns. Record Receipt/Delivery for a Purchase Order (Processing a Receipt) Navigate to the Receiving Receipt portal under Inventory, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the receiving record: Note: This list does not represent required fields. Purchase Order Receiving Location (Storage Location) Vendor After the Receipt record is created, add line items based on the purchase order pick list, as applicable, enter receiving quantities, and process the receipt to completion according to your business practices. The system adjusts inventory in stores based on the recorded received quantities. When receiving lot-managed or tracked assets the system displays dialogues to prompt for additional information such as the lot ID or asset ID. Purchasing returns can also be processed from this portal. Oracle Utilities Work and Asset Management User Guide 63

64 Refer to the Receipt Definitions section or the Receipt Line Definitions section for more information. Processing a Purchasing Return Navigate to the Receiving Return portal under Inventory, select Add, complete the required fields according to your business practices and Save. Processing a return can also be done from the Receiving Receipt portal if the item hasn t been accepted into inventory yet. Prerequisites: The following are referenced by the material return record: Note: This list does not represent required fields. Purchase Order Line Assets Stock Item Detail A return can be initiated as a follow up to a receipt. Alternately, the return might be initiated without a referenced receipt. Please refer to the Return Line Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 64

65 Chapter 5 Purchasing The following sections provide information on concepts related to managing purchasing. Understanding Purchasing Oracle Utilities Work and Asset Management uses Purchasing functions to plan, initiate, and process purchases and purchasing contracts. It also manages vendors, designated buyers, and stock items. The system can also automatically generate requisitions through Work Orders, through review of storeroom stocked items, or directly through purchase requisitions. Following a typical procurement life cycle, a requested item or service is listed on a requisition. Once reviewed and approved, if necessary, the requisition is copied into a purchase order. The purchase order is approved and issued to a vendor, and the requested item is received and inventoried. Throughout the process, different areas within the application are automatically maintained such as storeroom quantities and values depending on the type of item being purchased. If changes are required for a purchase order that has already been approved, a change order can be created within the purchase order. The system also facilitates expediting purchase orders and full or partial receipt of items. This section describes how various processes work together to manage purchasing throughout the system. Please refer to the Working with Purchasing section for procedural tasks related to these concepts. About Buyers Buyers are persons designated within your organization to make purchases and purchasing decisions. Buyers can be referenced on purchase requisitions and purchase orders to provide an official point of contact for the purchasing transaction. Depending on your business process and configuration settings, buyers may also be able to make changes on approved purchasing documents that affect price and quantity without re-obtaining approval. Buyers also manage automatic reordering. Refer to the Buyer Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 65

66 About Purchase Commodities Purchase commodities are used to assign a specific buyer to a classification of stock items in the storeroom. A buyer is specified on the purchase commodity so that when the commodity is then referenced on a stock item, the buyer association to that item is made. This allows buyers to be associated with a specialization over specific materials, equipment, etc. When items of that type are needed, the purchase commodity helps you to identify the buyer with that specialty. Refer to the Purchase Commodity Definitions section for more information and field definitions. About Manufacturers Use the Manufacturer portal to define attributes for product manufacturers. The use of this portal depends heavily upon your business practices, however, in general the manufacturers listed can be associated to specifications which can then be included on assets or components to provide additional reference information related to those objects. The manufacturer usually provides firmware, firmware updates, and specification information for assets and components. A manufacturer might also be referenced on regular stocked inventory. This does not include tracked assets. Manufacturer Specifications defines a list of asset specifications that belong to the manufacturer. Refer to the Manufacturer Definitions section for more information and field definitions. About Vendors Use the Vendor portal to maintain information about vendors, including their capabilities payment terms and delivery terms and various vendor sites. The vendor location distinguishes between multiple sites for one vendor. Each main Vendor record provides general information about your relationship with the vendor such as active blanket contracts, open requisitions, purchase order history, and a list of vendor locations. Vendor Locations One or many vendor locations are defined for each vendor to distinguish between multiple vendor sites. Each location provides more detailed information about the vendor site such as address, capabilities, payment details, contacts and so on. For example, it may be valuable to understand which location is shipping the goods that you have ordered from the vendor. Also, some vendors might ship from one site, but your payment terms are set with an alternate site. When a vendor has multiple locations, alternate locations are listed as related locations. Refer to the Vendor Definitions section or the Vendor Location Definitions section for more information and field definitions. About Capability Types Capability types refer to the types of products and services provided by a vendor. They are referenced on vendor locations to help identify what the vendor can provide, per location. Since they are primarily informational, your organization may use capability types in a variety of ways. For example, you might run reports on which vendors provide particular goods or services to have this information handy for buyers' reference when making purchasing decisions. Oracle Utilities Work and Asset Management User Guide 66

67 Refer to the Capability Type Definitions section for more information and field definitions. About Payment Terms Payment terms represent the payment and credit agreement between your organization and the vendor such as the number of days your organization has to pay the invoice or the forms of payment that are accepted. Refer to the Payment Term Definitions section for more information and field definitions. About FOB (Freight on Board or Free on Board) Freight on Board or Free on Board (FOB) represents the delivery charge terms negotiated for purchase orders from the vendor. This also includes the vendor or the seller's obligation to deliver goods at a designated place. This information is referenced on vendor locations, blanket contracts and expedite orders to help define delivery terms. Refer to the Free on Board Definitions section for more information and field definitions. About Purchase Requisitions Purchase requisitions are used to store and track requests for material resources and/or services. Requests can be created manually or by the system for the following situations for work orders that require materials or services. by the batch stock reorder process when the number of items falls below the reorder point. manually to replenish stock. After the purchase requisition is reviewed and approved, it can be transitioned to a purchase order to initiate the actual purchase with the vendor. Requisitions can also be used to create blanket contracts. While purchase orders can be created without a purchase requisition, the requisition can be used according to your business practices to formalize the purchasing process or create a more stringent chain of approvals for auditing or other purposes. Purchase requisitions affect pending order quantity for stock. Refer to the Purchase Requisition Header Definitions section or the Purchase Requisition Line Item Definitions for more information and field definitions. About Purchase Orders Purchase orders are contracts placed with vendors for the purchase of materials or services. Purchase Order records contain general information about the purchase including the requestor, when items are required, the vendor, and more. Details about each item or service are entered and maintained on purchase order line items. Your system configuration determines which stock items, services, and other types of items can be added as line items, how tax rates are handled for each line item, and so on. Additional processing on the purchase order allows you to it to the vendor, print to issue to the vendor, expedite, complete a change order, submit it for approval, or create a new revision. After the purchase order is approved within your organization and issued to the vendor, next steps involve waiting for the items to be received, then receiving them into the system. Refer to the About Receiving section for more information. When changes are made to the purchase order, the document may or may not need to re-enter the approval process depending on your business practices and system settings. For example, your system might be configured to allow changes to the purchase order that affect the total cost up to a certain percentage total value. Your system may also be set so that Oracle Utilities Work and Asset Management User Guide 67

68 the purchase order will transition directly to the approved or issued state, for instance, if the order was created by batch stock reorder. Note that only certain fields can be edited on an issued purchased order. If further updates are needed, such as changes that affect the pricing or quantity ordered, you have to create a new revision and resubmit to the vendor. Refer to the configuration guide for more information. Purchase orders affect the on demand quantity for stock. Refer to the Purchase Order Header Definitions section or the Purchase Order Line Item Definitions for more information and field definitions. About Expedite Purchase Order The expedite order process helps buyers and other purchasers to ensure that required goods arrive at the appointed date in the agreed quality at the agreed location. The Expedite Order portal is used to track purchase order items that have not yet been received. It allows users to modify select information on an issued purchase order without needing to create and process a change order. It is typically used when locations and delivery dates need to be altered, not when there are changes that would affect the cost of items or the total amount for the purchase order. Refer to the Expedite Purchase Order Definitions section for more information and field definitions. About Blanket Contracts A blanket contract is a purchasing agreement that your organization makes with a supplier to pre-plan the purchase of materials or services. These contracts typically contain multiple delivery dates over a period of time, often negotiated to take advantage of predetermined pricing or special discounts. Blanket contracts are also often used when there is a recurring need for expendable goods or when your organization buys large quantities from one vendor. Based on the blanket order sales orders (release orders), invoice items can be created as needed until the contract is fulfilled. As long as the blanket contract is in Active status, it can be referenced by new purchasing documents to order materials or services. Contracts can be transitioned to a suspended status so that they are temporarily unavailable for new purchases. This might be used while re-negotiating terms with a vendor, if you are researching new vendors for a particular item or service, or for other business requirements. Blanket Contract Access Lists Your system can be configured with lists of users who are authorized to issue purchasing documents against a blanket contract. Settings on the blanket contract determine whether or not the contract is restricted to a particular access list, which list of users has access or, if no access list is indicated, a default dollar value limit for the contract. When an access list is in use, a limit can be set for each individual user. Refer to About Blanket Contract Access Lists for more information. Blanket Contract Usage Spending against each blanket contracts is tracked via the Limit Used indicator and on the Activity and Usage tab. When a new blanket contract revision is created, these values reset for the new revision and are tracked as new. Refer to the Blanket Contract Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 68

69 About Blanket Contract Access Lists Blanket contract access lists identify which users have the authority to create charges against a blanket contract. The list also establishes a maximum dollar amount that the user is authorized to charge for a single purchase order. When a blanket contract is created, it references this list to provide the reference of authorized users. When a blanket contract is being applied toward creating a purchase order, the system verifies that the user is valid based on this list and that the person's purchasing limit is not exceeded. Refer to the Blanket Contract Access List Definitions section for more information and field definitions. Working with Purchasing Administration The following sections provide information on tasks associated to creating and maintaining the administrative records needed for purchasing functionality. Defining a Buyer Navigate to the Buyer portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the buyer record: Note: This list does not represent required fields. User ID Make sure that you activate the buyer after the record is created. Buyers are not available to reference on other records until they are active. Click the Activate button on the Buyer record. Please refer to the Buyer Definitions section for more information and field definitions. Defining a Purchase Commodity Navigate to the Purchase Commodity portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the purchase commodity record: Note: This list does not represent required fields. Buyer Refer to the Purchase Commodity Definitions section for more information and field definitions. Defining a Capability Type Navigate to the Capability Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Capability Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 69

70 Defining a Vendor Payment Term Navigate to the Payment Terms portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Payment Term Definitions section for more information and field definitions. Defining a FOB (Freight on Board or Free on Board) Navigate to the FOB portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Free on Board Definitions section for more information and field definitions. Working with Purchasing The following sections provide information on tasks associated to working with purchasing related functions. Refer to the Understanding Purchasing section for a conceptual overview of this functional area or to the Purchasing Object s sections for more information and field definitions. Working with Vendors and Manufacturers The following sections provide information on tasks associated to working with vendors and manufacturers. Defining a Manufacturer Navigate to the Manufacturer portal under Purchasing, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Manufacturer Definitions section for more information and field definitions. Creating a Vendor Navigate to the Vendor portal under Purchasing, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Vendor Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 70

71 Adding a Vendor Location Use this procedure to add locations to a vendor record. Prerequisites: The Vendor record must already be created. 1. Search for and select the appropriate Vendor record. 2. Navigate to the Vendor Locations section and click the Add link. 3. Complete the required fields according to your business practices and save. 4. Click the Activate button to make the vendor location available for reference on stock items and purchasing documents. You can use Duplicate to easily add another location for the same vendor. Any additional vendor locations that are added are automatically added as Related Vendor Locations. Once the vendor location has been defined, you can select the related link on the vendor record and update the information or enter notes, attach documents, define commodities, review purchase history, and so on. Refer to the Vendor Location Definitions section for more information and field definitions. Defining a Vendor's Payment Terms Use this procedure to add define your organization's payment terms with vendor. Prerequisites: The Vendor record must already be created, and you must have at least one vendor location defined. You must also have defined payment terms in the Payment Terms portal. 1. Search for and select the appropriate Vendor record. 2. Navigate to the Vendor Locations section and click the link for the appropriate location. Payment terms and other vendor details are defined at the location level, rather than on the main vendor record. 3. Click the Edit button and navigate to the Payment Details section. 4. Complete the field according to your business practices and save. Refer to the Vendor Location Definitions section for more information and field definitions. Adding Capabilities to a Vendor Use this procedure to add capabilities to a vendor record. Prerequisites: The Vendor record must already be created. You must also have capability types defined. 1. Search for and select the appropriate Vendor record. 2. Navigate to the Vendor Locations section and select the appropriate location. 3. Click the Edit button. 4. Navigate to the Capabilities section and add capabilities by capability type, as needed and Save. Refer to the Capability Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 71

72 Viewing Vendor Purchase Order History Use this procedure to add review a vendor's purchase order history. 1. Search for and select the appropriate Vendor record. 2. Navigate to the Vendor Purchase Order History Summary section to review completed transactions with the vendor. Viewing Open Requisitions with a Vendor Use this procedure to review your open requisitions with a vendor. 1. Search for and select the appropriate Vendor record. 2. Navigate to the Vendor Open Purchase Requisition section to review a list of requisitions that have not yet been recorded for receipt from the vendor. Working with Purchase Requisitions and Purchase Orders The following sections provide information on tasks associated to working with purchase requisitions and purchase orders. Creating a Purchase Requisition Manually Navigate to the Purchase Requisition portal under Purchasing, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the purchase requisition record: Note: This list does not necessarily represent required fields. Cost Center Expense Code Vendor Payment Term Stock Item and Stock Item Detail Purchase requisitions might be generated from batch stock reorder, from a work order, from a blanket contract, or created manually. Refer to the Purchase Requisition Header Definitions section for more information and field definitions. Adding Line Items to a Purchase Requisition Use this procedure to add line items to a purchase requisition. Prerequisites: The purchase requisition must already be created. 1. Search for and select the appropriate Purchase Requisition record. 2. Navigate to the Purchase Requisition Line Quick Add section. 3. Complete the required fields according to your business practices and save. Oracle Utilities Work and Asset Management User Guide 72

73 Purchase requisitions affect pending order quantity for stock, so the storeroom is required at this level if the line item is for stock items. Depending on your business practices, the requisition will next need to be routed for approval, approved, then transitioned to a purchase order. A purchase requisition can also be used to create a blanket contract. Refer to the Purchase Requisition Header Definitions section or the Purchase Requisition Line Item Definitions for more information and field definitions. Creating a Purchase Order from a Purchase Requisition Use this procedure to create a purchase order from a purchase requisition. You can also use this process to add to an existing purchase order. The requisition must be approved. 1. Search for and select the appropriate Purchase Requisition record. 2. Click the Process Purchase Order button. You can also navigate to below the Open Purchase Requisition Lines section, select appropriate items, and click the Create New PO button. This is used in cases where you do not want to add all of the line items from the requisition to the purchase order. You can also add the line items to an existing purchase order by clicking the Add to Existing PO button. The system transitions the requisition into a purchase order. You can navigate to the new purchase order by clicking the link in the Related Purchase Orders section on the requisition. Creating a Blanket Contract from a Purchase Requisition Use this procedure to create a blanket contract from a purchase requisition. The requisition must be approved. 1. Search for and select the appropriate Purchase Requisition record. 2. Click the Process Blanket Contract button. 3. Enter the Limit Amount and the Expiration Date, as applicable, and click OK. The blanket contract is created with the blanket contract number referenced in the Created Blanket Contract field on the requisition. Click the link to navigate to the blanket contract. 4. Click the Activate button to make the blanket contract available for use. You can use the link under the Vendor Information section to navigate to the record for the vendor that the contract applies to. Creating a Purchase Order Manually Navigate to the Purchase Order portal under Purchasing, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the purchase requisition record: Note: This list does not necessarily represent required fields. Vendor Payment Terms Oracle Utilities Work and Asset Management User Guide 73

74 Cost Center Stock Item and Stock Item Detail Purchase orders can be created directly, from a purchase requisition or they can be automatically generated from work requirements or stores replenishment requirements. Refer to the Purchase Order Header Definitions section for more information and field definitions. Adding Line Items to a Purchase Order Use this procedure to add line items to a purchase order. 1. Search for and select the appropriate Purchase Order record. 2. Navigate to the Purchase Order Line Quick Add section. 3. Complete the required fields according to your business practices and save. Purchase orders affect the on demand quantity for stock, so the storeroom is required at this level if the line item is for stock items. Refer to the Purchase Order Header Definitions section or the Purchase Order Line Item Definitions for more information and field definitions. Updating an Approved Purchase Order Typically changes that affect the overall cost total of an approved purchase order, must be re-approved. Use this procedure to update a purchase order after it has already been approved. Prerequisites: Purchase order is in Approved status. 1. Search for and select the appropriate Purchase Order record. 2. Click the Withdraw Approval button in the Record Actions section. The purchase order is transitioned back to Created status. 3. Update the Purchase Order as needed. 4. Click the Submit for Approval button. Issuing a Purchase Order Use this procedure to issue a purchase order. The purchase order must be in Approved status. 1. Search for and select the appropriate Purchase Order record. 2. Click the Issue button in the Record Actions section. 3. The system transitions the Purchase Order to Issued status. After the purchase order is issued, options become available under Additional Processing to perform actions such as e- mailing or printing the order, or creating a new revision. You can now send the purchase order to the vendor based on your business practices. Next you will receive the items within inventory processing, or you can force complete the purchase order. Oracle Utilities Work and Asset Management User Guide 74

75 Creating a Change Order Changes that affect the overall cost total of an issued purchase order should prompt a new revision, re-approval, and re-issue to the vendor. Use this procedure to create a change order. Prerequisites: Purchase order is in Issued status. 1. Search for and select the appropriate Purchase Order record under Purchasing. 2. Select the Create Revision link under the Additional Processing section. As required by your business practices, the purchase order is transitioned back to Created status, and actions to submit for approval are made available for selection. 3. Complete the updates and save. As necessary, resubmit the purchase order for approval then follow normal processing to issue and complete the order. Creating an Expedite Order Use this procedure to create an expedite order. Typically the terms of an expedite order are pre-negotiated with the vendor. The expedite order is used to record the new shipping date, and the number of items to expedite, as needed. The purchase order must be in Issued status. The entire purchase order may be expedited or only certain items on the purchase order. Expedite is used to track Purchase Order items that have not been received yet, and to allow users to modify selected information on an issued purchase order. 1. Search for and select the appropriate Purchase Order record. 2. Navigate to the Expedite tab and click the Add link in the Expedite Activity section. 3. Complete the required fields according to your business practices and save. The system creates an expedite order and adds to the list under the Expedite tab on the purchase order for reference. Refer to the Expedite Purchase Order Definitions section for more information and field definitions. Working with Blanket Contracts The following sections provide information on tasks associated to working with blanket contracts. Defining a Blanket Contract Access List Navigate to the Blanket Contract Access List portal, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the blanket contract access list record: Note: This list does not represent required fields. User ID Refer to the Blanket Contract Access List Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 75

76 Granting User Access to a Blanket Contract Use this procedure to grant users access to a blanket contract. 1. Navigate to the Blanket Contract Access List portal in Edit mode. 2. Add users and the dollar limit that each user is allowed to use for the blanket contracts where they have authorization. When a blanket contract with access list restrictions is being applied toward creating a purchase order, the system verifies that the user is valid based on this list and that the limit is not exceeded. Blanket contract access restrictions are determined by your business practices and configuration settings. Refer to the Blanket Contract Access List Definitions section for more information and field definitions. Creating a Blanket Contract Navigate to the Blanket Contract portal under Purchasing, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the blanket contract record: Note: This list does not represent required fields. Blanket Contract Access List Vendor Payment Terms Cost Center The blanket contract is added in Created status and needs to be activated before it can be used to generate related purchasing documents. Refer to the Blanket Contract Definitions section for more information and field definitions. Adding Line Items to a Blanket Contract Use this procedure to add line items to a blanket contract. 1. Search for and select the appropriate Blanket Contract record. 2. Navigate to the Blanket Contract Lines Quick Add section. 3. Complete the required fields according to your business practices and save. Refer to the Blanket Contract Line Definitions section for more information and field definitions. Re-sequencing Line Items on a Blanket Contract In cases where there are many line items, it can be useful to place frequently used or significant line items at the top of the list. Use this procedure to re-sequence line items on a blanket contract. 1. Search for and select the appropriate Blanket Contract record. 2. Navigate to the Blanket Contract Lines section and click the Resequence link. A dialog opens allowing you to change the order in which the items are listed. 3. Enter updated line numbers under the Sequence column as needed and save. Oracle Utilities Work and Asset Management User Guide 76

77 This does not change the actual item number. Creating a Purchase Requisition from a Blanket Contract Use this procedure to create a purchase requisition from a blanket contract. Purchase requisitions can be created directly, or they can be automatically generated from work requirements or stores replenishment requirements. 1. Search for and select the appropriate Blanket Contract. 2. Click the Create a Purchase Requisition link under Additional Processes. The blanket contract line item pick list opens to allow you to choose which line items to include on the purchase requisition. 3. Choose the appropriate Document Type for the order. This indicates whether the requisition is for a general purchase, stores replenishment, or for work generated. 4. Choose the appropriate receiving storeroom for the items. Certain additional fields may be required depending on the selected document type. For example, work order related requisitions may require an activity ID. Purchase requisitions affect pending order quantity for stock, so the storeroom is required at this level if the line item is for stock items. 5. Enter the quantity to order and the required by date. 6. Click Create Purchasing Document The system generates the requisition and navigates to the requisition record. From here you can review the requisition and/or submit it for approval. Creating a Purchase Order from a Blanket Contract Use this procedure to create a purchase order from a blanket contract. Purchase orders can be created directly, from a purchase requisition or they can be automatically generated from work requirements or stores replenishment requirements. 1. Search for and select the appropriate Blanket Contract. 2. Click the Create a Purchase Order link under Additional Processes. The blanket contract line item pick list opens to allow you to choose which line items to include on the purchase order. 3. Choose the appropriate Document Type for the order. This indicates whether the order is for a general purchase, stores replenishment, or for work generated. 4. Choose the appropriate receiving storeroom for the items. Certain additional fields may be required depending on the selected document type. Purchase orders affect the on demand quantity for stock, so the storeroom is required at this level if the line item is for stock items. 5. Enter the quantity to order and the required by date. 6. Click Create Purchasing Document The system generates the order and navigates to the purchase order record. From here you can review the order and/or submit it for approval. Oracle Utilities Work and Asset Management User Guide 77

78 Reviewing the Activity for a Blanket Contract Use this procedure to search for and review the purchases and usage against a blanket contract. 1. Search for and select the appropriate Blanket Contract record. 2. Navigate to the Activity and Usage tab. This tab shows all activity for the blanket contract including tracking of how much has been used against the limit amount. You can filter the results in this view by purchase order status or blanket contract revision numbers, or view a full list of results. Creating a Blanket Contract Revision Occasionally it is necessary to revise a blanket contract when vendor terms or prices change. Use this procedure to create a revision for a blanket contract. 1. Search for and select the appropriate Blanket Contract record. 2. Navigate to the Additional Processes section and select to create a revision. A new blanket contract revision is created and the system navigates to the new revision. The Create Revision for a New Time Period option creates a new revision with a new initiation date. The standard revision does not prompt for any changes when it is created. 3. Click the Edit button to make any needed changes to the revision and save. Oracle Utilities Work and Asset Management User Guide 78

79 Chapter 6 Resource Management The following sections provide information on concepts related to managing resources. Understanding Resource Management Resources encompass any object that contributes to the running of your organization. This includes hierarchies, employees, contacts, documents, standard notes and attachments, managing wage earning types and timesheets, and so on. This section describes how various processes work together to manage resources throughout the system. Please refer to the Working with Resource Management section for procedural tasks related to these concepts. About Hierarchies Organizations, locations, assets and components can be configured as part of a structured group, or hierarchy, to facilitate reporting, costing, and general organizational structure within the system. These hierarchies are represented in Tree View tabs where they are applicable. For example, navigating to the Organization portal and accessing the Tree View reveals the Organization Hierarchy with the current organization shown with its applicable parent and child organizations, locations, and assets in the tree. Clicking the broadcast icon next to any element within the tree displays a list of assets and components related to that element in the hierarchy. Clicking the actual link for an element navigates to the record for that element. The asset hierarchy is also considered part of this organizational structure. Refer to Asset Hierarchy for more information. About Organizations Organizations are used for categorization and reporting for locations. For example, your reporting may include a hierarchy that groups locations by a structure of parent and child organizations. Oracle Utilities Work and Asset Management User Guide 79

80 A basic Organization record shows the organization type, whether the organization is active or inactive, a description and any parent organization or location if applicable. The main attributes for organizations are managed in the Organizations portal. Refer to the Organization Definitions section for more information and field definitions. About Organization Types Organization types define the main attributes for organizations of a certain type. Organizations are used for categorization and reporting for locations. Valid Parent Types Parent types define the set of valid location types and organization types that can be used to define a parent location or parent organization. Refer to the Organization Type Definitions section for more information and field definitions. About Contacts Contacts are usually individuals or business entities who should be contacted in reference to a service point, work or any other issues. Contacts are referenced on locations to provide an associated person or business. The main attributes for contacts are managed in the Contact portal. For example, a contact might be referenced as the main person on site for asset or storage locations. Refer to the Contact Definitions section for more information and field definitions. About Contact Types Contact types establish parameters for contact of a specific type. Contacts are referenced on locations and other records to provide an associated person or business. The main attributes for contacts are managed in the Contact portal. Refer to the Contact Type Definitions section for more information and field definitions. About Resource Types Resource types define classes of resources that are used within your organization, usually to complete work. The system is delivered with craft, equipment, stock items, documents, and other as base package resource types. Your organization may define others depending on your business practices. Each activity on a work order is defined with one or more resource requirements which define resources that are needed to perform the activity. Typically planned work orders specify resource requirements on the related activities, and approvers can verify the requirements before the work order is approved. Requirements may be categorized as materials, labor, equipment or other. Refer to the Resource Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 80

81 About Documents (Attachments, Standard Notes and URL Attachments) The Documents portal is used to track, store and manage electronic documents for use throughout the system. Each document record contains information such as location, file type and a document description. Documents can be attached to entities such as assets, nodes, service history, and so on. Attached documents provide information to support records. For example, an installation guide can be attached to a component record, a safety data sheet to a stock item record, or a CAD drawing to a work order record. One document can be associated with more than one record and the document can be updated in one place at one time, and the new changes are applied wherever the document is attached. In the base package, documents are created as attachments, standard notes or as a URL. Refer to the Document Definitions section for more information and field definitions. Attachments Attachments can be any file, such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Attachment files are added to individual records such as an asset, purchase order, work order, activity, service history, and so on. Common Attachments The system also includes common attachments which are managed in the Admin Attachments portal. Common attachments only apply to the record where they are attached. Attachments that are maintained in the Admin Attachments portal are designed to be maintained in one place and referenced by other objects. Records such as warranties and specifications support common attachments since they would likely have an attachment that would only apply to that specific warranty or specification. However, creating attachments through the Documents portal is the recommended method for adding attachments which are needed throughout the system. Standard Notes Standard notes can be added as a type of document within the system and can then be associated to records wherever a note might be needed to provide additional information. Notes can be modified within the Documents portal and any changes or updates are reflected wherever the note is associated to a record. URL Attachments A URL can be added as a type of document within the system and can then be associated to records wherever it might be necessary to provide a link to additional information. The URL can be modified within the Documents portal and any changes or updates are reflected wherever the URL is associated to a record. Editing Documents After a document file has been added in the Document portal and it has been added to records throughout the system, it can be changed or modified by simply modifying the file that is uploaded to the Document record. In this way, the document can be maintained and kept up to date, and anywhere that it is associated to a record, the updated version will be accessible. Oracle Utilities Work and Asset Management User Guide 81

82 About Document Types Document types establish a basis for the types of documents that can be added within the system. This is referenced when creating a new Document record. Document types might be used to classify the types of documents being used such as work order doc, purchase order doc to help users find the documents they need by type. Your business process might also dictate that document descriptions include such information to help with searching for documents to attach. Please refer to the Document Type Definitions section for more information and field definitions. About Service Classes Service classes categorize activity types and indicate the type of work a shift is responsible for. Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity. Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity. Refer to the Service Class Definitions section for more information and field definitions. About Service Areas Service areas define a logical boundary of your organization's territory. Every crew shift is populated with a list of service areas that the crew shift is allowed to work. This is matched up with the service area indicated on the activity to help determine which crew shift can work the activity. Refer to the Service Area Definitions section for more information and field definitions. About Employees Employee records are used to manage human resource level information for the workers within your organization with details such as name and personal information, work status, the main craft worked by the employee, their business unit, payroll information, hire date, default timesheet information and so on. The employee record can also tie the employee to a service area where they are allowed to work as well as track training completed by the employee. Employee records are not required to reference a corresponding user profile. When there is no associated user profile, the module can be used to simply store information about employees who do not use the application. Information from the employee portal can be integrated with your external human resources system. Employee is referenced throughout the system on other records such as crews and crew shifts, contacts, direct charges, timesheets, on leave requests, to indicate which employee is responsible for or in possession of an asset, and so on. Various records can also be searched by employee. Employee type determines the kind of employee that is being created on an Employee record. Please refer to the Employee Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 82

83 About Employee Types Employee types define the kinds of employees that can be defined for your organization. For example, your organization might use employee types to define regular employees, skilled employees, and novice employees. Employee types are referenced on Employee records when they are defined. Refer to the Employee Type Definitions section for more information and field definitions. About Employee Unavailability Employee unavailability records establish periods of time where an employee has been given leave from his or her regular job duties. This might be due to circumstances such as vacation, sick leave, attending a training, jury duty, and so on. Logging employee unavailability allows the system to know when an employee is not available to perform work on the crews that he or she is associated with. Employee unavailability types define the kids of leave that might be used when creating an Employee Unavailability record. Refer to the Employee Unavailability Definitions section for more information and field definitions. About Employee Unavailability Types Employee unavailability types define kinds of situations where employees may be unavailable such as general leave, jury duty, vacation, sick leave, and so on. Employee unavailability types are referenced on Employee Unavailability records when they are defined. Refer to the Employee Unavailability Type Definitions section for more information and field definitions. About Resource Unit of Measurement Resource units of measurement (UOM) establish the acceptable units used to quantify resources such as stock items, materials, equipment or other used by your organization. Refer to the Resource Unit of Measurement Definitions section for more information and field definitions. About Crews A crew is a group of workers that can be assigned to complete work. Crews are used to group workers, schedule work, and help organize work schedules. Once a crew is created, shifts can be generated. Work order labor requirements can be assigned to the crew shift, and to a particular individual on the crew. Refer to the Crew Definitions section for more information and field definitions. About Crew Types Crew types define the kinds of crews that can be defined for your organization. For example, your organization might use crew types to define regular crews, skilled crews, and novice crews. Refer to the Crew Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 83

84 About Crew Shifts A crew shift is a planned period of time in which a crew (one or more workers) is scheduled to perform work. For example, a crew shift might be defined as Crew A, consisting of Jack and his van, working on a specific date from 9 am 5 pm. Crew shifts are associated with a crew shift type, that defines attributes common to all crew shifts of that type, including whether the shift is daily or weekly. For example, night shifts would have a different start time and duration than morning shifts, so they would have different shift types. Please refer to the Crew Shift Definitions section for more information and field definitions. About Crew Shift Types Crew shift types establish the kind of crew shift such as day, night, swing, and so on. Schedule Plan is a container for many daily schedules. Schedule Period defines if the crew shift type is a daily schedule or a weekly based planned schedule. Refer to the Crew Shift Type Definitions section for more information and field definitions. About Shift Plan Templates Shift plan templates are used to automatically generate crew shifts based on a set of pre-defined shift criteria such as the shift type, the shift rotation, the defined calendar and so on. Templates can be created as basic common templates for multiple crews, basic templates for a specific crew or templates that crews are subscribed to: Common templates: Common templates establish an initial date for rotations to start, number of weeks for rotation, work calendar and the type of schedule plan. These templates do not specify details such as the specific crew. Since they do not specify the crew, common templates cannot be directly used to generate shifts. Shifts are actually generated from the subscription template that references the common template. If a common template is changed after shifts have been generated, the changes are not reflected until the next time batch processing runs. You can apply changes to the specific crew shift manually. Subscription templates: Subscription templates link common templates to crews. They define an effective period to which shifts for the crew can be generated based on the details on the common template. Crew templates: Crew templates establish an effective and expiration date, a number of rotation weeks, work calendar and the shift plan type for a specific crew. Daily vs. Weekly Templates The shift plan type defined on common templates and crew templates, designate whether the template is for daily or weekly shifts. The type also defines the details for those shifts such as the daily start and end times for daily shifts, or the schedule period for weekly shifts. Weekly crew shifts represent a set of daily shifts, typically with one crew shift template per day of the week. A weekly template can map crew templates for rotating cycles of one or many weeks. This is used to account for shift variations across multiple week cycles. Please refer to the Shift Plan Template Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 84

85 About Crafts Crafts define a skill or work specialty for crew members such as mechanic, electrician, plumber, arborist and so on. When crafts are defined, a secondary craft can be added as part of the craft definition. Secondary crafts are regarded as additional or complementary skills to the primary craft. Every employee, i.e. crew member, is defined with a principal craft. The principal craft is used when scheduling activity labor requirements to shifts. Secondary crafts are also used during scheduling and appear as less important capacities to schedule. The secondary crafts are presented as available crafts during scheduling. Please refer to the Resource Type Definitions section for more information and field definitions. About Equipment Equipment is defined by your organization to be referenced as a resource type available for use to complete work. This might include machinery, tools or other equipment required to work activities (crane, bulldozer, drill, etc.). Equipment is referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity. Refer to the Resource Type Definitions section for more information and field definitions. About Other Resources Other resources are defined by your organization to be referenced as a resource type available for use to complete work. Other resources are referenced on activities as a material resource requirement. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity. Refer to the Resource Type Definitions section for more information and field definitions. About Other Direct Charges Other direct charges are defined by your organization to be referenced as a charge type to charge work against. This might include miscellaneous charges for activities such as meals, miles, hotel stay, and so on. Other direct charges are incurred on activities as a material resource requirement from other resources. The system tracks usage and reports the costing associated with that usage against the total cost of completing the activity. Refer to the Other Direct Charge Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 85

86 Working with Resource Management Administration The following sections provide information on tasks associated to creating and maintaining the administrative records needed for resource management. Defining a Resource Unit of Measurement (UOM) Navigate to the Unit of Measure Resource portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Resource Unit of Measurement Definitions section for more information and field definitions. Defining Organization Types Navigate to the Organization Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. You might define an organization type as a child organization type. In this case, the parent organization needs to be defined first. Organization types are referenced when creating organizations. Refer to the Organization Type Definitions section for more information and field definitions. Defining a Service Class Navigate to the Service Class portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Service Class Definitions section for more information and field definitions. Defining a Service Area Navigate to the Service Area portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Service Area Definitions section for more information and field definitions. Defining a Contact Type Navigate to the Contact Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Oracle Utilities Work and Asset Management User Guide 86

87 Contact type is referenced when creating contacts. Please refer to the Contact Type Definitions section for more information. Defining a Document Type Navigate to the Document Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Document Type Definitions section for more information and field definitions. Defining an Employee Type Navigate to the Employee Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. An employee type is referenced when creating an employee. Refer to the Employee Type Definitions section for more information and field definitions. Defining an Employee Unavailability Type Navigate to the Employee Unavailability Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the employee unavailability type record: Note: This list does not represent required fields. Cost Center Expense Code An employee unavailability type is referenced when entering employee unavailability. Employee unavailability is typically created for leave time or for work functions such as training or meetings. When you create the employee unavailability type, this is specified by the business object that is selected on the initial screen. Defining a Crew Type Navigate to the Crew Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Crew Type Definitions section for more information and field definitions. Defining a Crew Shift Type Navigate to the Crew Shift Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Oracle Utilities Work and Asset Management User Guide 87

88 Please refer to the Crew Shift Type Definitions section for more information and field definitions. Working with Resource Management The following sections provide information on tasks associated to working with resources. Refer to the Understanding Resource Management section for a conceptual overview of this functional area or to the Resource Management Object s sections for more information and field definitions. Working with Contacts The following sections provide information on tasks associated with creating, searching and updating contacts. Creating a Contact Navigate to the Contact portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the contact record: Note: This list does not represent required fields. Contact Type Refer to the Contact Definitions section for more information. Linking a Contact to a Storage Location When a new storage location is created, a contact can be entered to link the location to the contact. This is used for reporting and to provide a point of contact if needed when referencing the location. Working with Organizations The following sections provide information on tasks associated with creating and maintaining organizations. Creating an Organization Navigate to the Organization portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the organization record: Note: This list does not represent required fields. Organization Type Parent Organization (as applicable) Refer to the Organization Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 88

89 Linking an Organization to a Location When a new asset or storage location is created, a parent organization can be entered to link the location to the organization. This is used for reporting to establish a hierarchy of locations. Working with Documents The following sections provide information on tasks associated to working with resources. Creating a Document Use this procedure to create an attachment, standard note or URL in the Document portal for general access from within the application. 1. Navigate to the Document portal under Resource Management and select Add. 2. Choose the format by selecting from the Document Business Object field and click Ok. This allows you to indicate whether the document is an attachment, a standard note, a URL or any other file type customized by your organization, as applicable. 3. Complete the remaining fields according to your business practices and save. The system navigates back to the main portal where you can upload the file as a separate step. 4. Click the Upload button. 5. Browse to the file and click Upload. Make sure that you select a file with the same file type that you selected when you initially created the document. Adding an Attachment, Note or URL to a Record Use this procedure to add documents such as attachments or standard notes to general records throughout the system. The document must already be created in the Documents portal. If it is not already created, you can navigate to the Document portal from the current record and add it. 1. Open any record that supports documents. This generally includes any record that may require supplemental information. 2. Navigate to the Documents section and click the Add link. 3. Search for and select the appropriate Document ID and click Ok. The system adds the document link to the record. Viewing Documents Use this procedure to view an attachment that has been added to an individual record or in the Document portal. 1. Navigate to the record where the attachment was added. This could be the Document portal or an individual record. 2. Click the View button next to the document link. Oracle Utilities Work and Asset Management User Guide 89

90 Clicking the link for the actual document name navigates to the Document portal. The system opens the attachment, note or URL accordingly. Replacing a Document File Use this procedure to replace any document file. 1. Navigate to the Document portal in Edit mode. 2. Search for and select the appropriate document record. 3. Click the Upload button. 4. Browse to and select the new file then click Upload. The new file is updated anywhere the document is referenced. Refer to the Document Definitions section for more information. Deleting Documents from Records Use this procedure to delete a document that has been added to an individual record. 1. Navigate to the record where the attachment was added. 2. Navigate to the Documents section. 3. Click the delete icon. 4. Confirm that you want to delete the attachment. Refer to the Document Definitions section for more information. Working with Common Attachments The following sections provide information on tasks associated to creating and maintaining attachments. Use Documents if the attachment needs to apply to many records throughout the system. Creating a Common Attachment from the Attachment Portal Use this procedure to create an attachment from the Attachment portal for general access from within the application. Use Documents if the attachment needs to apply to many records throughout the system. 1. Navigate to the Attachments portal in edit mode. 2. Choose the attachment format by selecting from the Attachment Business Object field and click Ok. This allows you to indicate whether the attachment is a spreadsheet, an image, video or audio, a text document, or any other file type available. 3. Enter the file name and click Save. The system navigates back to the main portal where you can upload the attachment file as a separate step. 4. Click the Upload button. 5. Browse to the attachment file and click Upload. Oracle Utilities Work and Asset Management User Guide 90

91 Make sure that you select a file with the same file type that you selected when you initially created the attachment. Viewing Common Attachments Use this procedure to view an attachment that has been added to an individual record or in the Attachments portal. Use Documents if the attachment needs to apply to many records throughout the system. 1. Navigate to the record where the attachment was added. This could be the Attachments portal or an individual record such as an asset, service history, location, specification etc. 2. Click the link for the attachment. 3. Click the View button. A prompt is displayed to open or save the attachment. Editing Common Attachments Use this procedure to edit an attachment that has been added to an individual record or in the Attachments portal. When you edit an attachment you can only change the Attachment File Name. If you need to replace the attachment file select the Upload button and browse to select a different file. Use Documents if the attachment needs to apply to many records throughout the system. 1. Navigate to the record where the attachment was added. This could be the Attachments portal or an individual record such as an asset, service history, location, specification etc. 2. Click the link for the attachment. 3. Click the Edit button. 4. Modify the attachment file name as needed. Replacing an Common Attachment File Use this procedure to replace an attachment file that has been added to an individual record or in the Attachments portal. If you need to edit the attachment file name select the Edit button. Use Documents if the attachment needs to apply to many records throughout the system. 1. Navigate to the record where the attachment was added. This could be the Attachments portal or an individual record such as an asset, service history, location, specification etc. 2. Click the link for the attachment. 3. Click the Upload button. 4. Browse to and select the new file then click Upload. The new file is updated anywhere the attachment is referenced. Oracle Utilities Work and Asset Management User Guide 91

92 Deleting Common Attachments Use this procedure to delete an attachment that has been added to an individual record or in the Attachments portal. Use Documents if the attachment needs to apply to many records throughout the system. 1. Navigate to the record where the attachment was added. This could be the Attachments portal or an individual record such as an asset, service history, location, specification etc. 2. Click the delete icon. 3. Confirm that you want to delete the attachment. You can also delete the attachment by clicking the link and then selecting the Delete button. Working with Employees The following sections provide information on tasks associated to working with employees. Creating an Employee Navigate to the Employee portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the employee record: Note: This list does not represent required fields. Employee Type User ID Craft Business Unit Service Area In order for the employee to charge timesheets in the system, he or she must have a billable rate added to his or her Employee record. Note that secondary crafts or additional skills for a craft are defined on the craft. Any primary craft that is attributed to the employee will also attribute the secondary crafts for that primary craft. Please refer to the Employee Definitions section for more information and field definitions. Enter and Track Employee Training Information 1. Search for and select the appropriate Employee record. 2. Click the Edit button. 3. Navigate to the Training Information section and select the applicable course. Courses are entered and maintained by your organization during implementation. 4. Click Save. Oracle Utilities Work and Asset Management User Guide 92

93 Entering Employee Unavailability Navigate to the Employee Unavailability portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the employee unavailability record: Note: This list does not represent required fields. Employee Unavailability Type Refer to the Employee Unavailability Type Definitions section for more information and field definitions. Create an Employee Leave Request Use this procedure to request for leave. This can typically be completed by the employee, or by a manager or supervisor on the employee's behalf. 1. Navigate to the Employee Unavailability portal under Resource Management and select Add. 2. Select the appropriate Employee Unavailability Type. 3. Complete the required fields according to your business practices and Save. After the leave is approved, employees indicated on the attendees list are not available as work resources. This means that shifts generated during the leave time will not include the employee as part of the crew. Please refer to the Employee Unavailability Definitions section for more information and field definitions. Working with Work Resources, Crews and Crew Shifts The following sections provide information on tasks associated to working with crews, crew shifts, crafts, equipment and other miscellaneous resources. Entering Equipment Navigate to the Equipment portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the equipment record: Note: This list does not represent required fields. Resource UOM Non material class Cost Center Typically should be of the type that does not allow user charges. However this option can be allowed or disallowed. Expense Code Refer to the Resource Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 93

94 Entering an Other Resource Navigate to the Other Resource portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the other resources record: Note: This list does not represent required fields. Resource UOM Non material class Cost Center Typically should be of the type that does not allow user charges. However this option can be allowed or disallowed. Expense Code Refer to the Resource Type Definitions section for more information and field definitions. Creating a Crew Navigate to the Crew portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the crew record: Note: This list does not represent required fields. Crew Type Defines the default planning horizon days for the crew. Employee ID Refer to the Crew Definitions section for more information and field definitions. Adding Workers to a Crew Use this procedure to add workers to an existing crew. 1. Search for and select the appropriate Crew record. 2. Click the Edit button. 3. Navigate to the Default Crew Members section and enter or search for and select the employee IDs and role of the people who belong on the crew. The employee's principal craft is displayed with their name so that you can easily see the skills of each person added to the crew. This is also where you specify the crew supervisor role, as applicable. It is possible to have a crew with one member. 4. Click Save. Creating a Craft Navigate to the Craft portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the craft record: Note: This list does not represent required fields. Oracle Utilities Work and Asset Management User Guide 94

95 Resource UOM Expense Code Ensure that you Activate the craft after it is created so that it is available to be added to other records. You can also enter the hourly rate for the craft after it is created. Refer to the Resource Type Definitions section for more information and field definitions. Adding an Hourly Rate to a Craft Use this procedure to add an hourly rate to a craft. 1. Search for and select the appropriate Craft record. 2. Navigate to the Hourly Rate section and select the Add link. 3. Enter an Effective Date and the Hourly Rate and Save. Refer to the Resource Type Definitions section for more information and field definitions. Defining a Secondary Craft Use this procedure to define a secondary craft. Prerequisites: Crafts are considered as skills of a worker. You might define a secondary craft that would act as backup or which would be scheduled in cases where the primary craft is not available. 1. Search for and select the appropriate Craft record. 2. Click the Edit button. 3. Navigate to the Secondary Crafts section and enter or search for and select the secondary craft ID. 4. Save. Creating a Shift Plan Template Navigate to the Shift Plan Template portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the shift plan template record: Note: This list does not represent required fields. Crew Schedule Plan Type Work Calendar Refer to the Shift Plan Template Definitions section for more information and field definitions. Subscribing a Crew to a Common Shift Weekly Template Use this procedure to subscribe a crew to a common shift plan template. Prerequisites: The following are referenced by the shift plan template record: Note: This list does not represent required fields. Oracle Utilities Work and Asset Management User Guide 95

96 Common Shift Plan Template 1. Navigate to the Shift Plan Template portal and select Add. 2. Select Subscription Shift Plan Template and click OK. 3. Enter a specific Crew and Common Shift Plan Template. 4. Enter the effective date and expiration date. 5. Click Save. Please refer to the Shift Plan Template Definitions section for more information and field definitions. Creating a Daily Crew Shift Navigate to the Crew Shift portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the crew shift record: Note: This list does not represent required fields. Crew Crew Shift Type Schedule Plan Template Employee defaults from the crew Service Class (as applicable) Service Area (as applicable) Refer to the Crew Shift Definitions section for more information and field definitions. Creating a Weekly Crew Shift Navigate to the Crew Shift portal under Resource Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the crew shift record: Note: This list does not represent required fields. Crew Crew Shift Type Refer to the Crew Shift Definitions section for more information and field definitions. Reviewing a Crew Shift Schedule Use this procedure to review the shift schedule for a crew. 1. Search for and select the appropriate Crew record. 2. Navigate to the Crew Calendar section. The calendar displays days when the crew is scheduled for work as well as any downtime, training dates or other leave. 3. Click Save. Oracle Utilities Work and Asset Management User Guide 96

97 Chapter 7 Work Management The following sections provide information on concepts related to managing work including work requests, work orders, activities and so on. Understanding Work Management Work management is the process by which work orders are requested, approved and activated, work is performed and then work is finished and closed. While the work is being performed, materials, equipment assets and labor are tracked. As maintenance efforts create demand for parts, the system uses this information to help with inventory control. Work management functions are the primary user of information established elsewhere in the system including information about assets, stock items, employees, crews and financials information. Work management also channels information for use with inventory and purchasing by placing demand for parts. Work management allows work to be tracked through all stages of a project; from the initial observation of a problem and the resulting work request, through the initiation and approval of the work order and the completion of each activity. It also allows you to plan preventive maintenance that occurs in cycles, and helps you plan ahead for parts and labor requirements to so that you can streamline your maintenance operations. This section describes how various processes work together to manage work throughout the system. Please refer to the Working with Work Management section for procedural tasks related to these concepts. About Planners and Maintenance Managers Planners and maintenance managers are defined for your organization as personnel authorized to perform certain functions or who are responsible for overseeing specific work. For example, planners are usually responsible for planning work and materials for assets. Maintenance managers are typically more specifically involved with an aspect of work such as managing hazardous materials or specialized equipment. The usage of these roles depends entirely upon your business practices. Oracle Utilities Work and Asset Management User Guide 97

98 Every planner and maintenance manager references the User ID of the assigned person. Work statistics on the Home Page can be configured to display by planner or by maintenance manager. Refer to the Maintenance Manager Definitions section or the Planner Definitions section for more information. About Work Requests Work Requests are used to request work or services to be performed and, when approved, can become work orders. Work Requests can be created manually, as a follow-up to an activity, or by an external system. Work requests are mainly used to implement an approval chain for the requested work. When a work request is created it is reviewed by maintenance planners to determine if the request is valid and can be turned into a Work Order. If the work request is rejected or canceled the work requestor is notified and work request can be resubmitted. If the work request is approved, the planner can either add the request to an existing work order as a new task or create a new work order specifically for the work being requested. If necessary, it is possible to enter a work order directly if you have the proper authorization. Possible Duplicate WRs/WOs/Activities The system identifies any records which could possibly be duplicate work requests, work orders or activities in this zone. Any work records that are in non-final statuses (such as created, pending approval or approved ) with the same asset and location (including address) of the current work request are listed as duplicates. You can choose to include or exclude work records related to preventive maintenance. If a record is found to be a duplicate, it can be canceled under Record Actions. Refer to the Work Request Definitions section for more information and field definitions. About Work Orders Work orders group similar activities and are used to manage activities to perform any kind of work such as inspection, install, replacement, upgrade, and so on. They are mainly used to facilitate approval processing for work projects. Work orders might also be created to manage a set of activities where the activities are manually linked to the work order. Completion events are used on activities to document and process the work that was done and to update data associated to the activity. Work orders also provide summary information about the various activities and the assets that are being worked on those activities. Refer to the Work Order Definitions section for more information and field definitions. The Asset, Specification, Address and Location Information sections serve to select the assets that should be included on the work order. As many or as few of this criteria can be selected to narrow down the assets that are included for the work. Work Order Templates It is possible to create templates from most types of work orders so that the general work model can be reused. Work order templates can also be referenced for scheduled service history. Refer to the Template Work Order Definitions section or the About Template Work Orders for more information and field descriptions. Activity Information The Activity Information zone provides summary information regarding the activities that are included on the work order. Refer to the Activity Definitions section or the About Activities for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 98

99 Unplanned Work Since unplanned work simplifies small, uncomplicated, and/or one-time jobs, foregoing planning can be effective when the task to be completed is straightforward and does not involve many details. Completing Work Orders Work orders are automatically completed when every activity linked to the work order arrives at a final state based on the completion events for the activities. About Template Work Orders Template work orders, or benchmark work orders, are work orders that can be re-used to help your organization avoid repeating planning the same work for similar jobs. They can be used for basic work planning, but are also typically used with preventive maintenance. The template work order contains the header work order details. Template activities and template activity resource requirements are used to plan those aspects of the work plan. Work order templates can only be deleted when they are Created, Active, or Inactive and are not referenced from any associated work order, maintenance trigger or other records. Two types of work order templates can be utilized: General Template Work Order: used to plan for activities and resources which can be common to assets regardless of the asset disposotion. This type of template can be used in the maintenance schedule configured for asset specifications as well as on the override maintenance schedule configured for an asset. Asset Location Specific Template Work Order: used to plan for activities and resources which are specific to an asset location (where the asset is installed). This type of template cannot be used in the maintenance schedules which are configured for asset specifications. This type of template can be used in situations where there is an activity dependency. For example one activity must be performed at one specific location before the activity can be performed at a second location. This might apply, for instance, if a system needs to be shut down at a valve so that downstream components can be rebuilt or cleaned. Preventive Maintenance/Reliability Centered Maintenance Template work orders are used with preventive maintenance and reliability centered maintenance to create new work orders when the maintenance is triggered. The appropriate work order template is referenced on the maintenance trigger so that the appropriate work records are automatically created when the trigger is cycled. Usually, the work orders that are created from the template can be modified to represent the actual execution of work. For example, modifications may be needed if the requirements from the template don't match the exact requirements for the actual execution of the work. Refer to the Template Work Order Definitions section for more information and field definitions. Template Activities Template activities are activities that can be re-used to help your organization avoid repeating planning the same work for similar jobs. They can be used for basic work planning, but are also typically used with preventive maintenance. Template activities are part of a template work order and cannot be re-used by multiple template work orders. Refer to the Template Activity Resource Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 99

100 About Activities An activity is a task which needs to be completed. Activities manage asset changes, work, inspections maintenance and other actions that are performed on assets or components. As examples, activities may be created for maintenance of assets, to create service history, to install or exchange devices. They can also be used to create other activities. The benefit of using activities to process work is to keep a history of the work being done. This history can then be used for tracking and auditing. Activities can be created "on the fly", but they must be grouped and managed using work orders. Activity types control the purpose and configuration of activities such as which completion events are required and sequence to execute completion events. Completion events are used on activities to document and process the work that was done and to update data associated to the activity. For example, if a completion even moves an asset to a new disposition state, the state is not reflected until the completion event is processed. Refer to the Activity Definitions section for more information and field definitions. About Activity Types Activity types define the main attributes for activities of a certain type. The activity type specifies whether or not costs are tracked, the applicable service class, scheduling information as applicable, default requirements, attachments, identifiers, how to handle errors or exceptions, and completion details for activities of the type. The following activity types can be defined: Basic Activity Type: Defines a type of activity with no requirements or planning details. Does not include service history. Outbound Activity Type: Defines a type of activity with the details needed to send the activity to an external system. Operational Device Scheduled Activity Type: Defines an activity with planning details and scheduling details specifically for Oracle Utilities Operational Device Management. Planned Activity Type: Defines an activity with planning and scheduling details specifically for Oracle Utilities Work and Asset Management. Refer to the Activity Type Definitions section for more information and field definitions. About Activity Resource Requirements Each activity on a work order is defined with one or more resource requirements which define resources that are needed to perform the activity. Typically planned work orders specify resource requirements on the related activities, and approvers can verify the requirements before the work order is approved. Requirements may be categorized as materials, labor, equipment or other. Material requirements specify materials or stock items to be used for the activity (pipe, pump, bolt, etc.). Material requirements might also be fulfilled with a direct purchase. Labor requirements, or crafts, specify the type of skills needed for the activity (technician, plumber, electrician, etc.). This might include premium or regular labor. Equipment requirements specify the machinery, tools or other equipment required for the activity (crane, bulldozer, drill, etc.). Oracle Utilities Work and Asset Management User Guide 100

101 Other requirements cover miscellaneous requirements for the activity (meals, miles, hotel stay, etc.). Refer to the Activity Resource Requirement Definitions section for more information and field definitions. Note the following with respect to activity resource requirements: Activity resource requirements can only be added and navigated in the Activity portal under Resources. Material requests (issues and returns) can be applied against the resource requirement when the activity is active. When inventory materials are issued, the state of the resource requirement transitions to fulfilled. This is when the issued quantity is greater than or equal to the planned quantity. If materials are not in stock and need to be purchased to fulfill the requirement, a purchase order or requisition might be issued. These materials are typically tracked as direct purchases. When direct purchase are received, the material requirement state is set to fulfilled. This is when the receipt quantity greater than or equal to the planned quantity. Timesheets are used to track labor requirements. The labor requirement establishes an estimated number of work hours required. As timesheets are created and posted, the actual work hours are tracked. Other direct charges are used to track equipment and other requirements. Resource Estimates Activity resource requirements determine the original estimates or planned amount for labor, equipment, materials and other on activities. Even canceled activity resources requirements are calculated as part of the original estimate. The original estimate is the value of the resource requirement at the time the work order was initially, i.e. the first time, approved. The original estimate is snapshot into a separate column when the initial approval happened. Keep in mind that approved work order can be reopened to add new activities/resource requirements and resubmit for approval. Those new resource requirements won t have initial estimate (it will be zero). The system calculates a revised estimate to reflect the current value of the resource requirement. For example, a resource requirement was initially planned for 10 pumps at $10.00 each. Upon the initial/first approval, the initial estimate will be stamped with $ and the revised estimate is also $ If the planner changes the requirement to 15 pumps instead, the original estimate will stay at $ and the revised estimate will be $ Canceled requirements are not calculated as part of the revised estimate. Committed Amount Committed amount is the total of costs applied to the activity due to direct purchase costs that are committed when a purchase order is issued. This value uses the issued amount, not closed or completed since the costs are considered as committed once the purchase order is issued to the vendor. This amount reflects the total due to the vendor, as full or partial invoice amounts are closed. It does not reflect amounts that are completed or closed. For example, a purchase order line has been issued for 10 pumps at $10 each. Assume 4 pumps were received and a partial invoice line of $40 was issued for the 4 items. This partial invoice for $40 reduces the committed amount $100 minus $40 = $60. Once the other 6 items are received, the purchase order line moves to closed status and it does not have an impact on the committed amount. Unplanned Resources Unplanned resources are defined as issued or returned materials or timesheet entries that were not part of the original resource requirements or estimates. Activities include a zone which lists any unplanned activity resources. Fulfilling Requirements Material requirements can be fulfilled in the following ways: For inventory, if the issued quantity is greater than or equal to the planned quantity the system automatically changes the resource requirement to Fulfilled. This happens in cases where the crew has checked out all the planned quantity from the storeroom. Oracle Utilities Work and Asset Management User Guide 101

102 For direct purchased material, if the received quantity is greater than or equal to the planned quantity, the system updates the resource requirement to Fulfilled. This method of automatic fulfillment is only applicable to material. For inventory material, when the resource requirement is approved (as part of the WO approval), the system puts the quantity is Pending Demand on the storeroom, once the activity material requirement becomes Active, that quantity becomes On Demand (and Pending Demand is closed out, or becomes zero). Materials can also be reserved. If the storeroom has enough quantity then that quantity becomes reserved for the given amount. The reserved quantity provides storeroom manages with visibility into what is to come so that they can order materials accordingly. Note that, although it may not be part of work, when material is issued from storeroom, material issue will reduce demand by the issued quantity or the original planned quantity, whichever is less. This is to prevent a negative on demand quantity, (if the issue quantity is more than the planned quantity.) All resource requirements can become fulfilled in one of the following ways: Users click the Fulfill button. When the activity is completed, the system automatically changes all resource requirements to Fulfilled status. When a material requirement becomes fulfilled, the system closes out the On Demand/Reserved quantity left (planned quantity issued quantity). For Labor, Equipment and Other, fulfilled is only an informational status with no related processing. About Scheduling The scheduling process assigns tasks to crew shifts, matching work requirements to crew capabilities. The goal of the scheduling process is to produce the most effective schedule based on the requirements of the work. Planners can access the Scheduling portal to search and review new activity labor requirements and/or unfinished back log work and make allocations to available crew shifts. Users can also use this portal to view the capacity of shifts based on crafts. About Projects Projects provide a way to group work so that it can be planned and charged against large efforts. Typically, a project will be a task that is out of the ordinary, or that requires extra planning and resources. Examples would be adding new facilities or conducting a major overhaul of an assembly line. When a project is initiated and funds are approved, the project can be broken down into a hierarchical arrangement of smaller sub-projects, or the work breakdown structure. Each sub-project represents a controllable unit of work within the project. The ability to enter information about units of work, scheduling information, cost estimates and target dates for each project and sub-project forms the basis for planning the project and monitoring its progress to completion. Work orders and activities can be associated to the project and are automatically included in the cost of the project. Projects can be configured to go through regular approval processing, so that after the project is created it must be submitted for approval then approved. Note that if subprojects are planned, the project itself should have Allow Charge set to No. Charges should be tracked by subproject. Refer to the Project Definitions section for more information and field definitions. Project Categories Your organization can define project categories to create classifications for projects such as maintenance, capital, construction, and so on. Refer to the Project Category Definitions section for more information and field descriptions. Oracle Utilities Work and Asset Management User Guide 102

103 About Timesheets Timesheets are used to record the amount of time that workers (labor resources) spend on activities or work orders. Once charges are entered, processing allows employees to receive proper compensation for their work and labor charges are applied to the appropriate cost buckets. Generally only each individual and the person designated as the supervisor on that individual's crew can access timesheet information for that person. Refer to the Timesheet Detail Definitions section for more information and field definitions. Time Periods Your organization must create time periods to define valid from and to dates for labor costing and timesheet reporting. Time periods have to be distinct and cannot overlap. When a new timesheet is created, the system defaults to the current time period. Refer to the Time Period Definitions section for more information and field definitions. Labor Earning Types Labor earning types define earnings codes for your organization which includes an adder and a multipler to calculate labor costs. Refer to the Labor Earning Type Definitions section for more information and field definitions. Overtime Types Overtime types define overtime codes for your organization which includes a multiplier to calculate the premium rate that workers earn for overtime. Refer to the Overtime Type Definitions section for more information and field definitions. Shift Types When workers book time, they also specify the shift type they worked. Different shift types have different multipliers and adders which impact the labor costs. Timesheets can only specify daily shift types (as opposed to weekly shifts). About Preventive Maintenance Preventive maintenance is work that is routinely performed to prevent asset failure. This maintenance includes work such as inspections, repairs, part replacements and so on. Preventive maintenance can help your organization manage costs by reducing downtime due to unexpected asset failures, reducing incidents where maintenance is needed in response to a problem (reactive maintenance), and ensuring the proper care and maintenance of assets. One common example of preventive maintenance is routine oil changes on any vehicle. It is clear that proper vehicle maintenance depends on timely oil changes to prevent costly problems, failures and repairs. Preventive maintenance programs are based on time or operational usage. Template work orders are set up to plan detailed work requirements, and the preventive maintenance functionality manages when and how the related work orders are automatically created based on the established preventive maintenance cycles. Refer to the Preventive Maintenance Object s section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 103

104 About Preventive Maintenance Schedules Preventive maintenance schedules contain a basic list of maintenance triggers and a schedule of when maintenance should occur based on those triggers. For example, typical maintenance triggers would be when a car reaches a certain number of miles, when a certain amount of time has passed, or when an asset reaches a certain number of hours of runtime. Maintenance schedules provide a comprehensive set of analytics which provide information on failure types, failure modes, and repairs. Refer to the Preventive Maintenance Schedule Definitions section for more information and field definitions. About Preventive Maintenance Triggers Preventive maintenance triggers indicate a certain event which, when it occurs, maintenance should be done on an asset. For example, typical maintenance triggers would be when a car reaches a certain number of miles, when a certain amount of time has passed, or when an asset reaches a certain number of hours of runtime. Maintenance triggers are generally defined as one of the following: Calendar Anniversary is a fixed calendar interval type where regardless of the time lapse between the work creation and completion, the future maintenance schedule date remains the same. This type of interval scheduling is generally used to fulfill regulatory compliance for inspections and licensing requirements on fixed date schedules. For example, this would trigger an inspection every three months regardless of when the last inspection was completed. Runtime Anniversary is fixed interval type maintenance where regardless of the metered operation between the recent activity or service history and completion of work, the maintenance is not re-forecast. For example, this would trigger an inspection after every 100 hours of runtime service. Calendar Interval is a fluid interval type where the forecasted scheduled date is adjusted and re-forecast based on the completion date of the previously completed work which is managed through service history. For example, this would trigger an oil change every 3 months with the next trigger based on the most recent oil change. Runtime Interval is a fluid interval type where the maintenance schedule is adjusted and reforecast based on the completion runtime readings of the previously completed activity. For example, this would trigger an oil change every 3000 miles with the next trigger based on the odometer reading at the time of the last oil change. Refer to the Preventive Maintenance Trigger Definitions section for more information and field definitions. About Preventive Maintenance Calendar Preventive maintenance calendars establish work calendars with explicit effective dates and schedule dates. These are used to schedule activities created by preventive maintenance triggers. The main function of the calendar is to allow direct control over scheduled work dates. Refer to the Preventive Maintenance Calendar Definitions section for more information and field definitions. About Preventive Maintenance Asset Location Selection Preventive maintenance asset location selection allows you to create preventive maintenance specific to asset location. This functionality works with asset location specific template work orders which are used to plan for activities and resources which are specific to an asset location (where the asset is installed). This type of template cannot be used in the maintenance schedules which are configured for asset specifications. This type of template can be used in situations where there is an activity dependency. For example one activity must be performed at one specific location before the activity can be performed at a second location. This might apply, for instance, if a system needs to be shut down at a valve so that downstream components can be rebuilt or cleaned. Oracle Utilities Work and Asset Management User Guide 104

105 About Reliability Centered Maintenance (RCM) Reliability centered maintenance is a process which helps to ensure that assets run without fail. Define failure types, failure modes, failure repairs, failure components and failure profiles within the system, and use these elements together to form a comprehensive RCM system. Effective use of RCM can increase cost effectiveness, improve machine uptime, and help your organization to understand the level of risk you have undertaken with certain assets. Generally an RCM process includes the following: Define Failure Modes Effects and Critically Analysis (FMEA): FMEA is a design tool to systematically analyze component failures and identify the resulting effects on system operations. Identify assets, asset functionality, and the standards of performance for those assets. List all possible ways that the assets could fail and provide the required functions Provide detail on the types of events that could cause these failures Identify the effects on the system when failures happen Apply RCM Indicate the maintenance that can be performed to prevent or avid such failures. This maintenance contains cost effective tasks to preserve functions that are important to the system. In using RCM, your organization must define the following according to your business practices: Failure Types Represents the specific manner or way by which a failure occurs in terms of failure of the part. This may generally describe the way a failure occurs such as due to corrosion, debris, or distortion. Failure Mode Describes what has failed. Failure Repairs Indicates the repair that will be performed on the asset in case of failure. Failure Component Indicates the part of the asset for which the failure has occurred. Failure Profiles Groups valid failure types, failure modes and failure repairs into a profile which are attached to an asset type to define valid failure information for assets of that type. About Completion Events Completion events are used to execute business events within the application. For example, completion events may be configured for several types of asset processing such as asset update, state transition, replication, service history and activity creation. All activities have a set of required and optional completion events that can be executed to see the activity to completion. The Relationship Information section shows any other system objects that are associated to the completed object. For example, if you are looking at the completion event for an activity, the relationship information shows the asset, any components, the location, service history, etc. Completion Event Common Attachments Attachments added here are used as part of the completion event processing. For example, a completion event may be used to update a picture or other supporting file about an asset. Refer to the Completion Event Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 105

106 About Completion Event Types Completion event types are used to define completion events. For example, completion event types might be configured for several types of asset processing such as asset installation, asset removal, replication, service history creation, and activity creation. Completion event types are referenced on activity types to indicate which completion events should be included as part of the lifecycle of activities of that type. As examples, this can affect when service history is created for an activity, and the disposition of the assets on an activity as the activity is processed. Note that if you add activity types to the completion event type, you cannot set whether or not the completion event type is required for the activity type. Add the completion event type to the activity type using the Activity Type portal to also set the completion event types as optional or required. Refer to the Completion Event Type Definitions section for more information and field definitions. About Inbound Communication The Inbound Communication portal provides details related to the information received from an external system such as Oracle Utilities Mobile Workforce Management. Use inbound communication to create a completion event using information defined within the raw message coming from an external system. Inbound communication events receive completion event information from the external system and then process the necessary transactions to see the activity or other event to completion. This applies when completing tasks such as installing or inspecting meters or upgrading firmware. Please refer to the Inbound Communication Definitions section for more information and field definitions. Working with Work Management Administration The following sections provide information on tasks associated to creating and maintaining the administrative records needed for work management. Defining a Maintenance Manager Navigate to the Maintenance Manager portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the maintenance manager record: Note: This list does not represent required fields. User ID Refer to the Maintenance Manager Definitions section for more information. Defining a Planner Navigate to the Planner portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the planner record: Oracle Utilities Work and Asset Management User Guide 106

107 Note: This list does not represent required fields. User ID Refer to the Planner Definitions section for more information. Defining an Activity Type Navigate to the Activity Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the activity type record: Note: This list does not represent required fields. Service Class Completion Event Type (should be configured for the specific type of activity) Refer to the Activity Type Definitions section for more information. Defining Completion Event Types Navigate to the Completion Event Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the completion event type record: Note: This list does not represent required fields. Activity Type Refer to the Completion Event Type Definitions section for more information. Defining Time Periods Navigate to the Time Period portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Time Period Definitions section for more information. Defining a Labor Earning Type Navigate to the Labor Earning Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Labor Earning Type Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 107

108 Defining an Overtime Type Navigate to the Overtime Type portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Overtime Type Definitions section for more information and field definitions. Defining a Project Category Navigate to the Project Category portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. The project category is referenced when creating project. Refer to the Project Category Definitions section for more information and field descriptions. Working with Work Management The following sections provide information on tasks associated to working with work management. Refer to the Understanding Work Management section for a conceptual overview of this functional area or to the Work Management Object s sections for more information and field definitions. Working with Work Requests The following sections provide information on tasks associated with creating and maintaining work requests. Creating a Work Request Manually Navigate to the Work Request portal under Work Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the work request record: Note: This list does not represent required fields. Asset ID Work requests can be created manually or they can be sent from an external system as part of your integrated work creation processing. As applicable, after the work request is created, the system displays a list of possible duplicate requests. This is based on whether or not there are requests that are not in canceled or work order created status with the same asset or location (including address) of the current work request. If it appears that the request you just created is a duplicate, you can cancel it under Record Actions. Depending on your business practices, the next step is to submit the work request for approval. Oracle Utilities Work and Asset Management User Guide 108

109 Creating a Work Order or Activity from a Work Request Use this procedure to create a work order or activity from a work request. 1. Search for and select the appropriate Work Request record. 2. Click the Create Work button. 3. The system creates the work order based on the details in the work request. Alternately, you can create an activity directly from the work request. Finding Duplicate Work Requests Use this procedure to verify that a newly created work request is not a duplicate. Reviewing for duplicate requests is usually done before submitting the work request for approval, or it is the responsibility of the approver to search for duplicates before responding with an approval decision. 1. Search for and select the appropriate Work Request record. 2. Navigate to the Possible Duplicate WRs/WOs/Activities As applicable, after the work request is created, the system displays a list of possible duplicate requests. This is based on whether or not there are any work requests, work orders or activities in non-final statuses (such as created, pending approval or approved ) with the same asset and location (including address) of the current work request are listed as duplicates. You can choose to include or exclude work records related to preventive maintenance. If it appears that the request you just created is a duplicate, you can cancel it under Record Actions. 3. Click the link to any of the listed records to review further information as needed. Working with Work Orders and Activities The following sections provide information on tasks associated to working with work orders, activities and completion events. Creating a Work Order Navigate to the Work Order portal under Work Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: s referenced by the work order record depend on the type of work order being created. Please refer to the Work Order Definitions section for more information. Also see Creating a Work Order or Activity from a Work Request. The work order must have at least one activity added before it is submitted for approval. Creating a Template Work Order Navigate to the Template Work Order portal under Work Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the equipment record: Note: This list does not represent required fields. Oracle Utilities Work and Asset Management User Guide 109

110 Planner Approval Profile Refer to the Template Work Order Definitions section for more information. Creating a Purchase Requisition from a Work Order Use this procedure to create a purchase requisition from a work order. When a work order is created with requirements for direct purchase stock items, the action of seeing the work order through the approval process and setting it to Active status will prompt the system to generate a purchase requisition with line items for approved resources grouped by stock item detail, vendor location and blanket contract. Creating an Activity Use this procedure to create an activity from the Activity portal. 1. Navigate to the Activity portal under Work Management and select Add. 2. Select the appropriate activity type and click Ok. Activity type determines the business information required to create the activity. Typically your organization will have configured types for specific tasks such as replicating assets, installations, performing maintenance, or completing inspections. 3. Enter fields as required by your business process and save. Processing and completing activities is completed as a separate task. Generating Activities in Batch Processing Use this procedure to generate activities from a work order using batch processing. A work order of any kind except service schedule type is created and in Open status. 1. Search for and select the appropriate work order. 2. Click the Generate Activities button. The dialog to generate activities from the work order opens providing information on the number of activities that will be created and allowing you to verify whether you want to generate the activities immediately, or generate them in batch processing. 3. Click the Generate in Batch button. The work order remains in Open status and the activities are scheduled to be created when batch processing runs. If the system encounters any errors while generating activities, ToDo entries are created as designated by your system configuration. NOTE: Service schedule type work orders do not have the button to generate in batch since they are automatically set to be generated by batch processing. Oracle Utilities Work and Asset Management User Guide 110

111 Adding an Activity to a Work Order on the Work Order There are many ways to manage activities and work orders, and your specific business practices will determine how you create activities. This section describes a basic procedure for adding an activity to a work order from within the work order record. 1. Navigate to the Work Order portal under Work Management and search for and select the appropriate work order. 2. Click the Add Activity link in the Activity Info section. 3. Select an Activity Type and click Ok. 4. Complete the required fields according to your business practices and Save. The system inserts the work order number as a default. Adding Resource Requirements to an Activity Use this procedure to add resource requirements to an activity. Resource requirements are indicated at the activity level, not on the work order. 1. Navigate to the Work Order portal under Work Management and search for and select the appropriate work order. Alternately, you can search for and select the activity directly in the Activity portal under Work Management. 2. Navigate to the Activity Info zone and click the link for the appropriate activity. The activity opens displaying all of the relevant details. 3. Navigate to the Resources tab. Use the Quick Add zone to add resources. 4. Select the Resource Class from the drop-down. Typically this will add a craft, equipment, material, or other resources. After selecting a class, fields are displayed to complete the needed details. 5. Complete the required fields according to your business practices and Save. The system adds the requirements to a list under the activity on the work order as well as in the Activity Resource Action zone in the Resources tab on the activity. Click the link for any resource to navigate to the record for that resource. As the requirements are fulfilled they are moved to the Activity Resource Detail section where you can revew the follow up items that have been created to fulfill the request. For example, this section will show the material request and issue transactions needed for a material/stock requirement. Likewise it shows the purchasing documents created to fulfill direct purchase requirements, and so on. Processing and Completing Activities Use this procedure to process and complete an activity. For ad hoc and local activities, or activities that are not worked from an external system, it is necessary to process and complete the activity within the system after the activity has been physically completed. Activities should have already been generated from their respective work orders, as applicable. 1. Navigate to the Work Order portal in Search mode. 2. Search for and select the appropriate activity. Oracle Utilities Work and Asset Management User Guide 111

112 3. Locate the Completion Event Tree. 4. Click the Add icon next to the completion event type for the completion event that needs to be processed. Some of the listed completion event types might be for completion events that are required or optional. You must process each of the required types. Your business processes determine whether or not you need to process the optional ones. The completion event screen opens. 5. Fill in the completion event information as appropriate to your business processes and save. The way that you fill in the fields depends upon the type of activity and the type of completion event. 6. Return to the activity record. Depending on the type of completion event you may not automatically navigate back to the activity. For example, if the activity is to create service history, you might navigate to the service history screen, or you might navigate to the completion event record itself if the activity is for asset creation. Complete actions from the screen that the system opens, or select the hyperlink to the activity to return to the activity. 7. Click Complete in the Record Actions section. The system processes the completion event and transits the activity as appropriate to the requirements established by the activity type. If there are any errors in processing these are noted on the activity and To Do Entries are created and sent as needed. Manually Creating Completion Events Use this procedure to create a completion event manually. Completion events are most often created upon successful receipt of inbound communications related to an activity or command, and are used to create or update data to reflect the effect of activity. However, completion events might be created manually to process ad hoc or local activities. Users can create completion events using the following procedure: 1. Navigate to the Completion Event portal under Work Management and select Add. 2. Search for or enter an Activity ID. 3. Select the Completion Event Type. 4. Click Ok. 5. Enter required information as needed and save. Refer to the Completion Event Definitions section for more information. Manually Creating an Inbound Communication Use this procedure to create an inbound communication manually. Inbound communications are most often created upon successful receipt of completed activities from an external system such as Oracle Utilities Meter Data Management. They are used to create or update data to reflect the effect of activity. Inbound communications might be created manually, however, to process ad hoc or local activities. Users can create inbound communications using the following procedure: 1. Navigate to the Inbound Communication portal under Work Management and select Add. 2. Select the appropriate communication type. Communication type determines the required fields that need to be entered to create the inbound communication. 3. Enter required information as needed and click Save. Oracle Utilities Work and Asset Management User Guide 112

113 Refer to the Inbound Communication Definitions section for more information and field definitions. Working with Projects The following sections provide information on tasks associated with creating and maintaining projects. Creating a Project Navigate to the Project portal under Work Management, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the project record: Note: This list does not represent required fields. Project Category Cost Center To create a subproject, create a new project record then reference a Parent Project. After at least one sub-project is created you can select the Add Sub-Project link from the Project Detail Info section to create additional sub-projects. A Refer to the Project Definitions section for more information and field definitions. Viewing Subproject Information 1. Navigate to the Project portal under Work Management and select Search. 2. Search for and select the appropriate Project record. 3. Navigate to the Project Detail Info section. Here you can review the subproject details, navigate to subprojects, and add more sub-projects as necessary. Working with Preventive Maintenance The following sections provide information on tasks associated with creating and maintaining preventive maintenance objects. Creating a Maintenance Schedule Navigate to the PM Schedule portal under Preventive Maintenance, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the maintenance schedule record: Note: This list does not necessarily represent required fields. Asset Type Specification After creation, maintenance schedules can be linked to an asset specification to plan for the maintenance of related assets. Refer to the Preventive Maintenance Schedule Definitions section for more information. Oracle Utilities Work and Asset Management User Guide 113

114 Creating a Maintenance Trigger Navigate to the PM Trigger portal under Preventive Maintenance, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the maintenance trigger record: Note: This list does not necessarily represent required fields. Maintenance Schedule Template Work Order Activity Type Approval Profile Asset Location Failure Information (Type, Mode, Repair, Component) Refer to the Preventive Maintenance Trigger Definitions section for more information. Oracle Utilities Work and Asset Management User Guide 114

115 Chapter 8 Financials The following sections provide information about the portals and objects related to financial transactions throughout the system. Understanding Financials Financials management involves creating and managing entities such as expense codes, distribution codes, cost centers, cost categories, business units, tax rate schedules, accounting calendars, and so on. This section describes how various processes work together to manage financial transactions and related objects throughout the system. Please refer to the Working with Financials section for procedural tasks related to these concepts. About Financial Transactions Financial transactions are created in the system whenever an object generates a cost transaction. For example, the posting of a timesheet or other direct charges causes the creation of a financial transaction. Authorized users can access this accounting log at any time to review transactions. You can search for financial transactions according to the corresponding work order, activity, creation date, status, and so on. They can be viewed in the Financial Transaction portal. Financial transactions are automatically frozen immediately after they are created and the transactions that created them, sibling transactions, are finalized. For example, a material issue or a timesheet detail are considered the siblings to the financial transactions that they created. Once frozen, a financial transaction and its details are ready to be interfaced to the general issues. The system does not depend on batch processing to transition financial transactions between states. Instead, a batch GL interface program extracts frozen financial transactions and creates a flat file. If there happen to be any accounting setup issues or other issues, a financial transaction will enter an error state until an authorized user adjusts the configuration or other source of the issue. Refer to the configuration guide for more information. The error state allows any sibling transactions to continue and complete without being affected by the related transaction which is in error. Oracle Utilities Work and Asset Management User Guide 115

116 The system uses double entry accounting. For example, when time is booked against an activity, the system debits the cost centers on the activity and credits an offset account. In this case the offset account would be the payroll cost center defined on the crew member/employee's business unit. About Accounting Calendars Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application. As part of your general configuration your organization will define the accounting calendar in the Accounting Calendar portal then designate that calendar as the default in Financial Master Configuration. Only one accounting calendar is allowed for the entire system. Accounting calendars include a series of accounting periods with a start and end date. They also specify to and from dates when the calendar is open or when transactions can be posted to that calendar. Refer to the Accounting Calendar Definitions section for more information and field definitions. About Currency The overall system uses the base currency defined in Installation Options, and all financial transactions use the base currency. However, the purchasing system supports other currencies which can be defined in the Currency portal. Enter standard currency codes such as USD or GBP, a description, symbol and the number of decimal places to use. The currency code will then appear as an option wherever a currency code is required on purchasing records, such as on a blanket contract or purchase order. Any currency codes used in the purchasing system which are different from the base currency are converted into the base when the system creates financial transactions. About Colors Your organization can use the Colors portal to define custom colors used to represent transactions and other entities throughout the system. For example, colors defined here are used to distinguish cost categories as they are represented in graphs and/or pie charts throughout the system. Colors defined in this module are also used as the fill or outline color when Shapes are defined. The Color record provides a hex value, description and color sample. Once this is defined, the color can be specified on the Cost Category record as the designated color for that category. Each color should only be referenced by one cost category. Colors are also used when defining Shapes, to specify a fill color or outline color. Please refer to the Color Definitions section for more information and field definitions. About Cost Category Cost categories group expenses or costs into logical buckets for reporting purposes. The following details apply for cost categories: Each expense code references a cost category. Each cost category can be assigned a specific color so that the category is represented by that color in graphs and pie charts throughout the system. Each color should only be referenced by one cost category. Refer to the Cost Category Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 116

117 About Cost Centers As costs are incurred, the system tracks them and accumulates them at different levels or cost centers within your organization. Cost centers are part of the accounting hierarchy. Cost center records display financial statistics such as a budget amount, year to date actual amount, and committed amount for the cost center. These amounts represent the fiscal year rather than the actual year. A monthly statistics section also allows you to display more detailed information by month in a graph. General ledger account numbers are a concatenation of the cost center, project, and expense code, as applicable. Refer to the Cost Center Definitions section for more information and field definitions. About Expense Codes Expense codes are codes assigned to a financial expenditure indicating which payment category the cost falls into. They are part of the accounting hierarchy. Expense codes reference a cost category, resource class, and an account segment. This means that each expense code is only valid for a particular resource class (labor, material, equipment or other), and must be defined accordingly. General ledger account numbers are a concatenation of the cost center, project, and expense code, as applicable.. Refer to the Expense Code Definitions section for more information and field definitions. About Business Units Business units are used as cost reporting entities for timekeeping expenses. Employees are associated with a specific business unit so that when they report time charges, the costs are charged against that business unit. The system uses double entry accounting. For example, when time is booked against an activity, the system debits the cost centers on the activity and credits an offset account. In this case the offset account would be the payroll cost center defined on the crew member/employee's business unit. Refer to the Business Unit Definitions section for more information and field definitions. About Factors and Factor Values Factors are defined by your organization as a tax component needed to calculate tax values related to anything which incurs costs for your organization and must be taxed (such as purchases and resources used to complete activities). For example, you might define different factors for city tax, state tax and federal tax. Each type of factor would define a factor values list providing numerical values used to calculate the tax. The factor is then referenced on a Tax Rate Schedule. Refer to the Factor Definitions section or the Factor Value Definitions section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 117

118 About Tax Rate Schedules A Tax Rate Schedule defines the type of taxes that are applicable at various instances in time for related resources (materials, labor, equipment, and other). The tax rate can be defined on a resource type, but this can be overridden for specific storerooms if necessary. Your implementation will need to configure attributes so that tax rates are included on purchase requisitions, purchase orders and blanket contracts. Refer to the configuration guide for information about defining tax rates and how to incorporate them into purchasing documents during your implementation. Please refer to the Tax Rate Schedule Definitions section for more information and field definitions. About Distribution Codes Distribution codes simplify the process of generating accounting entries by defining valid combinations of values for charts of accounts. The system uses the distribution code as a flexible way to construct the final account number to send to the GL system. That algorithm can be coded to construct the final GL account number from data available anywhere in the system. When creating distribution codes you specify the general ledger account algorithm that will be used by the system when it interfaces financial transactions that reference this distribution code to the general ledger. This account algorithm will construct the actual GL Account Number. For example, the base algorithm constructs the account by concatenating account segments from cost center, project and expense code. If some accounts are static and do not need dynamic construction, the entire account number can be defined in the GL Account Detail and a simple algorithm can retrieve the account number from the same distribution code. Refer to the configuration guide for more information on the GL algorithm setup. Please refer to the Distribution Code Definitions section for more information and field definitions. Working with Financials The following sections provide information on tasks associated to working with financials. Refer to the Understanding Financials section for a conceptual overview of this functional area or to the Financial Object s sections for more information and field definitions. Creating an Accounting Calendar Navigate to the Accounting Calendar portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Accounting Calendar Definitions section for more information. Oracle Utilities Work and Asset Management User Guide 118

119 Defining Currency Navigate to the Currency portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: Once currency must be defined in Installation Options as the system's base currency. Defining a Color Navigate to the Color portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Cost categories will need to reference a unique color. Refer to the Color Definitions section for more information and field definitions. Defining a Cost Category Navigate to the Cost Category portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the cost category record: Note: This list does not represent required fields. Color you must have a unique color to represent each cost category. Expense codes will need to reference a cost category. Refer to the Cost Category Definitions section for more information. Defining a Cost Center Navigate to the Cost Center portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: : The following are referenced by the cost category record: Note: This list does not represent required fields. Expense Code Add Valid Expense Codes to the cost center after it is defined, as required by your business practices. This is determined by the Financial Master Configuration. Refer to the Cost Center Definitions section for more information and field definitions. Reviewing Cost Center Statistics Use this procedure to review cost center statistics. 1. Navigate to the appropriate Cost Center record in Edit mode. 2. Search for and select the cost center with the statistics to review. 3. Click the Accumulate Monthly Statistics button. Oracle Utilities Work and Asset Management User Guide 119

120 The system renders the graphs or pie charts to represent the statistics in the Cost Center Monthly Statistics section. Deactivating a Cost Center Use this process to deactivate a cost center. Cost centers must be in active status to be referenced elsewhere in the system. 1. Navigate to the appropriate Cost Center record in Edit mode. 2. Search for and select the cost center that should no longer be used. 3. Click the Deactivate button. Defining an Expense Code Navigate to the Expense Code portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the expense code record: Note: This list does not represent required fields. Cost Category Expense codes must be in active status to be used. Cost centers reference a list of valid expense codes, as required by your business practices. Refer to the Expense Code Definitions section for more information and field definitions. Deactivating an Expense Code Use this process to deactivate an expense code. Expense codes must be in active status to be used. 1. Navigate to the appropriate Expense Code record in Edit mode. 2. Search for and select the expense code that should no longer be used. 3. Click the Deactivate button. Defining a Business Unit Navigate to the Business Unit portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the business unit record: Note: This list does not represent required fields. Payroll Cost Center Oracle Utilities Work and Asset Management User Guide 120

121 Defining a Factor Navigate to the Factor portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Add factor values in the Factor Characteristic Values section after creating the factor. Tax rate schedules will need to reference a factor. Refer to the Factor Definitions section for more information. Defining a Tax Rate Schedule Navigate to the Tax Rate Schedule portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: The following are referenced by the tax rate schedule record: Note: This list does not represent required fields. Factor Cost Center Expense Code Defining a Distribution Code Navigate to the Distribution Code portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: Refer to the configuration guide. Refer to the Distribution Code Definitions section for more information. Reviewing a Financial Transaction Review financial transactions by navigating to the Financial Transactions portal and searching by specific criteria. Prerequisites: Transactions have posted to the accounting calendar. 1. Navigate to the Financial Transaction portal in Edit mode. 2. Search for and select the appropriate transaction. You can search by activity or work order ID, create dates, accounting date, status, or the financial transaction ID. 3. Click the link to the specific transaction to review more information such as the transaction log, related records such as work order or activity, and the general ledger details, as applicable. Oracle Utilities Work and Asset Management User Guide 121

122 Chapter 9 General Administrative Functionality This section provides information about miscellaneous administrative functions which may be used by your organization. About Access Control Access control provides a way for your organization to limit or classify record information by "plant" or varying work locations. For example, you may have an asset type that is only used at your northern location, so you would use an access type to designate that asset type as restricted to that location. Many administrative records throughout the system can specify an Owning Organization and an Instance Organization which, combined, allow you to choose which work location applies for the entity being created. The options for these fields are defined in the Access Group portal. About Statistics The Statistics portal captures metrics that are collected via batch processing. These embedded analytics are not present in real time, but rather are accumulated and presented as they are processed by batch. These analytics are displayed on the Home Page. This portal is mainly used as a method to speed up the processing associated with presenting complex statistics or statistics that represent a large amount of data. Processing these in batches rather than in real time significantly increases system performance. Authorized uses can also use the portal to manipulate the statistical data that is displayed on the Home Page such as selecting crews or dates. The Log tab tracks who made changes to the data, and when. Refer to the Statistics Definitions section or the About the Home Page section for more information and field definitions. Oracle Utilities Work and Asset Management User Guide 122

123 Understanding Communications Administration Communications administration involves creating, maintaining and working with communication types. This section describes communication types and how to create them. About Communication Types Communication types define the information required for the system to receive messages from external systems. Communication Data Mapping Communication Data Mapping information is used to populate communication business object elements from information within the inbound communication's raw message. Refer to the Communication Type Definitions section for more information and field definitions. Attachment Suppression When a message is received from an external system, the message may contain attachment data which is very large. The substitution text entered in this section can be used in place of that large data in the completion event list on the inbound communication. The attachment element xpath identifies the data to match it to the substitution text. This serves to prevent transfer delays in cases where large amounts of data might overload the browser. Defining Communication Types Navigate to the Communication Types portal under Admin, select Add, complete the required fields according to your business practices and Save. Prerequisites: None. Refer to the Communication Type Definitions section for more information. Oracle Utilities Work and Asset Management User Guide 123

124 Chapter 10 Business Objects/ s The following sections provide descriptions of the base attributes and valid statuses, as applicable, for the records and screens that are defined by base package business objects and maintenance objects. For detailed information on the related functionality, please refer to the specific sections for these objects throughout this guide. Approval Object s This section provides descriptions of the attributes used for approvals related objects as they are delivered in the base application. Refer to the Understanding Approvals section for a conceptual overview. Approval Profile Definitions Approval profiles are used to define the approval hierarchy within your organization. Refer to the Defining an Approval Profile section for more information. Amount Based Approval Profile Business Object: W1-AmtBasedAppvlProf This is the approval profile used when the record requiring approval involves dollar amounts such as a purchase requisitions or work orders. Approval Profile: Unique name for the approval profile. It is recommended that your organization name approval profiles according to their function or type of document that they are set to approve. Oracle Utilities Work and Asset Management User Guide 124

125 : of the approval profile which appears in drop down lists. It is recommended that your organization include the profile function or type of document in the description so that it is easy to identify when selecting from a drop down list. Work Calendar: Indicates the work calendar affecting the timeout threshold affecting the approval profile. For example, if the work calendar excludes Mondays, the system will not consider a Monday when calculating the timeout for the approval request. Document Type: Indicates the type of record that this approval profile applies to such as employee unavailability, other direct charges, purchase order, purchase requisition, project, work order, work request, and so on. Approval Request Business Object: Indicates the kind of approval request to create for this approval profile. This is only relevant if your organization has defined multiple approval request business objects to designate different kinds of approval requests. No Approval Limit: This value represents the dollar amount where nor approval is required. If the requested amount on the document requiring approval is less than or equal to the value entered in this field, the record does not require approval. Approval Information fields Hierarchy fields Defines the To Do Type that used for the approval profile. Defines the approval path followed when a record is submitted for approval to this approval path. Sequence: Defines the order in which each of the To Do Roles entered must approve the record. This is relevant when there are multiple To Do Roles and one approval is dependant on the next. For example, the first role might be a manager, then if they approve, the next might be a director or senior manager. To Do Role: Indicates the To Do Role designated to approve the record. Approval Type: Indicates whether this is a standard, mandatory or notification only role. Standard: A standard approver might appear on the approval hierarchy with other approvers with equal approval authority. Any standard approver can record the decision before the record moves on to the next approver in the hierarchy. Mandatory: Indicates that this approver must provide an approval decision on the record. Approval processing is not complete until this decision is recorded. Notification Only: Notification only approvers are only sent an alert that the approval is pending. The system does not validate an amount limit and the approver does not have to respond in order for the record to be approved. Initial Notification Method: Indicates whether the approver receives an , an alert in their To Do List, both or none. Amount Limit: Provides the maximum amount that the approver in the indicated role is allowed to approve. If the value on the record in need of approval exceeds this limit for the role, the approval path must move on to the next approver or the requestor is notified that no one on the approval profile has sufficient authority to approve the request. Timeout Threshold: Indicates the amount of time that the approver has to respond to the approval request, in days. For example, if the threshold is set to 2, the approver has 2 days to approve requests. If the approver does not respond within the set time, another alert is sent. Additional alerts are sent up to the set number of retries. Maximum Retry: Indicates the number of times that the system will retry sending the approval request to approvers with the ToDo Role before timing out the request. For example, of the Timeout Threshold is set to 2 and the Maximum Retry is set to 3 the system will try three times for a total of 6 days resending the alert or every 2 days. If the approvers fail to respond, the request is routed to the next approver in the hierarchy and that person receives the or alert. Oracle Utilities Work and Asset Management User Guide 125

126 Non-Amount Based Approval Profile Business Object: W1-NonAmtBasedAppvlProf This is the approval profile used when the record is not dependant on a dollar amount, such as employee unavailability or timesheet. This business object uses the same fields as W1-AmtBasedAppvlProf with the following exceptions: Approval Profile: See above. : See above. Work Calendar: See above. Document Type: See above. Approval Request Business Object: See above. No Approval Limit: n/a since this type of approval profile does not depend on dollar values. Approval Information fields Hierarchy fields See above Defines the approval path followed when a record is submitted for approval to this approval path. Sequence: Same as above. To Do Role : Same as above. Approval Type: Same as above. Initial Notification Method: Same as above. Authorized to Approve: When multiple To Do Roles are added to the profile, this field identifies which is authorized to approve. At least one to do role must be added with this value set to Yes. Timeout Threshold: Same as above. Maximum Retry: Same as above. Hierarchy fields See above No Approval Required Approval Profile Business Object: W1-NoAppvlRequiredProf This is the approval profile used in situations where approval processing should be used, but the record should be approved automatically. This might be applicable for emergency work orders or work requests. This business object uses the same fields as W1-AmtBasedAppvlProf with the following exceptions: Approval Profile: See above. : See above. Work Calendar: n/a Document Type: See above. Reason: Provides a reason for the approval, such as emergency. Reasons are defined in the Status Reason portal under the Admin menu. Approval Request Business Object: See above. Oracle Utilities Work and Asset Management User Guide 126

127 User Groups Approval Information fields Hierarchy fields No Approval Limit: n/a Indicates the user groups that can create an approval request routed to the indicated approval profile. This helps to control which users are allowed to submit no approval requests. User groups are defined as a listing of user profiles in the User Group portal. n/a n/a Approval Request Definitions Records within the system, such as purchase orders or work requests, often require an authorized person to provide approval for the purchase or work. Approval requests are used to route the request for approval to the appropriate individuals with the authority to approve or reject the request. Business Object: W1-ApprovalRequest Approval Profile: The approval profile designated to approve the request. Requested By User: User ID of the person initiating the approval request. Requested Amount: Indicates the dollar value on the request, as applicable. Request Date Time: The date and time that the request is initiated. Due Date: The date by which the approval request must receive a decision/response. Current/Future approver fields Historical Information fields Status (from the BO lifecycle) Indicates where the approval request is currently (which To Do Role has it), and what kind of approval type the To Do Role is configured to perform (mandatory, standard, or notification only). The current To Do role appears in the approval dashboard. If no action is taken in the allotted time, the approval request advances to the next future To Do Role. Approvers with that role will then be notified. Indicates the user ID and To Do Role of anyone who responded on the approval request with a decision. This section also shows the decision and the date that the decision was recorded. Determine Approvers Approval In Progress Approved No Approval Necessary Rejected Cancelled Final Approved Asset Management Object s This section provides descriptions of the attributes used for all asset related objects as they are delivered in the base application. Refer to the Understanding Asset Management section for a conceptual overview of this functional area. Oracle Utilities Work and Asset Management User Guide 127

128 Asset Object s This section provides descriptions of the attributes used for asset types, assets, components, and asset locations as they are delivered in the base application. Asset Type Definitions Asset types define the attributes for assets of a certain type. Refer to the Defining Asset Types section for more information. Asset Type Business Object: W1-AssetType Defines the attributes for assets of a certain type. Asset Type: The unique name for the asset type. : which appears in drop-down lists. Component Relationship: Indicates whether or not assets of this type can have attached components. Asset Category: An additional classification for the asset. Asset Business Object: Indicates the business object that will be used when creating assets of this type. Assessment Class: Indicates the assessment class that will be used when creating inspections for assets of this type. Valid Location Types fields Defines a list of location types where assets or components of this type can be attached. Asset Disposition: Determines the status required for the location type when an asset of this type is attached. Location Type: Defines a valid list of location types where assets of this type can be attached. Valid Service History Types fields Service History Type: Defines a list of service history types that can apply for assets of this type. Service history is entered as a record of work, inspections or other service on the asset or component. Asset Type Average Cost Business Object: W1-AssetTypeAveCost Defines an asset type with average cost per category statistics. Failure Profile field Valid Location Types fields Valid Service History Types fields See W1-AssetType. Failure Profile: Indicates the failure profile that will be used as default for assets of this type. The failure profile identifies the failure codes and information used to define the Reliability Centered Maintenance (RCM) system used to evaluate the asset. See W1-AssetType See W1-AssetType Oracle Utilities Work and Asset Management User Guide 128

129 Asset Average Costs fields Provides a summary of the average costs grouped by the asset type then by cost category (such as repair, inspection or maintenance). This retrieves all cost related information from the Service History Type for assets of the type. Cost Category Average Cost Status (from the BO lifecycle) Valid statuses include: Active Component Type Definitions Asset types define the attributes for assets of a certain type. Component Type Business Object: W1-ComponentType Defines the attributes for asset components of a certain type. Valid Attached To Asset Types Component Relationship: n/a Asset Disposition: Determines the disposition status required for the asset type when components of this type are attached. Asset Type: Defines a valid list of asset types where components of this type can be attached. Component Type Average Cost Business Object: W1-CompTypeAveCost Defines a component type with average cost per category statistics. Asset Average Costs fields Provides a summary of the average costs grouped by the component type then by cost category (such as repair, inspection or maintenance). This retrieves all cost related information from the Service History Type for components of the type. Cost Category Average Cost Status (from the BO lifecycle) Active Asset Definitions An asset is an object in an infrastructure, such as a smart meter, poles, pipes, transformer or any other material item owned or managed by an organization. Refer to the Working with Assets section for more information. Types of Assets Oracle Utilities Work and Asset Management User Guide 129

130 Assets are typically classified as: In/Out Service: In/Out of service assets are typically stationary, such as a pole or pipe. They stay in service until they fail and are then removed from service rather than being repaired or tracked. This type of asset will be recorded at an asset location with a disposition such as in service or out of service. Tracked: Tracked assets have their status and location carefully monitored and recorded as they move in and out of service or go for maintenance or repair. This type of asset will be tracked at a location with a disposition such as in receipt, in stores, in repair, retired or rejected. If the tracked asset is installed, or put in service, it will be related to an asset location. Tracked assets utilize more statuses and a status reason to more carefully track the asset as it moves from receipt to retirement. Within these classifications, several different types of assets can be managed for your organization. These include: Plant Assets: Stationary structures such as buildings, factories, or other facilities. Fleet Assets: Vehicles including cars, trucks, and equipment such as bulldozers or forklifts. IT Assets: Technology equipment such as phones, computers and laptops, monitors. OT Assets Operational technology assets such as smart meters and manual meters. Linear Assets: Assets that can be connected with each other such as pipes or telephone poles. Infrastructure Assets: Assets that makeup general infrastructure such as roads and parking lots. Tracked General Asset Business Object: W1-TrackedGeneralAsset Identification fields Detailed Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number Pallet Number External ID SCADIA ID Vendor fields Details about the vendor or supplier of the asset. Vendor: Identifies the seller or supplier of the asset. Vendor Part Number: The vendor supplied part number for the asset. Purchase Order Line: The purchase order line item for the asset, as applicable. Specification fields Specification: Identifies the specification applicable for the asset. BOM ID: Identifies the record number for the bill of materials related to the asset. Measurement fields Specifies a list of valid measurement types to use when creating measurements for this asset. Measurement Type Status (from the BO lifecycle) The current state of the asset. Valid statuses include: In Receipt In Store Oracle Utilities Work and Asset Management User Guide 130

131 Installed In Repair Retired Rejected Pending Disposition Tracked IT Asset Business Object: W1-TrackedITAsset Identification fields See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. SCADIA ID: n/a Vendor fields General Information fields Specification fields Status (from the BO lifecycle) See W1-TrackedGeneralAsset. Employee ID: Depending on your business practices, this can indicate the employee in possession of the asset, or the responsible employee. See W1-TrackedGeneralAsset. The current state of the asset. Valid statuses include: In Receipt In Store Installed In Repair Retired Rejected Pending Disposition In Out of Service General Asset Business Object: W1-IOSvcGeneralAsset Identification fields See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. SCADIA ID: n/a Vendor fields General Information fields Specification fields Status (from the BO lifecycle) See W1-TrackedGeneralAsset. Employee ID: Depending on your business practices, this can indicate the employee in possession of the asset, or the responsible employee. See W1-TrackedGeneralAsset. The current state of the asset. Valid statuses include: In Service Oracle Utilities Work and Asset Management User Guide 131

132 Out of Service Retired In Out Service IT Asset Business Object: W1-IOSvcITAsset Identification fields Vendor fields Specification fields Measurement fields Status (from the BO lifecycle) See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. See W1-TrackedGeneralAsset. The current state of the asset. Valid statuses include: In Service Out of Service Retired In Out of Service Infrastructure Asset Business Object: W1-IOSvcInfrastructureAsset Detailed Specification fields Status (from the BO lifecycle) of the asset. See W1-TrackedGeneralAsset. The current state of the asset. Valid statuses include: In Service Out of Service Retired In Out Service Fleet Asset Business Object: W1-IOSvcFleetAsset Identification fields Detailed Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number External ID Vehicle Identification Number License Number Oracle Utilities Work and Asset Management User Guide 132

133 Vendor fields Title: Ownership documentation for the vehicle. Details about the vendor or supplier of the asset. Vendor: Identifies the seller or supplier of the asset. Vendor Part Number: The vendor supplied part number for the asset. Purchase Order Line: The purchase order line item for the asset, as applicable. General Information fields Shop: Indicates a storage location where the vehicle is stored or maintained. Responsible Party: The Employee ID of the person in charge of managing the vehicle. Depending on your business practices this might be the person in physical possession of the vehicle or a department or person simply in charge of the vehicle. Specification fields Specification: Indicates the specification that is relevant to guide work for the fleet asset. BOM ID: Indicates the record number for the bill of materials that is relevant to the parts related to work on the fleet asset. Measurement fields Specifies a list of valid measurement types to use when creating measurements for this asset. Measurement Type Status (from the BO lifecycle) The current state of the asset. Valid statuses include: In Service Out of Service Retired Asset Disposition History - Installations Business Object: W1-AssetDposHistInstallations Asset ID Asset Type Business Object Status Asset Information fields Location Asset Disposition Effective Date/Time Attached to Asset ID Oracle Utilities Meter Data Management Asset Business Object: W1-MDMAsset Defines details for assets to be used with the integration to Oracle Utilities Meter Data Management. Asset ID Oracle Utilities Work and Asset Management User Guide 133

134 Device Type Serial Number Model Measurement Configuration: Drop-down indicating the asset configuration. Measuring devices such as utility meters can be configured to have different measurement components or registers. This level of detail might not be needed for Oracle Utilities Work and Asset Management, however this field might be used to indicate the 'type' of measurement components or registers configured during an integration with another system such as Oracle Utilities Meter Data Management. Badge Number Pallet Number Status Date/Time Operational Devices Smart Meter Business Object: W2-SmartMeter Smart meters are monitoring devices that send and receive information electronically. Detailed : of the asset. Specification: Indicates the specification that is relevant to guide work for the asset, as applicable. Identification fields Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number Pallet Number PO # Settings fields Firmware and configuration information for the meter. Metrology Firmware Version: The software for the functionality of the smart meter. NIC Firmware Version: The software for the network interface card in the smart meter. Measurement Configuration: Drop-down indicating the asset configuration. Measuring devices such as utility meters can be configured to have different measurement components or registers. This level of detail might not be needed for Oracle Utilities Work and Asset Management, however this field might be used to indicate the 'type' of measurement components or registers configured during an integration with another system such as Oracle Utilities Meter Data Management. Vendor fields Details about the vendor or supplier of the asset including the part number and warranty information. Warranty Expiration Date Warranty Detail: Free form text to describe the warranty. Vendor: Identifies the seller or supplier of the asset. Oracle Utilities Work and Asset Management User Guide 134

135 Status (from the BO lifecycle) Vendor Part No: The vendor supplied part number for the asset. The current state of the smart meter. Valid statuses include: In Receipt In Store Installed In Repair Retired Rejected Manual Meter Business Object: W2-ManualMeter Manual meters are monitoring devices that must be read and have their information recorded manually. Detailed : of the asset. Specification: The related specification if applicable. Identification fields Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number Pallet Number PO # Settings fields Firmware and configuration information for the meter. Measurement Configuration: Drop-down indicating the asset configuration. Measuring devices such as utility meters can be configured to have different measurement components or registers. This level of detail might not be needed for Oracle Utilities Work and Asset Management, however this field might be used to indicate the 'type' of measurement components or registers configured during an integration with another system such as Oracle Utilities Meter Data Management. Vendor fields Details about the vendor or supplier of the asset including the part number and warranty information. Warranty Expiration Date Warranty Detail: Free form text to describe the warranty. Vendor: Identifies the seller or supplier of the asset. Vendor Part No: The vendor supplied part number for the asset. Status (from the BO lifecycle) The current state of the smart meter. Valid statuses include: In Receipt In Store Installed In Repair Oracle Utilities Work and Asset Management User Guide 135

136 Retired Rejected Communication Component Business Object: W2-CommunicationComponent Communication components are devices that can be attached to an analog meter to connect the meter to the smart communication grid. These use the same fields and statuses as smart meters with the exception that they are never installed directly at a location, but are instead attached to another asset. Detailed : of the asset. Specification: The related specification if applicable. Identification fields Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number Pallet Number PO # Settings fields Firmware and configuration information for the meter. Communication Component Firmware Version: Communication components are devices that can be attached to a smart meter to connect the meter to the communication grid. This indicates the software version for this component. Measurement Configuration: Drop-down indicating the asset configuration. Measuring devices such as utility meters can be configured to have different measurement components or registers. This level of detail might not be needed for Oracle Utilities Work and Asset Management, however this field might be used to indicate the 'type' of measurement components or registers configured during an integration with another system such as Oracle Utilities Meter Data Management. Vendor fields Details about the vendor or supplier of the asset including the part number and warranty information. Warranty Expiration Date Warranty Detail: Free form text to describe the warranty. Vendor: Identifies the seller or supplier of the asset. Vendor Part No: The vendor supplied part number for the asset. Status (from the BO lifecycle) The current state of the smart meter. Valid statuses include: In Receipt In Store Installed In Repair Retired Rejected Oracle Utilities Work and Asset Management User Guide 136

137 Communication Relay Business Object: W2-CommunicationRelay Communication relays transmit messages between various points to facilitate communication between units. These typically use the same fields and statuses as meters. Detailed : of the asset. Specification: The related specification if applicable. Identification fields Additional information such as badge number, serial number, pallet number and PO number to help further classify and identify the asset. Badge Number Serial Number Pallet Number PO # Settings fields Firmware and configuration information for the meter. Communication Relay Firmware Version: The software for the functionality of the communication relay. Vendor fields Details about the vendor or supplier of the asset including the part number and warranty information. Warranty Expiration Date Warranty Detail: Free form text to describe the warranty. Vendor: Identifies the seller or supplier of the asset. Vendor Part No: The vendor supplied part number for the asset. Status (from the BO lifecycle) The current state of the smart meter. Valid statuses include: In Receipt In Store Installed In Repair Retired Rejected Component Definitions Components are devices or other objects that are attached to another device, usually an asset. Refer to the Creating Components Manually section for more information. In/Out of Service General Component Business Object: W1-IOSvcGeneralComponent Components related to general assets. In/Out of service components are typically stationary and stay in service until they fail and need to be removed. Oracle Utilities Work and Asset Management User Guide 137

138 Identification fields Detailed Additional information such as badge number, serial number, pallet number to help further classify and identify the component. Badge Number Serial Number Pallet Number External ID Vendor fields Details about the vendor or supplier of the component including the part number and purchase order number. Vendor Vendor Part Number Purchase Order Line Specification fields Specification: Indicates the specification that is relevant to guide work for the component. BOM ID: Indicates the record number for the bill of materials that is relevant to the parts related to work on the component. Status (from the BO lifecycle) The current state of the component. Valid statuses include: Attached Out of Service Retired In Out Service IT Component Business Object: W1-IOSvcITComponent Components related to general technology assets such as phones, laptops, or monitors. In/Out of service components are typically stationary and stay in service until they fail and need to be removed. Identification fields Vendor fields General Information fields Specification fields Status (from the BO lifecycle) See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. Employee ID: Depending on your business practices, this can indicate the employee in possession of the asset, or the responsible employee. See W1-IOSvcGeneralComponent. The current state of the component. Valid statuses include: Attached Out of Service Retired Tracked General Component Business Object: W1-TrackedGeneralComponent Components related to general assets. Tracked assets have their status and location carefully monitored and recorded. Oracle Utilities Work and Asset Management User Guide 138

139 Identification fields Vendor fields Specification fields Measurement fields Status (from the BO lifecycle) See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. Specifies a list of valid measurement types to use when creating measurements for this component. The current state of the component. Valid statuses include: In Receipt In Store Attached In Repair Retired Rejected Pending Disposition Tracked IT Component Business Object: W1-TrackedITComponent Components related to general technology assets such as phones, laptops, or monitors. Tracked assets have their status and location carefully monitored and recorded. Identification fields Vendor fields General Information fields Specification fields Status (from the BO lifecycle) See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. See W1-IOSvcGeneralComponent. Employee ID: Depending on your business practices, this may be the employee who is responsible for the equipment, or the person in possession of the equipment. See W1-IOSvcGeneralComponent. The current state of the component. Valid statuses include: In Receipt In Store Attached In Repair Retired Rejected Pending Disposition Oracle Utilities Work and Asset Management User Guide 139

140 Shape Definitions Use the Shape portal to define circles or lines used to draw linear assets. For example, a manhole would be represented as a circle, whereas a pipe would be represented as a line. Shapes can specify an outline color, fill color, width, and a radius (for circles). Refer to the Defining a Shape section for more information. Circle Business Object: W1-Circle Shape: The unique name for the shape. : The description of the shape which appears in drop-down lists. Managed Content: Managed Content is used to store elements such as XSL files used to create vector charts, JavaScript include files, and CSS files. These files are used to render the circle or line. Radius: Defines the radius of a circle shape. Fill Color: Defines the color used to fill the shape when it is displayed. Outline Color: Defines the outline color used for the shape when it is displayed. Outline Width: Defines the thickness of the outline used on the shape when it is displayed. Line Business Object: W1-Line This business object uses the same fields as with the following exceptions: See W1-Circle. Radius: n/a Asset Location Type Definitions Asset location types define the details of asset or component locations of a certain type. Refer to the Defining Asset Location Types section for more information. Asset Location Type Business Object: W1-AssetLocationType A type of asset location that is used to indicate the physical location where assets or components are installed. Location Type: Unique name for the location type. : of the location type which appears in drop-down lists. Oracle Utilities Work and Asset Management User Guide 140

141 Class: Used for reporting and establishes general characteristics of the location such as whether it is commercial or residential, a shop or warehouse, or any other possible categorization appropriate to your business. Location BO: Indicates the business object to use when creating locations of this type. Number of Assets Allowed: Defines whether the location can accommodate just a single asset or multiple. For example, a parking lot where multiple poles are installed would have multiple service points whereas a single residence would only have one. Service Type: Defines the type of service that assets at the location can perform. Example service types might include natural gas, electric, disposal or water. Valid Parent Location/ Organization Types fields Defines a list of parent locations and/or parent organizations that can be referenced on a location. Parent types establish a hierarchy for reporting purposes. Parent Location/Organization Type Valid Communicate-To Location Types fields Defines a list of asset location types that asset locations of this type can communicate to. The Tree View of any asset or location in the system will show the other related assets with a visual indication of their relationships. Asset Location Type General Asset Location Type Business Object: W1-GeneralAssetLocationType A type of general asset location that is used to indicate the physical location where assets or components are installed. Valid Parent Location/ Organization Types fields Valid Communicate-To Location Types fields See W1-AssetLocationType. See W1-AssetLocationType. n/a Linear Asset Location Type Business Object: W1-LinearAssetLocationType A type of asset location that is part of a system such as pipes and manholes or poles and cables. Valid Parent Location/ Organization Types fields Connected To Location Types fields See W1-AssetLocationType. See W1-AssetLocationType. Defines a list of asset location types where this asset location can be connected. For example, in a pipe system, a pipe can be connected to a manhole. The Tree View of any asset or location in the system will show the other related assets with a visual indication of their relationships. Asset Location Type Plant Asset Location Type Business Object: W1-PlantAssetLocationType A type of asset location for a fixed organizational structure such as a building, factory or other facility. Oracle Utilities Work and Asset Management User Guide 141

142 Valid Parent Location/ Organization Types fields Valid Communicate-To Location Types fields Valid Breaker Location Types fields See W1-AssetLocationType. See W1-AssetLocationType. n/a Defines a list of asset location types that can be considered as breaker points for assets of this type (basically where assets of this type can be connected). The Tree View of any asset or location in the system will show the other related assets with a visual indication of their relationships. Asset Location Type Asset Location Definitions Asset locations define the physical location where assets are installed. Refer to the Creating an Asset Location section for more information. General Asset Location Business Object: W1-GeneralAssetLocation Asset locations are used to indicate the physical location where assets or components are installed. Location Disposition: The current status of the location. Active or Inactive. : A useful description of the service point. Parent Location/Organization ID: The parent location or organization can be referenced to establish a hierarchy for reporting purposes. External ID: Identification number used to associate the service point in an external system. Work Request Approval Profile: Indicates the default approval profile to use for work requests created referencing this location. Address Information fields Contact Information fields Indicates the physical address along with GPS information if applicable. The Location Class is used for reporting and establishes general characteristics of the location such as whether it is commercial or residential, a shop or warehouse, or any other possible categorization appropriate to your business. The primary contact associated to the location. These fields are linked to the Contact portal. Main Contact: Indicates the Contact ID for the primary contact associated to the location. This is linked to the Contact portal. Maintenance Manager: Depending on your business practices, maintenance managers are defined as a particular kind of contact. Planner: Depending on your business practices, planners are defined as a particular kind of contact. Accounting Information fields Information fields Cost Center: List of cost centers which will incur costs for charges against the location. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Provides additional information about the location such as the tag point ID, service area and latitude/longitude coordinates. Oracle Utilities Work and Asset Management User Guide 142

143 Operational Device Asset Location Business Object: W1-AssetLocation Location Disposition: The current status of the location. Active or Inactive. : A useful description of the service point. Parent Location/Organization ID: The parent location or organization can be referenced to establish a hierarchy for reporting purposes. Operation: User-defined value to provide categorization for the location. Criticality fields Criticality: Defines the importance of the location in terms of the potential impact of having issues or problems at that location. For example, a hospital might have a high criticality rating since losing power there might result in deaths of patients, while a city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Reason: Specifies a reason for the location's criticality rating (if applicable). Information fields Address Information fields Peer Locations fields The latitude and longitude coordinates where the activity will occur (usually for GPS). See W1-GeneralAssetLocation. Communicate to Location Linear Asset Location Business Object: W1-LinearAssetLocation Asset locations that are part of a system such as pipes and manholes or poles and cables. Address Information fields Contact Information fields Accounting Information fields System Information fields See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. RCM System: Identifies the failure codes and information used to define the Reliability Centered Maintenance (RCM) system used to evaluate the asset. Environmental Rating: Typically a one time assessment performed to understand stress and/or environmental factors related to the asset such as humidity/corrosions levels for plant assets and soil acidity levels for below ground assets. This is a user defined and user entered value used for information only. It does not tie to any processing. Backlog Group: Indicates which crew is responsible for backlogged work against the asset location. Run to Failure: Should the asset be used until it fails. Yes/No. Peer Locations fields Provides information about related locations. These are other asset locations in the system. Connected To Direction: Indicates the literal direction of the next location from this location. Options include Left, Right or Source. Oracle Utilities Work and Asset Management User Guide 143

144 Information fields Offset Provides additional information about the location. Site Location: Drop-down indicating where the service point is actually located, such as whether it is interior or exterior, under the house or otherwise located. Point ID: Typically a tag point or an area of an asset that needs attention before work can be performed on the asset. For example, if a valve needs to be closed, a breaker needs to be shut off, and a panel needs to be locked on the asset, the valve, breaker, and lock would be defined tag points. This is a free form text field. Service Area: A geographical area where the asset is valid, according to your business practices. Latitude: Geographical latitude coordinate of the location. Longitude: Geographical longitude coordinate of the location. Plant Asset Location Business Object: W1-PlantAssetLocation An asset location for a fixed organizational structure such as a building, factory or other facility. Address Information fields Contact Information fields Accounting Information fields System Information fields Peer Locations fields See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. See W1-LinearAssetLocation Provides information about related location points. Breaker: An asset location type defined as a breaker can be entered here to indicate an applicable breaker point for this location. Runtime Source: An asset location type defined as a runtime source can be entered here. Offset Information fields Provides additional information about the location. Tag Number: If your organization uses tag point functionality, this would be the identification number assigned to a tag point. Site Location: Drop-down indicating where the service point is actually located, such as whether it is interior or exterior, under the house or otherwise located. Point ID: Typically a tag point or an area of an asset that needs attention before work can be performed on the asset. For example, if a valve needs to be closed, a breaker needs to be shut off, and a panel needs to be locked on the asset, the valve, breaker, and lock would be defined tag points. This is a free form text field. Service Area: A geographical area where the asset is valid, according to your business practices. Latitude: Geographical latitude coordinate of the location. Longitude: Geographical longitude coordinate of the location. Service Point Business Object: W2-ServicePoint Oracle Utilities Work and Asset Management User Guide 144

145 Service points are asset locations used to define a specific service point such as commercial or residential, gas or electric. See W1-GeneralAssetLocation. Work Request Approval Profile: n/a Address Information fields Peer Locations fields Contact Information fields Life Support/Sensitive Load fields Information fields See W1-GeneralAssetLocation. See W1-GeneralAssetLocation. Main Contact: Indicates the Contact ID for the primary contact associated to the location. This is linked to the Contact portal. Life Support/Sensitive Load: Drop-down indicating whether the service point is critical, hazardous or sensitive. Life Support Sensitive Load Detail: Free-form text field to provide additional detail about the sensitivity of the service point. Provides additional information about the location. Site Location: Drop-down indicating where the service point is actually located, such as whether it is interior or exterior, under the house or otherwise located. Site Location Detail: Free-form text field to provide additional information about the actual location of the service point. Disconnect Location: Drop-down indicating where the service point is disconnected. SP Warning: Drop-down indicating any potential hazards at the service point such as there is a dog or the meter is in a confined space. SP Instruction: Drop-down indicating any special instructions for the service point such as the technician needs to contact the customer. SP Instruction Detail: Free-form text field to provide additional detail about the special instructions. Key: Drop-down indicating whether there is a key needed for access and where it should be obtained. Key ID: Free-form text field to provide additional detail or identification of the key. Ok to Enter: Drop-down indicating whether entering the location is permitted. Latitude/Longitude: The latitude and longitude coordinates of the location. Bill of Material Definitions A Bill of Material (BOM) is a parts list containing a hierarchy of component parts that make up a piece of equipment or asset. Your organization can build parts lists for assets, components and fleet assets (vehicles). Bills of materials are used to simplify identifying materials when planning work. Refer to the Creating a BOM Part section for more information. General Stock Item Business Object: W1-BOMGenStockItem Defines a general piece of stock or equipment. A generic stock item BOM is automatically generated by the system when a stock item is created. : A description for the part. Oracle Utilities Work and Asset Management User Guide 145

146 Referenced on Assets: yes/no Allowed on BOM Assembly: yes/no BOM Assembly Frozen: yes/no Assembly Parts fields Part: The stock item number. Display Sequence Count: The number of parts that make up the item. Manufacturer Part Business Object: W1-BOMManufacturerPart Defines a general piece of stock or equipment with the manufacturer identified. A manufacturer part BOM is automatically generated by the system when a stock item is created with a Manufacturer/Model specified. See W1-BOMGenStockItem. Identifier Value Assembly Only Part Business Object: W1-BOMAssemblyOnlyPart Defines a piece of stock or equipment that requires assemblies. For parts requiring assemblies, your organization must update the BOM to specify which parts make up the stock item. A given stock item may have several different BOM assemblies that are unrelated to the manufacturer. For example, a sludge pump might have one assembly when a Johnson manufacturer motor is used, and a different assembly when a Mercury manufacturer motor is used. In this case the stock item would have Assembly Only BOM Part assemblies for which a parent part is needed. Assembly only parts use the same fields as W1-BOMGenStockItem Independent Part BOM Business Object: W1-BOMIndependentPartBOM Defines a generic part which is not a stock item, but can be composed of many parts. For example, a truck would be defined as an asset, not a stock item, but might reference a BOM with independent parts. These must be created manually. Independent parts use the same fields as W1-BOMGenStockItem. Service History Object s This section provides descriptions of the attributes used for service history related objects as they are delivered in the base application. Condition Assessment Question Definitions Questions and related answers can be entered to define inspection templates which guide asset inspections. Questions are associated to service history types which are then associated to asset types. Refer to the Defining Condition Assessment Questions section for more information. Oracle Utilities Work and Asset Management User Guide 146

147 Business Object: W1-Question Question: A unique name or code for the assessment question. Question Text: Free form text. Short Text: Shortened version of the question which appears in the question line on the service history. Service History Subclass: Classifies the question in relationship to the type of inspection that the question is related to, such as deficiency, general weighted, percent of new, or questionnaire. Questions can be searched by this criteria. Category: Further categorizes the question in relationship to the type of inspection. Questions can be searched by this criteria. Active: Indicates active/or inactive whether or not the question can be used in an inspection. Answers fields Establishes a valid list of answers to the question with points for each answer. This structure establishes the basis for the inspection scoring. For example if the question is: What is the state of the asset? Answers might be: Not functioning / Score = 0 Working great / Score = 10 Sputtering but still running / Score = 3...and so on. Service History Type Definitions Service history types define the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement and so on. Refer to the Defining Service History Types section for more information. Service History Type Business Object: W1-ServiceHistoryType Service History Type: A unique name or code for the service history type. : The description which appears in drop-down lists. Service History BO: The business object used when creating service history of this type. Category: An additional categorization of the service history type to describe the kind of service being performed such as downtime, failure, inspection, maintenance or repair. Service Schedule fields Sets the template work order and time intervals that should be used to schedule work order generation. Template Work Order: Establishes a list of valid work order templates that can be used when creating service history of this type. Interval Years Interval Months Interval Days Initiation Date: Indicates the first date that the generation is scheduled. Oracle Utilities Work and Asset Management User Guide 147

148 Service History Types for Asset Condition/Inspection Deficiency Inspection Type Business Object: W1-InspectionTypeDeficiency (noting various defects on the asset, which can be summed): The condition of the asset is based on accumulated defect points. As with the general weighted method, each potential defect is assigned a weight value based on the impact to service level. Then each defect is broken down into specific severity levels with a point value assigned to each. The more severe the nature of the defect, the higher the associated point value. Normally, the point scale is a range of 1-10, allowing for at least 10 different definitions or levels of severity. Unlike the general weighted method, each defect and severity identified during inspection is accumulated for the final deficiency score. That is, if there are 5 defects with a severity of 2 points each, then the deficiency score for the asset would be 10. A like new asset would exhibit none of the potential defects and be awarded a deficiency score of 0 (i.e., absolutely no defects were noted). A severely broken asset would exhibit the highest severity of each potential defect, probably numerous times, and would be awarded a higher deficiency score. Question fields See W1-ServiceHistoryType. Establishes a valid list of questions to guide the inspection. Questions are defined in the Question portal. Sequence: Determines the sequential order for the question. These fields can be used to reorder the questions, as needed. Question: The text which appears for the question. Weight: Represents the importance of the question in relationship to the other questions. This is represented as a decimal value. The total weight of all questions must equal 1. Behavior General Weighted Inspection Type Business Object: W1-InspectionTypeGenrlWeighted (grading on a 1-5 scale): The condition of the asset is based on a general assessment of potential defects using a weighted scale of 1-5. Each potential defect is assigned a weight value based on the impact to the service level. A potential defect that has significant impact on the service level will have a higher weight value than a potential defect with minimal impact on the service level. A like new asset would exhibit none of the potential defects and be awarded the minimum points resulting in a rating of 1. A severely broken asset would exhibit the highest severity of each potential defect and would be awarded the maximum points resulting in a rating of 5. Question fields See W1-ServiceHistoryType. Establishes a valid list of questions to guide the inspection. Questions are defined in the Question portal. Sequence: Determines the sequential order for the question. These fields can be used to reorder the questions, as needed. Question: The text which appears for the question. Weight: Represents the importance of the question in relationship to the other questions. This is represented as a decimal value. The total weight of all questions must equal 1. Behavior: n/a Percent of New Inspection Type Business Object: W1-InspectionTypePercentOfNew Oracle Utilities Work and Asset Management User Guide 148

149 (maps a percent value to the 1-5 scale): The condition of the asset is based on passing or failing characteristics of a new asset. A like new asset would pass all characteristics and be awarded the maximum points resulting in a 100% rating. A severely broken asset would fail all characteristics of a new asset and be awarded zero points resulting in a 0% rating. Question fields See W1-ServiceHistoryType. Establishes a valid list of questions to guide the inspection. Questions are defined in the Question portal. Sequence: Determines the sequential order for the question. These fields can be used to reorder the questions, as needed. Question: The text which appears for the question. Weight: Represents the importance of the question in relationship to the other questions. This is represented as a decimal value. The total weight of all questions must equal 1. Behavior: n/a Condition Assessment Definitions Condition assessments are used with asset assessment/condition rating functionality. They group assessment service history types (i.e. inspection types) and to factor in asset aging factors to comprise a weighted combination of elements that affect how condition ratings are calculated. Business Object: W1-AssessGrp Assessment Group: A unique name or code for the assessment group. : A description of the assessment group. Service History Type fields Establishes a list of valid service history types that can be used with this assessment group. Weight: Represents the importance of the service history type as it relates to the overall group. For example, you might add 2 types, one for visual inspection and one for mechanical inspection. The visual inspection might have a weight of.25 where the mechanical inspection is weighted more heavily at.75. The overall total weight must equal 1. Calculation: Indicates whether or not the service history type should be included in the overall scoring calculation for the inspection. Aging Factors fields Defines aging ranges which are used to assess inspection record ages and compute a weighted confidence rating. Confidence rating is a percentage scoring method for assets where 100% means complete confidence that the asset is in good condition. The percentage drops as asset condition data ages. Sequence Start Range/End Range: Define an age range, in number of days. Aging Factor: A numerical value which, when applied, decreases the validity of the inspection score as the inspection date becomes less relevant. The ranges and aging factor can be determined as best derived by your business practices. As an example, you may break the ranges down into quarters: 1.00 for 0 to 90 days.75 for 91 to 180 days.50 for 181 to 270 days Oracle Utilities Work and Asset Management User Guide 149

150 .25 for 271 to 99,999 days Note the final end range is entered as 99,999 since the system requires a fail safe end range. The confidence rating resets each time a new, fresh, inspection is completed. Condition Assessment Class Definitions Assessment classes are sets of condition assessments, and are necessary for asset assessment/condition rating functionality. They are used to manage assets according to a set of inspection criteria and are used to define an inspection rating system for inspections. The purpose of this rating system is to measure the deterioration of the assets and the effect of the deterioration on the service levels that are expected of the asset. Refer to the Defining a Condition Assessment Class section for more information. Business Object: W1-AssessClass Assessment Class: A unique name or code for the assessment class. : A description of the assessment class. Assessment Groups fields Establishes a list of assessment groups that can be used with this assessment class. Assessment Group Group Weight: Represents the importance of the assessment group as it relates to the class. For example, you might add 2 classes, one for visual inspection and one for mechanical inspection. The visual inspection might have a weight of.25 where the mechanical inspection is weighted more heavily at.75. The overall total weight must equal 1. Calculation: Indicates whether or not the assessment group should be included in the overall scoring calculation for the inspection. Status (from the BO lifecycle) The current state of the assessment class. Valid statuses include: Active Inactive Service History Definitions Use service history to enter relevant information regarding service or maintenance on assets. Typically it is used to record inspection feedback, pass/fail details, downtime, parts failure information, maintenance or service logs, or other information regarding service on the asset. Refer to the Entering Service History Manually section for more information. Inspection Root Business Object: W1-InspectionRoot Effective Date/Time: The date applicable to the service history. Typically the date and time that the service was done. Activity ID: The activity ID associated to the service that was completed, if applicable. Oracle Utilities Work and Asset Management User Guide 150

151 Inspected By: The user name of the person who completed the inspection. Comments: Free-form text field to enter notes. Failure Information fields Identifies the failure codes and information used to define the Reliability Centered Maintenance (RCM) system used to evaluate the asset. Failure Cause Failure Mode Failure Repair Failure Component Failure Root Cause Questionnaire fields Status (from the BO lifecycle) Presents the inspection questions and answers defined for the service history type. Pending Compute Score Computation Error Complete General Service History Business Object: W1-ServiceHistoryWAM See W1-InspectionRoot. Inspected By: n/a Questionnaire fields Failure Information fields Status n/a See W1-InspectionRoot. n/a Failure Information Business Object: W1-FailureServiceHistory A service history with failure information. See W1-InspectionRoot. Inspected By: n/a Questionnaire fields Failure Information fields Status n/a See W1-InspectionRoot. n/a Asset Downtime Business Object: W1-AssetDownTime A service history to capture downtime information. Oracle Utilities Work and Asset Management User Guide 151

152 See W1-InspectionRoot. Inspected By: n/a Start and End Date/Time: The timeframe that the asset was down due to the service. Downtime Reason: Reason for the down time such as planned maintenance, unplanned maintenance, and so on. Failure Information fields Questionnaire fields Status See W1-InspectionRoot. n/a n/a Service History for Asset Condition/Inspection General Weighted Inspection Business Object: W1-InspectionGenrlWeighted (grading on a 1-5 scale): The condition of the asset is based on a general assessment of potential defects using a weighted scale of 1-5. Each potential defect is assigned a weight value based on the impact to the service level. A potential defect that has significant impact on the service level will have a higher weight value than a potential defect with minimal impact on the service level. A like new asset would exhibit none of the potential defects and be awarded the minimum points resulting in a rating of 1. A severely broken asset would exhibit the highest severity of each potential defect and would be awarded the maximum points resulting in a rating of 5. Questionnaire fields Failure Information fields Status See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. Deficiency Inspection Business Object: W1-InspectionDeficiency (noting various defects on the asset, which can be summed): The condition of the asset is based on accumulated defect points. As with the general weighted method, each potential defect is assigned a weight value based on the impact to service level. Then each defect is broken down into specific severity levels with a point value assigned to each. The more severe the nature of the defect, the higher the associated point value. Normally, the point scale is a range of 1-10, allowing for at least 10 different definitions or levels of severity. Unlike the general weighted method, each defect and severity identified during inspection is accumulated for the final deficiency score. That is, if there are 5 defects with a severity of 2 points each, then the deficiency score for the asset would be 10. A like new asset would exhibit none of the potential defects and be awarded a deficiency score of 0 (i.e., absolutely no defects were noted). A severely broken asset would exhibit the highest severity of each potential defect, probably numerous times, and would be awarded a higher deficiency score. Questionnaire fields Failure Information fields Status See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. Oracle Utilities Work and Asset Management User Guide 152

153 Percent of New Inspection Business Object: W1-InspectionPercentOfNew (maps a percent value to the 1-5 scale): The condition of the asset is based on passing or failing characteristics of a new asset. A like new asset would pass all characteristics and be awarded the maximum points resulting in a 100% rating. A severely broken asset would fail all characteristics of a new asset and be awarded zero points resulting in a 0% rating. Questionnaire fields Failure Information fields Status See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. See W1-InspectionRoot. Service History for Operational Devices Smart Device Test Business Object: W2-SmartTest Questionnaire fields Failure Information fields Test Results See W1-InspectionRoot. n/a n/a Connectivity Status (Pass/Fail) Communication Status (Pass/Fail) Operational Test Status (Pass/Fail) Status n/a Operational Device Service History Business Object: W1-ServiceHistory Questionnaire fields Failure Information fields Status See W1-InspectionRoot. n/a n/a n/a Operational Device Basic Test Business Object: W1-BasicTest Questionnaire fields Failure Information fields See W1-InspectionRoot. n/a n/a Oracle Utilities Work and Asset Management User Guide 153

154 Test Results fields Status Test Status: Pass/Fail n/a Specification Object s This section provides descriptions of the attributes used for specifications as they are delivered in the base application. Specification Definitions A specification is contains the manufacturer, model, and other information about a set of assets. Refer to the Defining Specifications section for more information. Tracked General Specification Business Object: W1-TrackedGeneralSpecification General specifications define details relevant to specifications for general assets. Specification: Unique identifier for the specification. : A useful description of the specification. This can be searched from other records. Asset Type: The asset type that uses the specification. Item Detail fields Manufacturer: The manufacturer that provided the specification or that is associated with the asset. Values are defined in the Manufacturer portal. BOM ID: The associated bill of materials. Model: The model number for the asset. Maintenance Schedule fields In Service Maintenance Schedule: Indicates the preventive maintenance schedule to use when assets of the indicated type are in service (actively in use). In Store Maintenance Schedule: Indicates the preventive maintenance schedule to use when assets of the indicated type are in stores (typically not actively in use). IT Specification Business Object: W1-TrackedITSpecification IT specifications define details relevant to technology assets such as phones and laptops. Item Detail fields See W1-TrackedGeneralSpecification See W1-TrackedGeneralSpecification Infrastructure Specification Business Object: W1-TrackedInfrastructureSpec Infrastructure specifications define details relevant to assets that make up part of an infrastructure. Oracle Utilities Work and Asset Management User Guide 154

155 Item Detail fields Maintenance Schedule fields See W1-TrackedGeneralSpecification n/a See W1-TrackedGeneralSpecification Fleet Specification Business Object: W1-TrackedFleetSpecification Fleet specifications define details relevant to specifications for a vehicle. Item Detail fields Maintenance Schedule fields Vehicle Detail fields See W1-TrackedGeneralSpecification n/a See W1-TrackedGeneralSpecification Provides details about the vehicle such as model year, color, features and specifications. Model Year Color Cruise Control Drive Type: All wheel drive, four wheel drive, truck axle, and so on. Transmission Size Engine Size Fuel Type: Diesel, electric, gas, natural gas, hybrid, and so on Gross Weight Radio Tire Size Weight Smart Meter Specification Business Object: W2-SmartMeterSpecification Smart meters are monitoring devices that send and receive information electronically. Specification: Unique identifier for the specification. : A useful description of the specification. This can be searched from other records. Asset Type: The asset type that uses the specification. Manufacturer: The manufacturer that provided the specification or that is associated with the asset. Values are defined in the Manufacturer portal. Typically the specification would have come from the manufacturer; otherwise this may simply be informational. Detail fields Provide further identification for the specification or smart meter. This could be a model ID, stock code or other identifying information. Oracle Utilities Work and Asset Management User Guide 155

156 Firmware Information fields Metrology Firmware: The software for the functionality of the smart meter. NIC Firmware: The software for the network interface card in the smart meter. Analog Meter Specification Business Object: W2-ManualMeterSpecification Manual meters are monitoring devices that must be read and have their information recorded manually. Specification: Unique identifier for the specification. : A useful description of the specification. This can be searched from other records. Asset Type: The asset type that uses the specification. Manufacturer: The manufacturer that provided the specification or that is associated with the asset. Values are defined in the Manufacturer portal. Typically the specification would have come from the manufacturer; otherwise this may simply be informational. Detail fields Attribue fields Provide further identification for the specification or smart meter. This could be a model ID, stock code or other identifying information. Drive Rate Firmware Specification Business Object: W2-FirmwareSpecification Firmware specifications define the software and software versions that is applicable to certain devices. Asset Type Firmware Attributes n/a Specifies an asset identifier type and an external site. Communication Component Specification Business Object: W2-CommunicationComponentSpec Communication components are devices that can be attached to a smart meter to connect the meter to the communication grid. Communication component specifications are most important for managing the firmware versions and updates for these devices. This type of specification uses fields similar to W2-SmartMeterSpecification. Communication Relay Specification Business Object: W2-CommunicationRelaySpec Communication relays transmit messages between various points to facilitate communication between units. Communication relay specifications are most important for managing the firmware versions and updates for these devices. This type of specification uses fields similar to W2-SmartMeterSpecification. Oracle Utilities Work and Asset Management User Guide 156

157 Child Specification Definitions A specification is contains the manufacturer, model, and other information about a set of assets. Child specifications are referenced on specifications to indicate valid firmware versions. Business Object: W2-FirmwareVersion Firmware Version fields Firmware Version: Indicates the relevant version of the software used to cause the smart meter to function properly. Release Date: Indicates the release date of the applicable firmware version. Release Note: Provides any relevant comments regarding the firmware release. Status (from the BO lifecycle) Created Under Testing Rejected Approved Quarantined Deprecated Obsolete Operational Reading (Measurement) Object s This section provides descriptions of the attributes used for measurement related objects as they are delivered in the base application. Measurement Type (Operational Readings) Definitions Measurement types define the units to use for a particular measurement and establish the values needed to support the evaluation of measurements such as upper and lower reading thresholds, maximum reading value, and so on. Asset measurements, or operational data, might include mileage, hours of uptime, number of start-stops, and so on. Refer to the Defining a Measurement Type (Operational Reading) section for more information. Measurement Type Business Object: W1-MeasurementType Base business object for measurement types. This establishes the base structure for business objects of this type, but is not a selectable option for new records. Measurement Type: A unique name or code for the measurement type. : The description which appears in drop-down lists. Oracle Utilities Work and Asset Management User Guide 157

158 Measurement Business Object: The business object that will be used when creating measurements of this type. Measurement Unit of Measure: The measurement unit for measurements of this type such as KWH or PSI. Measurement Type Identifier fields Exception Handling fields Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. Defines the parameters for how the system should respond if there are issues with the reading such as the To Do Type and Role that should receive alerts, retries, and discard reason. For example, if the reading is outside of the measurement range, the system sends an alert to the indicated To Do Role. To Do Type and Role To Do Role Maximum Retries Retry Frequency Discard Reason Gauge Read Measurement Type Business Object: W1-GaugeReadThreshold Measurement type to capture gauge readings such as pressure or vacuum. See W1-MeasurementType Additional fields: Lower Limit/Upper Limit: The low and high values that define a valid range for the measurement. A reading that falls out of this range triggers an error based on the settings in the Exception Handling section. Measurement Type Identifier fields Exception Handling fields See W1-MeasurementType See W1-MeasurementType Metered Read with Rollover Business Object: W1-MeteredReadRollover Measurement type to capture meter readings such as energy, hours, water, or odometer. Typically these meters roll over, i.e, they reach a maximum value then start again at zero. See W1-MeasurementType Additional fields: Full Dial Value: Represents the highest possible reading prior to a rollover. For example, an odometer might have a maximum of 999,999 miles. This would be the full dial value. Maximum Measurement: Represents the maximum reading allowed without triggering an error. Measurement Type Identifier fields Exception Handling fields See W1-MeasurementType See W1-MeasurementType Oracle Utilities Work and Asset Management User Guide 158

159 Read with no Evaluate Business Object: W1-ReadNoEvaluate Captures a reading with no evaluation or measurement parameters. Measurement Type Identifier fields Exception Handling fields See W1-MeasurementType See W1-MeasurementType See W1-MeasurementType Operational Reading (Measurement) Definitions Measurements manage the asset operational and runtime data which is collected and tracked for assets. Asset measurements might include mileage, hours of uptime, number of start-stops, and so on. Refer to the Working with Operational Readings (Measurements) section for more information. Numeric Gauge Business Object: W1-NumericGauge A type of gauge, such as pressure, vacuum gauge, a thermometer, humidity and so on. Asset: The asset for which the measurement is being recorded. Reading Date/Time: The date and time that the measurement is taken. Current Value: The actual reading. Measurement Gauge Meter Reason Status (from the BO lifecycle) Entered Evaluate Evaluation Alert Valid Numeric Meter Business Object: W1-NumericMeter A type of meter such as gas meter, energy meter, water meter, or odometer. Asset: The asset for which the measurement is being recorded. Reading Date/Time: The date and time that the measurement is taken. Current Value: The actual reading. Initial Value: Yes/No. Indicates whether or not this is the initial reading. Measurement Numeric Meter Reason Oracle Utilities Work and Asset Management User Guide 159

160 Status (from the BO lifecycle) Entered Evaluate Evaluation Alert Valid Measurement Unit of Measurement Definitions Measurement unit of measurements (UOM) establish the types of units that can be used to measure assets. Each UOM identifies a definite magnitude of a measurement reading taken for an asset. This might include tire pressure (psi), temperature ratings (degrees), and so on. Refer to the Defining Measurement Unit of Measurement (UOM) section for more information. Business Object: W1-MeasurementUOM Measurement UOM: A unique name or code for the unit. : of the unit which appears in drop-down lists. Warranty Object s This section provides descriptions of the attributes used for warranty related objects as they are delivered in the base application. Warranty Term Definitions Warranty terms hold the duration, term, value or usage limit of assets or items that are under warranty. The warranty term also specifies the specification and/or vendor that a warranty claim can be issued to when needed. Refer to the Defining a Warranty Term section for more information. Calendar Warranty Term Business Object: W1-CalendarWarrantyTerm Calendar warranties are for a set amount of time, such as 2 years. Warranty Term: A unique code for the warranty term. Warranty Term Name: The description of the warranty term which appears in drop-down lists. Detailed : A more detailed description of the warranty term. Specification: As applicable, the specification that corresponds to the warranty term. Vendor: The vendor used to procure the asset with whom the warranty is valid. Terms fields Duration (in months): Indicates the amount of time that the warranty term is in effect. Oracle Utilities Work and Asset Management User Guide 160

161 Exception Handling fields Determines how the system will handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Runtime Warranty Term Business Object: W1-RuntimeWarrantyTerm Runtime warranties are for a portion of the life of the asset, such as up to 50, 000 miles. Warranty Term: A unique code for the warranty term. Warranty Term Name: The description of the warranty term which appears in drop-down lists. Detailed : A more detailed description of the warranty term. Specification: As applicable, the specification that corresponds to the warranty term. Vendor: The vendor used to procure the asset with whom the warranty is valid. Terms fields Term Value: Indicates the value of the term, such as 50,000 miles. Unit of Measure Allow Additional Term Value: Indicates whether or not the terms of the warranty can be extended. For example, if the initial coverage is for 50,000 miles, the term might be extended by an additional 15,000 miles. Exception Handling fields Determines how the system will handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Warranty Definitions A warranty is a written guarantee issued to your organization promising to repair or replace a damaged item within a specified period of time or usage limit. The Warranty portal manages the warranties held for assets or other purchased items for your organization. Refer to the Entering a Warranty section for more information. Calendar Warranty Business Object: W1-CalendarWarranty Calendar warranties are for a set amount of time, such as 2 years. Oracle Utilities Work and Asset Management User Guide 161

162 Warranty Term: The pre-defined term upon which the warranty is based. Asset ID: The asset to which the warranty applies. Start Date/Expiration Date: The date that the warranty goes into effect, and when it expires. Status (from the BO lifecycle) Valid statuses include: Active Expired Runtime Warranty Business Object: W1-RuntimeWarranty Runtime warranties are for a portion of the life of the asset, such as up to 50, 000 miles. Warranty Term: The pre-defined term upon which the warranty is based. Start Date/Expiration Date: The date that the warranty goes into effect, and when it expires. Initial Measurement: Indicates the measurement of the asset when the warranty goes into effect. For example, a vehicle most likely does not have a 0 odometer reading when it is procured, so it is valuable to record the actual reading to determine the warranty term. Additional Term Value: Extends the coverage of the warranty. For example, if the initial coverage is for 50,000 miles, the term might be extended by an additional 15,000 miles. Dependent Calendar Warranty: As applicable, references a related calendar warranty to supplement the runtime warranty being created by adding a time constraint in addition to the runtime constraint. This is used to define a warranty term such as 2 years or 50,000 miles. If either warranty expires, they both expire. Status (from the BO lifecycle) Valid statuses include: Active Expired Asset Configuration Object s This section provides descriptions of the attributes used for asset configuration related objects as they are delivered in the base application. Asset Configuration Type Definitions Configuration types define the information required for various asset configurations with other assets, components, firmware, and other aspects of a functioning configured system. Refer to the Defining Asset Configuration Types section for more information. Business Object: W1-ConfigType Configuration Type: A unique name or code for the configuration type. Oracle Utilities Work and Asset Management User Guide 162

163 : The description of the configuration type which appears in drop-down lists. Configuration Class: Indicates the classification for the configuration type, such as asset to asset, asset to component, and so on. Configuration Category: Indicates a category for the configuration such as commercial or residential. Configuration Business Object: Indicates the business object that will be used for configurations of this type. Asset Configuration Definitions A single asset or component can have many parameters and only certain combinations of parameter values that are allowed. Multiple assets and/or components may work together as a group with only certain combinations of settings that are allowed or supported. All configurations use the same set of fields: Configuration Detail fields Status (from the BO lifecycle) Indicates the assets, components, firmware and other elements in the setup of the configuration. Valid statuses include: Pending Under Testing Rejected Approved Deprecated Obsolete Single Asset Configuration Configurations document and manage the valid set ups for assets/and components. This includes a specification for each asset or component in the configuration as well as the valid value for each parameter, such as the firmware version of each asset. Business Object: W1-SingleAssetConfig Asset/Component Configuration Business Object: W1-AssetCompConfig Asset to Asset Configuration Business Object: W1-AssetToAssetConfig Asset/Component to Asset Configuration Business Object: W1-AssetCompToAssetConfig Asset to Asset/Component Configuration Business Object: W1-AssetToAssetCompConfig Oracle Utilities Work and Asset Management User Guide 163

164 Asset/Component to Asset/Component Configuration Business Object: W1-AssetCompToAssetCompConfig Configuration Report Definitions Configuration reports provide a summary of any currently installed configurations. Refer to the Creating an Asset Configuration Report section for more information. All configuration reports use the same set of fields: Reporting Mode: Indicates how the report is generated, such as one time or recurring. Report Criteria fields Report Results Status (from the BO lifecycle) Indicates the assets, components, firmware, characteristics and other identifiers that the system will use to filter which configurations appear in the report. Provides the link to the actual report with a summary of the time and date that the report was generated. Valid statuses include: Pending Submitted Generate Report Single Asset Configuration Report Business Object: W1-SingleAssetCfgRpt Asset/Component Business Object: W1-AssetCompCfgRpt Asset to Asset Business Object: W1-AssetToAssetCfgRpt Asset/Component to Asset Business Object: W1-AssetCompToAssetCfgRpt Asset to Asset/Component Business Object: W1-AssetToAssetCompCfgRpt Asset/Component to Asset/Component Business Object: W1-AssetCompToAssetCompCfgRpt Oracle Utilities Work and Asset Management User Guide 164

165 Inventory Object s This section provides descriptions of the attributes used for inventory related objects as they are delivered in the base application. Refer to the Understanding Inventory section for a conceptual overview of this functional area. Material Request, Issue and Return Object s This section provides descriptions of the attributes used for material request, material issue and material return objects as they are delivered in the base application. Material Request Template Definitions A material template is a collection of stock items that is used to easily populate a material request. For example, a template could exist for office supplies that contains the collection of office supply stock items that the user can add to the request. Likewise, you might have a template to request all of the items on a bill of materials. Refer to the Creating a Material Request Template section for more information. Business Object: W1-MaterialRequestTemplate Storeroom ID: The identifier for the applicable storeroom. : A useful description of the template which will appear in drop-down lists. Materials Information: Provides details about the stock items on the template including the stock item detail IDs, quantity and expense code. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Material Request Header Definitions Material requests, or checkout requests, manage the process of specifying the need to issue stock items from a storeroom. Material Request Header Business Object: W1-MaterialRequestHeader Defines the information for the main material request record. Refer to the Creating a Material Request (Checkout Request) section for more information. Storeroom: The storeroom from which the items are being requested. Oracle Utilities Work and Asset Management User Guide 165

166 Request Information fields Activity: The related activity, as applicable, where the stock items are be needed as materials. Provides more detail about the request: Required By Date Deliver To Location: Indicates the storeroom location where the goods should be delivered. Deliver To: Free form text field to indicate who should receive the delivery. Requested By: Free form text field to indicate the person who made the request. Phone Accounting Information fields Project: Indicates the Project ID related to the request. Cost Center: List of cost centers which will incur costs for charges against the request. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Issue Fulfilled Canceled Stock Transfer Header Business Object: W1-StockTransferHeader Defines the information for the main stock transfer record. Refer to the Processing a Stock Transfer section for more information. Issuing Storage Location: The storage location from which the items are being requested. Request Information fields Provides more detail about the request: Required By Date Deliver To Location: Indicates the storeroom location where the goods should be delivered. Deliver To: Free form text field to indicate who should receive the delivery. Requester: Free form text field to indicate the person who made the request. Phone Status (from the BO lifecycle) Valid statuses include: Created Ready for Issue Issued Canceled Oracle Utilities Work and Asset Management User Guide 166

167 Material Request Line Definitions Material requests, or checkout requests, manage the process of specifying the need to issue stock items from a storeroom. Material Request Line Business Object: W1-MaterialRequestLine Describes the details for line items added to the request. Refer to the Creating a Material Request (Checkout Request) section for more information. Requested Quantity: The amount of the stock item being requested. Expense Code: The expense code being charged for the transaction. Status (from the BO lifecycle) Valid statuses include: Created Issued Canceled Stock Transfer Request Line Business Object: W1-StockTransferRequestLine Describes the details for line items added to the request. Refer to the Processing a Stock Transfer section for more information. Requested Quantity: The amount of the stock item being requested. Expense Code: The expense code being charged for the transaction. Status (from the BO lifecycle) Valid statuses include: Created Ready for Issue Issued Canceled Material Issue Line Definitions Material issue, or stock checkout, manages the process of pulling out and releasing stock items from a storeroom. Refer to the Issuing Stock (Material Issue) section for more information. Material Issue Line Business Object: W1-MaterialIssueLine Describes the details for line items being issued. Oracle Utilities Work and Asset Management User Guide 167

168 Information Material Requst Line Stock Item Detail: The record number for the stock item being issued. Issue Quantity Total Cost Status (from the BO lifecycle) Valid statuses include: Pulled Completed Canceled Stock Transfer Issue Line Business Object: W1-StockTransferIssueLine Describes the details for line items being transferred. Stock Transfer Issue Line Stock Item Detail ID: Indicates the record number for the stock item being transferred. Asset ID: Indicates the record number for the asset related to the transfer. Issue Quantity Status (from the BO lifecycle) Valid statuses include: Pulled Completed Canceled Material Return Header Definitions Material returns manage the process of returning to the storeroom excess stock items that were previously issued. Material Return Header Business Object: W1-MaterialReturnHeader Describes the details for the return. Storeroom: The record number for the storeroom from which the items are being requested. Activity: The related activity, as applicable. Status (from the BO lifecycle) Valid statuses include: Created Ready for Return Oracle Utilities Work and Asset Management User Guide 168

169 Completed Rejected Stock Transfer Receipt Header Business Object: W1-StockTransferReceiptHeader Describes the details for the transfer. Receiving Storage Location: The record number for the storeroom where the material is being transferred. Return Information fields Provides more details about the return. Receipt Date Received By Phone Status (from the BO lifecycle) Valid statuses include: Created Ready for Receipt Completed Rejected Material Return Line Definitions Material returns manage the process of returning to the storeroom excess stock items that were previously issued. Refer to the Processing a Material Return (Returning Stock Items) section for more information. Material Return Line Business Object: W1-MaterialReturnLine Defines the details needed for line items added to the request. Return Quantity: The amount being returned. Expense Code: The expense code being credited for the return. Status (from the BO lifecycle) Valid statuses include: Created Accepted Returned Rejected Oracle Utilities Work and Asset Management User Guide 169

170 Stock Transfer Receipt Line Business Object: W1-StockTransferReceiptLine A material return triggers the creation of a stock receipt. This transaction returns the items to the storeroom. Status Stock Transfer Receipt Header: The record number for the stock transfer record where the line item is added. Status Reason Stock Item Detail ID: The record number for the stock item being transferred. Receipt Quantity Status (from the BO lifecycle) Valid statuses include: Ready for Receipt Received Physical Inventory Object s This section provides descriptions of the attributes used for physical inventory related objects as they are delivered in the base application. Physical Inventory Definitions Physical inventory is an auditing procedure within Inventory Management which your organization can use to ensure that the physical quantities of items, materials and stock that are housed in your storage locations are actually stocked per what is recorded within the system. This basically allows your organization to verify the accuracy of your inventory quantities and values. Please refer to the Performing a Physical Inventory section for more information. Business Object: W1-PIHeader Storeroom: The storeroom where the stock is being counted. Items to Create: Indicates the number of items to count. For example, you have 100 different stock items in inventory, but you only want to count 20 of them. This is not the quantity for each item, but rather, the number of individual items slated for counting. Type of Inventory: Indicates whether the count is for general, lot managed or tracked items. Optional Criteria fields Starting and Ending Stock Code: Indicates the stock codes to be included in the count. These should be stock items stored in the indicated storeroom/storage location. The included stock codes must also be of the same inventory type; lot managed, tracked or general. Starting and Ending Bin: Free form text fields indicating the bin location for stock items, as applicable. Vendor: Indicates the vendor/supplier of the items, as applicable. Stock Item Category: Categorization for stock items based on your organization's business practices. Oracle Utilities Work and Asset Management User Guide 170

171 ABC Class: Represents a system used to classify stock items based on their frequency of use and value. Class A items have the highest dollar usage value and are the most often counted while Class C items have the lowest dollar usage value and are the least often counted. Days Since Last Inventory: Indicates the number of days since items were counted. Minimum Total Value: Indicates the minimum value of the stock item before the item is put into the inventory count. (quantity x AUP) Random: Indicates whether or not items should be counted by bin or if a selection of stock items will be randomized. Status (from the BO lifecycle) Valid statuses include: Created Selecting Stock Items Stock Items Selected Count in Progress Completed Canceled Inventory Adjustment Definitions Inventory adjustments can be used to adjust inventory counts or price of stock items. Inventory Adjustment - Regular Inventory Business Object: W1-InventoryAdjustmentRI Adjust inventory for regular stock items. Reason: The reason for the adjustment. Comments: Free form text field. Status (from the BO lifecycle) Valid statuses include: Created Completed Inventory Adjustment - Inventory Lot Managed Business Object: W1-InventoryAdjustmentILM Adjust inventory for lot managed stock items. This type of inventory adjustment uses the same fields as W1-InventoryAdjustmentRI. Inventory Adjustment - Inventory Tracked Business Object: W1-InventoryAdjustmentIT Adjust inventory for tracked stock items. This type of inventory adjustment uses the same fields as W1-InventoryAdjustmentRI. Only a price adjustment is supported for tracked items. Oracle Utilities Work and Asset Management User Guide 171

172 Receipt Object s This section provides descriptions of the attributes used for receipts as they are delivered in the base application. Receipt Definitions The receiving process is used to track inventory that is received as the result of a purchase order by recording basic information such as the quantity received, receiving location, packing slip details, carrier, and so on. Refer to the Record Receipt/Delivery for a Purchase Order (Processing a Receipt) section for more information. Business Object: W1-ReceiptHeader : of the receipt. Temporary Marker: If your organization uses use a tagging system to physically mark deliveries you can enter the tag number here. Purchase Order: The purchase order for which the items are being received. Receipt Information fields Provides more details about the receipt such as the receiving location, UPC code, container quantity, vendor, packing slip number and comments. Receiving Location: The storage location within your organization where items are received. UPC Container Quantity Carrier Vendor: As applicable, the vendor or company that delivered the items. Packing Slip Comments Status (from the BO lifecycle) Valid statuses include: Created Completed Receipt Line Definitions The receiving process is used to track inventory that is received as the result of a purchase order by recording basic information such as the quantity received, receiving location, packing slip details, carrier, and so on. Refer to the Record Receipt/Delivery for a Purchase Order (Processing a Receipt) section for more information. Receipt Line Business Object: W1-ReceiptLine Defines the information needed to process the receipt of items for a purchase order. Oracle Utilities Work and Asset Management User Guide 172

173 Receipt Line Information fields Status (from the BO lifecycle) Quantity: The quantity being received. Comments: Free form text. Valid statuses include: Created In Receipt Complete Receipt Line Craft Business Object: W1-ReceiptLineCraft Defines the information required to process received work from an outside contractor as designated on a purchase order. Receipt Line Information fields Status (from the BO lifecycle) Hours: The number of hours worked by the craft Comments: Free form text. Valid statuses include: Created In Receipt Complete Return Line Definitions Returns track inventory that must be returned to a vendor. Returns are tracked in relationship to the purchase order for the original receipt of the items. Refer to the Processing a Purchasing Return section for more information. Business Object: W1-ReturnLine Purchase Order Line: Indicates the line item on the originating purchase order for the item being returned. Type of Return: Indicates how the return will be processed, such as for credit or as an exchange. Quantity: The amount being returned. Asset Information: Indicates the Asset ID for the asset being returned, as applicable. Lot Information: Indicates the stock item and quantity being returned, as applicable. Status (from the BO lifecycle) Valid statuses include: Created Returned Canceled Oracle Utilities Work and Asset Management User Guide 173

174 Reorder Review Definitions The system can be configured to automatically monitor and respond when inventory levels for stock items fall below set reorder points. Batch stock reorder monitors all storeroom stock items that are set up for reorder processing then processes any items that have reached the reorder point and creates Reorder Review for further processing. Reorder Review records cannot be created manually, they must be created by the batch stock reorder process. Refer to the Reviewing and Approving Items for Reorder (Reorder Review) section for more information. Business Object: W1-ReorderReview Stock Item Detail: The stock item for which the reorder will be processed Hold Override Date: If you want to approve the suggested order, but wish to delay processing until the Reorder By Date, you can select the Hold button to the status to Held. This action requires a Hold Override Date which indicates when the system should transition the Reorder Review from Held to Created status. This overrides the Reorder by Date. Buyer: The buyer responsible for reviewing and managing the reorder. Blanket Contract/Revision: The blanket contract number that will be used for the reorder. Reorder Details fields This section includes the information needed for the reorder. Reorder Source: Indicates the purchasing document that will be created to facilitate the reorder, either a purchase order or purchase request. Order Quantity: Indicates the amount to reorder when the reorder review is processed. Unit Price: Indicates the unit price per item. Unit of Purchase/Unit of Issue/Purchase to Issue Ratio: The system uses the Unit of Purchase, Unit of Issue, and Purchase to Issue Ratio information to maintain quantities as parts are issued and new parts are received. You may, for instance, issue in individual items but order the items by the box where one box would contain 10 individual items. The Unit of Purchase would then be BOX, the Unit of Issue would be EA, and the P/ I Ratio would be 10. Reorder By Date: The latest date that the items can be reordered to fulfill requirements. Typically this is the date the material is required, minus the number of days it takes the Vendor to supply the items (Lead Time) minus any additional time your organization requires to process the acquisition. Vendor Information fields This section includes the information about the vendor supplying the new quantities of the item. Vendor Location: The vendor/location supplying the items. Vendor Part Number Currency Code Exchange Rate Minimum Order Amount Status (from the BO lifecycle) Valid statuses include: Created Approved Held Canceled Oracle Utilities Work and Asset Management User Guide 174

175 Reorder Processed Stock Item Detail Definitions Stock Item Detail records define how a stock item is managed in the storeroom and manage and track quantities for stock items. Each record contains storeroom-specific information for the stock item such as pricing, reorder information, unit of issue, unit of purchase, expense code, and so on. Refer to the Adding a Stock Item to a Storeroom (Stock Item Details) section for more information. Storage Location Object s This section provides descriptions of the attributes used for storage location related objects as they are delivered in the base application. Storage Location Type Definitions Storage location types define the details of storage locations of a certain type. Valid locations might be storerooms, warehouses, receiving docks, or any other location as defined by your organization. Refer to the Defining a Storage Location Type section for more information. Business Object: W1-StorageLocationType Location Type: Unique name for the location type. : of the location type which appears in drop-down lists. Class: Used for reporting and establishes general characteristics of the location such as whether it is commercial or residential, a shop or warehouse, or any other possible categorization appropriate to your business. Location BO: Indicates the business object to use when creating locations of this type. Valid Parent Location/ Organization Types A parent location or organization can be referenced to establish a hierarchy for reporting purposes. Storage Location Definitions Storage locations define the physical location where assets or components are stored. Quantities are not tracked for storage locations. Refer to the Creating a Storage Location section for more information. Storage Location Storage locations are used to indicate the physical location where assets or components are stored. Storage locations use the same fields as Asset Locations with the exception that they do not include criticality fields. Business Object: W1-StorageLocation Oracle Utilities Work and Asset Management User Guide 175

176 Location Disposition: The current status of the location. Active or Inactive. : A useful description of the location which appears in drop-down lists. Parent Location/Organization: The parent location or organization can be referenced to establish a hierarchy for reporting purposes. External ID: Identification number used to associate the location in an external system. Address Information fields Contact fields Information fields Indicates the physical address for the location along with GPS information if applicable. The Location Class is used for reporting and establishes general characteristics of the location such as whether it is commercial or residential, a shop or warehouse, or any other possible categorization appropriate to your business. The primary contact associated to the location. This is linked to the Contact portal. The latitude and longitude coordinates where the activity will occur (usually for GPS). Storeroom with Inventory Management Business Object: W1-StoreroomInventoryManagemnt Location Disposition: The current status of the vehicle. Active or Inactive. : A useful description of the location which appears in drop-down lists. Parent Location/Organization: The parent location or organization can be referenced to establish a hierarchy for reporting purposes. External ID: Identification number used to associate the location in an external system. Contacts fields Main Contact: Indicates the Contact ID for the primary contact associated to the location. This is linked to the Contact portal. Supervisor: Indicates the Contact ID for the supervisor of the storeroom. This is linked to the Contact portal. Address Information fields Accounting Information fields Indicates the physical address for the location along with GPS information if applicable. The Location Class is used for reporting and establishes general characteristics of the location such as whether it is commercial or residential, a shop or warehouse, or any other possible categorization appropriate to your business. Inventory Cost Center: Indicates the cost center that will be charged for costs related to this storeroom. Inventory Expense Code: Indicates the expense code that will be charged for costs related to this storeroom. Inventory Adjustment Cost Center: Indicates the cost center that will be charged for costs related inventory adjustments in this storeroom. Markup Cost Center: Indicates the cost center that will be charged for markup costs related to this storeroom. Markup Expense Code: Indicates the expense code that will be charged for markup costs related to this storeroom. Stock Transfer Clearing Cost Center: Indicates the cost center that will be charged for costs related stock transfers involving in this storeroom. Storeroom Information fields Information fields Invoice Information fields Provides information about the storeroom such as the storeroom name, type, quality control storeroom and markup rate. The latitude and longitude coordinates where the activity will occur (usually for GPS). Provides default address and other contact information for invoices related to stock procurement in this storeroom. Oracle Utilities Work and Asset Management User Guide 176

177 Shipping Information fields Reorder Information fields Provides default address and other contact information for shipments related to stock procurement in this storeroom. Buyer: Indicates the buyer responsible for approving reorders in the storeroom. Reorder Review Approval Required: Indicates whether or not approval is required for automatic reorder of stock items in the storeroom. Purchasing Document Action: Indicates the default action for purchasing documents created in response to automatic reorder. Vehicle Vehicles are considered as storage locations within the Operational Device Management since if the asset is in transit and on a vehicle it is considered stored on that vehicle. It is also possible to reference vehicles within the system as fleet assets. Business Object: W2-Vehicle Location Disposition: The current status of the vehicle. Active or Inactive. : A useful description of the vehicle. Parent Location/Organization: The parent location or organization can be referenced to establish a hierarchy for reporting purposes. Contacts fields Crew: Indicates the crew assigned to the vehicle. Commodity Code Definitions Commodity Codes are an alternate way to describe stock items which can be helpful when you need to locate a specific stock code because they form a logical segmented code for a stock item. Codes are segmented by commodity category, name, type, and composition. The Stock Item portal can be searched by commodity code where you can filter by a variety of criteria. Refer to the Defining a Commodity Code section for more information. Commodity Category Business Object: W1-CommodityCategory Commodity Category: A unique name or code for the commodity category. : of the commodity category which appears in drop down lists. Commodity Names fields The second segment of the category. For each category, there is a unique list of commodity names. Commodity Name Business Object: W1-CommodityName Oracle Utilities Work and Asset Management User Guide 177

178 Commodity Name: The unique commodity name. : of the commodity name which appears in drop down lists. Commodity Type fields The third segment of the category. For each category and name combination, there is a unique list of commodity types. Commodity Type Business Object: W1-CommodityType Commodity Type: The unique commodity type. : of the commodity type which appears in drop down lists. Commodity Composition fields The fourth segment of the commodity code. For each category/name/type combination, there is a unique list of commodity compositions. Purchasing Object s This section provides descriptions of the attributes used for purchasing related objects as they are delivered in the base application. Refer to the Understanding Purchasing section for a conceptual overview of this functional area. Buyer Definitions Buyers are persons designated within your organization to make purchases and purchasing decisions. Refer to the Defining a Buyer section for more information. Business Object: W1-Buyer Buyer: A unique name or code for the buyer. User: The system username of the person defined as the buyer. : A useful description of the buyer which will appear in drop-down lists. Contact Information: The phone, fax and numbers for this buyer. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Oracle Utilities Work and Asset Management User Guide 178

179 Vendor Object s This section provides descriptions of the attributes used for vendor related objects as they are delivered in the base application. Vendor Definitions Use the Vendor portal to maintain information about vendors, including their capabilities payment terms and delivery terms and various vendor sites. The vendor location distinguishes between multiple sites for one vendor. Refer to the Working with Vendors and Manufacturers section for more information. Business Object: W1-Vendor Vendor: A unique name or code for the vendor. Vendor Name (): A useful description of the vendor which will appear in drop-down lists. Website: The URL of the vendor's website, as applicable. Vendor Location Definitions Use the Vendor portal to maintain information about vendors, including their capabilities payment terms and delivery terms and various vendor sites. The vendor location distinguishes between multiple sites for one vendor. Refer to the Adding a Vendor Location section for more information. Vendor Location Business Object: W1-VendorLoc Location Details fields Purchasing Details fields Location Name: The unique name or code for the vendor location. Provides the information for the vendor address including country, state, full address, currency, payment terms, and so on. Order From: Indicates whether or not the vendor location accepts orders. Allowed/Not Allowed. PO: Indicates whether or not purchase orders should be ed to this vendor location. Allowed/Not Allowed. After the purchase order is issued, an option becomes available under Additional Processes to the order. PO Address: The address where purchase orders should be sent for this location. This is required if PO is allowed. Minimum Order Amount: Indicates a dollar amount which is the minimum the vendor location will accept for one order. Contacts fields Payment Details fields Main Contact Indicates the Contact ID for the primary contact associated to the location. This is linked to the Contact portal. Pay To: Indicates whether or not the vendor location handles its own billing. Allowed/Not Allowed Oracle Utilities Work and Asset Management User Guide 179

180 Pay To Vendor: When Pay To is set to Not allowed this field indicates the name of the vendor location that handles the billing in place of this vendor location. The valid vendor locations to select here are alternate vendor locations for the same vendor. This is required if Pay To is set to Not Allowed. Pay Tax To Vendor: Indicates whether or not sales tax is paid to this vendor location. Yes/No Payment Terms: Indicates the terms for paying the vendor such as Net 30. This fields is controlled by the Payment Terms portal. Discount : Free form text field to provide information about any discounts negotiated with the vendor. Auto Pay Indicates that an invoice will be automatically created for the purchase order upon receipt. Capabilities fields Status (from the BO lifecycle) Defines a list of capability types for the vendor location. For example, for one vendor with multiple locations, one location might offer pick up at that location whereas another may not. Valid statuses include: Under Review Active Inactive Capability Type Definitions Capability types refer to the types of products and services provided by a vendor. They are referenced on vendor locations to help identify what the vendor can provide, per location. Refer to the Defining a Capability Type section for more information. Capability Type: A unique name or code for the capability type. : A useful description of the capability type which will appear in drop-down lists. Payment Term Definitions Payment terms represent the payment and credit agreement between your organization and the vendor such as the number of days your organization has to pay the invoice or the forms of payment that are accepted. Refer to the Defining a Vendor Payment Term section for more information. Business Object: W1-PaymentTerm Payment Term: A unique name or code for the payment term. : A useful description of the payment term which will appear in drop-down lists. Number of Days: Indicates the time frame required by the vendor for payment after the invoice is issued, such as Net 30 or Net 60. If Fixed Day is set, this value is not used. Fixed Day: Indicates a fixed day of the month that payment is due after the invoice is issued. If Number of Days is set, this value is not used. Discount %: Indicates the pre-negotiated discount given by the vendor, if any. Oracle Utilities Work and Asset Management User Guide 180

181 Free on Board Definitions Freight on Board or Free on Board (FOB) represents the delivery charge terms negotiated for purchase orders from the vendor. This also includes the vendor or the seller's obligation to deliver goods at a designated place. Refer to the Defining a FOB (Freight on Board or Free on Board) section for more information. Business Object: W1-Fob FOB: A unique name or code for the FOB. : A useful description of the FOB. Purchase Order Object s This section provides descriptions of the attributes used for purchase order related objects as they are delivered in the base application. Purchase Requisition Header Definitions Purchase requisitions are used to store and track requests for material resources and/or services. Refer to the Creating a Purchase Requisition Manually section for more information. Purchase Requisition Header Business Object: W1-PRHeader Requisition Type: Indicates where the purchase requisition is being generated from such as from a blanket contract, stores replenishment or from a work record. Initiating Blanket Contract: Indicates the blanket contract ID of the related blanket contract for the purchase, as applicable. Note: In most cases the purchase request would be created from the blanket contract, however, it is possible to create a purchase requisition first, then reference a blanket contract. This field would be used in such a case. : A description of the purchase. Requisition Information fields Vendor Location Information fields Accounting Information fields Provides information about the requisition such as the requestor and buyer, contact information, and dates. The Buyer is usually the person responsible for purchases, typically with the vendor of the stock item, material or service type. The Buyer can be different from the person indicated in the Requested By. Provides the information related to the vendor with whom the purchase requisition is negotiated. This includes the vendor location, contact ID, a carrier if applicable, currency, FOB, payment terms and whether or not this is an auto pay vendor. Project: Indicates the project ID of the project related to the work related to the the purchase, as applicable. Cost Center: List of cost centers which will incur costs for charges against the purchase requisition. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status Valid statuses include: Oracle Utilities Work and Asset Management User Guide 181

182 (from the BO lifecycle) Created Pending Approval Approved Canceled Rejected Partially Processed PO Processed Blanket Contract Processed Purchase Requisition Line Item Definitions Purchase requisitions are used to store and track requests for material resources and/or services. Refer to the Adding Line Items to a Purchase Requisition section for more information. Stock Item Purchase Requisition Line Business Object: W1-PRSILine Provides the information for a line item on a requisition where stock is being ordered. Stock Item Code: The record number for the stock item. Storeroom: The housing storeroom for the stock item. This is the Storeroom Location referenced on the Stock Item Detail associated to the Stock Item. Stock Item Detail: The storage details record for the stock item. : A description of the line item. Requisition Line Information fields Item Number: A sort of sequence number for the line item. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Unit of Purchase: The unit of purchase for the item such as each or box. Unit of Issue: The way in which the item is issued in your storerooms. Purchase to Issue Ratio: The difference between how you buy the item and how you issue it. You may, for instance, issue in individual items but order the items by the box where one box would contain 10 individual items. The Unit of Purchase would then be BOX, the Unit of Issue would be EA, and the P/I Ratio would be 10. The system uses the Unit of Purchase, Unit of Issue, and Purchase to Issue Ratio information to maintain quantities as parts are issued and new parts are received. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Expedite: Yes or No value to indicate whether or not this is an expedited order. Oracle Utilities Work and Asset Management User Guide 182

183 Print Price: Yes or No value to indicate whether or not prices should be printed on the requisition. Purchase Order Line ID: The record number for the related purchase order, as applicable. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Manufacturer Information fields Status (from the BO lifecycle) Indicates the manufacturer and manufacturer part number for the item. Valid statuses include: Created Approved Canceled PO Processed Blanket Contract Processed Craft Purchase Requisition Line Business Object: W1-PRCrLine Defines a requisition line item for procuring craft resources. Craft Code: Indicates the code for the skill of the person or resource being hired. Project: The related project ID, as applicable. : A description of the line item. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Requisition Line Information fields Item Number: A sort of sequence number for the line item. Hours: The number of expected work hours for the craft. Hourly Rate: The hourly wage for the craft. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Expedite: Yes or No value to indicate whether or not this is an expedited order. Print Price: Yes or No value to indicate whether or not prices should be printed on the requisition. Purchase Order Line ID: The record number for the related purchase order, as applicable. Status (from the BO lifecycle) Valid statuses include: Created Oracle Utilities Work and Asset Management User Guide 183

184 Approved Canceled PO Processed Blanket Contract Processed Purchase Requisition Equipment Line Business Object: W1-PREqLine Defines a requisition line item for procuring a piece of equipment. Equipment Code: Indicates the specific piece of equipment being ordered. Project: The related project ID, as applicable. : A description of the line item. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Requisition Line Information fields Item Number: A sort of sequence number for the line item. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Unit of Measure (UOM): Indicates how the equipment is ordered. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Expedite: Yes or No value to indicate whether or not this is an expedited order. Print Price: Yes or No value to indicate whether or not prices should be printed on the requisition. Status (from the BO lifecycle) Valid statuses include: Created Approved Canceled PO Processed Blanket Contract Processed Purchase Requisition Other Line Business Object: W1-PRORLine Defines a requisition line item for procuring a other materials or services not covered by the other options. Oracle Utilities Work and Asset Management User Guide 184

185 Other: Indicates the other resource being ordered. Project: The related project ID, as applicable. : A description of the line item. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Requisition Line Information fields Item Number: A sort of sequence number for the line item. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Unit of Measure (UOM): Indicates how the equipment is ordered. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Expedite: Yes or No value to indicate whether or not this is an expedited order. Print Price: Yes or No value to indicate whether or not prices should be printed on the requisition. Status (from the BO lifecycle) Valid statuses include: Created Approved Canceled PO Processed Blanket Contract Processed Purchase Order Header Definitions Purchase orders are contracts placed with vendors for the purchase of materials or services. Purchase Order records contain general information about the purchase including the requestor, when items are required, the vendor, and more. Refer to the Creating a Purchase Order Manually section for more information. Purchase Order Header Business Object: W1-PurchaseOrderHeader Purchase Document Type: Indicates where the purchase order is being generated from such as from a blanket contract, stores replenishment or from a work record. Approval Profile: The approval profile to route the approval request to for the purchase order. : A description of the purchase. Oracle Utilities Work and Asset Management User Guide 185

186 Order Information fields Provides information about the order such as the requested by and buyer, contact information, and dates. Buyer: Usually the person responsible for purchases, typically with the vendor of the stock item, material or service type. The Buyer can be different from the person indicated in the Requested By. Issue Date: Indicates the date that the purchase order was issued to the vendor. Required by Date: Indicates the date that the items on the order are required by your organization. This is typically negotiated with the vendor. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Shipping Information fields Ship To Location: Storeroom location where the goods should be shipped. Deliver To Location: Storeroom location where the goods should be delivered. Deliver To: Free form text. This can be the name of a person or a facility. Vendor Informationfields Blanket Contract Information fields Accounting Information fields Provides the information related to the vendor with whom the purchase order is negotiated. This includes the vendor location, contact ID, a carrier if applicable, currency, FOB, payment terms and whether or not this is an auto pay vendor. Blanket Contract: Indicates the blanket contract ID of the related blanket contract for the purchase, as applicable. Project: Indicates the project ID of the project related to the work that generated the purchase, as applicable. Cost Center: List of cost centers which will incur costs for charges against this purchase order. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Determine if Approval Needed Pending Approval Approved Rejected Issued Canceled Closed Purchase Order Line Item Definitions Purchase orders are contracts placed with vendors for the purchase of materials or services. Purchase Order records contain general information about the purchase including the requestor, when items are required, the vendor, and more. Refer to the Adding Line Items to a Purchase Order section for more information. Stock Item PO Line Business Object: W1-StockItemPOLine Provides the information for a line item on a purchase order where stock is being ordered. Oracle Utilities Work and Asset Management User Guide 186

187 Purchase Order Header: The purchase order record number. Stock Item Detail: The record number for the stock item. Storeroom: The housing storeroom for the stock item. : A description of the line item. Activity: The reference activity ID, as applicable. Purchase Requisition Line: The corresponding line item on the related purchase requisition, as applicable. Blanket Contract Line: The corresponding line item on the related blanket contract, as applicable. Order Line Information fields Item: A sort of sequence number for the line item. Item Type: Indicates whether the item is for materials, services or other. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Unit of Purchase (UOP): The unit of purchase for the item such as each or box. Purchase to Issue Ratio: The difference between how you buy the item and how you issue it. You may, for instance, issue in individual items but order the items by the box where one box would contain 10 individual items. The Unit of Purchase would then be BOX, the Unit of Issue would be EA, and the P/I Ratio would be 10. Allow Substitutes: Indicates that you do not want the vendor to substitute the item with an alternate. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Accounting Information fields Project: The project for which goods are being purchased, as applicable. Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against this line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Approved Issued Canceled Closed Craft PO Line Defines a purchase order line item for hiring an external worker or contractor as a craft resource. Oracle Utilities Work and Asset Management User Guide 187

188 Craft: Indicates the skill of the person or resource being hired. : A description of the line item. Activity: The reference activity ID, as applicable. Purchase Requisition Line: The corresponding line item on the related purchase requisition, as applicable. Blanket Contract Line: The corresponding line item on the related blanket contract, as applicable. Order Line Information fields Item: A sort of sequence number for the line item. Item Type: Indicates whether the item is for materials, services or other. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. UOP: The unit of purchase for the item such as each or box. Allow Substitutes: Indicates that you do not want the vendor to substitute the item with an alternate. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Accounting Information Project: The project for which goods are being purchased, as applicable. Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Approved Issued Canceled Closed Equipment PO Line Business Object: W1-EquipmentPOLine Defines a purchase order line item for procuring a piece of equipment. Equipment: Indicates the specific piece of equipment being ordered. : A description of the line item. Activity: The reference activity ID, as applicable. Oracle Utilities Work and Asset Management User Guide 188

189 Purchase Requisition Line: The corresponding line item on the related purchase requisition, as applicable. Blanket Contract Line: The corresponding line item on the related blanket contract, as applicable. Order Line Information fields Item: A sort of sequence number for the line item. Item Type: Indicates whether the item is for materials, services or other. Informational only. Quantity: The amount of the item being ordered. Unit Price: The price of the item. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. UOP: The unit of purchase for the item such as each or box. Allow Substitutes: Indicates that you do not want the vendor to substitute the item with an alternate. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Accounting Information Project: The project for which goods are being purchased, as applicable. Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Approved Issued Canceled Closed Other Resource PO Line Business Object: W1-OtherResourcePOLine Defines a purchase order line item for procuring a other materials or services not covered by the other options. Other: Indicates the other resource being ordered. : A description of the line item. Activity: The reference activity ID, as applicable. Purchase Requisition Line: The corresponding line item on the related purchase requisition, as applicable. Blanket Contract Line: The corresponding line item on the related blanket contract, as applicable. Order Line Information fields Item: A sort of sequence number for the line item. Item Type: Indicates whether the item is for materials, services or other. Informational only. Oracle Utilities Work and Asset Management User Guide 189

190 Quantity: The amount of the item being ordered. Unit Price: The price of the item. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. UOP: The unit of purchase for the item such as each or box. Allow Substitutes: Indicates that you do not want the vendor to substitute the item with an alternate. Required By Date: The date that the item is needed. Promise Date: The date that the vendor has indicated the item will be shipped or delivered. Vendor Part Number: The vendor's part number for the item. Accounting Information Project: The project for which goods are being purchased, as applicable. Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against this line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Approved Issued Canceled Closed Expedite Purchase Order Definitions The expedite order process helps buyers and other purchasers to ensure that required goods arrive at the appointed date in the agreed quality at the agreed location. Refer to the Creating an Expedite Order section for more information. Business Object: W1-Expedite Expedite Information fields Purchase Order: The number for the purchase order being expedited. Includes information such as the vendor, buyer, comments and expected and promise dates. The Yes/No Confirmed field allows you to record whether or not the expedite order is verified with the vendor. Vendor Contact: Free form text field indicating the contact person you are working with to expedite the order. Buyer: The buyer ID of the person responsible for the order. Confirmed: Yes/No selection provides an informal status for the expedite order. Comments: Free form text field to provide information about the expedite order. Expedite Date: The date that the expedite order was initiated with the vendor. Similar to the issue date on the original purchase order. Oracle Utilities Work and Asset Management User Guide 190

191 Items fields Promise Date: The date that the vendor has indicated the item will be shipped or delivered. These fields identify the item to be expedited along with a status data and an estimated delivery date. The Status field Item Sequence Status: Provides information such as whether the item is backordered, ready or shipped. Status Date: The date that the status was updated. Estimated Delivery: The expedited delivery date negotiated with the vendor. Shipment Quantity: The amount to ship. Shipment: Free form text field for information about the shipment. Reason Code: Allows the buyer to provide information such as whether the expedite order is being initiated because of an outage or there is just a rush for the shipment. Status (from the BO lifecycle) Valid statuses include: Open Canceled Closed Blanket Contract Object s This section provides descriptions of the attributes used for blanket contract related objects as they are delivered in the base application. Blanket Contract Definitions A blanket contract is a purchasing agreement that your organization makes with a supplier to pre-plan the purchase of materials or services. These contracts typically contain multiple delivery dates over a period of time, often negotiated to take advantage of predetermined pricing or special discounts. Refer to the Working with Blanket Contracts section for more information. Blanket Contract Header Business Object: W1-BCHeader Contract Information fields : A description of the blanket contract which will appear in drop-down lists. Limit Amount: The dollar value limit for the contract. Enforce Limit: If the Enforce Limit indicator is set to No, the Limit Amount field only acts as a suggestion. If set to yes, the system will not allow total purchase orders against the contract to exceed the Limit Amount. Initiation Date: The initiation date is the first date the blanket contract can be used. Expiration Date: The expiration date indicates the date by which the contract must be renegotiated. Oracle Utilities Work and Asset Management User Guide 191

192 Buyer: The buyer code shows the buyer assigned to monitor the contract. You can grant access to the contract to other users using the access list fields. Lead Time Days: This value indicates the number of days that the vendor has estimated it will take to deliver the items on the blanket contract. Blanket Category: The category field provides information indicating the type of contract such as whether it is for goods or services. Accounting Information fields Cost Center: List of cost centers which will incur costs for charges against the blanket contract. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Vendor Information fields Access List fields Provides the information related to the vendor with whom the blanket contract is negotiated. This includes the vendor location, contact ID, a carrier if applicable, currency, FOB, payment terms and whether or not this is an auto pay vendor. Blanket Contract Access List: Indicates the blanket contract access list that is in effect for this contract. The access list defines a list of users who are authorized to commit purchases against the blanket contract. Restrict to Access List: Defines a yes or no value to indicate whether or not the access list must be honored for the blanket contract. If set to Yes, only users on the access list can create purchase orders from the blanket contract. If set to No, anyone can create purchase orders up to the default limit set on the contract. Default Limit: If the blanket contract is not restricted to an access list, this field provides a dollar value limit for the blanket contract. A limit can also be set on the access list for each individual user. If this value is set to zero, users who are not on the access list cannot create a purchase order from the blanket contract. Status (from the BO lifecycle) Valid statuses include: Created Awaiting Activation Active Closed Suspended Blanket Contract Line Definitions A blanket contract is a purchasing agreement that your organization makes with a supplier to pre-plan the purchase of materials or services. These contracts typically contain multiple delivery dates over a period of time, often negotiated to take advantage of predetermined pricing or special discounts. Blanket Contract Stock Item Line Business Object: W1-BCStockItemLine Provides the information for a line item on a blanket contract where stock is being ordered. Blanket Contract Line Information Allow on PO: Indicates whether or not the item can be included on the purchase order or requisition when it is created from the blanket contract. The item does not appear on the item pick list if it is not allowed. This indicator is used in higher revisions where certain items may cease to be covered by the blanket contract. : Provides a description of the item. Oracle Utilities Work and Asset Management User Guide 192

193 Stock Item: Indicates the stock code for the item as it is defined in your organization's stock item details (storeroom). Unit Price: Indicates the price of the item. Lead Time Days: Indicates the number of days it is expected that it will take the for the vendor to supply the item after it is ordered. Unit of Purchase: Indicates purchasing units such as each or box. Purchase to Issue Ratio: Indicates the difference between how you buy the item and how you issue it. You may, for instance, issue in individual items but order the items by the box where one box would contain 10 individual items. The Unit of Purchase would then be BOX, the Unit of Issue would be EA, and the P/I Ratio would be 10. Stock Type: Provides information such as whether the item is hazardous, perishable, a raw material, and so on. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the blanket contract line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Manufacturer Information fields Manufacturer Manufacturer Part Number Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Complete Blanket Contract Craft Line Business Object: W1-BCCraftLine --> Defines a blanket contract line item for hiring a special worker or contractor related to a craft. Blanket Contract Line Information Allow on PO: Indicates whether or not the item can be included on the purchase order or requisition when it is created from the blanket contract. The item does not appear on the item pick list if it is not allowed. This indicator is used in higher revisions where certain items may cease to be covered by the blanket contract. : Provides a description of the resource type. Craft: Indicates the skill of the person or resource being hired on this blanket contract. Unit Price: Indicates the cost for the craft resource. Lead Time Days: Indicates the number of days it is expected that it will take the for the vendor to supply the item after it is ordered. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Oracle Utilities Work and Asset Management User Guide 193

194 Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the blanket contract line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Complete Blanket Contract Equipment Line Business Object: W1-BCEquipmentLine Defines a blanket contract line item for procuring a piece of equipment. Blanket Contract Line Information Allow on PO: Indicates whether or not the item can be included on the purchase order or requisition when it is created from the blanket contract. The item does not appear on the item pick list if it is not allowed. This indicator is used in higher revisions where certain items may cease to be covered by the blanket contract. : Provides a description of the resource type. Equipment: Indicates the specific piece of equipment being ordered on this blanket contract. Unit Price: Indicates the cost. Lead Time Days: Indicates the number of days it is expected that it will take the for the vendor to supply the item after it is ordered. Unit of Purchase: Indicates purchasing units such as one or pallet. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the blanket contract line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Complete Blanket Contract Other Line Business Object: W1-BCOtherLine --> Defines a blanket contract line item for procuring a other materials or services not covered by the other options. Oracle Utilities Work and Asset Management User Guide 194

195 Blanket Contract Line Information Allow on PO: Indicates whether or not the item can be included on the purchase order or requisition when it is created from the blanket contract. The item does not appear on the item pick list if it is not allowed. This indicator is used in higher revisions where certain items may cease to be covered by the blanket contract. : Provides a description of the resource type. Other: Indicates the other resource type being ordered on this blanket contract. Unit Price: Indicates the cost. Lead Time Days: Indicates the number of days it is expected that it will take the for the vendor to supply the item after it is ordered. Unit of Purchase: Indicates purchasing units such as one or pallet. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the blanket contract line item. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Status (from the BO lifecycle) Valid statuses include: Created Ready for Revision Revised Complete Blanket Contract Access List Definitions Blanket contract access lists identify which users have the authority to create charges against a blanket contract. The list also establishes a maximum dollar amount that the user is authorized to charge for a single purchase order. Refer to the Defining a Blanket Contract Access List section for more information. Business Object: W1-BCAccessList Blanket Contract Access List: A unique name or code for the access list. : A useful description of the access list which will appear in drop-down lists. User Information fields User: The list of users with authorization on the list being created. Limit: The maximum dollar amount for which the user is allowed to create blanket contracts Manufacturer Definitions Use the Manufacturer portal to define attributes for product manufacturers. Refer to the Defining a Manufacturer section for more information. Business Object: W1-Manufacturer Oracle Utilities Work and Asset Management User Guide 195

196 Manufacturer: A unique name or code for the manufacturer. : A useful description of the manufacturer which will appear in drop-down lists. Purchase Commodity Definitions Purchase commodities are used to assign a specific buyer to a classification of stock items in the storeroom. Refer to the Defining a Purchase Commodity section for more information. Business Object: W1-PurchaseCommodity Purchase Commodity: A unique name or code for the commodity. : A useful description of the commodity which will appear in drop-down lists. Buyer: The buyer ID of the person typically responsible for this commodity. This connection is used to assign the buyer to a classification of stock items in the storeroom. Resource Management Object s This section provides descriptions of the attributes used for resource management related objects as they are delivered in the base application. Refer to the Understanding Resource Management section for a conceptual overview of this functional area. Organization Object s This section provides descriptions of the attributes used for organization related objects as they are delivered in the base application. Organization Type Definitions Organization types define the main attributes for organizations of a certain type. Refer to the Defining Organization Types section for more information. Business Object: W1-OrganizationType Organization Type: A unique name or code for the organization type. : A useful description of the organization type which will appear in drop-down lists. Class: An additional way to categorize the organization type according to your business practices. Organization BO: The business object that will used to create organizations of this type. Valid Parent Location/ Organization Types fields The parent location or organizations that can be referenced to establish a hierarchy for reporting purposes. Oracle Utilities Work and Asset Management User Guide 196

197 Organization Definitions Organizations are used for categorization and reporting for locations. Refer to the Creating an Organization section for more information. Business Object: W1-Organization Organization Disposition: The status of the organization. Active or Inactive. : A useful description of the organization. The description can be used as search criteria to help find records, so it is helpful if it contains text that would make the organization easy to find. Parent Location/Organization ID: The parent location or organization that can be referenced to establish a hierarchy for reporting purposes. Resource Type Definitions Resource types define classes of resources that are used within your organization, usually to complete work. The system is delivered with craft, equipment, stock items, documents, and other as base package resource types. Your organization may define others depending on your business practices. Stock Item Resource Type Business Object: W1-StockItem Identifies a type of material inventory item. General stock items are created with the trackable and lot managed flags set to false on the stock item record. Please refer to the Entering a Stock Item section for more information. Stock Item Code: A unique name or code for the stock item type. : A useful description of the stock item type which will appear in drop-down lists. Detailed : More information about the stock item type. Accounting Information fields Inventory Expense Code: Indicates the expense code that will be charged for costs related to the storeroom housing the stock item. Usage Expense Code: Indicates the expense code that will be charged for costs related to the stock item being utilized. Commodity Coding Information fields Category: Commodity Category is the most general description of the item. A sample category code might be M for a piece of mechanical equipment. Name: For each category, there is a unique list of Commodity Names. A sample commodity name for mechanical equipment might be a Check Valve. Type: For each category and name combination, there is a unique list of Commodity Types. A sample commodity type for a check valve might be a high-pressure pneumatic check valve. Composition: For each category/name/type combination, there is a unique list of Commodity Compositions. The composition code is used to indicate the primary material in the item (e.g. titanium alloy). Oracle Utilities Work and Asset Management User Guide 197

198 Stock Item Information fields Size Stock Item Category: Categorization for stock items based on your organization's business practices. Hazardous/Hazardous Type: Indicates that the item may be hazardous in some way, and the type of hazard. Lot Managed: Lot managed items are also tracked in a special way in the system. These types of items are fabricated, sold, and delivered in lots or batches of the item. This is significant when there are qualities or details about the item that might vary between lots. If this item is lot managed, the system tracks a lot number with any transaction that changes the quantity of the item for the storeroom. Since each received lot also has its inventory tracked independently, lot managed item details all have child" stock item details for each lot that is received. This means a master stock item detail that is classified as "lot managed" on its stock item detail with many lot" stock item details (one for every lot that is received). When an activity references lot managed items as a resource requirement, the master stock item detail is referenced. Lots only become relevant when material is issued from or received into inventory. This means the material issue for lot managed stock items reference a lot stock item detail, but the planned activity references the master stock item detail. Shelf Life Days: Indicates the number of days that perishable items can remain in stores before it is no longer useful. Capital Spare: Indicates that the item is a relatively valuable piece of equipment kept in house as backup if the item primarily used should fail. Items such as a spare motor or generator might fall into this category. Tracked Asset Information fields Trackable: Trackable stock items merit being individually identified and followed from initial receipt on-site through complete usage. These are typically large, expensive or specialized assets or materials which are inspected when they are received into inventory, repaired if they break, can be installed on other assets, and are otherwise carefully dispositioned in the system. Repairable: Indicates whether or not the item is eligible to be repaired if it fails. Purchase Details fields Unit of Purchase/Unit of Issue/Purchase to Issue Ratio: The system uses the Unit of Purchase, Unit of Issue, and Purchase to Issue Ratio information to maintain quantities as parts are issued and new parts are received. You may, for instance, issue in individual items but order the items by the box where one box would contain 10 individual items. The Unit of Purchase would then be BOX, the Unit of Issue would be EA, and the P/ I Ratio would be 10. Tax Rate Schedule: Indicates the tax schedule applicable to the purchase. The drop down list is defined by entries in the Tax Rate Schedule portal. Purchase Commodity: The commodity classification for the stock item. Allow Substitutes: Indicates that you do not want the vendor to substitute the item with an alternate. Miscellaneous Information fields Truck Stock: Truck stock items are typically smaller, inexpensive items that are carried on the crew's work truck and not checked out from the storeroom. Check this box to indicate that this stock item is considered to be this type of item. Accept on Receipt: Applies to purchased resources to indicate whether or not the item can be accepted when it is received and does not have to be inspected. Default Values to Activity: Indicates whether or not the stock item information should be defaulted onto activities when resource requirements reference the stock item. If this is set to No, then the stock item can only be added to stock item details as a direct purchase item. Add to BOM on Material Issue: Indicates whether or not the system should automatically create a bill of materials reference when the item is issued. This helps to save time for future material requirements by earmarking the item as needed for related work. When the system issues stock to an activity that is linked to an asset, and that asset (or its specification) has a BOM reference, then the system updates that BOM to include the stock that was issued for that activity. Oracle Utilities Work and Asset Management User Guide 198

199 Vendors fields Vendor Location Indicates the specific vendor site that supplies the item. Vendor Part Number Vendor Priority: Used to denote which is the primary supplier of the item. At least one vendor must be set as primary. Alternate Stock Items fields Manufacturer fields Stock Item: Provides the record IDs of any stock items that can be used as substitutes for the current item. These alternates are offered as suggestions on material requirements when the primary item is out of stock. Manufacturer: The manufacturer of the item, as applicable. Copy to PO: Indicates whether or not manufacturer information should be automatically copied to purchasing records when they are created referencing the stock item. Manufacturer Part Number BOM Part: Indicates the record ID for the bill of materials part reference to the stock item. A BOM Part is automatically created for each manufacturer row. This is useful when building a full BOM, for an asset for instance. The BOM can can be specific down to the manufacturer level. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Craft Resource Type Business Object: W1-Craft A type of craft resource. Typically a special skill or contract worker. Please refer to the Creating a Craft section for more information. Craft Code: A unique name or code for the craft type. : A useful description of the craft type which will appear in drop-down lists. Detailed : More information about the craft type. Resource Source: Provides a reference to where the craft resource can be located or obtained. Internal or Purchased. Default Values to Activity: Indicates whether or not the item information should be defaulted onto activities when resource requirements reference the craft. If this is set to No, then the stock item can only be added to stock item details as a direct purchase item. Accept on Receipt: Applies to purchased resources to indicate whether or not the item can be accepted when it is received and does not have to be inspected. Accounting Information fields Scheduling Information fields Regular/Premium Expense Code: Indicates the expense code that will be charged from work completed by this craft. Premium expenses usually signify overtime or other special hourly rates. Schedule Priority: A numerical value which is used to denote the order in which the principal craft duration is determined when labor requirement assignments are made to a secondary craft. 1 is a high priority and 999 is a low priority. The default is 100. If two crafts have the same secondary craft, they should be set with different priorities. Oracle Utilities Work and Asset Management User Guide 199

200 Status (from the BO lifecycle) Secondary Crafts: Defines a lift of crafts that can act as backup as for this craft. Valid statuses include: Created Active Inactive Equipment Resource Type Business Object: W1-Equipment A type of equipment resource. Please refer to the Entering Equipment section for more information. Equipment Code: A unique name or code for the equipment type. : A useful description of the equipment type which will appear in drop-down lists. Detailed : More information about the equipment type. Resource Source: Provides a reference to where the equipment can be located or obtained. Internal or Purchased. Default Values to Activity: Indicates whether or not the stock item information should be defaulted onto activities when resource requirements reference the stock item. If this is set to No, then the stock item can only be added to stock item details as a direct purchase item. UOM: Units used to measure the equipment. Accept on Receipt: Applies to purchased resources to indicate whether or not the item can be accepted when it is received and does not have to be inspected. Accounting Information fields Status (from the BO lifecycle) Cost Center/Expense Code: Indicates the cost centers and expense codes that will be charged when this type of equipment incurs costs. Valid statuses include: Created Active Inactive Other Resource Resource Type Business Object: W1-Other A type of other resource. Please refer to the Entering an Other Resource section for more information. Other Resource Code: A unique name or code for the resource type. : A useful description of the resource type which will appear in drop-down lists. Detailed : More information about the resource type. Oracle Utilities Work and Asset Management User Guide 200

201 Resource Source: Provides a reference to where the resource can be located or obtained. Internal or Purchased. Default Values to Activity Indicates whether or not the stock item information should be defaulted onto activities when resource requirements reference the stock item. If this is set to No, then the stock item can only be added to stock item details as a direct purchase item. UOM: Units used to measure the resource. Fixed Unit Price: Indicates whether or not the unit price can be altered by users when they are creating a other direct charge against this resource. Accept on Receipt: Applies to purchased resources to indicate whether or not the item can be accepted when it is received and does not have to be inspected. Accounting Information fields Status (from the BO lifecycle) Cost Center/Expense Code: Indicates the cost centers and expense codes that will be charged when this type of equipment incurs costs. Valid statuses include: Created Active Inactive Contact Object s This section provides descriptions of the attributes used for contact related objects as they are delivered in the base application. Contact Type Definitions Contact types establish parameters for contact of a specific type. Refer to the Defining a Contact Type section for more information. Business Object: W1-ContactType Contact Type: A unique name or code for the contact. : A useful description of the contact which will appear in drop-down lists. Contact Business Object: The business object that will be used when creating contacts of this type. Contact Definitions Contacts are usually individuals or business entities who should be contacted in reference to a service point, work or any other issues. Please refer to the Creating a Contact section for more information. Business Business Object: W1-Business Oracle Utilities Work and Asset Management User Guide 201

202 Use business contacts to define the main attributes for businesses that your organization works with or that are associated to locations. Company Name: The business name. Business Phone: The business phone number. The primary business address. External ID: An identification number or code that can tie the contact to a related contact or person in an external system. This is used for integration. Contact Type: The contact type upon which the contact was based. Person Business Object: W1-Person Use person contacts to define the main attributes for individuals that your organization works with or that are associated to locations. Name: The contact name. Home Phone: The contact home phone number. Mobile Phone: The contact mobile phone number. The contact address. External ID: An identification number or code that can tie the contact to a related contact or person in an external system. This is used for integration. Employee Business Object: W1-PersonWAM Name: The contact name. Home Phone: The contact home phone number. Mobile Phone: The contact mobile phone number. The contact address. External ID: An identification number or code that can tie the contact to a related contact or person in an external system. This is used for integration. Employee: The employee number for the person. Contact Synchronization Add Business Object: W1-SynchronizationAddContact Used to synchronize contacts when integrating with other systems. Oracle Utilities Work and Asset Management User Guide 202

203 Contact ID: Free form text. A unique identifier for the contact. Contact Type: Free form text. A classification for contacts. Business Object: Indicates which related algorithm synchronizes the contacts. Create Date/Time: Provides the system date and type for the contact from the external system. Identifier Value Free form text. An additional identifier for the contact. Crew Object s This section provides descriptions of the attributes used for crew related objects as they are delivered in the base application. Crew Type Definitions Crew types define the kinds of crews that can be defined for your organization. For example, your organization might use crew types to define regular crews, skilled crews, and novice crews. Refer to the Defining a Crew Type section for more information. Business Object: W1-CrewType Crew Type: A unique name or code for the crew type. : A useful description of the crew type which will appear in drop-down lists. Crew Business Object: The business object that will be used when creating crew type of this type. Planning Horizon Days: The number of days into the future to plan for crew shifts. For example, if the planning horizon is set to 60, the system generates crew shifts sixty days into the future. Generation occurs in a sliding window in that each day generates data for the last day incrementally. At any given time, the number of days of planned shifts is equal to this value. Crew Definitions A crew is a group of workers that can be assigned to complete work. Crews are used to group workers, schedule work, and help organize work schedules. Refer to the Creating a Crew section for more information. Crew Business Object: W1-CrewWithCraft Crew Members fields Crew Name: A unique name or code for the crew. Employee: The employee ID for the crew member. Role: Indicates whether the crew member is the supervisor or simply a crew member. Oracle Utilities Work and Asset Management User Guide 203

204 Default Crew Service Areas fields Default Crew Service Classes fields Status (from the BO lifecycle) Service Area: Defines the boundaries of the crew's work area. Service Area Usage: Indicates the crew's restrictions with respect to the service area. Service Classes: Defines the classification for the work that the crew performs. Service Class Usage: Backup/Principle. Indicates the crew's role with respect to the service class. Valid statuses include: Active Inactive Crew Shift Object s This section provides descriptions of the attributes used for crew shift related objects as they are delivered in the base application. Crew Shift Type Definitions Crew shift types establish the kind of crew shift such as day, night, swing, and so on. Refer to the Defining a Crew Shift Type section for more information. Daily Schedule Type Business Object: W1-DailyScheduleType Defines the defaults for daily crew shifts of a certain type. Crew Shift Type: A unique name or code for the crew shift type. : A useful description of the crew shift type which will appear in drop-down lists. Start/End Time: The default start and end times for crew shifts of this type. Crew Shift Business Object: The business object that will be used when creating crew shift of this type. Crew Shift Template Business Object: The business object that will be used when creating crew shift template of this type. Crew Shift Differential Differential Calculation Type Weekly Schedule Type Business Object: W1-SchedulePlanType Defines the defaults for weekly crew shifts of a certain type. Crew Shift Type: A unique name or code for the crew shift type. : A useful description of the crew shift type which will appear in drop-down lists. Oracle Utilities Work and Asset Management User Guide 204

205 Schedule Period: Defines whether the crew shift type is daily or weekly. Crew Shift Business Object: The business object that will be used when creating crew shift of this type. Crew Shift Definitions A crew shift is a planned period of time in which a crew (one or more workers) is scheduled to perform work. For example, a crew shift might be defined as Crew A, consisting of Jack and his van, working on a specific date from 9 am 5 pm. Refer to the Creating a Daily Crew Shift section for more information. Crew Shift Template Business Object: W1-CrewShiftTemplate Defines the details to generate shifts for a crew. From Week Number: The relative week number within the shift template's rotation cycle that generated shifts are planned to start on. For example, if set to 1, generated shifts would start on the 1st week of each cycle. From Week Day: Weekday on which generated shifts are planned to start. From Time: Time of day at which generated shifts are planned to start. To Week Number: Relative week number within the shift weekly template's rotation cycle that generated shifts are planned to end on. For example, if set to 1 generated shifts would end on the 1st week of each cycle. To Week Day: Weekday on which generated shifts are planned to end. To Time: Time of day at which generated shifts are planned to end. Work Availability Duration: Establishes the total amount of time allotted for the shift. Crew Members fields Employee: The employee ID for the crew member. Role: Indicates whether the crew member is the supervisor or simply a crew member. Service Classes fields Service Classes: Defines the classification for the work that the crew performs. Service Class Usage: Backup/Principle. Indicates the crew's role with respect to the service class. Service Areas fields Service Area: Defines the boundaries of the crew's work area. Service Area Usage: Indicates the crew's restrictions with respect to the service area. Status (from the BO lifecycle) Valid statuses include: Active Inactive Daily Schedule Business Object: W1-DailySchedule Defines the details to generate daily shifts for a crew. Oracle Utilities Work and Asset Management User Guide 205

206 Planned Start/End Date Time: Indicates the start and end dates and times for the daily schedule. The times are defaulted from the crew shift type, as applicable. Work Availability Duration: Establishes the total amount of time allotted for the shift. Schedule Plan: Indicates the shift plan template that should be used to generate the schedule. Crew Members fields Employee: The members of the crew specific to this schedule. Members default from the Crew that is entered, but can be added or removed. Role: Indicates whether the crew member is the supervisor or simply a crew member. Service Classes fields Service Classes: Defines the classification for the work that the crew performs. Service Class Usage: Backup/Principle. Indicates the crew's role with respect to the service class. Service Areas fields Service Area: Defines the boundaries of the crew's work area. Service Area Usage: Indicates the crew's restrictions with respect to the service area. Status (from the BO lifecycle) Valid statuses include: Pending Planned Active Complete Canceled Schedule Plan Business Object: W1-SchedulePlan Defines the details to plan shifts for a crew. Status (from the BO lifecycle) Planned Start Date: Indicates the date for the start of the shift. Valid statuses include: Planned Complete Canceled Shift Plan Template Definitions Shift plan templates are used to automatically generate crew shifts based on a set of pre-defined shift criteria such as the shift type, the shift rotation, the defined calendar and so on. Please refer to the Creating a Shift Plan Template section for more information. Shift Plan Template Business Object: W1-ShiftPlanTemplate Defines a shift rotation for a specific crew. Oracle Utilities Work and Asset Management User Guide 206

207 Crew: The crew affected by the template. : A useful description of the template. Effective Period fields Shift Plan Control fields Effective Date/Expiration Date: The dates that the template is in effect for the crew. Number Of Weeks In Rotation: Specifies the number of weeks this template is effective for, starting from the effective date. Work Calendar: The work calendar that defines the holidays or other calendar changes that might affect the template. Schedule Plan Type: Defines the crew shift type which specifies whether the shift template is daily or weekly. Status (from the BO lifecycle) Valid statuses include: Pending Apply Applied Common Shift Plan Template Business Object: W1-CommonShiftPlanTemplate Defines a shift rotation which can be assigned for any crew. This type of shift plan template can be sent to an external system. Template Name: A unique name or code for the template. : A useful description of the template which will appear in drop-down lists. Initial Rotation Date: Defines the starting date for the rotation. This ensures that all generated shifts for crews subscribing to the template are at the same rotation position regardless of when the crew subscribed to the template. Rotation is calculated based on the common initial rotation date and not the subscription effective date. For example, if a common template has a 2 week rotation where on the first week the crew works on Monday but on the second week the crew works on Tuesday. If one crew subscribes to this template just prior to the first week and another subscribes just toward the end of the first week, then for the first crew the first generated shifts is a Monday whereas the second crew s first generated shift is a Tuesday. External ID: Reference identification number used when the template is interfaced with an external system. Shift Plan Control fields Number Of Weeks In Rotation: Specifies the number of weeks this template is effective for, starting from the effective date. Work Calendar: The work calendar that defines the holidays or other calendar changes that might affect the template. Schedule Plan Type: Defines the crew shift type which specifies whether the shift template is daily or weekly. Status (from the BO lifecycle) Valid statuses include: Pending Active Oracle Utilities Work and Asset Management User Guide 207

208 Subscription Shift Plan Template Business Object: W1-SubscriptionShiftPlanTemp Defines a shift rotation that crews can be subscribed to. Crew: The crew affected by the template. Common Shift Plan Template: The base common template for the subscription. Effective Date/Expiration Date: The dates that the subscription is in effect for the crew. Effective Period fields Status (from the BO lifecycle) Effective Date/Expiration Date: The dates that the subscription is in effect for the crew. Valid statuses include: Pending Active Active Apply Pending Cancel Canceled Document Object s This section provides descriptions of the attributes used for document related objects as they are delivered in the base application. Document Type Definitions Document types establish a basis for the types of documents that can be added within the system. This is referenced when creating a new Document record. Refer to the Defining a Document Type section for more information. Business Object: W1-DocumentType Document Type: A unique name or code for the document type. : A useful description of the document type which will appear in drop-down lists. Document Definitions The Documents portal is used to track, store and manage electronic documents for use throughout the system. Each document record contains information such as location, file type and a document description. Documents can be attached to entities such as assets, nodes, service history, and so on. Attached documents provide information to support records. Refer to the Working with Documents section for more information. Oracle Utilities Work and Asset Management User Guide 208

209 Document Attachment Business Object: W1-DocAttachment Attachments can be any file, such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Attachment files are added to individual records such as an asset, purchase order, work order, activity, service history, and so on. : A useful description of the attachment which will appear in drop-down lists. Document Type: The type of document used when creating this attachment, as defined in the Document Type portal. Category: Indicates the classification for the document. Document Number Attachment Type Status (from the BO lifecycle) An identification number given for the attachment, based on your business practices. This is not validated, but can be used as a search field. The type of attachment used when creating this attachment, such as an excel file, a word file, an audio file and so on. Valid statuses include: Created Active Inactive Standard Note Business Object: W1-StandardNote Standard notes can be added as a type of document within the system and can then be associated to records wherever a note might be needed to provide additional information. Notes can be modified within the Documents portal and any changes or updates are reflected wherever the note is associated to a record. : A useful description of the note which will appear in drop-down lists. Document Type: The type of document used when creating this note, as defined in the Document Type portal. Category: Indicates the classification for the document. Note: The contents of the note. This is free form text. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive URL Business Object: W1-DocUrl A URL can be added as a type of document within the system and can then be associated to records wherever it might be necessary to provide a link to additional information. The URL can be modified within the Documents portal and any changes or updates are reflected wherever the URL is associated to a record. Oracle Utilities Work and Asset Management User Guide 209

210 : A useful description of the url which will appear in drop-down lists. Document Type: The type of document used when creating this url, as defined in the Document Type portal. Category: Indicates the classification for the url. URL: The actual URL. Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Employee Object s This section provides descriptions of the attributes used for employee related objects as they are delivered in the base application. Employee Type Definitions Employee types define the kinds of employees that can be defined for your organization. For example, your organization might use employee types to define regular employees, skilled employees, and novice employees. Refer to the Defining an Employee Type section for more information. Business Object: W1-EmployeeType Name: A unique name or code for the employee type. : A useful description of the employee type which will appear in drop-down lists. Employee Business Object: The business object that will be used when creating employee types of this type. Employee Definitions Employee records are used to manage human resource level information for the workers within your organization with details such as name and personal information, work status, the main craft worked by the employee, their business unit, payroll information, hire date, default timesheet information and so on. The employee record can also tie the employee to a service area where they are allowed to work as well as track training completed by the employee. Refer to the Creating an Employee section for more information. Employee Information Business Object: W1-EmployeeInformation User: The system username for the employee. Principal Craft: The main craft that the employee is qualified to work. Oracle Utilities Work and Asset Management User Guide 210

211 Supervisor: The username of the employee's supervisor. Business Unit: The business unit that the employee belongs to. Generally costs incurred by the employee roll up to this business unit. Personal Information fields Payroll Information fields Employment Information fields Provides first name, last name and phone numbers. Provides information such as the employee's title and job code. Provides information such as the employee hire date, termination date (when applicable), and the employee number assigned to the employee from your internal HR system. Hire Date Termination Date HR Employee Number External ID: Unique identification for the employee for integration with external systems. Address Information fields Work Area fields Training Information fields Information fields Status (from the BO lifecycle) Provides the employee's personal address including type of house, state, county and postal code. Allows for a list of vaild service areas where the employee is authorized to work. Allows for a list of training courses completed by the employee. The latitude and longitude coordinates for the address (usually for GPS). Valid statuses include: Active Inactive Employee Unavailability Type Definitions Employee unavailability types define kinds of situations where employees may be unavailable such as general leave, jury duty, vacation, sick leave, and so on. Refer to the Entering Employee Unavailability section for more information. Leave Type Business Object: W1-LeaveType Defines a type of unavailability where employees can apply for general leave, such as vacation or sick time. Employee Unavailability Type: A unique name or code for the leave type. : A useful description of the leave type which will appear in drop-down lists. Employee Unavailability Business Object: The business object that will be used when creating leave of this type. Cost Center: The cost center that will be charged for costs related to this leave. Expense Code: The expense code that will be charged for costs related to this leave. Work Function Type Business Object: W1-FunctionType Defines a type of period of unavailability that may affect one or many employees, such as an off-site training session. Oracle Utilities Work and Asset Management User Guide 211

212 Employee Unavailability Type: A unique name or code for the function type. : A useful description of the function type which will appear in drop-down lists. Employee Unavailability Business Object: The business object that will be used when creating functions of this type. Cost Center: The cost center that will be charged for costs related to this function. Employee Unavailability Definitions Employee unavailability records establish periods of time where an employee has been given leave from his or her regular job duties. This might be due to circumstances such as vacation, sick leave, attending a training, jury duty, and so on. Logging employee unavailability allows the system to know when an employee is not available to perform work on the crews that he or she is associated with. Leave Business Object: W1-Leave Allows employees to apply for general leave such as vacation or sick time. : A useful description of the leave period. Applicant: The username of the person applying for leave. Duration Information fields Indicates the time period for the unavailability. Start Date/Time End Date/Time Status (from the BO lifecycle) Valid statuses include: Created Pending Approval Approved Rejected Function Business Object: W1-Function Defines a period of unavailability that may affect one or many employees, such as an off-site training session. Duration Information fields Indicates the time period for the unavailability. Start Date/Time End Date/Time Attendees fields Work Function Information fields Defines a list of the employee numbers for the people who will be unavailable during this period of unavailability. Indicates a description of the activity which the employees will be attending and provides the username of a valid contact for the activity. Oracle Utilities Work and Asset Management User Guide 212

213 Work Function Contact Address Information fields Information fields Status (from the BO lifecycle) Indicates the address and other location information where the activity will take place. The latitude and longitude coordinates where the activity will occur (usually for GPS). Valid statuses include: Active Inactive Other Direct Charge Object s This section provides descriptions of the attributes used for other direct charges related objects as they are delivered in the base application. Other Direct Charge Definitions Other direct charges are defined by your organization to be referenced as a charge type to charge work against. This might include miscellaneous charges for activities such as meals, miles, hotel stay, and so on. ODC Business Object: W1-ODC : A useful description of the charge. Employee: The employee number of the person incurring the charge. Status (from the BO lifecycle) Valid statuses include: Created Pending Approval Approved Rejected Posted Canceled Other Direct Charges Detail Definitions Other direct charges are defined by your organization to be referenced as a charge type to charge work against. This might include miscellaneous charges for activities such as meals, miles, hotel stay, and so on. ODC Equipment Business Object: W1-ODCEquipment Oracle Utilities Work and Asset Management User Guide 213

214 Defines details for other direct charges related to equipment. For example, this might be used to track costs for a rental truck. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the direct charge. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Equipment Charges Detail fields Charge Date: Indicates the date that the charge was incurred. Quantity Unit Price Total Cost Start/End Reading As applicable, allows you to enter a measurement reading for the equipment (such as an odometer). Comments Status (from the BO lifecycle) Valid statuses include: Created Posted Canceled Other Direct Charges Other Resource Business Object: W1-ODCOther Defines details for other direct charges related to. Accounting Information fields Cost Center/Expense Code: List of cost centers and expense codes which will incur costs for charges against the direct charge. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Other Charges Detail fields Charge Date: Indicates the date that the charge was incurred. Unit Price Total Cost Comments Status (from the BO lifecycle) Valid statuses include: Created Posted Canceled Oracle Utilities Work and Asset Management User Guide 214

215 Service Object s This section provides descriptions of the attributes used for service related objects as they are delivered in the base application. Service Area Definitions Service areas define a logical boundary of your organization's territory. Every crew shift is populated with a list of service areas that the crew shift is allowed to work. This is matched up with the service area indicated on the activity to help determine which crew shift can work the activity. Refer to the Defining a Service Area section for more information. Business Object: W1-ServiceArea Service Area: A unique name or code for the service area. : A useful description of the service area which will appear in drop-down lists. Service Class Definitions Service classes categorize activity types and indicate the type of work a shift is responsible for. Every crew shift is populated with a list of service classes that the crew shift is allowed to work. This is matched up with the service class indicated on the activity to help determine which crew shift can work the activity. Refer to the Defining a Service Class section for more information. Business Object: W1-ServiceClass Service Class: A unique name or code for the service class. : A useful description of the service class which will appear in drop-down lists. Renewal: It indicates whether or not related activities are for restoring or replacing an asset towards its original size, condition or capacity. This type of work tracks costs. Resource Unit of Measurement Definitions Resource units of measurement (UOM) establish the acceptable units used to quantify resources such as stock items, materials, equipment or other used by your organization. Refer to the Defining a Resource Unit of Measurement (UOM) section for more information. Business Object: W1-ResourceUOM Resource UOM: A unique name or code for the unit. : A useful description of the unit which will appear in drop-down lists. Oracle Utilities Work and Asset Management User Guide 215

216 Resource UOM Class: An additional classification for the unit such as material or non-material. Work Management Object s This section provides descriptions of the attributes used for work management related objects as they are delivered in the base application. Refer to the Understanding Work Management section for a conceptual overview of this functional area. Work Order Object s This section provides descriptions of the attributes used for work order related objects as they are delivered in the base application. Work Request Definitions Work Requests are used to request work or services to be performed and, when approved, can become work orders. Work Requests can be created manually, as a follow-up to an activity, or by an external system. Work requests are mainly used to implement an approval chain for the requested work. Work Request Business Object: W1-WorkRequest : A description of the work request. Detailed : More information about the request. Required By Date: The date by which the work request must be completed. Downtime Start: Indicates when the asset will be affected by downtown for the request. Contact Information fields Asset Information fields Information fields Status (from the BO lifecycle) Provides the name and phone numbers for the contact on the work request. Provides the asset ID and address information for the asset on the work request. The latitude and longitude coordinates where the activity will occur (usually for GPS). Valid statuses include: Created Pending Approval Rejected Approved Canceled Work Created Oracle Utilities Work and Asset Management User Guide 216

217 Work Order Definitions Work orders group similar activities and are used to manage activities to perform any kind of work such as inspection, install, replacement, upgrade, and so on. They are mainly used to facilitate approval processing for work projects. Refer to the Working with Work Orders and Activities section for more information. Basic Work Order Organize simple activities. These work orders cannot be used as templates for service history or recurring work. Business Object: W1-BasicWorkOrder Work Type: Indicates the class of work to be completed such as regular, preventive maintenance or emergency. Emergency: Yes/No. Indicates whether or not the work is in response to an emergency. Work Class: A classification of the work. Work Category: A categorization of the work. Project: The record identifier for the related project, as applicable. Accounting Information fields Status (from the BO lifecycle) Cost Center: List of cost centers which will incur costs for charges against the work order. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Valid statuses include: Open Closed Work Order (general) Business Object: W1-WorkOrder Organize simple activities and create templates. : A useful description of the work. Detailed Required By Date: Indicates when the work needs to be completed. Requestor: The user ID of the person requesting the work. Work Request: The record identification number of the related work request, as applicable. Parent Work Order: The record identification number of the related work order, as applicable. Work Order Data fields Work Type: Indicates the class of work to be completed such as regular, preventive maintenance or emergency. EmergencyYes/No. Indicates whether or not the work is in response to an emergency. Planner: Typically the person responsible for planning work and materials for assets. Oracle Utilities Work and Asset Management User Guide 217

218 Crew: The crew that should complete the work, as applicable. Work Class: A classification of the work. Work Category: A categorization of the work. Work Priority: Defines the importance of the work in terms of the potential impact of not addressing issues. For example, a work for assets at a hospital might have a high criticality rating since losing power there might result in deaths of patients, while work for assets at a city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Work priority is represented on a scale of low (little to no impact) to high (significant impact). Project: The record identifier for the related project, as applicable. Rough Estimate: Free form text field to indicate an estimate of the work cost. Auto Close: When this is set to yes work orders generated from the template automatically close if they are in Completed status for the amount of time specified by your business processes. This is set in the master configuration for work orders. Accounting Information fields Status (from the BO lifecycle) See W1-BasicWorkOrder. Valid statuses include: Planning Pending Approval Approved Active Reopened Rejected Completed Closed Canceled Asset Criteria Activity Generator Business Object: W1-AssetCriteriaActGenerator Create activities for tasks such as creating service history for assets based upon specified asset criteria. Work Order Data fields Accounting Information fields Asset Information fields See W1-BasicWorkOrder. See W1-BasicWorkOrder. Indicates the asset type, disposition and condition for assets generated by this work order. Asset Type: Indicates the type of asset to create as a result of the work order. Asset Disposition: Indicates the disposition status that the asset is to be created in. Asset Condition Identifier fields Status Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on search screens to add additional criteria. Open Oracle Utilities Work and Asset Management User Guide 218

219 (from the BO lifecycle) Generate Activities Error Template Canceled Closed Asset List Generator Create activities for tasks such as creating or updating new assets in the system. Business Object: W1-AssetListActGenerator Work Order Data fields Accounting Information fields Activity Information s See W1-BasicWorkOrder. See W1-BasicWorkOrder. Defines the information for the activities created by the work order. When creating a new work order, the Activity Type Activity Type: Determines the types of activities that can be created from the work order. This also defines the default lead days and work window days for the activity if they are not specified. This information is used for scheduling when the activity information is sent to external systems. Activity Disposition: Indicates the status that the activity should be created in. Activation Lead Days: Used to default the activity's activation date. The lead days will be added to the activity creation date to establish the activity's activation date. For example, if this value is set to 3 and the creation date is 4/21/2015, the activation date will be set as 4/24/2015. Work Lead Days: Used to default the activity's work window start date. This is the number of days after the activation date to start the work window. For example, if this value is set to 5 and the activation date is 4/24/2015 then the work window starts on 4/29/2015. Work Window Days: Used to default the activity's work window end date. This is the number of days after the work window start date to end the work window. For example, if this value is set to 10 and the activation date is 4/24/2015 then the work window ends on 5/9/2015. Maximum Activity Count Asset List Information fields Status Defines the list of assets that will be created by the activities on the work order. When creating a new work order, this list can be uploaded via a CSV file. Valid statuses include: Open Generate Activities Error Template Canceled Closed Component List Generator Create activities for tasks such as creating or updating new component in the system. Oracle Utilities Work and Asset Management User Guide 219

220 Business Object: W1-CompnAssetListActGenerator Work Order Data fields Accounting Information fields Activity Information s Component Asset List Information fields Status See W1-BasicWorkOrder. See W1-BasicWorkOrder. See W1-AssetListActGenerator. Defines the list of components that will be created by the activities on the work order. When creating a new work order, this list can be uploaded via a CSV file. Valid statuses include: Open Generate Activities Error Template Canceled Closed Component Criteria Activity Generator Create activities for tasks such as creating service history for components based upon specified component criteria. Business Object: W1-CompnCriteriaActGenerator Work Order Data fields Accounting Information fields Attached to Asset Information fields Component Information fields See W1-BasicWorkOrder. See W1-BasicWorkOrder. Serves to select the status of the asset where components are installed that should be included on the activities created from the work order. Serves to select the component type, disposition, condition, identifiers, and or characteristics for components that should be included on the activities created from the work order. Asset Type: Indicates the type of asset to create as a result of the work order. Asset Disposition: Indicates the disposition status that the asset is to be created in Asset Condition Identifier fields Status Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on search screens to add additional criteria. Valid statuses include: Open Generate Activities Error Template Canceled Closed Oracle Utilities Work and Asset Management User Guide 220

221 Location Criteria Activity Generator Create activities to move assets between locations. Business Object: W1-NodeCriteriaActGenerator Work Order Data fields Accounting Information fields Asset Installed fields Location Information fields Identifier fields Status See W1-BasicWorkOrder. See W1-BasicWorkOrder. Serves to select the status of the asset where components are installed that should be included on the activities created from the work order. Defines the location type, criticality, class, identifiers and characteristics for the location included on the activities created from the work order. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on search screens to add additional criteria. Valid statuses include: Open Generate Activities Error Template Canceled Closed Maintenance Schedule Asset Location Business Object: W1-MaintSchedAstLocCriteria This type of work order is used to plan for activities and resources which are specific to an asset location (where the asset is installed). This type of template cannot be used in the maintenance schedules which are configured for asset specifications. This type of template can be used in situations where there is an activity dependency. For example one activity must be performed at one specific location before the activity can be performed at a second location. This might apply, for instance, if a system needs to be shut down at a valve so that downstream components can be rebuilt or cleaned. Work Order Data fields Accounting Information fields Asset Installed fields Location Information fields Status See W1-BasicWorkOrder. See W1-BasicWorkOrder. See W1-NodeCriteriaActGenerator. Defines the location type, criticality, class, identifiers, service area and characteristics for the location included on the activities created from the work order. Valid statuses include: Open Generate Activities Error Template Oracle Utilities Work and Asset Management User Guide 221

222 Canceled Closed Configuration Criteria / Device Upgrade Business Objects All of these business objects use the same base set of fields: Work Order Data fields Accounting Information fields Configuration Detail fields Status (from the BO lifecycle) See W1-BasicWorkOrder. See W1-BasicWorkOrder. Provides details about the asset and component with characteristics, specifications and identifiers indicated. Open Generate Activities Error Template Canceled Closed Configuration Criteria A Business Object: W1-SingleAssetCfgWO Single Asset. Generate activity to modify the configuration for the asset in a single asset configuration. Configuration Criteria - A to A Business Object: W1-AssetToAssetCfgWO Asset to Asset. Generate activity to modify the configuration for an asset in an asset-communicate-to-asset configuration. Configuration Criteria - AC Business Object: W1-AssetCompCfgWO Asset/Component. Generate activity to modify the configuration for an asset with an attached component configuration. Configuration Criteria - AC to A Business Object: W1-AssetCompToAssetCfgWO Asset/Component to Asset. Generate activity to modify the configuration for an asset or component in an asset/componentcommunicate-to-asset configuration. Configuration Criteria - AC to AC Business Object: W1-AssetCompToAssetCompCfgWO Asset/Component to Asset/Component. Generate activity to modify the configuration for an asset or component in an asset/ component-communicate-to-asset/component configuration. Configuration Criteria A to AC Business Object: W1-AssetToAssetCompCfgWO Oracle Utilities Work and Asset Management User Guide 222

223 Asset to Asset/Component. Generate activity to modify the configuration for an asset or component in an assetcommunicate-to-asset/component configuration. Configuration Criteria Device Upgrade - A to AC Business Object: W1-AACCfgDeviceUpgrade Asset to Asset/Component. Create activities to replace an asset or component in an asset-communicate-to-asset/component configuration. Configuration Criteria Device Upgrade - A to A Business Object: W1-AACfgDeviceUpgrade Asset to Asset. Create activities to replace an asset in an asset-communicate-to-asset configuration. Configuration Criteria Device Upgrade - AC to AC Business Object: W1-ACACCfgDeviceUpgrade Asset/Component to Asset/Component. Create activities to replace an asset or component in an asset/componentcommunicate-to-asset/component configuration. Configuration Criteria Device Upgrade - AC to A Business Object: W1-ACACfgDeviceUpgrade Asset/Component to Asset. Create activities to replace an asset or component in an asset/component-communicate-to-asset configuration. Configuration Criteria Device Upgrade - AC Business Object: W1-ACCfgDeviceUpgrade Asset/Component. Create activities to replace the asset or component in an asset with an attached component configuration. Configuration Criteria Device Upgrade - A Business Object: W1-ACfgDeviceUpgrade Single Asset. Create activities to replace the asset in a single asset configuration. Configuration Criteria Firmware Upgrade A Business Object: W2-ACfgFirmwareUpgrade Single Asset. Create activities to upgrade the firmware of the asset in an asset only configuration. Configuration Criteria Firmware Upgrade - A to A Business Object: W2-AACfgFirmwareUpgrade Asset to Asset. Create activities to upgrade the firmware of an asset in an asset-communicate-to-asset configuration. Configuration Criteria Firmware Upgrade - A To AC Business Object: W2-AACCfgFirmwareUpgrade Asset to Asset/Component. Create activities to upgrade the firmware of an asset or component in an asset-communicate-toasset/component configuration. Configuration Criteria Firmware Upgrade - AC to AC Business Object: W2-ACACCfgFirmwareUpgrade Oracle Utilities Work and Asset Management User Guide 223

224 Asset/Component to Asset/Component. Create activities to upgrade the firmware of an asset or component in an asset/ component-communicate-to-asset/component configuration. Configuration Criteria Firmware Upgrade - AC To A Business Object: W2-ACACfgFirmwareUpgrade Asset/Component to Asset. Create activities to upgrade the firmware of an asset or component in an asset/componentcommunicate-to-asset configuration. Configuration Criteria Firmware Upgrade AC Business Object: W2-ACCfgFirmwareUpgrade Asset/Component. Create activities to upgrade the firmware of the asset or component in an asset/component configuration. Template Work Order Definitions Template work orders, or benchmark work orders, are work orders that can be re-used to help your organization avoid repeating planning the same work for similar jobs. They can be used for basic work planning, but are also typically used with preventive maintenance. Refer to the Creating a Template Work Order section for more information. General Template Work Order Business Object: W1-GeneralTemplateWorkOrder used to plan for activities and resources which can be common to assets regardless of the asset disposotion. This type of template can be used in the maintenance schedule configured for asset specifications as well as on the override maintenance schedule configured for an asset. Detailed Planner: Typically the person responsible for planning work and materials for assets. Work Class: A classification of the work. Work Category: A categorization of the work. Work Priority: Defines the importance of the work in terms of the potential impact of not addressing issues. For example, a work for assets at a hospital might have a high criticality rating since losing power there might result in deaths of patients, while work for assets at a city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Work priority is represented on a scale of low (little to no impact) to high (significant impact). Work Order Approval Profile: Indicates the approval profile authorized to approve the work orders created from the template. Allow Auto Close: When this is set to yes work orders generated from the template automatically close if they are in Completed status for the amount of time specified by your business processes. This is set in the master configuration for work orders. Required By Lead Days: This value adds on the given number of days from the creation date for the WO Required by Date. For example, if this value is set to 7 and the creation date is 1/1/2015, the Required by Date will be calculated as 1/8/2015. Work Order Business Object: Indicates the type of work order that will be created from the template. Oracle Utilities Work and Asset Management User Guide 224

225 Status (from the BO lifecycle) Valid statuses include: Created Active Inactive Asset Location Specific Template Work Order Business Object: W1-AssetLocSpecTemplWorkOrder used to plan for activities and resources which are specific to an asset location (where the asset is installed). This type of template cannot be used in the maintenance schedules which are configured for asset specifications. This type of template can be used in situations where there is an activity dependency. For example one activity must be performed at one specific location before the activity can be performed at a second location. This might apply, for instance, if a system needs to be shut down at a valve so that downstream components can be rebuilt or cleaned. This type of template uses the same fields as W1-GeneralTemplateWorkOrder. Activity Object s This section provides descriptions of the attributes used for activity related objects as they are delivered in the base application. Activity Type Definitions Activity types define the main attributes for activities of a certain type. Refer to the Defining an Activity Type section for more information. Basic Activity Type Business Object: W1-BasicActivityType Defines a type of activity with no requirements or planning details. Does not include service history. Activity Type: A unique name or code for the activity type. :A useful description of the activity type which will appear in drop-down lists. Track Cost (Yes/No): Indicates whether or not the system should track costs for activities of this type. Service Class: Indicates the applicable service class for activities of this type. Activity Business Object: The business object that will be used when creating activities of this type. Category:Provides an additional classification for the activity type such as measurement, replication, maintenance, update, and so on. Attachments fields Identifier fields Exception Handling fields Indicates a type of attachment which will apply to all activities of this type and the actual attachment ID. Attachments provide additional information to support the record. This can be any file such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. Determine how to handle errors or other exceptions. Oracle Utilities Work and Asset Management User Guide 225

226 To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Maximum Retries and Retry Frequency: The maximum number of times the system tries to complete the transaction before failing and how frequently it should submit the retry attempts. Discard Reason: If the transaction fails, the default discard reason that is set here displays on the record for auditing. Completion Event Types fields To ensure that the correct completion events are processed for activities, valid completion event types must be associated to each activity type. Completion Event Type: Indicates the type of completion event used to process and finalize activities of this type. Event Relationship Type: Indicates whether the completion is optional or required. Execution Sequence: Indicates the order in which completion events must be run. Outbound Activity Type Business Object: W1-OutboundActivityType Defines a type of activity with the details needed to send the activity to an external system. Activity Type: A unique name or code for the activity type. : A useful description of the activity type which will appear in drop-down lists. Track Cost (Yes/No): Indicates whether or not the system should track costs for activities of this type. Activity Business Object: The business object that will be used when creating activities of this type. Category: Provides an additional classification for the activity type such as measurement, replication, maintenance, update, and so on. Service Class: Indicates the applicable service class for activities of this type. Service History Type: Indicates the service history type to use with activities of this type. When applicable, this defines the type of inspection or maintenance that will be performed. Activity Schedule Information fields Provides default scheduling information. The lead days and work window days are used primarily for scheduling integration with an external system. Activation Lead Days: Used to default the activity's activation date. The lead days will be added to the activity creation date to establish the activity's activation date. For example, if this value is set to 3 and the creation date is 4/21/2015, the activation date will be set as 4/24/2015. Work Lead Days: Used to default the activity's work window start date. This is the number of days after the activation date to start the work window. For example, if this value is set to 5 and the activation date is 4/24/2015 then the work window starts on 4/29/2015. Work Window Days:Used to default the activity's work window end date. This is the number of days after the work window start date to end the work window. For example, if this value is set to 10 and the activation date is 4/24/2015 then the work window ends on 5/9/2015. Activity Disposition: The default disposition status that the activity is placed in when it created; On Hold or Released. Outbound Activity Information fields Defines the information that is needed to send the transaction to an external system. Oracle Utilities Work and Asset Management User Guide 226

227 Attachments fields Identifiers fields Exception Handling fields Indicates a type of attachment which will apply to all activities of this type and the actual attachment ID. Attachments provide additional information to support the record. This can be any file such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. Determine how to handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Maximum Retries and Retry Frequency: The maximum number of times the system tries to complete the transaction before failing and how frequently it should submit the retry attempts. Discard Reason: If the transaction fails, the default discard reason that is set here displays on the record for auditing. Completion Event Types fields To ensure that the correct completion events are processed for activities, valid completion event types must be associated to each activity type. Completion Event TypeIndicates the type of completion event used to process and finalize activities of this type. Event Relationship TypeIndicates whether the completion is optional or required. Execution Sequence Indicates the order in which completion events must be run. Operational Device Scheduled Activity Type Business Object: W1-ScheduledActivityType Defines an activity with planning details and scheduling details specifically for Oracle Utilities Operational Device Management. Activity Type: A unique name or code for the activity type. : A useful description of the activity type which will appear in drop-down lists. Activity Business Object: The business object that will be used when creating activities of this type. Track Cost (Yes/No): Indicates whether or not the system should track costs for activities of this type. Category: Provides an additional classification for the activity type such as measurement, replication, maintenance, update, and so on. Service Class: Indicates the applicable service class for activities of this type. Service History Type: Indicates the service history type to use with activities of this type. When applicable, this defines the type of inspection or maintenance that will be performed. Activity Schedule Information fields Provides default scheduling information. The lead days and work window days are used primarily for scheduling integration with an external system. Activation Lead Days: Used to default the activity's activation date. The lead days will be added to the activity creation date to establish the activity's activation date. For example, if this value is set to 3 and the creation date is 4/21/2015, the activation date will be set as 4/24/2015. Work Lead Days: Used to default the activity's work window start date. This is the number of days after the activation date to start the work window. For example, if this value is set to 5 and the activation date is 4/24/2015 then the work window starts on 4/29/2015. Oracle Utilities Work and Asset Management User Guide 227

228 Work Window Days: Used to default the activity's work window end date. This is the number of days after the work window start date to end the work window. For example, if this value is set to 10 and the activation date is 4/24/2015 then the work window ends on 5/9/2015. Activity Disposition: The default disposition status that the activity is placed in when it created; On Hold or Released. Attachments fields Identifier fields Exception Handling fields Indicates a type of attachment which will apply to all activities of this type and the actual attachment ID. Attachments provide additional information to support the record. This can be any file such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. Determine how to handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Maximum Retries and Retry Frequency: The maximum number of times the system tries to complete the transaction before failing and how frequently it should submit the retry attempts. Discard Reason: If the transaction fails, the default discard reason that is set here displays on the record for auditing. Completion Event Types fields To ensure that the correct completion events are processed for activities, valid completion event types must be associated to each activity type. Completion Event TypeIndicates the type of completion event used to process and finalize activities of this type. Event Relationship TypeIndicates whether the completion is optional or required. Execution Sequence Indicates the order in which completion events must be run. Planned Activity Type Business Object: W1-ScheduledActivityTypeWAM Defines an activity with planning and scheduling details specifically for Oracle Utilities Work and Asset Management. Activity Type: A unique name or code for the activity type. : A useful description of the activity type which will appear in drop-down lists. Activity Business Object: The business object that will be used when creating activities of this type. Category: Provides an additional classification for the activity type such as measurement, replication, maintenance, update, and so on. Service Class: Indicates the applicable service class for activities of this type. Service History Type: Indicates the service history type to use with activities of this type. When applicable, this defines the type of inspection or maintenance that will be performed. Default Labor Requirements fields Activity Schedule Information fields Craft/Quantity/Hours: Indicates the craft requirements for activities of this type. This is the expected skill needed to complete the work as well as an estimated quantity and number of hours. Provides default scheduling information. The lead days and work window days are used primarily for scheduling integration with an external system. Activation Lead Days: Used to default the activity's activation date. The lead days will be added to the activity creation date to establish the activity's activation date. For example, if this value is set to 3 and the creation date is 4/21/2015, the activation date will be set as 4/24/2015. Oracle Utilities Work and Asset Management User Guide 228

229 Work Lead Days: Used to default the activity's work window start date. This is the number of days after the activation date to start the work window. For example, if this value is set to 5 and the activation date is 4/24/2015 then the work window starts on 4/29/2015. Work Window Days: Used to default the activity's work window end date. This is the number of days after the work window start date to end the work window. For example, if this value is set to 10 and the activation date is 4/24/2015 then the work window ends on 5/9/2015. Attachments fields Identifier fields Exception Handling fields Indicates a type of attachment which will apply to all activities of this type and the actual attachment ID. Attachments provide additional information to support the record. This can be any file such as a photo, a document with instructions or specifications, a spreadsheet, or any other supporting documentation. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. Determine how to handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Maximum Retries and Retry Frequency: The maximum number of times the system tries to complete the transaction before failing and how frequently it should submit the retry attempts. Discard Reason: If the transaction fails, the default discard reason that is set here displays on the record for auditing. Completion Event Types fields To ensure that the correct completion events are processed for activities, valid completion event types must be associated to each activity type.to ensure that the correct completion events are processed for activities, valid completion event types must be associated to each activity type. Completion Event TypeIndicates the type of completion event used to process and finalize activities of this type. Event Relationship TypeIndicates whether the completion is optional or required. Execution Sequence Indicates the order in which completion events must be run. Activity Definitions An activity is a task which needs to be completed. Activities manage asset changes, work, inspections maintenance and other actions that are performed on assets or components. Refer to the Working with Work Orders and Activities section for more information. Local/Scheduled Activity (No Resource Planning) Business Object: W1-LocalActivityCore Local or scheduled activities are similar to ad hoc activities in that they can be used for immediate tasks and are not shared with any external system. They have built in fields to capture scheduling information if needed. Emergency: Indicates whether or not this is an emergency activity. Parent Activity: Where applicable, parent/child activity relationships establish a hierarchy of tasks. This is mainly used for reporting. This can be used, for example, if you are creating a follow-up activity to an existing activity. This field is informational only with no associated processing or validation. However, the activity detail section on the related asset will show all of the parent and child activities that reference the asset. Location: The physical location where the related asset is stored, installed or otherwise dispositioned. Defaults to where the asset is currently stored or installed. Oracle Utilities Work and Asset Management User Guide 229

230 Asset: The record number for the asset or component that will be worked on. Project: The record number for the related project. Work Order: The record number for the related work order that references the activity. Activity Number: Indicates which activity on the work order applies. Service Class: Indicates the applicable classification of service for the activity. Comments: Free form text for additional information and details. Schedule Details fields Details regarding the scheduling of the activity, usually in an external system. The work window The Activity Disposition field. Activation Date/Time: Used to default the activation date for the activity. The lead days are added to the activity creation date to establish this activation date. Work Window Start Date/Time: The beginning of the time frame within which the activity can be scheduled and completed. This signifies the number of days after the activation date to start the work window. Work Window End Date/Time: The end of the time frame within which the activity can be scheduled and completed. This signifies the number of days after the work window start date to end the work window. Activity Disposition: Indicates the default disposition status that the activity is placed in when it created; On Hold or Released. When activities are created in On Hold status, they need to be released before work can start or completion events can be processed. Accounting Information fields Status (from the BO lifecycle) Cost Center: List of cost centers which will incur costs for charges against the activity. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. The current state of the activity. Valid statuses include: Pending Validated Validation Error Work in Progress Execute Completion Events Completion Error Completed Discarded Local Activity Core WAM Business Object: W1-LocalActivityCoreWAM Local or scheduled activities are similar to ad hoc activities in that they can be used for immediate tasks and are not shared with any external system. This type of activity allows for resource planning in Oracle Utilities Work and Asset Management. Location: The physical location where the related asset is stored, installed or otherwise dispositioned. Defaults to where the asset is currently stored or installed. Asset Work Order Oracle Utilities Work and Asset Management User Guide 230

231 Activity Number: Indicates which activity on the work order applies. Service Class: Indicates the applicable classification of service for the activity. fields : A useful description of the activity. Work Priority: Defines the importance of the work in terms of the potential impact of not addressing issues. For example, a work for assets at a hospital might have a high criticality rating since losing power there might result in deaths of patients, while work for assets at a city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Work priority is represented on a scale of low (little to no impact) to high (significant impact). Detailed : More information about the activity. Emergency Originating Activity Template Activity Requestor Service Class Comments: Free form text for additional information and details. Schedule Details fields Details regarding the scheduling of the activity, usually in an external system. Crew Activation Date/Time: Used to default the activation date for the activity. The lead days are added to the activity creation date to establish this activation date. Work Window Start Date/Time: The beginning of the time frame within which the activity can be scheduled and completed. This signifies the number of days after the activation date to start the work window. Work Window End Date/Time: The end of the time frame within which the activity can be scheduled and completed. This signifies the number of days after the work window start date to end the work window. Activity Disposition: The default disposition status that the activity is placed in when it created; On Hold or Released. When activities are created in On Hold status, they need to be released before work can start or completion events can be processed. Activity Data fields Phase Project Work Request Work Priority Deliver to Location Outage Type Backlog Group Accounting Information fields Asset Cost Distribution fields Activity Dependency fields See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Predecessor Activity Timing Option (After finish/after Start) Oracle Utilities Work and Asset Management User Guide 231

232 Resource Option (Any/Separate/Separate from all) Minimum Offset Maximum Offset Status (from the BO lifecycle) Planning Pending Approval Approved Active In Progress Finished Execute Completion Events Completion Error Completed Canceled Ad Hoc Activity Business Object: W1-AdHocActivityCore Ad hoc activities are used to manage tasks that are not related to any external system and are not scheduled. They would typically be used when some action needs to be performed on the spot yet there should be a record kept that the action was performed. In particular these can be used for asset replication to manage the receipt and/or creation of multiple assets at one time. Accounting Information fields Asset Cost Distribution fields Status (from the BO lifecycle) See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Valid statuses include: Work in Progress Execute Completion Events Completion Error Completed Discarded Outbound Activity Business Object: W1-OutboundActivityCore Outbound activities are used to send activities to an external system such as Oracle Utilities Mobile Workforce Management. These activities use the same fields as Local activities with additional statuses to manage the sending and receipt of the activities to and from the external system. Schedule details indicated on these activities is also sent and received from the external system. Oracle Utilities Work and Asset Management User Guide 232

233 Status (from the BO lifecycle) The current state of the activity. Valid statuses include: Pending Validated Validation Error Sent Resend Send Error Execute Completion Events Completion Error Executed Completed Discarded General Asset Replication Activity Business Object: W1-AssetReplicationActivity As devices and other assets are received in large quantities, the replication portal allows for the receipt, inspection, storage and other processing of these assets in batches. This processing creates new asset IDs based upon general information that is entered related to each batch. Assets can then be modified and their disposition updated using Mass Asset Disposition Update. Activity Type The type of activity. Activity Type Work Order: The record number for the originating work order. New Asset Controls fields New Asset fields Status (from the BO lifecycle) The template asset will be used as the basis for replication. If the template asset is in an initial state then its location may be used, otherwise specify an alternate initial location. Indicate whether or not service history, which belongs to the template asset, should be replicated. Summary of the assets that were created with the related record numbers. The current state of the activity. Valid statuses include: Work in Progress Execute Completion Events Completion Error Completed Discarded Maintenance Schedule Update Business Object: W1-MaintenanceScheduleUpdate Describes an activity used to update the maintenance schedule for an asset. Oracle Utilities Work and Asset Management User Guide 233

234 Maintenance Schedule Status (from the BO lifecycle) See W1-ReplaceAssetLocal. The record number for the maintenance schedule. The current state of the activity. Valid statuses include: Work in Progress Execute Completion Events Completion Error Completed Discarded Measurement Quick Entry Activity Business Object: W1-MsrmtQuickEntryActivity Describes an activity used to record new measurements for an asset. New Measurements fields Work Order: The record number for the work order to reference on the activity. Sequence Measurement Type Asset Badge Number Reading Date and Time Measurement UOM Current Value Measurement ID Status (from the BO lifecycle) The current state of the activity. Valid statuses include: Work in Progress Execute Completion Events Completion Error Completed Discarded Replace Asset Local Business Object: W1-ReplaceAssetLocal Defines an activity used to replace an asset or device. Schedule Details fields New Device Information fields See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Indicates the specification used to create the new asset. Oracle Utilities Work and Asset Management User Guide 234

235 Accounting Information fields Asset Cost Distribution fields Status (from the BO lifecycle) See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Valid statuses include: Pending Validated Validation Error Work in Progress Execute Completion Events Completion Error Completed Discarded Replace Asset Outbound Business Object: W1-ReplaceAssetOutbound Defines an activity used to replace an asset or device. This is sent to an external system. Schedule Details fields Accounting Information fields Asset Cost Distribution fields New Device Information fields Status (from the BO lifecycle) See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Indicates the specification used to create the new asset. Valid statuses include: Pending Validated Validation Error Sent Resend Send Error Execute Completion Events Completion Error Executed Completed Discarded Oracle Utilities Work and Asset Management User Guide 235

236 Firmware Upgrade Command Local Business Object: W2-FirmwareCommandLocal Defines an activity used to upgrade the firmware on a device. Schedule Details fields Accounting Information fields Asset Cost Distribution fields Firmware Information Status (from the BO lifecycle) See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Indicates the target firmware version for in the upgrade. The current state of the activity. Valid statuses include: Pending Validated Validation Error Work in Progress Execute Completion Events Completion Error Completed Discarded Firmware Upgrade Command Outbound Business Object: W2-FirmwareCommandOutbound Defines an activity which is sent to an external system. These activities are used to upgrade the firmware on a device. Schedule Details fields Accounting Information fields Asset Cost Distribution fields Firmware Information Status (from the BO lifecycle) See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. See W1-ReplaceAssetLocal. Indicates the target firmware version for in the upgrade. The current state of the activity. Valid statuses include: Pending Validated Validation Error Sent Resend Oracle Utilities Work and Asset Management User Guide 236

237 Send Error Execute Completion Events Completion Error Executed Completed Discarded Template Activity Definitions Template activities are activities that can be re-used to help your organization avoid repeating planning the same work for similar jobs. They can be used for basic work planning, but are also typically used with preventive maintenance. Template activities are part of a template work order and cannot be re-used by multiple template work orders. General Template Activity Business Object: W1-GeneralTemplateActivity : A useful description of the template activity which will appear in drop-down lists. Detailed : More information about the template activity. Template Work Order: The template work order related to the activity. Service Class: The categorization of the service related to the activity. Activity Type: The type of activity created for the template. Required by Lead Days Activation Lead Days: Used to default the activity's activation date. The lead days will be added to the activity creation date to establish the activity's activation date. For example, if this value is set to 3 and the creation date is 4/21/2015, the activation date will be set as 4/24/2015. Accounting Information fields Template Activity Dependency fields Cost Center: List of cost centers which will incur costs for charges against the activity. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Predecessor Template Activity Timing Option Resource Option Minimum/Maximum Offset Asset Location Specific Template Activity Business Object: W1-AssetLocSpecTemplateAct : A useful description of the template activity which will appear in drop-down lists. Detailed : More information about the template activity. Oracle Utilities Work and Asset Management User Guide 237

238 Template Work Order: The template work order related to the activity. Activity Type: The type of activity created for the template. Service Class: The categorization of the service related to the activity. Required by Lead Days Scheduling Lead Days Crew: The crew that should complete the work, as applicable. Asset Location: The physical location where the related asset is stored, installed or otherwise dispositioned. Defaults to where the asset is currently stored or installed. Accounting Information fields Cost Distribution fields Cost Center: List of cost centers which will incur costs for charges against the activity. Percentage: Indicates the percent to allocate to each cost center when more than one are indicated. Sequence: The order in which the costs are processed. Asset Location: The physical asset locations which will incur costs for charges against the activity. Percentage Indicates the percent to allocate to each location when more than one are indicated. Template Activity Dependency fields Predecessor Template Activity Timing Option Resource Option Minimum/Maximum Offset Template Activity Resource Definitions Template activities are activities that can be re-used to help your organization avoid repeating planning the same work for similar jobs. They can be used for basic work planning, but are also typically used with preventive maintenance. Template activities are part of a template work order and cannot be re-used by multiple template work orders. Template Activity Equipment Requirements Business Object: W1-TemplateActEquipmentReq Defines an equipment requirement on a template activity. Indicates the record number for the equipment item, the quantity, units, price, vendor and accounting information. Labor for Template Activity Business Object: W1-TemplateActivityLaborReq Defines a labor requirement on a template activity. Indicates the record number for the craft, the number of people, hours per person, hourly cost and accounting information. Oracle Utilities Work and Asset Management User Guide 238

239 Material for Template Activity Business Object: W1-TemplateActivityMaterialReq Defines a material requirement on a template activity. Indicates the record number for the stock item, the quantity, units, price and accounting information. Required by Lead Days Other Resource for Template Activity Business Object: W1-TemplateActivityOtherReq Defines a template activity with other requirements. Indicates the record number for the other item, the quantity, units, price and accounting information. Completion Event Type Definitions Completion event types are used to define completion events. Refer to the Defining Completion Event Types section for more information. General Completion Event Type Business Object: W1-GeneralCompletionEventType Defines details for a general record completion. Indicates the unique name or code for the completion event type, description, business object and default event date/time. Completion Event Business Object: The business object that will be used when creating completion events of this type. Default Event Date Time Valid Activity Types fields Identifier fields Inbound Communication fields Defines a list of valid activity types that can be used with this completion event type. Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity. They are used on the search screen to add additional search criteria. The Inbound Communication information is used to create a completion event for this completion event type using information defined within the inbound communication business object, or within its raw message. Data Mover SS defines an override service script responsible for creating a completion event. Note that if a data mover service script has been defined, none of the following data mover statements will be used. Required Value Source XPath and Value defines elements within the inbound communication business object that must be present for a completion event of this completion event type to be created. The value is optional. If a value is not specified, then any value for the element will be valid. Completion Event Data Mover Source and Target XPath defines elements within the inbound communication business object that should be transferred to the completion event business object. Oracle Utilities Work and Asset Management User Guide 239

240 Maintenance Tip: The correct XPath values can be easily obtained using the View Schema link for the appropriate business object or data area. After clicking the link, click on any element within the displayed XML and the XPath will be available for copying at the top of the dialog. To support this strategy for the raw message XML within the inbound communication, it will be necessary to create a data area that represents the schema of the inbound communication's raw message. Note that this data area must be bounded within a group named 'rawmessage'. The inbound communication has two pieces: elements defined within the business object schema proper, and elements that only live within the raw message element of the inbound communication. References to either can be used as the source path for any of the references above. You can reference any element within the inbound communication business object directly, but all references to elements within the communication's raw message must be interpreted using the data area. Attachments fields Indicates the attachments that are applicable for the completion event. Attachment List Sequence: Defines the order in which attachments are listed. Attachment List Attachment BO and Attachment List Source XPath Attachment BO: Defines the business object of the attachment to create from the inbound communication. One or the other must be specified, but not both. Required Value Source XPath and Value: Defins elements within the inbound communication that must be present for an attachment to be created. The value is optional. If a value is not specified, then any value for the element will be considered legitimate. Attachment Data Mover Source and Target XPath: Define elements within the inbound communication that should be transferred to the attachment business object. Activity Completion Event Type Business Object: W1-ActivityCompletionEventType Defines details for the completion of an activity. Valid Activity Types fields Identifier fields Completion Event Information fields UI Payload Create Data Mover fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Indicates the activity type. The UI Payload Create Data Mover statements are executed when creating a completion event online. These statements are used to populate elements within the payload from the completion event business object. For example, if you wish to populate a service history assetid from the completion event's assetid, you might set up the information as follows: Completion Event Source XPath: relationshipinformation/assetid Payload Target Xpath: assetid Maintenance tip: The correct XPath values can be most easily obtained using the View Schema link for the appropriate business object. For example: Open the View Schema dialog for the W1-CreServiceHistoryPayCmpEvt business object, then click on the assetid, and finally copy the XPath value from the top of the view dialog, which is: relationshipinformation/assetid. Inbound Communication fields See W1-GeneralCompletionEventType. Oracle Utilities Work and Asset Management User Guide 240

241 Attachments fields See W1-GeneralCompletionEventType. Asset Completion Event Type Business Object: W1-AssetCompletionEventType Defines details for the completion of an asset activity or event. Valid Activity Types fields Identifier fields Completion Event Information fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Indicates the asset type. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Asset Disposition Completion Event Type Business Object: W1-AssetDposCmpEvtType Defines details for the completion of an asset activity for disposition. Valid Activity Types fields Identifier fields Completion Event Information fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Target Asset Disposition Status Reason Failure: Yes/No Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Asset Maintenance Trigger Update Completion Event Type Business Object: W1-AssetMaintTrigUpdateCevtTyp Defines details for the completion of an asset activity created from a preventive maintenance trigger. Valid Activity Types fields Identifier fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Oracle Utilities Work and Asset Management User Guide 241

242 Inbound Communication fields See W1-GeneralCompletionEventType. Data Area Completion Event Type Business Object: W1-DataAreaCmpEvtType Valid Activity Types fields Identifier fields Completion Event Information fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Indicates the applicable data area and UI Map.. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Document Completion Event Type Business Object: W1-DocumentCompletionEventType Defines details for the completion of a document. Valid Activity Types fields Identifier fields Completion Event Information fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Indicates the applicable document business object and document type.. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Measurement Quick Entry Completion Event Type Business Object: W1-MsrmtQuickEntryCmplEvtType Defines details for the completion of a measurement entry. Valid Activity Types fields Identifier fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Oracle Utilities Work and Asset Management User Guide 242

243 Replication Completion Event Type Business Object: W1-ReplicationComplEventType Valid Activity Types fields Identifier fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Service History Completion Event Type Business Object: W1-ServiceHistTypeCmpEvtType Valid Activity Types fields Identifier fields Completion Event Information fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Indicates the applicable service history type. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Activity Type Service History Completion Event Type Business Object: W1-SvcHistFromActvCmplEvtType Valid Activity Types fields Identifier fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Work Request Completion Event Type Business Object: W1-WorkReqCompletionEventType Valid Activity Types fields See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Oracle Utilities Work and Asset Management User Guide 243

244 Identifier fields Completion Event Information fields UI Payload Create Data Mover fields Inbound Communication fields Attachments fields See W1-GeneralCompletionEventType. Indicates the applicable work request business object that is used when creating completion events of this type.. See above: W1-ActivityCompletionEventType. See W1-GeneralCompletionEventType. See W1-GeneralCompletionEventType. Completion Event Definitions Completion events are used to execute business events within the application. For example, completion events may be configured for several types of asset processing such as asset update, state transition, replication, service history and activity creation. Refer to the Manually Creating Completion Events section for more information. All completion events use the same set of fields: Execution Sequence: Indicates the order in which the event should be processed with relationship to other completion events. Inbound Communication: Information used to create a completion event for this completion event type using information defined within the inbound communication business object, or within its raw message. Event Information fields Shows the date and time for execution of the completion event and any comments that should be included. Completion Event Date/Time: Defines the date and time to execute the completion event. Comments: Free-form text field to enter supporting notes. Crew Name: Specifies a valid crew for the activity, as applicable. Relationship Information fields Payload Information fields Status (from the BO lifecycle) Shows any other system objects that are associated to the completed object. For example, if you are looking at the completion event for an activity, the relationship information shows the asset, any components, the location, service history, etc. Payload is the object or information created as the result of a completion event. For example, if you have a completion event to create service history, the service history is the payload. Valid statuses include: Pending Executed Discarded Once the completion event is in an executed state and does not have any errors, the event is considered complete. Create Activity Business Object: W1-CreActivityPayCmpEvt Use create activity completion events to process the creation of follow-up activities as the result of an activity. Oracle Utilities Work and Asset Management User Guide 244

245 Create Asset Business Object: W1-CreAssetPayCmpEvt Use create asset completion events to process the creation of assets as the result of an activity. Create Asset Attachment Business Object: W1-CreAssetAttachCmpEvt Use create asset attachment completion events to process the creation of attachments on assets as the result of an activity. Create Location Attachment Business Object: W1-CreNodeAttachCmpEvt Use create location attachment completion events to process the creation of attachments on locations as the result of an activity. Create Service History Business Object: W1-CreServiceHistoryPayCmpEvt Use create service history completion events to process the creation of service history for assets as the result of an activity. Create Service History Attachment Business Object: W1-CreServiceHistoryAttCmpEvt Use create service history attachment completion events to process the creation of attachments on service history as the result of an activity. General Asset Replication Business Object: W1-AssetReplicationComplEvent Use general asset replication completion events to process the creation of assets from an asset replication activity. Replication Completion Event Type Business Object: W1-ReplicationComplEventType Use replication completion events to process the creation of assets from an asset replication activity. Transition Asset Business Object: W1-TrnAssetCmpEvent Use transition asset completion events to process changes in status and/or location for assets as the result of an activity. Update Asset Business Object: W1-UpdAssetPayCmpEvt Use update asset completion events to process the update of assets as the result of an activity. Update Location Business Object: W1-UpdNodePayCmpEvt Use update location completion events to process the update of locations as the result of an activity. Oracle Utilities Work and Asset Management User Guide 245

246 Asset Maintenance Trigger Update Business Object: W1-AssetMaintTriggerUpdateCEVT Defines details for the completion of an asset activity related to a preventive maintenance trigger. Create Asset Document Completion Event Business Object: W1-CreAssetDocumentCmpEvt Defines details for the completion of Create Document Pay Completion Event Business Object: W1-CreDocumentPayCmpEvt Defines details for the completion of Create Location Document Completion Event Business Object: W1-CreLocationDocumentCmpEvt Defines details for the completion of Create Service History Document Completion Event Business Object: W1-CreSvcHstDocumentCmpEvt Defines details for the completion of Create Work Request Document Completion Event Business Object: W1-CreWorkReqDocumentCmpEvt Defines details for the completion of Create Work Request Pay Completion Event Business Object: W1-CreWorkRequestPayCmpEvt Defines details for the completion of Measurement Quick Entry Competion Event Business Object: W1-MsrmtQuickEntryCmplEvt Defines details for the completion of an asset measurement. Inbound Communication Definitions The Inbound Communication portal provides details related to the information received from an external system such as Oracle Utilities Mobile Workforce Management. Use inbound communication to create a completion event using information defined within the raw message coming from an external system. Refer to the Manually Creating an Inbound Communication section for more information. Activity Completion Inbound Communication Business Object: W1-ActivityComplInboundComm Oracle Utilities Work and Asset Management User Guide 246

247 Event Information fields Initiating Activity ID: If the inbound communication is initiated by an activity, the ID is indicated here. Shows the date and time for execution of the completion event and any comments that should be included. Completion Event Date/Time: Defines the date and time to execute the completion event. Comments: Free-form text field to enter supporting notes. Crew Name: Specifies a valid crew for the activity, as applicable. Relationship Information fields Establishes the record numbers associated with the inbound communication. Asset ID: The identifier for the related asset. Attached to Asset ID: The identifier for the asset where the component is installed, if applicable. Location ID: The identifier for the related location. Service History ID: The identifier for the related service history. Identifier Information fields Identifiers are additional attributes, determined by your organization, that can be assigned to further characterize an entity and can be used to search for an object. On inbound communication, they may also be used to create a connection between the asset ID and an entity from the external system. Identifier Type and Value: The Asset, Component Asset, Activity Type and Location can use user-defined identifiers to provide additional reference information. Incoming Message fields Status (from the BO lifecycle) Raw Message: The message that comes from the external system. This can be entered manually if needed to simulate the message coming from the external system or to force completion of messages from the external system. Valid statuses include: Pending Validate and Create Validation Error Completed Discarded Create and Complete Activity Inbound Communication Business Object: W1-CreComActivityInboundComm This business object uses the same fields as W1-ActivityComplInboundComm with the exception that there is no Initiating Activity ID. Create Activity Inbound Communication Business Object: W1-CreateActivityInboundComm This business object uses the same fields as W1-ActivityComplInboundComm with the exception that there is no Initiating Activity ID. Communication Type Definitions Communication types define the information required for the system to receive messages from external systems. Please refer to the Defining Communication Types section for more information. Business Object: W1-GeneralCommunicationType Oracle Utilities Work and Asset Management User Guide 247

248 Communitcation Type: A unique name or code for the communication type. : A useful description of the communication type which will appear in drop-down lists. Inbound Communication Business Object: The inbound communication business object that will be used when creating communications of this type. Exception Handling fields Determines how the system will handle errors or other exceptions. To Do Type and To Do Role: Determine the follow up actions when an exception occurs. Maximum Retries and Retry Frequency: The maximum number of times the system tries to complete the transaction before failing and how frequently it should submit the retry attempts. Discard Reason: When the transaction fails, the default discard reason that is set here displays on the record for auditing. Message Validation fields Required Value Source XPath: defines source elements within the inbound communication business object or raw message. Required Value Source XPath Value: defines target elements within the inbound communication business object. Communication Data Mapping fields The Communication Data Mapping information can be used to populate communication business object elements from information within the communication's raw message. Source XPath defines source elements within the inbound communication business object or raw message. Note that a literal can be specified by using single quotes, for example 'W1BN' means move the string 'W1BN' to the target. Target XPath defines target elements within the inbound communication business object. Maintenance tip: The correct XPath values can most easily be obtained using the View Schema link for the appropriate business object or data area. For example, to obtain a target XPath element, open the View Schema dialog for the W1-ActivityComplInboundComm business object, then click on the identifiervalue element, and, finally, copy the XPath value (assetidentifierinformation/identifiervalue) from the top of the view dialog. To support this strategy for the inbound communication's raw message XML, it will be necessary to create a data area that represents the schema of the inbound communication's raw message. Please note that the outermost node of this data area must be 'rawmessage' as this element identifies the data structure within the inbound communication business object that houses the raw message. Attachment Suppression fields When a message is received from an external system, the message may contain attachment data which is very large. The substitution text entered in this section can be used in place of that large data in the completion event list on the inbound communication. The attachment element xpath identifies the data to match it to the substitution text. This serves to prevent transfer delays in cases where large amounts of data might overload the browser. Oracle Utilities Work and Asset Management User Guide 248

249 Project Object s This section provides descriptions of the attributes used for project related objects as they are delivered in the base application. Project Category Definitions Your organization can define project categories to create classifications for projects such as maintenance, capital, construction, and so on. Refer to the Defining a Project Category section for more information. Business Object: W1-ProjectCategory Project Category: A unique name or code for the project category. : A useful description of the project category which will appear in drop-down lists. Project Definitions Projects provide a way to group work so that it can be planned and charged against large efforts. Typically, a project will be a task that is out of the ordinary, or that requires extra planning and resources. Examples would be adding new facilities or conducting a major overhaul of an assembly line. Refer to the Creating a Project section for more information. Business Object: W1-Project : A description of the project. Detailed Project Category: The categorization for the project. Parent Project: The record identifier for the umbrella project. Subprojects are created by referencing a parent. Supervisor: The username of the person responsible for the project. Allow Charge: When this indicator is set to yes other records can charge against the project. The project must be in Approved, Started or Complete state for charges to be applied against it. For example, a resource such as a craft or equipment might reference the Project ID under the accounting information. Note that if subprojects are planned, the project itself should have Allow Charge set to No. Charges should be tracked by subproject. WO Approval Profile: The default approval profile authorized to approve the project. Accounting Information fields Account Segment: A free form field which builds the general ledger account number that is shown in the financial transaction log. Project Budget: Indicates a dollar value budget for the project. Cost Center/Percentage: List of cost centers which will which will incur charges against this project. The percentage field indicates the percent to allocate to each cost center when more than one are indicated. Oracle Utilities Work and Asset Management User Guide 249

250 Scheduling Information fields Indicates the estimated and actual start and end dates for the project. The actual dates are carried over from the work records as they are completed and closed. Estimated Start Date Estimated End Date Actual Start Date Actual End Date Status (from the BO lifecycle) Created Pending Approval Approved Started Completed Rejected Closed Canceled Material Disposition Definitions Material disposition is a process designed to track repairable assets/stock items. The process tracks the asset or component from when it is removed from service to where it is either retired, scrapped or repaired and returned to availability for reuse. The portal is accessed under the Work Management menu. Business Object: W1-GenMaterialDisposition : A useful description of the material disposition which will appear in drop-down lists. Detailed : A more detailed description. Free form text. Assets Asset: The record number for the asset or component being dispositioned Initial Relationship/Actions: Indicates the various disposition statuses. Statuses mange the asset that is installed as a replacement as and the broken asset that has been removed designated for repair. Possible disposition statues include install, repair, retire, store, change location, pending disposition, change status reason, and so on. Status (from the BO lifecycle) Valid statuses include: Open Closed Oracle Utilities Work and Asset Management User Guide 250

251 Timekeeping Object s This section provides descriptions of the attributes used for timekeeping related objects as they are delivered in the base application. Time Period Definitions Your organization must create time periods to define valid from and to dates for labor costing and timesheet reporting. Time periods have to be distinct and cannot overlap. When a new timesheet is created, the system defaults to the current time period. Refer to the Defining Time Periods section for more information. Business Object: W1-TimePeriod Time Period: A unique name or code for the time period. : A useful description of the time period which will appear in drop-down lists. Start/End Dates: Dates defining the time period. Labor Earning Type Definitions Labor earning types define earnings codes for your organization which includes an adder and a multipler to calculate labor costs. Refer to the Defining a Labor Earning Type section for more information. Business Object: W1-LaborEarningType Labor Earning Type: A unique name or code for the labor earning type. : A useful description of the labor earning type which will appear in drop-down lists. Adder: A value that is added to the base wage rate. Multiplier: A value that is multiplied by the base wage rate. Overtime Type Definitions Overtime types define overtime codes for your organization which includes a multiplier to calculate the premium rate that workers earn for overtime. Refer to the Defining an Overtime Type section for more information. Business Object: W1-OvertimeType Overtime Type: A unique name or code for the overtime type. Oracle Utilities Work and Asset Management User Guide 251

252 : A useful description of the overtime type which will appear in drop-down lists. Premium Rate Multiplier: A value that is multiplied by the base wage rate to derive the overtime (premium) rate. Timesheet Definitions Timesheets are used to record the amount of time that workers (labor resources) spend on activities or work orders. Once charges are entered, processing allows employees to receive proper compensation for their work and labor charges are applied to the appropriate cost buckets. Business Object: W1-Timesheet Status (from the BO lifecycle) Employee: The employee number of the person incurring the charge. Valid statuses include: Created Pending Approval Approved Posted Rejected Cancelled Timesheet Detail Definitions Timesheets are used to record the amount of time that workers (labor resources) spend on activities or work orders. Once charges are entered, processing allows employees to receive proper compensation for their work and labor charges are applied to the appropriate cost buckets. Business Object: W1-TimesheetDetail Accounting Information fields Timesheet Detail fields Status (from the BO lifecycle) Expense Code: The expense code to be charged for the timesheet. Detail Cost Center: A valid list of cost centers to be charged for the timesheet and a percent breakdown for each cost center. Indicates the date, crew shift, labor earning type, craft hours, work start and stop dates and times, travel time, comments and other information to complete the timesheet. Valid statuses include: Created Posted Canceled Oracle Utilities Work and Asset Management User Guide 252

253 Preventive Maintenance Object s This section provides descriptions of the attributes used for preventive maintenance related objects as they are delivered in the base application. Preventive Maintenance Calendar Definitions Preventive maintenance calendars establish work calendars with explicit effective dates and schedule dates. These are used to schedule activities created by preventive maintenance triggers. The main function of the calendar is to allow direct control over scheduled work dates. Business Object: W1-WorkCalendar Maintenance Calendar: A unique name or code for the calendar. : A useful description of the calendar which will appear in drop-down lists. Schedule Dates: Indicates the effective dates and schedule dates which define the schedule. Preventive Maintenance Schedule Definitions Preventive maintenance schedules contain a basic list of maintenance triggers and a schedule of when maintenance should occur based on those triggers. For example, typical maintenance triggers would be when a car reaches a certain number of miles, when a certain amount of time has passed, or when an asset reaches a certain number of hours of runtime. Maintenance schedules provide a comprehensive set of analytics which provide information on failure types, failure modes, and repairs. Refer to the Creating a Maintenance Schedule section for more information. Maintenance Schedule Business Object: W1-MaintenanceSchedule Detailed Asset Type: Indicates the type of assets to which the schedule applies. Status (from the BO lifecycle) Valid statuses include: Active Reliability Centered Maintenance Schedule Business Object: W1-RCMSchedule Oracle Utilities Work and Asset Management User Guide 253

254 Detailed Asset Type: Indicates the type of assets to which the schedule applies. Asset Location Selection Template: The record ID for the asset location selection template. Status (from the BO lifecycle) Valid statuses include: Active Preventive Maintenance Trigger Definitions Preventive maintenance triggers indicate a certain event which, when it occurs, maintenance should be done on an asset. For example, typical maintenance triggers would be when a car reaches a certain number of miles, when a certain amount of time has passed, or when an asset reaches a certain number of hours of runtime. Refer to the Creating a Maintenance Trigger section for more information. Calendar Anniversary Business Object: W1-CalendarAnniversary Calendar Anniversary is a fixed calendar interval type where regardless of the time lapse between the work creation and completion, the future maintenance schedule date remains the same. This type of interval scheduling is generally used to fulfill regulatory compliance for inspections and licensing requirements on fixed date schedules. For example, this would trigger an inspection every three months regardless of when the last inspection was completed. Maintenance Schedule: The maintenance schedule used with the trigger. Allow Multiple In Process Activities Copy Asset Location Cost Center Processing Information fields Work Order Default fields Template Work Order: The work order template used when creating the maintenance as a result of the trigger. Activity Type: The type of activity created as a result of the trigger. Work Priority: Defines the importance of the work in terms of the potential impact of not addressing issues. For example, a work for assets at a hospital might have a high criticality rating since losing power there might result in deaths of patients, while work for assets at a city park would have a low criticality since there are few consequences if the lawns are not mowed on time. Work priority is represented on a scale of low (little to no impact) to high (significant impact). Service Class: The service class to use on the work order. Outage Type: Indicates the type of outage such as general shut down, breakdown, and so on. Backlog Group: The team that is usually responsible for doing the actual maintenance. Approval Profile: The approval profile used when creating the work records from the trigger. Calendar Information fields Indicates the number of years, months, days and lead days that define the calendar interval for the trigger. For example, maintenance that needs to be done every 2 years, would indicate a 2 in the Years field. Lead Days: The value set here impacts the calculation of the trigger date. For example, if the trigger set as every 6 months and this value is set to 5, the trigger date is 6 months minus 5 days. Status (from the BO lifecycle) Valid statuses include: Active Oracle Utilities Work and Asset Management User Guide 254

255 Inactive Calendar Interval Business Object: W1-CalendarInterval Calendar Interval is a fluid interval type where the forecasted scheduled date is adjusted and re-forecast based on the completion date of the previously completed work which is managed through service history. For example, this would trigger an oil change every 3 months with the next trigger based on the most recent oil change. This trigger uses the same fields as W1-CalendarAnniversary with the following exceptions: Calendar Information fields Allow Multiple In Process Activities: n/a Indicates the number of years, months, days and lead days that define the calendar interval for the trigger. For example, maintenance that needs to be done every 2 years, would indicate a 2 in the Years field. Indicates the number of years, months, days and lead days that define the calendar interval for the trigger. For example, maintenance that needs to be done every 2 years, would indicate a 2 in the Years field. Lead Days: The value set here impacts the calculation of the trigger date. For example, if the trigger set as every 6 months and this value is set to 5, the trigger date is 6 months minus 5 days. Runtime Anniversary Business Object: W1-RuntimeAnniversary Runtime Anniversary is fixed interval type maintenance where regardless of the metered operation between the recent activity or service history and completion of work, the maintenance is not re-forecast. For example, this would trigger an inspection after every 100 hours of runtime service. This trigger uses the same fields as W1-CalendarAnniversary with the following exceptions: Runtime Information fields Runtime Value: Indicates the amount of time before maintenance is triggered. Lead Value Measurement UOM: Unit of measurement. Runtime Interval Business Object: W1-RuntimeInterval Runtime Interval is a fluid interval type where the maintenance schedule is adjusted and reforecast based on the completion runtime readings of the previously completed activity. For example, this would trigger an oil change every 3000 miles with the next trigger based on the odometer reading at the time of the last oil change. This trigger uses the same fields as W1-RuntimeAnniversary with the following exceptions: Allow Multiple In Process Activities: n/a RCM, or reliability centered maintenance, represents proactive maintenance processing which helps to ensure that assets run without fail. Your organization might define maintenance triggers specific to RCM processing. Oracle Utilities Work and Asset Management User Guide 255

256 RCM Calendar Anniversary Business Object: W1-RCMCalendarAnniversary This trigger uses the same fields as W1-CalendarAnniversary with the following exceptions: Calendar Information fields Asset Qualification Conditions fields Risk Priority Number Indicates a maintenance calendar and then the number of years, months, days and lead days that define the calendar interval for the trigger. For example, maintenance that needs to be done every 2 years, would indicate a 2 in the Years field. Asset Condition From Asset Condition To Location Criticality From Location Criticality To RCM Calendar Interval Business Object: W1-RCMCalendarInterval This trigger uses the same fields as W1-RCMCalendarAnniversary. RCM Runtime Anniversary Business Object: W1-RCMRuntimeAnniversary This trigger uses the same fields as W1-RCMCalendarAnniversary. RCM Runtime Interval Business Object: W1-RCMRuntimeInterval This trigger uses the same fields as W1-RCMRuntimeAnniversary with the following exceptions: Runtime Information fields Allow Multiple In Process Activities: n/a Runtime Value: Indicates the amount of time before maintenance is triggered. Lead Value Measurement UOM Unit of measurement. Asset Location Maintenance Trigger Business Object: W1-AssetLocMaintTrigger Location/Organization ID Maintenance Trigger ID Oracle Utilities Work and Asset Management User Guide 256

257 Failure Profile Definitions Reliability centered maintenance is a process which helps to ensure that assets run without fail. Define failure types, failure modes, failure repairs, failure components and failure profiles within the system, and use these elements together to form a comprehensive RCM system. Effective use of RCM can increase cost effectiveness, improve machine uptime, and help your organization to understand the level of risk you have undertaken with certain assets. Business Object: W1-FailureProfile Failure Profile: A unique name or code for the profile. : A useful description of the profile which will appear in drop-down lists. Failure Profile Failure Type Business Object: W1-FailureProfileFailureType Represents the specific manner or way by which a failure occurs in terms of failure of the part. This may generally describe the way a failure occurs such as due to corrosion, debris, or distortion. Failure Profile: The profile that defines the failure type. Failure Type: Defines a valid list of failure type codes related to the profile. Failure Profile Failure Mode Business Object: W1-FailureProfileFailureMode Describes what has failed. Failure Profile: The profile that defines the failure modes. Failure Mode: Defines a valid list of failure mode codes related to the profile. Failure Profile Failure Repair Business Object: W1-FailureProfileFailureRepair Indicates the repair that will be performed on the asset in case of failure. Failure Profile: The profile that defines the failure repair. Failure Repair: Defines a valid list of failure repair codes related to the profile. Failure Profile Failure Component Business Object: W1-FailureProfileFailureComp Indicates the part of the asset for which the failure has occurred. Oracle Utilities Work and Asset Management User Guide 257

258 Failure Profile: The profile that defines the failure component. Failure Component: Defines a valid list of failure components related to the profile. Financial Object s This section provides descriptions of the attributes used for financial objects as they are delivered in the base application. Refer to the Understanding Financials section for a conceptual overview. Accounting Calendar Definitions Your accounting calendar determines the accounting periods where financial transactions are posted. An open accounting period is the time period during which costs accumulate. You can configure these periods to match the accounting periods used by your general ledger application. Refer to the Creating an Accounting Calendar section for more information. Business Object: W1-AccountingCalendar Accounting Calendar: The unique identifier for the accounting calendar. : of the accounting calendar which appears in drop down lists. Number of Periods: Represents the number of periods within the accounting period defined by the calendar. This must be entered as a value greater than 0. Periods do not have to be months nor are they all required to be the same length. Periods fields Fiscal Year: Represents the year during which the accounting period occurs. Years do not have to begin on January first or end on December 31 or be 365 days long. Accounting Period/: Identifies the accounting period. Start Date/End Date: The time frame that defines the accounting period. Open from Date/Open to Date: Costs are allowed to accumulate for the accounting period during this time frame. Note the Open dates can be different than the period start and end dates. Adjustments and postings can be made until the Open to Date which also represents the date that the period is considered closed. Business Unit Definitions Business units are used as cost reporting entities for timekeeping expenses. Business Object: W1-BusinessUnit Business Unit: The unique name for the business unit. : of the business unit which appears in drop down lists. Payroll Clearing Cost Center: The cost center where payroll costs are applied. Oracle Utilities Work and Asset Management User Guide 258

259 Labor Cost Source: Either a craft billable rate or a employee billable rate. Commodity Code Definitions Commodity Codes are an alternate way to describe stock items which can be helpful when you need to locate a specific stock code because they form a logical segmented code for a stock item. Codes are segmented by commodity category, name, type, and composition. The Stock Item portal can be searched by commodity code where you can filter by a variety of criteria. Refer to the Defining a Commodity Code section for more information. Commodity Category Business Object: W1-CommodityCategory Commodity Category: A unique name or code for the commodity category. : of the commodity category which appears in drop down lists. Commodity Names fields The second segment of the category. For each category, there is a unique list of commodity names. Commodity Name Business Object: W1-CommodityName Commodity Name: The unique commodity name. : of the commodity name which appears in drop down lists. Commodity Type fields The third segment of the category. For each category and name combination, there is a unique list of commodity types. Commodity Type Business Object: W1-CommodityType Commodity Type: The unique commodity type. : of the commodity type which appears in drop down lists. Commodity Composition fields The fourth segment of the commodity code. For each category/name/type combination, there is a unique list of commodity compositions. Cost Category Definitions Cost categories group expenses or costs into logical buckets for reporting purposes. Refer to the Defining a Cost Category section for more information. Business Object: W1-CostCategory Oracle Utilities Work and Asset Management User Guide 259

260 Cost Category: The unique name of the cost category. : of the cost category which appears in drop down lists. Color: Defines the color that represents the cost category in graphs and pie charts. Color Definitions Your organization can use the Colors portal to define custom colors used to represent transactions and other entities throughout the system. For example, colors defined here are used to distinguish cost categories as they are represented in graphs and/or pie charts throughout the system. Colors defined in this module are also used as the fill or outline color when Shapes are defined. Refer to the Defining a Color section for more information. Business Object: W1-Color Expense Code: The unique name for the color. : of the color which appears in drop down lists. Hex Value: The html color code. Color Sample: Displays a rending of the color based on the color code. Cost Center Definitions As costs are incurred, the system tracks them and accumulates them at different levels or cost centers within your organization. Cost centers are part of the accounting hierarchy. Please refer to the Defining a Cost Center section for more information. Cost Center Business Object: W1-CostCenter Cost Center: The unique name for the cost center. : of the cost center which appears in drop down lists. Account Segment: A free form field which builds the general ledger account number that is shown in the financial transaction log. Allow User Charge: User records that result in costs or charges need to reference a cost center that has this value set to Yes. For example, when users create activities, the referenced cost centers must allow user charges. This value is set to No on cost centers that are specifically designated for general ledger or system generated costs. For example, an inventory cost center is referenced on storerooms to balance the debit and credit sides of the general ledger (issue materials for an activity to charge the debit side and reduce the inventory value adjusts the debit side). Budget Amount: Indicates the budgeted amount for the cost center. This is for informational purposes only, however, as the cost center accrues costs, the statistics fields for the cost center provide a year to date actual Oracle Utilities Work and Asset Management User Guide 260

261 Cost Center Status (from the BO lifecycle) costs value which your organization can use to compare to the budget amount. These are the actual costs incurred against the cost center for the current year. The unique name for the cost center. of the cost center which appears in drop down lists. Valid statuses include: Active Inactive Accumulate Monthly Statistics Distribution Code Definitions Distribution codes simplify the process of generating accounting entries by defining valid combinations of values for charts of accounts. Refer to the Defining a Distribution Code section for more information. Business Object: W1-DistributionCode Distribution Code: A unique name or code for the distribution code. : of the distribution code which appears in drop down lists. GL Account Construction Algorithm GL Account Details fields Effective Date: Indicates the date that the general ledger account goes into effect. GL Account: Indicates the account number for your organization's general ledger account. Expense Code Definitions Expense codes are codes assigned to a financial expenditure indicating which payment category the cost falls into. They are part of the accounting hierarchy. Refer to the Defining an Expense Code section for more information. Business Object: W1-ExpenseCode Expense Code: The unique name for the expense code. : of the expense code which appears in drop down lists. Resource Class: Indicates the type of resource that applies for the expense code such as material, craft, equipment or other. Expense codes are referenced on work and purchasing records where there are resource requirements. Cost Category: Indicates the cost category to use with the expense code. Account Segment: A free form field which builds the general ledger account number that is shown in the financial transaction log. Oracle Utilities Work and Asset Management User Guide 261

262 Status (from the BO lifecycle) Active Inactive Factor Object s This section provides descriptions of the attributes used for factor related objects as they are delivered in the base application. Factor Definitions Factors are defined by your organization as a tax component needed to calculate tax values related to anything which incurs costs for your organization and must be taxed (such as purchases and resources used to complete activities). For example, you might define different factors for city tax, state tax and federal tax. Each type of factor would define a factor values list providing numerical values used to calculate the tax. The factor is then referenced on a Tax Rate Schedule. Please refer to the Defining a Factor section for more information. Business Object: W1-Factor Factor: The unique name or code for the factor. : of the factor which appears in drop down lists. Characteristic Source Algorithm: The algorithm used to define the characteristic for the factor. Factor Characteristic Type Factor Characteristic Values fields The factor value that is to be applied to the factor. Factor Characteristic Value: List of factor values that are to be applied to the factor. Factor Value Definitions Factors are defined by your organization as a tax component needed to calculate tax values related to anything which incurs costs for your organization and must be taxed (such as purchases and resources used to complete activities). For example, you might define different factors for city tax, state tax and federal tax. Each type of factor would define a factor values list providing numerical values used to calculate the tax. The factor is then referenced on a Tax Rate Schedule. Please refer to the Defining a Factor section for more information. Business Object: W1-FactorValue Factor Characteristic Value Effective Date/Time: The date and time value for when the factor goes into effect. Factor Value: The tax component used to calculate tax values. Oracle Utilities Work and Asset Management User Guide 262

263 Financial Transaction Definitions Financial transactions are created in the system whenever an object generates a cost transaction. For example, the posting of a timesheet or other direct charges causes the creation of a financial transaction. Authorized users can access this accounting log at any time to review transactions. Business Object: W1-FinancialTransaction FT Processes fields GL Details fields Status (from the BO lifecycle) Accounting Date: The date when the transaction posted.. Indicates the batch control that was run to generate the transaction. Indicates the details about transaction, such as the amount, the account number, distribution code, project, cost center, expense code, GL account, characteristic type and so on. Created Populate GL Detail Error Frozen Tax Rate Schedule Definitions A Tax Rate Schedule defines the type of taxes that are applicable at various instances in time for related resources (materials, labor, equipment, and other). The tax rate can be defined on a resource type, but this can be overridden for specific storerooms if necessary. Business Object: W1-TaxRateSchedule Tax Rate Schedule: The unique name for the tax rate schedule. : of the tax rate schedule which appears in drop down lists. Tax Components fields Effective Date: The effective date of the tax component. Sequence: The order in which the tax component is applied. : The description of the tax component. Factor: The factor that defines the specific tax component. Cost Center: The cost center that tracks cost for the specific tax component. Expense Code: The expense code that tracks cost for the specific tax component. Refer to the Defining a Tax Rate Schedule section for more information. Oracle Utilities Work and Asset Management User Guide 263

264 General Administrative Object s This section provides descriptions of the attributes used for general administrative related objects as they are delivered in the base application. Statistics Definitions The Statistics portal captures metrics that are collected via batch processing. These embedded analytics are not present in real time, but rather are accumulated and presented as they are processed by batch. These analytics are displayed on the Home Page. Crew Work Order Summary Business Object: W1-CrewWOSummary Number of Weeks Organization WO Statistics fields Indicates the number of weeks to show on the graph or chart. Provides the parameters for rendering the graph or chart. Owning Organization Crew Week Number Planned WO Count Active Activity Count Status [from the BO lifecycle] Active Inactive Capture Planner Work Order Summary Business Object: W1-PlannerWOSummary Number of Weeks Organization WO Statistics fields Indicates the number of weeks to show on the graph or chart. Provides the parameters for rendering the graph or chart. Owning Organization Planner Week Number Planned WO Count Completed WO Count Active Activity Count Status [from the BO lifecycle] Active Oracle Utilities Work and Asset Management User Guide 264

265 Inactive Capture Oracle Utilities Work and Asset Management User Guide 265