Delivery of Developed Software Sample Clauses

Delivery of Developed Software. All source and object codes for the Developed Software (i.e. all software custom developed for NYSDOT’s EAMP System) shall be provided to NYSDOT during System Implementation to support the maintenance of the EAMP System. This will include the software, documentation of the customization, and training materials for the maintenance of the customized software.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
Delivery of Developed Software. All source and object codes for the Developed Software, i.e. all software custom developed for the BDIS application, shall be provided to NYSDOT during System Implementation to support the maintenance of the BDIS. This will include the software, documentation of the customization, and training materials for the maintenance of the customized software.
Sample 1Sample 2
Delivery of Developed Software. All source and object codes for the Developed Software, i.e., all software custom developed for the HOOCS application, shall be provided to NYSDOT during System Implementation to support the maintenance of the HOOCS. This will include the software, documentation of the customization, and training materials for the maintenance of the customized software.
Sample 1Sample 2
Delivery of Developed Software. All source and object codes for the Developed Software,
Sample 1
Delivery of Developed Software. PGIC will be responsible for unit testing and functional integration testing, as required, of the Developed Software and will deliver the Developed Software for each Phase to IGT for acceptance testing. Completion of the testing, and any required corrections for deliverables for a particular milestone will be considered a deliverable for the subsequent milestone whether or not shown as such in Exhibit D.
Sample 1
Delivery of Developed Software. Upon completion of the Developed Software, Springboard shall so notify 1401629 in writing and shall deliver to 1401629 such deliverable. 1401629 shall have a reasonable period of time to inspect and approve such Developed Software and to provide Springboard with a written acceptance thereof or a detailed written statement of errors. To the extent that 1401629 does not accept the Developed Software, the parties shall work together in good faith to rectify any problems identified in the Statement of Errors.
Sample 1
Delivery of Developed Software. PGIC will be responsible for unit testing and functional integration testing, as required, of the Developed Software and will deliver the Developed Software for each Phase to IGT for acceptance testing. Completion of the testing, and any required corrections for deliverables for a particular milestone will be considered a deliverable for the subsequent milestone whether or not shown as such in Exhibit D.
Sample 1
AutoNDA by SimpleDocs

Related to Delivery of Developed Software

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

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

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Software Warranty We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

  • Proprietary Materials Each of the Parties shall own its own intellectual property including without limitation all trade secrets, know-how, proprietary data, documents, and written materials in any format. Any materials created exclusively by IPS for the School shall be owned by IPS, and any materials created exclusively by Operator for the School shall be Operator’s proprietary material. The Parties acknowledge and agree that neither has any intellectual property interest or claims in the other Party’s proprietary materials. Notwithstanding the foregoing, materials and work product jointly created by the Parties shall be jointly owned by the Parties and may be used by the individual Party as may be agreed upon by both Parties from time to time.

  • Computer Software The Grantee certifies that it has appropriate systems and controls in place to ensure that state funds will not be used in the performance of this Grant Agreement for the acquisition, operation, or maintenance of computer software in violation of copyright laws.

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