WO2018045400A1 - Incident management & information capturing system - Google Patents

Incident management & information capturing system Download PDF

Info

Publication number
WO2018045400A1
WO2018045400A1 PCT/ZA2017/050053 ZA2017050053W WO2018045400A1 WO 2018045400 A1 WO2018045400 A1 WO 2018045400A1 ZA 2017050053 W ZA2017050053 W ZA 2017050053W WO 2018045400 A1 WO2018045400 A1 WO 2018045400A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
information elements
incident
vehicles
vehicle
Prior art date
Application number
PCT/ZA2017/050053
Other languages
French (fr)
Inventor
Brian Riggs
Original Assignee
Trackbox Technologies (Proprietary) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Trackbox Technologies (Proprietary) Limited filed Critical Trackbox Technologies (Proprietary) Limited
Publication of WO2018045400A1 publication Critical patent/WO2018045400A1/en
Priority to ZA2018/05235A priority Critical patent/ZA201805235B/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/26Government or public services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/101Collaborative creation, e.g. joint development of products or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G08SIGNALLING
    • G08BSIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B27/00Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations
    • G08B27/006Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations with transmission via telephone network

Definitions

  • THIS INVENTION relates to an incident management and information capturing system (IMICS).
  • IMICS incident management and information capturing system
  • the system provides a communications framework having particular, although not exclusive, application as a platform for crime fighting and emergency incident management. It exploits the prevalence of mobile electronic technology (such as mobile smartphones) in society to bridge communication gaps between the general public on the one hand, and civilian authorities such as law enforcement and emergency support authorities on the other. Information which is communicated can then be harnessed by the authorities for the purpose of providing appropriate incident responses.
  • the system provides a mechanism whereby the public and other users may capture information relating to suspicious persons and/or vehicles.
  • ERPC Emergency Response and Prevention Centre
  • Application (or “App”) - This terms includes reference to a system device software method installable on a processing means, for example an electronic device such as a mobile smartphone, tablet, notebook, laptop, personal computer, web- or cloud-based client, or the like.
  • Identity In addition to referring to a particular incident itself, this term encompasses within its meaning any persons, vehicles, objects and/or other factors associated with said incident. For example, if a particular incident involves an assessment by a member of the public that a person or vehicle is behaving suspiciously, or is suspected of involvement in the planning or commission of a crime, the term “incident” shall include reference to the person, vehicle, object or other factor involved.
  • information elements used in connection with said incident may accordingly include reference to information elements associated with said person, vehicle, etc., for example a set of characteristics, features and/or other profile data pertaining thereto.
  • Transmission imply transmission via a communication system, typically a wireless and/or cellular communication system.
  • references to the performance of actions or functions by a processing means are to be interpreted to imply that said actions or functions are mediated by way of the execution of corresponding software and the operation of corresponding hardware capable of executing said software.
  • This invention provides a mobile client-server architecture which allows users, including the general public, to capture various categories of information relating to crime and emergency incidents, to exchange such information with law enforcement and emergency response agencies, and to manage such incidents.
  • the system permits pertinent information elements relating to suspicious activities, persons and vehicles to be checked, logged and validated against a database.
  • a software application running on mobile devices (such as handheld smartphones carried by members of the public) communicates directly with the server so that information about persons and vehicles (inter alia) can be uploaded remotely to the server. The system can therefore be used to source and manage crime fighting and incident-related information.
  • an incident management and information capturing system comprising a communication infrastructure for capturing information pertinent to an incident and for managing said incident, said infrastructure including:
  • At least one processing means located remotely from said client, connected to and in electrical communication with said client and said data storage means, for processing said information elements;
  • information elements comprise information relating to characteristics of persons, vehicles and/or factors connected with said incident.
  • the information elements may be of types which are commonly categorised by civilian authorities (e.g. law enforcement authorities) for purposes of identification of persons, vehicles and/or other factors connected with an incident.
  • the information elements may include profile data, for example, characteristics and features, registration data and the like.
  • the application for the mobile client may be executable to display a menu- based GUI, said GUI being configured for prompting said user with regard to:
  • the application typically also provides routines for shortcuts to client functionality selected from the group consisting of cameras, audio and video recorders, GPS and other location means, and mapping tools.
  • the system may additionally include means for accessing databases of civilian authorities containing predetermined profile data of persons and vehicles.
  • the processing means may be configured for comparing and correlating uploaded (transmitted) information elements against said predetermined profile data in said databases, thereby to promote:
  • the system may include means for enabling authorised users to carry out checks selected from the group consisting of firearm checks; microdot checks; and identity number checks; and means for permitting alerts to be "pushed" or downloaded to the client (front end), said alerts comprising information extractable from said databases and being selected from the group consisting of wanted vehicle reports; wanted person reports; arrest reports; conviction reports; missing item reports; and found item reports.
  • the processing means may comprise at least one physical server or cloud- based processing platform.
  • the mobile application is typically supported by and connected to an emergency control centre.
  • the system typically includes a control centre comprising a back-end Emergency Control, Co-ordination and Response (ECCR) platform for managing a response to said incident by analysis and dissemination of said information elements, in some cases correlated against said databases of predetermined profile data.
  • Said platform may comprise infrastructure, personnel and process flows for managing said response and other activities of civilian authorities (such as law enforcement authorities and emergency support services), and the public.
  • the control centre typically also has process flows configured for the following purposes:
  • control centre may have pre-defined process flows adapted for managing the following:
  • the control centre may comprise an Emergency Response and Prevention Centre (ERPC).
  • ERPC Emergency Response and Prevention Centre
  • the client may comprise at least one mobile electronic device such as a handheld smartphone, tablet or the like).
  • the client may be operable by members of the general public, law enforcement authorities, emergency personnel, insurance companies, etc.
  • the client may include means for transmitting said information elements wirelessly to said server.
  • the system may include a wireless communications network connecting said client with said server or processing platform.
  • the system and application may provide a "Please Call Me” functionality on the client, so that with a single click or press of a GUI button or tab the ERPC will be prompted to call the user back.
  • This functionality is provided to address situations where the user has insufficient time or inclination to enter the information elements by way of the menus provided by the client GUI.
  • the database(s) are typically encrypted.
  • the information elements may be of types comprising a sub-set of types of such elements which are commonly categorised by civilian authorities (e.g. law enforcement authorities) for purposes of identification of persons and vehicles.
  • the information elements may include profile data of persons and vehicles.
  • the information elements may be selected from the group consisting of:
  • the information elements may be assigned to and relate to predefined categories in order to facilitate decision-making by a user of the mobile application, and to assist with information processing. These categories may additionally provide a menu structure for an application GUI as discussed further below.
  • the categories may be selected from the group consisting of: suspicious persons; suspicious vehicles; crime; medical incidents; fire and rescue incidents; traffic accidents; traffic alerts; roadside assistance; animal welfare; animal removal; municipal support; crisis centres; alarm monitoring; alarm technical support; administration and application support; and estate security.
  • the application may be executable to display a menu-based GUI on the client, said GUI being configured for prompting said user with regard to:
  • the application may provide routines for shortcuts to mobile client functionality selected from the group consisting of cameras, audio and video recorders, a GPS and other location means, and mapping tools.
  • the information elements which can be uploaded (or downloaded by authorised users) may include data relating to firearm checks; microdot checks; identity number checks; wanted vehicle reports; wanted person reports; arrest reports; conviction reports; missing item reports; and found item reports.
  • the user's cell phone number and IMEI number can also be captured.
  • the IMEI is a unique 15-digit number assigned to all cellular or mobile devices worldwide.
  • the control centre can use the IMEI number to block a mobile phone from being used by the user or another person or a phone company if it has been lost or stolen, or is sending false information.
  • the control centre can, furthermore, use the above information to track down and charge the user with "defeating the ends of justice” and any other associated crimes that may have been committed.
  • Emergency services both private and public are also able to claim any costs and damages against the user for the false information lodged.
  • IMICS Incident Management & Information Capturing System
  • FIG.1 exemplifies a smartphone screen interface by means of which a user may select a type of report which they wish to submit from a menu.
  • FIG.2 exemplifies a collapsed view of a Suspicious Person Report interface screen. This screen would be displayed if the menu item for SUSPICIOUS PERSON in Figure 1 had been selected.
  • the screen in Figure 2 provides a series of main categories of information pertinent to the suspicious person (DETAILS, LAST SEEN, CLOTHES and ACCESSORIES). It also provides shortcut icons allowing the user to capture and submit a photograph or the user's GPS location.
  • FIG.3 exemplifies an expanded view of the Suspicious Person Report interface screen shown in Figure 2.
  • Fig.4 exemplifies an expanded view of the Suspicious Person Report interface screen shown in Figure 2.
  • FIG.4 exemplifies a screen that provides a numerical selector modal for the "AGE (APPROX)" menu item in Figure 3.
  • a drum scroll facilitates input by the user of the approximate age of the suspicious person.
  • FIG.5 exemplifies a screen showing a populated Suspicious Person Report.
  • FIG.6 exemplifies a collapsed view of a Suspicious Vehicle Report interface screen.
  • FIG.7 exemplifies an expanded view of the Suspicious Person Report interface screen shown in Figure 6.
  • FIG.8 exemplifies a process flow diagram for a soft vehicle check which may be performed by operators of a "back-end" component of the system, after a report regarding a Suspicious Vehicle has been submitted by a mobile user.
  • the IMICS system comprises a communication infrastructure, not shown, having a client-server architecture for capturing information pertinent to an incident and for managing said incident.
  • the incident may, for example, involve a situation in which a member of the public has observed a suspicious person or vehicle and wishes to report this to the authorities.
  • the infrastructure includes a mobile client (not shown).
  • this mobile client may comprise a smartphone carried by the member of the public, who is the user.
  • the smartphone is loaded with an application which is executable to provide the user with an hierarchical, menu-based decision tree configured to prompt user input relating to information elements associated with the incident, and for capturing, storing and transmitting said information elements. Screens illustrating such a decision tree are represented in Figures 1 to 7.
  • the information elements relate to characteristics of persons, vehicles and other factors connected with the incident. These are uploaded onto the server.
  • the server may also have access to information contained in third party systems and databases such as those of various law enforcement authorities, insurance companies and the like.
  • a primary category of report is the General Report. As will be seen below, however, there are many other categories of reports envisaged for use with the invention.
  • the General Report is provided for purposes of reporting or submitting the following: a Suspicious Person; a Suspicious Vehicle; or an Anonymous Tip.
  • the system enables operators to check, log and validate persons and relevant elements of information pertaining to such persons against a database.
  • the App screen shown in Figure 3 illustrates how a user may be menu-prompted to capture and upload such information to the database.
  • the system enables operators to check, log and validate vehicles and relevant elements of information pertaining to such vehicles against a database.
  • the App screen shown in Figure 7 illustrates how a user may be menu-prompted to capture and upload such information to the database.
  • the information elements may be selected from the group consisting of:
  • VIN Vehicle Identification Number
  • a comprehensive list is set out below, comprising the main categories or types of information elements which may be collected and processed.
  • the first category is the General Report as discussed in detail above.
  • the list encompasses many other types of information elements which may pertain to possible incidents. This list can advantageously be applied to form the framework of an extended menu structure in the GUI of the application (App).
  • Duress Panic (code in key pad); Fixed Panic; Remote Panic; Burglary; Burglary with Zone ID; Mains Fail; Mains Restore; Low Battery; 24 Test; Bypass; Home; Business by Zone; Opening; Closing.
  • Estate Security e.g. Security at Residential & Business Estates
  • the App may be variously coded so that it is platform independent. For example, it may be configured to be executable under a variety of operating systems.
  • the App may provide shortcuts (as shown in Figures 2, 6) linking to ancillary smartphone functionality such as: a camera, microphone and/or video recorders (to photograph or record suspicious persons, vehicles, objects, etc.); GPS; and/or mapping systems.
  • ancillary smartphone functionality such as: a camera, microphone and/or video recorders (to photograph or record suspicious persons, vehicles, objects, etc.); GPS; and/or mapping systems.
  • the App may be provided free of charge to the public so that anybody may download it and participate in the operation of the system.
  • the App may also be provided as an ancillary component of paid-for services.
  • the system provides high level searching capabilities which enable comparisons of data. It includes a specialised backend interface with an Application Program Interface (API) to integrate into the systems of other authorities such as those of the police, fire brigade, medical services and security organisations.
  • API Application Program Interface
  • the server whether it is physically located or cloud-based, may include the following broad components:
  • This module includes an interface for managing suspicious persons in the database, including facilities to search manually for suspicious persons, update their data and capture new individuals as suspicious persons.
  • the information is captured in a format such that the suspicious person entry is able to be converted into a full profile on the IMICS profile database.
  • the profile would be categorised as a 'suspect' and the profile number would be referenced in a basic description in the suspicious person entry.
  • Descriptive fields are provided to record information as to what makes the subject person a suspicious person. These are pre-populated if the data came from a Case, but will need to be manually entered if the person is added to the suspicious person register manually. These fields can include a 'reason' (e.g. seen near crime, loitering, vagrant, suspicious behaviour, etc.) and the date and time seen.
  • a 'reason' e.g. seen near crime, loitering, vagrant, suspicious behaviour, etc.
  • a field for a Profile reference number (e.g. a security organisation membership number associated with a profile) is provided to link the sighting of the person with a single profile of the individual. Once a suspect is apprehended and their details verified, this field will allow for multiple sightings of the same suspect to be linked to a central record of the individual (Profile entry).
  • the system provides an interface for managing suspicious vehicles in the database, to enable operators to search manually for suspicious vehicles, update their data and capture new vehicles.
  • the vehicle data is automatically added to a "Suspicious Vehicles Database".
  • the vehicle may be deemed suspicious for various reasons. It could have been used in the commission of a crime, it could have been stolen from a victim or a complainant or it may have been behaving or positioned in a suspicious manner. Regardless, this vehicle description needs to be entered into the suspicious vehicle database such that any further queries on the registration number will be correlated to the previous sighting.
  • Descriptive fields are provided for entry of explanations as to why a particular vehicle has been deemed to be suspicious. These are pre- populated if the data comes from a Case, but can be manually entered if the vehicle is added to the suspicious vehicle register manually. These fields include a 'reason' (e.g. stolen, used in the commission of a crime, suspicious behaviour, etc.) and the date and time seen.
  • a 'reason' e.g. stolen, used in the commission of a crime, suspicious behaviour, etc.
  • a detailed search facility permits a search to be carried out using some of the populated description fields as well as information on Date, Time, "To” and “From” descriptors for "When Reported” times.
  • the system may be integrated with law enforcement databases.
  • such databases include:
  • NaTIS the National Traffic Information System which contains vehicle licensing and registration data
  • the system can correlate the vehicle with its corresponding details registered in NaTIS (e.g. details of its owner).
  • the SAPS Circulation System can then circulate a notification that the vehicle has been stolen, including date and time.
  • the system may therefore define user categories to determine which features and/or fields are relevant for particular users.
  • a user may be categorised as one or more of the following: an SAPS Member, Insurance Investigator, Neighbourhood Watch Member, General User, Medical Personnel member, etc.
  • GUI's with differing levels of complexity may be tailored for different categories of user.
  • Versions of the App for use by the police may contain features to which only the police have access, for example vehicle and firearm checks.
  • App screens for use by the public will typically have menus with fewer information elements, whereas interfaces intended for use by ERPC operators, the police and other authorities, or insurance companies, may have bespoke menus with a wider array of information elements.
  • the App does not permit the public to gain access to the majority of the information contained in police databases. At most, a user may be informed that a vehicle is stolen, but typically in the public domain such information will only be released to private response companies such as vehicle tracking companies or security companies. No further details will be given out.
  • the following hypothetical scenario provides an example of use of the IMICS system.
  • a user inputs a vehicle registration number or details of a suspicious person using the App.
  • the system performs a search against the IMICS database. Depending on the outcome of the search the case is either captured for future checking, or further action is taken by escalating it to the authorities as a "positive" vehicle that needs to be recovered or a person who needs to arrested, inspected, interviewed, etc.
  • the system permits a user to perform a soft check of vehicles or persons against a database.
  • a user is able to submit a vehicle registration number and vehicle description through the App as a "Soft Vehicle Check”.
  • the App will display a message to the user, such as "Thank you for submitting a registration number on a Soft Vehicle Check. We will contact you shortly to assist.”
  • the App user will not receive any notification of the results of the soft vehicle check, other than a telephone call response from the ERPC.
  • the ERPC operator On receiving a Soft Vehicle Check, the ERPC operator will call the member and ask for more details. The operator will be able to enter the details of their conversation in an "Action Taken" section of the Case. This opens a Suspicious Vehicle search window, which will automatically perform a search for suspicious vehicles against the database.
  • the result of the check is displayed onscreen, and the operator can then call the emergency services or provide feedback to the member that there was no suspicious behaviour detected.
  • IMICS is expected to provide advantages over and above other, more conventional methods of informing the police and for submitting tip offs.
  • the system has the potential to promote more effective and efficient interaction between the police and the general public.
  • the App provides convenient drop-down menus for the various information elements which are required for tip offs. Members of the public are therefore prompted in a structured and hierarchical manner as to the most important information required from them. This in turn can promote speed and relevance in regard to the capture and storage of data.
  • a further advantage is that a tip off report can be submitted without the Complainant first having to reach and engage with another person. This feature has the potential, again, to enhance speed of submission. It may also reduce issues relating to audio miscommunication and transcription errors which might otherwise occur in the recording of reports submitted orally by telephone (such as by the 101 1 1 system).
  • the IMICS system may have application in at least some of the following areas:
  • IMICS is, furthermore, "crowd-sourced”. By this is meant that it co-opts help from a broad societal base.
  • third party systems such as NaTIS, the SAPS Circulation System and the databases of insurance companies.
  • the system also promotes less conspicuous (more clandestine) submission of tip offs by the public, since no audible or visible outgoing telephone calls need to be made by members of the public wishing to report suspicious activities, persons or vehicles in their immediate vicinity.
  • the App menu can be used instead.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Alarm Systems (AREA)

Abstract

Incident management and information capturing system. The system has a communication infrastructure which includes a mobile client loadable with an application which is executable to provide a user with a hierarchical, menu- based decision tree configured (a) to prompt user input relating to information elements associated with an incident; and (b) for capturing, storing and transmitting the information elements. The system further comprises a data storage means and a remotely located processing means. The information elements comprise information relating to characteristics of persons, vehicles and/or other factors connected with the incident. In preferred embodiments the information elements relate to categories selected from the group consisting of: suspicious persons; suspicious vehicles; crime; medical incidents; fire and rescue incidents; traffic accidents; traffic alerts; roadside assistance; animal welfare; animal removal; municipal support; crisis centres; alarm monitoring; alarm technical support; administration and application support; and estate security.

Description

Description
Title of Invention:
INCIDENT MANAGEMENT & INFORMATION CAPTURING SYSTEM
Technical Field
[0001 ] THIS INVENTION relates to an incident management and information capturing system (IMICS). The system provides a communications framework having particular, although not exclusive, application as a platform for crime fighting and emergency incident management. It exploits the prevalence of mobile electronic technology (such as mobile smartphones) in society to bridge communication gaps between the general public on the one hand, and civilian authorities such as law enforcement and emergency support authorities on the other. Information which is communicated can then be harnessed by the authorities for the purpose of providing appropriate incident responses. In preferred embodiments the system provides a mechanism whereby the public and other users may capture information relating to suspicious persons and/or vehicles.
Background Art
[0001 ] The general public and law enforcement authorities lack an effective common platform for exchanging "real time" information relating to crime detection and reporting, for example information about criminal activities, crime suspects and those under investigation for various crimes in society. A need therefore exists for efficient systems to promote such a liaison.
[0002] Mobile devices such as smartphones have increasingly capable functionality and are in widespread use by the public; however, their functionality has not been fully exploited as a tool for management of criminal and emergency incidents.
[0003] In South Africa, the submission of reports and tip offs into the police system can be carried out by way of a telephone call to a 101 1 1 number. However, such call-based systems suffer a disadvantage insofar as they are often "human-memory driven." When a police officer on shift receives a call from a member of the public the information which he or she captures can be compromised by human limitations. Integrity of information can be lost as an officer goes off shift. There is also often no correlation between reports which are given independently for the same incident.
[0004] A need exists for systems and processes which can address the above shortcomings.
[0005] It is an object of the present invention to provide an infrastructure which will permit both the police and the general public to interact and exchange information about criminal activities as well as suspicious activities, persons, vehicles, objects and other factors, to track perpetrators of crime and, in general, to respond to incidents of a criminal or emergency nature. It is a further object of the invention to provide the public with tools enabling them to contribute to logging and verification in the crime elimination process. In short, the invention seeks to integrate police resources and community information through public input.
Definitions
[0006] As used herein, the following terms and acronyms have the following meanings:
ERPC - Emergency Response and Prevention Centre.
GPS - Geographical Positioning System.
GUI - Graphical User Interface.
SAPS - South African Police Service.
"Application" (or "App") - This terms includes reference to a system device software method installable on a processing means, for example an electronic device such as a mobile smartphone, tablet, notebook, laptop, personal computer, web- or cloud-based client, or the like.
"Incident" - In addition to referring to a particular incident itself, this term encompasses within its meaning any persons, vehicles, objects and/or other factors associated with said incident. For example, if a particular incident involves an assessment by a member of the public that a person or vehicle is behaving suspiciously, or is suspected of involvement in the planning or commission of a crime, the term "incident" shall include reference to the person, vehicle, object or other factor involved. The term "information elements" used in connection with said incident may accordingly include reference to information elements associated with said person, vehicle, etc., for example a set of characteristics, features and/or other profile data pertaining thereto.
"Transmission", "transmit" and the like imply transmission via a communication system, typically a wireless and/or cellular communication system.
"Comprises" (or "comprising") specifies the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps or components or groups thereof.
Numeral References
The claims appended to this description are to be considered as an integral part of the present disclosure. Reference numbers (directed to the drawings and figures) shown in the claims serve to facilitate the correlation of integers of the claims with illustrated features of the preferred embodiment(s), but are not intended to restrict in any way the language of the claims to what is shown in the drawings and figures, unless the contrary is clearly apparent from the context.
[0007] Unless otherwise indicated by the context, references to the performance of actions or functions by a processing means (such as a mobile electronic device, client, server, cloud-based processing means, application, control centre, etc.) are to be interpreted to imply that said actions or functions are mediated by way of the execution of corresponding software and the operation of corresponding hardware capable of executing said software.
Summary of Invention
[0008] This invention provides a mobile client-server architecture which allows users, including the general public, to capture various categories of information relating to crime and emergency incidents, to exchange such information with law enforcement and emergency response agencies, and to manage such incidents. In preferred embodiments of the invention the system permits pertinent information elements relating to suspicious activities, persons and vehicles to be checked, logged and validated against a database. A software application running on mobile devices (such as handheld smartphones carried by members of the public) communicates directly with the server so that information about persons and vehicles (inter alia) can be uploaded remotely to the server. The system can therefore be used to source and manage crime fighting and incident-related information.
Disclosure of Invention
[0009] According to a first aspect of the invention there is provided an incident management and information capturing system comprising a communication infrastructure for capturing information pertinent to an incident and for managing said incident, said infrastructure including:
at least one mobile client loadable with an application which is executable to provide a user with an hierarchical, menu-based decision tree configured to prompt user input relating to information elements associated with said incident, and for capturing, storing and transmitting said information elements;
data storage means for storing said information elements; and
at least one processing means located remotely from said client, connected to and in electrical communication with said client and said data storage means, for processing said information elements;
characterised in that said information elements comprise information relating to characteristics of persons, vehicles and/or factors connected with said incident.
[0010] In preferred embodiments the information elements may be of types which are commonly categorised by civilian authorities (e.g. law enforcement authorities) for purposes of identification of persons, vehicles and/or other factors connected with an incident. The information elements may include profile data, for example, characteristics and features, registration data and the like.
[001 1 ] The application for the mobile client may be executable to display a menu- based GUI, said GUI being configured for prompting said user with regard to:
high level (generalised) decisions as to which of a plurality of categories of report is to be input or submitted by the user (e.g. a General Report on suspicious persons and/or vehicles; or reports on crimes, medical incidents, fire and rescue incidents, traffic accidents; etc.);
low level (specific or granular) decisions regarding categories of information elements associated with at least one of said types of report; and data input of information elements, for onward transmission to the processing means and/or said data storage means.
[0012] The application typically also provides routines for shortcuts to client functionality selected from the group consisting of cameras, audio and video recorders, GPS and other location means, and mapping tools.
[0013] The system may additionally include means for accessing databases of civilian authorities containing predetermined profile data of persons and vehicles. The processing means may be configured for comparing and correlating uploaded (transmitted) information elements against said predetermined profile data in said databases, thereby to promote:
• at least partial identification of said persons and/or said vehicles; and
• management of said incident.
[0014] Thus the system may include means for enabling authorised users to carry out checks selected from the group consisting of firearm checks; microdot checks; and identity number checks; and means for permitting alerts to be "pushed" or downloaded to the client (front end), said alerts comprising information extractable from said databases and being selected from the group consisting of wanted vehicle reports; wanted person reports; arrest reports; conviction reports; missing item reports; and found item reports.
[0015] The processing means may comprise at least one physical server or cloud- based processing platform.
[0016] The mobile application is typically supported by and connected to an emergency control centre. Thus, the system typically includes a control centre comprising a back-end Emergency Control, Co-ordination and Response (ECCR) platform for managing a response to said incident by analysis and dissemination of said information elements, in some cases correlated against said databases of predetermined profile data. Said platform may comprise infrastructure, personnel and process flows for managing said response and other activities of civilian authorities (such as law enforcement authorities and emergency support services), and the public. [0017] The control centre typically also has process flows configured for the following purposes:
• to manage privacy and safety requirements, which are different for the public and the civilian authorities (police, fire brigade, medical service and security organisations); and
• to ensure that relevant information is kept secure or given to authorities where necessary.
[0018] Thus the control centre may have pre-defined process flows adapted for managing the following:
• a response to said incident, including the activities of civilian authorities and the public;
• privacy and safety; and
• security of information related to the incident.
[0019] The control centre may comprise an Emergency Response and Prevention Centre (ERPC).
[0020] The client (front-end) may comprise at least one mobile electronic device such as a handheld smartphone, tablet or the like). In use of the system, the client may be operable by members of the general public, law enforcement authorities, emergency personnel, insurance companies, etc.
[0021 ] The client may include means for transmitting said information elements wirelessly to said server. Accordingly, the system may include a wireless communications network connecting said client with said server or processing platform.
[0022] The system and application may provide a "Please Call Me" functionality on the client, so that with a single click or press of a GUI button or tab the ERPC will be prompted to call the user back. This functionality is provided to address situations where the user has insufficient time or inclination to enter the information elements by way of the menus provided by the client GUI.
[0023] The database(s) are typically encrypted. [0024] According to a further aspect of the invention there is provided an application loadable onto a client (front-end) and executable to provide a user with an hierarchical, menu-based decision tree configured for prompting user-input relating to information elements pertinent to an incident, said information elements comprising information relating to characteristics of persons, vehicles and/or factors relating to said incident; and for capturing, storing and transmitting said information elements.
[0025] Further features of the application may be as hereinbefore described.
[0026] Thus the information elements may be of types comprising a sub-set of types of such elements which are commonly categorised by civilian authorities (e.g. law enforcement authorities) for purposes of identification of persons and vehicles. The information elements may include profile data of persons and vehicles.
[0027] Without limitation thereto, the information elements may be selected from the group consisting of:
in respect of persons: a description of a person; details of a person; identity number of a person; place and time at which a person was last seen; clothes; accessories; and firearms;
in respect of vehicles: details of a vehicle; place and time at which a vehicle was last seen; vehicle identifying features; vehicle owner; vehicle cloning information; and microdot information; and
other factors pertinent to an incident, as categorised and listed in more detail below.
[0028] The information elements may be assigned to and relate to predefined categories in order to facilitate decision-making by a user of the mobile application, and to assist with information processing. These categories may additionally provide a menu structure for an application GUI as discussed further below.
[0029] The categories may be selected from the group consisting of: suspicious persons; suspicious vehicles; crime; medical incidents; fire and rescue incidents; traffic accidents; traffic alerts; roadside assistance; animal welfare; animal removal; municipal support; crisis centres; alarm monitoring; alarm technical support; administration and application support; and estate security. [0030] The application may be executable to display a menu-based GUI on the client, said GUI being configured for prompting said user with regard to:
high level (generalised) decisions as to which of a plurality of types of report is to be input or submitted by the user (e.g. report types relating to persons, vehicles, etc.);
low level (specific or granular) decisions regarding categories of information elements associated with at least one of said types of report; and
data input of information elements, for onward transmission to the processing means and/or said data storage means.
[0031 ] The application may provide routines for shortcuts to mobile client functionality selected from the group consisting of cameras, audio and video recorders, a GPS and other location means, and mapping tools.
[0032] In certain embodiments of the invention the information elements which can be uploaded (or downloaded by authorised users) may include data relating to firearm checks; microdot checks; identity number checks; wanted vehicle reports; wanted person reports; arrest reports; conviction reports; missing item reports; and found item reports.
[0033] To manage the possibility that criminals may send false information to deceive the police, all users of the IMICS system must preferably be registered and known. When sending information there is a live connection between the registered user and the control centre, which can capture the user's cell phone tower triangulation location to within ± 300 metres (network), and/or GPS location to within 6 metres.
[0034] The user's cell phone number and IMEI number (International Mobile Equipment Identity) can also be captured. The IMEI is a unique 15-digit number assigned to all cellular or mobile devices worldwide. The control centre can use the IMEI number to block a mobile phone from being used by the user or another person or a phone company if it has been lost or stolen, or is sending false information.
[0035] The control centre can, furthermore, use the above information to track down and charge the user with "defeating the ends of justice" and any other associated crimes that may have been committed. Emergency services both private and public are also able to claim any costs and damages against the user for the false information lodged.
[0036] Organisations operating the IMICS system must preferably provide reassurances to their users that their anonymity as tipsters will be preserved. This can be managed by way of contractual arrangements (terms and conditions) between the IMICS operator and the users. The IMICS operator and the control centre (ERPC) are the custodians and owners of all information, databases and processes. The information on file is used only for purposes of promoting appropriate goals and objectives of the system, for example the protection and saving of life or the recovery of stolen assets.
[0037] A proprietary name proposed for the system of the invention is "IMICS", an acronym for Incident Management & Information Capturing System.
Brief Description of Drawings
[0038] For a better understanding of the present invention and to show how the same may be carried into effect, specific embodiments of the invention will now be described by way of non-limiting example with reference to the accompanying diagrammatic Figures, wherein:
Fig.1
[Fig.1 ] exemplifies a smartphone screen interface by means of which a user may select a type of report which they wish to submit from a menu.
Fig.2
[Fig.2] exemplifies a collapsed view of a Suspicious Person Report interface screen. This screen would be displayed if the menu item for SUSPICIOUS PERSON in Figure 1 had been selected. The screen in Figure 2 provides a series of main categories of information pertinent to the suspicious person (DETAILS, LAST SEEN, CLOTHES and ACCESSORIES). It also provides shortcut icons allowing the user to capture and submit a photograph or the user's GPS location.
Fig.3
[Fig.3] exemplifies an expanded view of the Suspicious Person Report interface screen shown in Figure 2. Fig.4
[Fig.4] exemplifies a screen that provides a numerical selector modal for the "AGE (APPROX)" menu item in Figure 3. A drum scroll facilitates input by the user of the approximate age of the suspicious person.
Fig.5
[Fig.5] exemplifies a screen showing a populated Suspicious Person Report.
Fig.6
[Fig.6] exemplifies a collapsed view of a Suspicious Vehicle Report interface screen.
Fig.7
[Fig.7] exemplifies an expanded view of the Suspicious Person Report interface screen shown in Figure 6.
Fig.8
[Fig.8] exemplifies a process flow diagram for a soft vehicle check which may be performed by operators of a "back-end" component of the system, after a report regarding a Suspicious Vehicle has been submitted by a mobile user.
Detailed Description of Embodiments
[0039] Referring to the accompanying Figures, an IMICS system according to the invention is illustrated.
[0040] The IMICS system comprises a communication infrastructure, not shown, having a client-server architecture for capturing information pertinent to an incident and for managing said incident. The incident may, for example, involve a situation in which a member of the public has observed a suspicious person or vehicle and wishes to report this to the authorities.
[0041 ] The infrastructure includes a mobile client (not shown). For illustrative purposes, this mobile client may comprise a smartphone carried by the member of the public, who is the user. The smartphone is loaded with an application which is executable to provide the user with an hierarchical, menu-based decision tree configured to prompt user input relating to information elements associated with the incident, and for capturing, storing and transmitting said information elements. Screens illustrating such a decision tree are represented in Figures 1 to 7. [0042] The information elements relate to characteristics of persons, vehicles and other factors connected with the incident. These are uploaded onto the server. As is more fully described elsewhere herein, the server may also have access to information contained in third party systems and databases such as those of various law enforcement authorities, insurance companies and the like.
Categories & Types of Information Elements reportable by a User:
[0043] A primary category of report is the General Report. As will be seen below, however, there are many other categories of reports envisaged for use with the invention. The General Report is provided for purposes of reporting or submitting the following: a Suspicious Person; a Suspicious Vehicle; or an Anonymous Tip.
[0044] The following section discusses in greater detail the types of information elements that can be associated with the broad General Report.
A: Persons (Human Beings):
[0045] The system enables operators to check, log and validate persons and relevant elements of information pertaining to such persons against a database. The App screen shown in Figure 3 illustrates how a user may be menu-prompted to capture and upload such information to the database.
[0046] The information elements which may be logged in this connection fall under the following main headings (see the above "Disclosure of the Invention" for the individual bulleted elements of each heading):
• Description of Person
• Details
• Last seen
• Clothes
• Accessories
B: Vehicles:
[0047] The system enables operators to check, log and validate vehicles and relevant elements of information pertaining to such vehicles against a database. The App screen shown in Figure 7 illustrates how a user may be menu-prompted to capture and upload such information to the database.
[0048] The information elements which may be logged in this connection fall under the following main headings (see the above "Disclosure of the Invention" for the individual bulleted elements of each heading):
• Details
• Last Seen
• Vehicle Identifying Features
• Vehicle Owner
• Vehicle Cloning
[0049] Subsets of the above categories are listed further below in the detailed description of the invention.
[0050] In more detail, the information elements may be selected from the group consisting of:
(a) In respect of persons:
Description of:
• Suspicious Person
• Person of Interest
• Convicted Person
• Accused / Awaiting Trial
• Missing Person
• Missing Child
Details
• Age (Approximate)
Build
• Height
• Weight
• Complexion
• Gait
• Identifying Marks Hair
• Eye Colour
Last seen
• Physical address
• GPS Coordinates
• Date
• Time
• Photograph
Clothes
• Shirt
• Pants
• Shoes
• Headwear
• Jacket
• Sunglasses
• Balaclava
• Mask
Accessories
• Brief case
• Umbrella
• Cell phone
Wallet
• Backpack
• Weapons in possession spect of vehicles:
Details
• Vehicle Manufacturer
• Vehicle Type
Motorcycle
Tricycle Motorcycle
Passenger Car
Bus Taxi
Light truck
Pickup Truck
Commercial Truck
Trailer
Motor Caravan
Campervan
Motorhome
Armoured Car (VIP)
Armoured Car (Valuables)
Ambulance
Police
Traffic Police
Fire Engine
• Model
• Shade
• Colour
• Registration
• Year of Manufacture
• Vehicle Identification Number (VIN)
• Engine Number
• Licence Expiry Date
• Insurance Company
• Policy Number
• Photograph
Left Side
Right Side
Front
Back
Last Seen
• Physical address
• GPS coordinates • Date
• Time
• Photograph
Vehicle Identifying Features
• Rims
• Dents
• Scratches
• Missing Parts
• Aerial/Antenna
• Bullet Holes
• Rust
• Stickers
• Tow bar
• Fairing & Trim
• Spot lights
• Lights
Vehicle Owner
• Photograph (e.g. from an Identity Document)
• Name
• Surname
• Identity Document Number
• Telephone
• Cell Phone
• Address
• Police Case Number
Stolen
Recovered
• IMICS Profile Number
Vehicle Cloning
• Where the vehicle was originally registered.
• Financial institution through which the vehicle was financed.
• Who notified the legal owner of the cloning? • Location where the original legal log book (registration certificate) is held.
• To whom is the vehicle illegally registered now?
[0051 ] A comprehensive list is set out below, comprising the main categories or types of information elements which may be collected and processed. The first category is the General Report as discussed in detail above. In addition, the list encompasses many other types of information elements which may pertain to possible incidents. This list can advantageously be applied to form the framework of an extended menu structure in the GUI of the application (App).
[0052] Categories:
• General Report:
Suspicious Person; Suspicious Vehicle; Anonymous Tip.
• Crime:
Armed Robbery-Business; Armed Robbery-Home; Arson; Assault- Aggravated; Assault-Common; Assault-Grievous Bodily Harm (GBH); Assault-Physical; Assault-Weapon; Automated Teller Machine (ATM) Blown up; ATM-Card Cloning; ATM-Card Swopping; Bomb Blast; Bomb Threat; Burglary-Business; Burglary-Residential; Child Abuse; Corruption; Dangerous Driving; Disturbing the Peace; Domestic Violence; Drug Offences; Fraud; Handling Stolen Goods; Harassment; Hijacking- Attempted; Hijacking-Car; Hijacking-Truck; Hit and Run; House Breaking; Identity Theft; Intimidation; Kidnapping-Adult; Kidnapping-Child; Loitering; Looting; Malicious Damage to Property; Missing Person; Murder; Murder- Attempted; Other; Poaching; Police Brutality; Possession of Weapons; Public Disorder and/or Protests; Rape-Adult; Rape-Child; Rape- Incestuous; Scam; Sexual Assault; Sexual Harassment; Shoplifting; Stalking; Suicide; Theft-Electrical Cable; Theft-Electronics; Theft-Firearm; Theft-Motor Vehicle; Theft-Other; Theft-Out of Motor Vehicle; Theft-Stock; Theft-Telecommunications Cable; Theft-Truck;Trespassing; Vandalism; X- IN Human Trafficking.
Medical:
Allergic Reactions; Amputation; Asthma Attack; Breathing Difficulties; Burn Injuries; Chest Pains; Collapsed-Conscious; Collapsed-Unconscious; Concussion; Deceased; Diabetes; Difficulty Breathing; Electrical Injury; Epileptic Fit; Fractures-All; Heart Attack-Alive; Heart Attack-Deceased; Labour; Seizure; Spinal Cord Injury; Stroke.
Fire & Rescue:
Building Fire-Business; Building Fire-House; Building Fire-Warehouse; Deceased-Body Recovery; Fire-Bush and/or Veld; Fire-Chemical; Fire- Car; Fire-Truck; Fire-Taxi; Mountain Rescue.
Traffic Accident:
Motor Vehicle Accident; Motor Vehicle Collision; Pedestrian knocked down. Traffic Alert:
Abnormal Load; Animals on Road; Body on Road; Broken down vehicle; Congestion; Landslide; Obstruction; Potholes; Protesting; Road-Closure; Road-Maintenance; Road-Obstructed; Road Flooded; Roadworks; Sinkhole; Spill-Chemical; Spill-Fuel; Spill-Oil; Taxi Strike; Throwing Stones; Traffic Jam.
Roadside Assistance:
Breakdown; Engine Failure; Flat Tyre; Keys locked in vehicle; Dead Battery.
Animal Welfare:
Missing Pet; Poaching; Roaming Cattle; Roaming Goats; Roaming Horses. Animal Removal: Snakes; Bees. Municipal Support: Abandoned houses; Concrete drain culverts; Graffiti; Gutter cleaning; Illegal signage; Manhole covers; Missing Street signs; Outage: Electricity; Outage: Robots (Traffic Lights); Outage: Street Lights; Outage: Water; Overgrown trees and/or bushes; Pavements; Potholes; Request: Speed Timing; Road markings; Road repairs; Rubbish bins; Snake removals; Verge cutting; Water Leak; Other.
• Crisis Centre:
Attempted Suicide; Bipolar Mood Disorder; Domestic Violence; Runaway; Suicide.
• Alarm Monitoring:
Duress Panic (code in key pad); Fixed Panic; Remote Panic; Burglary; Burglary with Zone ID; Mains Fail; Mains Restore; Low Battery; 24 Test; Bypass; Home; Business by Zone; Opening; Closing.
• Alarm Technical Support:
Fault Reporting.
• Administration and App Support:
App Support; Admin Support; Accounts Support.
• Estate Security (e.g. Security at Residential & Business Estates):
News & Notifications; Estate Feedback.
[0053] The App may be variously coded so that it is platform independent. For example, it may be configured to be executable under a variety of operating systems.
[0054] The App may provide shortcuts (as shown in Figures 2, 6) linking to ancillary smartphone functionality such as: a camera, microphone and/or video recorders (to photograph or record suspicious persons, vehicles, objects, etc.); GPS; and/or mapping systems.
[0055] In use of the system, the App may be provided free of charge to the public so that anybody may download it and participate in the operation of the system. The App may also be provided as an ancillary component of paid-for services. [0056] The system provides high level searching capabilities which enable comparisons of data. It includes a specialised backend interface with an Application Program Interface (API) to integrate into the systems of other authorities such as those of the police, fire brigade, medical services and security organisations.
[0057] The server, whether it is physically located or cloud-based, may include the following broad components:
• a database management system for storing uploaded information;
• an access controller for identifying and authenticating user categories; and
• a listener for detecting client connections and requests.
Architecture and Modules of System: i) Module: Suspicious Person Database Management
[0058] This module includes an interface for managing suspicious persons in the database, including facilities to search manually for suspicious persons, update their data and capture new individuals as suspicious persons.
[0059] When a case is created which involves a suspect or a suspicious person, the description and any available information is automatically added to a "Suspicious Person Database".
[0060] The information is captured in a format such that the suspicious person entry is able to be converted into a full profile on the IMICS profile database. In this case, the profile would be categorised as a 'suspect' and the profile number would be referenced in a basic description in the suspicious person entry.
Capture suspicious person (external to a Case)
a. Create new entry; name and identity number is not mandatory.
b. All descriptive fields for a suspicious person as per the Case screen are available here.
c. A facility exists to upload images of the person or of a vehicle or object associated with the person, with a free descriptor field for each image.
d. Descriptive fields are provided to record information as to what makes the subject person a suspicious person. These are pre-populated if the data came from a Case, but will need to be manually entered if the person is added to the suspicious person register manually. These fields can include a 'reason' (e.g. seen near crime, loitering, vagrant, suspicious behaviour, etc.) and the date and time seen.
e. A field for a Profile reference number (e.g. a security organisation membership number associated with a profile) is provided to link the sighting of the person with a single profile of the individual. Once a suspect is apprehended and their details verified, this field will allow for multiple sightings of the same suspect to be linked to a central record of the individual (Profile entry).
Search suspicious vehicles
a. If the suspicious person entry is linked to a profile, it must be possible to search all suspicious person entries linked to that profile. This will allow for displaying the link between multiple sightings of a suspicious person back to a single individual.
b. A detailed search facility permits a search on some of the populated description fields as well as information on Date, Time, To and From descriptors for 'when reported' times. ii) Module: Suspicious Vehicle Database Management
[0061 ] The system provides an interface for managing suspicious vehicles in the database, to enable operators to search manually for suspicious vehicles, update their data and capture new vehicles.
[0062] When a case is created which involves a vehicle, the vehicle data is automatically added to a "Suspicious Vehicles Database". The vehicle may be deemed suspicious for various reasons. It could have been used in the commission of a crime, it could have been stolen from a victim or a complainant or it may have been behaving or positioned in a suspicious manner. Regardless, this vehicle description needs to be entered into the suspicious vehicle database such that any further queries on the registration number will be correlated to the previous sighting.
[0063] Although descriptive fields are able to be captured in full, both in the suspicious vehicle database directly or in Cases, the primary search criteria and the search criteria to perform a Soft Vehicle Check will remain the registration number (number plate).
[0064] The system provides the following functionality:
Capture suspicious vehicle (external to a Case).
a. Create new entry. The registration number is not mandatory and the facility to capture a partial number is allowable.
b. All descriptive fields for a vehicle as per the Case screen are available here. c. A facility exists to upload images of the vehicle with a free descriptor field for each image.
d. Descriptive fields are provided for entry of explanations as to why a particular vehicle has been deemed to be suspicious. These are pre- populated if the data comes from a Case, but can be manually entered if the vehicle is added to the suspicious vehicle register manually. These fields include a 'reason' (e.g. stolen, used in the commission of a crime, suspicious behaviour, etc.) and the date and time seen.
Search suspicious vehicles.
a. A facility exists to perform a "quick search" of a registration number or a partial registration number. The search result shows all relevant vehicles. b. A detailed search facility permits a search to be carried out using some of the populated description fields as well as information on Date, Time, "To" and "From" descriptors for "When Reported" times.
[0065] The system may be integrated with law enforcement databases. In South Africa, for example, such databases include:
• NaTIS (the National Traffic Information System) which contains vehicle licensing and registration data; and
• the SAPS Circulation System.
[0066] If information is provided relating to a stolen vehicle, the system can correlate the vehicle with its corresponding details registered in NaTIS (e.g. details of its owner). The SAPS Circulation System can then circulate a notification that the vehicle has been stolen, including date and time. Information Access and Access Control
[0067] For security and control purposes there is a restriction on what information is available to which user category. It will be appreciated that different categories of users require access to different levels of information. In some embodiments of the invention, the system may therefore define user categories to determine which features and/or fields are relevant for particular users. For example, a user may be categorised as one or more of the following: an SAPS Member, Insurance Investigator, Neighbourhood Watch Member, General User, Medical Personnel member, etc.
[0068] Accordingly, not all users need to be prompted for all the information elements. It follows that GUI's with differing levels of complexity may be tailored for different categories of user. Versions of the App for use by the police may contain features to which only the police have access, for example vehicle and firearm checks. App screens for use by the public will typically have menus with fewer information elements, whereas interfaces intended for use by ERPC operators, the police and other authorities, or insurance companies, may have bespoke menus with a wider array of information elements.
[0069] The App does not permit the public to gain access to the majority of the information contained in police databases. At most, a user may be informed that a vehicle is stolen, but typically in the public domain such information will only be released to private response companies such as vehicle tracking companies or security companies. No further details will be given out.
[0070] In certain circumstances, however, it may be deemed appropriate by the ERPC in consultation with law enforcement authorities, to communicate information contained within the database to public media and/or search and rescue service providers.
[0071 ] The following hypothetical scenario provides an example of use of the IMICS system. A user inputs a vehicle registration number or details of a suspicious person using the App. The system performs a search against the IMICS database. Depending on the outcome of the search the case is either captured for future checking, or further action is taken by escalating it to the authorities as a "positive" vehicle that needs to be recovered or a person who needs to arrested, inspected, interviewed, etc.
[0072] Referring to Figure 8 in this connection, the system permits a user to perform a soft check of vehicles or persons against a database. A user is able to submit a vehicle registration number and vehicle description through the App as a "Soft Vehicle Check".
[0073] This will appear as a Case of this type in the ERPC system. The vehicle registration details will be displayed in the Case and the ERPC operator is able to click a Check Suspicious Vehicle button. The soft vehicle check case will have the App's user details as the Complainant and the details of the registration number and description.
[0074] The App will display a message to the user, such as "Thank you for submitting a registration number on a Soft Vehicle Check. We will contact you shortly to assist." The App user will not receive any notification of the results of the soft vehicle check, other than a telephone call response from the ERPC. On receiving a Soft Vehicle Check, the ERPC operator will call the member and ask for more details. The operator will be able to enter the details of their conversation in an "Action Taken" section of the Case. This opens a Suspicious Vehicle search window, which will automatically perform a search for suspicious vehicles against the database. The result of the check is displayed onscreen, and the operator can then call the emergency services or provide feedback to the member that there was no suspicious behaviour detected.
Advantageous Effects of Invention
[0075] IMICS is expected to provide advantages over and above other, more conventional methods of informing the police and for submitting tip offs.
[0076] The system has the potential to promote more effective and efficient interaction between the police and the general public. The App provides convenient drop-down menus for the various information elements which are required for tip offs. Members of the public are therefore prompted in a structured and hierarchical manner as to the most important information required from them. This in turn can promote speed and relevance in regard to the capture and storage of data.
[0077] A further advantage is that a tip off report can be submitted without the Complainant first having to reach and engage with another person. This feature has the potential, again, to enhance speed of submission. It may also reduce issues relating to audio miscommunication and transcription errors which might otherwise occur in the recording of reports submitted orally by telephone (such as by the 101 1 1 system).
[0078] The IMICS system may have application in at least some of the following areas:
• Crime prevention;
• Detection, reporting and tracking down of criminal perpetrators;
• Wanted persons;
• Vehicle theft;
• Vehicles of Interest;
• Ownership enquiries;
• Logging Suspicious Vehicles;
• Emergency services;
• Medical Support Services;
• Roadside assistance;
• Access control; and
• Vehicles parked in Wheelchair Parking.
[0079] IMICS is, furthermore, "crowd-sourced". By this is meant that it co-opts help from a broad societal base. In addition to receiving input from the general public it can integrate with existing third party systems such as NaTIS, the SAPS Circulation System and the databases of insurance companies.
[0080] The system also promotes less conspicuous (more clandestine) submission of tip offs by the public, since no audible or visible outgoing telephone calls need to be made by members of the public wishing to report suspicious activities, persons or vehicles in their immediate vicinity. The App menu can be used instead.

Claims

Claims
[Claim 1 ] An incident management and information capturing system comprising a communication infrastructure for capturing information pertinent to an incident and for managing said incident, said infrastructure including:
at least one mobile client loadable with an application which is executable to provide a user with an hierarchical, menu-based decision tree configured to prompt user input relating to information elements associated with said incident, and for capturing, storing and transmitting said information elements;
data storage means for storing said information elements; and at least one processing means located remotely from said client, connected to and in electrical communication with said client and said data storage means, for processing said information elements;
characterised in that said information elements comprise information relating to characteristics [Fig.1 ] of persons, vehicles and/or factors connected with said incident.
[Claim 2] A system as claimed in Claim 1 , wherein said information elements relate to categories selected from the group consisting of: suspicious persons; suspicious vehicles; crime; medical incidents; fire and rescue incidents; traffic accidents; traffic alerts; roadside assistance; animal welfare; animal removal; municipal support; crisis centres; alarm monitoring; alarm technical support; administration and application support; and estate security.
[Claim 3] A system as claimed in Claim 1 or Claim 2, wherein said information elements are of types which are commonly categorised by civilian authorities for purposes of identification of persons and vehicles.
[Claim 4] A system as claimed in any one of Claims 1 to 3 inclusive, wherein said loadable application is executable to display a menu-based graphical user interface [Figs 1 -7] on said client, said graphical user interface being configured for prompting said user with regard to: decisions as to which of a plurality of types of reports [Fig. 1 ] is to be submitted by said user, said types including at least (a) a report type relating to persons and (b) a report type relating to vehicles;
decisions regarding categories of information elements [Figs. 2-7] associated with at least one of said types of report; and
data input of information elements, for onward transmission to the processing means and/or said data storage means.
[Claim 5] A system as claimed in any one of Claims 1 to 4 inclusive, wherein said loadable application provides routines for shortcuts to mobile client functionality selected from the group consisting of cameras, audio and video recorders, a geographical positioning system and other location means, and mapping tools.
[Claim 6] A system as claimed in any one of Claims 1 to 5 inclusive, which includes
databases of civilian authorities containing predetermined profile data of persons and vehicles; and
means for accessing said databases;
and wherein said processing means is configured for comparing and correlating said information elements against said predetermined profile data in said databases.
[Claim 7] A system as claimed in Claim 6, which includes
means for enabling authorised users to carry out checks selected from the group consisting of firearm checks; microdot checks; and identity number checks; and
means for permitting alerts to be downloaded to the client, said alerts comprising information extractable from said databases and being selected from the group consisting of wanted vehicle reports; wanted person reports; arrest reports; conviction reports; missing item reports; and found item reports.
[Claim 8] A system as claimed in any one of Claims 1 to 7 inclusive, which includes a control centre having pre-defined process flows adapted for managing: a response to said incident, including activities of civilian authorities and the public;
privacy and safety; and
security of information related to said incident.
[Claim 9] An application loadable onto a client and executable to provide a user with an hierarchical, menu-based decision tree configured for prompting user- input relating to information elements pertinent to an incident, said information elements comprising information relating to characteristics of persons, vehicles and/or factors relating to said incident; and for capturing, storing and transmitting said information elements.
[Claim 10] An application as claimed in Claim 9, wherein said information elements relate to categories selected from the group consisting of: suspicious persons; suspicious vehicles; crime; medical incidents; fire and rescue incidents; traffic accidents; traffic alerts; roadside assistance; animal welfare; animal removal; municipal support; crisis centres; alarm monitoring; alarm technical support; administration and application support; and estate security.
[Claim 1 1 ] An application as claimed in Claim 9 or Claim 10, wherein said information elements are of types which are commonly categorised by civilian authorities for purposes of identification of persons and vehicles.
[Claim 12] An application as claimed in any one of Claims 9 to 1 1 inclusive, wherein the information elements are selected from the group consisting of: in respect of persons: a description of a person; details of a person; identity number of a person; place and time at which a person was last seen; clothes; accessories; and firearms; and
in respect of vehicles: details of a vehicle; place and time at which a vehicle was last seen; vehicle identifying features; vehicle owner; vehicle cloning information; and microdot information.
[Claim 13] An application as claimed in any one of Claims 9 to 12 inclusive, which is executable to display a menu-based graphical user interface [Figs 1 - 7] on said client, said graphical user interface being configured for prompting said user with regard to:
decisions regarding which of a plurality of types of reports [Fig. 1 ] is to be submitted by said user, said types including at least (a) a report type relating to a person and (b) a report type relating to a vehicle;
decisions regarding categories of information elements [Figs. 2-7] associated with at least one of said types of report; and
data input of information elements, for onward transmission to the processing means and/or said data storage means.
[Claim 14] An application as claimed in any one of Claims 9 to 13 inclusive, which provides routines for shortcuts to mobile client functionality selected from the group consisting of cameras, audio and video recorders, a geographical positioning system and other location means, and mapping tools.
[Claim 15] An incident management and information capturing system which includes any new and inventive integer or combination of integers, substantially as herein described and/or exemplified.
[Claim 16] An application which includes any new and inventive integer or combination of integers, substantially as herein described and/or exemplified.
[Claim 17] An incident management and information capturing system, as claimed in Claim 1 , specifically as herein described with reference to or as illustrated in any one of the accompanying figures.
[Claim 18] An application, as claimed in Claim 9, specifically as herein described with reference to or as illustrated in any one of the accompanying figures.
PCT/ZA2017/050053 2016-09-05 2017-09-05 Incident management & information capturing system WO2018045400A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
ZA2018/05235A ZA201805235B (en) 2016-09-05 2018-08-03 Incident management & information capturing system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ZA2016/06119 2016-09-05
ZA201606119 2016-09-05

Publications (1)

Publication Number Publication Date
WO2018045400A1 true WO2018045400A1 (en) 2018-03-08

Family

ID=61309463

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/ZA2017/050053 WO2018045400A1 (en) 2016-09-05 2017-09-05 Incident management & information capturing system

Country Status (2)

Country Link
WO (1) WO2018045400A1 (en)
ZA (1) ZA201805235B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110674238A (en) * 2019-09-26 2020-01-10 四川科瑞软件有限责任公司 Toxicity prohibition information studying and judging system based on big data
US10692359B2 (en) 2018-04-23 2020-06-23 Green Line Business Group Witness request and alert notification and tracking system
JP7360295B2 (en) 2019-10-03 2023-10-12 一般財団法人電力中央研究所 Information collection system, information collection method, and program

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005027486A2 (en) * 2003-09-15 2005-03-24 Accenture Global Services Gmbh Remote media call center
US20130196614A1 (en) * 2012-01-29 2013-08-01 Crimepush Llc Mobile alert reporting and monitoring systems and methods
US20130300563A1 (en) * 2012-05-09 2013-11-14 Raymond Glaze Mobile incident reporting of organized retail crime

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005027486A2 (en) * 2003-09-15 2005-03-24 Accenture Global Services Gmbh Remote media call center
US20130196614A1 (en) * 2012-01-29 2013-08-01 Crimepush Llc Mobile alert reporting and monitoring systems and methods
US20130300563A1 (en) * 2012-05-09 2013-11-14 Raymond Glaze Mobile incident reporting of organized retail crime

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10692359B2 (en) 2018-04-23 2020-06-23 Green Line Business Group Witness request and alert notification and tracking system
CN110674238A (en) * 2019-09-26 2020-01-10 四川科瑞软件有限责任公司 Toxicity prohibition information studying and judging system based on big data
CN110674238B (en) * 2019-09-26 2022-11-04 四川科瑞软件有限责任公司 Toxicity prohibition information studying and judging system based on big data
JP7360295B2 (en) 2019-10-03 2023-10-12 一般財団法人電力中央研究所 Information collection system, information collection method, and program

Also Published As

Publication number Publication date
ZA201805235B (en) 2019-06-26

Similar Documents

Publication Publication Date Title
US7280042B2 (en) Standoff security and real-time vendor verification system and apparatus
US20160286156A1 (en) System for managing information related to recordings from video/audio recording devices
US20070239473A1 (en) System and method for non-law enforcement entities to conduct checks using law enforcement restricted databases
CN102460463A (en) Personal safety system, method, and apparatus
WO2018045400A1 (en) Incident management & information capturing system
KR20120066393A (en) Vehicle video recording and servicing apparatus and method, apparatus and method acquiring local area information using the same
KR20110094393A (en) Automatic crackdown system of illegal vehicle and method thereof
KR101666531B1 (en) Patrol and vehicles management system
Ganz It's already public: why federal officers should not need warrants to use GPS vehicle tracking devices
CN114940140A (en) Proximity device detection, monitoring and reporting
US20070094720A1 (en) Security system
US20190272743A1 (en) Safe Stop Surveillance System
Dowdell You Are Here-Mapping the Boundaries of the Fourth Amendment with GPS Technology
US20170132735A1 (en) Enforcement services techniques
US20210233381A1 (en) Hierarchical architecture of the security system of controlled areas of the terrain
CN106960576A (en) The video-unit for making an inspection tour police car 360 degrees omnidirection
Hardin Uncovering the secrecy of stingrays: what every practitioner needs to know
KR200367191Y1 (en) system for regulating vehicles
KR100427668B1 (en) Police work assistance system and the method using for data communication
CN113192348A (en) Vehicle abnormity warning method and device and computer equipment
Geldenhuys Police and private security companies-partners against crime
CN205644964U (en) Be used for vehicle supervision protection location high in clouds discernment early warning network system
KR102317937B1 (en) System for monitoring car using blockchain
Gordon et al. License plate recognition technology: Innovation in law enforcement use
Sewpersad An Investigation of the Bombing of Automated Teller Machines (ATMs) with Intent to Steal Cash Contents: A Case Study from Gauteng

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17847701

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17847701

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17847701

Country of ref document: EP

Kind code of ref document: A1