Drop in a spec, a prior programme or a whole folder. Ask for a schedule in plain English. The engine checks every edit before it lands, and what you export opens in P6.
free · no account · nothing uploadedThree things you bring, one engine, three things you leave with. Watch it run, or click any box — the panel below explains the one that is lit.
read by CSI section · drawings as sheet images
a prior schedule, as the template
standards · past jobs · rate tables
Edits arrive as ops — the same ones the undo stack uses. Each is checked for shape, references and permitted fields before it lands.
WBS, activities and logic from scratch
a fragnet in a scenario · AACE 52R-06
variance · movers · waterfall · DCMA
A spec is a thousand pages the planner will not read and the model cannot hold. So the Studio finds where every MasterFormat section starts, shows the model the index, and reads only the sections a planner needs — the parts that carry work and sequence, not the product catalogue. Drawings go in as sheet images to a vision model.
Attach last year's programme and switch it to template mode: its whole WBS tree and relationship list go to the model as the worked example, so the draft sequences the way your firm sequences, not the way a textbook does. Left in summary mode, the same file is something the assistant can answer questions about.
Grant the browser read access to one folder — standards, past programmes, rate tables, method statements. The model gets four tools and decides what to open: list, outline, read a section, search. Every result is text, so a wrong path is recovered by listing. Nothing in the folder goes anywhere except the passages the model asks for, to the model you chose.
The model never touches the document. It returns edits as ops — the same set / add / del / batch the editor and the undo stack use — and each is checked three ways before it lands: the shape is right, every id it names exists, the field is one a model may write. Actuals and existing ids are off-limits. Then the CPM engine, validated against P6, reschedules and the critical path moves on screen.
One sentence, and the draft comes back as WBS bands, activities, durations and logic — each line carrying the spec clause or template row it came from, so you can read the reasoning before you accept. It lands as a preview. Keep it, edit it in the grid, or undo the whole batch.
Describe the delay event. The model proposes the fragnet; it lands in a scenario, never the live plan; the engine reschedules and reports the difference the way AACE 52R-06 and the SCL Protocol expect it: the new finish, the float consumed, the activities pushed. Print it and it is the time impact analysis.
Set the baseline, bring in the update, and the engine already knows the variance, the movers and the waterfall. Ask for the narrative and the assistant writes it from those facts — judgement on top, numbers underneath. Then hand back an XER that patches the original rather than regenerating it.
Each of these is one request to the assistant and one result from the engine. The panels show what comes back — not a screenshot, the actual shape of the answer.
Open the spec. The Studio indexes every MasterFormat section, the model picks the ones a planner needs, and the draft comes back as WBS bands, activities, durations and logic — as ops you can read before you accept.
Describe the event. The model proposes the fragnet; it lands in a scenario, never the live plan; the engine reschedules and reports the difference the way AACE 52R-06 and the SCL Protocol expect it. Print it and it is the TIA.
Set the baseline, bring in the update, and the engine already knows the variance, the movers and the waterfall. Ask for the narrative and the assistant writes it from those facts — judgement on top, numbers underneath.
Most AI scheduling tools export to P6 and stop. You still need the licence, and the specialist, to finish the job. Aimavera is the editor: the details pane, calendars, constraints, resources, risk, print. The assistant is one way to edit it — the grid, the chart and the keyboard are the others.
And it opens the files you already have. XER, PMXML and MS Project XML come in; the same formats go out, with everything you did not touch returned byte for byte.
Turns a spec book and last year's programme into a first draft before lunch, then finishes it in the grid.
Runs the DCMA check and the monthly narrative on every update the subcontractors send, without opening P6.
Models each event as a fragnet in its own scenario and prints the time impact analysis the contract asks for.
Opens the XER from the email, sees the critical path in red and asks the assistant what moved.
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 we print it. Read the privacy policy for the long form.
no-store.By section. The Studio finds where every MasterFormat section starts, shows the model the index, and folds only the chosen sections into the request — the general and execution parts, not the product catalogue. With a local model this is slow, and the UI tells you so.
Attach a prior XER and switch it to template mode: its whole WBS and relationship list go to the model as the worked example to sequence from. A saved library of templates is not built yet, and we will say when it is.
A small network of activities that models one delay event, tied into the existing logic. Insert it, reschedule, compare: that is a time impact analysis under AACE 52R-06 and the SCL Protocol. The Studio puts it in a scenario so the live plan stays untouched.
Ones with a folder picker — Chrome and Edge today. Everything else works everywhere; attach files one at a time instead.
No. Files are parsed in the browser. Only the text the assistant needs for a request is sent to the model you chose, through a relay that keeps nothing — or to a model on your own machine, in which case nothing is sent at all.
Free, no account, nothing uploaded.