User
Profiles
Administration
Platform:
Super
Administrator (SA):
Creates
users
Administrates
catalog of emergency telephones
Administrates
values of points/rewards/medals
Administrates
catalogs of types/categories of reports
Administrates
users permissions/privileges for A & MO users
Administrates
and/or moderates reports
Administrates
official notifications
Administrates
location of police stations
Administrates
sponsored messages on the map
Administrates
catalogs for the city’s neighborhoods/zones
Administrates
app’s statistics/analytics from Apigee platform
Administrator
(A):
Administrates
users permissions/privileges for FM users
Administrates
and/or moderates reports
Administrates
official notifications
Administrates
location of police stations
Administrates
sponsored messages on the map
Administrates
catalogs for the city’s neighborhoods/zones
Administrates
app’s statistics/analytics from Apigee platform
Municipal
Official (MO):
Administrates
and/or moderates reports
Administrates
official notifications
Administrates
location of police stations
Administrates
sponsored messages on the map
Administrates
catalogs for the city’s neighborhoods/zones
Administrates
catalogs of types/categories of reports
App:
End
User (EU):
Creates
profile using Facebook, Twitter or Google accounts, or with his/her email
Starts
session by logging in with created profile.
Creates
report of a problem or shares idea
Takes picture or video and attaches to report
Chooses what social networks to share to (Facebook,
Twitter, G Plus)
Chooses exact location on the map
Chooses type of problem or idea
Adds description
Chooses whether to send as anonymous or not
Sees
existing reports and ideas organized by proximity to his/her area of interest
Views and engages with sponsored messages
Adds
users to his “friends” list
Earns
medals for accumulated points or specific actions taken.
Configures
his areas of geographical interest (i.e. home, work, school, etc.)
Configures
his profile
Links
his social network profiles/accounts for contact
Sees
closest police stations on the map
Sees
fellow users nearby
Sees
any users that have activated Panic Button
Can
contact local govt. (municipal) authorities using contact form
Can
configure contacts on Panic Button section (4 total)
Features
Following
is a brief detail of each type of usage based on the defined features for our
application, which have been designed for four (4) types of user, Super Admin,
Admin, Municipal Official and End User, on the Web and Android, iOS and
Blackberry mobile platforms.
Create
Users: The SA user will
create users from a web-based admin platform or control panel, in the following
fields: name, user, email, password, date of birth, type of user (Admin (A) or
Municipal Official (MO)).
Problem
Report: The SA and A users
will be able to update the status of reported problems and ideas by the End
Users (EU). The goal of this is to communicate with the community of users
giving them feedback about the problems and ideas reported or generated by
them.
To
update a report/idea, the SA & A users will click on any of the statuses to
the right of the shown report on a list.
The
following are the available statuses of reports:
Grey:
New
Green:
Resolved
Yellow:
In process
Red:
Overdue (time depends on type of Problem)
Official
notifications: SA, A and MO users will
be able to send push notifications to individual or groups of EU based on the
geographical areas of interest previously defined by the EU.
Creation
of police stations: SA and A users will be able to add to the map the location of police
stations, as well as their contact info (phone, address) so they can be seen by
EU and if needed, they are able to dial direct to the nearest station.
Sponsored
messages: SA and A users will
administrate the sponsored messages displayed as small objects on the map,
configure their exact location, awarded points and rewards to the EUs.
Sponsored
messages will be limited to a quantity of 4 max. at a time at any given map
screen, and will rotate to make sure all get equal amount of exposure.
Catalog
of city neighborhoods or zones: The
SA and A users will administrate a list of neighborhoods and/or city-defined
zones, and the EU will be able to add themselves to these in the profile
section.
Catalog
of Reports and Ideas: SA and A
users will administrate a catalog of the types of reports the EU will choose
from when reporting, and their detailed descriptions.
Administration
of values of points and rewards for engagement: SA users will administrate the points and rewards system
that will give credit to EUs based on their engagement with reporting,
generating ideas, and sponsored messages displayed as “treasures” on the map.
The
following are the actions which will earn points for EUs:
- Report
a problem
- Validate
or Vote on problem
- Invite/Add
friends
- Complete
the “optional” fields in the profile section
- Engage
with sponsored messages (treasures)
- Solved
problems
- Ideas
implemented
Apigee
analytics/usage reporting: SA will have
access to Apigee platform to be able to configure and generate reports with all
the data generated.
Emergency
phone numbers catalog: SA user will
administrate a list of official emergency contact phone numbers present in the
Panic Button.
Authenticate
user session: The EUs will be able to authenticate session using their social network
accounts (Facebook, Twitter, and Google Plus) and will allow them to import
their data to our system’s databases. They will also be able to create their
account in our platform manually, using their email.
Report
a problem/Share an idea: The EU will be able to report problems in the city or share ideas for
improving the city. The apps will allow them to attach an image that allows the
local authorities to better locate the reported incident or idea and send a
more detailed written description. The location will be automatically geo-located
on the map and the EU will also have the ability to correct the location to
make it more exact.
Anonymous
reporting: The EU will be able to report problems and share ideas anonymously,
activating this option in the last step before sending it. If they choose this
option, sharing to their social network profiles will be automatically
deactivated, if sharing was previously configured.
List
of reported problems and ideas: The EU will see reported problems and ideas by both
themselves or others, on lists, which will be clearly marked as “new”, “in
process”, “settled” or “overdue”. They will be able to apply geo-location
filters according to their areas of interest, if they so choose to.
Engagement
with sponsored messages: The EU will
be able to engage sponsored messages and will earn points and other rewards for
doing so.
Adding
users: The EU will be able to send friend requests and invites to join the
community. When those requests and/or invites are accepted, both EUs will be
able to see each other’s public profile.
The
EUs profiles will have privacy restrictions, and will only publicly display the
username, problems reported and ideas shared, points and rewards awarded, and
the profile picture or avatar.
Friend
requests or invites will be able to be sent by first importing the EUs friends
from Facebook, Twitter and/or Google Plus, or by accessing the mobile phones
contact list.
Medals/Prizes:
The end user will
be able to earn points and medals of commendation for reports and ideas shared,
as well as from engagement with sponsored messages. These will be available to
be seen on his public profile.
Areas
of interest. The EUs will be able to define three (3) geographical areas of interest
to be able to receive official push notifications and to prioritize other users
reports and ideas in a radius from closest to farthest. For example, home,
work, school, etc.
Profile
settings: The EUs will be able to configure his profile at any given moment after
they have created it. All fields can be edited and updated.
Police
stations: The EUs will be able to
see police stations previously added by local authorities on the control panel,
both on the map and on a list, and will be able to dial directly the chosen
station’s phone number(s) from the mobile apps.
Users
nearby: The EUs will see on
the map other nearby connected EUs, allowing them engagement options like
sending friend requests and viewing their limited public profile.
If
one of the EUs on the map on screen has activated the Panic Button, the rest of
the content on the screen (i.e. sponsored messages) will temporarily disappear
to capture the attention of all users, allowing them to call for help if they
so choose.
Panic
Button: The EUs will be able
to activate an SOS option from the mobile apps, which will allow them to send
to a previously defined list of personal contacts, a text message. It will also
post a predefined SOS public message on their social network profiles, so
friends and family members will be able to assist them either personally or by
contacting the police or other authorities. On social networks, it will also
post a location on the map.
On
the Android app, it will send the SMS text messages every 300 seconds. This
can’t be replicated on the iOS platform because it won’t allow it. The idea
behind this is so the EU in trouble can be traced. The troubled EU’s status on
the map changes as does their icon/avatar, to striking colors and image, to
catch everyone’s attention. After 5 minutes, the icon returns to normal.
All
contacts in the Panic Button section can be configured, as well as other
quick-dial contacts that will appear around the main Panic Button.
A
shortcut to the Panic Button can be created and added to the mobile phone’s
“desktop” area for faster access as a stand-alone app.
Business Process Model and Notation
Detailed next is the BPMN related to the features described previously.
Sign Up Users
Objective: To allow end users to sign up using the app.
Actors:
End Users (EU)
Flow description: The flow is started by the user that wants to become the EU of the app. The user downloads and installs the app from Google Play or the App Store. When launched, the app displays an authentication screen, asking the user if he has previously signed up for the service. If the user is not registered, he proceeds to create an account using the sign up form in the app. Once the system has issued credentials for the user, it allows him to sign up using social networks or the manual sign up mechanism.
If the users chooses to sign up using a social network, he's allowed to choose from Twitter, Facebook or Google Plus. Once the account has been created using a social network, a form is opened to complete the registration in the system. If the user chooses to use the manual sign up mechanism, a form is opened to allow him to generate his credentials. Independently from which way the user chooses, it's automatically registered and the account creation service is finalized, immediately letting the user now that the account has been created.
The EU is automatically logged in and the account creation points are assigned to his account.
Detailed next is the Business Process Model and Notation process:
Login Process
Objective: Allowing the EU to log into the app.
Actors:
End Users (EU)
Process description: The process is started by the EU opening the app, which saved login details of the user to allow quick access, making the experience for the user easier. If the credentials for the user are valid, the EU accesses the main screen of the app, winning points for using the app.
If the session has expired, the login screen is displayed and starts the authentication process, showing the end user the login options, social networks or registered account. After choosing any login option, the system verifies that the account is valid. If the account is valid, the user is assigned points for authenticating and is taken to the main screen.
If the system cannot find the login details of the user, it allows him to try to log in again.
If the user doesn't have an account, the system allows him to create an account using the "Sign Up Users" process.
Detailed next is the Business Process Model and Notation process:
Add Users
Objetive: Allowing the EU to add other users or contacts as friends within the app to see information on their profiles and other details.
Actors:
The End User (EU-1) the sends the request.
The End User (EU-2) that accepts or reject the request.
Process description: The process is started by the EU that sends the request, that wishes to add another user as a friend, who can use the app to find contacts that are nearby or adds them from the contact picker within the app.
If the user chooses to add another user based on his location, the EU-1 only has to tap on the EU that he wishes to add and the invite is sent. A list is automatically generated of all the requests that the user has sent. The app initiates the process to add users by sending the invite to EU-2, who receives the request via a dialog box and is stored automatically in the received requests section. When the invitation is accepted, EU-1 and EU-2 automatically are given points, and EU-1 is notified that EU-2 has accepted his request, ending the process satisfactorily. When the request is denied, the process ends automatically.
If the EU-1 chooses to add users from the contact picker, he's allowed to choose from registered users that used their social networks or contacts that are stored on his phone. If he decides to add users from social networks, the app compares existing users on social networks to the users registered in the app and verifies which one are already active contacts of EU-1 in the app. Once the comparison is done, a list of eligible users is generated and the process of adding users is started to send a request to EU-2, who receives the request via a dialog box and is stored automatically in the received requests section. When the invitation is accepted, EU-1 and EU-2 automatically are given points, and EU-1 is notified that EU-2 has accepted his request, ending the process satisfactorily. When the request is denied, the process ends automatically.
If EU-2 decides to add registered users using the contacts on his phone, the app procedes to cross check the contacts on the phone to verify if they exist on the user database. Once the process is finalized, the users that matched the database are shown and EU-1 selects from the auto-generated list, the users that he wishes to add. When he selects the user he wants to add, the app initiates the process to add users by sending the invite to EU-2, who receives the request via a dialog box and is stored automatically in the received requests section. When the invitation is accepted, EU-1 and EU-2 automatically are given points, and EU-1 is notified that EU-2 has accepted his request, ending the process satisfactorily. When the request is denied, the process ends automatically.
Detailed next is the Business Process Model and Notation process:
Report Incidents
Objetive: To allow the EU to report incidentes en his community, creating a report directed to the MO for its timely resolution.
Actors:
End User (EU)
Municipal Official (MO)
Process Description: The process is started by the EU when he visualizes an incident, then decides to report it by filling the fields in the form located in the reporting section in the app. The system allows the EU to attach an image that shows illustrates the incident report. The report is sent and the EU Report service is started, and at the same time points are given to the user for sending the report.
The report is not published automatically, it goes through a filter that's chekced by the MO, who notifies of the report to the entity responsible and updated the status of the report as created, making them visible to all EU.
The MO updates the status and follows up on all incidents as long as it's needed. The incidents are shown in a traffic light manner that allows the visualization and quick look of all reports sent by the EU.
The status of the reports can be:
Green: Report resolved.
Yellow: Report in process of being resolved.
Red: Report with more than 30 days of being submitted.
Grey: New report.
If the report is updated as resolved, the EU is given points because the municipal district has successfully solved an incident reported by him.
If the report already exists and had been validated by the MO as existing in any status (green, yellow, or red), he validates the user's report and gives him points for the activity.
Detailed next is the Business Process Model and Notation process:
Visualizing incident reports
Objective: To allow the EU to check all reports based on areas of interest.
Actors:
End User (EU)
Process description: The process is started by the EU by opening the report screen, the system then filters the reports based on the location, reports by the same EU, and his user profile to determine that areas of interest for this user in relation to reports by other users. The process is ended by the visualization of of a list of reports related to the areas of interest for the EU.
Detailed next is the Business Process Model and Notation process:
Visualizing police stations
Objective: To allow the EU to visualize the closest police stations.
Actors:
End User (EU)
Process description: The process is started by the EU when he opens the map, the system filters all the police stations and shows those closes to the EU in a list including the contact information for each and are presented on the map. The process ends by showing the police stations closet to the location of the EU.
Detailed next is the Business Process Model and Notation process:
Creating sponsored messages
Objective: To show sponsored messages and notifications from officials in the map to be seen by all EU.
Actors:
Super Administrador (SA)
Administrador (A)
Municipal Officer (MO)
Process description: The process is started by the SA, A or MO by opening the map events in the admin panel of the app using a web browser.
If the user has the permissions needed, he can choose between sponsored messages and the official notifications, allowing him to create, update or delete any message or notification in the app.
Each sponsored message or notification a value assigned, being zero "0" the default value that can be updated at any time.
A form is generated for sponsored messages or notifications, for which you also have to set a location in the map, icon, etc.
Once the sponsored message or notification has been created, the EU can see it reflected on the map.
Detailed next is the Business Process Model and Notation process:
Catalog Administration
Objective: To allow the administration of the system catalogs.
Actors:
Administrador (A)
Super Administrador (SA)
Municipal Officer (MO)
Process description: The process is started by the A, SA or MO by opening the catalog section, selecting any of the following catalogs that he wished to manage: Reports, neighborhoods and districts, Incidents, Police stations, Emergency Numbers, and Sponsors.
The catalog service is started, allowing the user to update, delete or create new elements in the catalog, and the changes are saved in the platform and ends the process.
Detailed next is the Business Process Model and Notation process:
Creating and managing users
Objective: To allow the creating and managing of users in the admin panel.
Actors:
Administrador (A)
Super Administrador (SA)
Process description: The process is started by the A or SA by opening the user section, selecting if he wishes to create or manage users. When creating users, the system shows a list of all the users created, the user completes the form and generates the user.
If the user decides to manage the account of an existing user, he had to select "update users" to visualize a list of all users created, and allowing him to delete users or update their description fields. The user selects the user to modify and ends the process.
Detailed next is the Business Process Model and Notation process:
Video Presentation
If your project has been nominated for global awards, please embed here your 3-minute Youtube presentation. (Select "Insert" --> "Youtube").
Global Urban Datafest. Images by