Vendor_Experience.docx

Vendor Experience Response

The following subsections request information from Proposers in the following areas:

1. General Experience

2. References Interface

3. Experience

4. Implementation Methodology

5. Public Safety Experience

Proposers are required to respond to all questions in one of two ways:

1. Provide information where requested directly in the spaces indicated; or

2. Provide information requested in an attachment clearly indicating the associated RFP page number and item number.

General Experience

1. Headquarters Address:

2. Address Serving Pasadena:

3. How many years has the company actively participated in public safety software?

Years: ______

4. How many employees does the company have?

Nationwide: _____ In Local Office(s): _____

5. What was the prime vendor's annual gross revenue during the last previous three fiscal years?

Fiscal Year 2023 _________ 2024 _________ 2025 __________

6. If a public company, please include a copy of your financial statements for the last year.

7. Provide Dun & Bradstreet number: _______________

8. Identify any contracts which have been cancelled or defaulted (for any reason) during the past five years.

9. Summarize all litigation (regardless of disposition/status) involving the Proposer as a plaintiff or defendant within the past five years. If the Proposer has been ordered by a Court not to disclose a summary of the case, list this fact.

Vendor Experience

In-Vehicle Mobile Audio and Video (MAV) Recording RFP – City of Pasadena Vendor Experience 2

10. Identify the providing-company name in the column next to the product or service to be provided by that vendor (add lines as required to describe the role of additional vendors/subcontractors).

Provided By (Vendor Name)

References Instructions: Complete the list below for ten (10) sites that are currently using the proposed system(s), and:

1. Identify the total number of installed sites with a similar configuration: _____

2. Provide a list of all reference sites (regardless of their stage of implementation). List attached? Y/N ___ Name, Title, Email, Phone

Fleet Size

Operational Applications

Interfaces

Installation Dates

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

Interface Experience

1. Describe your experience working with integration between the proposed solution and third-party software, such as CAD, ALPR, analytics software, mobile computing, etc.? What systems have you successfully integrated with? For which agency?

Attachment location ______

2. Has the vendor previously interfaced with the California Department of Justice for submitting criminal statistics (eCARS)? If so, confirm that the vendor is certified by the State for such purposes?

Y/N ______

3. Unless otherwise specified, PPD will collaboratively develop a single data exchange schema for each of the required data exchanges (interfaces). XML-based, NIST, National Information Exchange Model (NIEM) conformant exchanges are preferred. Although not all of the data elements agreed upon for a specific data exchange (interface) will contain data in each exchange instance, PPD expects to maintain a set of consistent and valid data exchanges across all of the system’s interfaces. The intent is to keep the interfaces and data exchanges as simple and as standardized as possible. Please explain, in an attachment, how you will participate in this process?

Attachment location ______

4. PPD prefers that solutions conform to criminal justice standards including but not limited to Department of Justice's (DOJ) National Information Exchange Model (NIEM)[footnoteRef:1], Global Justice Reference Architecture (JRA)[footnoteRef:2], and standards developed by the National Institute of Standards and Technology (NIST)[footnoteRef:3]. In particular, the JRA provides a framework for decision making about information sharing solutions by defining highly adaptive justice system service-oriented architecture (SOA). Please describe, in an attachment, how the proposed system will conform to these standards? [1: http://www.niem.gov/] [2: http://it.ojp.gov/default.aspx?area=nationalInitiatives&page=1015] [3: http://www.nist.gov/]

Attachment location ______

5. PPD will be responsible for providing adequate network connectivity between the system and the external systems and databases interfaced to the system as described herein. Please identify the bandwidth requirements between the system and externally interfaced systems and databases necessary to effectively accomplish the proposed interfaces. Where the network requirements for a specific interface differ from the requirements identified in the response to this paragraph, the specific network requirements for the interface should be described in the response/explanation for that interface?

Attachment location ______

6. PPD prefers a system that performs any required data formatting and transformation for exchanging information (e.g., discrete data, data streams, files, images, etc.) between system databases and external systems and databases. Please describe how the proposed system will provide this functionality?

Attachment location ______

7. PPD desires a system that is able to notify users if access to an interface or interface network is unavailable. Please confirm that your solution provides such functionality?

Y/N ______

Implementation Methodology

1. PPD requires a normal COTS design, configuration, testing, training and implementation schedule.

2. PPD requires a contract with a single company (Prime Contractor) that will manage the entire proposed system implementation and ongoing support. Provide all relevant information concerning the ability to provide Prime Contractor services during the complete lifecycle of the proposed system (e.g., design, configuration, testing, training, implementation, support and maintenance).

3. Describe the Proposer’s management, technical and organizational approach, resources, and controls to be employed to successfully accomplish project planning risk management, quality control, budget adherence, schedule requirements and integration process for all proposed systems.

Provide a proposed project schedule in MS Project format including resources and milestones. The intent of PPD is to develop and maintain a shared project schedule that includes all Proposer and PPD project stakeholders’ tasks and activities. The implementation schedule must incorporate the major subproject implementation phases such as installation, testing, training.

4. PPD will only accept Proposer personnel who have significant and relevant experience with the proposed system and can demonstrate a successful record at locations of similar size and complexity as the PPD project. Describe Proposer’s project management qualifications.

5. Identify staffing resources and level of effort for each major task.

6. Provide an organizational chart for proposed project personnel including proposed sub-contractors, and indicate the tasks to be assigned to subcontractors.

Define PPD requirements for staffing resources and level of effort by system for each major phase; including expected skill set needed to successfully complete each task.

7. Provide resumes of all key Proposer personnel that will be assigned to the project.

8. Describe the roles and responsibilities for all key Proposer personnel.

9. Identify whether PPD will be their primary assignment and/or a projection of other assignments they may be working on during the project life-cycle.

10. Description of facilities and equipment that PPD is required to provide for on-site staff.

11. Describe estimated on-site time for identified milestones.

12. All Proposer personnel assigned to work on-site on the proposed system shall be required to undergo a criminal history check and maintain a satisfactory status during the entire project. Off-site personnel may also be subject to a criminal history check. Please note that arrangements for required criminal history checks should be made in advance with appropriate PPD personnel. PPD reserves the right to reject any personnel for any reason. All key personnel will be required to sign a confidentiality agreement for access to sensitive data.

13. Provide the status of PMP and/or equivalent certification for key Proposer personnel.

14. Describe the proposed conflict resolution process if problems are encountered with Proposer personnel.

15. Describe the ability of the Proposer to participate in a weekly project meeting to report progress toward contract deliverables, update status from the previous reporting period, and advise current objectives, problems or delay issues, proposed corrections and other relevant information.

16. PPD understands the implementation of the proposed system will require new business processes and a change in some policies, procedures and training protocols. Describe any change management solutions provided by the Proposer that are a component of the proposal.

17. Describe the proposed approach to test the system throughout the life cycle of the project to ensure confidence prior to a formal “Go/No go” cutover decision.

Describe the approach to migrate to the new MAV system.

18. Confirm the Proposer shall provide a response for managing all system testing activities including but not limited to:

a. Product Performance Test

b. Factory Acceptance Test

c. Onsite Installation Test (e.g., immediately following initial install)

d. Reliability, Redundancy/Failover Tests

e. Peak Workload and Capacity Tests

f. Configuration Tests (e.g., through the course of the configuration process)

g. Interface Tests

h. Data Conversion Tests

i. System Integration Tests (e.g., all applications and interfaces of the proposed system)

j. Security Tests

k. Pre-Cutover Test

l. Functional Acceptance Test

19. Describe if the Proposer provides draft test plans for PPD to supplement and approve.

20. Describe the ability to meet and/or exceed the following reliability criteria:

After the successful completion of the cutover period, there shall be a minimum thirty (30) day Reliability Test Period during which the newly installed system will be in production and its performance monitored. During this period, the system must perform fully without degradation of any kind in order for the Reliability Test Period to be satisfied. If major defects or numerous minor defects are found during the Reliability Test Period, the defect(s) shall be documented by the Proposer along with PPD. Prior to completion of the Reliability Test Period, the Proposer shall resolve all outstanding issues. Once all of the issues have been addressed and resolved to PPD’s satisfaction, the City will proceed with internal steps to give final approval to the Reliability Test Period.

21. Describe how the Proposer could demonstrate through an acceptance process, a performance (stress) test that the system performs as required in PPD’s technical environment and that the system meets or exceeds the proposed performance requirements.

22. The Proposer agrees that the final acceptance test will exercise all functionality, interfaces and components successfully.

23. Describe the process for migration from one environment to another (e.g., test environment to production).

Public Safety Experience

1. Describe the company’s affiliation with public safety organizations such as IACP (International Association of Chiefs of Police) and CALEA (Commission on Accreditation for Law Enforcement Agencies).

Describe the company leverages federal law enforcement security standards, guidelines and best practices.

Describe the process the Proposer employs concerning security background checks of employees who will be working on the Pasadena project.

2. Describe how the proposed system is resilient to cyber security threats.

3. Describe how the proposed system meets and/or exceeds cyber security standards, guidelines and best practices.

4. Describe how the Proposer will maintain the system post-implementation to ensure it is safe from cyber security related problems.

Describe how the Proposer stays current with this emerging technology and ensures the proposed system is updated as required.