VICINITY Stakeholders Drivers and Barriers released, Requirements extracted

VICINITY Stakeholders Drivers and Barriers released, Requirements extracted

stake0

Many of the stakeholders are facing decisions as to adaptation of new technologies, and decisions on matters they have little or no knowledge about. In today’s dynamic world with so many large disruptive approaches and changing business models, it is difficult for decision makers to identify, prioritise and fully adapt and trust the new opportunities beyond viewing them as limitations.

The main challenge of moving from a plan- and frequency-based working method in public and private environments towards a conditional-based approach and work method is the amount of data generated. This, in turn, would lead towards continuously adjusting and evolving ways of performing tasks and reacting to operational changes in the public and private sector. This is relevant to all VICINITY intervention domains: Energy, Building, Transport and Healthcare.

stake1

Service rollouts provided by public entities require long implementation times and demand for such services naturally lags behind. Shared economies and new ways to deliver services could be enabled by the VICINITY solution in order to speed up the rollout of services as well as shorten implementation times. For example, the VICINITY consortium aims to demonstrate an extendable service for sharing available parking spaces through use cases at the pilot site in Tromsø, Norway.

Buildings are the objects that society spends most of its critical resources on, such as energy and capital. The VICINITY solution could facilitate ways to optimise these costs and enable better operations and management of these facilities while involving end users.

At the pilot site at the Oslo Science Park in Norway , VICINITY will test use cases that collect and combine information on energy systems and smart parking to find new and better approaches to some of these issues through the interoperable approach VICINITY would provide.

The pilot in Martim Longo, Portugal is focused on the transversal energy domain and municipal buildings management. The energy generating and energy consuming components could potentially form a municipal-scale smart-grid enabled by VICINITY. It aims to demonstrate value-added services that could be enabled through the VICINITY framework based on a renewable energy generation infrastructure. The aim is to cross leverage and create value through community-scale VICINITY enabled interoperability.

 

stake2

Building: Data capturing and sharing

Organizations are often characterised by the lack of systematic data capture and missing tools for handling complex data structures. Better information about the environment and the resources available and consumed should support optimal usage of the resources through data sharing between tenants and building facilities. IoT as a tool allows building owners to measure properties of building's; performance automatically. There is a potential to optimise their maintenance activities in small repetitive tasks. Overall better information about environment and resources should support optimal usage of the resources through data sharing with tenants.

 

stake3

Transport: Resistance and responsibilities

Barriers could include the lack of willingness of residents to share their parking space when not used. Complex ownership relationships and responsibilities can inhibit deployment of parking solutions. Bringing the IoT to the transport domain opens the door to new parking sharing services, which benefits visitors, parking space owners, rental companies and building owners/management.

 

stake4

Healthcare: Technical and social

For the Healthcare related use cases, it is difficult to convince elderly people to install IoT devices/sensors in their homes and to train them on their usage including handling and sharing of sensitive personal data. Drivers for the younger generation include the proliferation of affordable new technology equipment for fitness use, wider use of social networks and sharing of personal data. There is greater demand from the professional services providers by specialised staff (pathologist, dietitian) for health data monitoring for better services provision.

 

stake6

Energy: Communicating advantages

Optimisation of energy generation and consumption through the use of sensor data across domains promises positive outcomes. It is difficult to list all of the benefits that could be obtained upfront and quantify the synergies. It is widely anticipated that greater cross-domain interoperability would allow for the overall energy cost reduction and new services to evolve; Real-time data and monitoring promise a greater impact on consumers energy-resource use-patterns with a more efficient and rational use of energy. The common concern in IoT deployments are the ethical issues of collecting data within buildings and potential use of information related to people’s behaviour.

 

Overall, privacy and security issues, trust, complexity, data ownership and compatibility concerns are among of the most frequently raised concerns. According to the interviews, stakeholders' expectations become apparent from trying to understand stakeholders perceptions of the strengths and weaknesses of the proposed solutions. The following statements summarise the general perception of VICINITY by stakeholders:

“Strengths: efficient, time-saving, minimising environmental impact, cost saving and providing better quality of life”.

“Risks: Loss of privacy and security, compatibility, complexity and legislation, dependence on technology, disruption of existing business models; complexity, developing legislation regarding ownership of data”.

VICINITY Requirements elicitation

There are three types of requirements in VICINITY that are relevant for system design. The table below outlines the types and levels of requirements while identifying some considerations. Sources of the operational requirements in VICINITY were stakeholder interviews, workshops and advisory board members and the extended partner's networks.

 
stake5

In respect to the Business Requirements, VICINITY has defined several use cases that will be addressed in the different pilots. Interviews were conducted with a number of stakeholders, and the outcomes have taught us a lot about identifying business requirements and features that will be required in the VICINITY platform. These requirements will shape the final platform. To achieve this goal, tools based on SysML will be applied and used for testing.

The specifications will also be used to identify the system components of the VICINITY platform. This includes abstraction of physical devices and services, and best practise related to security, privacy, user experience, performance, availability and maintainability fields. Furthermore, the specifications will influence implementation of internal interfaces between the VICINITY components. The same applies to external interfaces available for surrounding systems, including adapters for integrating IoT infrastructures. These infrastructures may consist of both devices as well as third party components providing value added services to the VICINITY ecosystem.