Collaborative & Participatory Governance

Executive Order 2012-880 established the Technology Advisory Council (TAC) whose responsibility is to assist the CIO in appropriately aligning business requirements and technology investments. It also provides a forum for agency input on technology direction. The TAC began meeting in January 2013 and is comprised of business, financial, and IT staff as chosen by executive branch cabinet leadership. The TAC serves to improve coordination, accountability, and oversight of information technology across the executive branch of state government.

Technology Advisory Council (TAC)

Technology Advisory Council (TAC) workgroups/subcommittees are formed as needed to serve a specific need as defined by the TAC. Membership for each consists of a subset of TAC member volunteers. Below is a listing of current workgroups/subcommittees, their charge, and a short status.


Link to Additional Information:



Information Technology Standards Committee (ITSC)

In 2014 the long-standing Enterprise Architecture and Standards Committee (EASC) was repurposed as the Information Technology Standards Committee (ITSC) and designated as a subcommittee of the TAC. The ITSC serves as the enterprise governing body for the establishment and control of executive branch IT standards. Agencies, including COT, can request additions or modifications to existing standards to support new agency needs, to upgrade outdated standards, and/or to keep current with vendor offerings.


Link to Additional Information:



Capital Projects Status

KRS 45.818 states "The Executive Director of the Commonwealth Office of Technology shall provide to the Capital Projects and Bond Oversight Committee at its January, April, July, and October regular meetings, a status report on any information technology system not yet completed which received line item authorization by the Kentucky General Assembly …” Below is a subset of that quarterly report information


Link to Additional Information:



Change Management

Standardized methods and procedures for the approval of changes enacted upon the enterprise infrastructure and applications providing service to the public help minimize the impact of change-related incidents upon IT service quality and delivery.

The Request for Change (RFC) is assigned to the Change Management team. Upon receipt of notification from the ITSM system, a member of the team performs an initial review for accuracy and completeness of data. During the assessment phase, the request is reviewed by the Change Management team. The Change Evaluator confirms that all relevant information is provided, so that Approvers have a clear understanding of the work to be performed and its subsequent impact. If the Requestor fails to provide any of the required information, the RFC will be rejected. The approval phase secures authorization from the appropriate organizational approvers and the CAB, as determined by the Change Evaluator. Within the scheduling and notification phase of the request lifecycle, the approved RFC is scheduled and implemented, and notification of the expected implementation date is communicated to stakeholders and affected users. During the closure phase, the change management process continues with confirmation from the Change Coordinator that the RFC has been implemented. 

The Change Management team is responsible for coordinating a Post Implementation Review on RFC that meet one or more of the following conditions:

1) Created an unknown/unexpected impact;
2) Failed;
3) Was not properly communicated;
4) Resulted in greater impact than indicated from the review process.



  • Change: the addition, modification, or removal of approved, supported, or baseline hardware, network, software, application, environment, system, desktop build, or associated documentation that could have an effect on IT services.
  • Normal Change: a change that follows the full, predefined review by the Change Manager, and the Change Advisory Board (CAB), when required.
  • Emergency Change: a change that must be implemented immediately and cannot be scheduled, Emergencies are situations where critical systems are in a state of failure, or are in an imminent state of failure if action is not taken.

Link to Additional Information:


This page was last modified 6/14/2017 3:58 PM

COT Metrics Home Page



Questions? Comments?

If you have questions or comments, please contact the COT WebMaster.