Managing Requirements (Validation Management)

In Validation Management, Business Process Owner or System Owner users can create user requirements, functional requirements, design specifications, and configuration specifications individually or import via a templated set of requirements. This can allow your organizations to harmonize practices across departments and global sites and establish a library of commonly used requirements and specifications as new systems, equipment, processes, and other GxP systems and processes are introduced in production.

Creating Requirements

Depending on your configuration, only certain members of a Validation Entity’s Validation Team can create requirements for it. To create Validation Requirements:

  1. Navigate to the Entity Version layout for your Vault.
  2. In your custom Requirement Entity Version section, click Create.
  3. Select a Validation Requirement Type.
  4. Click Continue.
  5. Enter the required details.
  6. Optional: Select a Template Requirement. If selected, the template will populate the following fields on the requirement: Description, Requirement Category, Requirement Source, and Requirement Source Details.
  7. Click Save. If configured by an Admin, Vault automatically populates the Name field with the appropriate naming scheme.

The Validation Entity Version field on the Validation Requirement object indicates which entity version first used the requirement. Users do not need to manually enter the value for the field. Once a user associates a requirement with an entity version, Vault automatically updates the Validation Entity Version field.

Creating Requirements Using Quick Create

If configured by an Admin, the Create button in the Requirement Entity Version section allows users to initiate the creation of Validation Requirements for each object type, including custom object types, with a single click.

To create a new Validation Requirement using Quick Create:

  1. Navigate to the Entity Version layout for your Vault.
  2. In your custom Requirement Entity Version section, click Create to start a new Validation Requirement record. The default object type is associated with the Create button.
  3. Optional: Use the drop-down on the Create button to select a different record option based on your active object types. 
  4. Enter the required details in the dialog, and click Save. The new Validation Requirement record is created and associated with the appropriate Validation Requirement Entity Version record. 
  5. Optional: Click Save + Create in the dialog to save and initiate the new record for creation.

Users also can filter the columns listed in the Requirement Entity Version section. Any column that includes a filter icon can be filtered, and the filter can be saved. Text, long text, and rich text fields cannot be filtered.

Removing Requirements Using the Requirement Entity Version Section

If configured by an Admin, the Remove button in the Requirement Entity Version section allows users to quickly remove one (1) or more available requirements from the entity version. Requirements that are mandatory for the entity family or are being used by a test script are not available for removal. Using the Remove button does not delete the requirement or specification record from the Validation Requirement (val_requirement_svo__v) object but deletes the join object record between the Validation Requirement and the Entity Version on the Validation Requirement Entity Version (val_requirement_entity_version_svo__v) object.

To remove a requirement or specification from the Entity Version:

  1. Navigate to the Entity Version layout for your Vault.
  2. In your custom Requirement Entity Version section, select one (1) or more requirements or specifications from the record selector checkbox on the far left. If you want to select all, select the checkbox in the header of the checkbox column. When one (1) or more records are selected, the Add button changes to a Remove button.
  3. Click Remove.

Creating Requirements from Templates

Maintaining a set of template requirements helps your organization establish an approved repository of template requirements available for use in different types of entities regardless of validation discipline. If configured by an Admin, you can import sets of requirements to a Validation Entity.

Importing Template Requirement Sets

To import requirements from a template:

  1. Navigate to a Validation Entity record, via Business Admin or a custom Validation Entity Version object tab.
  2. Perform the Import Template Requirement Sets action.
  3. In the dialog, select one or more Template Requirement Sets.
  4. Click Save.

Validation Template Managers can create Template Requirements and Template Requirement Sets for their organizations. See Managing Templates for steps to create Template Requirements and Template Requirement Sets.

Linking Requirements to Entity Families

If configured by an Admin, you can perform the Sync Entity Family Requirement action to link your requirements to an Entity Family. This can help you manage the qualification and validation of either identical or equivalent entities by grouping these assets under a single Entity Family record.

Creating Reference Tables for Requirements & Specifications

Validation Management users can add and manage reference tables directly in requirements and specifications, allowing them to structure and maintain tabular data in a more efficient manner. You can create reference tables with up to 10 columns and 100 rows per requirement or specification. You can edit the table name and column headers, insert, edit, move, and delete rows and columns, and clone rows, along with performing table editing functionality, such as inline editing and navigating the tables through keyboard shortcuts. You can also edit and delete reference tables through the Edit Table and Delete Table actions, respectively.

Using the Download to PDF action, you can print Validation Entity Version records with all requirements and reference tables included. When you generate a PDF from a Validation Entity Version, if no requirements include a reference table, all requirements are consolidated into a single table. If at least one requirement contains a reference table, each requirement is exported in a separate table, with the reference table appearing immediately after the corresponding requirement. You can also export an individual requirement record as a PDF and include its reference table if present.

You can add reference tables to Template Requirements to provide a predefined structure. The table does not need to be fully populated in the template. When a Validation Requirement is created from the template, the reference table structure is copied, and you can easily modify the table as needed.

Configuring Reference Tables

Admins can configure reference tables for requirements and specifications by performing the following steps:

  1. Enable the Has Reference Table? field for all Validation Requirement object types.
  2. Add the Reference Table application section to the Design Specification, Functional Requirement, User Requirement, and Configuration Specification page detail layouts.
  3. Optional: Add layout rules to hide the Reference Table section if the requirement or specification does not have a reference table. You can use the Has Reference Table? field to determine whether the requirement or specification has a table.

For the Validation Requirement Reference and Requirement Reference Table object lifecycles, Admins must assign all roles from the Validation Requirement object lifecycle to enable role cascading to child object records. Additionally, Admins should configure lifecycle states and permissions to match those of the Validation Requirement object lifecycle, ensuring that users have equivalent Edit permissions at each corresponding state.

Users also must have Edit permissions for the system-managed fields, such as the Number of Columns field for the Validation Requirement Reference Table object and the Row # field for the Requirement Reference Table Row object, from the permission sets and atomic security settings.

To manage requirements, a user requires a security profile or role that grants the following permissions:

  • Read, Create, Edit, and Delete permissions on the Validation Requirement (val_requirement_svo__v), Validation Requirement Entity Version (val_requirement_entity_version_svo__v), Template Requirement (val_template_requirement__v), and Template Requirement Set (val_template_requirement_set__v) objects
  • To use Quick Create, Read, Create, and Edit permissions on the Validation Requirement (val_requirement_svo__v), Validation Requirement Entity Version (val_requirement_entity_version_svo__v), and Traceability Matrix (val_rtm_svo__v) objects
  • To remove records from the Requirement Entity Version section on the Entity Version layout, Delete permissions on the Validation Requirement Entity Version (val_requirement_entity_version_svo__v) object
  • To use the Requirement Entity Version section, View permissions for the Requirement Entity Versions object control on the Validation Entity Version (val_entity__v) object

Ensure that the following permissions are set for the Import Template Requirement Set action:

  • Read permissions for the following objects:
    • Template Requirement Set
    • Template Req - Template Req Set (if the Refactor Template Requirement setting is not enabled)
    • Template Requirement (if the Refactor Template Requirement setting is not enabled)
    • Validation Req - Template Req Set (if the Refactor Template Requirement setting is enabled)
  • Read, Create, and Edit permissions for the following objects:
    • Validation Requirement
    • Validation Requirement Entity Version
    • Requirements Traceability Matrix

To manage reference tables for requirements and specifications, users require the following permissions:

  • Create and Edit permissions for the Validation Requirement object
  • Create, Read, Edit, View, and Delete permissions for the Validation Requirement Reference Table object
  • Create, Read, Edit, and Delete permissions for the Requirement Reference Table Row object
  • Read permissions for the Validation Req - Template Req Set object
  • View permissions for the Unit object