# SKUs ## Overview A SKU (Stock Keeping Unit) is a unique identifier assigned to a specific product to allow Busroot to track production. When a schedule is created a SKU must be entered so the system knows which product is being produced. ## SKU Settings ### Performance Mode This defines how Performance data is measured. Choose the metric that matches the SKU. Select how you want the SKU to be measured in cycle time, units/minute or units/hour. #### Parts per Cycle (PPC) For SKUs that are produced in multiples. The 'Production Complete' signal or input on table tablet will be multiplied by this value to give the total unit count. #### Value Set the value in £ of each unit or batch. #### Instructions If you have an internal link to a process document you can include it here for the operator. #### Downtime Detection Cycle Time Multiplier When using 'Production Cycle' downtime detection mode, a duration based on the SKU cycle time is used to determine when a station should be considered stopped. By default, this value is 150% of the cycle time. So for an SKU with a cycle time of 2 minutes, Busroot would consider the station stopped if no production has been observed after 3 minute. Changing this multiplier to 2 (200%) would mean that downtime is not flagged until 4 minutes after the last observed production. #### Minimum Cycle Time Set a minimum cycle-time for the SKU. If more than one signal is received in this period, Busroot will only count one unit. This allows filtering of signals during setup process for example. #### Allow Use in Ad hoc Production Schedules Select whether the SKU will be available when creating Ad Hoc Schedules on the Operator Tablet. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.output.industries/configuration/skus.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.