name: Siemens API FinOps
specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Siemens
providerId: siemens
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:
  - Industry
  - Industrial IoT
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps placeholder for Siemens. Siemens does not bill API consumption as
  a discrete line; cost is bundled into the underlying industrial software license or platform contract.
  No public usage telemetry or per-call billing surface is documented at the corporate level.
sources:
  - https://www.siemens.com/
notes: No corporate-wide API billing model. FinOps treatment is product-specific; reconciliation
  pending direct vendor confirmation per Siemens product.
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: Siemens AG
serviceCategory: Industrial Software
billingModel:
  pricingCategory: Enterprise License / Contract
  billingFrequency: Per-Contract
  billingCurrency: EUR/USD
  chargeCategories:
    - Purchase
focusColumns:
  ServiceName: Siemens
  ServiceCategory: Industrial Software
  ProviderName: Siemens
  PublisherName: Siemens AG
  InvoiceIssuerName: Siemens AG
  BillingCurrency: EUR
meters:
  - name: license_subscription
    description: Siemens product license fee (per-product, per-seat, or per-asset depending on the
      product line); APIs ride on top of the licensed product.
    unit: varies
    aggregation: sum
    dimensions:
      - product
      - region
principles:
  - name: Visibility
    description: Spend visibility comes from the Siemens enterprise software invoice and asset/seat
      management within each product, not a unified usage API at the corporate level.
  - name: Allocation
    description: Allocate by Siemens product line, plant/site, and the engineering team operating the
      asset; tie back to procurement contract IDs.
  - name: Optimization
    description: Optimization is contractual and architectural — consolidate Siemens products, right-size
      seats and assets at renewal, and minimize duplicated platforms within the same plant.
  - name: Accountability
    description: Operations technology and procurement own the Siemens contract; integration teams
      own technical SLA conformance for each product API.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com