Aller au contenu principal

Blog

Textes sur le contrôle de projet des grands projets : latence des décisions, risque planning, avancement du chantier, et la conduite d'une IA en revue. Articles en anglais.

Decision latency, per eraFrom weeks to minutes: how long a fact waits for a decisionweeksdayshoursminutesPaper reports1960s to 1980s3 to 6 weeksSpreadsheets1990s to 2000s1 to 3 weeksDashboards2010sdaysAgents on one recordlate 2020shours to minutesIllustrative. The time between a fact on site and the decision it needed, in each era’s typical cadence.

L’équipe Verian

· 18 min de lecture

The future of project controls, when AI does the gathering

The method behind project controls is nearly seventy years old and still right. The monthly cadence around it is not. When machines read the documents and keep the record, the discipline changes shape: five shifts, a day in 2030, the risks, what to do in 2027.

The futureAIProject controls
Continuous simulationA thousand tomorrows before breakfastToday, 06:00data date, Rev 14Approvedby a person, 08:10Latethe runs to avoidIllustrative. Every line is one possible project, run overnight. One was chosen, and a name sits on it.

L’équipe Verian

· 12 min de lecture

A thousand tomorrows before breakfast

Simulation used to be a yearly exercise with a consultant and a report. Compute is now cheap enough to run the whole project a thousand times every night, show each decision as a spread of outcomes on the 3D model, and still leave the choice to a person.

The futureSimulation4D Scheduling
Decision latencyHow old is the news you decide on?Week 1Week 2Week 3Week 4Week 5Week 6Week 7Week 8Valves slip two weekssupplier letter, TuesdayMonthly reportwritten, reviewed, presentedDecisionseven weeks laterIllustrative. The work on site carries on through the wait.

L’équipe Verian

· 9 min de lecture

A week inside Verian: from a supplier's letter to an approved recovery

One fact, followed through the platform for three days: a letter is read, a risk is proposed, a question is answered in the review, three recoveries are tried, and one is approved onto the live schedule with a name on it.

ProductSchedule IntelligenceRisk Management
Verian in the roomThree rules for an AI in a meeting1Named

answers only when someone says its name

2With that person's access

never more than the asker may see

3From the record

figures computed by tools, with their source

“Verian, leave” works for anyone present.

L’équipe Verian

· 8 min de lecture

Figures by tools, sentences by the model: how Verian answers

A language model is good at words and unreliable with numbers. Verian keeps the two apart: every figure in an answer is computed by a tool from the project record and cited, and the model only writes the sentence around it.

ProductAITrust
Field progressForty updates. One held. Thirty-nine on the schedule.Each update is checked against the schedule, then a person approves itapproved and pushed · 39held: finishes before it starts · 1

L’équipe Verian

· 8 min de lecture

A twin of the build, not the building: progress on the 3D model

Verian's 4D model is not a digital twin of the asset. It is a twin of the construction, synchronised at the data date: every object's colour points back to a register row, an import and a date, and nothing changes on it without a person's approval.

Product4D SchedulingField progress
Agentic project controlsThe night shift18:0022:0002:0006:00Readera supplier's letter, 19:40Schedulercritical path re-run, 23:10RiskR-0233 proposed, 23:12Contractsnotice drafted, clause 8.4, 02:30Site214 photos matched to the model, 05:5007:00 · the morning brief3proposals wait for a personnothing changed on the record overnightIllustrative. Five agents, each with one job and one tool belt; one brief, one person deciding.

L’équipe Verian

· 13 min de lecture

The night shift: agents will run project controls while you sleep

An agent is a worker with one job, one tool belt and a boss. Give a project five of them and a night, and the morning starts with three proposals waiting for a signature instead of three hours of gathering data.

The futureAgentic AIProject controls
Decision latencyHow old is the news you decide on?Week 1Week 2Week 3Week 4Week 5Week 6Week 7Week 8Valves slip two weekssupplier letter, TuesdayMonthly reportwritten, reviewed, presentedDecisionseven weeks laterIllustrative. The work on site carries on through the wait.

L’équipe Verian

· 6 min de lecture

How old is the news you decide on?

Most capital projects run on a monthly cycle: something happens on site, it reaches a report four weeks later, and a decision follows the review. Measure that wait on your own project before you try to shorten it.

Project controlsDecision makingReporting
Verian in the roomThree rules for an AI in a meeting1Named

answers only when someone says its name

2With that person's access

never more than the asker may see

3From the record

figures computed by tools, with their source

“Verian, leave” works for anyone present.

L’équipe Verian

· 5 min de lecture

Three rules for an AI in a meeting

An assistant that joins your progress review changes who is in the room. Verian follows three rules there: it answers only when named, only with the asker's access, and only from the record.

Microsoft TeamsDecision makingGovernance
Field progressForty updates. One held. Thirty-nine on the schedule.Each update is checked against the schedule, then a person approves itapproved and pushed · 39held: finishes before it starts · 1

L’équipe Verian

· 6 min de lecture

Progress from site should pass through a person

Forty updates arrive from site in a week. Thirty-nine are consistent with the schedule; one says a task finished before it started. What happens to that one decides whether your schedule can be trusted.

Field progressProject controlsDecision making