Telecom
System truth across the BSS stack.
CRM, order management, provisioning, charging, billing, payments, mediation and the product catalogue were never designed to explain each other. Coharyn learns how they actually connect, proves it, and tells you what breaks before you change any of them.
Why telecom first
The same subscriber lives in six systems and agrees with itself in none of them.
Coharyn's learning core is industry-neutral, but telecom is where cross-system truth is hardest and most expensive to get wrong: activation journeys that span four platforms, charging and billing that must agree to the cent, vendor transitions that move millions of subscriptions, and a catalogue that changes every quarter. Coharyn's first synthetic estate was a telecom estate for that reason.
- Cross-system identity: MSISDN, account number, order reference, learned not configured
- Activation and lifecycle processes reconstructed from timestamps
- Learned propagation windows instead of hand-set SLAs
- Failure-boundary localisation: which hop broke, not just that something did
- Assess Change on any BSS schema before the change window
- Semantic reconciliation for vendor migrations
Synthetic demonstration
Synthetic estate, not a customerSix deliberate defects in a synthetic BSS estate.
Coharyn's demonstration estate (CRM, Product Catalogue, Provisioning, Charging, Billing, Payments; seed 42) is generated with realistic hidden relationships and these deliberate defects. What follows is what Coharyn detects there.
Orphan account
A billing account whose CRM account number matches nothing in CRM.
Relationship coverage below 100% on an undeclared key; orphan rows listed with evidence.
Missing subscriber mapping
A provisioned MSISDN with no billing subscriber and no charging profile.
Broken journey localised at the Provisioning → Billing boundary, outside the learned propagation window.
Discount inconsistency
A discount applied to a subscription whose segment no longer qualifies.
Validated invariant violated; compiled deterministic check raises an anomaly with the offending keys.
Invalid lifecycle state
CRM says TERMINATED while billing still bills ACTIVE.
Cross-system state contradiction; both observations attached as evidence.
Offer mismatch
An active subscription on a product retired from the catalogue.
Referential hypothesis against product_catalog fails for a cluster of rows; cluster characterised.
Cross-system status divergence
Charging allowance never created for a completed order.
Journey stage missing beyond p99 × 1.5 of the learned lag; incident opened with boundary label.
Walkthrough
Discover → Evidence → Assess Change → Blast Radius → Validation → Reconcile
- 01
Discover
Coharyn connects read-only to CRM, Provisioning, Billing and Charging. It profiles 27 tables, finds declared keys and 23 relationships that were never declared (Provisioning has none), and mines candidate rules.
- 02
Evidence
Every relationship carries containment, cardinality and orphan evidence; every rule carries a validation run. Nothing is promoted without passing a test against the data.
- 03
Assess Change
A DBA proposes dropping SUBSCRIBER.CUSTOMER_SEGMENT_ID. Coharyn traces it into discount rules, campaign segmentation, the retention branch of the activation process and a reconciliation rule.
- 04
Blast radius
7 direct and 14 inferred dependencies, 5 invariants, 3 processes, 2 connected systems. Risk CRITICAL, confidence 96%, decision DO NOT EXECUTE YET.
- 05
Validation
Pre-change checks, dependency verification, downstream simulation, reconciliation rehearsal and rollback validation, generated from validated knowledge rather than written by hand.
- 06
Reconcile
Billing → Target Vendor migration: 292 rows in, 292 rows out, and every row in the wrong lifecycle state. Row counts pass; semantic reconciliation blocks readiness.
All figures above are from the controlled synthetic estate and its seeded scenarios. They are not customer results and Coharyn does not claim production telecom deployments. See the example assessment.
Run a Telecom Intelligence Pilot.
Start with the System Intelligence Pilot (USD 15,000) across up to three BSS systems, or the Transformation Intelligence Pilot (USD 25,000) for a vendor migration. Read-only, evidence-backed, fixed scope.