specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Carrier Global providerId: carrier-global created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - FinOps - FOCUS - HVAC - IoT - Telematics - Building Automation description: 'FOCUS-aligned FinOps for Carrier Global: per-asset and per-building digital subscriptions (Lynx Fleet, Abound, i-Vu) bundled with hardware and dealer-network commercial agreements.' notes: Carrier does not bill API access as a separate SKU. FinOps mapping is provisional; reconcile against the customer's Lynx / Abound / i-Vu commercial agreement. sources: - https://www.corporate.carrier.com/ - https://doc-api.fleet.lynx.carrier.io/ alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Carrier Global Corporation serviceCategory: HVAC / IoT Platform billingModel: pricingCategory: Subscription + Per-Asset billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase - Usage - Adjustment focusColumns: ServiceName: Carrier Digital Platforms ServiceCategory: HVAC / IoT Platform ProviderName: Carrier Global PublisherName: Carrier Global Corporation InvoiceIssuerName: Carrier Global Corporation BillingCurrency: USD meters: - name: lynx_assets unit: asset-month aggregation: max dimensions: - asset_type - region - name: abound_buildings unit: building-month aggregation: max dimensions: - region - name: ivu_sites unit: site-year aggregation: max - name: api_requests unit: request aggregation: sum dimensions: - api - tenant - name: telemetry_volume unit: GB aggregation: sum dimensions: - api principles: - name: Visibility description: Visibility comes from the Lynx Fleet / Abound dashboards (asset count, alarms, telemetry volume); no separate API billing dashboard. - name: Allocation description: Allocate by asset (TRU), building, or site; multi-fleet operators should configure separate Lynx tenants per business unit. - name: Optimization description: Decommission inactive assets to reduce per-asset subscription burn; tune alarm and telemetry cadence to avoid redundant data ingestion. - name: Accountability description: Fleet-operations / facilities-management owner holds the relationship; quarterly asset and renewal reviews with the Carrier dealer network are typical. maintainers: - FN: Kin Lane email: info@apievangelist.com