Transformer Condition Monitoring Software: Custom Build or Vendor Platform
Buy. With thirty units, one monitor vendor and a single oil lab, that vendor's platform plus a disciplined engineer will beat a bespoke system nobody has time to maintain.
On this page
Buy. With thirty units, one monitor vendor and a single oil lab, that vendor's platform plus a disciplined engineer will beat a bespoke system nobody has time to maintain. Building earns its cost once your monitor fleet spans more than two vendors, once twenty years of lab results sit in spreadsheets, or once a health score has to survive questioning in a capital review.
What Doble, Qualitrol, TXpert and Perception actually do well
A substation asset manager is asking for a replacement on a 345 kV autotransformer in service since 1979. The question from across the table is never technical. It is how do you know, and what happens if we wait two more years. Software is only useful here if it makes that answer reproducible, and for a small fleet the vendor platform already does.
Doble has the deepest test and diagnostic ecosystem in this space. If your programme is built around their instruments and services, their data management is a reasonable home for test results and you should use it. Qualitrol, GE Vernova with Perception, Hitachi Energy with TXpert and Camlin with TOTUS all make good monitoring hardware and reasonable software for reading it, with dissolved gas and bushing analytics that a competent engineer can act on.
None of these is a weak product and none of them claims to be something it is not. If you own thirty large units, bought your monitors from one supplier and send oil to one lab, buy the vendor platform, appoint one reliability engineer to own it, and stop reading. A custom system at that size is overhead pretending to be infrastructure.
Where they stop: the software exists to make their device valuable
That sentence is the whole structural issue and it is not a criticism of quality. A monitor vendor has no commercial reason to become the neutral fleet record that treats a competitor's device, a paper inspection note from 1994 and a result from a third party lab as equal citizens. Ask any of them to score a unit that carries none of their hardware and you have found the edge of the product.
A fleet built over twenty five years has monitors from whoever won the bid that year, speaking DNP3, Modbus or IEC 61850 depending on device generation and how the substation integrator wired it. A meaningful share of your units have no online monitoring at all, because the business case never cleared for the smaller ones. Each portal shows its own units well and knows nothing about the rest, so nobody looks at the fleet. Engineers look at units, one at a time, when something alarms, and prioritisation happens by whoever raises their hand loudest.
Then there is the dataset that matters most and is maintained worst. Twenty years of oil lab results, sent to two or three different labs across the decades, arriving as portable document format, then comma separated files, then a lab portal, with the important ones keyed into a workbook by somebody who has retired. Units renamed after a substation rebuild. Some records referencing the transformer by serial number, others by station and bank designation. That history is what makes trending possible, and IEEE C57.104 in its current form leans harder on rate of change and population percentiles than the old fixed limit tables did. You cannot compute a rate without the history.
The last gap is your scoring model. A utility whose failures have historically been bushings should weight bushing indicators harder. A utility with 1960s units running near nameplate in a hot climate should weight thermal ageing and furans. Your model should encode what has actually killed your transformers, and it should show its work: component scores, the inputs behind each, the rule that converted input to score, and the date each input was last refreshed. Staleness matters as much as value, because a perfect gas result from 2019 on an unmonitored unit is not good news.
Custom versus off the shelf: the arithmetic per monitored unit
Get your own rate. Take the annual software, hosting and support line from your monitor vendor and divide it by the number of units that platform actually covers, not by your fleet size. Those two numbers are usually very different and the difference is the point.
On the build side, in Digital Heroes delivery experience a first release runs $70,000 to $150,000 across 12 to 16 weeks. Midpoint $110,000, plus the lab archive migration and four years of support, puts five years near $207,000, so about $41,000 a year.
At $400 per monitored unit per year, that is roughly 100 units. At $150 a unit it is closer to 275. Below whichever line applies to you, the vendor platform is cheaper and you should keep it.
Here is the part the per unit comparison hides, and it decides most of these cases. The units that most need a score are the ones with no monitor on them, and no per unit licence covers those at any price. If sixty percent of your fleet is invisible to your current platform, you are not choosing between two ways of scoring the same fleet. You are choosing between scoring part of it and scoring all of it. Once a second and third monitor vendor are in the estate, the arithmetic stops being the deciding factor at any unit count.
What a custom build actually costs, including the archive nobody scoped
A first release covering the transformer asset record, ingestion for two or three monitor families plus a historian connector, the oil lab archive migration and an explainable scoring engine with a fleet view runs $70,000 to $150,000 in 12 to 16 weeks. A full platform adding scenario modelling, alarm workflow with acknowledgement, spare unit and contingency planning, and integration into your asset management and capital planning systems runs $200,000 to $480,000 across 6 to 12 months.
Data migration runs 10 to 25 percent of the build and in this category it belongs at the top. Lab results across three vendors and two decades are a genuinely hard parsing problem, and the reconciliation of unit references is manual work that needs an engineer to confirm. Treat extraction as a one time migration tool with human confirmation rather than an ongoing autonomous process, and budget the confirmation hours explicitly.
Year two and each year after runs 15 to 20 percent of build cost annually. That funds new monitor families as procurement adds them, historian tag mapping when a substation is rebuilt, and the scoring weight revisions your reliability group will want after the first two failures the model did not anticipate.
The line that arrives around month seven is the historian. Tags were mapped to points rather than to assets, so load and top oil temperature are sitting there as names nobody can attribute. Reconciling them is unglamorous, nobody wants to own it, and it is on the critical path for any thermal ageing calculation.
The four situations where building wins
Regulatory and prudence fit. A health score that fed a replacement decision will be examined years later by somebody who was not there, possibly in a rate proceeding, possibly by an intervenor. Full lineage from score back to gas trend, loading history and the rule you applied is what makes that survivable. If your answer to how the number was produced is a machine learning model trained on the fleet, ask yourself how you defend that before a commission. Pattern detection belongs in flagging units for attention, not in producing the number that justifies spend.
Scale economics. Past roughly 100 to 275 monitored units, depending on your rate, and immediately once three monitor families are in service.
A workflow that is your competitive advantage. Your scoring model is yours and it should be. Encoding what has actually failed on your system, with overrides recorded with reasons that persist, is how the model improves over five years. Those overrides are also exactly what an auditor or an intervenor will ask to see.
Integration sprawl across three or more systems. Three monitor portals, a historian, a lab portal, Maximo or SAP Plant Maintenance for work history, and a capital planning tool. The question a capital committee asks needs all of them, and the first thing anyone says in that room is show me the underlying result.
How to decide in a week, then commission a written specification
Do the exercise before you spec anything. Pick your six worst transformers. Try to assemble the complete evidence file for each one by hand: online gas trend, bushing power factor history, every oil lab result you can find, loading and top oil temperature over the last three summers, inspection and maintenance events, and any furan result. Time it honestly, including the hours spent deciding whether two records refer to the same unit.
Multiply those hours by your fleet. That is your business case and it is yours rather than a vendor's. If six units took an afternoon, you have a small fleet and clean data and you should keep buying. If two of the six could not be assembled at all because the records reference names nobody recognises, that is the finding, and identity is your first project regardless of which path you take.
Ask the vendors one question at your next review: how would you score a unit that carries none of your hardware. The answer tells you where the boundary sits far better than a feature list.
Then buy a specification rather than a build. At Digital Heroes that means a signed product requirements document covering the asset and alias model, the monitor families in scope, the scoring rules with their inputs and acceptance criteria, written before any code exists and yours to take to three other firms.
We are the wrong firm for you if you want a score that cannot be traced back to its inputs. We will not build that, because it invites a committee to discount all of your numbers rather than one of them. We are also wrong if the scoring weights have to be agreed by a committee rather than by one empowered reliability engineer. What we bring is more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and India LLP, United States LLC and United Kingdom LTD entities so intellectual property assigns under your own law. Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing are all public record.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In a survey of 579 supply chain professionals (July 31 to October 1, 2024), only 29% had built at least three of the five capabilities Gartner identifies as needed for future competitiveness (agility, resilience, regionalization, integrated ecosystems, and enterprise-wide strategy). Source: Gartner (2025) →
- A later Nucleus Research review of analytics software ROI case studies found customers received $9.01 in benefits for every dollar spent on analytics technology, showing returns vary with deployment factors but remain strongly positive. Source: Nucleus Research (2019) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
What is the difference between a monitoring platform and a fleet condition record?
A monitoring platform reads a device and shows what that device sees, which is genuinely useful on the units it covers. A fleet condition record is the neutral, permanent home for every input on every unit, including transformers with no online monitor, paper inspection notes and results from a third party lab. The first is bought from your hardware supplier. The second has to outlive whichever supplier you use next.
How much does migrating twenty years of oil lab results cost?
Budget 10 to 25 percent of the build figure and expect it at the upper end. The parsing across multiple lab formats and decades is hard, but the expensive part is reconciliation: deciding which records refer to the same physical unit when one uses a serial number, another a station and bank designation and a third a number that meant something to somebody who retired. That confirmation needs an engineer, not a script.
Who owns the condition data if we change monitor vendors?
Ask before you sign the hardware contract, not after. You want raw measurements delivered into storage you control, in a documented format, with no requirement to hold a platform licence to read them. On the software side, settle repository, cloud account and intellectual property ownership in writing before kickoff. At Digital Heroes those belong to the client from the first commit, which matters when a monitor fleet turns over and the history has to stay.
Can we score units that have no online monitor at all?
Yes, and those are usually the units where a score changes a decision. The inputs are oil lab results with their sample dates, loading history from your historian, nameplate and age, inspection and maintenance events, and any offline test results. The score should be lower confidence rather than absent, with staleness treated as a first class input, so a good gas result from several years ago visibly weakens confidence instead of passing through as reassurance.
How long before an asset manager can use this in a capital review?
Twelve to sixteen weeks for a first release, and the review is the point of the exercise, so build toward it. That release covers the asset record, ingestion for two or three monitor families, the historian connector, the lab archive and a scoring engine with a fleet ranking. Scenario modelling, alarm workflow and integration into capital planning belong in the following phase, once the scores have survived one real committee.
What happens if a transformer is relocated and renamed?
Its history breaks, unless the asset record is keyed on something durable such as serial number with an alias table covering every station and bank name the unit has carried. Transformers do relocate, and renaming after a substation rebuild is the single most common way condition history is lost. Ask any developer this directly. If their design keys on station and bank, they have not worked with a real fleet.
Can machine learning produce the health score?
It can, and it should not be the number you defend. A commission or an intervenor will ask how a score was produced, and an answer that amounts to a model trained on the fleet invites them to discount everything rather than one figure. Use pattern detection to flag units for attention, then let an explainable rule set with editable weights produce the score an engineer signs their name to.
Should we include breakers and switchgear in the same system?
It is defensible and it roughly doubles the modelling work, so decide deliberately rather than by drift. The condition framework generalises, but the diagnostics do not: gas ratio interpretation and paper ageing have no equivalent in a breaker. Start with the transmission transformer fleet, prove the asset model and the scoring engine on it, then extend once the first capital cycle has tested whether anyone actually uses the output.
What happens if alarms from failed sensors overwhelm the system?
Whether the system is still used in year two depends almost entirely on this. A large share of raw alarms are sensor and communication problems rather than transformer conditions, and an engineer receiving forty a day will read none of them. The build must distinguish monitor faults from asset conditions, rank by impact, and carry diagnostic context so somebody is dispatched with a diagnosis. A tool that cries wolf is ignored within a quarter.
Is it worth building if our fleet is mostly distribution transformers?
Usually not with this design. Distribution units are managed statistically as a population, replaced on failure or on age, and the per unit evidence file that justifies this kind of system has little to work with. The case rests on large power and transmission transformers where a single replacement is a capital decision worth defending. Start there, and revisit distribution only if you already collect meaningful data on it.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
What do I need to prepare before contacting an agency about a dashboard project?
Bring three things: a list of your data sources with who controls access to each, the 5 to 10 recurring decisions the dashboard should support, and examples of the reports or spreadsheets it will replace. That package lets an agency quote in days instead of weeks, and in our discovery work it cuts the audit phase roughly in half. You do not need wireframes or a technical spec; a good agency produces those with you.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
Who owns the code, data models, and pipelines when an agency builds my dashboard?
You should own all of it, and the contract should say so explicitly: source code, data models, pipeline configurations, and infrastructure accounts in your name, with IP transferring on final payment. The trap to avoid is an agency hosting your dashboard on their proprietary platform, which quietly turns a custom build back into vendor lock-in. Digital Heroes delivers into the client's own cloud accounts and repositories by default, and any agency should agree to the same in writing.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Ben.
Senior SEO Strategist · New-york · 5 posts on the site
Published · Last updated .
