Adobe Captivate - Oracle



Slide 3 - Oracle Product Lifecycle Management Cloud

[pic]

Slide notes

Hello, my name is Kyle. Welcome to training for Product Development in Oracle Product Lifecycle Management.

In this session, we talk about Item, Change, and Integration Improvements in Product Development.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Agenda

[pic]

Slide notes

For the enhancements covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Then, we’ll walk you through a demonstration.

Next, we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 5 - Enhancements Overview

[pic]

Slide notes

For item management, improvements were made to the item create dialog along with item lifecycle phase alignment. Also, you can now obsolete an item in a structure along with other item structure improvements. Furthermore, item where-used is improved and change requests now show on items. And last of all, there is new item attachment functionality plus a CAD for Cloud integration.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Improvements in Item Create Dialog

[pic]

Slide notes

The item create dialog now displays Extensible Flexfields. All simple required attributes like Char/Number/Date/LOV are supported, and any numeric attributes marked as required with UOM are shown. Also, any value set attributes are marked required are displayed. The following is not yet supported: If any EFF attributes are part of a REJECT rule, then such attributes are shown too, irrespective of marking them required/non-required. And, if any EFF attributes are marked as Data Quality attributes in a class, then such attributes are shown irrespective of marking it as required/non-required.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Improvements in Item Create Dialog

[pic]

Slide notes

The dialog improvements enable the use of mandatory attributes to describe the minimal required item definition, and accelerate item creation in the item create pop-up. For example, when you configure an item class, you can now designate which fields (including extensible flexfields) must be completed in order for the item to be created.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Item Lifecycle Phase

[pic]

Slide notes

The general information tab now shows Lifecycle Phase instead of Lifecycle Code which harmonizes the way the field is displayed across the application.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Item Lifecycle Phase

[pic]

Slide notes

This update provides consistent information for the user and shows lifecycle phase information in user language. For example, when you review the lifecycle phases in a structure and click on one of the items in the structure, the lifecycle phase information now looks the same.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 10 - Obsoleting Item in Structure

[pic]

Slide notes

You can obsolete a child item in a structure, but only if the parent item is already obsoleted or the where-used relation is already ineffective.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 11 - Obsoleting Item in Structure

[pic]

Slide notes

The system now enables the obsoleting of an item while keeping the existing item structure intact. Also, if allows the user to check where the obsoleted item was used. For example, when I make changes to a structure, instead of deleting items and leaving little traceability for the deleted item, I can now obsolete the item so that the structure history is better preserved.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 12 - Further Item Structure Improvements

[pic]

Slide notes

Further item structure improvements include showing item component start and end effective dates, the inclusion of item structure descriptive flexfields in file-based data imports, and validation that an item can be assigned only once in a single level bill of materials.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Further Item Structure Improvements

[pic]

Slide notes

These improvements provide detailed insight as to when an item component will phase in an phase out of a bill of materials. Also, customers can now import specific attributes during data migration. And, the system now assures that items can only be added once, therefore validating unambiguous data. For example, when I place an item in a structure, the system will check to make sure it isn’t already there, and I can see the start and end dates to identify when this item should actually be used within the bill of materials.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Item Where-Used Improvements

[pic]

Slide notes

The Where Used tab now displays additional views: First level, Top level, and All levels. Also, the reference date used to run the where-used query is visible. The Where Used tab is always visible on the item page and you can export the where-used information.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 15 - Item Where-Used Improvements

[pic]

Slide notes

The system provides appropriate where used information to the user with much faster response time. Furthermore, there is now full transparency regarding what reference date is used to run the where used query. For example, when I go to the Where Used tab to find out how many structures use this particular item, I can now select which level I want to see and the date of the view.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Improvements for Manufacturer Parts

[pic]

Slide notes

You can now search for manufacturer part descriptive flexfields (DFFs) and see the DFF data in search results.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Improvements for Manufacturer Parts

[pic]

Slide notes

These improvements enhance manufacturer parts with customer specific attributes and provide efficient searching to identify Manufacturer Parts by customer specific attributes. For example, if you need to create additional fields on Manufacturer Parts, you can do so, and those fields will be available when you search.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 18 - Showing Change Request in Item Page

[pic]

Slide notes

The pending and released changes tab on items now displays change requests and deviation change requests. You can filter for a specific change type through the query by example tool.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 19 - Showing Change Request in Item Page

[pic]

Slide notes

This feature provides full visibility as to which changes are linked to an item and enables easy tracking of the changes that impact an item. For example, if you need to review all changes that may impact your item, you can do so straight from the changes tab without having to search.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 20 - New Item Attachment Functionality

[pic]

Slide notes

By activating the direct edit mode, you can modify the attributes of attachments directly and multiple attachments at one time.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 21 - New Item Attachment Functionality

[pic]

Slide notes

The direct edit features enables a more efficient way to manage item attachments and thus improves user acceptance. For example, if you need to update information about one or more attachments, you can now do so quickly by activating the Direct Edit screen to enable the modification of all applicable fields.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 22 - CAD for Cloud

[pic]

Slide notes

CAD for Cloud integrates an on premise Oracle Design Vault with PLM Cloud, allowing users to relate designs to Product Development items. It also enables users to publish attachments and structures to Product Development.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 23 - CAD for Cloud

[pic]

Slide notes

This integration allows you to include design processes and data in Cloud PLM while keeping CAD data on premise for security and better performance. Also, it uses CAD integrations with Oracle Design Vault to leverage the Design user experience. Furthermore, it provides seamless structure and attachment publishing from on premise Oracle Design Vault to Cloud PLM. For example, with this integration you can create a design in your CAD program, save it to the Oracle Design Vault, and publish a link to Product Development in the Cloud so that you can use the Cloud interface to process change orders and still retain reference links back to the design files stored in the Vault.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 24 - Enhancements Overview

[pic]

Slide notes

Here in the change management section, we will talk about new features such as Save As for change orders, clipboard support for affected objects of change requests, and other enhancements for change orders and change requests. Also, we will look at resolving revision conflicts, the increased number of change order header descriptive flexfields, and showing date and time according to the user’s time zone.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 25 - Save As for Change Order

[pic]

Slide notes

Using Save As you can copy a change order and select the change order type that you want to use. Non-revision type change orders (NRCOs) can be copied as engineering change order types that require revision changes and vice versa. Save As also allows you to copy over affected objects, attachments, and relationships. Be aware that Save As does not copy the descriptive flexfield values, nor does it copy the team members of the change order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 26 - Save As for Change Order

[pic]

Slide notes

The Save As features accelerates the creation of change orders based on existing change orders and allows you to assign a different change class to the new change order. For example, if I am routing a change order through an approval process based on one change order type, I can now copy that change order and assign it to another change order type which may assign different approvers from another department.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 27 - Clipboard Support for Affected Objects of Change Requests

[pic]

Slide notes

Clipboard support for change request affected objects allows you to copy and paste affected objects to and from a change request. It also enables you to use the clipboard to drag and drop items and documents to the affected objects tab.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 28 - Clipboard Support for Affected Objects of Change Requests

[pic]

Slide notes

This extension of the clipboard support to change requests improves usability and user acceptance. It also provides better re-use of information stored in the clipboard. For example, once a change request is approved, you can now go to the affected objects tab, copy the items from the tab, and paste them into an existing change order before it is submitted for approval.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 29 - Other Enhancements to Change Orders/Requests

[pic]

Slide notes

Other enhancements to change orders and change requests include making the description field optional and preventing submit for approval if no approvers are assigned.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 30 - Other Enhancements to Change Orders/Requests

[pic]

Slide notes

These additional enhancements reduce the effort required to create a change order or change request because users no longer have to fill in the description field. Also, it avoids change orders and requests getting stuck because they are missing approvers. For example, if I try to advance a change order to approval status but forget to add an approver, then the system returns an error message informing me to I need to add an approver.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 31 - Resolve Revision Conflicts

[pic]

Slide notes

The Resolve Revision Conflicts feature checks the correctness of old revisions during change order status change, refreshes the old revision of an affected object, and selects the revision which is effective according to the planned effective date of the affected object.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 32 - Resolve Revision Conflicts

[pic]

Slide notes

With this feature, the system now detects revision conflict early to avoid stuck change orders and assists the user in picking the appropriate revision as the old revision. For example, if you have been working on a change order for some time and are ready to advance it for approval, you can now check to make sure that items on your change order have not changed to other revisions based on other change orders. If they have changed, you are given the option for the system to advance the items to their most current revision before proceeding with the approval of your change order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 33 - Increased Number of Change Object Header DFF attributes

[pic]

Slide notes

More attributes have been added to the change object header such as additional character, number, and date attributes.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 34 - Increased Number of Change Object Header DFF attributes

[pic]

Slide notes

Now you can manage more customer specific attributes on change orders and requests. This allows you to move more data over from legacy systems and enables the use of this data to control the change process. For example, you can enable 50 additional character attributes and use them to receive data from an integrated or legacy system and require some of these attributes to be filled before a change order can advance to a specific status.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 35 - Show Date/Time According to User Time Zone

[pic]

Slide notes

Now, the system will show date/time attributes in accordance with your preferred time zone. Make sure that your correct time zone is set in the Preferences > General Preferences > Regional section.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 36 - Show Date/Time According to User Time Zone

[pic]

Slide notes

This enhancement displays accurate and consistent information and helps user avoid confusion with date/time attributes showing in different time zones. For example, when you set the date and time for a Need-by Date, it reflects your time zone for time and date, but when another user views the same attribute it will reflect the same universal time but display it according to that user’s time zone setting.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 37 - Enhancements Overview

[pic]

Slide notes

In this section, we’ll review the enhanced change status events, additional REST web services, and improve SOAP web services.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 38 - Enhanced Change Status Event

[pic]

Slide notes

A status change can now trigger an Oracle Integration Cloud Service event that contains key information about the change order. Furthermore, customers can subscribe to the event, call web services to get additional information about the change order, and based on the status that is being changed to, customers can trigger their own business logic.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 39 - Enhanced Change Status Event

[pic]

Slide notes

These enhancements allow customers to subscribe to events in Oracle Integration Cloud Service and trigger their own business logic based on the status. For example, if I have a down stream system that has an independent process that needs to happen after a change order is approved, I can now configure an event in Oracle Integration Cloud Service that will invoke the process in this down stream system after this change order advances to a scheduled or completed status.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 40 - Additional REST WebServices

[pic]

Slide notes

The new REST web services provide the ability to create, update, and delete change requests, along with managing change request attachments. Also, the web services enable you to manage affected objects on change requests and manage security for both change requests and change orders.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 41 - Additional REST WebServices

[pic]

Slide notes

The additional REST web services automate the definition of change requests and you can calculate required team members with external logic and can assign them automatically. For example, when you create a change request of change order, instead of manually adding users to the security tab, a web service could call out to another program that selects who should be on the security tab based on criteria about the change order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 42 - Improved SOAP WebServices

[pic]

Slide notes

The improved SOAP web services enable you to add and update item extensible flexfield attributes in a change order context, and Find and Get for change object will now return extensible flexfield values corresponding to the selected item revision.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 43 - Additional SOAP WebServices

[pic]

Slide notes

The value for these additions is that the system now allows for adding and updating information programmatically, and enables access to the most accurate item information including extensible flexfields. For example, if you are using web services to construct an action or integration to update items, you can now update extensible flexfields associated with each item as well.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 44 - Enhancements Overview

[pic]

Slide notes

We have enhanced Product Development OTBI to provide Change History Details and Alternate Structures. Change History Details help users to get timely notifications on updates occurring on the Change Order, enabling them to react in real-time. Also, users can now see the Alternate Structures that they have defined in Product Information Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 45 - Change History Details in OTBI

[pic]

Slide notes

The Product Management – Change Order Real Time subject area in Oracle Transactional Business Intelligence is enhanced to include the Change History (or Action Log) details. In addition, two flags have been added to get the chronological last entry in this table and last among the same action types.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 46 - Change History Details in OTBI

[pic]

Slide notes

Change History details provide deeper insight into the current status of the Change Order and can be used to generate a digest of Change Orders that are currently being worked upon along with their last update or action. Besides, this will also support the calculation of cycle time between two entries in the action log. For example, you can gain regular insight into change orders in approval by creating a list of change orders with the concise last update information using OTBI Alerts. Also, you can gain insight into process efficiency by calculating cycle time between two actions for a change order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 66 - Summary of Enhancement Capabilities

[pic]

Slide notes

Here is the summary of the features I have talked about today. Improvements in the Item create dialog show any required attributes in the create item pop-up. Also, the system now shows item lifecycle phase instead of lifecycle code. Furthermore, a user can now obsolete an item while the system keeps the item structure intact. In addition, item structure improvements show the start and end date of item components, prohibit duplicate sequence numbers, and support structure descriptive flexfield import through file based data import. And, item where used improvements show where-used information for the first level, top level, or all levels.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 67 - Summary of Enhancement Capabilities

[pic]

Slide notes

Continuing the feature summary, the CAD for Cloud integration allows you to upload attachment and structure information from on-promise to cloud. Also, improvements for manufacturer parts supports descriptive flexfields in the manufacturer part search. In addition, change requests are now shown in item changes together with change orders, and the new Direct Edit mode enables you to edit the attributes of multiple attachments. Moreover, the Save As feature for change orders allows you to copy change orders including affected objects, attachments, and relationships.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 68 - Summary of Enhancement Capabilities

[pic]

Slide notes

To summarize more features that I talked about today, change requests now have clipboard support providing the ability to copy and paste affected objects to and from change requests. Furthermore, the description attribute is now optional for change objects and the system now checks that an approver is assigned before a change object can be submitted for approval. Also, the system now helps you detect and resolve revision conflicts for the old revision of change order affected objects. And, change order headers now have more descriptive flexfield attributes available, plus, date and time fields convert to the each user’s preferred time zone.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 69 - Summary of Enhancement Capabilities

[pic]

Slide notes

And finally, here is the summary of the remaining features I have talked about today. Enhanced change status events provide the ability to trigger custom specific logic in Integration Cloud Service (ICS) on change order or change request status change. Also, additional REST web services allow you to manage change requests and the security of change orders and change requests. Moreover, enhanced SOAP web services help you manage extensible flexfield (EFF) attributes within the change order context and read EFF attributes according to the item revision. Furthermore, change order and change request history data is accessible through OTBI along with alternate structure data.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 70 - Implementation Advice

[pic]

Slide notes

In this implementation advice section, we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 71 - Feature Impact Guidelines

[pic]

Slide notes

This table depicts key update information for the features covered in this training. All of the features listed here are ready to use and can be accessed through existing shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 72 - Feature Impact Guidelines

[pic]

Slide notes

Continuing key update information, this set of features is also delivered ready to use, and can be accessed through existing shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 73 - Feature Impact Guidelines

[pic]

Slide notes

And like the others, all of the features listed here are ready to use, and can be accessed through existing shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 74 - Feature Impact Guidelines

[pic]

Slide notes

Here, only one of the features is delivered ready to use, but all can be accessed through existing shipped job roles. The actions required to make the remaining features ready to use will be covered later.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 75 - Feature Impact Guidelines

[pic]

Slide notes

Last of all, this table depicts the final set of key update information for the features covered in this training. Only one of the features listed here are ready to use but all can be accessed through existing shipped job roles. The action required to make the remaining one ready to use will be covered later.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 76 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

This table details the impact to your current business flows of features in this training that are delivered ready to use by your end-users. Improvements in the item create dialog will have a small impact because any require EFFs will now show up in the Create Item dialog. The item lifecycle phase enhancement will have a small impact because it changes the screen to read “Lifecycle phase name” instead of “Lifecycle phase code.” In addition, Obsoleting item structure has minimal impact to your business processes, while the other item structure improvements will have a small scale impact because they change the screen so that the start and end date is visible in the item structure and the system now prohibits the create of duplicate sequence numbers in the bill of materials.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 77 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

This table details the additional impact to your current business flows of more features in this training that are delivered ready to use by your end-users. Item where used improvements will have a small impact by changing the user interface to provide additional options. Also, improvements for manufacturer parts will have a small impact by changing the user interface to display descriptive flexfields in the manufacturer parts search. Showing change requests in the item page will also have a small scale impact because change requests are now shown along with change orders on the item changes page. However, the new item attachment functionality will have minimal impact.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 78 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

In this table of features that are delivered ready to use by your end-users, you’ll notice that the impact of the Save As for change orders and clipboard support for change requests is minimal. However, the other enhancements for change orders and change requests have some impact by changing the user interface and validating that an approver is added before a change can be submitted for approval. Also, the resolve revision conflicts feature has a large scale impact because it has complex process-based changes to recalculate the redline information of affected objects based on a new base revision.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 79 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

And finally, this table details the impact to your current business flows of remaining features in this training that are delivered ready to use by your end-users. Showing date and time fields according to the user’s time zone is a small scale change and will impact each user’s view by displaying date and time information according to their default time zone. The impact of change order history in OTBI is minimal.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 80 - Summary of Actions Needed to Use Feature

[pic]

Slide notes

The enablement for Increased Number of Change Header Descriptive Flexfields is achieved by opening Functional Setup Manager, which is the Setup and Maintenance work area, and using the task Manage Change Order and New Item Request Header Descriptive Flexfields to add more flexfields.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 81 - Summary of Actions Needed to Use Features

[pic]

Slide notes

The enablement for REST and SOAP web services is achieved by the system integrator to write programming logic that calls and uses the web services. And, the enablement for enhanced change status events requires the system integrator to leverage Integration Cloud Service (ICS) to listen to the change status event and to use the enriched event data set.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 82 - Enablement Detail for Change Header DFFs

[pic]

Slide notes

To create Change Header descriptive flexfields (DFFs), go the Setup and Maintenance work area and select Product Management. Within the Product Management setup area, click the Change Orders functional area. Click the Manage Change Order and New Item Request Header Descriptive Flexfields link. Click the Edit button and then click the Create icon. Use the Create Segment screen to create the new flexfield. When finished, remember to Deploy the new flexfields.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 83 - Enablement Detail for REST/SOAP Services

[pic]

Slide notes

To use a REST or SOAP web service, you need to include the URL to the server and pass in authentication information. Then proceed to either call or create the desired object.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 84 - Enablement Detail for Change Status Events

[pic]

Slide notes

In order for Integration Cloud Services (ICS) to listen for the Change Status Event, you must first create a new connection in ICS.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 85 - Job Roles

[pic]

Slide notes

This table details the shipped job roles that will access the new capabilities covered in this training. The shipped job roles include Product Manager, Design Manager, Design Engineer, and Supplier Product Design Engineer.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 86 - Business Process Information

[pic]

Slide notes

The business process associated with the new capabilities covered in this training is detailed here.

The high level business process is Manage Product Development with activities Develop Product Documents and Designs, Define Development Items, and Manage Product Changes.

This concludes this presentation, thank you for listening. You can easily pause and rewind any of these slides if you require additional time to take in the detail.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download