Production run-time operations

When you deploy the UCO OnScan, it will begin using the defined production attributes. At run time you can:

• Monitor for errors using the ProdAttrs.ErrorCode and ProdAttrs.ErrorMessage attributes.

• Change a production attribute input source or UseInputSource attribute to change how or where it will get its value.

• Set a production attribute value directly if its UseInputSource attribute is False.

When the product start job attribute is triggered (ProdAttrs.StartJobCmd=True), the production attribute values will be used to create a new work order.

Configured production attribute values that do not exist in the MES database, when triggered, will be created based on the properties in the table below.

The meanings of the table columns are:

Provide default value if blank

Indicates whether a default value will be provided if the production attribute value is left blank.

Default value

Indicates the default value provided for production attributes when no value is configured.

Create if doesn’t exist

Indicates whether a new MES type will be created with the value specified if it doesn’t already exist. For example, if the Item production attribute is set to "SuperWidget" and "SuperWidget" does not currently exist, it will be created when ProdAttrs.StartJobCmd is set True.

Create new data entry job if changed

Indicates whether a new job will be created if the specified production attribute’s value is changed and ProdAttrs.StartJobCmd is set True.

For the Operator attribute value, labor usage data will only be attributed to a valid user. If the user is not a valid user, the default background user will be used to execute the job and no labor will be captured. If the entity is configured to capture labor and a user is not provided for the Operator attribute, no labor records will be added.

None of the production attributes of type STRING have default values during configuration. The values listed are the defaults that will be supplied through system parameters when ProdAttrs.StartJob Cmd is set True if the production attributes are blank. For information about configuring default values, see MES Client User Guide or online help.

The triggered work order creation will occur once the product start job command attribute is set (ProdAttrs.StartJobCmd=True).

• If triggered and no production attribute values have changed since the last trigger, no new work order will be created.

• If triggered and a job containing a work order that requires a minimum quantity is running:

  • If the required quantity has been met, a new work order will be created.

  • If the required quantity has not been met, a new work order will not be created, and an error will be returned in the ProdAttrs.ErrorCode and ProdAttrs.ErrorMessage attributes.

• If a UCO creates a new job on an entity that is already running another UCO job, the running job will be completed and its operator will be logged off the entity. The operator associated with the new job will then be logged on to the entity and the new job is started if they are a valid user.

• If another user logs into the entity on which a UCO job is running through operator, that user will not receive labor for the job.

When the production end job attribute is triggered (ProdAttrs.EndJobCmd=True), an unconditional request will be sent to the middleware to end all jobs on the related entity.

Passing a new value to the Item attribute and supplying a WorkOrder value that already exists does not alter the item associated with the existing work order. A new job will be created using the new item and the existing work order ID, but the work order record itself will still be associated with the original item.

If an error is returned to a call to start or end a job, then the Reset command will need to be called to clear the error message and reset the production attributes primitive to the Ready state.