1. Oregon Department of Transportation Daylight Saving Time Solution Path

2. ODOT Solution Path ODOT’s Solution Path definition is: the systems, network, devices or services must remain functional, that is, enough of the expected functionality must be present, correct, and usable to continue to meet ODOT’s mission.

3. ODOT Solution Path – Assess the Current Environment ► Assess current situation  Impacts to systems  Impacts to applications  Impacts Devices  Impacts to the Network ► In-scope impacts work in coordination with SDC ► Out-of-scope impacts ODOT to remediate

4. ODOT Solution Path – Patches/Fixes ► Researching options for fixing issues ► Testing available fixes ► Validate with vendor regarding COTS. ► Collaborating with SDC & AD groups for Servers, Security, Mainframe, Linux and Unix required changes/upgrades/patches. ► Applying tested patches and fixes for at risk items.

5. ODOT’s Solution Path - Communication ► Communications Plan  Communications to ODOT staff and the Public  Inside ODOT article  ODOT Help Desks to communicate recommendations to ODOT Staff  Staff Command Center & Help desks during DST change and validate system availability.  Request computers to remain powered for SMS delivery packages.

6. ODOT Solution Path - Prepare Customers ► Leave your computer powered on when you go home, but log off. ► When organizing a meeting during the Extended DST period, write the correct meeting time in the subject line or body of the message. For example, include the following text in the subject line or body of the message:  Project planning meeting – 8:30 a.m.  Consider any appointments in the Extended DST period to be suspect. When in doubt, verify the correct time with the organizer.  Consider printing out your weekly calendars prior to the Extended DST period. (March 9 th )

7. ODOT Solution Path - Schedule ► 2/15 In-scope server patching on-going via SDC staff ► 2/15 Begin testing Exchange patching scenarios on AD (pre-prod) network (pre-prod) network ► 2/20 Begin Blackberry patching ► 2/21-2/26 Workstation DST patching (via SMS) ► 2/21-2/26 Workstation Outlook Calendar Update Tool (via SMS) ► 2/23 Begin DST patching out-of-scope servers (via SMS and manual) ► 3/1 Exchange CDO patch (manually to all Exchange servers) ► 3/1-3/3 Exchange Calendar Update Tool (to be run against all mailboxes) ► 3/11 DST begins at 2:00 A.M. Begin extended DST ► 4/1 End extended DST.