Run FactorySync Capacity Analysis and Review Projected Work-Order Dates

Run the FactorySync finite-capacity analysis in NetSuite and compare current and projected work-order end dates before changing a schedule.

The quick answer

In a configured FactorySync workspace, open Capacity Planning, check the Finite Sync overview, then choose Optimize → Run Analysis. Compare each work order’s Current End and Projected End dates. The result is a set of recommendations; this walkthrough does not apply or save them.

FactorySync is a vendor-specific extension inside NetSuite. Its Capacity Planning and Optimize controls are not standard NetSuite Manufacturing Scheduler controls. The screenshots use fictional person and company names, and the example dates and work orders are training data. Your available controls and projected dates depend on the installed extension, role, capacity data, and account settings.

Before you start

You need access to FactorySync’s Capacity Planning workspace and current work-center and work-order data. Pick a date range that covers the orders you need to review. The example uses May 28 through June 5, 2026. Keep material availability, dependencies, and customer commitments handy when you evaluate any proposed date change.

01. Open Capacity Planning

Open FactorySync and select Capacity Planning. Set your date range and filters, then review available hours, scheduled hours, utilization, and the work-center heatmap. In the example, Finite Sync is on, and the gear beside it opens the settings used for the next step.

FactorySync vendor demonstration: confirm Finite Sync and the planning range before opening settings.

02. Review the overview

Select the gear beside Finite Sync. In Finite Capacity Settings, read the Overview counts before optimizing. This example shows zero over-capacity work centers, zero overloaded operations, one past-due work order, and four work centers within capacity. Those counts give context for the date recommendations, but they do not identify which orders will move.

The overview shows one past-due work order, even though no work center is over capacity.

03. Run the analysis

Choose Optimize, then select Run Analysis. Wait for the per-order result table. The walkthrough shows the analysis action and its result; it does not show a schedule being changed at this point.

Run Analysis opens a comparison of current and projected end dates.

04. Compare projected dates

Read Current End, Projected End, and Change for each work order. The example analyzes five orders. WO-2101 is marked past due and would move from May 28 to June 5; WO-2102 through WO-2104 could finish earlier; WO-2105 has no proposed change. Check the proposed dates against materials, dependencies, resource availability, and promised dates in your own account. The walkthrough stops at this table and does not select Apply Selected or verify a saved work-order change.

One order would move later, three could finish earlier, and one would stay unchanged.

Check the result

  1. The analysis table lists the work orders in the selected capacity view.
  2. Each row shows a current end date, a projected end date, and a change description.
  3. No work-order reschedule is claimed until a separate apply-and-save action and its result are verified.

Common questions

Is FactorySync Capacity Planning standard NetSuite scheduling?

No. These screens belong to an installed FactorySync extension. Standard NetSuite manufacturing pages may have different controls and behavior.

Does Run Analysis change the work-order dates?

The demonstrated action shows projected dates in an analysis table. It does not show Apply Selected, a saved schedule, or a changed work-order record.

Why can a past-due order move later when capacity is available?

The example shows that combination, but the walkthrough does not expose FactorySync’s calculation. Review material availability, dependencies, work-center constraints, and commitments before acting on a proposal.

Will another account get the same projected dates?

No fixed result is established here. The five rows and dates are example data; your output depends on the extension configuration and current work orders and resources.

The sequence and vendor interface follow a FactorySync capacity-analysis walkthrough. The inspected account did not expose the FactorySync module, so the vendor-specific screens could not be checked against that account.