Understanding Publishing

You can publish Key Performance Indicators (KPIs)—aggregated upon end of day, end of shift, and user edit of a previously aggregated subgroup—as well as lot data and event data from Enact designated processes to a Receiver URL that you establish, allowing you to share this data with other plant systems (for example, ERP).

Using publishing, you can significantly expand the use and value of Enact data, enabling you to share the data with other plant reporting and information systems.

What You Need

  • Secure Receiver URL that can receive messages indicating that Enact data is available to be published.

  • Access key (up to 128 characters) for Enact provided by you that ensures data security when communicating between Enact and your system, including Receiver URL validation and Enact data publishing.

  • Application that uses APIs to retrieve data and acknowledges data transfer completion using the InfinityQS access key.

How It Works

Enact publishes KPI data as follows:

  1. Quality data aggregation is triggered by four user actions: End of Day, End of Shift, Lot Status Closed/Lot Testing Completed, and when a user edits a previously aggregated subgroup.

    Aggregated dashboards are built for larger sets of historical data, which Enact aggregates periodically in the background. Current data has not yet been aggregated, and therefore will not yet appear on aggregated dashboards. To view current (or "live") data, use raw dashboards. To understand how and when the data aggregation works, consider the following:

    • Daily Aggregation. From midnight to midnight in the process's time zone, Enact summarizes one whole day of data at a time. Enact checks for new data to aggregate every hour, so you will be able to see the previous day's data around 01:00 AM local time. When you use a dynamic or static time window or an aggregated dashboard, Enact returns data for your time window in whole-day increments. You can view one day or multiple days, but only in increments of whole days.

    • Shift Aggregation. Fifteen minutes after a shift ends, Enact summarizes the entire shift's data for each process. If you set your parameter set to By Shift | Previous Shift instead of Dynamic Time or Static Time), Enact uses the previous shift's aggregated data instead of the daily aggregation.

    • Lot Aggregation. When you set a lot's testing status to Testing - Complete, Enact immediately assembles data for the Lot Report, which disregards the parameter set's Time Window setting. For more information, please see Managing Lot Report Tiles.

    • Hourly Aggregation. Once every hour, Enact checks for previously aggregated data that's been edited, and re-aggregates the data using the edits. Enact will not re-aggregate data older than six months.

    You can use any parameter set for an aggregated dashboard, but it will differ from a raw dashboard, as follows:

    • Time Window. To view daily aggregated records, set the Time Window using Dynamic Time or Static Time. As stated above, Enact summarizes whole days of data at a time in midnight-to-midnight increments in the process's time zone.

    • By Shift | Previous Shift. To view the previous shift's aggregated records, configure By Shift | Previous Shift. As stated above, Enact summarizes the entire previous shift's data for each process.

    • Lot. To view a completed lot's aggregated records in the Lot Report, configure By Lot. As stated above, Enact immediately assembles data for the Lot Report, which disregards the parameter set's Time Window setting. For more information, please see Managing Lot Report Tiles.

    Because some parameter set fields do not apply, aggregated dashboards ignore the following parameter set fields: Hours/minutes, Shift, Lot (except for the Lot Report), and Data Collection Type.

  2. When aggregated records from designated processes in Enact are available, Enact sends a message to a Receiver URL, which contains instructions for retrieving the data.

    Enact only sends a message when you aggregate collected data or generated sampling requirement information. If there is no data, Enact will not send a message.

  3. When the Receiver URL receives the message, your plant system can call the Enact API using the subscription key from the Publishing page in Enact. For more information, please see Publishing Aggregate and Event Data.

  4. Enact publishes the KPI data in Javascript Object Notation (JSON) format, which is smaller in size, faster to use, and is very easy to read compared to other data formats.

    Enact only publishes the JSON files when you collect data or generate sampling requirement information. If you do not collect data but you do generate sampling requirement information, Enact will still publish the KPI data.

  5. Upon a failed publish, Enact automatically retries the KPI data publishing, which ensures publishing completion without manual intervention.

  6. Enact retains KPI data for 24 hours. You may opt to send an acknowledgment from your plant system to Enact, triggering Enact to delete all related published data immediately.

What Enact Publishes

  • Basic Information

    • Part: Part name

    • Process: Process name

    • Feature: Feature name

    • #Subgroups: Count of subgroups

    • #Pieces: Count of pieces

    • #OOS: Count of pieces out of specification

    • #Defects: Count of defects

    • #Defectives: Count of defectives

    • Mean: Mean

    • SD (ST): Short term standard deviation

    • SD (LT): Long term standard deviation

    • CQS (Total): Composite quality score derived from out-of-specification, defects, and defectives

    • CQS (PPM): Composite quality score per million

  • Net Content Statistics

    • # <MAV(L): Count below MAV(L)

    • # >MAV(U): Count above MAV(U)

    • # <T1(L): Count below T1(L)

    • # >T1(U): Count below T1(U)

    • # <T2(L): Count below T2(L)

    • # >T2(U): Count below T2(U)

    • DEV LSC(MAV): Process Mean - LSC

    • DEV LSC(T1T2): Process Mean - LSC

  • Requirement Event Statistics

    • #Due Data Collections: Count of expected Data collections only

    • #On-time Data Collections: Count of On-Time checks for Data collections only

    • #Missed Data Collections: Count of Missed checks for Data collection only

    • #Late Data Collections: Count of Late checks for Data collection only

    • #Due Checklists: Count of expected Checklists only

    • #On-time Checklists: Count of On-Time checks for Checklists only

    • #Missed Checklists: Count of Missed checks for Checklists only

    • #Late Checklists: Count of Late checks for Checklists only

  • Process Capability Indices

    CP, CPK, CPM, PP, PPK, PPM

  • Additional Information

    • Part Tags: List of tags associated with all the parts in the published data

    • Feature Tags: List of tags associated with all the features in the published data

    • Process Tags: List of tags associated with all the processes in the published data

  • Lot Statistics

    • #Pieces: Count of pieces

    • #OOS: Count of pieces out of spec

    • #Defects: Count of defects

    • #Defectives: Count of defectives

    • Mean

    • SD (LT): Long term standard deviation

    • PP

    • PPK

Use Case: Quality & Operational Management Reports

KPI Publishing is designed to easily facilitate the incorporation of Enact metrics and data into existing quality or operational reports or online dashboards. Consider the following examples of Enact metrics that might fit in to your existing reporting:

  • Sampling Compliance: Daily or by shift on-time data collection performance (%), which helps managers stay informed on their team's on-time data collection performance

  • Out of Specification Events: Counts of OOS events, which helps provide visibility into significant process variation issues

  • Yield: Daily or by shift, which helps managers stay informed on process yield issues

  • Lot Release: Helps managers make lot release decisions