IBM Telecommunications Global

Global satellite services provider

IT Operations Automation

The provider's Network Operations team struggled to collect, normalize, and analyze non-standard satellite and IoT performance data, forcing staff to manually assemble information from multiple subsystems before they could diagnose customer-impacting issues.

billions of individuals across the world

Reported impact

Business outcome

The provider consolidated previously fragmented network-performance data, accelerated incident handling through automated ticketing, improved service reliability, and even enabled sales teams to create customer-usage reports that support subscription growth.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

The satellite provider modernized network-operations monitoring by using IBM SevOne as the ingestion and normalization layer for performance data that traditional SNMP-centric tools could not handle. Kafka streams carrying satellite-specific and IoT telemetry feed IBM SevOne, which consolidates the disparate formats into a unified operational view. That normalized data then flows into IBM Netcool Operations Insight and IBM Cloud Pak for Watson AIOps, where the IT and NetOps teams correlate alerts, enrich alarms, and visualize cross-domain operational conditions in one dashboard. The company extended the design with a two-way ServiceNow integration so incidents can be created, tracked, and reported automatically from the same event flow. The resulting closed-loop architecture gives the provider one place to analyze global network health, automate ticketing, and support both operations and customer-facing reporting from a common performance-data foundation.

Data flow

Satellite-specific and IoT telemetry is streamed through Kafka into IBM SevOne, SevOne normalizes the data for Netcool Operations Insight and Cloud Pak for Watson AIOps, and the resulting events and insights trigger automated ServiceNow tickets and reporting workflows.

Solution architecture

4 components · 3 layers
  1. Ingest
    • IBM SevOne Ingests Kafka streams and normalizes non-standard satellite and IoT performance data into a consolidated monitoring view.
  2. Serving
    • IBM Netcool Operations Insight Provides advanced analytics and visualization on the normalized performance data flowing out of SevOne.
  3. Orchestration
    • IBM Cloud Pak for Watson AIOps Correlates, enriches, and consolidates operational alerts and alarms across the provider's environment.
    • ServiceNow Automatically generates and tracks incident tickets and reports from the AIOps event stream.

Architecture clues

  • A two-way ServiceNow integration closes the loop from monitoring to incident creation and reporting.
  • Kafka is used as the middle-ground transport for non-standard telemetry before SevOne normalization.
  • The company had already invested in IBM Cloud Pak for Watson AIOps and extended that environment rather than replacing it.

Evidence from the source

ServiceNow could automatically generate incident tickets, track open and closed tickets and generate reports automatically.
This seamless integration of IBM SevOne, IBM Cloud Pak for Watson AIOps and ServiceNow got us right where we wanted to be.
Using a Kafka-based resource as a middle ground, IBM SevOne was able to take in a range of Kafka streams containing data in non-standard forms, including satellite-specific formats and IoT data.
it could be ported it into IBM Netcool Operations Insight software ... seamlessly for rapid advances analysis and action.
the team too often had to manually cobble together data from different subsystems in order to correlate it to a particular device or other network resource.
Transparency Evidence & methodology 75/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Global satellite services provider customer story

    First-party
    https://www.ibm.com/case-studies/satellite-services-provider-sevone
    Source type
    Vendor-published customer story
    Published
    May 14, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.