CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Infrastructure Upgrades Rick Finnegan April 22, 2008.

Slides:



Advertisements
Similar presentations
Program Assessment Briefing (PAB) Instructions Chart 1: Overview Provide a narrative mission description – Self explanatory Provide executive level program.
Advertisements

Team 1: Aaron, Austin, Dan, Don, Glenn, Mike, Patrick.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Investigations Rick Finnegan April 22, 2008.
The CRM Textbook: customer relationship training Terry James © 2006 Chapter 11: Management.
Project Control Techniques
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Manage Quality
SUMMER 2005 JUNE Preparing an Organizational Change Management Plan Org Change Management Activities by Project Phase.
Managing the Information Technology Resource Jerry N. Luftman
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
Chapter 3: The Project Management Process Groups
Chapter 5: Project Scope Management
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Operations & Administration Rick Finnegan April 22, 2008.
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
Office of Project Management Metrics Report Presentation
CD FY09 Tactical Plan Review FY09 Tactical Plan for Wide-Area Networking Phil DeMar 9/25/2008.
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
1 DRAFT PROPOSED MAY 2011 INFORMATION TECHNOLOGY DEPARTMENT Gary Morris, Acting Director CITY OF HOUSTON FY12 Budget (Operating) PROPOSED Fiscal Year 2012.
Natick Public Schools Technology Presentation February 6, 2006 Dennis Roche, CISA Director of Technology.
Project ManagementDay 1 in the pm Project Management (PM) Structures.
Unit 7 Assignment Project Progress Report Charles W. Jansen, II
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
Project Management Metrics -- Why, What, and When Kerinia Cusick Director, ESI International.
Risk planning & risk management (RM)
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
CD FY09 Tactical Plan Status FY09 Tactical Plan Status Report for Site Networking Anna Jordan April 28, 2009.
BT Young Scientists & Technology Exhibition App Risk Management.
CD FY10 Budget and Tactical Plan Review FY10 Tactical Plans for Financial Management Valena Sibley October 8, 2009 Tactical plan nameDocDB# FY10 Tactical.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
The ProactiveWatch Monitoring Service. Are These Problems For You? Your business gets disrupted when your IT environment has issues Your employee and.
Project Plan. Project Plan Components Project Overview – Description and Strategy Business Case Summary Key Deliverables and Scope Critical Success Factors.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Information Management Matt Arena June 16, 2008.
CD FY09 Tactical Plan Review FY10 Tactical Plans for Administrative Support (DAS) Griselda Lopez September 26, 2008.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Infrastructure Upgrades Rick Finnegan April 22, 2008.
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
CD FY09 Tactical Plan Status FY09 Tactical Plan Status Report for Video Conference Project Sheila Cisko April 14, 2009 FY09 VC Tactical Plan2920v1.
CD FY10 Budget and Tactical Plan Review FY10 Tactical Plans for Database Services Nelly Stanfield October 7, 2009 Database Services3425-v1.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Videoconf Support Sheila Cisko 6/17/2008.
Risk Management How To Develop a Risk Response Plan alphaPM Inc.
Introducing Project Management Update December 2011.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Brent Tufts Alex Ferreira Drew Durham Arnie Anderson Vinitha Liyanage.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
IT 499 Bachelor Capstone Week 3. Adgenda Administrative Review UNIT two UNIT threeProject UNIT four Preview Project Status Summary.
Network design Topic 6 Testing and documentation.
CD FY09 Tactical Plan Review FY09 Tactical Plans for ES&H Amy Pavnica September 26, 2008.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
Request for Service (RFS) Process and Metrics Update June 24, 2008.
Contract Year 1 Review IMT Tilt Thompkins MOS - NCSA 15 May 2002.
CD FY10 Budget and Tactical Plan Review FY10 Tactical Plans for Database Services [Presenter’s Name] [Date] Database Services3425-v1.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for LSCS-DBI-APP Dennis Box June
CD FY09 Tactical Plan Review FY09 Tactical Plans for Scientific Database Applications Igor Mandrichenko Sept. 24, 2008.
Info-Tech Research Group1 Manage IT Budgets & Cost World Class Operations - Impact Workshop.
Project Information. Contact Information Project Being Developed.
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Investigations Rick Finnegan April 22, 2008.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
CD FY09 Tactical Plan Review FY09 Tactical Plans for Computing Infrastructure Igor Mandrichenko 9/24/2008.
1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM.
OFFICE OF INNOVATION & TECHNOLOGY CITY OF PHILADELPHIA Innovation & Technology Status Update Adel W. EbeidCity of Philadelphia, Office of Innovation &
CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Networks Physical Infrastructure Rick Finnegan April 22, 2008.
CD FY09 Tactical Plan Review FY09 Tactical Plans for Information Systems Matt Arena 9/24/2008.
CD FY08 Tactical Plan Review FY08 Tactical Plans for Site Networking Rick Finnegan November 7, 2007.
FY09 Tactical Plan Status Report for Site Networking
Guidance notes for Project Manager
Presentation to Project Certification Committee, DoIT August 24, 2008
Presentation transcript:

CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Infrastructure Upgrades Rick Finnegan April 22, 2008

CD FY08 Tactical Plan Status FY08 Tactical Plan for Network Infrastructure Upgrades Relevant Strategic Plan: –Core Networking Strategic Plan FY2008 v1 Tactical Plan Leader – Rick Finnegan Organizational Unit home –LSC-CNCS-NET Tactical Plan Goals –Maintain network infrastructure capacity well ahead of current use and projected near term requirements –Network infrastructure should be maintained at the forward end of established network technology –Reliability of network infrastructure and services should be maximized –Wireless network support should be fully integrated in the general network infrastructure –The network architecture should provide for varying levels of access needs for attached systems

CD FY08 Tactical Plan Status Activities Summary: FTEs Level 0 Activity:UPGRADES% of FY Complete:50% Personnel Usage (FTEs) AllocationActual YTD Current Tactical Plan Level 1 ActivityFTE-yrsFTE-mos FTE-yrs (Ave/mo.)FTE-mos% Consumed YTD FY08 Forecast Upgrades Customer % 70% Core %100% Wireless %120% Firewall % 25% WISM %100% DNS-DHCP % 70% Total %

CD FY08 Tactical Plan Status Activities Summary: M&S (Internal Funding) Level 0 Activity:UPGRADES% of FY Complete:50% Operating & Equipment M&S CD Internal Funding Operations M&SEquipment M&S Tactical Plan Level 1 Activity FY Obligation Budget YTD Obligations + RIPS% Spent Current FY08 Forecast FY Obligation Budget YTD Obligations + RIPS% Spent Current FY08 Forecast Upgrades % 100% % 100% Customer Core Wireless Firewall WISM DNS-DHCP Total % 100% % 100%

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Customer Projects related to Customers Deliverables 1.These are planned upgrades to customer networks 2.When – throughout the year 3.Acceptance criteria is the customers accepting and planning for the upgrades 4.Recipients are Network Customers Key Milestones 1.Switch and routers to be upgraded 2.Individual upgrades planned throughout the year 3.Impact is low if the date is not met Issues and Risks (specific to this activity, includes budget impact) 1.Issues are that customers may have to endure minor outages 2.Risks are the network gear will be end of life or outages may occur

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Core Projects related to Core Networks Deliverables 1.These are planned upgrades to core networks 2.When – throughout the year 3.Acceptance criteria is the successful completion of the upgrades 4.Recipients are all networking Customers Key Milestones 1.Switch and routers to be upgraded 2.When planned throughout the year 3.Impact is low if the date is not met Issues and Risks (specific to this activity, includes budget impact) 1.Issues are that customers may have to endure minor outages 2.Risks are the network gear will be end of life

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Wireless Brief Description – Installation of additional access points Deliverables 1.Planned installs of new Access Points for additional coverage in Fixed Target, DO & CDF 2.Actual progress is on schedule 3.Acceptance criteria is the users testing the new Access Points 4.Recipients are the customers using the new Access Points Key Milestones 1.What is it – implementing new access points 2.When – The plan is 15 of 30 for the first half of the year, actual is 14 3.Impact is low and is felt by users needing additional coverage Metrics (see the next page for a chart of progress) Issues and Risks 1.Risks are that customers will continue to have no coverage until new planned Access Points are installed

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Wireless Metrics for new access points to improve coverage. Issues & Risks 1.The risks are that if the new access points are not installed we will continue to have areas with not enough coverage.

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Firewall Brief Description – Rolling out the yellow zone to new subnets Deliverables 1.What is it – moving user subnets to the yellow zone 2.When – The plan is based on soliciting volunteers 3.Acceptance criteria is users being put behind the transition tool and accepting traffic flows 4.Recipient is Customer subnets Key Milestones 1.What is it – number of subnets converted to the yellow zone 2.When – plan is dependent on soliciting new customers 3.Impact is low – this is a security concern and not a functional requirement 1.URL – Project Plan Metrics – none at this time, the project is on hold Issues and Risks (specific to this activity, includes budget impact) 1.The Risks are that we are not getting groups/subnets to volunteer to move to the yellow zone. This has slowed the progress of the project, however, BSS has agreed to move to the yellow zone.

CD FY08 Tactical Plan Status Project Activity: Network Upgrades WISM Brief Description - wireless access point upgrades to Wism Deliverables 1.Planned upgrades of Access Points from IOS to WISM 2.Actual progress is ahead of schedule 3.Acceptance criteria is the users testing the converted Access Points 4.Recipient is the customers using the Access Points Key Milestones 1.What is it – the number of access points converted 2.When – planned vs actual 260 for the year, 240 are done at this point 3.Impact is medium – Customers of unconverted access points are still functioning but they do no support the WISM blocking 1.URL – Project Plan Metrics (see the next page for a chart of progress) Issues and Risks 1.Issues are that customers may not be willing to take minor outages, this is the case currently with the Accelerator Division

CD FY08 Tactical Plan Status Project Activity: Network Upgrades Wireless Metrics for upgrades of access points from IOS to WiSM Issues & Risks 1.Devices remaining to be converted are from the Accelerator Division. The timing is dependant on AD, there are no risks.

CD FY08 Tactical Plan Status Project Activity: Network Upgrades DNS-DHCP Brief Description – Upgrading DNS/DHCP software Deliverables 1.What is it – Upgrading DHCP/DNS to Linux and the latest software also converting all systems to standard builds to be taken over by central server management. 2.When – planned vs actual – the current progress is slightly ahead of the plan 3.Acceptance criteria is testing DHCP and DNS from selected areas of the lab 4.Recipients are all Customers at the lab. Key Milestones 1.What is it – The number of servers converted compared to the total, When – planned vs actual – The plan is to have half the servers converted 3.Impact is high because the current software we are running is unsupported 1.URL – Project Plan Metrics (see the next page for a chart of progress)

CD FY08 Tactical Plan Status Project Activity: DNS/DHCP Upgrade Metrics for DNS/DHCP Upgrade. Issues & Risks 1.The risks are that the current software is so old that we can not receive support from the vendor.

CD FY08 Tactical Plan Status Tactical Plan Issues and Risks Action Items –We need to stay focused on project upgrades even though we have a reduction in FTE’s. Issues and Risks (includes overall budget impact) –Reduction in staff could cause delays in projects. –Fewer resources could cause delays in projects. –There are no serious consequences for CD and stakeholders 1.Fewer resources working on projects due to operational activities 1.Estimated probability of occurring is medium. 2.Estimated impact is that some projects could get pushed in to next year. 3.Fall-back or Contingency plan is to add resources to key projects from other parts of the networking team.

CD FY08 Tactical Plan Status Tactical Plan Status Summary Status Summary –FTE’s for Operations are slightly below the targets. This will be fixed with the new hire. –A reduction in staff for the first 6 months has adversely affected the number of hours spent on projects. –Fewer resources results in a higher percentage of time spent on operations resulting in less availability for projects.