Implementation of a Collaborative Engineering Data Management System. Tony Metz Fermilab 04 May 2015

Transcription

1 Implementation of a Collaborative Engineering Data Management System Tony Metz Fermilab 04 May 2015

2 Agenda Introduction Engineering Data Management System (EDMS) History Problem to resolve Solution Benefits Hurdles Next Steps Summary 2

3 Introduction Many new engineering projects typically involving collaborators Real time access to consume and author data Engineering documents and calculations CAD and visualization Participate in workflow activities Many types of collaborators Labs (both national and international) Universities Contractors and Vendors Access methods to engineering data historically not conducive to collaboration Large file sizes and graphics intensive applications 3

4 EDMS History at Fermilab Siemens Teamcenter Production at Fermilab since 2012 Fermilab user facts 500 active accounts 250 unique users per month 80 daily concurrent users Continues to grow 4

5 EDMS History at Fermilab Documents stored within Teamcenter CAD Models and Drawings Engineering documents PDF, STEP, Image(s) Risk Assessments Calculations Specifications Plus many more. 5

6 EDMS History at Fermilab Workflow processes Review and Approve Work Requests 6

7 EDMS History at Fermilab Integrations NX (CAD) Microsoft Office products (Word, Excel, PowerPoint, Visio, Project, Outlook) MultiCAD Strategy AutoCAD (Mechanical, Electrical, Inventor, Revit) SolidWorks, Solid Edge Also available Pro/E, Creo, CATIA Collaborators Jefferson Lab Argonne SLAC, BNL, LBNL, India (BARC and RRCAT) Others 7

8 Problem to resolve After deploying our EDMS to collaborator sites we realized: Performance was ok at US collaborator sites (not great) Existing installation methods were time consuming Collaborator sites make changes as frequent as Fermilab Java versions changed Re-installs Very time consuming to fix collaborator issues Internal fixes take minutes to hours External fixes take days to weeks No control or visibility of collaborator environments Security and methods were different at each collaborator Understood that we needed to improve how we were solving external collaborator issues 8

9 Solution Asked vendors if they had similar collaborator experiences NVIDIA contact discussed beta testing going on with NVIDIA K1 and K2 cards (GPU Sharing) via Citrix Initial Citrix Demo Citrix rep located in South Carolina; server in Los Angeles Operating real time in Chicago using a small CAD (NX) assembly Fermilab has significant VMware footprint Determined if VMware had a solution Issue at the time was latest version of OGL (graphics driver) Decided on Citrix due to leading technical solution Help from senior management allowed us to purchase hardware and licenses to get started Lab perspective as an engineering point solution 9

10 Solution Publish applications via a browser interface Hide the underlying VM resources from end-users 10

11 Solution What did we build? Hardware Production environment (2) Dell R720 servers 2 CPU, 10 core 128 Gb Memory (4) NVIDIA K2 graphics cards Cuda Cores per card 8Gb GDDR5 RAM Development environment (1) Dell R720 server (hot spare) (1) NVIDIA Quattro

12 Solution Citrix Software (20) Enterprise Citrix XenDesktop licenses (initial) (1) Netscaler VPX 200 (200 Mb max throughput) (4) XenServer CPU license XenCenter for management Citrix receiver Client side GPU Pass-through 12

13 Solution Microsoft Software Windows Server 2012 OS licenses Windows Server terminal server CALs Microsoft Office licenses Microsoft Office user CALs 13

14 Solution Security LAN domain password WAN Cisco VPN or 2-factor authentication RSA Token 14

15 Solution Architecture 15

16 Benefits Solved our initial problem How to better support external collaborators No Installs Alleviate support needed for external environments Minimal hand holding ( a document on how to use Citrix) We do not need to understand security and IT models at collaborators location Modifications of S/W at collaborator location has no effect on EDMS Better control of the environment 16

17 Benefits Removed waste from existing processes (Lean) Example collaborator CAD process Prior to Citrix, many steps in the process 1. Fermi login to EDMS 2. Fermi - export reference data from EDMS 3. Fermi - send STEP file to collaborator 4. Collaborator - read STEP file at collaborator EDMS 5. Collaborator - create parts around reference data 6. Collaborator - remove reference data prior to export 7. Collaborator - export collaborator parts to STEP file 8. Fermi Read in STEP file into EDMS 9. Fermi Get admin support if issues with STEP file 10.All - Confirm parts are valid 11.Fermi If issues repeat above steps and manage old data 17

18 Benefits Removed waste from existing processes (Lean) Example collaborator CAD process After Citrix, few steps in the process 1. Collaborator login to Fermi EDMS via Citrix 2. Collaborator - create parts around reference data 3. All Confirm parts are valid Value Fewer steps in process See changes daily in reference data (less errors) Use same reference data (no copies) Collaborator data gets added in immediately instead of at end of the project Less data and less management of data Real Team approach (instead of us versus them) 18

19 Benefits Multi operating system support Windows Macintosh Linux 19

20 Benefits Mobile support Tablets/Phones ipad, iphone, i Android Microsoft 20

21 Benefits Many additional benefits Slow workstations and laptops can use Citrix (until new computers are ordered) All data located at Fermilab (Secure) Printing and local drive support (can be turned on or off) Citrix as a backup system during major upgrades Development and Test Environment client installs One environment per workstation Control publishing of apps to each individual or OU group No User Downtime (in theory) User has a problem with Teamcenter on workstation Use Citrix until computer is fixed 21

22 Hurdles Screen capture Needs network drive mapped or USB access to save images Application Modifications Modifications need to be applied to all VM s SpaceBall deployment Requires a traditional VM environment Significant resources from servers to deploy Increased total cost of ownership Separate VM s have unique user profiles Cached area is different on each VM Slightly impact performance See next steps slide 22

23 Next Steps Citrix roaming profiles Login and synchronize user profile in the background Wyse Terminals Support two monitors Number of USB connections Speaker connections Real hardware in server room Locate in non-office environments Secure Culture Change 23

24 Summary Cost: About $70K (total) for 60 concurrent user configuration Value: Allows for real time engineering collaboration with multiple laboratories Could be used with any EDMS Easy to install and configure Many, many, many benefits.. Few hurdles Thank you for your attention! Any questions or comments? FERMILAB-CONF CD 24