Wind Farm O&M Software: Custom Build Versus Power Factors and Maximo
Buy, unless you are defending money. Under about sixty turbines on one manufacturer with the availability guarantee sitting on the service provider, Power Factors plus a maintenance system is the right purchase and a build is capital wasted.
On this page
Buy, unless you are defending money. Under about sixty turbines on one manufacturer with the availability guarantee sitting on the service provider, Power Factors plus a maintenance system is the right purchase and a build is capital wasted. Cross into multiple manufacturers, self-performed service, or lender reporting you have to reproduce from source, and one component becomes worth owning: the production loss ledger.
What the off-the-shelf products actually do well
Your asset manager has six tabs open and none of them agree about turbine A07 last Tuesday. That is the situation, and it is worth being fair about the tools in those tabs before deciding any of them should be replaced.
Power Factors, which absorbed Greenbyte, is a serious product. It ingests supervisory control and data acquisition (SCADA) feeds from most manufacturers, computes lost production, and produces the monthly reporting pack a lender will accept without argument. Bazefield does similar work with a stronger real time operations centre flavour. SkySpecs has built a genuine business around blade inspection and turned it into an operations and maintenance (O&M) workflow product. On the maintenance side, IBM Maximo is the enterprise standard for good reason: work order routing, spares, labour costing and approval chains that survive audit. Fiix and UpKeep serve smaller fleets at a fraction of the cost and do it well.
The manufacturer portals deserve credit too. Vestas Online Business, GE's Digital Wind Farm and Siemens Gamesa WebWPS give you fault detail on their own machines that no third party can match, because the fault taxonomy was written by the people who built the pitch controller.
If you own one wind farm on one turbine model under a full service agreement where the manufacturer carries availability risk, the portal plus Fiix is the correct answer and you should stop reading. Buying is cheaper, faster and safer, and the money you would spend on a build is better spent on an analyst who actually reads the reports.
Where they stop: reconstructing a claim inside the window
The workflow that breaks every product in this category is the availability dispute, and it breaks them for a structural reason rather than a technical one.
IEC 61400-26 defines the availability and lost production categories the industry argues in. Implementing it cleanly means joining ten minute SCADA intervals, fault code logs, work order timestamps and a contracted power curve, per turbine, per interval, then allocating each interval to a responsible party under the exclusion list in your specific service agreement. Your counterparty runs the same standard with their exclusions, which conveniently treat grid curtailment, low wind and anything they classify as scheduled as outside the guarantee.
So a quarterly dispute is an argument about method, not facts, and the party with the better ledger wins. Usually not you, because your version was rebuilt in a spreadsheet two weeks after the event by someone reading work order comments.
Then the part that costs the most and shows up nowhere. Your full service agreement has a claim window, commonly thirty or sixty days from the event. Assembling the evidence pack takes hours, so it happens for the obvious large failures and quietly does not happen for the medium ones. Those claims expire in silence. Nobody files a report saying you failed to claim, which is exactly why the leak survives.
Maximo cannot fix this because it has no concept of a power curve or a lost megawatt hour. It knows an asset was down between two timestamps. Power Factors does compute lost production, but with its allocation logic on its category tree, and when you need to defend one number you cannot open the arithmetic. And the manufacturer portal is never going to build you a tool for claiming money from the manufacturer.
The arithmetic: per-turbine licensing against a build
Do this with the quote in front of you, because published pricing in this category is scarce and negotiated.
Monitoring platforms here price per turbine per year, and maintenance systems price per seat per month. Take both numbers from your own proposals. Suppose the monitoring platform lands at $600 per turbine per year and you run 180 turbines. That is $108,000 a year. Add a maintenance system at $95 per seat per month for forty technicians, planners and asset managers, which is another $45,600. You are at roughly $153,000 a year, or $460,000 over three years, and at the end of it the allocation logic still belongs to somebody else.
Against that, a focused first release sits at $60,000 to $130,000 once. The crossover is close to 150 turbines across three or more sites, or about 40 platform seats, whichever you reach first. Under that, buying wins clearly.
One number that does not move the comparison: turbine count barely affects build cost. Eighty machines or eight hundred, the software is the same. What moves it is the number of distinct manufacturer data sources, because each one is a new protocol, a new status code taxonomy and a new normalisation mapping, and that is genuinely three to six weeks of work each rather than a configuration toggle.
What a custom build actually costs
These are Digital Heroes delivery bands across more than 2,000 projects, not industry averages. A focused first release covering the site, turbine and component asset model, SCADA ingestion for one manufacturer, the production loss ledger, fault to work order automation and availability reporting runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding multi-manufacturer ingestion, an offline technician application, warranty claim automation, condition monitoring integration and campaign planning runs $150,000 to $400,000 phased over 6 to 12 months.
The two lines that get left off proposals:
- Migration takes 10 to 25 percent of the build budget. Ten years of ten minute SCADA data across a few hundred turbines is billions of rows, and making it queryable is an engineering problem with a real price. Work order history migrates alongside it, with free text technician comments classified into a structured failure taxonomy and a human checking a sample before anyone relies on it.
- Ongoing support lands at 15 to 20 percent of build cost every year after launch. Manufacturer application programming interfaces change, status code tables get extended, service agreements get renegotiated with new exclusion lists, and the rules engine has to follow. Budget it as a line rather than discovering it as a surprise.
Other cost drivers specific to this category: four service agreements with four availability formulas means the rules engine models four; NERC CIP obligations, if any of your assets are in scope, add cybersecurity boundary work between the SCADA network and the business network; and lender or grid operator reporting brings audit trail and data lineage requirements that a lighter build can skip and a serious one cannot.
The four situations where building wins
Four conditions, and you need at least two before the numbers work.
- Regulatory and contractual fit. IEC 61400-26 implemented against your exclusion list, not a vendor's. Data lineage from a lender report figure back to the raw ten minute interval. NERC CIP boundaries where they apply. Lockout tagout records and torque readings that hold up as compliance evidence rather than as notes.
- Scale economics. Above roughly 150 turbines and 40 seats, per-turbine and per-seat pricing compounds every year while your build cost does not.
- A workflow that is your competitive advantage. The claim pipeline is the honest example. Any downtime event whose category and duration match your contract criteria drafts its own claim with the fault trace, the ledger rows, the work order cost and the clause reference, with the claim window counting down on a dashboard. Firms that file the medium claims recover money that firms without the pipeline never see.
- Integration sprawl across three or more systems. Two manufacturer portals, a monitoring platform, a maintenance system and a spreadsheet is five sources for one fault, and reconciling them is a job somebody is doing full time whether or not it has a job title.
The position we will defend: the production loss ledger should be yours even when everything else is bought. It is the number your contracts, claims, lender reports and any future sale all run on.
How to decide in a week
Pick the last availability dispute you lost or settled. Give one competent person four hours and the raw data, and ask them to rebuild the number from SCADA intervals, work orders and the contract clause. Not the summary. The arithmetic.
If they can do it in four hours, your current stack is fine and your problem is process. If they cannot, you have just measured the cost of not owning your allocation logic, and you can put a figure on it by adding up the claims that expired unfiled last year.
Then run the second half of the test. Ask two vendors to whiteboard the asset model before quoting. The right answer separates site, turbine and maintainable component, with the component carrying a serial number and a failure history that survives being refurbished and reinstalled on a different machine. A flat asset table with a location column means they have built facilities software.
What follows is a paid discovery phase. At Digital Heroes it produces a signed product requirements document before any code is written, covering the asset model, the allocation rules, the integration surface and acceptance criteria. You own that document whichever firm you hire. We contract through India LLP, US LLC and UK LTD entities so the intellectual property assigns under law your own counsel already reads, and you meet the named engineers before signing rather than after.
We are the wrong firm if you want a fixed price before a specification exists, or if you need a vendor to also operate the platform for you. We build it and hand it over.
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.
- Grand View Research valued the global field service management market at USD 4.43 billion in 2022 and projects it to reach USD 11.78 billion by 2030, a 13.3% CAGR, driven by growing field operations in telecom, utilities, construction and energy. Source: Grand View Research (2023) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
Frequently asked questions
What is the difference between a SCADA historian and an O&M platform?
A historian such as OSIsoft PI or Canary stores time series measurements and serves them back quickly. It has no view of contracts, work orders or responsible parties. An operations and maintenance platform sits above it and turns those measurements into availability, lost production and maintenance actions. Many operators keep the historian and build or buy the layer above it rather than replacing storage that already works.
Can one system read Vestas, GE and Siemens Gamesa data together?
Yes, and normalising them into one asset model is usually the main reason an operator builds anything. Each manufacturer brings its own protocol, its own rate limits and its own status code taxonomy, so budget roughly three to six weeks of engineering per additional manufacturer to build and validate the mapping. What you get back is one fault taxonomy and one availability calculation across the whole fleet.
How long does it take before the first useful output appears?
The first release ships in twelve to sixteen weeks, and in a staged rollout on one site the production loss ledger and availability reporting are usually live around week ten. Value shows up first as the end of manual spreadsheet reconstruction, and second as claims that used to expire unfiled because assembling the evidence pack took longer than anyone had. Multi-site rollout follows over the next two quarters.
Who owns the data model if an agency builds this?
You should own the repository, the cloud accounts and the unrestricted right to hire another firm, agreed in writing before kickoff. In this category the asset model and the production loss ledger are the real asset, because they are what you use to defend disputes and to support diligence in a sale. A vendor who owns that model holds the stronger hand in every future negotiation.
What happens if our service agreement is renegotiated after the build?
The rules engine has to change, which is why availability formulas and exclusion lists belong in configuration rather than in code. Model each agreement as a record with a guarantee percentage, an exclusion list, a claim window and a damages formula, all with effective dates, so historic quarters still reproduce correctly after the new terms take effect. Expect this work in your annual support budget rather than as a project.
Should we build if the manufacturer still carries availability risk?
Usually no. Under a full service agreement where the manufacturer owns the guarantee, you are paying to solve somebody else's problem, and the portal plus a maintenance system is proportionate. The calculation changes the day you move to self-performed service or an independent service provider, because availability risk transfers to you and you suddenly need evidence rather than a monthly summary.
Can artificial intelligence predict which turbines will fail?
Naming a failure date for a specific bearing is a research project. Ranking your fleet by probability of a major component event in the next ninety days, trained on your own condition monitoring, oil analysis and SCADA history, is achievable and is enough to turn an emergency crane mobilisation into a planned campaign. Classifying years of free text work orders into a failure taxonomy is the other application that reliably pays.
How do we handle ten years of historic SCADA data during a migration?
In two tracks. Live ingestion starts first so the new system is useful immediately, then history backfills in parallel into a time series store with partitioning, continuous aggregates and a considered retention policy. A naive relational table will demonstrate well and become unusable in year two. Ask any developer what happens to query performance at billions of rows before you sign anything.
Is Maximo worth keeping alongside a custom system?
Often yes, particularly if your finance team already reconciles spares and labour cost through it. The sensible split is that Maximo remains the work order and cost system while your build owns the turbine component hierarchy, the fault to work order automation and the production loss ledger, writing to Maximo rather than replacing it. Rebuilding approval chains and spares management rarely earns its cost.
What compliance obligations apply to a wind operations platform?
NERC CIP where assets fall in scope, which drives the boundary between the SCADA network and the business network and constrains how data leaves the control system. Beyond that, audit trail and lineage requirements if the platform feeds lender or grid operator reporting, and immutability for lockout tagout records and torque readings, since those become your evidence in an incident investigation years later.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
What features should the first version of a custom field service app include?
Version one needs the daily loop and nothing else: job creation, a drag-and-drop dispatch board, a technician mobile app that works offline, photo and signature capture, and invoicing that reaches your accounting system. Customer portals, route optimization, inventory, and reporting dashboards belong in phase two. The test for every feature is whether a dispatcher or technician touches it every day; if not, cut it.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What are the biggest mistakes companies make when building custom field service software?
Four mistakes cause most failures: scoping only the happy path so offline work and job reassignment surface later as change orders, leaving QuickBooks sync until the end instead of designing for it, skipping technician input until launch, and having no post-launch support plan. Across 2,000+ Digital Heroes projects, failed field service builds almost always failed on process, not programming. Every one of these is prevented in the scoping phase, which is why discovery matters more than the framework.
What does it cost per year to maintain custom field service software?
Budget 15 to 20 percent of the original build cost per year, so $15,000 to $20,000 on a $100,000 platform. That covers hosting, security patches, integration API changes, a monthly block of small improvements, and the iOS and Android updates Apple and Google ship on their own schedule. Skipping it is not a savings; the technician app needs attention every OS cycle or it eventually stops opening on new phones.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software 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 field service management software 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
Published · Last updated .
