Common use of Implementation Planning/Functional Requirements Verification Clause in Contracts

Implementation Planning/Functional Requirements Verification. Immediately after contract execution, the CONTRACTOR shall develop a formal Functional Specifications Document, which details the capabilities of the CONTRACTOR’s system and which will serve as the basis for confirming conditional and final acceptance. Working with DLEC’s Project Team, the CONTRACTOR and DLEC shall validate the RFP functional requirements, mutually agree in writing to any further modifications to the software that will be required beyond those identified in Exhibit I (Correspondence) and clarify any issues relating to the implementation of the CONTRACTOR’S proposed products. The documentation shall include a description of any functional changes or additions beyond those identified in Exhibit I (Correspondence), the operational impact of said changes, and screen layout(s) showing the new data elements and descriptions of their functionality that will be included in the final system to be installed. The CONTRACTOR shall also provide, at that time, a fixed price quote to cover all costs related to the modification effort. Changes or additions shall not occur until DLEC has approved them in writing and instructed the CONTRACTOR to proceed. Concurrent with this effort, the CONTRACTOR will prepare a formal, expanded Project Schedule that includes all project tasks, subtasks, resource requirements, and associated start and end dates for each identified task/subtask. This expanded project schedule shall be submitted to DLEC for review and approval. This document shall be completed and submitted to DLEC within ten (10) working days subsequent to the completion and approval of any functional modifications. Failure to complete the expanded project schedule document and the functional specifications documentation as required herein, may result in default of the Agreement and release DLEC from any further obligations to the CONTRACTOR.

Implementation Planning/Functional Requirements Verification. Immediately after contract execution, the CONTRACTOR shall develop a formal Functional Specifications Document, which details the capabilities of the CONTRACTOR’s system and which will serve as the basis for confirming conditional and final acceptance. Working with DLECSECC’s Project Team, the CONTRACTOR and DLEC SECC shall validate the RFP functional requirements, mutually agree in writing to any further modifications to the software that will be required beyond those identified in Exhibit I (Correspondence) and clarify any issues relating to the implementation of the CONTRACTOR’S proposed products. The documentation shall include a description of any functional changes or additions beyond those identified in Exhibit I (Correspondence), the operational impact of said changes, and screen layout(s) showing the new data elements and descriptions of their functionality that will be included in the final system to be installed. The CONTRACTOR shall also provide, at that time, a fixed price quote to cover all costs related to the modification effort. Changes or additions shall not occur until DLEC SECC has approved them in writing and instructed the CONTRACTOR to proceed. Concurrent with this effort, the CONTRACTOR will prepare a formal, expanded Project Schedule that includes all project tasks, subtasks, resource requirements, and associated start and end dates for each identified task/subtask. This expanded project schedule shall be submitted to DLEC SECC for review and approval. This document shall be completed and submitted to DLEC SECC within ten (10) working days subsequent to the completion and approval of any functional modifications. Failure to complete the expanded project schedule document and the functional specifications documentation as required herein, may result in default of the Agreement and release DLEC SECC from any further obligations to the CONTRACTOR.