Skip to main content

Use Cases

This section provides illustrative use cases that demonstrate how the Base Product Specification (BPS) can be applied across different domains.
The scenarios are illustrative, not prescriptive — they show the versatility of the PDS/PROD split without limiting its scope.

1. Data Product: Customer Transactions Dataset​

  • Scenario:
    A bank wishes to publish a Customer Transactions Data Product for internal analysts and external regulators.

  • PDS (Deployment):

    • Input port: Secure SQL endpoint (Trino).
    • Output port: Parquet files delivered via S3 bucket.
    • Version: Published v1.2, maintained quarterly.

  • PROD (Semantics):

    • Purpose: “Captures all debit/credit transactions for retail customers.”
    • Ownership: Corporate Banking Data Team.
    • Governance: GDPR-compliant, lineage documented.
    • Risk: Classified as “sensitive financial data.”
    • Classification: finance/transactions taxonomy.

2. AI Product: Credit Scoring Model​

  • Scenario:
    A fintech offers a credit scoring AI model through its marketplace.

  • PDS (Deployment):

    • Input port: REST endpoint for applicant features (JSON).
    • Output port: Prediction score (0–1).
    • SLA: Latency < 100ms, uptime 99.9%.

  • PROD (Semantics):

    • Purpose: “Predicts creditworthiness of loan applicants.”
    • Governance: Classified as “High-Risk AI” under EU AI Act.
    • Evaluation: Bias test results included.
    • Ownership: Risk Analytics Team.
    • Classification: Binary Classifier; domain=credit risk.

3. Physical Product: Storage Device​

  • Scenario:
    A hardware manufacturer sells a 2TB external storage device through a retail channel.

  • PDS (Deployment):

    • Input: Power supply (USB-C).
    • Output: Data storage capacity (2TB, NTFS format).
    • Delivery: Shipped with warranty card.

  • PROD (Semantics):

    • Category: “Consumer Electronics > Storage.”
    • Compliance: CE certified, RoHS compliant.
    • Provenance: Manufactured in batch #SD2025A.
    • Ownership: Vendor support desk responsible for warranty claims.
    • Consumer Electronics > Storage.

4. Software Product: Payment Orchestration Service​

  • Scenario:
    A SaaS provider publishes a Payment Orchestration API to enterprise customers.

  • PDS (Deployment):

    • Input: JSON payment requests (REST API).
    • Output: Payment status responses.
    • Version: API v2.1, OpenAPI spec available.

  • PROD (Semantics):

    • Purpose: “Manages multi-gateway payment routing and retries.”
    • Ownership: SaaS Payments Division.
    • Governance: PCI-DSS compliance.
    • Evaluation: 99.99% uptime SLA audited annually.
    • Classification: Payments > Orchestration.

5. Cross-Domain Marketplace​

  • Scenario:
    A unified marketplace allows consumers to discover Data, AI, Software, and Physical Products side by side.

  • Benefit of BPS:

    • PDS provides consistent operational details (how to access, install, deploy).
    • PROD provides consistent semantic meaning (what it is, why it matters, governance context).
    • Together, they enable seamless discoverability, evaluation, and trust across domains.

6. Lessons from Use Cases​

  • The PDS view ensures reproducibility and usability.
  • The PROD view ensures meaning, trust, and governance.
  • BPS works across digital and physical products, avoiding silos.
  • Examples are illustrative, not exhaustive — spec authors are free to define additional domain-specific profiles.