CI Configuration Control Board (ERB): The CI System Engineer is the CI CCB Chair and the Project Analyst is the board Secretary who is a nonvoting member of the board. As Configuration Manager, the SE tracks the status of ECRs, forwarding them to the Secretary when complete and ready for board review. The Secretary schedules CI CCB meetings, ensures that all necessary documentation is available to the board at least one week prior to the meeting, and keeps the minutes and action items for each meeting.
Board membership consists of the Executive Management Team and the System Engineering Team (Sections 2.2.1 and 2.2.2). This group is divided into two types of CI CCB members. The core CI CCB membership consists of the Project Director, Deputy Project Director, Project Manager, System Engineer, Quality Manager, Senior System Architect, System Development Manager and Operations Manager. Each person has a single vote, and a quorum of 66% of the core members (except for the Project Director and Deputy Project Director, who collectively count as a single member for the purpose of achieving a quorum) must be present to hold a board meeting. The remaining members of the Executive Management Team (Project Scientist, Chief Architect and EPE Manager) may attend CI CCB meetings at their discretion, and will be able to vote if present. The Chair will request their attendance when issues that he believes to require their advice are under consideration.
If a board member cannot attend a given meeting, then he/she should forward their comments and vote in advance of the meeting to the Secretary, who will provide the comments to the board and hold the vote in confidence until the remainder of the board has voted. An absentee member does count toward the board quorum. Under unusual circumstances, a board member may appoint an alternate from within the project who is not already a member of the board, and the alternate may vote for the member. For Class II changes that do not affect the project cost, schedule or scope baselines (such as revisions to projectc plans), an email vote by a quorum of the CI CCB will be allowed.
All board attendees are expected to review the issues before the board in advance of the meeting and formulate a list of comments or issues for consideration by the entire board. The originator of an ECR will collect the comments and issues in advance of a board meeting, and attempt to reconcile any conflicts in order to formulate a clear recommendation to the board. The ECR originator will attend the CI CCB meeting if not already a member, and present the ECR and recommendations to the board for further discussion prior to the vote. The IO CCB's roles and responsibilities include:
1. Track, review, evaluate and document all requested changes and board actions.
2. Ensure requested change is beneficial to the system.
3. Evaluate alternatives that would achieve the same results.
4. Evaluate all impacts and their effect on scope, cost, and schedule.
5. Approve or reject requests for change.
6. Document the approved change, and communicate decisions to all stakeholders.
7. Ensure the EVMS system is appropriately updated when a change has been approved.
8. Track and report the cost and schedule changes to the COTR and OOI Program Office.
9. Forward all IO approved Class I ECRs to the System Level CCB for review and approval.
10. Notification of System Level CCB and provision of documentation for all IO approved Class II ECRs (notification only, not for approval).