Legacy Systems, Business Impacts, Release Management Melissa Spencer and Michiko Quach

From Legacy System to  Modern System e.g. Infrastructure, Network, Servers e.g. Programmers, Processese.g. VFS Online, VHS Modern Platform Modern People & Processes Modern Application

Network Upgrade Project 140 offices – Remaining 40 offices – DONE

Upcoming Legislative Projects HB 1129 – Ferry Vessel Replacement SB 5785 – Display and Replacement of License Plates HB 2100 – Seattle University specialty plate HB 2700 – Breast cancer awareness specialty plate  Effective JANUARY 1, 2015

Post-release triage plan Planned for the day after the monthly application release IT will be stationed at headquarters directly with Vehicle & Vessel support More immediate response Better understanding of the issues reported Reduce business impacts

Application (VFS) Release Management Process PlanningAnalysisDesignCodingTestingRelease Items are planned 2-6 months in advance Application Release – 2 nd Sunday of the month Coding must be complete 3 weeks before the release to allow time for testing After testing, there is time dedicated for code management & release prep

Current Types of Releases Application (VFS) release Server updates Network (CTS) updates Security patches

VFS RELEASE SERVER UPDATES SECURITY PATCHES NETWORK UPDATES (CTS) OFFICE VOLUMES OUTAGE Potential Business Impacts

From Legacy System to  Modern System e.g. Infrastructure, Network, Servers e.g. Programmers, Processese.g. VFS Online, VHS Modern Platform Modern People & Processes Modern Application

Looking Ahead Improve where we can today Modernize our application – Business & Technology Modernization Stabilize – So that we can focus on delivering value to your business