Fiber network operators running IQGeo Network Manager Telecom as their OSP platform can now connect it directly to COS Business Engine. The integration links physical network records to commercial BSS/OSS workflows, with a defined source of truth on each side and no manual data reconciliation between them.
How the Integration Works
The two platforms connect through IQGeo’s Address feature layer, using the IQGeo Address feature ID as the shared key identifier across both systems.
Address import from IQGeo into COS Business Engine
Addresses are pulled from IQGeo and mapped into COS Business Engine. IQGeo is the source of truth. No manual re-entry, no divergence between the GIS record and the BSS address base.
Service location data written back to IQGeo
When a subscriber is activated or a service status changes in COS Business Engine, the relevant attributes are written back to the Address feature layer in IQGeo. Operators get a live commercial view of each address — who is connected, which service is active — directly inside the GIS.
Automatic circuit association
Where a circuit exists in IQGeo linked to an address, its ID and name are automatically mapped to the corresponding Circuit property in COS Business Engine. This removes the manual reconciliation work that typically falls on operations teams managing OSP records and service orders in separate systems.
Bidirectional attribute exchange
Additional properties on the IQGeo Address feature layer can be retrieved by COS Business Engine. Operators surface relevant OSP data within commercial workflows without duplicating records across systems.
Why This Matters
The disconnect between GIS/OSP data and BSS order management is a persistent source of operational error in fiber network operations. When the address record, the circuit record, and the service record live in separate systems with no automated linkage, mistakes compound: provisioning on incorrect addresses, stale service status in field tools, and manual reconciliation during audits.
This integration resolves the structural cause. IQGeo holds the network: physical plant, circuit topology, and address geography. COS Business Engine holds the commercial lifecycle: subscriber sign-up, provisioning, billing, and service management. Both systems stay coherent without either being replaced or subordinated.
For open access and wholesale operators, address accuracy is foundational. Multi-ISP operations depend on clean, unambiguous address records to route orders, provisioning commands, and billing correctly across service providers. A GIS-authoritative address layer connected directly to the BSS eliminates that risk at the source.
Frequently Asked Questions
What is the COS Business Engine and IQGeo integration? It is a native bidirectional integration between COS Business Engine and IQGeo Network Manager Telecom. It links the IQGeo Address feature layer to the COS Business Engine address base, keeping OSP and BSS records coherent without manual data entry.
Which IQGeo product does this integrate with? The integration is built specifically for IQGeo Network Manager Telecom. It uses IQGeo’s Address feature layer as the shared data layer between the two platforms.
Does this require replacing either system? No. COS Business Engine and IQGeo each retain their authoritative role. IQGeo holds the network and physical plant records. COS Business Engine holds the commercial subscriber lifecycle. The integration keeps both in sync.
How are circuits handled? Where a circuit in IQGeo is linked to an address, its ID and name are automatically mapped to the corresponding Circuit property in COS Business Engine. Manual reconciliation between OSP records and service orders is not required.
Is this integration relevant for open access operators? Yes. Multi-ISP environments require clean, unambiguous address records to route orders, provisioning, and billing correctly across service providers. A GIS-authoritative address source connected directly to the BSS reduces that risk at the source.
Where can I learn more about COS Business Engine integrations? See the full integrations overview or contact us to discuss your OSP stack.
