CSVtoCSAPractical Software Assurance
SearchSubscribe
Menu

Fictional worked example · CSVtoCSA editorial

Training Management System

A qualification-status decision spanning curriculum effectivity, expiry, role mapping, and a manufacturing interface.

Published 12 September 2026 · Context updated 21 September 2026 · Version 2.0

All organizations, identifiers, test results and decisions in this example are fictional teaching material.

Information available and assumptions

Training requirements, curriculum effectivity and operator identity are authoritative. The receiving work-control system relies on the qualification status.

Scope and decision record

Standard case study record

Scope and decision fields

Read these fields before the detailed worked case. All organizations, identifiers, test outcomes, and decisions are fictional teaching material.

GxP Assessment
The system calculates whether personnel are qualified to perform a controlled manufacturing operation. Curriculum effectivity, completion, expiry, role mapping, and the MES status interface are GxP-relevant.
Change or Issue
A curriculum revision changes the effective version while a delayed interface message leaves an operator shown as qualified.
Functions Affected
  • Curriculum version and effectivity
  • Training completion and expiry
  • Role-to-curriculum mapping
  • Qualification-status interface and exception handling
Potential Impact
A person with expired or incomplete training could be permitted to perform regulated work.
Deviations / Known Issues
The fictional execution shows a stale qualified status during message-queue recovery. Release requires a fail-closed rule, reconciliation alert, and successful recovery retest.
In this example

Situation

A training management system sends operator qualification status to a manufacturing execution system. A curriculum revision and interface retry occur during the same shift.

Intended Use

The system determines whether an identified operator has completed the effective curriculum and remains within the approved training period for operation OP-21. The manufacturing system uses that status to permit or prevent operation start.

Failure Scenarios

  • An obsolete curriculum version remains effective.
  • Expired training is treated as current.
  • A role mapping excludes a required course.
  • A failed or delayed interface message leaves stale qualified status.
  • An override lacks authorized approval and audit history.

Existing Controls and Evidence

Role-based curriculum assignment, effectivity dates, expiry rules, interface acknowledgements, exception queues, daily reconciliation, and supervisor review exist. Supplier tests cover standard calculation logic but not the local curriculum, interface, or fail-closed behavior.

Evidence Gaps and Testing Approach

Script effective-version, completion, expiry, grace-period, role-change, and override rules with exact expected results. Challenge missing, duplicate, delayed, and out-of-order messages; interface downtime; recovery; and reconciliation. Use trained-user testing for curriculum assignment and exception resolution.

Validation Conclusion

The fictional recovery test shows a stale qualified status. Release is conditional on a fail-closed rule, aged-message alert, accountable exception ownership, and successful recovery without incorrect authorization.

Reassessment Criteria

Reassess curriculum rules, role mappings, interfaces, overrides, identity services, expiry logic, or incidents involving unqualified work.

Limitations and unresolved questions

Conditional use depends on fail-closed behavior, alerts and verified recovery. New role mappings, expiry logic or interfaces require reassessment.

Relevant regulations and guidance

These sources apply within their stated scope. The suggested worksheet fields, test designs and fictional decisions are practitioner recommendations, unless a source requirement is expressly identified. Completing a template does not establish compliance.

Computer Software Assurance for Production and Quality Management System Software ↗

Regulatory guidance / GMP guideline · United States · February 2026

Scope: Medical-device manufacturers assuring software used in production or their quality management system.

Relevance: For medical-device production or QMS software, supports selecting assurance activities from intended use, risk and available evidence. It is nonbinding guidance and does not determine other sectors’ obligations.

Status: Final / published · Checked 2026-09-21

Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.

Read source details and applicability →

EudraLex Volume 4, Annex 11 — Computerised Systems ↗

Regulatory guidance / GMP guideline · European Union · January 2011 revision

Scope: Computerised systems supporting activities in the applicable EU pharmaceutical GMP context.

Relevance: For computerised systems used in EU GMP activities, informs lifecycle, supplier and record controls. Confirm applicability to the actual activity; the example does not establish it.

Status: Final / published · Checked 2026-09-21

The Commission index confirms the January 2011 operative revision. The linked PDF could not be retrieved in this check; retained detailed section mappings need review against an authorized copy.

Read source details and applicability →
Was this useful? Leave feedback

Was this resource useful?

Tell us what helped and what could be clearer. Usefulness feedback does not establish technical validity or regulatory compliance.

Loading contribution options…

Questions and moderated discussion

Questions and discussion

What additional information would you need before making this decision?

Loading contribution options…

Suggest a correction

Sent privately to the editorial moderation queue. Your account email and correction are not published as a comment. Do not include confidential or personal information.

Resource: Training Management System

Loading sign-in status…

Correction details