http://www.atositchallenge.net/ideas/shift-ctrl-3

1. Project summary 100 words
Present here the use of the application, the benefits for the end­user, the business model, and
the technical approach.
Our aim is to simplify the auxiliary functions around volunteering at the Olympic Games, and
allow staffing coordinators and volunteers to spend their time focussing on the job at hand.
We provide functions to dynamically schedule volunteers by role, and a mechanism to
request training.
We propose a solution which introduces flexibility into the volunteering schedule, whilst
having the reassurance of real­time information: Shift+Ctrl – a multiplatform mobile
application designed to be used by volunteers and coordinators. It tracks and dynamically
allocates staff to scheduled events to ensure the smoothest experience for all.
Your project in 25 words 25 words
Describe the uniqueness of your app.
A single application encompassing all features required to effectively coordinate event
personnel providing easy mechanisms for communication, real­time tracking and training.
Demonstrator
300 words
If your team is selected in the pre­selection phase, you will have 3 months to develop your
project. 3 months is not long and we do not require you to develop the entire scope of your
project in this time frame. If you wish you can choose to focus on a sub part that will be relevant
enough to present your application and make a live demo of it. For example you could only
implement the one or two relevant use cases or have your application work with some static data
on your server. Describe here what you want to develop during the second phase (if pre
selected), and what you would present to the final jury.
The demonstrator will consist of prototypes for the Web Application and an Android app
covering the Event List and Event attendance use cases. We have included screenshots for the
Event List and Event Details screens as a part of our submission.
The Web Application will show functionality for event and volunteer profile management however
the event and volunteer data will be entered manually, rather than being imported from external
systems.
The Android app will show notifications via email and text message, and depending on team
capacity across the development phase, we would like to implement the Google Cloud
Messaging for the Push Notifications within the Android App.

2. Benefits for end­users
300 words
Describe here in more details what the application will be doing and in what way people are going
to use the application. You can include screenshots of what the final app will look like, and/or use
cases.
There are two groups of end users for Shift+Ctrl. The first group consists of the staffing
coordinators, while the second are the volunteers.
For coordinators, the benefits match those of a management tool. Shift+Ctrl allows
coordinators to quickly set and see how many volunteers are at each event, and takes
away the complexity of coordinating a large group of people. Through the dynamic
schedule, coordinators no longer need to struggle to find enough people to cover an event,
whilst the leader board assists in ensuring that less popular events are still adequately
staffed. The alert system notifies coordinators of any potential issues to allow them to stay
in control of the situation. The instant messaging interface allows them to rapidly
disseminate information to their entire team, as opposed to relaying information through
several points of weakness.
For volunteers, the benefits are plentiful. The DSS helps keep track of which part of the
stadiums they need to be at and provides guidance on how to get there. It also allows them
to quickly inform a staffing coordinator if they cannot make it to their position for any
reason, enabling someone else to cover them. Volunteers can request additional training
and enhance their skills. The leader board enables volunteers to partake in the competitive
atmosphere with their own games and monitor their performance. The ability to opt­in to
cover additional events is a fantastic way for volunteers to earn more points and make their
way to the top of the leader board, whilst making the most of the once­in­a­lifetime
experience at the Olympics. The instant messenger also allows volunteers to talk to one
another, and their coordinators.

3. Business model
300 words
Describe here in more detail what business model you foresee for your application. If you need
specific partnership (source of data, brands,..) please detail them here, describe also the
benefits these partners will gain from being your partner in the project.
The model for Shift+Ctrl is one of a hosted service. The infrastructure will be managed by
us, with clients using their app to login to the service. This will allow us to benefit from scale,
whilst benefiting the client by reducing the complexity of their processes.
Our clientele, which will initially consist of multi­stage event hosts such as the Olympics,
Wimbledon, and the FIFA World Cup, will be able to license Shift+Ctrl with a predefined
number of seats (or volunteer users) and will provide us with the data required for the
navigation tool. The client will have access to an unlimited number of administrator users,
and the ability to create normal user accounts up to the number of seats they have licensed.
There will be an option to purchase additional seats if required. End­users will be able to
download the Shift+Ctrl app at no cost, as valid login credentials created by a client
administrator will be required to use the service.
The initial target market of large events such as the Olympics is relatively niche.
Wimbledon is hosted annually, the Olympics are bi­annual, and the FIFA World Cup is held
once every four years. For this reason, we will be diversifying our target market to include
concerts, festivals, and even industrial applications; Shift+Ctrl can be deployed in any
environment where there is a dynamic workforce.
There are risks associated with a hosted solution and licensing; any technical issues or
outages could potentially affect all clients, and clients may be unwilling to take that risk and
may prefer to keep it in­house and so we will offer a white­label solutions to high­value
clients who wish to run the service themselves.

4. Technical approach 300 words
Describe the technical architecture / approach planned for your project. Include both the mobile
front end and the server back end. Detail what you will develop yourself, third party solutions and
other providers. Include the estimated workload for each sub­part of your project.
Shift+Ctrl adopts a Services Architecture hosted in the cloud for the server components.
The Notifications Process will use Google Cloud Messaging, Apple Push Notification
Service, or SQL Server Notifications Services. The Integration services are dependent on
the access methods and formats for data extraction from the Event Management and
Volunteer Vetting applications. Changes to the external applications are out­of­scope.
The Presentation Layer includes native smartphone apps for iOS, Android and Windows
Mobile. The apps read device sensor information (like GPS) and provide that to the
services layer. Users interact with native apps or a browser based web application for
more complex administration features. Messaging will utilise existing email and text
messaging servers.
Our development will adopt an Agile approach using Scrum and the tasks below are the
current Product backlog with estimates based on standard work days. Development tasks
may be run in parallel within the team and include unit and integration testing.
Our confidence level for the development of the following components is at 80%. Server
components including architecture and development for the service layer, dynamic
scheduling service and application data structures ­ 50 days. Web application for
application administration ­ 30 days.
Our confidence level for the development of the remaining components is at 60% due to
skills acquisition for the mobile platforms and their respective push services, and a lack of
knowledge on the existing applications for the integration services.
Integration Services architecture ­ 5 days
Data import from Events Management application ­ 5 days
Data import from Volunteer Vetting application ­ 5 days
Windows Mobile App & SQL Notification Services ­ 40 days
Android & Google Cloud Messaging ­ 40 days
iOS & Apple Push Notification Service ­ 50 days
The total development effort is estimated at 225 development days with a 70% confidence
level.