Skip to content
MxAPS app iconMxAPSScheduling engine

Forward Finite Capacity Scheduling for Microsoft Dynamics 365 Business Central

Business Central's standard planning schedules backward from the due date at infinite capacity, so on a busy work center the planned load can exceed the hours the machines actually have. MxAPS, Insight Works' finite capacity production scheduling app for Business Central, schedules production forward from a chosen start date and time against real work center and machine center capacity.

Each run reports how many order lines will be late, early, or on time, and nothing changes in Business Central until you commit the result.

How Forward finite capacity scheduling works in MxAPS

  1. Production orders exist in Business Central, created by planning or by hand.
  2. The planner opens a scheduling configuration and sets the start date and time, the duration, and the routing line filter.
  3. MxAPS sends the work to the scheduling engine, which sequences operations by rank against machine capacity and any constraints.
  4. A numbered schedule result returns with late, early, and on-time counts and total setup and run time.
  5. The planner adjusts and reschedules if needed, then commits the dates to production order routing lines.
Video thumbnail: Forward and backward scheduling with MxAPS
Forward and backward scheduling with MxAPS For production planners who want start and finish dates based on the resources available today. Transcript and details →

Key capabilities

Forward from now

A planner sets a start date and time and a schedule duration, and MxAPS places operations forward from that point, so no operation is scheduled to start in the past.

Real capacity

Operations are placed against the capacity of each work center and machine center, so a machine center is never booked for more hours than it has.

Your rules decide the order

Scheduling rules rank operations, by criteria such as priority and due date, and the engine uses that rank to choose what runs next.

A filter on what to schedule

Each run uses a filter on production order routing lines, so a planner can schedule the whole plant or a defined set of orders.

Late work is visible first

Every run produces a schedule result with late, early, and on-time counts, so the planner sees which orders are at risk before the shop floor does.

A constraint-based engine

Scheduling runs on a constraint-based engine hosted as a remote service in Azure. Business Central connects to it, and identifying data is sent as anonymous identifiers in normal operation.

Details that matter on the floor

A realistic horizon

A detailed schedule of about 30 days is a sensible horizon. Shop floor reality moves the plan within a day or two, so rerunning a shorter horizon serves the floor better than one long run.

Your routings set the ceiling

The schedule is only as accurate as the routings, work centers, machine centers, and setup and run times behind it.

Missing material holds work back

When components are not available, operations that need them are pushed out rather than scheduled as if the material were there.

Who uses Forward finite capacity scheduling

Production planners and schedulers

Run the schedule, read the late and early counts, adjust, and commit.

Plant managers

Judge whether the plant can absorb the current order book, and test changes such as an extra shift by rerunning.

Operations managers

Cut late orders and work in process caused by the floor choosing its own sequence.

Supply chain managers

See where material shortages will push operations out.

Questions about Forward finite capacity scheduling

What is finite capacity scheduling in Business Central?

Finite capacity scheduling places each operation only where a machine has capacity for it. MxAPS adds it to Business Central, scheduling production forward from a start date against real work center and machine center capacity.

How is this different from Business Central's standard scheduling?

Business Central's standard planning schedules backward from the due date without holding machines to their available hours. MxAPS extends it by sequencing operations forward against real capacity and reporting which orders will be late.

Does running a schedule change my production orders?

No. Each run creates a schedule result. Dates are written to production order routing lines only when you commit a result.

Does MxAPS create production orders?

No. MxAPS schedules production orders that already exist. Planning and order creation happen upstream, in Business Central planning or in an app such as Enhanced Planning Worksheet.

Where does the scheduling engine run?

The engine runs as a remote service hosted in Azure and connects to Business Central. Identifying data is sent as anonymous identifiers in normal operation.

How is MxAPS licensed?

Licensing depends on your setup. See the licensing FAQ or contact your Microsoft Partner.

MxAPS app icon

Part of MxAPS

Automated finite capacity production scheduling, built into Business Central.

Have a question about Forward finite capacity scheduling?

Send us a note and the MxAPS team will reply by email. Ready to plan a rollout? Contact your Microsoft Partner.

Ask a product question

Product Questions