Energy / Utilities · Renewal Call
Energy / Utilities Renewal Call Script: Saving an Asset Analytics Account Six Weeks From Expiry
Your contract with the DNSP ends in six weeks. The Head of Asset Management took the meeting, and you already know why: the SCADA feed never cleared OT security review so they've been running your model off a monthly CSV drop, field services never got past four of forty seats, and when the January heatwave stacked four days of overnight minimums with no thermal recovery and the pole-mounts started letting go in clusters, your ranked list had almost none of them in it. They sat in the post-event review with the Chief Engineer and the Manager Network Performance & Reliability and got asked whether the tool changes anything they do or whether it's a dashboard. They didn't have an answer. Now a competitor is in their inbox at 28% under you and already through the procurement portal.
This is a save call, not a renewal call. The paperwork is the last five minutes. If you open with the order form, or the discount, or "so what would it take to get this done," you confirm the exact thing they suspect — that you only turn up when money is due — and you hand the account to the cheaper vendor. If you open with ticket numbers, dates, what broke internally on your side, and a 90-day plan with names against every line including theirs, the same person starts negotiating with you instead of against you.
The numbers in this script are placeholders shaped like a real utility account — ticket IDs, seat counts, SLA misses, failure counts. Replace every one of them with your own before you dial. The structure survives; the specifics are the entire point, and a utility buyer will test whether you actually pulled the data or just skimmed the CRM.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
1. Before the call: the renewal autopsy
Walk in knowing the bad year better than they do. Pull and read, don't skim: - **Every ticket, 12 months.** ID, open date, first response, resolution, sentiment. Flag anything over 48 hours to first touch. Know the three worst by number and by month. Note which ones landed during storm season or a heatwave cluster — a 9-day response in a quiet week is bad; a 9-day response while the control room is running a major event is the one they'll name. - **Seat usage by function, month over month.** Not "adoption is 40%." It's: "asset management 9 of 10 weekly active; field services 4 of 40 since March; the vegetation program never onboarded." - **Integration and access status.** Where did the OT security architecture review stall? Are they still on a manual data drop instead of the SCADA/OMS feed you sold? How many months? How much of that delay was your security pack arriving late? - **Model performance against their own events.** Before the call, run your ranked list against the last major event. If it missed, know the number. They will. - **Fleet coverage.** What percentage of the distribution transformer fleet did you actually model, and what was the reason — missing nameplate data, wrong install dates on the rural fleet? Was that scoped in writing before signature or discovered after? - **Every QBR commitment never delivered.** The LiDAR vegetation layer. The ADMS/OMS workflow integration. The training day rescheduled twice. - **CSM/AE turnover on your side.** Three owners in eighteen months is your fault and you name it before they do. - **Org changes on theirs.** Did the person who signed still hold the budget? Has the reliability program moved under a new GM? Is Regulatory Affairs now driving the next determination submission? **Get internal alignment before you promise anything.** Written confirmation from Support leadership on the named escalation contact and SLA, from your security lead on the OT architecture pack and the date it lands, from CS on the onboarding hours you can commit. A second broken promise ends this account permanently and it gets attributed to you personally. **Decide your walk-away.** Floor on price, term and seats before you dial. Decide now that service credits — not a discount — are your instrument for the Q2 failures.
- 2
2. Opening: name it before they have to
Do not ask how things have been going. You go first, inside the first thirty seconds. "I know the contract's up on the 31st. I'm not here to talk about renewal yet — I want to talk about this year first, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 41-882, opened 12 June, nine days to first response, and that was in the middle of your winter storm run. Across Q2 we missed the 24-hour first-response SLA eleven times. You've had two CSM changes, February and May. Asset management is at nine of ten seats weekly active — field services is at four of forty, and the vegetation program never got onboarded at all. And the SCADA feed still hasn't cleared your OT security review thirteen months in, so you've been running the model off a monthly CSV. That's what I can see from my side. What am I missing, and what did it actually cost you?" Then stop talking. The silence after this is where the meeting is won. Do not fill it.
- 3
3. The listening phase: let it be worse than you thought
Budget 40–50% of the call here. On a 30-minute call, under fifteen minutes means you rushed it. No "but." No "to be fair." Do not defend a single ticket, even the ones where their team sat on a data request for three weeks. You may be right and you will lose the renewal being right. Probes that work on this buyer: - "Take me through the January cluster. How many units went in those four days, and where did our list have them?" - "Who did you have to explain this to? Was the Chief Engineer in that review?" - "Did any of this land on the Manager Network Performance when they were defending unplanned SAIDI minutes to the regulator?" - "Did it come up in the reset submission drafting — did Regulatory Affairs ask whether they could cite the model in the business case?" - Follow the emotional word. When they say "we were basically flying blind during the June event" — "tell me about that week." Write it down visibly and read it back: "So: Q2 response times, the OT review that's thirteen months old and left you on a monthly file, four of forty-three units in the January cluster, field services never rolled out, and Regulatory Affairs can't use the scores in the submission. Anything else?" Ask "anything else?" twice. The second one usually produces the real wound.
- 4
4. The apology: once, specific, unhedged
One apology. By ticket and by date. Then move. "The Q2 response times were a failure on our side. We re-segmented the support queue in March and your tickets landed behind an enterprise escalation. You paid for a 24-hour first response and we missed it eleven times. That's an explanation, not an excuse. On the OT security review — thirteen months isn't all yours. We didn't get the security architecture and network segregation pack to your OT architect until month five. That delay is ours and it's the reason you bought a thermal picture and got a four-week-old spreadsheet. And on fleet coverage — we modelled 58% because the rural register is missing nameplate data. That's a normal state for a distribution fleet, but we should have put the coverage number and the register gaps in writing before you signed rather than after. That's on me." What you do not do here: explain that their outage history export was six months late, that the vegetation team was reorganised twice, or that the register was always going to be the constraint. Not this meeting.
- 5
5. Proof of change: show, don't promise
They have heard "we're really investing in support." Only three things carry weight. **1. Structural change with a date, shown in their own data.** "We split the support queue by segment on 1 September and added a utilities-specific tier. Your median first response since then is 3.2 hours across nine tickets — I'll send you the list with IDs, not a company-wide average." **2. Evidence from a network like theirs.** "There's a DNSP roughly your size that hit the same wall on OT review. Their Chief Engineer signed off in eleven weeks once we ran the segregation assessment against their standard rather than ours. I'll offer you their Principal Engineer for a call — not a case study, an actual conversation." **3. Something already done, unasked.** "I had the team close out the three tickets sitting in your queue last week, and I've had our security lead rebuild the architecture pack against the AS/NZS framework your OT team uses. It's with your architect as of Tuesday — you should see it before this call ends." If nothing has genuinely changed, say so and change what you control: your own coverage, a named escalation path, an exec sponsor. Do not manufacture progress. They will check.
- 6
6. Rebuild on what works: find the person, not the feature
They still like one or two things. Go find out exactly why, because that's your switching cost. "You said the criticality-weighted ranking is the one thing you'd miss. Who's actually using it?" "What did it replace — was that a spreadsheet the planners kept by hand?" "How many units came off that list into the proactive replacement program last year, and what did it do to the unplanned failure rate per 1,000 units on those feeders?" "If we went dark on the 31st, whose Monday breaks?" That person — usually the Principal Distribution Engineer or a planner in the works program team — is your remaining champion and almost certainly wasn't invited to this call. Get their name and get them in the next one. Then say the switching cost out loud, once, without pressure: "The licence fee is the cheap part. What you'd be rebuilding is two years of normalised outage history, the criticality weighting your engineer tuned against your own asset ranking, and the feed into the works program. That's not a migration, it's a re-implementation — and it lands right when the reset submission is being drafted."
- 7
7. Handling the competitor
Surface it yourself rather than waiting. "I'd assume you've had a quote from someone else — I'd be surprised if you hadn't. What did you like about it?" Then find out how far it's actually gone, because a lunch and a signed order form are different meetings: - "Have they been through your OT security architecture review, or is that still ahead of them?" - "Have they scoped the migration of the historical outage and switching data?" - "Have they given you a fleet coverage number against your register, or a platform number?" - "Is that price in writing, and has procurement got it?" Never disparage them. Reframe from price to total switching cost: "If they're 28% under, that's real money and I'm not going to pretend otherwise. What I'd want you to price alongside it is thirteen more months of OT review with a new vendor, retraining the one team that did adopt, and the period where the ranked list feeding your works program is empty. And plainly: the risk you inherit a new vendor's version of the same support problem, without the two years of history you've got with us to hold over my head." Do not match on price here. Price is the last section.
- 8
8. The 90-day plan, built live, with their names on it too
This is the artefact that changes the decision. Build it on the call in their words, send it inside 24 hours. Four fields per line: **what, who by name on both sides, by when, what 'done' looks like.** Example lines for this account: - **OT security review:** revised architecture and segregation pack to [their OT architect] by the 14th, joint working session week of the 21st. Owner: [your security lead] and [their OT architect]. Done = SCADA feed approved for read-only ingest or a written list of what blocks it. - **Fleet coverage:** register gap report on the 42% we can't model, ranked by feeder criticality. Owner: [your data lead] with [their asset data analyst]. Done = a prioritised fix list of the 200 records that unlock the most fleet. - **Event back-test:** re-run the model blind against the January cluster and the last two summers, compared against the ranked list your engineers would have written. Owner: [named CSM] and [their Principal Distribution Engineer]. Done = a written comparison the Chief Engineer can read. - **Field services adoption:** onboarding for the 36 field services users who never got trained, run by [named CSM], week of the 14th. Done = 20 of 36 weekly active by day 60. - **Vegetation program:** span-level risk pilot on two rural feeders with [Vegetation Management Program Manager]. Done = a comparison of cycle-driven versus risk-targeted spans, and what it implies for spend per line kilometre. - **Support:** named escalation contact, direct line, 4-hour P1 response, effective at signature. - **Governance:** 30/60/90 reviews with written usage reports, dates in the calendar today. - **What I can't do:** "The methodology documentation Regulatory Affairs needs to cite in the determination submission isn't ready. I can commit to a draft methodology statement by day 60 for their review — I'm not going to pretend it's a finished artefact." Then ask for their side: "Half these lines need a name from your team. Who owns the OT review internally, who can give the vegetation program manager an hour, and who mandates the field services rollout — because last time nobody on your side owned adoption and that's part of why it stalled." **Tie a commercial consequence to it.** "I'd rather sign a six-month break clause against these milestones than argue about price. If we haven't cleared the OT review and hit 20 of 36 in field services by day 90, you walk with no penalty."
- 9
9. Only now: the commercial conversation
Earn the transition explicitly: "If we can agree that plan is real, can I walk you through what renewal would look like?" - **Structure before number.** "You're paying for 50 seats and using 13. I'd rather right-size to 25 with a documented expansion price than discount the whole thing — I'd rather be right than big, and it kills the shelfware argument permanently." - **Term traded for comfort.** Shorter term with a break clause for their comfort, or a longer term for price protection. Their choice, priced differently. - **Service credits, not a discount, for the bad year.** "You had eleven SLA misses in Q2. I'm not offering you a price cut for that, because a discount isn't an apology and it tells you the list price was always soft. What I'll do is credit the three months affected. It's specific, it's finite, and it's the honest instrument." - **Any discount is traded.** For a multi-year, a reference call with their Principal Engineer, an early signature, or a named exec sponsor meeting. - **If they're funding from the maintenance line:** "Is this sitting in opex against the maintenance budget or against a capex allowance? Because if the argument is deferred replacements and fewer emergency truck rolls, the paper is different — and it should be written now, while the next submission is being drafted, not after."
- 10
10. Multi-thread, close, and the 24-hour follow-up
Six weeks is tight in a utility. Before you hang up: - "Walk me through what happens between now and signature. Does this go to the asset investment committee? Does procurement need three quotes? Is there a panel arrangement, and are we on it?" - "Who else signs — does the GM Operations need to see the field services plan, does the Chief Engineer need the methodology, does Regulatory Affairs have a view given the submission timing?" - "I'd like your Principal Distribution Engineer in the plan review, and I'd like to bring our head of engineering so the OT conversation happens between the two people who actually own it." - **Book the next meeting on the call.** Date and time, not "I'll follow up." - **Temperature check, honestly:** "On a scale where 1 is you've already decided to leave — where are we right now, and what specifically moves it?" Take the honest answer over the polite one and write down the thing they name. **Within 24 hours, send four things:** 1. The 90-day plan with names and dates on both sides. 2. The ticket data you quoted — IDs, dates, response times, including the bad ones. 3. The reference introduction to the comparable network. 4. A one-page summary of what they told you went wrong, in their words. That last document does more work than any proposal you'll ever send.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before anything else — I know the contract ends on the 31st, and I don't want to talk about renewal yet. I want to talk about this year, because it wasn't the year we sold you. Ticket 41-882, opened 12 June, nine days to first response, right in the middle of your storm run. Eleven misses against the 24-hour SLA across Q2. Two CSM changes, February and May. Asset management is at nine of ten seats weekly active; field services is four of forty; the vegetation program never got onboarded. And the SCADA feed still hasn't cleared OT security review thirteen months in, so you've been running off a monthly CSV. That's my side. What am I missing?
Buyer
You're missing January. Four days, overnight minimums that never dropped, no thermal recovery on the pole-mounts. We lost forty-three units in the cluster. Your ranked list had four of them in the top two hundred. I sat in the post-event review and had to explain why we'd spent a year paying for a model that didn't see it.
Rep
Four out of forty-three. Who was in that review, and what did they ask you?
Buyer
Chief Engineer, GM Operations, and the Manager Network Performance, who had already spent that fortnight working out which of those unplanned minutes she could exclude and which ones were going to sit in the SAIDI number. The question was simple: does this tool change anything we do, or is it a dashboard? I didn't have a good answer.
Rep
That's the question I'd have asked too. Before I respond to any of it — anything else?
Buyer
Plenty. Coverage. You modelled fifty-eight per cent of the fleet because our rural register is a mess. We knew that going in, but the pitch was that the exercise would tell us which records to fix first. Thirteen months later we've got a coverage percentage and no fix list. And Regulatory Affairs came to me in March asking whether they could cite your risk scores in the reliability program business case for the next determination. Answer was no — no documented methodology they'd be comfortable putting in front of the regulator. So the one place it could have paid for itself, it can't go.
Rep
Anything else?
Buyer
Only that I'm the one who championed this internally. That's the part I'd rather not repeat.
Rep
Then let me be specific rather than sorry in general. The Q2 response times were ours — we re-segmented the support queue in March and your tickets landed behind an enterprise escalation. You paid for 24 hours and we missed eleven times. That's an explanation, not an excuse. On the OT review, thirteen months isn't all your process — we didn't get the security architecture and segregation pack to your OT architect until month five, and that's why you bought a thermal picture and got a four-week-old file. And the coverage number and register gaps should have been in writing before signature, not discovered after. That's on me.
Buyer
Right. Well, I'll be straight with you. There's a quote sitting with procurement that's twenty-eight per cent under yours, they've already been through the portal, and they say span-level vegetation risk off LiDAR is out of the box for them. My Vegetation Program Manager is under pressure on spend per line kilometre and that landed well.
Rep
I'd have been surprised if you weren't talking to them, and I'm not going to run them down. Two honest questions. Have they been through your OT security architecture review, or is that thirteen months still ahead of them? And have they given you a fleet coverage number against your register, or a platform number? Then one more before we get anywhere near price — if we went dark on the 31st, whose Monday actually breaks?
Buyer
They haven't started the OT review, and the coverage figure was generic, I'll grant you that. Whose Monday? Priya's. Principal Distribution Engineer. She built the criticality weighting into your ranking and it feeds straight into the works program. She'd be genuinely annoyed.
Rep
What did that replace before she built it?
Buyer
A spreadsheet three planners maintained by hand. And to be fair, three hundred and forty units came off that list into the proactive replacement program, and the unplanned failure rate per thousand on those feeders is down. But that's one engineer and one list, and I can't take that to the asset committee as a reason to sign another year at your number.
Rep
Agreed, you can't. So let's build what you could take. Four things, with names on both sides. One: revised security pack against your OT standard, to your architect by the 14th, joint session the week after — done means approved read-only ingest or a written list of what blocks it. Two: we re-run the model blind against January and the last two summers, and Priya writes the list she'd have written, and the Chief Engineer reads the comparison. If we just confirm what she already knew, that's a cheap validation and you've lost nothing. Three: the register gap report — the two hundred records that unlock the most fleet, ranked by feeder criticality. Four: a draft methodology statement for Regulatory Affairs by day 60, and I'll say plainly it's a draft, not a finished artefact. And I'll sign a six-month break clause against those milestones.
Buyer
The break clause is the only part of that I haven't heard before from a vendor. If the security pack is genuinely with our architect by the 14th and Priya runs the blind comparison herself, I can put that in front of the committee. But I want the Chief Engineer in the room when you present the comparison, and I'm not moving on price being an issue.
Rep
Then let's put a date on the committee and a date for the comparison session with the Chief Engineer and Priya, both today before we hang up. On price: you're paying for fifty seats and using thirteen. I'd rather right-size the seat count than cut the rate, and for the eleven Q2 misses I'll credit the three affected months rather than discount — a price cut isn't an apology. Last question, honestly. On a scale where one is you've already decided to leave — where are we?
Buyer
A three. Four if that pack actually lands on the 14th. Send me the plan with the names on it and I'll get Priya and Regulatory Affairs in the diary.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Your model missed the January cluster. Four of the forty-three units that failed were in your top two hundred. Our engineers have run this network for thirty years and they'd have done better."” | Don't defend the model and don't imply the engineers are wrong — they usually aren't about which feeders. Take the number head-on: "Four out of forty-three is a bad result and I'm not going to explain it away. Here's what I want to test with you: was it a model problem or an input problem? We were running on a monthly file, not the SCADA feed, so the model never saw the overnight minimums that killed those units. I want to re-run it blind on the real loading and temperature history from that week and put its ranked list next to the one your Principal Distribution Engineer would have written. If it confirms what she already knew, that's a cheap validation and you've lost nothing. If it flags units nobody was watching, that's the conversation." Let the engineers be the judges, not the target. |
| “"Thirteen months and the SCADA feed still hasn't cleared OT security review. We've been paying full price for a spreadsheet."” | Take your share of the delay by name before they assign it. "Your process isn't the problem — we didn't get the architecture and segregation pack to your OT architect until month five, and it was written against our framework, not yours. That's ours." Then shrink the next step and date it: revised pack against their standard by a specific day, a joint working session with their OT architect and the Chief Engineer, and a definition of done that includes failure — "approved read-only ingest, or a written list of exactly what blocks it." And price the reality: credit or suspend the portion of the fee tied to the live feed until it's ingesting. Charging full rate for a capability they can't use is the thing that will be quoted back to you at the committee. |
| “"Regulatory Affairs can't cite your risk scores in the determination submission — no documented methodology. So the one thing that would have justified this, it can't do."” | Don't overclaim a regulatory-grade artefact you don't have. "You're right, and it's the gap that matters most given the submission timing." Then find out precisely what would survive: is it a written methodology statement, model provenance and version control, sensitivity analysis, or an independent review? Get the Manager Regulatory Affairs on a call and ask what a business case needs to contain to hold up — cost-benefit, risk quantification, alignment to the reliability program. Commit to a draft methodology statement with a date and say plainly it's a draft. The strongest argument for staying is that a submission written on two years of their own data beats one written on a new vendor's brochure — but only if you can actually document how the numbers were produced. |
| “"There's a quote with procurement that's twenty-eight per cent under you, and they say span-level vegetation risk off LiDAR is out of the box."” | Never disparage; ask what they liked and how far it's gone. Then reframe from price to total switching cost in their terms: "Have they been through your OT security architecture review, or is that thirteen months still ahead of them? Have they given you a fleet coverage number against your register, or a platform number? Have they scoped migrating two years of normalised outage and switching history?" Add the human cost — retraining the one team that did adopt, and the period where the ranked list feeding the works program is empty. Then say the risk plainly: they may inherit a new vendor's version of the same support problem with none of the leverage they now have over you. Do not match price in this section. |
| “"Field services never adopted it. We're paying for fifty seats and thirteen people log in. That's shelfware and my committee will say so."” | Concede it fully and fix the commercial shape rather than the rate: "You're right, and I'd rather right-size to twenty-five seats with a documented expansion price than discount fifty seats you don't use. That kills the shelfware argument permanently." Then diagnose honestly — usually it's a separate login the crews never opened, or outputs that never reached the works program the planners actually run. Ask who owns the field services rollout on their side, because a plan where only the vendor has obligations is a wish list. Put a number on done: twenty of thirty-six weekly active by day 60, run by a named CSM, in a named week. |
| “"Our register is a mess and you only ever modelled fifty-eight per cent of the fleet. That's not what we bought."” | Don't argue that the data doesn't matter — utilities respect honest scoping more than confident hand-waving. "You're right that we should have written the coverage number and the register gaps down before signature. Here's what changes it: loading, fault history and switching records carry more signal than a clean register, so the constraint is narrower than the whole rural fleet." Then deliver the thing you promised and didn't: a ranked register gap report — the specific two hundred records, ordered by feeder criticality, that unlock the most fleet when fixed. Give it a date and a named owner on both sides. It's the cheapest thing you can hand them and it's the one they'll remember at the committee. |
| “"Send me the plan and I'll take it to the asset investment committee."” | Find out what the committee actually decides and what a paper has to contain to survive it — cost-benefit, risk quantification, alignment to the reliability program, safety outcome. Then offer to build it with them rather than emailing a PDF that gets forwarded once and dies. Get the committee date. Get a fifteen-minute prep call beforehand so you know the questions even if you're not in the room. And ask the question that saves renewals: "Does this need three quotes through procurement, and is there a panel arrangement we need to be on?" Most stalled utility renewals die in procurement, not in the business. |
| “"Honestly, none of this has made us safer. If it doesn't reduce live-line work or callouts, it doesn't get priority this year."” | Make the safety line concrete instead of implied, in the Chief Engineer's language: a failure found before it happens is planned switching in daylight with a full permit-to-work and access authority, not a night callout to an energised fault with a crew working near a burning pole-top. Fewer emergency responses means fewer kilometres driven under fatigue rules and fewer live-line jobs. Then make it measurable in the 90-day plan: count of emergency callout jobs and live-line jobs on the feeders where proactive replacements came off the ranked list, versus the rest of the fleet. If you can't show it yet, say so and commit to measuring it — reducing unplanned reactive work is a safety outcome the Chief Engineer can put in front of the board, but only with the count attached. |
Questions reps ask about this call
- How is a renewal call script for energy and utilities different from a generic save call?
Three things change it. First, the failure modes are seasonal and public — a missed SLA in the middle of a storm run or a heatwave transformer cluster costs them SAIDI minutes and possibly STPIS dollars, so your support lapse has a regulatory shadow. Second, the gates are real: OT security architecture review, type approval and Chief Engineer sign-off aren't procurement theatre, and if you stalled at one of them you cannot renew without a dated plan to clear it. Third, the money often isn't where you think — the renewal may sit in an opex maintenance line, while the real decision is whether the program gets written into the next determination submission. Ask when that submission is being drafted; it's usually the timeline that matters more than the contract end date.
- Who should actually be on the call, and is the person who signed still the buyer?
Check before you dial. The Head of Asset Management often signs, but the Manager Network Performance & Reliability owns the SAIDI and SAIFI outcome, the Chief Engineer or Principal Distribution Engineer holds a genuine veto on anything touching an energised asset or the OT network, and the Manager Regulatory Affairs controls whether your outputs can appear in a business case. If your value story is vegetation, the Vegetation Management Program Manager owns spend per line kilometre and may never have been onboarded. Your remaining champion is usually a Principal Distribution Engineer or a planner who built a workflow on your ranking — get them into the plan review, because they are your switching cost.
- A competitor has quoted 20–30% under us. Should I match it?
Not in this call, and probably not at all. Matching before you've re-established value tells them your list price was always soft and resets your floor permanently. Instead, price the switching cost in their language: has the competitor started the OT security architecture review, or is that a year of runway they haven't spent yet; have they scoped migrating two years of normalised outage and switching history; is their fleet coverage number against this register or a generic platform figure; who retrains the team that did adopt. If you need to move commercially, right-size the seat count to actual usage and use service credits for the months you missed SLA. Credits are specific, finite and honest. A discount reframes the whole bad year as a pricing dispute.
- They're saying capex is locked for this determination period and there's no allowance. Is the renewal dead?
Not necessarily, but you need to find out which budget it's living in. Ask directly whether the current contract sits against capex allowance or the maintenance opex line, and who owns the reliability program business case for the next submission. If the argument is deferred transformer replacements, fewer emergency truck rolls and fewer unplanned outages, it may sit inside maintenance rather than needing new capex. And use the timing: a submission built on two years of their own data is far stronger than one built on a vendor's brochure, which makes staying the cheaper path into the next period. Get the submission drafting date in your calendar and multi-thread to Regulatory Affairs.
- How do I handle it when they say the model missed a major event?
Never argue the number down. Establish whether it was a model problem or an input problem — if you were running on a monthly file because the SCADA feed never cleared OT review, the model never saw the loading and overnight temperature data that drove the failures, and you should say that without using it as an excuse. Then propose the cheapest credible test: re-run it blind against the event and the previous two summers, and have their Principal Distribution Engineer write the list they would have produced. Put the two side by side in front of the Chief Engineer. Confirmation is a cheap validation; divergence is a conversation. Either way the engineers are judging it, not being judged.
- Six weeks feels tight. What has to happen before I hang up?
Four things. Confirm the actual decision path — asset investment committee date, whether procurement needs three quotes, whether there's a panel arrangement and whether you're on it, and who signs besides the person on the call. Book the next meeting with a date and time, ideally the plan review with the Chief Engineer and your remaining power user in the room. Take an honest temperature reading: "on a scale where one is you've already decided to leave, where are we, and what moves it." Then send within 24 hours the 90-day plan with names and dates on both sides, the ticket data you quoted including the bad ones, the reference introduction, and a one-page summary of what went wrong in their words.