Technical Change Control Sample Clauses

Technical Change Control. (i) At all times ACI shall be responsible for establishing ACI’s IT architecture, standards and strategic direction; provided, however, that Vendor shall actively participate in and provide subject matter expertise to ACI as it establishes such IT architecture, standards and strategic direction. In performing the Services, Vendor shall conform with and shall support such architecture, standards and strategic direction in accordance with the technical change control procedures defined in this Section 10.6 and in the Procedures Manual. (ii) Vendor shall be responsible for all Changes to ACI’s IT environment pertaining to the Services, including Changes to programs, Procedures Manuals, job control language statements, distribution parameters and schedules. Vendor shall comply with the following Change control requirements: (A) Prior to using any new Systems Software or new Equipment to provide the Services, Vendor shall have verified that the item is (1) consistent with the IT architecture, standards and strategic direction specified by ACI, (2) has been properly installed, is operating in accordance with its specifications, (3) is performing its intended functions in a reliable manner, and (4) has been thoroughly tested and been proven compatible with and within ACI’s then-existing IT infrastructure environment. (B) Vendor may make temporary Changes required by an emergency if, after making Commercially Reasonable Efforts, Vendor has been unable to contact an appropriate ACI Confidential Master Services Agreement manager to discuss Vendor’s proposed actions. Vendor shall document and promptly report such emergency Changes to ACI, which Changes shall then be subject to ACI’s approval. (C) Vendor shall not make the following Changes, including implementing a Change in technology, without first obtaining ACI’s approval, which such approval ACI may withhold in its discretion: (1) a Change adversely affecting the function or performance of, or decreasing to any significant degree the resource efficiency of, the Services; (2) a Change increasing ACI’s Charges under this Agreement or other costs or fees of ACI; (3) a Change inconsistent with ACI’s physical or information security policies or procedures to the extent such policies or procedures have been provided to Vendor in writing and in advance; (4) a Change impacting the safety or security of ACI personnel, resources or information; (5) a Change inconsistent with the IT architecture, standards or strategic dire...
Sample 1Sample 2
AutoNDA by SimpleDocs
Technical Change Control. (i) At all times Phoenix shall be responsible for establishing Phoenix’s IT architecture, standards and strategic direction; provided however, Vendor shall actively participate in and provide subject mater expertise to Phoenix as it establishes such IT architecture, standards and strategic direction. In performing the Services, Vendor shall conform with and shall support such architecture, standards and strategic direction in accordance with the technical change control procedures set forth in this Section 10.5. (ii) Vendor shall be responsible for all changes to Phoenix’s IT environment pertaining to the Services, including changes to programs, manual procedures, job control language statements, distribution parameters and schedules. Vendor shall comply with the following change control requirements: (A) Prior to using any new Systems Software or new Equipment to provide the Services, Vendor shall have verified that the item is (1) consistent with the IT architecture, standards and strategic direction specified by Phoenix, (2) has been properly installed, is operating in accordance with its specifications, (3) is performing its intended functions in a reliable manner, and (4) has been thoroughly tested and been proven to inter-operate with and within Phoenix’s then-existing IT infrastructure environment. (B) Vendor may make temporary changes required by an emergency if it has been unable to contact an appropriate Phoenix manager to obtain such approval after making Commercially Reasonable Efforts. Vendor shall document and promptly report such emergency changes to Phoenix, which changes shall then be subject to Phoenix’s approval. (C) Vendor shall not make the following changes, including implementing a change in technology, without first obtaining Phoenix’s approval, which such approval Phoenix may withhold in its discretion: (1) a change adversely affecting the function or performance of, or decreasing to any significant degree the resource efficiency of, the Services; (2) a change increasing Phoenix’s Charges under this Agreement or other costs or fees of Phoenix; (3) a change inconsistent with the IT architecture, standards or strategic direction specified by Phoenix; or (4) a change impacting the way in which Phoenix conducts its business or operations which impact Phoenix considers to be adverse. (D) Vendor shall move programs from development and test environments to production environments in a controlled and documented manner, so that no changes ...
Sample 1
Technical Change Control. EDS shall implement any changes in the technical ------------------------ environment and systems used to provide the Services only in accordance with the terms of the applicable Authorization Letter.
Sample 1
Technical Change Control. EDS Providers shall implement any changes in the technical environments and systems used to provide the Services in accordance with Section 2.3.10 of Exhibit A and with the applicable Procedures Manual. Until an EDS Provider’s Procedures Manual is finalized (or updated as described in Section 9.7(b) above), such EDS Provider shall follow Coors’ or the applicable Coors Recipient’s existing procedures for the implementation of technical changes. Notwithstanding anything to the contrary in any Procedures Manual or any Coors Recipient’s existing procedures: (a) No EDS Provider shall make any change that would have a material effect on the Services (including, without limitation, changes in Equipment, Software and systems configurations, changes that would affect the remigration of the Services back to the Coors Recipients or to a third party service provider, system-architecture changes, or changes that would affect end users), Service Levels, the amounts payable to the EDS Providers under this Agreement or other costs and expenses of the Coors Recipients without Coors’ prior written consent, [*****]. Notwithstanding the foregoing, the EDS Providers may make temporary changes required by an emergency but shall, if reasonably practicable, contact appropriate Coors personnel to obtain prior approval. The EDS Providers shall promptly document and report such emergency changes to Coors. (b) The EDS Providers shall move programs from development and test environments to production environments in a controlled and documented manner, and shall not permit any changes to be introduced into such programs during such move without first obtaining Coors’ approval.
Sample 1
Technical Change Control. EDS shall implement any changes in the technical environment and systems used to provide the Services in accordance with Section 10.13 of Exhibit A and with the Procedures Manual. Until such Procedures Manual is finalized, EDS shall follow Coors' existing procedures for the implementation of technical changes. Notwithstanding anything to the contrary in the Procedures Manual or Coors' existing procedures: (a) EDS shall not make any change that would have a material effect on the Services (including, without limitation, changes in Equipment, Software and systems configurations, changes that would affect the remigration of the Services back to Coors or to a third party service provider, system-architecture changes, or changes that would affect end users), Service Levels, the amounts payable to EDS under this Agreement or other Coors costs and expenses without Coors' prior written consent, which consent may be withheld in Coors' sole discretion. Notwithstanding the foregoing, EDS may make temporary changes required by an emergency but shall, if reasonably practicable, contact appropriate Coors personnel to obtain prior approval. EDS shall promptly document and report such emergency changes to Coors. (b) EDS shall move programs from development and test environments to production environments in a controlled and documented manner, and shall not permit any changes to be introduced into such programs during such move without first obtaining Coors' approval.
Sample 1
Technical Change Control. Supplier shall implement any changes in the technical environment and systems used to provide the Services in accordance with the applicable Service Agreement, and any applicable Procedures Manual, and the recommendations of any provider of Third Party Software. Until such Procedures Manual is finalized, Supplier shall follow Advantica's existing procedures or instructions for the implementation of technical changes. Notwithstanding anything to the contrary in the Service Agreement, the Procedures Manual, or Advantica's existing procedures: (a) Supplier shall not make any change that adversely affects the functions or performance of, or decreases the operational efficiency of, the Services, including without limitation the implementation of technological changes, without first obtaining Advantica's approval, which may be withheld in its sole discretion. Notwithstanding the foregoing, Supplier may make temporary changes required by an emergency but shall, if reasonably practicable, contact appropriate Advantica personnel to obtain prior approval. Supplier shall promptly document and report such emergency changes to Advantica. (b) Supplier shall move programs from development and test environments to production environments in a controlled and documented manner as described in the Procedures Manual. (c) Supplier shall not install any Equipment or Software upgrade within the Advantica environments unless such installation is in accordance with the terms of the Procedures Manual or the Change Control Procedures. If Supplier advises Advantica that, due to a change in the technical environment, Supplier may no longer be able to achieve one or more Service Levels unless an upgrade is authorized and Supplier provides documentation of Supplier's position acceptable to Advantica, Supplier shall not be subject to subsequent Service Level Credits otherwise owed under a Service Level Agreement to the extent Advantica does not approve such upgrade and Supplier demonstrates that the applicable Service Level failure was a direct result of the failure to install the upgrade requested by Supplier. In such event, however, Supplier shall use Commercially Reasonable Efforts to meet the applicable Service Level notwithstanding that the upgrade has not been installed. Such Commercially Reasonable Efforts shall include further discussions by Supplier with the applicable Third Party provider to determine if other alternatives are available and any such other alternatives shall be ...
Sample 1
Technical Change Control. 31 Section 10.8 Contract Change Control................................................................ 32 Section 10.9 System Change Benchmarking............................................................. 33 Section 10.10 Subcontracting......................................................................... 33 ARTICLE 11................................................................................................. 34 ii
Sample 1
AutoNDA by SimpleDocs
Technical Change Control. Supplier shall implement any changes in the technical environment and systems used to provide the Services in accordance the Service Agreement and any applicable Procedures Manual. Until such Procedures Manual is finalized, Supplier shall follow Wards' existing procedures or instructions for the implementation of technical changes. Notwithstanding anything to the contrary in the Service Agreement, the Procedures Manual, or Wards' existing procedures: (a) Supplier shall not make any change that adversely affects the functions or performance of, or decreases the operational efficiency of, the Services, including without limitation the implementation of technological changes, without first obtaining Wards' approval, which may be withheld in its sole discretion. Notwithstanding the foregoing, Supplier may make temporary changes required by an emergency but shall, if reasonably practicable, contact appropriate Wards personnel to obtain prior approval. Supplier shall promptly document and report such emergency changes to Wards. (b) Supplier shall move programs from development and test environments to production environments in a controlled and documented manner, and shall not permit any changes to be introduced into such programs during such move without first obtaining Wards' approval.
Sample 1

Related to Technical Change Control

  • Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.

  • AMENDMENT AND CHANGE CONTROL Any amendment or change of any nature made to this Agreement and the Schedule of Requirements thereof shall only be valid if it is in writing, signed by both Parties and added to this Agreement as an addendum hereto. In this regard a Change Notice must first be defined and issued by the requesting Party. A Change Notice Response must then be issued by responding Party. A formal approval of the Change Request will then trigger the issue of the addendum to this Agreement.

  • Exchange Control If at any time legal restrictions prevent the prompt remittance of part or all royalties with respect to any country in the Territory where Licensed Product is sold, payment shall be made through such lawful means or method as the Parties reasonably shall determine.

  • Change Control Procedure 34.1 In the event that either Party desires any change the terms of this Agreement or any Contract which may materially impact on the timings, scope, Specification or Charges of the Goods or Services, or the scope of either parties’ obligations under this Agreement or the relevant Contract, or which the relevant Party otherwise reasonably determines warrants the use of this change control procedure, the following procedures will apply: (a) the Party requesting the change will deliver a “Change Request” (in the form (or substantially in the same form) contained in Schedule 5 to this Agreement) which describes: (i) the nature of the change; (ii) the reason for the change; (iii) the effect that the requested change will have on the scope or Specification for the Goods or Services; and (iv) any change to the Charges and the Term. (b) Upon receipt of a Change Request, the receiving Party’s authorised representative will contact his/ her counterpart within 5 working days to discuss and agree the Change Request. The parties will negotiate the proposed changes to the Agreement and/or affected Contract in good faith and agree a timeline in which to finalise the Change Notice. (c) Neither party is obliged to agree to a Change Request, but if the parties do agree to implement such a Change Request, the appropriate authorised representatives of both parties will sign the Change Request which will be effective from the date set out in the Change Request. (d) If there is any conflict between the terms and conditions set out in the Agreement or any Contract and the Change Request, then the terms and conditions set out in the most recent fully executed Change Request will apply. (e) The Supplier shall neither be relieved of its obligations to supply the Goods and/or Services in accordance with the terms and conditions of this Agreement or any Contract, nor be entitled to an increase in the Charges as the result of: (i) a General Change in Law; or (ii) a Specific Change in Law where the effect of that Specific Change in Law on the Goods and/or Services is reasonably foreseeable at the Commencement Date of this Agreement, or, where the Change Request relates to a Contract, the applicable Contract Commencement Date. 34.2 The Parties agree that any variations to the Agreement or any Contract to reflect non- material changes (including for example a change to the name/contact details of a Party’s representative) may be agreed in writing and shall not be required to be made in accordance with the procedure in this clause 34, provided always that UKRI shall, in their absolute discretion, decide whether a proposed change is non-material for these purposes.

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order. (b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation. (c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled. (d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Technical Reports All technical reports are to be prepared jointly by the Recipient/Institution conducting Work and all collaborating institutions or as deemed acceptable by the Centre’s contact.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Change Control Procedures (a) No changes or additions may be made to any Work Order without the written agreement of LAUSD as evidenced by a duly executed Change Order. (b) Contractor will not take an action or make a decision which may have a material effect on LAUSD or which adversely affects the function or performance of, or decreases the resource efficiency of, the Services, including implementing changes in technology or equipment and software configuration, without first obtaining LAUSD’s written approval, which approval LAUSD may withhold in its sole discretion as respects any change which may have an adverse effect on LAUSD or the Services.

  • Exchange Control Information Exchange control reporting is required for cash transactions exceeding AUD10,000 and for international fund transfers. The Australian bank assisting with the transaction will file the report for you. If there is no Australian bank involved in the transfer, you will have to file the report.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!