4
ERCOT Change Management Trey Felton – ERCOT IT

ERCOT Change Management Trey Felton – ERCOT IT. 2 Change Management ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking,

Embed Size (px)

DESCRIPTION

3 IT Operations Change Advisory Board (CAB) The CAB is an IT Operations staff communication forum of all changes being requested for or made to the Production environments. CAB will coordinate the scheduling of CRs in order to mitigate any risks or impacts to the production environments due to scheduling conflicts. Members: –Mgr. System Engineering and Administration (SE&A) –Mgr. Commercial Applications Services –Mgr. Corporate Applications –Mgr. Enterprise Information Systems (EIS) –Mgr. Network –Mgr. Information Systems Security (ISSD) –Mgr. EMMS Production Support –Mgr. Data Base Administrators –Mgr. Facilities –Mgr. Console Operations –Mgr. Release Management –Change Coordinator –Release Coordinators (representing Functional Area).

Citation preview

Page 1: ERCOT Change Management Trey Felton – ERCOT IT. 2 Change Management ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking,

ERCOT Change Management

Trey Felton – ERCOT IT

Page 2: ERCOT Change Management Trey Felton – ERCOT IT. 2 Change Management ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking,

2

Change Management

• ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking, managing and routing a CR for changes made to ERCOT's production environments– OP 6.6.1 currently Classified as ERCOT Limited – SAS 70 compliant– ITIL v3 compliant

Page 3: ERCOT Change Management Trey Felton – ERCOT IT. 2 Change Management ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking,

3

IT Operations Change Advisory Board (CAB)

The CAB is an IT Operations staff communication forum of all changes being requested for or made to the Production environments.

CAB will coordinate the scheduling of CRs in order to mitigate any risks or impacts to the production environments due to scheduling conflicts.

Members:– Mgr. System Engineering and Administration (SE&A)– Mgr. Commercial Applications Services– Mgr. Corporate Applications– Mgr. Enterprise Information Systems (EIS)– Mgr. Network– Mgr. Information Systems Security (ISSD)– Mgr. EMMS Production Support– Mgr. Data Base Administrators– Mgr. Facilities– Mgr. Console Operations – Mgr. Release Management– Change Coordinator– Release Coordinators (representing Functional Area).

Page 4: ERCOT Change Management Trey Felton – ERCOT IT. 2 Change Management ERCOT Operating Procedure 6.6.1 describes the required steps for initiating, tracking,

4

Routine Change Process

6.1.1 Submit/Update

Change Request

6.1.2Change Coor.

submits Change Requests to CAB

6.1.3CAB reviews

Forward Schedule of Changes

6.1.5Review Change

6.1.6Reject CR

6.1.7Approve CR

6.1.8Perform Change

6.1.9Verify Change

Cha

nge

Req

uest

erC

ange

Coo

rdin

ator

Cha

nge

Adv

isor

y B

oard

App

rove

r(IT

and

Bus

ines

s)Im

plem

ente

r Te

amVe

rifie

r Tea

m

6.1.4Change Coor.

Assigns Approver(s), Implementer(s) &

Verifier(s)