Item specifications define the details of items you manufacture and repair. You use item specs on your manufacturing floor to complete assembly and repair work orders. You also use item specs to do assembly cost rollups for items you manufacture and repair.
Item specifications contain the following:
Item specifications describe how to build or repair items you manufacture.
When you're creating item records for an item you manufacture or repair, you create the item specification after you create the item.
Work orders use item specifications as the basis for manufacturing and repairing items.
MRP looks at item specifications to determine what components to order.
Before you create item specifications, you must have the following set up:
To create a new item specification, follow these steps:
To learn more about these fields and checkboxes, see Item Specification Field Descriptions.
The item specification record is created.
Kenandy creates an Expanded BOM for the item specification that contains only the item to be manufactured using this item specification. After you add components to the item specification, the Expanded BOM expands to include those components.
Go on to add components and routings to this item specification.
Routings define specific tasks or chunks of work you do to manufacture an item. When you release a work order for an item specification that has routings, Kenandy converts each routing to an operation. You can then record completion of each operation separately.
Routings are optional.
We recommend using routings if your business needs to track every step of your manufacturing process, and every movement of your inventory. Use routings to track standard hours per task, to issue components for each task in your manufacturing process, and to record completion of each task.
To add routings to an item specification, follow these steps:
Tip: To make it easy to add unexpected operations to work orders later, use a numbering system that leaves unused numbers between each routing. For example:
The routings are saved to the item specification.
Add components to the item specification and if needed, tie them to the routings you created.
To enter the component items you expect to use to manufacture your assembly item or to repair your item.
The components are saved in the item specification.
Kenandy adds the components to the Expanded BOM for the item specification. If you added subassembly components that you manufacture, Kenandy automatically creates multiple levels in the Expanded BOM.
If you manufacture or repair many items that use the same routings or components, you can save time creating item specifications by creating item specification templates. The template stores the routings and components you add to it, so you can choose them from a list of templates when you're creating Assembly and Repair item specifications.
Note: You can't use item specification templates to create lots of item specifications with the same detail information (for example, revision number, model number, facility, and so on) . If that's what you need to do, you can clone an existing assembly or repair item specification. To learn more, see Clone an Item Specification.
To create an item specification template, follow these steps:
To learn more about these fields and checkboxes, see Item Specification Field Descriptions.
The item specification template is created.
Add routings and components to this template.
If you need to create an item specification that uses most of the same information as an existing item specification, you can save time by cloning the existing item specification.
To clone an item specification, follow these steps:
The new item specification is created.
Kenandy creates an Expanded BOM for the item specification that contains only the item to be manufactured using this item specification. After you add components to the item specification, the Expanded BOM expands to include those components.
Add routings and components to the new item specification.
Important: You cannot delete an item specification if it's tied to any open work orders.
To delete an item specification, follow these steps:
The item specification is deleted.
The following table lists the fields that Kenandy provides. Your system administrator selects the fields that are displayed on your user interface.
| Field | Description |
|---|---|
| Company | The company that makes this item. |
| Copy Phantom Routings |
Select this option if you want routings in your phantom subassemblies to copy to work orders automatically. When checked, Items of type Phantom with routings (that become operations in a work order) not only transfer their item specifications (and corresponding items) to any parent item that includes them, but they also carry over their routings to the work order so that the parent item may include both the phantom items and operations defined by the phantom item. |
| Costing | Select Costing only if you want Kenandy to take this item specification into account in assembly cost rollups, but you do not want MRP to look at this item specification. |
| Default Work Order Packaging UOM |
The default packaging UOM used for work orders to manufacture this item. For example, the Specification UOM = EA (eaches). But when you complete work orders for this item, you package it in CS (cases). So the Default Work Order Packaging UOM = CS. |
| Facility |
The facility that makes this item. Enter a facility if you make this item in only one of your facilities. |
| Item |
The item described by this item specification. Choose an item from a list of existing item records in Kenandy. |
| Item Specification |
The name of this item specification. This is always the same as the Item Name. Kenandy changes this name automatically if you try to enter a different name. |
| Model |
The model name or number of the item described by this item specification. If you use CPQ, Kenandy automatically populates this field. [See a CPQ topic for more information] |
| Notes | Informative notes about this item specification that will help other Kenandy users or your manufacturing floor understand the item specification better. |
| Production | Select if you want to use this item specification as part of your manufacturing process (in work orders). |
| Revision |
The revision number for the version of the item described by this item specification. One item can have many item specifications, differentiated by Revision. |
| Specification UOM |
The UOM for this item specification. For example, if you're creating an item specification for a case of 12 finished goods, the Quantity per Assembly = 12 and the Specification UOM = CS (case). |
| Start Date |
The date you plan to start using this item specification for manufacturing or costing. If you plan to enter records into Kenandy from previous manufacturing runs, make sure the start date on the item specification comes before the dates of work orders or other records that use the item specification. |
| Type |
Choose one of the following:
|
| Field | Description |
|---|---|
| Component Item | The name of the component item. |
| Description | A brief description of this component item. |
| Item Specification | The item specification used to manufacture this component item. |
| Level |
A component's level in the BOM hierarchy. Here's how that works:
You can't change levels. |
| Quantity per Assembly |
The quantity of this component required to manufacture one specification UOM of this item. For example, the specification UOM for an item specification for fishing rods is EA (eaches). A fishing rod requires 10 screws. The Quantity per Assembly of screws = 10. If the component item is part of a manufactured or phantom subassembly item, the Quantity per Assembly tells you how many of the component are required to manufacture the subassembly. |
| Quantity per Top Assembly | The number of this component item that you need to build one of the assembly items described in this item specification. [Liz to change this based on Specification UOM, probably use an example] |
| Revision | The revision of this component item. |
| Source | Where this component item comes from. |
| Yield |
The amount of this component you expect to be used (not scrapped) when manufacturing or repairing this item. The Yield value is shown as a percentage. If the expanded BOM expects that a work order will use 100% of a component (no scrap expected), Yield = 100.00. When a Yield value is less than 100%, a work order using this item specification takes this into account and issues the number of components needed to complete the full work order. |
| Field | Description |
|---|---|
| Backflush Resource |
Select this option if the resource you entered is a backflush resource. If you want the standard hours for this routing to automatically populate when you record an operation in a work order, check this box. |
| Description | A description of this routing that helps other Kenandy users understand how the routing works or why it is used. |
| Fixed Hours |
Select if the number of hours it takes to complete this routing is the same regardless of the quantity of items being manufactured. For example, if it takes the same number of hours to complete this routing for 5 items as it does to complete this routing for 500 items, select Fixed Hours. |
| Notes | Enter any additional information about this routing. |
| Resource Quantity |
Required. The number of resources, either person or machine, required to complete this routing. |
| Resource Sequence |
Defines where in the manufacturing process this routing happens. To make it easy to add unexpected operations to work orders later, use a numbering system that leaves unused numbers between each routing. For example:
|
| Routing |
A unique Kenandy-generated number that identifies each routing. You can't change the routing number. |
| Standard Hours |
The number of hours usually required to complete this routing. |
| Work Center |
Required. The work center where this routing is performed. |
| Work Center Resource |
Required. The work center resource, either person or machine, required to complete this routing. |
| Field | Description |
|---|---|
| Allocate on Receipt |
You must also check Allocation Required if you select this option. If you select this option, when you run MRP it creates a PO for the components. When you receive this PO, it automatically allocates the components to the work order. |
| Allocation Required |
Select if you want to require this component be allocated to work orders. |
| Component Item |
Required. The component item you choose from a list of available items in Kenandy. |
| Component Sequence |
Optional. A number that defines where in the manufacturing process this component gets used. |
| Component Stocking UOM | This component's stocking UOM, used to cost this component. |
| Description | A brief description of this component item that helps other Kenandy users and your manufacturing floor understand what the component is and how it's used. |
| Quantity per Assembly | The number of this component required to manufacture one of the items defined by this item specification. [need to update based on Spec UOM info from other places in this doc] |
| Reference | Notes about this component that will help other Kenandy users and your shop floor understand more about this component. |
| Routing |
The routing that uses this component. To tie this component to a routing, enter the routing number in this field. |
| Supplier |
The supplier you use for outside processing of this assembly item. This is populated only when the Source of the assembly item is Outside Processing. |
| Type |
Choose one of the following:
|
| Yield |
The amount of this component you expect to be used (not scrapped) when manufacturing or repairing this item. The Yield value is shown as a percentage. When a Yield value is less than 100%, a work order using this item specification takes this into account and issues the number of components needed to complete the full work order. |
_________________________________
To search the KnowledgeBase and documentation, ask a question, or log a case, please visit the Kenandy Community. To access our online training, visit the Kenandy Learning Center.
Version: Spring 2017