Solar Farm O&M Software: Custom Build vs Off-the-Shelf Monitoring
Buy, and keep buying the portals. AlsoEnergy PowerTrack, Power Factors and the OEM dashboards do device monitoring better than a build will, and under roughly 60 MW on one inverter maker with one contract shape they are the whole answer.
On this page
Buy, and keep buying the portals. AlsoEnergy PowerTrack, Power Factors and the OEM dashboards do device monitoring better than a build will, and under roughly 60 MW on one inverter maker with one contract shape they are the whole answer. Build only the layer above them, and only once you carry availability guarantees with liquidated damages across three or more monitoring portals.
What AlsoEnergy, Power Factors and the OEM portals actually do well
The advice most operators need is to buy, so take it first. If you run under about 60 MW alternating current on a single inverter manufacturer, with one contract structure and no availability guarantee carrying liquidated damages, PowerTrack plus a cheap computerised maintenance management system costs less per year than one performance engineer and it will do the job. Building at that size is vanity, and we have talked operators out of it.
Give the products their due, because the parts they solve are genuinely hard. Protocol work is unglamorous and endless: Modbus TCP register maps that differ per inverter model, DNP3 to the substation remote terminal unit, SunSpec where a manufacturer implemented it properly, OPC-UA where the balance of plant controller speaks it. AlsoEnergy, Power Factors and Huawei FusionSolar have all done that work across a long device list and keep doing it as firmware moves. They handle data acquisition system commissioning, weather station ingest, and performance ratio calculation aligned to the measurement classes in IEC 61724-1. Several OEM warranties oblige you to keep the manufacturer's portal running at all, which settles the question before it is asked.
On the work order side, UpKeep, Fiix and Limble schedule preventive maintenance competently and cost very little. Raptor Maps handles aerial thermography and the module level defect catalogue that follows it better than anything you would write.
So the honest position is that almost nobody should replace the data acquisition layer. The single most expensive mistake we watch solar operators make is deciding to rebuild it, which means owning protocol drivers, device commissioning and an OEM warranty argument for no commercial return.
Where they stop: the availability definition written in your agreement
Here is the workflow no product models, because it cannot. Your O&M agreement and your power purchase agreement each define availability, and those definitions are negotiated rather than standard. Is it time based per inverter or energy based and weather adjusted at the revenue meter. Are curtailment hours excluded, and capped at how many. Does a grid outage upstream of the point of interconnection count against you. Does a forty percent inverter derate count as available. Is the measurement interval one minute or fifteen, which on its own can move the figure by half a percentage point.
PowerTrack computes availability its way. Your contract defines it another way. With fourteen assets you probably carry nine different definitions, and no portal on the market lets you encode nine of them side by side with evidence attached.
The second thing that stops them is the alarm flood, and it is a money problem disguised as a user interface problem. At dawn the data acquisition system reconnects and every inverter at every site logs communication restored while every site logs irradiance below threshold. Three hundred alarms in four minutes. Buried inside is one inverter that tripped on a direct current ground fault at two in the morning, and nobody sees it until a technician happens to be on site for vegetation control. The portals alarm on device state because that is what they know. They do not know your contract rate, so they cannot tell you that a tracker controller fault costs a fraction of what a dark inverter block costs. Ranking by dollars per day rather than by timestamp requires expected energy from plane of array irradiance and cell temperature against your PVsyst model, priced at the contract rate, which is your data joined to your commercial terms.
Third, the asset register at serial level with warranty terms. That is your commercial data, not the manufacturer's, so it lives in a spreadsheet last accurate at commercial operation date.
The arithmetic: per-megawatt monitoring fees against the cost to build
Monitoring is usually priced per megawatt per year with a per site minimum, and the maintenance tool is priced per user per month. Take both invoices, add the performance engineer's loaded salary share, and divide by megawatts under management. That is your true unit cost and it will be higher than either line.
A worked example with numbers you should replace. Say monitoring plus the maintenance tool plus one analyst's time comes to $290 per megawatt per year across 180 MW, so about $52,000 annually, and say the layer you would build lands at $180,000 with $32,000 a year to keep. On subscription cost alone the crossover never arrives, and any vendor telling you it does is selling. The build does not pay for itself out of licence savings in this category, and pretending otherwise would insult your finance director.
It pays for itself out of two other lines. First, avoided truck rolls, which you can price directly from your own dispatch records. Second, and much larger, availability disputes. A single quarter reported at 96.8 percent against a 98 percent guarantee turns into a liquidated damages line that can exceed the entire build. The crossover that matters is therefore contractual, and it sits at roughly 120 MW across three or more monitoring portals, because that is where definitional disputes stop being annual and start being quarterly.
What a custom O&M platform actually costs to build and keep
From Digital Heroes delivery experience, a focused first release covering alarm normalisation across your portals into one fault taxonomy, a dollar ranked event queue, work orders and an offline capable field app runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding the contract availability engine, the serial level asset and warranty register, dispatch optimisation and counterparty reporting runs $150,000 to $400,000 phased over 6 to 12 months.
Historical data migration takes 10 to 25 percent of the build and it is its own workstream. Backfill through the same ingest path live data uses so history and live rows share one schema and one fault taxonomy. Expect gaps, out of order backfills from a cell modem that dropped for six hours, and at least one OEM register map change buried in the record. Include a reconciliation pass against the revenue meter rather than treating it as a copy. For twenty to thirty sites at one minute intervals, plan two to four weeks.
Year two runs 15 to 20 percent annually, and here it is real work rather than a support retainer. Firmware updates change register maps silently and will corrupt weeks of data if nobody watches. New acquisitions arrive with new portals. Contract templates get renegotiated. Time series storage also needs a retention and downsampling policy designed on day one, because thirty sites at a few thousand tags each on one minute intervals runs to tens of billions of rows a year.
The four situations where building wins
- Regulatory fit. Any asset registered with NERC changes hosting region, access control, audit logging and change management for the entire system, and retrofitting those into a platform built without them costs more than building them in. Interconnection obligations under IEEE 1547 and ride-through settings also need to be recorded against equipment rather than remembered.
- Scale economics. Not licence savings, which do not materialise, but dispute exposure. Once liquidated damages under one guarantee could exceed the build, the arithmetic is settled by risk rather than by subscription.
- A workflow that is your competitive advantage. If you sell O&M services to third party owners and your pitch is cost per megawatt, the software is the product. A classifier trained on your own closed ticket history that predicts self clear, remote reset or truck required is the highest return model we build for operators, and it works because it learns your fleet rather than a generic one.
- Integration sprawl across three or more systems. PowerTrack for the older assets, FusionSolar for the 2023 builds because the EPC bought those inverters, a legacy portal from an acquired asset, plus UpKeep, plus the availability workbook one person maintains. When onboarding an acquisition means adding a portal rather than adding sites, the sprawl is the cost.
Digital Heroes is the wrong firm if you want us to replace your data acquisition system. We will decline that scope. Keep the portals for device monitoring and warranty obligations, and let us build above them.
How to decide in a week: recompute one quarter two ways
Take last quarter and one asset that carries a guarantee. Have your performance engineer compute availability twice: once exactly as the O&M agreement defines it, with the measurement interval, derate threshold and exclusion rules the contract names, and once as your portal reports it. Then ask for the evidence behind every excluded minute, meaning the SCADA tag, the timestamp, the switching order and the operator note.
Two things come out of five days of that. You learn the size of the gap between the two figures, which is your exposure expressed in real numbers rather than anxiety. And you learn how long evidence assembly takes, which is the work the build removes. If the gap is under a tenth of a percentage point and evidence took an afternoon, you do not need this and we would rather you spent the money on technicians.
Then buy a paid discovery phase, not a build. At Digital Heroes that means a signed product requirements document before any code, covering the tag model, the fault taxonomy, the availability profile schema for each agreement, the retention policy and acceptance criteria. Hand a shortlisted firm the actual availability clause from one agreement and ask them to model it. If the answer contains the words availability percentage field, end the conversation. You keep the specification either way.
We operate India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. Over 2,000 projects, more than fifty specialists, a named team you meet before signing, and our own products, ShopScore, HeroCheckout and Section Vault, running on our own revenue. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- ServiceTitan's KPI guide cites an average first-time fix rate near 80% (90% ideal) and describes strong technician-utilization rates as falling in the 60-80% band, with average travel time typically 30-60 minutes depending on service-area size. Source: ServiceTitan (2026) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
How much does custom solar O&M software cost for a mid-sized fleet?
A focused first release with alarm normalisation across portals, a dollar ranked event queue, work orders and an offline field app runs $60,000 to $130,000 in Digital Heroes delivery experience. A full platform adding the contract availability engine, warranty register, dispatch and counterparty reporting runs $150,000 to $400,000. The main drivers are how many distinct monitoring portals and protocols you integrate and how many contract definitions you carry.
How long does a first release take to ship?
Twelve to sixteen weeks, with a full platform phased over six to twelve months. The single biggest schedule variable is data source integration, because an AlsoEnergy pull, a FusionSolar pull and a raw Modbus poll over a cellular modem are three unrelated engineering efforts. Budget real weeks per source rather than assuming they collapse into one connector, and sequence the noisiest portal first.
Who owns the code and the historian data if an agency builds it?
You should own the repository, the cloud accounts, the data and the deployment pipeline outright, with no runtime dependency on the developer's platform. At Digital Heroes the client owns the code from the first commit, assigned through our India LLP, US LLC or UK LTD entity. Any firm hosting your production system in their own tenant is creating a commercial hostage situation.
What happens if an inverter maker changes its register map in firmware?
Without a guard it silently corrupts data, and you find out weeks later when a performance ratio looks wrong. The system should validate incoming values against expected ranges and units per tag, quarantine a device whose readings shift shape, and alert rather than ingest. Ask any developer about this specifically before signing, because it is the failure that costs the most to unwind.
Can we keep PowerTrack and FusionSolar and still build our own layer?
Yes, and it is what we recommend. Keep the portals for device level monitoring and any warranty obligation that requires them, and build one normalised time series store, one fault taxonomy, one dollar ranked queue and one availability engine on top. Replacing the data acquisition system outright means owning protocol drivers and OEM warranty arguments for no commercial return.
What are the alternatives to a full custom platform for a growing operator?
Power Factors Drive and QOS Energy both aggregate across portals and are worth pricing before any build, particularly if your contract definitions are close to standard. A disciplined data warehouse fed by portal exports, with the availability calculation in version controlled queries, covers a surprising amount for a fraction of the cost. It fails when field capture and dispatch enter the picture.
Should we build if we are acquiring assets every year?
Acquisitions are the strongest push toward building, because each one usually arrives with its own portal, its own contract definitions and an asset register that was last accurate at commercial operation date. Time one acquisition through your current process and count the days to a single fleet view. If that is measured in weeks rather than days, the case is already made.
What is the difference between performance ratio and availability?
Performance ratio measures how much energy the plant produced against what the irradiance and temperature conditions should have produced, so it captures soiling, degradation and derates. Availability measures whether equipment was capable of producing, usually under a contractual definition with exclusions. A plant can be fully available and still miss its performance ratio target, and confusing the two is how disputes start.
Can software genuinely reduce truck rolls?
Yes, when the model is trained on your own closed ticket history rather than a generic one. A classifier predicting whether a fault will self clear, needs a remote reset or needs a technician learns your specific inverter mix and resolution patterns. Price the saving from your own dispatch records before funding it, because the honest number varies enormously between a compact fleet and a scattered one.
Does NERC registration change how we host the system?
Yes, and it should be decided before architecture rather than during it. If any asset in the fleet is a registered generator, hosting region, access control, audit logging and change management become requirements for the whole platform rather than implementation details. Retrofitting role separation and audit logging into a system built without them typically costs more than including them from the start.
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.
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.
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.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
How big a team does it take to build field service management software?
The standard Digital Heroes team for a field service build is five to six people: a project lead, a designer, two or three developers split across the mobile app and backend, and a QA tester who works on real devices in real signal conditions. Bigger is not better; experience with offline sync is. The riskier pattern is the opposite, a single developer quoting the entire system alone.
Should I hire a freelancer or an agency to build my field service software?
An agency in almost every case, because a field service build spans a mobile app, a dispatch web console, a backend, offline sync, and accounting integrations, which is four or five specialties one person rarely covers. A freelancer is the right choice for a single integration or a well-scoped add-on under $15,000. The solo-built field service systems Digital Heroes inherits fail most often at handover, when the freelancer has moved on and nobody can safely modify the sync engine.
How long does it take to build a custom field service app with scheduling, dispatch, and a technician mobile app?
Plan on 12 to 16 weeks for a working first release covering scheduling, dispatch, and a technician mobile app, and 5 to 7 months for a full platform with offline mode and accounting sync. Across 2,000+ Digital Heroes projects, field service timelines slip in two predictable places: underscoped offline behavior and integration testing against QuickBooks or the payment processor. Both belong in week one of planning, not month four.
What should I have ready before I contact a development agency about field service software?
Bring your current workflow, not a feature list: how a job moves from first call to paid invoice today, where it breaks, what tool you use now with its monthly bill, and the workaround spreadsheets your team maintains. Add your integration list (accounting system, payment processor, phone system) and an honest budget range. A good agency can scope accurately from that in one or two calls, while a vague request for an app like ServiceTitan costs you weeks of discovery.
We're outgrowing Jobber. Should we move up to ServiceTitan or build our own?
Move to ServiceTitan if the problem is missing features on a standard residential trades workflow, because migrating between products is far cheaper than building. Build custom when the problem is fit: multi-day commercial jobs, subcontractor crews, or pricing rules that neither Jobber's Grow plan (about $199 per month billed annually, up to 15 users) nor ServiceTitan models cleanly. In Digital Heroes scoping calls, about half the teams asking this question turn out to need an integration or add-on rather than a new platform, so name the exact workflow gap before committing either way.
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 .
