Planning

Planning combines three views of the same scoped production schedule: Scheduler, Kanban, and List. The Scheduler is the time-based workspace for assigning and sequencing splits on work centres. Open it in a workspace where Planning is enabled and your current access permits it.

Access and scope

The available schedule is always limited to the selected tenant, site, and system environment.

• planning.read allows a user to read planning data.
• planning.manage is required to plan, move, resize, unplan, commit, or change shared Scheduler configuration.

If the Scheduler is missing, first confirm the active site and environment and then ask an access administrator to check planning.read. Changing the browser URL or request headers does not grant access to another scope.

Open a planning surface

Use the compact surface button at the left of the planning toolbar to switch between Scheduler, Kanban, and List. The last available surface and Scheduler layout are remembered for the current planning scope.

Find production work

Select Find work in the Scheduler toolbar to search active production work across all dates and work centres in the current site and environment. Enter at least two characters from an order number, product, operation, or work centre. Planned and unplanned results appear together. Select Show more results to continue through a longer result list.

Select a scheduled result to open its date and work centre on the timeline. When the work centre is outside your saved view, Scheduler opens a focused view; use Back to previous view to return. A waiting operation already loaded in the current view is revealed in the unplanned table. Other unassigned results open their order details. You can also open order details directly from any search result. Navigation preserves your uncommitted draft.

Use Search work in this view above the split tables to filter planned work and search waiting work throughout the saved view. Enter at least two characters to search waiting work beyond the loaded pages. Planned and Unplanned tabs remain visible with matching counts. If the current tab has no matches, use the action in the empty table to open matching work in the other tab. Clear search to restore the table. The timeline action on a planned row brings that operation into view.

Navigate dates and larger views

Use the visible date range to choose a date, the arrows to move to the previous or next period, and Day or Week to fit that calendar period to the timeline. Dates follow the factory calendar's timezone. Select scheduled work and choose Fit selected order to see the order's full scheduled span, including work outside the currently loaded dates. Very long orders open a 56-day window around the selection and show a notice. Zooming preserves the selection and your place on the board.

Large views show work centres in pages. Use Next work centres and Previous work centres to browse them; the waiting-work search still covers the whole saved view. Waiting work loads separately in pages of 50. Load more adds the next page, and the footer shows how much is currently displayed.

When a newly opened view has waiting work and nothing scheduled, Scheduler opens Unplanned. Your subsequent tab choice is remembered for that view during the session. Empty tables distinguish an empty period from a search or filter with no matches and offer an appropriate next action.

Choose visible time

Open Visible time in the toolbar. Working time shows the union of the work centres' shifts, with an adjustable buffer before and after. Custom shows your chosen weekday/time windows, including overnight windows. Add date ranges to hide a particular closure or an irrelevant part of a day. All time shows the continuous calendar. Explicit hidden date ranges apply in every mode; remove a range to show that period again.

A narrow break marks each hidden interval. Select it to reveal that interval temporarily. Work that spans a break remains one operation, and work entirely inside hidden time remains discoverable at the break. Hiding changes the display, not appointments, working calendars or durations. The factory timezone applies throughout. Visible-time settings belong to your saved view; changing views clears temporary reveals.

Open production-order details

Double-click a scheduled block in Scheduler, select a split card in Kanban, or a row in List to open the same production-order drawer used by Orders Overview. The shared drawer provides Overview, Details, Paperwork, and Reports tabs, so the available order information does not depend on the planning surface.

Order and report data is loaded for the active site and environment using the current user's permissions. A missing permission or unavailable scoped record is shown as an error; Planning does not fall back to data from another scope.

Plan and edit splits

Scheduler changes are prepared as a draft before they are committed.

1. Drag eligible work from Unplanned splits onto a work-centre row, or select its checkbox and use Plan selected.
2. Check the local preview. Enter a duration if one is missing.
3. Drag a scheduled block to move it; drag either edge to resize it. The board scrolls when you hold the pointer near an edge. Escape cancels a drag.
4. Right-click a block and choose Edit appointment for exact start, end and work-centre inputs, or Unplan to return it to the waiting table.
5. Select Commit plan when ready to update production. The server validates the complete draft against the current schedule before saving it.

Selecting or dragging work reveals its order's dependency connections. Dashed previews show affected steps; a pin marks a fixed final step. Connections preserve the actual routing's branches and omit detached links.

While dragging, subtly tinted regions show calculated valid start times. During resizing they show possible positions for the active edge. Unsuitable work centres and unknown calendar or dependency coverage stay neutral rather than appearing valid. The complete plan is still validated before commitment.

Blocks and resize edges gently align with visible appointment edges and shift boundaries within eight screen pixels. Hold Alt while dragging to bypass alignment. Hidden interior timestamps do not attract the pointer; visible gap boundaries remain available.

Committing an operation or partial quantity changes its owning order from Draft to Planned. Other operations or quantities may remain unplanned. Editing or synchronizing a draft does not change the production order's status. Planning does not release the order for manufacturing. Later statuses are preserved, and unplanning does not reset the order to Draft.

A click selects a block; Ctrl/Cmd-click adds to the selection. Focus a block and press E to edit its appointment, Delete to unplan, or Alt+Left/Right to move it by one minute (Shift+Alt moves 15 minutes). Press Enter to apply an appointment edit. Undo and Redo work locally in a private draft. Refresh preserves pending work; use the draft's discard action when you intend to remove it.

If a collaborator changes an open appointment, Reload appointment loads the latest values before you continue.

An in-progress split, a completed or cancelled order, or a split without an eligible operational work centre cannot be changed from Planning.

Plan together in a shared draft

Open Shared drafts, name a draft and create it. Any current private draft changes are included. Under People, the owner chooses authorized colleagues; Copy link opens that same workspace for them. A link alone grants no access. Participants need planning management access to edit. Read-only participants can inspect the draft. Your view, selection and visible-time choices remain personal.

Every gesture is calculated locally. Edits sync in the background; the compact status shows Synced, Syncing, or Offline · changes kept. Pending edits are stored in this browser and recovered after a reload. Avoid clearing browser storage while work is pending. Independent edits combine; conflicting edits stay visible for Review changes. Compare your changes with the shared version, choose the shared version, or recalculate and reapply your changes.

Undo removes your own latest planning action when it is still safe. It does not undo another planner's work or sharing settings. Shared drafts use conditional Undo; private drafts also offer Redo. Konnie can prepare changes in the same shared workspace. Its calculations use the synchronized draft and preserve fixed final steps. Newer edits require a fresh calculation. Private conversations and personal skills are not shared with draft participants.

Commit plan commits the exact synchronized revision after validation. Another planner editing during validation requires another review. Pending/offline edits cannot be committed. An uncertain response is recovered using the same operation or commit identity, so a retry does not apply the plan twice.

If production changed, or the draft was closed, choose Continue in a new draft. The changes are recalculated against current production before a separate draft is saved. The source draft and pending edits remain available if recovery fails. If access was removed, you can leave the unavailable draft or copy only your own pending edits, subject to current permissions. Committed and archived drafts are closed to edits. Use Show history in the draft list to open closed workspaces. Active drafts remain until closed; closed history follows the workspace's retention and legal-hold rules.

Plan backward from an exact final step

With an enabled, matching Scheduling Policy, place the chain's last connected step at the required time and work centre. Scheduler keeps that slot unchanged and plans its predecessors locally. Placing the first step continues to plan forward. Moving or resizing the last step recalculates its predecessors; unplanning it also unplans its connected predecessors. Detached links delimit the chain, and fixed or started work is preserved or blocks an incompatible placement.

Configure the gaps between steps in the Scheduling Policy's connections. For a next-working-day gap, choose a lag of 1 day with Working time. Both planning directions use the same gaps and factory calendars. Existing blocking capacity can move preceding work earlier; it does not move the final anchor.

Review the local draft, use Undo or Redo as needed, then select Commit plan to validate and save it. No loading or delivery date is required for this flow.

Schedule backward from loading or delivery

When creating a production order, set its Loading date or Delivery date, enable Automatically schedule production, and choose Backward from loading or delivery date. The server derives the production dates and schedules all workstation splits in the same transaction as order creation.

For an existing order:

1. Save its loading date or delivery date in the order details.
2. Open Scheduler and select Schedule backward in the toolbar.
3. Select the order and calculate a preview.
4. Review every workstation, start, and finish, then select Apply schedule.

Loading takes precedence over delivery. The deadline is the end of the selected target day in the Factory Calendar's timezone. Work is placed as late as feasible before that deadline, accounting for working shifts, breaks, occupied blocking capacity, eligible work centres, and configured routing or Scheduler relationships. Standard routings without explicit relationships follow operation sequence. Frozen variant relationships and enabled scheduling policies preserve branches, lead/lag, and the four dependency types. Component orders must be ready before their parent starts.

All steps require a configured or measured duration. Backward scheduling requires unstarted splits and supports up to 250 splits within a 61-day planning horizon. Active routing exceptions and dependencies outside the order network require manual review. A rejected plan leaves the schedule unchanged. Changing the loading or delivery date, calendar, relationships, or capacity after preview requires a new preview. Finish or reset an existing local draft before opening this flow.

Operation sequence and component readiness inferred by backward planning are recalculated each time you use this flow. Enable matching Scheduler policies or dependency chains when later manual moves must also propagate those relationships automatically. Automatic planning during order creation requires planning.manage in addition to order-creation access.

Customer orders keep requested loading and delivery dates separately, on the header and each position. When you release production with automatic backward scheduling, a position's loading date overrides the header's loading date. If neither is set, its delivery date falls back to the header's delivery date. Every manufactured position uses its material routing. Konnie, the normal order flow and the Order Creator App use the same production scheduler; automatic planning needs planning management access. PDF intake remains reviewed customer demand until you explicitly release production. In the Order Creator App, configure automatic scheduling and its direction, supply the loading date, and configure durations for manual steps.

You can still drag work to another date or eligible work centre, resize it, split it, or use routing pins and detached relationships. The loading target does not lock later manual edits. Blocking centres prevent overlap; parallel centres permit it. There is currently no numeric concurrency limit: use separate blocking work centres for a finite pool of machines. Changing calendars and policies remains a planner decision. Standard inferred relationships propagate only when persisted as Scheduler relationships.

Deadline and working-time buffer

Select an operation to see its order's deadline and remaining working-time buffer beside the date controls. The timeline marks the deadline even when it falls in hidden time; a flag at the edge indicates a deadline outside the visible range. The main order's loading date takes priority over its delivery date. Both include the whole day in the factory calendar's timezone.

The buffer runs from the finish of all required work to the deadline, using the finishing work centre's effective calendar. Breaks, nights and closed days do not add buffer. A negative buffer indicates missing working time; work finishing after the deadline is marked Late, including a finish during closed time. Incomplete work, missing calendars or insufficient coverage show an unavailable buffer rather than an estimated margin.

Moving or resizing work previews lateness locally. For a linked chain, the full buffer appears after the local chain preview settles; further movement clears that result until the new preview is ready. Cancelling restores the current draft's dates and buffer. Production changes only through Commit plan.

Working time, duration, and capacity

Placement uses one-minute precision independently of the visible time-grid scale. The Scheduler applies the effective Factory Calendar of the target work centre:

• a drop in closed time moves to the next available working interval;
• working duration is preserved across breaks and non-working periods; and
• a blocking-capacity work centre sequences splits rather than running them in parallel.

The preview and final draft use the same calendar- and capacity-aware target. The server validates the rules again when the plan is committed, so a draft can still be rejected if another planner changed the schedule first.

Dependencies

Open Scheduler settings, then Dependencies, to manage named dependency chains. A rule links a predecessor and successor using finish-to-start, start-to-start, finish-to-finish, or start-to-finish timing with an optional lead or lag.

Dependency changes and propagated schedule changes are validated against the same scope, calendars, eligibility, and capacity rules. Cycles, missing or inaccessible splits, and unsafe downstream changes fail without a partial schedule update.

Saved views and layouts

Choose a saved view from the toolbar dropdown to filter the visible work centres. Each view remembers each table's visible fields, column order, and configuration independently. The star marks the default view; the number shows its work-centre count. Live search text is not stored in a saved view.

• Select the plus icon to create a saved view.
• Use Edit view beside the toolbar controls to change the name, work centres and lane colours together. From a lane's settings, Edit view opens this same editor at that work centre. From All work centers, save a new view instead.
• Open Scheduler settings and View management to set a default or delete a saved view.
• Choose one of four layout icons in Scheduler settings: Scheduler above tabbed tables, Scheduler above separate tables, tabbed tables beside the Scheduler, or stacked tables beside the Scheduler.
• Drag the shared pane edges to resize the Scheduler and tables. Sizes are remembered for the active planning scope.
• In a planned or unplanned table, open Fields, choose the visible fields, use the arrow controls to set their order, and apply the table configuration.
• In the view editor, select a work centre's colour swatch for presets, a custom colour or Use default color. Default lane color changes the fallback used when there is no work-centre group colour. Save applies the selection and colours together. Search for work centres in the current site and environment; the list also includes centres outside the currently visible schedule. Load more results when needed. A search or partial-page selection preserves the rest of the view.
• Ask Konnie to create a personal resource view, for example: “Create an assembly view with Assembly and Packing, and make Packing orange.” Konnie resolves the work centres in your current site and environment, follows your configured action review, and returns a link to the saved view. Existing planning permissions apply.

If a saved custom field is no longer available, Scheduler removes the stale reference, restores safe fields, and displays a recovery notice.

Work-centre capacity mode is shared operational configuration, not a personal view setting.

The thin capacity strip below each work centre follows your current local draft. Hover or focus it to inspect that day's planned working hours and appointments. Blocking work centres show utilization against their Factory Calendar; overlapping work is marked even when the day's total is below capacity. Parallel work centres show load without a percentage because they have no fixed numeric capacity limit. Missing or incomplete data stays neutral. Hidden time changes the display only. You can hide the strip under Scheduler settings → Capacity strip. This choice is personal and is saved for your current site and system.

Time controls

Use the minus and plus magnifier icons to zoom out and in. Zoom changes the visible cell duration and width; it does not change the Scheduler's one-minute placement precision. Select the clock icon to return the timeline to the current time.

Conflicts, retries, and recovery

Every committed planning change carries the schedule revision and an idempotency key. If the server response is lost or a retryable server error occurs, use Retry same change. This repeats the exact command instead of creating a second change.

For a stale revision, capacity conflict, changed eligibility, or invalid calendar window:

1. Read the displayed conflict message.
2. Reset or reload the Scheduler to obtain the current canonical schedule.
3. Review the affected split and work centre.
4. Prepare the change again against the refreshed schedule.

Do not repeatedly retry a non-retryable conflict. Rejected commands are transactional and must not leave a partial schedule change.

Troubleshooting

Symptom	What to check
Scheduler is not available	Confirm the active site/environment and planning.read.
A split cannot be dragged	Confirm its order and split lifecycle state, an eligible operational work centre, and planning.manage.
A drop appears later than the pointer	Check closed Factory Calendar periods and earlier blocking-capacity assignments.
Resize is unavailable	The assigned work centre may no longer be eligible; unplan the split or move it to an eligible work centre.
Commit is disabled	There may be no staged changes, a request may still be running, or manage access may be missing.
The schedule changed after an error	Reset to canonical state and use Retry same change only when the error is marked retryable.

When requesting support, provide the site and environment, approximate time, affected split or order ID, the displayed error code, and a screenshot. Do not include custom-field values, credentials, tokens, or personal data that is not needed for diagnosis.

Planning responsibility

The Scheduler supports planner commands and configured scheduling rules. Review priorities, prerequisites and the resulting schedule before committing. It does not autonomously decide what should be produced. Calendar or policy changes can require a new preview and planner review.

Related pages

• Production orders overview
• Factory Calendar
• Order networks
• Roles and permissions
• Troubleshooting and support