Product Lifecycle Management

Why TDM for CATIA with SMARTEAM?

(5 reasons)

Reasons for SMARTEAM Integration Access 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 for their parts Keep CATIA links

Access information filebased

Problem
Such information sometimes is saved in the CATIA attributes, only accessible within CATIA The only source of FB information is the filename and windows attributes But this requires strictly methodology, which is just a source for errors Further more, filenames cannot be handled
Product Lifecycle Management

Reasons for SMARTEAM Integration Access 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 take into account during lifecycle Manages CATIA links like MML, constraints, application data ...

Product Lifecycle Management

Reasons for SMARTEAM Integration Lifecycle

Users want to
Define released data Have reliable configurations Develop alternatives Work concurrently Take technological links into account Open files exclusively ...

Problem
CATIA does not offer versioning mechanisms Possible approach #1: indexing version in filename CATIA uses absolut paths to objects (CATPart) > no changes in filenames (with version indized) are allowed Without changing filenames, any change becomes active in any context Approach #2: Versioning with folders: When copying files of assemblies in complete directories, you will have to create new folders for each new version 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

Product Lifecycle Management

Reasons for SMARTEAM Integration Lifecycle

TDM approach
Automatic versioning during Edit operations Control of filenames and indices Reliable Configurations, even if single parts have changed Revisions View Different lifecycle steps (checked out, checked in, released, obsolote) allow control of access/functional rights Icons indicating document state Taking techn. Links into account
Product Lifecycle Management

Reasons for SMARTEAM Integration Business 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
Product Lifecycle Management

Reasons for SMARTEAM Integration Business 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

Product Lifecycle Management

Reasons for SMARTEAM Integration Security

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 access permissions on all the files (released files <> checked out files)
In the right way At the right time

Rights are changing frequently (release)

Security without PDM

Product Lifecycle Management

Reasons for SMARTEAM Integration Security TDM approach

Automatic communication with Vault No direct access, only via SMARTEAM Files sorted automatically, according to administrators criteria (based on file-type, on lifecycle step) User maintenance based on object type and lifecycle step

Secured IC
Product Lifecycle Management

Reasons for SMARTEAM Integration Teamwork

Users want to

Save data in one central system But anyway make it accessible to all users outside the engineering departments Engineers are only using CAD-files but also Officedocuments which underly the same criterias as CAD-documents (versioning, secure store) Can you send me the ... BOM and files in

Problem
ALL users need to know about the methodology where data is saved ALL users need the right access rights Almost no query functionality Do not know what information was shared
Teamwork without

latest revision?

Product Lifecycle Management

Reasons for SMARTEAM Integration Teamwork

TDM approach
Web-interface Office-Integrations Standard query mechanisms Customizable user interface for casual users Right access rights by SMARTEAM Web Editor/ Navigator

Product Lifecycle Management