Bring the documents.
Leave with the programme.
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 to open · no account · nothing uploadedOne pass, start to finish.
Three 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.
Spec
read by CSI section · drawings as sheet images
Programme
a prior schedule, as the template
Knowledge folder
standards · past jobs · rate tables
The model proposes.
The engine judges.
Edits arrive as ops — the same ones the undo stack uses. Each is checked for shape, references and permitted fields before it lands.
Build
WBS, activities and logic from scratch
Impact
a fragnet in a scenario · AACE 52R-06
Risk
Monte Carlo · P10–P90 · criticality index
Review
variance · movers · waterfall · DCMA
Spec — read by CSI section
parsed in the browser · nothing uploadedindex03 30 00 Cast-in-Place Concrete ✓
05 12 00 Structural Steel Framing ✓
07 42 13 Metal Wall Panels ✓
09 91 23 Interior Painting · not sent
+210 more · not sent
keptPART 1 GENERAL · PART 3 EXECUTION · PART 2 PRODUCTS cut to its head
savedsubstation-51-spec.md · the PDF is read once
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.
Programme — a prior schedule as the template
template mode · .xer · .xmlWBS1 Enabling · 2 Substructure · 3 Steel frame · 4 Envelope · 5 Fit-out
activities847 · durations and calendars as built
relationships1,204 · FS 1,102 · SS 71 · FF 31
patternpour → cure 7d → strip → steel · the way you sequenced it last time
summary mode instead: 6 lines, for questions rather than drafting
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.
Knowledge folder — read on request
four read-only tools · Chrome · Edgelist_files standards/ · past-jobs/ · rates.xlsx · method-statements/
outline_file standards/sequencing-rules.pdf → 9 sections
read_file §4 Concrete: strip formwork at 70% f'c, min 3 days
search_files "lead time steel" → 3 hits, rates.xlsx row 41
12 tool rounds max per message · files read once and cached · nothing sent but what the model asked for
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 engine — every op judged, then CPM
shape · references · fields · reschedule✓ link A1020 → A1030 FS both ends exist · no cycle
✗ set A1010.act_start_date — actuals are yours, rejected
✓ add A1040 Erect steel 15d calendar 5d
91 applied · 1 rejected · applied as a preview · one undo
reschedulefinish 14 Mar · critical A1020 → A1030 → A1040 → A1060
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 deterministic CPM engine reschedules and the critical path moves on screen.
Build — a first draft you can read
WBS · activities · logic+ WBS 2.1 Substructure · 2.2 Steel frame · 2.3 Envelope
+ 38 activities · 51 relationships · 3 milestones
A1020Formwork & rebar, grade slab 12d
A1030Pour & cure, grade slab 9d ← 03 30 00 §3.11 cure 7d min
A1040Erect steel, grid A–D 15d ← 05 12 00 §1.05 lead 6wk
engine validated 92 ops · applied as a preview · one undo
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.
Impact — a fragnet in a scenario
AACE 52R-06 · SCL Protocolfragnet+3 activities · tied FS into A1040 · in scenario TIA-03
finish14 Mar → 4 Apr · +15 working days
float consumed6d on Envelope · 0d remaining on Steel
pushed41 activities · critical path now through A1040Make this the plan · or print it as the TIA and leave the live plan untouched
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.
Risk — the date with a probability on it
Monte Carlo · register · QSRA / QCRAregistersteel delivery 3–15d · weather Feb–Mar 0–8d · permit 0–10d
deterministic14 Mar · the single date the CPM gives you
P5021 Mar
P802 Apr · the date worth committing to
on time31% against the contract date
criticalityA1040 Erect steel 94% · A1060 Envelope 71%
Complete work risks nothing · started work risks only its remainder
A single finish date says nothing about how likely it is. Put ranges on the drivers you already argue about — deliveries, weather, permits — and the engine samples the network thousands of times to give you the spread, the date you would commit to, and which activities actually drive it. Print it and it is the QSRA.
Review — the month, in numbers then words
baseline · movers · waterfall · DCMABL-Jan → Feb-P03finish variance +9 wd
critical pathmoved from Envelope to Steel (A1040 → A1070)
top moversA1040 +11d · A1055 +6d · A1032 −3d
waterfallsteel +11 · weather +3 · recovered −5
DCMA11 pass · 2 fail (hard constraints 6, high float 43) · 1 n/a
✓ Feb-P03.xer · byte-identical except 214 changed fields · opens in P6
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.
Say it. Check it. Keep the file.
Each of these is one request and one result from the engine. The panels show what comes back — not a screenshot, the actual shape of the answer.
Draft from the spec
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.
sections chosen03 30 00 · 05 12 00 · 07 42 13 · 07 92 00 +9
templatesubstation-42.xer (WBS + 1,204 links as example)
+ WBS 2.1 Substructure · 2.2 Steel frame · 2.3 Envelope
+ 38 activities · 51 relationships · 3 milestones
A1020Formwork & rebar, grade slab 12d
A1030Pour & cure, grade slab 9d ← 03 30 00 §3.11 cure 7d min
A1040Erect steel, grid A–D 15d ← 05 12 00 §1.05 lead 6wk
engine validated 92 ops · applied as a preview · one undo
Model the delay
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.
fragnet+3 activities · tied FS into A1040
data date04 Feb 2027
project finish+15 wd · 14 Mar → 4 Apr
float consumed6d on Envelope · 0d remaining on Steel
activities pushed41 · critical path now through A1040
Make this the plan · or leave it as evidence
Put a probability on the date
A single finish date says nothing about how likely it is. Give the drivers you already argue about a range, and the engine samples the network thousands of times: the spread, the date worth committing to, and the activities that actually drive it.
steel delivery3–15d triangular, most likely 7d
weather Feb–Mar0–8d calendar-aware
permit0–10d correlated with weather
deterministic14 Mar · the single date the CPM gives you
P5021 Mar
P802 Apr · the date worth committing to
on time31% against the contract date
criticality indexA1040 Erect steel 94% · A1060 Envelope 71%
Complete work risks nothing · started work risks only its remainder
Open the model
Open the IFC in the 4D view, beside the schedule you already have. Each storey and class is offered the activity that builds it, with how sure the match is; take the sure ones in one step and play the build. The links are held by Activity ID, so next month’s update keeps them. The model is read in this browser and never uploaded.
links18 lines · 14 high · 3 medium · 1 low
accepted14 in one step · 4 to review
at 14 Mar3 storeys built · Level 4 under way
driving pathA1010 → A1020 → A1030 → A1210
sequence checkSlab L3 programmed before Columns L3
nothing uploaded · the geometry cache stays on this device
Review the month
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.
finish variance+9 wd
critical pathmoved from Envelope to Steel (A1040 → A1070)
top moversA1040 +11d · A1055 +6d · A1032 −3d
waterfallsteel 11 · weather 3 · recovered −5
DCMA 14-point11 pass · 2 fail · 1 n/a
failshard constraints 6 (>5%) · high float 43
fix proposals ready · tick to apply as one batch
export Feb-P03.xer · byte-identical except 214 changed fields
Not a co-pilot that hands you a file.
Most AI scheduling tools export to P6 and stop. You still need the P6 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.
Everyone who owns a date.
Planner
Turns a spec book and last year's programme into a first draft before lunch, then finishes it in the grid.
Scheduling lead
Runs the DCMA check and the monthly narrative on every update the subcontractors send, without opening P6.
Delay analyst
Models each event as a fragnet in its own scenario and prints the time impact analysis the contract asks for.
Site lead
Opens the XER from the email, sees the critical path in red and asks the assistant what moved.
Your programme 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 we print it. Read the privacy policy for the long form.
- 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 a request to the model you chose and keeps no copy. Response headers say
no-store. - local modelPoint it at Ollama or LM Studio and the request never leaves the machine at all. Slow on a spec book; we say so in the UI.
- not presentAnalytics, tracking cookies, third-party fonts. The fonts are served from our own site for the same reason.
Questions
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.
You give the drivers ranges — a delivery of three to fifteen days, weather across February and March — and the engine samples the network thousands of times, so the answer is a spread rather than one date. Complete work risks nothing and started work risks only its remainder, so a run mid-project narrows as the job progresses. Runs are kept, so you can show what changed between them.
Ones with a folder picker — Chrome and Edge today. Everything else works everywhere; attach files one at a time instead. The drafting guide covers what each file type gives the model, the ceilings, and the order of work.
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.
Open your schedule. Right now.
Free to open, no account, nothing uploaded.