Float is computed, not imported.
A real forward and backward pass over your network, so critical means critical, not a color from the file.
Import the P6 or Microsoft Project file and Specset computes the network itself: total float, the critical path, and variance against baseline. Then ask what slipped, what is driving the finish, and what the crews should do next week, with every answer linked to its activities.
A real forward and backward pass over your network, so critical means critical, not a color from the file.
What slipped, what is driving the finish, what is near-critical. Every answer opens the Gantt where it points.
Agent changes run with approval and snapshot the schedule first, named and restorable.
“The monthly update used to be a day of clicking through P6 filters. Now we ask what slipped and the driving chain comes back with the activities linked.”
The .xer lives on a scheduler's laptop and everyone else reads a PDF of it. Import it once and the whole team, and every agent, can question the live network instead.
Activities, the WBS tree, dependencies, and the data date come in as built. Monthly updates re-import against stable activity IDs, so links and lookahead plans survive the swap.
Specset runs its own forward and backward pass: all four dependency types with lag, constraints, actuals, and workday math. Float is computed, not imported.
Answers cite their activities and open the Gantt. Edits run only with your approval, and every agent change snapshots a named version you can inspect or restore.
Not the longest bar, the binding chain. Specset walks the driving predecessors behind any date and returns the sequence in forward order, with the link and lag at each step and the constraint where it stops. That is the conversation your schedule review should start from.
Primavera P6 (.xer) and Microsoft Project (.mpp), including the WBS tree, all four dependency types with lag, constraints, actuals, and the data date. The schedule also exports back out in both formats, including any saved version.
Yes. It runs its own forward and backward pass over the imported network: early and late dates, total float, critical and near-critical identification, and the driving predecessor behind every date, all in workday math with the data date applied to unstarted work.
The overview numbers, filtered activity lists by float, progress, company, or WBS branch, the driving chain behind any finish date, variance against the baseline or any saved version, and the lookahead window on screen. Every answer cites its activities and links back to the Gantt.
Only with your approval. Edits run as batch changes you confirm first, and every agent change automatically snapshots a named version with its change summary, so the before state is always inspectable and restorable.
Each re-import upserts against stable activity IDs, so links and lookahead plans survive the monthly swap. Versions capture baselines, monthly updates, and recovery schedules; the pinned baseline drives every variance figure, including how far substantial completion moved.
Scheduling is in beta. It ships behind an add-on your account team enables, and the rest of Specset works the same with or without it. If you want the schedule in the record, ask and we will turn it on.
Send the current .xer or .mpp. We'll return the computed network, the chain driving your finish date, and the variance against your baseline.