My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TIBURON (FORMERLY COMPUDYNE - PUBLIC SAFETY - SOFTWARE LICENSE) 2006
Clerk
>
Contracts / Agreements
>
T
>
TIBURON (FORMERLY COMPUDYNE - PUBLIC SAFETY - SOFTWARE LICENSE) 2006
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2014 12:54:09 PM
Creation date
4/13/2006 10:17:17 AM
Metadata
Fields
Template:
Contracts
Company Name
Compudyne Public Safety & Justice, Inc.
Contract #
A-2005-251
Agency
Fire
Council Approval Date
10/17/2005
Insurance Exp Date
4/1/2006
Notes
Amends A-2000-162
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
150
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
24SEVEN Version 2.6 CAD Services — Overview <br />CompuDyne Proprietary <br />0 2. OVERVIEW OF MESSAGE SCHEMA <br />Every message sent must be in a format that uses a valid XML, implementing the Message Receive <br />Schema (Message.XSD). <br />24SEVEN identifies Incidents by a combination of Incident Number/ Incident Date (Year). The product <br />uses these two fields as pseudo primary keys for recognizing whether or not the Incident exists. <br />If valid, it sends a CAD message, and if the Incident Number/Incident Date (Year) combination is unique, <br />the 24SEVEN CAD Feed will create a new Incident. If the Incident Number/Incident Date (Year) <br />combination is not unique, it will attempt to update the located Incident. <br />You can send any combination or order of Apparatus, Incidents or Alerts messages, in a single CAD <br />Message. <br />We do not allow Empty or Null Date/Time fields in our CAD messages. (If you must send a value, or <br />need to reset a Date Time to empty or null, you can send 01/01/1900 00:00:00. The 24Seven application <br />will treat this as an empty or null date time, and it will not be displayed in the application. If you send this <br />value though, it will overwrite any previous value you have in the database for that field). <br />2.1 MESSAGE SCHEMAS <br />The Message Receive Schema defined in the Message.XSD attached. It handles three types of messages: <br />• Incidents, Apparatus, and Alerts. All Messages require the following information: Incident Number and <br />Incident Date Fields to identify the specific Incident added or updated. The CAD Reply Message Schema <br />defined in the CAD Reply Message.XSD attached. It currently replies with basic information, but will <br />have additions down the road. The most useful information sent back from the CAD Reply Message is the <br />Size Column. It sends the Size of the XML message received in bytes. This can inform you of any <br />problems with poorly formed XML, from your CAD feed. <br />2.2 MESSAGE FORMAT XML <br />All CAD messages that 24SEVEN Web Service Adapter processes are standard, formatted, valid XML <br />documents. We have defined the Schemas and we distribute the XML Schema (.xsd) to you for review. <br />Our Web Service Adapter only understands well - formed, valid documents, which implement our schema. <br />Message Receive Schema — Defined in the Message.xsd and receives CAD massages. <br />CAD Reply Message — Defined in CADReplyMessage.xsd. The CAD Reply Message replies to CAD <br />messages (For extra copies of this documentation contact Tiburon, Inc.). <br />CompuDyne Proprietary <br />CompuDyne December 28, 2005 Page 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.