A STEP based Business Process “A Case Study” Bill Marler, Pratt & Whitney January 17, 2001 ®...

A STEP based Business Process “A Case Study”

Bill Marler, Pratt & WhitneyJanuary 17, 2001

®PDES, Inc.

PDES, Inc. Copyright PDES, Inc. 2001®

A STEP based business processObjective

The purpose for this talk is to review The purpose for this talk is to review the events of an actual ‘STEP pilot’ the events of an actual ‘STEP pilot’ based upon the given business based upon the given business condition and summarize the ‘good, condition and summarize the ‘good, the bad, and the ugly’ the bad, and the ugly’

My expectation is that the issues and My expectation is that the issues and answers resulting from this pilot answers resulting from this pilot activity will be beneficial for someone activity will be beneficial for someone developing a STEP based business developing a STEP based business procedureprocedure


…..a little background Experience with ‘homegrown’ translators ~1991 AeroSTEP with Boeing ~ 1994PowerSTEP project ~ 1995Turbine pilot with MTU and P&W 1995-99Current PDES, Inc. pilot: Aerospace Engine

AllianceSTEPnet and CAx-Implementors Forum test rallies


A STEP based business process‘The Business Strategy’

Today’s business climate requires international partnering of products to stay competitive in the marketplace

Product Design and Manufacturing is out-sourced to partners worldwide

A conglomeration of ‘systems’ need to talk to each other to ensure product assembly and integrity

The Business Strategy: “Outsource”


A STEP based business process….this is the scenario

A major Aerospace Engine company, JetJockeys, is A major Aerospace Engine company, JetJockeys, is providing Digital Mock-up (DMU) Data and Interface providing Digital Mock-up (DMU) Data and Interface Geometry to an Airframe Company , Flybywire, in the US.Geometry to an Airframe Company , Flybywire, in the US.

The Engine company has partnered with 2 Overseas The Engine company has partnered with 2 Overseas companies Fiazco and LeJette along with another US companies Fiazco and LeJette along with another US company, Fans-r-Us Inc., to share in the Design and company, Fans-r-Us Inc., to share in the Design and Manufacturing of the Propulsion system. Manufacturing of the Propulsion system.

As Integration manager for the Propulsion System, As Integration manager for the Propulsion System, JetJockeys want to manage the Product Data using UG JetJockeys want to manage the Product Data using UG and Iman. Unfortunately, the other partners are on and Iman. Unfortunately, the other partners are on different CAD and PDM systems creating a Data Exchange different CAD and PDM systems creating a Data Exchange dilemma.dilemma.


A STEP based business process…”The Problem”

Multiple CAD and PDM systems involved in the Enterprise

Integration team has to ‘manage and integrate’ the partnered product and provide appropriate DMU (Digital Mock Up) and interface information to the customer


A STEP based business process“The Problem-Graphically”

Outsource design Outsource design and Buildand Build

OutsourceOutsource

OutsourceOutsource


A STEP based business process“CAD impact of globalization”

Company Responsibility CAD Tool PDM Prod.

Flybywire

JetJockeys

JetJockeys

Fiazco

LeJette

Fans-r-Us

Air-framer

Integrator

Externalcomponents

LPT

Fan

High Spool

Catia

Cadds

UG

UG

PTC

Enovia

Windchill

UG

ImanIman

ImanIman

LocationLocation

Taiwan

Islip, NY

St.Louis, MO

Islip, NY

Palermo,IT

Bordeaux,FR


A STEP based business process….“At the Program Level”

A ‘Statement of Work’ is prepared for all members of the enterprise to endorse

The SOW spells out the areas of responsibilities and their products

Program Executives approve the SOWData Exchange (DEX) IPTs for each

alliance member are identifiedand of course an unrealistic ‘schedule’


A STEP based business process

The DEX Planning PhaseThe DEX Planning Phase


A STEP based business processDEX IPTs have face-to-face to...

Identify program DEX requirementsAgree to a STEP-based DEX process that

supports the SOW business planAssign CAD/PDM responsibilitiesIdentify new ‘tools’ that need to be

deployed to meet objectivesDocument the entire ‘to-be process’Dry run: walk the process….


A STEP based business process….the face-to-face realizations

Current STEP success ratio < allowableIntegrated CAD-PDM data not “RFPT” An effective STEP DEX procedure

needs to be put in place at each siteValidation criteria needs workDEX business process to be automatedCurrent STEP functionality insufficient


A STEP based business process…some immediate mitigators

A pilot process is initiated by all to begin de-bugging the to-be DEX process

CAD vendor participation is obtained to address throughput issues

Local IT support is obtainedWeekly conference calls are scheduled and

action lists are maintainedSTEP experts from PDES, Inc. agree to

participate in the pilot


A STEP business processDEX IPT membership structure

DMU process ownerDMU DEX focalInternal Design Process supportInternal IT participationHotline for CAD vendor(s)PDES, Inc. representatives for STEP

support



The DEX Integration and The DEX Integration and Deployment phaseDeployment phase


A STEP based business process...results of pilot teamwork

Comprehensive requirements document

Flybywire/JetJockeys

Working Together

Business Requirement Document

and

Data Exchange Agreement

December 25, 1997

REFERENCE DOCUMENTS .................................................................LEGAL AGREEMENTS........................................................................ACRONYMS & DEFINITIONS ..............................................................1.0 INTRODUCTION .....................................................................1.1 Purpose ..............................................................................1.2 Scope ..............................................................................1.3 Background ..............................................................................2.0 REQUIREMENTS.....................................................................2.1 Concurrent Product Definition.....................................................2.2 Digital Product Definition ...........................................................2.3 Digital Mock-up.........................................................................2.3.1 Maintenance of DMU .................................................................2.3.2 DMU Search Capability..............................................................2.3.3 Interference Checking ................................................................2.3.4 DMU Data Base Synchronization..................................................2.3.4.1 Database to Model File....................................................2.3.4.2 Database to Database ......................................................2.3.5 Coordinate System.....................................................................2.3.6 STEP Standards ........................................................................2.3.6.1 Product Structure ..........................................................2.3.6.2 Configuration Management .............................................2.3.6.3 Coordinate System .........................................................2.3.6.4 Units ............................................................................2.3.6.5 STEP File Size Recommendations .....................................2.3.6.6 STEP Format ................................................................2.3.6.7 Flybywire CATIA Name Mapping2.3.6.8 STEP File Naming Convention .........................................2.3.7 CATIA Standards......................................................................

2.3.7.1.1 JINX Naming Convention .................................................................2.3.7.1.2 Trade Study Model Names ................................................................2.3.7.1.3 Flybywire Naming Convention...........................................................2.3.7.1.4 Flybywire CATIA Name Mapping to JINX .........................................2.3.7.2 Coordinate System ...........................................................................2.3.7.3 Solid Approximation Recommendation...............................................2.3.7.4 Layers.............................................................................................2.3.7.5 Model Size.......................................................................................2.3.7.6 Units...............................................................................................2.4.6 Data Recovery .............................................................................................2.4.7 Disaster Recovery.........................................................................................2.4.8 Data Volumes ..............................................................................................2.4.9 Configuration Control ..................................................................................2.5 Catia Requirements......................................................................................2.5.1 Catia Synchronization...................................................................................3.0 PROCESSES ...............................................................................................3.1 DMU Process...............................................................................................3.1.1 Flybywire DMU Process................................................................................3.4 Synchronization of DMU Data Bases ..............................................................3.4.1 Synchronization of Engine Build Numbers/Effectivities ....................................3.5.1 Problem Resolution Management...................................................................3.5.2 Data Exchange Monitoring ............................................................................3.5.3 Computer Operation Scheduling ....................................................................3.5.5 Data Flow Time ...........................................................................................3.5.6 Data Recovery .............................................................................................3.5.7 Disaster Recovery.........................................................................................

1.0 INTRODUCTIONThis document is a joint agreement between Flybywire and theJetJockey Integration and Translations Company, "JINX", whichdescribes the digital mockups and data exchange processes to beused for the F409.1.1 PurposeThe intent of this document is to record the requirements, andprocesses to be established, in support of the digital productdefinition and data exchange for the JJMEE engine and associatedstructures for the F409-"she's real fine my F409" program..1.2 ScopeThis document is limited in focus to the requirements and procedureswhich must be established between Flybywire and JINX and doesnot address the business or technical issues which may need to beresolved by JINX and JetJockeys. However the material enclosed isrelevant and beneficial to both establishments.The technical material is divided into two main sections: the firstdefines requirements for the F409 design and development. The lastportion, will be developed as documentation for the agreedprocedures.1.3 BackgroundThe design team for the F409 derivative airplanes, will use theconcepts of collaborated Product Definition, Digital Pre-Assembly,and Integrated Product Teams.Although JINX and Flybywire will use functionally equivalentcomputing platforms and techniques to achieve the F409 design, anydifferences could result in unsatisfactory time delays in the exchangeof design data. It is a goal to reduce the typical flow times for thesynchronization of DMU databases to the smallest practical time.The processes agreed to in this document, facilitate that goal.

2.0 REQUIREMENTSThis section contains the basic requirements that regulate the approach used by each company to achieve the mission of the F409-program.2.1 Concurrent Product DefinitionConcurrent product definition is a systematic approach to the integrated, simultaneous design of products and their related processes,including engineering, manufacturing and support. The F409 family will be designed using this principle. All of the approved designand DMU processes have been selected with this goal in mind. It is a requirement that the F409 engine external design participants worktogether to perform concurrent product definition of the F409 family of airplanes.2.2 Digital Product DefinitionThe Flybywire F409 design program team will use Dassault Systemes Catia to develop the digital product definition. The JINX will useUG Solutions Unigraphics to develop the digital product definition. The Standard for the Exchange of Product Models (STEP AP203) isthe preferred process for the exchange of digital mock-up models. Catia will be used as the back-up process.2.3 Digital MockupDigital Mock-up (DMU) is the computer implemented process of solid modeling engine and engine build-up parts and simulating theassembly of these parts. The F409- engine design participants will support the IPT/DMU process by providing solid models in either apre-released or released configuration to the necessary IPT members. Each site will have a DMU administrator function to facilitate theexchange of DMU data between all sites. The JINX DMU management group will integrate the design at each buy-off stage and release,to ensure compliance to the Flybywire/JINX F409 Engine Propulsion Master Phasing Plan (Reference when defined).Designers at all sites will input models into the DMU at the earliest possible opportunity to facilitate rapid communication of designinformation. This is crucial to the DMU process at all four sites.

2.3.1 Maintenance of DMUAll designs must be maintained in DMU after release. Therefore, all post-release changes that affect geometry must beincorporated into the DMU. Also, any change that affects the packaging of DMU models (i.e. how parts are dividedbetween DMU models), must be reflected in the DMU.Maintenance of the digital engine is required through the life cycle of the airplane.

2.3.2 DMU Search CapabilityA volume search capability allows the IPT team members to search the DMU database for parts located in the samearea. Every designer must search the DMU often to assemble parts in their area to support design integration. TheFlybywire PDM system supports a volume search capability. PDM also supports an effectivity search capability.JINX's DMU function must also support these capabilities.

2.3.3 Interference CheckingThis is the ability to check for interference with adjacent parts. The capability to perform interference checking on eachDMU model before it is shared with other design participants is a requirement to support concurrent product definition.Both companies will use a computer system to support this process.

It is imperative that interference checking be performed prior to submitting models for use by other team members.Performing interference checking at the time of release to manufacture is a program wide requirement.

2.3.4 DMU Data Base Synchronization

Synchronization of DMU data between the JINX and Flybywire is a requirement. It is recognized that synchronizationdoes not mean that at any given instant, both sites have exactly the same data. This is the goal, but there is a time lagdue to transmission and processing that makes this goal difficult to attain. Synchronization is therefore defined as beingable to identify discrepancies between sites, analyze the discrepancy, initiate corrective action and provide metricsabout the state of synchronization.


XY

Z

A irp lan e A xis

B W L

BSTA BBL

XY

Z

X

Y

Z

E ngine A xis

N ace lle A xis

E W L

ESTA EBL

N W L

NSTA NBL

N S TA = E S TAN W L = E W LN B L = E B L+100

GE90 Engine, Nacelle and Airplane Coordinate System

Airplane to Engine axis transformation matrix

.030538x .032012y .999021z 811.452704

.994058x .103502y -.033703z -485.751371-.104480x. 994114y -.028661z 31.703752

Engine to Airplane axis transformation matrix

.030538x .994058y -.104480z 461.396940

.032012x .103502y .994114z -7.216880

.99902x -.033703y -.028661z -826.120932


A STEP based business process..results of pilot teamwork

Comprehensive requirements document More effective STEP DEX process

Problem Resolution procedure


A STEP based business processschematic

Flybywire“Catia”

JINX“UG”

Fans-r-usPTC

LeJetteCADDS

JetJockeysUG

FiazcoUG

STEP Exchange

XX

XX NNN

NN

PDES, Inc.PDES, Inc.®


A STEP based business processdetailed schematic

Methods

ProcessOwner

ProcessOwner

LeJette data exchange

focals

Send Data Exchange focal

LibrarySupplier

LeJette JetJockeys

Server

Methods

Suppliersend

Email

Email

Firewalls

JJs

Server

“VPN”environment

EagleSTEPEagleSTEP

PDES, Inc.®


STEP based business process “effective STEP DEX procedure”

Native Model

CreateTarget

File

Do Quality Checks

Create Step File

Check for Errors

Documentation. STEP

Best Practices &model quality

Validate/heal

Notify Sender& Recipient

Archive

Validation OK?

Send STEP file

Contents complete?Contents complete?

Complete Model?

Log file look ok?Log file look ok?

To heal or not to heal..

Target systemcapabilities?

Bspline tolerancesBspline tolerances

Problem Resolution

PDES, Inc.®


A STEP based business process Pilot effectiveness

Low

STEPProblems

High

Time

Production use

70 - 75% Success

TARGET:90 - 95% successful exchanges

Add quality checks

Incorporate Healing

Model Quality Issues

Accuracy issues

Begin pilotBegin pilot



Comprehensive requirements document More effective STEP DEX processProblem Resolution procedure

Integrated and automated business process


A STEP business processProcess Improvements

MPAMPASTEP-in

Target

VisualizationProgram ““Automated Process”Automated Process”

Prepare UG file

Add Attributes

Add CM

Val props

Run EagleSTEP

Check for errors

Archive & FM

Autoname + Send

ftp

Sending System

validatevalidate

PDES, Inc.®


A STEP based business processProcess Improvements


A STEP business processProcess Improvements

MPAMPASTEP-in

Target

VisualizationProgram ““Automated Process”Automated Process”

Prepare UG file

Add Attributes

Add CM

Val props

Run EagleSTEP

Check for errors

Archive & FM

Autoname + Send

ftp

Sending System

validatevalidate

PDES, Inc.®


Effective STEP exchange“Integration Tools”


A STEP based business processProcess Improvements

STEP

SendingCAD System

Receive

STEP UG

Check Log File

Create CM Data Set

Validategeometry

Archive & Library Prep

Notify Owner

CM Template

Library

Meta Data

Send

PDES, Inc.®


A STEP based business process“Integration Tools”



Comprehensive requirements document More effective STEP DEX processProblem Resolution procedureIntegrated and automated business

process

Improved validation technique


INSTANCE VPs

•Upper image highlit part selected for mass property table

•Lower image shows mass properties for:

a) Individual comp.

b)CG to parent asm.


INSTANCE VPs

•Post process CADDS part with GVP

•Display results in DXN or browser



Ongoing improvements...Ongoing improvements...


A STEP business processOngoing Improvements

More robust translators


5 Universal Joints in UG are hollow




5 Universal Joints inCadds are not hollow


Reflective testing:File processes OK




Problem Solids isolatedfor STEP translation

Problem Solids isolatedin UG for translations



Problem Solids in Caddsfile are the “inverse” of

the actual geometry



CATIA STPCAT..reads OK into

catia!!



STEP file fails to read into ProE!!


A STEP business process..after much PRP with PDES, Inc. team

The problem was solved by identifying “how” the vendors processed the information in the STEP files

Some STEP processors handled the two CIRCLEs trimming the SPHERICAL_SURFACE (the 'outer' portion of the bearing) as the two 'tops' of the Sphere; others used the CIRCLEs as the middle of the Sphere

Both methods were “valid” according to STEP, but an agreement between the vendors had to occur to avoid this problem in the future

Updated Recommended Practices for CAD vendor implementation



Translator improvements

Enhanced validation properties


A STEP business process…more STEP functionality

CADDS FILE VPD DATA

L Bracket

L-Bracket S/AInstance 1

Nut/BoltSubAssy

instance 1

Nut/BoltSubAssy

instance 2

Nut/BoltSubAssy

instance 3

NAUO

NAUO

NAUO

NAUO

Bolt

NutNAUO

NAUO

Bolt

NutNAUO

NAUO

Bolt

NutNAUO

NAUO

N-B S/A vpd1x10.0,y7.50,z1.50

N-B S/A vpd1x10.0,y7.50,z1.50

N-B S/A vpd1x10.0,y7.50,z1.50

Rod S/A vpd1x14.59,y20.20,z10.0

Bolt vpd1x0.0,y0.0,z16.94



Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5

L Bracket

L-Bracket S/AInstance 2

Nut/BoltSubAssy

instance 1

Nut/BoltSubAssy

instance 2

Nut/BoltSubAssy

instance 3

NAUO

NAUO

NAUO

NAUO

Bolt

NutNAUO

NAUO

Bolt

NutNAUO

NAUO

Bolt

NutNAUO

NAUO

N-B S/A vpd1x10.0,y7.50,z1.50

N-B S/A vpd1x10.0,y7.50,z1.50

N-B S/A vpd1x10.0,y7.50,z1.50

Rod S/A vpd1x14.59,y20.20,z10.0




Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5



BracketSubAssyinstance 1

Sonbrh Assy vpd1x92.17,y76.59,z18.0

Bracket S/A vpd1x16.72,y-50.0,z17.33

C1 BracketC2 Nut-BoltAssyC3 Nut-BoltAssyC4 Nut-BoltAssy

UG FILE VPD DATA

SonbrhAssembly


Plate Rod SubAssembly

Plate vpd1

x90.0,y75.0,z10.0Rod S/A vpd1

x0.0,y0.0,z100.0

Bracket S/A vpd1

x16.72,y-50.0,z17.33

C1 BracketC2 Nut-BoltAssyC3 Nut-BoltAssyC4 Nut-BoltAssy

NAUO NAUO

NAUO NAUO

NAUO NAUO

Rod

Nut

Nut

Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5

Rod vpd1x0.0,y0.0,z100.0

NAUO

NAUO

NAUO




UG SONBRH ASSY VS CADDS SONBRHASSY VPD DATA

BracketSubAssy

instance 1


UG SonbrhAssembly

BracketSubAssy

instance 2

Plate Rod Sub-Assy

Plate vpd1x90.0,y75.0,z10.0

Rod S/A vpd1x0.0,y0.0,z100.0


NAUO NAUO

NAUO NAUO

BracketSubAssy

instance 1



CADDS SonbrhAssembly

BracketSubAssy

instance 2

Plate Rod Sub-Assy


Rod S/A vpd1x0.0,y0.0,z100.0


NAUO

NAUO

NAUO

NAUO

C of G values do not match




BracketSubAssy

ins tance 1

Sonbrh Assy vpd1x92.1 7,y76.59, z18.0

Bracket S/A vpd1x16.7 2,y-50.0,z17.33

UG SonbrhAssembly

BracketSubAssy

ins tance 2

Plate Ro d Sub -Assy

Plate vpd1x90.0 ,y75.0,z10.0

Ro d S/A vpd1x0.0, y0.0,z100.0


NAUO NAUO

NAUO NAUO

BracketSubAssy

ins tance 1

Sonbrh Assy vpd1x90.0 ,y75.0,z18.86



BracketSubAssyins tance 2

Plate Ro d Sub -Assy

Plate vpd1x90.0 ,y75.0,z10.0

Ro d S/A vpd1x0.0, y0.0,z100.0


NAUO NAUO

NAUO NAUO

C of G values do match







BracketSubAssy

instance 1



UG SonbrhAssembly

BracketSubAssy

instance 2

Plate Rod Sub-Assy


Rod S/A vpd1x0.0,y0.0,z100.0


NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

BracketSubAssy

instance 1




BracketSubAssy

instance 2

Plate Rod Sub-Assy


Rod S/A vpd1x0.0,y0.0,z100.0


NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2








BracketSubAssy

ins tance 1

Sonbrh Assy vpd1x92.17,y76. 59,z18.0

Bracket S/A vpd1x16.72,y-50.0, z17 .33

UG SonbrhAssembly


Plate Rod Sub-Assy

Plate vpd1x90.0,y75.0 ,z10 .0

Rod S/A vpd1x0.0 ,y0.0,z100.0


NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

BracketSubAssy

ins tance 1

Sonbrh Assy vpd1x90.0,y75.0 ,z18 .86




Plate Rod Sub-Assy

Plate vpd1x90.0,y75.0 ,z10 .0

Rod S/A vpd1x0.0 ,y0.0,z100.0


NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

C of G values do not match






C1 BracketC2 Nut- BoltAssyC3 Nut- BoltAssyC4 Nut- BoltAssy

UG FILE VPD DATA

SonbrhAssembly


Plate Rod Sub-Assy

Plate vpd1

x90.0,y75.0,z10.0Rod S/A vpd1

x0.0,y0.0,z100.0

Bracket S/A vpd1

x16.72,y-50.0,z17.33

C1 BracketC2 Nut- BoltAssyC3 Nut- BoltAssyC4 Nut- BoltAssy

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2 Rod

Nut

Nut

Nut vpd1x10.0,y7.5,z1.5

Nut vpd1x10.0,y7.5,z1.5

Rod vpd1x0.0,y0.0,z100.0

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2

NAUO

Shove-it vpd2


Instance Validation Properties

•Upper image highlight part selected for mass property table

•Lower image shows mass properties for:

a) Individual comp.

b) CG to parent asm.


INSTANCE VPs

•Post process CADDS part with GVP

•Display results in DXN or browser

Checking Instance craig11/l-bracket_asmMass Properties Check - INSTANCE

Centroid STCENTROID = 0.158106E+03, 0.370222E+02, -.750000E+02 CALCULATED = 0.158106E+03, 0.370226E+02, -.750000E+02 CADDS Calculated Centroid location is outside tolerance



Translator improvementsEnhanced validation propertiesExpanded STEP functionality



‘Build to Design using 100% Product Data requires more complete STEP file’

Need Parametrics– Lost in STEP exchange

Features/tolerances also missingAnnotation and text also needed

– All required to eliminate drawings and obtain full benefit of STEP in Enterprise

A STEP based business processCAx Implementor Forum

activities

Model SH AC IN MD CT ID PE ST TC TU AL SD UG DB EC HI AI

CAD/PDM integration (External References) no no no no yes yes yes no yes yes no no no yes yes yes Imp.

Retest K1 yes yes no yes yes yes yes yes Imp. Imp. yes yes yes no yes yes no

Recheck Benchmark Model yes yes yes yes yes yes yes yes yes yes Imp yes yes no yes yesImp/ Exp?

New Production Models yes yes yes yes yes yes yes yes yes yes yes yes yes no yes yes yes

3D Text no yes no no yes no yes no yes yes no yes ? no no no no

B-rep, surface and curve (incl. overriding) Colour no yes yes ? yes yes yes yes yes yes no yes yes no yes yes yes

Layers no yes no yes yes yes yes no yes yes yes no yes yes yes yes no

Entity names no yes no yes yes Exp yes no yes yes yes yes yes yes yes no no

Dimensional Tolerance no no no no no no 7J no no yes no no no no ?(Imp) no no

Val Props (according Bills Proposal) no no no ? no Exp yes no yes yes no no no no yes ?(yes) no

Draughting (reuse D3) no no no no no no yes no yes yes no no no yes no Imp. no

CAX Implementors Forum: Who will do what in Round6J V2.0


A STEP business processSummary

“Pilot” activity benefits process development efficiency

Management buy-in is criticalUse PDES, Inc., CAD vendors, and CAx

Implementor Forum to help get improvements in process

Dedicated team and automated STEP process are keys to success

Date post:	14-Dec-2015
Category:	Documents
Upload:	ambrose-shaw
View:	217 times
Download:	4 times

A STEP based Business Process “A Case Study” Bill Marler, Pratt & Whitney January 17, 2001 ®...

Documents