specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
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/
provider: Ford
providerId: ford
publisherName: Ford Motor Company
serviceCategory: Connected Vehicle / Mobility
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:
  - Automobiles
  - Connected Vehicle
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps mapping for Ford's Developer Marketplace — partner-licensed connected-vehicle APIs typically billed on a per-vehicle subscription plus per-call usage basis under a partnership agreement.
notes: No public pricing. Meters reflect typical connected-vehicle/OEM API invoicing patterns (per-VIN subscription, per-call fees, premium-data add-ons).
sources:
  - https://developer.ford.com/
  - https://developer.ford.com/apis
billingModel:
  pricingCategory: Subscription + Usage
  billingFrequency: Monthly
  billingCurrency: USD
  chargeCategories:
    - Usage
    - Purchase
    - Tax
    - Adjustment
    - Credit
focusColumns:
  ServiceName: Ford Developer Marketplace
  ServiceCategory: Connected Vehicle / Mobility
  ProviderName: Ford Motor Company
  PublisherName: Ford Motor Company
  InvoiceIssuerName: Ford Motor Company
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
  - name: vehicle_subscriptions
    description: Active connected-vehicle (VIN) subscriptions enrolled with the partner application
    unit: vehicle-month
    aggregation: max
    dimensions:
      - region
      - vehicle_model
      - data_package
  - name: api_calls
    description: API requests against vehicle, location, telemetry, or dealer endpoints
    unit: request
    aggregation: sum
    dimensions:
      - api
      - endpoint
      - data_class
  - name: streaming_events
    description: Webhook / streaming events delivered (telemetry, status changes, alerts)
    unit: event
    aggregation: sum
    dimensions:
      - event_type
      - vehicle_model
  - name: premium_data
    description: Premium-data add-ons (high-resolution telemetry, historical replay, OBD-II extended PIDs)
    unit: request
    aggregation: sum
    dimensions:
      - data_class
principles:
  - name: Visibility
    description: Pull partner-portal usage reports daily and reconcile against your own request logs to catch billable polling against vehicles whose owners have revoked consent.
  - name: Allocation
    description: Tag every request with end-customer/account, VIN, and use-case so spend is allocable to the downstream product feature.
  - name: Optimization
    description: Replace polling with webhooks/streaming where Ford supports it; respect minimum poll intervals to avoid wasted billable calls and TCU wake-ups; cache static data (VIN-decode, model trims).
  - name: Accountability
    description: Connected-vehicle product owner owns the partnership agreement; finance audits per-VIN subscription counts against active consent records monthly.
maintainers: []