You are here:
Communications Cloud Data Model Objects
Data model objects (DMOs) store different types of data in Data 360. Get access to standard model objects as part of the SSOT package that’s automatically installed in your Salesforce org with Communications Cloud and Data 360.
| REQUIRED EDITIONS |
|---|
| Available in: Lightning Experience |
| Available in: Enterprise, Developer, and Unlimited Editions |
After you import your service and customer data into Data 360, map the data to the required DMOs before using the data for segmentation, activation, analytics, or any other operation. To get started with data mapping, add a connected data source to Data 360. After you connect a source, Data 360 accesses the source so that you can create mapping sets between objects and fields within it and the Customer 360 Data Model.
Communications Cloud Network Communications Data Model Objects
Communications Cloud data model objects contain network communications data that help communications providers model and store data on communications service usage and performance. The Salesforce Standard Data Model SSOT package contains network communications data model objects that communications companies can use if they have Communications Cloud and Data 360 in their org.
You can use the network communications data model objects for these use cases.
- Monitor and predict SLO breaches by using Generative AI and predictive analytics.
- Monitor the customers' bandwidth usage and suggest a service upgrade.
- Trigger actions such as sending emails to customers by integrating with Data Action or Salesforce Flow.
Asset Service Level Objective Data Model Object
Asset Service Level Objective (SLO) data model is a structured representation of the targets and thresholds for a digital service to meet the service quality standards. This model includes attributes such as performance metrics, acceptable thresholds, and evaluation periods that define the service level objective.
The Asset Service Level Objective (SLO) is information about the data, such as the source and destination IP addresses, timestamps, and the type of data such as TCP and UDP.
| field | description |
|---|---|
| Asset | The ID of the asset related to the Service Level Objective (SLO). |
| Asset Measure | The specific metric being considered for the Service Level Objective (SLO), such as Network Bandwidth, Latency, or Jitter. |
| Asset Service Level Objective ID | The unique ID for the Service Level Objective (SLO). |
| Asset Service Level Objective Status | The current state of an asset's Service Level Objective, indicating whether the performance and reliability targets are being met. |
| Conformance Comparator | Operator specifying how the measured value should relate to the target. |
| Conformance Period | The time period over which the metric is evaluated. |
| Conformance Period Unit of Measure | The unit used to quantify the time period over which the metric is evaluated. |
| Description | A brief description of the SLO. |
| Grace Period | The time allowed to fix the issue before it is considered a breach. |
| Grace Period Unit of Measure | The unit of measure for the time allowed to fix the issue before it is considered a breach. |
| Internal Organization | A reference ID to the business unit or other internal organization that owns the Asset Service Level Objective. |
| Key Qualifier Asset Service Level Objective ID | A unique identifier that references a specific Service Level Objective (SLO) in the context of a particular asset. This ID is essential for distinguishing and managing SLOs that are tied to specific assets, ensuring precise tracking of performance and reliability targets for those assets. |
| Name | A Human-readable name for the Service Level Objective. |
| Threshold Target | The threshold value for warnings or alerts. |
| Threshold Target Unit of Measure | The unit of measure used for the threshold value for warnings or alerts. |
| Validity End Date | The date and time when the Service Level Objective validity ends. |
| Validity Start Date | The date and time when the Service Level Objective validity starts. |
Asset Service Level Objective Consequence Data Model Object
Asset Service Level Objective (SLO) consequence data model has network communications data that is sent over a network when the SLO isn’t met. These are computer networks (for example, the internet) or a telecommunications network that includes all the data packets sent and received over a network, such as emails, voice calls, video streaming, web browsing, and any other type of data transfer.
| FIELD | DESCRIPTION |
|---|---|
| Asset | The ID of the asset related to the Service Level Objective (SLO) consequence. |
| Asset Service Level Objective Cnsqnc ID | The unique identifier for the Service Level Objective consequence. |
| Data Source | The origin of the data used for analysis, monitoring, or reporting. This includes network devices, servers, monitoring tools, and user devices. |
| Data Source Object | A specific object or component within a data source that provides detailed information or metrics for analysis. |
| Internal Organization | A reference ID to the business unit or other internal organization that owns the Asset Service Level Organization consequence. |
| Key Qualifier Asset Service Level Objective Cnsqnc ID | A unique identifier that references a specific Service Level Objective (SLO) consequence in the context of a particular asset. This ID is essential for distinguishing and managing SLOs that are tied to specific assets, ensuring precise tracking of performance and reliability targets for those assets. |
| Service Level Spec Consequence | The actions or penalties that occur when the Service Level Objective isn’t met. |
Network Usage Data Model Object
Network Usage data model is a canonical representation of usage records for analytics and AI triggered events. This ensures data consistency, interoperability, and quality across diverse systems and simplifies integrating new data sources, enhance data processing efficiency, and prepares data for AI and machine learning.
This data model helps to provide reliable analytics and enables automated responses to data patterns, facilitating informed decision-making in a complex digital ecosystem.
| field | description |
|---|---|
| Account | The ID of the account related to the network usage. |
| Asset | The ID of the asset related to the network usage. |
| Average Availability (%) | The percentage representing the average time a service is operational and accessible over a specified period. Higher percentages reflect more consistent and reliable performance. |
| Average Call Drop Rate (%) | The percentage of calls that are unexpectedly terminated or dropped before completion during a specified period. A lower rate indicates better call stability and reliability, essential for evaluating network performance. |
| Average Call Setup Success Rate (%) | The percentage of successful call setups out of the total call attempts over a specified period. A higher rate indicates a more reliable network, ensuring users can establish calls without issues. |
| Average Error Rate (%) | The percentage of data packets corrupted during transmission. A lower error rate indicates better network quality and reliability, ensuring accurate data communication. |
| Average Jitter (ms) | The average variation in packet arrival times, measured in milliseconds, over a specified period. Indicates the stability and consistency of the network connection. |
| Average Latency (ms) | The average time, measured in milliseconds, it takes for a data packet to travel from the source to the destination across the network over a specified period. Indicates the responsiveness of the network connection. |
| Average Mean Opinion Score (MOS) | The average score that represents the perceived quality of voice or video calls as rated by users on a scale of 1 to 5 over a specified period. |
| Average Packet Loss (%) | The percentage of data packets that are lost or fail to reach their destination out of the total number of packets transmitted over the network during a specified period. |
| Average Response Time (ms) | The average time, measured in milliseconds, it takes for the service provider to respond to a service request or a support ticket over a specified period. Lower response times indicate faster service, improving customer satisfaction, and efficiency. |
| Average Throughput Download (bps) | The average rate, measured in bits per second (bps), at which data is successfully received from the network by a user over a specified period. Higher values indicate a greater capacity to transfer data quickly and efficiently from the network to the user's device. |
| Average Throughput Upload (bps) | The average rate, measured in bits per second (bps), at which data is successfully sent from a user to the network over a specified period. Higher values indicate a greater capacity to transfer data quickly and efficiently from the user's device to the network. |
| Average Time To Repair (TTR) | The average time it takes to diagnose and fix a network issue or failure from the moment it is reported until normal service is restored, measured over a specified period. Lower TTR indicates faster resolution, enhancing reliability and user satisfaction. |
| Data Source | The origin of the data used for analysis, monitoring, or reporting. This includes network devices, servers, monitoring tools, and user devices. |
| Data Source Object | A specific entity or component within a data source that provides detailed information or metrics for analysis. |
| Destination Address | The endpoint or address that received the usage, important for understanding the target or service accessed. |
| Duration | The total time span of the usage event. |
| Duration Unit of Measure | The unit used to quantify the total time span of a usage event, typically measured in seconds or minutes, depending on the service type. |
| Internal Organization | A reference ID to the business unit or other internal organization that owns the network usage. |
| Network Activity Type | The specific category of actions and events occurring within a network. For example, DNS Lookup for resolving domain names, Proxy Browsing for privacy, P2P File Sharing for direct user-to-user sharing, Video Streaming, Secure Web Browsing with HTTPS, VoIP for internet voice calls, and Telephony Service for traditional and mobile communication. |
| Network Location | The physical or network location where the service usage occurred, useful for regional analysis and troubleshooting. |
| Network Usage Start Date Time | The specific date and time when a network usage event or session starts. |
| Network Usage End Date Time | The specific date and time when a network usage event or session ends. |
| Network Usage Id | A unique identifier assigned to each network usage event. |
| Protocol | The protocol used for the service, dictating the rules for data exchange between the source and destination. |
| Source Address | The Originating endpoint or address of the usage, critical for identifying the user's device or entry point into the network. |
| Usage Volume | The specific date and time when a network usage event or session starts. |
| Usage Volume Unit Of Measure | The unit used to quantify the volume of network usage, such as bytes, kilobytes, megabytes, or gigabytes. |
