The document discusses challenges in implementing Product Lifecycle Management (PLM) software and tools for educational use. It outlines Oakland University's experience deploying PLM systems and lessons learned. To address issues like cost, licensing, and online access, the university developed a new IT architecture using virtual machines to host PLM applications. This allowed remote access and standardized deployment processes. Going forward, they plan to utilize cloud computing to further improve scalability and access for teaching PLM tools.

1. Developing an IT Infrastructure for
Educational Institutions
Teaching Product Lifecycle Management
Atul S. Khiste Robert Van Til
M.S. student Professor
Industrial & Systems Engineering Dept.
Oakland University
Hillberg Patrick
Solutions Architect
Siemens PLM Software Inc.

2. Agenda
❏ What is PLM
❏ Challenges at academic institutions for PLM
implementation
❏ PLM implementation at Oakland University – What
did we learn
❏ Overview of our solution
❏ PLM system level architecture
❏ Platform level architecture
❏ Conclusions and Future Considerations

3. What is PLM?
❏ PLM is about collaboration
❏ Digital tools saves money and time
❏ Digital models replace prototypes
❏ It’s cheaper to bend bits and bytes than it is to bend metal
❏ PLM leads to a reduction in time, energy and
material

4. PLM Implementation - Challenges
❏ Challenges for academic institutions
❏ Lack of skilled IT support
❏ High cost for PLM softwares
❏ Standard PLM software installation templates
❏ Customization required for teaching PLM tools
❏ Issues using PLM tools online
❏ Licensing
❏ Compatibility
❏ Connectivity and latency issues

5. What did we learn?
❏ Planning prior to starting course
❏ Need for flexible IT infrastructure
❏ Consider security related issues
❏ Check software vendor license policies
❏ Limitations of written training materials

6. What did we do?
 Normal PLM software setup
 Deployed softwares on local physical machines
 Identified, resolved and documented operational issues
 Online course – the need for a virtual lab
 Created virtual machine allowing 50 concurrent users
 Pre-configured Teamcenter PLM client installed
 Performance comparison of remote vs local
 Failed attempt to virtualize CAD software
 Use of social forum for sharing issues
 Created lab materials

7. How did it go?
 Operational issues due to wrong IT implementation
method
 Gaps between course goals and IT infrastructure
 Online course premises/local deployment
impediment
 No licenses to support collaborative education goals
 Virtualizing PLM application was identified as best option
 Virtualization helped administrator to control deployment
and maintenance
 Cost and scalability of virtual servers

8. How did we respond?
❏ Designed and implemented new IT architecture
❏ Developed procedures for PLM application
deployment
❏ Created digital video library for PLM - CAD labs
❏ Proposal for cloud providers to support schools for
hosting PLM applications
❏ Proposal for providing licenses for CAD virtualization
and work instructions
❏ Standard PLM software installation templates
designed for academic institutions

9. Training and Support
Manufacturing process planningTeamcenter
Plant Simulation

10. Product management - Teamcenter

11. IT Architecture Overview

13. System level architecture

14. Platform level architecture

15. Conclusions and the future
❏ Teamcenter (PLM) - Solid edge (CAD) integration
successfully implemented
❏ Developed and implemented an IT infrastructure for
off-campus virtualization
❏ Package application for remote users to solve
deployment and compatibility issues
❏ Standard practice document for PLM and
Tecnomatix suites implementation
❏ Plan to use cloud computing shared platform for
hosting Teamcenter application