Real-Time Decisioning: Turn Every Network Event into Action
Process incoming EDRs as they arrive, recognize meaningful conditions, and automatically trigger the right business or operational response.
Bonyan System's Real-Time Decisioning platform transforms high-volume telecom events into immediate, controlled actions. It receives EDRs and events from mediation, charging, network, customer, and digital systems; validates and enriches them with subscriber and service context; evaluates configurable business rules; and executes the required response.
Instead of waiting for overnight processing and delayed reports, operators can respond while each event is still commercially or operationally relevant.
Closed-loop lifecycle
From Event to Decision to Verified Action
A useful decision platform must understand the event, place it in subscriber and service context, evaluate current and historical conditions, prevent duplicate or conflicting actions, and prove what happened after a decision was made.
01
Receive
Accept incoming EDRs and business events from supported telecom and enterprise sources.
02
Validate
Decode, normalize, classify, deduplicate, and apply event-time and ordering controls.
03
Enrich
Add subscriber, account, product, service, network, and campaign context.
04
Update State
Maintain counters, rolling windows, profiles, sequences, and previous-decision state.
05
Evaluate
Apply configurable rules, eligibility, priorities, exclusions, and conflict controls.
06
Decide
Select the correct treatment and action for the current business context.
07
Execute
Invoke campaigns, APIs, provisioning, notifications, cases, or downstream events.
08
Verify
Track acknowledgment, failure, retry, reconciliation, and the final outcome.
Context and state
Make Decisions with More Than a Single EDR
The platform enriches isolated events and maintains state across time so rules can recognize cumulative usage, inactivity, repeated failures, sudden changes, threshold crossings, and meaningful sequences.
Customer, account, segment, value tier, tenure, and lifecycle stage
Products, packages, service status, and prepaid or postpaid classification
Device, location, roaming, network, and enterprise-service information
Recent usage, recharge behavior, counters, and rolling consumption windows
Previous offers, contacts, responses, exclusions, and customer consent
Campaign eligibility, profile state, groups, and service-level conditions
Configurable business rules
Put Decision Logic Under Control
Rules evaluate live events, enriched profiles, counters, time windows, history, products, network context, previous actions, and external responses. Priorities, effective dates, exclusions, frequency limits, cooldowns, approvals, and conflict resolution prevent uncontrolled automation.
80%
Allowance Threshold
Notify the subscriber and present an eligible add-on when data consumption reaches a defined threshold.
ROAM
First-Time Roaming
Recognize entry into a new destination and start the appropriate roaming journey.
TOP-UP
Recharge Reward
Provision a qualifying bonus package and send confirmation after a successful recharge.
SLA
Service Protection
Open a priority incident after repeated failures or an enterprise operational breach.
RISK
Behavior Change
Route unexpected device, SIM, location, recharge, or usage patterns to a specialist workflow.
WIN-BACK
Retention Journey
Move an inactive subscriber into a controlled retention or reactivation program.
Automated triggers
Connect Decisions to Operational Outcomes
01
Campaign Trigger
Enroll, update, personalize, or suppress a subscriber journey using the event and decision context.
02
API or Webhook
Invoke REST, SOAP, messaging, or other supported interfaces with correlation and customer data.
03
Automatic Provisioning
Activate, suspend, modify, or remove services, packages, features, quotas, and policies.
04
Customer Notification
Trigger SMS, push, email, USSD, or another controlled channel using the correct template and language.
05
Profile or Segment Update
Write classifications, scores, flags, lifecycle states, or eligibility to customer platforms.
06
Case, Alarm, or Task
Create care cases, incidents, fraud alerts, assurance tasks, or manual reviews with supporting evidence.
07
Downstream Event
Publish a reusable business event for analytics, applications, and journeys without tight coupling.
Action reliability
Automation Without Losing Operational Control
External calls are tracked through acceptance, rejection, timeout, retry, completion, or manual intervention—essential for actions that can affect service or revenue.
Unique decision and action identifiers
Idempotency and duplicate prevention
Timeouts, retry, backoff, and circuit breaking
Dead-letter and manual-review queues
Acknowledgment and completion tracking
Action reconciliation and controlled replay
Rule governance
Change Rules Safely
Business agility is supported through a governed lifecycle while technical teams retain control over integration, security, performance, and production release requirements.
Ownership, roles, review, approval, publication, and retirement
Effective dates, scheduled activation, versions, and rollback
Test events, simulation, and pre-deployment impact estimation
A/B groups, frequency caps, consent, privacy, and exclusions
Emergency rule or connector suspension
Measured results by rule, segment, campaign, and action
Platform capabilities
Designed for Measurable Real-Time Operations
Real time is treated as a service objective. Decision latency, throughput, event freshness, queue depth, action completion, and failure rates are monitored for each use case.
High-Volume Ingestion
Handle sustained and bursty traffic while isolating slow consumers.
Normalization and Enrichment
Produce canonical events with the context needed for decisions.
Stateful Evaluation
Evaluate events, counters, windows, sequences, and prior decisions.
Low-Latency Execution
Route decisions according to each action's response objective.
Resilience and Back Pressure
Protect decision paths with queues, rate controls, retries, and recovery.
Audit and Explainability
Record input, context, rule version, conditions, actions, and outcomes.
Telecom use cases
One Decision Layer Across Customer and Network Operations
Design ingestion, enrichment, state, rules, execution, security, monitoring, availability, and recovery against measured volumes.
Engineering and Testing
Implement event models, state stores, integrations, rules, and adapters; test correctness, concurrency, latency, load, failure, replay, and reconciliation.
Managed Operations
Provide dashboards, runbooks, rule-release support, connector management, tuning, knowledge transfer, and managed services.
Why Bonyan System
Decisions That Are Executable, Observable, and Adaptable
Telecom events first
Deep familiarity with EDRs, mediation, charging, subscriber data, provisioning, billing, assurance, and telecom operations.
Connected to action
A complete path from event receipt and rule evaluation to verified execution—not just dashboards or recommendations.
Production discipline
Every rule change remains versioned, testable, observable, reversible, and controlled according to business impact.
Open architecture
APIs, messaging, open dataflow patterns, operator-controlled infrastructure, and private Kubernetes where appropriate.
