The series of sequence diagrams presented here outline the lifecycle of a FRIDGE instance and project.
Project Initialisation¶
Before deploying and using a FRIDGE instance, the project must get approval for the use of sensitive data from the Data Owner and receive an allocation of resources to use from the FRIDGE Hosting Organisation.
FRIDGE provisioning¶
After the Project Initialisation a FRIDGE instance may be deployed. The TRE Operator Organisation triggers the TRE Administrators and Hosting Provider Administrators to deploy the TRE (if it isn’t already), FRIDGE instance, and connect them. Once this is complete, the Principal Investigators will be informed the FRIDGE instance is ready to be used.
FRIDGE research loop¶
With the TRE connected, the research team can now dispatch jobs to the FRIDGE instance.
The Principal Investigators are able to upload the sensitive input data to immutable storage.
The Safe Researchers can now work using FRIDGE in the loop,
Identify question
Design and submit job specification
Check job progress
Retrieve outputs
FRIDGE teardown¶
When there is no longer the need for a FRIDGE, the Principal Investigators request the instance teardown. The TRE Operator Organisation instructs the TRE Administrators and Hosting Provider Administrators to conduct the teardown.
Project termination¶
Finally, with the teardown complete the TRE Operator Organisation and FRIDGE Hosting Organisation must finalise the FRIDGE allocation. Guarantees that and sensitive data has been deleted (or is otherwise unrecoverable) must be passed back to the TRE Operator Organisation and Data Owner to meet their data protection and data sharing agreement obligations.