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


IDFeature Description
Relevant Module(s)
Risk
36169
Smart Ticketing & Surveys

Surveys ModuleRisk Assessment Pending
36171

Client Asset Manager


Service Manager    Risk Assessment Pending
38533

Unit of Measure Conversions in Uncertainty Budgets


Service Administration
Risk Assessment Pending
38534

Specification and Product Management Improvements


Asset ManagerRisk Assessment Pending
38535

Large Order Creation Responsiveness


Asset Manager, Service Manager
Risk Assessment Pending
38536

Client and Vendor Management Options


Asset Manager, Service Manager
Risk Assessment Pending
39695

Fulfillment UI improvements


Fulfillment Interface
Risk Assessment Pending
36756

Enhanced Recall Support Notices


Service Administration
Risk Assessment Pending
34054

Service Event Change Control and Audit Trails


Asset Manager
Risk Assessment Pending



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
(highly unlikely)

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.