When a wind turbine needs maintenance, a delayed answer can mean a delayed repair: engineers need to know what is wrong and whether the right parts and materials are ready. EDF Power Solutions’ DataVolt initiative was designed to make those decisions easier by bringing data from fragmented systems into a governed environment that operational teams could use more directly.
The approach paired Informatica for integration, metadata and governance with Snowflake for data storage and processing, and Microsoft Power BI for reporting. Its central lesson is that a shared platform alone does not empower decision-makers: people also need to find, understand and trust the data it contains.
EDF’s problem was fragmented access, not a lack of data
Before DataVolt, relevant information sat across legacy systems, spreadsheets and SharePoint. Teams did not always know what data existed, who owned it, or whether it was reliable. Answering a question could require reconciling sources, contacting specialists or raising a request and waiting for an extract.
In an ITPro interview, EDF data-governance consultant Kenny Scott described a perception in parts of the organization that “we don’t have any data.” The more precise issue was that information was not consistently available in the right place, format or governed context. That made decisions slower and made it harder for employees to judge whether an answer was trustworthy. ITPro’s account of EDF’s data strategy describes the initiative and its starting conditions.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Why EDF chose a business-led data strategy
EDF selected a new digital strategy in June 2023. The reported goals were to support growth, put useful information in decision-makers’ hands, improve colleague engagement and make operations more sustainable. In the case described by ITPro, the purpose was not simply to modernize technology; it was to shorten the path from a business question to a decision.
The initiative began with wind and battery teams. That initial scope matters: the available account does not establish that DataVolt covered every EDF business unit or replaced every legacy system. The strategy was intended to support the wider business, but its described proving ground was operational.
How DataVolt’s architecture fits together
DataVolt combines three technologies in distinct roles. EDF’s Scott described Informatica as the foundation and “cohesive glue,” Snowflake as the scalable data layer, and Power BI as the place users go to answer questions. Those are EDF’s descriptions of the stack, not independent performance assessments.
| Layer | Technology | Reported role |
|---|---|---|
| Integration, governance and metadata | Informatica | Connects data and helps make it discoverable, governed and interpretable, including through metadata and quality context. |
| Data platform | Snowflake | Provides centralized cloud storage and processing for the initiative. |
| Reporting and consumption | Microsoft Power BI | Provides dashboards and a common user-facing view of data. |
The intended flow is from legacy applications and informal stores into an integrated, described and governed data environment, then into reports and analysis. Power BI’s “single pane of glass” role should not be confused with a claim that it became the authoritative source for every EDF metric.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
Informatica describes its Intelligent Data Management Cloud as a cloud-native platform for connecting, governing, protecting and preparing enterprise data across cloud and hybrid settings. Its Snowflake integration materials outline that product relationship; they do not independently verify EDF’s implementation details.
Metadata and ownership make self-service useful
Putting tables in one cloud platform would not by itself solve EDF’s access problem. A user still needs to know what a dataset means, who is accountable for it, when it was refreshed, what systems contributed to it, which definition a metric uses, and what limitations or access rules apply.
ITPro reported that EDF spent about 18 months labelling and moving legacy data into Snowflake. The account does not specify the exact start date or say that all legacy data was migrated. The labelling work points to the effort behind a usable platform: inventorying sources, resolving definitions, assigning ownership and making lineage and quality visible. Without that context, a consolidated warehouse can simply centralize confusion.
Good self-service is governed access, not unrestricted access for every employee. Sensitive customer, asset and infrastructure data still require appropriate permissions and controls. The goal is to reduce unnecessary dependence on reporting queues while preserving accountability and security.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #3
What decisions DataVolt was intended to support
Wind-turbine maintenance and equipment readiness
When a turbine needs attention, operational teams have to assign engineers and ensure they arrive with the right oils, tubes and other materials. If equipment is missing, downtime can extend by another day or more, according to the ITPro account. EDF reported that consolidating data and using Power BI shortened the time required to analyze information and reach an operational decision. No quantified change in turbine downtime was published.
Wind-generation forecasting
EDF can use historical information to help predict upcoming wind-generation figures. The account presents forecasting as a use case, but does not report a forecast-accuracy improvement or explain the forecasting model.
Potential wind-farm locations
Historical and consolidated data can inform evaluation of potential sites for new wind farms. This is a decision-support use case, not evidence that DataVolt alone determined a particular investment or site selection.
Battery operations
Battery teams were among the initial groups using the initiative. The public account does not name the specific battery datasets, performance indicators or measured operational outcomes, so the scope of that work cannot be assessed in detail.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11How EDF approached adoption and resistance
Data programs often challenge the idea that data is merely an IT by-product, as well as familiar team processes. EDF’s reported obstacles included skepticism, concern about the work involved in labelling and standardizing information, and the risk that apparent agreement in meetings would not translate into adoption.
The response described by Scott was to start with focused teams, demonstrate value “little and often,” and use successful examples to attract other stakeholders. EDF also treated disagreement as something to surface rather than suppress. A skeptical team may be pointing to a real problem with ownership, access, definitions or workflow; resolving that problem can improve the platform and build support.
This approach also helps distinguish genuine use from adoption theater. A dashboard rollout is not a transformation if people continue to rely on private spreadsheets because the new system does not meet their daily needs.
What the published results do—and do not—show
The available DataVolt account reports qualitative improvements: faster access to information and decisions, a consolidated view through Power BI, improved visibility into data ownership and quality, and support for wind and battery use cases. It does not provide independent operational or financial validation.
Best Value
- Reported, but not quantified: faster analysis and decision-making, data consolidation, and support for operational planning.
- Not disclosed for DataVolt: turbine downtime reduction, decision-time baselines, return on investment, user or dataset counts, data-quality improvement, forecast accuracy, cost savings, or carbon reductions attributable to the platform.
- Not established: that all EDF legacy systems were retired or all legacy data migrated, or that the initiative alone enabled a particular generation target.
For another organization evaluating a similar effort, useful measures would include the time to answer recurring operational questions, the proportion of users who can find data without a central ticket, data-product reuse across teams, and evidence that faster decisions improve maintenance scheduling or equipment readiness. Costs, access-control incidents and refresh latency matter too: speed is not useful if the information is stale or the governance model is bypassed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep EDF’s customer analytics program separate
EDF also has a distinct Snowflake-based customer analytics initiative, the Intelligent Customer Engine (ICE). Snowflake’s customer case study describes a Brighton-based customer-data operation intended to replace the Customer Analytics Zone for data science and machine-learning work.
That separate case says one model had taken about four months to deploy in the previous environment; Snowflake reports that model development moved from months to days, with some customer products built in three or four weeks. The case also describes work to identify financially vulnerable customers and support energy-efficiency services. These are vendor-published claims about ICE, not DataVolt results. Snowflake said EDF expected to triple or quadruple annual data-product output; that was an expectation, not a reported achieved outcome.
AI is a possible next layer, not a demonstrated DataVolt result
Natural-language tools can make data discovery easier, but only when users encounter well-described, permissioned and reliable data. Informatica’s CLAIRE GPT materials describe capabilities including asset discovery, metadata exploration, lineage and stakeholder identification, and drafting pipelines. The ITPro account presents CLAIRE GPT as a prospective extension for EDF, not proof that these capabilities were already deployed in DataVolt production. Informatica’s CLAIRE GPT product sheet explains the stated product capabilities.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAI cannot resolve ambiguous business definitions by itself. Before adding natural-language access, an organization needs metadata that reflects business meaning, clear owners, effective permissions and quality rules. Otherwise, the interface may make unreliable answers easier to obtain rather than more reliable.
Lessons for organizations pursuing a similar strategy
- Start with a consequential decision. Pick a recurring operational question where time, accuracy or readiness matters, rather than beginning with a platform purchase.
- Inventory informal sources too. Include spreadsheets and collaboration sites, not only managed databases.
- Assign ownership and definitions. Identify who is accountable for each data product, its quality, refresh expectations and business meaning.
- Build governance into access. Make data discoverable while enforcing permissions and controls appropriate to its sensitivity.
- Prove value in a focused domain. Repeat small, visible wins before expanding into areas with different workflows.
- Measure the change. Record decision latency and operational outcomes before rollout so that “faster” can be evaluated rather than merely asserted.
- Plan for coexistence and cost. Migration does not automatically retire source systems, and cloud consumption needs visible ownership and monitoring.
- Use resistance as discovery. Investigate whether objections reveal a real issue in data quality, access, process or accountability.
EDF’s case presents consolidation as an operating-model change as much as a technology project. Informatica, Snowflake and Power BI formed the reported stack, but metadata, ownership, governance and adoption work were what could turn a shared data environment into something decision-makers could use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
