Production Event Tracking

in the manufacturing industry, the process or processes which are directly related to creating value are these related to turning raw material into a sellable product success is typically measured profit which is at a high level calculates as revenue, which is typically the quantity of product sold at a specific price reduced by the combined cost associated with making this quantity this does include cost for raw materials utilities such as electricity, water and other liquids and industrial gases labor costs shipping cost recall cost / replacement cost / fines due to damage / poor quality to maximize profit, lowering the cost of making product is one of the most popular strategies, as increasing the price of your product is often a hard sell in a competitive market for reducing the cost of manufacturing, it is of utmost importance to identify where the biggest gains can be made with the least investment therefore, recording events related to making a product which include information related to runtime at each step wait times quality process values set points / recipe values utility consumption labor are the first step of being able to identify the root causes for high cost and identify solutions for reducing this cost scenario a manufacturing company creates four different products using four different lines and one common single separate station for quality testing to improve their competitiveness, the organizations seeks to record data related to their manufacturing process, with the goal to use these data to identify potential for improvements data of interest are especially runtime runtime per production step wait times between steps overall run time process and quality data quality results set points / recipe data in process data data related to cost energy consumption raw material quantity quantity of utility mediums like fluids and gases solution the company has litmus edge deployed on a line to line base as well as a dedicated litmus edge at the quality station data are collected both from the lines control system such as plc's as well as manual recorded through a litmus partner solution as the company also uses an energy management system, these data are also recorded through litmus edge as many of the triggers do require the monitoring of different tags as well as are only true if certain combinations of data are present, the trigger monitoring is performed through the flow provided by the solution https //portal litmus io/accelerators/litmus production record event processing flow the data collected for each trigger are send to litmus production record database and are organized and recorded there what triggers record what data? each line is capable of creating each of the four products, which in turn has its own distinct series of operations and steps to perform as the four different products do share some commonalities, a single data model is used where each event is identified by a unique combination of the product number and serial number the production process is considered as started, once an operator enters the product number and serial number and acknowledges this combination for this trigger, beside the product number and serial number, also the start time, asset and line are recorded further triggers are setup to monitor each specific production step like extrusion, drying, shaping and so on for each of these process steps, the start and end time are recorded as well as the operational set point and the process value at the start and end of the step at each line, the stations are connected via conveyer belt and a signal is recorded if a product does leave or access a station the transfer to the quality station is done via a tray system at the quality station, the operator does manually test each product which arrives using another litmsu partner solution for manual process recording the data recorded by this system include the product number and serial number which allows to append the quality data to the event record if the product do pass the test, the event is considered as finished and the final end time is recorded in case the part does fail, two options are available to the operator either the piece is marked as scrap, this will also close the event and record the end time with the final status of scrap if the piece is considered reworkable, it is returned to the line with a node what to do if the piece is then reworked, the respective operation is recorded again against the event for steps where data from the energy management system are available, the data for the start and end of the step is recorded to provide an indication about the amount of utilities used data model on litmus production record database the picture below shows a graphical representation of the data model the orange box shows the node name and therefore the name of the data model the blue boxes show the names of the stations as level 1 while the dark gray boxes are operations defined as level 2 operations are executed depended on the product and are not run for each product number green boxes show items recorded the purple boxes are the item which are also the identifiers for a production event the identifiers are what users will typically use to retrieve the data data models can be created using the litmus solution https //portal litmus io/accelerators/litmus production record data model configurator tag configuration on litmus production record database the picture below shows, which tags would need to be defined on each litmus edge as the minimum for both event trigger monitoring and as data for the recorded event the orange box represents the device name of the device on litmus edge, as litmus edge the blue boxed represent the tag names while the purple box the data type external event monitoring configuration used by litmus production record event processing flow the picture below shows the event trigger configurations which are used by flows using a flow like the litmus solution https //portal litmus io/accelerators/litmus production record event processing flow , allows the monitoring of triggers which depend on multiple tags such as for the start and end of the production process as each production line and the quality station have their own litmus edge, the flow will run on each of these devices running the respective configuration the processed data are all send to litmus production record database where the data can be stored correctly due to the identifiers transmitted the event monitoring configurations used by the flow downloadable from the litmus solution https //portal litmus io/accelerators/litmus production record event processing flow , can be defined using the litmus solution https //portal litmus io/accelerators/litmus production record external event configurator what data can look like the picture below shows how flexible the data recording for each event can be the last event, highlighted in red, shows how the quality of the product was first set to a fail state (value = 0) and went back to the line for rework