Sales CRM for Telecommunications PSR catalog

  • Release version: Zurich
  • Updated April 23, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Sales CRM for Telecommunications PSR catalog

    The Sales CRM for Telecommunications Product, Service, and Resource (PSR) catalog is a unified framework designed to streamline telecom product management by consolidating product, service, and resource definitions into a single catalog. Based on the TM Forum Shared Information and Data (SID) model, this catalog eliminates the need for synchronizing product data between separate sales and fulfillment systems. It supports multiple telecom domains, including B2C Retail Mobile, B2C Retail Wireline, B2B Enterprise Connectivity, and Beyond Connectivity.

    Show full answer Show less

    PSR Catalog Hierarchy

    • Product Offering: The sellable item to customers, including pricing attributes such as recurring charges, one-time charges, ramp-up pricing, mark-ups, mark-downs, and discounts. It references product specifications.
    • Product Specification: A structured definition of a product that maps to exactly one service specification and can reference multiple resource specifications.
    • Service Specification: Defines the service layer with two types:
      • CFSS (Customer Facing Service Specification): Services provided to customers (e.g., Voice, Text, FTTH Access).
      • RFSS (Resource Facing Service Specification): Underlying network resource services delivering the customer service (e.g., HSS, OLT).
    • Resource Specification: Defines physical or logical network resources used to fulfill services (e.g., IMSI, Modem).

    Commercial Features

    • Product Bundling and Hierarchy: Enables grouping of product offers, linking product offers to product specifications, and defining hierarchical relationships among specifications.
    • Pricing Rules: Supports various pricing models including recurring charges, one-time charges, ramp-up, mark-up, mark-down, contract-based pricing, and pricing based on characteristic values.
    • Multidimensional Rules and Relationships: Facilitates complex relationships and rules between product offers, specifications, and contextual factors such as location and customer type.

    Fulfillment Features

    • Catalog-Based Decomposition: Breaks down customer orders into order line items aligned with product offerings and specifications, further decomposed into product, service, and resource orders.
    • Quote Data Carry-Over: Ensures that quote attributes are accurately transferred to order tasks for seamless service orchestration and API interactions.
    • Orchestration Dependencies: Supports staggered order decomposition based on catalog characteristics and rules, simplifying complex dependency management in order workflows.

    The Sales CRM for Telecommunications Product, Service, and Resource (PSR) catalog is a unified catalog that defines all required entities in a single location. It is based on the TM Forum (TMF) Shared Information and Data (SID) model.

    The Sales CRM for Telecommunications PSR catalog consolidates product, service, and resource definitions into a single catalog structure, eliminating the need for product data synchronization between separate sales and fulfillment catalogs. It provides a consistent framework for managing telecom product offerings across multiple domains like B2C Retail Mobile, B2C Retail Wireline, B2B Enterprise Connectivity, and Beyond Connectivity. The following table contains examples of Mobile, Broadband and Dedicated leased lines.

    Because the catalog defines and maps all necessary entities in one place, you don't need explicit entity-to-entity API mapping or separate product data harmonization across sales and service catalogs.

    Sales CRM for Telecommunications PSR catalog

    PSR catalog hierarchy

    Each level in the catalog maps to a specific layer of the product-service-resource model:

    • Product offering: Defines the item to be sold to a customer. Pricing attributes include recurring charges (RC), one-time charges (OTC), ramp-up pricing, mark-up and mark-down percentages, and discounts. A product offering references a product specification which in turn can have child product specifications.
    • Product specification: The structured definition of a product. One product specification maps to exactly one service specification and can reference one or more resource specifications.
    • Service specification: Defines the service layer. Service specifications are of two types:
      • CFSS: Represents the service provided to the customer, for example, Voice and Text CFSS or home fiber FTTH Access CFSS.
      • RFSS: Represents the underlying network resource services that are used to deliver service to the customer, for example, Home Subscriber Server (HSS), RFSS or Optical Line Terminal (OLT) RFSS.
    • Resource specification: Defines the physical or logical network resources that fulfill the service, for example, IMSI or Modem RS.

    Commercial features

    The PSR catalog supports the following commercial capabilities:

    • Product bundling and hierarchy: Supports product offer grouping, product offer-to-product specification definitions, and product specification hierarchies with relationships between specifications.
    • Product offer pricing rules: Supports multiple pricing rule types, including recurring charges, one-time charges, ramp-up pricing, mark-up pricing, mark-down pricing, contract-based pricing, and characteristic value-based pricing.
    • Multidimensional rules and relationships: Supports product offer-to-product offer relationships, product offer-to-product specification relationships, specification-level relationships, characteristic value-based rules, and context-based rules such as location and customer type.

    Fulfillment features

    The PSR catalog supports the following order fulfillment capabilities:

    • Catalog-based decomposition: Decomposes a customer order into order line items based on product offerings and product specifications. Order line items are further decomposed into child or domain orders, such as product orders, service orders, and resource orders.
    • Quote data carry-over into orchestration: Maps attributes from the quote through to order tasks, making the correct data available to southbound APIs during service order orchestration.
    • Orchestration dependencies: Supports staggered decomposition based on catalog characteristic values and decomposition rules. This eliminates complex workflow rules when order line items have dependencies on each other.