Show pageOld revisionsBacklinksExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== Table of Contents ====== * **Devices** * //The NIS in the line// * How to implement the NIS in the field\\ \\ * **Interfaces** * //The LED TV (Andon board)// * The Andon board interface * //The touch panel interface// * Advancement of the pieces * Declaring scrap * Tooling * Declaring stop for failure or slowdown * Declaring stop for organizational cause * Production change * The flashback function\\ \\ * **In the office** * //NIS web platform// * The main menu * Users * The environment * Non-compliant causes * Downtime causes * Productions * Utilities * //Reports// * Production line status * Efficiency * Reports * //OEE overview// * How does it works ====== NIS user handbook ====== ===== Devices ===== ==== The NIS in the line ==== **NIS** is an acronym that stands for Next Improve System. NIS allows the control and monitoring of production efficiency, both real time (Andon) and in a certain period (OEE).\\ \\ === How to implement the NIS in the field === To implement a NIS system, you need the following devices: * A TV LED (we recommend a size from 40 inches up) * A mini PC * A Tuch Panel * A Barcode reader * A PLC\\ \\ For each line production there will be a touch panel and a LED TV (The Andon board).\\ \\ {{:cli:franke:insieme-ott.jpg?1024| The NIS system}}\\ \\ \\ \\ Connected to the touch panel there is the barcode reader that will help the operator to **change the production order** and, in case of absence of the PLC, to **increase the number of pieces produced**.\\ The barcode reader is connected to the touch panel via a USB port. The touch panel is connected to the system via ethernet cable.\\ \\ {{:cli:franke:touch-barcode.jpg?1024| how to wire a touch panel}}\\ \\ {{:cli:franke:touch-panel.jpg?1024| The barcode reader}}\\ \\ \\ \\ The Mini PC is connected to the LED TV via HDMI port; it’s also connected to the system via ethernet cable.\\ \\ {{:cli:franke:led-tv.jpg?1024| LED TV and mini PC}}\\ \\ \\ \\ The main difference to a line without a PLC, concerns the signaling mode of the advancement of a piece: the PLC automatically sends a signal, when the operator performs the last operation.\\ Another signal from the PLC regards if the machine is running or not.\\ Each PLC can be connected to 4 machines because it is provided with 8 slots.\\ \\ {{:cli:franke:plc.jpg| The PLC}}\\ \\ \\ \\ ===== Interfaces ===== ==== The LED TV (Andon board) ==== The Andon board shows different data relating to the real time production. \\ \\ {{:cli:franke:andon-green2.png?1024| The Andon Board interface}}\\ \\ \\ \\ === The Andon board interface === At the top of the page, a horizontal bar shows the sequence of stops of any type (programmed stop, stop for maintenance, etc.).\\ In green, the time the line is running, in red when it is stopped, in blue when the stop si scheduled.\\ \\ {{:cli:franke:barra.png?1024| the sequence of stops}}\\ \\ \\ \\ Let's see the meaning of each element: * At the top on the left there is the «**Production Order code**» currently ongoing * At the top on the right there is the **date and time** * **Takt-time**: is the time that each operator has to carry out its task * **Expected items**: it represents the theoretical production * **Produced items**: it represents the number of produced products, both goods and scraps * **Remaining batch**: the number of pieces that remain to complete the entire lot production * **Non-compliant items**: the number of parts not good (scrap items) * **OEE**: on the right there is the OEE value expressed as a percentage, referred to the current shift. Single percentages are also specified for availability, speed and quality\\ \\ {{:cli:franke:elementi-interfaccia.png?1024| The Andon board interface}}\\ \\ \\ \\ Even the colors of some elements have a specific meaning.\\ **Green background**: the background is green when the number of the «Expected items» (for current production) is equal to the number of «Produced items».\\ \\ {{:cli:franke:andon-green2.png?1024| Green background}}\\ \\ \\ \\ **Yellow background**: the background is yellow when the number of the «Expected items» (for current production) is greater than one or two items compared to the number of «Produced items».\\ \\ {{:cli:franke:yellow2.png?1024| Yellow background}}\\ \\ \\ \\ **Red background**: the background is red when the number of the «Expected items» (for current production) is greater than the number of «Produced items» of three or more.\\ \\ {{:cli:franke:andon-red.png?1024| Red background}}\\ \\ \\ \\ Also the area “Non-compliant items” has its own background color. Now we see the meaning of these colors.\\ * **Green background**: there were non scrap items * **Yellow background**: there were one or two scrap items * **Red background**: there were three or more scrap items\\ \\ {{:cli:franke:non-compliant.png|Non-compliant items background}}\\ \\ \\ \\ Also the box that hosts the percentage of OEE will appear with different colors. * **Green**: the percentage value is greater then 81% * **Yellow**: the percentage value is between 71% and 80% * **Red**: the percentage value is between 0 and 70%\\ \\ {{:cli:franke:oee-percentage.png| OEE percentage}}\\ \\ \\ \\ These percentage values can be customizable line by line, so they may differ from those shown in this guide.\\ Likewise, the individual boxes of "Availability", "Speed" and "Quality" can take on different colors.\\ \\ ==== The touch panel ==== === The touch panel interface === This is the interface of the touch panel. \\ The red, blue, yellow and green areas are buttons that allow the operator to access certain functions.\\ \\ {{:cli:franke:cattura01.png?1024| The touch panel interface}}\\ \\ \\ \\ The «**Scrap items**» button provides access to a dialog box containing the datasheet of the loss of quality causes. The operator must specifies the appropriate.\\ For more information, see paragraph «**Declaring scrap**».\\ \\ {{:cli:franke:scrap-items.png| Scrap items}}\\ \\ \\ \\ The «**Tool changeover time**» button provides to start the setup process.\\ For more information, see unit «**Tooling**».\\ \\ {{:cli:franke:tooling.png| Tooling}}\\ \\ \\ \\ The «**Failure / Slowdowns**» button provides access to a dialog box containing the datasheets of the causes of the stops. \\ The operator must specifies the appropriate.\\ For more information, see unit «**Stop for failure or slowdown**».\\ \\ {{:cli:franke:failure.png| Failure / Slowdowns}}\\ \\ \\ \\ The «**Organizational**» button provides access to some particular stop causes that have to concern organizational factors.\\ The operator must specifies the appropriate cause.\\ For more information, see unit «**Declaring stop for organizational cause**»\\ \\ {{:cli:franke:organizational.png| Organizational}}\\ \\ \\ \\ Below the four buttons, you can read the name of the line and the order of production that is processed at that time.\\ \\ {{:cli:franke:line.png| Production order and production line name}}\\ \\ \\ \\ At the bottom on the left, there is the «**OP button**» that allow the operator to change the production order.\\ For more information, see unit «**Production change**»\\ \\ {{:cli:franke:op.png| production order change}}\\ \\ \\ \\ At the bottom on the right, there is the «**Flashing back**» button that allow the operator to switch, to SAP, quantity of produced units and non-compliant items.\\ For more information, see unit «**Flashback function**»\\ \\ {{:cli:franke:falshingback.png| Flashback function}}\\ \\ \\ \\ Near the «Flashing back» Button there is the buttun to **refresh** the page.\\ \\ {{:cli:franke:aggiorna.png| Refresh page}}\\ \\ \\ \\ === Advancement of the pieces === Here we’ll show how to do the advancement of the pieces (with or without a PLC).\\ **Without a PLC**\\ When the operator finishes all the operations, before moving on to the next piece, he/she will indicate the progress of the piece using the barcode reader, scanning the univoque item number.\\ \\ {{:cli:franke:worker.png?900| Advancement of the pieces with the barcode reader}}\\ \\ \\ \\ **With a PLC**\\ The main difference, to a line without a PLC, concerns the signaling mode of the advancement of a piece: it is the PLC that, automatically, sends a signal, when the operator performs the last operation.\\ \\ {{:cli:franke:worker2.png?900| Advancement of the pieces with the PLC}}\\ \\ \\ \\ The number of pieces will be updated on the Andon board (LED TV), under the heading «**Produced items**»\\ \\ {{:cli:franke:andon-green3.png?900|The Andon board}}\\ \\ \\ \\ === Declaring scrap === The following paragraph will show how the operator can declare the scrap items.\\ * Press the red area called «**Scrap items**» {{:cli:franke:01-bis.png?900| Scrap items}}\\ \\ \\ \\ * The operator has to choose from a list of causes {{:cli:franke:02-bis.png?900| The list of causes}}\\ \\ \\ \\ * Once the type of defect has been chosen, the operator can define the amount of pieces to be discarded {{:cli:franke:03-bis.png| the amount of pieces to be discarded}}\\ \\ \\ \\ A message will inform the operator that the scrap declaration has been successful\\ \\ {{:cli:franke:04-bis.png?900| Scrap declaration successful}}\\ \\ \\ \\ === Tooling === The following paragraph will show how the operator can start the tool changeover time.\\ * Press the blue area called «**Tool changeover time**» {{:cli:franke:05-bis.png?900| ool changeover time}}\\ \\ \\ \\ * The system will ask for confirmation of the choice to start the tooling {{:cli:franke:06.png| The system will ask for confirmation}}\\ \\ \\ \\ * Once the tooling has started, it will start blinking blue/orange for the entire duration.\\ \\ {{:cli:franke:07-bis.png?900| Blinking}}\\ \\ \\ \\ * Press the blinking area to end the tooling. The system will ask for confirmation. {{:cli:franke:08.png| The system will ask for confirmation}}\\ \\ \\ \\ === Declaring stop for failure or slowdwn === The following paragraph will show how the operator can stop the system for failure or slowdown\\ * Press the yellow area called «**Failure/slowdowns**» {{:cli:franke:01-bis2.png?900| Failure/slowdowns}}\\ \\ \\ \\ * The operator will have to choose the correct stop cause {{:cli:franke:02-bis24.png?900| Stop causes}}\\ \\ \\ \\ * The system will ask for confirmation of the choice {{:cli:franke:03ter.png?600| Ask for confirmation}}\\ \\ \\ \\ * Once the stop has started, it will start blinking yellow/orange for the entire duration {{:cli:franke:04-bis23.png?900| Blinking}}\\ \\ \\ \\ * Press the blinking area to end the stop machine. The system will ask for confirmation {{:cli:franke:05ter.png| Ask for confirmation}}\\ \\ \\ \\ * It’s also possible to switch from the stop machine, to tooling while stop is active {{:cli:franke:06tool.png?600| Begin tool changeover time}}\\ \\ \\ \\ === Declaring stop for organizational cause === The following paragraph will show how the operator can stop the system for an organizational cause\\ * Press the green area called «**Organizational**» {{:cli:franke:stop.png?1024| Organizational}}\\ \\ \\ \\ * The operator will have to choose the correct organizational stop cause {{:cli:franke:cause.png?1024| Orgaizational stop causes}}\\ \\ \\ \\ * The operator will have to confirm the choice {{:cli:franke:selezione_043.png?600| Ask for confirmation}}\\ \\ \\ \\ * Once the stop has started, it will start blinking yellow/orange for the entire duration {{:cli:franke:stop-active2blink.png?1024| Blinking}}\\ \\ \\ \\ * Press the blinking area to end the stop machine. The system will ask for confirmation {{:cli:franke:end-stoporg.png| Ask for confirmation}}\\ \\ \\ \\ * It’s also possible to switch from the stop machine to tooling while stop is active {{:cli:franke:stop-tool.png?1024| Begin tool changeover time}}\\ \\ \\ \\ === Production change === The following paragraph will show how to change a production\\ * Open the list of workorders and Press on the "**OP**" button to open the list. That list is sorted by release date in ascending order. {{:cli:franke:change-prod.png?1024| Change production}}\\ \\ \\ \\ * Choose the workorder from the list. Use the buttons at the bottom to navigate. {{:cli:franke:stepfirst.png?1024| Choose the workorder}} * Press the "**Play**" button on the desired workorder to start a new production. A confirmation message will be shown. {{:cli:franke:stepsecond.png?1024| start a new production}}\\ \\ \\ \\ * Verify information on the touch panel. The new production will be configured and the information about the selected work order, will be shown on the touch panel. {{:cli:franke:successfullychange.png?1024| The new production}}\\ \\ \\ \\ === The falshback function === The **flashback function** allows the operator to switch to SAP, quantity of units produced and non-compliant items.\\ * Press the button at the bottom on the right, representing the icon of a lightning {{:cli:franke:01fb.jpg?1024| Flashback function}}\\ \\ \\ \\ * Enter the RUEK code. By default, the system proposes the current production code. {{:cli:franke:cattura02ruek.png?1024| Enter the RUEK code}} * From this screen the operator can communicate the quantity of units produced up to that time, and the quantity of non compliant items. The operator may also modify: * the quantity of units produced (1) * the amount of non compliant items (2) * he can declare the order completed (3) * finally, the operator must press the "Flashback" button at the bottom right (4) {{:cli:franke:03ruek.jpg?1024| Flashback data to SAP}}\\ \\ \\ \\ * This is the screen to change the amount of units produced. {{:cli:franke:cattura04fb.png?1024| Change the amount of units produced}}\\ \\ \\ \\ * This is the screen to change the amount of non compliant items. {{:cli:franke:cattura05fb.png?1024| Change the amount of non compliant items}}\\ \\ \\ \\ * When the operator presses the "Flashback" button, the system asks for confirmation of the operation {{:cli:franke:cattura06fb.png?1024| Ask for confirmation}}\\ \\ \\ \\ === Tracking maintenance === It's possible to **track the maintenance** during a stop machine.\\ When the resource has a stop machine running, two additional buttons will be shown.\\ \\ {{:cli:franke:screen2.png?1024| stop machine running }}\\ \\ \\ \\ The operator will press the green one with the wrench icon and then will confirm the choise.\\ Success / error message will be shown based on the result of the operation.\\ Now, the green button become grayout (disabled) and the other button with the wrench icon become red: the operator has to press it to end the maintenance.\\ The running stop machine remains as is until the operator press the yellow blinking button “failure / slowdowns”.\\ \\ ===== In the office ===== ==== NIS web platform ==== === The main menu === From the office the user will be able to **view**, **manage** and **customize** the entire NIS system.\\ All the operations the user can do are listed in the main menu. The menu provides different entries, depending on who is logged.\\ This is the menu that can see a user with the role of administrator.\\ \\ {{:cli:franke:main-menu3.png?900| The manin manu}}\\ \\ \\ \\ The «**Environments**» section contains some general voices describing users, departments, lines, shifts, cycle time adjustments and scheduled pauses.\\ Through each single entry the user will be able to make settings and changes related to the context.\\ We will deepen this topic in the paragraphs «**Users**» and «**The environment**».\\ \\ {{:cli:franke:environment.png| Environment}}\\ \\ \\ \\ The «**Causes**» section represents the list of possible downtime or non-compliant causes.\\ We will deepen this topic in the paragraphs«**Non-compliant causes**» and «**Downtime causes**».\\ \\ {{:cli:franke:causes.png| Causes}}\\ \\ \\ \\ The «**Production**» section contains the list of products, the list of production orders, and the list of active productions at the moment.\\ We will deepen this topic in the paragraph «**Productions**».\\ \\ {{:cli:franke:productions.png| Productions}}\\ \\ \\ \\ In the «**Utilities**» section, there are three entries «**Devices status monitor**», «**PLC Signals**» and «**User manual**».\\ The first, gives access to the list of all devices involved and some control functions; the second shows the signals of a specific PLC; the third gives direct access to a web version manual.\\ We will deepen this topic in the paragraph «**Utilities**».\\ \\ {{:cli:franke:utilities.png| Utilities}}\\ \\ \\ \\ The «**Production line status**» section lists the monitored lines.\\ Through this list you will be able to view the data of each line, relating to the Andon: you will be able to view the screen of the Andon board (TV LED) and also the screen of the touch panel.\\ We will deepen this topic in the paragraph «**Production line status**».\\ \\ {{:cli:franke:production-line-status.png| Production line status}}\\ \\ \\ \\ The «Efficiency» section lists the monitored lines.\\ Through this list you will be able to view the OEE of today's turn, but you will also be able to view the OEE of that line in a certain period of time.\\ We will deepen this topic in the paragraph «**Efficiency**».\\ \\ {{:cli:franke:efficiency.png|}}\\ \\ \\ \\ === Users === The NIS web platform has several roles.\\ Using the "**Users**" button, you can add new users, associating it with one or more roles. Depending on the role, each user will have access to different views and functions.\\ Users and groups can be managed only if the logged in user has the «**Administrator**» level of rights.\\ \\ {{:cli:franke:environment2.png| Users}}\\ \\ \\ \\ After clicking on the "**Users**" button, the user have access to the list of already registered users, displaying //Name//, //Surname//, //username//, //e-mail//, and the //roles// associated with each of them.\\ \\ {{:cli:franke:users1-bis.png?1024| List of users}}\\ \\ \\ \\ * «**Add**»: by clicking it, we can add a new user. * «**Edit**»: by clicking it, we can modify a user after selecting it. * «**Delete**»: by clicking it, we can cancel a user after selecting it. * «**Export XLS**»: by clicking on it, we can export this table in Excel format. * «**Groups management**»: by clicking on it, we can edit an existing role or add a new role.\\ \\ {{:cli:franke:buttons2.png?1024| Functions}}\\ \\ \\ \\ To add a new user, you have to click on "**Add**". This is the form to fill in to add a new user: "**Code**" (username) and "**Name**" are necessary.\\ \\ {{:cli:franke:buttons3.png| Information}}\\ \\ \\ \\ === Groups === By clicking on "**Groups management**" you can access the list of existing roles. Currently they are: //Administrator//, //Master Data Manager//, //OEE Managers// and //Supervisors//.\\ Each role is enabled to perform specific functions: * **Administrator**: all functions enabled. * **OEE manager**: environment configurations, scrap and stop machine causes, OEE summary, reports. * **Supervisor**: all functions except users and groups management\\ \\ === The environment === The remaining entries of the menu "**Environment**", are used to define the environment in which the NIS system is operational.\\ So this section include the departments and lines involved, the length of the shifts, the cycle time adjustment, and the the scheduled pauses.\\ \\ {{:cli:franke:environment3.png| The environment}}\\ \\ \\ \\ == Departments == This section will show the list of departments where the NIS system is installed.\\ A department can contain one or more production lines.\\ The user who has the rights to edit this section can add new departments or edit/delete existing ones, or export this table in Excel format.\\ \\ {{:cli:franke:departments.png?900| The departments}}\\ \\ \\ \\ == Production lines == This section will show the list of production lines where the NIS system is installed.\\ The user who has the rights to edit this section, can add new production lines or edit/delete existing ones, or export this table in Excel format.\\ \\ {{:cli:franke:production-lines.png?900| Production lines}}\\ \\ \\ \\ The user, when adds or edits an existing line, will have to set some values such as: * the department to which the line belongs * the number of workers (zero means gathered from ERP) * the number of shifts * setting **OEE percentages**, which will be represented by red, yellow and green * setting the **Cycle Time Factor** * setting the thresholds for OEE, failure, tooling and scraps reports (monthly and daily) (//see also paragraph «**Reports**»//)\\ \\ {{:cli:franke:edit-line.png?900| Editing line}}\\ \\ == Shifts == this section will show the list of planned shifts.\\ The user can add a new shift, or edit an existing shift. He will have to set the start and end of each turn.\\ The user can also delete an existing shift.\\ \\ {{:cli:franke:shifts.png?900| Shifts}}\\ \\ \\ \\ == Cycle time % adjustment == The Cycle time is based on the cycle time gathered from ERP or manually entered by the operator in case of NO ERP data exchange.\\ It’s coupled by articole code and the line involved. Examples of coefficient adjustments.\\ * 50% => cycle time halved * 100% => no change applied * 200% => cycle time doubled\\ \\ {{:cli:franke:cycle-time.png?900| Cycle time % adjustment}}\\ \\ \\ \\ == Scheduled pauses == this section shows the list of scheduled pauses. The user can add a new scheduled pause.\\ \\ {{:cli:franke:scheduled00.png?900| Scheduled pauses}}\\ \\ \\ \\ Before adding a new scheduled pause, the user will need to select a production line.\\ \\ {{:cli:franke:scheduled02.png?900| Start time and duration}}\\ \\ \\ \\ Finally, the user have to specify the start time of the pause and its duration.\\ \\ {{:cli:franke:scheduled.png| Selecting a production line}}\\ \\ \\ \\ === Non-compliant causes === The "**Causes**" section allows the user to manage both the causes of quality problems and machine stops\\ \\ {{:cli:franke:causes01.png| Non-compliant and downtime causes}}\\ \\ \\ \\ The section **Non-compliant causes** shows the list of non-compliant causes provided.\\ The user can add a new cause, cancell or modify an existing one.\\ \\ {{:cli:franke:causes000.png?900| Non-compliant causes}}\\ \\ \\ \\ When adding a new non-compliant cause, the user have to give a description and to associate a resource (a production line).\\ \\ {{:cli:franke:add-causes.png?900| Adding a new non-compliant cause}}\\ \\ \\ \\ === Downtime causes === The **downtime causes** are all those causes that lead to a stop in production.\\ Causes can be of different kind (//failure//, //scheduled// or //slowdown//) and have been organized in three different depths, helping to define more and more in detail the cause of stop\\ \\ == Downtime causes – Lev. 1 == This section shows the list of causes for first level.\\ Each item in the table specifies an identifier code, a description, the type (failure, scheduled or slowdown), the level (1st, 2nd or 3rd).\\ \\ {{:cli:franke:downtime02.png?900| Downtime causes}}\\ \\ \\ \\ The user who has the rights to edit this section can add new downtime causes or edit/delete existing ones, or export this table in Excel format.\\ Adding a new downtime causes, the user will have to set some values such as: * Code and ERP code * A description of the downtime causes (Ex. «Planned – Lunch») * A type («Failure», «Scheduled» or «Slowdown») * If it is or not, an organizational causes * The resource (line) involved * The level * Sort of index * OEE stratification (the user have to select a reason of the stop. See also the paragraph «**Reports**»)\\ \\ {{:cli:franke:add-downtime.png?900| Adding a downtime}}\\ \\ \\ \\ == Downtime causes – Lev. 2 & 3 == The tables relating to the downtime causes of 2nd and 3rd levels are similar to each other, //but are different from the table of the downtime causes of 1st level//.\\ \\ {{:cli:franke:downtime03.png?900| Downtime causes – Lev. 2 & 3}}\\ \\ \\ \\ In these tables there is a column reporting the description of the previous level («Level 1» or «Level 2»): in this way it is clear at what level, each sub-level belongs.\\ \\ {{:cli:franke:downtime04-bis.png?900| Levels and sub-levels}}\\ \\ \\ \\ === Productions === In this section, the user will be able to manage all the products and related production orders and to view and modify the active productions.\\ \\ {{:cli:franke:productions00.png| Productions}}\\ \\ \\ \\ == Products == This section shows the list of all products.\\ \\ {{:cli:franke:products.png??900| Products}}\\ \\ \\ \\ Adding a new product or editing an existing one, the user will have to set some values such as: * a code * a description * the related production line (optional)\\ \\ {{:cli:franke:add-product.png| Add a product}}\\ \\ \\ \\ == Production order == This section shows the list of production orders.\\ {{:cli:franke:production-order.png?900| Production order}}\\ \\ \\ \\ The information in this table relates to: * the article * the code of the production order * the ERP code * the number of items provided * the lines where it is possible to work the article, its cycle time and the number of workers involved\\ \\ {{:cli:franke:add-production-order.png?900| Production order table}}\\ \\ \\ \\ == Active productions == This section shows the list of active productions at this time.\\ The information in this table relates to the production order being processed in each line, the cycle time and the start time.\\ \\ {{:cli:franke:active-productions.png?900| Active productions}}\\ \\ \\ \\ Adding a new active production or editing an existing one, the user will have to provide some data: * the line * the production order * the takt time\\ \\ {{:cli:franke:add-active-productions.png| Adding an active production}}\\ \\ \\ \\ === Utilities === The "**Utilities**" menu allows the user to navigate some aspects of hardware\\ \\ {{:cli:franke:utilities00.png| Utilities}}\\ \\ \\ \\ == Devices status monitor == This section shows the list of all devices involved in the NIS system.\\ For all devices it is possible to know: //IP address//, //MAC address//, //Name//, //Type// (Tablet, PLC, Computer), //Asset// (NeXT ID), //ID Kiosk//, //Status and History//.\\ \\ {{:cli:franke:devices2.png?900| Devices}}\\ \\ \\ \\ Through the column «**Status**» the user can to check the status of the device, if it is working or not.\\ \\ {{:cli:franke:check.png| Status}}\\ \\ \\ \\ The "**History**" feature allows the user to see the history of the device's status. These are automatically recorded every 5 minutes.\\ \\ {{:cli:franke:history.png?900| History}}\\ \\ \\ \\ == PLC signals == This function allows the user to monitor the signals of a specific PLC.\\ Entering the **PLC Asset Code** (//PLC NeXT ID//) will display all PLC inputs. For each input we can know the type of signal associated and the number of received signals.\\ Green color means that the signal is 1 (the machine is running or a pieces is counted); white color means that the signal is 0 (the machine is stopped or a piece is not completed)\\ \\ {{:cli:franke:plc.png?900| PLC signals}}\\ \\ \\ \\ == User manual == This function allows the user to open the //NIS system guide// in a web version.\\ \\ {{:cli:franke:manuale.png| User handbook}}\\ \\ \\ \\ ==== Reports ==== Through the NIS web application the user can view some reports. === Production line status === This section shows the list of departments involved in the NIS system.\\ \\ {{:cli:franke:oee-overview.png| Departments involved in the NIS system}}\\ \\ \\ \\ By clicking on one of the departments (for example, «//Hohlkorperline//»), the user can see a summary of the real time efficiency of the lines (six in this case) in that department.\\ \\ {{:cli:franke:andon2.png?900| The summary of the real time efficiency}}\\ \\ \\ \\ At the top on the right of each box there are two buttons: * the button on the left (1) allows to display the TV LED screen; * the button on the right (2) allows to display the touch panel screen.\\ \\ {{:cli:franke:tv-touchpanel.png| TV LED and touch panel}}\\ \\ \\ \\ (1) This is an example of a TV LED screen, present on each line.\\ The detailed description of the information shown on the LED TV can be found in the paragraph «**The Andon board interface**»\\ \\ {{:cli:franke:andon3.png?900| TV LED screen}}\\ \\ \\ \\ (2) This is an example of a touch panel screen, present on each line.\\ The detailed description of the touch panel interface can be found in the paragraph «**The touch panel interface**»\\ \\ {{:cli:franke:touch-panel.png?900| Touch panel screen }}\\ \\ \\ \\ === Efficiency === This section shows the list of departments involved in the NIS system.\\ \\ {{:cli:franke:oee.png| Departments involved in the NIS system}}\\ \\ \\ \\ By clicking on one of the departments (for example, «Hohlkorperline»), the user can see a summary of the Overall Equipment Effectiveness (OEE) value\\ \\ {{:cli:franke:oee2bis.png?900| OEE summary}}\\ \\ \\ \\ At the top on the right of each box there is a button. It allows: * to display the OEE value of that line, in a certain period * to access to some reports \\ \\ {{:cli:franke:oee-detail.png| OEE details}}\\ \\ \\ \\ Thie following image shows the OEE interface. By default, it shows the OEE value of the current day, hour by hour, starting from the beginning of the shift.\\ \\ {{:cli:franke:oee3.png?900| OEE}}\\ \\ \\ \\ At the top of the interface the user can choose the line to be analyzed, the time span to view (today, yesterday, current week, last week, current month, last month, current year last year).\\ \\ {{:cli:franke:turno2.png| OEE}}\\ \\ \\ \\ Below, we find a series of buttons that allow the user to view a series of reports.\\ This topic will be discussed in the paragraph «**Reports**».\\ \\ {{:cli:franke:reports.png| Reports}}\\ \\ \\ \\ In the middle of the interface, a series of histograms show the OEE value, hour by hour.\\ The different colors refer to: * Yellow: stop for a quality problem (scrap) * Blue: speed loss * Red: stop machine * Green: the OEE\\ \\ {{:cli:franke:oee4.png?900| OEE}}\\ \\ \\ \\ At the bottom of the interface you can see **details** about losses due to machine stops and scraps.\\ The duration of each stop is immediately visible.\\ {{:cli:franke:details.png?900| Details about losses}}\\ \\ \\ By clicking on «**Details**» you can deepen the knowledge by going to see the start and end of each stop.\\ \\ {{:cli:franke:details00.png| Details}}\\ \\ \\ \\ Here the user can see the stops (not scheduled) that contribute to the amount of minutes we saw in the previous screen. For each stop we know the start time and the end time.\\ The user can export this table in excel format.\\ \\ {{:cli:franke:details3.png?900| start and end of each stop}}\\ \\ \\ \\ In the following chart, the user can find a variety of information. * total items produced * items processed for one hour * cadence * non-compliant items * time available * stop minutes * RF: Machine efficiency * RV: efficiency of machine availability * RQ: Object quality efficiency * OEE\\ \\ {{:cli:franke:grafico.png| Graph}}\\ \\ \\ \\ === Reports === From the OEE interface, the user can view a series of specific reports\\ \\ {{:cli:franke:menu-reports.png| Reports}}\\ \\ \\ \\ == Recalculate == The "**Recalculate**" function allows the NIS system to recalculate the OEE.\\ For example, this function is very useful if, at a later time, the cause of a stop has to be changed: from a stop programmed to an unplanned stop.\\ This change affects the calculation of OEE, so a recalculation is required.\\ \\ {{:cli:franke:recalculate.png?900| Recalculate}}\\ \\ \\ \\ == Tabular OEE data == This feature allows the user to view all OEE data in tabular form. This table can also be exported to Excel format.\\ \\ {{:cli:franke:tabular-oee.png?900| Tabular OEE data}}\\ \\ \\ \\ == OEE stratification == The "**OEE stratification**" function allows the user to view all causes of stop (block, minor stop, TPM, Scraps & Rework, Toolchange, Speed Losses, Startup / Shutdown) and the value of the OEE.\\ The goal is achieved using a graph that highlights the most frequent stops in the selected time span.\\ \\ {{:cli:franke:oee-stratification.png?900| OEE stratification}}\\ \\ \\ \\ == Productions == This function allows the user to view a list of productions made in the selected time frame in a table format.\\ The user can read the order of production, the article code, the cycle time, the number of items produced, the number of non-compliant items, the start time of processing, the end time of processing.\\ \\ {{:cli:franke:productionsbis.png?900| Productions}}\\ \\ \\ \\ == Movements == This function allows the user to view the entire list of events, in the time interval selected: produced items, cycle time, type of movement (load or downtime), cause of downtime, type of downtime, duration of downtime, non-compliant items.\\ \\ {{:cli:franke:movements.png?900| Movements}}\\ \\ \\ \\ == Cellboard Reports – OEE effective production == In this report, the user can see the monthly and daily OEE value (relative to the selected month).\\ In red, the user can see the treshold limit configured under "//Production lines//" in the "//Environment//" menu.\\ \\ {{:cli:franke:selezione_599.png?900| OEE effective production}}\\ \\ \\ \\ == Cellboard Reports – setup percentage == This function reports, on the left, as a percentage, the length of setup (tooling) over the entire time span (monthly).\\ On the right, this function shows, the time in minutes of setup, compared to the entire time span (daily).\\ \\ {{:cli:franke:selezione_604.png?900| Cellboard Reports – setup percentage}}\\ \\ \\ \\ == Cellboard Reports – setup average == This function shows the average length of the setup (tooling) in minutes, each month (on the left) or day by day in the selected month (on the right).\\ \\ {{:cli:franke:selezione_605.png?900| Cellboard Reports – setup average}}\\ \\ \\ \\ == Cellboard Reports – downtime percentage == This function reports, on the left, as a percentage, the length of downtime over the entire time span (monthly).\\ On the right, instead, this function shows, the time in minutes of downtime, compared to the entire time span (daily).\\ \\ {{:cli:franke:selezione_606.png?900| Cellboard Reports – downtime percentage}}\\ \\ \\ \\ == Cellboard Reports – downtime Pareto == This function shows the various causes of downtime that have occurred, in percentage, using the Pareto graph.\\ \\ {{:cli:franke:selezione_607.png?900| Cellboard Reports – downtime Pareto}}\\ \\ \\ \\ == Cellboard Reports – scrap items == This function reports, as a percentage, the length of scrap items over the entire time span (monthly on the left, daily on the right).\\ \\ {{:cli:franke:selezione_610.png?900| Cellboard Reports – scrap items}}\\ \\ \\ \\ == Cellboard Reports – scrap Pareto == This function shows the various causes of quality problems that have occurred, in percentage, using the Pareto graph.\\ \\ {{:cli:franke:selezione_609.png?900| Cellboard Reports – scrap Pareto}}\\ \\ \\ \\ ==== OEE overview ==== === How does it works === The OEE overview is the central application for management. It allowed: * hierarchical organization of the Franke group based on macro areas * step by step focus on macro areas, plants, departmens, production resources * data warehouse used for computation The hierarchical order is: * Franke * macroarea (eg "Sinks stainless steel") * plants * departments * production lines\\ \\ {{:cli:franke:menu-overview.png?900| The OEE overview menu}}\\ \\ \\ \\ Once you click on a macro area, you can see: * the plants that are part of it (sub-locations). * the monthly OEE value (with graph) * the last day OEE value (with graph)\\ \\ {{:cli:franke:selezione_613.png?900| The macroarea view}}\\ \\ \\ \\ Sub-locations tabular summary * OEE of selected month with trend indicator (related to the previous month) and % variation * OEE of last day with trend indicator (related to the previous day) and % variation * direct access to detailed information of the single sub-location\\ \\ {{:cli:franke:selezione_616.png?900| Sub-locations tabular summary}}\\ \\ \\ \\ **OEE of selected month** * W: worked time (hours) * U: unplanned stops (hours) * P: planned stops (hours) * colors are based on OEE thresholds (same as andon boards)\\ \\ Trend percentage between current selection and previous period * selected month => previous month * colors are based on predefined percentage values (-10%, -5%, 0, +5%, +10%) {{:cli:franke:selezione_614.png| OEE of selected month}}\\ \\ \\ \\ **OEE of last day** * W: worked time (hours) * U: unplanned stops (hours) * P: planned stops (hours) * colors are based on OEE thresholds (same as andon boards)\\ \\ Trend percentage between current selection and previous period * last month => the day before * colors are based on predefined percentage values (-10%, -5%, 0, +5%, +10%) {{:cli:franke:selezione_615.png| OEE of last day}}\\ \\ \\ \\ **Sub-locations graph summary** * monthly OEE * daily OEE related to the selected period (month, year) * thresholds defined for C.I.C. reports\\ \\ {{:cli:franke:selezione_618.png?900| Sub-locations graph summary}}\\ \\ \\ \\ ===== The OEE ===== ==== Definition ==== OEE (Overall Equipment Effectiveness) measures how close you are to perfect production (manufacturing only good parts, as fast as possible, with no stop time). OEE correlates **real production** with the **ideal production** planned.\\ The difference between these two values represents the loss of production in terms of: * **RF = Availability (Time)** * **RV = Performance (Speed)** * **RQ = Quality**\\ \\ There are three kind of losses: * **Availability Loss**: an availability score of 100% means that the process is always running during **planned production time** (the time your process is scheduled to run). Any time the process is not running due to an unplanned stop (e.g., some type of mechanical failure) or a planned stop (e.g., cleaning) is an Availability Loss * **Performance Loss**: a performance score of 100% means that the process is running as fast as possible. Performance can be calculated as the ratio of **Actual Run Rate** to **Theoretical Maximum Rate** (the design capacity of a machine or process) * **Quality Loss**: a quality score of 100% means that the process is only making good parts. Quality is the ratio of **Good Material** to **All Material**. Some process applications only produce good materials, while others may have Quality Loss due to non-conforming materials.\\ \\ ==== How to calculate the OEE ==== The OEE is simplified in the multiplication of the indexes described above, then **OEE = RF x RV x RQ**\\ * Availability (RF) = ? Run Time / ? Planned Production Time, that is >> **RF=(d-s)/d** [d=time availability; s=stops]; * Performance = ? (Ideal Cycle Time × Total Parts) / ? Run Time that is >> **RV=(CtxNp)/(d-s)** [Ct= cycle time; Np=Number of pieces]; * Quality = ? Good Parts / ? Total Parts, that is >> * **RQ=(Np-Nc)/Np** [Nc= non-compliant pieces]\\ \\ NIS classifies stop-cause in **3 classes**: * **Not programmed Stop (F)**: it's required a causalization of stop * **Programmed Stop (P)**: the worker set the begin and the end of this kind of stop using touch panel * **Micro-stop (M)**: it's not required a causalization of the stop \\ \\ cli/franke/nis_user_manual.txt Last modified: 2018/05/18 08:45by f.zoppini