How Data Quality Can Negatively Impact an Implementation
These days in energy and commodities, data is everywhere and comes in many formats, meaning that the data governance function at any company is becoming an increasingly critical function. ComTech has tracked data management and observed that it has become a major focus for many companies in the space and yet, there are so many aspects to the issue of data management that it is tough area to crack. One area that has interest for ComTech is in how having high-quality data can enhance the success of enterprise software implementations.
Data conversion and loading is a feature of all new system implementation projects – even at greenfield sites where the metadata still needs to be loaded. However, implementing CTRM, Commodity Management – and even credit solutions, which utilise or source data across the enterprise, face the challenges of aligning data. Energy companies, in particular, often have very fragmented data from across multiple departments and geographic locations due to their decentralized and often siloed nature of systems usage. Common data inconsistencies include everything from counterparty names spelled differently across systems to mismatched invoice numbers, and incomplete market data. Ultimately, AI could prove to have significant value in this area and can be a useful tool for speeding up data cleansing, but human oversight remains essential.
I recently talked to CubeLogic’s, Head of Operations, Ellen Stars, about a variety of topics and we ended up talking about data and how implementations can be faster, smoother and more cost-effective when the data is well prepared. In fact, she told me that around seventy-percent of all CubeLogic implementation projects encounter some sort of data quality issue that can result in project delays and increased implementation costs. “Credit risk systems are particularly complex because they touch multiple systems throughout organizations including treasury, trading, accounting, and legal systems,” she said. “Excel spreadsheets remain a major source of data quality issues due to lack of data entry validation and increased potential of human error. Companies need dedicated master data management programs with proper governance before implementing new systems, rather than trying to clean up data as part of the project,” she suggested.

Based on her experience over the years and at CubeLogic, Ellen Stars recommends that companies implement master data management programs with dedicated data governance teams rather than handling data cleanup within individual department budgets. She also suggests that companies may need data stewards to establish and maintain policies for standardizing items like counterparty names, invoice numbers, addresses, and account numbers. She emphasized that companies should audit existing data, establish governance rules for cleansing, and create processes for maintaining data quality over time. By performing such activities, new system implementations would become one area of benefit amongst many others.
The cost of poor data quality on implementation projects can be significant, in extreme cases adding up to $100K and delaying projects by months. “On troublesome projects, multiple cycles of reloading data, testing, finding new issues, taking fresh production cuts, and repeating the process can take place,” she said. “The problem is that many underestimate the problem thinking that they are 99% there – only to run into significant delays and incremental costs.” But with a proactive approach to data governance, companies can avoid repeated cycles of testing and reloading.
Proper preparation for a systems implementation should always include looking at data quality and in anticipating possible issues and impacts from data mismatches and the like. However, by adopting a prudent approach to data management and governance, implementations can be performed faster and costs kept under control. Certainly, it appears that CubeLogic emphasizes this fact to its implementation clients to insure it achieves implementation success with its credit solution in an acceptable timescale and reasonable cost. A recent CubeLogic project is showing evidence of good progress due to the benefit of upfront planning of a data layer consolidating data from multiple sources (e.g. trading, treasury, accounting) and thus eliminating the need to build custom connectors during implementation and enabling cross-functional teams to collaborate during the simultaneous implementation of a new CTRM together with a market risk and credit risk solution, saving on both time and cost.
However, readers should note that pretty much all E/CTRM and related software implementations suffer from this issue and prepare accordingly. The key takeaway is that by investing in data governance early, organisations can unlock faster implementations, lower costs and better outcomes.
By Gary Vasey, originally posted on CTRM Center