Home
Regulatory compliance
PLA 3.0 supports you in achieving compliance with regulations such as ISPE GAMP^® 5 and 21 CFR Part 11. It also provides options to validate PLA 3.0 in your environment.
Traceability
Traceability ensures logical data integrity, that is, you can trace your data across your entire system, from its current status back to its original source. In PLA 3.0, you can require users to specify why they modify documents and protected values to improve traceability and protect data from intentional and unintentional changes.
Example 2: Set technical outlier state with reason and credentials
If your organization requires users to enter their user name and password together with a reason when setting the technical outlier state, you can set up your database policies so.

Get started
Explore PLA 3.0, its key features and ongoing enhancements. Learn how it fits into your environment, and how to log in and register.
User interface
PLA 3.0 supports you in your daily work by providing a set of graphical and textual user interface elements. Learn about the different elements and how to use them efficiently.
Key concepts
Details on documents and templates, the data editors and the Content editor of PLA 3.0.
Data analysis
Data analysis add-ons offer a wide range of capabilities, ranging from analytical methods over comprehensive analysis to statistical process control. PLA 3.0 also provides a set of add-ons that support and supplement data analysis add-ons.
Data import
Use data acquisition and data import add-ons to import external response values and observation data into PLA 3.0 for further processing and evaluation.
Installation
Details on the deployment and installation of licensed PLA 3.0 versions.
Licensing
Details on the licensing solution of PLA 3.0, the available licensing options, and the activation and management of licenses.
Administration
Details on system administration tasks such as setup and maintenance of databases and add-ons, user accounts, access rights, and migration and update procedures.
Regulatory compliance
PLA 3.0 supports you in achieving compliance with regulations such as ISPE GAMP^® 5 and 21 CFR Part 11. It also provides options to validate PLA 3.0 in your environment.
- Integrity
  Data integrity refers to the completeness, accuracy, and consistency of data over its entire life cycle. PLA 3.0 stores all your data in electronic documents, which are in turn stored in a database. When handling documents, PLA 3.0 utilizes digital signatures to ensure that documents are not tampered with.
- Authenticity
  Authenticity of digital data verifies that data is genuine and comes from its purported source. In PLA 3.0, users can employ electronic signatures to protect complete documents, document structures, and document data. Administrators can configure the handling of electronic signatures such that it supports regulatory compliance.
- Confidentiality
  Data confidentiality ensures that data is protected from unauthorized access and disclosure, and that personal privacy and proprietary information is protected.
- Traceability
  Traceability ensures logical data integrity, that is, you can trace your data across your entire system, from its current status back to its original source. In PLA 3.0, you can require users to specify why they modify documents and protected values to improve traceability and protect data from intentional and unintentional changes.
  - Example 1: Set technical outlier state with reason
    If your organization requires standardized reasons for setting the technical outlier state, you can set up the required reasons. When setting the state, users can select one of the provided reasons.
  - Example 2: Set technical outlier state with reason and credentials
    If your organization requires users to enter their user name and password together with a reason when setting the technical outlier state, you can set up your database policies so.
- Validation
  Achieving compliance with ISPE GAMP^® 5 requires software to be validated in the target environment.
PDF downloads
Download PDF guides of current and previous framework and add-on versions.
Sample lab
Meet the team of Stegmann Labs Inc. and use our sample laboratory to explore core features and functions of PLA 3.0.
Glossary
Find definitions of terms.

Example 2: Set technical outlier state with reason and credentials

If your organization requires users to enter their user name and password together with a reason when setting the technical outlier state, you can set up your database policies so.

Procedure

To change the default behavior:

On the System menu, select Database policies.
In the Database policies dialog, on the Signatures tab, under General, activate the Requires user name option.
On the Traceability tab, under Changes to protected values, from the Change technical outlier state list box, select Permitted with reason and signature.
Confirm your settings with OK.

Result

The templates you set up are available in the Template list box of the Set technical outlier state dialog. Users need to enter their user name and password.

The following figure shows the dialog for the setting with the Requires user name option enabled on the Signatures tab. It displays three text boxes where users enter the reason for making changes, their user name, and their password.

Templates for changing the technical outlier state in combination with user credentials — Figure 1. Templates for changing the technical outlier state in combination with user credentials

Note: With the Requires user name option deactivated, PLA 3.0 automatically inserts the user name of the current user as read-only.