Released states

After jobs and production are complete, they require formal release. This is known as setting to a released quality state.

By default, the production order schedule base report does not show details of job or production order quality status. If you need this state to be modeled and tracked, then both can be made visible, individually or collectively. All jobs and orders will default to the unreleased state. However, you can manage the default state in the production order release state master data.

To manage the quality state transition of a job or order, you must first set up a production order release state workflow. You can manage this by creating state mappings between the various release states. State-to-state mapping is built up one at a time, with each transition controlled by selected user roles.

If a quality state workflow has been implemented, then you can change the state of any closed job or order using the quality status task or job quality status task. The quality status of each job is controlled independent of the overall order. Only state-to-state changes that have been mapped and are available to the user role can be selected.

If a job or order is set to a released state, MES will observe settings made on the Prod Order/Jobs tab of the plant settings form.

These are the available options for selection:

Unfulfilled Event Based Checks

Check this option to specify that any attempt to release a job when there are any outstanding event based inspections will be rejected.

Unacknowledged Inspection Alarms

Check this option to specify that any attempt to release a job when there are any inspection alarms still open will be rejected.

Unacknowledged Atypical Events

Check this option to specify that any attempt to release a job when there are any atypical event alarms still open will be rejected. This option applies to workflow enabled orders only.

Checklist Items not done

Check this option to specify that any attempt to release a job that has checklist steps in an indeterminate state will fail. Checklist inspections are used to encode a series of true/false confirmation steps that must be carried out. If such an inspection has begun but has some steps as yet unanswered, the job cannot be released.

Checklist items answered false

Check this option to specify that any attempt to release a job when there are any checklist inspections that have checklist steps with false steps will fail. Use this option if any of the checklist inspections are also to be treated as confirmations that everything is in order.

On Complete?

Check this option to specify that any attempt to set an incomplete order to released results in an error. This is the default setting in MES

Job Auto Approve?

Check this option to automatically release jobs, if they do not violate any of the previous rules.

Order # Auto Approve

Check this option to automatically release orders, if they do not violate any of the previous rules

Order # Blocks Job Start?

Check this option to specify that any attempt to release an order will fail if any of the constituent jobs are not already in the released state. Use this option if an order comprises more than one job