Tx-Rails — Combined IIoT + Smart Contracts Pricing Sheet
The auditable underlay for organisations whose operational systems span more than one of our nine vertical sheets — or whose use case combines continuous cryptographic IIoT capture with self-executing multi-party smart contracts. Cryptographic continuous audit of telemetry + multi-party contract execution + cross-counterparty attestation, sitting underneath your existing PLC / SCADA / DCS / MES / historian / batch-record / OPC-UA / sensor-fleet / ERP / contract-management / treasury systems. We don’t replace any of them — we bind to them via a published integration mode and produce tamper-evident, jurisdiction-independent records of everything they emit, plus contract execution that fires automatically when IIoT-attested conditions are met.
This sheet is horizontal — applicable to customers whose deployment crosses multiple of our vertical-specific sheets (aviation, manufacturing, mining, transport, energy, supermarket, housing × {UK / AU}, health, local-government). For single-vertical engagements, the per-vertical sheets are calibrated more tightly; use this one when the deal spans verticals, when smart-contracts execution is the lead value driver rather than pure audit, or when you’re scoping a platform deployment that anchors multiple future use cases.
What you get
Three integrated capabilities, one platform:
- Continuous cryptographic IIoT audit infrastructure (the IIoT half — see
iiot-aviation.md,iiot-manufacturing.md,iiot-health-medical.md,iiot-housing.md,iiot-defence.md,iiot-asset-management.md)
Every sensor reading, every PLC tag change, every state transition, every calibration event, every firmware update, every batch-record entry committed to a Byzantine-fault-tolerant ledger and Merkle-anchored to the Hedera public DLT. Raw 1 Hz / 100 Hz / 1000 Hz telemetry stays in your historian where it belongs — we capture the audit-significant events that auditors, regulators, customers, and investigators want to verify. - Self-executing multi-party smart contracts with IIoT-triggered conditions (the Smart Contracts half — see
smart-contracts-manufacturing.md,smart-contracts-aviation-manufacturing.md,smart-contracts-health-medical.md,smart-contracts-housing.md,smart-contracts-defence.md,smart-contracts-asset-management.md)
Multi-party agreements (between OEM + supplier + customer + insurer + regulator + financier) running as on-chain logic, with conditional escrow, IIoT-triggered condition resolution, automated payment release on attested outcomes — and full audit of which rule fired, which event triggered it, and who authorised the underlying agreement. Smart-contract templates available for: Equipment-as-a-Service (pay-per-runtime), milestone-payment release, Power-by-the-Hour leasing, outcomes-based payer contracts, recall-execution co-ordination, AD-compliance retrofit, supplier-quality-event payment gating, cyber-supply-chain firmware promotion, Scope-3 emissions evidence-flow, multi-party recall + insurer coordination. - Regulator, customer, financier & insurer-grade evidence pipeline
Live data access for every relevant regulator across the verticals you operate in; customer-audit-grade evidence packs for tier-up audit programmes; financier-grade evidence for green-finance + sustainability-linked-loan compliance; insurer-grade telemetry for product-liability + business-interruption + recall + cyber-supply-chain underwriting. Cross-vertical: one platform, one evidence trail, multiple regulator interfaces.
What we sell — and what we don’t
What we don’t sell at any price: full transaction-front-end replacement. We don’t build your MES, your SCADA HMI, your ERP, your customer portal, your contract-management system, your treasury platform, your supplier portal. Your operational and customer-facing screens stay put. If you need a new screen, your engineering team builds it against our published SDK with our reference connectors.
What we do sell falls into two groups:
A. Operator utilities (bundled — Items 2 + 4 in the pricing table)
- Evidence-retrieval portal — your compliance + treasury + risk team pulls cryptographic proofs in response to any regulator, customer-auditor, financier, insurer, accident-investigator, or coronial-inquiry question. Generates evidence packs in formats acceptable across the verticals you operate in.
- Smart-contract dashboard — live view of every active multi-party contract, their attached IIoT-resolution conditions, escrow balances, pending counterparty signatures, automated execution history. Real-time view of “what’s about to fire next”.
- Trust-management UI — operator-side controls for your enterprise PKI: certificate issuance for plant managers / quality engineers / treasury officers / contract counterparties / regulator inspectors / customer audit reps, revocation, partner-org onboarding across all the federations you operate, kill-switch.
B. Counterparty / supply-network smart-contract participation UI (optional — Item 5 in the pricing table)
Thin signature surface for every external counterparty that participates in your multi-party smart contracts — tier-2/3 suppliers, customers signing-off on outcome attestations, financiers releasing escrow, insurer surveyors triggering claim settlements, regulators co-signing compliance retrofits, accreditation surveyors signing-off on outcome verification. This is explicitly in scope for us to develop, distinct from the “no contract-management platform replacement” line above.
What it does:
– DID / certificate-based authentication (multi-vertical credential acceptance)
– Per-tenant queue of pending smart-contract signatures and outcome attestations
– Sign + submit with cryptographic proof landing in the BFT mesh and (where conditions are met) firing the contract’s automated release
– Multi-tenant via entnum — each counterparty sees only their own queue across whichever federations they participate in
What it explicitly is NOT:
– A contract-lifecycle-management replacement (ContractWorks, Icertis, Ironclad stay put)
– A counterparty CRM
– A treasury / escrow / payments platform replacement (the contract triggers payment release; your treasury system actually moves the money)
When you’d buy this: complex multi-party multi-vertical contracts where M-of-N cryptographic co-signature is structurally required (Power-by-the-Hour leasing spanning manufacturing + aviation; multi-tier recall coordination spanning manufacturing + insurer + regulator; outcomes-based payer contracts spanning health + payer + reinsurer).
Pricing — five line items, four budget homes (Item 5 optional)
| # | Item | Type | Indicative price (AUD) |
|---|---|---|---|
| 1 | One-off integration & onboarding — integration-mode selection, wiring against your IIoT data sources (PLC / SCADA / DCS / MES / historian / OPC-UA / batch-record) + your contract-counterparty systems (ERP / treasury / contract repository), certificate-authority setup, smart-contract template selection, UAT, launch | One-off CapEx — capitalisable over 3–5 years | A$180,000 – A$400,000 |
| 2 | One-off operator-UI + smart-contract configuration — evidence-retrieval portal skinned to your brand; smart-contract dashboard customised; regulator + customer-audit + financier export templates calibrated for the verticals you operate in; SSO with your IdP; smart-contract templates instantiated for your specific use cases | One-off CapEx — capitalisable over 3–5 years | A$80,000 – A$180,000 |
| 3 | Annual support & maintenance (security patches, OS/library upgrades, 24×7 help desk for IIoT-safety-critical + contract-execution-time-sensitive operations, 99.95% uptime SLA, integration-mode adjustments, smart-contract-template updates as new patterns are released) | OpEx — renewable annually | A$130,000 / year |
| 4 | Tx-Rails platform access — BFT infrastructure, audit attestation, Hedera anchoring, dual-DC redundancy, smart-contract execution layer, regulator + customer-audit + financier pipeline. Includes the three operator utilities. Tiered by deployment complexity — see range governance below. | OpEx — annual platform subscription, complexity-tiered | A$120,000 – A$3,000,000 / year |
| 5 | Counterparty smart-contract participation UI (optional) — thin signature surface for every external counterparty that participates in your multi-party smart contracts. NOT a contract-lifecycle-management or treasury replacement. | One-off CapEx — capitalisable over 3–5 years | A$100,000 – A$280,000 |
| Year 1 total (Tier-3 example: 3–4 pyramids, multiple smart-contract types, Items 1+2 mid-points, Item 5 excluded) | A$900,000 | ||
| Year 1 total with Item 5 mid-point | A$1,090,000 | ||
| Year 2+ ongoing (Tier-3 example) | A$530,000 / year |
Item 4 — deployment-complexity tier pricing:
Cross-vertical complexity is the dominant variable here — not portfolio size, not facility count, not pyramid count alone. Tiering reflects the operational complexity of running multi-party smart contracts across multiple federations and verticals.
| Tier | Customer profile | Deployment shape | Annual platform fee (Item 4) |
|---|---|---|---|
| Tier 4 | Single-vertical, IIoT-only, no smart contracts — Shape 3 single pyramid or pilot | 1 pyramid, IIoT audit only | A$120,000 |
| Tier 3 | Single-vertical IIoT + 2–3 smart-contract types, OR cross-vertical IIoT-only on 2–3 pyramids — Shape 2 small cluster | 2–3 pyramids, IIoT + simple SC | A$340,000 |
| Tier 2 | Cross-vertical IIoT + 5+ smart-contract types, or multi-counterparty smart-contract networks (e.g. tier-1 manufacturer with sub-tier supplier smart contracts + customer outcomes contracts + insurer recall contracts) — Shape 2 grouped | 4–7 pyramids, IIoT + multi SC | A$900,000 |
| Tier 1 | Multi-vertical, multi-jurisdiction, deep smart-contract integration (a global OEM with PBH leasing + recall co-ordination + Scope-3 supply-chain + cyber-supply-chain firmware promotion + tier-2/3 supplier payment contracts all running on the same underlay) — Shape 1 sovereign + Shape 2 cross-federation | 8+ pyramids, full multi-SC | A$2,500,000+ |
Item 1 — what governs the range:
– A$180k floor — hash-only attestation (Mode A) + single-template smart-contract instantiation: your IIoT sources commit as normal; we receive content hashes; one smart-contract template (e.g. just EaaS pay-per-runtime).
– A$400k ceiling — atomic dual-write (Mode B) + multi-template smart-contract instantiation: your MES / ERP and Tx-Rails commit in the same transaction; multiple smart-contract templates wired across multiple federations.
– Most operators land mid-range with CDC observation (Mode C) + 2–3 smart-contract templates at ~A$260–330k.
Item 5 — what governs the range:
– A$100k floor — single-flow counterparty kiosk (e.g. just sub-tier-supplier milestone signoff), single role, default branding.
– A$280k ceiling — multi-flow hub (PBH credit + milestone payment + recall-batch-receipt + outcome attestation + Scope-3 evidence + insurer claim signoff), multiple role tiers, DID auth, deep brand alignment, complex multi-vertical workflows.
Smart-contract templates included
The following multi-party smart-contract templates ship with the platform and can be instantiated under Item 2 (configuration) without separate per-template licensing. Add new bespoke templates as part of Item 2 (within the band) or as a follow-on scope.
| Template | Trigger source | Typical parties | Used in vertical sheets |
|---|---|---|---|
| Equipment-as-a-Service (pay-per-runtime) | IIoT runtime telemetry | Equipment vendor + customer + financier | Manufacturing, Aviation (PBH), Mining |
| Milestone payment release | Multi-party signoff event | OEM + tier-1/2 supplier + financier | Manufacturing, Aviation, Local Govt (capital works), Mining |
| Multi-party recall execution | Manufacturer-initiated recall event | Manufacturer + regulator + customer + insurer | Manufacturing, Supermarkets, Health |
| Outcomes-based payer contract | Multi-party clinical / outcome attestation | Provider + payer + reinsurer + clinical specialists | Health (lead vertical) |
| AD-compliance retrofit | Regulator-issued directive + retrofit attestation | Regulator + OEM + operator + DAR | Aviation (lead vertical) |
| Cyber-supply-chain firmware promotion | Multi-party firmware-verification signoff | OEM + tier-1 + cybersec auditor + operator | Aviation, Defence, Health, Energy |
| Scope-3 emissions evidence flow | Supplier-attested emissions data | Tier-2/3 supplier + tier-1 + customer | Manufacturing, Mining, Supermarkets, Energy |
| Power-by-the-Hour leasing | IIoT engine-run-time telemetry | Engine OEM + airline + financier | Aviation (lead vertical) |
| Cold-chain breach insurance auto-claim | IIoT temperature-deviation event | Shipper + 3PL + insurer + receiving facility | Health, Supermarkets, Pharma manufacturing |
| Royalty-payable settlement | IIoT production-volume telemetry | Producer + royalty authority + landholder | Mining (lead vertical), Energy |
| Outage-credit / SLA-credit automation | IIoT outage-event telemetry | Utility + customer + retail intermediary | Energy, Transport (rail), IT-services |
| Multi-party planning-approval co-sign | Multi-party regulatory signoff | Council + state planning authority + applicant + objector | Local Government |
| Conflict-of-interest declaration binding | Self-attested declaration event | Councillor + matter under decision | Local Government |
| Supplier-quality-event payment gating | IIoT FAI / PPAP / quality-deviation event | Supplier + buyer + customer-of-record | Manufacturing, Aviation, Health |
Payback and ROI
The combined IIoT + Smart Contracts platform value sits where pure-IIoT and pure-contract-management both leave money on the table — automating multi-party flows that today happen via email + phone + spreadsheet reconciliation.
For a Tier-3 deployment crossing 2–3 verticals (typical: a Tier-1 manufacturer running supplier-quality smart contracts in manufacturing + EaaS-runtime contracts in industrial-machinery + recall-coordination contracts in product-liability), ~A$900M revenue spanning the relevant operational scope:
| Annual benefit | Conservative | Realistic |
|---|---|---|
| Audit IT-controls displacement (multi-vertical external auditor + multi-regulator audit + customer-audit programmes) | A$200,000 | A$500,000 |
| Multi-party contract execution overhead reduction (replacing email + spreadsheet + phone reconciliation cycles with cryptographically-attested automation) | A$500,000 | A$2,000,000 |
| Reduced cash-cycle (escrow + automated release shorten multi-party payment cycles by weeks; A$50M of cash-cycle compression at 6% cost of capital = A$3M/yr opportunity cost reduction) | A$300,000 | A$1,500,000 |
| Reduced exposure to product-liability, recall, AD-compliance, outcomes-failure-to-pay events (multi-party smart contracts make outcome-failure-attribution attestation-driven, not litigation-driven) | A$400,000 | A$2,500,000 |
| Insurance-premium reduction tied to telemetry-backed evidence + automated incident-response contracts (product liability, cyber, business-interruption, recall-cost, professional indemnity) | A$250,000 | A$1,000,000 |
| Customer-of-record + supplier-tier retention (multi-party contract participation increasingly becomes a procurement requirement; market-share retention value) | A$200,000 | A$800,000 |
| Total annual value delivered | A$1,850,000 | A$8,300,000 |
| Tx-Rails Year 2+ cost (Tier-3 example) | A$530,000 | A$530,000 |
| Net annual return | A$1,320,000 | A$7,770,000 |
| ROI multiple | 3.5× | 15.7× |
The combined-sheet ROI is materially higher than any single-vertical sheet because:
1. Cash-cycle compression is a step-change in multi-party contract execution; single-vertical sheets understate this because vertical scopes often have shorter intra-vertical cycles.
2. Cross-vertical evidence reuse — Scope-3 evidence captured for one customer relationship satisfies a CSRD obligation that also satisfies a green-finance covenant that also satisfies a sustainability-linked-loan margin trigger. One IIoT capture, three independent value lines.
3. Smart-contract automation removes labour that was distributed across the vertical sheets as separate ROI lines — when those lines combine, the absolute labour-cost reduction stacks.
How this sheet relates to the per-vertical sheets
Use this sheet when at least one of the following applies:
- Multi-vertical deployment — your operational footprint crosses 2+ of our vertical sheets (e.g. a Tier-1 utility that is simultaneously an Energy customer + Asset-Management customer + Local-Government counterparty).
- Smart-contracts-lead use case — you’re buying the smart-contracts execution layer as the primary value driver, with IIoT capture as the supporting infrastructure (e.g. an OEM whose Power-by-the-Hour contracts are the lead deliverable, with IIoT being how the conditions resolve).
- Platform-anchoring deployment — your first use case is single-vertical but the deployment is sized for future cross-vertical use (e.g. starting in manufacturing but anchoring future expansion into recall-coordination smart contracts that span manufacturing + supermarkets + insurer).
- Counterparty-of-record across multiple verticals — you’re a sub-tier supplier or counterparty participating in smart contracts initiated by customers across multiple verticals, and you want a single platform participation rather than separate per-customer deployments.
For single-vertical, single-purpose deployments, the per-vertical sheets are calibrated more tightly — they reflect that vertical’s specific regulator anchors, customer-tier patterns, and ROI drivers. Use them in preference unless one of the above applies.
The per-vertical sheets:
| Vertical | Sheet |
|---|---|
| UK Housing Association | ha-pricing-sheet.md |
| AU Community Housing Provider | au-chp-pricing-sheet.md |
| Transport | transport-pricing-sheet.md |
| Energy | energy-pricing-sheet.md |
| Mining & Minerals | mining-pricing-sheet.md |
| Supermarkets | supermarket-pricing-sheet.md |
| Aerospace Manufacturing | aviation-pricing-sheet.md |
| General Manufacturing | manufacturing-pricing-sheet.md |
| Local Government | local-government-pricing-sheet.md |
| Health & Medical | health-medical-pricing-sheet.md |
Pilot terms — non-binding, parallel-run, zero operational risk
- 3 months running Tx-Rails alongside your existing systems. No production switchover.
- Mode A (hash-only) integration with one chosen federation for the IIoT half, plus one smart-contract template instantiated for the Smart Contracts half.
- Walk-away clause: if at month 3 the metrics don’t meet agreed targets, the engagement ends.
- Regulator + customer-of-record pre-validation: before signing, we’ll meet with your relevant regulator + at least one major customer’s audit team to confirm evidence-pack and smart-contract acceptability.
- Data ownership: cryptographic exports are open-format, re-readable indefinitely.
Why now
- CSRD + ESRS + ISSB IFRS S2 climate-disclosure regimes now in their first reporting cycles — multi-vertical Scope-3 evidence-flow is operationally non-negotiable.
- Multi-jurisdictional insurance market hardening — product-liability, cyber-supply-chain, business-interruption, recall coverage all hardening; telemetry + smart-contract-attestation increasingly required for coverage.
- Cyber-supply-chain regulatory regimes maturing in parallel (EASA Part-IS, FAA NPRM 22-04, EU NIS2, US Executive Order 14028) — firmware-provenance smart contracts move from “interesting” to “mandatory”.
- Outcomes-based contracting scaling across multiple verticals (health, infrastructure, defence, education, justice) — multi-party attestation infrastructure becomes the differentiator vs traditional fee-for-service procurement.
- Modern Slavery + Forced-Labor regulations (AU MSA, US UFLPA, EU CSDDD, UK MSA reform) — multi-tier supplier-attestation flows materially change procurement cost structures.
- Industry 4.0 + IIoT maturity — the underlying telemetry already exists; Tx-Rails adds the trust + automation layer to investment your organisation has already made.
Next steps
- 60-minute discovery call (longer than per-vertical sheets because the cross-vertical scope warrants it) with your CFO + CTO + General Counsel + the operational leads from each in-scope vertical.
- Scoping workshop (2-day on-site or extended remote) to identify the 2–3 lead smart-contract use cases and the 2–3 lead IIoT federations to anchor the pilot.
- Letter of Intent — non-binding, signals pilot interest.
- Pilot kick-off within 12 weeks of LOI (longer than per-vertical pilots because of cross-vertical scope).
Contact: John Olsen · john@itotchaincloud.com.au · +61 490 114 879
Reference data sources: combined reference base across all 10 per-vertical sheets (see those sheets for full citations); cross-vertical: CSRD + ESRS implementation studies (CDP, GRI Standards); ISSB IFRS S2 implementation studies; OECD Due Diligence Guidance for Responsible Supply Chains; ENISA + CISA cyber-supply-chain regulatory framework studies; sustainability-linked loan margin-impact studies (S&P Global, Bloomberg NEF); McKinsey + BCG industry-4.0 outcome studies; multi-party contract execution overhead benchmarks (Aberdeen, Forrester). Full citations available on request.
Tx-Rails — Built by IT/OT Chain & Cloud Australia (ITOTCCA). Sydney · London.