Bi-Directional CAD Support

StreetWise CADlink can support bi-directional communication of data between an agency’s computer-aided dispatch (CAD) system and the StreetWise Central Server, allowing an agency to use StreetWise CADlink as its primary mobile data computer (MDC).

BiDirectional Diagram

Incident data can be sent from the CAD system to StreetWise at the time of dispatch using a number of different methods, depending on the capabilities of the CAD system (see Dispatch/CAD Support ).

StreetWise also has a Return Data API (application programming interface) available to allow CAD vendors to receive unit data for an agency’s mobile devices, including GPS coordinates and status timestamps. Through this Return Data API, the CAD vendor can use StreetWise data to update the location information for the agency’s mobile devices within the CAD software and update status timestamps (enroute, arrival, cleared) that indicate the unit’s current status or availability within the CAD resource tables. This Return Data API is fast, simple and easy to use, and will allow a CAD vendor to make full use of the StreetWise data in the same manner as data from any conventional mobile data workstation.

Use of the StreetWise Return Data API for sending data back to a CAD system is optional and is not necessary for the basic functionality of StreetWise software in mobile devices. It is intended for those agencies that wish to upgrade to a more sophisticated bi-directional data exchange in which the StreetWise field devices feed data back to the CAD system for full MDC operation. It can reduce the workload in the dispatch center by allowing automatic vehicle tracking, use of closest unit response logic, and silent status updating.

StreetWise cannot force data back into a CAD system, as any such software system is highly proprietary. The Return Data API is made available for CAD vendors to implement within their software. We can work directly with your CAD vendor on this effort if you wish. However, as their direct client, you would need to discuss the integration with your particular CAD vendor and direct them to work with us to accomplish your desired outcome. We can’t tell you whether or not your particular CAD vendor would charge you for their involvement or what that cost might be.

We create “plugins” for our Return Data API to adapt the data to both the format (XML, JSON, TAIP, NMEA, delimited text, etc.) as well as the method that each CAD vendor wishes the data to be sent by (HTTP, TCP, UDP, etc.). Often, the integration of AVL data is fairly simple, since many CAD systems are set up to receive AVL data in TAIP or NMEA format over UDP or TCP connections. Often, this is a basic “turn-it-on-and-it-works” process that is simple for both us and the CAD vendor. Status button integration can be a bit more complicated because CAD vendors don’t necessarily have a “common” method for taking in this type of data.  If they have any existing API for receiving unit status changes or AVL, they could provide their documentation to us for review. We could then discuss the best way to move forward, and if any customized middleware were necessary, you could determine whether you wanted them or us to do any such custom development work. If we do custom development work of middleware or API plugins, there would be a development charge, but we would be happy to provide a pricing estimate in advance for your review and approval.

Contact your CAD vendor to discuss any desired implementation of the Return Data API and whether or not their system is capable of using the API and the data. Our staff is available to discuss the Return Data API  directly with your CAD vendor by contacting us at 800-718-8027.

For a complete list of CAD vendors with whom we currently have a bi-directional data feed established, call or email our staff.