Laserfiche WebLink
False Alarm Management-Outsource Services <br />Contract Agreement Page 17 of 18 <br /> <br />EXHIBIT 1 - CAD to CryWolf Data File Transfer Specifications <br /> <br />CryWolf System database can accept data from a CAD or RMS system that can export, or <br />have extracted, false alarm data in a format the CryWolf can read. These formats include <br />ASCII text (flat file) where the data fields are delimited (separated) by commas, fixed lengths, <br />or “pipe” characters; XML (web services); or MS Excel, CSV, SQL. <br />A. All the data will be read as string from the file. <br />B. CryWolf System does not dictate the order of the fields in the text file. <br />C. CryWolf System only mandates a few fields (indicated below), but including as many <br />fields as possible, in the extracted false alarm CAD file, is the best approach. <br />D. All others can be included to simplify the work of the false alarm unit Administrator. <br /> <br />It is recommended that the CAD extraction routine export daily alarm incident data, at a set <br />time each day as specified by the CITY. The extracted data will be in the form of a comma- <br />or fixed- length separated, ASCII text file (or other format see above) and will be transferred <br />to a “mm/yyyy” designated folder. This folder will be at a specific network directory location <br />that is accessible by both CAD (or RMS) and CryWolf System. This file will include the date <br />in its name, so that it can be easily selected by the agency’s CryWolf System operators for <br />import and processing by CryWolf System. The data fields in the CAD (or RMS) extracted file <br />will be specified by CITY. At a minimum the data fields will include a unique incident number, <br />incident date, street address, suite or apartment if possible, and false alarm clearance code. <br />The maximum number of fields will be limited by the data CryWolf System currently maintains <br />as described in Table 1.1. <br /> <br />Mandatory Fields: <br />• Case No: must be unique for each alarm incident <br />• Incident Date: must be in some standard format (mm/dd/yy, mm/dd/yyyy, etc) <br />• Incident Address: such as '123 MAIN ST' <br />• Apartment/Suite, if applicable <br /> <br />The date is stored as a date, but the text string (01/01/01, 01/21/2001, etc.) in the text file is <br />read and then converted as the field is loaded on the screen. <br />The next fields are used when the program is run in 'interactive' mode, where the program <br />determines whether to charge or not, which assists in processing false alarms faster. The next four <br />fields should be included, if possible. <br />Desired Fields: <br />• Dispatch Code: any code used by the CAD system to tell the type of call <br /> <br />• Clearance Code: any clearance code usually given by the officer to the dispatcher <br />indicating whether this was a real crime, a false alarm, nothing found, etc. <br />• Dispatch Comments: what the dispatcher types in usually what is relayed to him/her <br />about the call. ('motion detector going off in back room','owner enroute', etc) <br />• Officer Comments: whatever the officer says to the the dispatcher that is typed into the <br />narrative area of the CAD ('nothing found', 'building checked secure', etc) <br />All other fields are optional. <br />A complete list of data fields is shown in Table 1.1