CIT COM INC. 1 - 2004 - Laserfiche WebLink

Home Browse Search

^ Mobile Accessibility and Reporting Requirements • GIS/Mapping Integration Requirements • NCIC/NLETS/DMV Interface Requirements Internal and External Reporting Requirements Additionally, we would document user requirements including, but not limited to ^ Reliability Requirements • Peripheral Requirements ^ Documentation and Training Requirements ^ Security and Access Controls ^ Performance, Response Time, Implementation and Timeframe Requirements The RFP document would fully describe the criteria to be used in evaluating the proposals as well as set forth the plan to be followed in conducting the evaluation. The RFP would be submitted in draft form to project team members for review and amendment. Following Steering Committee approval, a final copy would be delivered to the City for release. The RFP would be released to a list of qualified vendors and third party integrators (prepared cooperatively with the City), as well as to any vendor responding to the open bid (in concurrence with City requirements). Apre-proposal conference would be conducted for prospective vendors, addressing questions and issues. Task III - 2: Proposal Evaluation (50 Hours) Cit Com, acting as a member of the evaluation team, would review each proposal response to determine which vendor can best meet the City's requirements. Each proposal would also be reviewed by members of the City for completeness and to ensure that they properly address the functional requirements of the RFP. During this portion of the project, the evaluation and selection criteria methodology would be applied, thus eliminating vendors who fail to meet the requirements. Using the evaluation criteria as a guide, qualified proposals would be evaluated in depth based upon (at a minimum) the following seventeen criteria: l . Adherence of the proposal to the format. 2. Completeness of the proposal. 14