Southern California Edison · Network assets, weather and customer notification

A Evidence level

South California Edison: grid assets, weather and customer notifications

Publisher: Palantir · Vendors ' official customer information · Direct sources at the case level

Claim origin: Public disclosure by manufacturer or customer · Independent verification: No · Accessed: 2026-09-19

Evidence level measures whether a source can be located and reviewed; it does not mean vendor-reported claims were independently audited.

Standard case | Useful reference with remaining gaps 9 / 12

Business context1 / 2

Transformation workflow1 / 2

Technical workflow2 / 2

Human roles & governance1 / 2

Measured outcomes2 / 2

Source traceability2 / 2

Remaining gaps: Business context, Transformation workflow, Human roles & governance

This case focuses on transforming “grid assets, weather and customer notification” from a one-time analysis or single-point tool into a production stream that can be embedded into real business, verifiable and sustainable.

Business problem

Tens of millions of asset, meteorological and inspection records need to be harmonized, and customer notifications in the event of wildfires and electricity grid incidents must be fast and accurate.

Solution

Foundry links assets, meteorology, inspection and client data to support equipment positioning, risk analysis and customer notification processes.

Technical architecture & production workflow

Step 01

Multi-source operating data and historical events

→

Step 02

Foundry harmonized data models and privileges

→

Step 03

Online map of business objects, relationships, status and executable Action

→

Step 04

AIP/rules/prediction model generation recommendations or automated steps

→

Step 05

First-line personnel confirm and execute in Workshop/Application

→

Step 06

The feedback, the results and the new facts form a closed loop.

Key technology & infrastructure components

FoundryAsset dataMeteorological forecastingInspection dataClient notification workflow

Human roles & accountability

The grid operation, meteorology and client teams are responsible for risk judgement and implementation.

FDE delivery actions

With grid operations and wildfire protection first-line teams, complete processes to identify nodes that really need decision-making rather than displaying data
Collapse decentralized data sources, competencies and business terms into a single, operational Ontology
Combine business rules, optimization models, LLM and traditional software according to a reliable boundary, instead of letting the LLM operate
Insert recommendations directly into existing operating workstations and design approvals, rejections, upgrades and write back to Action
Continue to modify Ontology, rules and automation with operational KPI acceptance and feedback

Reusable delivery patterns

Let's be clear about the client, the relationship, the state and the action, and then talk about Agent.
The recommendation must enter the executable stream, otherwise it's just another dashboard.
High-value deployment is often a combination of data integration + rules/ optimization + AI + Human-in-the-lop
Continuous rewriting of the results of implementation to build cumulative operational memory

Business outcomes & delivery results

Official FY2022 Business Update discloses: 20M assets, 150M meteorological prediction points, 5M survey/vegetation records; client notifications are reduced from hours to minutes, with a 60 per cent reduction in leak notifications.

Evidence boundaries & verification notes

Official Business Update clearly discloses data size and notification indicators.
The source can be directly located in the case; the value remains disclosed by the source and does not represent an independent audit.

Primary source: South California Edison: grid assets, weather and customer notifications ↗