Long-lead equipment expediting that shows a transformer slip against the projects it feeds, the morning the supplier writes
See the 128-week transformer slipping before the project does.
See one case, screen by screen ↓A large power transformer ordered today arrives in about two and a half years. Between the purchase order and the day it stands on its plinth, the supplier sends acknowledgments, monthly progress reports, revised factory schedules, test reports and shipping notices — as emails and PDFs, to whoever is on the thread. The expediter reads them, retypes dates into a tracker, and once a month the project managers compare that tracker with their schedules.
So a three-week slip at the winding stage is in the supplier's email the day it is sent, and the project learns about it when the delivery date moves, often at the port. By then crews, outages and commissioning are booked, and with lead times this long an order that loses its factory slot cannot be bought again elsewhere in time. Frame contracts add a clock of their own: miss the delay-notice window and the right to delay damages lapses. One public power utility in Michigan received a transformer bid with a lead time of 194–246 weeks (APPA Public Power).
Estimated split for one slip on one long-lead order, in calendar days, by hand and with the solution.
Six agents read every supplier update, move the milestones and trace each slip to its projects; the expediter acts.
Lumina Utilities has 11 long-lead orders open, worth $56.4M, feeding 8 projects. Two 90 MVA 132/33 kV transformers are on the same winding line at Aster Transformer Works: T2 for the new Kestrel Ridge substation and T1 for the Fernhill reinforcement. On Tue 13 Oct 2026 at 07:41, Aster writes. Here is what happens next, screen by screen, in the working solution.
Each order is one line of factory milestones — design, core, winding, factory test, ex-works — against the date its project needs it on site. The board reads 11 orders, 7 suppliers, 8 projects fed, 0 late and 5 under 21 days to spare. T2 and T1 each have 7 days to spare. In the right rail, a new email from Ilse Brandt at Aster names both orders.
“…the winding of units 2 and 3 under FC-0219 (your PO 45-118207 and 45-118214) will complete three weeks later than in schedule rev. E: unit 2 on 13 Nov 2026, unit 3 on 11 Dec 2026…”
Rafael clicks Read and apply. The supplier mail reader reads the email and schedule rev. F: two orders, and the cause — conductor late at Aster's sub-supplier. The milestone tracker moves the windings 21 days, T2 from 23 Oct to 13 Nov and T1 from 20 Nov to 11 Dec, and carries the slip down the line using the 49 days from factory to site.
“Carried down the line: T2 on site 4 Jun 2027 · T1 on site 2 Jul 2027 (49 days factory to site)”
On the board the winding milestones jump right with a “W +21 d” marker, and both lines go red at −14 days. The project impact mapper finds both deliveries on the zero-float path to energization: Kestrel Ridge −14 days, Fernhill −14 days. The contract checker finds clause 14.2 of frame contract FC-0219: the delay notice is due by 27 Oct.
“Winding slips 3 weeks on T2 and T1 · Projects late: Kestrel Ridge −14 d · Fernhill −14 d · Delay notice by 27 Oct · 10 working days”
The order page shows T2 — PO 45-118207, $4.82M — needed on site 21 May 2027, now arriving 4 Jun 2027, 14 days late. Rev. E and rev. F sit one above the other, so the moved milestones are plain to see. Every date change carries its source, from the PO acknowledgment of 2 Apr 2025 to today's revised schedule. Delay damages run at $24K a week.
“Schedule rev. F: windings +21 days; on site 4 Jun 2027”
The project page follows T2 through the site sequence — on the plinth, dress, oil fill and dry-out, site tests, protection and control — to energization, now forecast 14 Oct 2027 instead of 30 Sep. Kestrel Ridge enables the 38 MW Northgate Business Park connection and 4,100 homes at Kestrel Fields.
“Late by 14 days since this morning… The Northgate 38 MW connection date of 1 Oct 2027 would be missed.”
T1 drives Fernhill energization, now forecast 12 Nov 2027 against 29 Oct. The second transformer restores N-1 at Fernhill primary, which runs at 104% of its winter rating, and it is needed before the winter peak from 1 Nov 2027.
“N-1 would not be restored before the winter peak.”
A second shift on Aster winding line 2 at the contract's acceleration rate ($38K, 9 days on both units). A direct road haul from Ardmouth quay for T2 ($22K, 6 days). Protection works alongside dressing at Kestrel Ridge, from Tom's site sequence rev. 3 ($0, 8 days). Weekend commissioning at Fernhill ($31K, 7 days). The agents' plan takes all four: Kestrel Ridge +9 days, Fernhill +2 days, for $91K against $412K of contractor standby avoided.
Ruled out: “Swap the 90 MVA spare in for T1 — the spare winds from 17 Mar 2027, after T1.”
Recovery spend over $25K needs the head of capital delivery. Daniel sees the plan — 4 options, $91K, Kestrel Ridge +9 days, Fernhill +2 days — and signs with the meaning of his approval recorded. The plan holds pending Aster's confirmation of the second shift.
Meaning: “I approve the recovery spend and the site re-sequencing”
The drafter writes to Ilse Brandt: what moved, the need dates it misses, and a request under clause 14.5 for a recovery plan by Tue 20 Oct — the second shift and the days it recovers, conductor from the alternate sub-supplier, and the test-bay slots of 22 Mar and 19 Apr 2027 kept. Rafael edits if he wants and sends it under his own name.
Agents draft; a named person sends. Nothing goes to a supplier on its own.
The notice under clause 14.2 is drafted in the contract's wording: Lumina became aware of the delay on 13 Oct 2026, and reserves its right to delay damages of 0.5% of the unit price per complete week, up to 10%. Sunita signs and sends it the morning of the slip — day 1 of 10 working days.
“Delay notice sent on day 1 of 10 · delay damages kept claimable”
The same slip, seen by the five people who carry it — what their week looked like, and what it looks like now.
Six agents read every supplier update, move the milestones and trace each slip to its projects; the expediter acts.
Reads supplier emails, progress reports, revised schedules, inspection reports and shipping documents, and finds the orders, milestones, dates and causes in them — PDF schedules row by row, Gantt tables included.
Compares new dates with the last promise and the PO baseline, moves the milestones and carries a slip down the line to the site date, using the supplier's stage durations and the lane's factory-to-site time.
Links each order to the project activity that needs it, computes days to spare, and follows the zero-float path to energization and to the connection agreements and reliability needs that depend on it.
Finds the delay-notice window, delay damages, recovery obligations and acceleration rates in the frame contract, and counts the notice deadline in working days from the day Lumina became aware.
Drafts recovery-plan requests, status chases, witness bookings and delay notices — what moved, what is needed and by when, and the clause that applies — for a named person to send.
Reads bills of lading, carrier notices, heavy-haul permits and export papers for every order past factory test, computes the ETA and flags a missing document 10 working days before it is needed.
Sends follow-ups; the head of capital delivery approves recovery. The agents propose; a named person decides.
Ask about any order, supplier or project — or say what to chase. Every answer points to the email, schedule or clause behind it.
Which projects does the Aster slip put at risk?
Two substations, 14 days late each. Aster's rev. F moves windings three weeks on units 2 and 3, so T2 reaches Kestrel Ridge on 4 Jun 2027 against 21 May, and T1 reaches Fernhill on 2 Jul against 18 Jun. Both deliveries are on the zero-float path to energization; at Kestrel Ridge that puts the Northgate 38 MW connection date of 1 Oct 2027 at risk.
What does the contract say about this delay?
Frame contract FC-0219: notify the claim for delay damages within 10 working days of knowing of the delay — by Tue 27 Oct. Damages are 0.5% of the unit price per complete week, up to 10%: about $24K a week on T2. Aster owes a recovery plan within 5 working days of our request. The notice is drafted for Sunita to sign.
Which other orders have less than 21 days to spare?
Before today's Aster email, five: T2 and T1 (+7 each), the Saltmarsh 400 kV GIS (+11) — waiting on our own drawing comments, 11 days overdue — the Orchard Vale pump motors (+10), held by a pending export licence, and the Linden Park reactor (+15), after its core steel arrived late.
Ask Brennmoor for the export licence
The chase to Brennmoor Motors asks for the licence number and the final packing list, so the Orchard Vale delivery can be booked for 20 Nov. The motors have 10 days to spare; you will be reminded on Mon 19 Oct if there is no reply.
13 screens from the working solution, on its sample data. Pick one to see it large.
The days-to-spare bands, the contract defaults, the sources and who decides are settings, chosen by the supply chain team. Changes are audited.
| Setting | Default | Choose from |
|---|---|---|
| Days to spare — healthy | 21 days or more | Set in days; Watch is 0 to 20 days and Late is an arrival after the need date, coloured on every line |
| Follow-up cadence | Weekly status request per order | Daily once an order is under 21 days to spare · in the supplier's local working days |
| Delay notice window | 10 working days | Read from each frame contract |
| Delay damages | 0.5% per week · cap 10% | Read from each frame contract |
| Recovery plan due | 5 working days after request | Read from each frame contract |
| Witnessed tests | Factory test for every unit over 30 MVA | Witness booked from the order page, with a request drafted to the supplier |
| Approves recovery over $25K | Daniel Moreau, head of capital delivery | Signs delay notices: Sunita Varga, category manager · sends supplier follow-ups: Rafael Okoye, expediters |
| Sources the agents read | expediting@ shared mailbox | Personal mailboxes opt-in (2 expediters) · ERP purchase orders nightly · project schedule export nightly 02:00 · forwarder notices and bills of lading |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate: the standby figure uses the sample's inputs, 2 sites × 14 days × $14,700 a day, and the split of days is an estimate · “typical” = published figures: Wood Mackenzie Q2 2025 survey via pv magazine and EE Power (power transformers about 128 weeks, generator step-up units 143–144; 30% US supply deficit for power transformers in 2025; prices up 77% since 2019) · APPA Public Power (a 194–246 week transformer bid). Lumina Utilities and the people, suppliers, projects, orders and documents named on this page are fictional — characters and sample data in the working solution.
It is the work of tracking an order for equipment such as a power transformer, switchgear, a reactor or a large motor after the purchase order, through the factory to the site, so it arrives by the date the project needs it. Long-Lead Equipment Expediting shows every such order as a line of factory milestones against its need date, and six agents keep those lines current from the suppliers' own emails and documents.
The supplier mail reader reads every email, revised schedule and report as it lands and finds the dates that moved. The milestone tracker carries the slip down the line to the site date, and the project impact mapper follows it to energization and the customer connections behind it. In the sample case the agents read and applied the supplier's email in 1 min 50 s, the morning it arrived and 31 weeks before the need date.
Yes, read-only. It reads purchase orders from the ERP and project activities, finish dates and float from the nightly schedule export, and links each order to the activity that needs it. It never changes a purchase order, a contractual date or a schedule; project managers own their schedules.
No. The expediting action drafter drafts recovery-plan requests, status chases, witness bookings and delay notices with citations, and a named person sends each one. Supplier replies are read back onto the milestone lines.
The contract checker finds the delay-notice window and the delay-damages clause in the frame contract and counts the deadline in working days from the day the delay became known. The notice is drafted in the contract's wording that day for the category manager to sign; in the sample case it went out on day 1 of 10.
Yes. The sample covers power and generator step-up transformers, gas-insulated switchgear, a 33 kV switchboard, a shunt reactor, and pump motors and transformers for a water pumping station, each with its own milestones — for switchgear, parts and assembly; for motors, the stator.
Yes. The agents price recovery options and propose a plan, and rule out options that would not help, such as a spare that winds after the late unit. Recovery spend over $25K and any site re-sequencing need the head of capital delivery's signed approval, and every step is recorded.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your frame contracts, a sample of supplier emails and schedules, your purchase orders and project schedule exports — and it goes live once every quality gate has passed. We will walk you through it on your own long-lead orders first.
Pay for the work done, at the contracted rate.
1-min demoTender Bid EvaluationEvery bid levelled to the same scope, so a hidden exclusion never wins the award.
1-min demoContract Obligation ManagementEvery penalty owed claimed inside its window, and no renewal missed.
1-min demoWe'll run Long-Lead Equipment Expediting on a sample of your own supplier emails, schedules and project dates.