Difference between revisions of "Analytics Data Model"

Revision as of 04:43, 29 July 2020

Data Model

The Analytics Data Model is divided into 4 sections:

1. Workcenter Shift Productivity Data Model
2. Part Shift Productivity Data Model
3. Hourly Data Model
4. Policy Data Model

Workcenter Shift Productivity Data Model

MInt Productivity data, that is data about performance. This data is rolled up at the shift level for shift level productivity analysis.

Here is a diagram that represents the data model. 

The main tables are: 

WorkcenterShiftFact: Productivity data is centred around a 'workcenter' (essentially a machine that is performing the task). This table contains the primary shift-level productivity parameters.

WorkcenterShiftDowntimeReasonsFact: Downtime represents the time duration for which the machine was non-operational. This table contains information about durations and reasons for the downtimes of a workcenter for a given shift.

WorkcenterShiftRejectionsFact: Rejections are the quality defects that occurred on a workcenter. The table contains information about these quality rejections for a workcenter for a shift and the reasons for it.

WorkcenterShiftOperatorsFact: This table contains information about the operators working on the workcenter for a given shift.

WorkcenterShiftProductivityDowntimeReasonsFact: Performance loss is the metric to highlight the less-than-ideal rate at which the machine was working. If the machine is working slower than the expected (ideal) rate, the user can book a performance loss and associate a reason for it. This table contains the performance loss downtime information.

WorkcenterShiftProductionParametersFact: The table contains Production parameter data at a shift level. Production parameters are used to store the production quantity in different units based on customer requirements.

e.g. Some customers want to measure production quantity in Batch Counts but for their internal assessment, they need Batch Weight. In such cases, MInt will show Batch Count and Batch Weight will be sent to their internal system (say the customer's ERP system).

Please refer to the following link for description of each table column.

Examples of using the object model to create a chart:

Here is an example video of how you can use the data model to analyze average OEE by Workcenters.

Part Shift Productivity Data Model

MInt Part Productivity data gives insights about your part level performance. This data is rolled up at the shift level for doing shift level part productivity analysis.

Here is a diagram that represents the data model.

The main tables are:

WorkcenterPartOperationShiftFact: The Part Productivity data is centred around a part that is being produced on the workcenter. This table contains the primary shift level part productivity parameters.

WorkcenterPartOperationShiftDownTimeReasonsFact: Downtime represents the time duration for which the machine was non-operational. This table contains information about the downtimes that occurred throughout the duration for which a part was booked within a shift and the reasons for those downtimes.

WorkcenterPartOperationShiftRejectionsFact: Rejections are the quality defects that occurred on a workcenter. The table contains information about these quality rejections for a part for a shift and the reasons for it.

WorkcenterPartShiftProductionParametersFact: The table contains Production parameter data at a part and shift level. Production parameters are used to store the production quantity in different units based on customer requirements.

e.g. Some customers want to measure production quantity in Batch Counts but for their internal assessment, they need Batch Weight. In such cases, MInt will show Batch Count and Batch Weight will be sent to their internal system (say the customer's ERP system).

Examples of using the object model to create a chart:

Here is an example video of how you can use the data model to analyze Part Cycle Times by Shift.

Hourly Data Model

MInt Hourly Data is aggregation of Condition Based Monitoring (CBM), Part Process Quality, and Performance. This data is rolled up at an hourly level.

Here is a diagram that represents the data model.

The main tables are:

WorkcenterHourlyFact: Productivity data is centred around a 'workcenter' (essentially a machine that is performing the task). This table contains the primary hourly level productivity parameters.

WorkcenterHourlyCbmParamsFact: Condition Based Monitoring (CBM) is the process of monitoring a key parameter in a workcenter (vibration, temperature etc.). This helps in locating a significant change which may be indicative of a developing fault in a machine. The table contains information about the CBM parameters, their control limits and details of violations.

WorkcenterHourlyProcessParamsFact: Process parameters are the parameters dependant on the part (temperature of Part-1, temperature of Part-2 etc.). This helps in identifying a significant change that may be indicative of developing a quality defect. The table contains information about the Process parameters, their control limits and details of violations.

WorkcenterHourlyProcessOperationFact: The table contains Part - Operation information for each part at an hourly level.

WorkcenterPartHourlyProdParamsFact: The table contains production parameter data at a part and hourly level. Production parameters are used to store the production quantity in different units based on Customer requirements.

e.g. Some customers want to measure production quantity in Batch Counts but for their internal assessment, they need Batch Weight. In such cases, MInt will show Batch Count and Batch Weight will be sent to their internal system (say the customer's ERP system).

Examples of using the object model to create a chart:

Here is an example video of how you can use the data model to analyze CBM Parameter Violations by Hour.

Policy Data Model

MInt Policy data gives information about your manual policy bookings. For e.g. Safety Checksheets, Part Dimension Checklists, etc. This data is then used for correlations with other process/ productivity parameters or to create dashboards from your manual booking data.

Here is a diagram that represents the data model.

Policy Object Model

The main tables are:

PolicySchedule: The table contains policy master data along with the schedule of the policy booking.

PolicyBooking: This table has the actual manually entered booking data for e.g. part length values, checklist values etc.