Data Collection Compliance
Compliance is a monthly report that covers the data collection or reporting exception in lieu of data collection per each asset's defined periodicity. This periodicity setting, the Minimum Compliance Periodicity, is a calendar-based setting for each asset.
Note: The collection periodicity is the frequency with which a machine's data is expecte to be collected. It is used to determine if a machine has met collection compliance in order to mark the machine as complete for the period and display it in the compliance metric in PredictivePortal.
To Access the Data Collection Compliance Table
The Data Collection Compliance widget in the Dashboard lets you to view the data collection compliance percentage so you know whether the machines in your program are being tested based on their collection periodicity. There are two numbers presented: data collected percentage, which represents assets that have had data collected during their periodicity for the monthly report, and a compliance percentage, which includes assets which have been reported upon in lieu of collection as either a planned exception or period exception.
Click the Data Collection Compliance widget title to view a detailed compliance report providing information on compliant and non-compliant assets based on their periodicity. In addition, the report includes data collection compliance and non-compliance percentages, planned and period exceptions, expected tests based on periodicity, and so on. The report assists you in making informed decisions to ensure that your analyst receives data on time.
The following columns are available:
| Column | Description |
| Date |
Displays the list of months for which you can view the data collection compliance metrics. When you expand a month node, you can view the hierarchy for the asset hierarchy level you've chosen. You can view the asset/equipment by expanding the nodes. The compliance metric is displayed next to each hierarchy level. |
| Overall Compliance |
Displays the percentage of completed data collection tests compared to the total number of expected data collection tests. The number of planned exceptions is also included in the Overall Compliance. The Overall Compliance for a hierarchy level is calculated by aggregating the compliance percentage of all child hierarchy levels. |
| Non Compliant |
Displays the number (as well as the percentage) of data collection tests that did not produce any results in comparison to the total number of expected data collection tests. This category also includes the number of period exceptions. The non-compliance for a hierarchy level is calculated by aggregating the non-compliance percentage of all child hierarchy levels. |
| Data Collected | Displays the number (as well as the percentage) of successful data collection tests in the current month compared to the total number of expected data collection tests. |
| Planned Exception |
Displays the number (as well as percentage) of assets (based on the total number of assets) for which data collection is not expected in the current month. An asset may be unavailable for collection for an extended period, such as during a repair or a seasonal outage. Setting a planned exception will exclude the machine from the calculation of compliance. |
| Period Exception |
Displays the number (as well as percentage) of assets that are not available for collection test. When attempting to collect data in the field, it's possible that an asset may not be available. In such cases, a Period Exception can be recorded through either the TRIO or PredictivePortal system. It's important to note that the asset will not be removed from the list of due machines, and the exception will only be reported after the period has ended. |
| Compliance Graph |
Enables you to view the cumulative data collection compliance percentage for each hierarchy level. The bar chart is useful when comparing the number of complaint assets (number of successful tests) vs the number of non-compliant assets (number of tests that were expected but did not happen). The green color represents the percentage of compliant assets, while the red color represents the percentage of non-compliant assets. |
| Expected Collection |
Displays the total number of machine tests that are expected to be completed in the current month, regardless of the machines' periodicity. All the machines with planned exceptions, are excluded. Example: Consider there are 81 machines in a plant with the following periodicity:
The total number of tests expected in the quarter spanning April 2023 to June 2023 will be as follows:
|
| Number of Assets |
Displays the total number of machines whose periodicity ends in the current month. Example: Consider there are 81 machines in a plant with the following periodicity:
The total number of machines due for testing in the quarter spanning April 2023 to June 2023 will be as follows:
|
Additional information can be found here:
Comments