Solid Edge ST4 Event: Session 223 Best Practices for Working with the Solid Edge Embedded Client by Gary Lindsay

© Siemens AG 2011. All Rights Reserved.

Best practices for working with the Solid Edge

embedded client


Siemens PLM SoftwarePage 2

Solid Edge. Design better.

Speaker Bio:

Background:

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

areas of responsibility include Revision Manager, Insight, Teamcenter

Integration for Solid Edge (SEEC), View and Markup, and JT translation.

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 added in the Solid Edge ST3 and ST4 releases and

provides valuable tips and best practices in the areas of implementation

and daily use.

Key Takeaways:

What Teamcenter releases does Solid Edge ST4 support.

How you can use Teamcenter to successfully manage your Solid Edge

design data and improve the efficiency of your design-through-

manufacturing processes.




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-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 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




What’s New in Solid Edge ST4

Solid Edge ST4 – Teamcenter Software Compatibility matrix

Teamcenter Integration for Solid Edge (SEEC)

Primary Business Objects (PBO)

Teamcenter Security Services (TcSS) -> Single Sign-On (SSO)

Solid Edge Item Number to Teamcenter Find No. Integration

Open STEP, X_T, and IGES (translation)

Multi-CAD Support using JT

Search Performance




Software Compatibility

Solid Edge Teamcenter

Express

Teamcenter 8

(unified)

Teamcenter 9

(unified)

SE/ST4 5.3.1.1*8.1.1.3, 8.1.2.0*

8.3.1.1, 8.3.2.0*

9.0

9.11

* Recommended1 Teamcenter 9.1 would be supported by a Solid Edge ST4 Maintenance Pack (MP# and release date are TBD).

Solid Edge with synchronous technology 4

SE/ST4 does not support:

- Teamcenter 8.2

- Teamcenter 2007.2

- Teamcenter 2007.1

- Teamcenter Engineering

- And all TcX versions based any of the above

See SEEC_Readme.htm Software Compatibility Matrix for latest details.




Solid Edge ST4 – Teamcenter Express V5.3

Special action required for Teamcenter Express customers.

TcX v5.3 customers must update to the SEEC Overlay Template.

TEM provides the mechanism to update deployed Templates.

SEEC Administrator ST4 delivers the SEEC Overlay Template.

Use the Template: Teamcenter 8.3.

Could also impact those who have built templates with a dependency on SEEC

Overlay Template.

Note: This is the first time customers have been required to execute an

independent template update.




Display Teamcenter Item Types

Before ST4 with Teamcenter 8, SOA API was influenced by preference:

TYPE_DISPLAY_RULES_list_types_of_subclasses

If the preference was not modified, only three Item Types were listed on CPD

(item and two secondary business objects).

Before ST4 and with Teamcenter 8, Teamcenter SOA API was influenced by

preference: TYPE_DISPLAY_RULES_list_types_of_subclasses

If the preference was not modified, only three Item Types were listed




Display Teamcenter Item Types (continued)

Solid Edge ST4: No longer have to edit this preference.

Use new SOA API.

SOA API does not depend on any preference.

Use Solid Edge preference to trim list of available Item Types.

Use SEEC_ItemTypeList_* to trim the list because there's now too much.

SEEC_ItemTypeList_SE Part




Using Primary Business Objects

This project tracked testing of Primary Business Objects (PBO) workflows with

Solid Edge, Structure Editor, and Add to Teamcenter (AtT). Teamcenter 8

introduced meta model project. This project enhanced Teamcenter and provides

the ability to add properties to COTS classes. This project considered:

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 default value.




Teamcenter Meta Model – Primary Business Objects

Attributes in Teamcenter have traditionally been attached to a Form class and

not to the Item or Item Revision class directly.

For example, an attribute destined to describe

an Item was attached to the Item Master

Form and not the Item class itself.

The same process was used for an

Item Revision. An attribute destined to

describe an IR was attached to the

Item Revision Master Form.

Forms are not deprecated.

Teamcenter deployments now have an option

to create attributes on the class itself.

Object must be defined as a Primary Business Object.

Item Revision

Item Master Form

Item Revision Master Form

SE Part

SE Draft

DirectModel

Item




Using Primary Business Objects (continued)

Consider the following when defining your attribute mapping:

An Item object is always prefixed by “Item” regardless of class.

An Item Revision object is always prefixed by “ItemRevision” regardless of

class.

As part of the mapping exercise, the Item and ItemRevision mapping

definitions are put into an Item Type specific section.

A mapping definition where the RHS (Teamcenter side of definition) does not

include “keyword” is assumed to be the Dataset itself.

Must capture the Case of the ObJecT NaMes correctly.

Item is not the same as ITEM or item.




Using Primary Business Objects (continued)

Example mapping (Teamcenter 8.3)

If /master is not specified, default is “both”

{ Dataset type="SE Part"

{ Item type=“SE99_My_PBO“

SEItem_P1 : Item.SE99_My_Item_P1 /description=“Item”

SEItemRev_P1 : ItemRevision.SE99_My_IR_P1 /description=“ItemRevision”

SEItemM_P1 : Item.GRM(IMAN_master_form,Item Master).SE99_My_IM_P1

/description="Item Master Form"

SEItemRM_P1 : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).SE99_My_IRM_P1

/description="Item Revision Master Form“

Author : ItemRevision.owning_user.user_name /master=iman /write_once

/description="Owning User Username“

TcStatus : release_status_list.name /master=iman /description="Release Status"

}

}




Using Teamcenter Security Services (TcSS)

This project integrates TcSS into Embedded Client.

Teamcenter Security Services (TcSS) integrates authentication, SSO, and

application-level authorization services across the Teamcenter product suite.

The user experience is a single login to the first Teamcenter application, and

then subsequent applications are automatically authenticated.

For example, when I start Teamcenter Rich Application Client and login, when I

start Solid Edge and go to Open, the system uses credentials from the first

application to login to Teamcenter.

Integrated into Define Teamcenter Databases application.

Note: TcSS is not delivered in Teamcenter Express. This project is not

available to TcX customers.




Using Teamcenter Security Services (continued)

2-tier or 4-tier

SSO definitions are not presented on SEEC Login dialog.

Multiple SSO definitions can be defined.

An SSO definition is “Activated” for it to become Active.

Only one SSO definition can be active. Once active, the SEEC Login is

suppressed.

Teamcenter does not provide an option for the user to input Group/Role. As a

result, they get their default group/role.









This project integrates TcCS into Embedded Client.

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.

Note: Teamcenter 9.0 is the first release supporting Communication

Services.




How to configure RAC with Communication

Services

Teamcenter Communication Services is configured by TEM.




How to configure RAC with Communication

Services (continued)

TEM (continued)




Running Teamcenter Rich Application Client (4-tier)

configured with Communication Services




Using Solid Edge with Teamcenter Communication

Services

Solid Edge reads the configuration and displays results in Define Teamcenter

Databases application.






Define Teamcenter Databases (continued)

Minimum is Teamcenter 9.0 configured environment settings for Client

Communication System.






Define Teamcenter Databases (Cont’d)

Name -> Teamcenter Description

URI -> Teamcenter URL

Tag property values are not synchronized

Teamcenter Security Services

If SSO definition(s) exist, then Security Services are enabled

SSO App ID -> Application ID

SSO Login URL -> Login service URL

You must “Activate” an SSO-enabled definition. Select the checkbox if this

is the Teamcenter installation you plan to use.






Environments for Client Communication System




Integrating Solid Edge Item Number with

Teamcenter Find No

This project integrates Solid Edge Assembly Item Numbers to Teamcenter

Product Structure’s Find No.

The user experience is the Item Numbers defined in Solid Edge are saved to

Teamcenter BOM, and then those same Item Numbers are available to Solid

Edge Draft.

The integration is between Solid Edge Assembly and Teamcenter BOM.

Allows customers to leverage the new functionality delivered in Solid Edge ST3

for Frame and Pipe uniqueness criteria.

Solid Edge Draft Parts List can consume Assembly Item Number, and now the

Solid Edge Parts List and corresponding balloon numbers are equal to

Teamcenter Find No. (formerly Sequence Number).




Solid Edge – Item Numbers

Definition: Item Number

An Item Number is numeric value that is assigned to a specific document

reference. Each unique document reference is assigned a unique numeric

value, and then subsequent placements of a document reference (that is, all

occurrences) assume that specific Item Number.

Solid Edge ST3 introduced new functionality to address special requirements

of Frame and Pipe design. That functionality is exposed as options for Frame

and Pipe uniqueness.

The item numbers are saved with the assembly and are available for

downstream use, for example, in PMI balloons placed on the model and in

ballooned parts lists on an assembly drawing. This ensures that consistent

part numbering is propagated across all applications of the model.





Teamcenter Find No (continued)

Packed

Unpacked

Solid Edge Assembly

Solid Edge Draft

Teamcenter






A new Teamcenter Preference is used to define the Solid Edge Item Number

options, and then these options are applied to each Solid Edge Assembly when it

is either created or opened.

SEEC_Synchronize_ItemNumbers

Preference scope is Site.

Preference is included with SEEC Administrator.

This new functionality is FALSE (0) by default,

Special AtT option






When Solid Edge Item Numbers are enabled, Solid Edge will assign Item

Numbers to newly placed occurrences.

Item Numbers are viewed in Occurrence Property Manager/

SEEC provides a bidirectional synchronization.

Solid Edge accounts for non-modeled occurrences.

Solid Edge ST4 does not provide a means of viewing Item Numbers assigned to

non-modeled Item Revisions and their associated occurrences.

Item Numbers assigned to non-modeled Item Revisions are considered “locked”

or fixed.






Important governing rules:

Item Numbers are supported for “Top level only.”

Any change to the Item Number options results in a “reset.”

Item Numbers assigned to non-modeled Item Revisions are considered

“locked” or fixed. These BOMLines are not included in SE Save.

Solid Edge will not assign an Item Number that is currently assigned to non-

modeled Item Revision.

The reset command will not impact an Item Number that is currently assigned

to a non-modeled revision.

Item Numbers must be unique by document reference. If they are not unique,

Solid Edge will keep the lowest Item Number and assign it to all occurrences of

that reference.






Recommendations:

Teamcenter Preference impacting Find No.

Should consider any USER_EXIT customizations and set the Solid Edge

preference to be consistent with Teamcenter. For example,

/Start=10

/Increment=10




Item Numbers in Assembly

Item numbers for the Solid Edge BOM can now be defined in the assembly.

The Parts List Properties also must be set to “Use assembly generated item

numbers.”




Opening Managed STEP, X_T & IGES (Translation)

This project provides the ability to open managed STEP, IGES, or X_T files and

considers the following workflows:

Translation - Create

Translation - Update or retranslation




Opening Managed STEP, X_T & IGES (continued)

The translation file is selected on File-Open (Create).

The top-most document default is to return to the same Item Revision where

the translation file was selected.

The balance of the translated files are presented to the user in CPD, where

they assign all the necessary attribute information and then save the new

documents to Teamcenter.

The native Solid Edge filenames are updated to match the assigned Item IDs,

and all the links are updated.

The process captures a manifest of input-output.




Opening Managed STEP, X_T & IGES (continued)

The retranslation process happens once the input is updated, and then the

translated file is reopened in Solid Edge.

The translation process happens, and the resulting documents that were

created on the previous translation/save are renamed to the target Item IDs

with link fix-up.

Any new files are presented to the user in CPD, where they assign all the

necessary attribute information and then save the new documents to

Teamcenter.

Retranslation marks all documents as candidates for upload.

Retranslation of indirect documents are targeted at latest revision for upload

IGES does not support retranslation. If the IGES file is updated, the next Open in

Solid Edge is a translation and create.




Benefits of Translation Framework

The Translation project framework enhancements provide a benefit to an adhoc

vendor part workflow.

The Designer downloads a standard part from the internet and then uses

unmanaged Parts Library to place the component in a managed assembly.

When the new component is saved to Teamcenter, the assigned Item ID is

used to rename the Solid Edge component and then link fix-up is done before

the documents are saved to Teamcenter.

Benefit: Risk of filename collision in the cache is reduced by aligning the Item

ID with the filename.

Data Prep and Add to Teamcenter (AtT) remain at the core of the process

that validates unmanaged content and then imports it into Teamcenter.




What is Multi-CAD?

Teamcenter and Multi-CAD

Multi-CAD is the ability to manage the content from multiple CAD systems

and then create a comprehensive product design using content from more

than one CAD authoring system.

The Product is designed in Solid Edge (deliverable).

The Product includes content from another authoring system.

Consider design reuse of a sub-assembly (vehicle’s engine)

That content could be in its primary design phase (concurrency).

That foreign authoring system owns the content.

Solid Edge assembles content as required (by position or constraints).

Solid Edge Draft documents the product as required.




Multi-CAD using JT

Overview: How content is managed

Master model with corresponding JT file

Component Assembly

No JT content in Item Rev.

Specification

Item

Item Revision

Item Master Form


SE Assembly

BOM View

BOM View Revision

Rendering

Specification

Item

Item Revision

Item Master Form


SE SheetMetal

DirectModel

*.jtJTPART




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

Driven Reference

Solid Edge driven references are read-only.

Open or in-place activate (IPA) results in read-only document; Read-Only

Assistant provides messaging.

Save As is provided as a means of creating a new item for edit.




Solid Edge support for Multi-CAD Design (continued)

Solid Edge

Foreign CAD

Foreign CAD

Solid Edge




Solid Edge support for Multi-CAD Design (continued)

Teamcenter provides product structure (BOMView).

Structure is configured per a revision rule.

A BOMLine provides occurrence data that includes position (transform).

Teamcenter supports assembly features (absolute occurrences).

Once the Product structure is configured, query each unique Item Revision for

geometric information.

Use the information from Teamcenter to composite the data in Solid Edge

Assembly. Assembly considers the following:

Native Solid Edge content

Driven references (foreign data that has a geometric representation)

Non-modeled content (no geometric representation exists)




Solid Edge Support for Multi-CAD Design (continued)





Search for Solid Edge Assembly and Open

Synchronize structure changes and check out those ASM(s)









Position the foreign assembly in context of the parent.

The Solid Edge owns the context to locate that foreign content.

Assemble command – use constraint-based technique

Move command – use model in-place or position-based technique

Save the Solid Edge assembly to Teamcenter.

Update the Transform associated with foreign assembly

Create assembly drawing and document product design.

Save drawing to the same Item Revision (with Solid Edge assembly).

Save drawing to a new Item.





Value Proposition:

The foreign data is expected to change. Therefore, the framework needs to

have an ability to track out-of-dateness and when the foreign data changes,

drive that change thru Solid Edge (that is, synchronize product design).

Do all the right things when you open the first time.

Do all the right things when you open the assembly the next time.

Solid Edge option to save Solid Edge content back to Teamcenter

Option is per user (Default: On)

When enabled, when the assembly is saved to Teamcenter, Solid Edge will

create a Solid Edge dataset under the source Item Revision and then upload

the Solid Edge document (marked as a driven reference).









Background

New Teamcenter preference enables this functionality

SEEC_Foreign_Datasets

Enable Teamcenter preference for SEEC BOM synchronization

SEEC_BOM_Synchronize

The framework was built to support the concept of a search order as defined by

the preference.

Search for Solid Edge 3D managed content first

If the configured Item Revision does not include Solid Edge 3D content, then

search for an alternate 3D representation.

Currently, the only alternate is DirectModel (*.jt)

If there is no DirectModel, then it is a non-modeled occurrence





Project considered those Teamcenter integrated CAD systems that generate JT

as part of their Save to Teamcenter.

NX

CATIA

Pro/E

SolidWorks

Inventor

Note: Not all CAD systems and their associated JT translators are equal.

Solid Edge is not tracking out-of-date status between foreign CAD system and

the corresponding DirectModel (JT).





The following are examples where JT adds value:

Open and select JT

Part Copy and select JT

Assemble with JT (Drag-Drop from Parts Library)

Multi-CAD design with JT (from previous slide)




File – Open, Filter for *.jt

SE ST4 displays a JT file saved to a DirectModel dataset

New Files of filter type

The DirectModel is connected to Item Revision by rending relation

The JT file is connected with a Named Reference JTPART




Solid Edge / SEEC creates JT for visualization.

Solid Edge must distinguish between an Item Revision with a Driven

Reference, DirectModel datasets, and an Item Revision with Solid Edge

dataset and its DirectModel dataset.

Prior to SE/ST4, Solid Edge did not offer JT as input.

If file filter = *.jt, then we cannot distinguish between a JT written by another

CAD system from one written by Solid Edge.

If the user selects a JT file from an Item Revision where Solid Edge is

master, Solid Edge will open the native document (dynamic switch).

When driven references are saved to Teamcenter, Solid Edge does not generate

a JT.

Benefits of Driven Reference Framework




Multi-CAD and Teamcenter Parts Library

SE/ST4 Teamcenter Parts Library displays a JT

RMB – File Types…

Default: Off

The DirectModel is connected to Item Revision by rending relation

The JT file is connected with a named reference JTPART

Drag and drop the JT file into Graphics Window -> Place Part




Multi-CAD and Teamcenter Parts Library (continued)

Type = DirectModel (*.jt) is visible.

Select DirectModel

Drag into graphics window




Multi-CAD and Teamcenter Parts Library (continued)





Summary of Preferences and Options

New Teamcenter preference enables this functionality.

SEEC_Foreign_Datasets

Preference scope is site

Preference is included with SEEC Administrator.

This new functionality is FALSE (0) by default.

Solid Edge ST4 supports DirectModel (i.e. JT) only.

Enable Teamcenter preference for SEEC BOM synchronization

SEEC_BOM_Synchronize

New Solid Edge option to save Solid Edge content back to Teamcenter

Option is per user (Default: On)





Known limitations

Solid Edge SEEC requires the structure configures only one Item Revision; no

support for multiple revisions from the same item.

Solid Edge SEEC does not support Foreign CAD’s assembly features (absolute

occurrences).




Solid Edge – NX Interoperability

Before SE ST4

Solid Edge support for NX managed content before SE ST4.

Insert –> Part Copy with Link to maintain associativity.

File -> Open

Filter to *.prt, and select NX document.

This is a translation workflow.

Opening a component resulted in a new file ready to save to Teamcenter.

Opening an assembly resulted in a set of assembly files that needed to be

saved to new items and then a set of part files with part copies to the NX

files, providing associativity at the part level. There was no ability to track

structure updates.





Before SE ST4 (continued)

Solid Edge support for NX-managed content before SE ST4.

This behavior was not changed in ST4. If you use File -> Open and select an

NX managed document, the result will be the same.

Solid Edge process the user’s request to open NX content.

If the Item Revision contains a structure, the structure is configured by the

revision rule.

The resulting configured Item Revisions are queried for UGMASTER

datasets. If there is no UGMASTER, it is considered non-modeled.

The NX content is downloaded to cache and converted to Solid Edge. Then

that result is ready to be uploaded to Teamcenter.

This approach mirrored what happened unmanaged (that is, native)





Before SE ST4 (continued)

Summary

NX content was converted to Solid Edge before it could be reused.

No practical interoperability at assembly level. The process created another

item to manage.

There was no structure synchronization.

The only option for associativity was at component level through IPC.

Presented challenges to Revise and Save As workflows.




Solid Edge ST4 – NX Interoperability

Solid Edge ST4 support for NX-managed content

Leverage JT written by NX when design is saved to Teamcenter

The approach is consistent, regardless of the authoring CAD.

The implementation accounts for structure saved by NX assembly and is

capable of recognizing structure updates.

The implementation consumes JT at component level.

The Insert -> Part Copy workflow continues to be supported in those cases

where geometric value is being added in Solid Edge.

Recommendation: Save Solid Edge document in new item and align with the

master model concept.




Improved Search Performance

Improve Search performance

New Teamcenter Preference – Query limit

When number of results exceeds the query limit, the user is presented with a

message box.

Refactor how Revision Filter was applied to query results




Conclusion:

Solid Edge continues to deliver valuable new functionality on the latest

Teamcenter platform.

Technology

Solid Edge ST4 Event: Session 223 Best Practices for Working with the Solid Edge Embedded Client by Gary Lindsay