Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We are excited to announce updates to our standard analytics data model, which includes the addition of new dimensions and fields. These updates are aimed at providing more granular insights into your data, specifically focusing on sub-job data. If your plant is using the sub-job feature in shoplogix, then you will find this data helpful to get more detailed and flexible insights into sub-job level details.

The following new dimensions have been added to the standard analytics data model:

...

production insights.

What are Sub-Jobs?

Sub-Jobs are a feature in Shoplogix that allows users to manage subproducts with different cycle factors for the same job. Sub-Jobs are defined as part of the job import process in Shoplogix.
If you are interested in using sub-jobs, or want to learn more, reach out to your Shoplogix representative to see if this feature is right for you.

Deployment and Data Refresh

...

  • Live Data Update: All live data (data within the last 60 days from , as of the deployment date in May 2024) will be updated to include the new dimensions.

  • Historical Data: Historical data will not automatically include the new dimensions. To update historical data, a history refresh must be requested from our support team.

...

  • Rollup/Summary by Sub-Job across multiple days or job instances

This works across multiple days or job instances

...

  • Scrap reasons and amounts by sub-job, also at rollup level across multiple job instances

This also works at a rollup level across multiple job instances

...

  • Breakdown of sub-job level data by Shift

...

  • Sub-Job Total Production Reporting: Reporting on Sub-Job Total Production in the same widget that is pivoted by scrap reason is not supported.

    • Widgets with scrap reasons filter out records without scrap, leading to potential data discrepancies.

...

Note

Notice that the second widget (without a scrap reason) has 2 extra job instance records that are missing in the first widget. If you add a scrap reason to a widget, it will filter out Fact Core records that do not have scrap assigned.

Scrap reasons should only be used in a widget that measures the actual sub-job scrap amount

  • Calculated Metrics Including Scrap (e.g., OEE): These metrics can only be accurately calculated at the parent job level.

    Sub-

    job level

    calculations may not account for all scrap, affecting accuracy

    .

...

Note

Notice above that the OeeProductive value (which is used to calculate OEE in Analytics) is the same for both sub-jobs even though one of them had scrap.
In order to accurately calculate OEE, it should be done at the parent job level, as this will ensure all sub-job level scrap is included in the calculation

...