Systems & Tools

Code: INFRA-PROV

The systems, tools and infrastructure that underpin research practice. This includes provisioning access, procuring software and hardware, ensuring secure storage, standardising templates, integrating tools into organisational systems, enabling automation and managing the tool lifecycle.

INFRA-PROV 1.0.0 Systems & Tools Infrastructure

The foundational systems and access required before research begins, including environment setup, tool provisioning, and baseline capability support.

INFRA-PROV 1.1.0 Tool Access & Readiness

G

INFRA-PROV 1.1.1

Ensure Tool Access Before Starting

Ensure access to tools for recruitment, scheduling, consent, transcription, analysis and secure storage.

  • tool onboarding documentation
  • clear ownership for each tool
  • monitored service-status and support routes
  • toolkit baselines for each research maturity level
G

INFRA-PROV 1.1.2

Environment Provisioning (Physical & Digital)

Provision required physical and digital environments.

  • research labs, observation rooms and usability spaces
  • secure laptops, microphones and recording equipment
  • remote testing tools with encryption
  • assistive technologies for accessibility needs

INFRA-PROV 2.0.0 Procurement, Evaluation & Licensing

Ensuring research tools meet organisational, financial and legal requirements.

INFRA-PROV 2.1.0 Procurement Rules & Evaluation

R

INFRA-PROV 2.1.1

Procurement & Licensing Requirement

Any tool handling research data must meet procurement, licensing, information security and legal standards.

G

INFRA-PROV 2.1.2

Tool Evaluation Guidance

Evaluate tools using criteria:

  • data protection compliance
  • service accessibility
  • cost effectiveness
  • exportability & interoperability
  • vendor security posture

INFRA-PROV 3.0.0 Templates & Standardised Artefacts

INFRA-PROV 3.1.0 Template Library

G

INFRA-PROV 3.1.1

Standard Template Library

Maintain a version-controlled template library including:

  • research plans
  • risk logs & non-conformance reports
  • consent forms
  • fieldnote sheets
  • analysis frameworks
  • playback decks

INFRA-PROV 4.0.0 Access, Security & Permissions

INFRA-PROV 4.1.0 Security Requirements

R

INFRA-PROV 4.1.1

Access Control & Security Requirement

Tools must enforce:

  • RBAC (role-based access control)
  • logging & audit trails
  • end-to-end encryption
  • secure credential management

INFRA-PROV 5.0.0 Tool Integration & Automation

INFRA-PROV 5.1.0 Integration & Workflow Design

G

INFRA-PROV 5.1.1

Integrating Research Systems

Integrations should reduce duplication, errors and manual effort.

  • recruitment → scheduling
  • consent → secure storage
  • repository → analytics tools
  • participant CRM → incentives systems
G

INFRA-PROV 5.1.2

Automation Opportunities

Support automation patterns including:

  • automated consent records
  • triggered incentive payments
  • automatic transcription routing
  • retention-expiry alerts

INFRA-PROV 6.0.0 Maintenance, Support & Lifecycle Management

INFRA-PROV 6.1.0 Lifecycle Planning

G

INFRA-PROV 6.1.1

Lifecycle Management Guidance

Each tool must have a documented lifecycle, including:

  • ownership
  • acquisition → review → deprecation phases
  • scheduled maintenance
  • exit / deletion plans

INFRA-PROV 7.0.0 Non-Conformance, Incident Reporting & Risk

INFRA-PROV 7.1.0 Incident Management

R

INFRA-PROV 7.1.1

Incident Logging Requirement

All non-conformances must be logged with:

  • date and time
  • description
  • severity & impact
  • mitigation & lessons learned

Glossary & Definitions

Tool Lifecycle
The stages a research tool moves through, from procurement to decommissioning.
RBAC
Role-based access control ensuring only authorised staff can view or modify data.
Integration Workflow
A defined pattern that connects two or more research tools or systems.
Non-Conformance
Any deviation from expected standards, behaviours or thresholds.

Templates & Artefacts

Change History

Version Date Summary of Changes Author / Owner
0.2-draft 2025-12-11 Restructured using A1 model; added integration, automation, lifecycle and risk sections. ResearchOps Governance Team