Operational Change Control Sample Clauses
The Operational Change Control clause establishes procedures for managing and approving changes to operational processes, systems, or services within an organization or between contracting parties. Typically, it requires that any proposed modifications—such as updates to IT infrastructure, workflows, or service delivery—are formally documented, reviewed, and authorized before implementation. This clause ensures that changes are controlled and communicated, minimizing the risk of disruptions, errors, or security breaches, and maintaining the integrity and reliability of operations.
Operational Change Control. The procedures that will govern (i) the process by which a Party may propose or request operational Changes, (ii) the process to be followed by the Parties in analyzing the effects of, and deciding whether to implement, any such Change, and (iii) the manner in which any agreed upon Changes are to be implemented (the “Operational Change Control CONFIDENTIAL TREATMENT HAS BEEN REQUESTED FOR PORTIONS OF THIS EXHIBIT. THE COPY FILED HEREWITH OMITS THE INFORMATION SUBJECT TO A CONFIDENTIALITY REQUEST. OMISSIONS ARE DESIGNATED [ * * * ]. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. Procedures”), are set forth in the applicable Procedures Manual. Among other things, the Operational Change Control Procedures will provide that:
(i) no Change will be implemented without Customer’s prior written approval, except as may be necessary on a temporary basis to maintain the continuity of the Services;
(ii) with respect to all Changes, other than those Changes made on a temporary basis to maintain the continuity of the Services, Provider will prepare and deliver to the Customer Technical Alliance Manager a written analysis describing any changes in products, services, assignment of personnel and other resources that Provider believes would be required, together with, as appropriate or applicable (A) an estimation of the increase or decrease, if any, in the Charges that would be required, (B) a description of how the Change would be implemented, (C) a description of the effect, if any, such Change would have on this Agreement, including on Service Levels and Winddown Expenses, (D) an estimation of all resources required to implement such Change, including a description of the delivery risks and associated risk mitigation plans, and (E) such other information as may be relevant to the Change;
(iii) with respect to all Changes, other than those Changes made on a temporary basis to maintain the continuity of the Services, Provider will (a) schedule Changes so as not to unreasonably interrupt Customer’s business operations, (b) prepare and deliver to Customer each month a rolling schedule for ongoing and planned Changes for the next three month period, and (c) monitor and report to Customer the status of Changes that are in-progress against the applicable schedule; and
(iv) with respect to any Change made on a temporary basis to maintain the continuity of the Services, Provider will document and provide to Customer not...
Operational Change Control. (1) Prior to using any new Software or new Equipment to provide the Services, HPES will have verified that the item (a) is consistent with the HPI Architecture, standards and strategic direction specified by HPI, (b) has been properly installed, (c) is operating in accordance with its specifications, and (d) is performing its intended functions in a reliable manner.
(2) HPES will not make any Changes without first obtaining HPI’s approval in accordance with Section 16.6(B). All operational Changes will be implemented in accordance with HPI’s change management procedure listed in Schedule 13.
(3) HPES will assist the Service Recipients in moving programs from development and test environments to production environments in a controlled and documented manner, so that no Changes are introduced into the programs by HPES during such activity.