CORE & MAIN LP (#2027021) - Laserfiche WebLink

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 7 Internal Use Only E.Approvals for work. F.Change orders. Each AR Form shall include at a minimum the following: G.Unique identifying number for document reference. H.Date of submission, previous submission history and date of approval. I.Project name and reference number. J.Name and signature of the Contractor’s Project Manager. K.Description of work the Contractor is requesting Acceptance on. L.Supporting documents as may be required by the City. M.Description of approval / corrective action required. The City shall review all submitted AR Forms within fifteen (15) business days of receipt and provide one of the following responses: N.Acceptance Approval: The City accepts the Work detailed. O.Conditional Approval: The City accepts the Work detailed, but the City has provided some additional actions the Contractor shall perform to complete the Work. Conditional Approval may or may not hold up payment. P.Acceptance Not Approved. The City rejects the Contractor’s request for acceptance. This will not allow the Contractor to proceed to invoice for the work detailed on the AR Form. 1.3.Integration and Testing Process 1.3.1.System Architecture Diagram The Contractor shall develop a system architecture diagram that includes all proposed systems and interfaces that connect to the existing City systems. 1.3.2.Interface Development Steps The Contractor and the City shall work together through the following steps for each proposed interface: A.Business Requirement Gathering Meetings: The Contractor shall develop and lead a series of business requirements gathering sessions that will identify the required scope and any functional alternatives that may be available. The Contractor shall document the outcomes and decisions that will allow the development of the Functional Design Document. B.Functional Design Document (FDD): The Contractor and the City shall document all fields of data that will be passed between systems, how data will be passed, the frequency with which it will be passed, detail the list of acceptable values of each system, detail any data validations performed prior to or during data transfer, and define any conditions and triggers that will initiate an action through the interface. The FDD must include field-level mapping, data validation rules, error handling procedures, and security requirements (e.g. encryption standards for data in transit and at rest). The FDD document for each interface shall be signed off on by all parties (including City IT), agreeing that the documents represent the required functionality for the specific business function. It is expected that the FDD process will go through numerous reviews and a minimum of three (3) weeks of testing. C.Interface Development: The Contractor and the City shall develop their respective sides of all interfaces based on the required details in the approved FDD document. It is expected the interface development step shall take six (6) weeks from the approved FDD document. Docusign Envelope ID: 6AD75F50-8A33-85A5-8039-9E3E1257A838Docusign Envelope ID: 177582DA-4F1C-8834-813C-BC4FD03AA45E