Specifications include, but are not limited to: 4.1.2.1.1 Incident Reports 1. The EMIS shall enable authorized users to create, update, and view incidents from browsers, and mobile applications. 2. The EMIS shall geolocate the incident based on the incident location data and update the Common Operating Picture (COP). 3. The EMIS shall receive, record, and log incident situation reports submitted by authorized users. These reports may contain but not limited to the following personal identifiable information (PII): 4.1.2.1.1.3.1 First Name 4.1.2.1.1.3.2 Last Name 4.1.2.1.1.3.3 Phone Number 4.1.2.1.1.3.4 Address The EMIS solution will not store medical records or other data related to a person’s health conditions. 4. The EMIS shall provide a component to create, collect, and notify data related to different type of incidents that are reported through the Watch Center. These are the reports include but not limited to: Arson Investigations, Tip Rewards, Mine Incidents, Workplace Safety Tips, Safe Schools, Industrial Incidents, State Interoperable Radio Network (SIRN) operators’ reports, and Infrastructure Protection Incident Notification (IPIN). The system shall allow the user to attach videos, photos, documents, and call recordings. 5. The EMIS shall enable the system users to change the status report and the system sends the report automatically as an email notification. Sample reports to use as a reference will be provided to the awarded vendor during the implementation phase. 4.1.2.1.2 Incident notification. The EMIS shall support automatic notification and support organizational as well as external email addresses.; 1. The EMIS must enable authorized users to assign or remove members of the contact lists to associated message groups to facilitate rapid dissemination of messages to specific sets of recipients.; 4.1.2.1.3 Contact lists and Directory. The EMIS shall enable users to create contact lists for emergency management staff and external contacts.; 1. The EMIS shall use these contact lists to send reports, email, and notifications.; 2. The EMIS shall eliminate the duplication of effort by enabling users to update contact data one time and update the instances where that contact is used.; 4.1.2.1.4 User-based permissions. This system shall be capable of assigning user-based permissions to data. These permissions will be based on security levels determined by system administrator(s). The system will be capable of determining access to data based on user permission level.; 1. Functional structure. The EMIS shall enable approved users to designate groups of users, by name or by functional position.; 2. Incident management. The EMIS shall enable users to manage daily activities and to monitor and track all aspects of an incident or event.; 3. Duty and Call Logs. The EMIS shall enable users to access Duty Logs and Call logs.; 4. User management. The EMIS shall enable the system administrator(s) to define roles, assign privileges to users, create, maintain and/or delete users.; 4.1.2.1.5 Interoperability. Vendor shall provide a solution that could interface with common EMIS web-based solutions.; 1. The EMIS must be fully interoperable with Emergency Management Assistance Compact (EMAC) Operations System (EOS) for all functions.; 2. The EMIS can be integrated and interoperable with the resources management software implemented at the local level, the WVEMD resources management, and EMAC platform, and the Geospatial platform implemented at WVEMD. Currently, the WVEMD uses AssetCloud for managing assets and Inventory Cloud for WVEMD's warehouse items. The Geospatial platform implemented at WVEMD is based on ArcGIS platform.; 3. The EMIS must have the capability to interoperate with the State's financial administration system to report material transactions including order and receipt of ordered material. Currently, the WVEMD uses wvOASIS Enterprise Resource Planning (ERP).; 4. The EMIS must interoperate with the West Virginia National Guard (WVNG) EMIS and FEMA EMIS. Currently, WVNG and FEMA use WEB-EOC. The interoperability between systems must be automatic, and it is without user intervention by downloading and importing datasets.