11-Appendix J - Questionnaire.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Next Generation 9-1-1 Evolution
- Solicitation number
- GSS26716-E911_SVC
- Issued by
- Delaware
About this file
This is a questionnaire document for the Next Generation 9-1-1 Evolution contract opportunity in Delaware, addressing comprehensive requirements for public safety software solutions serving Delaware's Public Safety Answering Points (PSAPs) and emergency response agencies, including the Delaware State Police (DSP). The questionnaire consists of twelve detailed technical inquiries requiring vendors to demonstrate how their proposed Computer-Aided Dispatch (CAD) and Mobile solutions address specific operational needs across the state's five geographically dispersed system cores. Key requirements include maintaining regional configuration autonomy while enabling statewide information sharing, accommodating DSP's need to operate uniformly across the state on a single server while retaining unique organizational identifiers and personnel assignments, supporting differentiated CAD templates by jurisdiction, enabling cross-system event sharing via CAD-to-CAD functionality using NENA standards (EIDO and Conveyance), and providing native iOS/Android mobile applications with enterprise security protocols.
Additional technical requirements addressed in the questionnaire encompass hybrid fire and EMS dispatch capabilities combining Automatic Vehicle Location (AVL) data with static station response methods, integration with fire pre-planning documents accessible through mobile platforms, robust Esri-based mapping with dynamic layer ingestion and advanced location services, advanced paramedic split-crew management to comply with state ALS staffing mandates, NERIS-compliant fire records management system with pre-population of tactical benchmark times, integration with the state's LEISS system for impaired driving report data capture and analysis, handheld solutions supporting continuous logged-in ready-state capability for volunteer fire services, and interoperability with existing third-party applications such as Chief360. Vendors are required to provide text-based responses only in the specified Excel format without modifying worksheet structures, using special characters, formulas, or alternative file formats.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 7-Appendix F - Interfaces Integrations.xlsx | XLSX spreadsheet | |
| 4-READ ME FIRST Appendix C Online Bid Submission Portal Instructions.pdf | ||
| 8-Appendix G - CAD Mobile Data Functional Specifications.xlsx | XLSX spreadsheet | |
| 13-Appendix L CHaaS-Recorder Service Level Agreement.pdf | ||
| 10-Appendix I - Fire Records Specification Inspections.xlsx | XLSX spreadsheet | |
| 14-Appendix M ESInet-NGCS Service Level Agreement.pdf | ||
| 1-26716-E911 SVC.pdf | ||
| 2-Appendix B - Pricing CHaas-REC and ESInet-NGCS.xlsx | XLSX spreadsheet | |
| 12-Appendix K - Professional Services Agreement Draft.pdf | ||
| 6-Appendix E - Technical Combined.xlsx | XLSX spreadsheet | |
| 9-Appendix H - Law Enforcement Records Management Specifications.xlsx | XLSX spreadsheet | |
| 5-Appendix D Required Vendor Forms.xlsx | XLSX spreadsheet | |
| 3-Appendix B1 - Pricing CAD, Mobile, LERMS and Fire RMS.xlsx | XLSX spreadsheet |
Show all 13
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| [insert contract name] |
| insert contract number] |
Questionnaire
Instructions
| Please provide a response to each question identified on the Questionnaire tab. These responses are intended to supplemental your technical proposal, not replace. |
| When pasting content, please use Paste Special as Text without any formatting. |
| You can only submit text based responses, please do not use special characters like emojis. |
| Please do not change the structure of any of the worksheets. Changing the structure will invalidate your submission. |
| Any additional information outside of the given structure of the worksheets will not be visible to the purchaser. |
| Please do not save this file in a different format. Saving this file in a different format will invalidate your submission. |
| Please do not use Excel formulas in your responses. |
Questionnaire
| NEXT GENERATION 9-1-1 EVOLUTION |
| GSS26716-E911_SVC |
| Question | Response |
| Autonomy across CAD Cores - As described in the background section of this RFP, PSAPs across Delaware are assigned to one of five system cores geographically dispersed throughout the state and, consequently, PSAPs have autonomy as to how their assigned core is configured. The statewide map within each core is also configured to display only the geographic areas specific to the agencies assigned to that core. Delaware PSAPs seek to maintain a certain degree of configuration autonomy but are interested in a solution that would enhance situational awareness and information sharing across cores. Describe how your solution could provide a more efficient statewide deployment yet retain the ability to implement unique configuration parameters by region. | |
| Delaware State Police (DSP) CAD Core – DSP currently operates on the North, Central, and South Cores, which creates several operational challenges. DSP has expressed a desire to operate uniformly across the State so that units can be tracked across counties while maintaining their unique unit identifiers. DSP will continue to use three (3) Originating Agency Identifiers (ORIs), but will operate on a single server. The solution must allow the same unit numbers and personnel to be used under each ORI, while ensuring that officers can work anywhere in the State and remain ORI-specific to the county in which they are operating. The current CAD system does not support this functionality, as unit numbers must be unique even when different ORIs are being used. DSP also seeks the ability to access DELJIS statewide through the appropriate ORI, regardless of where officers are operating. Describe how you would implement your solution to accommodate these DSP business needs. | |
| DSP Templates – DSP operates in combined dispatch centers where DSP can differentiate their CAD templates from those commonly used by other telecommunicators within the center. DSP templates are aligned to the area they are working in, if working in Sussex County dispatch, they only need to view incidents for Sussex County; however, they need the ability to create selectable tabs for other areas/counties on their screen where they can toggle to view incidents in that region. These selectable other region tabs would not be viewable on screens of other dispatchers at that dispatch location. Please explain how your solution can accommodate this capability. | |
| DSP Unit Identifiers – Each trooper in Delaware is assigned a take-home vehicle that is provided a fixed number based on their assigned badge or personnel number, e.g., Unit Identifier (IDN) 1321. With the current multi-core infrastructure, IDN 1321 assigned to Kent Co. cannot be reassigned to cover a shift in another county or core region because the same IDN cannot be reused. This is problematic for DSP as troopers are routinely assigned to other counties to cover shifts. In the current system the trooper assigned to a neighboring county cannot sign in to the CAD/Mobile core for that county and, consequently, cannot receive data dispatches or be viewed on the CAD map. This must be rectified in the new CAD/Mobile environment. How would your solution overcome this obstacle and allow for unique identifiers for DSP vehicles regardless of their assignment during a given shift and allow them to be visible to any PSAP, regardless of the core they were operating on. | |
| CAD-to-CAD – This is an important capability currently in use extensively in the South Core where events are transferred between Tyler and CentralSquare systems. It is used daily for remote PD’s such as Smyrna and Milford. And to DELDOT for crash events. Further, if multiple cores are proposed, as is the case today, CAD-to-CAD between cores should be an inherent capability. Describe how your proposed system will allow for event sharing across system and whether the use of national standards – NENA EIDO (https://www.nena.org/page/standards#NENA-STA-021) and NENA Conveyance (https://www.nena.org/page/standards#NENA-STA-024) – will be employed in your solution. | |
| Handheld – Native iOS/Android applications are a necessity in the CAD solution as many first responders will rely on smartphones and tablets for both incident data and advanced location services. Explain whether native iOS/Android applications are offered, what security protocols are used to access the software (e.g., agency provided multi-factor authentication), and what capabilities it offers to emergency responders in the field. | |
| Fire Pre-Plan – Although various fire records management systems (FRMS) are utilized by the fire services throughout the state, these systems do not allow in field access to pre-plans in the CAD/Mobile environment. Please explain if your solution can support the ability to access pre-plans, building schematics, etc. if a PDF file is available and can be hyperlinked to the location (e.g., high school) through mobile software. | |
| Hybrid Dispatch Capability – The proposed CAD system must have the capability to utilize a hybrid method for fire/EMS dispatching that allows for both AVL-based recommendations along with the standard unit recommendations consistent with a static station response. Specifically, the system should be able to use a standard emergency response zone method and should allow for transitioning to AVL (Automatic Vehicle Location) location—or a mix of both. This hybrid method would utilize the standard static “in station” resource list while at the same time allowing for “closest goes” based on AVL data. Sussex County is dependent on AVL data to dispatch the closes advance life support ambulance to medical calls in their jurisdiction. While CAD may recommend a resource based on static response parameters, dispatchers should have the capability to toggle and override that recommendation with the closest-available units based on AVL data. Proposers should explain if this type of dispatch feature is available in the solution offered and how it functions within your system. | |
| Fire Personnel Access to Mobile – Fire personnel rely heavily of Chief360 (https://chief360.com/) as the mobile data application to receive notifications of CAD events. Please explain if you have integrated with Chief360 and if your mobile data solution could be a better alternative for CAD to mobile/handheld event data transfer. In addition to the above, mobile data clients or handheld smartphones are often continuously logged into the system so they are always in ready mode for immediate response without the need for individual login. Further, with Delaware having many volunteer fire companies throughout the state, staffing of apparatus is fluid and the use of generic logins has alleviated any issues with assigning logins to personnel who are consistently rotating in and out of the fire service. Although the PSAPs recognize this is not an ideal security posture, the Delaware fire agencies desire to maintain “ready state” capability while enhancing security and are interested in solution alternatives to meet this need. | |
| CAD/Mobile Mapping Capabilities – Agencies are interested in robust mapping capabilities that fully integrated with Esri and can ingest layers natively and dynamically. Advancements in mapping capabilities should be available in the CAD and mobile data environments where mapping layers not routinely utilized can be accessed and rendered within the application. Boat ramp locations, buoy markers and other GIS data layers should be accessible when needed and imported dynamically through an Esri interface. The mapping solution must incorporate unit AVL data and handheld device locations but also be capable of showing the precise location of 911 callers using third-party advanced location services feeds from smartphones (e.g., RapidSOS). Proposers should describe in detail their integrated Mapping solution and how it addresses the above-described capabilities and what other features are offered (e.g., geofencing). | |
| ALS response – State law requires two paramedics to all advanced life support (ALS) calls. Thus, ALS units have two paramedics on board. These paramedics can be re-assigned after arrival on scene (a split crew). By way of example, Kent County uses two-unit IDs upon dispatch, Medic 7A and 7B (7B being a phantom unit created in the unit table as an accompanying unit), and status them both so in the event of a split, they can use the 7B side of the unit and leave from the scene. However, due to this two-paramedic state mandate, another ALS must also be suggested for the call if a split-crew scenario takes place to ensure appropriate staffing addresses the medical event. Explain how your solution would address this state mandated requirement. | |
| National Emergency Response Information System (NERIS) – Delaware fire agencies require a NERIS-compliant fire RMS solution for reporting purposes. Consequently, fire agencies seek a CAD that will pre-populate as many of the required data fields as necessary. NERIS captures “tactical” or “benchmark” times, such as water on the fire, extrication complete and primary search complete, to name a few. Fire agencies report these tomes to the to the communications center and would like to see specific data fields where these times are captured so they can then be imported into fire RNMS downstream. Capturing such times in the CAD event narrative is ineffective to accomplish this data transfer. Explain how your solution would address this requirement. | |
| Impaired Driving Reports – Law Enforcement agencies must complete Impaired Driving Reports to comply with state reporting requirements when encountering such incidents. Just as the LEISS system is the primary tool to input incident reports, LEISS also collects the data for Impaired Driving Reports. The RMS must be able to receive, store and analyze this data when received by the state’s LEISS system. Describe how your system will accommodate this requirement. |
File details come from the government source that posted it. Updated .