Technical_Aspects_and_System_Capabilities.pdf

ATTACHMENT A

TECHNICAL ASPECTS AND SYSTEM CAPABILITIES

The County will evaluate the Proposer's ability to provide a secure, cloud-based incident management system that meets the County's functional and operational requirements. Evaluation will consider system capabilities, technical architecture, security, interoperability, implementation, hosting, training, and support services. (30 Points)

General System Requirements: Yes No

a) A Cloud Hosted, Web-based and mobile device-compatible system accessible through major browsers and mobile devices for both PC, Android and Mac / IOS

b) Support and differentiate multiple simultaneous incidents, exercises, and planned events.

c) Support multiple Emergency Operations Centers (EOCs), jurisdictions, departments, and partner agencies within a unified platform.

d) Comply with National Incident Management System (NIMS) and Incident

Command System (ICS) form standards.

e) Ability to host unlimited user accounts and configurable user roles.

Incident Management: Yes No

a) Manage incidents, documentation, personnel, objectives, activities, and operational records.

b) Support real-time collaboration, notifications, task assignments, and activity tracking.

c) Maintain complete audit history and reporting for all incident activities.

d) Generate analytical reports to support after-action reviews and continuous improvement.

Communications: Yes No

a) Integrated messaging supporting email, SMS, in-system messaging, Microsoft Teams/webhooks, and interoperable messaging with external systems.

b) Message templates, automated notifications, and distribution lists.

c) Support emergency communication standards including CAP, EDXL, and

IPAWS interfaces.

Resource Management: Yes No

a) Track personnel, equipment, supplies, contracts, vendors, inventory, costs, and resource requests.

b) Support resource request workflows, approvals, status tracking, templates, and mobile access.

c) Allow local jurisdictions and departments to manage resources while escalating requests to the Operational Area EOC when needed.

Task Management: Yes No

a) Assign, monitor, prioritize, and document incident tasks.

b) Support attachments, templates, subtasks, workflows, reporting, dashboards, and mobile field access.

c) Maintain complete audit logs for all task activities.

Situational Awareness: Yes No

a) Configurable dashboards and status boards displaying real-time operational information.

b) Integration with GIS, tasks, resources, weather, and other operational data.

c) Support Operational Area and jurisdiction-specific dashboards.

Incident Action Planning: Yes No

a) Create, edit, and manage NIMS-compliant Incident Action Plans (IAPs) and

ICS Forms.

b) Support collaborative workflows and export to PDF and Microsoft Word.

Damage Assessment: Yes No

a) Collect, manage, analyze, and report public and private damage assessments.

b) Support public reporting portals, custom surveys, FEMA Public Assistance

(PA) and Individual Assistance (IA) documentation, and ArcGIS integration.

GIS Integration: Yes No

a) Native integration with ESRI ArcGIS Online and Enterprise.

b) Display and manage incident data, road closures, shelters, damage assessments, resources, and other GIS layers

c) Import and export common GIS and emergency management data formats.

Administration & Security: Yes No

a) Secure, role-based administration with comprehensive auditing and reporting.

b) Encrypted communications and compliance with industry cybersecurity best practices.

c) Vendor shall demonstrate independent security review or equivalent cybersecurity certification.

d) Role-based security with integration to Active Directory (AD), LDAP, and

Single Sign-On (SSO).

Hosting & Performance: Yes No

a) Describe hosting architecture, uptime guarantees, disaster recovery, redundancy, and scalability during major incidents.

b) Provide 24/7 technical support and monitoring.

c) Provide implementation methodology, project management approach, training, data migration, testing, and estimated deployment timeline.

d) Describe available APIs, third-party integrations, and future product enhancement process.

Training & Support: Yes No

a) Provide user and administrator training, documentation, software updates, technical support, and Service Level Agreements (SLAs).

System Architecture: Yes No

a) Describe supported operating systems, browsers, databases, backup capabilities, ADA compliance, licensing model, and any user or data limitations.