Tailings Storage Facility Monitoring Software: Build vs Buy
Buy if you hold one facility on one logger network. Vista Data Vision over your loggers plus Seequent Central for geotechnical models is genuinely adequate, and the money belongs in more instruments.
On this page
Buy if you hold one facility on one logger network. Vista Data Vision over your loggers plus Seequent Central for geotechnical models is genuinely adequate, and the money belongs in more instruments. Build once you hold more than three facilities, once survey and satellite data arrive from parties who share no platform, and once trigger levels live only in issued documents.
What Vista Data Vision, Worldsensing and Seequent actually do well
The starting recommendation for a single facility operator is to buy, and to spend what you save on instrumentation and a more frequent inspection regime. That is usually a better risk purchase than software.
Worldsensing hardware is genuinely good at getting readings off instruments in difficult places, and the Loadsensing ecosystem has solved a hard problem around wireless nodes, battery life and rugged deployment. Vista Data Vision is a capable way to visualise logger data and raise threshold alarms, and for a straightforward instrument set it does what a geotechnical engineer needs on a Tuesday morning. Seequent Central is a sensible way to manage geotechnical and geological models with your consultants, with version control over the models themselves rather than over a folder of files.
Between them you get plots, alarms, model management and a place for your engineer of record to work. None of that is trivial and none of it is worth rebuilding.
So buy if you operate one facility with a single logger network, a modest instrument count and one consultant. A custom platform at that scale is expensive ceremony, and we tell operators so when they call us with a budget already approved. The honest advice is more piezometers, more frequent inspection and a trigger action response plan your site actually rehearses.
Where they stop: the trigger that nobody evaluates
The monthly monitoring report lands on the 14th. On page 31 there is a plot of a vibrating wire piezometer in the downstream shell, and the phreatic surface has been climbing for eleven days. The reading crossed the amber trigger on the 3rd. Nobody acted, because the data from that logger goes to the consultant's portal, the consultant compiles the report monthly under their scope, and the trigger levels for that instrument sit in a table inside a document issued by a different engineering firm two years ago.
The site was not ignoring the dam. The site had no mechanism to know. That is the standard failure in this category and it is not a sensor problem.
Two structural gaps produce it. First, a facility is monitored by four or five parties on four or five schedules: an automated logger network reporting hourly, a survey contractor picking up prisms weekly, a drone survey monthly, manual standpipe dips read by a technician, and satellite radar displacement products arriving as a monthly deliverable. Each party has a portal. None holds the trigger levels and none owns the response. Second, the same instrument carries three identities, one from the site, one from the installing contractor and one from the logger channel. If those are not reconciled to a single instrument record with an installation history, every trend is quietly wrong the day a node is replaced.
There is a third gap nobody sells against. A dam safety system must alarm on missing data, not only on exceedances, because the most dangerous state is a sensor that stopped reporting during the wet season and nobody noticed. Set an expected reporting interval per instrument and raise a fault when it is missed. That single feature catches more real risk than any analytics screen.
The arithmetic: per instrument channel fees against a build
Monitoring platforms are priced per data channel per month, per site, or as a hardware bundle with the software included. Consultant portals are usually inside a monitoring services retainer, which means you are paying for them without seeing a line item. Ask for that line item, because you cannot compare anything until you have it.
Run it against your own portfolio. Suppose you hold 18 facilities with 1,400 instrument channels between them, and platform and portal costs across sites and consultants come to $6 per channel per month. That is roughly $100,000 a year, or about $530,000 across five years, and it does not include the survey contractor's reporting or the person who assembles the group pack. Against that, a monitoring and trigger response layer at $200,000, plus $40,000 of migration, plus 18 percent a year from month thirteen, lands near $460,000 over five years and replaces the pack assembly entirely.
The crossover sits near three facilities, or roughly 800 instrument channels across more than one data owner. Below that, buy. Between three and six facilities the decision turns on how many separate parties feed you data rather than on the channel count. Above six facilities the group reporting burden alone justifies it, because the annual conformance position currently costs a graduate two weeks and a senior engineer's patience every time somebody asks.
What a custom monitoring platform actually costs
Across more than 2,000 delivered projects, Digital Heroes prices this category as follows. A monitoring and trigger response layer, meaning multi source ingestion with instrument identity and installation history, versioned trigger levels, rate and correlation based evaluation, missing data alarms, and an acknowledgement and escalation workflow with an append only audit trail, runs $90,000 to $200,000 and ships in 14 to 20 weeks. A full platform adding water balance and deposition tracking, survey derived freeboard, construction quality records, document and review registers, and group portfolio and disclosure reporting runs $250,000 to $600,000 over 9 to 15 months.
Two lines get missed. Data migration runs 10 to 25 percent of build cost, and it sits at the top of that band in tailings because historical readings arrive from several contractors in several formats and instrument identity has to be reconciled backwards through every logger swap. Year two onward runs 15 to 20 percent of build cost annually for support, new facilities and trigger level revisions after each design review.
What drives cost up: the number of distinct consultants and contractors feeding data, because each relationship is a data contract to negotiate as much as an integration to build. Survey and geospatial processing, since datum conversion and deriving freeboard from point clouds is specialist work. Multi jurisdiction reporting. Offline field inspection capture. And taxonomy normalisation across facilities, which is a workshop with your engineering partners rather than a coding task.
What holds it down is starting with your highest consequence facility and rolling the same model outward.
The four situations where building wins
Regulatory and governance fit. The Global Industry Standard on Tailings Management, published in August 2020 by ICMM together with UNEP and PRI, put named accountability on an accountable executive at corporate level and a responsible tailings facility engineer at each facility, alongside the engineer of record. Whether or not you are an ICMM member, lenders, insurers and major customers increasingly ask for the same evidence, and dam safety guidance from bodies such as the Canadian Dam Association and ANCOLD carries its own review cadence. Confirm your obligations with your engineer of record and counsel rather than with any software vendor, including us. What software must do is unchanged: produce the conformance position as a report rather than a project.
Scale economics. Past three facilities, and certainly past six, portfolio assembly cost exceeds platform cost.
A workflow that is your competitive advantage. Your trigger action response process is the thing insurers and review boards actually examine. Alarm raised, acknowledged within the specified period, inspection completed with photographs, engineer of record consulted where the plan requires it, condition closed with a reason, all append only so nothing is quietly edited later.
Integration sprawl across three or more parties. Logger network, survey contractor, satellite radar provider, laboratory, drone survey. Five owners, five schedules, and the trigger levels in a document none of them holds.
How to decide in a week, using one past exceedance
Pick a trigger exceedance from the last 18 months, ideally one that was managed well. Then spend five short sessions on it.
Session one: reconstruct the timeline. When was the reading taken, when did it arrive, when did a human see it, when was it acknowledged and by whom. Session two: produce the trigger level that applied on that date, and the document that authorised it, without asking a consultant. Session three: list every instrument in that facility that stopped reporting for more than 48 hours in the same period, and check whether anyone noticed. Session four: ask for the current conformance status of your three highest consequence facilities and time how long it takes to arrive. Session five: price those hours and compare with the bands above.
If the timeline took more than an afternoon to rebuild, and if session three found silent instruments, the conditions are met. If a single system answered all of it, stay on the licence and buy more instruments.
When you do cross the line, buy a paid discovery phase before any build. Digital Heroes writes a signed product requirements document covering the instrument model, installation history, trigger level versioning, the response workflow and acceptance criteria, and you keep it whichever firm builds. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, and the delivery record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm if you want geotechnical modelling software, or an opinion on dam safety. Those belong to your engineer of 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.
- Retailers improving Core Web Vitals saw measurable gains: Vodafone improved LCP by 31% for 8% more sales, Lazada saw a 16.9% mobile conversion increase, and Cdiscount saw a 6% Black Friday revenue uplift. Source: web.dev (Google Chrome team) (2021) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Retailers connecting point-of-sale and loyalty data in an omnichannel strategy reported up to 15% lower cost per purchase and nearly 20% higher incremental store revenue. Source: Deloitte (2024) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
Frequently asked questions
How much does tailings monitoring software cost per instrument?
Platforms are commonly priced per data channel per month, per site, or bundled with the hardware. Consultant portals usually sit inside a monitoring services retainer, so you pay for them without a visible line item. Ask each supplier to separate the software cost from the services cost, then work out what your figure becomes if you add a facility or double your instrument count.
How long does a custom tailings monitoring platform take to build?
Fourteen to 20 weeks for a monitoring and trigger response layer with multi source ingestion, instrument identity, versioned trigger levels, missing data alarms and an acknowledgement workflow. Water balance, deposition, survey derived freeboard, construction records and group reporting add nine to fifteen months. Onboarding all facilities at once is the usual cause of delay, because the first six months disappear into data mapping meetings.
Who owns the monitoring data and the code if we commission a build?
You should own the repository, the cloud accounts and every reading, agreed in writing before kickoff. At Digital Heroes the code is the client's from the first commit. For a facility whose monitoring record may need to be produced decades from now, and possibly long after closure, portability is part of the risk management case rather than a commercial preference.
What happens if an instrument stops reporting and nobody notices?
That is the scenario to design against, because a silent sensor during a wet season is more dangerous than a reading above amber. Set an expected reporting interval per instrument and raise a fault when it is missed, with the same escalation path as an exceedance. Systems that alarm only on threshold breaches are quiet in precisely the situation that should worry you most.
Can we keep our consultant's portal and still build a group layer?
Yes, and it is often the right sequence. The group layer ingests from the consultant portal, the survey contractor and the satellite radar provider, holds the trigger levels and owns the response workflow, while the consultant keeps doing the engineering interpretation they are contracted for. What changes is that the trigger evaluation and the audit trail move to you, which is where accountability already sits.
Should a single facility operator build anything at all?
Almost never. One facility on one logger network with a straightforward instrument set is well served by a visualisation product plus a rehearsed trigger action response plan. The money is better spent on additional instrumentation and inspection frequency. Revisit the question when a second facility arrives, or when a survey contractor and a satellite provider start feeding data that your logger platform cannot hold.
What is the difference between a monitoring platform and a data historian?
A historian stores time series and serves it back quickly. A monitoring platform for tailings has to reconcile instrument identity across reinstallations and logger swaps, evaluate versioned trigger levels including rate of change and correlated readings, alarm on absence, and carry a time bound response workflow with sign off. The second is a workflow product with a monitoring front end, which is the part most vendors underbuild.
Can trigger levels be kept in sync with the engineering documents?
They can, and it is the point of building. Hold trigger levels as versioned dated data attached to each instrument, with the issuing document and the engineer who authorised the change recorded. A reading from March is then evaluated against March levels, and a reviewer can see exactly why. Levels held only inside an issued document will drift out of alignment with whatever the system evaluates.
What happens to our conformance reporting during a build?
It continues exactly as it does now, which is the reason to start with one facility rather than the whole portfolio. Prove the ingestion, trigger evaluation and response loop on your highest consequence facility, run it in parallel with the existing monthly reporting for a quarter, then extend. Nothing about the governance position should depend on software that has not yet been proven on site.
Is it worth building just for the portfolio view?
For a group with more than six facilities, frequently yes, and it is the argument that gets budget approved. An accountable executive personally accountable for a position currently assembled by hand once a year is carrying a real risk. The harder work is not the dashboard, it is normalising taxonomy across facilities whose consultants each classify and name things differently.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
Who can build a custom software system?
Digital Heroes builds custom 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 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
More from Reyansh.
iOS Lead · Delhi · 1 post on the site
Published · Last updated .
