Attachment_3_-_Narrative_Response.docx

ATTACHMENT 3 – NARRATIVE RESPONSE

Bidder Name: Enter Bidder Name

Instructions: Complete responses and submit with proposal as directed below. Refer to Request for Proposal (RFP) Sections 3.1.1 and 6.3.2 for more information.

SECTION A: ADMINISTRATIVE RESPONSES

Bidders must provide responses in the table provided below and submit with proposals as “Attachment 3 – Administrative Responses”.

Administrative Responses

1. Secretary of State (RFP Section 3.2.2) – Provide your organization type (e.g., Corporation, Limited Liability Company (LLC), Limited Liability Partnership (LLP), or a Limited Partnership (LP)). Provide your company’s Secretary of State business number or indicate application status.

Bidder Response:

2. Darfur Contracting Act (RFP Section 3.2.5) – Has your company conducted business outside of the United States in the last three (3) years? Please indicate “Yes” or “No”. If “Yes”, complete and submit the Darfur Contracting Act form.

Bidder Response:

3. Subcontractors (RFP Section 3.2.14) – Are you planning to utilize subcontractors for this MSA? Complete and return the Bidder Declaration Form, GSPD-05-105 with your proposal.

Bidder Response:

4. California-Certified Small Business (RFP Section 3.2.15) – Are you a California certified small business claiming the small business preference? Please indicate “Yes” or “No”.

Bidder Response:

5. Non-Small Business Subcontractor (RFP Section 3.2.15) – Are you a non-small business claiming at least 25 percent small business subcontractor preference? Please indicate “Yes” or “No”.

Bidder Response:

6. California-Certified DVBE (RFP Section 3.2.17) – Are you a California certified Disabled Veteran Business Enterprise (DVBE)? If “Yes”, complete and return the DVBE Declaration Form (DGS PD 843) with your proposal.

Bidder Response:

SECTION B: TECHNICAL RESPONSES

Bidders must provide information for each line item outlined below in a separate attachment titled “Attachment 3B – Technical Responses”. Response should be in Microsoft Word format and labeled with the corresponding item number.

1. Corporate Qualifications

· Date of incorporation;

· Overview of main offices, highlighting any offices and support staff located in California;

· Experience with GTFS-Realtime Services, On-Vehicle Devices, and/or journey planning applications.

The response should be limited to one (1) page.

2. Experience

Bidder must include the following information for each project:

· Client name;

· Client contact (Name/Title/Email/Phone);

· Project description;

· Products or services provided;

· Dates of service;

· Number of routes and number of vehicles involved;

· Contract dollar value;

· List of journey planning application(s) involved;

· Why project experience is relevant to this RFP.

The response should be limited to five (5) pages.

3. Technical Proposal

i. Approach to feed creation, quality control for feed accuracy, and feed maintenance.

ii. Prediction algorithm (particularly how your solution deals with unplanned diversions, delayed start of trips, connectivity dead zones, etc.).

iii. Method and process to accurately ascertain the trip_id, vehicle_id, and route_id from the On-Vehicle Device.

iv. Approach to providing the Service Change and Alerts Management Service, including a description of the platform, functionality, and accessibility of the solution.

v. Approach to data storage (including data capacity, data retrieval mechanisms, and level of access / ownership offered to the Transit Provider).

vi. Approach to creating an Ingestion Point that facilitates the integration of GTFS-Realtime data from On-Vehicle Devices not supplied by the Contractor.

a. Bidder must also include as an attachment to the Technical Proposal a specification sheet for the solution’s Ingestion Point in OpenAPI format, including details for protocol (e.g., HTTP), interface language (e.g. JSON, YAML, XML), and authentication (e.g., API key). Specification sheet will not count towards item #3.a page limit.

vii. Approach to Service Acceptance for GTFS-Realtime Services (including installation instructions for Transit Provider personnel for On-Vehicle Device(s), if applicable, and estimated timelines, and training overview).

a. Bidder must also include as an attachment a generic template(s) that can be used as a starting point for engaging with Transit Providers on a project implementation plan. The template(s) should reflect the Bidder’s approach and should be limited to five (5) pages. Templates will not count towards the section page limit.

viii. Overview of solution for Customer Support for GTFS-Realtime Services, including creation and dissemination of training plans and educational materials, staff resourcing, and customer support ticketing system.