ARMY CONFIGURATION CONTROL BOARD CCB

1
ARMY CONFIGURATION CONTROL BOARD
(CCB) September 25, 2001 Ms. Carole
Johnson CCB Secretary
2
ARMY CONFIGURATION CONTROL BOARD

• Army CCB developed to manage the standard
  configuration of the modern DCPDS including Army
  unique and infrastructure changes.
• Process has changed since MFAD became proponent.
• Army CCB not part of normal problem reporting
  process.
• A few problem reports become CPMS CCB items.
• CPMS CCB Process
• Army CCB membership appropriate level?
• Current initiatives under development (FASCLASS
  II, APMS XXI, SPRING) considered approved and
  beyond Army CCB process.
• Clinger-Cohen must be addressed for approved
  initiatives.
• Prioritization considerations--funding,
  development order.

3
ARMY CONFIGURATION CONTROL BOARD

• Next Army CCB meeting
• Thursday, November 15 (10 a.m. - 12 noon EST)
• (NOTE Meeting subsequently changed to November
  14 at 1 p.m. EST)
• Concept descriptions submitted to
• MFAD by Wednesday, October 17
• Manual email approach to be used again
• Developing email/web-based process for
  submitting, reviewing, and commenting on concept
  descriptions.

4
ARMY CONFIGURATION CONTROL BOARD

• Roles and Responsibilities
• Army CCB Responsibility
• Recommend action on proposals and system change
  requested from submitters.
• Validate requests for commercial off the
  shelf/non-developmental items equipment and
  software.
• Recommend funds.
• Prioritize requirements.
• Ensure security is not compromised.

5
ARMY CONFIGURATION CONTROL BOARD

• Roles and Responsibilities
• Army CCB Committee Member Responsibilities
• Review/comment on concept descriptions to be
  presented at CCB meeting.
• Focal point within his/her organization to ensure
  agenda items are fully coordinated and approved.
• Attend (or arrange for alternate) Army CCB
  meetings.
• As the concept proponent, present/defend items
  submitted by them (or requests other presenter).
• Ensure action items assigned are completed by the
  suspense date.

6
ARMY CONFIGURATION CONTROL BOARD FLOW DIAGRAM
CPMS CCB
If applicable
If applicable
Army CCB
Concept Not Approved/ On Hold for Implementation
Army Development
MFAD posts to web-site. CCB members review and
comment.
MACOMs
CPOCMA
OCONUS CPOCs and CPACs
CONUS CPOCs
7
ARMY CCB PROCESS FLOW DIAGRAM
Submitter enters proposed Concept Description on
web and forwards to their chain of command via
email.
Chain of command reviews/concurs and submits to
the appropriate CCB member for consideration. CPAC
to MACOM to MFAD CONUS CPOC to CPOCMA to
MFAD OCONUS CPOC to MACOM to MFAD
CCB member reviews/approves and forwards Concept
Description to MFAD by email.
MFAD does cursory review and posts to web. (2
days) MFAD may call CCB subgroup meeting to
review/discuss packages. (5 days if necessary)
MFAD notifies DA staff and CCB members that new
Concept Description(s) is/are on the web for
review, comment and prioritization. MFAD
notifies members of the next CCB meeting date and
cut off date for comments. (Minimum 10 days)
Submitter accesses considers comments on the
web and prepares for presentation at the
scheduled CCB meeting. (At least 5 days prior
to CCB meeting.)
CCB meeting held. Concept Description(s)
presented at CCB meeting by CCB member that
submitted the Concept Description. (1 day)
Summary report of CCB meeting/results posted and
status/ results maintained on web. (2 days)
Actions taken by appropriate offices to implement
results and begin development efforts. MFAD
tracks/reports status, as necessary. (If concept
approved, Clinger-Cohen documentation must be
prepared IAW DA guidance as part of the
development process.)
Note Total CCB process from MFAD receipt to CCB
Report is 20 days. Plan is to hold CCB meetings
once a month, considering CDs received.