-----------------------------------------------------------------------
  NASA Integrated Services Network Configuration Control Board Procedure

  July 23, 2007

  -----------------------------------------------------------------------

![](media/image1.wmf){width="1.4694444444444446in"
height="0.9736111111111111in"} *NASA Integrated Services Network*

  --------------- -------------------------------------------- -------------
  NASA Integrated                                              
  Services                                                     
  Network                                                      

  NISN                                                         
  Configuration                                                
  Control Board\                                               
  Procedure                                                    

                                                               

                                                               

  Effective: July                                              
  23, 2007                                                     

                                                               

  Contract:                                                    
  NNM04AA02C                                                   

                  Approved by:                                 

                  Elizabeth Paschall Date\                     
                  NISN Project Manager\                        
                  NASA Marshall Space Flight Center            

                  Approved by:                                 

                  Bradford Torain Date\                        
                  NISN Deputy Project Manager\                 
                  NASA Goddard Space Flight Center             

                                                               

                                                               

                                                               

                                                               
  --------------- -------------------------------------------- -------------

Contents

**1.** **Purpose [1](#purpose)**

2\. Scope [1](#scope)

3\. References [1](#references)

4\. Definitions [1](#definitions)

5\. Membership and Responsibilities:
[2](#membership-and-responsibilities)

5.1 CCB Chair [2](#ccb-chair)

5.2 Voting Members [2](#voting-members)

5.3 Secretariat [2](#secretariat)

5.4 Requester [3](#requester)

5.5 Sponsor [3](#sponsor)

6\. Procedure [3](#procedure)

6.1 Criteria for CCB [3](#criteria-for-ccb)

6.2 Information Required for Presentation to the CCB
[5](#information-required-for-presentation-to-the-ccb)

6.3 CCB Procedure Steps [6](#ccb-procedure-steps)

7\. Quality Records [6](#quality-records)

8\. Change Log [7](#change-log)

Appendix A. CCB Request Form [8](#ccb-request-form)

Appendix B. CCB Controlled Documents [10](#ccb-controlled-documents)

NISN Configuration Control Board Procedure

# Purpose

The purpose of this procedure is to provide guidance in the
administration and processing of National Aeronautics and Space
Administration (NASA) Integrated Services Network (NISN) Configuration
Control Board (CCB). This procedure shall outline requirements, standard
protocols, and process steps necessary in obtaining CCB approval.

# Scope

This procedure applies to all civil servant and contractor personnel
involved in the NISN Project request and approval process. All items
included in Appendix A are under configuration control of the NISN CCB,
as well as individual service requests meeting the criteria in Section
6.

# References

a.  NISN Configuration Control Board Membership and Procedures January
    1998

b.  CCB Guidelines October 1997

c.  4500-FORM-031, NISN CCB Change Request Form

# Definitions

a.  CBACS -- Common Badging and Access Control System

```{=html}
<!-- -->
```
d.  CCB -- Configuration Control Board

e.  HEMI -- Headquarters Enterprise Messaging Initiative

f.  MOVE -- Mission Operations Voice Enhancement

g.  NISN -- NASA Integrated Services Network

h.  NSSC -- NASA Shared Services Center

i.  NSR -- NISN Service Request

j.  NESC -- NASA Engineering and Safety Center

k.  PSLA -- Project Service Level Agreement

l.  SLAN - Secure Local Area Network

m.  SONET -- Synchronous Optical Network

n.  UNITeS -- Unified NASA Information Technology Services

o.  VoIP -- Voice Over Internet Protocol

p.  WDM -- Wavelength Division Multiplexing

# Membership and Responsibilities:

The NISN CCB is chaired by the NISN Project Manager and includes the
Deputy Project Manager and leads from the various NISN organization
groups. The CCB Chair may identify individuals to evaluate certain
change proposals, upon recommendation by the change sponsor. These ad
hoc members provide subject expertise; however, they do not vote on
change proposals.

The membership of the CCB is as follows:

## CCB Chair

The NISN CCB Chair is the NISN Project Manager, or in their absence the
Deputy NISN Project Manager. It is the responsibility of the CCB chair
to evaluate inputs and issues from voting members, to ensure issues
between the change sponsor and the voting members have been resolved,
and to assess whether the change proposal should be reviewed by other
governing bodies. The CCB Chair also has the final approval authority
for the CCB item once the CCB item has been presented and a vote has
been received.

## Voting Members

It is the responsibility of each voting member to assess the change
proposal's effect to their respective area, to cast votes in a timely
manner and to identify and document specific issues with the proposed
changes. Voting Members include the following:

a.  Deputy NISN Project Manager

```{=html}
<!-- -->
```
q.  Network Services Group Leads

r.  Business Management Group Leads

s.  Customer Interface Group Leads

t.  Russian Project Manager

u.  Security Managers

v.  Operations Managers

## Secretariat

The Secretariat is a non voting member. It is the responsibility of the
NISN CCB Secretariat to:

a.  record and archive minutes of CCB minutes

b.  distribute CCB items for voting members review

c.  solicit votes

d.  notify CCB members of CCB disposition

e.  archive CCB-approved material

## Requester

A requester can be a customer or the NISN support contractor. Requester
will submit CCB topic by using 4500-FORM-031 (see Figure 1). It is the
responsibility of the CCB Requestor to:

a.  identify items for approval by the CCB

```{=html}
<!-- -->
```
w.  secure a NISN civil servant sponsor for the item

x.  assist in developing change proposal material

y.  coordinate changes with subcontractors, vendors, and local center
    support

## Sponsor

A NISN civil servant sponsor is required on every proposed change. It is
the responsibility of the sponsor of the proposed change to:

a.  set up review meetings

```{=html}
<!-- -->
```
z.  coordinate presentation material

a.  circulate materials for membership review

b.  solicit comments and issues from all NISN personnel to determine its
    effects and/or benefits

c.  incorporate comments and resolve issues with the voting members and
    chair

d.  ensure changes are not made until the CCB approves the proposal

e.  implement the change once approved

f.  report back to the CCB once the change is implemented

# Procedure

## Criteria for CCB

a.  A NISN Service Request (NSR) that:

```{=html}
<!-- -->
```
1.  has nonrecurring costs that exceed \$100,000.00. Exception to this
    is standard ViTS rooms which meet the standard architecture, but may
    exceed \$100,000.00 limit due to equipment needs.

2.  is sensitive, high profile, and problematic, technically or
    otherwise

3.  requires contract modifications or involves procurement approaches
    different than the standard for the service

4.  is for an activity that should be treated as an **internal** NISN
    project (multiple service requests and/or locations)

5.  is for a new NASA location/program/project/mission directorate,
    particularly those requiring multiple services and is provided
    Agencywide (ex. MOVE, NSSC, CBACS, HEMI, NESC)

6.  is for non-NASA customers

7.  involves joint responsibility with other service providers (other
    NASA contractors or projects or international partners)

8.  involves any implementation that includes a NISN demarcation point
    which is different than the standard demarcation point for the
    service

9.  has service or network support implementation with non-standard or
    custom elements (equipment, provisioning, operations, or security)

10. request services not currently being provided by NISN. An example of
    this is EOS performance monitoring capability.

```{=html}
<!-- -->
```
g.  New types of service. Examples include, but are not limited to
    Secure Local Area Network (SLAN) and Voice over Internet Protocol
    (VoIP).

h.  Infrastructure architecture and demarcation interface changes.
    Examples include, but are not limited to WDM, Dense WDM, SONET, and
    10 Gigabit Ethernet.

i.  Procedures and documentation changes that require NISN management
    review and approval. NOTE: Minor changes/edits to existing
    procedures can be taken directly to the NISN CCB Chair with a
    completed CCB Change Request Form for approval out of the normal CCB
    process.

j.  Operations and service documentation and applications. See Appendix
    B for a current list.

k.  Any item that affects the NISN Security Posture and/or the
    Certification and Accreditation status such as but not limited to:

    1.  New service offering or total removal of a service offering
        (also impacts the NSD)

    2.  Architecture changes (new technology or non-standardized
        architecture)

    3.  Any connection which bypasses existing Intrusion Detection
        devices via encryption or physical connection

    4.  Any NSR which has an initial Security Risk Assessment rating of
        High

l.  Topic requested by the NISN Project Manager, Deputy Project Manager
    or NISN Service Owner as requiring CCB approval.

## Information Required for Presentation to the CCB

Based on the nature of the CCB item, the information needed for
presentation to the CCB varies.

a.  All CCB Items

```{=html}
<!-- -->
```
1.  Brief description of change and engineering solution, including the
    service affected

2.  Points of Contact including the CCB Requester, the CCB sponsor, and
    the NISN customer, if different from CCB Requester

3.  List of required document changes and new equipment , including
    security plans and operations procedures

4.  Cost and funding organization

5.  Pre-installation test information

6.  Test Plan

7.  Implementation Plan including service outage that affects other
    customers not related to the requested work

8.  Coordination data: who, where, what, when, how

9.  Schedule for work implementation

10. Issues and concerns

```{=html}
<!-- -->
```
m.  Additional information required for new NISN Service and
    Infrastructure architecture and demarcation interface changes

```{=html}
<!-- -->
```
1.  Service description to be included in the NISN Services Document

2.  Definition of the standard customer demarcation point

3.  Service performance level guarantees and metrics

4.  Operations concept

5.  Pricing methodology, both implementation and sustaining

6.  Changes in any existing NISN process, procedure, or documentation

7.  Service announcement to be sent to customers

## CCB Procedure Steps

The NISN CCB is held on the last Wednesday of the month. An emergency
CCB can be scheduled as needed, but it is encouraged that planning be
incorporated into the project schedule to allow for CCB review to be
held at the normal time. The steps included in the CCB procedure are:

a.  The CCB requester and sponsor prepare all relevant information and
    perform all coordination efforts with the customer to obtain
    consensus with the affected community.

```{=html}
<!-- -->
```
n.  If the change fits the criteria referenced in Para 6.1 (f) above, IT
    Security must enter change in ITSC for bi-monthly reports to HQ.

o.  The CCB sponsor submits the CCB request form and presentation to the
    Secretariat to be placed on the agenda for discussion. The
    presentation must be submitted 24 hours prior to the NISN Status
    Meeting (normally held each Wednesday).

p.  The CCB sponsor shall present the change to the NISN CCB Members for
    review and discussion.

q.  Voting members have one (1) week to review and submit comments to
    the CCB secretariat.

r.  The CCB Chair approves, approves with comments, or disapproves
    change based on data presented and membership votes.

```{=html}
<!-- -->
```
1.  If the requested CCB item is approved with comments, requester shall
    make the required changes prior to implementation.

2.  If the requested change is disapproved and it is a NSR, sponsor
    shall inform the affected customer of the NISN CCB decision. If the
    disapproved change is an internal NSR, requester shall rework the
    change and reboard it at the next CCB.

3.  If the requested procedure or document is disapproved, requester may
    revise based on CCB comments or cancel the effort.

# Quality Records

  ---------------------------------------------------------------------------------------------
  **Record        **Record\     **Storage    **Storage    **Index    **Retention   **Disposal
  Description**   POC**         Media**      Location**   Method**   Period**      Method**
  --------------- ------------- ------------ ------------ ---------- ------------- ------------
  Member votes    Secretariat   Electronic   NISN Website Topic      Duration of   Delete
                                                                     contract      

                                                                                   

                                                                                   
  ---------------------------------------------------------------------------------------------

# Change Log

  ------------------------------------------------------------------------------------
  Status                Document   Effective   Revision Purpose
  (Baseline/Revision/   Revision   Date        
  Cancelled)                                   
  --------------------- ---------- ----------- ---------------------------------------
  Baseline              0          05/31/05    Original issuance of procedure

  Revision              A          07/17/06    6.1 Criteria for CCB a.1 changed for
                                               ViTS exception.

  Revision              B          11/03/06    6.1 Criteria for CCB add paragraphs a.4
                                               and f for security

  Revision              C          07/23/07    6.1 d Added note, 6.1 f Added 1-4 for
                                               security criteria, 6.1 g. Added NISN
                                               Project Manager and Deputy Project
                                               Manager, Appendix A & B updated
  ------------------------------------------------------------------------------------

######## CCB Request Form

![](media/image2.wmf){width="6.35in" height="7.591666666666667in"}

Change Request Instructions

1.  Assigned by CM

2.  Date CR was submitted

3.  Self explanatory

4.  Place Title, NSR \# and Requesting Customers name in this block

5.  Check emergency if out of cycle CCB is required. All others are
    routine

6.  Level I change affects 1 service or process; Level II affects
    multiple service(s) or processes

7.  List the CCB date requested

8.  List the main service or process affected or the only service or
    process affected

9.  List all other service(s) or processes affected

10. List controlled comments that are affected by this change

11. Short description explaining the change request and list attachments
    if applicable

12. Self explanatory

13. Self explanatory

14. Self explanatory

15. Self explanatory

16. Self explanatory

17. Self explanatory

######## CCB Controlled Documents

The following items are under control of the CCB, and all changes to
them require CCB coordination and approval:

a.  The NISN Services Document, including the baselined list of NISN
    services

```{=html}
<!-- -->
```
s.  NISN Service Request process

t.  Project Service Level Agreement (PSLA) (Structural changes only)

u.  NISN service owner listing

v.  NISN Customer Interface Group assignments

w.  Funding methodology

x.  Service pricing methodology

y.  NISN technology roadmap

z.  Standard Operating Procedures (including but not limited to the
    trouble ticketing, activity and outage notification process)

a.  Application access request form

b.  NISN input to Agency Enterprise Architecture

c.  NISN Service EA Overview

d.  Desktop Appliance Video Conference (DAV)

e.  NASA Collaborative Infrastructure (NCI) Resource Scheduler (NRS, aka
    VCRS)

f.  Voice Conferencing Online Registration System (ORS)

g.  NISN Home Page (structural changes only)

h.  NISN Service Request System (NSRS)

i.  Performance Reporting Requests from Customer

j.  Customer Survey

k.  Activity & Outage Posting Notification System (AOPNS) (Structural
    changes only)

l.  Mission Outage Notification System (MONS) (Structural changes only)

m.  Flash Report (Structural changes only)

n.  NISN Service Announcement Tool (NSAT) (Structural changes only)