This article details components of the Events workflow and functionality. Jump ahead to:
Events Severity and Probability (Risk)
When creating an event, you may need to indicate the Severity and Probability of the event. During event creation, this is an initial judgment that may change over time, which is why these properties can be updated as the event is investigated.
The "Risk" parameter is calculated using the Severity and Probability values as inputs. If one or both of these fields is marked as “N/A,” the Risk will also be N/A.
However, some organizations use a 5-point risk assessment scale, which can cause some confusion when it comes to applying their assessment to Qualio's built-in risk calculation. Below is a suggestion of how some organizations manage these differences.
Example 5-point Risk Calculation Table
Note: Despite the calculation of Low (5) for Negligible x Frequent, this value is considered Medium due to the Frequent probability.
The customer is to define the quantitative/qualitative threshold for each level of severity and probability, as this varies by product and scale of distribution.
Calculate the Risk Priority Number (RPN) using the labels on the 5-point scale above and the formula below.
Severity x Probability = RPN
Then, convert the RPN into Risk Level by defining a threshold for Low, Medium, and High. And finally, when entering severity and probability on the event, confirm the auto-calculated risk aligns with the 5-point scale Risk using the table below. Adjust fields as needed.
Create Products and Root Causes
Events can be categorized by Product and/or Root Causes. This facilitates dynamic event reporting, allowing users to search for events by product and root cause along with other filters like status and owner.
Once created, Products and Root Causes can be specified during initial event creation or later by editing the event.
How To Create New Products
Navigate to the Events tab, and select the Products sub-tab.
Click the Add product button.
Provide a Product Name and additional details of the product in the Description field, to help users understand what the product is.
Then click the Add product button.
How To Create New Root Causes
Navigate to the Events tab, and select the Root Causes sub-tab.
Click the Add root cause button.
Provide a Name for the root cause and additional details in the Description field.
Then click the Add root cause button.
Note: that a product and/or root cause cannot be deleted if associated with any event (open or closed). If trying to delete a pop-up will appear:
Export Events
Generate a report of multiple events
From the Quality Events tab, select either the Events or Tasks sub-tab.
Then use the filters to identify events or tasks needed in the report.
Click the expansion menu to the right of the filters.
Select either an Export list as XLSX or PDF.
The file will be prepared and prompt users to click to download.
Exported report will be downloaded to your computer.
Export a Single Event
From the Quality Events tab, select the Events sub-tab.
Select an event by clicking anywhere in the line item. (Hint: Use filters to narrow results and identify the event.)
Click the Export Event button.
A zip file will be prepared and prompt users to click to download.
Exported zip file will be downloaded to your computer. The zip file will contain:
Event PDF with details and properties including probability, risk, owner, creator, creation and resolution dates.
Documented steps for each phase (Analysis, Tasks, and Validation) of the event as well as Status and Status Updated date/time stamp.¹
Validation PDF - a separate document for validation results is provided to…
Attachments - Any attachment included in any step of the event. (Included PDFs will indicate a link to attachments. When clicked, users will be taken to the step/attachment in Qualio. However, the attachments are included in the zip file.)
Event Step IDs
Each step in an event is assigned an ID for identification and search functionality. Step IDs are derived from their related event type prefix. Next, an auto-incrementing letter will be added to the end of the event prefix, starting with A.
Example:
A 'FDBK' event would generate step IDs with a prefix of FDBK.
The first step of a FDBK event would be 'FDBK-A', the second step would be 'FDBK-B', and so on.
If enough steps are added to an individual event, double letters will be appended starting at AA.
Step Creation
Dashboard
Event Workspace
Lastly, an auto-incrementing number is appended following a dash. However, this number is assigned in the order of creation of all event steps in your instance of Qualio.
Example:
NCR-1 and NCR-2 have been created by two different users in the system.
The user who created NCR-2 is the first to click “Create” on step 1 of the NCR, therefore, the Event Step ID is NCR-A-1.
The user who created NCR-1 clicks “Create” on step 1 the following day and that Event Step ID is NCR-A-2.
Step IDs can be found while initially creating the step, or will be displayed on the Dashboard and in the Workspace when actions are needed on the step.
Note: The dash may not appear if the event template for that step was made prior to 2024. (It would show as DEVA-6 and not DEV-A-6).
Event and Task Date Fields
Events and tasks include several date/time fields that can be viewed within the application and/or exported formats. But depending on the export format (PDF and XLSX) and what is being exported (single event or event/task report) not all are displayed. Below is a comprehensive list of what fields are displayed with definitions.
Object | Field Name & Definition | Single Event PDF | Report PDF | Report XSLX | Application |
Event | Created At: Creation date of the event - When the Create event button is clicked on the new event form. | Yes | Yes | Yes, on the Events tab | Yes |
Task | Created At: Creation date of the task - When the Create Task button is clicked on the new task form. | No | N/A - tasks are not detailed | Yes, on the Tasks tab | Yes |
Event | Completed At: Date/time stamp when the final Event Validation Step approval is granted. ¹ | No | No | Yes, on the Events tab | No |
Task | Completed At: Date/time stamp when the task 'Complete' button was pushed. ² | No | N/A - tasks are not detailed | Yes, on the Tasks tab | No |
Event | Resolved At: Date/time stamp when the final Event Validation Step approval is granted. 1 | Yes | No | No | No |
Task | Closed At: Date/Time stamp when the task 'Complete' button was pushed. ² | Yes - unique for each task | N/A - tasks are not detailed | No | No |
Event & Task | Last Modified: When an event, event step, or task was modified (saved). This includes changes to properties, content, or status, but not comments. ³ | No | No | Yes, on the Events tab | Yes for both event and tasks |
Event | Due Date: Generated from the "Time to resolve (days)" filed on the new event form | No | Yes - Displayed as "Due at" | Yes, on the Events tab | Yes |
Task | Due Date: Generated from the "Complete before" field on the new task form | Yes - Displayed as "Due at" | N/A - tasks are not detailed | Yes, on the Tasks tab | Yes |
Event | Acknowledged At: Recorded when the first task is updated. (i.e. a document is created for a step.) Customers can leverage this metric to track "Time to Response" | No | No | Yes, on the Events tab | No |
Event | Status Updated At: Recorded when an event step status is modified, e.g. change from "open" to "closed" | Yes - unique for each event step | No | No | No |
Event | Updated At: When an event, event step, or task was modified (saved). This includes changes to properties, content, or status, but not comments. ³ | No | Yes | No | No |
Task | Comment: Each comment records the date/time stamp when it was added. | No | No | No | Yes |
1. The event date field Completed At is the same as the event date field Resolved At.
2. The task date field Completed At is the same as the task date field Closed At.
3. The Last Modified date field is the same as the Updated At field.
Compare Versions of an Event
Similar to Qualio Documents, managing an event content step through multiple updates and versions, it can be helpful to understand when major and minor versions are auto-incremented, and compare one version against another version.
When viewing the event step, you can select which version to display and which version to compare it against using the two respective buttons. New content will be highlighted in green and removed content will be shown in red.
An event step’s version number is automatically incremented (starting at 1) and controlled by triggers within the document lifecycle to update either the major or minor version.
Major Version
Whole number before the decimal point. Example: 4.0 represents the fourth major version of an event step.
Increments are triggered when an event is approved.
Minor Version
Decimal number to the right of the decimal point. Example: 0.2 represents the second minor version of an event step.
Increments if the event step is put back into draft status after being sent for review or approval.