Industry Solutions
 
      
Fire Dept & Emergency Medical Personnel:
ID Solutions   Professional Scheduling System
SPARK system   ASURE ID product family
      

   
   
For further information please visit
www.policescheduling.com

      

   
   
   

SPARK Accountability System

Symbology Enterprises, Inc is pleased to introduce our latest public service software package, SPARKS™. Designed using the input of Emergency Management Supervisors from across the state, SPARKS™ Simplifies the tracking of personnel activities.

SEI will create a solution utilizing inexpensive portable bar code scanners, a software product and ID cards to automate this operation. The system will eliminate all data entry and will not rely on volunteers signing a sheet of paper.

   

Firemen Response Tracking System 

Overview

Many Fire departments and EMT departments consist of and are operated by volunteers.  In the vast majority of cases there is a full time employee of the municipality that manages the volunteers and their stipend fund.  In departments with a mix of volunteer and full time employees the full time supervisors are responsible for logging the volunteers into and out of incidents.  In the full time volunteer departments the stipend fund is ran on an honor system. 

Currently the tracking of volunteers and the number of incidents that they respond to is handled manually.  The volunteer or a supervisor creates an incident report that the volunteer signs.  A full time employee of the municipality is then in charge of entering all the incidents and names into some form of spread sheet.  This manual effort is redundant, prone to error and of course takes many hours per month to accomplish. 

SEI will create a solution utilizing inexpensive portable bar code scanners, a software product and ID cards to automate this operation.  The system will eliminate all data entry and will not rely on volunteers signing a sheet of paper.

 

Objective

Provide software and hardware which will allow the supervisors to log fireman and EMT responses to emergency and non-emergency calls.  An emergency call would, of course be an incident like a fire or auto accident.  A non-emergency call could be firehouse cleanup, training,  parade or any number of other activities. 

Each incident would be identified by Incident number (auto generate) address, zone location, time out, time in, date, code, Building, Owner, fire companies responding and supervisors on site.  There should also be a free form accident report area and a “fireman injured” button which can be selected if there are injuries associated with the call. 

At any time, a supervisor should be able to run any one of several reports for an employee, incident, date or range of dates, type of incident (Code), location or any other of the primary fields.   

Codes should be user defined with a three or 4 character abbreviation, a full description and also linked to a Code type.  Code might be fire, traffic accident, fire drill, parade.  Code type similarly would be a user defined three or 4 character abbreviation, full description.  Code type might be mandatory emergency, optional emergency, non-emergency, training, certification, clean up.  

Firemen would be coded as users, supervisors or Admin. A fireman could be coded all of the above for reporting and operational purposes.  A fireman would have an employee number, Name, station assignment and perhaps some other personal data. 

Locations and Zones.  Locations can be associated with a zone.  A zone would be user defined  3 or 4 character abbreviation along with a full description.  A zone would be a geographic area. 

 

Operation

Supervisors would be able to log firemen by scanning their ID badge using a data collector.  This could be accomplished at the incident or following the incident at the station.  Alternately, the firemen could scan their badge at a PC which is running FRTS.  If using a data collector, upon return to the station, the supervisor would start FRTS, log on, and create an incident by entering the time, date location, incident category and other pertinent data.  Once this information is entered and saved, it should be permanent and only modifiable by an administrator level. 

Once the incident has been opened, the supervisor would place the data collector in the upload cradle, connected directly to the PC and upload the data into the FRTS application.  Once uploaded, the data would be editable by the supervisor.  The data uploaded from the data collector would consist of a series of records with the volunteer’s number along with a time/date stamp registering the time the volunteer was scanned. 

If there are duplicates, they would be noted in the upload data and the supervisor would be able to delete the erroneous record.

 

Reports

Incident detail:  For a date, date range, or incident number, Date, Location, Time Out, Time Returned, Code Number,  Building, Cause of Fire, Owner, Firemen reporting, and number of firemen reporting Accident report, supervisors in attendance.  Subtotal by Code, Subtotal by Code Type, Total for date range.  For a multi-location system, the reports could be subdivided by station. 

Employee detail: 
For a date range
Date, Incident number, Code, Time logged, Subtotal by Code, Subtotal by Code Type, Total for date range. 

 

General

Multi-location Operation: Each location should function as a stand alone system.  Initial setup would be accomplished at headquarters where all the fields and set up are configured.  Once the basic set up is done, the operator should be able to export a default set up file which can be imported into subsequent installations.  This would consist of information like codes, zones, and code types. 

Synchronization and upload of data: Each location in a multi-location system should be able to generate an export file with all the detail for a date range.  This should be of a format which can either copied across a network or emailed to the central system.  The central system would be able to import this file and update the central records. 

Password Access:
User – Only able to view personal records
Supervisor – Able to set up new incident and run reports.  Not able to modify saved data.
S
upervisor Admin – Able to modify saved data
Admin – Access to all function 

Database: MSDE  (NOT ACCESS) 

Interface: Visual Basic (NOT ACCESS) 

Install: Must be a single CD which is self installing.  The CD would automatically configure to accept data from whatever data collector or scanner is selected during the setup.  Online and electronic manual included in CD.  Getting started guide.  Default database which includes standardized codes, code types.  During install, the user would be prompted for the name and location of the department.

  

For further information about SPARKS™, please contact:  

Sales:
Symbology Enterprises, Inc  
185H Industrial Parkway  
Somerville, NJ 08876  
908-725-1699 Telephone

www.policescheduling.com