--- sourceDocument: Australia Telecommunications, Media, and Technology sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-media-technology Release : - australia ft:locale : - en-US ft:publication_title : - Australia Telecommunications, Media, and Technology ft:clusterId : - telmt bundleId : - telmt workflow : - Customer and Industry --- # Data model # Customer Service Problem Management data model {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Customer Service Problem Management data model Customer Service Problem Management (CSPM) provides a structured framework to efficiently handle and resolve customer-reported service issues, ensuring a seamless customer experience. It aligns with the TeleManagement Forum (TMF) framework to manage service disruptions reported by customers or identified by the Network Operations Center (NOC). CSPM emphasizes diagnostic testing to identify root causes and recommend resolutions. Show full answer Show less ## Life cycle of the CSPM data model * **Verify:** Review and validate the service problem case details, including possible modification of the service. The system suggests diagnostic tests based on the case information. * **Diagnose:** Utilize system-defined test specifications to diagnose the root cause. Agents can run or schedule tests immediately and access test details. * **Repair:** Generate repair tasks automatically based on diagnostic test results to address the identified problem. * **Test and Resolve:** Coordinate service problem fulfillment following the established fulfillment flow. * **Close:** Finalize the problem management life cycle by closing the case. ## Data model components and APIs The CSPM data model integrates tables from the Service Test Management application, including definitions for tests, measures, characteristics, thresholds, diagnostic tasks, and resolution tasks. It also includes a key table from the CSPM application for managing service problem cases. CSPM uses two types of APIs to manage and execute tests: * **Northbound APIs:** Utilized during the design phase to create and manage test definitions, characteristics, measures, and thresholds. They enable generating test runs and decomposing complex tests into smaller tasks. * **Southbound APIs:** Responsible for executing tests on external systems or devices, such as routers, by sending test instructions to these platforms. This two-tiered API approach ensures smooth progression from test setup within CSPM to execution on external network components, facilitating effective problem diagnosis and resolution. Customer Service Problem Management (CSPM) provides a framework that enables you to follow a structured approach to handle and resolve customer-reported issues. The framework ensures a seamless and satisfactory customer experience. CSPM follows the TeleManagement Forum (TMF) defined framework to manage service problems. These problems arise when customers experience service disruptions, or when the network operations center (NOC) team identifies network faults and raises complaints about service disruptions or other issues. The CSPM application focuses on the test diagnostic capability to resolve service problems. This includes conducting relevant tests to diagnose the root cause of the problem and then suggesting resolutions based on the test results. ## Customer Service Problem Management data model life cycle {#spm-data-model__section_jlc_r22_jbc} CSPM enables a service-related problem to move through the various stages of Service Problem Management's life cycle to get resolved.{#spm-data-model__table_v2f_2f2_jbc__entry__2} | Stage | Description | |-|-| | Verify | Verify the case created for a service problem experienced by the customer. This includes reviewing the details provided in the case. If necessary, the agent can also modify the service based on the problem. Based on these details, the system suggests the diagnostic tests. | | Diagnose | System-derived test specifications, defined during the initial setup. These specifications are crucial for diagnosing the root cause of service problems. Agents can run these tests immediately or schedule them for a later time. Additionally, the system enables agents to view and run these tests. | | Repair | Based on the diagnostic test results, the system generates the repair tasks to fix the problem. | | Test and Resolve | Service problem fulfillment coordination that follows the fulfillment flow. | | Close | Final step in the Service Problem Management life cycle. | [Table 1. Life cycle of the CSPM data model] {#spm-data-model__table_v2f_2f2_jbc} ## Customer Service Problem Management data model {#spm-data-model__section_upx_fj2_jbc} The following diagram shows the applications, tables, and their relationships that build the CSPM data model. The CSPM data model uses a combination of these tables to store data: * Tables that are from the Service Test Management application includes the following tables: * Test Definition * Test Measure Definition * Test Definition Characteristics * Test Definition Relationship * Specification to Test Definition Relationship * Threshold Rule * Measure Consequences * Diagnostic Task * Resolution Task {#spm-data-model__ul_m3v_5jt_vbc} * Table that is from the Customer Service Problem Management application includes, service problem case. {#spm-data-model__ul_llv_4j2_jbc} The Customer Service Problem Management (CSPM) data model relies on Northbound and Southbound APIs to manage and execute test processes. Northbound APIs play a critical role during the design phase by creating and managing essential components like test definitions, characteristics, measures, and thresholds. These APIs enable the CSPM system to define the specifications and parameters for each test, such as the test type and scope. These are then used to generate unique test runs with identifiers, such as external IDs or sys_id. After these test definitions are established, Northbound APIs facilitate the creation of test runs based on these predefined specifications. If a test requires further breakdown into smaller tasks, the Northbound APIs handle this decomposition. For more information, see [Service Test Management Open API](https://www.servicenow.com/docs/access?context=service-test-management-api&version=australia&pubname=australia-api-reference&ft:locale=en-US). Southbound APIs come into the picture when it's time to execute the tests. For example, if the test involves running a speed test, it isn't conducted directly on your system. It conducts on an external device, such as a router or another network component. The Southbound APIs are responsible for sending these test instructions to the external systems where the tests are to be performed. For more information, see [Integrating Customer Service Problem Management with southbound external systems](https://www.servicenow.com/docs/644siicQWMw7Ah_RCFOetw "If you have a Customer Service Problem Management subscription, you can submit outbound service test run requests to various external systems by integrating the Customer Service Problem Management application with the external southbound systems."). Overall, Northbound APIs are used to design and set up the tests within the CSPM application, while Southbound APIs handle the execution of these tests on external systems. This two-tiered approach promotes a seamless flow from test definition to execution across different platforms.