Overview

You can configure an entity to store items through the Operations Capability Object. Whenever you execute a job, items are produced and consumed in the process. You can specify the location to store items that are produced or consumed while executing a job.

To enable storage capability, select the Entity Can Store Items check box in the General tab. This check box will also display the Storage Execution tab.

You can configure the storage execution options for an entity that is used to store multiple items and lots. You can also configure the initial status of an entity, which indicates whether the entity is available to store items.

Specifying Default Storage Entities

A storage entity is used to store items that are produced or consumed while executing a job. You can specify the default storage entities for good production, rejected production, and consumed items when jobs are executed.

Entities must exist with the option for storage before these fields can be set. Generally this means that the Entity Model Builder must have been run once to populate the MES database with the entities that have the storage option set. These are default settings stored with the entity and can be overridden at runtime during execution of the job.

When you run the Entity Model Builder, entities for which the Entity Can Store Items option is enabled in the General tab, the Entity Model Builder creates a new default storage entity or updates the existing storage entity settings. You can configure the following default storage entities in this tab:

Default Storage Entity for Good Production

When a production request is made with a production quality of “good,” and if the production request does not contain a storage location identifying where the production item to be stored, then the default storage location configured for the entity is used to store the production item. This default storage location is used in the following scenarios:

• A storage location is not specified while adding good production recorded by production counters in the Operations Capability Object or an operator.
• A storage location is not configured to log good production for a job on an entity.

Default Storage Entity for Reject Production

When a production request is made with a production quality of “bad,” and if the production request does not contain a storage location identifying where the production item to be stored, then the default storage location configured for the entity is used to store the production item.

This default storage location is used in the following scenarios:

• A storage location is not specified while adding rejected production recorded by production counters in the Operations Capability Object or an operator.
• A storage location is not configured to log rejected production for a job on an entity.

Default Storage Entity to Consume Items

When a consumption request is made without identifying storage location from where the items can be consumed, then the default storage location configured for the entity is used to consume the items from this location.

This default storage location is used in the following scenarios:

• A storage location to consume items is not specified while adding consumption recorded by consumption counters in the Operations Capability Object or an operator.
• A storage location is not configured to log consumption for a job on an entity.