Air Emissions Compliance Software: Build the Calculation Engine or Buy a Platform
The threshold is a Title V permit with more than roughly 30 emission units, continuous monitors in play, and emission calculations living in unit level workbooks.
On this page
The threshold is a Title V permit with more than roughly 30 emission units, continuous monitors in play, and emission calculations living in unit level workbooks. Below that, on a minor source permit with a handful of units and annual reporting, buy nothing and keep a well built workbook with a calendar reminder, because your risk is whether somebody remembers the submission and software does not fix a calendar problem. Above it, the answer for most sites is not a platform at all: keep the environmental suite you already run and build only the calculation and deviation engine, at $65,000 to $130,000 over 12 to 16 weeks.
When is off the shelf genuinely the right call here?
Buy, and be specific about what you are buying. Sphera has real depth in industrial environmental and process safety work and is a credible enterprise choice, particularly where you need obligations, actions and process safety in one place. Intelex is a broad, well built environmental, health and safety platform and it is strongest on incidents, audits, actions and management systems. Cority comes from an occupational health heritage and covers environmental modules competently across a large estate. Envirosuite is genuinely good at a different problem, namely ambient monitoring and dispersion around a site including community facing odour, dust and noise, so if your issue is neighbours rather than permit limits, look at it seriously and do not confuse the two.
The clearest buy case is a minor source permit with a handful of units and annual reporting. The calculation load fits a workbook, the risk profile does not justify engineering, and a platform licence would buy you obligation tracking you can do with a shared calendar. We would say so rather than quote.
The second buy case is corporate breadth. If your actual need is a consistent way to hold obligations, run audits, assign corrective actions and roll findings up across twelve sites, that is what these suites were built for and they do it well. Rebuilding it is a poor use of capital.
What none of them ships with is your permit. That is not a criticism of the vendors, it is the structure of the market, and it is where the build question actually starts.
When does a custom build actually pay off?
Build when your permit conditions cannot be expressed in a configuration surface and are therefore living in spreadsheets. This is the recurring outcome at refineries and power plants: a suite holding obligations, audits and actions, with the emission calculations still in workbooks because that was the only place the permit specific method could be written down.
The specific trigger to watch for is when deviations are discovered. If your semiannual monitoring report is the mechanism by which you learn you were out of compliance in March, the gap between the event and the discovery is your real exposure. Prompt deviation reporting timelines run from when the deviation occurred, not from when you noticed it, so a six week discovery gap turns one problem into three.
The second trigger is calculation variety. A unit with one annual throughput cap is trivial. A unit carrying an hourly limit, a thirty day rolling average and a rolling twelve month cap, each with its own permit specified method and its own exclusion rules for startup, shutdown and malfunction periods, is three engineering problems wearing one label. Thirty limits of that shape is a build. Thirty throughput caps is not.
The third is backward correction. A rolling window has to recompute whenever any input inside it changes, including a historian value corrected four months later and monitoring data invalidated after a failed quality assurance test. Spreadsheets handle the forward calculation fine and the backward correction badly, which is where most sites get caught.
The fourth is a consent decree. Its obligations have their own dates, evidence requirements and reporting, and they carry a higher bar for auditability than permit conditions do.
How do they compare on the things that matter in this industry?
Permit expression. A suite models limits through its configuration surface, so your permit method either fits or it becomes services work and a workbook beside the system. A build holds each limit as a structured record: the unit, the pollutant or parameter, the value and units, the averaging period and how it is computed, the monitoring basis, the applicable exemptions, the citation and the effective date range.
Historian access. This is a project in every implementation we have seen, not a connector you switch on. AVEVA PI, Honeywell PHD, Aspen IP.21 and Wonderware all have supported access paths. The discipline that decides whether the numbers are right is tag mapping: each calculation input naming a specific tag with unit conversion, expected range and defined handling for bad or missing values. A tag renamed during a control system upgrade will otherwise feed a calculation with nothing and produce a reassuringly compliant zero.
Transparency. A defensible evaluation is reproducible: here is the limit version, here is the averaging window, here are the inputs used, here is the arithmetic, here is whether an exemption applied. Configurable engines can produce a number. Producing the derivation an inspector will ask for is a design decision, and it is easier to get in something you own.
Change speed. Permits get modified. The difference between an environmental engineer changing a limit themselves in an afternoon and raising a change request that takes three weeks is the difference between a system that tracks the permit and one that quietly falls behind it.
What does total cost of ownership look like at your scale?
On the buy side, take the platform licence, add the configuration and professional services you pay whenever a permit condition has to be accommodated, and add the workbook maintenance that is happening anyway. That third line is invisible on every invoice and it is usually a named person's job.
On the build side, a first release covering the permit limit register, historian integration and continuous evaluation of your highest risk limits with deviation workflow runs $65,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding the site wide emission inventory, monitor quality assurance scheduling, leak detection and repair, statutory report assembly and greenhouse gas reporting runs $170,000 to $380,000 across 6 to 12 months. A multi site rollup adds $50,000 to $130,000.
In a worked refinery example with 140 emission units and roughly 90 calculable conditions, the register itself was $37,000, historian integration $29,000, the evaluation engine for the highest risk 28 limits $34,000, deviation workflow $22,000 and engineer configuration tooling $16,000. That is $138,000 for a first release, with phase two taking the programme to about $362,000 across eleven months.
The recurring costs are the honest part. Permit renewal and modification work is $15,000 to $60,000 per event and is a scheduled certainty rather than a risk. Historian tag maintenance is $8,000 to $22,000 a year. Hosting and retention of high frequency monitoring data is $6,000 to $18,000. Support and enhancement runs 15 to 20 percent of build. Engineer training is $4,000 to $10,000, because environmental staff turn over and a limit configuration nobody understands is a limit that stops matching the permit.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In this category the hybrid is not a compromise, it is our standing recommendation for any site already standardised on an environmental suite.
The split is clean because the two halves genuinely differ. Keep Sphera, Intelex or Cority for obligations, audits, corrective actions, training records and management system evidence, which they do well and which is common across every one of their customers. Build the calculation and deviation engine, which is specific to your permit and will never be common to anybody. Feed deviations from the engine into the suite as records so action management, assignment and closure stay where your organisation already works.
That is a smaller project with most of the value. It also avoids the failure mode of a replacement programme, which is that you spend a year reproducing audit and action management competently while the calculations you were actually trying to fix wait their turn.
A second hybrid worth naming is scope rather than systems. Build the engine for the twenty or thirty limits that carry real exposure and leave the rest on workbooks for now. Extending afterwards is mostly configuration on the same engine, and twenty identical heaters share one calculation method rather than needing twenty.
The condition on both is deviation ownership. A system that detects deviations nobody has been assigned to close creates a documented record of unaddressed exceedances, which is materially worse than not detecting them. Assign that before go live.
Which should you choose, by operator size and stage?
Minor source permit, a handful of units, annual reporting. Buy nothing bespoke. A well built workbook and a calendar reminder is proportionate. If you want obligation tracking across several small sites, a suite licence is the cheapest route to it.
Title V permit, under about 30 emission units, no continuous monitors. Stay with the suite you have and tighten the workbooks. Document who owns each calculation and make sure two people understand it. The exposure here is key person risk more than calculation risk.
Title V permit, more than 30 units, continuous monitors, calculations in workbooks. This is the crossover and the hybrid is the answer. Build the limit register, historian integration and continuous evaluation for the limits that carry real exposure, feed the suite, and stop there for a year. Choose the first tranche by consequence rather than by ease, because the easy limits are easy precisely because nobody worries about them.
Refinery or power plant under a consent decree, or a multi site estate. Build the full platform, phased. Decree obligations carry their own evidence and reporting bar, and a site in that position generally lands near the top of the published range rather than the middle. Start the historian access conversation in week one, because it is rarely a technical blocker and frequently an organisational one.
The payback across all of these is avoided deviations and the penalty and decree exposure attached to them, not headcount. That is a harder business case to write and a much larger number when it lands.
If you would rather scope this before committing budget, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Flexera's 2025 State of the Cloud Report (survey of 750+ technical and executive leaders) found that 84% of respondents believe managing cloud spend is the top cloud challenge for organizations today, with cloud budgets already exceeding limits by 17%. Source: Flexera (2025) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
- The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
Frequently asked questions
What does it cost to switch off Sphera, Intelex or Cority?
In the recommended shape you do not switch. The engine sits beside the suite and feeds it deviation records, so obligations, actions and audits stay where your organisation already works and there is no migration to fund.
If you did replace outright, the cost is not the data, it is the management system evidence. Audit histories, action closures and training records support external certifications, and reproducing that in a new system is a year of work that solves none of the calculation problems you started with.
What happens if our platform vendor changes its pricing or its modules?
The exposure depends on what the platform is carrying for you. If it holds obligations and actions, a price change is annoying and portable. If it also holds your emission calculations through configuration, a price change or a module restructure reaches into your compliance record.
That asymmetry is a reason to own the calculation layer regardless of price. The engine that produces the numbers behind an annual compliance certification should not sit inside a commercial relationship you may want to exit.
How long does it take to build the calculation engine?
Twelve to 16 weeks for a first release covering the permit limit register, historian integration, continuous evaluation of your highest risk limits and a deviation workflow, in Digital Heroes delivery experience.
Three to six weeks of that is environmental engineering time reading the permit line by line, which is the least glamorous part and usually the most valuable, because it routinely surfaces limits nobody was actively tracking. Start the historian access conversation in week one, since it runs on process control or information technology calendars rather than yours.
Is Sphera enough for a refinery under a consent decree?
For obligations, actions, audits and management system evidence, yes, and keeping it is the sensible choice. Where sites end up is running Sphera for those while the actual emission calculations stay in workbooks, because the permit specific method could not be expressed in the vendor engine.
Under a decree that gap is worse, because decree obligations carry a higher auditability bar and their own dates and evidence requirements. The build worth doing is the calculation and deviation engine feeding Sphera, not a replacement.
Can we keep the suite and build only the deviation detection?
Yes, and it is the shape we recommend most often. The engine holds the limit register, reads the historian, evaluates continuously and raises a deviation record with the timestamp, the inputs used and the operating context. The suite then owns assignment, corrective action and closure.
Insist on configuration tooling inside that engine, roughly $16,000 in our worked example, so an environmental engineer can change a limit in an afternoon after a permit modification rather than raising a three week change request.
Why is historian integration harder than it sounds?
Reading tags is straightforward. What is not is handling bad quality data, gaps during instrument outages, and the substitution rules your permit specifies for missing monitoring data, all of which are unavoidable if the calculated value has to hold up in a report.
Budget around $29,000 at refinery scale plus $8,000 to $22,000 a year in tag maintenance. Instruments are replaced and tags are renamed, and a calculation silently reading a dead tag producing a comfortable zero is the failure mode you least want.
How many limits should the first release cover?
Twenty to thirty, chosen by consequence rather than by ease. Modelling the whole permit at once is the most common reason these projects stall, and your environmental engineers already know which limits keep them awake.
The limits that are easy to model are usually easy because nobody worries about them, so a system covering only those has never told anybody anything they did not know. Extending later is mostly configuration on the same engine.
What is the business case if this does not reduce headcount?
Avoided deviations and the penalty and consent decree exposure attached to them. It is a harder case to write than a labour saving and a much larger number when it lands.
The concrete measure is your discovery gap. Take the last two years and ask how many deviations were found during report preparation rather than when they happened. Prompt reporting timelines run from occurrence, so every week of that gap is exposure you are carrying without knowing it.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
How do I work out whether a custom dashboard will pay for itself?
Add up three numbers: hours of manual reporting it removes each month, license seats it replaces or avoids, and the value of one or two decisions it speeds up, like catching margin slippage a month earlier. Across Digital Heroes projects, internal dashboards typically pay back in 8 to 18 months, and customer-facing dashboards pay back faster when analytics is a paid feature or reduces churn. If the honest math does not clear payback within 2 years, buy an off-the-shelf tool instead.
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 many people does it take to build a custom BI dashboard?
A typical build runs with 3 or 4 people: a data engineer for pipelines and modeling, a full-stack developer for the application and charts, a part-time designer, and a project lead. One strong freelancer can handle a single-source internal dashboard, but in our experience solo builds stall once multiple integrations, permissions, and customer access are added. Team size matters less than having one person explicitly own the data model.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
Should I embed Power BI or Tableau in my SaaS product, or build custom charts?
Embed first if you need analytics inside your product within weeks, but treat it as a bridge rather than the destination. Embedded licensing meters your customer traffic, so your analytics cost grows with your user count, and the look and feel never fully matches your product. In Digital Heroes projects, SaaS teams usually switch to custom charts built in React with a library like ECharts or Recharts once analytics becomes a selling point instead of a checkbox.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
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.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
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 Dhruv.
Director of DevOps & Infrastructure · Delhi · 5 posts on the site
Published · Last updated .
