Traffic Incident Management

Inspiration

The need for faster jotting down of information on any incident, its timely action, faster retrieval of the existing incident related information and better communication between the patrol officers and the doctors inspired to build this application.

What it does

The application has been designed for 3 roles: Patrol Officer, Senior Officer, Doctor.

Patrol Officer

1. The patrol officer can create an incident of type: Accident, Non - Compliance, Theft, Over Speeding.
2. When creating an incident, he can add the offender and the casualties if any.
3. Different reports which highlight the following are provided for better handling:
   • All incidents reported by the officer grouped by the status.
   • All the incidents occurring in his patrol area grouped by incident type.
   • ER helplines of all the hospitals.
   • All casualties reported by the officer and the ones which are stable to be interrogated.
4. A QR code is provided for immediate fine clearance on the offender if any.

Senior Officer

1. The senior officer can also create incident, add casualties or traffic offenders.
2. The senior officer gets to view the following reports:
   • All incidents reported till now grouped by the status.
   • Patrol area wise incident grouping.
   • ER helplines of all the hospitals.
   • All casualties who are stable to be interrogated.
3. A QR code is provided for immediate fine clearance on the offender if any.

Doctor

1. A doctor will be able to view and edit the casualties he/she is attending and view the related incidents.
2. Once the doctor marks the status of the casualty as 'Stable', an email notification is sent to the related patrol officer updating the same.

Additional feature

• Whenever an incident is created, a pipeline is used to post a relevant message in slack channel traffic-mgmt in workspace Mangalore Traffic Incident Updates.

How we built it

• Analysing the use case and coming up with the tables needed for the application and the relationship between them.
• Adding in mocked data to these tables.
• Adding roles: Patrol Officer, Senior Officer, Doctor and users with proper permissions.
• Creating different reports for the 3 roles.
• Creating dashboards for the 3 roles.
• Use of email notification to update the officer when a casualty reported by him is ready to be interrogated.
• Use of pipeline to post message in a slack channel whenever an incident is reported.

Challenges we ran into

• Creating personalised report based on user login. This was overcome by understanding the filtering available in the report settings and use of mocked users, user data type in the tables.
• Use of pipelines to post messages in slack channel.

Accomplishments that we're proud of

• Understanding of pipelines and how to use it.
• The ability to understand use case, come up with tables, relationships and the application itself using quickbase.

What we learned

In addition to the quickbase features used in the application, learnt about app variables, quickbase actions, different types of reports that can be created, the way relationship works in quickbase.

What's next for Traffic Incident Management

• A way to communicate with traffic offenders on any updates on the cases against them.
• In case of vehicle theft, integrating the use of fastag or vehicle registration number and the Toll records to get the vehicle location.

Built With

• slack