The IMU (Incident Management Utilities) is a tool that can be used to simplify the execution of a CAP incident. This tool replaces the functionality of the MMU and provides more robust operations and is designed to support the CAP implementation of the ICS system.

The MMU is no longer supported because it is based on obsolete VB6 programming technology that is no longer supported by Microsoft. As a result, many issues in the MMU cannot be resolved. Users that do not use features in the MMU that have issues, can continue to use the MMU in their ES programs. However, all MMU users should consider moving to the IMU. The IMU is based on state-of-the-art .NET technology from Microsoft.

A significant feature of the IMU is its ability to operate in various network environments. It can function as a stand-alone system using a single PC in the LOCAL mode. When an ICP is used in an incident, the PCs can be connected using a LAN and the IMU applications on each machine can communicate using the LAN mode. A third mode is the DISTRIBUTED mode. This mode is designed for typical incidents where the incident is being run out of the staff homes (such as ELT incidents). The DISTRIBUTED mode uses the WMU server to provide a common database and PC at each staff member’s home are connected via the internet to the WMU server and act as though they were all at an ICP.

The IMU has been tested on systems using Windows XP, 2000, and 98SE. It should be able to run on any platform that has a corresponding .NET framework from Microsoft.

Compatibility

The IMU uses a different database schema than is used in the MMU. As a result, these databases are not compatible and missions run on the IMU will not be available to MMU users and conversely, MMU incidents are not available to IMU users.

Both the IMU and MMU use Access Databases that are populated using data from MIMS and the WMU. Creation of the database and subsequent upload of mission data is several orders of magnitude faster using the IMU that for those using the MMU.

Features

Initial Screen

When the IMU is started, the main form will be displayed on the PC. This is the form that is used to select IMU utilities. When the form is first displayed, all functions except for the Configuration and Login are disabled. It should be noted that the form has tabs that are used to select the functional areas associated with CAP incident management. These areas are General, Command, Planning, Operations, Logistics, and Finance/Administration. Each tab has an associated set of buttons that activate sub forms for section functionality.

The General tab provides a summary of activity for the selected incident number. When the form is first opened, no incident is selected and these summary boxes are empty. The form also displays the local and GMT times in the upper right hand corner. The selected incident information is displayed in the upper left hand corner. When no incident is selected, these fields are red. When an incident has been selected, they will have a green background.

Configure Network Button

Prior to using the IMU for the first time, it is necessary to establish a network configuration and database location. This is accomplished using the Configure Network button. Once any other buttons or options are activated, the Configure Network button will be invisible until the application is closed and restarted. When you click on the Configure Network button, a form will be displayed that will allow you to select the configuration and define the database. The selected network mode will be saved and will default when the IMU is restarted.

Local Network Mode

The Local network mode is used when the database resides on the local workstation. It must reside in the same folder as the application. The Local network mode is selected when the user clicks on the Local radio button at the upper left corner of the Configure Network form. The user must select a wing name for the local mode. This name is used to establish the local database name and a database with this name must be downloaded from the WMU and be in the local folder. The database name will always be “<wing>NETwing.mdb” where <wing> is the selected wing.

The Local network mode should be used when a single workstation is being used to support a CAP incident – i.e., ELT searches run from the IC’s home.

ICP LAN Mode

The ICP LAN mode is used to support a multiple workstation environment such as an incident command post or a training classroom environment. In this mode, a single database is shared between all the workstations. The naming convention remains the same as is used with the Local mode where the prefix is established by the wing selected in the Wing Name selector.

However, the ICP LAN mode has a second parameter to establish the path used from the local workstation to the workstation designated as the master database. The file selection dialog box is used to select the database and is activated by double clicking the Database Path/Name box. The path can be established using a network mapped drive (i.e., “I:\myPath\ORNETwing.mdb” where I is a mapped drive –it must reconnect at startup) or by finding the database master using the network neighborhood or by entering the computer name and path (i.e., “\\pander\myPath\ORNETwing.mdb”).

Distributed Mode

The Distributed Mode provides a direct link to the WMU server database using the Internet. No local database is required in this operating mode; however, the system(s) using this mode must have an active internet connection. Because, database information is sent and received over the internet, this mode will be somewhat slower than the Local or ICP LAN modes.

Care should be taken not to overuse this mode since operations will share the server processor with WMU users. Training and incidents involving and ICP should not use this mode. This mode is generally used for ELT type incidents where the staff consists of an IC, CUL, and one or two other positions, each run from the member’s home.

When the Distributed mode is selected, the user must again enter the wing identifier and a base name for the local workstation. The base name should be limited to no more than 10 characters.

Login

Before the workstation can be used, the user must identify themselves and be validated as having access to the IMU. To use the IMU, the user must have an ES base staff qualification of MSA or higher (members with only General ES or only crew qualifications cannot log into the IMU). The login process is initiated by clicking on the Login button.

The Login form verifies the identity of the user by comparing the member CAPID and associated DOB with what is in the National MIMS database. The user enters the CAPID, then moves to the Month field (a Tab, Enter, or mouse click) and enters the month of his/her birthday (1 – 12). Moving to the Day field, the date of the month (1 – 31) is entered and finally the year is entered into the Year field. Tabbing, using the Enter key, or using the Mouse will submit the data to the database for verification. If there is a match and the user has the minimum ES achievement qualification, the main form will return with the Login button disabled, and the Logout and Incident Open functions enabled. The user name will be displayed at the top of the main form.

Open Incident

After a user has successfully logged into the IMU, an incident must be opened before activity can begin. Incidents are opened by clicking on the File menu option on the main form, then clicking on the Open Incident option. Only one incident can be open at a time.

All fields must be completed before the incident can be opened. If the incident has previously been opened for the incident date on the workstation, all the data will be defaulted and it is only necessary to click on the OK button to open the incident.

A new incident number can be typed directly into the Incident box or the user may select from existing incidents in the database by using the pull-down selector. Incident dates can be selected using the pull-down selector or by clicking on the New button to create a new date (today’s date will always be shown in the pull-down selector).

Entries are made by either entering data into the box (Incident, IC, ICP), using the pull-down selectors (Incident, Agency, Type, Date, Mission Symbol), or by clicking in the box with the mouse (New button, Open Time). Clicking in the Incident Open Time box will activate a form that allows entry of the open time.

Clicking on the Enter button will create the necessary entries into the database and open the Incident. When the Incident has been opened, the Incident information will be shown in the main form Incident summary boxes and they will have a green background. The function tab strip will also be enabled.

Functional Tabs

After logging in and opening an Incident, the user should select a tab corresponding to the staff section to which he/she is assigned. Each tab has a set of buttons corresponding to the tools available in the IMU for that section. A summary of the tools in each tab is shown below. Note that may tools exist on more than one tab.

General Tab

Incident Checkin button – Allows a member to check into the incident. It is also used to check-in aircraft or vehicles. Members are assigned functional positions using the Incident Checkin. Finally, it provides a tool for checking members and assets out of the incident.

Incident Statistics – A summary of incident statistics is always displayed on the General Tab. This information is updated each 5 minutes. Information provided includes:

Data for the current date

· Active Personnel – The number of personnel currently participating in the Incident. Members who have checked out of the incident will not be counted.

· Total Personnel – The total number of personnel who have participated in the incident for the selected date.

· Aircraft – The number of aircraft that have been checked into the incident.

· Vehicles – The number of vehicles that have been checked into the incident.

· Hours Flown – The number of flight hours flown on completed sorties

· Sorties – The number of flight sorties that have been or are being conducted.

Data for the incident

· Man Hours – The total number of man hours that have been expended by CAP personnel during the incident.

· Total Personnel – The total number of personnel who have participated in the incident.

· Aircraft – The total number of aircraft that have participated in the incident

· Vehicles – The total number of vehicles that have participated in the incident.

· Hours Flown – The number of flight hours flown on completed sorties

· Sorties – The number of flight sorties that have been or are being conducted.

Command Tab

The Command Tab has functions that are commonly used by member in the Command positions in the ICS organization. It is primarily oriented to the IC/AL needs. Functions available include:

Incident Checkin button – Allows a member to check into the incident. It is also used to check-in aircraft or vehicles. Members are assigned functional positions using the Incident Checkin. Finally, it provides a tool for checking members and assets out of the incident
ICS 202 – This function allows the input of the Incident Action Plan. Information from the plan will rollup into CAPF 104 and CAPF 109 sorties when they are created.
Procedures – This function allows the input of standard procedures to be used by teams participating in sorties. Information entered provides procedures for 1) Communication procedures; and 2) Actions to be taken if the objective is located. Separate entries are made for air and ground sorties.
Air Operations – This function is used to support air operations. It is used to assign members to aircrews; to define tasking requests to create sorties to perform needed tasks; to create and manage air sorties. Tools are also provided that allow verification of questionable or missing pilot documentation.
Ground operations – this function is used to support ground operations. It is used to assign members to teams; to define tasking requests that create sorties; to perform the tasks to create and manage ground stories; tools are also provided that allow verification of questionable or missing CAP driver’s licenses.

· Status Board – The status board provides a visual representation showing the status of sorties created during the incident date. The information shown on the display is updated each minute. Color coding is used to quickly bring attention to any sorties that may require attention. In the default mode, both air and ground sorties are displayed. Options are provided that allow the user to filter the information so that only error or ground sorties are displayed. The user may also choose to include sorties that are not active.

· ICS 122 – The ICS 122 automates the capture of all the information that is required for the daily closing report. It simplifies the incident commander’s workload when preparing and delivering the report to the AFRCC each night. When this report is run, and option exists that will check out all members participating in the incident.

· Grid Assist – The grid assist utility is used to provide graphical tools that allow the staff to view charts and chart information related to the incident.

Typical sequence

This section will provide a typical sequence of events that may be used to create and manage the typical incident. It will help the user to learn and understand how to use the incident management utilities.

Login

When a request for a new incident is received, the incident commander must first logon to the incident management utilities. This is done by clicking on the login button, then entering the user’s CAPID and date of birth information into the screen. Pressing the submit button will validate the user and allow for their operations in the IMU.

Open Incident

The IC/AL must next open the new incident. This is done by clicking on the File menu item and clicking on the Open Incident selection. The incident number should be entered into the incident box. Pressing the tab key will move the focus to the requesting agency pull-down selector. Using the mouse, select the appropriate entry and then either click in the incident date or press the tab key. Today’s date will always default in the incident a selector box. If needed other dates may be either selected or generated by pressing the New button. Pressing the tab key again will move the focus to the Incident Type selector. Use the mouse to select the appropriate incident time. To enter the incident open time, click in the Incident Open time blocks. This will bring up the Incident Open Time Selector. The default time will be shown in GMT format. Make adjustments to the time then click on the OK button to enter this into your mission information.

Pressing the tab key will move the focus to the Incident Commander name box. The incident commander or Agency Liaison name is entered using his or her last name.

Use the mouse to select the appropriate Mission Symbol for this incident then press the tab key to move to the Incident Command Post (ICP) box.

Enter the Incident Command Post name, preferably using the FAA airport identifier for the airport closest to the ICP. In any case the maximum number of characters for the ICP could not exceed ten characters.

When running the utilities using the DISTRIBUTED mode an additional input box will be shown on the screen. This box is used to identify the location of the distributed workstation. Enter the identification of your specific site into this box.

Click on the OK button to create the mission in the database.

Checkin

Incident Action Plan

Before we can sign anyone in, we should open the ICS 202 and enter the information pertinent to the incident. The ICS 202 has four text boxes that are used to input the action plan.

In the first box is the mission objective. This box should have the information as to the ultimate requirements to complete the mission. For example, if the incident is an ELT, indicate that the mission objective is to locate the ELT.

The second box is for control objectives. This box will contain information as to how we are going to actually deploy our assets to meet the mission objectives. For example, if this is an ELT mission, we may indicate that we want to coordinate ground and air crews. to locate and silence ELT.

The third box is for input of the general weather forecast during the period covered by the ICS 202.

The fourth box is used to input the general safety message for all personnel. This box will have a default safety message which is based on the CAP safety oath.

When all information has been entered, click on the Enter into ICS 202 button to save the information. You will note that the form has beginning and ending times associated with the period for which this information is valid. To simplify entry of new information, a button exists in the lower right corner of the form that will create a new entry using the information in the previous entry. After information has been entered, click on the close symbol in the upper right corner of the form to close this form.

Procedures

Each incident commander generally has a set of standard operating procedures that he or she prefers to use during the mission. This information is used during the briefing for all aircrews and ground teams. Before creating air or ground sorties, the incident commander should click on the procedures button and enter his or her standard operating procedures.

When the procedures button is clicked, the procedures form will be displayed. This form has four sections for inputting information.

One section is for aircrew communication procedures. For example, if the incident commander wants the aircrew to call the ICP up on takeoff, entering the assigned area, leaving the assigned area, and returning to base, that information will be entered in the air crew communications procedures box. A similar box exists for defining the preferred to communications that should be conducted by ground teams during sorties. The third box is used to input standard procedures for aircrews should they locate the target. Finally, the fourth box is used to input the procedures to be used by a ground team should they find the target.

When all information has been entered onto the form, it is saved in the database by clicking on the enter into database button. As in the ICS 202, the procedures have beginning and ending times that are associated with these procedures. If a new set of procedures is required, clicking on the menu file option in the upper left corner of the form, will allow creation of a new set of procedures based upon the old procedures as a template.

Sortie Tasking

Before either air or ground sorties c an be assigned, it is necessary to define the tasks that are to be accomplished by the air and ground sorties. These tasking orders are entered through either the air or ground operations forms.

When either the air for ground operations buttons are clicked, the associated form will have a tab identified as Tasking. Clicking on this tab will display the form that allows input and maintenance of tasking orders.

In many cases, the requested task is in support of a particular agency. The tasking form provides input boxes that will allow entry of the agency and agency contact. If not applicable, these boxes may be left blank.

To ensure a new task, first click on either the air for ground sortie selector as appropriate, then click on the short name selector and select new. The short name box will default to a generic sortie description. You should enter a unique short description that describes the task.

There are four Tabs associated in the detail tasking requirements. A full description of what the crew is supposed to do should be entered under the description tab. The deliverables tab is used to the find exactly what the team is expected to deliver at the completion of the sortie. The special instructions tab is used to define special procedures for restrictions related to the sortie.

The results tab is used to input or edit the results of the sortie when it is completed.

When entering Information into the tasking tab, it should be noted that information will be saved in the database each time the focus leaves a specific box and a change has been made in that box.

Air Crew Creation

The operations air crew tab provides the ability to take members from the various pools and assign them to air crews or ground teams. Clicking on the air crew tab will expose a portion of the form that is used to select the members that will constitute an air crew. The air crew creation tab will support up to eight members in an air crew. Members are selected by using pull-down selector boxes which will contain the names of those members were qualified to fly in the indicated position.

Before selecting crew names a validation mode should be selected. There are three validation modes. The first validation mode is called the air crew pool. In this mode, only members who have checked into the air crew pool will be displayed. The only members who can be input into an air crew pool are those members that have full qualifications for that position.

The pool mode will display those members who are in the air crew pool and also those members that have been placed in the general ES pool. This pool selection does not guarantee that the members have met all the required qualifications. Anyone being assigned from the general pool should have their qualifications checked prior to dispatch on the team.

The check-in mode will list all the names of all individuals who have checked into the mission. In this mode, there are no checks to validate either qualifications or assignment to another position.

When a pilot is selected, information will be provided next to the pull-down box showing the pilot rating, medical certificate, and duty day. In addition, there are check boxes that indicate if the pilot is qualified for over water and for mountainous areas. In addition, all the aircraft that the pilot is qualified to fly, based on CAPF 5 information from the database, will be displayed in the box labeled qualified to the PIC.

If a member display indicates a mission pilot or transport pilot is followed by question marks, this indicates that the pilot credentials could not be verified by the data provided in the database and must be checked prior to release for flight. This is done using the pilot qualification tab.

Each crew member can be chosen by selecting the appropriate name from the pull-down list. As each name is selected, the names will be removed from the other pull-down lists.

When all members of the crew have been selected, clicking on the build crew button will create a crew with a crew name corresponding to the pilot’s last name and first initial.

Pilot Qualification

Updates made to our home page and are only valid for the incident. Permanent changes must be made in either the WMU or MIMS. Only the IC for AL they may make changes using this form.

A pull-down selector will contain the names of all members who have checked into the incident and have either mission pilot or transport pilot ratings. Clicking on a selected name will cause the information in the database for that pilot to be displayed. Only information pertinent to allowing the pilot to act as PIC are displayed.

The information that is displayed consists of the pilot rating (Private or Commercial), the valid medical class (Class 3 or Class 2), qualification as Mountain Qualified, and qualification for over-water flight. All aircraft that are shown in the database as having valid and current CAPF 5’s are listed.

The IC/AL can use this form to validate information from the pilot’s credentials, logbooks, and paperwork and upgrade the pilot information as appropriate to allow him/her to participate as PIC.

Air Sortie Generation

Once taskings have been defined and crews created, it is possible to assign a sortie to a crew and tasking. This is done using the General tab.

The Sortie list box contains a list of all previously created sorties. Clicking on an existing sortie will display the information for that sortie. To create a new sortie, click on the New entry in the selector box.

When a sortie has been selected or created, the tail number box will have the tail numbers of all aircraft checked into the incident that are not already assigned to a sortie. The aircraft can be assigned to the sortie by clicking on the tail number. Information as to the aircraft type and CAPFLIGHT information will be displayed using the information from the aircraft checkin. The type cannot be modified; however, the CAPFLIGHT number may be changed if necessary.

After an aircraft has been selected, the sortie type should be selected. This selection will be used to insure that the PIC has the proper ratings to fly the sortie.

The Pilot pull-down selector will contain the names of the crew teams in which the pilot is qualified to act as PIC given the aircraft type and sortie type. Select the desired pilot name to link the crew with the sortie.

The Task Summary selector will show those tasks that are available for the sortie to perform. A task can be linked to the sortie by selecting the desired task.

Information should be entered showing the Departure Airport (use the FAA airport identifier), the Destination Airport, the ETE (wheels off to wheels down), and the fuel on board (ETE and fuel on board can be entered using either decimal or hours:minutes format). An ETD is required before the sortie can be released.

Flight Release

The IMU supports an electronic flight release for a sortie. This flight release can be generated using the Flight Release tab. To electronically release a sortie, the user must be shown in the WMU database as a flight release officer for the wing associated with the incident.

After the flight release officer verifies the required information by discussing the sortie with the PIC, the sortie can be released by clicking on the Release the Sortie button.

Ground Team Creation

The operations Ground Team tab provides the ability to take members from the various pools and assign them to ground teams. Clicking on the Gnd Team tab will expose a portion of the form that is used to select the members that will constitute a ground team or UDF team. The Gnd Team creation tab will support up to ten members in a team. Members are selected by using pull-down selector boxes which will contain the names of those members were qualified to participate in the indicated position.

Before selecting a validation mode, the team type selector should be set to the type of team being assembled. Options are Ground Team, UDF Team, or Transport Team.

Before selecting crew names a validation mode should be selected. There are three validation modes. The first validation mode is called the Gnd Pool. In this mode, only members who have checked into the Gnd Pool will be displayed. The only members who can be input into an Gnd Pool are those members that have full qualifications for that position.

The pool mode will display those members who are in the Gnd Pool and also those members that have been placed in the general ES pool. This pool selection does not guarantee that the members have met all the required qualifications. Anyone being assigned from the general pool should have their qualifications checked prior to dispatch on the team.

The check-in mode will list all the names of all individuals who have checked into the mission. In this mode, there are no checks to validate either qualifications or assignment to another position.

When a Leader is selected, information will be provided next to the pull-down box showing the duty day.

If a member display indicates a Leader is followed by question marks, this indicates that the CAPF 75 credentials could not be verified by the data provided in the database and must be checked prior to release. This is done using the team qualification tab.

Each crew member can be chosen by selecting the appropriate name from the pull-down list. As each name is selected, the names will be removed from the other pull-down lists.

When all members of the crew have been selected, clicking on the build crew button will create a crew with a crew name corresponding to the leader’s last name and first initial.

Team Qualifications

Because many of the required team qualifications do no exist in MIMS and thus cannot be downloaded into the IMU database, a form is provided to allow users to validate crew qualifications and enable them for the remainder of the incident. This form is also used to show specialized personal equipment that a member may have available for the incident.

A member may be selected by clicking on the member name in the Member Name pull-down selector. Information available in the IMU database for that member which is related to ground operations will be displayed. This information includes the member’s radio call sign, the existence of a valid state driver’s license, the existence of a valid CAPF 75 driver’s license, expiration date of the license, vehicles that the member is qualified to drive, and personal equipment.

Updates can be made and entered into the database by clicking on the Update button.

Ground Sortie Generation

Once taskings have been defined and teams created, it is possible to assign a sortie to a team and tasking. This is done using the General tab.

When a sortie has been selected or created, the license box will have the license numbers of all vehicles checked into the incident that are not already assigned to a sortie and have been defined as being available at check-in time. The vehicle can be assigned to the sortie by clicking on the license number. Information as to the vehicle type and call sign information will be displayed using the information from the vehicle check-in. The type cannot be modified; however, the call sign may be changed if necessary.

After a vehicle has been selected, the sortie type should be selected. This selection will be used to insure that the driver has the proper credentials to lead the sortie.

The Leader pull-down selector will contain the names of the crew teams in which the leader is qualified to act as driver given the vehicle type and sortie type. Select the desired leader name to link the team with the sortie.

The Task Summary selector will show those tasks that are available for the sortie to perform. A task can be linked to the sortie by selecting the desired task. The full description of the task, taken from the Tasking order, will be displayed in the Primary Assignment area.

Vehicle information not already available in the database can be entered through the Vehicle Information tab. This information includes the vehicle make, color, radio call, available frequencies, corporate vehicle ID, roof markings, and odometer mileage readings.

An ETD is required before the sortie can be released.

Sortie Status Updates

Each sortie must be monitored for the safety of the crew. The IMU performs this function using either the Contacts tab of the Air or Ground Operations forms, or through the CAPF 110 communications inputs. The CAPF 110 inputs will be described later in this document.

The operations form Contact inputs can be made using either the sortie number or the sortie call sign (or CAPFLIGHT number). An identification Criteria selector determines which mode to use and will populate the pull-down selector with those sorties that are either waiting to depart or are active. The user should click on the appropriate sortie so that the contact information can be applied to the correct sortie. When a sortie has been selected, all previous contacts with that sortie will be displayed in the Contact History box.

The types of contacts are selected by clicking on the appropriate identifier. Options are Radio Check, ATD, In assigned area, Returning to base, Target located, ELT heard, Enroute to assignment, New ETA, or other.

The contact time will default in the Event Time box (using local time) to the time at which the Contacts tab was clicked. It may be changed if necessary.

The contact event source is used to indicate where the contact information originated.

The contact is entered into the database by clicking on the Enter Contact button.

Status Board

The status board provides a visual representation showing the status of sorties created during the incident date. The information shown on the display is updated each minute. Color coding is used to quickly bring attention to any sorties that may require attention. In the default mode, both air and ground sorties are displayed. Options are provided that allow the user to filter the information so that only error or ground sorties are displayed. The user may also choose to include sorties that are not active.

In addition to the general status board, both the Air and Ground Operations forms display information for active sorties in their respective area. This information is updated each minute. Concerns are automatically detected and color coded to bring them to the user’s attention.

ICS 205 Communications Assignments

The incident radio communications plan can be entered into the incident database using the ICS 205 form. This form is available on the Logistics tab. Information entered into the form is used to populate air and ground sorties information when new sorties are created.

This information is normally entered by the Communications Unit Leader; however, in a small ELT type incident, the IC/AL may have to enter the information. If information is not entered into this form, a default set of frequency assignments will be used by the system.

The form allows the entry of the ICP tactical call sign, channel/frequency assignments for each type of communication that is likely to be used in support of the incident, ICP phone numbers, and PAO phone numbers for external calls related to the incident.

When all information has been entered onto the form, it is saved in the database by clicking on the enter into database button. As in the ICS 202, the assignments have beginning and ending times that are associated with this information. If a new set of assignments is required, clicking on the menu file option in the upper left corner of the form, will allow creation of a new set of frequency assignments based upon the old information as a template.

Communications Log

The communications log is a key element to simplifying and efficiently executing an incident using the IMU. This log is used by the mission radio operators to record communications with assets, sorties, and other agencies. Whenever communications are recorded that are related to an active air or ground sortie, a contact event is automatically recorded for that sortie and the sortie status is updated to reflect the event.

The form will always default to the channel “A” selection. If the communications are taking place on another channel, it can be selected by pressing a single key to indicate the channel. The next field is the aircraft check box. It can be entered from the frequency selector by pressing the Enter key, pressing the Tab key, or clicking in the field. Clicking the box or pressing the Space bar will toggle the aircraft entry.

The Call Sign field is entered form the aircraft check box by either pressing the Enter key, pressing the Tab key, or clicking in the Call Sign box. The call sign of the station with which communications are taking place is entered into the call sign. Call signs can be entered as only numeric values or by a prefix and numeric value.

The next field is the Sortie field. It is entered from the call sign field by pressing the Enter key, pressing the Tab key, or by clicking in the Sortie input box. If entering from the Call Sign field, the system will pre-fill the sortie with the active sortie that has the indicated call sign. This value may be adjusted if required.

The next field is the Type field. It is used to indicate the type of communications taking place. This field is entered from the Sortie field by pressing the Enter key, pressing the Tab key or clicking in the Type selector box. Communication types fall into three categories; Normal, Status, or Message. The message type is selected by pressing the key corresponding to the first letter of the message type or by using the mouse to click on the appropriate selection. Depending of the selection, the remainder of the form will have inputs that correspond to the type.

Normal communications are those that are not related to a sortie and are not formal message traffic. In this mode, a brief summary of the message is entered into the Remarks box.

Status communications are those that are conducted with a sortie that has been assigned by the staff. These events are normally associated with a status update from the sortie. When Status communications are selected, the form will show a section that allows the user to click on the event type being reported (if necessary, additional information can be entered or the reporting event time can be changed). Using the event type check boxes simplifies the creation of the log entry and automatically updates the status of the sortie in the database.

Message communications are those that involve receipt of formal traffic from another station. A standard message form input screen will be displayed to allow entry of the message (When the entry is made, the formal message will be printed using the internet browser so that it can be delivered to the appropriate individual.

Clicking on the Enter button, will enter the information into the database and the log entry will be shown in the log summary at the bottom of the form. Clicking on an entry in the log summary will allow that entry to be edited.

Reports

Each functional form has the ability to print the associated form using the File menu. All IMU printing is performed by creating the form in an instance of the Microsoft Internet Browser. It can then be printed using a system printer, or forwarded using the email function if available. All forms are derived from the official forms on the National CAP website.

The forms that are available in the IMU are:

ICS 202
ICS 205
ICS 211
ICS 218
CAPF 104[1]
CAPF 105
CAPF 109
CAPF 110
CAPF 122

The Finance/Admin tab provides the ability to generate multiple forms from a single location. All forms that have applicable data associated with the open incident are listed along with a checkbox. If the checkbox is checked and the Print Selected Reports button is clicked, the reports will be generated.

Grid Assist

The Grid Assist form provides a graphical representation of selected areas. It consists of a lat/long grid with a form width of 30 minutes, 1 degree, 2 degrees, and 5 degrees. For widths of less than 5 degrees, the grid will also show the CAP grids, broken into the standard 4 sections. As the mouse is moved over the grid, the form shows the lat/long and grid section. The grid will also show the public use airports that exist in the selected area.

A new grid center is defined when the user double left clicks on a point on the grid. The grids will then be redrawn using the new point as a center.

If the user double right clicks on a point, a selection form will be displayed. If the computer has internet access, options are provided that will display an Aeronautical chart, a Topo Map, or a photo (if available) of the selected point.

Databases

In the Distributed mode, the system(s) will use database tables on the WMU server using the internet as a connection to move the information. In this mode, there is no need to upload incident information at the end of the incident since the data already resides there. This mode should not be used for testing or training. Data is available for all wings. New incidents can only be created by a user that is registered. Once open, general users can access the information by using the IC/AL information related to a registered user