CHANGE CATEGORIES Clause Samples
The "Change Categories" clause defines and organizes the types of changes that may occur within a contract or project, typically by grouping them into specific categories based on their nature, impact, or required approval process. For example, changes might be classified as minor, major, or emergency, with each category subject to different procedures or levels of authorization. This structure helps ensure that all parties understand how proposed changes will be handled, streamlining decision-making and reducing disputes by clarifying the process for managing modifications.
CHANGE CATEGORIES. A Change is always applied within one of the following Change categories where all Changes follow the Change Management Process: TABLE 8: CHANGE CATEGORIES # OF INFLUENCE ON APPROVAL CATEGORY DESCRIPTION SITES BUSINESS PROCESS OF ----------------- ----------------------------- --------- ---------------- --------- Minor Change Change that affects One No CAB only one site, with no influence influence on the daily business processes. Medium Change that affects One or Little CAB Change one or more sites, with more influence little influence on the daily business processes. Major Change Change that affects More Influence CAB more then one site, than one with influence on the daily business processes. Any side may not implement this Change without prior approval from the CAB, in writing Commercial Change has major More Influence Stirring Change commercial affects on than one Committee this agreement and/or has major affects on the business processes of either sides PORTIONS OF THIS AGREEMENT HAVE BEEN OMITTED PURSUANT TO A REQUEST FOR CONFIDENTIAL TREATMENT FROM THE SEC Statement of Work (SOW) # OF INFLUENCE ON APPROVAL CATEGORY DESCRIPTION SITES BUSINESS PROCESS OF ----------------- ----------------------------- --------- ---------------- --------- Emergency Minor Change or One or No or little Country Change without Medium Change more Influence Manager extra cost to required on an or Customer emergency basis that Customer affects one or more Project sites and is essential for Manager. a resolution of a serious Written problem in the IT Report will Environment. In such be to CAB. case HP-OMS may submitted implement the Change afterwards without Customer approval, provided that the Change is reported to Customer promptly after such implementation. Emergency Minor Change or One or No or little Country Change with Medium Change more Influence Manager extra cost to required on an or Customer emergency basis that Customer affects one or more Project sites and is essential for Manager. a resolution of a Written serious problem in the IT report will Environment. HP-OMS be afterwards should get prior submitted to CAB. approval from the Customer Project Manager or the manager of the applicable Customer Site, in writing. In such case HP-OMS may implement the Change without Customer approval, provided that the Change is reported to Customer promptly after such implementation. PORTIONS OF THIS AGREEMENT HAVE BEEN OMITTED PURSUANT TO A REQUEST FOR CONFIDENTIAL TREATMENT FROM...
CHANGE CATEGORIES. The following table defines Change Categories to be applied to the ODT IT Platform, and provides examples. Category Change Impact Summary Emergency Change that must be introduced as soon as possible, in order to repair a P1 or P2 incident within the ODT IT Platform. Email notification of the change and possible impact must be provided to the Business Owner as soon as is reasonable (including after the fact if necessary), along with a Post Implementation Report summarising the change performed and the results, including issues encountered. Major Change to a service or infrastructure component of the ODT IT Platform for which the risk has been assessed as medium or higher and may require a customer or operational outage. Change must be approved by Business Owner 24 hours prior to execution Change must be Business Owner at least 1 business day prior to the change (such approval not to be unreasonably withheld or delayed) to allow the operational Category Change Impact Summary risk to be assessed and mitigation plans to be identified, developed and put in place Examples: major version software upgrade or patching, restarting entire platform component resulting in an outage, migrating service or component to entirely new technology, releasing new client application versions. Minor Change to a service or infrastructure component of the ODT IT Platform for which the risk has been assessed as low. An email notification of the change and possible impact must be provided to the Business Owner at least 1 business day prior to the change to allow existing operational mitigation plans to be put in place. Examples: application of a minor patch version, migrating workloads to new hosts, restarting service components without customer or operational impact. The following table defines Service Level Metrics to be applied to the ODT IT Platform support arrangements provided by Supplier. ODT IT Platform Service Levels