509 Bestpracticesforworkingwiththesolidedgeembeddedclient Garylindsay 120918124520 Phpapp01

Best Practices for Working with the Solid Edge Embedded Client
Gary Lindsay Siemens Solid Edge Product Manager Document Management
#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
#SEU12
Siemens AG 2012. All Rights Reserved. Siemens PLM Software
Executive Summary:
Todays 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-throughmanufacturing processes.
#SEU12
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 Whats New in SEEC for Solid Edge ST5 Solid Edge ST3 & ST4 - Delivered Q&A
#SEU12 Siemens AG 2012. All Rights Reserved. Siemens PLM Software
Solid Edge Embedded Client Seamless 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-throughmanufacturing 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 Client Key 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
#SEU12
Solid Edge Embedded Client Synchronized 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
TeamcenterReleaseCompatibility June2012
Solid Edge with synchronous technology 5
Solid Edge Teamcenter Express
1
As of Jun 13, 2012
Teamcenter 8 (unified) 8.1.2.3* 8.3.3.2*
Teamcenter 9 (unified) 9.1.0.1, 9.1.1.1*1
SE/ST5
5.3.1.1*, 9.1*
* Recommended 1 Teamcenter 9.1 introduces native 64-bit application (32-bit and 64-bit Teamcenter Server support on Windows)
SE/ST5: Last release supporting: - Teamcenter 8.1 - Teamcenter 8.3 - And all TcX versions based on the above Would not support: - Teamcenter 10.0 Compatibility subject to change
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
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
#SEU12
Using Solid Edge in a Teamcenter Managed Environment

Whats 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
#SEU12
Whats 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
#SEU12
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!)
#SEU12
How to Improve Login Performance (Contd)

Use these to define the list of Item Types for each Dataset Type Use Item Type real names There is no inheritance
#SEU12
Solid Edge Startup Screen

The Solid Edge startup screen provides another visual queue - Is Teamcenter managed mode enabled?
TeamcenterMode On
TeamcenterMode Off
#SEU12
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 doesnt enable managed env.
#SEU12
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
#SEU12
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)
#SEU12
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
#SEU12
Teamcenter 9.1 Teamcenter 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
#SEU12
Teamcenter 9.1 Teamcenter 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

#SEU12

#SEU12
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 BOs definition) Localization - the ability to define a BOs 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
#SEU12
Teamcenter BMIDE - Display Names
RealName,SE99_3620_1 DisplayName,PBODesign_1
Localization DisplayNamesbyLocale
#SEU12
Teamcenter BMIDE - Display Names (Contd)
PropertiesonPBO RealName,se99_Str_32_01 DisplayName,STR32_01
Localization DisplayNamesbyLocale
#SEU12
Teamcenter BMIDE - Display Names (Contd)

Display Name for Model Elements Supports Localization, as shown in previous slide Instance Display Name (Object) ItemRevision: SE99_3620_1Revision, DisplayName = $item_id+/+$item_revision_id+;$sequence_id+-+$object_name
#SEU12
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 BOs displayable name. Background: Name | Value pair Name has both a real name and a displayable name.
#SEU12
CPD: Display Names - Item Type

CPD presents each Item Types displayable name in list.
TeamcenterRichClient
New>Design
SolidEdge CPD NewDocument
#SEU12
CPD: Display Names - Item Type (Contd)

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 Types displayable name and Solid Edge does lookup to transact on real name.
#SEU12
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 propertys displayable name. User selected the context (like the Item or the Item Master) A form renders with Propertys 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.
#SEU12
Display Names - Meta Model & Mapped (Contd)

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:Donot recommendusingrequiredattributesonaRelationBO!
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 propertys displayable name.
#SEU12

#SEU12
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!
#SEU12
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!
#SEU12
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:Donot recommendusingrequired attributesonaRelationBO!

Teamcenter Rich Client Meta Model - New Design
#SEU12
Solid Edge ST5 Meta 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
outoftheboxproperties metamodelproperties mappedproperties
The implementation accounts for overlap of required properties and mapped properties.
Conceptual:
Presentation: outoftheboxproperties
metamodel
overlap
mapped
#SEU12
Meta Model Compliant (Contd)

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: Metamodel
Metamodel&Mapped(Overlap)Mapped
#SEU12

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

New ANSI Part > Save CPD - New Document (Contd) Meta Model defines (8) required properties on Item Revision
#SEU12

New ANSI Part > Save CPD - New Document (Contd) Attribute mapping defines (4) properties (1 is an overlapped)
#SEU12

Changes to CPD - New Document
TeamcenterBO.Property Name SolidEdgePropertyName DescriptionfromMappedProperty <Input>


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

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)
#SEU12
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
#SEU12
Meta Model Compliant Configure SE Draft with Custom Form (Contd)

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 (Contd)

SE Draft -> Named Reference -> Custom Form (Contd)
#SEU12

#SEU12
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
#SEU12
Teamcenter Naming Rules (Contd)

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
#SEU12
Naming Rules - Item ID - New

Select Item Type
Select the required pattern
Assign
#SEU12
Naming Rules - Item ID - Save As

Item Type is defined
Assign
#SEU12
Naming Rules - Revision - New

Select Item Type
Assign
#SEU12
Naming Rules - Item Name - New

Select Item Type
Assign
Type Item Name
#SEU12
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
#SEU12

#SEU12
Teamcenter Classic Variants

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.
#SEU12
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
#SEU12
Solid Edge - 150% Design Assembly Master Revision configuration No Variant Rule
#SEU12
Rich Client - Structure Manager - Define Variants

Define variant condition(s) and create variant rules
#SEU12
Solid Edge - Open Variant Assembly
Revision Rule Variant Rule Configuration Zone
#SEU12
Solid Edge - Open Variant Assembly (Contd)

10011-001/A, Latest Working, Model, FX
#SEU12
Solid Edge - Open Variant Assembly (Contd) Rich Client Structure Manager Solid Edge Assembly Assembly PathFinder
#SEU12
Solid Edge Draft - Variant Assembly

10011-001/A, Latest Working, Model, FX
#SEU12
Solid Edge Embedded Client: Variants Summary

Solid Edge ST5 Build the 150% design using Structure Synchronization Item Revisions with no Solid Edge Document MultiCAD Define product variants in Tc Open Variant Assembly Configures to load (performance) Synchronize structure Assembly PathFinder shows only configured Item Revisions Create a product drawings
#SEU12

Whats 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
#SEU12
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 Administrators Guide
#SEU12
Putting it all Together (Contd)

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 Assemblys Virtual Components Structure Editor (0D) as a method of creating Product Structure
#SEU12
Putting it all Together (Contd)

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
#SEU12
Integrating Solid Edge Item Number with Teamcenter Find No (continued)
SolidEdge Assembly
SolidEdge Draft Unpacked
Teamcenter
Packed
#SEU12
Solid Edge Support for Multi-CAD Design
#SEU12
Solid Edge support for Multi-CAD Design (continued)
Solid Edge Foreign CAD
Solid Edge
Foreign CAD
#SEU12
Solid Edge Support for Multi-CAD Design (continued)

Search for Solid Edge Assembly and Open Synchronize structure changes and check out those ASM(s)
#SEU12
Solid Edge Support for Multi-CAD Design (continued)
#SEU12
Solid Edge Support for Multi-CAD Design

Solid Edge introduces a Driven Reference. A driven reference is a document reference whos 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.
ForeignContent
#SEU12
Solid Edge Embedded Client Forum

http://www.siemens.com/gtac Need your Sold-to ID & Webkey Access Code located in the header of your License File
#SEU12
Thank You!
Questions?
#SEU12

509 Bestpracticesforworkingwiththesolidedgeembeddedclient Garylindsay 120918124520 Phpapp01

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

509 Bestpracticesforworkingwiththesolidedgeembeddedclient Garylindsay 120918124520 Phpapp01

Transféré par

Droits d'auteur :

Formats disponibles

Best Practices for Working with the Solid Edge Embedded Client

Gary Lindsay Siemens Solid Edge Product Manager Document Management

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge Embedded Client Key features

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge Embedded Client Synchronized Releases

As of Jun 13, 2012

Teamcenter 8 (unified) 8.1.2.3* 8.3.3.2*

Teamcenter 9 (unified) 9.1.0.1, 9.1.1.1*1

Updating SEEC Foundation Template

Using Solid Edge in a Teamcenter Managed Environment

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Whats New - The little things

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

How to Improve Login Performance

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

How to Improve Login Performance (Contd)

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge Startup Screen

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge Options - Manage

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Assembly PathFinder Commands

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Workflow Improvement - Revise

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Family of Part (FOP)

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Teamcenter 9.1 Teamcenter Client Model Cache

New SEAdmin option

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Teamcenter 9.1 Teamcenter Communication Services (TcCS)

ST5 support for Kerberos.wmv

Using Solid Edge in a Teamcenter Managed Environment

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Teamcenter - Display Names

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Teamcenter BMIDE - Display Names

Teamcenter BMIDE - Display Names (Contd)

PropertiesonPBO RealName,se99_Str_32_01 DisplayName,STR32_01

Teamcenter BMIDE - Display Names (Contd)

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge - Display Names

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

CPD: Display Names - Item Type

SolidEdge CPD NewDocument

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

CPD: Display Names - Item Type (Contd)

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Display Names - Meta Model & Mapped

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Display Names - Meta Model & Mapped (Contd)

Display Names - Open/Libraries

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Using Solid Edge in a Teamcenter Managed Environment

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

SE/ST4 - Meta Model - Primary Business Objects

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

SE/ST4 - Meta Model - Primary Business Objects

Siemens AG 2012. All Rights Reserved. Siemens PLM Software

Solid Edge ST5 - Meta Model Compliant