Base Configuration Check

Why did you enable OEE on Machine 1, Spray Line 1, and Manual Pack 1, but not on CoreForge, Philadelphia, or the areas?

OEE is enabled on the physical equipment where operational data such as counts and states can be collected and monitored, such as a production line, vessel, or process cell. The enterprise, site, and area assets organize the hierarchy; they don't run production themselves. Enabling OEE on an asset also creates its assetOEE tag instance and lets you set its process type and OEE targets. See Assets.

Why does the Philadelphia site need a time zone?

Kanoa associates time zone information with assets through the site, so at a minimum a site must exist somewhere in the hierarchy. Because the gateway and database run in UTC, the site's time zone (Eastern Standard Time for Philadelphia) is what lets production events, shifts, and schedules be interpreted in local time. See Assets.

Why organize items into item classes such as CoreForge\WIP\Machined and CoreForge\FG?

Item classes work like a folder structure for categorizing items. They make items easier to find and manage, and with Kanoa Quality they let you set specifications for an entire item class instead of each individual item. If an item has no color, its item class color is shown. See Materials.

What is the difference between the standard rate and the scheduled rate?

The standard rate is the theoretical speed at which the asset should process material, in infeed units; it drives the OEE Performance calculation. The scheduled rate is the rate you actually expect based on historical OEE data, and it's used to estimate how long a production order will take when it's scheduled. For example, Spray Line 1 has a standard rate of 50 units/min and a scheduled rate of 45 units/min. See Configure Production Rates.

Manual Pack 1 consumes 100 units to produce 1 box. What package count do you configure, and what must you create first?

A package count of 100 (the number of infeed units that equate to one outfeed unit), with infeed units units and outfeed units boxes. You must first create the boxes unit from the units menu. See Configure Production Rates.

What must exist before you can enter a production rate for an item on an asset?

An item-asset link. You create links in the Item Asset Link Editor on the Production Rates tab; each link creates a blank rate entry that you then edit. See Configure Production Rates.

How are availability, performance, and quality calculated, and how do they combine into OEE?

OEE = Availability × Performance × Quality.

• Availability = runtime / (runtime + unplanned downtime), based on the state type of each state event. Planned downtime is excluded.
• Performance = infeed count / (rate × runtime), using the standard rate from the item-asset link.
• Quality = outfeed count / infeed count.

See OEE.

Why is the Production mode type special?

Only count and state events that occur while the asset is in a mode of type Production are included in production analysis and OEE. Events outside production modes are still recorded but don't affect production metrics. See Modes.

What creates an assetOEE UDT instance, and where does it live?

Marking an asset as OEE-enabled. Kanoa creates an instance of the assetOEE UDT for that asset in the Kanoa tag provider that you created when setting up the gateway. See Connect To Your Tags.

Which assetOEE UDT folder is most important for integration, and which should you usually leave alone?

The Inputs folder: it's where external values such as counts, state, mode, product code, and work order enter the UDT and create Kanoa events. The Configuration and OEE Thresholds folders are mainly for debugging and reference and generally shouldn't be modified. See Connect To Your Tags.

Why does the training use an Asset Inputs UDT instead of wiring logic directly into the assetOEE UDT?

It separates calculation from commitment: the Asset Inputs UDT is a staging area where data is calculated and prepared, while the assetOEE UDT Inputs commit that data into Kanoa. You link the two by setting the assetOEE UDT's MQTT path parameter to the Asset Inputs tag path. See Connect To Your Tags.

An asset only has an outfeed counter available. Can Kanoa still track production and calculate OEE quality?

Kanoa can track production from a single count, and it calculates the missing counts from the ones it has. However, OEE quality needs at least two counts (infeed and outfeed, outfeed and waste, or infeed and waste). With only one count, quality defaults to 100%. See OEE.

What is the difference between a mode and a state?

A mode is the intended operation, what the asset is supposed to be doing, such as Production or Idle. A state is equipment feedback, what the asset is actually doing, such as Running or Faulted. See Configure Modes.

The Audit mode has Can Schedule turned on and Can Select turned off, and it's linked only to Spray Line 1. What does that allow?

Audit can be scheduled on Spray Line 1, but an operator can't set the line to Audit from the asset operation screen. Because Audit isn't linked to Machine 1 or Manual Pack 1, it isn't available on those assets at all. See Configure Modes.

You created the Spray Nozzle Clog state in the State Editor. Why do you also link it to Spray Line 1, and what is the state code on that link used for?

A state is only available on the assets it's linked to. Each asset-state link is assigned a numeric state code; when the asset's state comes from a PLC tag, that code must match the integer value the PLC sends for that condition. See States.

An asset is in Production mode and its state is Faulted. How is that time treated?

As downtime during planned production. The mode says what the asset was supposed to be doing; the state says what it actually did. Faulted is an Unplanned Downtime state, so that time reduces availability. See Configure States.

What do item states add to a waste count, and how do you keep operators from seeing irrelevant reasons?

A waste count records how much waste occurred; an item state records why (for example, Damaged Parts). Linking item states only to the assets or items where they apply, on the Item States Link tab, limits the reasons operators see. See Using Item States.

An operator entered the wrong outfeed count for yesterday's run on Machine 1. Where can you correct it?

In Ops → Operations → Run Review. Select Machine 1 and the production run, open it with the eye icon, and edit the count on the Counts tab. Run Review also lets you edit mode events and downtime events. See Run Review.

Why set up asset groups now, when there is only one asset of each type?

Asset groups let you report on similar assets together even when they aren't in the same part of the hierarchy, for example all machines across different areas or sites. They become more valuable as you scale: later in the course, the asset rollout script finds its template asset (Machine 1) through the Machines asset group and copies it to create new machines. See Configure Assets.