Emergency Planning Software

The vendor is required to provide emergency planning software for focus is to support stakeholders with implementing and maintaining a recurring, hands-on process that facilitates regular coordination and communication among stakeholders to develop, implement, train, exercise, and maintain emergency plans.
- Involve identifying and tracking plan updates on a continual basis based on lessons learned from exercises and real-world events.
- This effort is an emergency planning software (EPS) solution that allows stakeholders to manage the emergency planning process and to develop and maintain functional plans in a simple, efficient, and concise manner.
- EPS solution:
• Security, stability, and resiliency performance expectations in a public safety environment.
• The solution shall have a simple, intuitive design that is easy to use.
• The solution should drive the development of functional emergency plans that are simple, clear, concise, and includes the ability to incorporate tools such as checklists, tear sheets, flip charts, etc.
• Scalability and flexibility to support current and future needs and to add other entities that need an emergency plan onto the solution at different timeframes.
• A solution that is accessible and useable on mobile devices.
• Efficient and flexible user registration and management.
- Provide project management services throughout the life of the project.
- These services include but are not limited to, oversight of Offeror staff delivering and maintaining the work plan, communications plan, requirements management plan, risk management plan, change management plan, final report, and lessons learned.
- The solution must be usable on mobile devices (e.g., phone, tablet, etc.) and support search and plan accessibility for iOS and Android.
- The solution should allow draft plans to be edited by multiple users, with edits tracked, similar to a SharePoint type functionality.
- Particular aerial imagery, shape files, and other GIS data formats.
(1) All standard types such as Word, Excel, PDF
(2) Aerial imagery and shape files
(3) GIS Data import formats:
(a) CSV
(b) GDB
(c) Esri REST/ ArcGIS Rest
(d) JSON
(e) GeoJSON
(f) KML
(g) SHP
- OGC Web services:
(a) GeoTIFF
(b) KML
(c) WMS
- Incident Management. Provide and manage a process to track, monitor, and resolve reported problems and issues; describe its methodology to triage problem criticality and impact including resolution procedures and escalation process for each classification of problems and issues.
• NOC/SOC operations: Describe its operations model for systems monitoring to ensure it is operational and secure.
• Logging: Support real-time and historical logging of system events, as well as event resolution concerning the solution on a 24 x 7 x 365 basis; this is for logging errors, alerts, alarms, and statistical information related to the performance and health of the solution.
• Multiple trouble reporting methods: A single, toll-free phone number, email address and electronic reporting dashboard, shall be provided for reporting system troubles on a 24 x 7 basis.
• Escalation procedures & status updates: Provide single point of contact on a 24 x 7 basis for users to escalate and receive status updates on incidents affecting the system.
• Escalation procedures and contacts must be defined and kept current.
• Trouble tickets: Log all support requests and provide a monthly report detailing tickets opened, pending, resolved, and closed.