Reading your question
Prompt scheduling.
Ask the schedule. It answers, and it acts.
Prompt scheduling is planning in plain words. Ask the schedule what you would ask a colleague, and Fogg reads it, answers in a few lines and puts the answer on the screen: filtered, marked, ready to send.
Planners do an amazing job. Running today’s schedules, thousands of activities in a demanding market, is an astonishing effort. But an intense one. The effort spent on extracting the data would go into action, if the legwork were done by someone else. That someone else is Fogg.
Compared · 26 Jun → 10 Jul
ROS dates · 8 slipped
- Reformer Reactor+21 d
- Reformer Drum+21 d
- Reformer Package+20 d
- CO Cold Box+16 d
- Ammonia Convertor+13 d
ROS slips · 10 Jul
- Reformer Reactor+21 d
- Reformer Drum+21 d
- Reformer Package+20 d
- CO Cold Box+16 d
- Ammonia Convertor+13 d
- Gas Cooling Reactors+10 d
- Gas Cooling Drums+6 d
- CO Drum+6 d
Fogg, compare this schedule with the last one.
Reading both updates
Here. I summarised them in the pane. What needs your eyes now: the ROS dates. There are major slips.
OK, filter them out. Export them to Excel, and the bars as a picture.
Filtering the ROS dates
Ready. What else would you like to look into? The critical path, the peak head count, the major changes. I will guide you through them.
What keeps slipping in the engineering?
Reading the project
On the screen: the 2 engineering activities that slipped at every update since the Baseline.
Both are the piling of 93 Supporting Facilities. The EWP now finishes 14 Aug 2026, 53 wd later, and the CWP follows it.
Shall I show what they drive?
Every language on the team.
A project team speaks many languages. Fogg is learning to answer in any of them: ask in one, read the answer in another, in the same conversation.
Scorecard · 10 Jul 2026
Path scorecard · critical path
- The finish is 30 wd late in two steps, all started in the same place.
- 20 of the 30 wd sit on the Client’s side.
- The chain has no float left (−30 wd) and the pace says 5‑Oct‑29, not 29‑Mar‑29.
The verdict
- One place carries the whole delayAll 30 wd started in 10 Steam Reformer Unit › Civil: CO-CIV-1000 Piling works, slow progress, 10 wd on 5-Jun-26.
- The Client’s hand-over came lateCO-CIV-1094 Additional Piling, Re-Work (SI-011) (Client) → CO-CIV-1003 Excavation (Contractor): 20 wd crossed the hand-over.
- Late work is rolling forward35 activities the Baseline had finished by 10-Jul-26 are still open, more at every update (3 → 8 → 15 → 35).
- The cushion is goneThe path’s float went 0 → 0 → −10 → −10 → −30 wd and the critical set tripled, 34 → 109.
- The date holds only on paperScheduled 29‑Mar‑29. At the pace kept since the Baseline (SPI(t) 0.84) the finish lands 5‑Oct‑29.
Wat zijn de zwakke punten van de planning?
Planning inlezen
Op het scherm: de scorecard van de update van 10 juli 2026.
De zwakste punten: van de 87 activiteiten die nu afgerond hadden moeten zijn, zijn er 52 afgerond (BEI 0,60); 70 activiteiten hebben negatieve float en 100 missen een voorganger of opvolger.
Zal ik ze in de planning filteren?
Wo landet der Endtermin beim bisherigen Tempo?
Leyendo la ruta crítica
En pantalla: el scorecard de la ruta crítica y el pronóstico.
El programa marca el 29 de marzo de 2029, pero al ritmo mantenido hasta ahora (SPI(t) 0,84) la fecha de finalización se retrasa hasta el 5 de octubre de 2029, 136 días laborables más tarde.
La ruta crítica ya no tiene holgura: −30 días laborables. ¿Lo paso a una presentación?
OK, exporte ça dans une présentation.
Création des diapositives
Voilà : la présentation est prête, au format 16:9.
Deux diapositives : le scorecard du 10 juillet 2026 et celui du chemin critique, avec la prévision.
Autre chose ?
Ask it the way you would ask a colleague.
The construction manager, the planner, the project manager and the contract manager each bring their own question. Fogg answers each in a few lines, with the schedule beside it.
Steel FTE · histogramSteel FTE · criticalityCritical Near-critical On track
Give me the 3-week look-ahead.
Reading the project
On the screen: the 3-week look-ahead, 10 to 31 Jul 2026: 15 construction activities, 3 of them critical.
Shall I export it for the site meeting?
Show me the steel FTE histogram.
Reading the project
On the screen: the steel manpower per month, in FTE, from the main and the secondary steel hours.
The peak is 30 FTE in March 2027.
What is the critical load in the steel manpower?
Reading the driving path
On the screen: the criticality histogram of the steel FTE, each month in the colours its bars wear.
The March peak has no critical work. The critical load comes in May 2027: 13 of the 19 steel FTE work on critical activities, the main steel of 10 Steam Reformer Unit.
Shall I filter the schedule to them?
Which activities lost float since the last update?
Reading the project
On the screen: the 165 activities that lost float since the Previous.
39 of them are critical now: 22 in 14 CO Removal & Gas Cooling Area and 11 in 10 Steam Reformer Unit.
Shall I follow them, so you hear when they move at the next update?
The finish, update by update
What drives the finish?
Reading the driving path
On the screen: the driving path to the finish, 30 activities.
All the delay started in one place, the piling of 10 Steam Reformer Unit: first CO‑CIV‑1000, slow progress, then CO‑CIV‑1094, the additional piling. The path has no float left.
Shall I play it update by update?
Yes, play it.
The finish moved in two steps, on 5 Jun and 10 Jul: 29 Mar 2029, 30 wd later than the Baseline.
Delay by party · driving path · since the Baseline
Where it sits
- CO‑CIV‑1094 Additional Piling, Re-Work (SI‑011) Client → CO‑CIV‑1003 Excavation Contractor: 20 wd crossed the hand-over
- CO‑CIV‑1000 Piling works Contractor: slow progress, 10 wd on 5‑Jun‑26
Who is responsible for the delay?
Reading why the finish moved
On the screen: the delay on the driving path since the Baseline, by party.
20 wd sit with the Client: the additional piling, CO‑CIV‑1094 (re-work, SI‑011), crossed the hand-over to the excavation. 10 wd sit with the Contractor: slow piling progress, CO‑CIV‑1000.
That is what the schedule shows by the party of each activity, not who is entitled to time or money. Shall I export it for the contract file?
Named after the man who won by trusting his schedule.
In Around the World in Eighty Days, the novel Jules Verne published in 1872, Phileas Fogg bets that he can go around the world in eighty days, on a timetable everyone at his club doubts. Trains ran late, a bridge was out, a ship was missed. He took every delay as it came, found the way around it, and kept the plan whole. Of course it ends happily, but no spoilers here.
A project runs the same race. The plan is set, the world moves, and hundreds of struggles hit the schedule, waiting for the project team to solve them while the finish drifts. Challenges of that size need support from someone who sees each delay early and answers it. So what better name for an assistant built on today’s AI, always awake, helping the team plan better, than Fogg.
Full AI scheduling.
Next, Fogg builds the schedule with you, from a prompt.
Build a level 3 detailed construction schedule for a container-type substation. Take average sizes and quantities.
Reading typical container substations
Here it is: a level 3 schedule in four groups, from site handover to energisation in 40 weeks. Sizes and quantities are the averages of typical container substations.
Squeeze the overall duration by 10 % by changing the sequence, maybe with a bit of overlap.
Finding the driving path
Done: 36 weeks, 10 % shorter. The earthing and the trenches overlap the foundations, cable pulling starts with the switchgear, and the relay tests run beside the pre-commissioning.
OK, convert it to .XER.
Writing the XER
Ready for Primavera P6.
Let us meet for the demo.
Book a demo