--- sourceDocument: Brazil Telecommunications, Media, and Technology sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-media-technology Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Telecommunications, Media, and Technology ft:clusterId : - telmt bundleId : - telmt workflow : - Customer and Industry --- # Map PSR catalog to TMF SID # Mapping of Sales CRM for Telecommunications PSR catalog to TMF SID {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Mapping of Sales CRM for Telecommunications PSR catalog to TMF SID The Sales CRM for Telecommunications PSR catalog aligns its core entities---product offerings, product specifications, customer-facing service specifications, resource-facing service specifications, and resource specifications---with the TM Forum (TMF) shared information and data (SID) model. The TMF SID model is an industry standard framework providing a common language and data model for communications service providers (CSPs), defining key business entities like customers, products, services, and resources and their relationships. Show full answer Show less This alignment ensures that the catalog supports TMF APIs such as TMF 620 and TMF 633, facilitating standardized integration and interoperability. ## Key Components and Their Mapping * **Product Offering:** Represents the commercial market view of a product, including pricing, terms, and customer-facing catalog information. It references product specifications and can be a simple item or a bundle. Product offerings support commercial parameters such as price, market segments, validity dates, and allowed customer actions. * **Bundle Product Offering:** Groups multiple product offerings into a single package (e.g., triple play services). It inherits standard product offering attributes, supports hierarchical bundling, and enables bundle-specific pricing and rules. * **Product Specification:** Provides a detailed, business-focused template for products, describing their characteristics and lifecycle. It forms the basis for instantiating customer products and subscriptions through service specifications. * **Resource Specification:** Defines templates for physical or logical resources (e.g., routers, SIM cards, software components) with common attributes and lifecycle status, serving as blueprints for resource instances. * **Customer-Facing Service Specification (CFSS):** Describes services from the customer's perspective, focusing on service characteristics, SLAs, and configurable parameters. CFSS connects product specifications to resource-facing service specifications and can be atomic or composite. * **Resource-Facing Service Specification (RFSS):** Details the technical and domain-specific service characteristics required to implement and manage resource-facing service instances. It translates customer service needs into network resource requirements and can be hierarchical. ## Practical Application for ServiceNow Customers By using the Sales CRM for Telecommunications PSR catalog mapped to TMF SID, ServiceNow customers can: * Standardize product, service, and resource definitions using an industry-agreed data model, improving consistency and integration across systems. * Leverage TMF-compliant APIs for automation and interoperability with external CSP systems. * Model complex product offerings including bundles with flexible pricing and eligibility rules. * Manage product lifecycles and service realizations from a customer-centric viewpoint aligned with technical resource specifications. * Map business-level product and service definitions directly to technical network resources, facilitating end-to-end service management. ## Example The SASE Custom Solution Bundle in the catalog illustrates this mapping: it is a bundle product offering containing child offerings (internet connectivity, SD WAN GW, SD WAN Controller), each linked to product specifications. These product specifications map to service specifications, which in turn require resource specifications such as Edge Router and VNF components. This structured mapping supports coherent product and service management aligned with underlying resources. The Sales CRM for Telecommunications PSR catalog entities, product offering, product specification, customer facing service specification, resource facing service specification, and resource specification map directly to the corresponding entities in the TM Forum (TMF) shared information and data (SID) model. ## TMF SID model {#somt-map-sid-catalog__tmf-sid} The TMF SID model is an industry-agreed framework by TM Forum that provides a common language and data model for communications service providers (CSPs). It defines business entities such as customer, product, service, and resource and their relationships across enterprise systems. The Sales CRM for Telecommunications PSR catalog maps its core entities to the product, service, and resource layers of the TMF SID model. The TMF APIs that the catalog supports, including TMF 620 and TMF 633, are also based on the SID model. ## Product offering {#somt-map-sid-catalog__product-offering} A product offering defines how a product specification is made available to the market, including its pricing, terms, and conditions. * Market view: Represents the commercial view of a product that customers see in a catalog and agree to contractually. * Relationship to product specification: References a product specification to define what is being sold. One product specification can have multiple product offerings, for example, the same product can be offered with different price points for different time periods. * Components: Can be structured as a simple item or a bundle of other product offerings. * Commercial parameters: Includes price, market segments, valid dates, and allowed actions such as subscription or upgrade. * Catalog management: Categorized in a catalog and can be constrained so that it is sold only within a bundle. {#somt-map-sid-catalog__ul_ihl_xzm_1jc} ## Bundle product offering {#somt-map-sid-catalog__bundle-product-offering} A bundle product offering is a type of product offering that groups two or more product offerings into a single package. A simple product offering represents a single, atomic item such as a mobile handset. A bundle product offering represents a combination of offerings, such as a triple play package (internet, TV, and voice). * Inheritance: Inherits all attributes of a standard product offering. * Composition: Can contain other bundle product offerings or simple product offerings, supporting hierarchical, multi-level bundling. * Reusability: References simple product offerings rather than embedding them, so the same component can appear across different bundles. * Pricing and marketing: Supports bundle-specific pricing, price adjustments, and rules such as eligibility, compatibility, and commitment terms. * Containment: Indicates whether a product offering represents a single item or a collection. {#somt-map-sid-catalog__ul_jhl_xzm_1jc} ## Product specification {#somt-map-sid-catalog__product-specification} A product specification is a detailed description of a tangible or intangible object that serves as the template from which customer products and subscriptions are instantiated. * Commercial focus: Represents the product as perceived by business users, not as technical network components. * Structure: Can be simple (atomic) or a composition of other product specifications. * Attributes: Includes characteristics such as color, relationships with other specifications, and characteristic values. * Realization: Realized through customer-facing service specifications (CFSS) and resource-facing service specifications (RFSS). * Lifecycle: Manages the product lifecycle status. {#somt-map-sid-catalog__ul_khl_xzm_1jc} ## Resource specification {#somt-map-sid-catalog__resource-specification} A resource specification defines the characteristics, behaviors, and relationships of a managed or unmanaged resource. It serves as the template for instantiating specific resource instances of the same type. * Template functionality: Defines the resource type. The resource class defines a specific instance based on that specification. * Definition scope: Captures common attributes such as name, version, and lifecycle status, along with physical or logical parameters that apply to all instances of a resource type. * Resource types: Can describe physical components such as a router or SIM card, or logical components such as software or virtual network functions. * Service realization: Defines the technical components that RFSS requires to deliver a service. {#somt-map-sid-catalog__ul_lhl_xzm_1jc} ## Customer-facing service specification {#somt-map-sid-catalog__cfss} A customer-facing service specification (CFSS) defines technology-agnostic service characteristics that a customer directly purchases. It connects product specifications to resource-facing service specifications, focusing on service parameters, service level agreements (SLAs), and features. * Customer-centric view: Describes services from the customer's perspective, for example, internet access rather than a specific DSL or fiber profile. * Product realization: Represents the realization of a product specification. * Service components: Includes service characteristics such as service name and service rate, parameters that customers can configure during ordering, and links to related product offerings. * Structure: Can be atomic (single) or composite (a grouping of services). * Product offering support: A single CFSS can support multiple similar product offerings. {#somt-map-sid-catalog__ul_mhl_xzm_1jc} ## Resource-facing service specification {#somt-map-sid-catalog__rfss} A resource-facing service specification (RFSS) defines the technical characteristics, attributes, and requirements of a service that maps to underlying resources. Unlike a CFSS, an RFSS is domain-specific or technology-specific. * Definition and purpose: Defines the technical implementation of a service and serves as the blueprint for managing the lifecycle of resource-facing service instances. * Relationship to resource-facing service: Serves as the specification used to instantiate actual resource-facing service instances. * Technology specific: Represents reusable, technology specific components such as DSL, VPN, or MPLS connections to network infrastructure. * Structure: Can be atomic or composite (containing other RFSSs) and defines relationships with physical or logical resources such as routers and IP addresses. * Mapping: Maps a logical service requirement from the CFSS layer to the network resources needed to deliver it. {#somt-map-sid-catalog__ul_nhl_xzm_1jc} ## Product definition in the Sales CRM for Telecommunications catalog {#somt-map-sid-catalog__section_xhf_2fw_bjc} The following example shows how the SASE Custom Solution Bundle is defined in the Sales CRM for Telecommunications catalog. The bundle product offering contains three child product offerings: internet connectivity, SD WAN GW, and SD WAN Controller. Each child offering is linked to its own product specification, which maps to service specifications. For example, Site Connectivity PS maps to SD WAN Edge and Connectivity service specifications. Those service specifications require resource specifications such as Edge Router, VNF, OLT Port, and ONT.