Home :: Content

System Health - Rolling System and Network Availability Graphs - Phase I


SysHealth-NetAvail.jpg
Quick View
Summary: 

Develop and implement a mechanism for measuring and reporting system and network availability on a rolling basis over the last 6 months. The graphs will be available via a link on the System Health page. Phase one will show system and network availability at an aggregate level. Subsequent phases will provide drill down capability to specific system or network components. It will also provide access to view historic availability.

Resource requirement:

  • 1 - SysHealth Consultant (Care)
  • 1 - Statistics gatherer (Ops)
  • 1-  SysHealth Development(Dev/CORDA)

 

Start Date: 
April 8, 2009
Go Live: 
June 30, 2009
End Date: 
July 31, 2009
Current Milestone: 
Post-production cleanup -- 7/31/2009
Project Plan: 
Project Schedule
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Lead Customer: 
Adrian Sannier
Project Manager: 
Mike Brown
Contact for more information: 
Dave.McKee@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Dave McKee
More Info
Source: 
Internal
Priority: 
Needs Prioritization
Scope: 

System availability of critical ASU systems:

  • Blackboard
  • Blackberry email
  • CRM Self-Service
  • Exchange email
  • Gmail for ASU
  • My ASU
  • My Apps
  • My Docs
  • My Files
  • Outlook Web Access
  • Sakai
  • Other?
  • -------------
  • Supporting Systems
  • AFS
  • CIFS
  • CRM
  • HRSA

Availability of critical ASU network components.

  • Internet 1
  • Internet 2
  • Data Center network
  • Links between campuses
  • Voice Systems
  • Other? 
Mockups: 
Revised System Health Page
All Milestones and Schedule: 

Phase I:

  • Project Approval -- Completed
  • Project Kick-Off Meeting -- Completed
  • Develop Project Plan - Completed
  • Research Industry Standards and ASU Measurement Points -- Assigned to: Mike Brown - Completed
  • Identify list of critical (Oxygen) systems to be reported on --Assigned to: Mike Brown - Completed
  • Review Research Results -- Assigned to: Team - Completed
  • Create Mock-up System Health -- Assigned to:  Nathan Corwin - Completed
  • UTO Feedback -- Assigned to: Mike Brown -Completed
  • UTO Prioritization -- Assigned to: Mike Brown - by 6/21/09
  • Refine requirements --  Assigned to: Team - Complete
  • Request/Allocate resources -- Assigned to: Mike Brown - Complete
  • Determine costs (if any) -- Assigned to : Mike Brown - Complete
  • Determine data source and measurement mechanism -- Assigned to Zeph -- Complete
  • Determine presentation methodology --  Assigned to: Venkatesh - Complete
  • Build graphs using production data -- Assigned to: Venkatesh - Complete
  • UTO approval -- Assigned to: Mike Brown -6/29/2009; 7/7/2009  Complete
  • Migrate Database DEV to PROD -- Assigned to Rick Strong & Venkatesh - 7/9/2009--Complete
  • Implement in production via System Health (Go-Live) -- Assigned to: Nathan Corwin - by 7/10/2009-- Completed
  • Post-production cleanup -- Milestone to be met by July 31, 2009  (Assigned to: Team )
  • Post Implementation Review -- Milestone to be met by July 31, 2009  (Assigned to:  Team)

Phase II:

  • Add links for individual buildings
  • Develop mechanism for accounting for scheduled maintenance periods for Managed Service metrics.

Phase III:

 

  • Identify Vital System application reliabilty measurement metrics.
    • Service reachability/reliability
    • Correlation of multiple Server and Server process reliability
  • Add Vital Systems
  • Add availability & bandwidth graphs for each building & vital system.
Deliverables: 
  • Provide a mechanism for measuring and reporting system and network availability on a rolling basis over the last 6 months via a link on the System Health page.
  • Graphs will depict an average availability over the previous 6 month period.
  • Phase one will show system and network availability at an aggregate level.
Links
Cisco Presentation on Network Availability
Internet1 NOC
Internet2 NOC
Sample: Internet2 Graphs-LA
Sample: Internet2 IP Layer Nationwide
Sample: Internet Traffic Report
Sample: Cenic NOC
Sample: SUNYnet
Sample: Michigan State University
Syndicate content