Check the power and deployment economics before you take an architecture further.
Compare two candidate architectures in one directional model focused on battery/service interval and deployment economics. MoleculeX connects telemetry-driven network cost, infrastructure, field service and fleet TCO so weak assumptions become visible before deeper RF, regulatory or project-specific engineering validation.
Define the deployment.
Use one currency consistently. Changing the currency label does not convert values or exchange rates.
Price the maintenance burden.
Model two candidate architectures.
Rename the options for your real candidates. Fixed recurring charges, usage-based network charges and infrastructure operating costs are modelled separately so telemetry can affect TCO.
Architecture screening result.
| Model output | Example A | Example B |
|---|---|---|
| Total modelled cost | $221,490 | $303,992 |
| Battery life | 23.6 yr | 7.6 yr |
| Battery target | MEETS | MEETS |
| Hardware + install | $95,167 | $109,808 |
| Infrastructure CAPEX | $2,700 | $0 |
| Fixed recurring | $109,892 | $183,153 |
| Usage-based network | $42 | $42 |
| Infrastructure OPEX | $2,700 | $0 |
| Failure field service | $10,989 | $10,989 |
| Battery service | $0 | $0 |
Don't spend capital until these assumptions are checked.
- Recurring operating cost dominates the model; supplier pricing, data charging and minimum fees are high-leverage assumptions.
- Measure real current consumption on target hardware across connect, transmit, retry and sleep states.
- Validate radio coverage, infrastructure count and supplier-specific billing with a pilot before extrapolating.
Go deeper only when the decision needs stronger evidence.
Pro is for repeatable three-scenario economics, ROI, NPV and sensitivity. The Decision Pack is the finished one-project output when stakeholders need structured analysis, evidence gaps, risks, QA and a validation plan. Paid product prices are in South African rand.
Model methodology · MX-FEAS v1.1
Battery life = usable battery capacity ÷ modelled daily mAh. Daily mAh combines active current during message events with sleep current for the remaining time.
Telemetry = messages/day × average days/month × payload bytes × protocol overhead. Usage-based network cost then feeds directly into each architecture's TCO using its cost/GB input.
TCO includes hardware + installation, infrastructure CAPEX, fixed per-device recurring cost, usage-based network cost, infrastructure OPEX, expected failure field service and modelled battery-service events over the selected horizon.
Model limitations
This is a directional power and deployment-economics screening model. It does not evaluate RF propagation, coverage, throughput, latency, regulatory suitability, safety, environmental robustness, protocol compatibility or full technical feasibility.
It also does not model temperature, battery ageing, self-discharge, regulator efficiency, peak-current limitations, protocol-specific airtime, network retries, carrier minimums, taxes, financing or currency conversion unless represented explicitly in your inputs. Validate material assumptions against measurements, supplier quotes and project-specific evidence.
Need to pressure-test one variable first?
The specialist calculators remain free. Use them for a narrow engineering question, then return to the architecture screening when you need the assumptions connected.