specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Amdocs providerId: amdocs publisherName: Amdocs Limited serviceCategory: Telecom Software 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: - Telecom - BSS - OSS - Billing - Customer Management - MVNO - 5G - SaaS - FinOps - FOCUS description: >- FinOps scaffold for Amdocs connectX BSS. Amdocs invoices telecom operators under enterprise SaaS contracts; usage telemetry is exposed through tenant dashboards but a public FOCUS-aligned billing schema is not published. Reconcile when Amdocs publishes consumption or chargeback documentation. notes: >- Amdocs connectX is a B2B cloud-native BSS SaaS platform sold to telecom operators under enterprise master service agreements. Pricing is bespoke per operator (subscriber count, modules enabled, AWS region) and is not published publicly. Rate limits and quotas are governed by per-tenant capacity provisioning. Reconcile when Amdocs publishes a public pricing or rate-limit page. sources: - https://devportal.amdocs-dbs.com/ - https://developer.amdocs-dbs.com/reference/getting-started-with-your-api - https://focus.finops.org/focus-specification/v1-3/ 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/ billingModel: pricingCategory: Enterprise / Bilateral billingFrequency: Per-Contract billingCurrency: USD chargeCategories: - Purchase - Usage - Tax - Adjustment focusColumns: ServiceName: Amdocs connectX BSS API ServiceCategory: Telecom Software ProviderName: Amdocs PublisherName: Amdocs Limited InvoiceIssuerName: Amdocs Limited BillingCurrency: USD ChargeCategory: Purchase meters: - name: contracted_engagement description: >- Placeholder meter for engagements settled outside a metered API. Real meters cannot be enumerated until Amdocs publishes a metered API billing surface. unit: varies aggregation: sum principles: - name: Visibility description: >- Without a public usage API, consumers must rely on contract reporting, invoice line items, and any tenant dashboards provided under the partner agreement. - name: Allocation description: >- Allocate spend by purchase order, contract identifier, or business unit receiving the Amdocs service. Tag at the procurement layer, not the API call layer. - name: Optimization description: >- Optimization levers live in commercial negotiation (volume commitments, term length, scope) rather than in API-level caching or throttling. - name: Accountability description: >- Procurement and the business owner of the Amdocs relationship own the spend; finance reviews invoice lines on the contract cadence. maintainers: - FN: Kin Lane email: kin@apievangelist.com