COE2010 Razorleaf ENOVIA SmarTeam Deployment at AS&E

3,279 views
3,336 views

Published on

AS&E struggled initially with their ENOVIA SmarTeam deployment, but ultimately got the system up and running in production, winning over a number of skeptical users in the process. View this presentation to learn what made the difference for them.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,279
On SlideShare
0
From Embeds
0
Number of Embeds
1,220
Actions
Shares
0
Downloads
47
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Transportation Security Administration Department of Homeland Security North American Treaty Organization US Domestic Nuclear Detection Office US Navy US Air Force US Marine Corps
  • There is something to be learned from how AS&E organizes their team. While there is cross-training within the group, there are specialists for CAD-related software, and for workflow and general document management. The CAD supervisor focuses on how the tools are being used to optimize efficiency.
  • COE2010 Razorleaf ENOVIA SmarTeam Deployment at AS&E

    1. 1. ENOVIA SmarTeam Deployment at AS&E Maureen Murphy - AS&E Jonathan Scott - Razorleaf
    2. 2. Agenda <ul><li>Introductions </li></ul><ul><li>Message </li></ul><ul><li>History of PLM at AS&E </li></ul><ul><li>AS&E’s PLM objectives </li></ul><ul><li>Problems & Solutions </li></ul><ul><li>Future of PLM at AS&E </li></ul><ul><li>Summary </li></ul><ul><li>Q&A </li></ul>
    3. 3. American Science & Engineering <ul><li>400 employees in Billerica, MA + worldwide </li></ul><ul><li>Founded in 1958 </li></ul><ul><li>Specialty: Backscatter X-Ray Equipment </li></ul><ul><li>Fame: SmartCheck </li></ul><ul><li>Customers: </li></ul><ul><ul><li>TSA </li></ul></ul><ul><ul><li>DHS </li></ul></ul><ul><ul><li>NATO </li></ul></ul><ul><ul><li>Confidential </li></ul></ul><ul><ul><li>US Customs </li></ul></ul><ul><ul><li>UK Customs </li></ul></ul><ul><ul><li>US DNDO </li></ul></ul><ul><ul><li>USN </li></ul></ul><ul><ul><li>USAF </li></ul></ul><ul><ul><li>USMC </li></ul></ul>
    4. 4. Backscatter Technology
    5. 5. Backscatter Technology
    6. 6. SmartCheck
    7. 7. SmartCheck
    8. 8. AS&E – Engineering Services Group <ul><li>Maureen Murphy </li></ul><ul><ul><li>Engineering Services Manager </li></ul></ul><ul><ul><li>Deep background in CM </li></ul></ul><ul><li>Bill Abely </li></ul><ul><ul><li>CAD Services Manager </li></ul></ul><ul><ul><li>Focused on methodology & practices for mechanical design </li></ul></ul><ul><li>Raul Rosa </li></ul><ul><ul><li>Principal Business Systems Analyst </li></ul></ul><ul><ul><li>CAD and CAD integration specialist, mechanical design focus </li></ul></ul><ul><li>Laura Murphy </li></ul><ul><ul><li>Business Systems Analyst </li></ul></ul><ul><ul><li>Combined IT/business perspective for non-engineering users </li></ul></ul>
    9. 9. Razorleaf <ul><li>Consulting & Services Provider (not reseller) </li></ul><ul><li>ENOVIA SmarTeam Experts </li></ul><ul><li>North America </li></ul><ul><li>Jonathan Scott </li></ul><ul><ul><li>Mechanical Engineer from Nuclear Industry </li></ul></ul><ul><ul><li>PLM Consultant for ~10 years </li></ul></ul><ul><ul><li>BOM / CM Expert </li></ul></ul><ul><ul><li>Williamsburg, VA </li></ul></ul>
    10. 10. Today’s Message
    11. 11. Message <ul><li>Never a shortage of technical issues </li></ul><ul><li>AS&E’s biggest issues weren’t technical </li></ul><ul><li>Culture change is hard </li></ul>
    12. 12. PLM History at AS&E: pre-2004 CAD PDM ERP 1980’s - - Legacy 1990’s AutoCAD - Fourth Shift Late 1990’s Inventor + AutoCAD network Fourth Shift 1998 SolidWorks network Fourth Shift 2001 SolidWorks PDMWorks Fourth Shift 2004 SolidWorks SmarTeam Fourth Shift
    13. 13. PLM History at AS&E: post-2004 <ul><li>Struggled to deploy ENOVIA SmarTeam (2004-2007) </li></ul><ul><li>ENOVIA SmarTeam in production (2007) </li></ul><ul><li>Replaced Fourth Shift with Oracle Apps (2007-2008) </li></ul><ul><li>Redeployed ENOVIA SmarTeam on PLMDB (2008) </li></ul><ul><li>Light SmarTeam – Oracle integration in place (2008) </li></ul><ul><li>Added Sequence for MES (2008) </li></ul><ul><li>Added 3DVIA Comp. for manufacturing content (2009) </li></ul>
    14. 14. PLM Objectives <ul><li>Engineering data management </li></ul><ul><li>Multi-disciplinary BOM management </li></ul><ul><li>Automated CM (configuration management) </li></ul><ul><li>Integration with ERP & MES </li></ul><ul><li>Regulatory compliance (ITAR / EAR) </li></ul><ul><li>Move to MBD (away from drawings) </li></ul><ul><li>Supply/design chain management </li></ul><ul><li>Program management </li></ul>
    15. 15. Problems & Solutions <ul><li>Partner Skills </li></ul><ul><li>Partner Experience </li></ul><ul><li>Sponsorship </li></ul><ul><li>Training </li></ul><ul><li>Data Load </li></ul><ul><li>Impact Poor User Adoption </li></ul>
    16. 16. Problems & Solutions: Partner Skills <ul><li>Original partner got out of ENOVIA SmarTeam; services subcontracted to second partner “No we don’t sell it anymore, but we can run your project.” </li></ul><ul><li>Second partner brought inexperienced resources “What is SolidWorks, is it like CATIA?” </li></ul><ul><li>Second partner brought training challenges “I may not speak your language well, but let’s start training.” “I may not know this software module, but let’s start training.” </li></ul>
    17. 17. Problems & Solutions: Partner Skills <ul><li>Original partner got out of ENOVIA SmarTeam; services subcontracted to second partner “No we don’t sell it anymore, but we can run your project.” </li></ul><ul><li>Second partner brought inexperienced resources “What is SolidWorks, is it like CATIA?” </li></ul><ul><li>Second partner brought training challenges “I may not speak your language well, but let’s start training.” “I may not know this software module, but let’s start training.” </li></ul><ul><li>Solution: Engaged Razorleaf in early 2006 </li></ul><ul><li>Advice: Select partners carefully </li></ul>
    18. 18. Problems & Solutions: Partner Experience <ul><li>Followed user demands, against best practices “Sure, name your files however you like, its no big deal.” “So what if its so complicated no one knows how to search?” </li></ul><ul><li>Default settings from installation, unaware of impact “We didn’t know what we didn’t know.” </li></ul>
    19. 19. Problems & Solutions: Partner Experience <ul><li>Followed user demands, against best practices “Sure, name your files however you like, its no big deal.” “So what if its so complicated no one knows how to search?” </li></ul><ul><li>Default settings from installation, unaware of impact “We didn’t know what we didn’t know.” </li></ul><ul><li>Solution 1: Changed SmarTeam configuration </li></ul><ul><li>Solution 2: Redeployed PLMDB </li></ul><ul><li>Advice: Select partners carefully </li></ul>
    20. 20. Problems & Solutions: Sponsorship <ul><li>Reality check – sales is not consulting “The salesperson said we’d be up-and-running by now.” </li></ul><ul><li>Did we pick the wrong software? “We hire smart people, so it must be a software problem” </li></ul><ul><li>I support this initiative, really I do “Please, could you kinda, maybe try the software again?” </li></ul>
    21. 21. Problems & Solutions: Sponsorship <ul><li>Reality check – sales is not consulting “The salesperson said we’d be up-and-running by now.” </li></ul><ul><li>Did we pick the wrong software? “We hire smart people, so it must be a software problem” </li></ul><ul><li>I support this initiative, really I do “Please, could you kinda, maybe try the software again?” </li></ul><ul><li>Solution: Spoke the truth, even when it hurt </li></ul><ul><li>Advice: Get deep management sponsorship </li></ul>
    22. 22. Problems & Solutions: Training <ul><li>Power users must understand “why”, can’t self-train “Do it this way, because that’s what the manual says.” “Just show me the software, I’ll figure out what to do with it.” </li></ul><ul><li>The data matters (somewhat) “Our assemblies have 5,000 parts, not 5.” </li></ul><ul><li>Training is not optional “I’m busy with a project, I’ll catch up on using PDM later.” </li></ul>
    23. 23. Problems & Solutions: Training <ul><li>Power users must understand “why”, can’t self-train “Do it this way, because that’s what the manual says.” “Just show me the software, I’ll figure out what to do with it.” </li></ul><ul><li>The data matters (somewhat) “Our assemblies have 5,000 parts, not 5.” </li></ul><ul><li>Training is not optional “I’m busy with a project, I’ll catch up on using PDM later.” </li></ul><ul><li>Solution: Retrained 30+ users </li></ul><ul><li>Advice 1: Require training, make it relevant </li></ul><ul><li>Advice 2: Have enough rollout support </li></ul>
    24. 24. Problems & Solutions: Data Load <ul><li>No detailed specification, insufficient planning “Well, you didn’t ask for that. ” “I didn’t know they would want to search on that field.” </li></ul><ul><li>Poor reliability and performance Unpredictable crashes, unable to resume, long run times </li></ul><ul><li>Insufficient validation - consultant Missing records, duplicate records, records without revision </li></ul><ul><li>Insufficient validation - users “Yeah, I kinda looked at the data. It seems OK.” </li></ul>
    25. 25. Problems & Solutions: Data Load <ul><li>No detailed specification, insufficient planning “Well, you didn’t ask for that. ” “I didn’t know they would want to search on that field.” </li></ul><ul><li>Poor reliability and performance Unpredictable crashes, unable to resume, long run times </li></ul><ul><li>Insufficient validation - consultant Missing records, duplicate records, records without revision </li></ul><ul><li>Insufficient validation - users “Yeah, I kinda looked at the data. It seems OK.” </li></ul><ul><li>Solution: Remediated data through SQL </li></ul><ul><li>Advice: Specify and validate data loads (in detail) </li></ul>
    26. 26. Status <ul><li>Non-CAD users love the system </li></ul><ul><li>CAD user champions are leading the charge and converting the last remaining holdouts </li></ul><ul><li>Struggling with some technical issues in V5R19 </li></ul><ul><li>Overall, users have adopted it - FINALLY </li></ul>
    27. 27. PLM Future at AS&E <ul><li>Creating neutral files for design/supply chain </li></ul><ul><li>Managing transmittals for design/supply chain </li></ul><ul><li>End-to-end 3D managed content (SolidWorks and 3DVIA Composer both integrated) </li></ul><ul><li>Investigate full BOM management </li></ul><ul><li>More rich PDM-ERP integration (bi-directionality, BOM structures) </li></ul><ul><li>Investigate program management </li></ul>
    28. 28. Summary <ul><li>There are always plenty of technical issues </li></ul><ul><li>AS&E’s biggest issues weren’t technical: </li></ul><ul><ul><li>“ The data is junk, I can’t trust the system” </li></ul></ul><ul><ul><li>“ Training was nice, but that will never work for me” </li></ul></ul><ul><ul><li>“ You can’t make me use the system” </li></ul></ul><ul><ul><li>“ The system slows me down, I’m faster without it” </li></ul></ul><ul><li>Culture change is the hardest thing about PDM </li></ul>
    29. 29. <ul><li>Jonathan Scott </li></ul><ul><ul><ul><li>www.Razorleaf.com </li></ul></ul></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><ul><ul><li>330.676.0022 x7133 </li></ul></ul></ul><ul><ul><ul><li>@JonathanPScott </li></ul></ul></ul><ul><li>Maureen Murphy </li></ul><ul><ul><ul><li>www.AS-E.com </li></ul></ul></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><ul><ul><li>978.262.8874 </li></ul></ul></ul>

    ×