OIConnect: from the Interop-Fibre project to the infrastructure operators’ platform

How a business application built for a group of operators became a product, available as SaaS or on-premise

All the versions of this article: [English] [français]


Originally developed for a group of operators engaged in fibre roll-out, the Interop-Fibre application became OIConnect, IPEOS’s business platform for infrastructure operators. A look back at the road from a client need to a product.

The context: data exchanges to harmonise

As part of large-scale fibre roll-out, a group of operators wanted to harmonise their data exchanges to simplify and speed up technical procedures. Every stakeholder handles the same information — access orders, appointments, after-sales, IPE/CPN files — but with its own systems and processes. IPEOS first answered this need with the Interop-Fibre application: a single platform to manage and standardise interoperability data between network stakeholders.

The challenges met

  • A constantly evolving protocol: the INTEROP’FIBRE standard is regularly updated; the business logic must adjust without a rebuild.
  • A reliable implementation: guaranteeing the consistency and accuracy of exchanged data despite deployment complexity.
  • Multi-stakeholder collaboration: ensuring compatibility between operators, each with its own systems and processes.

From application to product: the birth of OIConnect

The chosen architecture — a modular web platform on a Django back-end, with a responsive dashboard and dynamic business-logic updates — proved itself in the field. IPEOS then industrialised it into a fully-fledged product: OIConnect.

The platform now covers four areas:

  • Repository & mapping — PRDMs, PMs, links, PBOs, buildings, PTOs and optical routes in a structured base, with interactive mapping.
  • End-to-end production — Info PM, PB, link and access orders; FTTH, FTTE and STOC appointments, tracked at every step.
  • OI–OC interoperability — IPE/CPN files, FTP, REST APIs, OAPC, operator change and after-sales, compliant with the INTEROP’FIBRE protocol.
  • Operations & steering — tracking of orders, incidents and indicators, with rights configurable per module.

The results

  • A unified process: operators rely on a centralised repository that standardises exchanges and improves coordination.
  • Measurable time savings: automating exchange files frees technical teams from manual data handling.
  • A sustainable product: designed to evolve with the protocol, OIConnect is now deployed as SaaS or on the operator’s own infrastructure, with support from the IPEOS team.

The IPEOS expertise mobilised

This trajectory — a custom development turned into a product — illustrates IPEOS’s approach: business web applications built on Django, implementation of standardised exchange protocols, data-flow automation and long-term support. Browse our business-platform expertise.

Your network deserves its platform

You are an infrastructure operator and want to see OIConnect applied to your network? Request a demo or get a quote.

About the author

Olivier Watté

See also

Public WiFi Deployment: A...

Under the European WIFI4EU program, a...

City-Connect : Modernization

As part of a modernization project...

Interop-Fibre App : Standardiz

In the drive to expand fiber optic...