In 2014 the newly appointed CSIO of Radboudumc was tasked to come up with a solution for researchers in line with the Board of Directors policy. During the exploration phase to really understand what researchers and their stakeholders needed, it became clear that
next to needs described in the VRE definition, the organization's care of duty (needs, requirements, and responsibilities) became a if not the driving force.
In the past 5 years the basic needs of researchers did not change that much, what dramatically changed was the care of duty of the organization. In the exploration phase it became clear that the three main drivers related to the care of duty of an Radboudumc were:
- GDPR
- Cyber security
- Cost control
The DRE as a concept was born and was defined as:
Digital Research Environment (DRE):
“innovative, cloud-based*, research ecosystem driven, flexible, and secure working environments to do research and meeting the needs, requirements, and responsibilities of all stakeholders”.
The collaboration under the name RSRCH won the European Tender for the DRE issued by Radboudumc. Based on Aridhia framework and Vancis infrastructure the RSRCH Platform was built.
2017 - DRE definition by NFU
On 2017-01-01 in a collaboration between
NFU Data4lifesciences WP2 & WP4, and SIG-PRIMA the document Reference Architecture Workspaces, corroborated by AcZie,
2018 - Lessons-learned: Sustainability, scalability, and collaboration are key
The DRE, as a place to process the digital part of research, was in the NWO grant application: National Roadmap for Large-Scale Research Infrastructure 2017-2018.
DRE, the Digital Research Environment, was developed at Radboudumc as a secure user-driven collaboration
platform bringing together data and tools for digital biomedical research projects. The DRE platform meanwhile supports a great variety of studies and is being piloted by all UMCs and several other research organizations.
.....
Radboud UMC DRE has demonstrated their potential to attract researchers as the infrastructure offers key
opportunities and assets relevant for academic and industrial researchers.
Source: NWO Elixir-NL Proposal-final.pdf
This, the evaluations of VRE/DRE solutions, and other l
essons-learned in 2018 underlined the need for co-development of a DRE; created by, for, and with researchers and stakeholders to ensure a viable solution for the research ecosystem as a whole.
RSRCH failed to deliver (not fulfilling the market vision, insufficient scalability, vision misalignment on predefined tooling and data models), they need tool and data agnostic solution) and Radboudumc decided not to renew the contract with RSRCH and to build its own DRE; the Azure DRE.
2019 - Emerging of anDREa Consortium, Azure DRE / myDRE
In 2019 Radboudumc, UMC Utrecht, and Erasmus MC joined forces. Starting with a letter of intent, followed by creating the anDREa Consortium to develop, maintain, and valorize the Azure DRE / myDRE.
2020 - Viable business model requires anDREa to be a commercial entity
UMCs are not in the business to develop, maintain, and valorize a DRE. The anDREa Consortium because of its legal constructs is limiting growth. Growth that is needed to ensure a viable, affordable, sustainable, and continuously improving service beyond the typical 3-7 years. In the best interest of all, it was decided that anDREa had to become a BV. But fully owned by the three founding UMCs: Radboudumc, UMC Utrecht, and Erasmus MC to ensure the alignment of anDREa BV with the needs of the ecosystem of which they are part of as well. Among many decisions to ensure this, was the decision that also Radboudumc, UMC Utrecht, and Erasmus MC would, with respect to myDRE, be a normal client with no extra privileges.
2021 - anDREa BV is born
As of 2021-07 anDREa BV is a legal entity and open for business for any organization that needs a Digital Research Environment: being able to create within one hour and manage Workspaces to safely work on data with own tooling, the compute, storage and the infrastructure needed, in collaboration; including with people external to your organization. Each organization uses their own Microsoft Azure contract (conditions and pricing) for the Microsoft Azure resources used, all data is stored and processed in the organization's own Microsoft Azure subscription, the organization's own license servers can be used, local support teams are well supported and can collaborate even across organizations if so desired.