Difference between revisions of "AOD - Assistance on Demand Infrastructure"
|Line 55:||Line 55:|
= Documentation/FAQs =
= Documentation/FAQs =
Example use scenarios of AoD can be found here: [[
Example use scenarios of AoDcan be found here: [[P4A_WP205_D205-1_v2_20141217_WOAnnexII.pdf]]
= Related/Alternative Tools =
= Related/Alternative Tools =
Revision as of 18:15, 26 January 2015
The Assistance on Demand (AoD) Services infrastructure is a generic open-source infrastructure that enables the rapid deployment of new machine/human/crowd-based assistance services on demand by allowing service suppliers to easily register their assistance service and individuals to seek assistance in an organized fashion from a set of predefined sources based on type of need, quality of service desired, and other personal preference at the moment.
The AoD, once instantiated, will offer a set of unique features since it will:
- allows individuals to set up services that seek assistance in an organized fashion from a set of predefined sources based on the type of need, the type (human or machine based) and quality of the required service, and other personal preferences,
- allows application developers and service providers to easily register the services they offer (or set up new ones), which can be of any type e.g. machine, human, crowd-based assistance services,
- supports multiple charging models and enables payment for all services through the associated P4A payment system, including the support of micropayment and micro-funding schemes,
- enables the set up of user-defined network of assistance services supports the set up of multi-modal technical support including both human based and machine-based (e.g. text, voice or video-based) AoD
- supports set up of QoS-price negotiation and “try harder” approaches
- offers zero/default configuration mode options for efficiently supporting non professional with low digital literacy users to set up AoD services, while allowing for configuring the service to fit the user needs
It will allow the developers and other stakeholders interested in offering AoD services to:
- promote and sell their services bringing them closer to large audiences, relieving them from deploying their own charging/payment infrastructures
- discover new user needs and undertake the development of new services.
The target users of the AoD infrastructure are:
- service providers / developers (SP) who want to offer
- a bundle of services for a specific target group of service consumers; such SP instantiates the AoD and acts as mediator between end-users and service providers and can be either a company or any community/organisation,
- individual service providers trying to sell through a specific P4A AoD instance their service avoiding to set up their own infrastructure to reach customers
- individual end users/ service consumers.
For the SP/developers, the P4A AoD infrastructure added value stems from the fact that it:
- consists an access point to a very wide userbasesince it enables the set up of assistance services of any type (machine or human based) for any type of disability/literacy,
- offers security and payment functionality through interconnection to the relevant systems developed in P4A, allowing the developers to concentrate on the functionality of the service they develop.
For the individual end users (service consumers), the added value stems from the fact that it offers:
- a great variety of service and an easy personalised user interface that facilitates searching for services in an intelligent multi-criteria manner
- the opportunity to set up a network of services for the people they take care of (friends, family members, e.t.c.). For example, a lady can choose specific services for housekeeping, nurses, doctors and other daily life tasks for her parents that are incapable of taking care of these tasks.
- improved ease of use through multi-modal technical support
- easy billing and charging accumulating micro-charges and forming a monthly bill
- micro-funding opportunities and definition of services that are desired but not available.
Currently there is no generic open source infrastructure that can support the set up of several types of machine- and human- based AoD services, notably for non-developers and family members. As such, the P4A AoD can be very valuable for service consumers of AoD, as well as individuals and organisations wanting to offer AoD services.
The AoD platform aspires to be the entry point for numerous assistance services just like Google Search platform is the entry point for whatever we look for in the internet. As such, it can attract a very large group of users. Consider, for example, consumers (e.g. hard of hearing persons) who are in need of subtitling services. Once the request from a consumer for receiving a subtitling service is received, the AoD infrastructure will expose the registered subtitling service(s) to the consumers who need it; the services can be machine-enabled (automatic) or offered by humans. This is one of the criteria that the service listing functionality of the AoD infrastructure will use to rank the services that will be presented to the consumer – other criteria under examination are the cost of the service, the quality of the services as assessed by other consumers, etc. Now, let’s suppose that the consumer selects an automated subtitling service but after using it for a short period, she is not satisfied with the quality of service. The AoD infrastructure will enable her to push the “try harder’ button and be presented with similar services which are of higher quality but also higher cost (e.g. services offered by humans).
On the other hand, there are large numbers of developers that can develop very interesting and effective assistance applications/services, who, however, are not fully aware of the consumers’ needs or do not want to spend too much time in building a complete framework that takes care of payment issues and security issues. The AoD infrastructure will facilitate the set up of AoD services for such developers by offering them, e.g., payment and security components that are easy-to-integrate in existing or newly built services, thus lowering the delivery cost of the service. Moreover, the AoD infrastructure, by interconnecting to the micro-payment and biding components, will bring developers closer to what consumers want, request and are willing to micro-fund.
AoD can be easily instantiated by organisations to help their members easily identify and pursue assistance services (e.g. organisation addressing people with all or specific types of disabilities). It can also be used by associations of service suppliers (e.g. developers or volunteers or non-IT expert service suppliers) to approach their audience.
As the P4A architecture and requirements are ongoing, a final decision regarding the technologies that will be used has not been reached. The technologies under consideration are:
(a) Linux (e.g. Ubuntu, CentOS) as the main OS supporting the AoD services, Wirecloud as the main user interface enabler
(c) Django framework, Apache Web Server, MySQL, MongoDB for the backend services, BootStrap, JQuery for the UI development, Eclipse/Netbeans as the development environments, Git as the main source control system, Jenkins as build service provider, SonarCube as code quality manager/monitor.
The licences accompanying the AoD software contain re-distribution friendly directives (Apache, BSD etc.). None of them is proprietary and/or of limited (re)use.
Status, Known Issues & Planned Work
The user and system requirements of the AoD have been captured. The AoD implementation architecture will be finalised by end of January 2015. The implementation of the AoD has started.
Example use scenarios of AoDcan be found here: RTENOTITLE
Currently, there are platforms/sites offering quite flexible service search to the users. However, they are limited to either software or human based services and focused on specific application areas (e.g. health, training, babysitting).