D205.2 Consumer/Family/ Professional configurable AOD

Ecosystem infrastructure for smart and personalised inclusion and PROSPERITY for ALL stakeholders

D205.2 Consumer/Family/ Professional configurable AOD

Project Acronym Prosperity4All Grant Agreement number FP7-610510

Deliverable number D205.2 Work package number WP205

Work package title Assistance on Demand Services Infrastructure

Authors SingularLogic team Status Final

Dissemination Level Public Delivery Date 10/3/2016

Number of Pages 43

Ecosystem infrastructure for smart and personalised inclusion and PROSPERITY for ALL stakeholders www.prosperity4all.eu

2

Abstract

This deliverable presents the prototype of the Consumer/Family/Professional configurable AoD feature of the generic Assistance on Demand (AoD) infrastructure and is the output of T205.4. While the (already delivered) D205.1 includes the use scenarios and general architecture for all AoD modules, including the Consumer/Family/Professional AoD feature, this deliverable focuses and provides more details on the implementation of the specific feature as carried out in the framework of task 205.4. The nature of the deliverable is Prototype, thus this is an accompanying document.

Keyword List

Assistance on Demand (AoD), open source, network of services, carer, configurable AoD, network of Assistance on Demand services

Version History

Revision Date Author Organisation Description

01 10/11/2015

SILO SingularLogic S.A. ToC

02 17/12/2015 SILO SingularLogic S.A. Chapters 1 added,

First draft input added in chapters 2, 3 and 4

03 25/01/2016 SILO SingularLogic S.a. Revised ToC based on comments

received on 19/1/2016 and chapter 5 contents added.

04 27/01/2016 SILO SingularLogic S.a. Revised chapter 3.

05 22/02/2016 SILO SingularLogic S.A. Internal quality control and

comments

06 26/2/2016 SILO SingularLogic S.A. Full draft sent to project peer

reviewers:

29/2/2016 MLS Adam Stavridis Internal Peer Review

29/2/2016 FHTW Chris Veigl Internal Peer Review

final 10/3/2016 SILO SingularLogic S.A. Final version taking into account the

feedback provided by the internal reviewers

http://www.prosperity4all.eu/


3



4

Table of Contents

Executive Summary .........................................................................................................10

1 Introduction ..........................................................................................................11

1.1 The purpose and structure of D205.2 ....................................................................... 11

1.2 Innovation beyond the state-of-the-art of the Network of Assistance on demand Services component .............................................................................................................. 12

1.3 Contribution to the global architecture .................................................................... 13

2 P4A AoD infrastructure supporting consumer/family/professional configurable AoD service Use scenarios .......................................................................................................15

2.1 State-of-the-art in carer support for assistance service configuration ..................... 15

2.2 Use scenarios ............................................................................................................. 21

2.3 Scenario discussion .................................................................................................... 26

3 User requirements related to Network of Assistance Services ................................28

3.1 Analysis of use scenarios in Use Cases ...................................................................... 28

3.2 Requirement extraction ............................................................................................ 33

3.3 Requirements Inherited from AoD infrastructure .................................................... 36

3.4 Supported functionalities .......................................................................................... 37

4 Specifications and Development plan ....................................................................38

4.1 Positioning of Network of Assistance Services in the overall AoD platform architecture and other P4A components ............................................................................. 38

4.2 NAS component specifications .................................................................................. 39

4.3 NAS component and actors interaction .................................................................... 40

4.4 Development and testing plan .................................................................................. 42

5 Installation guidelines ............................................................................................43

6 Conclusions ...........................................................................................................47



5

List of Tables

Table 1: The remaining chapters of D205.2 and their inter-relation with P4A activities/goals .................................................................................................................................... 12

Table 2: The multi-layered service categorization agreed with P4A users (Evaluation iteration 1) ................................................................................................................................ 22

Table 3: Description of use case „SC6_UC1: Define and get approval of the service consumer “ .................................................................................................................................. 29

Table 4: Description of use case „SC6_UC2: Configure assistance services related to daily activities“ .................................................................................................................... 30

Table 5: Description of use case „SC6_UC3: Configure assistance services related to layer-1 service category“ ........................................................................................................ 31

Table 6: Description of use case „SC6_UC4: Service search based on keywords“ .................. 31

Table 7: Description of use case „SC6_UC5: Review and manage the network of assistance services“ ..................................................................................................................... 32

Table 8: List of use cases .......................................................................................................... 33

Table 9: List of requirements that the component „Network of Assistance Service” has to meet ........................................................................................................................... 34

Table 10: User Requirements Inherited by AoD platform ....................................................... 36



6

List of Figures Figure 1: Position o fT205.4 in the P4A Architecture: Being a component of WP205, its

outcomes are delivered to SP4 for user testing. ....................................................... 14

Figure 2: AoD state-of-the-art platforms ................................................................................. 16

Figure 3: GreatAupair. Account page that focuses on Job details ........................................... 16

Figure 4: QuikrServices. Profile creation focuses on general Employer or Employee role ..... 17

Figure 5: Upwork. It focuses on explicit position details ......................................................... 17

Figure 6: Guru. Focuses on skills .............................................................................................. 18

Figure 7: Care.com. Offered services ....................................................................................... 18

Figure 8: Urbanclap. Question/steps during matchmaking process ........................................ 19

Figure 9: Thumptack. Matchmaking process indicative steps ................................................. 20

Figure 10: Peopleperhour. At the final stage of the purchase there are more services offered by the same employee that may be added ............................................................... 21

Figure 11: The final view of the central part of the screen during the set –up of a network of assistance services. .................................................................................................... 24

Figure 12: AoDemand Interface, the list of authorised carers as it appears to the user ........ 27

Figure 13: Scenario 6: Configurable Assistance on Demand service network - Use Cases Diagram ...................................................................................................................... 28

Figure 14: The organisation of the search in the multi-layered service categories structure seems rather complicated and is replaced by a filtering approach to avoid paralysis-analysis ....................................................................................................................... 29

Figure 15: AoD architecture including the „network of assistance services“ component ...... 38

Figure 16: Network of assistance services EER diagram (part of overall AoD database) ........ 39

Figure 17: Carer dashboard ...................................................................................................... 41

Figure 18: The carer selects some services exploiting the guided process ............................. 41

Figure 19: Final step: overview of selected services ................................................................ 42

Figure 20: Login in administrative panel of AoD ...................................................................... 43

Figure 21: Landing page in administrative panel of AoD ......................................................... 44

Figure 22: List of AoD components .......................................................................................... 44

Figure 23: Deactivation of the Network of assistance services component............................ 45

Figure 24: List of supported categories .................................................................................... 45



7

Figure 25: Change the parent category of the Transportation category ................................. 46



8

List of abbreviations (Glossary)

Abbreviation Full Form

AoD Assistance on Demand

API Application programming interface

C4A Cloud for All project

DoW Description of Work

EER Enhanced (also called extended) entity-relationship

FAQ Frequently Asked Questions

GPII Global Public Inclusive Infrastructure

GPL General Public License

HTML5 Hypertext Markup Language

ICT Information and Communication Technologies

ID Identifier

IT Information Technology

MTV Model-Template-View

NAS Network of Assistance Services

NF Non-functional

NF-Req Non-functional Requirement

P4A Prosperity for all

PHP PHP: Hypertext Preprocessor

REST Representational State Transfer

SCa_UCb Use Case b of Scenario a

SP Sub – Project

SR System Requirement

UC Use Case

UG User Group

UI User Interface

UL Unified Listing

UML Unified Modeling Language

UR User Requirement

URL Uniform Resource Locator

WAI Web Accessibility Initiative



9

Abbreviation Full Form

WCAG Web Content Accessibility Guidelines

WP Work Package



10

Executive Summary

This deliverable describes the component of the Assistance on Demand infrastructure that allows any users to set up a network of assistance services either for themselves or for a person they care about. While the main functionality has already been described in D205.1, in this deliverable we describe the targeted usage scenarios, their split in use cases which drive the requirements identification work, we specify the implementation architecture and details and finally we provide guidelines for the installation of this component as part of AoD open source infrastructure. It should be noted that the nature of this deliverable is prototype. The implementation code, the documentation and installation guidelines can also be found in https://github.com/silop4all/aod .



11

1 Introduction

1.1 The purpose and structure of D205.2 This deliverable discusses the functionality of the AoD that focuses on the creation of a network of assistance services either by the interested users themselves or by a carer through a simple procedure. This functionality is provided by a dedicated component that is tightly coupled with the rest of the AoD infrastructure. We refer to this component as “Network of Assistance Services” or NAS hereafter. The aim is to make configuring a personal network (i.e. a network/group of services offered by humans or machines or both) easy enough to be carried out by an individual (consumer) or by a family member, as well as by a professional.

The support of network of assistance services creation is considered a distinct feature of the AoD and is addressed in T205.4. As such, the relevant implementation is considered to be a module of the generic AoD platform that can be activated (or not) during the platform instantiation by the administrator of the specific AoD instance.

The users that interact or are relevant to the NAS component are:

- Consumers with or without disabilities who are interested in setting up a network of services.

- Formal and/or informal carers who are interested in setting up a network of services for those that they provide care for. It is important to note here that the P4All project (notably T205.4) is concerned mainly with the technical implications of this possibility and not the legal or social ones although the latter is also very relevant in cases of user representation by third parties (e.g. formal/informal carers). It is expected that the legal or social issues will be tackled by those parties that will use the general AoD platform to set up specific instances of it following local, regional and national relevant laws and best practices.

- AoD platform administrators who are interested in including the specific component in their AoD instantiation.

- Service providers are indirectly addressed as this component allows them to offer their services to consumers.

This deliverable includes six chapters as shown in Table 1. It is worth stressing that the procedure of defining potential users and actors relevant to the AoD platform, as well as the methodology related to analysing the use scenarios to extract user requirements and to consolidating the requirements so as to specify the implementation architecture has been included in D205.1 and is, thus, not repeated in the current deliverable. Instead, here we focus on additional/more detailed requirements that the NAS component has to satisfy and on NAS’ specifications.



12

The latest versions of the implementation code, the documentation and installation guidelines can be found in the AoD wiki space https://github.com/silop4all/aod

Table 1: The remaining chapters of D205.2 and their inter-relation with P4A activities/goals

Chapter Title Feeds/Supports

2

P4A AoD infrastructure supporting consumer/family/professional configurable AoD service Use scenario

Component design in T205.4 and SP4 efforts – user testing

3 User requirements related to Network of Assistance Services

Component design and specifications (T205.4)

4 Specifications and Development Plan

Guides the implementation/prototype development and Prototype delivery in M24

5 Installation guidelines The prospective AoD platform administrator that instantiates AoD and needs details on how to activate/deactivate the feature

6 Conclusions Concluding remarks

1.2 Innovation beyond the state-of-the-art of the Network of Assistance on demand Services component The NAS component inherits the innovation of the general AoD infrastructure already presented in D205.1. It also adds value to the AoD because it:

1. Allows the carer to define/pre-select a set of services for the people they care about so that they can use it,

2. Helps the carer take care of all possible needs through a simple guided process that that can be followed by any user with typical PC use skills; this process helps to ensure that the carer he will not neglect any need and that the user will receive the services that better suit their needs,

3. Offers zero-configuration options (at least in those cases where the service supplier supports such a feature) to further facilitate service configuration and execution.


https://github.com/silop4all/aod


13

Zero configuration option (as described in the P4A DoW) is a default configuration of a service (either digital or human) which fits the needs of a large group of consumers. The service suppliers are left to decide the service parameters that can be configured and whether to provide “zero configurations” leaving the consumers to define other configurations (providing at the same time appropriate instructions).

We intend to further clarify these three aspects in chapter 2 through indicative use case scenarios.

1.3 Contribution to the global architecture This activity focuses on the “user-built” personal Assistance on Demand network concept. It is carried out in the framework of Task 205.4. The goal is to make configuring a personal network for an individual easy enough to be carried out by an individual or by a family member. The user will be guided to configure a multilayer Assistance on Demand network of services (including free and paid services). This will be achieved through the design and implementation of an easy-to-use interface that allows users with typical personal computer use skills and relatives to configure assistance networks.

To accomplish this goal, T205.4 needs to communicate with T205.1 which designs the architecture of the AoD and provides the high level specification of the AoD configuration interface/service, including the relevant interfaces/interconnections with other AoD subsystems. The outcome is delivered to Sub-project 4 for user testing. The work carried out in T205.4 is reported in the current deliverable D205.2 Consumer/Family/Professional configurable AOD which is accompanied by the relevant software code. The position of T205.4 in the overall P4A architecture is shown in Figure 1.



14

Figure 1: Position o fT205.4 in the P4A Architecture: Being a component of WP205, its outcomes are delivered to SP4 for user testing.

WP401 Evaluation Framework and Technical Validation

WP403 Evaluation w/ end users U. Listing & C-D Connection

WP405 Demonstrations

WP402 Iterative Pilot Testing (of Dspace) with Developers

WP404 Assessment of Prosperity4all Platform

WP502 Dissemination & Training WP503 Standards & Exploitation

Prosperity4all Infrastructure

WP201 - Infrastructure Architecture

WP204Media & Material Transformation Infrastructures

WP203Collaborative Devel Tools/Environments

Payment / Pledge Mechanisms

Unified Listing&

openMarketplace

WP205 Assistance on

Demand Services Infrastructure

WP302Education, eLearning,

Business and Employment Developers

WP303 Assistance on Demand Services

for home, school, work, travel, etc.

ConsumersClinicians, Teachers,

etc.

Librarians, PAPs

Use of infrastructure by Implementers who create access solutions and services - in different domains of life

WP202Building Block Components

P4A

Infra

stru

ctur

e To

faci

litat

e so

lutio

n de

velo

pers

& p

rovi

ders

Solu

tion

Dev

elop

ers

& Pr

oivd

ers

(Infra

stru

ctur

e U

sers

)

Solu

tion

Use

rs

Third Party Providers

WP301Communication, Daily Living

Health and Accessibility Developers

Customers of the Solution ProvidersIndirect beneficiaries of this project. Not direct users of Prosperity4all except for

1) Unified Listing and Open Marketplace and 2) Consumer Developer Connection

Federal and Local

Governments

WP101

-M

odeling and M

arketplaceW

P102-

Dem

and-Supply Transaction M

odeling

WP103

-Ecosystem

& Infrastructure Requirem

ents Needs, Models, & Requirements



15

2 P4A AoD infrastructure supporting consumer/family/professional configurable AoD service Use scenarios

Before defining the use cases we target, we performed a survey on state-of-the-art existing platforms to examine the functionality that they provide to carers. We include our findings in section 2.1 and then we define the use scenarios P4A considers in section 2.2. It is worth mentioning that these use scenarios were defined through an iterative process: we drafted use scenarios which were examined by user groups and experts from the consortium and we refined them based on the received feedback (see D205.1 for more details on the methodology).

2.1 State-of-the-art in carer support for assistance service configuration By reviewing the list of Assistance Services web sites, as presented in D205.1, we are able to revise the list and pinpoint the differences in the issues of interest to us. The possibility to join the AoD portal as a third party, e.g. as a carer/representative of someone else, is of special importance. So far, we have not come across such functionality being offered by existing AoD-related portals. As already noted above, the P4All project (notably T205.4) is concerned mainly with the technical implications of this possibility and not the legal or social ones although the latter is also very relevant in cases of user representation by third parties (e.g. formal/informal carers). It is expected that the legal or social issues will be tackled by those parties that will use the general AoD platform to set up specific instances of it, following local, regional and national relevant laws and best practices.

In our state-of-the-art analysis, we also focused on the easiness of setting up a network of services, which in P4A is ensured thanks to a guided process of selecting services among a well-structured services categorisation. This feature, too, appears to be offered in a very limited way in existing platforms.

Next we present, in tabular format, a summary of the revised state-of-the-art review, focusing on the two issues (advantages of the P4A AoD) presented above. We, then, proceed to providing some further comments on specific state-of-the-art platforms.



16

Figure 2: AoD state-of-the-art platforms

Most existing AoD-related portals focus on job posting and some offer extensive details on position offering or seeking descriptions. Examples are given in the figures below (namely Figure 3 to Figure 7).

For example, GreatAupair is an online international job matching service used by families to find affordable, trustworthy caregivers. In Figure 3 we see the user account page which mainly focuses on the specific job details.

Figure 3: GreatAupair. Account page that focuses on Job details

Freelance Proffesionals

Domestic-Daily life

Travel-Leisure

Can manage account on

behalf of user

Can buy service on

behalf of usergreataupair care4hire care quikrservices booking amara urbanclap upwork guru freelancer peopleperhour greatlance thumptack fiverr

Application domain CarerServices Wizard



17

Quikr, an online classifieds platform acts as a place where people can connect with each other to buy or sell goods and services. In the services section, the profile creation this site offers to its users is built around general employer or employee roles, Figure 4.

Figure 4: QuikrServices. Profile creation focuses on general Employer or Employee role

In Figure 5 we see the job posting details of Upwork, a platform for companies to hire and work with independent professionals, around the world.

Figure 5: Upwork. It focuses on explicit position details

Guru also provides businesses with the tools to find and hire freelancers all over the world; and offers freelancers the opportunity to market their skills to a global audience. In Figure 6 their matchmaking tool is presented.



18

Figure 6: Guru. Focuses on skills

Another relevant portal is Care4hire but its service offering is limited to simply matching available services with consumers in need based on locality. Care.com, Figure 7, is another position posting site but this one offers the possibility for a carer to hire aid on behalf of an elderly or special needs individual.

Figure 7: Care.com. Offered services

An interesting feature we came across on two separate sites is a very detailed guide, asking explicit questions, during the employer-employee matchmaking process, as in Urbanclap, Figure 8. Urbanclap, also offers some services that may be bought on behalf of someone else.



19

Figure 8: Urbanclap. Question/steps during matchmaking process

.

Thumptack focuses on matching experts with employers who need a project accomplished on a domestic level, based on locality. Their detailed matchmaking process is depicted in Figure 9.

Step 1

Step 3

Step 2



20

Figure 9: Thumptack. Matchmaking process indicative steps

After the main transaction is completed, the portal Booking.com offers limited guidance related to additional services that the consumer might need. Peopleperhour, Figure 10, may have the closest feature we have found to a service wizard, in the P4A sense: additional services are offered by each employee – Add ons – that may be added to the purchase, if the consumer decides that they are needed.



21

Figure 10: Peopleperhour. At the final stage of the purchase there are more services offered by the same employee that may be added

2.2 Use scenarios The main scenario that illustrates the functionality offered by the feature for the creation of a user-built network of Assistance on Demand services has been included in D205.1 (scenario 6). Scenario 6, entitled “Configurable Assistance on Demand service network” (initially presented in D205.1) is further elaborated here. The aim of this feature is to make configuring a network of services for an individual easy enough to be carried out by an individual or by a family member (informal carer) as well as by a professional (formal carer).

The prospective user enters the AoD and through an intuitive and simple user interface, which can be configured according to their personal preferences, can set up a network of assistance on demand services covering multiple activities of their life and exploiting the wealth of AoD services accessed through the AoD platform. Placing emphasis on easiness of use, users with advanced PC use skills are offered the option to define more detailed configurations of the AoD services network, while more novice users or users with basic PC use skills will have certain options set to default values so that the configuration burden is minimised, provided that the service suppliers support the, so-called, zero-configuration option.

The complexity of navigating a multi-tiered system sliced up into many different service categories may get out of control, depending on the type and number of assistance services a person needs. In order to alleviate such complexity and help the user find the appropriate needed services, during the user testing of AoD in SP4, it was suggested that AoD should allow its users to search for assistance services:



22

• either based on keyword search • or following a structured search. To enable this structured search, the categorisation

shown in Table 2 was co-developed with the users during testing in SP4. It is important to note that the administrator of each AoD instance is capable of modifying this categorisation so as to fit the needs of the target user group since categorisation of services is expected to be very much instance-specific. The categorisation of Table 2 below is only indicative and subject to change based on further user input.

Table 2: The multi-layered service categorization agreed with P4A users (Evaluation iteration 1)

Layer 1 Layer 2 Layer 3

Daily Life

Caretaking

Babysitting

Child care Senior care Individuals with disabilities Pets

Housekeeping Cleaning Cooking Miscellaneous e.g. party help

Transportation e.g. driving, taxi, parcel delivery

Food services Delivery Catering

Advertisements e.g. employment, real estate, tourist

Health/Fitness

Management

Assistance

Medical care e.g. doctors, nurses Pharmaceutical providers Personal training Other e.g. Holistic approaches

Miscellaneous e.g. Guides

Entertainment Gaming applications Other e.g. event announcements

Digital Services Disability Services

Visual impairment Audio impairment Cognitive impairment Physical impairment Other



23

Miscellaneous

Technical Support Communication with public services Finance Services

Although several of the above categories can be split in sub-categories, it is reminded that a) the above categories are indicative and have been formed based on user feedback and b) the categories organization can be modified by the platform administrator to fit the needs of the targeted user groups.

Act 1: Guided configuration of AoD service network

Elena Rippcorde (a persona defined in SP1) suffers from Multiple Sclerosis which is now in advanced stage. Her brother, George, decides to use the P4A AoD to help his sister organize her daily life. He registers and enters the AoD. During registration, he indicates that he intends to play the role of the relative/carer and defines Elena as the person he cares for. The AoD notifies Elena requesting her confirmation; namely, a notification is presented to her the next time she enters the AoD platform and an e-mail is sent to her as well. Once the confirmation is received, George can continue setting up a network of assistance services. In his dashboard, he sees a button indicating “Your assistance service network”. He presses the button and he is offered the option to either follow a guided process (a step-by-step wizard) to identify the needed assistance services or to search just using the free text search (based on keywords). George selects the guided process. Given that the AoD services are categorised in 7 basic (i.e. layer-1) groups, George will be prompted to visit/inspect these 7 service groups. These 7 service groups are: Daily Life, Health/Fitness, Entertainment, Digital Services, Finance Services and Communication with public services and Technical Support. Given that George selected the guided process, the first step is “daily activities”. Since Elena has mobility problems, she needs assistance. So George selects the “daily Life” category from the layer-1 service category menu (shown on the left hand side of Figure 1). The view presented in the same figure appears; it includes all the relevant layer-2 groups (namely Caretaking, Housekeeping, Transportation, Food services, Advertisements) and next to them the full list of services of this layer-1 group.



24

Figure 11: The final view of the central part of the screen during the set –up of a network of assistance services.

George is allowed to either

• deselect any (one or more) of the layer-2 categories; this will lead to a shorter list of services

• or turn to “search services by keyword” mode within this layer-1 category (i.e. daily life).

George can select from one to multiple services from any layer-2 category. He selects a human-based service included in the housekeeping category: let’s say a service named “Kate Maid” which is offered in Elena’s neighbourhood and includes both house-cleaning tasks as well as shopping. Once George has finished with daily activities, he is guided to the next layer-1 service group which is: “health/fitness services”. This includes the following layer-2 subcategories:

• Management • Assistance



25

• Miscellaneous The first category offers a variety of digital and human services ensuring that Elena will be e.g. reminded to take her pills or take physical exercises. George selects: “MedReminder”. The 2nd category includes four sub-categories: care, pharmaceutical providers, personal training, other. George selects the care which includes:

a) human-based services (based either on volunteers or professionals) who can, for instance, regularly visit Elena to check her condition and safety and

b) machine-based services that allow readings from sensors placed on Elena to be forwarded to her doctor.

George chooses from the “regular safety checks” services one where a person, Daniel, is communicating with Elena to check on her condition. For this service, the default configuration (zero-configuration in P4A terminology) is to perform this check every three hours. Once George has finished with the “care services”, he proceeds to other layer-1 service groups such as: entertainment. He is presented with all services of this layer-1 group which belong to “gaming applications” or “other” groups. At this point, he is tired of following this structured manner of setting up a network of assistance services and decides to turn to the “keyword based” search. He enters “gaming console” and from the list of available services he selects and downloads a gaming console for people with hearing problems for his sister. Before he leaves the process of NAS configuration, the AoD platform presents him with the full list of services he has denoted as interesting and purchased and the categories they belong to, asking him to confirm whether he has selected all necessary services. Before confirming, George inspects the categories for which he has not selected a service and realises that it would be nice to select a technical support service, so he selects the category and presses the “select service” button. He denotes a service as an interesting one clicking on the “Interesting service” button (alternatively, he can purchase it directly), again the platform provides an overview of both the interesting and purchased services per category. As he decides that he will not search for additional services, he goes back to the carer dashboard. There, George clicks on “Preview services” button. He is presented with the set of interesting services as well the set of purchased services he has selected for Elena. George cancels a service from the set of interesting ones. At this point, he can return to the basic view of AoD and continue enjoying his navigation.

Act 2: Configuration of the AoD service network by professionals Elena is treated by Dr. Smith. Five days after the initial treatment definition, Dr. Smith decides that Elena is better so there is no need to check her health every three hours. The regular safety checks can be relaxed to twice every day. This means that the “Daniel’s safety



26

checks” service has to be re-configured appropriately. He also decides that she should start physical exercising. Dr. Smith is already a registered AoD platform user. He indicates that he intends to configure Elena’s service list. A notification is sent to Elena and her brother through AoD and e-mail. As soon as one of them confirms Dr. Smith’s right to configure Elena’s service, Dr. Smith is notified accordingly. Dr. Smith enters the AoD. A tab with the users he cares for appears on his dashboard. He selects Elena and checks the services associated with her. He selects the safety checks service and configures it appropriately. By default (zero configuration), this service issues safety checks every three hours. Dr. Smith configures the safety checks to be performed twice per day. He also clicks on the “training” category and selects a human-based service for “MHealth Physical Training”. The end result is a screen where all the services selected for Elena are depicted.

2.3 Scenario discussion Guiding the consumers/carers towards setting up an AoD service network aims to ensure that no necessary service will be overlooked, e.g. if a person has an accident and his caregiver tries to make his life more comfortable, he may look for appropriate care service but omit taking care of housekeeping tasks or every-day life activities or entertainment. Thus, it is not within the scope of P4A/T205.4 to design a full checklist or step-based approach covering all possible services offered to a user but to implement an indicative one and ensure that any similar procedure can be flexibly supported by the AOD platform and implemented in the future by interested parties (e.g. association of people with disabilities that can specify in detail how the needs and preferences of their members can be best catered for through various networks of services). As such, the aforementioned process is just an example aiming to show that the user will be guided to select services for every aspect of life or relevant condition. Additionally, popular bundles of services could be suggested to people declaring similar needs and preferences with peers. To avoid analysis-paralysis (meaning that a carer may find it hard to walk through the existing multiple service category layers) the AOD platform offers service selection both through a well-structured process but also through a free text keyword search. Moreover, within each layer-1 category of services, further categorisation is used mainly as a way to filter services while, in parallel, supporting keyword based search within each category.

Additionally, the carer is left to decide whether to purchase a service or just select it and put it to a “wishlist” so that the people he cares for do not have to make extensive searches but be presented with interesting services; instead, they would only have to purchase a service from the pre-selections when needed. For example, a housekeeping service or a care service



27

may be selected by the carer for a specific consumer, however the carer may leave it up to the consumer to decide when to use (purchase) them.

It is worth to say that the consumer can grant permission to more than one carer, let say carer A and carer B (see Figure 12), to setup/configure his/her network of services. Let‘s suppose that the carer A has already set up certain services for him/her. Moreover, the carer B wants to enrich the set of services that this person uses. Therefore, carer B can select additional services on behalf of the consumer and also, can modify/reconfigure a subset of services that carer A has already selected.

Figure 12: AoD Interface, the list of authorised carers as it appears to the user



28

3 User requirements related to Network of Assistance Services

While in D205.1 a set of requirements has been identified for the AoD infrastructure as a whole, in this chapter, we define the requirements that the NAS component has to satisfy. These requirements are either inherited from the requirements that the full AoD infrastructure has to satisfy or captured after the analysis of the use scenarios described in chapter 2.

3.1 Analysis of use scenarios in Use Cases To identify the user requirements that NAS has to meet, we first analyse the use scenarios in use cases (following the same approach as in D205.1) and work on them so that we finally extract the user requirements.

To support the user to set up a network of assistance services, the implementation of the use cases shown in Figure 16 is necessary.

Figure 13: Scenario 6: Configurable Assistance on Demand service network - Use Cases Diagram

The three green use cases in figure 16 above describe the (structured) search of services in three different layer-1 categories. While in P4A, seven layer-1 categories have been defined, in the figure we show only three of them. The platform should support a number of similar use cases equal to the number of layer-1 categories.

To avoid analysis-paralysis, we do not further proceed to structured search within each layer-1 category. If we did, the situation would look like the one shown in Figure 17, which is

All layer 1 categories

… (all layer 1 categories)



29

rather complicated for the average IT user. Instead, within each layer-1 category the full list of services belonging to any of the layer-2 category is presented. Next to the selected layer-1 category a list with its entire layer-2 categories appear. The user can de-select one or more layer-2 category(ies) to reduce the number of services presented. Alternatively, he/she can search by keyword within each layer-1 category.

Figure 14: The organisation of the search in the multi-layered service categories structure seems rather complicated and is replaced by a filtering approach to avoid paralysis-analysis

Table 3: Description of use case „SC6_UC1: Define and get approval of the service consumer “

Use Case

ID SC6_UC1

Name Define and get approval of the service consumer

Storyline

The user- carer enters the AoD and selects the “set-up or modify an assistance service network” that appears in his personal page. In the first screen, he is prompted to add a person he cares for and the people that have accepted his offer to care for also appear. He selects to add the user he cares for. The AoD sends an SMS and an e-mail to the person he cares for requesting his confirmation. He cannot proceed to any other action, unless he gets approval from the person he cares for.

Actors User-service consumer, User-carer, Security infrastructure

Goals To define the person that he cares for and get his approval.

Preconditions Both the carer and the consumer have been registered in AoD.

Post Conditions The carer gets the approval of the service consumer to configure the network of assistance services.

Trigger Events The user –carer selects „set-up or modify an assistance service network“ that appears in his personal page.



30

Table 4: Description of use case „SC6_UC2: Configure assistance services related to daily activities“

Use Case

ID SC6_UC2

Name Configure assistance services related to daily activities

Storyline

The user is prompted to select assistance services related to daily activities. He first selects the layer-1 category and all layer 2 services of this category appear. Next to them, the list of layer-2 categories of the same layer-1 category is presented. He can deselect any layer-2 category so as to filter the presented services. Alternatively, he can use search by keyword to find a service of interest in this layer-1 category. Once he selects a service, this is added to the “network of Assistance Services” of the person he cares for. (At the moment, this is not purchased instantly; however, we may include the possibility to purchase the service instantly, or just select it and include it in the network of assistance service. He will be prompted to purchase and configure the service.)

Actors User-service consumer, Security infrastructure, Payment infrastructure

Goals Select assistance services related to daily activities that will be consumed by the person with disabilities.

Preconditions The carer has got approval from the person he cares for.

Post Conditions

The assistance services related to daily life activities are selected.

Trigger Events The user –carer selects „create/modify an assistance service network“ button that appears in the screen with the persons he cares about.



31

Table 5: Description of use case „SC6_UC3: Configure assistance services related to layer-1 service category“

Use Case

ID SC6_UC3

Name Configure assistance services related to x layer-1 service category

Storyline

This use case is a generalisation of SC6_UC2. The user is prompted to select assistance services related to the x layer-1 service category. He first selects the layer-1 category and all layer 2 services of this category appear. Next to them, the list of layer-2 categories of the same layer-1 category is presented. He can deselect any layer-2 category so as to filter the presented services. Alternatively, he can use search by keyword to find a service of interest in this x layer-1 category. Once he selects a service, this is added to the “network of Assistance Services” of the person he cares about. (At the moment, this is not purchased instantly, however, we may include the possibility to purchase instantly as well as simple service selection, depending on user feedback. He will be prompted to purchase and configure it.)

Actors User-service consumer, Security infrastructure

Goals Decide whether services from this layer -1 service category are needed.


Post Conditions The services related to this layer -1 service category are selected.

Trigger Events The user-carer has finished configuring the assistance services related to previous layer-1 service categories and proceeds (selects from the right hand menu) the next layer-1 service category”.

Table 6: Description of use case „SC6_UC4: Service search based on keywords“

Use Case

ID SC6_UC4

Name Service search based on keywords



32

Use Case

Storyline

This Use case is similar to the SC3_UC1 which is included in D205.1 and allows the AoD user to search for a service based on keywords. There are however two significant differences:

- Once a service is found and selected, this is added not to the user’s service list but to the network of assistance services of the person he cares for.

- This search can be performed within any layer-1 service category. When the carer opts to look for an assistance service based on keywords only, he enters the keywords in the search bar and the platform returns all the services that match the keywords provided by the carer. These can be ranked according to criteria such as cost or Quality of Service. He can scroll through the list and select a service. Once the service is selected, it is included in the network of assistance services associated with the person he cares for.

In case the user decides to use the search bar to look for a service within a certain layer-1 category, this is equivalent to searching with the keywords entered by the user, plus the selected layer-1 service category.

Actors User (carer), AoD

Goals Find an assistance service that meets the user needs

Preconditions The carer is provided with authorization by the person he cares for.

Post Conditions An assistance service is selected and added to the network of assistance services.

Trigger Events The carer uses the keyword-based search bar.

Table 7: Description of use case „SC6_UC5: Review and manage the network of assistance services“

Use Case

ID SC6_UC5

Name Review and manage the network of assistance services



33

Use Case

Storyline

The user is offered a full view of the network of assistance services organized in categories and is capable of inspecting and modifying parameters (configuration), or of purchasing the service. All layer-1 service categories are listed and next to them there is a sign allowing them to distinguish whether any service has been selected from each category. If there is a layer-1 category for which he has not selected any service, he is reminded that a certain layer -1 category has not been covered. He accesses the list of services of a specific layer-1 category clicking on the corresponding “select service” button. Afterwards, he can declare a service as interesting or purchase it. He has also the capability to access both the services that constitute the wishlist and the purchased ones via the preview services button in the carer dashboard.

Actors User-service consumer, Security infrastructure, payment infrastructure

Goals Modify the network of assistance services.


Post Conditions The assistance services configuration has been updated.

Trigger Events

The user-carer has finished configuring the assistance services and presses „complete the configuration of the network of assistance services“ or from the first page of assistance services network configuration presses the button „inspect and modify assistance service network“.

The list of the above presented use cases, is presented in Table 8.

Table 8: List of use cases

UCID UCID Title

SC6_UC1 Define and get approval of the service consumer

SC6_UC2 Configure assistance services related to daily activities

SC6_UC3 Configure assistance services related to x layer-1 service category

SC6_UC4 Service search based on keywords

SC6_UC5 Review and manage the network of assistance services

3.2 Requirement extraction In this section we identify the user requirements that NAS has to meet. These are listed in the following Table 9. To keep the relation with the requirements captured in D205.1 more clear, we have kept the numbering of requirements the same as in D205.1 (even though we



34

elaborate their description) and we have numbered additional ones as SRi_x where x shows the SRi_x is relevant to SRi (even though it highlights a need not necessarily captured by SRi).

Table 9: List of requirements that the component „Network of Assistance Service” has to meet

System Req. ID Description UC/UR Priority Scenario

SR35

Each user can play the role of carer, i.e. be associated with other users and is capable of configuring/selecting/purchasing services for them.

SC6_UC1 1 6

SR35_a The role of carer has to be supported by the P4A security infrastructure.

SC6_UC1 1 6

SR36 The user is offered the option to configure a network of assistance services for other users (consumers of services).

SC6_UC1 1 6

SR36_a The network of assistance services can be a list of services targeting the same or different services potentially in prioritized order.

SC6_UC1 2 6

SR37 The user cannot configure services for other users without their approval.

SC6_UC1 1 6

SR37_a The approval is provided either through SMS or through e-mail.

SC6_UC1 1 6

SR38

The platform guides the user (carer) to set up a network of assistance services through a step-by-step approach executed over all layer-1 service categories (e.g. daily activities, health, training and entertainment).

SC6_UC2 1 6

SR38_a

When the carer has selected the layer-1 category "daily life" he is offered two options: to proceed to the selection from a list of services or to search for a service based on keywords.

SC6_UC2 1 6

SR39 Assist the user in selecting assistance services for daily life activities allowing him to filter them based on layer-2 categories.

SC6_UC2 1 6



35


SR40

Allow the user to skip a specific step (layer-1) in services selection, e.g. skip the step of assistance services for daily life activities and proceed to the next step of assistance services for care.

SC6_UC2 1 6

SR41

When the carer has selected the x layer-1 category, he is offered two options: to proceed to the selection from a list of services or to search for a service based on keywords.

SC6_UC3 1 6

SR41_a

Define the sequence of layer-1 service categories. For the P4A prototype, the sequence will be this followed in the table of service categories that appears in chapter 2 of D205.2

SC6_UC3 2 6

SR41_b Assist the user in selecting assistance services for x layer-1 service category allowing him to filter them based on layer-2 categories.

SC6_UC3 1 6

SR42 Allow the user to skip the set up assistance services for x layer-1 service category and proceed to the next step of assistance services.

SC6_UC3 1 6

SR43 Allow the user to search for an assistance service based on keywords within any layer-1 category.

SC6_UC4 1 6

SR44

Allow the user to skip the set up of assistance services related to any layer-1 service category and proceed to the next step (completing the configuration of assistance services).

SC6_UC3 1 6

SR45 The user is offered a view of the assistance service network in the page "assistance service network review and management".

SC6_UC5 1 6

SR45_a The carer can assign different priorities to the selected services or sequence in which they will be received by the consumer.

SC6_UC5 2 6



36


SR46

The user can modify the service parameters of any service of the assistance service network (assuming approval from the service consumer) in the page "assistance service network review and management".

SC6_UC5 1 6

SR46_a The user can use the "zero configuration" option if supported by the service supplier.

SC6_UC5 1 6

SR46_b The user-service supplier will be prompted to provide "zero configuration" options and setting when possible.

SC6_UC5 1 6

SR47 A checklist with the service categories covered for the person in need is presented to the user-carer.

SC6_UC5 1 6

3.3 Requirements Inherited from AoD infrastructure The component of AoD that is responsible for the set-up of a network of assistance services has to also satisfy a set of requirements that the whole AoD platform has to meet. We call them “inherited” requirements and they are shown in Table 10.

Table 10: User Requirements Inherited by AoD platform

User Requirement ID

Description

UR-1 Different dashboards for each user type will be offered.

UR-3 Service rating and sorting based on diverse criteria will be possible.

UR-4 Offering zero/default configuration options for efficiently supporting novice users.

UR-5 or each service, a set of attributes including charging model, service supplier, support of „try-harder“ concepts, etc. will be presented to the user.

UR-6 Upon selection, the AoD platform communicates with the payment infrastructure for notifying on the selection and enact payment procedures.



37

User Requirement ID

Description

UR-8 Flexible assistance network configuration services for easy access and tailoring of assistance services

UR-9 High-quality multimodal technical support to ensure service acceptance.

UR-12 Capability for customization per person or community/group

UR-14 Support more than three application domains

UR-15 Support three service types

UR-16 Support high set of service characteristics

UR-17 Support the above three charging models

UR-18 Indicative application domains are: health, domestic/daily life, transportation travel, leisure

It should also be stressed that the presented components has to support high levels of accessibility (e.g. AA in the third year of the project).

3.4 Supported functionalities In this section, we summarise the main functionalities of the presented component:

- Linkage between users (of different roles). The relation is between the user (service consumer) and the carer (user selecting, configuring and/or purchasing services). The carer can be a family member or third individual, novice user or professional of any discipline. This means that a formal carer can play the role of carer and configure a certain service of his patient/person he cares for.

- Creation and management of network of assistance services, i.e. a list of services that may target diverse user needs.

- Guidance/assistance in covering all aspects of consumer life.



38

4 Specifications and Development plan

4.1 Positioning of Network of Assistance Services in the overall AoD platform architecture and other P4A components In this section, we detail the specifications of the NAS component which has been included in the AoD platform. The functionality described in chapter 2 is mainly carried out by the “network of assistance services” component included in the AoD architecture already presented in D205.1. The relevant use cases involve also the security and payment infrastructures as a carer has to have rights so as to select a service that another person will consume; moreover, the payment infrastructure should be notified accordingly, when necessary.

Figure 15: AoD architecture including the „network of assistance services“ component

Back-end

Front-end

AoD API

Service Registration & management

Service search and selection Try harder

Notifications

Multimodal technical support

File System

Network of Assistance Services

User preferences

User profile Social networking

Service statisticsProviders

Individuals/Organizations

Carer givers

Service rating

Presentation layer

templates

Business layer

urls views

Data layer

models

Data resources

AoD application

Social networking

back-end

Security InfrastructureSecurity Infrastructure

Payment InfrastructurePayment Infrastructure



39

Τhe source code of the configurable network of assistance service component can be found in https://github.com/silop4all/aod.

4.2 NAS component specifications Since the Network of Assistance services (NAS) component is an extension of the AoD platform (Figure 18), the back-end part of AoD application has been enriched in terms of layers (presentation, business and data one) and Data resources. Regarding the Data resources, the data model of the AoD platform has been extended with several tables (Figure 19). A carer sends a request to a consumer by requiring permissions to set up his/her network of assistance services. The consumer accepts or declines the request of the carer. The entity Carers_assist_consumers is used to keep the request of a carer and the reply to it from the person with disabilities. A carer can send requests for permissions to multiple consumers; so both the Carers entity and the Consumers entity are associated with the Carers_assist_consumers via 1-to-N relationship.

Figure 16: Network of assistance services EER diagram (part of overall AoD database)

The carer can select a set of services on behalf of a consumer that are stored in the entity Nas_temp_setup. More specifically, the entity Nas_temp_setup includes the id of the carer, the id of the consumer, the service that the carer has selected and the timestamp of every



40

action. Furthermore, the carer has the capability to purchase a service on behalf of a consumer. This information is kept in the entity Nas_consumers_services. This entity consists of the consumer id, the service id, the cost of service, a feedback from the user as a rating (score), and the flag is_completed that depicts the status of the service. Every registered service can be associated with a configuration. This configuration is kept in the Services_configuration entity; each instance consists of the service id, a parameter and its value and the is_default flag. It is worth to say that a service probably has multiple customized parameters, so there is a 1-to-N relationship among the Services and Services_configuration entities. The carer can access and modify the configuration of the service that he/she aims to purchase (before the service purchase) whether the service provider offers it. Therefore, the updated configuration is stored in the Network_services_configuration entity. Also, the Components entity keeps the title of a supported component and its status (active/disable). The NAS component disposes a set of new URLs that the users can access via a browser. Since these URLs are handled from the Business layer of AoD application, the urls and views modules have been enriched with additional functionalities. The Business layer interacts both with the Data layer and the Presentation layer to present to the user the desirable information.

4.3 NAS component and actors interaction At this point, it is worth to stress the sequence of movements of actors involved in the NAS component; the main actors are the carer and the consumer (we suppose that both actors have already registered in the AoD platform):

1. The carer accesses the Network of assistance services page (Figure 20) and wants to set up the network of assistance services on behalf of a consumer.

2. The carer searches for the consumer based on their name/email and requires permission to set up his/her network of assistance services via an email.

3. The specific consumer accesses his/her email account and accepts (or rejects) the carer’s request (Figure 23).

4. The carer accesses the AoD page (tab) in which he/she can configure the network of services and selects the services that the consumer needs, using the structure step-by-step search (wizard), or the search facility (Figure 24).

5. In the final step, the platform presents to the carer the services that he/she has selected ordered by category (Figure 25); the platform asks the carer to confirm his/her selection and gives him/her the opportunity to add more services, if desired. Also, the carer can purchase one or more services from the selected ones, and store other selected services in a “wishlist” by clicking on action buttons.

6. The consumer receives an email notification every time the carer purchases a service on behalf of him/her.



41

Figure 17: Carer dashboard

Figure 18: The carer selects some services exploiting the guided process



42

Figure 19: Final step: overview of selected services

4.4 Development and testing plan In this section, we provide the development and testing plan of the NAS component.

Planned delivery date Involved SP

First (complete) version of prototype 30/1/2016 SP2

Technical testing and bug fixing 15/2/2016 SP2

User testing February to April 2016 SP4

Revised NAS prototype July 2016 SP2



43

5 Installation guidelines

Given that the component “Network of Assistance Services” (NAS) is an extension of the AoD platform, it inherits the software dependencies of the AoD platform such as a database server (MySQL, SQLite, PostgreSQL), an application server (apache and wsgi module), the python version 2.7 and the Django framework. For more details, please take a look in Annex II of the deliverable D205.1 already submitted. The Assistance on Demand (AoD) platform includes a mechanism that provides the capability to its administrator to activate/deactivate some components, including the “network of assistance services”. Indeed, the administrator has to access the admin site of the AoD via a web browser which is located at the “{ip_address}:{port}/admin/” url and provide his/her credentials (admin sets them during the installation of the Django project).

Figure 20: Login in administrative panel of AoD

After the administrator’s authentication, the administrator is directed to the landing page of the AoD administrative panel that consists of some blocks such as the App, Authentication and Authorization and Sites (see Figure 27). When the administrator accesses the App> Components link, a list of customized components is presented (Figure 28). By clicking on the link network_of_assistance_services, the administrator can deactivate the Network of assistance services component if he/she unchecks the Is enabled checkbox and clicks on Save button ( ).



44

Figure 21: Landing page in administrative panel of AoD

Figure 22: List of AoD components



45

Figure 23: Deactivation of the Network of assistance services component

Figure 24: List of supported categories



46

Furthermore, the administrator can update the registered categories of services or manage the supported relationship among the categories and their subcategories either from the admin panel or the database. In case that the administrator prefers the administrative panel, he/she must follow the App> Categories link (Figure 30). Afterwards, the administrator can insert a new category by clicking on the Add categories button or modify an existing one by clicking on the ID column of a specific category (Figure 31).

Figure 25: Change the parent category of the Transportation category



47

6 Conclusions

In this deliverable, we have elaborated the functionality provided by AoD platform to carers. AoD allows the carers to select, potentially purchase and configure services that will be consumed by the user/ consumer they care for (following their authorization). Furthermore, AoD guides the carer through a wizard to select services from a structured set of services to avoid neglecting a certain aspect of life. To our knowledge, this feature is not supported by any other platform at the moment. Additionally, AoD allows the administrator of the platform to define the set and order of the supported categories and sub-categories supported by the NAS component. This way, the presented component can be flexibly configured to support any user group. It is reminded at this point that NAS, as part of AoD, is offered as open source at https://github.com/silop4all/aod. We presented indicative use scenarios which were analysed to draw the system requirements which in turn have driven the specifications of the NAS component. Finally, we present the NAS component installation guidelines to allow the prospective administrators exploit the flexibility and features of NAS. Future work includes the testing of the specific functionality in the 2nd evaluation iteration and integration of feedback received.


D205.2 Consumer/Family/ Professional configurable AOD

Documents

Transcript of D205.2 Consumer/Family/ Professional configurable AOD