Choosing between Direct Air Capture (DAC) and Airborne/Atmospheric Carbon Capture on-site systems (often grouped under “AOC” in telecom vendor discussions, such as atmospheric capture units integrated with power and hardware at the edge) is no longer a theoretical exercise. For telecom operators, the decision is driven by deployment constraints, energy availability, permitting timelines, and the full lifecycle cost picture—not just the capture unit’s sticker price. This quick-reference cost analysis is designed to help engineers, procurement leads, and sustainability teams evaluate DAC versus AOC for telecom applications with a practical, comparable framework.
Scope and terminology (so you’re comparing the right things)
In telecom RFPs, “DAC” is typically unambiguous: capture equipment designed to remove CO2 directly from ambient air, typically at fixed sites with engineered airflow and regeneration. “AOC” is more variable in vendor language. Some vendors use it for “atmospheric capture on-site” or “air capture on the edge,” often implying a smaller footprint unit integrated with telecom infrastructure (site power, enclosure, controls) where the capture system is installed near the load.
- DAC (Direct Air Capture): Centralized or fixed-site air capture with engineered contactor/regenerator cycles.
- AOC (Atmospheric/On-site Capture): A capture unit deployed at or near the telecom site, often modular, with tighter integration to site power, HVAC, and monitoring.
- Telecom application context: Macro sites, microcells, data centers, or edge POPs where power, uptime, and space are constrained.
Because “AOC” can mean different architectures, you must request an apples-to-apples cost basis: cost per net ton of CO2 captured, including energy and lifecycle elements, and cost per deployed site, including integration and O&M.
Decision checklist: what to lock before you do cost analysis
Before any numbers, confirm these items. If you don’t, your cost analysis will be unavoidably biased toward the vendor who provided the most complete assumptions.
- Capture basis: Net CO2 captured per year (tCO2/yr) and whether regeneration losses are included.
- Energy intensity: kWh per ton captured, including auxiliary loads (fans, pumps, controls, thermal management).
- Power supply: Delivered electricity vs. renewable procurement assumptions; peak vs. average draw.
- Operational constraints: Minimum/maximum operating temperature and humidity; downtime policy.
- Consumables: Sorbent/media replacement frequency and expected yield degradation.
- CO2 handling: Compression, transport, storage, or utilization requirements; whether CO2 is delivered to a sink.
- Integration scope: Who supplies enclosures, HVAC interfaces, grounding, comms, and safety systems.
- Regulatory responsibilities: Permitting, emissions monitoring, and any local environmental compliance.
Cost analysis framework for telecom deployments
A telecom-grade cost analysis should be structured into repeatable cost buckets that map to procurement and engineering scopes. Use these buckets for both DAC and AOC and normalize results by output.
Cost buckets (use the same structure for both options)
- CAPEX (upfront): Capture hardware, site integration hardware, civil works, enclosures, commissioning.
- Energy (OPEX major driver): Electricity consumption, demand charges, and any thermal energy needs.
- O&M: Labor, scheduled maintenance, spare parts, sensor calibration, software maintenance.
- Consumables: Sorbent/media, reagents (if applicable), filters, and replacement kits.
- CO2 logistics: Compression/purification, transport, storage or utilization fees.
- Compliance and monitoring: Permitting renewals, reporting, emissions checks, audits.
- Reliability and uptime costs: Replacement units, SLA penalties, downtime during outages.
- End-of-life: Decommissioning, waste handling, disposal costs.
Normalization metrics you should require
- Levelized cost per ton: $/tCO2 captured (net) over the assumed life.
- Site-level cost: $/site/year and CAPEX per installed site.
- Power impact: kW per site and annual kWh per site, including auxiliaries.
- Throughput reliability: annual capture expectation adjusted for weather and downtime.
Typical cost structure: DAC vs. AOC at a glance
In most telecom scenarios, the decisive differences are (1) energy handling, (2) integration and site civil work, and (3) reliability under real operating conditions. DAC is often engineered for high capture performance but may require centralized facilities or larger site footprints. AOC is often modular and easier to place near the load, but may have higher relative integration complexity and potentially less favorable throughput per unit hardware.
| Cost Element | DAC (Typical Pattern) | AOC (Typical Pattern) | What to Verify in Vendor Quotes |
|---|---|---|---|
| CAPEX hardware | Higher per “capture train,” often fewer sites | Modular units per site; may increase total installed count | Unit throughput, scalability, and included enclosure/controls |
| Civil works & footprint | Often a dedicated pad/utility scope | Can be smaller but still needs site readiness | Permitting, foundation needs, and mechanical/electrical tie-ins |
| Energy intensity | May be efficient at scale but regeneration can be power/heat heavy | May have higher total kWh/ton due to smaller scale or less optimized thermal integration | kWh/ton, duty cycle, auxiliary loads, seasonal derating |
| O&M labor | Centralized technician support; predictable schedules | Distributed maintenance increases travel and spares management | Service coverage model, response time, spares stocking strategy |
| Consumables | Media replacement may be lower frequency at designed operating points | Replacement frequency may vary by site conditions and duty cycle | Media yield degradation assumptions and replacement intervals |
| CO2 logistics | Centralized capture may simplify aggregation and transport | Distributed capture can complicate collection/transport economics | Who owns compression, bundling, transport, and sink contracting |
| Uptime reliability | Engineered redundancy; easier to operate at designed conditions | More sensitive to site-level constraints and power quality | Guaranteed capture availability and degradation curves |
Energy and power: where cost analysis usually decides the winner
For telecom applications, power is not an abstract input. It’s a measurable operational constraint with a direct impact on cost, capacity planning, and site uptime. Energy costs often dominate OPEX, especially when electricity prices include demand charges or when capture systems increase peak loads.
Energy cost model (what to compute)
- Annual energy cost: (kWh/ton) × (tCO2/yr) × (electricity $/kWh) + demand/peak components.
- Capacity impact: kW draw vs. site power provisioning and backup generator capability.
- Derating: adjust throughput for temperature/humidity and seasonal operating windows.
Energy-related vendor evidence to request
- Measured or validated kWh/ton under representative conditions.
- Demonstrated duty cycle and minimum load requirements.
- Auxiliary loads breakdown: fans, controls, heating/cooling, pumps, sensors.
- Demand charge treatment: whether the system can shift loads to off-peak or modulate safely.
Practical rule: If one vendor cannot provide kWh/ton with a credible test basis and operating envelope, treat their quote as non-comparable and require a revised basis before final cost analysis.
CAPEX and integration: telecom site realities that skew costs
Telecom sites are not blank industrial plots. Space, zoning, power distribution, and safety constraints can multiply integration costs. AOC’s “near-site” concept reduces transport distance but can increase distributed integration CAPEX across many sites.
CAPEX components to itemize in your spreadsheet
- Mechanical: enclosures, mounting, ducting/airflow paths, corrosion protection.
- Electrical: switchgear modifications, breakers, UPS/backup compatibility, grounding/earthing.
- Controls and comms: SCADA/telemetry integration, cybersecurity controls, network backhaul needs.
- Safety: hazard analysis, fire suppression, signage, ventilation requirements.
- Commissioning: acceptance testing, calibration, performance verification, training.
Integration cost skew: when DAC wins and when AOC wins
- DAC tends to win when: you can concentrate capture capacity at fewer, better-prepared sites with stable utilities and centralized maintenance.
- AOC tends to win when: you need distributed capture for specific telecom assets (e.g., data centers with strict local accounting) and can keep integration standardized across sites.
The “winner” often depends less on capture chemistry and more on how many unique sites you must equip and how standardized your installation process can be.
O&M, reliability, and lifecycle: the hidden multipliers
Distributed telecom deployments amplify operational overhead. A cost analysis that only compares unit CAPEX without modeling service logistics will mislead decision-makers.
O&M cost drivers to model
- Maintenance frequency: planned service intervals and mean time between failures (MTBF).
- Consumables cost: media replacement, reagent needs, filter changes, and associated downtime.
- Spare parts strategy: stocking locations, lead times, and replacement kit pricing.
- Service labor: technician hours per visit and average travel costs.
- Performance degradation: capture rate changes over time and the impact on net tCO2/yr.
Reliability and downtime: incorporate capture availability
Instead of assuming nominal throughput, use a capture availability factor:
- Net capture throughput: (rated capture) × (availability) × (seasonal derating) − (losses).
- Availability: 1 − (planned downtime + unplanned downtime) over the evaluation period.
For telecom, downtime can also trigger compliance or reporting gaps. That can convert technical downtime into organizational cost.
CO2 handling and sink economics: don’t let this be an afterthought
Capturing CO2 is only one part. Telecom operators must still address what happens to captured CO2: compression, transport, and storage/utilization. These costs can dominate when capture units are distributed and aggregation is expensive.
CO2 logistics cost model (quick approach)
- Compression/purification cost: $/ton delivered at specified purity.
- Transport cost: distance and frequency based on your aggregation strategy.
- Sink cost: storage or utilization contract $/ton (often indexed).
- Measurement and verification: MRV costs for credible accounting.
Vendor questions you should ask verbatim
- Does the system deliver CO2 as a stream, solid, or concentrated output? What purity/spec is guaranteed?
- Who pays for compression and how is it metered?
- What is the minimum economical batch size for transport?
- How do you support MRV at telecom site granularity?
Worked comparison template (fill in your numbers)
Below is a practical table structure to use in your cost analysis. It’s intentionally telecom-centric: site count, energy, and integration are explicit.
| Line Item | DAC (Option A) | AOC (Option B) | Notes / Inputs Needed |
|---|---|---|---|
| Installed sites (count) | How many telecom assets you will equip | ||
| Capture per site (tCO2/yr) | Rated × availability × derating | ||
| Annual capture (tCO2/yr) | Sites × capture per site | ||
| CAPEX per site ($) | Include enclosure, electrical, comms, commissioning | ||
| Total CAPEX ($) | CAPEX/site × sites | ||
| kWh per ton (kWh/t) | Include auxiliaries | ||
| Annual electricity cost ($/yr) | (kWh/t × tCO2/yr) × $/kWh + demand | ||
| Consumables ($/yr) | Media + filters + reagents; include degradation impact | ||
| O&M labor and service ($/yr) | Travel, technicians, calibration, software support | ||
| CO2 handling + sink ($/yr) | Compression, transport, storage/utilization | ||
| MRV + compliance ($/yr) | Monitoring, reporting, verification, audits | ||
| Total annual cost ($/yr) | Sum of OPEX buckets | ||
| Levelized $/tCO2 (net) | CAPEX amortized + OPEX over life / net tons |
Common cost pitfalls (how projects go wrong)
- Comparing “capture rate” without availability: telecom sites experience outages; systems must be derated accordingly.
- Ignoring demand charges: large intermittent loads can spike costs even if average kWh looks acceptable.
- Underestimating distributed maintenance: travel time and spares logistics scale with site count.
- Leaving CO2 sink costs vague: the cheapest capture option can become the most expensive once transport/storage is included.
- Assuming identical integration scope: “turnkey” claims often exclude electrical upgrades, safety, or comms hardening.
- Omitting end-of-life: disposal and decommissioning can be non-trivial, especially for sorbent/media handling.
Pragmatic guidance: which should telecom teams prefer?
There is no universal winner. The right choice depends on your deployment pattern and constraints. Use this decision logic to guide the first pass of your cost analysis.
Choose DAC when most of these are true
- You can deploy at fewer, more controlled sites (fewer unique integration packages).
- Centralized MRV and maintenance are operationally feasible.
- You have stable power provisioning and can support regeneration/thermal requirements.
- CO2 aggregation for transport/storage is economically efficient.
Choose AOC when most of these are true
- You need capture closer to specific telecom assets for accounting, branding, or regulatory reporting.
- You can standardize installation across many sites to reduce integration variability.
- You have a robust service network and can manage distributed spares effectively.
- Your site power and environmental conditions match the capture system’s operating envelope.
Next steps: run a vendor-neutral cost analysis sprint
To get to a defendable procurement outcome, run a short, structured sprint with clear deliverables. This avoids “spreadsheet theater” and forces consistent assumptions.
- Request standardized data packs from both DAC and AOC vendors (kWh/t, availability, consumables, integration scope, MRV approach, CO2 handling specs).
- Build a normalized model using the cost buckets and table above; enforce a single electricity price and a single sink contract assumption (or scenario set).
- Model two deployment scenarios (pilot and scale) with different site counts and maintenance coverage.
- Stress test assumptions (electricity price +20%, availability −10 points, media replacement frequency +25%).
- Score outcomes on $/tCO2 and operational risk (uptime, integration complexity, compliance burden).
If the cost difference is within your uncertainty range after stress testing, prioritize the option with the higher operational certainty and lower execution risk—because telecom projects fail more often on delivery than on theory.
Quick reference summary
- Energy dominates telecom cost analysis: require kWh/ton with auxiliaries and derating assumptions.
- Integration scope matters: itemize mechanical, electrical, comms, safety, commissioning.
- Distributed O&M scales: AOC can increase travel, spares, and downtime risk across many sites.
- CO2 sink costs can flip the result: include compression/transport/storage/utilization and MRV.
- Normalize by net tons and availability: don’t compare rated throughput.
Use this framework to produce a vendor-neutral, telecom-realistic cost analysis that stands up to procurement scrutiny and engineering execution. When you can defend each input and translate costs into $/tCO2 captured (net) under realistic uptime and integration constraints, the DAC vs. AOC decision becomes a technical procurement outcome—not a sustainability debate.
