Customer Service Problem Management data model
Summarize
Summary of Customer Service Problem Management data model
Customer Service Problem Management (CSPM) provides a structured framework aligned with the TeleManagement Forum (TMF) standards to manage and resolve customer-reported service issues effectively. CSPM focuses on diagnosing service problems through test diagnostics and coordinating their resolution, ensuring a seamless and satisfactory customer experience. It addresses issues detected both by customers and network operations centers (NOC), such as service disruptions and faults.
Show less
Life Cycle of the CSPM Data Model
- Verify: Review and validate the service problem case details. Agents can modify service information if necessary, and the system suggests relevant diagnostic tests.
- Diagnose: Utilize system-defined test specifications to identify the root cause. Agents can run or schedule these diagnostic tests as needed.
- Repair: Generate repair tasks automatically based on diagnostic results to address the identified problem.
- Test and Resolve: Coordinate service problem fulfillment following the established fulfillment process.
- Close: Complete the service problem management process by closing the case.
CSPM Data Model Components
The CSPM data model integrates multiple applications and tables to manage problem data and test processes:
- Service Test Management application tables: Includes tables such as Test Definition, Test Measure Definition, Test Characteristics, Test Relationships, Threshold Rules, Diagnostic Tasks, and Resolution Tasks to support detailed test configurations and results.
- Customer Service Problem Management application table: Includes the Service Problem Case table to manage individual customer issues.
Northbound and Southbound APIs
CSPM employs a two-tiered API approach to manage test lifecycle:
- Northbound APIs: Used during the design phase to create and manage test definitions, characteristics, measures, and thresholds. They facilitate decomposition of tests into smaller tasks and generate unique test runs with identifiers.
- Southbound APIs: Handle the execution of tests by sending instructions to external devices or systems (e.g., routers, network components) where tests are performed.
This combination enables CSPM to seamlessly transition from test design to execution across different platforms, enhancing diagnostic accuracy and resolution efficiency.
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 raise complaints, such as service disruptions, errors, 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
| 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. |
Customer Service Problem Management data model
The following diagram shows the applications, tables, and their relationships that build the CSPM data model.
- 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
- Table that is from the Customer Service Problem Management application includes, service problem case.
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, which 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.
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 but instead 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.
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.