Laserfiche WebLink
APPENDIX 1 <br /> CAD INTERFACE SPECIFICATIONS <br /> • All the data will be read as string from the file. <br /> • CryWolf does not dictate the order of the fields in the text file. <br /> • CryWolf only mandates a few fields (indicated below), but including as many fields as <br /> possible, in the extracted false alarm CAD file, is the best approach. <br /> • All others can be included to simplify the work of the False Alarm Unit administrator. <br /> The mandatory fields are: <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 /> The date is stored as a date, but the text string (01/01/01, 01/21/2001, etc) in the text file is read <br /> and then converted as I load the field 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. Even if the agency does not run in "interactive" mode, the <br /> next 4 fields are very helpful and should be included if possible. <br /> Dispatch Code any code used by the CAD system to tell the type of call <br /> Clearance Code any clearance code usually given by the officer to the dispatcher indicating whether <br /> 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 about the call.("motion <br /> detector going off in back room","owner enroute",etc) <br /> Officer Comments whatever the officer says to the dispatcher that is typed into the narrative area of the <br /> 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 on the following page. <br /> Page 19 of 27 False Alarm Management Services <br /> Contract Agreement <br />