top of page
Tactien Group aviation and UAS consulting logo

THE TACTIEN GROUP

AVIATION • UAS • CUAS • ADVISORY

The Silo Tax: What Infrastructure Companies Pay to when Autonomous Tech is not Cross Utilized

  • 3 days ago
  • 3 min read
Aerial view of a fixed-wing VTOL inspection drone banking over an oil refinery where a pipeline runs to the horizon, with eight labeled callouts marking the departments that share the aircraft: Asset Integrity, Refinery Operations, Operations and Maintenance, Capital Projects, Environmental, Real Estate, Pipeline Maintenance, and Corporate Safety and Security.
One aircraft, eight budgets. That's the difference between a tool that looks too expensive and one that pays for itself.

Around 2011, when commercial UAS were new to energy operations, the pitch was simple: this technology is cheaper. Buy the aircraft, retire the manned aircraft or the rope-access crew, and watch the savings accrue. Plenty of early programs were built on that promise, and plenty stalled when the spreadsheet didn’t cooperate. On a direct, machine-for-machine comparison, a capable/scaled sUAS program rarely came out cheaper than the method it was meant to replace.


The industry learned to measure differently, and the lesson cost real money and real credibility along the way. The same correction is happening now with ground-based robotics in surface maintenance. The sector would do well to skip the expensive part this time.



CAPEX is the wrong yardstick


The framing is where it goes wrong. Put a coating robot next to a crew of painters, compare purchase price to wages, and the robot looks expensive. It is expensive, on that line item. But that line item describes almost none of what the asset costs an operator over its working life.


Load in the rest. Direct labor hours. Material waste, where spraying a coating can lose more than half the product to overspray while a rolled application does not. The hazardous hours removed when nobody has to rope down the side of a tank or work at height on a corroded structure. The downtime on an asset that sits out of service due to staffing issues, the crew can’t be scheduled, or the permits to put people where the work is won’t come through. Add those up and the comparison flips. The robot is the more expensive tool to buy, yes, but the cheaper method to execute at scale.


That distinction changes what you are deploying. Not a substitute for a worker, but a reduction in fully burdened operating cost, and that reduction only appears if you measure across the whole operation instead of one purchase order or department’s ROI.


The tax nobody invoices


This is where most infrastructure companies leave ROI on the table. The economics work. The technology works. The org chart does not support the tech model.


Picture the asset that justifies itself three times over and never gets bought, because no single department can carry the cost alone. Inspection has a budget. Maintenance has a budget. Engineering has a budget. The platform that would serve all three gets measured against one of them, fails that narrow test, and dies in committee. Or one group buys it, uses it for a single task, and parks it the rest of the year while the department down the hall re-buys something nearly identical next quarter.


That is the silo tax: the premium an organization pays when capable, multi-use equipment get trapped inside a single/few cost centers. Nobody writes it on an invoice. It is still real, and it usually runs larger than the price of the asset everyone was arguing about.


A tracked-and-suction robot climbing the steel hull of a ship in dry dock to strip and coat the surface, with six labeled callouts marking the cost categories it reduces: Hazardous Labor Hours, Employee Overhead, Workforce Training, Schedule Shifts, Staffing Issues, and Indirect Cost.
The robot's price is one line item. The costs it removes are spread across six budgets that rarely get counted together.

One machine, three budgets


Look at what a single inspection/repair robot achieves over one deployment. It climbs the tank and captures reality data, the kind that builds a digital twin. That dataset serves inspection. It feeds predictive maintenance scheduling. It tells the engineering team how the structure is aging. Then the same platform comes back and does the physical work, grinding and coating the surface it just mapped. One asset, one trip, feeding inspection, maintenance, and engineering, all of it flowing into the same asset lifecycle management system.


Charge that robot to one department for one job and it is an expensive tool that does a single job. Spread it across every department that touches the asset, align the depreciation schedule to the multi-use reality rather than a single-use fiction, and let more than one team pull from the data it produces. The fully burdened number drops hard. Same technology, completely different economics. The only variable that changed was who is allowed to claim it.


Ask where the budgets sit


Before approving any robotics or airborne platforms, the first question is not whether the technology is ready. It mostly is. The question is where the budgets sit and how much the asset gets cross-utilized across them. If one cost center carries the whole expense and one-use case must justify it, that investment will struggle to pay off, and the post-mortem will blame the technology for being too expensive when the technology was never the problem.


Get the model right and the math follows. Shared assets across departments. Depreciation that tracks actual use across cost centers. Data more than one team can pull from. None of that requires a better robot. It requires an operator willing to stop paying the silo tax.




Learn more about our work in UAS for utilities: www.tactiengroup.com/uas
















bottom of page