Controlled fulfilment across business systems, inventories, operational platforms, and heterogeneous network domains.
Bonyan System works as a systems integrator and implementation partner within operator-controlled infrastructure. We connect BSS, OSS, inventories, activation platforms, domain controllers, network elements, and operational teams so that each order has a traceable path from acceptance to completion.
From order to active service
One controlled fulfilment state
Commercial orders often cross multiple systems and teams. The implementation keeps dependencies, network actions, evidence, and exceptions visible throughout the journey.
01
Confirm and validate
Check customer, product, location, eligibility, serviceability, commercial data, and scheduling before network changes begin.
02
Decompose and reserve
Translate products into service and resource work, then allocate the identifiers, ports, profiles, policies, devices, and capacity required by the agreed scope.
03
Orchestrate and activate
Sequence dependencies, parallelize independent work, coordinate approvals, and send validated actions to the relevant service and network domains.
04
Verify and synchronize
Evaluate acknowledgements, read-back, tests, inventory, and assurance evidence before updating order, inventory, billing-readiness, and operational states.
Manage validation, dependencies, priorities, scheduled work, parallel tasks, approvals, external work orders, and completion rules.
02
Multi-vendor activation
Keep domain- and vendor-specific behavior behind controlled adapters instead of embedding it throughout upstream business systems.
03
Resource lifecycle
Coordinate the logical and physical resources required by the selected services, with allocation, reservation, state, and ownership made explicit.
04
Failure handling
Use durable state, correlation, timeouts, safe retries, exception queues, controlled resubmission, and rollback or compensation where technically appropriate.
05
Verification and reconciliation
Compare intended, recorded, and observed states using available acknowledgements, read-back, tests, events, inventory, and assurance indicators.
06
Operational control
Provide searchable execution records, correlation identifiers, audit history, dashboards, alerts, security boundaries, and recovery procedures.
07
Low-touch fulfilment
Automate the normal path while retaining human control for approvals, field activity, security-sensitive work, and genuine exceptions.
08
Phased modernization
Use coexistence flows, common models, adapters, staged cutovers, reconciliation, and rollback planning to replace legacy components safely.
Integration landscape
Separate commercial intent from network commands
A canonical service model and adapter layer can reduce point-to-point dependency. Exact standards, protocols, and interface versions are selected according to the connected systems and approved architecture.
Northbound
Orders and business context
Sales channels, CRM, product and order management, partner portals, MVNO systems, scheduling, and operational workflows.
Southbound
Resources and live-service actions
Service and resource inventories, activation platforms, network management, domain controllers, network elements, billing, charging, devices, and assurance.
APIsTM Forum patternsRESTSOAPJMSeventssecure file exchangeapproved vendor interfaces
Synchronous flows suit simple actions requiring an immediate response. Asynchronous flows suit long-running orders, external dependencies, field activity, and callback- or event-based completion.
Selected by project scope
Service and network domains
Coverage depends on the service portfolio, available interfaces, vendor constraints, security requirements, and operational ownership.
Mobile services
Subscriber activation, numbers, SIM or eSIM association, voice, messaging, data, roaming, access profiles, policy, barring, and service-package changes where supported by the connected platforms.
Fixed and broadband
Access and account activation, ports, fibre or DSL profiles, customer equipment, authentication, addressing, VLANs, quality of service, and service changes.
Enterprise connectivity
Dedicated internet, Ethernet, Layer 2 or Layer 3 VPNs, multi-site connectivity, routing, addressing, bandwidth, quality of service, and managed policies.
IoT and value-added services
Batch or individual onboarding, connectivity profiles, device groups, private access profiles, messaging, voicemail, short codes, content access, and coordinated bundled services.
Delivery approach
A phased route to production
01DiscoverOrder journeys, models, systems, exceptions, ownership, and acceptance criteria.
02DesignTarget architecture, workflow state, topology, integration contracts, security, and audit.
03BuildPlatform configuration, workflow logic, adapters, interfaces, monitoring, and controls.
04TransitionData and process mapping, coexistence, rehearsals, reconciliation, cutover, and rollback.
05ProveFunctional, integration, failure, recovery, data, performance, security, and readiness testing.
06OperateHandover, incident analysis, controlled change, workflow tuning, and knowledge transfer.
Practical questions
Provisioning and activation FAQ
What is the difference between provisioning and activation?
Provisioning allocates and configures the services and resources required by an order. Activation applies the changes to a live network or service platform. Complete fulfilment includes both and verifies the result before closure.
Can existing legacy provisioning systems be retained?
Yes, where interfaces and operational constraints allow it. Adapters and orchestration can support coexistence while target capabilities are introduced in controlled stages.
How is multi-vendor provisioning implemented?
A common service model and workflow call domain-specific adapters. Each adapter translates a controlled service action into the interface and data required by that vendor system.
How is successful activation verified?
Evidence can include command acknowledgements, configuration read-back, inventory comparison, service tests, network or device events, and assurance indicators. Completion rules are defined per service.
How can this support MVNO and telecom B2B services?
MVNO flows can connect partner channels with host-operator subscriber, number, policy, charging, and assurance processes. B2B orchestration can coordinate sites, links, devices, policies, and dependencies under one enterprise order.
