Change Control Board. Parties agree to support as a governing body the Change Control Board (CCB) consisting of members and those providers contracted to provide Support Services for the system, whose collective responsibility and authority is to review, evaluate and approve functional and technical change requests (CRs) for the system. It is understood by Parties, that the CEC defines the collective scope of responsibility and authority for the CCB and establishes financial and other limits within which the CCB can act without further CEC review and approval. Parties agree that the voting representatives of the CCB are empowered by their organization with the authority to make decisions on all matters coming before the CCB within those limits. Parties agree that the CCB is comprised of one (1) voting representative for each member and provider. Parties also agree that final approval of CRs is only required by impacted members and providers, but participation in reviews and evaluations are the responsibility of all representatives. In support of the CCB, each Party agrees that the CEC representative for their state will designate one (1) primary representative and at least one (1) backup representative to the CCB. The Parties agree that the representative’s responsibilities to the CCB will take priority over their responsibilities outside of the Consortium. Parties acknowledge that the Consortium has established and documented as part of the SOP a change management process which all members and providers are required to support and follow in order to participate or provide service to the Consortium. Each Party further acknowledges that essential to this process is that ownership and responsibility for approval of CRs can only reside with a member. Parties agree that the PMO is responsible for monitoring and reporting on the performance of the CCB to the CEC, and may at its own discretion, or upon request by a voting representative, schedule a formal CCB meeting which all voting members are required to attend to address departures from SOP. It is agreed by all Parties that when disposition of CRs by the CCB is not possible, a risk item will be recorded, and when approval is unattainable or outside of established limits, an escalation to the CEC will occur.
Change Control Board. A Change Control Board (the "CHANGE CONTROL BOARD") will review all change requests, and approve, disapprove, or escalate all requests as required. The Chairpersons for this team will be the EMW Contract Executive and IBM Contract Executive. The Chairpersons will assign operational team members to the Change Control Board as appropriate. The Change Control Board is expected to meet at least weekly. In the event of a dispute regarding procedural or scheduling issues, EMW shall make the final determination.
Change Control Board. A formally constituted group of stakeholders responsible for reviewing, evaluation, approving, delaying, or rejecting changes to a project, with all decisions and recommendations being recorded. A Change Control Board (CCB) will be defined to review, approve, reject and disposition any submitted changes to the project. The CCB will include a representative from AEP and a representative from the vendor. The representatives from the AEP and the vendor will have the decision making responsibility in the CCB. The CCB will have authority to approve, reject or delay any submitted Change Order at any step in the process and the decision will be recorded. Note - If the change impacts the budget of the program, the AEP CCB members will have the authority to review and accept the Change Order but not the authority to sign the document. See CCB Approves/Rejects Change section for additional details.
Change Control Board. 6 2.5 Change Control Process........................................... 7 2.6 Key Staff........................................................ 9
Change Control Board. (a) The Client Program Manager will organize the Change Control Board. Each party will designate two management-level employees, including that party's Program Manager, to participate in the Change Control Board.
Change Control Board. FHWA-NJ is invited to Change Control Board Meetings and provides appropriate project guidance for Federally Funded Projects. NJDOT provides a detailed description and supporting documentation of the project changes prior to the CCB meeting. NJDOT provides FHWA-NJ with a copy of the final CCB action. Environmental Documents – FHWA-NJ approval of all environmental documents (EA/FONSI, EIS/ROD, non-self-certified CED, 4(f), 106, 6(f) etc.) are required by Federal laws and regulations. Submission and review times/standards will differ based on magnitude of document, starting with 14 day approval for CEDs and graduating from there. The NJDOT will submit all environmental documents, with exception of self- certified CEDs and ERs that do not require approval, to FHWA-NJ for review. Proprietary products – In accordance with 23 CFR 635.411, the NJDOT will submit all requests for public interest findings or experimental requests on the NHS for approval. FHWA-NJ will provide approval/comment of all public interest findings or experimental requests for proprietary products within 14 days. NJDOT will provide all delegated Proprietary product approvals by the NJDOT to the FHWA-NJ Engineering Coordinator for record.
Change Control Board. (a) Within three months of the Service Commencement Date, the Crown and Contractor will establish the Change Control Board, which will meet monthly.
Change Control Board. (CCB/CIP CCB) means the decision-making body of the CIP-Users pursuant to clause 4.
Change Control Board. The Parties agree that a Change Control Board will be established to coordinate Change Requests initiated in accordance with the Agreements. Both Parties will be equally represented in this Change Control Board and will discuss in good faith its procedures, and frequency of meetings.
