|
24SEVEN Version 2.6 CAD Services — Overview
<br />CompuDyne Proprietary
<br />2.3.8 ADDRESS FIELDS
<br />It is recommended that CAD partners send parsed address elements in the address parts we provide,
<br />(number, street prefix, street, street suffix, street type, apartment, city, state, postal code). This way, the
<br />24SEVEN application will have the most accurate information. If you are not able to send parsed address
<br />parts, you can use the unparsed address elements: address], address2, city, state, zip. We parse these
<br />fields into the address parts, before placing them into our 24SEVEN database, but we only expect to be
<br />able to parse approximately 90% of addresses properly. If the address parses improperly, the customer
<br />can always correct this inside of the 24SEVEN application. CAD vendors need to be aware of this.
<br />2.3.9 SEQUENCES
<br />Sequences are used the same way in both the Message Alerts and Message Mutual Aid, along w/ the
<br />"remarkssequence" column in the Message Incident. They are pseudo -keys that can be used by CAD to
<br />keep track of updating or inserted data into the RMS. 24SEVEN will check if one of these messages has
<br />a sequence, and if the sequence value matches a sequence value currently in the RMS, then it will update
<br />the record instead of inserting the record. This is very valuable with handling of re- transferring calls, so
<br />alerts or other data elements are not duplicated.
<br />2.3.10 USING ADDRESS PARSING
<br />If using the 24SEVEN Queue Processor to parse the addresses, you need to be aware of certain precedents
<br />we use for parsing. If you are sending an unparsed address in "address 1 ", we will parse the address only if
<br />you are not sending any of the parsed street parts (number, street prefix, street, street suffix, street type,
<br />apartment). The "addressl" element can be either a street address or both street address and cross street
<br />• on intersection location types. If you are sending both street and cross street, use one of these symbols to
<br />separate them: (I / \). Use only "Address2" for cross street information, and it will only parse if we do not
<br />receive any of the Cross Street Address parts: (xstreet prefix, xstreet, xstreet suffix, xstreet type,
<br />directions).
<br />•
<br />2.3.11 SENDING MULTIPLE MESSAGES VERSUS SINGLE MESSAGE
<br />The CAD partner has the option to send one or multiple messages per CAD message. You can send one
<br />or multiple incidents, apparatus or alerts per single CAD message. We recommend, depending upon the
<br />traffic, sending one incident, apparatus, or alert per message. Our CAD feed can handle a significant
<br />volume of traffic, but by breaking down the messages into one message per CAD message, it enables
<br />possible error caching without restricting other messages.
<br />When you send a single message or multiple messages with any combination of apparatus, incidents or
<br />alerts and if one of the messages fails because of bad data or some other error, none of the messages will
<br />be processed and they will be placed as far along in the receiving process as possible. The decision to
<br />send one message or multiple messages is dependent upon your configuration, hardware and other
<br />factors.
<br />Note: For further assistance, please contact Engineering.
<br />CompuDyne Proprietary
<br />CompuDyne December 28, 2005 Page 6
<br />
|