Intranets 2014, Mobility for Queensland Police
- 1. SPOT THE DANGEROUS CRIMINAL Delivering the right mobile information quickly Cornè Grotius 21 May 2014
- 2. What is it like to be a police officer? 1
- 3. 3 PERCEPTION
- 4. 4 REALITY
- 5. 5 THE REALITY OF RADIO “Operator can you check car registration 456HAA for me?” “Hang on, you are number 8 in the queue” “No, 456HAA … anything?” “Sorry, was that 496 HDA?” “The car checks out. The owner is one Derek Trotter, male 35 yrs old with brown hair, wanted for questioning” “He says Derek is his brother, he left his license at home … without a picture, I had to let him go”
- 6. 6 WHAT IF GOOGLE HAD AN OPERATOR?
- 8. 8 SOLUTION ARCHITECTURE BEFORE MOBILITY T Q C Queue
- 9. 9 OPPORTUNITY 1) REMOVE THE OPERATOR T Q C
- 10. 10 REMOVE THE OPERATOR – SEARCH ON DEMAND Before: • Talk to an operator • Wait in a queue • Search databases only from the office/station After: • Direct access • Immediate response • Search from anywhere
- 11. 11 OPPORTUNITY 2) SEARCH ONCE Q C T
- 12. 12 SEARCH ONCE - CLICK THROUGH RESULTS BEFORE • Search for vehicle in QPRIME • Search for driver in Transport • Search for driver history in QPRIME AFTER • Search for vehicle • Returns information related to the vehicle from all available data sources
- 13. 13 OPPORTUNITY 3) CAPTURE INFORMATION IN FIELD QPRIME
- 14. 14 CAPTURE NOW - NOT AT THE STATION BEFORE • Written notes • … including descriptions • Enter information at the station • Delays in information sharing AFTER • Capture new info on the spot • .. Including photos • Information shared instantaneously
- 15. 15 RADIO VS MOBILE Before Now Radio/Operator Device Talk/Listen See/Read Queue/Wait… Immediate response See part of the picture See the full picture Notebook/Retype Capture information at the source Delayed information sharing Information shared immediately
- 17. 17 DESIGN CHALLENGE | SIMPLIFY THE SEARCH
- 18. 18 DESIGN VISION • Single Search Bar • Simple type selection • Always visible
- 19. 19 USER INTERFACE I want to search for a person… Step 1: Select the person icon Step 2: Type the search criteria into the field Stewart Jarrod 37
- 20. 20 OUTCOMES BEFORE • Open QPRIME • Navigate to Person Search • Complete multiple fields with search criteria • Search >> • Open CrimTrac and repeat AFTER • Select person type • Type all the details into a single field • Search >>
- 21. 21 DESIGN CHALLENGE | HIGHLIGHT CRITICAL INFORMATION Who is this person? Can they hurt me? Do I need to take any action?
- 22. 22 DESIGN VISION Wanted for questioning Previous firearms offences … Weapons license holder … Expired license …
- 23. 23 USER INTERFACE • Officer alerted with a red Person flag • User can drill down further into the person’s details to review flag details Demonstrating alerts using flags – Search for a vehicle
- 24. 24 OUTCOMES BEFORE • Search for a vehicle in QPRIME • Receive a list of matches • Open every record to inspect • Search for the registered owner • Open matching record > Person is dangerous! AFTER • Search for a vehicle • Flag: Registered owner is dangerous!
- 25. 25 DESIGN CHALLENGE | MINIMIZE DATA RE-ENTRY “Never rekey. Reuse” Q T C DerekFirst name Last name Trotter DerekFirst name Last name Trotter 78541254Drivers Licencse no.
- 27. 27 USER INTERFACE Navigate to linked records Only had to type the information once and was able to navigate to related records by simply linking to them
- 28. 28 OUTCOMES BEFORE • Search for a person in QPRIME • Rekey in Queensland Transport database • Rekey in CrimTrac AFTER • Search for a person in QPRIME • Link to related vehicle records • Link to drivers license information in Queensland Transport database • Link to CrimTrac search results for the person
- 29. 29 DESIGN CHALLENGE | CAPTURE NEW INFORMATION EASILY Less typing … … More Swiping
- 30. 30 DESIGN VISION
- 31. 31 USER INTERFACE Creating a Street Check Occurrence • To add the current record to the Street Check, use the context menu The “Green man” indicator shows that a street check is currently in progress • Users can tap on the “Green man” on the navigation bar to finalise the Street Check • On the Street Check screen we can see the entities that were added. The officer can now complete the remaining information and Submit the record
- 32. 32 OUTCOMES BEFORE • Record details in a notebook • Enter details into QPRIME at the station • Multiple searches and rekeying of information to complete entry AFTER • Search for a record • “Add to cart” • Link to or search for other records • “Add to cart” • “Checkout” to complete record entry
- 34. 34 34 iOS Device The user must learn how each system work The user must know what information is available in each system The user must conduct separate searches on each system The user must combine and interpret information from each system Users must learn, understand and work across all the different systems “WE WANT WHAT WE HAVE ON OUR DESKTOPS, ONLY MOBILE
- 35. 35 35 iOS Device 1. Developed a single mobile app 2. Created a common data model 3. Inserted a web service layer - The user doesn't need to know about the back end systems - The user doesn't need to know what information is stored where - The user’s only concern is the device and single interface WHAT CHANGES DID WE MAKE TO THE ARCHITECTURE?
- 36. 36 36 HOW DID THE NEW ARCHITECTURE SUPPORT OUR DESIGN GOALS? Search once? Minimize navigation? Present the required information quickly? - Who is this person? - Can they hurt me? - Do I need to take any action? Before After
- 37. User Feedback5
- 38. 38 FEEDBACK FROM OUR USERS? “On a quick note, the I-pad mini’s are excellent. As an example, because of Q-Lite we were able to identify an offender wanted for almost 3 years on two warrants (6 offences), who had managed to create a new identity through Queensland Transport. He was only found due to the associate function on a passenger in the vehicle with him and the ease of accessing QPRIME photos. In the 3 years he was wanted, he had come into Police contact several times under his new identity and remained undetected.”
- 39. 39 FEEDBACK FROM OUR USERS? “Only last week out here at Longreach we were conducting patrols of the Highway between Longreach and Ilfracombe. This is an area that has many radio black-spots. At about 11:30pm we intercepted a vehicle containing three occupants. Two of which provided false names and we were able to verify this using the (mobile device) to check on scene. As a result of this intercept, all three persons were arrested and identified as either wanted for questioning, wanted on bail act warrants or wanted on return to prison warrant. About seven fresh charges were also laid. It also should be noted that the person wanted on the return to prison warrant had been actively evading or running from Police for some five months. ”
- 40. 40 FEEDBACK FROM OUR USERS? “Friday and Saturday night shift completed and what a difference the iPad made! Often on these nights it's difficult to even get on the radio, and even when you do you are often 6th in queue looking at a substantial wait. In the past you may have to give up on checking only to return to station later to find they were wanted. The ability to conduct my own checks immediately allowed me to be far more productive not to mention the fact that it appears far more professional than making Joe Citizen wait 10 minutes just to check his licence. The only problem is that I am now the team inquiries office as everyone has worked out that it's far quicker to do checks with me than through inquiries.”
- 41. 41 FEEDBACK FROM OUR USERS? “I am a full time motorcycle rider. The device is fantastic and is a great step forward for the QPS. Being on the bike I am often working one up. We all know the dramas with overloading of the enquiry radio channel. It is not good to be standing on the side of the road with a high risk suspect and be told you are fifth in the queue. Many times I have released persons prior to doing the necessary checks because of the delays on the enquiry channel. With Qlite that information is readily available in seconds.”
- 42. “This is the most exciting thing I have seen in my entire policing career” Paul Stewart, Assistant Commissioner, 30 years in the field
Editor's Notes
- #2: Opportunity New tool for Front line officers What is it? Information Fundamental change to frontline policing
- #3: So what is like to be a police officer? What do police officers do on a day to day basis? And what are police information systems like?
- #4: Hollywood: Detectives, Forensic experts and good looking Car chases, murder investigations, criminal psycologists and forensic suitcase is standard issue Information systems: Cutting edge, integrated, colourful user interfaces
- #5: Reality: Lots of organisational units. Front line police largest RBT > Issue infringements > Break ins > Taser? Reqs > Priority one: Officer safety IT systems > Old, legacy, disparate systems > technologies, location, owners > Limited integration Biggest issue: Interface > Radio
- #6: Limited operators Miscommunication No Photos Frustration / Risk
- #7: Useful? Use often? Reliable with middle man? Large info sets? Image searches?
- #8: Sold on need for mobility? What opportunities does mobility provide?
- #9: Before we get there – what did the solution look like before? Queue Verbal request Search Different systems Different interfaces Multiple – rekey or copy / paste Interpret Verbal relay
- #10: First – obvious – remove operator
- #11: The benefits here are fairly obvious: No middle man – direct access No queue – instant Search from anywhere
- #12: One device but still multiple search interfaces or apps for back end systems Search all systems at once Use web services
- #13: Search for a vehicle: QPRIME Driver: TMR Driver: QPRIME Now: Search for a vehicle
- #14: Not only get info but also capture information Simpler process – capture information at the source! Better DQ
- #15: Notebook > Station > Rekey Delays More information (descriptions etc) Device Some info already there Photos Immediate
- #16: Summary: Then Radio / Operator Now Device Then Talk / Listen Now See / Read Then Queue / Wait… Now Immediate response Then See part of the picture Now See the full picture Then Notebook / Retype Now Capture information at the source Then Delayed information sharing Now Information shared immediately
- #18: Before how: Where? What? How? Multiple field Difficulty navigating on little screens Other jurisdictions kept multiple field approach
- #19: Single Search Box Client referred to as “Google like” Single string – textbox have smarts to interpret and break it up Always visible Type selection
- #21: Before: Multi field Repeat other systems Now Single field > Search
- #22: Critical Officer Safety!!!! 3 Qs
- #23: Interpret not only that record but also related records Assign risk according to business rules Display flags
- #24: So we start off by searching for a vehicle.
- #26: Time Situational awareness Never rekey Also related information (or deduced)
- #27: User and applications view Had to be changed Disregard location
- #28: Search for a person, Barend Nothdurft No photo CrimTrac > Aliases Navigate to the Transport database record for photos The user only had to type the information once and was able to navigate between records afterwards
- #29: Search > Rekey > Rekey Search > Link to > Link to
- #30: Reduce keying information – small screens etc. Use the device features What? Street check – explain Type of event (middle of the triangle)
- #31: Use shopping cart model Add to > Add to > Check out
- #32: Show demo Talk about complexities of adding from other systems
- #33: Before Record Rekey Search multiple systems Now: Add to cart
- #35: We want what we have on our desktops but only mobile REQS: Search once Minimize navigation Present the required information quickly: Who is this person? Can they hurt me? Do I need to take any action?
- #36: Single app Single simple information model Web service layer The user no longer needed to know what back end systems existed. They didn’t need to know what information was available from each system. Add systems without user’s knowledge The user’s area of concern became much smaller.