#SEU15 What s New in Teamcenter integration for Solid Edge (seec) Realize innovation.
Agenda Teamcenter Solid Edge Compatibility Schedule Strategic Priorities What s New Page 2
Teamcenter and Solid Edge Compatibility Schedule This matrix can change regularly As of Oct 19, 2015 ST6 (EoL) MP14, Apr 2015 ST7 MP10 ST8 ST9 Spring 2016 Tc 8.3 N N N N Tc 9.1 9.1.3 9.1.3 9.1.3 N Tc 10.1 10.1.3 10.1.4 10.1.4\AW24 10.1.5\AW30 P 10.1.5\AW31* Tc 11.2 N N ST8MP2 11.2.1\AW30 P 11.2.1\AW31* Page 3 * AW31 minimum releases are 10.1.5 and 11.2.1 (AW31 is full featured with 10.1.6 and 11.2.2)
Strategic Priorities Reliability/Performance Structure Editor Solid Edge diagnostics Finish what we started MultiField Keys (MFK) Naming Rules Item Number to Find Number integration Teamcenter Clients New Open in Solid Edge command. Rich client (RAC) Standalone Active Workspace client Page 4
Reliability/Performance Structure Editor Performance Open Align with Solid Edge Open improvements. Save As All (complete clone) Revise All Set Actions Assign All Validation Perform Actions (execution) Page 6
Reliability/Performance Open with Where Used This pertains to an assembly file open in Solid Edge If where used is run to find a draft file then open is selected If the draft file only references the open assembly then the BOM is not expanded increasing performance Note: The draft is opened with the same Revision Rule as the currently open 3D file. If there are other 3D files referenced they will expand using the same Revision Rule. Page 7
Reliability/Performance (Cont d) Solid Edge Diagnostics BOM Validation New preference, SEEC_Diagnostics_BOMValidation Scope = User Default is off (0) Set to 1 to enable this feature. These registry keys have been deprecated. SEEC_VALIDATE_BOM_AFTER_CHECKIN SEEC_VALIDATE_BOM_AFTER_CHECKOUT BOM Duplicate Occurrence IDs New preference, SEEC_Diagnostics_BOMDuplicateIDs Scope = User Default is off (0) Set to 2 to enable repair (1 to enable just logging). Page 8
Reliability/Performance (Cont d) Solid Edge Diagnostics (cont d) Fix-up missing GRM links Draft in same Item Revision as Model (SE Interpart Draft Link) Word\Excel\Image in same Item Revision (SE External Link) New diagnostics logfile $logs\seecdiagnostics_<stamp>.csv Includes following logging information. Missing files (i.e. broken links) BOM mismatch BOM duplicate Teamcenter virtual components BOM duplicate occurrence IDs BOMline quantity per occurrence mismatch Microsoft Excel Worksheet Page 9
Reliability/Performance (Cont d) Solid Edge Save Mapped Properties In many customer deployments, we see the number of mapped properties owned by Teamcenter to be as high as 70%. Those properties come to Solid Edge as read-only. SEEC changes how these are handled as follows. Properties not validated (type, string length, range, etc). Properties are not included in Save transaction (sent to Teamcenter). The preference SEEC_Property_Sync_PDM_Master continues to manage the reverse property synchronization immediately after create or update transaction and before file is uploaded to the Volume. Page 10
Reliability/Performance (Cont d) Open Draft change in behavior. When BOM synchronization is enabled and Structure is out of date, the user receives a message and the draft opens with inactive drawing views. This behavior was changed in Solid Edge ST8. The user received a message. They are informed, the Structure is candidate for BOM synch. After the message box, the drawing opens as requested (active). The drawing views only know what was loaded last. If the assembly was previously up to date, the drawing view may not show model out of date. The responsibility transitions to the customer. They must have a process that updates the structure(s) and then updates their drawing views. Page 11
MultiField Keys (MFK) MFK is supported in all applications Solid Edge / SEEC Structure Editor AtT and AtTi Solid Edge Standard Parts Use BMIDE to define the set of key property(ies). Solid Edge implementation is specific to Item types. Teamcenter supports modification of key property values. Solid Edge does not support changing key property values. Consistent with Item ID support. Page 12
MultiField Keys (Cont d) Create new Item using a Type whose uniqueness is more than Item ID User selects Type Key properties are denoted by a gold asterisk (required and key property) If there are no MFK types, we continue to use red asterisk (like Tc91) Do not map key property values. Page 13
MultiField Keys (Cont d) Tip configure meaningful Display Names Couple details to help set perspective Item has to be globally unique (uniqueness is defined @ Item level) Browsing a list of Items, you want to be able to distinguish the difference. When Solid Edge loads a file, it is from a Dataset that is attached to Item Revisions. We present information about that Item Revision! This is not unique to Solid Edge. You will see the same in RAC. Task for your Teamcenter Administrator Item Display Name Include the property(ies) that make the Item unique. Properties are at the Item level! Item Revision Display Name Use a compound property to bring that Item property to Revision Construct a Display Name that includes that uniqueness data! Page 14
MultiField Keys (Cont d) Usability Solid Edge uses these Display Names File -> Open uses Display Names Use Details=Full to show Item Revision Dataset Column 0 shows the Display Names Cache Assistant includes a column for Item Display Name Document Name Formula (PathFinder) Default = [Object] This is the Item Revision Display Name This is consistent with Teamcenter Rich Client Structure Manager Page 15
Naming Rules Add to Teamcenter Define pattern for automatic assignment of an Item ID. Define pattern for automatic assignment of Revision. Deployment must consider this during Data Prep. Solid Edge and Structure Editor Naming Rule - applied to Item ID Naming Rule - applied to Revision (better to use Revision Naming Rule) Naming Rule - applied to Item Name Revision Naming Rule - Revision specific implementation Generation, Validation, and Read-Only behavior mostly consistent with RAC If Item type has single Pattern, do not show the Pattern column on CPD. Page 16
Naming Rules (Cont d) Standard Parts support Naming Rules Specify an Item Type with Naming Rule Patterns Specify pattern to be used when generating components Revision Pattern is for Naming Rule, not Revision Naming Rule Page 17
Item Number Find No Integration Overall project goals: Documentation methodology begins with a dummy assembly where the subassembly to be documented is placed in context of its surrounding design data. The drawing includes a parts list with Item Numbers from that specific subassembly. Integration completed the following enhancements. Added ownership (Teamcenter or Both) Item Number synchronization remains 1-level Added new Item Number Status & Synchronize cmds Current behavior: Assembly BVR integration Draft enhanced Parts List Parts List from Selected Subassembly Page 18
Parts List from Selected Subassembly Create a Parts List from a subassembly anywhere in a top level assembly. Parts List Command Ribbon From Selected Subassembly Button Displays the Select Assembly Dialog Preview and Highlight Selection Page 19
Parts List from Selected Subassembly (contd.) Create a Parts List from a subassembly anywhere in a top level assembly. Select your Saved Settings for the new Parts List Place the Parts List Items of selected subassembly Item numbers of selected subassembly Item balloon only selected subassembly Page 20
New Preference for non-modeled Items (TcVCs) Item Revision with no Solid Edge 3D Dataset To date, these Item Revisions were always added to the Solid Edge assembly as virtual components (i.e. Teamcenter VCs - TcVCs). This functionality was not controlled by Structure Synchronization (SEEC_BOM_Synch) SEEC_Synchronize_VirtualComponents Scope = Role Default = TRUE (1) Important If Item Number Find Number synchronization is enabled and ownership is set equal to Both, if your structures include Item Revisions with no Solid Edge 3D Datasets, you should enable this option so Solid Edge knows what Item Numbers have been assigned to these Item Revisions. Page 21
Teamcenter Rich Client Enhancements Open in Solid Edge Page 22
Teamcenter Rich Client Enhancements (Cont d) My Teamcenter Open in Solid Edge use cases Browse to an Item, Revision or Solid Edge Dataset and open in Solid Edge. Find an Item or Revision and open in Solid Edge. Create a new Item and open in Solid Edge. Classification Open in Solid Edge use case. Browse Classification and open a classified Item Revision in Solid Edge. Minimum software release: Teamcenter 10.1.4.2 Page 23
Teamcenter Rich Client Enhancements (Cont d) My Teamcenter: Start/Open in Solid Edge Search for Item ID Select Item Revision Select Start/Open in Solid Edge command from toolbar. Page 24
Teamcenter Rich Client Enhancements (Cont d) Assembly is opened in Solid Edge Page 25
Teamcenter Rich Client Enhancements (Cont d) Installation and Configuration: Solid Edge integration (SEEC Admin) delivers new Preference, SEEC_TcClient_Enable_Open_Cmd Scope = Site (Group, Role, User) Default = TRUE (1) Preference enables new Option (Edit -> Options ) Default is On (checked), which enables the Toolbar and File menu. Page 26
Standalone Active Workspace Client Open in Solid Edge command Page 27
Contact Gary Lindsay Solid Edge Product Manager Document Management Mainstream Engineering 675 Discovery Drive Huntsville, AL 35806 E-mail: gary.lindsay@siemens.com Realize innovation. Page 28