##  1\. Introduction

The purpose of this deliverable is to provide a data management plan for
ENVISION. The data management plan describes how data is being collected,
stored, documented and shared and reused during and after the project. Various
types of (big) data will be collected in ENVISION: survey, case study and log
data.

We consider the data management plan to be a living document that has to be
updated over the course of the project. Some decisions in this document are
tentative since they require further specification of the tools and platform
in WP2 and WP3. The data management plan has interdependencies with the
research database (D5.1) and the informed consent forms (D4.3, D5.5).

#  2\. Data collection

The following data collections will take place in the different Work Packages
of The Envision project.

###  WP2 Flexible BMI Tooling

Both WP2 and WP3 will include three scopes of development. In the first scope,
tooling from WP2 will mainly involve downloadable templates, and hence will
not generate any log data.

In the second scope, tooling will include interactive tooling such as storing
and sharing business model ideas. At that stage, users will therefore store
their personal data which may be sensitive for competitiveness. For sharing
business model ideas with other users, access rights will have to be defined.
Specific measures on how to collect, manage and archive data for WP2 will be
defined during the development of the second scope.

###  WP3 Development BMI Platform

In the first scope, the platform from WP3 will collect log data on who visits
the platform through Google Analytics. The number of unique users and
returning users will be collected. Data will be collected on where users come
from, length of sessions, time spent on a page, on which page a user leaves
the platform, browser type, device type etc. Privacy sensitive data like IP
addresses are not being collected. The log data will be used for research
purposes, i.e. to compute descriptive statistics on platform usage and
realized dissemination levels. For these purposes, data will be aggregated on
such a level that they cannot be traced back to the level of an individual
user.

Users will be able to log in to the platform. Mandatory data to register are
date of birth and email address. Further information can be entered but is not
mandatory. These login data will _not_ be used for research purposes. They
will also _not_ be disseminated as open data to outsiders.

The first scope of the platform will include an _Idea challenge_ , where users
are challenged to solve a BMI problem for an SME. Depending on whether this is
based on real cases, data management issues will have to be addressed in the
design of the _Idea challenge_ .

Specific measures on how to collect, manage and archive data for WP3 during
the second and third scope are to be further defined.

Assuming the foreseen adoption rate of 400,000 SMEs, size of the data will
grow exponentially during the project.

###  WP4 Quantitative longitudinal research

Three waves of survey data will be collected through a European market
research agency. The collection of data in the longitudinal survey follows the
common practices of research agencies and/or the Dutch and Finnish statistical
offices involved in the project. Exact procedures for data collection are
specified in the quantitative protocol (D4.1) and informed consent forms
(D4.3). Survey data will comprise answers to the survey instrument developed
in WP4. Background demographics will be collected on gender, nationality,
industry sector etc. It should be taken into account that these background
demographics are on such level of aggregation that they cannot be traced back
to individuals. Data collected will be anonymized by the research agency and
made available to the researchers. After the project open data that will be
shared with the outside world will not be traceable to individuals or
companies, even due to small industry segments and dominance of individual
firms in a small industry sector. Data will be collected in SPSS and Excel
files.

###  WP5 Action design case research

BMI case descriptions will be collected in various formats. Exact procedures
for data collection are specified in the qualitative protocol (D5.1) and
informed consent forms (D5.5). Raw data will include interview tapes,
transcripts, videos, annual reports, photos and so on. The data has to be
available for qualitative analyses with tools such as ATLAS.ti for WP5
researchers. Some of the data will also be utilised by other WPs. Data
heterogeneity will be an issue.

For the 60 short cases, pre-existing data will be reused which has been
collected in an Excel-based database.

Figure 1 describes how we see WP5 qualitative research data builds up and
responds to differing purposes.

**Figure 1.** ENVISION research material and access rights.

#  3\. Data Storage and Back-up

###  WP3 Development BMI Platform

For the first scope, EVO’s subcontractor will host the platform and data.

For second scope and later, EVO will host the platform and store data
themselves in their self-administered server.

The second scope of platform development should specify how long data from
SMEs will be stored.

###  WP4 & WP5 Quantitative research & Case research

Datasets from both work packages will be stored in a research database to be
developed by the University of Turku (UTU) in task T5.1. The database defines
the access and use rights for the author, WP5 researchers and the consortium.
Public access will be defined later.

Prototype version 1.0 is being developed and hosted by the University of Turku
at _http://envision.utu.fi_ . It will be available to WP5 researchers for
testing early June 2015. By autumn 2015 the version 2.0 will be available to
ENVISION consortium partners. The database and associated website will be
continuously maintained during the time period of the project. The technical
and structural modifications will be continuously held according to the Grant
Agreement, internal consortium requirements, research protocols from WP4 and
WP5, and database needs.

The development environment for metadata database is an open source
environment, which is based on the testing platform Rasberry Pi, server Linux
Debian, database MySQL, MyPHPAdmin, PHP and web platform Wordpress at the
University of Turku.

The public environment runs on a Webhotel of University of Turku's IT
Services. It contains database MariaDB (MySQL compatible), MyPHPAdmin and web
platform Wordpress on Linux Debian server.

For the WP4 survey data, personal information will not be collected by the
consortium but by the research agency and thus not be stored.

For WP5, the case studies may be fully open for dissemination purposes based
on rules as formulated with regard to informed consent, in which case personal
data from participants is being stored and disseminated. Case studies may also
be anonymized, in which case personal data is not to be disseminated. Personal
data from the case studies will be stored encrypted.

#  4\. Data Documentation

All involved researchers are aware that generating metadata is highly
important during data collection.

**WP2 & WP3 BMI Tooling & Platform **

To be defined during the second scope of developing tooling and platform.

###  WP4 Quantitative survey research

Metadata will be collected in the form of labels in the SPSS files. Variable
names will include question numbers that are identifiable in the questionnaire
document. For computing statistics in SPSS, syntax files will be stored
including a short text-based description on what is being computed. For
conducting SEM analyses, researchers should maintain a logbook that describes
the steps being taken so that they can be reproduced. Logbook should be stored
on a separate folder on the Google Drive.

###  WP5 Action design case research

Each ENVISION case study contains multiple data documents (such as voice
recordings, memos, videos, photos, transcripts, case report etc.). The access
rights to each document has to be defined, by the responsible researcher, so
that it is accessible either to general public, to consortium, to WP5
researchers or to the responsible researcher.

However we need to provide meta-level information about all research documents
for the consortium members to be able to search the database and identify
interesting documents from the whole database (even though he/she does not
have access to certain documents).

The following Metadata entity relationship diagram describes the meta-level
data.

ER diagram of the metadata database v1.0

Users of the database Companies in Cases Companies

  * User id, Int, NULL, primary key - Case_id,  M 1  \- Company_id, Int, NULL, primary key 

  

  * User role, text ((author, WP5 - Company_id - company_name, text researchers, consortium, public ) - address (street, city, country, mail, 

  

  * name, text phone) 

  

  * Organisation, text M - turnover, Int 

  

  * balance sheet total, Int 

  

1 1 1 - female, Yes/No/

M Cases -- family,no. of employees, Yes/No/ Int

  * Case_id, Int, NULL, primary key - Industry, text 

  

  * Case_name, text - Confidentiality, text M M 1 - Case_description, text, 

  

Research Documents - Case_Responsible(refers to user id) researcher_id, Int 1
1

  * Doc_id, Int, NULL, primary key - Case_type, text (Short case, ADR) 

  

  * Doc_name, text - Case_driver of BMI, text 

  

  * Doc_version, text (dr#, fv) - Case_BMI tool, text 

  

  * Doc_date - Case_Main message towards SMEs, text M M 

  

  * Case_id, Int (referring key) - Case_Suggestions for usage of the case 

  

  * Doc_Description, text material, text Contacts/Interviewees 

  

  * Doc_author, Int (refers to user id) - Case_Lessons learned, text \- Contact person _id, Int, NULL, 

  

  * Doc_language, text - Case_use_rights, text (author, WP5 primary key 

  

  * Doc_format, text researchers, consortium, public ) - Case_id, Int 

  

  * Doc_size Int 

  

  * Doc_location of master, text - company_id, text 

  

(upload link) 1 M Document classification -- Name,address (street, city,
country, mail,

  * Doc_use_rights, text (author, WP5 - Doc id, Int phone) researchers, consortium, public ) - keyword, text - Informed consent, Yes/No/ 

  

**Figure 2.** Entity relationship Diagram of the metadata database v1.0

UTU will develop the Metadata database structure according to the Figure 2.
The access to the database will be available at envision.utu.fi. The web site
contains the forms for adding and editing the data and a search engine for
browsing the data. During the summer the web site will be tested and adjusted
accordingly to the accumulated research data, which will be added to the
database by responsible researchers.

#  5\. Data Access

In general, data ownership is jointly shared among consortium partners.
Commercial exploitation of data is not foreseen.

**WP2 & WP3 BMI Tooling & Platform **

Data will be accessible to EVO project participants only through
username/password.

###  WP4 & WP5 Quantitative research & Case research

The data access, share and change rights are assigned according to the
ENVISION project's management decisions.

The responsible researcher of each case will take care of adding the meta-
level information to the database by using the 'add new data' forms at
envision.utu.fi.

The responsible researcher uploads the respective original research documents
to envision.utu.fi. If this is not possible (for instance because the research
data is not collected during the ENVISION project, or is owned by someone who
is not part of ENVISION project) then at least the metadata has to be provided
with information where the original, full document is located.

The naming practices of files have to be distinct in order to achieve a clear
structure in the database. Each file will begin with a short name given to the
case referring to the organization such as “SmartScope”. After this comes the
content related part of the file name such as “CEO interview transcript” or
“short case description”, and the version information referring to the day,
month and year, of the last alteration of the file.

Then the affiliation, version (dr =draft, fv = final version) and reviewer
initials if needed.

ENVISION_WP5_"case"_”content”_”date”_”affiliation”_dr#_”reviewer
initials”.filetype E.g. ENVISION_WP5_Rauma_Owner
Interview_25052015_UTU_dr1.doc

Both draft and final versions can be stored in the database, but remember to
include dr# or fv to the name.

The responsible researcher is responsible that the access rights to each
document are correct. The access rights are maintained via envision.utu.fi

The ENVISION consortium partners can search the data using the search tools
provided at envision.utu.fi.

The search result will show the metadata and provide 'upload' link to the
original research documents.

#  6\. Data Sharing and Reuse

**WP2 & WP3 BMI Tooling & Platform **

To be decided by General Assembly since it was not defined in the grant
agreement.

###  WP4 Quantitative survey research

Data gathered in the survey will be made openly available after the project
has finished and scientific papers have been published, once it has been
anonymized in such a way that it cannot be tracked back to individual
respondents, directly nor indirectly.

These data will be stored and made available in the 3TU.Datacentrum, which
complies fully with H2020 requirements. 3TU.Datacentrum is a Trusted Digital
Repository for technical-scientific research data in the Netherlands and
located at the TU Delft Library.

Data that we do not produce in the project (e.g. existing cases, existing
survey data, existing data from statistical offices) will not be made openly
available.

###  WP5 Case studies

Research Data that is not privacy sensitive will be available open access
through the data center mentioned above, after the project has finished and
scientific papers have been published.

Data gathered in the case studies will be made openly available as long as it
does not harm privacy or competitiveness of the business being studied. This
will likely imply that we will make interview summary reports available, but
not interview recordings.

##  7\. Governance

To safeguard compliance with all aforementioned data management decisions, the
following governance measures are applied.

WP leaders are responsible for adhering to the above specifications for their
respective work package. For the overall project, TUD will be responsible for
complying with the data management plan. All consortium partners are
responsible for making sure personnel working on the project have read the
data management plan and internalized the principles. Data management will be
on the agenda in all monthly executive board Skype meetings as of September
2015.

The data management plan is considered a living document. As specified at
various points in this deliverable, some decisions cannot be taken yet because
they require further specifications of for instance the WP3 platform and WP2
tools. Updates to the data management plan are to be made and circulated
within the consortium in M12, M18, M24, M30 and M36. Major changes in the way
data is being managed in the WPs should be specified then. Major changes or
discussion points that cannot wait shall be addressed in the executive board
meetings.

To evaluate the efficacy of the data management plan, we will conduct an
evaluation in M12. The evaluation will at least include:

  * WP2: Is the metamodel still consistent with what is being done in WP4 and WP5? Is updating the metamodel required? 

  

  * WP3: Is usage data of the platform being collected? Is it sufficiently aggregated to preserve anonymity? 

  

  * WP4: Is the survey data from first wave anonymized correctly and issued with unique identifier? Is the survey data being stored safely in the WP5 UTU database? Does the survey data include meaningful metadata (i.e. labels) that are understandable for outsiders? Do informed consent forms (D4.3) align with datamanagement plan? 

  

  * WP5: Is the instantiated WP5 UTU database consistent with the specifications in this document? Is data and metadata from the first cases being generated correctly and understandable for outsiders? 

  

Do informed consent forms (D5.5) align with datamanagement plan?

  * WP5: Should we update the metamodel for data collection (i.e. Figure 2 in this deliverable) to include the method used to collect data, time period covered by the data, geographical area covered by the data? Should the metamodel for data collection be updated to meet standards like CERIF (Common European Research Information Format) or Dublin Core metadata standard? 

  

24 August 2015

Page 14

For

_**ENVISION** _

_Empowering SME Business Model Innovation_

– Project

About ENVISION

In the current tough economic environment, business model innovation can be
the key to becoming or staying

competitive. To support European competitiveness and job creation, the
ENVISION project aims at activating

small and medium sized enterprises (SME) across Europe to re-think and
transform their business models

with the help of an easy-to-use, open-access web platform. Through this
platform, every small or medium

company, regardless of the country, sector or industry, will be guided in
selecting the right tools for their

business makeover. The platform is being built for the use of 20 million
European SMEs.

The ambitious goal of the ENVISION project is pursued by a consortium of nine
partners from seven countries:

Delft University of Technology (The Netherlands), University of Turku
(Finland), Innovalor Ltd (The

Netherlands), evolaris next level Ltd (Austria), University of Maribor
(Slovenia), University of Murcia (Spain),

AcrossLimits Ltd (Malta), bgator Ltd (Finland), Kaunas University of
Technology (Lithuania).

http://www.envisionproject.eu

http://www.facebook.com/InnovateBusinessModels

_https://twitter.com/InnovateBM_

; @innovateBM

Website:

Facebook:

Twitter: