Change Control Overview for the State Technology Resource Center

Slides:



Advertisements
Similar presentations
Project Change Management
Advertisements

McGraw-Hill/Irwin ©2008 The McGraw-Hill Companies, All Rights Reserved SECTION 12.1 PROJECT MANAGEMENT.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Business Plug-In B15 Project Management.
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved. BUSINESS DRIVEN TECHNOLOGY Business Plug-In B10 Project Management.
MyFloridaMarketPlace Roundtable January 21, :00 a.m. – 12:00 p.m. MyFloridaMarketPlace.
Project Management Processes for a Project
MyFloridaMarketPlace CRB Meeting MFMP 2.0 Upgrade Status February 23, 2007.
CHANGE CONTROL PROCESS SEPTEMBER 22, /16/2015 Purpose  a methodical approach for capturing, managing and implementing IT changes  ongoing management.
Request for Service (RFS) Process and Metrics Update June 24, 2008.
Revisions to original presentation are in "Red"1 Available Flow-gate Capacity Stakeholder Kickoff Meeting January 19, 2005.
Federal Acquisition Service 4 th Annual Government Transportation Forum TransPort Integrator Overview.
Weekly Status Reporting Tracking to Build Organizational Capacity.
System Status Update February Overview Review of year to date demand and energy Review of recent system performance Outlook for summer 2012 What.
ME 3.0 to ME 5.0 ME3.0 review scheduled during the Joint NDSWG/NATF meeting in July. There were approximately 180 comments on the ME3.0 paper. Deadline.
GFS Tier 2 Update. GFS A Partnership Focused on the Global Success of GFS with Cisco 2 Tier 2  Tier 2 was designed to be a remote, case based, service.
ENRON TRANSPORTATION SERVICES Customer Service Review ETS Gas Logistics.
MGT 437 Week 4 Learning Team Project Planning Human Capital Paper To purchase this material click below link
Supervisor’s Guide for Employees in Professional Series
Remote Site Initiation Visits
Project Management Business Management.
Managing Expectations and SLA
BUSINESS PLUG-IN B15 Project Management.
BUSINESS DRIVEN TECHNOLOGY
POC Open House Welcome to the POC Open House. My name is _____ and today we will learn about the iPad Courses for the Month of September. If you have any.
Managing Expectations and SLA
11.1 Plan Risk Management The process of defining how to conduct risk management activities for a project Detailed risk planning enhances the overall probability.
BAPI Communities.
Stacking Implementation Plan
Easter Bank Holiday Closures
Easter Bank Holiday Closures
May 2017 Four Year Old Class S&T: red 2 S&T: yellow 3 S&T: blue 4 5 6
SCPS Elementary School Summer Flex Schedule Notification
Human resources announces: electronic employee contract/notification system contract/notification offers will be distributed via utilizing.
Steering Committee Meeting
Training for New District Test Coordinators
Future State Business Process Discovery & Design Recap
Quarterly Business Review – SAMPLE DATA
IBC Review Pathway Approximate Timeline Online status Online“Sub”State
Time management School of Rock.
General Services Department
Procure to Pay Project EUAT Weekly Communication and Training Meeting
IEEE Task Group G Adopted Agenda for January 2001 Session
May 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4s Closing Report for May 2016] Date Submitted:
Oral statements or discussion during the Pre-Bid Meeting will not be binding, nor will they change or affect the IFB or the terms or conditions within.
Lawson ProcessFlow Overview and Actual ProcessFlow Solutions
Action/ Deadline/ Event
Coordinate Operations Standard
System Restoration Coordinator Subcommittee Thursday February 28th
Monday Tuesday Wednesday Thursday Friday Super student Great job Good choices Ready to learn Think about it Teacher’s choice Parent contact Monday.
Managing Multi-source Feedback
Testing Center – Finals
CANNABIS CONTROL COMMISSION
Mrs. Padelford’s Penguins
Attendance Policy 2019 Updates
TGg Report to the IEEE Working Group
IEEE Task Group G Adopted Agenda for January 2001 Session
POC Planning Next Steps
doc.: IEEE <doc#>
JUNE 2010 CALENDAR PROJECT PLANNING 1 Month MONDAY TUESDAY WEDNESDAY
doc.: IEEE <doc#>
Week of October 28- November 1, 2013
AN AGILE DEVELOPMENT METHODOLOGY
Managing Project Work, Scope, Schedules, and Cost
Project Kick-off <Customer Name> <Project Name>
Agenda for Overview SBCUSD Commission-approved Programs
doc.: IEEE <doc#>
Principles of Change Management
UC ANR UCPath Network June 26, 2019 John Fox, Human Resources
Supplier Corrective ACTION RESPONSE REVIEW TRAINING
Doral Academy Open House
Presentation transcript:

Change Control Overview for the State Technology Resource Center Why are we making these changes? As part of the STO’s process improvement plan, Change Control has been identified as the central process with direct feeds to all Data Center critical processes including asset management, capacity planning, problem management and others. Change control is only the first of many process improvements that will be implemented over the next several months. Why is Change Control so important? Change is the number one cause of problems in any technology environment. The changes being implemented will help us coordinate and reduce the risk associated with any change. Although risk can never be totally eliminated, it is our hope that by providing a central point of management and tracking of change effectiveness, we can reduce risk to acceptable levels.

Change Control Process Overview What is the difference between the new process and the old process? All changes must be submitted and approved by Tuesday, close of business, for the upcoming week and weekend. Changes are reviewed for collisions and may be rescheduled depending on other factors. All changes are reviewed by the Change Control Board (CCB). All changes are followed up to ensure the modifications were completed as scheduled. Metrics will be developed and distributed to all shareholders who track the effectiveness of changes. An emergency change process has been defined to allow emergency changes that meet certain criteria, to be implemented in an expedited manner. Use of Magic as the workflow tool for Change Control processing.

Weekly Change Meetings The CCB will conduct a meeting every Wednesday to: Review the schedule of all new changes Review all Minor, Normal and Emergency changes that were processed during the week Review changes that were rejected or failed from the previous weeks schedule Review all successful completions Items generated from this meeting will include: Update to the Magic change calendar Meeting minutes distributed to all Stakeholders Quality metrics tracking process improvements The CCB will conduct a weekly customer conference call: Thursday at 1:00 p.m. The Call-in number is 850-487-9580, SUCOM 277-9580. Review Meeting Minutes and gather customer feedback and concerns Make appropriate changes to the schedule distribute revised meeting minutes to all stakeholders.

Change Control Process Flow

Change Control Process Timeline Weekly Schedule: Monday: Notification: Upcoming Week 1: weekend’s changes and the results of the previous weekends changes when necessary. Tuesday: COB: All changes for the Week/ Weekend opened in the Magic tool for CCB review. Wednesday: CCB Meeting: Review and approve: Changes for the upcoming Week/Weekend, Review completed and failed changes and Re-approve any rejected changes from previous weekend for the upcoming Week/Weekend due to CCB and or Customer Review. Meeting Minutes to all stakeholders Thursday: Weekly Customer Meeting at 1:00 p.m. Dial in: SC:277-9580 or 850-487-9580. revised Minutes sent out. Thurs - Tues 6:00 a.m.: Execute approved changes for the week/weekend. Repeat process.

Change Control Calendar Below is a schedule of all opened change events to be, or which have been, reviewed and scheduled by the CCB. To view the calendar go to: http://etsdreports.myflorida.com/cm_sto_public.htm Emergency Change: Displayed in “red”. Requires ECCB approval and is implemented immediately. Normal Change: Displayed in “yellow”. Requires CCB approval and implemented per schedule. Minor Change: Displayed in “light green”. Requires no approvals and is implemented per schedule.