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: Johnson & Johnson
providerId: johnson-and-johnson
publisherName: Johnson & Johnson
serviceCategory: Healthcare / Enterprise Integration
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
notes: J&J does not expose a public usage-billing surface. FinOps shape is inferred from a
  negotiated-enterprise model. Meters listed reflect typical integration line items (API
  calls, file transfers) and should be re-modeled against the actual contract once available.
tags:
  - Healthcare
  - Medical Devices
  - Pharmaceuticals
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps scaffold for Johnson & Johnson integration surfaces.
  Treated as negotiated enterprise; no first-party billing API.
sources:
  - https://www.jnj.com/
  - https://www.finops.org/framework/
  - https://focus.finops.org/focus-specification/v1-3/
billingModel:
  pricingCategory: Enterprise / Negotiated
  billingFrequency: Per-Contract
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Adjustment
focusColumns:
  ServiceName: Johnson & Johnson Integration APIs
  ServiceCategory: Healthcare / Enterprise Integration
  ProviderName: Johnson & Johnson
  PublisherName: Johnson & Johnson
  InvoiceIssuerName: Johnson & Johnson
  BillingCurrency: USD
meters:
  - name: api_requests
    unit: request
    aggregation: sum
    dimensions:
      - integration
      - business_segment
      - partner
  - name: file_transfers
    unit: file
    aggregation: count
    dimensions:
      - integration
      - business_segment
principles:
  - name: Visibility
    description: Track usage at the integration-contract level since J&J does not expose
      first-party usage telemetry; instrument calls on the consumer side.
  - name: Allocation
    description: Allocate by business_segment (Innovative Medicine vs MedTech vs Supply
      Chain) and by integration_id to reflect the multi-OpCo structure.
  - name: Optimization
    description: Use bulk / batch interfaces where contracts permit, and reconcile usage
      against contract minimums periodically.
  - name: Accountability
    description: Each integration has a J&J relationship owner; pair with an internal API
      product manager who owns the consumer-side cost.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com