TABLE OF CONTENTS DOCUMENT HISTORY

Transcription

1

2 TABLE OF CONTENTS DOCUMENT HISTORY 4 UPDATE 17D 4 Revision History 4 Overview 4 Optional Uptake of New Features (Opt In) 5 Update Tasks 5 Feature Summary 6 Installed Base 7 Track Quantity Changes of Nonserialized Assets 7 Maintenance 9 Prioritize Work Order Execution Based on Material Availability 9 UPDATE 17C 14 Revision History 14 Overview 14 Optional Uptake of New Features (Opt In) 14 Update Tasks 14 Release Feature Summary 15 Oracle Maintenance Cloud 15 Installed Base 15 Track Nonserialized and Intangible Assets 15 Capture Key Asset Information During Outbound and Inbound Fulfillment Processes 17 Create and Update Customer Assets Using Enhanced Installed Base Web Services 20 Upload Data Using Spreadsheets 21 Integrate Customer Asset Information with Third Party Applications Using Business Events 22 UPDATE 17B 23 Revision History 23 Overview 23 Optional Uptake of New Features (Opt In) 24 Update Tasks 24 Release Feature Summary 24 Maintenance Cloud 25 Maintenance 26 Define Maintenance Master Data 26 Create and Use Maintenance Organizations 26 Quickly Set Up Common Components and Facilities 27 Define and Manage Assets 28 Create Assets 28 Procure Assets 29 Build Assets 29 Import Assets 30 Define Asset Parts List 30 Work Execution 31 Use the Maintenance Work Area Landing Page 31 Execute Work Orders 33 Use Simplified Reporting for Maintenance Tasks 33 2

3 Outside Processing 35 Manage and Execute Supplier Operations 35 Create and Manage Purchasing Documents 35 Monitor and Review Supplier Operation Details 36 Additional Maintenance Management Enhancements 37 Visually Design Maintenance Work Definitions 37 Manage Maintenance Work Orders 37 Report Maintenance Work Order Costs Comprehensively 39 Select and Access Favorites in Maintenance 40 Collaborate with Stakeholders on Work Definitions and Work Orders Using Oracle Social Network 41 Oracle Installed Base 41 Streamline Asset Creation and Return Process 42 Integrate with Oracle Enterprise Contracts Cloud 43 Integrate with Oracle Maintenance Cloud 44 Use Web Services to Manage Data 45 Upload Data Using Spreadsheets 45 APPENDIX A: FUNCTION SECURITY PRIVILEGES AND AGGREGATE PRIVILEGES 46 3

4 DOCUMENT HISTORY This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table: Date Update Version Notes 20 OCT 2017 Update 17D New features delivered in update 17D. 01 SEP 2017 Update 17C New features delivered in update 17C. 21 APR 2017 Update 17B New features delivered in update 17B. UPDATE 17D REVISION HISTORY This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table: Date Feature 20 OCT 2017 Notes Created initial document. OVERVIEW This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. SECURITY AND NEW FEATURES The Role section of each feature in this guide identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup unless otherwise indicated. If you have created custom job roles, then you can use this information to add new privileges to those roles as needed. GIVE US FEEDBACK We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. 4

5 OPTIONAL UPTAKE OF NEW FEATURES (OPT IN) We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by opting in to the feature when you re ready. You can opt in to a feature in two ways: by using the New Features work area, or by using the Setup and Maintenance work area. To opt in using the New Features work area: Click the Navigator, and then click New Features (under the My Enterprise heading). On the New Features page, select the offering that includes new features you d like to review. Click Opt In for any feature that you want to opt in to. On the Edit Features page, select the Enable option for the feature, and then click Done. To opt in using the Setup and Maintenance work area: Click the Navigator, and then click Setup and Maintenance. On the Setup page, select your offering, and then click Change Feature Opt In. On the Opt In page, click the Edit Features icon. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 5. Click Done. UPDATE TASKS This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don t forget to check back and get the latest information before your update starts. 5

6 FEATURE SUMMARY Action Required to Enable Feature Feature None (Automatically Available) Enable via Opt In UI Plus Enable via Additional Opt In UI Only Steps Not Enabled via Opt In UI but Setup Required Issue Service Request Installed Base Track Quantity Changes of Nonserialized Assets Maintenance Prioritize Work Order Execution Based on Material Availability 6

7 INSTALLED BASE TRACK QUANTITY CHANGES OF NONSERIALIZED ASSETS You can now track asset quantity changes for nonserialized assets in Oracle Installed Base Cloud in the following manner. TRACK INCREASE IN QUANTITY Prior to this release, you could directly increase the quantity of an asset using the customer asset import process and REST API. With this release, you cannot update the quantity directly. Instead, you must create an asset with the characteristics of the original asset and the required quantity. Enterprise Contracts uses the new asset to create the corresponding addition of quantities for contracts. TRACK DECREASE IN QUANTITY You can still decrease the quantity of an asset using the customer asset import process or REST API. However, some modifications have been made in this release. The process of decrease in asset quantity is carried out in the following manner: 1. The application creates a split asset from the original asset and assigns the value of the decreased quantity to the split asset. 2. The quantity of the original asset is decreased by the value assigned to the split asset. 3. The split asset is terminated. 4. The information is sent to Enterprise Contracts, which allows a corresponding change in the quantity of contracts. The following example illustrates the process of decrease in the quantity of an asset: Current quantity of an asset. Asset Number Quantity UOM Customer Asset End Date A1 Each Blank (the asset is active) 10 You decrease the asset quantity from 10 to 8 with the transaction date of using the customer asset import process or initiate a similar request through REST API. Based on the original asset information and the requested action to change the quantity, the following is the result: Asset Number Quantity UOM Customer Asset End Date Split-from Asset A1 8 Each Blank (the asset is active) Blank A2 2 Each (the asset is terminated) A1 The split-from asset attribute is added to the asset entity to keep track of the origin of these split assets. 7

8 TRACK SALES ORDER SHIPMENTS QUANTITY With this release, a new asset is created for each shipment of a product or a lot. Therefore, for a single sales order line, if there are multiple shipments, an asset is created for each shipment with the corresponding shipped quantity of the product or the lot. The following is an example where a quantity of 52 is shipped with the first shipment, and then a quantity of 12 with the second shipment. As a result, the following two assets are created: Shipment Asset Quantity UOM Lot Number Shipment1 A1 52 Each LOT.XYZ Shipment2 A2 12 Each LOT.XYZ TRACK SALES ORDER RETURN QUANTITY As explained in the previous section, assets of the same product and lot are created for each shipment. Therefore, in case of returns, Installed Base decreases the customer asset quantities up to the most recent returned quantity in the order of the shipments. In the example below three shipments, each of quantity 4 were made (assets A1, A2, and A3). A quantity of 7 is returned by the customer. Therefore, asset A1 is terminated and a quantity of 3 is consumed against asset A2 triggering the creation an termination of the split-from asset A4 If the asset quantity is fully consumed, the asset is terminated. If the asset quantity is partially consumed, a splitfrom asset with the decreased quantity is created and terminated. The following table illustrates the example: Shipment Asset Quantity UOM Lot Number Customer Asset End Date Split-from Asset Shipment1 A1 4 Each LOT.XYZ (the asset is terminated) Blank Shipment2 A2 1 Each LOT.XYZ Null Blank Shipment3 A3 4 Each LOT.XYZ Null Blank Blank 3 Each LOT.XYZ (the asset is terminated) A2 A4 No steps are required to enable this feature. ROLE INFORMATION Customer Asset Import and Customer Asset REST Service: Job Role Name and Code: Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR) Privilege Name and Code: Import Customer Assets (CSI_IMPORT_CUSTOMER_ASSETS_PRIV) Privilege Name and Code: Manage Customer Asset by Service (CSI_MANAGE_CUSTOMER_ASSETS_BY_SERVICE_PRIV) 8

9 MAINTENANCE PRIORITIZE WORK ORDER EXECUTION BASED ON MATERIAL AVAILABILITY As a maintenance manager, you can ensure all materials are available for a work order prior to its release to the shop floor. As priorities change, you might need to execute work orders of lower priority that now have become a high priority. When materials are scarce, you can decide which work orders you can release, and which work orders you must place on hold until materials become available. To gain visibility into material availability for work orders, you can now do the following in this release: Recommend a list of work orders for material prioritization to be released, based on a combination of various attributes such as item and date criteria. Reassign available materials to work orders with higher priority when shortages exist. Release or hold work orders based on material availability and shortages to minimize shop floor disruptions. RECOMMEND PRIORITIZED LIST OF WORK ORDERS BASED ON MATERIAL AVAILABILITY AND OTHER CRITERIA You can define material availability rules that are used by the application to create an initial recommendation based on which work orders should be released when materials are scarce. The set of rules can be defined at an organization level to list work orders for material prioritization based on the following sorting and filtering criteria: List work orders in the order of material assignment priority based on critical items and work order start date. Include work orders within a specified time fence and having specific statuses, types, and subtypes. Include work orders with specific materials, or materials based on attributes such as make versus buy, and supply type. Exclude work orders from material deprioritization based on specific attributes of the item, and work order. You can configure the rules using the Work Order Assignment Priority tab of the Material Availability Rules task, as shown in the following screenshot: Work Order Assignment Priority Tab You can configure which work orders to include in the assignment criteria using the Inclusion Criteria of the Material Availability Rules task. This helps you to include work orders and specific materials based on time fence and specific attributes, as shown in the following screenshot: 9

10 Inclusion Criteria Tab You can configure to exclude work orders from deprioritization on force assignment of other work orders in the Force Assignment Criteria tab of the Material Availability Rules task, as shown in the following screenshot: Force Assignment Criteria Tab You can view the list of work orders with assignment priority to assess if materials are available or if there is a shortage of materials in the Work Orders tab of the Material Availability Assignments task, as shown in the following screenshot: Availability Assignments: Work Orders Tab You can view the material availability details for a work order, as shown in the following screenshot: 10

11 Assignment Details: Work Orders Tab VIEW EXPECTED SUPPLIES TO ADDRESS MATERIAL SHORTAGES In case of material shortages, you can view the expected supplies information of purchase orders and transfer orders for the scarce material. This helps you to decide whether to release a work order or to unrelease a released work order. You can view the expected supplies for the material, as shown in the following screenshot: Expected Supplies for Materials VIEW WORK ORDERS THAT REQUIRE MATERIALS TO ADDRESS SHORTAGES In case of material shortages, you can view the work orders that require materials and the corresponding availability and shortages pertaining to the material. This helps you know which material is critical for a work order, and you can decide to manually adjust the work order material assignments. You can view the material shortages in the Materials tab as shown in the following screenshot: Material Availability Assignments: Materials Tab You can view the work orders requiring the materials in the Materials tab, as shown in the following screenshot: 11

12 Affected Work Orders: Materials Tab VIEW AND ADJUST MATERIAL ASSIGNMENTS FOR WORK ORDER PRIORITIZATION From the list of prioritized work orders, you can manually change the material assignments. You can either force assign materials for a selected work order to ensure that all of its critical materials are available, or force unassign materials to release all of the critical materials for a work order. When changing the material assignment, you can preview the changes affecting the selected work order and other impacted work orders that are prioritized or deprioritized. A visual indicator of reassigned materials is shown in the list of work orders after implementing the change. You can view the work order material availability and force assign the work order as shown in the following screenshot: Force Assign Work Order You can preview the work orders which are unassigned on force assigning of the work order, as shown in the the following screenshot: Preview of Force Assigned and Unassigned Work Orders You can view the visual indicator to identify the force assigned and force unassigned work orders after implementing the material reassignment as shown in the following screenshot: 12

13 Visual Indicator to Identify the Force Assigned and Force Unassigned Work Orders CHANGE THE STATUS OF MULTIPLE WORK ORDERS BASED ON MATERIAL ASSIGNMENTS Once you have previewed the material assignments and adjusted your changes accordingly, you can release work orders that are ready for execution, unreleased work orders, or place a hold on work orders that you do not want the shop floor to work on currently. You can achieve greater shop floor efficiency, flexibility, and higher profits by ensuring that the highest priority work orders are released to the shop floor when there are material shortages. Work orders without all materials available can be quickly unreleased, or put on hold until materials are available and assigned. By only working on work orders that can be completed and shipped, companies can improve efficiency and increase revenue. You can change the status of one or multiple work orders using the mass action menu as shown in the following screenshot: Mass Action: Release Work Order You must opt in to and enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document. TIPS AND CONSIDERATIONS This feature is also applicable to Oracle Manufacturing Cloud. ROLE INFORMATION Privilege Name and Code: Report Material Transactions (WIP_REPORT_MATERIAL_TRANSACTIONS_PRIV) Job Role Name and Code: (_JOB) 13

14 UPDATE 17C REVISION HISTORY This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table: Date Feature 01 SEP 2017 Notes Created initial document. OVERVIEW This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. SECURITY & NEW FEATURES If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of. GIVE US FEEDBACK We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com. OPTIONAL UPTAKE OF NEW FEATURES (OPT IN) We continue to add many new features to Oracle Cloud Applications and we now give you the option to take advantage of new functionality at a pace that suits you. The New Features UI is available to you from your cloud homepage, where you can make your choices and do any configuration necessary. UPDATE TASKS This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don t forget to check back and get the latest information before your update starts. 14

15 RELEASE FEATURE SUMMARY Action Required to Enable Feature Feature Automatically Available End User Administrator Action Action Required Required Oracle Service Request Required Oracle Maintenance Cloud Installed Base Track Nonserialized and Intangible Assets Capture Key Asset Information During Outbound and Inbound Fulfillment Processes Create and Update Customer Assets Using Enhanced Installed Base Web Services Upload Data Using Spreadsheets Integrate Customer Asset Information with Third Party Applications Using Business Events ORACLE MAINTENANCE CLOUD In this update, Oracle Installed Base Cloud is our focus. Installed Base is a central repository for both internally owned enterprise asset information and customer owned asset information. Internal enterprise asset insight is critical to ensure effective asset maintenance for asset-intensive companies, particularly those who rely heavily on physical assets for the manufacture and delivery of their products. Customer asset information is increasingly critical as businesses continue to expand their offerings to include post-sale services, or transform to product-service systems. In this update, Installed Base provides you greater asset insight with more comprehensive asset information and integration with Oracle Order Management Cloud. INSTALLED BASE TRACK NONSERIALIZED AND INTANGIBLE ASSETS In addition to tracking serialized assets, with this release, Installed Base tracks nonserialized assets and intangible assets (e.g. noninventory tracked subscription licenses). Regardless of how your customers obtain their products, you always have the most current and accurate information about your customer s assets. FEATURE DETAILS With this release, Installed Base is adding support for assets based on the following type of products: 15

16 Nonserialized tangible products: products typically managed in inventory,lot controlled or not. Intangible products : noninventory-tracked products such as subscriptions or software licenses. The following capabilities have been enabled in Installed Base: Creation and update of customer assets referring to nonserialized and intangible products via the filebased data import capability. Creation and update of customer assets referring to nonserialized and intangible products via the customer REST API capability. Capturing creations and updates of customer assets product instances during the logistics and order management integration, for example: If an asset-tracked and lot controlled product is shipped, a customer asset is created. If an asset-tracked and lot controlled product is returned from the customer, the returned quantity is deducted from the customer asset. IMPORTING NONSERIALIZED ASSETS Installed Base now allows you to import an asset associated to a nonserialized product as well as providing the asset quantity. Going forward, these assets can be updated in the same manner as any other assets such as changing the asset customer ownership, location or terminating it. USING THE CUSTOMER ASSET REST API FOR NONSERIALIZED ASSETS Installed Base now allows you to create an asset associated with a nonserialized product as well as provide the asset quantity. Going forward, these assets can be updated in the same manner than any other assets such as changing the asset customer ownership, location or terminating it. LOGISTICS AND ORDER MANAGEMENT INTEGRATION Installed Base is now creating the nonserialized customer assets at the time of shipment or order fulfillment, provided that the corresponding item is set up with the Enable Asset Tracking attribute as either Customer Asset or Full Lifecycle, similar to serialized assets. Likewise, nonserialized products can be returned by the customer via the return and RMA process. This information is also interfaced to Installed Base by the logistics and order management products. If the asset is fully returned it is then terminated; if the asset is partially returned then the corresponding customer asset quantity is decreased from the returned quantity. You can enable tracking of nonserialized products as customer assets in the same manner as for serialized products. Set the item attribute Enable Asset Tracking as either Customer Asset or Full Lifecycle. TIPS AND CONSIDERATIONS ASSET TRACKING ITEM SETUP Note that while setting the nonserialized items as Full Lifecycle tracked is not prevented, it has no effect for this type of product. Unlike serialized product, nonserialized customer assets are exclusively created at the time of product shipment and order fulfillment with no form of prior tracking. This means that setting them as Customer Asset or Full Lifecycle tracked has the same effect. You can set the nonserialized product to Customer Asset tracked. 16

17 ITEM SETUP FOR SALES PRODUCT TYPES Note that for customer asset creation, asset tracking is considered for the following values of the sales product type: Goods Software Customer asset tracking is ignored (customer assets are not created) for the following values: Included Warranty Extended Warranty Service Level Agreement Software Maintenance Preventive Maintenance Installation Training Subscription One-Time Service CAPTURE KEY ASSET INFORMATION DURING OUTBOUND AND INBOUND FULFILLMENT PROCESSES Installed Base integrates seamlessly with Order Management, enabling the capture of key asset information during the outbound and inbound fulfillment processes. During outbound fulfillment, Installed Base now helps you do the following: It identifies and associates a specific asset to a customer location, to which the asset is to be shipped or fulfilled. It initiates the creation of any included warranties for assets in Enterprise Contracts. It tracks the initial price for which the asset was sold as this information is now captured along with the bill-to-customer information. It captures information about the asset structure at the point when it is sold. During inbound fulfillment, Installed Base captures information about returns, such as: It identifies which assets are being returned It identifies whether an asset is being returned permanently, for credit, or for repair If the asset is returned for credit or permanently, Installed Base properly disassociates the asset from the customer, and initiates the termination of any associated warranties or contracts in Enterprise Contracts. Integration of Installed Base with Order Management now enables you to track assets that have been sold and shipped to a customer, and assets that have been returned, so you always have the most current and accurate information about your customer s assets. Installed Base tracks the bill-to customer information associated with the asset, as well as the asset s initial sales price. Details of an asset s component structure are now captured and maintained throughout the life of the asset. This provides insight into the as-sold and as built configuration of your customer s assets. As changes are made to an asset s structure throughout its life, such as component changes, Installed Base captures and tracks these changes. This flexibility provides you with a comprehensive and granular perspective on asset information about your customer s assets throughout the life of the asset. FEATURE DETAILS With this release, Installed Base integration with Order Management allows you to capture additional asset information, as compared to the previous release where Installed Base was integrated only with Logistics. The additional asset information is captured in the following forms: 17

18 Asset bill-to-customer information and sold by business unit Asset charges As-sold asset structure and matching of this structure with the as-built asset structure Intangible assets The following diagram explains the Installed Base and Order Management integration process in a simplified manner: Installed Base and Order Management Integration CAPTURE AND CREATION OF CUSTOMER ASSET STRUCTURES The following table provides definitions for what is captured in the customer asset structures: Term Definition As-built structure Asset structure as captured during manufacturing of the asset-tracked components used in an assembly; it applies only to serial-tracked manufacturing. As-sold structure It is the combination of the as-built structure with the structure information as received from order management. This information consists of the assemble-toorder (ATO) or the pick-to-order (PTO) models, the configured item for ATO and the options classes. The as-sold structure also encompasses the results of the asset explosion process. Asset Explosion The asset explosion is a supplemental process taking place at the time of Order Management integration. If the shipped or fulfilled asset does not have an as-sold or as-built structure, the application first checks if the item has a primary asset structure in the issuing organization. If such structure exists then a flat asset structure is created with any items in the structure setup with the attribute asset tracking equal to Customer Asset or Full Lifecycle. 18

19 The following is an example of an asset structure encompassing as-sold and as-built information: Asset Structure Product Item Structure Type Item Asset Tracking Value Asset Structure Level A1 ATO Model 1 Model Full lifecycle As-sold --A2 ATO Model 1**123 Configured Item Neutral As-sold ----A3 Option Class 1 Option Class Neutral As-sold A4 Included Item 1 Standard Full lifecycle As-sold A8 Included Item Component 1 Standard Full lifecycle As-built The as-sold customer asset structure is created at the time of Order Management integration in the following manner: 1. Customer assets and their associated structures are created from Order Management information (assold structure) 2. The as-sold information is then matched with the as-built information, and asset-tracked components are added to the customer asset structure 3. For any assets not having a structure created by the two first steps, the asset explosion is attempted The following table summarizes the various behaviors of asset creation depending on product type and item setup: Product Type Behavior ATO If the ATO product or model is Customer Asset or Full Lifecycle tracked then the product or model and the configured item respectively, is created as a customer asset. For a configured product, the option classes are considered as tracked if the model is tracked, and customer assets are created. Selected option items are created as customer assets if they are Customer Asset or Full Lifecycle tracked. PTO and kits If the PTO model or kit is Customer Asset or Full Lifecycle tracked then the product or model respectively, is created as a customer asset. For PTO models, the option classes are considered as tracked if the model is tracked, and customer assets are created. Selected included items are created as customer assets if they are Customer Asset or Full Lifecycle tracked. Serialized manufacturing products If the item is Customer Asset or Full Lifecycle tracked then the item is created as a customer asset. As-built asset structure is created as customer asset if they are Customer Asset or Full Lifecycle tracked. 19

20 This also applies to the ATO option items and kit or PTO included items. Nonserialized products, serialized products without serialized manufacturing, and intangible products If the item is Customer Asset or Full Lifecycle tracked then the item is created as a customer asset. The resulting asset is subjected to the asset explosion process. This also applies to the ATO option items and kit or PTO included items. You can now enable tracking of item components to be tracked as customer assets by setting the tem attribute Enable Asset Tracking as either Customer Asset or Full Lifecycle. CREATE AND UPDATE CUSTOMER ASSETS USING ENHANCED INSTALLED BASE WEB SERVICES Installed base information can originate from, be updated by, or used by a variety of sources and systems. To allow for this flexibility, Installed Base provides an external REST web service, enabling any system to easily search for, create, and update asset information. In addition to serialized assets, this web service has been enhanced to also support nonserialized and intangible assets. It supports asset structure information and its configuration information, enabling you to obtain and update asset structure details, including changes to the asset such as component changes, ensuring Installed Base always has the most current and accurate asset information. FEATURE DETAILS The Customer Asset REST API has been enhanced to support the following: Allows creation and update of nonserialized assets Allows creation and update of customer asset structure CREATING AND UPDATING NONSERIALIZED CUSTOMER ASSETS Installed Base now allows you to associate a nonserialized item to an asset to be created and for which you can also provide the quantity details. Going forward, these assets can be updated in the same manner like any other assets. CREATING AND UPDATING CUSTOMER ASSET STRUCTURES Installed Base now allows you to create and update a customer asset's structure via the Customer Asset REST API. This is achieved by exposing a new Asset Structure resource in the web service. The following methods must be used to achieve the desired asset structure: By using the POST method, you can add an asset as a child of a given asset By using the DELETE method, you can remove a relationship from the asset By using the GET method, you can obtain the list of assets that are components of a given asset Note that with this release, it cannot be verified if the asset structure is valid in the perspective of which item can be a child of another item. No steps are required to enable this feature. 20

21 ROLE INFORMATION Privilege Name and Code Job Role Name and Code Manage Customer Assets by Service Asset Administrator CSI_MANAGE_CUSTOMER_ASSETS_BY_SERVICE ORA_CSE_ASSET_ADMINISTRATOR UPLOAD DATA USING SPREADSHEETS Installed Base provides you with the option to upload data using spreadsheets. Not only is this feature helpful when initially uploading asset information during implementation, it is also useful for ongoing updates, such as those necessitated by mergers, acquisitions, and reorganizations. In addition to serialized assets, this import process has been enhanced to now support the import and update of nonserialized and intangible assets, as well as the import of asset structure and configuration information. This ensures that Installed Base remains your single source of truth for asset information. FEATURE DETAILS The customer asset import capability has been enhanced to support the following: Allows you to create and update nonserialized assets Allows you to create and update customer asset structure CREATING AND UPDATING NONSERIALIZED CUSTOMER ASSETS Installed Base now allows you to associate a nonserialized item to an asset to be imported as well as providing the asset quantity. Going forward, these assets can be updated in the same manner as any other assets. CREATING AND UPDATING CUSTOMER ASSET STRUCTURES Installed Base now allows you to create and update a customer asset's structure via the Customer Asset Import capability. This is achieved by exposing a structure action code (add and remove), and a parent asset identifier part of the.xlsm import template. By using the add structure action code, you can make the imported asset a child of the designated parent. By using the remove structure action code, you can remove the imported asset from its designated parent. NOTE: With this release, it cannot be verified if the structure is valid in the perspective of which item can be a child of another item. No steps are required to enable this feature. ROLE INFORMATION Privilege Name and Code Job Role Name and Code Import Customer Assets Asset Administrator CSI_IMPORT_CUSTOMER_ASSETS ORA_CSE_ASSET_ADMINISTRATOR 21

22 INTEGRATE CUSTOMER ASSET INFORMATION WITH THIRD PARTY APPLICATIONS USING BUSINESS EVENTS Installed Base now has business events, which enable you to easily integrate your customer asset information with third party applications. Business events are raised whenever a customer asset or its structure is created or updated in Installed Base. The third party applications interact with these business events to perform the appropriate actions. FEATURE DETAILS Installed Base now raises public business events whenever the customer asset repository is updated: Whenever a customer asset is created or updated. Whenever a customer asset structure is created or updated, that is, whenever a component is added or removed from the asset structure. The events are raised based on the following sources of modification of an asset: Creation or update of assets via the asset import Creation or update of assets via the Customer Asset REST API Creation or update of assets via any of these integration: Creation of customer assets via sales order shipment fulfillment Update of customer assets via returns Direct asset returns via inventory receipt The events start as soon as the customer asset is created. This occurs typically when an instance of a product is shipped or fulfilled. The events stop as soon as the product instance cease to be a customer asset, for example if a product is returned for credit it is not considered a customer asset anymore. ASSET BUSINESS EVENTS Two business events can be raised for the asset level changes which have been described in the following table: Event Code Description Business event raised when a customer asset is created. The event payload contains key asset information such as asset identifier, product information, and customer information. CUSTOMER_ASSET_CREATE The application interacting with the event can retrieve all asset information by using the GET method of the Customer asset REST API. Business event raised when a customer asset is updated. The event payload contains key asset information such as asset identifier, CUSTOMER_ASSET_UPDATE product information, and customer information, including old and new values for some of the main attributes. In both cases, the application interacting with the events can retrieve all asset information by using the GET method of the Customer Asset REST API. 22

23 ASSET STRUCTURE BUSINESS EVENTS Two business events can be raised for the asset structure changes which have been described in the following table: Event Code Description CUSTOMER_ASSET_RELATIONSHIP_ADD Business event raised when a customer asset is added as a component of another asset. The event payload contains the key information of new relationships created, such as the child and parent asset identifiers. Business event raised when a customer asset is removed from a structure of another asset. The CUSTOMER_ASSET_RELATIONSHIP_REMOVE event payload contains the key information of new relationships created, such as the child and parent asset identifiers. In both cases, the application interacting with the events can retrieve all the immediate components of the parent asset by using the GET method of the Customer Asset REST API. No steps are required to enable this feature. Business events are systematically generated upon asset or asset structures changes, and third party applications must subscribe to the events for integration purposes. UPDATE 17B REVISION HISTORY This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table: Date 21 APR 2017 Feature Notes Created initial document. OVERVIEW This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you. 23

24 SECURITY & NEW FEATURES If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of. Appendix A provides a listing of the security attributes needed to employ the new features when you have decided to implement them. GIVE US FEEDBACK We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com OPTIONAL UPTAKE OF NEW FEATURES (OPT IN) This release of Oracle Maintenance Cloud does not include any opt-in features. UPDATE TASKS This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don t forget to check back and get the latest information before your update starts. RELEASE FEATURE SUMMARY Action Required to Enable Feature Feature Automatically Available End User Action Required Administrator Action Required Oracle Service Request Required Maintenance Cloud Maintenance Define Maintenance Master Data Create and Use Maintenance Organizations Quickly Set Up Common Components and Facilities Define and Manage Assets Create Assets Procure Assets Build Assets 24

25 Import Assets Define Asset Parts List Work Execution Use the Maintenance Work Area Landing Page Execute Work Orders Use Simplified Reporting for Maintenance Tasks Outside Processing Manage and Execute Supplier Operations Create and Manage Purchasing Documents Monitor and Review Supplier Operation Details Additional Maintenance Management Enhancements Visually Design Maintenance Work Definitions Manage Maintenance Work Orders Report Maintenance Work Order Costs Comprehensively Select and Access Favorites in Maintenance Collaborate with Stakeholders on Work Definitions and Work Orders Using Oracle Social Network Oracle Installed Base Streamline Asset Creation and Return Process Integrate with Oracle Enterprise Contracts Cloud Integrate with Oracle Maintenance Cloud Use Web Services to Manage Data Upload Data Using Spreadsheets APPENDIX A: FUNCTION SECURITY PRIVILEGES AND AGGREGATE PRIVILEGES MAINTENANCE CLOUD An integrated asset management system is fundamental for organizations that are heavily dependent upon physical assets in the manufacture or delivery of their products. Asset-intensive firms of all sizes, locations, and industries face unprecedented challenges in today s changing global economy. With shrinking margins and decline in capital spending, firms need to operate their assets with greater efficiency, uptime, and 25

26 effectiveness. Plant managers are asked to do more with less with current resources; Oracle Maintenance Cloud will help you address these challenges in a dynamic global economy. MAINTENANCE Oracle Maintenance Cloud provides a comprehensive ability to define and maintain assets across the enterprise using maintenance processes that are consistent and repeatable. Maintenance is part of a suite of applications that includes other Oracle Cloud solutions, such as Procurement, Inventory and Cost Management, Product Lifecycle Management, and Financials. A simplified setup helps you quickly set up supply chain common components, as well as basic features for maintenance, inventory management, and cost management. DEFINE MAINTENANCE MASTER DATA Work order execution and data capture provides the basis to evaluate the effectiveness of your maintenance strategy. The execution relies on a series of processes including: determining work priorities, management of the daily schedule, reviewing the dispatch list, data capture of labor and material, and work order completion. The actual transactions recorded during the work order execution process are then costed (see the Report Work Order Costs Comprehensively feature in this document). This financial information helps you determine which assets are the most costly to maintain and which assets you might want to consider replacing as opposed to repairing. CREATE AND USE MAINTENANCE ORGANIZATIONS To avoid the challenges of master data duplication and synchronization common to add-on maintenance solutions, Maintenance extends the existing Oracle Cloud Enterprise Resource Planning and Supply Chain Management data model to support additional maintenance-specific master data. Your maintenance manager can now easily define, view, and update the maintenance organization data and its relationships in the following areas: Maintenance organization. Define an organization where you can specify maintenance setup data, run maintenance processes, and support maintenance, repair, and overhaul (MRO) materials. Configure organization parameters that determine the behavior of work definitions, work orders, and work execution. Use an organization calendar to schedule maintenance resources. Maintenance calendar. Define a maintenance calendar that includes work days, shifts, and exceptions. Work areas. Define work areas that represent locations in the organization, where multiple work centers comprise each work area. Work centers. Define each work center, such as a department or maintenance location, where maintenance operations are performed. Each work center is comprised of maintenance resources that provide capacity and availability. Maintenance resources. Define common equipment and labor resources that your organization uses in maintenance. Define resource calendar exceptions, such as training, according to day or shift. Define and view resource rates in Oracle Cost Management Cloud. Standard operations. Create a predefined library of standardized maintenance operations and their resources and usages, so you can add them to work definitions and work orders. Automatically publish subsequent changes that occur to a standard operation to the work definitions that reference it. No steps are required to enable this feature. 26

27 TIPS AND CONSIDERATIONS For a clear segregation of parts, materials and resources, it is recommended to define the maintenance organization separate from the manufacturing organization. However technically there is no restriction to use the same organization for both. QUICKLY SET UP COMMON COMPONENTS AND FACILITIES In order to simplify and to guide you towards recommended best practices, an automated setup flow assists you with the setup process, reuses existing setups, asks important questions and, for some tasks, provides default values for setups according to recommended practices. You can: Set up your calendar. Set up shifts, workday patterns, and schedules. Set up units of measure. Set up unit of measure classes, units of measure, and conversions. Set up inventory organizations and maintenance organizations. Set up master item organization and inventory organizations or maintenance plants, and set inventory organization and maintenance plant parameters. Automatically predefine required receiving, inventory, and shipping tasks for your organization: Manage inventory configuration. Manage subinventories, locator structure, inventory transaction reasons, material statuses, ABC classes, ABC classification sets, ABC assignment groups, and pick slip grouping rules. Manage receiving configuration. Manage receiving parameters. Manage shipping configuration. Manage rules that release pick waves and release sequence rules. Automatically default required setups for maintenance plants by creating default maintenance organization data. Create default work area, work center, labor, and equipment resources. The following screenshot illustrates the pages you use to define a maintenance organization: Manage Inventory Organization Parameter Page with the Option to Define a Maintenance Organization For details about setting up Maintenance, see Oracle SCM Cloud: Implementing Manufacturing and Supply Chain Materials Management, available on the Oracle Help Center 27

28 DEFINE AND MANAGE ASSETS You can create maintainable assets in Maintenance by way of four distinct flows: On the Manage Assets page, you can create a new asset. Through an acquisition process using the procurement flow, you can purchase an asset and track its lifecycle from purchase to receipt through implementation, maintenance, and eventual disposal. Using Oracle Manufacturing Cloud, you can build your own asset, then track and maintain it though Maintenance. If you are converting from another maintenance system or have collected your asset information in a spreadsheet, you can import assets. The Manage Assets page is the starting point for most asset-related activities. This page allows you to quickly and easily create and retrieve asset and component information using enhanced search (including key word search, autosuggest, filters, and a combination of autosuggest or keyword search and filters), and to see the details of location. These functions are available using a mobile device, tablet, or desktop. Maintenance enables faster on-boarding of new assets and timely asset information for all assets spanning the complete maintenance lifecycle. CREATE ASSETS In order to manage and maintain your assets, you need to be able to create them in the system. You access the create assets capability from the Manage Assets page. Asset creation includes uniquely identifying the asset, defining its relationship to an item, defining the asset s location, and providing default parameters for work order execution. The attributes for the create asset feature include the following: Number. Asset number is alphanumeric and unique across the organization. If not specified, the asset number is automatically generated. This field is mandatory. Description. Description of the asset. This field is optional. Item. Item is defined in the Product Information Management work area and associated with an asset. This field is mandatory. Item Serial Number. Item serial number is alphanumeric, is unique in combination with asset item, and is unique within an organization and across organizations. This field is optional. Asset Location. The work center or subinventory location associated with the asset. This field is optional. Work Center. The work center location associated with an asset. This association does not have any influence on work orders. This field is optional. Default Maintenance Work Order Type. Work order type default value assigned when creating a maintenance work order. This field is optional. Default Maintenance Work Order Subtype. Maintenance work order subtype default value assigned when creating a maintenance work order. This attribute is one of the Source Parameters in the subledger accounting for asset maintenance. Oracle Cost Management Cloud derives work order accounts based on this attribute. This field is optional. The following screenshots illustrate the pages that you can use to create assets manually either from scratch or through copy of an existing asset: 28

29 Create Asset Dialog to Create an Asset From Scratch or as a Copy of Another Asset To track an item instance as an asset, the associated item in the Product Information Management work area needs to be defined as Full Lifecycle Tracking. If you want to track it as a maintainable asset, make sure the associated item in the Product Information Management work area is defined as Maintainable. PROCURE ASSETS There are times when you will need to procure a new asset, whether to replace an aging asset or as a critical spare. Using Oracle Procurement Cloud, you can purchase an item that has been defined in the Product Information Management work area as inventory-tracked, Full Lifecycle Tracking, and Maintainable. After receiving the item, an asset is automatically created, and the maintenance manager can update the record in the Manage Assets page to identify it as a Maintainable Asset. To track an item instance as an asset, the associated item in the Product Information Management work area needs to be defined as Full Lifecycle Tracking. If you want to track it as a maintainable asset, make sure the associated item in the Product Information Management work area is defined as Maintainable. BUILD ASSETS In some industries, operations build the assets used in production. This may be because the assets are unique to your business or hard to procure. In Oracle Manufacturing Cloud, you can manufacture an asset by defining 29