Change Request Management Sample Clauses

Change Request Management. A Change Request will be raised based on the need to change a system baseline or the need to cater to a new requirement. The system baseline is the agreed/delivered functionality of the system as set forth in the Program Specifications. Planet Payment will advise Acquirer on the Change Management process that is to be followed at the time of requesting change to system baseline or to address a new requirement. With the exception of new business related change request which will be submitted by Acquirer, Planet Payment will arrange for other change requests. The following are examples of change requests: · Development of a new Acquirer business or Acquirer operations report from an existing system (Acquirer) * Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. · Application system or service enhancements to cater to a new requirement from Acquirer (Acquirer) · Proposed changes to the specific implementation of Acquirer Program for Acquirer (Planet Payment) comprising material modifications or deletions to the functionality of the services. The following shall not require a change request by Planet Payment for the purposes of this Agreement. Changes by Planet Payment in the following circumstances. · As may be necessary on an emergency basis to maintain the continuity of the services. · If the proposed change is de minimis · Changes necessary to implement the twice yearly Card Association compliance changes and any other changes mandated by the Card Associations. · Routine patches and bug fixes
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Change Request Management. Should the need for a change to Project scope, schedule, and/or cost be identified during the Project, the change will be brought to the attention of the Steering Committee and an assessment of the change will occur. While such changes may result in additional costs and delays relative to the schedule, some changes may result in less cost to the City; for example, the City may decide it no longer needs a deliverable originally defined in the Project. The Change Request will include the following information: ▪ The nature of the change. ▪ A good faith estimate of the additional cost or associated savings to the City, if any. ▪ The timetable for implementing the change. ▪ The effect on and/or risk to the schedule, resource needs or resource responsibilities. The City will use its good faith efforts to either approve or disapprove any Change Request within ten (10) Business Days (or other period as mutually agreeable between Xxxxx and the City). Any changes to the Project scope, budget, or timeline must be documented and approved in writing using a Change Request form. These changes constitute a formal amendment to the Statement of Work and will supersede any conflicting term in the Statement of Work. Acceptance and Acknowledgement Processes The implementation of a Project involves many decisions to be made throughout its lifecycle. Decisions will vary from higher level strategy decisions to smaller, detailed Project level decisions. It is critical to the success of the Project that each applicable City office or department designates specific individuals for making decisions on behalf of their offices or departments. Both Xxxxx and the City will identify representative project managers. These individuals will represent the interests of all stakeholders and serve as the primary contacts between the two organizations. The coordination of gaining City feedback and approval on Project deliverables will be critical to the success of the Project. The City project manager will strive to gain deliverable and decision approvals from all authorized City representatives. When possible, to ensure an efficient response process, the Xxxxx Project Manager will notify the City Project Manager of an upcoming Deliverable or Control Point to allow the City Project Manager adequate time to align resources for review and to effectively use the review timeline window, in order to meet mutually agreed upon response timelines. This will typically occur during recurring bi-weekly st...
Sample 1
Change Request Management. The supplier classification is conducted on the basis of these processes for assessment in accordance with Appendix 1. The results of the process assessments are to be presented in accordance with Appendix 2.
Sample 1
Change Request Management. Should the need for a change to Project scope, schedule, and/or cost be identified during the Project, the change will be brought to the attention of the Steering Committee and an assessment of the change will occur. While such changes may result in additional costs and delays relative to the schedule, some changes may result in less cost to the Health Care Agency; for example, the Health Care Agency may decide it no longer needs a deliverable originally defined in the Project. The Change Request will include the following information: ▪ The nature of the change. ▪ A good faith estimate of the additional cost or associated savings to the Health Care Agency, if any. ▪ The timetable for implementing the change. ▪ The effect on and/or risk to the schedule, resource needs or resource responsibilities. The Health Care Agency will use its good faith efforts to either approve or disapprove any Change Request within ten (10) Business Days (or other period as mutually agreeable between Xxxxx and the Health Care Agency). Any changes to the Project scope, budget, or timeline must be documented and approved in writing using a Change Request form. These changes constitute a formal amendment to the Statement of Work and will supersede any conflicting term in the Statement of Work.
Sample 1
Change Request Management. It may become necessary to amend the SOW for various reasons. In the event either party desires to change the SOW, the following procedures will apply: A) The party requesting the change will deliver a Change Request Management document, in the form substantially similar to Attachment A, to the other party. The Change Request Management will describe the nature of the change, the reason for the change, and the effect the change will have on the SOW, which may include changes to the deliverables and the schedule. B) A Change Request Management may be initiated by either party for any material changes to the SOW. The designated Resource of the requesting party will review the proposed change with his/her counterpart. The parties will evaluate the Change Request Management and negotiate in good faith the changes to the Services and the additional charges, if any, required to implement the Change Request Management. If both parties agree to implement the Change Request Management, the appropriate authorized representatives of the parties will sign the Change Request Management, indicating the acceptance of the changes by the parties. C) Upon execution of the Change Request Management, said Change Request Management will be incorporated into, and made a part of, the SOW. The Reseller will provide a revised purchase order, as required. D) Whenever there is a conflict between the terms and conditions set forth in a fully executed Change Request Management and those set forth in this Agreement or in a previous fully executed Change Request Management, the terms and conditions of the most recent fully executed Change Request Management shall prevail for the specific SOW identified in the Change Request Management document.
Sample 1
Change Request Management. The supplier classification is conducted on the basis of these processes for assessment in accordance with Appendix 1. The results of the process assessments are to be presented in accordance with Appendix 2. In the event of an A classification, the identified discrepancies must be remedied autonomously. In the event of a B or C classification, the supplier must submit a program for improvement to the Project responsible person from Schaeffler for approval, complete with measures, responsible persons and dates. The supplier must also conduct a self-assessment, to verify the effectiveness of the measures taken, and communicate the results of the self-assessment to Schaeffler. Software in the context of Functional Safety Depending on the application and corresponding contractual statement with Schaeffler, internationally valid standards must be taken into account for software development activities conducted in the context of functional safety. In particular, these standards include ISO 26262 "Road Vehicles" and ISO 13849 "Safety of machinery – Safety-related parts of control systems", as well as IEC 61508 "Functional safety of electrical/ electronic/ programmable electronic safety-related systems", which does not relate to a specific sector. Term This Quality Assurance Agreement is effective once it has been signed by both contract parties and is valid for an indefinite period. It applies to the full extent of the business relationship between the contract parties involved.
Sample 1

Related to Change Request Management

  • Change Request Either Landlord or Tenant may request Changes after Landlord approves the Approved Plans by notifying the other party thereof in writing in substantially the same form as the AIA standard change order form (a “Change Request”), which Change Request shall detail the nature and extent of any requested Changes, including (a) the Change, (b) the party required to perform the Change and (c) any modification of the Approved Plans and the Schedule, as applicable, necessitated by the Change. If the nature of a Change requires revisions to the Approved Plans, then the requesting party shall be solely responsible for the cost and expense of such revisions and any increases in the cost of the Tenant Improvements as a result of such Change. Change Requests shall be signed by the requesting party’s Authorized Representative.

  • Change Requests 4.1.1. Either party can request changes to the Service.

  • Contract Management Contractor shall report to the Health and Human Services Agency Director or his or her designee who will review the activities and performance of the Contractor and administer this Contract.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • 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.

  • CHANGE DIRECTIVE A Change Directive means a written instruction, which shall be deemed incorporated into and forming part of the Agreement, prepared by the Contract Administrator and signed by the Owner directing the Contractor to proceed with a change in the Work prior to or in the absence of the Owner and the Contractor agreeing upon adjustments in the Contract Price and the Contract Time.

  • Exit Management 58.1. The Service Provider shall perform its relevant Exit Management obligations as part of the Contract whether applicable on either the expiry or early termination of this Contract. 58.2. The Service Provider agrees that if it breaches (or attempts or threatens to breach) its obligation to provide Exit Management, the Purchaser and their respective customers and stakeholders shall be irreparably harmed. In such circumstance, the Service Provider agrees that the Purchaser may proceed directly to court notwithstanding anything to the contrary in the dispute resolution procedure outlined in Clause 53 (Dispute Resolution). If a court of competent jurisdiction finds that the Service Provider has breached (or attempted or threatened to breach) any such obligation, the Service Provider agrees that without any additional findings of irreparable injury, or other conditions to interdict, the Service Provider shall not oppose the entry of an appropriate order compelling performance by the Service Provider and restraining the Service Provider from any further breaches or attempted or threatened breaches of its obligations in relation to Exit Management. 58.3. A draft of the Exit Plan shall be produced by the Service Provider and supplied to the Purchaser within [three (3) months] after the Commencement Date and shall include or address the matters specified in Clause 59.3. The Purchaser shall provide to the Service Provider the Purchaser’s comments on the plan within one (1) month of the Purchaser’s receipt of the plan. The Service Provider shall take into account the comments and suggestions of the Purchaser and shall issue the final version of the Exit Plan to the Purchaser within ten (10) Working Days of receipt of the Authority’s comments. 58.4. The Service Provider shall throughout the period of the Contract review, maintain and continuously update the Exit Plan which shall include: 58.4.1. the activities required to enable the Purchaser to re-tender the Purchaser Requirements and/or the provision of the Services; 58.4.2. the activities necessary to support any Replacement Service Provider or the Purchaser in carrying out any necessary due diligence relating to all or part of the Services; 58.4.3. details of the Exit Management to be provided by the Service Provider prior to the Exit Management Date; 58.4.4. support for the Replacement Service Provider or the Purchaser during their preparation of any relevant plan for the transition of the System to the Replacement Service Provider or Purchaser, including prior to and during such transition period; 58.4.5. the maintenance of a ‘business as usual’ environment for the Purchaser during the period when Exit Management obligations are applicable; and 58.4.6. all other necessary activities to support the preparation for, and execution of, a smooth and orderly Exit Management and transfer of all or part of the Services to either a Replacement Service Provider or the Purchaser. 58.5. No amendment of the Exit Plan shall be made without prior written consent of the Purchaser.

  • Construction Management Landlord or its Affiliate or agent shall supervise the Work, make disbursements required to be made to the contractor, and act as a liaison between the contractor and Tenant and coordinate the relationship between the Work, the Building and the Building’s Systems. In consideration for Landlord’s construction supervision services, Tenant shall pay to Landlord a construction supervision fee equal to three percent (3%) of Tenant’s Costs specified in Section 7.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Project Management Plan 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 and

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