Acumatica Work Center Screen — A Deep Dive

The Work Center screen (AM207000) defines the physical or logical production resource that route operations get assigned to — a machine, a production line, or a labor group, depending on how granular a given plant wants its capacity model. The DAC is AMWorkCenter, and it's the anchor point for capacity, cost rates, and (if Scheduling is licensed) shift calendars.

Capacity type: finite vs. infinite

Each work center is configured with a capacity type — infinite capacity assumes the resource can always absorb more work (fine for a manual assembly bench with flexible staffing, less fine for a single CNC machine), while finite capacity feeds the scheduling engine's constraint logic and will actually push operations to later time slots when the work center is already loaded. Setting every work center to infinite capacity "to keep it simple" quietly disables the part of Scheduling that's supposed to catch overbooked machines, so it's worth confirming this setting matches reality rather than accepting whatever default came through at implementation.

Labor and machine rates, and where they feed cost

A work center carries labor and machine rate defaults (overridable per operation on the route) that flow into production order cost rollup — this is one of the two places (the other being the route operation itself) where a manufacturing cost calculation can go wrong if setup was rushed. A work center left at a zero or placeholder rate will understate labor cost on every production order that routes through it, and because the error is silent (no validation blocks a zero rate by default), it tends to surface as a finance question months later rather than an error at data-entry time.

Shift and calendar assignment

When Scheduling is active, each work center references a shift calendar defining working hours, days off, and capacity per shift. This is what lets the scheduling engine calculate realistic start/finish times for operations instead of assuming 24/7 availability. A work center with no calendar assigned, or one pointing at a calendar that hasn't been updated for the current year's holidays, is a common cause of production schedules that look fine on paper but slip in practice — worth checking early when a client complains that "the scheduled dates never match what happens on the floor."

Common customization points

A DAC extension adding a custom field to AMWorkCenter — an external asset tag, a maintenance schedule reference, a department code for cross-charging — is the most common request, surfaced through the Customization Project Editor on a new tab. Slightly more involved is a graph extension on the Work Center Maintenance graph adding a RowPersisting validation that blocks saving a work center with a zero labor or machine rate when its capacity type is finite, closing the silent-zero-rate gap mentioned above before it reaches a live production order.

A gotcha with Work Center Groups and reassignment

Work centers can be organized into Work Center Groups for scheduling and reporting purposes, and reassigning a work center to a different group doesn't retroactively update historical production order records that already reference it under the old grouping — reports that filter or roll up by group can therefore show inconsistent historical vs. current-period totals for the same physical resource, purely because of when the group reassignment happened relative to when each order ran.

Wrapping up

Work Center is a small setup screen that quietly controls two things people usually attribute to other parts of the system: whether cost rollup numbers are trustworthy, and whether a production schedule reflects real shop-floor availability. Both failure modes are silent by default, so a periodic audit of rates, capacity type, and calendar assignment is worth more than any customization you'd build on top of the screen.