17-RFP-07-Questionnaire and Requirements.docx

CITY OF FORT WORTH - PURCHASING DIVISION PROPRIETARY INFORMATION, QUALIFICATION QUESTIONNAIRE, AND MANDATORY REQUIREMENTS

RFP Title: Customer Information System (CIS) Software

Legal Name of Proposer:

1.0 PROPRIETARY INFORMATION

i. All material submitted to the City becomes public property and is subject to the Texas Public Information Act upon receipt.

ii. If a Bidder does not desire information that it believes to be proprietary in the bid to be disclosed, the bidder must list each page number in the chart below and must clearly mark and identify each page by including the word “PROPRIETARY” in all caps and highlighted yellow on the bottom center of each page at the time of submittal. The City will, to the extent allowed by law, endeavor to protect such information from disclosure. The final decision as to the information that must be disclosed lies with the Texas Attorney General. Note: Pricing may not be marked proprietary and will be made publicly available in the form of a bid tab following evaluation of all bids. By submitting a response, Bidders agree that pricing is not proprietary and may be released.

iii. Failure to identify proprietary information, as required in section 15.5 of “RFP-01 Instruction to Proposers,” will result in all unmarked sections being deemed non-proprietary and available upon public request.

2.0 PROPOSER’S QUALIFICATION QUESTIONNAIRE

The information provided on this questionnaire and in the Proposal submittal will be used to determine the responsiveness of the Proposal. Please answer each question thoroughly. Answers may be provided on a separate sheet as long as each response is labeled according to the question.

2.1 Will the agreement be available for Cooperative Agreement use?

Please refer to the Cooperative Purchasing clause in the “RFP-01 Instruction to Proposers” document.

Yes_______ No________

2.2 Prompt Payment Discount Terms: ____ Percent _______ Days (i.e. 3% Net 15, etc.)

2.3 How long has your company been in business?________________ (Attach information that can be used to verify your years of experience.)

2.4 Have there been any past or ongoing legal proceedings or disputes involving your company in relation to CIS implementations? _______

2.4.1 If so, provide any context or public documentation you are able to share. ____________________________________________

2.5 In the last 5 years, how many SaaS implementations of U.S. water / wastewater utilities >250,000 accounts has your company completed?

2.5.1 List additional implementations that have been started but have not yet been completed.

2.6 Are your Company’s Data Centers located in the U.S.?

Yes_______ No________

2.7 Does your company have a Level 1 support team located in the U.S.?

Yes_______ No________

2.8 Upgrades and Additional Capabilities Available

2.8.1 Provide an overview of the proposed CIS product’s evolution, by major release, from the first release of the product to present. (If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.8.2 Describe the expected future frequency of keeping the proposed solution current and patched under a standard maintenance contract.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.8.3 Describe how future releases and enhancements of the proposed CIS solution are priced?

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.8.4 Do enhancements require relicensing or a relicensing fee?

Yes_______ No________

If yes explain why:

2.9 Vision and Planned Enhancements

2.9.1 Describe the vision and strategy for the future of the proposed CIS solution, including a description of the product enhancements that are in the planning or design stage. Provide an estimated release schedule for these product enhancements. (If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.9.2 Describe the foreseeable roadmap for the software including technology and underlying platform.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.9.3 Provide a roadmap of upgrades/features for the core CIS and all other products being proposed.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.10 Warranty and Maintenance Information

2.10.1 Describe the nature of maintenance coverage available to the City.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.10.2 Provide all warranty information in responder’s standard format. *As an attachment (If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.10.3 Provide the period of coverage of the warranty. The City expects that the Maintenance Agreement will go into effect upon System Acceptance following a successful go-live and that the City will submit its first annual maintenance payment one year from that date.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.10.4 Describe the support hours, methods of support available to the City’s staff, and problem resolution times.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.10.5 Describe available technical training curriculum for the City’s administrators and staff.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11 Solutions Support

2.11.1 Are there components that your company outsources?

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

Yes___ No ___ If yes provide a list of components

2.11.2 Describe your company’s usage of offshore resources.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.3 Describe available training and support related to version changes.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.4 Describe system documentation made available by default to users of the CIS and all other modules included in this response.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.5 Does your company maintain an electronic “knowledge base” of known problems that FWWD may access online?

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.6 Describe your company’s escalation process in the event FWWD is not satisfied with the quality or timeliness of responses to problems.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.7 Describe any User Forum, User Groups, or Development Community that your company hosts. Describe the type and frequency of organized meetings or communications.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.8 Does your company publish a customer contact list to facilitate discussions among customers, e.g., user groups.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.11.9 Describe the ownership of CIS data. FWWD expects to own all data whether customer data, meter data, processed data, system data, or the work product of a system FWWD is licensing. FWWD’s ownership of the data is perpetual, regardless of the status of licenses or maintenance agreements.

(If included in the proposal, please specify the corresponding page number and section where it can be found.)

2.12 Separate from the price proposal, propose options that may positively affect price or schedule to accomplish the goals of the project. (As an attachment)

3.0 Proposal Should Include:

3.1 Executive Summary

3.2 Software Description

3.2.1 Description of the software

3.2.2 Description of all modules and components inclusive of all third-party applications

3.3 List recommendations and cost of items that may be missing from the scope.

3.4 Solution Support (general information).

3.5 No more than 25 pages

4.0 DOCUMENTS REQUIRED FOR PROPOSAL TO BE CONSIDERED RESPONSIVE

The following documents and information is required to be submitted to be considered responsive:

4.1 RFP-02-CIQ Form

4.2 RFP-03-Authorized Signature and Contact Details

4.3 RFP-04-Reference Sheet

4.4 RFP-07-Questionnaire and Requirements

4.5 Signed Addendum(s)

4.6 Exhibit A - Reports

4.7 Exhibit B – FWWD RFP Functional Requirements

4.8 Exhibit C – FWWD RFP Technical Requirements

4.9 Exhibit D – FWWD Narrative Requirements

4.10 Exhibit E – FWWD CIS Pricing Model

4.11 Warranty Information

image1.jpeg