Overview

A work order is a request for some quantity of an item to be produced on or before a due date. A work order may be generated in-house to restock inventory for an item that your company produces and then later uses as a component for another item.

A work order may be comprised from a collection of jobs that produce an item. A job is a list of steps or procedures that is executed to produce an item or a version of an item. Multiple jobs can be performed to produce a single item.

The Work Order and Jobs module is available by accessing the Order Management group in the Wonderware MES Client. When you open the Work Order and Jobs module, a list of all the existing work orders is shown in the tabbed workspace. Expand the work orders to see the job assigned to each of them.

You can also create a work order from a process. Processes are templates for work orders. All entities, step groups, steps, BOM, folders, data log, and certifications linked to the process becomes a part of the new work order.

You can import a work order from a ERP system. After importing a work order from a ERP, you may need to customize the work order for production. However, you can also use the Work Order and Jobs module to create a work order with a process or ERP information.

Job Execution

In the Operations Capability Object, you can specify details of a job that you want to run on an entity such as work order, operation IDs, and commands to specify the action to be performed on the entity when the job is run.

To view Job Executions tab in the object editor, select the Entity Can Run Jobs check box on the General tab. The Job Execution tab appears in the object editor.

Use the Job Execution tab to configure the job execution attributes and trigger the job execution commands.

You can control the execution of a job using job commands configured to perform the following changes to jobs on the entity for this Operations Capability Object instance.

• Start an existing job on the entity
• Pause or end a running job on the entity
• Start a job that is next in the queue for the entity
• Reset the command to start a job that is next in the queue for an entity after an error has occurred

Job Execution Attributes

You must specify the work order, operation, and sequence number to identify the job you want start, pause, or end on an entity.

To configure attributes to run a job, in the Job Execution Attributes tab, do the following:

• In the Work Order, Sequence Number, and Operation boxes, type the respective values or provide references.
• In the Job Position box, type the job position that indicates the position at which a job is currently running on the entity. The default value for this attribute is zero.
• In the Operator box, type the name of the operator who preforms an action on a job, such as starting a job, ending a job, and adding production to a job.

The operator attribute is used to track the user who performs an action on a job. If the operator name is not specified, the default operator name that is configured in the system, User ID for background tasks attribute is used. If the default operator name cannot be retrieved from the system, the user name that is used to connect the database from the middleware server is used as the operator for a request that is initiated from Operations Capability Object.

Job Attributes Available at Runtime

The job attributes that are available at runtime are described in the following table.

Job Execution Commands

You can control the execution of a job using job commands. You can configure the job execution commands to perform the following changes to jobs on the entity for this Operations Capability Object instance.
To trigger the job execution commands, in the Job Execution Commands section, do the following:

• In the Start Job Command box, provide a reference to a trigger command to start the existing job on the entity.
• In the Pause Job Command box, provide a reference to a trigger command to pause the running job on the entity.
• In the End Job Command box, provide a reference to a trigger command to end the running job on the entity.
• In the Start Next Job Command box, provide a reference to start the next ready job in the queue for this entity. This command starts the job to run on the entity if there is a job position available.

Production Counters

In the Operations Capability Object, you can use production counters to track the production of a material for an entity. You can configure up to 20 production counters for an entity in the Production Counters tab.
When you configure multiple production counters for an Operations Capability Object instance, all the job positions contain the same number of production counters at runtime.

For example, if you configure three production counters for the particular Operations Capability Object instance and there are four job positions, each job position will have three production counters, and a total of 12 production counters are created at runtime.

To view the Production Counters tab in the object editor, select the Entity Can Run Jobs and Production Counters checkboxes in the General tab.

Job Position

A job position is a number that indicates a position on an entity to run a job. You must specify job positions if you want to simultaneously run multiple jobs on an entity. When you run a job at the specified job position, the configured production counters are used to log the produced item count.
You can configure production counter attributes for each job position.

General Counter Attributes

The item configured in this section is used as the production item for the job. You can override the production item by configuring a different item and BOM position configured for the job.
A value zero for the BOM position indicates a produced item and a negative value indicates a by- product.

Rolling Counter Attributes

You can configure a rolling counter to count the number of items produced and update the production count when items are being produced at runtime.

A rollover counter is typically used in manufacturing operations where a value for production or consumption is needed using a device like a PLC or other counting device that, either through manual or automatic action, resets its value to zero.

At a certain point the counter would reset to a lower number between update intervals in the Operations Capability Object. The Operations Capability Object understands this resetting and it knows how to calculate the counts required based on the last known value and the current value. The Operations Capability Object also handles the case where you want a counter to reset at the start of a shift in order for the production crew to understand their production for the shift.

Absolute Counter Attributes

You can configure absolute counter attributes to specify the quantity of items consumed by an entity. When the Add Cons Quantity Abs Command is triggered, the specified consumption quantity is logged for the entity.

You can use Absolute Consumption Counters to specify the quantity of consumed items if any errors in the consumption count were automatically recorded or if an additional quantity that is consumed needs to be logged.