5 reasons for st integration in catia

8/3/2019 5 Reasons for ST Integration in CATIA

1/11

Product Lifecycle Management

Why TDM for CATIA with SMARTEAM?

(5 reasons)


2/11

Product Lifecycle Managemen

Reasons for SMARTEAM IntegrationAccess Information

Users want to Browse standard parts

Find their own parts

Identify buying parts

Use cheapest alternatives

Parts of a certain material

Use same data frequently

Know where parts are used

Find the drawings fortheir parts

Keep CATIA links

Problem

Such information sometimes is saved in the CATIA attributes,only accessible within CATIA

The only source of FB information is the filename and windowsattributes

But this requires strictly methodology, which is just a source forerrors

Further more, filenames cannot be handled

1

Access information filebased


3/11


Reasons for SMARTEAM IntegrationAccess Information

TDM* approach Right out of CATIA Save personal and general queries

Query by metadata, not on filename

Select the attributes to be shown for the results

Use Where used functionality

Preview functionality

Geometries are linked to their drawings by dependencies, which are takinto account during lifecycle

Manages CATIA links like MML, constraints, application data ...

1


4/11Product Lifecycle Managemen

Reasons for SMARTEAM IntegrationLifecycle

Users want to Define released data

Have reliable configurations

Develop alternatives

Work concurrently

Take technological links intoaccount

Open files exclusively

...

Problem CATIA does not offer versioning mechanisms

Possible approach #1: indexing version in filename CATIA uses absolutpaths to objects (CATPart) > no changes in filenames (with versionindized) are allowed

Without changing filenames, any change becomes active in any context

Approach #2: Versioning with folders: When copying files of assemblies incomplete directories, you will have to create new folders for each newversion

No possibility to releave history of parts

It is difficult to ensure that only one person is modifying a specific part

CATIA links not visible in Explorer

2



Reasons for SMARTEAM IntegrationLifecycle

TDM approach Automatic versioning during Edit operations

Control of filenames and indices

Reliable Configurations, even if single parts have changed Revisions View

Different lifecyclesteps (checked

out, checked in,released, obsolote)allow control ofaccess/functionalrights

Icons indicatingdocument state

Taking techn.Links into

account

2

R f SMARTEAM I i



Reasons for SMARTEAM IntegrationBusiness Processes

Users want to

Share data

Use standardized

processes

Work in teams

Link data to processes

Get off the break of media

Track progress

Problem without PDM

Processes on paper

Manual checklists without tracking functionality

How to identify data impacted by a process?

Speed

Daily work Not flexible

3

R f SMARTEAM I t ti


7/11


Reasons for SMARTEAM IntegrationBusiness Processes

TDM approach (extention) Easy definition of customized processes

Covered by all products (SMARTEAM - Editor, Web

Editor, Community Workspace) Tracking possibility (status, history)

Definition of responsibilites

Automatic transfer of data through the process

3

R f SMARTEAM I t ti


8/11


Reasons for SMARTEAM IntegrationSecurity

Users want to

Share files

Know that their files are secured

...

Problem

Has to be done on windows

level Has to be done manually

Very hard to set right accesspermissions on all the files

(released files checked out files)

In the right way

At the right time

Rights are changingfrequently (release)

4

Security without PDM

Reasons fo SMARTEAM Integ ation


9/11


Reasons for SMARTEAM IntegrationSecurity

TDM approach

Automatic communication with Vault

No direct access, only via SMARTEAM Files sorted automatically, according to

administrators criteria (based on file-type, onlifecycle step)

User maintenance based on object type andlifecycle step

4

Secured IC

Reasons for SMARTEAM Integration


10/11


Reasons for SMARTEAM IntegrationTeamwork

Users want to

Save data in one central system

But anyway make it accessible to all users outsidethe engineering departments

Engineers are only using CAD-files but also Office-documents which underly the same criterias as

CAD-documents (versioning, secure store) ...

Problem

ALL users need to know aboutthe methodology where data is saved

ALL users need the right access rights

Almost no query functionality Do not know what information was shared

5

Teamwork without

Can you send me thBOM and files inlatest revision?

Reasons for SMARTEAM Integration


11/11


Reasons for SMARTEAM IntegrationTeamwork

TDM approach

Web-interface

Office-Integrations

Standard query mechanisms Customizable user interface for casual users

Right access rights by SMARTEAM Web Editor/Navigator

5

5 reasons for st integration in catia

Documents