Documentation of Software Configuration. If the Services include configuration of Software by Supplier, Supplier shall provide to the appropriate Authorized User documentation containing a description of the configuration. Such documentation shall be sufficiently detailed such that any appropriately trained employee or Agent of any Authorized User may reconstruct the configuration of the Software.
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide Documentation containing a description of the configuration to the appropriate DMAS. The Documentation must be of sufficient detail so that any appropriately trained employee or Agent of DMAS may reconstruct the configuration of the Software.
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide Documentation containing a description of the configuration to VDOT. The Documentation must be of sufficient detail so that any appropriately trained employee or Agent of VDOT may reconstruct the configuration of the Software.
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide to the appropriate Authorized User documentation containing a description of the configuration. Such documentation shall be sufficiently detailed such that any appropriately trained employee or Agent of any Authorized User may reconstruct the configuration of the Software. acceptance 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 ...
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide Documentation containing a description of the configuration to the appropriate OAG. The Documentation must be of sufficient detail so that any appropriately trained employee or Agent of OAG may reconstruct the configuration of the Software.
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide Documentation containing a description of the configuration to DCJS. The Documentation must be of sufficient detail so that any appropriately trained employee or Agent of DCJS may reconstruct the configuration of the Software. ACCEPTANCE AND CURE PERIOD Software and Deliverable Acceptance Criteria Software and Deliverables are deemed accepted when DCJS determines that the Software and Deliverables successfully operate in accordance with the Requirements. Acceptance of the Software and Deliverables, and for the Solution as a whole, requires delivery to DCJS of all of functionality listed in the Requirements as set forth in Exhibit A of the Contract. Supplier shall be responsible for ensuring that all Deliverables function properly within the Solution. Acceptance of any one Deliverable will not imply DCJS’ 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 cover all costs associated with the modification. DCJS shall commence Acceptance testing within two (2) calendar days after receipt of the Software or Deliverable. The Acceptance testing period for the first instance of each Product type set forth in Exhibit B will last no longer than fifteen (15) calendar days, unless a longer period is agreed to in writing between DCJS and Supplier. Throughout the Acceptance testing period, Supplier shall provide to DCJS any assistance and advice as DCJS 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 DCJS pursuant to the terms and conditions of the “Reimbursement of Expenses” section of this Contract below. DCJS shall provide to Supplier written notice of Acceptance upon completion of successful Acceptance testing. In the event that DCJS 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, the Solution will be deemed Accepted. Solution Acceptance Criteria The Solution will be deemed accepted when DCJS determines that the Solution successfully operates in accordance with the Requirements. DCJS shall commence Acceptance testing within two (2) calendar days after dep...
Documentation of Software Configuration. If the Solution includes configuration of Software by Supplier, Supplier shall provide Documentation containing a description of the configuration to VDH. The Documentation must be of sufficient detail so that any appropriately trained employee or Agent of VDH may reconstruct the configuration of the Software. DocuSign Envelope ID: D69B105E-7A47-46ED-8B09-C0071CE057F5
Documentation of Software Configuration. If the license fee for the Software listed in Exhibit B includes configuration by the Supplier, Supplier shall provide to the appropriate Authorized User documentation containing a description of the configuration. Such documentation shall be sufficiently detailed such that any appropriately trained employee or Agent of any Authorized User may reconstruct the configuration of the Software.
