Records Management System (RMS) Modernization Project Pre-Proposal - - PowerPoint PPT Presentation
Request for Proposals (RFP) RFP 16-011 Phoenix Fire Department Computer Aided Dispatch (CAD) & Records Management System (RMS) Modernization Project Pre-Proposal Meeting December 3, 2015 9:00 A.M. Fire Administration Building Finance
December 3, 2015 – 9:00 A.M. Fire Administration Building
Finance Department
Procurement Officer – Andria Williams Project Sponsor – Jeff Case, Deputy Chief Technical Consultant – William “Bill” Romesburg
2
3
4
5
6
Tab 1 Phoenix Fire CAD & RMS Functional Requirements, Subsections 3.1, 3.2 Tab 2 Phoenix Fire System Architecture and Technical Design, Subsection 4 Tab 3 Implementation & Support, Subsections 5, 6, 7, 8, 9 Tab 4 Qualifications, Experience and References Tab 5 Pricing Tab 6 References Tab 7 Submittal of Offer, Including Source Code Escrow Agreement, Software License Agreement, Support Maintenance Agreement and Software Warranty Agreement Tab 8 Addenda Tab 9 Alternative Terms/Exceptions Tab 10 Evaluation literature, illustrations, specification sheets, blueprints and photos
7
Functional and Technical Requirements 0-400 Points Implementation and Support 0-250 Points Qualifications, Experience and References 0-150 Points Compliance with Terms and Conditions 0-100 Points Pricing 0-100 Points Total Possible Points 1000 points
8
9
functional requirements for PFD, as outlined in the RFP.
availability, security, and reliability.
CAD system to allow PFD to meet current and future needs without extensive software customization (this should
vendor to provide long-term support and the ability of PFD to implement future upgrades and enhancements to the product).
satisfaction.
departmental performance and efficiency.
for reporting and inquiries without the need for a programming specialist.
integration with the PFD- Record Management System (PFD RMS) and other applications (such as the City of Mesa Fire Department CAD). 10
reporting formats.
data and allow retrieval from all levels of the department(s).
solution for all departmental training and certifications.
and store transactional data related to Incidents.
PFD operations (e.g. Electronic Patient Care Reporting).
tools.
management tool for fire facilities and equipment.
Fire Prevention activities:
11
implementation of comparable projects with agencies of similar size and complexity as the City of Phoenix and its Automatic Aid Consortium
to the CAD business.
company.
project staff to assign to PFD for the duration of the entire project.
customer support on a 24 hours per day, 7 days per week basis.
strategy that factors-in customer needs and wants. 12
Q1: Are we able to respond to the RMS portion of the RFP? A1: Only integrated CAD and RMS solutions will be considered responsive. Q2: If so, are we able to respond on our own and also with any CAD vendors we choose? A2: There are no restrictions on a single RMS solution being included with more than one solution proposal. Q3: Section IV - Scope of Work - Section 1.4 Current Environment - Please identify the FRMS systems in use by members of the Automatic Aid Consortium, such as the Mesa Fire Department? A3: We do not have access to this information.
13
Q4: Section IV - Scope of Work - Section 1.4 Current Environment - For licensing purposes, please provide the number of CAD, Mobile and RMS users of the proposed system? A4: The count of active user accounts on the current CAD system is 8200. There is only one class of user in the current model. Q5: Attachment C - Technical Interfaces - Should interfaces identified as both current and future phases be included in vendor proposals? A5: Yes all interfaces listing in Attachment C are in scope. Q6: Attachment A - Tab B - B.8.17.2: Do other agency CAD systems have an interface or remote console access to the Back Up Status System (BUSS)? A6: No, only City of Phoenix Fire Employees can access the BuSS.
14
Q7: Attachment A - Tab G - G.5.24 and Attachment A - Tab B - B.7.01, Is there a requirement to synchronize the computer time to the logging recorder if it can be done with an NTP device? A7: The intention is that the system clock of all devices should be in sync at all times with the same NTP device. There was no intention to describe how this should be accomplished. Q8: 7.2 Product Configuration. “The Vendor must supply a price listing for continued training of PFD’s project team in order to achieve a level
performed during the project, or post-acceptance refresher training? A8: Proposers should include all training required to support the transition to operations that will be required. If post-acceptance refresher training has been found to be a beneficial activity, please include it in the response.
15
Q9: 7.6 Post Installation Support. 4.712.03 “PFD requires the Vendor to provide immediate production critical support on site at PFD during the first 120-180 days of operation. Please describe the team that will be present to provide the post installation support.” Is the City looking for a 24/7 onsite support, or on-call remote support? A9: Yes, on-site support for 120-180 days is required. Q10: 8.2 Training: Can the City provide a roll-based breakdown of the “150 operational employees” that the City requires to receive train-the–trainer training (i.e.; system administrators, call-takers, dispatchers, supervisors, ad hoc reporting specialists, etc) by application (CAD vs Fire RMS). A10: No, the count of city employees to be trained was provided for estimating purposes based on prior project experience. The exact breakdown will be finalized during project planning.
16
Q11: Does the city identified the budget for the project? A11: Yes Q12: Who is the vendor currently providing the existing system? A12: Northrop Grumman
17
18