New Engineering Client for Agile PLM

<Insert Picture Here>

Oracle Agile PLM MCAD Connectors Release 3.0 New Features Overview

June 2010

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.2

Agenda

• Release Themes• New and Changed Features• Additional Resources


Release Themes

• Fully Web Based• Use Agile web client for all PLM activities like search & browse• All CAD dialogs are browser-based, no thick client

• Improved User Functionality• Improved ease of use through streamlined use cases• Strong emphasis on CAD advanced use cases

• Significantly Increased Performance• Fully based on new Agile 9.3 web services• File and database operations modularized for best performance

PLM Design data is fully upward compatible from MCAD 2.5.x connectors


New and Changed Features

• Web-based User Interface• Streamlined PLM Processes• Multiple Workspaces• Advanced CAD Feature Support



Web-based User Interface

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.

Previous EC Client Framework

Agile PLM

Server

Web ClientPLM OperationsEC Thick Client

CAD and some PLMOperations

CAD SystemAuthoring

CAD Connector

SDK

• Thick EC Client for all CAD operations

• EC Client also required for some PLM operations, like searching for a design to load to CAD

• Since the EC Client provides only a subset of client features, the web client is also required for some operations (viewing redlined BOM, thumbnails, etc.)

Client

Server

6


CAD SystemAuthoring

New Web-based Framework

EC Web DialogsCAD-specificOperations

• Fully web based, no thick client

• No duplication of client functionality

• Single login between web client and EC dialogs

Web ServicesClient

Server

Agile PLM

Server

CAD Connector

Web ClientPLM Operations

7


Web Dialogs Example – “Save”

List ViewList View

Tree ViewTree View

• The Agile “Save” function brings up the web dialog

• CAD model displayed in List and Tree views

8


Web Dialogs Example – “Save”

List ViewList View

Tree ViewTree View

SidebarSidebar

• The left Sidebar is opened for additional functionality for Design and Item details, Workspaces, and Preferences

9


List View and Tree View• The List and Tree views work together, providing much

better navigation and search capability

Tree View• Zoom, Pan, Fit

• Color-coded by status

• Fit to selected object in list (locate object in tree)

• Print tree

List View• Sort by any column

• Search on data in any column

• Select displayed columns

• Select pre-defined views

10


Other Tree View Features

• Tree-based context menu functions

• Both down and up the tree

• Functions include• Set save mode

• Set / cancel check out

• Save As

• Create Parts

• Assign Change

Select here

11


Other List View Features

Standard View SelectorStandard View Selector

Column Display SelectorColumn Display Selector

Search on any column Search on any column

• Base View – standard view

• Item Assignments – shows Parts assigned to Designs

• Reference Details – shows family table and external ref info

• Workspace Details – shows local filename and status

12


Using the Agile Web Client• All PLM search and browse activity is done in the standard Agile web client

• Load is initiated from the Agile web client using Load to CAD

• This sends the selected Design to the Load Preview dialog, and from there to CAD

Load to CAD

Load to CAD is available from:

• Search results (Designs)

• Design objects

• Item Attachments tabs (attached Designs)

Web ClientWeb Client

Web Dialog – Load PreviewWeb Dialog – Load Preview

CADCAD

13



Streamlined PLM Processes


Existing EC Client Process

CAD Workstation Agile

CAD System

Working Directory

FILE

DESIGN

PART

EC Client

CAD Design Structure

Save

AutoVue for Agile

Part BOM

CreateItem/BOM

Two-Step Process

1. Save Designs using “Save” command

2. Publish BOMs using “Create Item/BOM” command

• Time consuming, since the user must enter two separate dialogs to perform the two functions

• Confusing for inexperienced users

15


New Streamlined Process

CAD Workstation Agile

CAD System

FILE

DESIGN

PART

Workspaces

EC Web Dialog

CAD Design Structure

Save

and Publish BOM

AutoVue for Agile

Part BOM

ONE-Step Process

• “Save” command saves Designs and creates or updates associated Parts and BOMs as appropriate

• Configurable preference settings to control publishing behavior

• Much simpler to use

WorkspacesWorkspaces

16


Process Option Preferences

• The Preferences form contains important Process Option settings

• The administrator can “lock” any setting to control specific site processes

Example of a locked settingExample of a locked setting

17


Important Design-Part Process Options

• Three main settings control the behavior of Design and associated Parts

Part Assignment – Controls if parts can be created by the user, or just used if they exist already

18




Save As – If creating Parts is allowed, will they be automatically created at the same time as Designs.

19




Publish to Item – Controls what actions take place during publishing – BOM update, attachment of Designs to Parts, or both

20


Combined Design-Part Creation

“Create New Part” mode“Create New Part” mode “Use Existing Part” mode “Use Existing Part” mode

• Depending the process options that are enabled, the user will have different options for creating Designs and associated Parts

• The Part autonumber is used for the new Part object and also drives the Design numbering

• The filename can be optionally renamed as well

• Search for existing Parts can be performed right from the Number and Description fields

• The existing Part number can be used to drive the Design number and filename

21


Multiple Numbering Options

Design Number

Filename

Design Autonumber + Extension

Part Number + Extension

CAD Property + Extension

Special Drawing Logic

(use 3D Model Number)

Special Design-only Logic

(always use Design number)

File

Don’t Rename file

Rename file

Part Number

Part Autonumber

CAD Property

Use Existing Part

• These tables describe the options available for numbering Designs and Parts, and naming Files, when using the MCAD connectors

• New built-in logic for certain filetypes simplifies the numbering process:• CAD drawings are named equal to their child 3D model, with the appropriate

CAD drawing extension (e.g. P12345.DRW for P12345.PRT)

• Special “Design-only” logic for skeleton files, manufacturing files, etc.

22


Item Assignments View

• The “Item Assignments” view shows all important attributes related to the assigned Parts – similar to the former “Create Item/BOM” dialog

• This view can be used to assign and view the Change object information

23


Item Assignments View

• The “Item Assignments” view shows all important attributes related to the assigned Parts – similar to the former “Create Item/BOM” dialog

• This view can be used to assign and view the Change object information

Can select from multiple pending changes for publishing

24


Combined Design-Part Change Process• Since Design objects cannot be directly on a Change object, they get approved

through their associated Part’s change process

• The Design’s “Revision” attribute is set to correspond to its associated Part’s Revision code, plus an incremental minor revision

• Supplementing the MCAD Connector, this process relies on the Design Update script PX to trigger attribute updates upon workflow status changes

• This script is available as a Sample, see Additional Resources for details

Set by MCAD Connector upon Save

Set by Design Update script upon Release

25



Multiple Workspaces


Using Workspaces

• Workspaces are the local file locations used by the MCAD connectors

• Initially the user will have one workspace called “Default”

• Users may create as many workspaces as needed

• The active workspace can be set prior to operations like “Load” and “Save As”, to control where files go

• CAD files with the same name may exist independently in different workspaces, even at different PLM version levels

• Workspaces are the local file locations used by the MCAD connectors

• Initially the user will have one workspace called “Default”

• Users may create as many workspaces as needed

• The active workspace can be set prior to operations like “Load” and “Save As”, to control where files go

• CAD files with the same name may exist independently in different workspaces, even at different PLM version levels

27


Controlling Workspaces

• A context menu allows you to create, delete, and activate workspaces

• Workspaces can be nested to multiple levels

• The file status for active commands (such as the Load shown here) is automatically updated to reflect the state of the active workspace

• A context menu allows you to create, delete, and activate workspaces

• Workspaces can be nested to multiple levels

• The file status for active commands (such as the Load shown here) is automatically updated to reflect the state of the active workspace

28


Workspace Manager Window

• The Workspace Manager command brings up this Windows-style file browser

• Shows combined local and PLM status

• Performs status checks and PLM actions

• The Workspace Manager command brings up this Windows-style file browser

• Shows combined local and PLM status

• Performs status checks and PLM actions

29


Archiving Workspaces

• The “Zip and Upload Workspace” command will zip up all files in the workspace, and store this zip file in PLM.

• The zip file is saved into a Design object, and the Design is put into the user’s Bookmarks for reference

• The “Zip and Upload Workspace” command will zip up all files in the workspace, and store this zip file in PLM.

• The zip file is saved into a Design object, and the Design is put into the user’s Bookmarks for reference

30



Advanced CAD Feature Support


Pro/E External References

• This release supports a full range of Pro/E External References including:

• Copy Geometry

• Publish Geometry

• Merge / Inheritance

• Shrinkwrap

Reference Details View displays the reference information

Stored in PLM using the Relationships tab to keep distinct from regular CAD structure

32


Loading External References

• In the Load Preview dialog, a checkbox allows the user to select whether or not External Reference files should be loaded

33


Pro/E Interchange Assemblies

• For working with Interchange Assemblies, additional relations for components of interchange ASM's can be created during the "Save" process.

• The “Load” command recognizes these relations and so the complete Pro/E context can be restored

34


Pro/E Find Number Support

• Once Find Numbers are created for the BOM in PLM, they can be used to populate balloon callouts in Pro/E drawings

Find Numbers defined in PLM

35



Additional Resources


Additional Resources

• For the Design Update sample script PX• http://www.oracle.com/technology/sample_code/products/

agile/9.3/index.html

• For more information about Oracle Agile PLM• http://www.oracle.com/applications/agile/agile-product-lifecycle

-management.html

• For more information about Education• http://www.oracle.com/education/index.html

• For Agile PLM Product documentation• http://www.oracle.com/technology/documentation/agile.html

• For the Agile PLM Blog• http://blogs.oracle.com/plm

New Engineering Client for Agile PLM

Technology

Transcript of New Engineering Client for Agile PLM