Software and Deliverable Acceptance Criteria Sample Clauses

Software and Deliverable Acceptance Criteria. Software and Deliverables shall be deemed accepted when the Authorized User determines that such Software and Deliverables successfully operate in accordance with the Requirements and applicable order or SOW. At a minimum, Acceptance Criteria for Software and Deliverables, and for the Solution as a whole, shall ensure that all of the functionality described in the Requirements set forth in Exhibit A and required by the Authorized User in the applicable order or SOW has been delivered to the Authorized User. Acceptance of any one Deliverable shall not imply Authorized User's concurrence that the Deliverable will function properly with or within the Solution. Supplier shall be responsible for ensuring that all Deliverables function properly within the Solution. Should a previously Accepted Deliverable require further modification in order to work properly with or within the Solution, Supplier shall be responsible for all costs associated with such modification. Such Authorized User agrees to commence Acceptance testing within five (5) days, or within such other period as set forth in the applicable order or SOW, after receipt of the Software or Deliverable. Acceptance testing will be no longer than fifteen (15) days, or such other period as may be agreed in writing between Authorized User and Supplier, for the first instance of each product type set forth in Exhibit B. Supplier agrees to provide to such Authorized User such assistance and advice as such Authorized User may reasonably require, at no additional cost, during such Acceptance testing, other than pre-approved travel expenses for time and materials type orders or SOWs or for fixed price type orders or SOWs in which travel expenses were expressly excluded from the total price of the order or SOW. Any such travel expenses must be pre-approved by the Authorized User and shall be reimbursable by such Authorized User at the then-current per diem amounts as published by the Virginia Department of Accounts (xxxx://xxx.xxx.xxxxxxxx.xxx), or a successor URL(s)). If the Authorized User is a private institution chartered in Virginia and and granted tax-exempt status under §501(c)(3) of the Internal Revenue Code, such private institution may have its own per diem amounts applicable to Supplier's pre-approved travel expenses. Authorized User shall provide to Supplier written notice of Acceptance upon completion of successful Acceptance testing. Should Authorized User fail to provide Supplier written notice...
AutoNDA by SimpleDocs
Software and Deliverable Acceptance Criteria. Software and Deliverables are deemed accepted when DMAS determines that the Software and Deliverables successfully operate in accordance with the Requirements and Contract documents. Acceptance of the Software and Deliverables, and for the Solution as a whole, requires delivery to DMAS of all of functionality listed in the Requirements as set forth in Exhibit A and required by DMAS in the Contract documents. Supplier shall be responsible for ensuring that all Deliverables function properly within the Solution. Acceptance of any one Deliverable will not imply DMAS’ concurrence that the Deliverable will function properly with or within the Solution. In the event that a previously Accepted Deliverable requires further modification in order to work properly with or within the Solution, Supplier shall provide the modification and cover all associated costs. DMAS shall commence Acceptance testing within thirty (30) calendar days, or within the agreed to period set forth in the Contract documents, after (i) receipt of the Software or Deliverable or (ii) being granted access to the Solution. The Acceptance testing period for the first instance of each Product type set forth in Exhibit B will last no longer than thirty (30) calendar days, unless a longer period is agreed to in writing between DMAS and Supplier. Throughout the Acceptance testing period, Supplier shall provide to DMAS any assistance and advice as DMAS may reasonably require. Supplier shall provide this assistance and advice at no additional cost, other than pre-approved travel expenses incurred which are reimbursable by DMAS pursuant to the terms and conditions of theReimbursement of Expenses” section of this Contract below. DMAS shall provide to Supplier written notice of Acceptance upon completion of successful Acceptance testing. In the event that DMAS fails to provide Supplier written notice of successful or unsuccessful Acceptance testing within five (5) business days following the end of the Acceptance testing period, Supplier should escalate the Acceptance response as appropriate. There is no deemed Acceptance of the Solution.

Related to Software and Deliverable Acceptance Criteria

  • Scope of Work and Deliverables 9.1 Background and Scope

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Tasks and Deliverables A description of and the schedule for each task and deliverable, illustrated by a Xxxxx chart. Start and completion dates for each task, milestone, and deliverable shall be indicated. Must include deliverables specified in SOW-RFP as well as other deliverables that may be proposed by Contractor.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

Time is Money Join Law Insider Premium to draft better contracts faster.