About Organizations and Responsibilities

The following organizations in the Information Technology (IT) Services Division will be involved in configuration management activities for the :

§  Architecture Group

§  Operation Group

§  Deployment Group

In addition, two CM entities – the SN Change Control Board and the SN Working Group will provide cross-organizational CM control and coordination.

IT Services Directorate

Architecture Group is responsible for the SN architecture and its components.  It tests and deploys SN components, modifies existing network components, and identifies potential SN enhancements.  Only Architecture Group is authorized to make changes to the SN and its components.  Architecture Group will be responsible for the establishment of the Component Folders.

Operation Group is responsible for the day-to-day operation of the SN.  It maintains the deployed components of the SN and ensures that the SN is up and operational.  The Operation Group Help Desk is the initial point-of-contact for reported network incidents. 

Deployment Group is responsible for deploying field office network hardware and integrating them into the SN.

SN CM Entities

The SN Change Control Board (CCB) and the SN Working Group (WG) will provide cross-organizational CM control and coordination.

SN Change Control Board

The SN CCB will be established as a formal approval authority for changes.  It primarily exists to control changes to the SN architecture (e.g., deployment of a new piece of hardware); however, any SN issue with significant cross-organizational impact should involve the SN CCB.  Written Change Requests (CRs), Impact Assessments (IAs), and meeting minutes will document the CCB’s consideration of an issue.

A Change Request (CR) form will initiate CCB consideration of a change.  Typically, Architecture Group will originate most CRs, but any SN organization may submit a CR to the CCB.  Upon receipt of a CR, the CCB will request each member organization to research the incident and record its analysis on an IA.  These IAs will document the data upon which the SN CCB will have based its decision.  The SN CCB will identify the appropriate change resolution activities and will authorize the affected organizations to perform them.  The SN CCB will be notified immediately when the actual change has been completed and the configuration status information will be updated accordingly.  The decision of the SN CCB and its rationale will be recorded on the CR.  The CR will be closed and copies distributed to each member organization.  Section 4 presents this process in greater detail.  Appendix A contains sample Change Request and Impact Assessment forms.

The SN CCB will be comprised of representatives from the following IT organizations:

·         Architecture Group

·         Operation Group

·         Deployment Group

Each representative must have the authority to commit his or her organization.  Since the SN CCB will consider and resolve cross-organizational issues, its Chair should be a person with the authority to mandate actions to the IT organizations. In addition, since final responsibility resides with the CCB Chair, this person will have the authority to mandate or override decisions made by the CCB.  Typically, the CCB Chair is a representative from the next level of management. Figure 3-1 graphically presents the organization of the SN CCB.  Appendix B contains a template for the SN CCB charter.

Figure 3-1.  SN CCB Organization Chart

SN Working Group

The SN WG is a less formal change control organization that coordinates minor SN changes (e.g., changing settings on a particular router) between Architecture Group and Operation Group.  The SN CCB delegates this authority to the SN WG to provides a more streamlined CM control mechanism for those changes that do not affect multiple SN organizations.  Although the WG is less formal than the CCB, all requests and decisions must still be documented.

An Engineering Request (ER) form submitted to Architecture Group will initiate WG consideration of a change.  Typically, Operation Group will originate most ERs, but any SN organization may submit an ER.  Upon receipt of an ER, Architecture Group will research the request and record its analysis on the ER.  If the request only involves component-level changes, then WG will authorize the changes and the ER will document the decision.  If the incident involves more significant architectural changes, then the WG will originate a CR, and the CR Control Number will be recorded on the ER for traceability.  The ER will be closed and returned to the originator.  Section 4.0 presents this process in greater detail.  Appendix A contains a sample Engineering Request form.

The SN WG will consist of the managers of the Architecture Group and Operation Group organizations or their designated representatives.  The SN WG may be considered a mini-CCB.