Acceptance Review Period. For each Milestone Deliverable, DIR shall have either (1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a DIR-approved plan, thirty (30) days following Service Provider's notification to DIR that Service Provider has completed any Milestone Deliverable, which shall include Service Provider's internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). The Acceptance Review Period shall begin on the date that Service Provider provides written notification to DIR that the Milestone Deliverable is ready to be reviewed by DIR. Unless otherwise agreed, Service Provider shall perform comprehensive testing (e.g. unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to DIR for Acceptance.
Acceptance Review Period. For each Milestone Deliverable, DIR shall have either (1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a DIR-approved plan, thirty (30) days following Service Provider's notification to DIR that Service Provider has completed any Milestone Deliverable, which shall include Service Provider's internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). Unless otherwise specified in the applicable plan, the Acceptance Review Period for Milestone Deliverables identified as Interim Milestones (in the Transition Plan or the Transformation Plan) shall be ten (10) days. The Acceptance Review Period shall begin on the date that Service Provider provides written notification to DIR that the Milestone Deliverable is ready to be reviewed by DIR. Unless otherwise agreed, Service Provider shall perform comprehensive testing (e.g. unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to DIR for Acceptance. The acceptance review process for Milestone Deliverables identified as Checkpoint Deliverables (in the Transition Plan or the Transformation Plan) is defined in the Service Management Manual.
Acceptance Review Period. Each Customer shall provide written feedback to Contractor by its respective Customer Program Manager stating its respective acceptance or non-acceptance of a Key Milestone within four (4) weeks from notice and delivery of Contractor on completion of a Key Milestone. If a Key Milestone is not accepted by either Customer, that Customer shall provide detailed information on the cause of the non-acceptance and the reason(s) why that Customer contend and reasonably demonstrate that the Contractor did not fulfill its duties and obligations as set forth in this Contract and the applicable Exhibit Set. Non-Acceptance of a Key Milestone by one Customer shall be deemed to be non-acceptance by all Customers. For Key Milestones associated with Product Deliverables, if a Key Milestone is not accepted by Customer(s) due to nonconformance with the Specification (i) Customer(s) shall detail the functionality and test criteria not conforming to the Specification and (ii) Customer(s) shall reasonably demonstrate the nonconformance, enabling the Contractor to reproduce the nonconformance.
Acceptance Review Period. For determining whether to Accept or reject each Deliverable, OCA shall have either (A) the period of time set forth in the Statement of Work, or (B) if no such period is set forth, ten (10) Business Days following OCA’s acknowledgement of receipt of Contractor’s notification that Contractor has completed such Deliverable (any such period of time, the “Acceptance Review Period”). Contractor shall perform comprehensive testing (e.g., unit, string, integration, stress/performance, volume, system testing, regression, security/intrusion, user acceptance), if applicable, on each such Deliverable prior to submitting such item to OCA for Acceptance.
Acceptance Review Period. For agreed to deliverables and milestones (each of the foregoing a Critical Testing Deliverable) and any other established Critical Testing Deliverable, Triad will have either (1) the period of time set forth in the applicable plan or Acceptance Documentation, if any, or (2) [**] if no such period is so established, to determine whether the Critical Testing Deliverable Complies to its Acceptance Criteria (such period of time the “Acceptance Review Period”). The Acceptance Review Period will begin on the date that Supplier provides written notification to Triad that the Critical Testing Deliverable is ready to be reviewed by Triad (a Deliverable clearly marked “Final—Delivery for Acceptance Pursuant to Section 4.6 of the Agreement” and delivered in accordance with this Section 4.6 shall constitute such notification). Unless otherwise agreed, Supplier will perform comprehensive testing (e.g., unit, string, integration, stress, volume, system testing, as appropriate) on each such Critical Testing Deliverable prior to submitting such item to Triad for Acceptance.
Acceptance Review Period. For each Milestone Deliverable, TxDOT shall have either
(1) the period of time set forth in the applicable plan, if any, or (2) if no such period is set forth in a TxDOT-approved plan, thirty (30) days following Service Provider's notification to TxDOT that Service Provider has completed any Milestone Deliverable, which shall include Service Provider's internal testing as required under this Agreement, to determine whether it Complies with its Acceptance Criteria (such period of time, the "Acceptance Review Period"). Unless otherwise specified in the applicable plan, the Acceptance Review Period for Milestone Deliverables identified as interim Milestones (if any)(in the Transition Plan or the Transformation Plan) shall be ten (10) days. The Acceptance Review Period shall begin on the date that Service Provider provides written notification to TxDOT that the Milestone Deliverable is ready to be reviewed by TxDOT. Unless otherwise agreed, Service Provider shall perform comprehensive testing (e.g. unit, string, integration, stress, volume, system testing) on each such Milestone Deliverable prior to submitting such item to TxDOT for Acceptance.
Acceptance Review Period. Ten (10) business days total Upon Agency approval of the Historical Data Conversion Specifications document, Avocette will provide a program(s) to migrate appropriate historical data into Accela Civic Platform. Upon receipt of the conversion from Avocette, the Agency DBA will load the data into the Test environment for validation. In terms of specific output, the following will be executed for this deliverable: ⮚ Completion of migrated data into Accela Civic Platform development or test environment. • Provide a program to migrate historical and in-flight data into the Agency’s AA test database environment. • Each data conversion will include up to three (3) conversion loads for client testing. • Validate the successful completion of the migration of historical data into the Agency’s test environment. • Providing the legacy data source in an accepted format. • Assist in the execution of the data conversion program and provide access to environments as needed. • Provide resources to validate the conversion statistics and the quality of the data converted into Accela Civic Platform • Historical and in-flight data has been converted to Accela Civic Platform testing environment according to the Data Conversion Mapping document. • Ten (10) business days total Following the data conversion of the historical and in-flight data the documents attached to the legacy data will be loaded into the Accela system on a record-by-record basis. In terms of specific output, the following will be executed for this deliverable: ⮚ Completion of document migration to the converted records. • Provide an interface to transfer the converted data documents on a record-by-record basis. • Providing the documents on an accessible shared directory with directories for each converted records. • Metadata and documents to be imported will be in the directories. • Provide resources to validate the document conversion. • Historical data has been converted to Accela Civic Platform testing environment according to the Data Conversion Mapping document.
Acceptance Review Period. The City will have 5 business days to conduct an initial review of the Interface Specification document(s.) If no changes or comments are requested within the 5 days, the Interface Specification document(s.) is considered approved by the City. Upon delivery of initial feedback, Avocette will complete the necessary changes and updates. The second and final review will have 3 business days for acceptance. If no changes or comments are requested within the 3 days, the Interface Specification document(s.) is considered approved and eligible for invoicing.
Acceptance Review Period. Ten (10) business days total DELIVERABLE 8: HISTORICAL DATA CONVERSION DEVELOPMENT - TIDEMARK Upon Agency approval of the Historical Data Conversion Specifications document, (Deliverable 7), Accela will provide a program(s) to migrate appropriate historical data into Accela Civic Platform. Upon receipt of the conversion from Accela, the Agency DBA will load the data into the Test environment for validation. In terms of specific output, the following will be executed for this deliverable: Completion of migrated data into Accela Civic Platform development or test environment. • Provide a program to migrate historical data into the Agency’s AA test database environment. • Each data conversion will include up to three (3) full conversion loads for client testing • Validate the successful completion of the migration of historical data into the Agency’s test environment. • Providing the legacy data source in an accepted format • Assist in the execution of the data conversion program and provide access to environments as needed • Provide resources to validate the conversion statistics and the quality of the data converted into Accela Civic Platform • Historical data has been converted to Accela Civic Platform testing environment according to the Data Conversion Mapping document. • Ten (10) business days total SYSTEM INTERFACES For each interface, the Accela technical lead will work together with Agency’s technical lead and business leads to document functional and technical requirements of the interface in an Interface Specifications Document. Interface development begins upon written approval of the specifications. It is expected all interfaces will use Accela’s GovXML, web services or batch engine. No custom or third party integration tool will be used to accomplish input or output of data to/from the Accela system. In other words, data coming into Accela and data coming from Accela will use the existing integration technology. Agency responsibility includes obtaining permission for level/type of integration from appropriate application owners (including on premises or cloud/hosted, etc.). Further, Agency will ensure that Accela resources have access to a Dev or Test version of the 3rd party system for interface development. All interfaces will be developed against 1 (one), agreed upon version of the 3rd party system. Accela will conduct Analysis and Development (Deliverable 9) for each system that will be interfaced with Accela within the scope of this imp...
Acceptance Review Period. Ten (10) business days total DELIVERABLE 10: BUSINESS RULES During the configuration Analysis stage of the implementation project, Accela will identify opportunities to supplement the Accela Civic Platform base functionality via Event Manager Script Engine (EMSE) scripts and Expression Builder in order to validate and automate business processes. Accela will work with Agency to identify desired functionality, and subsequently will assist with prioritizing the needs in order to determine that will be developed by Accela within the scope of this implementation. The Business Rules developed by Accela can be used as models whereby Agency staff can develop and modify additional functionality as needed. Business Rules are broken out into two areas as defined below: • EMSE (Event Manager Scripting Engine) – used to script based on system activities, such as a before or after event, that allow the system to automate activities (example: do not allow an inspection to be scheduled prior to a specific workflow task, or, auto-calculate and invoice a fee upon application submittal) • Expression Builder – used to script form based interactions that occur prior to triggering and event or master script activity (example: auto-population form based data fields based on user-selected values) Prior to the development, the Agency will approve a design specification document that will be created jointly by the Agency and Accela. The approved document will be used as a basis for determining completion and approval of the deliverable. In terms of specific output, the following will be executed for this deliverable: Prioritized list of requirements that require Automation Specification documents for each required Automation Demonstration of completed Automations in development or test environments per the specifications document(s) • Work with Agency staff to identify potential uses of scripting • Assist with development of list of desired functionality • Aid the Agency in prioritizing which scripts will be developed by Accela • Develop scripts based on the specifications • Demonstrate functionality of scripts per specifications • Allocate the time for qualified business and technical experts for the script requirements sessions that are critical to the project success • Identify resources that will learn scripting tools and approaches for ongoing maintenance • Prioritize desired functionality to determine which scripts Accela will develop • Provide timely and appropriate ...
