NSA Capstone Project III final pp
- 1. NSA Capstone Project III CNUSD COMPUTER LABS
- 2. Team Members Chaz Parada Alfonso Zamorano Robert Cortez
- 3. Summary Project Description Project Objectives Project Scope Deliverables Project Schedule Project Risk Management Server Configurations Client Configurations Quality Management Plan Stakeholders Requirements
- 4. Summary Cont. Acceptance Criteria Project Estimated Effort/Cost/Duration Project Assumptions Project Risk Management Project Constraints Project Dependencies Project Approach Communication Plan Project Guidelines Project Approvals Total Cost
- 5. Project Description The Technology director of CNUSD wants three new fully functional computer labs for various groups of students. These labs will give students the means to thrive in a growing technological world by providing the infrastructure and technology with the will to learn basic computer literacy.
- 6. Project Objectives The objective of this project is to be able to design and implement a network infrastructure for three functional computer labs in the Corona Norco Unified School District. These labs will provide students and teachers will e-mail capability on both client and mobile devices, as well as secure authentication. There will be basic productivity software installed to provide students the means to complete all assigned classwork and labs. Web access will be provided within a secure network infrastructure so that students, teachers, and guests can navigate the web safely. A user guide web page will be designed and will be used for and type of training and documentation purposes.
- 7. Project Scope In Scope: Procurement of all necessary software/hardware to meet client requirements Installation and configuration of hardware and devices Providing wireless access for only the approves mobile devices Configuring a secure network environment for the safe storage of sensitive data Testing of all hardware devices or software installed by TSM Production of any applicable documentation for the project Warranty replacement or rework off any defective devices for 30 calendar days after successful completion
- 8. Project Scope Cont. Out of Scope No technical support will be provided after the successful completion of the project Any installation or modification of any electrical wiring is not a concern for TSM Laboratory furniture will not be procured or installed by TSM Any installation of any hardware or software, outside of what is stated in the project requirements will not be completed by TSM
- 9. Deliverables Active Directory Schema Physical Network Diagram Logical Network Diagram Disaster Recovery Plan Detailed Bill of Materials89 Quality Management Plan
- 10. Deliverable Cont. Gantt Chart Network Activity Diagram Work Breakdown Structure Risk Management Plan Change Management Plan Project Agendas
- 11. Project Schedule Week 1: Site inspection then Brainstorm to make a rough outline of needed phases we will need to go though Week 2: Write up a charter to cover what we found we needed in week 1 Week 3: Write up all needs for the severest up Week 4: Write up all needs for the labs setup Week 5: Design a network layout (i.e IP address, wiring ect.)
- 12. Project Schedule Cont. Week 6: Find pricing for needed components Week 7: Confirm components work with each other and programs will run smoothly Week 8: Do install and server set ups Week 9: Configure labs make sure all programs are running Week 10: Have random users test the computers in labs to make sure they work for different users Week 11: Present to stakeholders the finished outcome
- 13. Project Risk Management Risk Planning Process This project followed a systematic, proactive approach to risk planning, which involved as many stakeholders as feasible. The process for risk planning was: 1. Risk identification – identified possible risk events that could occur on the project, the triggers that could precipitate the risk, and the symptoms that would indicate that the risk occurred. 2. Risk qualification – determined the qualitative probability and impact of the risks, based on stakeholders’ input, to prioritize the risks for further planning actions.
- 14. Project Risk Management Cont. 3. Risk quantification – high score risks were analyzed further to quantify their probability in percentage and their impacts in cost, time or quality measures. The result of quantification is the risk exposure, which is the product of the probability and impact values. 4. Risk response development – proactive risk response strategies were developed reduce, transfer or eliminate unfavorable risks and exploit, enhance or share favorable risks. Some risks had contingency plans and fallback plans developed in case the risks occur.
- 15. Server Configurations Server 1 Server Name: DC118 Short description: Controls security protocols for the domain OS: Microsoft Windows Server Standard 2012 R2 FQDN: DC118.CNUSD.com IP Address: 125.1.1.3/24 Server Role(s): Domain controller and Schema Master
- 16. Server Configurations Server 2 Server Name: DNS118 Short description: Resolves and distributes IP addresses for devices on the network OS: Microsoft Windows Server Standard 2012 R2 FQDN: DNS118.CNUSD.com IP Address: 125.1.1.4/24 Roles: DNS and DHCP
- 17. Server Configurations Server 3 Server Name: Print118 Short description: Handles print jobs from devices on the network. Also hosts the local intranet web page. OS: Microsoft Windows Server Standard 2012 R2 FQDN: print118.CNUSD.com IP Address: 125.1.1.5/24 Roles: Print server and IIS (web server)
- 18. Server Configurations Cont. Server 4 Server Name: BU118 Short description: Backup server used to seize roles in the event of a server failure. OS: Microsoft Windows Server Standard 2012 R2 FQDN: BU118.CNUSD.com IP Address: 125.1.1.6/24 Roles: Domain controller, IIS, Print Server, DNS, and DHCP. These roles will be preconfigured but inactive. In the event of a server failure, any of these roles can be activated to minimize downtime between repairs.
- 19. Client Configuration Install windows 7 OS Install KASPERSKY TOTAL SECURITY FOR BUSINESS Install Microsoft Office (word, outlook, power point, excel, note) Remove run commands Set auto power on/off
- 20. Client Configuration Cont. Remove ability to open/run security program Remove control panel Remove system tools Remove preloaded games Setup Auto updates
- 22. Purpose The purpose of this Quality Management Plan is to ensure that the customer is receiving not only a quality network from TSM, but also a network described within the project documentation. The project has certain deliverables to help in this process. This plan is one of those deliverables, and outlines what is being checked. This plan includes two types of documentation. 1. Checklist for all documentation. 2. Checklist for all hardware and software that is involved with the end user.
- 23. Objectives The objectives within the Quality Management Plan are to provide the customer with the documents that will guide their inspection of services. Quality will meet the following objectives: Complete informative documentation Labs cabled to code Functional network Up-to-date server environment Up-to-date workstation environment
- 24. Stakeholders Stakeholders How are they affected? Students Students will use the labs to learn basic computer literacy skills for use in the modern workplace. They will have the ability to email class assignments and homework to their teachers. Teachers Teachers have the benefit of sending assignments progress reports, and reminders to all their students via email. School District The school district will benefit from higher performing schools that utilize an effective learning environment. School The school will benefit by having a more effective means of communication between faculty and students.
- 25. Requirements Hardware Severs One Domain Controller for Active Directory Schema and LDAP authentication One DNS/DHCP Server for client IP addressing and domain name resolution One IIS Server for hosting user intranet web page and documentation and a secondary role as a print server One file server for backing up critical data
- 26. Requirements Cont. Clients 90 desktop computers for students’ use (30 per lab) 3 desktop computers for teachers’ use (1 per lab) Printers 3 high capacity printers (1 per lab), for students and teachers to print assignments and other school related documents Wi-Fi 3 wireless access points (1 per lab), for teachers and students to gain network access on approved mobile devices
- 27. Requirements Cont. Functionality Logins for three specific groups Students Instructors Guests Mail Mail for both students and instructors Mobile mail for both students and instructors Microsoft Exchange Online for 1500 users Login LDAP authentication
- 28. Requirements Cont. Software Microsoft Windows Server 2012 R2 Licensing for 4 Servers CAL licensing for 200 devices Microsoft Windows 7 SP 1 Licensing for 105 workstations Microsoft Office 2013 Licensing for 105 workstations Kaspersky Total Security for Business
- 29. Requirements Cont. Network Infrastructure Copper UTP cabling from the labs to the server room Copper UTP patch cabling from wall drops to workstations Copper UTP patch cabling patch panels to servers 3 Cisco 48 port managed switches 3 Cisco standalone wireless access points 1 Cisco 8 port managed switch 1 Cisco integrated services router 1 Cisco firewall Server Room Locking racks for server security and integrity
- 30. Acceptance Criteria Hardware All hardware will be new, and neither used nor refurbished Servers Will have a minimum of 8GB RAM Will have a minimum of 4 processor cores Will have a minimum of 500GB Storage Will be rack-mounted Wi-Fi Will support up to 20 concurrently connected devices per access point Will support wireless 802.11n technology
- 31. Acceptance Criteria Cont. Clients Will have a minimum of 8GB RAM Will have a minimum of 1TB hard drive storage Will have Ethernet 10/100/1000 network adapters Will have a minimum of 25” LED monitors Will have wired keyboards and mice Will have lockable cases with locks in place for workstation security and integrity Printers Will have a minimum of 50 PPM printing capacity Will print both color and B&W
- 32. Acceptable Criteria Cont. Software All software will have current licensing and not violate any copyright or antipiracy laws Workstations All workstations will have Microsoft’s Windows 7 SP1 operating system All workstations will have Microsoft’s Outlook, Word, Excel, and PowerPoint All workstations will have antivirus and antimalware software Servers All servers will have Microsoft’s Windows Server 2012 R2 operating system All servers will have antivirus software Email servers will use Microsoft’s Exchange 2013 software
- 33. Acceptable Criteria Cont. Functionality Teachers, students, and guests will be able to authenticate to the domain from any workstation in any of the labs All users will have access to the local intranet documentation website All users will have internet access Users with mobile devices will be able to gain access to the network wirelessly Network Infrastructure Only Cisco brand networking devices will be used: routers, switches, etc. Routers will have VPN capability to communicate with other district laboratories Traffic from site to site will use a minimum of 128 bit encryption
- 34. Project Estimated Effort/Cost/Duration Milestone Projected Completion Date Deliverable(s) completed Planning Phrase 10/2/15 Project Charter Project Scope Project Schedule Design Phrase !0/30/15 Bill of Materials Risk Management Implementation Phrase 11/5/15 Workstation /Server Configurations Closing Phrase 11/21/15 Project Manager Signoff Client Signoff Estimated Cost: $295,496.45 Estimated Effort Hours: 150 – 250 hours Estimated Duration: 8-10 weeks
- 35. Project Assumptions It is assumed that: This is validated by: The existing lab rooms will have adequate space and cooling capacity for the new lab equipment Conducting a site inspection The existing server room will have adequate space and cooling capacity for the new lab equipment Conducting a site inspection The electrical infrastructure is in place and meets the wattage and usage requirements of the new equipment in both the labs and server room. Conducting a site inspection Service will be provided to demarcation point Testing the internet connection provided for the server room
- 36. Project Risk Management Risk Area Level (H/M/L) Risk Plan Responsibility Backordered or factory defective hardware Medium In the event that hardware is unavailable when it’s time for installation we have prepared an additional means of procuring hardware that meets our standards. Robert Cortez Team member absences or failure to meet assigned deadlines. Medium All tasks and deliverables have second person assigned to assume responsibilities in the event of a member absence or failure to complete the given task. Robert Cortez
- 37. Project Constraints The project must be completed before the start of the school year on August 16th, 2016
- 38. Project Dependencies The successful completion of this project is dependent of the following: Building access for the duration of the installation within the school’s specified hours of operation. This includes, but is not limited to, access to the server and laboratory rooms, as well as access to any rooms needed to properly install and route network cabling. Any and all permits required to meet county, city, state, and federal regulations applicable to this installation before the implementation phase begins.
- 39. Project Approach Planning Phase Site inspection: A site inspection is necessary to determine materials needed, physical layout, and any possible project impedances. Project Charter: The project charter is the outline for the project and encompassing elements. Scope of Work The scope of work will dictate was is to be expected, and also not expected, as it pertains to this project. Network Activity Diagram. The network activity diagram is a visual aid to help understand the project process and progression. Project Schedule The project schedule will dictate at when deliverables will be completed. Change Management Plan The change management plan will explain the process to request changes to be made the project or its deliverables.
- 40. Project Approach Cont. Design Phase Work Breakdown Structure Hardware Software Network Infrastructure Active Directory Schema Bill of Materials Risk Management Plan
- 41. Project Approach Cont. Implementation Phase Hardware Installation Software Installation Configurations Quality Plan and Testing Closing Phase Deliverables Checklist Deliver Finished Product Project Manager Signoff Customer Signoff
- 42. Communication Plan All project related questions and concerns should be directed to the project manager, who may then use the following contact information to communicate any issues. Below is the contact information and respective titles for the persons involved in this project. It is recommended, for documentation purposes, that communication should be made primarily by email.
- 43. Communication Plan Member Role Email Phone Chaz Parada Project Manager chazparada@yahoo.com (951)-252-5054 Alfonso Zamorano Team Member alfie03rocks@aim.com (951)-532-3575 Robert Cortez Team Member robertgenecortez@gmail. com (951)-281-9626 Anna Coriddi CNUSD Treasurer acoriddi@cnusd.k12.ca.us (951)-736-5000 Michael H. Lin CNUSD Superintendent mlin@cnusd.k12.ca.us (951)- 736-5010 Brian Troudy Technology Director btroudy@cnusd.k12.ca.us (951)- 736-5190
- 44. Project Guidelines All team members must complete deliverables in a timely manner so that a reviews and revisions can be made before the specified date of completion. All team members must follow the communication plan, as stated above, for any project related issues. All documents should be saved to the shared google drive, as well as, locally to the responsible party’s computer. All team members must notify the project manager upon completion of any tasks, deliverables, or documentation.
- 45. Project Approvals Approver Position/Role Signature Anna Coriddi CNUSD Treasurer Michael H. Lin CNUSD Superintendent Brian Troudy Technology Director Chaz Parada Project Manager
- 46. Total Cost Total Cost: $295,496.45