© Copyright Intelligrated. Engineering Drawing Solution January 26, 2007 Carole Landgrebe Gary...

© Copyright Intelligrated.

Engineering Drawing Solution

January 26, 2007

Carole Landgrebe

Gary Giuliano


Intelligrated Products

Leading provider of conveyor systems for distribution centers


Statement of Problem

Engineering drawing revisions had no relationship to Oracle revisionUse of Oracle revision was not consistentOne drawing can reference many item numbersMaking sure the shop floor and vendors had the

appropriate revision of drawing was a nightmareElectronic filing structure was inconsistentIssue was putting ISO certification at riskEngineers were spending lots of time chasing down

drawings


CAD Files

SolidWorks is used for 3D modeling

SolidWorks files are huge and contain proprietary data

Vendors need one of several different file formats depending on their internal processes, mainly DWG or PDF


High Level Solution

Macro in SolidWorks to automate revision and creation of DWG and PDF versions

Marry the drawing revision to the Oracle item revision

PDF file attached to item revision, made accessible on BOM, Work Order, PO, Sales Order

Extension done to PLM Change Order so that when a drawing is revised, all of the relevant items are added automatically

Only do PLM Change Order when drawing is revised; BOM component changes still done via ‘old’ ECO process

Audits to keep it all in synch


Filing Structure Standardized

Filename standardized as 123456-R01.pdf or 123456-R01-S1of1.dwg where drawing number = 123456 and revision = R01

Intellignas0

Standards

PDF’s

History

DWG’s

History


SolidWorks Save Macro

Revision number can only be saved in one place

File name automatically created with standard format in each of the required file formats

Prior revisions in all formats are automatically moved to History folders


Synchronize Revisions

All drawing and Oracle item revisions had to be synchronized up to the highest number

Had to re-number all Oracle revisions because original implementation was a single numeric character, but field is VARCHAR, so you run into trouble when you hit 10

We standardized on a 3 character revision of format R00, R01, etc


Item Revision Attachments

Enabled attachment at the revision level, so that full history of the drawing can be maintained

Attached to files on our network so as not to pull those all into our database

Stored on organization item for manufacturing org

Stored by revision_id, because that is what PLM uses, but that is not fully implemented in all the apps, so had to use some advanced attachments functionality where revision_id is not stored, such as PO Line

Propagated visibility of the drawing to BOM, Work Order, PO, etc using standard functionality


Change Order in PLM

PLM Change Orders have standard functionality for managing changes to attachments

Use of extended attributes to incorporate Drawing Number and Revision

Use of custom function to automatically add all revision lines related to that drawing

Made process as quick and painless as possible for the engineers


Audits and Other Safeguards

Forms Personalization to disallow update of the revision from the Item Master or Engineering ECO forms – the only way to update a revision is through this new process

Audit process to look at filename as stored on network and compare to related Oracle revision to ensure revision levels are the same

Audit process to verify the presence of drawings on certain item types


Screenshots


Next Steps

Transition rest of ECO’s from Engineering to PLM

Rollout Product Workbench

Convert Excel Shop Issue Log to PLM Issue Log

Automatically attach PDF’s of drawings to E-mail PO’s

© Copyright Intelligrated. Engineering Drawing Solution January 26, 2007 Carole Landgrebe Gary...

Documents

Transcript of © Copyright Intelligrated. Engineering Drawing Solution January 26, 2007 Carole Landgrebe Gary...