IT systems · Practical guide

Validating aiti-suite: linking document versions, process decisions and training

An approved SOP and closed change record do not show that every affected employee has a training record for the right revision. In aiti-suite, trace the relationship between document control, forms and training. Test the actual handovers between SOP-Guard, FORM-Guard and SKILL-Guard against independently specified expectations.

Table of contents

At a glance

How do you validate aiti Life Science Suite?

Validate the intended use of the installed aiti modules and their connections. Check supplier packages for version, prerequisites and coverage. Add evidence for document revisions, form decisions, roles, training assignments and operation of the supplied environment. A delivered virtual machine or general validation promise does not establish that the full process connects the correct data and decisions traceably.

  • The current product family is called aiti-suite and includes SOP-Guard, FORM-Guard, and SKILL-Guard.
  • The supplier describes a web-based deployment as a virtual machine. Record who is responsible for operating it.
  • SOP approval, form completion, training certification, and activity decision have different meanings.
  • A review-based expected comparison demonstrates stronger evidence of compliance than an isolated final yield.

1. Product family, modules, and operating mode to be clearly named

The product family under the search term "aiti Life Science Suite" is referred to by the manufacturer as "aiti-suite". SOP-Guard is used for document management, FORM-Guard for form and quality processes, and SKILL-Guard for training management. The modules are offered individually or in combination. Therefore, a standalone SOP-Guard installation does not automatically constitute the complete trio integration.

The suite page describes a web application as a virtual machine operated either within the company or at a data center. For SOP-Guard, the manufacturer explicitly identifies a private cloud as a potential installation location. This does not permit the inference of a general SaaS model. Document the environment, modules, version, data storage, infrastructure ownership, and maintenance scope of your contract.

This article addresses the use of AI in human medicinal product GMP processes. The European Commission provides relevant guidance through Annex 11, as well as Chapters 1, 2, and 4. Other life sciences areas require separate classification. A manufacturer designation including GxP or FDA does not automatically establish which requirements apply to each of your data sets.

Sources: [1] [2] [6] [7]

2. Compare supplier packages against our own process

The public module descriptions specify validation packages comprising installation documentation, test case documentation, and risk analysis. This forms a basis for planning. The actual version, components, configurations, and conditions covered by a delivered package must be derived from its contents. A product specification with a GAMP category does not address this question for the customer process.

Align appropriate evidence to your requirements and identify remaining gaps. For example, a supplied test may verify general form functionality without addressing your multi-stage approval process. Conversely, a function adequately supported by evidence does not require retesting solely because the evidence originates from the supplier.

The following internal assistance document separates components and transitions. It prevents treating the provision of a virtual machine as a complete technical justification or a single module validation as coverage of the entire suite.

Scope – Work aid for modules and shared operation
ComponentPublicly described functionOwn validation within the intended use
SOP-Guard Create, review, approve, distribute, and archive documents. Correct revision, authorization, recipient group, and future readability.
FORM-Guard Assigned form sections, routing, deadlines and escalation. Appropriate decision-making steps, mandatory information, and exception handling.
SKILL-Guard Roll-based training programs, training matrix and learning progress. Complete designated personnel, appropriate content, and obtained evidence.
VM and Integrations Web application and directory service, for example Active Directory via LDAP. Environment, identity assignment, authority, and proven restoration.

Sources: [2] [3] [4] [7]

3. Document approval, efficacy, and distribution separation

SOP-Guard describes the creation, review, release, distribution, and archiving. The industry overview complements versioning with history and links to changes, deviations, and CAPAs. For your validation, it should be clearly defined how a new revision proceeds through this process and which version may be used at any given time.

Prepare a document with clearly distinguishable revisions. Verify the authorized approval pathway and access rights for a standard user role. Can this individual identify the currently valid edition? Is historical evidence of the previously applicable edition still comprehensible? A search based solely on document title is insufficient when multiple revisions have similarly named titles.

An approved change may require additional actions prior to its specified effective date. Such actions may include appropriate training or a controlled transition. This assessment should be based on the actual change, not automatically triggered by any editorial correction. Evaluate the internal process including the absence of a prerequisite, without asserting unproven software safeguard mechanisms.

Sources: [2] [5] [8] [9]

4. Link form fields to professional judgment decisions

FORM-Guard processes, among other things, CAPA, change, and deviation management workflows. The module description states that personnel edit the assigned form section in accordance with their responsibilities, and the form is then forwarded accordingly. Authorizations, deadlines, and escalation levels are configurable. These functions should reflect the professionally approved workflow.

Therefore, for each step, specify the required information, who evaluates it, and what occurs in the case of rejection. Fully completed fields do not constitute a viable root cause analysis. Similarly, forwarding a form does not demonstrate that an independent decision has been made. Verify the absence of information, an inappropriate operator role, and a justified rejected decision.

Widgets and reports can display the current processing status. Define which status meaning a report should convey. The statuses "complete entry," "submitted for decision," and "professionally closed" must not inadvertently overlap within the same process. For quality-related actions, reasoned evaluation—including mandatory effectiveness verification—remains decisive.

Sources: [3] [5] [9] [7]

5. Determine training requirements independently of the completion report

SKILL-Guard describes training plans by job role, department, or competency, along with a training matrix aligned to organizational units. These mechanisms can support assignment decisions. Verify whether they fully reflect your actual needs by comparing against an independently defined workforce group and the associated responsibilities.

Consider attendance, role changes, coverage, and departure. Upon a role change, it must be demonstrable which existing justifications remain valid, which new requirements arise, and which assignments are no longer applicable. The presence of an employee in the closing report by chance does not automatically imply membership in the required group. If an assignment is missing, the affected individual must not be silently removed from the required group, thereby improving coverage metrics.

Chapter 2 of the EU GMP Guideline requires need-based initial and ongoing training, along with periodic evaluation of its practical effectiveness. An electronic completion record initially verifies the defined training process. Whether a person is authorized and practically competent to perform a specific task remains a separate professional judgment. An LMS status should not be used without an appropriate procedural framework.

Sources: [4] [10] [7]

Further reading:

6. Test example: The correct revision and the correct denominator

The following example does not constitute a completed product test. Amendment CH-24 pertains to SOP-P12 Revision 4. The pre-defined target group consists of A, B, C, and D. For this case, the approved procedure requires a valid training documentation prior to the defined date of activity commencement. A general obligation for mandatory refresher training for each SOP amendment is not derived therefrom.

A and B have appropriate documentation for Revision 4. C has documentation only for Revision 3; no equivalence decision is in place. D is new and still under review. E has completed Revision 4, but is not part of the required group. The original personnel list and the revision requirements remain as independent references.

The test compares the actual report, assignments, and associated document statuses against this reference. If a form process is closed despite the fact that the internal closure process still requires additional steps, this shall be evaluated as a finding. The appropriate technical or organizational control must be demonstrated for the specific workflow.

Expected results for training records by revision
PersonIn the required group?Existing test documentationTreatment in the as-tended comparison
A Yes SOP-P12 Revision 4 Appropriate evidence.
B Yes SOP-P12 Revision 4 Appropriate evidence.
C Yes Only Revision 3; no equivalence decision Open for revision 4; historical record available.
D Yes No final conclusion yet Open; visible indication of missing compliance.
E No Revision 4 completed Exclude it from both the expected denominator and the number completed.

Sources: [2] [3] [4] [10] [8]

7. Verify roles, signatures, and identities across module boundaries

The product pages reference electronic signatures, audit trails, and role-based access. Crucially, it is essential to define which actions a person is authorized to perform within a specific process. Read-only access to a SOP, editing of a form section, and approval of a quality decision should be established and reviewed in accordance with functional responsibilities.

The documented LDAP integration opens up an additional validation area. Determine how users are uniquely assigned and which changes from the directory are actually implemented. Cases such as a disabled directory account, modified group membership, and a proxy representation are distinct scenarios. Expected behavior and responsibilities are defined prior to testing; automatic processing is not required.

For electronic signatures used, verify the intent and binding association to the correct document or form version. Any subsequent modification should be assessable and traceable within the prescribed procedure. Technical authentication alone does not establish authorization or confirm the specific action or statement affirmed by the individual. Annex 11 addresses these controls in the context of access and electronic signature.

Sources: [5] [1] [7]

8. Clearly document historical events and inherited evidence

During an introduction, documents and training records are often transferred from existing archives. Prior to transfer, clearly define which information must be retained: for example, name, content, revision number, date, and original evidence linkage. Not every historical dataset contains the same level of detail. Gaps should be assessed visibly, rather than inadvertently introducing a new professional conclusion during import.

An old closing statement should not appear without appropriate foundation as evidence of current training under the latest revision. Test not only complete datasets but also ambiguous person identifiers and missing version references. A successful import does not automatically validate the correct interpretation of transferred datasets. Retain the original reference for comparative purposes.

For export and storage, you maintain a complete workflow through the relevant modules. Can a subsequent reader identify which SOP was in effect, which formulation decision was made, and on which training documentation it was based? The scope and retention period depend on the process. A random collection of PDF files or a current dashboard status does not automatically substitute for this traceability.

Sources: [2] [3] [4] [7] [8]

Further reading:

9. Assess modifications and restoration of the linked process

Changes relate not only to software versions. Even a form field, a group, an escalation rule, or a document assignment can affect the validity of the evidence. Assign each change to the relevant requirements and evaluate ongoing and historical processes. A new rule must not be silently accepted as justification for an outdated closure.

Leverage appropriate supplier documentation and supplement targeted reviews of your own process. Unaltered functions should be considered when changes to their data or prerequisites occur. Conversely, a system update does not necessitate a blanket reexecution of all tests. Critical is a transparent evaluation of the remaining coverage.

The operation as a virtual machine makes responsibilities for backup, recovery, and maintenance particularly concrete. Verify that the intended recovery provides a consistent state of application, data, and required relationships. A standalone server is insufficient for this purpose. Coordinate with the operator and supplier to define how roles, interfaces, and relevant historical activities will be reviewed thereafter.

Sources: [1] [2] [7] [8]

10. Preparation and Checklist for QA and IT

Begin with a typical change process and its actual transition points. QA defines the required revision, decision, and training needs. Document owners and training coordinators determine content, target groups, and existing evidence. IT describes the environment, identities, integrations, and operational responsibilities. The system owner consolidates these inputs with supplier documentation.

The effort depends particularly on different formular pathways, role models, legacy data, and module integrations. For a small and medium-sized enterprise (SME), therefore, a manageable and representative selection of variants is helpful. It must capture critical differences, rather than simply counting a large number of similar documents. Open professional guidelines should be clarified prior to the development of a comprehensive test catalog.

  • Capture module versions, VM environments, and contractual operational responsibility.
  • Assign supplier packages to their actual coverage of requirements.
  • Document approval, efficacy, and necessary supporting actions to be defined.
  • Describe formulation steps with responsible parties, information, and acceptance criteria.
  • Determine the training target group and revision requirements independently of the results report.
  • Review user, group, and signature behavior based on targeted negative cases.
  • Migration, history and export with original references compared.
  • Define how changes are assessed and how the full context of the evidence can be restored.

Sources: [7] [1] [10]

Project experience and collaboration

Trace an SOP change across the aiti modules

We start with a change affecting an SOP and its associated training. With QA, document owners and IT, we establish which revision applies to which users, then trace that rule across the aiti modules in use. A missing assignment may need a simple correction. In other cases, several handovers between documents, forms and training need revision. We use supplier evidence where its version and test scope match, and assign an owner to each open issue.

Frequent Questions about the aiti Module Integration

What is included in the aiti Life Science Suite?

The manufacturer refers to the suite as aiti-suite with SOP-Guard for documents, FORM-Guard for form processes, and SKILL-Guard for training. The modules are available individually or in combination. Prior to validation, clearly define which modules are actually installed and integrated together. A product family designation does not constitute evidence of the specific functional scope of the environment.

Sources: [1]

Is the aiti-suite automatically a SaaS solution?

Public disclosures describe a web application hosted on a virtual machine; the manufacturer of SOP-Guard also references a private cloud. Whether your offering operates as a SaaS must be determined for the specific deployment scenario. Clearly define the location of installation, operator, data hosting, and scope of maintenance. Browser-based access alone does not indicate how operational responsibilities are distributed.

Sources: [1] [2]

Does the provided validation package replace the company's own documentation?

A suitable package can provide key evidence. Compare the version, prerequisites, scope, and results against your requirements. Additional documentation may be necessary for internal workflows, roles, integrations, or operations. The general manufacturer statement "validated" does not replace this alignment. Similarly, it would be unnecessary to completely discard existing, relevant documentation without a sound rationale.

Sources: [2] [3] [7]

Must every employee be retrained after every change to an SOP?

No. The need for training depends on the content, impact and affected tasks. In this example, revision 4 was explicitly set as a new requirement for four people. This case does not establish a general rule. Record whether new training, another measure or justified recognition of existing evidence is appropriate. Base the assignment in the software on that decision.

Sources: [9] [10] [4]

Is an approved SOP immediately effective?

Not mandatory. According to EU GMP Chapter 4.3, instructions are authorized by authorized personnel and a validity date is established. Authorization and the start date of validity may differ, for example in the case of a prior training phase. At the specified time, verify access, version, and any required supporting actions. A general technical blocking function of the suite is therefore not demonstrated.

Sources: [8] [2]

Why is a high training rate not enough?

The ratio depends on who is part of the target group and which evidence is considered valid. An outdated review status may be professionally inappropriate; a person trained outside the target group may distort the figure. Therefore, verify personnel and content against an independent reference. Furthermore, a suitable electronic closing does not alone demonstrate practical competence for each task.

Sources: [4] [10]

Does the transfer in FORM-Guard already constitute professional authorization?

Not solely. The manufacturer's description explains the forwarding procedure following processing of the assigned form section. The evaluation and authorization behind this must be defined by your process. Review mandatory information, rejections, and unauthorized processing using clear acceptance criteria. A fully completed form may still contain an open or inadequately justified quality decision.

Sources: [3] [9] [7]

How do we handle outdated training records lacking clear revision?

Obtain the original information and assess the gap. A system import shall not implicitly claim completion of training for the current version. Clarify the verifiable scope, the relevant activity, and where appropriate, any necessary additional actions. Perform migration validation using unambiguous test datasets and document the decision; do not invent missing historical data.

Sources: [8] [7]

Does a successful start of the restored VM suffice?

It first confirms that the environment starts. For the intended process, additional harmonised data and relationships are required: document revision, form workflow, user, and training certification. Review representative processes as well as required roles and integrations. The scope and extent are determined by the organisation's specific recovery requirements; a fixed, general test coverage cannot be inferred therefrom.

Sources: [1] [7]

What should we prepare for a realistic effort estimation?

Compile modules, operating models, roles, form variants, and existing supplier documentation. Select a change process with document revision and independently defined training recipients. Enhance the legacy data and interface pathways. This enables genuine differences to become visible. Ambiguous responsibilities or revision references typically generate more clarification needs than a large volume of similarly structured documents.

Sources: [7] [1]

Sources and review date

Source date: 6 October 2026. The manufacturer documentation describes the aiti-suite and its three modules, but does not provide a consistently unique current build number. Specific operational configuration, modules, and scope of supplier packages must be verified on a project basis. Regulatory reference: Human medicinal product GMP; other usage areas shall be assessed separately.

  1. aiti-suite: Product family and technical deployment
  2. SOP-Guard: Document Management
  3. FORM-Guard: Process Management
  4. SKILL-Guard: Training Management
  5. European Commission: EudraLex Volume 4
  6. EU GMP Annex 11: Computerised Systems
  7. EU GMP Chapter 4: Documentation
  8. EU GMP Chapter 1: Pharmaceutical Quality System
  9. EU-GMP Chapter 2: Personnel

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Secure your aiti process with comprehensible evidence

Daniel Herrmann Consulting helps you consider document control, form approval decisions, and training records as an integrated process. We assist with aligning existing documentation and conducting targeted reviews of remaining gaps.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →