[ILHam] Emergency Management Information System

[Garth Kennedy]

This is part of an announcement of a software system upgrade/release that
may be of some interest to ARES or other organizations. This system was
initiated by the needs of an Emergency Management organization which is why
some parts of the extended system capabilities are present.  The scope of
the
system is much broader than needed for most radio groups, but a partial
implementation should be easy and straight forward.

On-Line documentation is at http://home.comcast.net/~Garth.Kennedy/EMIS/

Please forward this to anyone you think might be interested.

The following are a couple of brief comments as I think they apply to
ARES/EC activity.

The system contains most of the info used on the ARES form. Training and
activity participation can be tracked.  People could be "assigned" to one or
more "agencies".

Multiple "agencies" and the channels that they use may be defined as well.
This lets you do rosters and have contact info for people and agencies.
There is also the capability to link agencies through Emergency Operating
Plans (who functionally supports agency A and in what role).

 My demo system is running on a 400 MHz PC with all open source software
(Linux, MySQL, Apache, perl) so the cost can be low. The application
distribution will be made available for free download if any one wants it.

 73
Garth   W9KJ
W9KJ@arrl.net

----------------------------------------------------------------------------
---------


The T356 Inventory System computer system that was released last summer to
manage "what radio, which is where, can talk to whom" has had a significant
increase in capability. The name of the system has been changed to more
closely reflect the system capabilities. It is now called Emergency
Management Information System (EMIS).

This release represents a significant expansion of capabilities. On-line
documentation is available at http://home.comcast.net/~Garth.Kennedy/EMIS/ .
Please note that several of the report screen example documents are very
large and may take some time to load.

EMIS has several different segments that may be implemented alone or in
combinations. These segments are:
1. Agency
    a) Emergency Operating Plan (EOP) Relations between agencies may be
mapped.
    b) Agencies may be subdivided into units with people assigned to units
    c) Training (or certifications) may be defined at several levels by a
unit and people assigned to one or more levels
2. Channel
   a) logical channels may be defined, used by agencies and mapped to
channel positions in radios.
3. Equipment
    a) Equipment is defined and owned by Agencies
    b) Equipment is located in a location and may be moved
4. Location
    a) locations are defined and subdivided into areas and equipment
positions
5. People
   a) People are defined and assigned to one or more agency units.
   b) equipment may be assigned by an agency to a person
   c) People take training classes and participate in activities
   d) if the person is an amateur radio operator,  ARES information is
managed.
6. Training and Activities
    a) Training classes are defined
    b) Sessions of presented training classes are defined and rosters
maintained.
    c) Activities are defined and participation records kept.

And of course reporting on all of the above is included.  See the
documentation for more details.

The system is probably not complete and suggestions are requested.

This system runs on a web server and will support multiple agencies. Details
are included in the on-line documentation. If an organizations wishes to
implement the system, the source can be made available.

grk