Packetalk Intelligent Engine

Creates an environment where multiple vendors can contribute to a common policing platform/view that includes functions that allow gis mapping, ptz camera manipulation, and connections to a CAD (computer aided dispatch) system. These connections allow a police force to realize gains in force multipliers by leveraging the technologies that they already have in order to make an existing force more efficient.

Abstract Description:

The system will be comprised of 3 different components. The service that manages all the traffic flow, the service that manages all the decision making, and the management console that will give a heads-up view into all activities within the system.

The Traffic Service (TS) will be implemented as a windows service that has the ability to instantiate the Decision Engine (DE) interface with any vendor that currently provides an implementation of the Packetalk Intelligent Engine interface (PIE). The PIE can be implemented via a C# .net dll or via a TCP Socket connection.

The Decision Service (DS) is responsible for taking any input/request received from the TS and performing any defined rules analysis before sending the requests on to the respective connected Action Providers (AP). The AP items will be added as new functionality is desired from within the system. There are 3 AP items (GIS Mapping, PTZ Camera Control, CAD Ticket Creation) that will be available with the basic implementation of the PIE system.

The Management Console (MC) will be developed to allow designated users to alter any system settings (rule definition, request hierarchy, etc). This same console will allow users to view the current activity in the system including, but not limited to, a list of historical events, a list of currently queued events, a list of currently connected vendors, a list of currently connected action providers. The console will also include a set of diagnostic tools to enable testing the system in order to isolate issues with specific components.

Technical Description:

  • Items To Develop:
    • Traffic service
    • Decision service
      • Allow definable hierarchy setting for connected vendor/services
    • External API definitions
      • TCP Type
      • C# dll Type
    • Internal Actions (mapped to external api calls)
      • GIS Mapping
        • ShowPointOnMap
          • Parameters
            • Location
              • From address
              • From xy
              • From intersection
              • From landmark
            • AutoRemoveTimeout
        • MoveCameraToPoint
          • Parameters
            • Location
              • From address
              • From xy
              • From intersection
              • From landmark
        • CreatePassiveIncident
          • Parameters
            • Location
              • From address
              • From xy
              • From intersection
              • From landmark
            • IncidentCode
        • CreateActiveIncident
          • Parameters
            • Location
              • From address
              • From xy
              • From intersection
              • From landmark
            • IncidentCode
            • UnitCount