BOOK: Support SECTION: FMIS Pg. 1 of 2

BOOK: Support SECTION: FMIS Pg. 1 of 2

FMIS

TABLE OF CONTENTS

ADN/002BUSINESS HOURS(Chief CSM Only)

OPS/001 COMPUTER OPERATIONS MANUAL

OPS/002 INTEGRITY OF INCIDENT REPORTING

OPS/003 FIRE INCIDENT REPORT DATA ENTRY PROBLEMS

CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY
C
H
I
E
F
C
S
M
O
N
L
Y /

ADN/002BUSINESS HOURS

Normal business hours for FMIS administrative staff will be Monday through Friday, 0800 - 1700 hours. Staff will be granted a one-hour lunch interval during normal business hours.
Occasional situations will exist that may necessitate a deviation from normal business hours. Conditions that may require variation from normal business hours include high priority assignments and special projects. Approval from the Fire Information Systems Officer must be obtained prior to any schedule changes. / C
H
I
E
F
C
S
M
O
N
L
Y
CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY CHIEF CSM ONLY

OPS/001COMPUTER OPERATIONS MANUAL

The Fire Management Information System (FMIS) Computer Operations Manual should be kept in an accessible location of each computer terminal’s work station.

Each module explains and illustrates the correct procedures to follow when entering information in: Incident, Premise, Daily Staffing, Future Staffing, and Fire Hydrant reports. Also covered are procedures to follow for email, Mobile Data Terminal and Report Review operations and functions.

All personnel are required to review each module to ensure the method of data entry you presently use conforms to the correct procedures outlined in the manual. Questions pertaining to operating procedures described in this manual will be directed to your District/Shift FMIS Computer Coordinator.

If you discover any irregularities in this manual, please contact your District/Shift FMIS Computer Coordinator so corrections can be made. Comments or suggestions about additional materials that should be included or changed in the manual are also encouraged.

OPS/002INTEGRITY OF INCIDENT REPORTING

When an individual enters an incident report, it must be entered using his/her individual account, at no time should a report be entered under another Users ID. According to page 2-3 of the OCFD Computer Operations Manual, “Any employee can enter the information for an incident, but onlythe Incident Commander or the Officer in charge of a scene can verify and lock an incident.” All incidents are considered as legal documentation and must be verified and locked by the person in charge of the incident. Under no circumstance should an incident report be verified and locked by any person other than the Incident Commander or the Officer in charge.

OPS/003FIRE INCIDENT REPORT DATA ENTRY PROBLEMS

The following are fields and areas that are of concern:

If information for a field is not known or not applicable, leave the field blank, do not enter N/A or UNKNOWN. If a field asks for duplicate information already entered in another area of the report, do not put SAME AS ABOVE or SAME as an entry. Re-enter the information so that valid information can be retrieved for report inquiries. Refer to pages 2-3 and 2-6 of the OCFD Computer Operations Manual for further information.

In the OCC/DBA field and First and Second Person NAME fields, in the General Information section always enter in the format of LAST NAME, FIRST NAME when entering an individuals name.

Example: Allen Lee Brown would be Brown, Allen L.

If the telephone number is unknown do not enter zeros in the Phone field, leave blank. Refer to page 2-3 of the OCFD Computer Operations Manual for further information.

If the dispatch computer enters an intersection for an address of the incident, always replace the intersection with the correct address. Refer to page 2-4 of the OCFD Computer Operations Manual for further information.

All incidents with an incident type of 32 - EMS CALL must have the Local Data section of menu selection 2 - Casualty/EMS Entry; Patient information, Add/Update Detail and Local data fields completed if OCFD was on the scene first. Incidents with an incident type of 31 - Load or lift patient only; the Local Data fields portion does not have to be completed, but Patient information and Add/Update Detail fields must be completed if possible. Refer to pages 2-4 and 2-8 of the OCFD Computer Operations Manual for further information.

In selection 3 - Company Response of the Fire Incident Reporting program (FIRINC), in the Incident Times section, alltimes and dates must be completed which includes: Time and Date of Alarm, Dispatched, On Scene, Under Control and Incident Close time. If the dispatch computer does not supply these dates and times and/or enters zeros in these fields, the person entering the report shall enter the correct dates and times. Dispatched time should be on the Hot Printer in the DSP: field of the incident printout. Make the changes to the first apparatus on the scene and the Incident Times fields will change. Do not leave blanks or zeros in these fields. Refer to pages 2-21, 2-22, and 7-38 of the OCFD Computer Operations Manual for further information.

Always complete Incident Selection 6 - Vehicle/Equipment Entry, anytime there is a vehicle/equipment involved in an incident. This may be a vehicle/equipment incident only, a structure fire with a vehicle/equipment involved or other type of incident with a vehicle or other equipment involved. Refer to pages 2-3 and 2-32 - 2-34 of the OCFD Computer Operations Manual for further information.

Format Property of FireNotes, Inc® (OCFD.com) DO NOT DUPLICATE Last Revised: 1/16/2006 9:32:00 PM