Incident response manager

By Jack Lamyman, Alex Volley, Joseph Goodley and

Tom Robertson

Who?

Members of an emergency agencies (councils ect.)

What? For use when areas are under threat from emergencies

When? 24/7, all year round

Where?In the ‘agencies’ constituency

Why?Easier way of communicating between team members, easier

for teams to stay updated on situations.

Problem

o Lack of commutation between members of councils

o Lack of communications between agencies that can help in certain situations

o People being kept out of ‘the loop’ of situations

o Loss of ‘logs’ with important information or miss logging of information

How can we address emergencies with efficiency and speed?

Incident managers couldn’t always contact other team members

The team members at the bottom of the list would be told last

Team members couldn’t contact other agencies (homeless agencies, emergency food agencies) during incidents

Mini Elevator Pitch

My team, Penguin People, is developing a web application to help councils and other agencies so that communication can be improved within incident teams ,using an easy to use, simple app making it easy for team members to solve problems much faster.

User Profiles

Similar products My council service UK & IRELANDThis app is used by the public to contact their local council, the public can report problems to the council and upload images to the app. The council have a choice of creating or deleting incidents in the app. As you can see, the image bellow shows the front of the app, which can be compared to our app. This doesn't quite work for our app, since it is open to the public and doesn’t have a login system.

Incident ReportingThis app, again, is for reporting incidents via an app, although it is slightly different as it is more used for reporting problems in the work place. Because it is more business based than council based, it wouldn't work with what were looking for, especially on a larger scale incident with a lot of members working towards the incident.

Similar products

This app will be mostly used for the members of a council team which need to contact each other during a major incident. The app will have an ‘incident feed’ which shows a feed with all the members of a team

in, they can enter a post into the feed, so that other can see it. The app will also hold the contact information for each user, so at the touch of

a button, they can be called.

The main user of this app will be incident teams that have login details for the app.

flowchart

Login page

This screen will be for everyone to log into the app. It only requires a login and password to get in which will be handed out to the people that require it.It is displayed in a simple manner because nothing else needs to be displayed as all information will be shown once a user is logged in.

incident page

When logging in, the user will be taken straight to the live feed. It contains a list of all the items in the live feed and has two states for each item. Active or Inactive, a filled in square means it is active and unfilled is inactive. If a user clicks on the item then they will be taken into more details about the incident

Contact page

If the user slides the item to the left then two more options will be available, one for contacts such as the active managers and one for the memo. If the person choose contacts then it will show any active managers and the person may contact any one displayed. The memo is used for writing in information in case anything needs to be recorded.

Feasibility

The method that will be used to reached the goals that we have set for ourselves will be to make sure that we do enough testing and also

receive enough feedback from consumers to allows us to be absolute certain the project will be a success after release. It is important that we

do this and do as much testing on the application as we can so we can reduce the amount of bugs that may be on there and even get rid of all

of them so that the final product that will get released will be to the expectations of the employer. It is also important that we record all of

the bugs that are found in some kind of testing plan, this shall hold all of the information about what we are currently testing and how we have fixed or come up with solutions to older problems or bugs that we may

have found.

This application Is aimed at the N.E. Lincs council. They requested an

app that would be easy to use and simple to look at, yet do a multitude of things, but mostly be used for reporting and sharing

things about incidents within the application.

Marketing strategy

Our marketing strategy is word-of-mouth; we will use this strategy to help our deliverable reach its full potential and maybe reach the point of a national product, used by other companies other than the one were creating it for. We will encourage our users to suggest our app, for its purpose , to other councils and agencies. This is a very effective form of business since most people like to talk about positive things. We could also rely on the media, if it gains good reviews, to write something about our app. it is also effective because it is free, as you don’t' pay your users to give you a good review of your product.

flowcharts

The structure chart that I have shown above is a basic concept structure chart of navigation hat will be used when working round 3 of the pages on the applications. The three pages that I have primarily looked into is the Team Members, Incidents and Map Page. The team members page is where there will be a full list of each member on the incident team and also clicking them will give a pop up that allows you to contact them using contact details that they have previously provided. The incidents page is where you are able to create a new incident and also view both currently active and closed incidents. Both of which you are allows you access important information that you might otherwise struggle to get hold of or may have to spend ages searching for.