Pi MEDIATION / NETWORK DATA PROCESSING

Turn network data
into business-ready data.

Prepare diverse sources and formats for billing, analytics and new services in one processing layer. Reuse integrations across consumers and scale processing capacity with demand.

Pi Mediation is developed and supported by Tadam. Explore the Pi product family.

Email us to book a demoinfo@tadamsoft.com
Explore capabilities
  • ASN.1
  • CSV
  • XML
  • JSON
  • Binary formats
  • Real-time
  • File-based

01 / WHY MEDIATION

Connect diverse sources. Reuse the work.

Each new source or downstream consumer can add another parser, script or billing-side workaround. Pi Mediation centralizes collection and common preparation, then applies the fields, formats and delivery rules each consumer needs.

  1. 01

    Collect

    Network elements, gateways, probes and files

  2. 02

    Process

    Decode, validate, enrich, aggregate and deduplicate

  3. 03

    Deliver

    Billing, warehouses, analytics and downstream systems

Pi Mediation architecture: Collect: Network elements, gateways, probes and files; Process: Decode, validate, enrich, aggregate and deduplicate; Deliver: Billing, warehouses, analytics and downstream systems
Pi Mediation architecture. Swipe horizontally to explore the diagram, or use arrow keys when focused. Enlarge diagram

02 / WHAT YOU CAN DO

Mediation capabilities

01

Keep preparation work out of billing

Filter, aggregate and prepare records before delivery to billing and other consumers. Combine real-time and file-based processing in one installation, with rules for each destination.

02

Give your team control over change

Decode ASN.1, CSV, XML, JSON, binary and text formats in visual workflows. Adapt validation, normalization and delivery rules as sources and business requirements change.

03

Add business context to network records

Enrich data using reference information, with caching and individual or bulk queries to external databases.

04

Make processing traceable. Recover from errors.

Use processing audits, live monitoring and alerts to investigate exceptions. Reprocess affected data after errors.

03 / BUILT TO BE OPERATED

Deployment and operations

Cloud-native. On your infrastructure.

Run a containerized, Kubernetes-based platform on your infrastructure, including on-premises. Execution workers are separate from administration and user access services.

Plan for service continuity

Use automatic load balancing across processing workers. Plan active/active or active/standby geo-redundancy around your availability requirements.

Keep changes manageable

Manage workflows through a web interface and automate configuration promotion between environments with CI/CD. Use role-based access and LDAP synchronization to organize team permissions.

IN PRACTICE / RESOURCES FOLLOW THE WORK

Scale for the workload. Release capacity when it falls.

Traffic varies through the day, and a delayed source can deliver a backlog alongside live data. An elastic execution layer lets you respond to these changes instead of keeping peak processing capacity allocated throughout the day.

  1. 01 / QUIETER HOURS

    Free capacity for other work

    When overnight traffic falls, reduce processing workers and release cluster resources for other workloads.

  2. 02 / A QUEUE BUILDS UP

    Put more workers on the backlog

    Add execution capacity and distribute accumulated work across workers to accelerate processing.

  3. 03 / BACK TO NORMAL

    Release the extra capacity

    As the queue clears, return to the capacity needed for ongoing traffic instead of retaining the peak allocation.

Validate the economics on your workload.

During a scoped pilot, compare processing rate, queue size and allocated resources. Agree scaling policies, recovery checks and source and destination limits against your service requirements.

04 / A CLOSER LOOK

Questions about Mediation

Can cloud-native Mediation run on-premises?

Yes. Cloud-native describes the containerized, Kubernetes-based architecture; on-premises describes where it runs. Pi can run on the operator’s infrastructure. Cluster requirements, capacity and integration with existing operations are defined during deployment planning.

What determines the throughput gained from extra workers?

The result depends on how the workflow can distribute work and on source, storage and destination capacity. Scaling policies and resource limits are configured for the deployment and validated against the target workload.

How can elastic processing improve infrastructure economics?

On-premises, released capacity can serve other workloads on infrastructure you already own. A lower cloud bill depends on the billing model and whether paid resources are actually reduced; fewer processing workers alone do not guarantee lower charges.

Does Mediation replace charging or billing?

No. Mediation prepares and delivers records. Rating, pricing and invoicing remain in the relevant business systems. The processing moved out of billing depends on the source records and accounting requirements.

Are analytics and predictive models part of Mediation?

Mediation can prepare inputs for traffic analysis, security analysis and predictive models when suitable source data and integrations are available. The receiving applications perform the analysis; those applications and models are not supplied by Mediation itself.

From product to deployed solution.

Tadam assesses your requirements, integrates Pi Mediation with your systems and prepares the solution for production. We support its integrations and configuration, with 8×5 or 24/7 coverage by agreement.

Delivery and support

Contact us

FZCO IFZA Business Park, DDP, Dubai, United Arab Emirates

Diagram