#seu12 - 509 best practices for working with the solid edge embedded client - gary lindsay

#SEU12

Best Practices for Working with the Solid Edge Embedded Client Gary LindsaySiemensSolid Edge Product ManagerDocument Management

© Siemens AG 2012. All Rights Reserved.Siemens PLM Software#SEU12

Speaker Bio:

Background: I am the document management product manager for Solid Edge. My

areas of responsibility include Revision Manager, Insight, Insight XT integration for Solid Edge, Teamcenter Integration for Solid Edge (SEEC) and View and Markup. I began my professional career with McDonnell Douglas as Structural Dynamic and Loads Engineering working on F/A-18 and other defense-related projects before joining an SDRC reseller. I joined EDS as a Solid Edge Applications Engineer before joining the Solid Edge Product Planning team in 2005.

Areas of Expertise: Managing your Product data Teamcenter Microsoft Windows Server


Executive Summary:

Today’s Topics: This session explores the new capabilities in the Teamcenter Integration

for Solid Edge (SEEC) and provides valuable tips and best practices in the areas of implementation and daily use.

Key Takeaways: What Teamcenter releases does Solid Edge ST5 support. How you can use Teamcenter to successfully manage your Solid Edge

design data and improve the efficiency of your design-through-manufacturing processes.


Agenda

Teamcenter Integration for Solid Edge (SEEC) The Solid Edge Embedded Client Software compatibility matrix Updating SEEC foundation template

SEEC - Teamcenter preferences Teamcenter preferences impacting SEEC

Using Solid Edge in a Teamcenter managed environment What’s New in SEEC for Solid Edge ST5 Solid Edge ST3 & ST4 - Delivered

Q&A


Solid Edge Embedded ClientSeamless integration of Solid Edge with cPDM

Solid Edge Embedded Client (SEEC) enables Solid Edge users to integrate their design data and processes into the collaborative product data management environments provided by Teamcenter and Teamcenter Express resulting in: Wide access to a single source of product data for

improved reuse and less errors Improved efficiency of design-through-

manufacturing processes Improved collaboration between departments and

with suppliers and customers

Tightly integrates Solid Edge data and processes into a collaborative product data management environment


Solid Edge Embedded ClientKey features

Secure vaulting of Solid Edge documents with access control

PDM capability is built into all Solid Edge commands that retrieve files.

Search PDM database directly from Solid Edge Preview graphics of Solid Edge parts and

assemblies Assembly Pathfinder displays PDM status of

referenced parts. Integrated revision and release management Structure Editor to configure new assemblies

and clone and revise existing assemblies Synchronized releases with Solid Edge Single supplier for CAD and PDM


Solid Edge Embedded ClientSynchronized Releases

Full CAD/PDM compatibility with each Solid Edge release The latest Solid Edge technologies are

incorporated into the Solid Edge Embedded Client Teamcenter and Solid Edge are tested as

a “matched set” Solid Edge Embedded Client releases

are an integral part of Solid Edge software delivery

Single supplier for CAD & PDM ensures synchronized releases and comprehensive integration

© Siemens AG 2012. All Rights Reserved.Siemens PLM Software

Teamcenter Release CompatibilityJune 2012

Solid Edge Teamcenter Express Teamcenter 8(unified)

Teamcenter 9(unified)

SE/ST5 5.3.1.1*, 9.1*1 8.1.2.3*8.3.3.2*

9.1.0.1, 9.1.1.1*1

* Recommended1 Teamcenter 9.1 introduces native 64-bit application (32-bit and 64-bit Teamcenter Server support on Windows)

Solid Edge with synchronous technology 5

SE/ST5 does not support: - Teamcenter 9.0- Teamcenter 8.2- Teamcenter 2007.2- Teamcenter 2007.1- Teamcenter Engineering- And all TcX versions based

on the above

SE/ST5:Last release supporting: - Teamcenter 8.1- Teamcenter 8.3- And all TcX versions based

on the aboveWould not support: - Teamcenter 10.0

As of Jun 13, 2012

Compatibility subject to change


Updating SEEC Foundation Template

SEEC Foundation Template is included with SEEC Administrator …\SEEC Overlay Template\<Teamcenter Release> Solid Edge ST5 introduces new schema (prerequisite to using ST5) Use Teamcenter Environment Manager (TEM) to deploy the update Could also impact those who have built templates with a dependency on SEEC

Overlay Template (strongly discouraged)

Required action for Teamcenter Express v5.3 customers TcX v5.3 customers must update to the SEEC Overlay Template TEM provides the mechanism to update deployed Templates SEEC Administrator ST5 delivers the SEEC Overlay Template Use the Template: Teamcenter 8.3 This is consistent with the process Teamcenter customers use when they

move to a new Solid Edge release


Using Solid Edge in a Teamcenter Managed Environment

What’s new in SEEC for Solid Edge ST5 “The little things” Display Names Meta Model Compliant Item ID Naming Rules Revision Naming Rules Teamcenter Classic Variants


What’s New - The “little” things

Other ST5 Enhancements How to improve Solid Edge “login” performance Solid Edge Startup Screen Solid Edge Options - Manage Additional Assembly PathFinder shortcut commands Revisions…, New -> goes directly to CPD - Revise Document Family of Part enhancements Teamcenter 9.1 enhancements


How to Improve “Login” Performance

Performance - Additional Teamcenter preferences were added for all the Datasets Solid Edge interacts with.

SEEC_ItemTypeList_<Dataset Name> (15) Teamcenter preferences in total (7) Solid Edge Datasets (8) Other Datasets (new in ST5) MSExcel, MSExcelX, MSWord, MSWordX, DirectModel, Image, PDF, UGMASTER Default Value = All Good for uneducated implementers (it just works) Bad for performance (retrieve more than what is required!)


How to Improve “Login” Performance (Cont’d)

Use these to define the list of Item Types for each Dataset Type Use Item Type real names There is no inheritance


Solid Edge Startup Screen

The Solid Edge startup screen provides another visual queue - Is Teamcenter managed mode enabled?

Teamcenter Mode ‐ On

Teamcenter Mode ‐ Off


Solid Edge Options - Manage

The Manage tab options are now specific the current managed environment (Insight, Insight XT, Teamcenter) Document Name Formula was moved to Helpers tab Manage tab is not displayed if the license doesn’t enable managed env.


Assembly PathFinder Commands

When working with Managed assemblies, you can now perform document management functions on multiple indirect documents.

Select multiple documents, RMB > Manage > Upload RMB > Manage > Check In

Added more Managed commands Undo Check Out All Upload All Check In All


Workflow Improvement - Revise

Revisions…, New -> goes directly to CPD - Revise Document Select New from Revisions dialog

Select Revision (showing new functionality - support for Revision Naming Rule)


Family of Part (FOP)

When populating Family of Parts you enter all the required property data for each listed Part and then all those documents are saved to Teamcenter. FOP master and populated members are up-to-date Close master immediately after populate - Undo Check Out


Teamcenter 9.1Teamcenter Client Model Cache

Teamcenter 9.1 introduces a client model cache Teamcenter SOA manages this new option automatically and enables it when

the Teamcenter release is at least Tc9 This new cache can improve performance when Solid Edge requests certain

data model (i.e. schema) information. Teamcenter manages client cache (create and update)

New Solid Edge option

New SEAdmin option


Teamcenter 9.1Teamcenter Communication Services (TcCS)

Teamcenter 9.1 introduces TcCS Teamcenter Communication Services (TcCS) provide a new integration

interface for accessing Teamcenter services (web tier and FSC) via forward and reverse proxies (restricted to 4-tier). TcCS provides centralized configuration for defining web tier, SSO URLs and

proxy configurations. Integrated into Teamcenter SOA. SEEC integrated UI into Define Teamcenter Databases application. When configured, Teamcenter manages UserID/Password challenge TcCS feature worth noting - Kerberos/Applet Free Configure option to suppresses

UserID/Password challenge.

ST5 support for Kerberos.wmv



What’s new in SEEC for Solid Edge ST5 “The little things”

Display Names

Meta Model Compliant Item ID Naming Rules Revision Naming Rules Teamcenter Classic Variants


Teamcenter - Display Names

Teamcenter introduced requirement to prefix all new schema beginning in Teamcenter 8.3 Each BMIDE Template owner would have a unique prefix This approach would eliminate two or more Template owners from creating the

same Business Object (BO) (duplication leading to collision) COTS vs. Custom (custom can extend a COTS BO’s definition)

Localization - the ability to define a BO’s Displayable Name Background: Name | Value pair Name has both a real name and a displayable name Value has a real value and can have multiple displayable values


TeamcenterBMIDE - Display Names

Real Name, SE99_3620_1Display Name, PBODesign_1

Localization ‐ Display Names by Locale


TeamcenterBMIDE - Display Names (Cont’d)

Properties on PBO ‐ Real Name, se99_Str_32_01‐ Display Name, STR32_01

Localization ‐ Display Names by Locale


TeamcenterBMIDE - Display Names (Cont’d)

Display Name for Model Elements Supports Localization, as shown in previous slideInstance Display Name (Object) ItemRevision: SE99_3620_1Revision, DisplayName =

$item_id+”/”+$item_revision_id+”;”$sequence_id+”-”+$object_name


Solid Edge - Display Names

Teamcenter 8.3 introduces display names support. For a Name | Value pair Name has both a real name and a displayable name. Value has a real value and can have multiple displayable values

Solid Edge ST5 introduces the following support for display names. Focused on presentation of a BO’s displayable name. Background: Name | Value pair Name has both a real name and a displayable name.


CPD: Display Names - Item Type

CPD presents each Item Type’s displayable name in list.

Teamcenter Rich Client► New > Design…

Solid Edge ‐ CPD ‐ New Document


CPD: Display Names - Item Type (Cont’d)

New Teamcenter preference determines what is written to Item Type custom property. SEEC_Item_Type_DisplayableName 0 - Default - write the real name 1 - write the displayable name Impact for existing customers - changing this preference will require Solid Edge

to synchronize this custom property - impacts performance. New customers should consider setting this preference to write the displayable

name to Solid Edge custom property.

AddtoTeamcenter supports either real or displayable name. Data Prep your unmanaged documents with Item Type’s displayable name and

Solid Edge does lookup to transact on real name.


Display Names - Meta Model & Mapped

In Teamcenter Rich Client, you select the BO and then select to view or edit properties. The resulting presentation shows the property’s displayable name. User selected the context (like the Item or the Item Master) A form renders with Property’s name and associated value

In Solid Edge, the properties of several BO are presented in a single row. This presentation requires some means of identifying the BO the properties are associated with. Introduces prefixes intended to uniquely identify the BO. This presentation is consistent for meta model and mapped properties.


Display Names - Meta Model & Mapped (Cont’d)

Presenting attributes from several BOs Open/Libraries has “Details” CPD shows these on a single row

Presentation: <Parent BO>.<Attribute> Item.<propName> ItemMaster.<propName> ItemForm.<propName> ItemRev. <propName> ItemRevMaster. <propName> ItemRevForm. <propName> Dataset* <propName>

Note: Do not recommend using required attributes on a Relation BO!


Display Names - Open/Libraries

Solid Edge continues to own the display name localization for the fixed list of available properties (everything but mapped).

Mapped properties are presented with a prefix that identifies the Parent followed by the property’s displayable name.



What’s new in SEEC for Solid Edge ST5 “The little things” Display Names

Meta Model Compliant

Item ID Naming Rules Revision Naming Rules Teamcenter Classic Variants


SE/ST4 - Meta Model - Primary Business Objects

Teamcenter 8 introduced primary business object (PBO) and provided the ability to add new attributes and behaviors.

An SE/ST4 project tested workflows using Primary Business Objects (PBO). This project considered the following scope. Add attributes to COTS classes (Item and Item Revision) Create custom classes (Item and Item Revision) and add attributes. Attributes marked as “required” must have a initial value. Did not consider support for Datasets as PBOs!


SE/ST4 - Meta Model - Primary Business Objects

Teamcenter 8 introduced primary business object (PBO) and provided the ability to add new attributes and behaviors.

An SE/ST4 project tested workflows using Primary Business Objects (PBO). This project considered the following scope. Add attributes to COTS classes (Item and Item Revision) Create custom classes (Item and Item Revision) and add attributes.

Attributes marked as “required” must have a initial value.

Did not consider support for Datasets as PBOs!


Solid Edge ST5 - Meta Model Compliant

A meta model compliant application is capable of discovering the properties required to create a set of objects and submits that to create SOA. Item Item Master Custom Form Item Revision ItemRev Master Custom Form SE Draft (Dataset) Custom Form

Note: Do not recommend using required attributes on a Relation BO!


Teamcenter Rich ClientMeta Model - New Design…


Solid Edge ST5Meta Model Integration Approach

When saving a new design to Teamcenter you will see the (8) OOB properties, the required properties (new) and then the mapped properties. There are (3) basic groupings

The implementation accounts for “overlap” of required properties and mapped properties.

out of the box properties meta model properties mapped properties

Conceptual:

Presentation:out of the box properties meta model overlap mapped


Meta Model Compliant (Cont’d)

CPD - New Document Out of the box properties - to the left and off screen (not shown) Columns include: (2) Meta model, (1) Overlap and (1) Mapped

Conceptual:

Presentation:Meta model Meta model & Mapped (Overlap) Mapped



New ANSI Part > Save … CPD - New Document Meta Model defines (2) required properties on IM Form Item property, STR32_04, is “overlapped”



New ANSI Part > Save … CPD - New Document (Cont’d) Meta Model defines (8) required properties on Item Revision



New ANSI Part > Save … CPD - New Document (Cont’d) Attribute mapping defines (4) properties (1 is an overlapped)



Changes to CPD - New Document

‐‐‐ Teamcenter BO.Property Name‐‐‐ Solid Edge Property Name‐‐‐ Description from Mapped Property‐‐‐‐ <Input>



Once the new Item is created, CPD - Upload Document presents only the mandatory and mapped properties. CPD - New Document

CPD - Upload Document

Mandatory Meta Model Overlapped Mapped



Rounded out support for List of Values (LOV) applied to Item Name Exhaustive LOV Suggestive LOV (new) Cascading LOV (new)

Note: We have not considered Item Name with Description (PDA)


Meta Model Compliant Configure SE Draft Dataset with Custom Form

You can extend the properties that describe an “SE Draft” using a Form.

“SE Draft” -> Named Reference

-> Custom Form


Meta Model Compliant Configure SE Draft with Custom Form (Cont’d)

Step 1: Use BMIDE to create your custom Form This custom Form can have required properties Create BMIDE Package and deploy with TEM There is no requirement to define a mapping to a meta model property that is

marked as required (regardless of an initial value).

Step 2: Create the following Teamcenter preference and set its value SEEC_CreateFormType_SE Draft Value: <Form Name>: <Named Reference Relation Name> Example: SE99_Draft_Attr_2:SE_Draft_Attr Scope: Site

When configured, all new Solid Edge Draft Datasets will have Form Save As (or New > Save) Revise


Meta Model Compliant Configure SE Draft with Custom Form (Cont’d)

“SE Draft” -> Named Reference -> Custom Form (Cont’d)



What’s new in SEEC for Solid Edge ST5 “The little things” Display Names Meta Model Compliant

Item ID Naming Rules Revision Naming Rules

Teamcenter Classic Variants


Teamcenter Naming Rules

BMIDE guide:Naming rules define the data entry format for a business object property. Naming rules can be used to name items, item revisions, datasets, forms, projects, and work contexts. A naming rule consists of rule patterns and a counter. After you create a naming rule, you must attach it to the business object property. You can also attach the naming rule to a property on all business objects that use that property.

Preferences guide:Business rule that defines the naming conventions for the string property value in different type objects. Naming rules can be attached to the following properties: Item ID, item revision ID, and name in item types Dataset name, ID, and revision number in dataset types Name form types


Teamcenter Naming Rules (Cont’d)

This project considered the following capabilities Naming Rule - applied to Item ID Naming Rule - applied to Revision (recommend Revision Naming Rule) Naming Rule - applied to Item Name Revision Naming Rule - Revision specific implementation

Naming rules use the following Pattern - Naming rules are considered pattern variables (ex: NNNNN) Counter - Used to define/manage the increment

Impacts Solid Edge - CPD


Naming Rules - Item ID - New

Select Item Type

Select the required pattern

Assign


Naming Rules - Item ID - Save As

Item Type is defined


Assign


Naming Rules - Revision - New

Select Item Type


Assign


Select Item Type

Assign

Type Item Name

Naming Rules - Item Name - New


Revision Naming Rules

A revision naming rule is a business rule that defines the naming convention and sequence for a Revision. Initial Revision (Type, Start and Description) Secondary Revision (Type, Start and Description) Exclude list (I, O, Q, S, X, Z) Honor Teamcenter preference: SEEC_MakeReadOnly_Revision If preference is set to make Revision read-only, list is Exhaustive If preference is set to make Revision writable, list is Suggestive



What’s new in SEEC for Solid Edge ST5 “The little things” Display Names Meta Model Compliant Item ID Naming Rules Revision Naming Rules




You can define options and the corresponding allowed values and attach them to an item, typically the top-level item in the structure. For example, you could define a engine option with allowed values of 1200 and 1600. You then attach a logical expression, referred to as a variant condition, to any occurrences of components that are configurable. The expression refers to the defined options and can be as complex as necessary.


Solid Edge and Variants

Plan your Product variants

Design master assembly in CAD Union of all Product variants No integration with SE/FOAs

Teamcenter Structure Manager Classic Variants Create / apply variants options Create variant rules


Solid Edge - 150% Design

Assembly Master Revision configuration No Variant Rule


Rich Client - Structure Manager - Define Variants

Define variant condition(s) and create variant rules


Solid Edge - Open Variant Assembly

Revision Rule Variant Rule Configuration Zone


Solid Edge - Open Variant Assembly (Cont’d)

10011-001/A, Latest Working, Model, FX


Rich ClientStructure Manager

Solid Edge AssemblyAssembly PathFinder

Solid Edge - Open Variant Assembly (Cont’d)


Solid Edge Draft - Variant Assembly

10011-001/A, Latest Working, Model, FX


Solid Edge Embedded Client: VariantsSummary

Solid Edge ST5Build the 150% design using Structure Synchronization Item Revisions with no Solid Edge

Document MultiCADDefine product variants in TcOpen Variant Assembly Configures to load (performance) Synchronize structure Assembly PathFinder shows only

configured Item RevisionsCreate a product drawings



What’s new in SEEC for Solid Edge ST5 “The little things” Display Names Meta Model Compliant Item ID Naming Rules Revision Naming Rules Teamcenter Classic Variants

Putting it all together with delivered functionality


Putting it all Together

Tailoring the behavior of Solid Edge Solid Edge Options > Manage SE Administrator Teamcenter Preferences

Call to action: See Solid Edge Embedded Client Administrator’s Guide


Putting it all Together (Cont’d)

Design Centric? If you are CAD centric, Solid Edge creates and modifies all managed CAD content Preference SEEC_BOM_Synch = FALSE If you are not exclusively CAD centric, Content is created or modified in Teamcenter Rich Client Solid Edge Assembly is required to update to Structure changes Preference SEEC_BOM_Synch = TRUE If you plan to take advantage of MultiCAD functionality, Preference SEEC_Foreign_Datasets = TRUE

Call to action: Learn about Solid Edge Assembly’s Virtual Components Structure Editor (0D) as a method of creating Product Structure


Putting it all Together (Cont’d)

Integration between Solid Edge Item Number and Teamcenter Find No Review preference SEEC_Synchronize_ItemNumbers Integration is between Solid Edge Assembly and Teamcenter Structure Set preference PS_new_seqno_mode = existing Enable the Solid Edge Draft, Parts List Properties option - Use Assembly generated item numbers


Integrating Solid Edge Item Number withTeamcenter Find No (continued)

Packed

Unpacked

Solid Edge Assembly

Solid Edge Draft

Teamcenter


Solid Edge Support for Multi-CAD Design


Solid Edge support for Multi-CAD Design (continued)

Solid Edge

Foreign CAD

Foreign CAD

Solid Edge


Solid Edge Support for Multi-CAD Design (continued)

Search for Solid Edge Assembly and OpenSynchronize structure changes and check out those ASM(s)


Solid Edge Support for Multi-CAD Design (continued)


Solid Edge Support for Multi-CAD Design

Solid Edge introduces a “Driven Reference.”A driven reference is a document reference who’s geometric definition was defined by a foreign source. A driven reference has the following features: Driven reference is read only (Open, IPA). Driven reference goes through an out-of-date check. If the foreign source

changes, that change will be synchronized on next Open. Driven Reference is uniquely identified in Assembly PathFinder.

Foreign Content


Solid Edge Embedded Client Forum

http://www.siemens.com/gtac

Need your Sold-to ID & WebkeyAccess Code• located in the header of your

License File

#SEU12

Thank You!Questions?

#seu12 - 509 best practices for working with the solid edge embedded client - gary lindsay

Technology

solid edge seec

seecusing solid edge

solid edge applications

solid edge st5 support

solid edge embedded

solid edge design data

solid edge data andprocesses

solid edge single supplier