This setup guide is applicable for IFS/OEE 2.0.0 onwards, i.e., the first version released within the IFS Rich Web Client (.Net technology).
Note: When the document refers to older versions it refers to the earlier versions of IFS/OEE (prior to version 2.0.0) that was released within the IFS Windows Client.
Defining basic data also means to define the basic requirements in the system. These are standard data that you need within the production units with which you will be working. Please ensure that all required basic data have been defined before starting to work with the system. This helps to guarantee that you use the correct basic data throughout the system for event reporting, follow-up and analysis of work without having to enter it again.
One of the major distinctions between IFS/OEE 2.0.0 and older versions is that with version 2.0.0 all basic data have been separated from IFS Maintenance. This makes the functions of today's IFS/OEE more independent of the data that is also used by other functions within IFS Maintenance. In addition this also reduces the frequency of selecting incorrect basic data across the maintenance components.
All basic data can be accessed from a single starting point, namely the Setup OEE window (accessed from the IFS/Navigator). Furthermore all basic data relevant to IFS/OEE can be set to Inactive, such basic data will be available for analysis but cannot be used to report new events. It should be noted that while IFS/OEE is independent for the most part, it does make use of other components within IFS Applications such as equipment object, employees, units, work order series etc.
Basic Definitions
Event types need to be defined for two different types of events (stop event types and log event types) that will be reported in IFS/OEE. While these two event types are user defined, they should in turn be connected to a system stop event type and a system log event type respectively (the system event types are predefined).
Production units have to be defined for all parts in the facility to follow-up on. Based on the production and the follow-up that will be performed on it a follow-up type has to be specified for every production unit.
Define Actions
Here you will define the actions that should be available for stop event reporting. These actions are used to describe what actions have been performed by the operating personnel to solve a problem related to the stop.
Products
Define Products and Qualities
Used to define combinations of products and qualities to be produced by a production unit. You can define and connect one or more qualities for a product.
Connect Production Units and Products
A matrix used to connect the products to be produced by each production unit defined.
Loss Causes
Define Loss Cause Groups
Used to define loss cause groups in the system of two types: Internal and External. A loss cause group can have several loss causes connected to it. Internal cause groups are used for causes that are related to objects which belong to the production unit whereas External cause groups are used for causes that are related to objects outside the production unit, but will still cause an APQ loss for the production unit.
Define Loss Causes
Used to define loss causes in the system that will be used later during event reporting. All loss causes defined in the system must be connected to a loss cause group.
Connect Production Units and Loss Causes
A matrix used to connect all loss causes that should be valid for each production unit defined.
Goals
Show Goals for Production Unit
Used to define different types of goals for a certain production unit and also planned revenue loss for products.
For each combination of product and quality to be produced on a production unit, both a maximum production rate and a goal production rate have to be defined. Ones production rate values are defined they are valid until the next valid values are entered.
APQ Goals
Goal values should be defined separately for all figures, i.e., Availability (A), Performance (P), Quality (Q) and APQ. The goal values you define are valid until you enter new values.
Revenue Loss
Enter the expected revenue loss per hour for a product that will be produced on a production unit. The revenue loss indicates the expected cost per produced unit, e.g., a tonne.
Erroneous External Event Messages
Correct Erroneous Event Messages
Used to correct external events that have come to IFS/OEE via IFS/Connect (i.e., other external production systems) but which are logically incorrect.
The OEE folder in the IFS/Navigator is also a link to an overview that is possible to configure to see the status of several production units on a higher level. The child nodes are of two types:
The Setup OEE window which provides an access point for all basic data.
The production units - Depends on the production units defined. If the production unit is defined with the follow -up type APQ the node will in turn contain four more child nodes that are linked to the following windows: APQ Analysis, Stop Length Analysis and Object Structure Stop Analysis.
Prior to IFS/OEE 2.0.0 when an event was reported in IFS/OEE the event was always connected to an object group and in turn all follow-up activities would be carried out on this object group. Since the object group as a concept is often used by many customers for other purposes in IFS Maintenance, a new entity by the name of Production Unit is introduced in IFS/OEE 2.0.0 to be used as a base for event reporting and follow-ups.
The production unit is an essential element within IFS/OEE. You can specify different types of production units based on what needs a follow-up. For instance an entire facility can be defined as one production unit with several sub units connected to it or each sub unit within the facility can be defined as separate production units.
Your decision on what should be defined as a production unit should depend on how the customers are actually running the plant instead of how the maintenance department have setup their object structure. This gives the customer more freedom, for instance you can have a one-to-one connection between the object group and the production unit but it is not mandatory. The object group is still used in it's definition but it is mostly there to provide assistance to the user when it comes to choosing the correct object during, for example stop event reporting.
For each production unit defined in the system a follow-up type must also be specified. At present there are three different follow-up types available in the system:
All production units of follow up type Overview and APQ will automatically be included in the IFS/Navigator.
Event Types
The older versions of IFS/OEE contained three windows for the different types of event reporting: Event (includes Stops, Logs and Speed), Produced and Scrapping event windows. With IFS/OEE 2.0.0 the number of windows were increased to five, one for each event type. This makes things easier and clearer for the operators where they will not be forced to enter more information than what is necessary for an event type. This also makes it easier to perform different types of follow-ups.
Stop Event
Stop events should be used when production have been halted on a production unit. You can also take care of stops planned for the future (that is yet to take place) and also define stops that should not get in the way of any calculations performed on the production unit. All stop event types must be connected to one of the following predefined system stop event types:
All system stop event types have an impact on the APQ and/or the TEEP (Total Effective Equipment Productivity) calculations except for No Production Loss.
Log Event
Log events can be used for different kind of messages with information that should be stored and spread to other colleagues. All log events must be connected to one of the following predefined system log event types:
Production Rate Event
Used to report a change in production rate (speed), as well as a change of product and/or quality to be produced.
Production Event.
Similar to the type in the older versions of IFS/OEE. Used to report how much have been produced during a certain time period.
Scrapping Event.
Similar to the type in the older versions of IFS/OEE. Used to report how much have been scrapped. A scrapping has to be connected to a production unit in order to get the right follow-up values.
You receive events into IFS/OEE as external events from other production systems via IFS/Connect. If an external event is logically incorrect it will pass as OK in IFS/Connect, but then has to be corrected in the Correct Erroneous Event Messages window. However if an external event has an incorrect file format and cannot be interpreted as an event by IFS/Connect it has to be corrected directly in the failure handling within IFS/Connect.
Note: Error handling within IFS/OEE is only available for Super Users.
In IFS/OEE there are two different production rates to be defined,
Goal Production Rate - The ideal speed against which production should run in practice, i.e., an optimal speed from an economic life perspective.
Both these production rates are defined per quality for a product to be produced at a production unit.