Education & research | Modelled case study
Preserve provenance across a multi-university research consortium
Can collaborators prove which institution, instrument, pipeline, and researcher produced each dataset version?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Research IT · Principal Investigator · Data Steward functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A university or research consortium combines student systems, federated identity, shared instruments, data repositories, partner institutions, and long-lived research records.
What is at stake
Open collaboration must coexist with durable privacy, research provenance, grant obligations, and identities that span institutions with different change windows.
Situation
Research data is copied, transformed, and re-hosted across institutions while identity, software, and signature context is lost.
Event that forces action
New consortium, reproducibility requirement, IP dispute, or regulated-data collaboration.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
partner datasets
research transformations
shared analysis platforms
publication and archive evidence
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Research data is copied, transformed, and re-hosted across institutions while identity, software, and signature context is lost.
Frame the decision the owners must make
Can collaborators prove which institution, instrument, pipeline, and researcher produced each dataset version?
Apply QNSI to the controlled boundary
Use QNSI-supported signatures and inventory identifiers to bind datasets, instruments, pipelines, institutions, and approvals.
Leave the team with a concrete result
A consortium provenance manifest showing custody, transformations, signers, software versions, and unverifiable contributions.
Prove the result in the organisation's environment
Partners agree authorship, ethics, data-use, export, retention, identity, and reproducibility rules.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A consortium provenance manifest showing custody, transformations, signers, software versions, and unverifiable contributions.
Independent validation boundary
Partners agree authorship, ethics, data-use, export, retention, identity, and reproducibility rules.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.