Let’s Talk About Compliance – Part 5: The Compliance Summary Tile

Natalia Ochoa
By Natalia Ochoa | January 13, 2022
Product Operations Manager

Fact checked by Stephen O'Reilly

Okay. So, we decided to finish off our Compliance blog series with a close-up look at a feature we love in Enact®: the Compliance Summary tile. It’s a handy tool in the software and seems like a fitting way to wrap things up.
 
In the Introduction, InfinityQS VP of Product Management, Eric Weisbrod, laid out the plan for this series. In Part 2, Senior Product Analyst, Matt Ryan, discussed collecting good quality data to help ensure that the products you’re creating are compliant with set specifications and that your processes are performing well. In Part 3, I picked up the reins and talked about how the compliance efforts for timed data collections in your organization relate to how you manage your operators’ day-to-day jobs and responsibilities. And, in Part 4, Product Analyst Heewon Kim discussed how Enact notifications and workflows can help you remain compliant.
 
So, here we are putting a bow on the series with a discussion of an Enact function I know can help manufacturers with their compliance efforts. We all know that manufacturers implement comprehensive, standardized quality plans that require data collections and checklists to be performed on schedule, right? Manufacturing, as we all know, can be fast-paced and hectic. Anything we can provide (like the Compliance Summary tile in Enact) that will make your job easier is worth looking at. So, let’s dive in.
Enact Makes Compliance Easy

Making Compliance Easy

With the Compliance Summary tile, you can monitor high-level compliance data for timed data collections by site and drill down to the process level to help you pinpoint underperformers very easily.
 
The Compliance Summary tile helps you to:
  • Know if timed data collections are happening on each process to a level that you’ve configured.
  • Know if timed data collections are happening across each site to a level that you’ve configured.
  • See how much compliance to timed data collections is changing over time.
The tile highlights underperformers, enabling a clear identification of which areas need attention. We’ll cover the easy configuration of the Compliance Summary tile a little later in this article.
 
The Compliance Summary tile enables management to monitor the compliance of their various sites on a weekly or monthly basis. Is your data being collected on time? Which processes or subprocesses are not meeting your compliance standards?
 
A process, for example, could be a filling line; a subprocess would therefore be a filling head on that line. Make sense?
 
This powerful tile shows performance (based on the % of processes at a site that meet or exceed a user-defined compliance threshold) while still allowing you to drill down into the data—to individual processes. This helps you make better decisions and proactively manage your sites.
 
Here’s what the Compliance Summary tile looks like:
Enact Compliance Summary Tile

Using the Compliance Summary Tile

In our example, all values < 95% are highlighted in red in the Site Compliance Summary view above. Values equal to or greater than the threshold value are not highlighted.
 
Only those processes for which data is collected contribute to the compliance calculation.
 
As you can see in the example above, the Site Compliance % for “DA – Dallas” on Week 1 of February is 87.5% and it is highlighted in red because that value is below the site threshold of 95%. The 87.5% value is calculated as follows:
 
The Compliance % for Site = Count of Compliant Process(es)/Total count of Process(es) and/or subprocess(es).
 
Out of all the processes in the Dallas site, 87.5% of them are meeting the 85% process compliance threshold. But because my site threshold is set to 95%, this is telling me that there is still a 7.5% gap of process(es) within that site that are not meeting the 85% process compliance target. Now, the next question would be which process or processes are not meeting the company’s process compliance threshold?
 
It’s that simple.
 

Drilling Down

From the Compliance Summary view above, we click “DA – Dallas” to open the following Details window:
Drilling Down into Compliance Details 
In this example, there are a total of eight processes in “DA – Dallas” in which sampling requirement data has been collected (4 processes and 4 subprocesses). Filling Line 001 (the topmost one) has a subprocess with a compliance issue. [The four subprocesses for this line are denoted by the red  symbol and “4.”
 
Clicking this line enables you to drill down even further to the subprocess level:
Subprocess Info in the Compliance Tile 
Here you can see that one of the subprocesses (Filling Head 003) is highlighted in red – 79.07%. This filling head did not meet the process compliance threshold of 85%. Management can now look into why this particular subprocess is not meeting your compliance standards—why data for this filling head was not collected sufficiently on-time.
 
This is what I would call an “at-a-glance” way to determine where you stand in terms of compliance at a site. It’s easy to get to, easy to read, and decisions can be made quickly to turn things around and remain compliant.
 
We’ve seen the valuable information that the Compliance Summary tile can offer you, now let’s dive into configuring it. It’s really quite simple.
 

Configuring the Compliance Summary Tile

Configuring the Compliance Summary tile could not be easier. It allows you to set your own target values, as well define how the data will be displayed. You can see in the Configure Options dialog below is based two factors: Site Performance and Process Compliance
Compliance Tile Configuration 
For our example Compliance Summary, we’ve selected to View timed data collection results by the week. And we’ve set the Site Summary threshold to 95%—this means that the site is considered successful if 95% or more of that site’s processes meet their timed data collection goal. Because of this selection, only values that are not meeting the threshold will be highlighted in the Site Compliance Summary view.
 
In addition, for Process Compliance, we’ve selected On-Time and set the threshold to 85%—this means that an individual process is considered successful if the number of on-time data collections are 85% or more.  
 
These are the basic settings you need to create the tile so it will display in your Enact dashboard (here’s what it looks like in the dashboard):
Compliance Summary Tile in the Dashboard
(The Compliance Summary tile is located at the lower right in this screen shot.)
 
So, the tile is always there at your fingertips when you need it. Keeping close tabs on your operations’ timed data collection compliance efforts will give you peace of mind.
 

In Summary

Compliance is important for manufacturers. You need to avoid legal penalties, while ensuring that your company is meeting standards and in compliance with regulations. The Compliance Summary tile is “top-down” analysis that helps you identify root causes and facilitates corrective action.
 
Your supervisors can easily and quickly identify a lack of compliance with scheduled data collections at all your sites. They can drill down into a process or subprocess and pinpoint the issue. 
 
It’s another way that InfinityQS quality management solutions help your organization’s professionals focus on their day-to-day activities that keep your high-quality products rolling off the production lines.
 
Read the other articles in this blog series:  
 
Take advantage of the technology at your fingertips today: contact one of our account managers (1.800.772.7978 or via our website) for more information.
 

InfinityQS Fact Checking Standards

InfinityQS is committed to delivering content that adheres to the highest editorial standards for objective analysis, accuracy, and sourcing.

  • We have a zero-tolerance policy regarding any level of plagiarism or malicious intent from our writers and contributors.
  • All referenced articles, research, and studies must be from reputable publications, relevant organizations, or government agencies.
  • Where possible, studies, quotes, and statistics used in a blog article contain a reference to the original source. The article must also clearly indicate why any statistics presented are relevant.
  • We confirm the accuracy of all original insights, whether our opinion, a source’s comment, or a third-party source so as not to perpetuate myth or false statements.

 

SUBSCRIBE TO OUR BLOG

Never miss a post. Sign up to receive a weekly roundup of the latest Quality Check blogs.

Archives

Take the Next Step