A planned release will be made to the Qualer platform on January 21st, 2019. This release will include various bug fixes, and added functionality to improve your overall experience with the Qualer system. A summary of the functionality included in this release, and an impact assessment for each feature is listed below:
Relevant Dates:
Go-Live Date: January 21, 2019
Access to Validation Site: December 31, 2018
Access to Preview: December 10, 2018
Announcement: November 26, 2018
| ID | Feature Description | Relevant Module(s) | Risk |
| 36169 | Smart Ticketing & Surveys | Surveys Module | 1 - Low |
| 36171 | Service Manager | 1 - Low | |
| 38533 | Unit of Measure Conversions in Uncertainty Budgets | Service Administration | 1 - High |
| 38534 | Specification and Product Management Improvements | Asset Manager | 2 - Medium |
| 38535 | Large Order Creation Responsiveness | Asset Manager, Service Manager | 1 - High |
| 38536 | Client and Vendor Management Options | Asset Manager, Service Manager | 2 - Medium |
| 39695 | Fulfillment Interface | 1 - High | |
| 36756 | Enhanced Recall Support Notices | Service Administration | 3 - Low |
| 34054 | Service Event Change Control and Audit Trails | Asset Manager | 1 - High |
Overview of Qualer's Risk Assessment Procedure
Risk is defined as Low, Moderate, or High based on the criteria identified in the following table:
| Consequence | Likelihood Based on the Frequency of Use | |||
Low | Medium (credible/not likely) | High (credible/likely) | ||
| Low (Unregulated) | Low | Low or Medium | Medium | |
| Medium (Business operations) | Low or Medium | Medium | Medium or High | |
| High (IS0 9000/GxP impact) | Medium | Medium or High | High | |
Controls will be tested, as indicated:
| Risk | Level of Testing |
| Low | Significant controls and functions will be tested for correct function. Invalid inputs and/or usage will not be tested, but will be noted if found. |
| Medium | All controls and functions will be tested for correct function. Invalid inputs and/or usage will not be tested, but will be noted if found. |
| High | All controls and functions will be tested for correct function. Where possible, invalid inputs and/or invalid usage will be tested to verify appropriate failure conditions. |