The DoDIN-A Change Advisory Board (CAB) is the Army enterprise change management process. Army Commands submit proposed changes to the DoDIN-A for mission unique systems or network access. Technical SMEs evaluate proposed changes to assess the overall impact to the DoDIN-A in terms of engineering, security, interoperability, latency, and policy. The CAB processes standard Requests for Change, firewall modifications, Block/Un-block Requests, system baseline changes, change packets to Risk Management Change records, and Authority to Connect (ATC) requests. Processes and procedures for the DoDIN-A CAB are outlined in the DoDIN-A CAB Charter. Change requests may be processed as critical, moderate, or routine.
Unique Support Tasks
1) Receive all incoming RFC, verify the request form is complete, signed, and all required supporting documentation is provided and complete. Coordinate with the requestor for all missing data.
2) Assign a unique identification number using the established naming convention and provide to requestor.
3) Review, prioritize, and prepare all RFC packages for the CAB Board Member review.
4) Validate the RFC against the CMDB and provide configuration, interoperability, and security constraints as part of the RFC package for Board Members and CAB Chair.
5) IAW Government timeframes distribute all RFC packages to CAB voting members for review. Consolidate board member recommendations and provide the final RFC to the CAB Chair for final determination.
6) Distribute the final determination to RFC initiator and board members. Update electronic records to reflect status and closure determination.
7) Maintain all materials related to the identification, storage, distribution, and tracking of RFC actions and store materials on portals and/or in classified containers.
8) Draft Change Management procedures and implementation guidance including items such as the CAB charter, SOP, and process diagrams.
9) Track use of ITSM and portal to automate change management processes and integrate with configuration and release management processes.
10) Participate in ITSM automation planning and operational rehearsals as required.
