Incident Command System

Required in the U.S. for disaster response. This is a bit of brainstorming on what is needed to fit into ICS for use by Citizen Corps programs (CERT, Neighborhood Watch, etc.) Initial version not quite done... still thinking about best way to organize people, roles, incidents, schedules... NDA

Because one of the principles of ICS is that it can be used for all sorts of "incidents," including training, exercises, etc., this model treats everything it possibly can as an incident, using incident types to distinguish. Part of the intent is to encourage teams to use ICS regularly.

Components

• Location: address, coordinate, postal info
• Person: individual
• Role: hierarchy of structure and command
• Organization: companies, teams, agencies, etc., with inter-relationships
• Membership: relationship of people to organizations
• Incident: deployment, training, exercise, debriefing, etc.
• Credential: training, skill, certification, vaccinations, etc.
• Prerequisite: what credentials needed before a person can participate in an incident
• Event: what happened at a particular time and place; logging
• Equipment: personal and organizational gear
• Resource: supplier of equipment, skills, etc.
• Project: workflow for planning and management
• Email: contact info
• Phone: contact info
• Web page: associated with people, organizations, resources

Functions

• Add, modify, remove each kind of component
• Generate lists of each kind of component
• Print identification cards/badges
• Select individuals by various criteria, then send notifications
• Interface to calendar, recurring automatic emails for meeting notifications
• Issue training certificate
• Alerting - instant messaging, SMS, printed phone tree generation
• Export KML data for mapping, with symbols
• Dashboards for incidents, teams, resources, projects
• Training reports - who needs which courses, what expires soon?
• ICS/NIMS forms
• Access control
• Automatic data dump to forms suitable for laptops, mobile - cache critical data for when network is down.
• Data import
• MORE TBD

Table structures

PERSON

person_id	PK	|
person_title	CHAR
first_name	CHAR
nickname	CHAR
last_name	CHAR
photo	BLOB
physical_limitations	TEXT
comments	TEXT
gender	ENUM(m, f)
birthdate	DATE
status	ENUM(interested, pending, active, related) # related is for people who are in the database but not part of a team
emergency_contact	FK person_id

ROLE

role_id	PK
ICS_level	ENUM(Command, Section, Division, Individual)
ICS_role	ENUM(PIO, Safety, Operations, Planning, Logistics, Intelligence, Finance/Admin)

LIAISON

# Could belong in incident_event, but it is a persistent relationship sometimes.

liaison_id	PK, FK
person_id	PK, FK
organization_id1	PK, FK
organization_id2	PK, FK
when_assigned	DATETIME
when_unassigned	DATETIME

ACCESS_CONTROL TBD

EQUIPMENT

equipment_id	PK
equipment_name	CHAR
equipment_type	ENUM (HT, mobile radio, antenna, first aid kit, boots, backpack...)
equipment_category	ENUM (communications, PPE, medical, SAR...)

PERSON_EQUIPMENT

# Equipment that volunteers have or should have.

person_id	PK, FK
equipment_id	PK, FK
needs	INT
has	INT

LOCATION

location_id	PK
location_type	ENUM (home, work, incident, organization, company, division)
street_address	CHAR
street_address2	CHAR
city|CHAR	|
county	CHAR
state/province	CHAR
country	CHAR
postal_code	CHAR
longitude
latitude
last_updated	(DATE)

PERSON_LOCATION

person_id	PK, FK
location_id	PK, FK
location_type	ENUM(home, work, organization)
comments	TEXT

PERSON_ORGANIZATION

# Tracks people's membership in an organization

person_id	PK, FK
organization_id	PK, FK
active	BOOLEAN
leader	BOOLEAN
role_id	FK
membership_started	DATE
membership_expires	DATE

EMAIL

email_id	PK
email_address	CHAR
email_type	ENUM(normal, pager)
last_updated	DATE

PERSON_EMAIL

person_id	PK, FK
email_id	PK, FK

PHONE # Can belong to person, organization, resource

phone_id	PK
phone_type	ENUM(home, work, mobile, other)
country_code	INT
area_code	INT
phone_number	INT
extension	INT
service_provider	CHAR
confidential	BOOLEAN
primary	BOOLEAN
24_7	BOOLEAN
last_updated	DATE
organization_id	FK
resource_id	FK
time_of_day	ENUM(any, day, night)
comments	TEXT

PERSON_PHONE

person_id	PK, FK
phone_id	PK, FK

CREDENTIAL

# Any kind of certificate, training, other prerequisite associated with a person

credential_id	PK
credential_name	CHAR
credential_description	TEXT
credential_type	ENUM(communications, ICS, EMS, SAR, CERT, vaccination...)

PERSON_CREDENTIAL

person_id	PK, FK
credential_id	PK, FK
issuing_organization_id	PK, FK
completion_date	DATE
verified_by	FK person_id
verified_date	DATE
credential_expires	DATE
credential_certificate_id	CHAR

INCIDENT

incident_id	PK
incident_name	TEXT
planned	BOOLEAN
incident_description	TEXT
incident_comments	TEXT
activation_code	CHAR
incident_contact	FK person_id
incident_type_id	FK
location_id	FK
address_id	FK
incident_page	FK page_id
twitter_hashtag

INCIDENT_TYPES

incident_type_id	PK
incident_category	ENUM (preparedness, response)
incident_type	ENUM(fire, flood, earthquake, medical, evacuation, terrorism, other emergency, critical incident debrief, operational debrief, class, seminar, workshop, game, training, table-top exercise, functional exercise, full-scale exercise)
incident_geography	ENUM(neighborhood, city, county, region, state, national, global)

PAGE # web pages

page_id	PK
URL	CHAR
title	CHAR
description	TEXT
last_reviewed	DATE

PERSON_PAGE

person_id	PK, FK
page_id	PK, FK
page_type	ENUM(Personal, Twitter, Facebook, YouTube, other

PERSON_INCIDENT

# This belongs with logging...

person_id	PK, FK
incident_id	PK, FK
notified	DATETIME
committed	DATETIME
committed_by	FK person_id
arrived	DATETIME
departed	DATETIME
met_requirements	BOOLEAN
verified_by	FK person_id

INCIDENT_ROLE

# Volunteer slots to be filled

incident_id	PK, FK
role_id	PK, FK
shift_id	PK, INT
starting	DATETIME
ending	DATETIME
people_needed	INT

INCIDENT_EVENT

# Logging - most of this will probably happen on paper, then transcribed

event_id	PK
event_type	ENUM(person, resource, objective, assessment, situation report, status_report, strategy, intelligence, incident location, incident command, incident base, joint information center)
incident_id	FK
person_id	FK
person_event	ENUM (notified, en-route, checked_in, assigned, rehab, demobilized, available)
role_id	FK
address_id	FK
resource_id	FK
authority	FK person_id
incident_timestamp	DATETIME
public	BOOLEAN
incident_communications_primary	CHAR
incident_communications_secondary	CHAR
comment	TEXT

ROLE_PREREQUISITE

# qualifications, training, etc.

incident_id	PK, FK
role_id	PK, FK
prerequisite_id	FK
required	ENUM(True, recommended)

CURRICULUM

# Series of classes that typically would be taken together # Curriculum itself becomes a prerequisite

curriculum_id	PK
curriculum_name	CHAR
incident_id	FK
recommended_sequence	INT
required	ENUM(Yes, Recommended

ASSIGNMENT

assignment_id	PK
incident_id	PK, FK
assignment_description	TEXT

ASSIGNMENT_PERSON

# Move into logging...

assignment_id	PK, FK
person_id	PK, FK
assigned_when	DATETIME
removed_when	DATETIME

ORGANIZATION

# Companies, government agencies, etc. - association or group of people with like objectives

organization_id	PK
organization_name	CHAR
organization_phone	FK
organization_page	FK
organization_type	ENUM(company, foundation, government agency, NGO, responder)
organization_purpose	ENUM(medical, supplies, elder care, child care, church, shelter, school, public works, communications, transportation, firefighting, emergency management, mass care/emergency assistance/housing/human services, logistics, public health, SAR, hazardous materials, agriculture/natural resources, energy, law enforcement, long-term recovery)
vulnerable_population	ENUM (children, elderly, disabled)
donor	BOOLEAN
parent_organization	FK organization_id
organization_scope	ENUM(neighborhood, city, county, state, national, global)

ORGANIZATION_SERVICE_AREA

# Geographic description of areas that an organization serves: TBD

ORGANIZATION_PAGE

organization_id	PK, FK
page_id	PK, FK
description	TEXT

RESOURCE

resource_id	PK
resource_name	CHAR
resource_page	FK page_id
resource_type	ENUM(web site, park, storage, fire station, gas station, atm, water)
resource_scope	ENUM(neighborhood, city, county, state, national, global)
category	ENUM(training, operations, discussion, communications)

RESOURCE_LOCATION

resource_id	PK, FK
location_id	PK, FK

RESOURCE_PERSON

resource_id	PK, FK
person_id	PK, FK
primary_contact	BOOLEAN

RESOURCE_ORGANIZATION

resource_id	PK, FK
organization_id	PK, FK

DIVISION

# this needs to be generalized to include neighborhood teams?

division_id	PK
division_number
division_name	CHAR
division_command_address_id	FK
primary_frs_channel
primary_frs_pl
tactical_frs_channel
tactical_frs_pl