Software Release Control Sample Clauses

Software Release Control. The Provider’s responsibilities include the following: 1. Perform all functions required to maintain the current Software environment. 2. Unless otherwise approved by the Company, maintain all Third Party Software products at the release levels and currency as specified in Exhibit 2.2 (Cross Functional – Equipment and Software Services) to this Schedule. 3. Perform all Software modifications, testing, and acceptance testing needed to maintain the aforementioned degree of currency. 4. Assume full responsibility for release packaging and project commitments for the Software. Amendment I (September 11, 2012) 5. Follow or, with the Company approval, improve the Company’s service delivery and release management processes in accordance with the existing the Company business planning, work authorization, and release management processes. 6. Support the Company’s process for priority setting, planning, and scheduling of releases. 7. Monitor the release schedule and report all schedule exceptions to the Company as required by the release management process. 8. Provide the necessary interfaces during the development testing and implementation phases. 9. Distribute and implement releases. 10. Maintain source code and version control. 11. Perform virus scanning and eradication on new and modified Software.
Sample 1
AutoNDA by SimpleDocs

Related to Software Release Control

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • Flexible Work Schedules An employee may request a modification of their current work schedule to another schedule. The Employer, or its designees, may approve or deny flexible work schedules and retain the responsibility for determining exemptions from, or terminations of, flexible work schedules which adversely affect the operation of the Minnesota Judicial Branch or the level of service to the public.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

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