Governance Scope
Study provisioning, metadata lineage or access controls in your environment.
At Review
Do IT and QA accept the control design?
Clinical / Governance and Custom Work
Fix Study Setup, Metadata or Access Bottlenecks.
We standardize study provisioning, document data lineage or build a custom workflow. Choose the platform controls or development work you need, with tests, documentation and handover included in the scope.
For Biometrics operations, IT, QA and quantitative sciences leads
The Engagement / Governance and Custom Work
What Your Team Receives.
Select the platform controls or custom workflow you need; these are separate scopes. Agree the selected deliverables and review criteria in the scope.
Custom Build Scope
A workflow specification and source for the agreed bespoke implementation.
At Review
Does the build meet the named user need?
Review Evidence
Specifications, tests, change records and acceptance criteria for the selected work.
At Review
Can each deliverable be reviewed against a written criterion?
Ownership and Handover
Configuration, operating guidance, training and agreed support responsibilities.
At Review
Is there an owner for operation and future changes?
Two Distinct Engagements
Start with the Constraint in Your Operation.
01 / Platform and Governance
Metadata, Governance and Clinical Cloud
When study setup, inconsistent access or unclear lineage delays the team, establish the platform controls before adding another automation.
- SAS Management Console administration for the existing estate
- Study provisioning under approved procedures
- Metadata lineage and access-control documentation
- Client-owned Azure or AWS architecture, with controls defined for your framework
Best for: platform owners, biometrics operations and IT/QA leads responsible for the study environment.
Review the Governance Deliverables →02 / Bespoke Delivery
Custom AI for Quantitative Sciences
When a named service does not fit, scope the workflow with the people who own its inputs, review its outputs and approve its release.
- A design tied to agreed acceptance criteria
- Implementation inside your existing environment
- Source code and validation documentation delivered together
- Training, operating guidance and a controlled handover
Best for: quantitative sciences and programming leaders with a defined bottleneck and a named reviewer.
Review the Custom Deliverables →Governance Scope
What You Receive.
What You Review.
Agree on the environment, ownership and acceptance before implementation.
Metadata, Governance and Clinical Cloud
You Provide
Metadata server access, the provisioning SOP, a cloud tenancy you own and your security policy.
You Receive
Provisioning automation, lineage reports, a reference architecture in your tenancy and access-control documentation.
Who Signs Off
Your IT and QA leads accept the architecture. Provisioning runs under your identity system and approved procedures.
Custom Development, Implementation and Deployment
You Provide
The workflow, environment, acceptance criteria and a named reviewer.
You Receive
A scoped design, the build with source code, validation documentation, training and handover. Deliverables and ownership are recorded in the statement of work.
Who Signs Off
Your change-control board approves the design. Your reviewer accepts each deliverable against the agreed criteria.
Before You Commit
Bring the Workflow and the Review Requirements.
Start with the platform constraint or custom workflow. Identify dependencies and review responsibilities, then decide whether a separate assessment is needed before a build. Governance work can be commissioned independently.
Prepare a Governance or Custom Scope →Clinical / Your Next Decision
Choose Governance or a Custom Build.
Identify the constraint first. Agree whether the work is platform governance, custom development or a sequenced combination, then document the deliverables for that scope.
Built for Your Team to Operate.
Receive the agreed source or configuration, specifications, test records and operating handover. The statement of work identifies client-owned deliverables, existing INNOVIZZ methods, third-party licenses and support terms.