Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Slide 1 - SDSU College of Engineering


Published on

Published in: Technology, Business
  • Be the first to comment

Slide 1 - SDSU College of Engineering

  1. 1. Challenges in the COE Computing Environment Staffing Funding Equipment
  2. 2. Relatively Small College (FTE’s) Large Usage of Computing Resources and Applications Support Unix, Windows, & MAC
  3. 3. Software and Resources Faculty, staff, and student accounts, file storage, email Web and database servers Domain controllers Many complicated and robust applications
  5. 5. Important COE Policies Standardization of hardware and software Batch purchasing of computers Computer warranties Software utilities for IT Staff
  6. 6. Computer Staffing History Current situation Proposal
  7. 7. History Equipment technicians Student help Changing computer needs
  8. 8. Current situation 4 full time IT Staff One work study student helper, (no experience) No equipment tech help 655+ computers and growing
  9. 9. Proposal Add one full time IT staff member Non- work study student assistants Equipment Technician computer support Redefine computer responsibilities/service Recycle old equipment out
  10. 10. Computers in the College of Engineering <ul><li>Number of computers and Age </li></ul>
  11. 11. We have a total of 655 computers Total >3years <3 years Faculty 98 62 36 Staff 37 30 7 Research Labs 67 40 27 Computer Labs 438 309 129 Servers 15 14 1 Totals 655 455 200
  12. 12. Total Computers in the College of Engineering Faculty 15% Staff 6% Research 10% Student 67% Servers 2% Faculty Staff Research Student Servers
  13. 13. Total number of computers Total number of computers with and with out Warranty no warranty 69% Warranty 31%
  14. 15. Staff Computers No Warranty 81% Warranty 19%
  15. 16. Research No Warranty 60% Warranty 40%
  16. 17. Student No Warranty 71% Warranty 29%
  17. 18. Servers No Warranty 93% Warranty 7%
  18. 19. Support for Existing Infrastructure <ul><li>Many midrange servers and workstations were purchased using funds derived from the Defense Conversion program (1995-2001) </li></ul><ul><li>Dino, Dino2, Kind, Kahuna, Jason, Attila, Astro all categorized as “obsolete” by respective vendor (Dell, Sun, SGI). </li></ul><ul><li>College remains heavily dependent on services provided by our midrange servers: WWW, e-mail, file sharing, remote backup, computational software. </li></ul><ul><li>Starting to see significant wear and component failures (disk drive, motherboard, power supply failures) </li></ul><ul><li>Some failures can not be serviced due to vendor “End Of Life” (EOL) policies. </li></ul><ul><li>What can we do to protect our investment? </li></ul>
  19. 20. Support for Existing Infrastructure <ul><li>Proactive vs. Reactive: Proactive is the better policy. </li></ul><ul><li>Critical midrange servers and workstations not covered by a hardware maintenance contract or warranty should be placed under a support agreement with the respective vendor. </li></ul><ul><li>Obsolete servers and workstations should be replaced using vendor provided “return for credit and upgrade” programs when possible. </li></ul><ul><li>College administration has history of being reactive when crises occur. </li></ul><ul><li>Historically, funds to replace broken or worn components were garnered in haste after a problem has occurred, causing unnecessary stress for the analyst and downtime for the faculty, staff and students. </li></ul>
  20. 21. Support for Existing Infrastructure <ul><li>There is a better way to manage our existing IT infrastructure: adopt a proactive management strategy . </li></ul><ul><li>Allocate some amount of capital at the beginning of each fiscal year for the sole purpose of purchasing replacement components with a high probability of failure. </li></ul><ul><li>Proactive strategy provides the analyst with an ability to plan and schedule downtime when servers are to be upgraded and components replaced. </li></ul><ul><li>Users (faculty, staff, students) are given reasonable advanced notice and the analyst can perform repair and replacement operations in a careful and unhurried manner. </li></ul><ul><li>Users experience less frustration and analyst makes fewer mistakes. Conclusion: everyone benefits from a proactive strategy! </li></ul>
  21. 22. Support for Existing Infrastructure <ul><li>Our recommendations for equipment replacement : </li></ul><ul><ul><li>Annually replace 125 desktop PC’s with new PC’s </li></ul></ul><ul><ul><li>Replace any PC’s and workstations that have a date of manufacture 4.5 years or more in the past </li></ul></ul><ul><ul><li>Replace at least one midrange Microsoft Windows servers each year </li></ul></ul><ul><ul><li>Replace at least one midrange Sun Solaris server with a new midrange Linux server each year </li></ul></ul><ul><li>Our recommendations for warranty services and hardware maintenance agreements : </li></ul><ul><ul><li>Purchase 5 year hardware protection plans for all critical midrange servers </li></ul></ul>
  22. 23. Support for Existing Infrastructure <ul><li>Supporting existing hardware infrastructure requires software too! </li></ul><ul><ul><li>Solstice Backup </li></ul></ul><ul><ul><li>NetOp </li></ul></ul><ul><ul><li>DeepFreeze </li></ul></ul><ul><ul><li>X-Win32 </li></ul></ul><ul><ul><li>Integrity Desktop </li></ul></ul><ul><ul><li>Citrix MetaFrame </li></ul></ul><ul><ul><li>Norton Ghost </li></ul></ul>
  23. 24. We need Solstice Backup <ul><li>Centralizes data protection and management across heterogeneous environments (Windows, Sun, SGI, Linux, and Macintosh). </li></ul><ul><li>Allow us to automatically create nightly tape archives of faculty, staff, and student personal data. </li></ul><ul><li>Faculty and staff can restore lost files without calling helpdesk! </li></ul><ul><li>Allow use of our Hewlett-Packard SureStore 4/40 DLT (tape) Library (never been used).  </li></ul>
  24. 25. We need NetOp <ul><li>Remote control software for Windows. </li></ul><ul><li>Allow us to remotely configure desktop PC’s from our individual offices. </li></ul><ul><li>We will be able to fix a computer problem without having to walk over to your office! </li></ul><ul><li>Less hassle for the Faculty/Staff customer, more efficient for technician. </li></ul>
  25. 26. We need Deep Freeze <ul><li>Allow us to automatically restore student computing lab PC’s to a production configuration after each restart. </li></ul><ul><li>Will cancel or correct unauthorized modifications made to a lab PC. </li></ul><ul><li>Quickly and effortlessly recover from virus destruction, human error, student mischief, hacking. </li></ul>
  26. 27. We need X-Win32 <ul><li>Allow remote graphical access to campus Unix servers from desktop PCs running Microsoft Windows. </li></ul><ul><li>$4,400.00 for 100 licenses. </li></ul>
  27. 28. We need Integrity Desktop <ul><li>Prevent users from modifying IT-defined security rules. </li></ul><ul><li>Employees remain productive and data is secured with minimal technician effort. </li></ul><ul><li>Blocks PC software threats proactively. </li></ul><ul><li>Real-time protection against proliferating worms, viruses, Trojan horses, spyware, malicious code. </li></ul>
  28. 29. We need Citrix MetaFrame <ul><li>Allow student access to commercial software from home. </li></ul><ul><li>Easier than having helpdesk install individual instances of software on student laptops. </li></ul><ul><li>Install software on application server – student access over campus network or Internet. </li></ul><ul><li>Essential if we migrate to a student laptop paradigm instead of maintaining desktop PC labs. </li></ul>
  29. 30. We need Norton Ghost <ul><li>Mandatory to effectively install lab PCs. </li></ul><ul><li>Allow technicians to construct one PC software configuration, then replicate that configuration to many PCs. </li></ul><ul><li>Make new software available to students in minutes. </li></ul><ul><li>Easily install software upon faculty demand. </li></ul>
  30. 31. College of Engineering Challenges in Computing!
  31. 32. College of Engineering Challenges in Computing! Challenges of Existing Infrastructure Challenges of College Growth Challenges of Changing Environment
  32. 33. Staffing <ul><li>Understaffed by any standards </li></ul><ul><li>Comparison within SDSU </li></ul><ul><li>With Industry </li></ul><ul><li>Staffing has actually declined </li></ul><ul><li>Department Techs no longer support computing </li></ul><ul><li>Increasing Workload </li></ul><ul><li>Growth in Students & Faculty </li></ul><ul><li>Security Initiatives </li></ul>
  33. 34. Equipment <ul><li>Computer Equipment is rapidly aging! </li></ul><ul><li>No significant investment in Computer Equipment in past 3 years! </li></ul><ul><li>Significant Quantity of Equipment presently over 4 years old! ($500.000 + ) </li></ul><ul><li>Majority of our Computer Equipment is out of warranty! </li></ul><ul><li>Equipment hardware failures are causing increased workload and adverse impact on faculty, staff, and students! </li></ul>
  34. 35. Software Acquisition & Maintenance <ul><li>Never been a plan or allocation of resources for purchase and maintenance of Computer Software! </li></ul><ul><li>Software Purchase coordination within College and at the University level! </li></ul>
  35. 36. Management <ul><li>Slow Death by Computer Committees! </li></ul><ul><ul><li>No Decisive Leadership in Information Technology </li></ul></ul><ul><ul><li>No Strategic Planning or Implementation </li></ul></ul><ul><li>Lack Organizational Structure for Information Technology! </li></ul><ul><li>Not recognized as an integral and important part of College of Engineering Team! </li></ul>
  36. 37. Challenges of Changing Environment New Faculty means greater use of computer technology in Instruction and Student Projects Industry is demanding more technologically trained graduates PLTW Students will come with expectation of advanced technology capabilities and training
  37. 38. Challenges of Growth of College Increasing Faculty New Faculty want Desktop and Laptop Increasing Students Limited Lab Space Available Increasing Computer Resources to Manage
  38. 39. Insufficient Staff + Equipment Out of Warranty –Software Acquistion Plan – Management +Changing Environment + Growth of College = Significant Challenge for Computing
  39. 40. Financing Requirements 2004 2005 2006 2007 2008 Workstations Replace 125/Yr 200000 200000 200000 200000 200000 Repairs 25000 25000 25000 25000 25000 Warranty Ext 10000 5000 7500 7500 7500 Servers Replacement 16000 16000 16000 16000 16000 Warranty Ext 15000 6000 7000 8000 4500
  40. 41. Financing Requirements 2004 2005 2006 2007 2008 Computer Support Software BackUp Software 6000 2000 2000 2000 2000 Ghost Software 3300 660 660 660 660 NetOp Remote 9000 2500 2500 2500 2500 X-Win32 4400 800 800 800 800 DeepFreeze 3000 600 500 500 500 Integrity Desktop 3250 3250 3250 3250 3250 Citrix Software 20000 25000 30000 45000 50000
  41. 42. Proposed Strategy Promote Immediate Short Term Solutions to Issues Staffing – Student Help ( Non WorkStudy) Equipment Replacement/Repair Pro-active approach to University Funds Extend Equipment Warranties wherever possible Prioritize Computer Support considering staffing levels Obtain Grants for Development Courses to fund Software Requirements in Specific Areas (i.e. ArcGIS, SolidWorks)
  42. 43. Proposed Strategy Long Term Strategy Develop Financial Plan for College Computing Requirements Develop Resources to Finance Plan Develop Organization Plan for College Computing Develop Remote Accessible Software Capabilities