Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Planning and CPM: activities, logic, calendars, constraints and progress

Planning and CPM: activities, logic, calendars, constraints and progress

Every input the scheduling engine reads, from the WBS outline, activities, calendars, relationships, lags and constraints to progress, the data date and how a version is saved.

On this page

The Planner holds one canonical schedule definition per project. You edit a local draft, and saving it runs the CPM engine. A successful calculation becomes a new immutable version. This page covers what goes into a definition and how the engine treats it.

The plan

Setting What it does
Plan name The schedule’s display name.
Planned start Where the forward pass begins for unstarted work.
Data date The status cutoff. Work before it is history, recorded as actuals. Work after it is forecast. See data date.
Must finish by An optional project finish limit for the backward pass. If the network can’t meet it, float goes negative.

The definition also carries P6-style scheduling options. Imports set them, and you edit them on Schedule › Settings (or through the API): progress mode (retained logic, progress override or actual dates), lag calendar, data date convention, total float method, how critical activities are defined, and more. The defaults are retained logic, the predecessor’s calendar for lags, and start float. P6 compatibility lists every setting and whether the engine applies it.

WBS outline

Add WBS summaries and nest them under a parent to build the outline. WBS IDs are assigned automatically. A summary can’t be moved under itself or one of its own descendants, and it can’t be removed while activities still point at it. Before anything is calculated, the engine checks that the outline is a valid forest: unique IDs, parents that exist, no cycles. Load saved summary history restores a removed summary or activity exactly as it was saved. See WBS and hierarchy for building the outline, the WBS window and publishing the hierarchy to field tasks.

Activities

Each activity has an ID, a name, a kind, a calendar, a working duration and, once started, a remaining duration with actual start and actual finish dates. Kinds:

  • Task: ordinary work.
  • Start milestone and finish milestone: zero duration.
  • Level of effort: spans the work it supports.
  • WBS summary: rolls up its children.

Edits change only the field you touch. Data you didn’t edit, including imported precision such as exact times and minute durations, is kept. Editing a date or duration drops only its own exact-time companion.

Calendars

A calendar has a name, hours per working day, working weekdays, and dated exceptions: non-working days such as holidays, or working exceptions such as a Saturday pour. Each activity uses its own calendar, so durations, lags and float are counted in that calendar’s working days. Calendars imported with detailed shift patterns are kept exactly but can’t be edited in the Planner. See schedule calendar.

Relationships, lags and leads

All four relationship types are supported:

Type Meaning
FS finish-to-start The successor starts after the predecessor finishes. Use it by default.
SS start-to-start The successor starts after the predecessor starts.
FF finish-to-finish The successor finishes after the predecessor finishes.
SF start-to-finish The successor finishes after the predecessor starts. Rare.

Lag is a delay in working days; a negative value is a lead. The DCMA checks flag leads and heavy lag use, because both can hide logic. See Lags and leads.

Constraints

Each activity takes a primary and a secondary constraint, chosen from the ten types P6 and Microsoft Project use:

Constraint Also called
Start on Must start on (soft)
Start on or after Start no earlier than
Start on or before Start no later than
Finish on Must finish on (soft)
Finish on or after Finish no earlier than
Finish on or before Finish no later than
As late as possible ALAP
Mandatory start Hard start
Mandatory finish Hard finish
None

Mandatory constraints override logic and can produce negative float. Use them for contract dates, not to make a bar sit where you want it. See Constraints.

Progress

Record actual start, actual finish and remaining duration as of the data date. The progress mode decides how unfinished work is scheduled when it started out of sequence:

  • Retained logic (the default): the remaining work still waits for its unfinished predecessors.
  • Progress override: incoming links to started and completed activities are released for the calculation but kept in the definition. Remaining work no longer waits for unfinished predecessors.
  • Actual dates: the calculation is driven from recorded actuals rather than forecasts.

The two main modes can give materially different finish dates from the same file. The result records which mode produced it.

Relationships the calculation suppresses under the selected mode are listed in the calculation result, so they’re visible rather than silently dropped.

What the calculation returns

For every activity, the engine returns early and late start and finish dates, total float and free float in working days, the critical flag and whether the activity is on the longest path. It also returns an explanation of the date basis: recorded actuals, a driving predecessor, or the calculated network. For the plan, it returns the project start and finish, the duration in working days, critical and activity counts, the ordered longest path, the full driving set (ties can drive the finish too), the driving predecessors of each activity, and any constraint violations or issues.

Saving, versions and conflicts

  1. Your draft is local until you save. Reload latest version discards local edits. While you have unsaved edits, the Gantt hides calculated bars and date traces are disabled, because neither would match what you see.
  2. Saving calculates first. Only a successful calculation creates a new version. The version, its calculation and the new head are written in one transaction.
  3. Concurrent edits are caught. Each save names the version it started from. If the head moved, the save is refused with a conflict, and nobody’s work is overwritten silently.
  4. Saving never changes field dates. Field tasks change only through a separate, reviewed publication. See Publish the plan to field tasks.
  • Mistake: Using constraints to hold bars in place

    In the app: Health check 5 counts hard constraints, and date traces show when a constraint, not logic, set a date.

  • Mistake: Open ends that make float meaningless

    In the app: Health check 1 lists every activity missing a predecessor or successor, and links each one to the Planner.

  • Mistake: Progress recorded after the data date

    In the app: Health check 9 flags invalid dates: forecasts before the data date and actuals after it.

  • Mistake: Two schedulers overwriting each other

    In the app: Each save checks the version it started from and refuses a stale save.

Limits

  • The Planner doesn’t edit detailed calendar shifts imported from P6, but it keeps them.
  • Dragging a Gantt bar sets a constraint or a lag, depending on the move mode, rather than a fixed date. See Dragging bars.
  • A stored plan, including retained P6 metadata, can be at most 48 MiB, and a schedule at most 30,000 activities. See Large schedules.
  • The calculation API, definition API and Planner require Schedule admin.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file