TRITECH SOFTWARE SYSTEMS 2 - Laserfiche WebLink

Home Browse Search

Standard E-9-1-1 Interface TriTech Software 3.5.1 Design Constraints Rebid determination is made within a message type. If rebid information is received in a different message type than the initial message, identification and update as a rebid will not be possible. Depending on the message type identification scheme configured, some Phase I E911 received data may not correspond to the same message type as receive Phase II data. 3.6 Use Case: Address Conversion The E911 Interface provides several configurations to assist with conversion of E911 data for use in VisiCAD. • The E911 Interface can convert street types provided in the E911 data to street types recognized in VisiCAD, through a configurable translation. (e.g., 'HY' to 'HWY', 'BLVD' to 'BL', etc.) • The E911 Interface can optionally convert numerical street names (e.g., 2 ST' to '2nd ST') • The E911 Interface can identify and replace text strings within an address to account for abbreviations or problematic names for VisiCAD to process. • City codes or abbreviations provided in E911 data can be converted into a format recognized in VisiCAD through a configurable translation in the E911 Interface. 3.7 Use Case: Heartbeats from E911 Controller If required by the E911 Controller, the Interface will acknowledge all heartbeats. A heartbeat is a formatted message, with an identified text string as content that is to be delivered at regular intervals. Through the Interface setup, the user can specify the time allowed between heartbeats before it is determined that the E911 Controller is not sending messages, and VisiCAD workstations are to be notified of connection failure. 3.8 Use Case: Acknowledgement to E911 Controller If required by the E911 Controller, the Interface can be configured to acknowledge all valid messages received. The acknowledgement will be in the form of a formatted message containing a single ASCII character (typically ASCII value 6). It is typical that the E911 Controller re -send the message if the acknowledgement is not received within a prescribed period. 3.9 Use Case: Logging The interface shall log data process details of the interface. The data will be recorded into a log that the System Administrator can view. This information will not be displayed to the VisiCAD user and is primarily used for diagnostic purposes. The file name and location (path) of the logs are predetermined (local C Drive). The interface maintains the log files. As the logs reach their maximum size, the interface archives the current log file by modifying the filename with a date and time stamp string, and creates a new active/current file. The interface maintains a set number of archived log files. When the maximum allowed number of archived log files is reached, the interface will delete the oldest archived log file before archiving the current log file. Under this configuration there is little concern of the logging affecting system performance. Interface Requirements Document 7 of 11