Overview
The Quality Management (QM) Configuration Workbook helps you build forms more efficiently while reducing configuration errors. Following these best practices will improve data consistency, streamline setup, and ensure your QM programs function as intended within the system.
Tip 1 — Reduce Redundant Attributes
When first building a workbook, it’s common to include every form field as an attribute. However, many of these data points already exist in the system as common attributes and do not need to be recreated.
Common Attributes Examples
These are standard fields typically reused across forms:
- QM Program Name (form name)
- Plant
- Collection Time
- Technician Name
- Instructions (form guidance text)
- Product Identification
Best Practice
Only include attributes that are unique to the specific form. Avoid duplicating system-level or reusable data points.
Tip 2 — Avoid Duplicate Attribute Names or Codes
Problem
Duplicate Attribute Codes or Attribute Names within the same QM Program are not supported and will result in a configuration error.
Solution
Ensure each attribute within a QM Program is unique. If similar attributes are required, differentiate them using a consistent naming convention.
Example Fix
Instead of:
- Product Temperature
- Product Temperature
Use:
- Product Temperature 1
- Product Temperature 2
Tip 3 — Always Define Both Min and Max Values
Rule
If you define a Minimum Acceptable Value, you must also define a Maximum Acceptable Value, and vice versa.
Why This Matters
Defining only one boundary can result in incomplete validation rules and configuration errors.
Tip 4 — Maintain Consistent Data Types
Problem
Using different data types for the same attribute across QM Programs will result in errors.
Example Issue
- Appearance = Text in one QM Program
- Appearance = Numeric in another QM Program
Solution
Once an attribute’s data type is established, it must remain consistent across all QM Programs where it is used.
Tip 5 — Keep Forms Short and Focused
Instead of creating large forms with 50–100+ data collection points, break them into smaller, task-specific checks.
Benefits of Shorter Forms
- Easier to maintain and update
- Encourages more frequent saving
- Reduces risk of session timeouts
- Improves data accuracy and completion rates
Best Practice
Design forms around individual inspection steps or focused activities whenever possible.
Tip 6 — Separate Multi-User Inspections by Job Function
If multiple users may access the same form at the same time, separate the form based on job function within the QM Workbook.
Best Practice
Avoid designing workflows where more than one user inputs data into the same form simultaneously.
Why This Matters
Separating by role helps prevent:
- Data overwrites
- Conflicting inputs
- Workflow confusion during inspections