The AI scheduling studio that speaks fluent P6.
Build a programme from a blank sheet, or open a Primavera P6 or Microsoft Project file. Tell it what you want in plain English: it proposes the edit, the CPM engine judges it, and the critical path moves — live. Export a file P6 or MS Project opens. Open the IFC model beside it and watch the building go up in schedule order. Nothing is uploaded.
What planners do with it
Draft from the spec
Open the spec book. It is read by CSI section, sequenced like a prior programme you attach as the template, and comes back as WBS, activities and logic you can read before you accept.
How the draft is checked →Model the delay
Describe the event. The fragnet lands in a scenario, never the live plan, and the time impact analysis follows AACE 52R-06 — new finish, float consumed, activities pushed — ready to print.
Time impact, as one command →Review the month
Baseline variance, top movers, the delay waterfall and a DCMA score on every update the subcontractors send — then ask the assistant to write the narrative from those numbers.
The reviewer's checks →Open the XER from the email
No P6 licence, no upload. Read the critical path in red, ask what moved, fix a date, and hand back an XER that is byte-identical except for your edits — free up to 100 activities.
The free XER viewer →See it built, in order
The IFC beside the schedule, coloured by date, links kept through every update. Find what is built before what holds it up, and fix it with a link you see the effect of first.
The 4D view →Change a duration. Watch the critical path change its mind.
Two chains race to the same door. The equipment is designed, approved, ordered, fabricated off site and delivered, while the civils crew pours the bases — and installation waits for whichever of the two lands last. Commissioning follows it, then Handover. This is the engine, not an animation: lengthen fabrication and the equipment chain eats its float, then takes over and pushes Handover — exactly what happens in the Studio on your own programme, on every edit, with no Schedule button to press.
In the Studio you drag the bars directly — and a drag writes a constraint, not a date, because in a CPM schedule the logic decides when work happens. When an activity lands later than where you dropped it, Aimavera tells you whether logic or the calendar did it.
A recording of the Studio's 4D view of the sample six-storey office block, played from site start to completion, 16 February to 20 October 2026: the piles go in, then the frame rises floor by floor with the curtain walling following a few floors behind, and the roof plant goes on last. Work under way is amber, critical work red, finished work grey and work not started a faint outline; after the 14 July data date the colours turn paler, as a forecast.
Watch the building go up in the order your schedule builds it.
Open the IFC model next to the programme and press play. Each storey and trade is linked to the activity that builds it, and the model fills in as the dates pass: work under way highlighted, the critical path in red, what has not started a ghost. A floor going in before the frame under it is obvious in a second, where a Gantt would hide it on page nine.
The model is read in your browser, never uploaded. Links are suggested from the storey and trade in your activity names; you confirm them, and the count says how much of the model is linked. Export IFC then hands the linked schedule to tools that read IFC 4.3 work schedules. What the 4D view does.
Opens P6 and MS Project.
Returns files both open.
Import Primavera XER and PMXML, or a Microsoft Project .xml — and export both ways. The XER export patches your original file rather than regenerating it, so every field you didn't touch comes back byte-for-byte: the file your client's P6 receives is the file they sent, plus your edits and nothing else. The MS Project export writes an .xml MSP opens cleanly.
And IFC 4.3 out, for a 4D tool or a client who asks for open standards: the schedule as an IfcWorkSchedule with its tasks, logic and lags, and every model element you linked named by its own GlobalId. It is a separate file: the XER stays the file of record.
Multi-calendar CPM with constraints, the total-float convention the XER format carries, and retained-logic progress — so a file scheduled here and a file scheduled in the tool that sent it are answering the same question the same way.
The reviewer's checks, before the reviewer runs them.
Every check runs against the schedule as it is now — not the dates it was imported with, which stopped being true at your first edit. A 5,000-activity programme scrolls in under 10 ms, and a synthetic 10,000-activity programme in 9.7 ms median.
DCMA 14-point
Scored live. A check that can't be assessed is N/A, never failed — the score is out of what could actually be judged.
Monte Carlo risk
P10/P50/P80/P90 finishes, on-time probability, criticality index. Complete work risks nothing; started work risks only its remainder.
Baselines & variance
Snapshot, then track slippage in the activity's own working days. Positive means late, as in every progress report you've ever signed.
Resource levelling
P6's serial method, shown as an overlay you accept or discard. The histogram reports the peak day — never an average that hides the spike.
Earned schedule
SPI(t), weeks ahead or behind, and the forecast finish — read from progress against the baseline, period by period.
Float paths
The longest path, then the next most critical chains after it — the ones that become the driving path the moment the first one recovers.
Cost risk & the register
A risk register, correlation and branching, weather days, calibration against finished work, kept runs, and a QSRA/QCRA report with the method and the drivers.
Movers & waterfall
Which activities moved furthest from the baseline, and where the driving path gained and lost days between one update and the next.
Saved filters
Named, combinable filters over sixteen fields, matching ALL or ANY, twelve built in. Tick several and they union the way P6 does. They ride in layouts and name themselves on the printed sheet.
Print, page setup and PDF
Paper size, orientation, margins, fit to pages or scale from 10 to 500 per cent, and a three-section header and footer with tokens and your logo. Bars print as vectors, and the preview paginates before it goes to PDF.
Time impact analysis
Describe the delay event; the assistant proposes the fragnet, it lands in a scenario, and the report follows AACE 52R-06 and the SCL Protocol — the finish, the float consumed, the activities pushed.
Quality fixes
Each failing DCMA check unfolds to the activities behind it. Where there is one obvious fix, it is proposed; tick the ones you agree with and they apply as a single undoable batch. Profiles swap the thresholds for your firm's.
The model proposes.
The engine judges.
A model never touches your schedule. It returns edits in the same form the undo stack uses, every one validated before it can apply — a bad response is a rejected parse, not a corrupted programme. And it is never allowed to write actuals: recording that work happened belongs to whoever was there.
Bring your own key — Anthropic, OpenAI, Google, or any OpenAI-compatible endpoint, including a local model that keeps everything on your machine. Keys stay in your browser.
Or bring the assistant your firm has already approved. Claude, Copilot or Cursor connect through a small bridge on your own machine, chosen in the assistant’s own Settings beside the built-in and your-own-key options, and what they propose lands in the same checks and the same approve list. Every applied edit is logged with what was asked, which model and the DCMA score either side, and the schedule from before the first one is a click away.
"Design, procure and install 4 no. 33kV transformer bays including civils, cabling and commissioning. Completion within 9 months of award."
→ proposed: 4 WBS bands · 26 activities · 31 links Rendered as a preview diff. Accept it into the project, edit it first, or throw it away — nothing applies until you say so.> push procurement two weeks
→ 6 activities move · finish slips 4 working days Previewed in plain language, applied through the normal undo path. One command, one undo.$ npx aimavera-mcp
bridge on 127.0.0.1:4815 · pairing code 482913
Your schedule is commercially sensitive. So it never leaves your machine.
No SOC 2 report, because there is no server holding your data to audit. The route a file takes is short enough to print, so here it is.
- your browserThe XER, spec or folder is parsed here. Nothing is uploaded, so there is nothing to clear with anyone.
- your browser storageAutosave goes to IndexedDB on your machine. Close the tab and nothing remains anywhere else.
- localStorageYour model key stays in the browser. We never see it.
- relay · stores nothingOne function forwards an assistant request to the model you chose and keeps no copy. Response headers say
no-store. - your team folderCalendars, code dictionaries, resources and rates are files in a folder your team already shares, on SharePoint, OneDrive or Dropbox. Each schedule says when it has drifted from the library.
- 127.0.0.1 · bridgeYour firm's own assistant connects through a program on your machine, paired by a code and read-only until you allow edits. It talks to this tab and nothing else.
- local modelPoint it at Ollama or LM Studio and the request never leaves the machine at all.
- not presentAnalytics, tracking cookies, third-party fonts. Read the privacy policy for the long form.
The questions a planner actually asks.
No. Parsing, scheduling and autosave run in your browser. Only if you use the AI assistant is the text it needs for that request sent — to the model provider you chose, with your key, through a relay that keeps nothing — or to no one if that model runs on your machine. The route is written out above.
Opening, editing, checking, risk and print are free on a programme of any size, with your own model key or a local model, for personal and evaluation use. Exporting to P6 or MS Project is free up to 100 activities, and Excel and CSV are part of the paid plan; deliver work commercially and you need the licence whatever the file size, at £15 per user per month. Full detail on the pricing page.
Yes — the export patches your original XER, so everything you did not change comes back byte-for-byte. Round-trip it as often as you like.
Yes, both directions — open the .xml (MSPDI) file straight from Microsoft Project, edit, and export an .xml MS Project opens. Or cross it over: open an MS Project file and send back a P6 XER.
No, and it is not trying to. Most P6 programmes are not files at all — they live in an enterprise database, with the EPS, the code libraries, the resource pool and the baselines that the PMO owns and controls. An XER is a snapshot taken out of that. Aimavera works on the snapshot: draft it, edit it, check the logic, run the analysis, hand it back as a file that opens in P6 with only your changes in it. The database stays exactly where it is. What changes is how long the developing and the checking take. Standalone programmes it will build outright, from a blank sheet — but that is a use, not the point. Multi-user and portfolio remain roadmap, not product, and we say so.
Open your schedule. Right now.
Start from a blank sheet, or drop an XER on the page — nothing to install, nothing to sign up for.