Work centers

Use this function to define a production resource that is to be used for an operation in a routing.

A work center can be defined as a machine used in your manufacturing processes, a labor resource, or an operation in a routing that is subcontracted to an external supplier.

Your work center definitions are central to your production planning:

  • Work centers are used for planning load times (preparation time, waiting time, and post run time), and tracking production time.
  • Work centers provide capacity data, efficiency data, and shrinkage percentages.
  • Should a breakdown or a bottleneck occur, replacement, or alternative work centers can be nominated, and prioritized.
  • Work center costings can be managed using a link to a costing dimension.
  • Multiple work centers can be linked with the same cost type, to then link with Project management. In a labor context, a cost type defines the types of labor resource that can affect a project, such as operator costs.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Work center function contains a home section and one section per feature of the requirement:

  • Home section. The home section defines the characteristics of the work center, such as its operational use.
  • Management. This is the main section for this function. You use this section to define control parameters, such as the workers shift pattern.
  • Variation. You use this section to control capacity.
  • Replacement. You use this section to nominate and prioritize replacement, or alternative work centers.
  • Optimization matrix. You use this section to assign a setup time matrix to this work center which can be used to optimize production.
  • Load. This section displays load for this work center in a graphical format.

Header

The home section defines the characteristics of the work center. These include the manufacturing site at which the work center is located, the operational use of the work center, and the group of work centers to which the work center is associated.

Tab Management

You use this section to define control parameters for this work center. These include the workers shift pattern, the number of operators, and for work centers of type Machine, whether this work center must continue running whilst the operator is on a break.

Tab Variation

You use this section to control capacity for this work center.

Work center capacity comprises multiple elements:

  • A general weekly structure, which defines the available periods for the work center. This is defined in the Management section.
  • Periods of non-availability, such as when the manufacturing site is closed, or an operator is on annual leave.
  • The number of work center resources generally available.

You use this section to define exceptions to the availability, or capacity of this work center. For example, to define a specific date this work center is not available because of maintenance. Alternatively, a labor work center might have a variation because a mechanic is on leave, or only 2 workers are available instead of the normal 3.

You can attach a reason for a variation. Reason codes are defined in miscellaneous table 801 - Capacity variation reasons.

Tab Replacement

You use this section to nominate and prioritize replacement, or alternative work centers. Alternative work centers can be used to carry out operations in a routing should this work center breakdown or a bottleneck occur, for example.

Tab Optimization matrix

You use this section to assign an optimization matrix to this work center if you are using the generic Finite scheduleradvanced interface. The Finite scheduler interface provides an integration connector to connect to Sage X3 Web Scheduling or to any web scheduling solution developed by an ISV (independent software vendor) for either cloud or on-premises solutions. The Finite scheduler advance interface is active if the GFSA - Finite scheduler advanced activity code is active.

An optimization matrix links products and attributes defined in setup time matrices to define reduced setup times for products with like products to optimize production. This is particularly useful if your organization produces multiple products using common resources (work centers and machines) and wants to organize the sequence of production so that the setup time between products and operations is minimized. For example, it is more cost effective to spray paint all white colored products, before cleaning the spray system to paint all blue colored products, before then applying a varnish to the paint.

Reminder: An optimization matrix can provide cumulative setup times for each related setup time matrix defined, or provide the setup time matrix with the longest setup time from the list of related matrices.

Attributes and the setup time matrix are only used with your web scheduling solution. They are not used with work orders or Production Scheduler.

Sage X3 Web Scheduling cannot optimize production times when multiple resources are assigned to a work center. This is a limitation of Sage X3 Web Scheduling. As a result the No. of resources field (WSTNBR) in the Management section must be set to 1.

Tab Load

This section displays load for this work center in a graphical format. Data displays reflects the calculated firm, and planned load, the load from material requirements planning, and the load from the master production schedule.

Reports

By default, the following reports are associated with this function :

  WORKSTATIO : Work center listing

This can be changed using a different setup.

Specific actions

Reschedule

Click the Reschedule action to recalculate the workload for all work orders that use this work center. This will rebuild (resynchronize) the load buckets according to the period breakdown (days, weeks and months) defined in the scheduling parameters. All work orders with a start date later than today are processed, whatever their status (suggested, planned or firm).

Limitations

You cannot delete a work center if it has been an active operation in a routing.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation