• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
#SEU12 - 509   best practices for working with the solid edge embedded client - gary lindsay
 

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

on

  • 1,276 views

Many of our customers are using Teamcenter / Teamcenter Express to successfully manage their Solid Edge data and improve the efficiency of their design-through-manufacturing processes. This session ...

Many of our customers are using Teamcenter / Teamcenter Express to successfully manage their Solid Edge data and improve the efficiency of their design-through-manufacturing processes. This session explores the Solid Edge Embedded Client – the integration between Solid Edge and Teamcenter / Teamcenter Express, and provides valuable tips and best practices in the areas of implementation and daily use. This session also covers the new capabilities in the areas of product structure management and multi-CAD data management.

Statistics

Views

Total Views
1,276
Views on SlideShare
1,275
Embed Views
1

Actions

Likes
0
Downloads
27
Comments
0

1 Embed 1

http://www.docseek.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    #SEU12 - 509   best practices for working with the solid edge embedded client - gary lindsay #SEU12 - 509 best practices for working with the solid edge embedded client - gary lindsay Presentation Transcript

    • Best Practices for Working withthe Solid Edge Embedded ClientGary LindsaySiemensSolid Edge Product ManagerDocument 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • AgendaTeamcenter Integration for Solid Edge (SEEC)  The Solid Edge Embedded Client  Software compatibility matrix  Updating SEEC foundation templateSEEC - Teamcenter preferences  Teamcenter preferences impacting SEECUsing Solid Edge in a Teamcenter managed environment  What’s New in SEEC for Solid Edge ST5  Solid Edge ST3 & ST4 - DeliveredQ&A © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Embedded ClientSeamless integration of Solid Edge with cPDMSolid Edge Embedded Client (SEEC) enablesSolid Edge users to integrate their designdata and processes into the collaborativeproduct data management environmentsprovided by Teamcenter and TeamcenterExpress 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Embedded ClientSynchronized ReleasesFull CAD/PDM compatibility with eachSolid 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. #SEU12 Siemens PLM Software
    • Teamcenter Release CompatibilityJune 2012 As of Jun 13, 2012Solid Edge with synchronous technology 5Solid Edge Teamcenter Express Teamcenter 8 Teamcenter 9 (unified) (unified) 1 8.1.2.3*SE/ST5 5.3.1.1*, 9.1* 9.1.0.1, 9.1.1.1*1 8.3.3.2** Recommended1 Teamcenter 9.1 introduces native 64-bit application (32-bit and 64-bit Teamcenter Server support on Windows) SE/ST5: SE/ST5 does not support: Last release supporting: - Teamcenter 9.0 - Teamcenter 8.1 - Teamcenter 8.2 - Teamcenter 8.3 - Teamcenter 2007.2 - And all TcX versions based - Teamcenter 2007.1 on the above - Teamcenter Engineering Would not support: - And all TcX versions based - Teamcenter 10.0 on the aboveCompatibility subject to change © Siemens AG 2012. All Rights Reserved. Siemens PLM Software
    • Updating SEEC Foundation TemplateSEEC 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • What’s New - The “little” thingsOther 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • How to Improve “Login” PerformancePerformance - Additional Teamcenter preferences were added for all theDatasets 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!) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Startup ScreenThe Solid Edge startup screen provides another visual queue - IsTeamcenter managed mode enabled? Teamcenter Mode ‐ On Teamcenter Mode ‐ Off © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Options - ManageThe Manage tab options are now specific the current managedenvironment (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. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Assembly PathFinder CommandsWhen working with Managed assemblies, you can now perform documentmanagement functions on multiple indirect documents.Select multiple documents, RMB > Manage > Upload RMB > Manage > Check InAdded more Managed commands Undo Check Out All Upload All Check In All © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Workflow Improvement - ReviseRevisions…, New -> goes directly to CPD - Revise Document Select New from Revisions dialog Select Revision (showing new functionality - support for Revision Naming Rule) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Family of Part (FOP)When populating Family of Parts you enter all the required property datafor 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Teamcenter 9.1Teamcenter Client Model CacheTeamcenter 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 optionNew SEAdmin option © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Teamcenter - Display NamesTeamcenter introduced requirement to prefix all new schema beginning inTeamcenter 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • TeamcenterBMIDE - Display Names Real Name,       SE99_3620_1 Display Name,  PBODesign_1 Localization  ‐ Display Names by Locale © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • TeamcenterBMIDE - Display Names (Cont’d) Properties on PBO  ‐ Real Name,       se99_Str_32_01 ‐ Display Name,  STR32_01 Localization  ‐ Display Names by Locale © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge - Display NamesTeamcenter 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 valuesSolid 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. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • CPD: Display Names - Item TypeCPD presents each Item Type’s displayable name in list. Teamcenter Rich Client Solid Edge ‐ CPD ‐ New Document ► New > Design… © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • CPD: Display Names - Item Type (Cont’d)New Teamcenter preference determines what is written to Item Typecustom 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. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Display Names - Meta Model & MappedIn Teamcenter Rich Client, you select the BO and then select to view or editproperties. The resulting presentation shows the property’s displayablename. User selected the context (like the Item or the Item Master) A form renders with Property’s name and associated valueIn Solid Edge, the properties of several BO are presented in a single row.This presentation requires some means of identifying the BO theproperties are associated with. Introduces prefixes intended to uniquely identify the BO. This presentation is consistent for meta model and mapped properties. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Display Names - Meta Model & Mapped (Cont’d)Presenting attributes from several BOs Open/Libraries has “Details” CPD shows these on a single rowPresentation: <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! © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Display Names - Open/LibrariesSolid Edge continues to own the display name localization for the fixed listof available properties (everything but mapped).Mapped properties are presented with a prefix that identifies the Parentfollowed by the property’s displayable name. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • SE/ST4 - Meta Model - Primary Business ObjectsTeamcenter 8 introduced primary business object (PBO) and provided theability 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! © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • SE/ST4 - Meta Model - Primary Business ObjectsTeamcenter 8 introduced primary business object (PBO) and provided theability 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! © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge ST5 - Meta Model CompliantA meta model compliant application is capable of discovering theproperties required to create a set of objects and submits that to createSOA. Item  Item Master  Custom Form Item Revision  ItemRev Master  Custom Form SE Draft (Dataset)  Custom FormNote: Do not recommend using required attributes on a Relation BO! © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Teamcenter Rich ClientMeta Model - New Design… © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge ST5Meta Model Integration ApproachWhen saving a new design to Teamcenter you will see the (8) OOBproperties, the required properties (new) and then the mapped properties. There are (3) basic groupings out of the box properties meta model properties mapped properties The implementation accounts for “overlap” of required properties and mapped properties. Conceptual: Presentation: out of the box properties meta model overlap mapped  © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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) MappedConceptual:Presentation:Meta model Meta model & Mapped (Overlap)              Mapped  © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)New ANSI Part > Save … CPD - New Document Meta Model defines (2) required properties on IM Form Item property, STR32_04, is “overlapped” © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)New ANSI Part > Save … CPD - New Document (Cont’d) Meta Model defines (8) required properties on Item Revision © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)New ANSI Part > Save … CPD - New Document (Cont’d) Attribute mapping defines (4) properties (1 is an overlapped) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)Changes to CPD - New Document ‐‐‐ Teamcenter BO.Property Name ‐‐‐ Solid Edge Property Name ‐‐‐ Description from Mapped Property ‐‐‐‐ <Input> © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)Once the new Item is created, CPD - Upload Document presents only themandatory and mapped properties. CPD - New Document Mandatory              Meta Model              Overlapped               Mapped CPD - Upload Document © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model Compliant (Cont’d)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) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model CompliantConfigure SE Draft Dataset with Custom FormYou can extend the properties that describe an “SE Draft” using a Form. “SE Draft” -> Named Reference -> Custom Form © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model CompliantConfigure 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: SiteWhen configured, all new Solid Edge Draft Datasets will have Form Save As (or New > Save) Revise © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Meta Model CompliantConfigure SE Draft with Custom Form (Cont’d)“SE Draft” -> Named Reference -> Custom Form (Cont’d) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Teamcenter Naming RulesBMIDE 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 implementationNaming rules use the following Pattern - Naming rules are considered pattern variables (ex: NNNNN) Counter - Used to define/manage the incrementImpacts Solid Edge - CPD © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Naming Rules - Item ID - NewSelect Item TypeSelect the required patternAssign © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Naming Rules - Item ID - Save AsItem Type is definedSelect the required patternAssign © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Naming Rules - Revision - NewSelect Item TypeSelect the required patternAssign © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Naming Rules - Item Name - NewSelect Item TypeAssignType Item Name © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Revision Naming RulesA revision naming rule is a business rule that defines the namingconvention 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Teamcenter Classic VariantsYou can define options and the corresponding allowed values andattach them to an item, typically the top-level item in the structure. Forexample, you could define a engine option with allowed values of 1200and 1600. You then attach a logical expression, referred to as a variantcondition, to any occurrences of components that are configurable.The expression refers to the defined options and can be as complex asnecessary. © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge and VariantsPlan your Product variantsDesign master assembly in CAD  Union of all Product variants  No integration with SE/FOAsTeamcenter Structure Manager  Classic Variants  Create / apply variants options  Create variant rules © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge - 150% DesignAssembly Master Revision configuration No Variant Rule © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Rich Client - Structure Manager - Define VariantsDefine variant condition(s) and create variant rules © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge - Open Variant Assembly Revision Rule Variant Rule Configuration Zone © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge - Open Variant Assembly (Cont’d)10011-001/A,Latest Working,Model, FX © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge - Open Variant Assembly (Cont’d)Rich Client Solid Edge AssemblyStructure Manager Assembly PathFinder © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Draft - Variant Assembly10011-001/A,Latest Working,Model, FX © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Embedded Client: VariantsSummarySolid 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Using Solid Edge in aTeamcenter Managed EnvironmentWhat’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 VariantsPutting it all together with delivered functionality © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Putting it all TogetherTailoring the behavior of Solid Edge Solid Edge Options > Manage SE Administrator Teamcenter PreferencesCall to action: See Solid Edge Embedded Client Administrator’s Guide © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 = TRUECall to action: Learn about Solid Edge Assembly’s Virtual ComponentsStructure Editor (0D) as a method of creating Product Structure © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Integrating Solid Edge Item Number withTeamcenter Find No (continued) Solid Edge  Assembly Solid Edge  Draft Unpacked Teamcenter Packed © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Support for Multi-CAD Design © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge support for Multi-CAD Design (continued) Solid Edge Foreign CAD Solid Edge Foreign CAD © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Support for Multi-CAD Design (continued)Search for Solid Edge Assembly and OpenSynchronize structure changes and check out those ASM(s) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Support for Multi-CAD Design (continued) © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Support for Multi-CAD DesignSolid 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 © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Solid Edge Embedded Client Forumhttp://www.siemens.com/gtacNeed your Sold-to ID & WebkeyAccess Code• located in the header of your License File © Siemens AG 2012. All Rights Reserved. #SEU12 Siemens PLM Software
    • Thank You!Questions? #SEU12