information technology division y2k status briefing december 3, 1999 9:30 a.m.- noon

45
Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon Pendleton Room, Michigan Union

Upload: gitel

Post on 09-Jan-2016

31 views

Category:

Documents


0 download

DESCRIPTION

Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon Pendleton Room, Michigan Union. Today’s Agenda. University perspective and coordination ITD products and services Rollover and contingency management Communications and problem reporting - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Information Technology DivisionY2K Status Briefing

December 3, 19999:30 a.m.- noon

Pendleton Room, Michigan Union

Page 2: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Today’s Agenda•University perspective and coordination

•ITD products and services

•Rollover and contingency management

•Communications and problem reporting

•Departmental guidelines

•Questions and answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 3: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Y2K is “Necessary”

“Technology… brings you great gifts with one hand, and it stabs you in the back with the other.”C.P. Snow, New York Times, 15 March 1971

“For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled.”Richard Feynman, What Do You Care What Other People Think?

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 4: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

CIO Perspective

•U-M Y2K priorities per 5/25/1999 memo

1. health and safety

2. health care and patient services

3. maintenance of research specimens

4. delivery of teaching and learning

5. security and preservation of facilities and equipment

6. maintenance of community/U-M partnerships

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 5: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

CIO Perspective

•U-M readiness activities over the last 12 months remediation, upgrade, replacement, and testing business continuity and contingency planning quality assurance communications

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 6: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

ITD Perspective•ITD services focus on

priority 1 911 and telephone services priority 4 network, e-mail, instructional systems,

administrative systems priority 6 telephone and data services

•ITD is major service provider in Y2K rollover with DPSS Plant Housing Medical Center

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 7: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

How Prepared Are Enterprises to Face the Y2K Crisis?

Watch Out for That Cloud!

SOURCE: Gartner Group (http://www.gartnerweb.com)

<0.5% embedded device failures

Total global cost of compliance: > $1 trillion,

< $2 trillion

Total software fix cost: $300-600 billion

Limited, short duration government outages

Minor utility outages of less than 1 week

<0.1% of all enterprises fail

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 8: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Y2K Rollover Schedule

•Mon 1/3 University Housing move-in

Student registration begins

Some professional school classes begin

•Wed 1/5 First day of classes

•Fri 1/7 Financial aid disbursement

•Mon 1/10 First full week of classes

First biweekly payroll production run

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 9: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

U-M Y2K Response Center Responsibilities

•Coordinate U-M Y2K incident response and communications

•Ensure a university-wide view of Y2K conditions

•Build on current practices

•Insure Y2K incidents are resolved quickly

•Provide a well-trained and properly supplied center

•Coordinate communications for a comprehensive view of Y2K issues being addressed at U-M

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 10: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Y2K Communication Plan•“Bug Bytes”

published in University Record and Michigan Daily www.year2000.umich.edu

•University toll-free Y2K information number 1-877-UM-Y2K-OK

•Letter to “3D list” and unit representatives

•Advertisement in University Record

•Mailer to students’ permanent addresses

•FASAP Y2K “brown bags”This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 11: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

ITD Products, Services, and Units

•Products computing infrastructure - OM/DSC legacy administrative systems - PD&D M-Pathways systems - Pathways Project UMCE services - PD&D voice-data-video services - OM/ITComm

•Services 4-HELP consulting - PD&D administrative systems hotline - OM/DSC network operations - OM/ITComm

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 12: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

ITD Information Resources

•U-M Y2K home page “bug” icon displayed on www.umich.edu www.year2000.umich.edu

•ITD compliance status www.year2000.umich.edu/itdcompliance.html

•ITComm product and service information www.itcom.itd.umich.edu/y2k/

•Merit Network compliance status www.merit.net/year2000/

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 13: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Computing InfrastructureChallenges

•Computer room facilities infrastructure Halon fire protection system key card access control system air conditioning power distribution and UPS systems network

•Arbor Lakes Data Facility has UPS and generator•CPUs, disks, tapes, controllers, consoles

server Processors, disks, consoles firmware and microcode for all equipment

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 14: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Computing InfrastructureChallenges

•Operating System Software MVS, AIX, NT

•Teleprocessing systems IMS, CICS, TSO, Tuxedo, Roscoe

•Data Base systems IMS, DB2, Oracle

•System management Tools scheduling systems output management systems language environments

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 15: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Computing InfrastructureActions Taken

•Built mainframe and server Y2K test environments

•Assessed Y2K compliance and corrected deficiencies replaced key card system and upgrading network software upgraded hardware firmware and microcode replaced communication controllers upgraded MVS and AIX Operating System Software upgraded IMS, DB2, Oracle, CICS, TSO, Tuxedo, Roscoe upgraded scheduling systems, output management systems,

mail systems, language environments, sorts, etc.

•Re-checked vendors for changes to Y2K compliance This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 16: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Computing InfrastructureRisks

•Simultaneous failure of both University and Detroit Edison power

•Failure of UMNET network or subnet serving Data Systems Center

•Non-compliant components missed during remediation efforts or inaccurately reported by vendors

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 17: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Computing InfrastructureRisk Management

•Generator on site if both U-M and DetEd power fail

•12/31 9pm DSC staff on-site

•12/31 10:30pm Production processing and special

backups completed

•12/31 11:00pm Bring down online systems, batch

initiators, development databases

•1/1 12:30am Run Y2K test suites

•1/1 1:00am Analyze results and fix problems

•1/1 2:30am Bring systems up, start productionThis is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 18: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions and Answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 19: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Legacy Administrative SystemsChallenges

•Identify non-compliant applications and systems central departmental (client-funded)

•Acquire and retain skilled technical human resources for remediation

•Partner with user office staff for testing and approval

•Work with vendors to remediate purchased software

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 20: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Legacy Administrative SystemsActions Taken

Remediation and unit testing of non-replaced administrative applications

Integrated systems testing for “first business week” and other significant events

Business continuity and unit contingency planning

Communication planning

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 21: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Legacy Administrative SystemsRisks

Environmental outagesDependence on vendorsLower U-M Y2K priority for administrative systems

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 22: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Legacy Administrative SystemsRisk Management

•Normal production and problem reporting procedures•Y2K Response Center communications•Contingency plans coordinated with customers

e.g. Registrar’s Office

•Identification of critical staff and alternate locations for work•Monitoring of impact of regional and international Y2K fallout•Monitor vendor compliance•DSC administrative hotline 763-4000

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 23: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions and Answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 24: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

M-Pathways Administrative SystemsChallenges

•Develop a Y2K test environment

•Test multiple infrastructure components at correct version levels

•Test version compatibility of vendor software

•Financial and HE applications at different version levels

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 25: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

M-Pathways Administrative SystemsActions Taken

•Dedicated test environment with all technical components as of 1/1/2000•Installed all version levels required for 1/1/2000 and tested with rollover dates•Tested critical business functions for Financial and HE applications with appropriate version levels and infrastructure components

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 26: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

M-Pathways Administrative SystemsRisks

•Power or network not available•Lower U-M Y2K priority for administrative systems

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 27: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

M-Pathways Administrative SystemsRisk Management

•Staff will test system availability on 1/1/2000 and will follow the campus-wide plan created to address physical component outages

•M-Pathways Help Desk 936-7000 open 12/27 to 12/30 8am - 5pm

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 28: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions and Answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 29: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

UMCE ServicesChallenges

•Computer Center facility infrastructure old North Campus Computing Center machine room in Argus Building

•Mixed hardware environment (Sun, IBM, Dell) CPUs, disk, tapes, consoles, etc.

•Server operating system software Solaris, AIX, NT

•Vendor and “open system” application software server and client-side Kerberos, AFS, Novell, IMAP, Telnet, etc.

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 30: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

UMCE ServicesActions Taken

•Assessed compliance of installed base review all vendor sites and updates modified, patched, upgraded as needed

•Created Kerberos DCE Y2K rollover test cell rolling over all systems in Y2K test cell

•Moved production servers to new center

•Replaced complete systems electronic directory - X.500 to Open LDAP transparent change when possible during 7 x 24 operations

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 31: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

UMCE ServicesRisks

•Work still in progress IBM review of UMCE preparedness rollover of ABS, UMCE subscription, DNS, GPCC, mail

clients Mulberry and Eudora upgrade of pre-production Oracle Solaris web interface

applications identified during review

•Interdependent system complexities components missed in cross system matrix unplanned shutdown of distributed systems

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 32: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

UMCE ServicesRisk Management

•Generator automatically engages if DetEd power fails

•764-HELP consulting services• open 12/27 - 12/30 1pm - 5pm, voicemail/page other times

•12/15 Install some redundant equipment

in alternate space

•12/27 - 12/30 Staff on-site to complete work

•12/31 9:00pm Production back-ups completed

Staff on-site during rollover

•1/1 6:00am Staff on-call, remote monitoring,

on-site within 30 minutesThis is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 33: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions and Answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 34: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Voice-Data-VideoChallenges

•Many legacy systems and LANs - up to 15 years old•Vendors not always cooperative•Over 20 million lines of code in SL-100 voice switch•Video scheduler non-compliant•Multiple legacy outboard processors•Inability to run real-time test•Emergency power for remote equipment•Y2K compliance versus upgrades

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 35: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Voice-Data-VideoActions Taken

•100% network vendor response on Y2K compliance•Develop rollover and contingency plans•Large-scale upgrades to ensure Y2K compliance•SL-100 Y2K compliance testing•Site preparation and prioritization•Complete network evaluation•Backbone upgraded•Cabletron electronics upgraded or replaced•Communication with all “at risk” units

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 36: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Voice-Data-VideoRisks

•Inter-system dependencies•External communication dependencies•Power dependencies•Vendor overload

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 37: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Voice-Data-VideoRisk Management

•Rollover plans•Contingency plans•Vendor Y2K contracts•Staff education

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 38: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions and Answers

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 39: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

U-M Y2K Response Center andMajor Service Providers

U-M Y2KResponse Center

ITD PlantHousingDPSS

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Hospital

Page 40: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

U-M Y2K Information Flow

Dial-0Operators

StatusBoard

DPSSDispatch

PressRoom

EmergencyOperations

Center

OtherService

Providers

MajorService

Providers

ConferenceBridge

1-800 auto-attendant

Hotline

InformationTeam

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

UniversityCommunity

Page 41: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

U-M Y2K Information Flow Schedule

•Response Center polls major service providers every 30 minutes updates EOC status board every 30 minutes

•Information Team updates Dial-0 operators and 1-877 status line every 2 hours holds conference call with service providers every 2 hours

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 42: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

ITD Command Centers•Data Systems Center - administrative computing•Network Operations Center - voice, data, video

UMCE - e-mail, directory, web 4-HELP consultants

•DSC, NOC and other ITD units have on-site and on-call staffing plan customer trouble reporting procedures rollover operations schedule contingency plans fan-out information plan

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 43: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Customer Problem Reporting

•ITD consulting - general problems 764-HELP

•DSC administrative hotline - administrative systems 763-4000

•M-Pathways hotline 936-7000

•University dial-0 operators - general information 764-1817

•Y2K information line 1-877-UM-Y2K-OK

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 44: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Departmental Guidelines

•Back up critical computer files•Catch up on e-mail and phone calls•Clear unnecessary voicemail and e-mail messages•Coordinate with department LAN administrators•Shut down and unplug non-critical desktop systems•Secure critical desktop systems with surge protectors•Report problems per usual department procedures or to ITD 764-HELP•Check 1-877-UM-Y2K-OK for latest information

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act

Page 45: Information Technology Division Y2K Status Briefing December 3, 1999 9:30 a.m.- noon

Questions & Answers

José-Marie Griffiths

Al McCord

Bill Aikman

Dorothy Stewart

Gloria Thiele

Mike Loviska

Sandy Colombo

Dan Kjos

This is a Year 2000 Readiness disclosure under the Year 2000 Information and Readiness Disclosure Act