Scheduling: CPM planning, analysis and evidence in one workspace
A native critical path scheduling workspace with a P6-validated engine, P6-style layouts and views, Line of Balance and takt planning, Last Planner weekly work plans, activity discussion and a change feed, P6 import options, DCMA health, three-point risk, a reviewed update cycle, portfolio programs, reports, baselines, versions, resources, costs and period performance.
Scheduling in os.construction is a critical path method (CPM) workspace built into the project, not a file passed around beside it. You build the network: activities, a WBS outline, calendars, all four relationship types with lags and leads, and P6-style constraints. You record progress against a data date. A calculation engine cross-validated against Primavera P6 then works out every early and late date, total and free float, and the longest path. Each saved calculation is kept as an immutable version you can baseline, compare, analyse and explain.
- Who
- Schedulers, project controls, PMs and owners’ reviewers
- Where
- Project Tools › Schedule: Overview, Plan, Update, Analyze, Resources & cost, Import & export
- Access
- Schedule admin for full-network planning and analysis
- Connects to
- Field scheduleBudgetInsights
The engine
The calculation engine runs in an isolated worker with no access to application data. Each request gets an authorized snapshot of the saved plan. The engine is the original scheduling code, adopted byte for byte with checksums, not a simplified rewrite. Its development suite compares its dates with P6’s own stored answers. On the P6 23.12 cross-validation fixture, 156 of 160 date comparisons match, and each known difference is documented in the engine source with the reason it remains.
The engine understands what P6 schedulers rely on:
- Four relationship types: finish-to-start, start-to-start, finish-to-finish and start-to-finish, with positive lags and negative leads.
- Ten constraint types, primary and secondary: start on, start on or after, start on or before, finish on, finish on or after, finish on or before, as late as possible, mandatory start, mandatory finish, and none. Plus a project must finish by date.
- Progress modes: retained logic (the default), progress override and actual dates, read from P6 project settings on import.
- Scheduling options: lag calendar, data date convention, total float method, expected finish dates and make open-ended activities critical, measured against P6 23.12, plus suspend and resume of started work.
- Resource-dependent activities, each driving assignment on its own resource calendar with its assignment lag and P6’s Drive Activity Dates flag, and units % complete carried through import and export.
- Calendars with working weekdays, hours per day and named exceptions.
- Activity kinds: tasks, start and finish milestones, level of effort and WBS summaries, with level-of-effort and summary dates derived from the work they span.
- Time precision: whole days or exact working minutes, detected automatically from the file. Agreement with P6 on 39 real projects rises from 81.5% to 87.6% of compared values with it on.
- P6 cost, units and earned value fields: roll-ups by resource type with expenses included, cost and units % complete, baseline variances and P6’s earned value indices. On 34 projects, 98.7% of the costs and units P6 stored agree. See P6 compatibility.
- Scale: up to 30,000 activities per schedule. A 19,000-activity programme imports in about 10 seconds or less, at about half the peak memory of the previous release, and calculates in about 5. Above 2,000 activities the Planner loads a lean plan, about 10 MiB at 25,000 activities, and saves only what changed.
What you can do
How the pieces fit
Everything downstream reads a saved version, never an unsaved draft. When a report, trace or analysis says “version 12”, it means one exact, digest-verified definition and the calculation saved with it. That’s what makes the evidence hold up later: you can show what the schedule said on the day you said it.
Status
Scheduling is live. Everything in this section runs in the app today, and each guide states its own limits. Most capabilities have local release evidence, including browser journeys and contract tests. Authenticated production acceptance is still being recorded for several of them. Line of Balance, takt planning, Last Planner, discussion, presence, the change feed, rebasing, the new Activity Details tabs, the WBS window and Open projects are covered by unit and service tests; browser acceptance journeys for them haven’t been written yet. The P6 view features still to come, such as exporting layouts to P6 .plf files, are listed under Views and layouts.
Keep exploring
Related across os.construction
- DocsViews and layouts: filters, Group & Sort, columns, Network and Trace LogicOpen and save P6-style layouts for yourself, the project or the company, export and import them as files, build filters with nested All/Any criteria and highlight mode, group and sort to five levels with totals, choose from 45 core columns plus baseline, cost, units and earned value columns, draw a progress line, read the logic in the Activity Network, Trace Logic and Assignments views, and roll the plan up in the WBS window.
- DocsP6 compatibility: settings, import, export and what round-tripsHow closely os.construction matches Primavera P6. Which scheduling settings the engine honours, which P6 calculated fields it works out, what crosses an XER or P6 XML file in both directions, the measured agreement with P6's own dates and costs, and the limits that remain.
- GlossaryPercent Plan Complete (PPC)The share of a week's commitments that were finished as promised, used in the Last Planner System to measure how reliable short-term planning is.
- GlossaryLook-Ahead ScheduleA short-range schedule, usually two to six weeks, that breaks the master schedule into the specific tasks crews will perform next.
- ExplainerHow the critical path worksForward pass, backward pass and float on an eight-activity network, then one slip moves the critical path.
- BlogHow to build a three-week look-ahead schedule the field will actually useThe master schedule says what has to happen. The three-week look-ahead says who does it, where, and what has to be cleared first. Here is how to pull it from the master, break it down to crew level, screen every activity for constraints, get commitments from the trades, and roll it forward each week, with a worked example.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →