A regulator funds what the evidence supports.
A rate case, a resiliency plan, a safety order or a storm season puts one decision under scrutiny. Two Quant8 engineers sit with the people who make it and build that evidence into an application they use, on the systems you already run.
Where a team fits
Five decisions, and the systems behind each.
Each has one owner, and each needs data from several systems that do not agree.
| The decision | Who owns it | What the software joins |
|---|---|---|
| Which spans to trim first | Vegetation management | LiDAR, GIS, work orders and outage history |
| Where crews go first in a storm | Outage response | The outage system, crew locations and damage reports |
| Which assets to replace this year | Asset investment | Asset records, inspections, failures and cost |
| Which large-load request to connect, and when | Planning and interconnection | The request queue, studies, substation capacity and contracts |
| Whether two customer records are one customer | Customer operations, in a system migration | The old and the new customer systems, and meter data |
These five are examples. Name the decision you must defend this year, and we start there.
Three ways to start
A team for one decision. Two reviews for a utility that runs Foundry.
Any platform
Forward deployed team
The head of vegetation, outage response, asset investment, new connections or customer operations names one decision. Two engineers build for it beside the planners who make it.
How the team works
Foundry
Governance and security review
When the platform plans work or sends outage notices, the review shows who controls it: who approves a change, and whether every automated message leaves a record.
What the review covers
Foundry
Cost review
The same pipelines on less compute. Each change first names what must not get worse, such as how fresh the outage data is and how soon a notice arrives.
How a saving is proven
Under scrutiny
Four facts for a regulated business.
- Who makes the decision
The software ranks, and your planner decides. A regulator asks who made the decision, and the answer is a person.
- What the evidence is
A decision note comes first: the problem, the evidence from your own data, and the proposal. The sponsor decides before anything is built.
- Where the data stays
In your environment, under your accounts and your security rules. We do not copy customer records or personal data into our working papers.
- Which platform
The one you run. On Palantir Foundry we bring the depth: most of our engineers came from Palantir. On Databricks, Azure, AWS or Google Cloud we work beside your platform engineers.
Questions utilities ask
Four answers for a utility.
Will the software make the decision?
No. The software joins the data and ranks the options. Your planner decides.
We do not run Foundry. Can you still help?
Yes. A forward deployed team works on the platform you already run, beside your platform engineers. The two reviews are for utilities that run Palantir Foundry.
Does the governance and security review certify NERC CIP compliance?
No. It is a review against a written standard of 32 controls. It is not a NERC CIP, SOC 2 or regulatory certification, and not a replacement for one.
Our consultancy runs our systems. Can you work with it?
Yes. Your consultancy holds the contract and the relationship, and named Quant8 engineers lead the work.
Name one decision.
Tell us the decision you must defend this year, and who owns it. We start there.
Book a briefing James replies to you himself.