IT systems · Practical guide

d.velop Life Sciences: testing SOPs and training in dls eQMS

An SOP is approved, training tasks are still open and an old paper copy remains at the workstation. In dls | eQMS, follow the change through the base platform, licensed modules and configured workflows to actual use. The example helps smaller human medicinal product manufacturers identify useful supplier evidence and the local checks still needed.

Table of contents

At a glance

What does your organisation need to validate in dls | eQMS?

Assess the intended process on your particular d.velop documents installation, including the dls modules, roles, configurations and interfaces in use. Evaluate which supplier evidence applies and where gaps remain. Focus on transitions between document approval, effective status, training and CAPA. A PDF, training completion percentage or closed workflow represents only one part of the process.

  • dls | eQMS, d.velop documents and engamp are not interchangeable product designations.
  • Supplier certifications are accepted based on inspection object, version, and configuration.
  • Release, current document version, and individual training require separate decisions.
  • Electronic records and controlled copies must meet the respective audit purpose.

1. Determine the actual product combination

The former d.velop Life Sciences GmbH has been called Digital Life Sciences GmbH since February 2023. Its dls eQMS suite combines modules for document management, training and quality processes. For document management, the manufacturer d.velop documents is the basis. The earlier company name alone therefore does not refer to a clearly versioned application. Keep separate platform, modules, extensions and operating form.

The suite is described as being available for on-premise infrastructure and as a cloud-based offering. This does not necessarily indicate the specific contract covering your installation. Capture provider details and responsibilities for operations, identity management, security, disaster recovery, and changes. For a hosted system, for example, tasks such as role-based access assignment, document content, and user access decisions remain the responsibility of the organization.

A reliable public numerical version of the specific dls modules cannot be determined from the product pages. Therefore, obtain the installation inventory and corresponding delivery documentation. This uncertainty is practically relevant: A current product description may reveal features that are not included in your existing installation or license.

Sources: [1] [2] [3] [10]

2. Define the GMP process prior to the evidence package

First, describe the outcome upon which your organization intends to rely: for example, a valid SOP in use at the workplace, the appropriate training documentation, and a logically justified decision related to a corresponding CAPA. Identify input data, involved roles, relevant records, and limitations. A general objective such as "electronic quality management" is insufficient for this purpose.

This guide addresses computerized activities within the human medicinal product GMP domain. Annex 11 serves as the applicable GMP guideline; the scope and depth of validation evidence are justified based on usage and risk. Other application areas, such as medical devices or clinical trials, require separate evaluation. A FDA reference is not established solely by the product name or the manufacturer's industry.

The supplier provides a validation package including support for scope and risk assessment, as well as documentation of installed software and configuration. Verify the actual package delivered: What version, environment, requirements, test results, and deviations are included? Accept appropriate documentation with justified attribution. Subsequently, supplement customer-specific transition activities, rather than retesting standard processes.

Sources: [10] [9] [6] [14]

3. Combine delivery notes and local inspection samples

The following matrix serves as a working aid for package inspection. It does not claim to be equivalent to existing manufacturer documentation. Request the referenced documents and record what is actually available. If a document is missing, assess first its relevance to your process; the absence of a document does not necessarily indicate a corresponding significant gap in technical knowledge.

Assign each relevant requirement to an existing record or to a targeted supplementary justification. Particularly effective are transitions between building blocks: a module review can demonstrate correct task generation, while the local assignment of a new employee role remains unverified.

Work aid: Coverage of a specific dls-installation validation
ComponentVerify delivery noteLocal inspection questionAdditional evidence
Infrastructure and Hosting Installation status, operating concept Do our records cover our environment? Comparison and relevant restoration
Document circulation process Configuration specification Do the release authority role and substitute hold? Authorized and unauthorized role scenarios
Training integration Functionality and Assignment Record Has Revision 05 reached all intended personnel? Match each person to the document revision
CAPA and PDF/A Process and Output Description Are decisions, relationships, and processes traceable? Compare Fail-Akte and export records
Controlled Copies Printing and Feedback Concept Has the open archived copy been actually resolved? Compare employee roster against workplace occupancy records
Changes Release and Change Documentation Which local transitions are affected? Justified selection of repeat tests

Sources: [6] [3] [4] [5] [10]

4. Separate release and activation

Document routing defines configurable workflows per template and different version statuses. It also distinguishes between release and activation: typically, activation follows a training phase, but it may also occur manually. Translate these options into a clear operational procedure. Who determines the timing, which prerequisites apply, and which version appears in the production workflow?

Review a planned transition including intermediate states. A previously approved revision must not inadvertently become immediately valid if your procedure anticipates a later start date. Conversely, the current valid state must remain reliably available during the transition period. Consider dependencies, favorites, and the actual entry point used at the workplace.

According to the manufacturer's description, authorized users may view older versions. This is not automatically a failure: historical data may be required for investigations. What is essential is that the status of such data remains visible and that its unauthorized operational use is prevented. A general prohibition of all historical read access would not constitute an appropriate alternative control.

Sources: [3] [11] [10]

Further reading:

5. Link training to personnel, responsibilities, and revision history

With integrated document management, the training module defines responsibilities for newly released revisions. Qualification profiles and a matrix support assignment. Therefore, verify not only that a task has been generated, but for whom, based on which activity, and for which document version. Completion of a task for revision 04 does not automatically fulfill the required evidence for revision 05.

A single read-through and documented practical competence address different questions. Chapter 2 covers appropriate training, ongoing qualification, and the assessment of their practical effectiveness. Determine, based on content, whether reading is sufficient or whether an on-the-job orientation and practical observation are required. An automatically generated task does not establish this professional judgment.

Role rotation, attendance, absence, and temporary substitution should be included in the assessment. A representative may, for example, assume organizational responsibilities without automatically possessing the same decision-making authority. Describe specifically which authorities may actually be delegated. Open training sessions require a concrete evaluation; a universal technical work station lock cannot be inferred from a product overview or from any individual training requirement.

Sources: [4] [12] [10]

Further reading:

6. Correctly categorize CAPA data, PDF/A, and paper copies

The CAPA module includes features such as forwarding, escalation, coverage, and integration with other quality processes. According to the manufacturer's information, form status is archived as PDF/A. However, for root cause analysis planning, the key information that enables future decisions to be understood includes: reason for action, corrective actions taken, responsible parties, relevant changes, associated documents, and the predefined effectiveness evaluation.

Therefore, compare a representative electronic case record with its issued version. Are key relationships and temporal dependencies preserved or visible only within the system? PDF/A may support an appropriate presentation, but it alone neither guarantees complete record transfer nor ensures protection against any modification. Retention and retrievability are determined by the actual records required and their intended purpose.

The description of controlled printing covers the reason, logging and reporting the return or destruction of printouts. The log is evidence of a step. Someone must still deal with the physical copy. Define how to track outstanding copies and who confirms their actual status. Distinguish closing an action from closing the CAPA when effectiveness assessment is still pending.

Sources: [5] [3] [11] [13] [10]

Further reading:

7. Example: a CAPA modifies a SOP

This worked example has not been executed as a product test. CAPA K-026 requires SOP revision 05 in place of revision 04. Twelve employees are assigned. Nine training records for revision 05 are available. Two controlled old copies remain. The internal rule in this example permits the activity only after the individual training record is available. The rule is not a general regulatory requirement.

The test responsible party shall predefine roles, starting conditions, and expected responses. They shall evaluate both the visible decision and associated documentation. If a system does not technically enforce a condition, the intended additional control must be specifically described and assessed for suitability.

Example: Revision 05 control matrix, twelve employees involved, two obsolete copies
Test caseInitial conditionExpected result and calculationEvidence to retain
Scope covered by the supplier Standard workflow documented; no local substitute appointed Targeted additional verification instead of unverified acceptance Version-based coverage decision
Revision approved 9 out of 12 evidences available 9 ÷ 12 = 75 %; 3 open. Quote does not grant usage permission Person and revision information for each record
Unauthorized Representative Representatives without required release authority No release authorized by this role; separately evaluate assigned alternate role Roll position and observed decision
Legacy copy 1 of 2 copies recalled 2 − 1 = 1 track one open specimen Inventory records and actual location
CAPA-Closure PDF available; actions completed; efficacy pending Closure according to the example plan has not yet been justified Effectiveness decision and link to the case file

Sources: [3] [4] [5] [10] [13] [12] [11]

8. Treat changes and engamp as its own scope

For ongoing operations, you need a process to identify changes to the base platform, modules, roles, and interfaces. Assess the impact of these changes on your released processes. An update might alter the display, but could also affect task delegation or export functionality. The decision to reperform evaluations should address these actual differences.

engamp is being offered as a new product line. Its functionalities, license roles, and update information must not be unverifiedly transferred to existing dls installations. The public FAQ directs existing customers to their project contact for transition support. This does not imply a mandatory migration nor a confirmed automatic transfer of all data and histories.

During a system transfer, particularly review open activities, valid document versions, training assignments, roles, and required historical information. Request specific transfer and reconciliation rules. For hosting changes, additionally include access, recovery, and operational responsibility. Justify which prior evidence is to be carried forward and which transitions require new documentation.

Sources: [7] [8] [10] [11]

9. Plan workload for decisions and transitions

For a small and medium-sized enterprise (SME), a clearly defined initial process is often more practical than the concurrent implementation of all available modules. Designate a subject-matter expert, a document and training point of contact, and a point of contact for IT, as well as the in-house quality function. Available authorities and competencies are key; a specific universal signature workflow is therefore not required.

The effort arises primarily from diverse document types, local workflows, role variations, poor historical data quality, and integration points. The question of which historical information must be migrated can generate significant clarification needs. A useful delivery package reduces the need for internal validation evidence, but does not eliminate the work associated with unclear internal guidelines.

Prepare a version inventory, example records, role list, and known edge cases prior to scheduling the meeting. Separate requirements that the product has already demonstrably met from configuration work and organizational decisions. This enables concrete discussion with the supplier regarding which documents and inspections are to be provided by whom. Reliable duration or pricing information can only be provided once this scope is clearly defined.

Sources: [6] [2] [10] [12]

10. Checklist for Justified Decision on Intended Use

Use this checklist as a separate final check for the agreed scope. A hook should point to a detectable proof or a reasoned decision. Open points are evaluated according to their importance for the intended use; a mere number of completed tests do not replace this evaluation.

Following implementation, the distinction remains useful: New modules, additional sites, and revised training models can be assessed against the previously established workflow. Additionally, document who handles pending activities during system outages and how a consistent work status is established upon system recovery.

  • Base platform, dls modules, versions, licenses, and hosting are clearly documented.
  • Invoices have been reviewed, assigned, and evaluated against local limits.
  • Release, commissioning, and productive access demonstrate the intended document status.
  • Persons, activities and evidence of training are assigned audit-related.
  • Delegation and unauthorized actions were reviewed based on specific roles.
  • CAPA links, outputs, and required histories remain traceable.
  • Controlled copies and open trainings require a structured handling procedure.
  • Operation, modifications, restoration, and usage decisions are the responsibility of the designated responsible parties.

Sources: [10] [11] [12] [13]

Project experience and collaboration

Manage document changes and training needs together

An SOP revision following a CAPA helps show how your d.velop and dls components work together. With QA and process owners, we identify when the revision should take effect and who needs evidence of it. A single missing link may justify targeted work. If documents, training and forms follow different paths, we first agree a common process rule. We map supplier documentation to the combination in use and assess what it actually demonstrates before accepting or rejecting it.

Frequent Questions about d.velop, SOPs, and Training Documentation

Is DevLife Sciences today the same as dls | eQMS?

The previous company name has been changed to Digital Life Sciences GmbH in 2023. dls eQMS refers to the offered modular suite; d.velop documents is the named basis of document management. Therefore, for your validation scope you need the actual installed combination with versions and modules. The company name alone does not identify any release or configuration.

Sources: [1] [2] [3]

When using engamp, do we need to re-create all dls references?

Not automatically. engamp is described as a new product line, therefore the transferability of existing documentation must be specifically evaluated. Compare requirements, data model, roles, process flows, and operating procedures. Suitable evidence may remain usable; however, modified transitions and transferred data require appropriate additional documentation. A general automatic equivalence of all functions has not been publicly demonstrated.

Sources: [7] [8] [10]

What does the provided validation package cover for us?

The public description mentions support for specifications and risk work, as well as documentation of installed software and configuration. It cannot be conclusively identified which requirements and test cases your package actually covers. Read the scope delivered including version, results and limitations. Your local roles, training assignments and paper processes must be clearly covered or specifically supplemented.

Sources: [6] [10]

Is a released SOP immediately the current valid version?

Not mandatory. According to the manufacturer's statement, a document is typically automatically activated at the end of the planned training phase; alternatively, manual activation is possible. Therefore, release and the current working version may occur at different times. Define the professional starting point and verify during transitions which revision the personnel are actually authorized to use.

Sources: [3] [11]

May no one work while a training session remains open?

Such a general statement would be overly broad. What is decisive is the specific activity, training content, and the justified qualification rule. For a particular task, a personal qualification proof prior to work commencement may be required, without necessitating the restriction of any other activity. Verify whether the system supports the selected rule technically and identify any additional appropriate organizational controls that may be required.

Sources: [4] [12] [10]

Does the training matrix demonstrate that personnel have proficiency in a new SOP?

It supports visibility into assignments and recorded evidence. This does not in any case imply practical competence. Determine, per content, whether a read authorization is sufficient or whether onboarding and learning assessment are required. Additionally, verify the correct person, responsibility, and version. A 75 percent figure represents a current status, not a blanket authorization.

Sources: [4] [12]

Does the CAPA-PDF/A serve as a complete archive?

A PDF/A copy of a form version does not constitute a complete CAPA file by itself. Required links, changes, or decision dependencies may be missing. Therefore, compare the electronic file with the output and determine which information must remain available, readable, and traceable. The file format alone neither ensures completeness nor demonstrates retention control.

Sources: [5] [11] [10]

How do we verify controlled paper copies following a SOP change?

Verify the register against the actual disposition of issued copies. The software documents print justification, logging, and feedback. An open copy requires responsible clarification; a set status does not replace the actual action. In the example of this article, with two issued and one returned copy, one copy remains open. Its potential use must be assessed.

Sources: [3] [11]

Is an electronic release automatically a Part 11 signature?

No. First determine whether the FDA-related records and signatures fall within Part 11. Then evaluate the signing function, identity, meaning and link to the record in the actual workflow. Product advertising or workflow status alone is insufficient. Assess the relevant electronic signature requirements for human medicines GMP separately.

Sources: [14] [10]

What should a small company begin with when implementing a system?

With a clearly defined process, appropriate example records, and a coverage matrix for the supplied delivery package. First, clarify versions, modules, roles, and the determination of valid document versions. Subsequently, review the transitions to training, CAPA, and paper copies. This sequence serves as a practical planning aid; it neither replaces your risk assessment nor the evaluation of other relevant processes.

Sources: [6] [10]

Sources and review date

Sources were checked on 6 October 2026. The scope is dls | eQMS from Digital Life Sciences on d.velop documents. Public module descriptions do not establish a specific version number. The engamp product line is distinct. We assessed the public description of the validation package without access to the full package. The regulatory focus is GMP for human medicinal products, Annex 11 and Chapters 1, 2 and 4. The examples and matrices are our own planning aids. They do not describe product tests we performed.

  1. Renaming: d.velop Life Sciences will be renamed to Digital Life Sciences
  2. Digital Life Sciences – Quality Management Software and Operational Models
  3. dls | document control
  4. dls | training management
  5. dls | capa – corrective and preventive action
  6. Digital Life Sciences – Validation Services
  7. engamp – new product line from Digital Life Sciences
  8. engamp – FAQ on Provision and Licensing
  9. European Commission: EudraLex Volume 4
  10. EU GMP Annex 11: Computerised Systems, January 2011 revision
  11. EU GMP Chapter 4: Documentation, January 2011
  12. EU-GMP Chapter 2: Personnel, Revision 2013
  13. EU GMP Chapter 1: Pharmaceutical Quality System
  14. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

The gaps in module integration are addressed

We support you in defining the actual scope, evaluating supplier certifications, and planning targeted audits for document control, training, and quality processes.

  • 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 →