Difference between revisions of "Digital Factory:Digital Factory"

From Datonis
Jump to: navigation, search
(Maintenance with Datonis Digital Factory)
(Maintenance with Datonis Digital Factory)
Line 69: Line 69:
 
* Dashboards and Reports  
 
* Dashboards and Reports  
 
Various Personas that are involved in this app are:
 
Various Personas that are involved in this app are:
*# Maintenance Manager – Responsible for overall maintenance of operations. Responsible for running TPM program,  responsible for key metrics like OEE, MTBF, cost of spares, etc. Responsible for maintenance budget and expenses.  
+
* Maintenance Manager – Responsible for overall maintenance of operations. Responsible for running TPM program,  responsible for key metrics like OEE, MTBF, cost of spares, etc. Responsible for maintenance budget and expenses.
*# Maintenance Engineers/Supervisors – Typically working on field and responsible for actual operations.  
+
* Maintenance Engineers/Supervisors – Typically working on field and responsible for actual operations.
*# Production Operators and Supervisors - These are the team members who can raise a request for problems on the machines / tools they are working on.
+
* Production Operators and Supervisors - These are the team members who can raise a request for problems on the machines / tools they are working on.
*Workcenter maintenance Workflow--This will include regularly scheduled service, routine checks, and both scheduled and emergency repairs. It also includes replacement or realignment of parts that are worn, damaged, or misaligned. Machine maintenance can be done either in advance of failure or after failure occurs. Typically, an engineer / operator will be working on the machine for his day-to-day work. The maintenance department is responsible for the continuous operation of all machinery and systems necessary for a manufacturing facility.  
+
'''Workcenter Maintenance Workflow -''' This will include regularly scheduled service, routine checks, and both scheduled and emergency repairs. It also includes replacement or realignment of parts that are worn, damaged, or misaligned. Machine maintenance can be done either in advance of failure or after failure occurs. Typically, an engineer / operator will be working on the machine for his day-to-day work. The maintenance department is responsible for the continuous operation of all machinery and systems necessary for a manufacturing facility.
*# The first consists of planned shutdowns for maintenance and/or upgrades to the systems.
+
# The first consists of planned shutdowns for maintenance and/or upgrades to the systems.
*# Suddenly some breakdown occurs in the machine and the operator is seeking help from the maintenance department to correct it.
+
# Suddenly some breakdown occurs in the machine and the operator is seeking help from the maintenance department to correct it.
*# The Maintenance Department will have their regular guidelines / SOPs / TPM checks to work upon in order to keep the machines health and productivity as expected.
+
# The Maintenance Department will have their regular guidelines / SOPs / TPM checks to work upon in order to keep the machines health and productivity as expected.
*# For the sudden or unplanned breakdowns the maintenance engineer has to work on it to find the issue and take corrective actions against it.
+
# For the sudden or unplanned breakdowns the maintenance engineer has to work on it to find the issue and take corrective actions against it.
*# Maintenance Order is all the information about a maintenance task and outlines a process for completing that task. A work request is used by non-maintenance staff to make the maintenance team aware of a task. At times the maintenance department team will also create this as part of his job card.
+
# Maintenance Order is all the information about a maintenance task and outlines a process for completing that task. A work request is used by non-maintenance staff to make the maintenance team aware of a task. At times the maintenance department team will also create this as part of his job card.
 +
'''Maintenance Request ''' ''':'''A maintenance request is a request for maintenance, possibly raised by an operator, or a supervisor. Maintenance requests can be created for an asset (Workcenter / Tool) by specifying the description of the issue/problem. A maintenance supervisor has an ability to convert a maintenance request to maintenance order. Else, the requests can also be deleted. Maintenance App provides the option to create the maintenance Request from the Maintenance Dashboard. Operators can create maintenance request from console app. Supervisors can also raise the requests from Production Timeline from Productivity app.A maintenance request can have following information
 +
# Maintenance Of : Workcenter or a tool for which Operator / Supervisor is finding a problem and wants to raise a request.
 +
# Description : enter additional description of the maintenance request.
 +
# Priority : Allows users to assign priority of the request (High/Medium/Low).
 +
# Status : status of maintenance order (Open/In Progress/Closed).
 +
[[File:MaintReq.png]]
  
*'''Maintenance Request ''' ''':'''A maintenance request is a request for maintenance, possibly raised by an operator, or a supervisor. Maintenance requests can be created for an asset (Workcenter / Tool) by specifying the description of the issue/problem. A maintenance supervisor has an ability to convert a maintenance request to maintenance order. Else, the requests can also be deleted. Maintenance App provides the option to create the maintenance Request from the Maintenance Dashboard. Operators can create maintenance request from console app. Supervisors can also raise the requests from Production Timeline from Productivity app.A maintenance request can have following information
+
'''Maintenance Order ''' ''':'''A maintenance order is a directive to perform maintenance of one asset. Maintenance order specifies  the asset of which the maintenance is to be carried out, maintenance description along with additional information such as scheduled start/end time, priority, status, order number, type etc. The purpose of a maintenance order is to create a plan along with its schedule to ensure that timely maintenance of target assets is initiated and tracked. Maintenance Supervisor may initiate a new maintenance order in following cases:
*# Maintenance Of : Workcenter or a tool for which Operator / Supervisor is finding a problem and wants to raise a request.
 
*# Description : enter additional description of the maintenance request.
 
*# Priority : Allows users to assign priority of the request (High/Medium/Low).
 
*# Status : status of maintenance order (Open/In Progress/Closed).
 
[[File:MaintReq.png]]
 
*'''Maintenance Order ''' ''':'''A maintenance order is a directive to perform maintenance of one asset. Maintenance order specifies  the asset of which the maintenance is to be carried out, maintenance description along with additional information such as scheduled start/end time, priority, status, order number, type etc. The purpose of a maintenance order is to create a plan along with its schedule to ensure that timely maintenance of target assets is initiated and tracked. Maintenance Supervisor may initiate a new maintenance order in following cases:  
 
 
* Upon receiving a maintenance request from an operator (from operator dashboard).
 
* Upon receiving a maintenance request from an operator (from operator dashboard).
 
* Asset health is low as per the defined maintenance threshold.  
 
* Asset health is low as per the defined maintenance threshold.  
Line 102: Line 102:
 
# Created At : Datetime at which the order has been created.  
 
# Created At : Datetime at which the order has been created.  
 
# Assigned To : Email id of the user to whom the order has been assigned.  
 
# Assigned To : Email id of the user to whom the order has been assigned.  
*'''Maintenance Record''' ''':''' A maintenance record captures the actual maintenance work performed against the maintenance order. A maintenance record may fulfil multiple maintenance orders. Following information must be recorded.  
+
'''Maintenance Record''' ''':''' A maintenance record captures the actual maintenance work performed against the maintenance order. A maintenance record may fulfil multiple maintenance orders. Following information must be recorded.
*# Record Number This is an auto-generated number. The number will be generated on creation of any new maintenance record. Format is MR-n, where n is a number greater by 1 than the last maintenance record.  
+
# Record Number This is an auto-generated number. The number will be generated on creation of any new maintenance record. Format is MR-n, where n is a number greater by 1 than the last maintenance record.  
*# Associated Maintenance Orders : Users should be able to associate one or more maintenance orders with the maintenance record. When multiple orders are selected, those must belong to the same asset. Users should be allowed to select any of the open maintenance orders. Additionally, users should also be able to create and associate a new maintenance order. Table of associated orders should be displayed with following columns:
+
# Associated Maintenance Orders : Users should be able to associate one or more maintenance orders with the maintenance record. When multiple orders are selected, those must belong to the same asset. Users should be allowed to select any of the open maintenance orders. Additionally, users should also be able to create and associate a new maintenance order. Table of associated orders should be displayed with following columns:
*## Order Number
+
## Order Number
*## Description
+
## Description
*## Maintenance Of
+
## Maintenance Of
*## Maintenance Type
+
## Maintenance Type
*## Scheduled Start
+
## Scheduled Start
*## Scheduled End
+
## Scheduled End
*## Priority
+
## Priority
*## Actions [edit, delete]
+
## Actions [edit, delete]
*# Observations : Maintenance engineers may enter observations, if any.
+
# Observations : Maintenance engineers may enter observations, if any.
*# Work items: user (maintenance engineer) can record work items, if any. Work items are added as text. Table of work items should be displayed with following columns:
+
# Work items: user (maintenance engineer) can record work items, if any. Work items are added as text. Table of work items should be displayed with following columns:
*## Sr No
+
## Sr No
*## Work Item
+
## Work Item
*## Actions [edit, delete] to edit or delete the Work Item
+
## Actions [edit, delete] to edit or delete the Work Item
*# Spare Parts Used : List of spare parts used along with quantity,Table of spare parts used should be displayed with following details:
+
# Spare Parts Used : List of spare parts used along with quantity.
*## Sr No
+
# Consumables Used :List of consumables used along with quantity, if any. Users shall be able to select a consumable from a dropdown list (searchable list, displayed in format ‘<consumable_code>-<description>’.
*## Spare Part Code
+
# Maintenance Start Time : Actual start time of maintenance.
*## Description
+
# Maintenance EndTime :Actual end time of maintenance.
*## Quantity (values displayed shall be appended with unit of measure)
+
# Status : Status of maintenance record (Open/In Progress/Closed). On change, status of associated maintenance orders shall also get changed to the new value.
 
+
# Reset Maintenance Threshold : If set to True, resets the maintenance threshold of the asset for which maintenance has been performed. NOTE: maintenance is reset only when the status is changed to ‘Closed’. It should not get reset on save, when previous as well as the current status is ‘Closed’.
*# Consumables Used :List of consumables used along with quantity, if any. Users shall be able to select a consumable from a dropdown list (searchable list, displayed in format ‘<consumable_code>-<description>’.Table of consumables used should be displayed with following details:  
+
# Created By : Email id of the user who has created the maintenance record.
*## Sr No
+
# Created At :Date and time at which the record has been created.
*## Consumable Code
+
'''How to onboard the Maintenance App''':
*## Description
 
*## Quantity (values displayed shall be appended with unit of measure
 
  
*# Maintenance Start Time : Actual start time of maintenance.
+
Following are the easy steps with which maintenance department users can start using maintenance App
*# Maintenance EndTime :Actual end time of maintenance.
+
# Onboard assets (Workcenter and Tool) : By using Configuration App , add your Workcenter configuration in Digital Factory. This is the first step. You should add the Code, description and other necessary details of the Workcenter. Similarly one should add all the information for Tools using the Configuration app.  
*# Status : Status of maintenance record (Open/In Progress/Closed). On change, status of associated maintenance orders shall also get changed to the new value.
+
# Periodic Maintenance : To start with maintenance activity Digital Factory's Maintenance App gives us facility to define 2 kinds of maintenance Regime. By using configuration app under Workcentre onboarding one has to give information about following.[[File:MaintSchedule.png|thumb]]
*# Reset Maintenance Threshold : If set to True, resets the maintenance threshold of the asset for which maintenance has been performed. NOTE: maintenance is reset only when the status is changed to ‘Closed’. It should not get reset on save, when previous as well as the current status is ‘Closed’.
+
##Periodic Maintenance Regime : Maintenance Supervisors can decide the frequency based on calendar here. One can give a specific date under Set Maintenance Date or one can specify maintenance interval in days.[[File:MaintRegime.png|thumb]]
*# Created By : Email id of the user who has created the maintenance record.
+
## Runtime Based Maintenance Regime : Maintenance can be calculated based on the running ours of the asset. We call it as Runtime based maintenance. Here user can specify the no of hours after which the maintenance is due for the service. The setting has to be done under Maintenance Threshold (hrs) in Workcenter Configuration.
*# Created At :Date and time at which the record has been created.
+
## User has to also specify the Last Maintenance Done On for the further use.
*'''How to onboard the Maintenance App''': Following are the easy steps with which maintenance department users can start using maintenance App
+
## Based on the Maintenance Regime been set the application will calculate the Next Maintenance Due Date.
*# Onboard assets (Workcenter and Tool) : By using Configuration App , add your Workcenter configuration in Digital Factory. This is the first step. You should add the Code, description and other necessary details of the Workcenter. Similarly one should add all the information for Tools using the Configuration app.  
+
# Spare Parts and Consumable Masters : The next step is to upload / add the spare parts and consumable master inventory.  
*# Periodic Maintenance : To start with maintenance activity Digital Factory's Maintenance App gives us facility to define 2 kinds of maintenance Regime. By using configuration app under Workcentre onboarding one has to give information about following.
+
## Spare Parts- Maintenance activity may require replacement of spare parts. As a Maintenance Manager/Maintenance Engineer one should be able to maintain a list of Spare Parts which are needed in the asset maintenance. While creating a maintenance record, the user should be able to add the quantity of spare parts used, if any.Maintenance Supervisors will be able to track the inventory of spare parts used and cost associated with it in the maintenance activity.
*##Periodic Maintenance Regime : Maintenance Supervisors can decide the frequency based on calendar here. One can give a specific date under Set Maintenance Date or one can specify maintenance interval in days.
+
## Consumables : Consumables can be uploaded by using simple bulk uploads as part of master data upload activity. [[File:SpareParts.png|328x328px]][[File:Consumable.png|354x354px]]
*## Runtime Based Maintenance Regime : Maintenance can be calculated based on the running ours of the asset. We call it as Runtime based maintenance. Here user can specify the no of hours after which the maintenance is due for the service. The setting has to be done under Maintenance Threshold (hrs) in Workcenter Configuration.
+
## Both the Consumables and Spareparts will be having the lot code, vendor information.
*## User has to also specify the Last Maintenance Done On for the further use.
+
# Maintenance Request can be created when the operator or maintenance engineer look for a visual anomaly in the working of the machine.
*## Based on the Maintenance Regime been set the application will calculate the Next Maintenance Due Date.
+
# Maintenance Order : Maintenance Order can be created by the Maintenance Supervisor in order to work on the requisition been created in order to do an unplanned or planned maintenance activity on workcenter or Tools. The details of it it are created in above section.[[File:MaintOrder.png|334x334px]]
*# Spare Parts and Consumable Masters : The next step is to upload / add the spare parts and consumable master inventory. Spare Parts- Maintenance activity may require replacement of spare parts. As a Maintenance Manager/Maintenance Engineer one should be able to maintain a list of Spare Parts which are needed in the asset maintenance. While creating a maintenance record, the user should be able to add the quantity of spare parts used, if any.Maintenance Supervisors will be able to track the inventory of spare parts used and cost associated with it in the maintenance activity.
+
# Maintenance Record : Maintenance Record is the actual work done. The Maintenance engineer will add all the details for the work been done. Based on whether the maintenance is planned / routine work or an unplanned work to solve some problem occurred the maintenance record will be created. For a planned maintenance routine the user has to check the Reset Maintenance Threshold
*# Maintenance Request can be created when the operator or maintenance engineer look for a visual anomaly in the working of the machine.
+
# Condition Based Maintenance : Since the machine on the manufacturing shop floor is capable of giving real condition of various machine parameters via sensors, controllers etc, it becomes very much important to track the machine's condition based parameters while looking fro the maintenance perspective. Configuring the Maintenance specific parameters is also an important step here. We can add master data for maintenance app like Spare part inventory and Consumables.  Various maintenance parameters and checklists at different levels of assets and components. Administrative users (Production and Maintenance Managers/ Supervisors) can configure operating limits (USL, LSL, expected value). Administrators can configure the maintenance parameters under the Workcenter using Configuration app. Please refer to the screenshot reference here.
*# Maintenance Order : Maintenance Order can be created by the Maintenance Supervisor in order to work on the requisition been created in order to do an unplanned or planned maintenance activity on workcenter or Tools. The details of it it are created in above section.
 
[[File:MaintOrder.png]]
 
*# Maintenance Record : Maintenance Record is the actual work done. The Maintenance engineer will add all the details for the work been done. Based on whether the maintenance is planned / routine work or an unplanned work to solve some problem occurred the maintenance record will be created. For a planned maintenance routine the user has to check the Reset Maintenance Threshold
 
*# Condition Based Maintenance : Since the machine on the manufacturing shop floor is capable of giving real condition of various machine parameters via sensors, controllers etc, it becomes very much important to track the machine's condition based parameters while looking fro the maintenance perspective. Configuring the Maintenance specific parameters is also an important step here. We can add master data for maintenance app like Spare part inventory and Consumables.  Various maintenance parameters and checklists at different levels of assets and components. Administrative users (Production and Maintenance Managers/ Supervisors) can configure operating limits (USL, LSL, expected value). Administrators can configure the maintenance parameters under the Workcenter using Configuration app. Please refer to the screenshot reference here.
 
[[File:SpareParts.png]]
 
[[File:Consumable.png]]
 
  
 
==Checklist with Datonis Digital Factory==
 
==Checklist with Datonis Digital Factory==

Revision as of 13:45, 23 February 2022

Getting started with Datonis Digital Factory

Datonis Digital Factory is a cloud based application suite for digital transformation focused on a targeted set of users. This is used to bring the organizations (Plant) manufacturing related data together from many sources spreading across the multiple dimensions. Digital Factory is an enabler for IoT as well as not IoT systems which will help digitization as well as helps the manufacturer to look at various important elements. This gives a facility to use targeted app for targeted set of people. Digital factory helps in propagation of the information between systems / machines and various people (including shop floor operators). Following are the different aspects of Datonis Digital Factory.

Configuration with Datonis Digital Factory

We start with Configuration App. This is the space which is used to create the digital Twin of the Plant / Manufacturing Processes. This covers various onboarding activities like mentioned below:

  • Organisational Data: To start with one can onboard the logical hierarchy of the manufacturing assets (Workcenter) under Department, Cell /Line. The workcenter is the logical entity which represents the digital twin of the physical machine connected under IIOT process.The workcenter configuration will have various settings in terms of Automatic Booking, Maintenance settings etc as shown below.
  • Shift and Shift Plans: It will also allow to configure Shift and Shift Plans. Shift Plans are the calendar been created by the Shift Supervisor as per the Production Schedule.

Media:Shift Plan.png

  • Productivity Master Data Configuration app will also allow the administrators and supervisors to load the masters for Productivity
    1. Loading the Part masters with using application user interface or by using the bulk uploads provided. Supervisors can also add the Routing masters providing the cycle time, operation code and operation name and default workcenter on which this operation can be performed.
    2. Another important masters are for Downtime Reason codes, Performance Reason Codes. The downtime Codes will be used while calculating the Availability. And Performance Reason codes will be used while measuring the Performance Loss.
  • Alerts Configuration app will also allow the administrators to configure the alerts for various apps and types. Alerts configured can help the users to track the escalation around various activities happening in Plant.
    1. Productivity Alerts: These are the alerts intended to track various productivity aspects as mentioned below:
      1. To check if the Production is not happening and machines are in idle state
      2. To check the Production Rate
      3. To Check the KPI based alerts for e.g. Alert me if my Availability is below 70% for a workcenter or Alert me if OEE of the workcenter is below 60% etc
    2. Maintenance Alerts
      1. To track the maintenance parameters or condition based parameters of the machine to check the anomalies based on outlier.
      2. To track the maintenance of the workcenter if its due.

Media:Workcenter.png

Productivity with Datonis Digital Factory

Productivity is the important aspect of Datonis Digital Factory. It is one of the important application which showcases various production activities. However, at the same time as productivity is seen as one of the most vital factors affecting a manufacturing company’s performance and other aspects. Productivity Application covers various aspects. This mainly covers

  • Real Time monitoring of Production: Productivity app captures the real time monitoring of production which helps the supervisor and operators to track the production. We have different dashboards and analysis which will show what is happening in the Plant.
    1. Productivity KPIs: Productivity Application keeps an eye on computing various important productivity KPIs such as Availability, Performance, Quality and OEE.
    2. Realtime Timeline views tells the supervisor whats happening on the Cell or Line. Units can generally monitor this so that they can track the SKUs, their production and how good they are from their targets.
      1. Availability : This is very important KPI looked from Productivity. Datonis Digital Factory's Productivity Application give various aspects of Availability. While capturing Availability it takes into account Availability Losses, which includes any events that stop planned production for an appreciable length of time. There are various dashboards showing other details of availability. It also showcases the Planned and Unplanned Downtimes, Major and Minor Stoppages and Unbooked Downtimes. Productivity application also offers various reports like Downtime analysis and MTBF and MTTR Analysis at Cell and Workcenter levels.
      2. Performance : Performance – One of the three OEE Factors. Takes into account Performance Loss (factors that cause the process to operate at less than the maximum possible speed, when running). This should be measured in an OEE program, usually by comparing Actual Cycle Time (or Actual Run Rate) to Ideal Cycle Time (or Ideal Run Rate). This takes into account anything that causes the manufacturing process to run at less than the maximum possible speed when it is running (including both Slow Cycles and Small Stops).
      3. Quality : Quality takes into account manufactured parts that do not meet quality standards, including parts that need rework. Remember, OEE Quality is similar to First Pass Yield, in that it defines Good Parts as parts that successfully pass through the manufacturing process the first time without needing any rework.
  • Actions : Productivity Application allows to perform various manual actions such as Production Booking, Downtime Booking.
    1. Production Booking : This will be looking at which kind of Parts are produced in the specific time. This is an important action to measure the performance loss. The Production booking can happen using the Production Booking Option provided in Operator Console App or in Timeline view of Productivity App.
    2. Downtime Booking : Downtime booking will taking into consideration of what is the reason for the machine to go into the breakdown and leading to availability loss. The Downtime booking can happen using the Downtime Booking Option provided in Operator Console App or in Timeline view of Productivity App.
    3. Quality Booking : This facilitates the quality engineer to track the rejected quantity and reason for rejection. By this action it will help to compute Quality KPI in OEE.
  • Dashboards and Reports: There are various reports available for Production Supervisors and Plant heads to go through the Productivity App. There are various dashboards showing the current state of production as well. Productivity App also provides various trend reports to track various important KPIs.
    1. Productivity Dashboard: Plant dashboard presents KPIs at plant level and at cell level for the current working day. Additionally, the dashboard also displays maintenance and quality alerts for every cell. Following are the definitions of the displayed KPIs.Percent values represented are calculated based on weighted averages.
      1. Availability takes into account Availability Loss, which includes any events that stop planned production for an appreciable length of time.Availability = Actual Production Time / (Actual Production Time + Total Downtime - Planned Downtime)
      2. Performance takes into account Performance Loss, caused due to factors causing the process to operate at less than the desired speed. Evaluated by comparing Actual Cycle Time to Standard Cycle Time. Performance = Actual Production Time / Expected Production Time.
      3. Quality takes into account Quality Loss, due to manufactured parts that do not fulfill quality requirements. Quality = (Produced Qty - Rejected Qty) / Produced Qty
      4. OEE (Overall Equipment Effectiveness) is a measure of how well a manufacturing operation is utilized compared to its full potential, during the periods when it is scheduled to run. It identifies the percentage of manufacturing time that is truly productive. OEE = Availability * Productivity * Quality
      5. Planned Utilization measures the impacted production time due to planned downtime. Planned Utilization = (Available Time - Planned Downtime) / Available Time
      6. Uptime is a sum of running time of individual workcenters.Uptime = Total Time - Downtime
      7. Planned and Unplanned Downtime : Planned Downtime is a sum of duration of downtime marked with planned downtime reason codes. Planned Downtime = Downtime - Unbooked Downtime - Unplanned Downtime. Unplanned Downtime is a sum of duration of downtime marked with unplanned downtime reason codes. Unplanned Downtime = Downtime - Unbooked Downtime - Planned Downtime
    2. Cell / Line Productivity Analysis : Cell Productivity Analysis shows trends the last 30 days with an option to choose a custom timeline. This also shows a tabular view of the Productivity KPIs for each Workcenter under the selected Cell / Line A shift level view is also available to compare performance across shifts for the chosen period. An administrator can set appropriate preferences for configuring the dashboard.
    3. Workcenter Productivity Analysis :Important trend report showing various KPIs for the last 30 days when you land here and with an option to choose a custom Workcenter. This also shows a tabular view of the Productivity KPIs for selected Workcenter. A shift level view is also available to compare performance across shifts for the chosen period. An administrator can set appropriate preferences for configuring the dashboard.
    4. Downtime Analysis: This shows a downtime analysis for the selected Cell / Line. Also available at Workcenter level. By default trends are shown for the last 30 days. One can select Planned / UnPlanned filter to see the analysis of Downtime. One can also dig into a specific Downtime Category to further analyse. This shows Total unbooked down time, Total Booked Downtime, Top Downtime Categories for which the breakdown is observed in the selected time period. One can also see the bifurcation based on Top 3 reason codes with Downtime and Top 3 Workcenters having maximum Downtime in this period. It also shows a Bar graph showing the Downtime for each Downtime Code. A pie chart of downtime is also available at the bottom of the dashboard.

Additionally there are various other reports as well which can be used by the Production Team. Some examples are SKU Analysis, MTBF and MTTR Analysis etc.

Maintenance with Datonis Digital Factory

Maintenance App is the part of the Digital Factory which will have a framework to enable total predictive maintenance (TPM),  condition monitoring and predictive maintenance. Some of the high level functionalities of this app are.

  • Workcenter and Asset Onboarding : The ability to define components under an asset and monitor the condition of these sub components/assemblies separately along with that of the asset. These Workcenters can be either connected ones or non-connected ones.
  • Define the Maintenance Regime : In order to perform the maintenance activities we can define the Maintenance regimes as Time based on Periodic
  • Spare Parts and Consumables : Inventory management of spare parts and consumables can be done by using Maintenance App.
  • Vendor Master : Adding vendor data with simple bulk uploads.
  • Digital maintenance checklists: Defining the Checklist Templates as part of Planned Maintenance. Digitisation of SOPs, Documents, covering various aspects of maintenance and Employee Health and Safety by using Checklists
  • Engineering documentation : Users can also use and integrate the documents required for the Workcenters and Assets. These could be Maintenance SOPs, Maintenance Worksheets or any other important documents which is related to the assets and workcenters.
  • Looking at Total Preventive Maintenance (TPM) by using maintenance orders and maintenance records
  • Real time monitoring of various critical parameters of Workcenter. This will help monitoring the health of the workcenter and helps to capture the various capabilities over process like cp, cpk and other statistical capabilities. Condition Based Monitoring is the process of monitoring a parameter of condition in work center (vibration, temperature etc.), in order to identify a significant change which is indicative of a developing fault. Condition monitoring has a unique benefit in that conditions that would shorten normal lifespan can be addressed before they develop into a major failure.
  • Alerting on Maintenance adherence
  • Alerting on Spare Parts and Consumable inventory levels.
  • Dashboards and Reports

Various Personas that are involved in this app are:

  • Maintenance Manager – Responsible for overall maintenance of operations. Responsible for running TPM program, responsible for key metrics like OEE, MTBF, cost of spares, etc. Responsible for maintenance budget and expenses.
  • Maintenance Engineers/Supervisors – Typically working on field and responsible for actual operations.
  • Production Operators and Supervisors - These are the team members who can raise a request for problems on the machines / tools they are working on.

Workcenter Maintenance Workflow - This will include regularly scheduled service, routine checks, and both scheduled and emergency repairs. It also includes replacement or realignment of parts that are worn, damaged, or misaligned. Machine maintenance can be done either in advance of failure or after failure occurs. Typically, an engineer / operator will be working on the machine for his day-to-day work. The maintenance department is responsible for the continuous operation of all machinery and systems necessary for a manufacturing facility.

  1. The first consists of planned shutdowns for maintenance and/or upgrades to the systems.
  2. Suddenly some breakdown occurs in the machine and the operator is seeking help from the maintenance department to correct it.
  3. The Maintenance Department will have their regular guidelines / SOPs / TPM checks to work upon in order to keep the machines health and productivity as expected.
  4. For the sudden or unplanned breakdowns the maintenance engineer has to work on it to find the issue and take corrective actions against it.
  5. Maintenance Order is all the information about a maintenance task and outlines a process for completing that task. A work request is used by non-maintenance staff to make the maintenance team aware of a task. At times the maintenance department team will also create this as part of his job card.

Maintenance Request :A maintenance request is a request for maintenance, possibly raised by an operator, or a supervisor. Maintenance requests can be created for an asset (Workcenter / Tool) by specifying the description of the issue/problem. A maintenance supervisor has an ability to convert a maintenance request to maintenance order. Else, the requests can also be deleted. Maintenance App provides the option to create the maintenance Request from the Maintenance Dashboard. Operators can create maintenance request from console app. Supervisors can also raise the requests from Production Timeline from Productivity app.A maintenance request can have following information

  1. Maintenance Of : Workcenter or a tool for which Operator / Supervisor is finding a problem and wants to raise a request.
  2. Description : enter additional description of the maintenance request.
  3. Priority : Allows users to assign priority of the request (High/Medium/Low).
  4. Status : status of maintenance order (Open/In Progress/Closed).

MaintReq.png

Maintenance Order :A maintenance order is a directive to perform maintenance of one asset. Maintenance order specifies the asset of which the maintenance is to be carried out, maintenance description along with additional information such as scheduled start/end time, priority, status, order number, type etc. The purpose of a maintenance order is to create a plan along with its schedule to ensure that timely maintenance of target assets is initiated and tracked. Maintenance Supervisor may initiate a new maintenance order in following cases:

  • Upon receiving a maintenance request from an operator (from operator dashboard).
  • Asset health is low as per the defined maintenance threshold.
  • Planned maintenance of an asset.
  • Emergency maintenance in cases such as machine breakdown.

A maintenance order is consisted of:

  1. Order Number - This is an auto-generated number. The number will be generated on creation of any new maintenance order. Format is OD-n, where n is a number greater by 1 than the last maintenance order. Order number is not displayed while creating the maintenance order, but is visible while editing the order.
  2. Maintenance Of : The user will select the asset type (Workcenter OR Tool). Based on this selection, users should be able to select one Workcenter, or one Tool.
  3. Description : Additional description of the maintenance order.
  4. Maintenance Type :Allow users to check if the maintenance is Planned or Unplanned.
  5. Scheduled Start : Planned start time of maintenance.
  6. Scheduled End : Planned end time of maintenance.
  7. Priority : Allows users to assign priority to the order (High/Medium/Low).
  8. Status : status of maintenance order (Open/In Progress/Closed).
  9. Created By : Email id of the user who has created the maintenance order.
  10. Created At : Datetime at which the order has been created.
  11. Assigned To : Email id of the user to whom the order has been assigned.

Maintenance Record : A maintenance record captures the actual maintenance work performed against the maintenance order. A maintenance record may fulfil multiple maintenance orders. Following information must be recorded.

  1. Record Number This is an auto-generated number. The number will be generated on creation of any new maintenance record. Format is MR-n, where n is a number greater by 1 than the last maintenance record.
  2. Associated Maintenance Orders : Users should be able to associate one or more maintenance orders with the maintenance record. When multiple orders are selected, those must belong to the same asset. Users should be allowed to select any of the open maintenance orders. Additionally, users should also be able to create and associate a new maintenance order. Table of associated orders should be displayed with following columns:
    1. Order Number
    2. Description
    3. Maintenance Of
    4. Maintenance Type
    5. Scheduled Start
    6. Scheduled End
    7. Priority
    8. Actions [edit, delete]
  3. Observations : Maintenance engineers may enter observations, if any.
  4. Work items: user (maintenance engineer) can record work items, if any. Work items are added as text. Table of work items should be displayed with following columns:
    1. Sr No
    2. Work Item
    3. Actions [edit, delete] to edit or delete the Work Item
  5. Spare Parts Used : List of spare parts used along with quantity.
  6. Consumables Used :List of consumables used along with quantity, if any. Users shall be able to select a consumable from a dropdown list (searchable list, displayed in format ‘<consumable_code>-<description>’.
  7. Maintenance Start Time : Actual start time of maintenance.
  8. Maintenance EndTime :Actual end time of maintenance.
  9. Status : Status of maintenance record (Open/In Progress/Closed). On change, status of associated maintenance orders shall also get changed to the new value.
  10. Reset Maintenance Threshold : If set to True, resets the maintenance threshold of the asset for which maintenance has been performed. NOTE: maintenance is reset only when the status is changed to ‘Closed’. It should not get reset on save, when previous as well as the current status is ‘Closed’.
  11. Created By : Email id of the user who has created the maintenance record.
  12. Created At :Date and time at which the record has been created.

How to onboard the Maintenance App:

Following are the easy steps with which maintenance department users can start using maintenance App

  1. Onboard assets (Workcenter and Tool) : By using Configuration App , add your Workcenter configuration in Digital Factory. This is the first step. You should add the Code, description and other necessary details of the Workcenter. Similarly one should add all the information for Tools using the Configuration app.
  2. Periodic Maintenance : To start with maintenance activity Digital Factory's Maintenance App gives us facility to define 2 kinds of maintenance Regime. By using configuration app under Workcentre onboarding one has to give information about following.
    MaintSchedule.png
    1. Periodic Maintenance Regime : Maintenance Supervisors can decide the frequency based on calendar here. One can give a specific date under Set Maintenance Date or one can specify maintenance interval in days.
      MaintRegime.png
    2. Runtime Based Maintenance Regime : Maintenance can be calculated based on the running ours of the asset. We call it as Runtime based maintenance. Here user can specify the no of hours after which the maintenance is due for the service. The setting has to be done under Maintenance Threshold (hrs) in Workcenter Configuration.
    3. User has to also specify the Last Maintenance Done On for the further use.
    4. Based on the Maintenance Regime been set the application will calculate the Next Maintenance Due Date.
  3. Spare Parts and Consumable Masters : The next step is to upload / add the spare parts and consumable master inventory.
    1. Spare Parts- Maintenance activity may require replacement of spare parts. As a Maintenance Manager/Maintenance Engineer one should be able to maintain a list of Spare Parts which are needed in the asset maintenance. While creating a maintenance record, the user should be able to add the quantity of spare parts used, if any.Maintenance Supervisors will be able to track the inventory of spare parts used and cost associated with it in the maintenance activity.
    2. Consumables : Consumables can be uploaded by using simple bulk uploads as part of master data upload activity. SpareParts.pngConsumable.png
    3. Both the Consumables and Spareparts will be having the lot code, vendor information.
  4. Maintenance Request can be created when the operator or maintenance engineer look for a visual anomaly in the working of the machine.
  5. Maintenance Order : Maintenance Order can be created by the Maintenance Supervisor in order to work on the requisition been created in order to do an unplanned or planned maintenance activity on workcenter or Tools. The details of it it are created in above section.MaintOrder.png
  6. Maintenance Record : Maintenance Record is the actual work done. The Maintenance engineer will add all the details for the work been done. Based on whether the maintenance is planned / routine work or an unplanned work to solve some problem occurred the maintenance record will be created. For a planned maintenance routine the user has to check the Reset Maintenance Threshold
  7. Condition Based Maintenance : Since the machine on the manufacturing shop floor is capable of giving real condition of various machine parameters via sensors, controllers etc, it becomes very much important to track the machine's condition based parameters while looking fro the maintenance perspective. Configuring the Maintenance specific parameters is also an important step here. We can add master data for maintenance app like Spare part inventory and Consumables. Various maintenance parameters and checklists at different levels of assets and components. Administrative users (Production and Maintenance Managers/ Supervisors) can configure operating limits (USL, LSL, expected value). Administrators can configure the maintenance parameters under the Workcenter using Configuration app. Please refer to the screenshot reference here.

Checklist with Datonis Digital Factory

This is a framework for enabling TPM, TQM, Quality Control Plans, EHS improvement initiatives. Framework for enabling paperless operations. This helps in Covering digitization of TPM, TQM, Quality Control Plans, Maintenance & EHS improvement initiatives.Some of the features provided by Checklist are:

  • Checklist Templates : The templates are the masters to be added for various types of manual logbooks pertaining to Quality, TPM, Productivity types of checklists. This framework helps in Defining policies / Checklist templates. Administrators can add thease masters with filling simple forms. We will be able to capture various parameters in this template and basic configuration for scheduling, owner etc.
  • Checklist Recording can be done by the operators while they are working on the machine. This enables the users to record the readings for these policies or logbooks for the defined Checklist Templates. Calendaring of policies by user so as to track the adherence and discipline in reporting on entered data / compliance.
  • Provides capabilities to integrate variety of media like photos, videos,documents, symbols

Documentation

Documents App is the repository to manage / add / update various kinds of documents required for the manufacturing usage. The Administrators in the plant or units will make this as a single vault to mange various documents like various SOPs, documents, images, checklists etc. Documents app provides a single interface for uploading/managing documents.The repository is kept up to date so that no manual refresh required for fetching updated content. This has got following features:

    1. Document Management Lifecycle : The app facilitates to Upload, update/change, manage documents. Various image types, .pdfs, .txt, and other media types are supported. One can add the desired documents in the folder / directory. Users can created nested folders in the file system. All these actions will be audit logged.
    2. Searching made easy : It becomes very much important to search the documents easily when we build a big repository with various kind of documents. Documents app gives ability to search by specifying different criteria such as Tag based, Owner based searches, Based on the Created at etc.
    3. Integration with Digital Factory : Once the repository is built it becomes important for the users to refer to these various SOPs , manuals and reference documents while they are working on the machine.

BI

MInt supports the analytics application with the reports which the user can create on their own. This helps to show the descriptive analytical reports covering the Productivity Workspace from MInt. This helps in creating a rich set of data visualizations. It also provides an easy-to-use interface for exploring and visualizing data. This allows to create and share dashboards to the users. This is the DIY framework (Do It with Yourself) which will allow the user to create their own reports. There are out of the box following reports created:

  • Production Insight By Workcenter : This will show the Production KPIs like Uptime, Down Time, Availability, Performance, Quality , OEE, Planned vs Unplanned Time for each workcenter.
  • Production Trend : This report will show the Production trend across the days for all the Workcenters in the Organization.
  • Loss Insight : Loss Insight report will help to see the details about the losses happened. This helps to see which are the Losses having more time booked and also helps to see the losses per workcenter.
  • MTBF and MTTR : For the selected Loss/ Reason code this reports shows the Mean Time Between Failure and Mean Time To Recover.