We understand the importance of maintaining quality standards and ensuring seamless production processes. That's why we offer comprehensive alert configurations within our Quality Module to keep you informed and proactive.
Under your quality controller, alerts can be configured for the quality module. This is meant to send alerts when quality checks have failed or have not been completed (expired). In addition, SPC alerts can also be configured The Quality Controller feature allows for the configuration of alerts within the quality module, enabling notifications for failed quality checks or incomplete/expired ones. Additionally, Statistical Process Control (SPC) alerts can be set up under the quality module.
Alerts for Failed Checks
In the qualitycontroller section of the quality module configuration (accessible via URL in the format of https://demo.shoplogix.com/qualitycontroller/) there will be a drop down menu to configure a schedule for each of the individual checks listed in the group:, a dropdown menu facilitates the scheduling of alerts for individual checks grouped by type.
...
| Info |
|---|
Only checks of type categorized as Measurement and PassFail can be configured since there is no failure criteria for a check type String, as checks of type String lack failure criteria. |
Once the check name in the group is selected, a schedule can be configured by hitting clicking the “Add Schedule” button.
...
Alerts for
...
Missed/
...
Incomplete Checks
...
The “Alerts for Incomplete Checks” option is meant for alerting when checks are not performed in the expected time frame. This is applicable only for active checks that are meant for production type stages (such as Job Start, Jobs triggers notifications when checks aren't completed within the expected timeframe. This applies solely to active checks pertinent to production stages (e.g., Job Start, Job End, Job Pulled, Shift Start, Daily, and Production) and are not applicable for ad hoc , excluding Ad Hoc checks. The alert would only be triggered after the check has expired depending on the stage in which the check has been configured for.
For example, if the stage has been configured under the “Job Start” stage and the check was active for the job, if the next job has started then this would be considered a missed check.
...
Multiple schedules can be created for different user groups of users. The scheduling aspect is applicable for . Schedules apply to both Failed Checks OR and Missed/Incomplete/Expired checks - these terms are used interchangeably.
The schedule is meant for having an active time frame for when the alert will be sent. There are options to select different days as well as time:
...
. Users can specify active timeframes for alert delivery, including options for days, times, and date ranges. Repetition on certain days and limiting alerts to occur after a set number of occurrences are also supported.
...
Moreover, if we want to replicate the exact same schedule across multiple days, we can also create the schedule for one day, and have it repeat on certain days.
...
...
In addition, to filter out too many alerts; there is an option to only send an alert only after 'X' number of occurrences.
...
The final section labeled as
...
Email addresses intended to receive alerts should be listed in the “Email to:” is for the set of email addresses that wishes to receive the alertsection, separated by commas:.
...
The schedule time frame will determine when the emails will be sent. Anything failures outside of the scheduled time frame will not be sent.
...
Alerts are dispatched within the specified schedule timeframe; failures occurring outside this window won't trigger notifications.
Appending Schedules
This feature is an easy way of adding existing schedules from one check to other checks.
By clicking on the “Append Schedule to” button
...
we are able to append the created schedule to other checks:
...
| Info |
|---|
NOTE: The schedule would “Append” to any existing schedule schedules for the target check. If there is an existing schedule in the destination it will not be overwritten. This does also create the possibility of receiving multiple alerts for the same check if there are schedules with duplicate timeframes. |
...
The following is an example of a schedule scheduled alert created for the alert called “Safety Check P/F”“Test-1-Measurement” check:
...
This alert will send be sent if the “Safety Check P/F” “Test1-Measurement” check fails at any time (after 1 occurrence) only for during every Monday, Tuesday, and Wednesday during between 7 AM to 3 PM to the email address test@shoplologix kzhu@shoplologix.com. The alert would not be sent outside of this schedule. For example, if there is a failed check for “Safety Check P/F” “Test1-Measurement” on Monday at 8:00 AM, an email would be sent out to test@shoplogixkzhu@shoplogix.com and no further emails would be sent out on Monday even if the same check fails again. On Tuesday, the schedule resets, and if a failure occurs from between 07:00AM to 3 PM for this same check “Test1-Measurement”, an email would be sent.
Example 2 - Missed/Incomplete Checks
...
...
...
The check named “Safety Check P/F” “Test1-Measurement” above is configured for a safety check to be complete at the start of a job. If this check was just saved it would not take affect for the current running job since the start of the job as has already passed. The schedule is set for Monday, Tuesday, Wednesday, Thursday, Friday from 7 am-3pm which means no alerts will be sent outside of the time range. This is also configured to send an alert after 3 occurrences. This means that the alert will be sent only after the it check has expired and was not complete after 3 additional job changes (not including the current running job) during the time frame of 7am-3pm. This counter will be reset the following day. For example, if 3 expired missed checks occurred where 3 jobs changed on Monday between 7 am - 3 pm, then a single alert will be sent.
| Info |
|---|
If an “Alert for Incomplete Check” is created for a check at in the “ad hoc” “AdHoc” stage, the alert will never be sent. This is because ad hoc Ad Hoc checks do not have a defined production stage and would never be missed. |