COS Systems Knowledge Hub | Field Operations | April 2026
Work Order Management for Fiber Networks
Work order management is the operational backbone of fiber deployment. It controls what technicians do, in what sequence, at which address — and whether the outcome is logged, verifiable, and tied to provisioning. For fiber operators scaling hundreds or thousands of activations, the difference between disciplined and ad-hoc work order handling compounds quickly.
What Is a Work Order in a Fiber Network?
A work order is a structured task record scoped to a specific job at a specific address. It defines the sub-tasks required, the assignees responsible, the documentation to collect, and the status that triggers the next step in the activation chain.
In COS Business Engine, work orders are used to support the process of delivering a service to a customer. Once an object is set to In Deployment, a work order is automatically created to connect and check that object. The work order holds all actions required to bring a functioning service to the customer — including physical installation, ONT setup, testing, and sign-off.
Work orders are distinct from service tickets. A ticket addresses a fault or customer request post-activation. A work order governs the installation itself, with a defined start state (address in deployment) and a defined end state (service ready to activate).
Why Fiber Deployments Require Structured Work Orders
Fiber installation is not a single-step job. A typical FTTH activation involves civil crew work on the distribution network, a drop installation to the premises, ONT mounting and cabling, light level testing, and provisioning confirmation. These steps may involve different crews, different skill sets, and different scheduling windows.
Without a structured work order, this sequence depends on verbal handoffs, spreadsheets, and tribal knowledge. Each gap is a potential missed step. Incomplete work orders lead to truck rolls with missing information, on-site delays, and repeat visits. In a scaled deployment, repeat truck rolls are one of the highest preventable costs an operator carries.
Structured work orders eliminate the ambiguity. Every technician arrives at a job knowing exactly what to do, in what order, and what to document before closing the work order.
What a Fiber Work Order Contains
Work order templates are set up by the operator to organize the required tasks. Multiple templates can be created to accommodate various installation types or work required for an object. Each template can be customized to specific installation requirements, enabling efficient management of diverse tasks across projects.
A standard FTTH work order typically includes sub-tasks across these categories:
Physical Installation
Fiber drop from the distribution point to the premises. Conduit or aerial entry. ONT mounting and cabling. Completion photo documentation.
Testing and Verification
Light level measurement at the ONT. Speed test after provisioning. Results logged directly in the system from the field technician’s mobile device.
Provisioning Trigger
Task completion fires the provisioning event in the BSS/OSS. Service is activated without a manual step from the NOC.
Customer Communication
Status updates are sent to the customer portal as the work order progresses. Customer is notified when the service is ready to activate.
Upon installation completion, light levels and speed test results are saved automatically, providing a reliable reference for future troubleshooting and SLA verification. This installation record — effectively a birth certificate for the connection — is tied permanently to the address object in the BSS/OSS.
Assigning Work Orders Across Operator Staff and Contractors
Most fiber operators deploy a mix of internal crews and external contractors, particularly during aggressive rollout phases. Tasks in a work order can be assigned to different assignees — for example, if both the operator’s staff and a contractor will be involved in the installation process.
This split-assignment model is critical for accountability. When a task is assigned to a specific individual or crew, the work order system records who completed it, when, and what was documented. If a job requires a return visit, the history is clear. There is no ambiguity about which crew touched what.
Automated Work Order Creation from Deployment Triggers
Manual work order creation does not scale. When a project area enters the “In Deployment” phase, work orders are automatically created for all orders. This eliminates the administrative step of creating individual work orders for each address and ensures nothing is missed when a batch of addresses moves into the active build phase.
End-to-end automation ensures that once an order is placed, a work order is generated automatically, required materials are identified, and tasks are routed to the right crew. Dispatch does not depend on email threads or last-minute clarifications — it is driven by structured data that follows the order from the start.
In COS Business Engine, this trigger is tied to the object status model. Addresses exist as objects in the system, each with a tracked status. When the operator moves an area from surveyed to in-deployment, the platform creates work orders across all affected objects in batch — no manual step required.
The Field Technician Interface
Installers access a portal to view their tasks and document work directly in the system via mobile or tablet. This mobile interface removes the dependency on paper forms, end-of-day reporting, and back-office data entry. Technicians log task completion, upload photos, record test results, and close the work order from the field — in real time.
Technicians use a mobile interface to access real-time work instructions, mark tasks as completed, and upload documentation such as photos or notes. This portal allows for progress tracking during the installation process.
Real-time field data has downstream value beyond the individual work order. Operations teams see live deployment progress. Customer communications are triggered by actual status changes, not manual updates. And the installation record that feeds future network troubleshooting is accurate because it was captured at the point of work, not reconstructed afterward.
COS FSM: Field Service Management Built for Fiber Scale
COS Business Engine provides work order management, scheduling, and a field technician interface as part of the core BSS/OSS. For operators who need a dedicated field service management layer — with advanced scheduling, route optimization, and contractor management — COS FSM extends those capabilities as a standalone product or integrated add-on.
COS FSM streamlines field operations with skill-based scheduling, self-service appointment booking, and route optimization. It can be used standalone or together with COS Business Engine to go from customer order to completed install with minimal manual handling.
COS FSM supports any type of work order, with workflows defined to match the operator’s processes. Skill-based assignments route tasks based on field technicians’ skills. Customers can pick a suitable time based on technician availability, while the actual installers are assigned closer to appointment time to ensure minimal drive time and efficiency.
When COS FSM is integrated with COS Business Engine, the full activation chain becomes automated: customer order triggers a work order, the work order enters the scheduling queue, a technician is dispatched, the job is completed and documented in the field, and provisioning fires on task close. No manual handoff at any stage.
Work Order Management in Open Access Networks
Open access deployments add a structural layer that retail ISP operations do not face. The network owner is responsible for the physical infrastructure. The ISP is responsible for the service. A work order for an open access installation must track physical completion by the network operator and logical service activation by the ISP as two separate status events.
COS Business Engine is designed for this model. The platform manages the full lifecycle of an open access network, tracking physical installation status per address and notifying the relevant ISP when the infrastructure is ready for service activation. The system monitors installation status per address and informs customers when services are ready to be activated — including for post-deployment connections in already built areas.
For wholesale operators running multi-ISP networks, COS Wholesale Engine complements COS Business Engine by handling the ISP-layer billing and reporting that follows activation. Work order completion feeds the activation record; the activation record feeds the billing cycle.
Connecting Work Order Completion to Provisioning and Billing
A work order system that operates in isolation from provisioning and billing creates a gap. Field teams close jobs; the back office re-enters data to activate service and start billing. That gap introduces errors, delays, and revenue leakage.
In an integrated BSS/OSS, work order completion is a system event, not just a status flag. Thanks to COS Business Engine’s integrations, services are automatically activated once the CPE is installed. Customers choose and activate services directly through the customer portal, without manual handling from the network or service providers.
Scheduling and planning integrates with the network management system, enabling automatic updates and synchronization across network elements and provisioning tasks. This reduces manual intervention, minimizes errors, and improves efficiency, ensuring smoother and faster deployments.
Billing follows the same logic. When provisioning confirms service is live, the billing cycle starts. No manual trigger, no lag between activation and first invoice. The work order that began with a deployment trigger ends with a live, billing-active service at the address.
Frequently Asked Questions: Work Order Management for Fiber
What is a work order in a fiber network?
A work order in a fiber network is a structured task record assigned to a technician or crew for a specific job at a specific address. It contains sub-tasks, required documentation, and status checkpoints for activities such as fiber drop installation, ONT setup, light level testing, and service activation. In BSS/OSS platforms like COS Business Engine, work orders are generated automatically when an address moves into deployment status.
How are work orders generated automatically in fiber BSS/OSS platforms?
When an operator sets an address or project area to In Deployment status in the BSS/OSS, the platform creates a work order automatically against that object. The work order inherits the applicable template, pre-populates sub-tasks, and queues for scheduling. No manual order entry is required. COS Business Engine uses this trigger-based approach to connect customer orders directly to field dispatch.
What is the difference between a work order and a field service management system?
A work order is a single record defining what needs to be done at a location. A field service management system is the platform that creates, schedules, dispatches, tracks, and closes work orders at scale. FSM adds skill-based routing, route optimization, real-time status visibility, and mobile access for technicians on top of the underlying work order structure.
Can work orders be assigned to contractors as well as internal crews?
Yes. Work order tasks can be split across multiple assignees. Internal technicians and external contractors can each hold different sub-tasks within the same work order. This is standard in FTTH deployments where operators use a mix of their own crews and subcontractors for drops, ONT installation, and network testing.
What documentation is captured when a work order is completed?
At completion, technicians log light level measurements, speed test results, photos, and task sign-off directly from a mobile device. COS Business Engine stores this as a permanent installation record tied to the address. This record is available for future troubleshooting, SLA verification, and network audits.
How does work order completion trigger service provisioning?
In an integrated BSS/OSS, completing the relevant work order task triggers automatic ONT provisioning. The service defined in the customer’s order is activated without a manual step from the network operations center. COS Business Engine handles this integration with provisioning vendors including Adtran, Nokia, and Calix.
How does work order management differ in open access fiber networks?
In open access networks, a single work order may relate to infrastructure the network owner installs, while service activation is handled by the ISP. The BSS/OSS must track status across both layers — physical installation by the network operator and logical service activation per ISP — without conflating the two. COS Business Engine and COS Wholesale Engine are both designed to manage this separation cleanly.
COS FSM and COS Business Engine manage work orders, field dispatch, and provisioning in a single integrated platform. See how fiber operators use COS to automate the full installation chain.
Book a Demo
COS Systems förvärvar Fiber Flow och inleder ett strategiskt partnerskap med Vinnergi, vilket skapar Nordens ledande plattform för fiberoperatörer
Förvärvet skapar Nordens starkaste erbjudande för fiberoperatörer genom att kombinera Vinnergis breda expertis inom utveckling och drift av fibernät med COS Systems ledande mjukvaruplattform som stärks ytterligare genom förvärvet av Fiber Flow.
Umeå, Sverige, 8 september 2026 — COS Systems och Vinnergi inleder ett strategiskt partnerskap. Som en del av affären förvärvar COS Systems mjukvaran Fiber Flow från Vinnergi och dess dotterbolag Bitvis. Fiber Flow provisionerar idag över 400 000 aktiva abonnenter i närmare 30 nät i Norden.
Aktiva abonnenter som provisioneras i Fiber Flow
Nordiska nät som använder plattformen
Produkter i COS portfölj, inklusive COS Fiber Flow
Därför går COS Systems och Vinnergi ihop
Bolagen kommer från varsitt håll. Vinnergi är ett ledande konsultbolag inom energi, fastighet och telekom som säljer och implementerar Fiber Flow på den nordiska marknaden, med en särskilt stark position i Sverige. COS Systems är ett renodlat mjukvarubolag med rötterna i Umeå som vuxit globalt och idag är den ledande BSS/OSS-leverantören för öppna nät i Nordamerika för både kommunala fibernät och de största operatörerna, s.k. Tier 1:s.
Så påverkas Fiber Flows kunder
Efter affären tar COS Systems över ansvaret för att vidareutveckla Fiber Flow som en del av den bredare plattformen. Vinnergi fortsätter att fronta kunderna med försäljning, implementation, integration och support. I samband med partnerskapet får Vinnergi tillgång till hela COS Systems portfölj.
Om COS Systems
COS Systems levererar en molnbaserad BSS/OSS-plattform för stadsnät, tjänsteleverantörer och kommunikationsoperatörer. Plattformen är modulariserad och integreras med kringliggande system för att automatisera driften av bredbandsnät. Med moduler för allt från dörr-till-dörr försäljning, tjänsteportal och kundportal och installationer till ärendehantering, automatiserad tjänsteaktivering och fakturering erbjuder COS en komplett lösning för att optimera driften av fibernät. Resultatet är ökad försäljning, minskade driftskostnader och nöjdare kunder. Portföljen omfattar COS Business Engine, COS Wholesale Engine, COS FSM, COS Prospector, COS Marketplace och numera även COS Fiber Flow.
Om Vinnergi
Framtidsintegratören Vinnergi är en svensk teknikkonsult som bygger smartare infrastruktur inom telekom, energi och fastighet. Vi tar ansvar hela vägen, från beslut till drift. Bland kunderna finns nätägare, mobiloperatörer, energibolag, kommuner och fastighetsägare. Verksamheten är organiserad i fyra affärsområden: Communicate för fasta och mobila nät, Power för elkraft och förnybar energi, Living för fastighetsteknik och fysisk säkerhet, samt Construction för totalentreprenad inom samhällskritisk infrastruktur. Vinnergi har huvudkontor i Linköping och kontor på ett tjugotal orter. Koncernen omsätter cirka 900 miljoner kronor och sysselsätter över 600 personer. Bolaget är delvis medarbetarägt och huvudägare är Polaris.
Vanliga frågor
Vad har COS Systems förvärvat?
COS Systems har förvärvat mjukvaran Fiber Flow från Vinnergi och dess dotterbolag Bitvis. Fiber Flow är en BSS/OSS-plattform för fiberoperatörer och provisionerar idag över 400 000 aktiva abonnenter i närmare 30 nät i Norden.
Vad förändras för Fiber Flows kunder?
Ingenting förändras i den dagliga driften. Vinnergi fortsätter att fronta kunderna med försäljning, implementation, integration och support. Samma kontaktpersoner, samma avtal och samma support gäller som tidigare.
Vem vidareutvecklar Fiber Flow nu?
COS Systems tar över ansvaret för att vidareutveckla Fiber Flow som en del av den bredare plattformen.
Är det här ett förvärv av Vinnergi?
Nej. Vinnergi fortsätter som fristående teknikkonsult. COS Systems har förvärvat mjukvaran Fiber Flow. Bolagen har inlett ett strategiskt partnerskap där Vinnergi får tillgång till hela COS Systems portfölj.
Vilka produkter ingår i COS Systems portfölj?
Portföljen omfattar COS Business Engine, COS Wholesale Engine, COS FSM, COS Prospector, COS Marketplace och numera även COS Fiber Flow.
Ladda ner pressmeddelandet (PDF)
Kontakt
Mikael Philipsson, VD
mikael.philipsson@cossystems.com
+46 70 843 10 43
Pierre Wallgren, VD
pierre.wallgren@vinnergi.se
+46 70 939 69 64
COS Systems Expands Global Fiber Software Leadership with Fiber Flow Acquisition and Strategic Partnership with Vinnergi
The transaction creates the Nordic region’s leading software platform for broadband operators combining Vinnergi’s network expertise and local delivery organization with COS Systems’ cloud-based BSS/OSS and network automation platform.
West Palm Beach, FL, September 8, 2026 — COS Systems and Vinnergi today announced a strategic partnership. As part of the agreement, COS Systems has acquired the Fiber Flow software platform from Vinnergi and its subsidiary Bitvis. Fiber Flow is one of the major BSS/OSS platforms in the Nordics and manages more than 400,000 active subscribers across nearly 30 networks in the Nordic region.
Active subscribers managed on Fiber Flow
Nordic networks running the platform
Products in the COS portfolio, including COS Fiber Flow
What Fiber Flow adds to the COS Systems platform
Fiber Flow strengthens COS’s current capabilities within network management and provisioning, especially for Active Ethernet access equipment. Today the dominant technology on most markets is PON, but there are still a lot of Active Ethernet networks deployed. COS’s capability to bring full automation to these networks and streamline a transition from Active Ethernet to PON is greatly enhanced with the acquisition.
Why COS Systems and Vinnergi are partnering
The two companies bring complementary strengths to the partnership. Vinnergi is a leading Swedish engineering and technology consulting company with extensive experience in fiber network development and operations. It sells and implements Fiber Flow throughout the Nordic market and has a particularly strong position in Sweden.
COS Systems is a dedicated software company founded in Umeå that has expanded globally. Today, COS Systems is a leading BSS/OSS provider in North America, serving municipal broadband networks, regional service providers and major Tier 1 carriers.
What changes for Fiber Flow customers
Following the transaction, COS Systems will assume responsibility for the continued development of Fiber Flow as part of its broader software platform. Vinnergi will remain the customer-facing partner in the Nordic market, providing sales, implementation, integration and support. Through the partnership, Vinnergi will also gain access to the full COS Systems product portfolio.
About COS Systems
COS Systems provides a cloud-based BSS/OSS platform purpose-built for broadband operators. Operators choose COS Business Engine to run full retail ISP operations: subscriber management, billing and provisioning; or COS Wholesale Engine to orchestrate multi-provider Open Access networks. COS FSM and COS Prospector extend the platform with automated field service management and door-to-door demand aggregation, so operators can sell faster, scale better, and automate everything. The portfolio comprises COS Business Engine, COS Wholesale Engine, COS FSM, COS Prospector, COS Marketplace and now also COS Fiber Flow.
About Vinnergi
Vinnergi is a Swedish technology consultancy building smarter infrastructure across telecom, energy and property. The company takes end-to-end responsibility, from decision to operation. Customers include network operators, mobile operators, energy companies, municipalities and property owners. The business is organised into four areas: Communicate for fixed and mobile networks, Power for electricity and renewable energy, Living for building technology and physical security, and Construction for turnkey delivery of critical infrastructure. Vinnergi is headquartered in Linköping with offices in around 20 locations. The group turns over approximately SEK 900 million and employs more than 600 people. The company is partly employee-owned; its majority owner is Polaris.
Frequently asked questions
What has COS Systems acquired?
COS Systems has acquired the Fiber Flow software platform from Vinnergi and its subsidiary Bitvis. Fiber Flow is a BSS/OSS platform for broadband operators. It manages more than 400,000 active subscribers across nearly 30 networks in the Nordic region.
What changes for existing Fiber Flow customers?
Nothing changes in day-to-day operations. Vinnergi remains the customer-facing partner in the Nordic market and continues to provide sales, implementation, integration and support. Points of contact and agreements stay the same.
Who develops Fiber Flow now?
COS Systems assumes responsibility for the continued development of Fiber Flow as part of its broader software platform.
Is this an acquisition of Vinnergi?
No. Vinnergi remains an independent technology consultancy. COS Systems acquired the Fiber Flow platform only. The two companies have entered a strategic partnership, and Vinnergi gains access to the full COS Systems product portfolio.
Does COS Systems support Active Ethernet provisioning?
Yes. Fiber Flow provisions Active Ethernet access equipment directly, and that capability now belongs to COS Systems. PON dominates new builds, but large Active Ethernet estates remain in service and still have to be operated. The acquisition brings automated Active Ethernet provisioning into the COS platform alongside PON, so an operator can run both from one system and migrate from Active Ethernet to PON without changing platforms.
What products make up the COS Systems portfolio?
The portfolio comprises COS Business Engine, COS Wholesale Engine, COS FSM, COS Prospector, COS Marketplace and now also COS Fiber Flow.
Download the press release (PDF)
Press contacts
Mikael Philipsson, CEO
mikael.philipsson@cossystems.com
+46 70 843 10 43
Pierre Wallgren, CEO
pierre.wallgren@vinnergi.se
+46 70 939 69 64
ISP Consolidation Whitepaper: Consolidate Operations, Keep Local Brands
Most broadband acquisitions merge everything at once. Network, systems, staff and brand. The cost savings arrive late. The churn arrives immediately.
This whitepaper sets out a different sequence. Consolidate network operations first, because that is where duplicated cost sits. Leave the acquired brand, its customer relationships and its billing stack running, because that is where revenue sits. Migrate systems later, per network, on the acquirer’s timetable.
It is written for infrastructure investors, acquiring ISPs and the operators being acquired.
Why full-stack integration costs more than it saves
Full migration of one ISP into another is slow, expensive and a management distraction. Plans run optimistic. Costs run over. Savings land later than modeled.
Two costs are routinely underpriced in the model. The first is brand equity. A local provider’s name carries trust built over years, and that trust does not transfer to a national brand on the day the sign changes. The second is migration churn. Forced moves require retention pricing to hold customers, and they still lose some.
Both costs land at the worst possible moment. Revenue dips exactly when the deal model says it should rise.
A better playbook: consolidate operations, keep the brands
Separate the layers. Take cost out of network operations. Protect revenue in the customer relationship. The whitepaper covers five moves.
Unify network operations
One shared NOC, one set of processes and tools. Immediate cost reduction. Customer-facing teams stay small, local and unchanged.
Keep each billing stack at first
No rip-and-replace on day 1. Staff keep the tools they know. Systems migrate in a controlled sequence later.
Lift take-rates through choice
Multiple ISP brands on shared infrastructure means cross-sell across every market in the portfolio. More choice raises penetration.
Shorten time to market
Deferring the customer and IT migration means going live sooner. Revenue starts earlier while operational cost falls in the background.
Profitability improves twice
First from retained revenue and cross-sell. Then from phased system consolidation that lowers unit cost without a churn event.
What an open access structure gives the acquirer
Open access decouples infrastructure from services. Multiple ISP brands run on a single network, with clean separation between the network owner and the service provider.
That structure serves the buyer’s thesis directly. Shared infrastructure and shared field operations lower operating cost per paying subscriber and raise utilization of capital already sunk into the build. Keeping the brands avoids the day 1 revenue shock. Deferring the IT migration protects cash flow.
European operators have run networks this way for two decades. North America is applying the same model to a different problem: one operator, many acquired networks.
Who should read it
Infrastructure investors evaluating a roll-up, and modeling what penetration the portfolio can reach and how fast.
Acquiring ISPs deciding how much of an acquired operator to absorb, and in what order.
Operators being acquired who want a case for keeping their brand, their team and their customer relationships intact.
Get the whitepaper
ISP Consolidation Success: Streamlining Operations While Preserving Local Brands. PDF, no cost.
Frequently asked questions
Can an acquired ISP keep its own brand and billing system?
Yes. A wholesale layer above the acquired network takes over provisioning, ticketing and wholesale settlement. The acquired operator’s retail brand, customer portal and billing stack keep running. System consolidation then happens in phases rather than as one cutover.
Why do broadband acquisitions lose customers after integration?
Most integration churn traces to billing and support failure at cutover. Customers receive an unfamiliar bill or an incorrect plan, or reach an agent who cannot see their record. Forced brand and portal changes compound it by altering the subscriber experience at the same moment.
Does keeping multiple ISP brands raise operating cost?
Not where the cost actually sits. Duplicated cost is concentrated in network operations, field operations and licensing, and those consolidate under a shared NOC regardless of how many retail brands sit above. Brand and customer relationship are cheap to keep and expensive to replace.
How does multi-brand operation affect take-rate?
Multiple providers on one network give the subscriber a real choice of package, price point and provider. That raises the share of passed premises that connect, which is the financial case for consolidation in the first place.
What is an open access network operator?
An open access network operator owns and runs the fiber infrastructure and sells wholesale access to multiple retail service providers. It does not sell broadband subscriptions itself. Responsibility for the network and for the customer relationship sit in separate organizations.
Which COS product supports multi-network consolidation?
COS Wholesale Engine. It manages service locations, multi-vendor provisioning, RSP API integrations and wholesale billing across acquired networks, without forcing migration off the systems already running. COS Systems has been certified to ISO 27001 since May 2026.
Read more on consolidation
American Broadband Consolidation: The Investment Playbook Reshaping Fiber Networks — the strategic playbooks by operator type, and the three paths open to an ISP.
What’s Really Driving the Biggest Moves in American Broadband — the 11 investment theses behind the current wave of deals.
The Network Utilization Strategy — why penetration, not passings, decides the return.
Altnet Consolidation: The Integration Bill Nobody Priced In — the same problem in the UK market, with published integration timelines.
To discuss how this applies to a specific portfolio, get in touch.
Altnet Consolidation: The Integration Bill Nobody Priced In
Consolidation & M&A
By Ashley Poling, VP Business Development, COS Systems · 2 September 2026
UK altnet consolidation is not slowing because fibre stopped being valuable. It is slowing because buyers cannot absorb what they acquire.
AlixPartners put it in one line this summer: anyone can buy fibre, but almost no one can integrate it. That diagnosis was written for the American market. It describes the UK more precisely.
Why is UK altnet consolidation slowing down?
The capital is available and the assets are cheap. The constraint has moved to operations.
CityFibre put over 400 roles at risk in January 2026 and a further 200 in July, citing consolidation moving slower than anticipated. Netomnia put around 100 staff on notice in the same month. Both are consolidators, not targets. Neither is short of funding.
ISPreview’s tracker counts 3 announced deals in 2026 against 6 in 2025. Valuation disagreement is the reason usually given. Absorption capacity is the reason usually left out.
What does the take-up gap actually cost a consolidator?
Ofcom’s Telecoms Access Review statement of 17 March 2026 records altnet take-up averaging around 18% against approximately 38% for Openreach. That 20-point gap is the whole thesis of consolidation. Buy the passings, raise the penetration, take the margin.
The gap is also wider than the average suggests. Point Topic’s Q1 2026 figures put Toob at 36% and Community Fibre at 32%, with Netomnia at 17% and Trooli at 8%. G.Network was serving roughly 25,000 customers across a network reported at 255,000 premises when it filed for administration in January 2026.
Enders Analysis puts sustainable profitability somewhere near 40% penetration. The largest altnets lost £1.5bn in 2024 on around £9bn of debt, with financing costs averaging 121% of revenue.
So the acquirer’s business case is a penetration case. Every month of integration delay is a month the acquired network keeps running at its old take-up.
How long does it take to integrate an acquired altnet?
Published UK evidence gives a range of roughly 7 to 20 months, and only for the customer-facing layer.
CityFibre reported integrating Connexin within 7 months. FullFibre merged Zzoomm’s operational, commercial and technology systems inside about 9 months, retiring the BeFibre brand and migrating those customers. Netomnia agreed to buy Brsk in June 2024; Brsk customers were not notified of the YouFibre migration until February 2026, with phased migration running through the first half of that year.
Freedom Truespeed took the honest route and said so publicly. On completion in April 2026 the group stated there would be no immediate change to service delivery, with systems, processes and teams integrated over time.
Three brands, three timetables, one platform question underneath all of them.
Why does OSS/BSS decide the timetable?
Because the network merges on paper long before the systems do.
Two altnets with the same technology rarely share a product catalogue, a service definition, an address model or a provisioning workflow. PXC described its own altnet onboarding problem as a patchwork quilt of disparate technologies, varying OSS/BSS maturity and inconsistent taxonomies. That is a wholesale aggregator describing the same heterogeneity a buyer inherits on day one.
INCA’s Wholesale Standards Initiative exists for this reason. Max Fernando, who chairs it, framed the problem directly: retail ISPs have pointed out the costs and complexity associated with needing to onboard new networks.
Standardising the wholesale interface helps the ISP above. It does nothing for the operator holding 4 incompatible back offices below.
What does the buyer’s own stack have to absorb?
Most diligence examines the target. The harder question is what the buyer can run.
Three things have to work on the first day after cutover. Provisioning has to reach the acquired network without two systems both believing they control a live service. The first bill after integration has to reach the right customer on the right plan. Support has to see plan, order and network status for a subscriber whose records came from somewhere else.
Billing is where this becomes expensive. Recon Analytics, analysing 1.47 million US survey responses between 2022 and 2025, found that 35.8% of customers who called about a billing issue intended to leave, against 18.8% who did not need to call. Migration cutover is exactly when billing breaks.
Churn at the moment of integration is the most expensive churn there is. It arrives precisely when the penetration case is supposed to start paying.
Can you consolidate systems without migrating subscribers?
Yes, and the sequencing is the entire argument.
Rip-and-replace treats cost consolidation and revenue protection as one project. They are not. Cost sits in duplicated operations, licences and teams. Revenue sits in the subscriber relationship: the brand they signed up with, the customer portal they log into, the bill they recognise.
A wholesale layer above the acquired networks separates the two. The acquired operator keeps its brand and its customer portal. Its billing stack keeps running. Provisioning, ticketing and wholesale settlement move first, because those are invisible to the subscriber and expensive to duplicate. Subscriber migration happens later, per network, on the buyer’s timetable.
Profitability then improves twice. First from retained revenue and cross-sell across every brand in the group. Then from phased system consolidation that lowers unit cost without a churn event.
This is not a new mechanism. Running many service providers over shared infrastructure, with clean separation of commercial and operational responsibility, is how Nordic municipal networks have worked for 2 decades. Consolidation reverses the direction: 1 operator, many networks. The machinery is the same.
What consolidators should ask before the next deal
The CMA’s Phase 2 statutory deadline on nexfibre and Substantial falls on 15 December 2026. That decision shapes whether the UK ends with 3 wholesale platforms or 2. Either way, the deals continue and the tail of roughly 80 altnets keeps shrinking.
One question separates buyers who compound from buyers who stall. Not what is it worth. How many networks can we run before something breaks?
That number is a capability, and it can be built before the next term sheet.
COS Wholesale Engine is the wholesale layer described above. It sits over acquired networks as a normalisation layer for provisioning, ticketing, wholesale billing and reporting, without forcing migration off the systems already running. It is in live production with wholesale operators in North America, and COS Business Engine runs live operations for broadband operators in Sweden and Finland. COS Systems has been certified to ISO 27001 since May 2026.
See how COS Wholesale Engine handles multi-network operations
The same argument, applied to the US market and the brand and take-rate case behind it, is set out in full in our whitepaper: ISP Consolidation Success: Streamlining Operations While Preserving Local Brands.
Frequently asked questions
What is post-acquisition OSS/BSS integration?
Post-acquisition OSS/BSS integration is the work of making an acquired network’s operational and business support systems function alongside the buyer’s own. It covers provisioning, service activation, ticketing, billing and reporting. It is usually the longest task in a broadband merger and the one that determines when synergies arrive.
How long does altnet integration take in the UK?
Published UK examples range from roughly 7 months to over 20. CityFibre reported integrating Connexin within 7 months. Netomnia’s acquisition of Brsk was agreed in June 2024, with customer migration to YouFibre beginning in early 2026. Timelines depend on how far subscriber migration is attempted alongside system consolidation.
Why do broadband acquisitions lose customers after integration?
Most integration churn traces to billing and support failure at cutover. Customers receive an unfamiliar bill, an incorrect plan or a support agent who cannot see their record. Forced brand and portal migration compounds this by changing the subscriber experience at the same moment.
Can an acquired ISP keep its own brand and billing system?
Yes. A wholesale layer above the acquired network can take over provisioning, ticketing and wholesale settlement while the acquired operator’s retail brand, customer portal and billing stack continue to run. System consolidation then happens in phases rather than as a single cutover.
What is the altnet take-up gap?
The altnet take-up gap is the difference between the proportion of passed premises connected on altnet networks and on Openreach. Ofcom’s Telecoms Access Review statement of March 2026 recorded around 18% for altnets against approximately 38% for Openreach. Closing that gap on acquired networks is the core financial case for consolidation.
How many altnets are left in the UK?
Around 80 remain active, from roughly 100 at the 2023 peak, according to ISPreview’s consolidation tracker and KPMG’s 2025 analysis. No regulator publishes an authoritative count. Analysts including Enders and KPMG expect the market to settle around Openreach, VMO2/nexfibre, CityFibre and a tail of smaller and niche operators.
COS Systems at Connected Britain 2026
COS Systems CTO Sajan Parikh takes this argument to the panel “Making consolidation a reality: integration and value creation” in Theatre 2 on 10 September at 12:40 BST. Read the announcement.
How to Run a Fiber Demand Campaign: From Territory Map to Build Decision
Last updated: June 2026 · Maren Buchmüller, Head of Marketing, COS Systems
A fiber demand campaign is how a network operator validates subscriber interest before committing to construction. Operators map a target build area, deploy a field sales team to canvass it door-to-door, and track take rate against a pre-set threshold. COS Prospector manages every stage of the campaign; COS Business Engine converts the results into a build decision.
What Is a Fiber Demand Campaign?
A fiber demand campaign is a pre-construction sales process. The operator defines a geographic build area, sends reps to canvass every address in it, and measures how many households or businesses commit to subscribing at a given price. That commitment rate — the take rate — is compared to a financial threshold. If take rate meets the threshold, the build is viable. If not, the operator adjusts the area or the approach before spending on construction.
The model exists because fiber infrastructure is capital-intensive and difficult to reverse. Demand campaigns replace speculation with data.
Step 1 — Define the Build Area and Set a Take Rate Threshold
Before deploying a sales team, the operator defines two things: where the campaign runs and what take rate constitutes a go decision. The build area is typically a polygon drawn around a neighborhood, subdivision, or municipal district with a discrete address count. The threshold is the minimum percentage of addresses that must commit to service before construction is approved.
Take rate targets vary by project type, capital structure, and operator model. Community FTTH projects commonly target 30–50% pre-registration. Municipal and utility-backed builds may accept a lower threshold where anchor-tenant commitments or grant funding cover baseline costs. Whatever the threshold is, it is documented before a single door is knocked. The number cannot move after canvassing starts — that is how demand campaign data loses credibility.
Step 2 — Map the Serviceable Footprint in COS Prospector
COS Prospector’s territory mapping tools let operators draw polygon boundaries around the target build area using address and parcel data. Every address inside the polygon is loaded as a prospect record, giving the field sales team a complete, bounded universe of potential subscribers. See how COS Prospector works.
Polygons can be subdivided into zones and assigned to individual reps or subcontracted teams. This creates manageable canvassing assignments and lets managers track progress at the zone level rather than waiting for a campaign-wide rollup at the end. The map is the operational spine of the campaign: it controls where reps work, what they can see, and how outcomes are recorded against each address.
Step 3 — Deploy Field Sales Reps for Door-to-Door Canvassing
Reps work their assigned territory using the COS Prospector mobile app. At each address, they log the outcome: interested, not interested, no answer, or already served. For interested prospects, reps complete a full order without leaving the doorstep — serviceability check, plan selection, and PCI-compliant payment tokenization are all handled in the app.
Subcontracted sales teams operate inside the same system under role-appropriate access credentials. Managers can see every rep’s activity, progress, and order count in real time. Nothing is reported at the end of the day from a spreadsheet — every interaction is recorded at the address level as it happens.
Step 4 — Track Take Rate and Prospect Interest in Real Time
COS Prospector’s 12 analytics panels give campaign managers live visibility into what is happening across the entire build area: doors knocked, interest rate by zone, orders placed, and cumulative take rate against the threshold. Managers can identify underperforming zones, redeploy reps, or schedule a second-pass canvass on addresses that were unavailable — without waiting for end-of-week reports.
Prospect data flows from COS Prospector into COS Business Engine continuously. The build team has a live demand picture throughout the campaign, not a static snapshot at the close. Learn more about COS Business Engine.
Step 5 — Analyze Results and Trigger the Build Decision in COS Business Engine
When canvassing is complete, the final take rate is measured against the threshold. COS Business Engine holds the prospect interest data and service location delivery states that Prospector generated throughout the campaign. Network planners use this data directly: if take rate meets the threshold, they confirm the build area, sequence construction, and initiate service activation workflows for pre-registered subscribers.
If take rate does not meet the threshold, the data still has value. Zone-level performance shows which parts of the build area drove interest and which did not, informing a boundary adjustment, a second canvass phase, or a decision not to build — before any construction spend is committed. That is the point of the campaign: replace guesswork with structured demand data.
Frequently Asked Questions
What is a fiber demand campaign?
A fiber demand campaign is a pre-construction process where a fiber network operator canvasses a defined geographic area to measure subscriber interest. The campaign generates take rate data that determines whether a build area is financially viable before construction begins.
What take rate do most fiber operators target?
Take rate targets depend on project type, financing structure, and operator model. Community fiber builds commonly target 30–50% pre-registration. Municipal and utility-backed projects may accept lower thresholds where anchor-tenant commitments or public funding cover baseline costs.
How long does a fiber demand campaign take?
Campaign duration depends on the size of the build area and the field sales team. A focused campaign covering a few thousand addresses with an active team typically runs 4–8 weeks. Larger territories or multi-phase builds may require longer campaigns with interim take rate reviews.
How does COS Prospector support a fiber demand campaign?
COS Prospector provides the full operational stack for a demand campaign: territory polygon mapping, prospect record management, a field sales mobile app, in-field order creation with PCI-compliant payment, 12 real-time analytics dashboards, and role-based access for direct and subcontracted sales teams. Take rate is calculated continuously against every address in the build area as the campaign runs.
How does demand campaign data connect to a build decision?
Prospect interest data from COS Prospector flows directly into COS Business Engine. Service location delivery states track each address from initial contact to confirmed subscriber. When take rate meets the threshold, network planners in COS Business Engine have the demand data needed to confirm the build area and sequence construction.
Can demand campaigns work for open access networks?
Yes. Open access operators run demand campaigns using the same model, with the added complexity that multiple ISPs may offer competing services in the same build area. COS Prospector and COS Business Engine support multi-ISP scenarios, letting the network operator track demand across service tiers and ISP offerings from a single platform.
Ready to Run a Demand Campaign?
COS Prospector gives fiber operators the territory mapping, field sales tools, and real-time analytics to run structured demand campaigns and connect results directly to build decisions in COS Business Engine.
See how COS Prospector works
PRIME FiBER Selects COS Systems to Power Wholesale Operations and AT&T Integration for Sun City, Arizona Expansion
[West Palm Beach – May 2026]:
West Palm Beach— May 16, 2026 — PRIME FiBER, a leading Open Access fiber-to-the-home service provider, has selected COS Systems and its wholesale broadband software, COS Wholesale Engine, to support wholesale operations and integration workflows for PRIME FiBER’s expanding partnership with AT&T in Arizona.
The deployment supports PRIME FiBER’s new fiber market launch in Sun City, Arizona, part of the company’s broader wholesale fiber expansion across the greater Phoenix region. Through COS Wholesale Engine, PRIME FiBER will automate operational workflows and enable direct integration between wholesale infrastructure and retail service delivery processes.
COS Wholesale Engine is a carrier-grade orchestration platform purpose-built for Open Access and wholesale fiber environments. It handles service qualification, order orchestration, appointment management, and partner interoperability through standards-based APIs and operational automation. The platform lets infrastructure operators and retail service providers integrate, automate workflows, and coordinate across multi-party environments without the manual overhead
“Open Access requires more than infrastructure. It requires interoperability across systems operated by multiple parties, while still delivering a seamless experience to the end customer,” said Rob Johnson, CTO of PRIME FiBER. “COS Wholesale Engine gives us the operational foundation to efficiently support our wholesale model, automate complex partner interactions, and accelerate market launches with major service providers like AT&T.”
“We designed COS Wholesale Engine specifically for the realities of wholesale broadband ecosystems. PRIME FiBER is building a modern Open Access model at significant scale, and we are proud to support the operational and integration framework behind that growth,” said Sajan Parikh, CTO of COS Systems.
The Sun City deployment builds on PRIME FiBER’s growing footprint and ongoing collaboration with AT&T to expand high-speed fiber access in underserved and high-growth markets.
About PRIME FiBER
PRIME FiBER is an Open Access fiber-to-the-home service provider serving ISPs, infrastructure consolidators, and enterprises across the United States. The company is backed by InLight Capital and focused on accelerating high-speed fiber deployment through scalable wholesale infrastructure models.
About COS Systems
COS Systems provides software platforms for wholesale broadband operators, Open Access fiber networks, and service providers. COS Business Engine powers full retail ISP operations — subscriber management, billing, provisioning, and field service. COS Wholesale Engine drives large-scale partner interoperability, operational automation, and API-driven orchestration across modern broadband ecosystems. COS FSM and COS Prospector extend the platform with automated field service management and door-to-door field sales, so operators can sell faster, scale better, and automate everything.
Fiber First Migrates to COS Business Engine and COS FSM | COS Systems
Customer Story
By Isak Finer · April 28, 2026
Selling fiber Internet should be straightforward: a customer wants service, you check if they’re on the network, you sign them up, and you get them connected. But when your systems aren’t talking to each other and your team can’t always trust the data in front of them, even that simple process can grind to a halt.
That was the reality for FiberFirst before they partnered with us. Operating across several US states on Ubiquity’s open access fiber infrastructure, they were growing fast — but their previous BSS/OSS solution couldn’t keep up. Manual processes slowed down sales, field operations were disconnected from customer records, and staff couldn’t always be certain whether a given address was on the fiber network or what services could be offered there.
A platform built for how ISPs actually work
We implemented two products in tandem: COS Business Engine including the COS Marketplace, our core BSS/OSS platform, and COS FSM, our field service management solution. Rather than switching everything over at once, FiberFirst started by using COS Business Engine to onboard new customers across all their markets — giving both teams the time to validate workflows and fine-tune processes in a live environment before migrating their existing subscriber base.
Today, when a sales rep — or a customer shopping online — looks up an address, they see accurate, real-time data: whether fiber is available, which services can be offered, and what the next steps are. And at the moment of sale, they can immediately schedule a fiber installation appointment. No follow-up calls, no back-and-forth. The customer picks a time that works for them, right then and there.
First markets live in California
With workflows proven and both teams confident in the platform, migration of the legacy subscriber base began. FiberFirst’s first California markets have now been successfully migrated — a significant milestone that brings those subscribers into the same streamlined experience new customers have been enjoying for months.
The success builds on a strong relationship, great cobuilding driven by FiberFirst’s feedback and a joint view of what matters most – the subscriber. Tens of thousands of subscribers across the rest of their markets are next, and we couldn’t be more excited to get there together.
Frequently asked questions
What is COS Business Engine?
COS Business Engine is COS Systems’ core BSS/OSS platform for broadband operators. It manages subscriber records, real-time service availability, billing, and sales workflows on a single platform. On open access fiber networks, it coordinates service delivery across a shared physical infrastructure used by multiple ISPs.
What is COS FSM?
COS FSM is COS Systems’ field service management solution. It connects installation and maintenance crews to the same customer and network records that sales and back-office teams use, coordinating dispatch, scheduling, and job completion in a single integrated workflow.
What is a Ubiquiti open access fiber network?
Ubiquiti provides networking hardware used to build open access fiber infrastructure: a single physical fiber plant shared by multiple ISPs. Each ISP manages its own subscriber base on top of the shared network. Open access models have operated in Europe for decades; North American deployment is now accelerating.
How did Fiber First migrate without disrupting existing subscribers?
Fiber First onboarded all new customers on COS Business Engine across every market before beginning the legacy migration. That approach created a live environment where both teams could validate every workflow under real operational load. The California markets migrated only after the platform was confirmed stable.
Can customers schedule a fiber installation appointment at point of sale?
Yes. When a sale closes on COS Business Engine, the customer or sales rep selects a fiber installation time slot immediately. The appointment is confirmed in the same transaction — no separate scheduling step is required.
Field Service Management Software for Fiber Operators: What to Look For
Last updated: April 2026 | By Maren Buchüller, Head of Marketing, COS Systems
Fiber network operators evaluating FSM software face a purchasing decision that generic software reviews don’t address well. The criteria that matter for an HVAC company — scheduling efficiency, mobile job forms, customer notifications — are necessary but not sufficient for fiber. Fiber deployments add ONT provisioning, splice coordination, multi-party subcontractor handoffs, and a hard requirement for BSS/OSS integration. The wrong tool creates data gaps that stall installations and require manual reconciliation at scale.
This guide covers the criteria that determine fit, what to ask vendors, and how purpose-built fiber FSM compares to general-purpose alternatives.
The Buying Context: FSM for a Scaling Fiber Operation
A fiber operator running 20 installations a week can manage field work with spreadsheets and phone calls. An operator scaling to 500 installations a week cannot. At that volume, the cost of uncoordinated dispatch, missed provisioning triggers, and manual data entry between field and back office compounds quickly.
The specific pressure points fiber operators report at scale:
These are not FSM problems in the abstract. They are fiber-specific workflow gaps that only appear when the FSM has no knowledge of what a fiber installation actually involves.
5 Criteria That Matter for Fiber FSM
1. Fiber-specific workflow templates
A fiber drop installation is not a service call. It involves ONT placement, cable certification, port assignment, and provisioning confirmation — in a specific sequence, with data capture at each step. The FSM platform needs pre-built workflow templates that map to this sequence, not a generic job form that requires your operations team to build the workflow from scratch.
Ask vendors: Do your workflow templates include ONT provisioning steps, cable certification capture, and post-installation sign-off? Can technicians capture structured field data (not just notes) at each workflow step?
2. Native BSS/OSS integration
When a technician completes a fiber installation, service activation should happen automatically. That requires the FSM platform to communicate directly with the operator’s provisioning and billing layer — not via a webhook that fires into a queue, not via an export that someone processes at end of day.
Native integration means address data, customer records, and network inventory are shared in real time between FSM and BSS/OSS. Completed field work closes the loop in the back office without a manual handoff.
Ask vendors: Is the BSS/OSS integration native or via webhook/API? What triggers service activation — a technician action in the mobile app, a manual step, or an automated event?
3. Multi-party subcontractor support
Most fiber builds involve subcontractors. Generic FSM platforms are designed for a single organization dispatching its own staff. They have no model for assigning work to an external company, giving that company’s technicians role-appropriate access, and tracking their progress alongside your own crew.
Fiber-native FSM supports multi-party operations natively: task assignment across organizations, role-based mobile access for subcontractor technicians, photo and note capture, and acceptance workflows that let the network operator sign off on completed subcontractor work.
Ask vendors: Can you assign work to external subcontractor organizations? Do subcontractor technicians use the same mobile app with restricted access, or a separate system?
4. Customer self-scheduling
Inbound scheduling — subscribers booking their own installation appointment — reduces call volume and no-shows. The FSM platform should integrate with the operator’s customer portal to surface real-time technician availability and allow subscribers to select appointment windows directly.
Ask vendors: Does the platform support customer-facing self-scheduling? How does it handle reschedules and appointment reminders?
5. Mobile-first field execution
Field technicians work from phones and tablets in variable conditions. The mobile app needs to match the actual workflow: structured data capture at each installation step, photo upload, cable certification entry, and digital customer sign-off. A desktop interface that scales to mobile is not the same thing.
Ask vendors: Is the mobile app purpose-built or a mobile view of the desktop? Can technicians complete the entire installation workflow offline?
COS FSM vs. Generic Alternatives
The table below compares COS FSM against two commonly evaluated general-purpose FSM platforms on criteria that matter specifically for fiber network operations.
ServiceMax and FieldEdge are capable platforms for their intended markets. The gap is not feature depth — it’s that fiber-specific objects and workflows require configuration that those platforms were not designed to support.
What Fiber Operators Report After Switching
Ting selected COS FSM to modernize and scale fiber installations across the United States. The requirement was a platform that could handle the full installation lifecycle — scheduling, dispatch, subcontractor coordination, and provisioning handoff — without the manual reconciliation steps that had constrained throughput.
COS FSM is used by fiber network operators across North America and Europe, including network owners, retail ISPs, open access networks, and municipal broadband operators. The common thread: operators who need field operations to connect directly to billing and provisioning without manual intervention.
Learn more about COS FSM →
Frequently Asked Questions
What should fiber operators look for in FSM software?
The non-negotiable criteria: fiber-specific workflow templates (not generic job forms), native BSS/OSS integration that triggers service activation automatically, multi-party subcontractor support, customer self-scheduling via a customer portal, and a mobile app purpose-built for field execution rather than a scaled-down desktop interface.
Can generic FSM software work for fiber network operators?
Generic FSM platforms can be configured to manage fiber field operations, but the configuration burden is significant. Platforms built for HVAC or facilities management have no native concept of ONTs, splice sequences, service areas, or provisioning triggers. Operators typically report ongoing manual workarounds for BSS/OSS handoffs and subcontractor coordination that fiber-native FSM handles natively.
How does FSM software integrate with BSS/OSS for fiber operators?
In a fiber-native FSM platform, completed installations trigger automated service activation in the BSS/OSS layer without a manual step. COS FSM integrates natively with COS Business Engine: address data, customer records, and network inventory are shared in real time. Generic FSM tools typically connect via webhooks or API middleware, which introduces latency and potential failure points.
What is the difference between COS FSM and ServiceMax or FieldEdge?
ServiceMax and FieldEdge are general-purpose FSM platforms built for field service trades. COS FSM is built specifically for fiber network operators: it treats fiber-specific objects as native data types, supports multi-party subcontractor operations, and integrates natively with BSS/OSS for automated service activation. The platforms serve different markets.
How do fiber operators manage subcontractor field work in FSM?
Fiber-native FSM supports multi-party operations: the network operator assigns work to subcontractor organizations, subcontractor technicians access tasks through a role-restricted mobile interface, and the network operator tracks progress and completes acceptance workflows in real time. COS FSM includes purpose-built subcontractor collaboration tools — no separate system required.
Work Order Management for Fiber Networks
COS Systems Knowledge Hub | Field Operations | April 2026
Work Order Management for Fiber Networks
Work order management is the operational backbone of fiber deployment. It controls what technicians do, in what sequence, at which address — and whether the outcome is logged, verifiable, and tied to provisioning. For fiber operators scaling hundreds or thousands of activations, the difference between disciplined and ad-hoc work order handling compounds quickly.
What Is a Work Order in a Fiber Network?
A work order is a structured task record scoped to a specific job at a specific address. It defines the sub-tasks required, the assignees responsible, the documentation to collect, and the status that triggers the next step in the activation chain.
In COS Business Engine, work orders are used to support the process of delivering a service to a customer. Once an object is set to In Deployment, a work order is automatically created to connect and check that object. The work order holds all actions required to bring a functioning service to the customer — including physical installation, ONT setup, testing, and sign-off.
Work orders are distinct from service tickets. A ticket addresses a fault or customer request post-activation. A work order governs the installation itself, with a defined start state (address in deployment) and a defined end state (service ready to activate).
Why Fiber Deployments Require Structured Work Orders
Fiber installation is not a single-step job. A typical FTTH activation involves civil crew work on the distribution network, a drop installation to the premises, ONT mounting and cabling, light level testing, and provisioning confirmation. These steps may involve different crews, different skill sets, and different scheduling windows.
Without a structured work order, this sequence depends on verbal handoffs, spreadsheets, and tribal knowledge. Each gap is a potential missed step. Incomplete work orders lead to truck rolls with missing information, on-site delays, and repeat visits. In a scaled deployment, repeat truck rolls are one of the highest preventable costs an operator carries.
Structured work orders eliminate the ambiguity. Every technician arrives at a job knowing exactly what to do, in what order, and what to document before closing the work order.
What a Fiber Work Order Contains
Work order templates are set up by the operator to organize the required tasks. Multiple templates can be created to accommodate various installation types or work required for an object. Each template can be customized to specific installation requirements, enabling efficient management of diverse tasks across projects.
A standard FTTH work order typically includes sub-tasks across these categories:
Physical Installation
Fiber drop from the distribution point to the premises. Conduit or aerial entry. ONT mounting and cabling. Completion photo documentation.
Testing and Verification
Light level measurement at the ONT. Speed test after provisioning. Results logged directly in the system from the field technician’s mobile device.
Provisioning Trigger
Task completion fires the provisioning event in the BSS/OSS. Service is activated without a manual step from the NOC.
Customer Communication
Status updates are sent to the customer portal as the work order progresses. Customer is notified when the service is ready to activate.
Upon installation completion, light levels and speed test results are saved automatically, providing a reliable reference for future troubleshooting and SLA verification. This installation record — effectively a birth certificate for the connection — is tied permanently to the address object in the BSS/OSS.
Assigning Work Orders Across Operator Staff and Contractors
Most fiber operators deploy a mix of internal crews and external contractors, particularly during aggressive rollout phases. Tasks in a work order can be assigned to different assignees — for example, if both the operator’s staff and a contractor will be involved in the installation process.
This split-assignment model is critical for accountability. When a task is assigned to a specific individual or crew, the work order system records who completed it, when, and what was documented. If a job requires a return visit, the history is clear. There is no ambiguity about which crew touched what.
Automated Work Order Creation from Deployment Triggers
Manual work order creation does not scale. When a project area enters the “In Deployment” phase, work orders are automatically created for all orders. This eliminates the administrative step of creating individual work orders for each address and ensures nothing is missed when a batch of addresses moves into the active build phase.
End-to-end automation ensures that once an order is placed, a work order is generated automatically, required materials are identified, and tasks are routed to the right crew. Dispatch does not depend on email threads or last-minute clarifications — it is driven by structured data that follows the order from the start.
In COS Business Engine, this trigger is tied to the object status model. Addresses exist as objects in the system, each with a tracked status. When the operator moves an area from surveyed to in-deployment, the platform creates work orders across all affected objects in batch — no manual step required.
The Field Technician Interface
Installers access a portal to view their tasks and document work directly in the system via mobile or tablet. This mobile interface removes the dependency on paper forms, end-of-day reporting, and back-office data entry. Technicians log task completion, upload photos, record test results, and close the work order from the field — in real time.
Technicians use a mobile interface to access real-time work instructions, mark tasks as completed, and upload documentation such as photos or notes. This portal allows for progress tracking during the installation process.
Real-time field data has downstream value beyond the individual work order. Operations teams see live deployment progress. Customer communications are triggered by actual status changes, not manual updates. And the installation record that feeds future network troubleshooting is accurate because it was captured at the point of work, not reconstructed afterward.
COS FSM: Field Service Management Built for Fiber Scale
COS Business Engine provides work order management, scheduling, and a field technician interface as part of the core BSS/OSS. For operators who need a dedicated field service management layer — with advanced scheduling, route optimization, and contractor management — COS FSM extends those capabilities as a standalone product or integrated add-on.
COS FSM streamlines field operations with skill-based scheduling, self-service appointment booking, and route optimization. It can be used standalone or together with COS Business Engine to go from customer order to completed install with minimal manual handling.
COS FSM supports any type of work order, with workflows defined to match the operator’s processes. Skill-based assignments route tasks based on field technicians’ skills. Customers can pick a suitable time based on technician availability, while the actual installers are assigned closer to appointment time to ensure minimal drive time and efficiency.
When COS FSM is integrated with COS Business Engine, the full activation chain becomes automated: customer order triggers a work order, the work order enters the scheduling queue, a technician is dispatched, the job is completed and documented in the field, and provisioning fires on task close. No manual handoff at any stage.
Work Order Management in Open Access Networks
Open access deployments add a structural layer that retail ISP operations do not face. The network owner is responsible for the physical infrastructure. The ISP is responsible for the service. A work order for an open access installation must track physical completion by the network operator and logical service activation by the ISP as two separate status events.
COS Business Engine is designed for this model. The platform manages the full lifecycle of an open access network, tracking physical installation status per address and notifying the relevant ISP when the infrastructure is ready for service activation. The system monitors installation status per address and informs customers when services are ready to be activated — including for post-deployment connections in already built areas.
For wholesale operators running multi-ISP networks, COS Wholesale Engine complements COS Business Engine by handling the ISP-layer billing and reporting that follows activation. Work order completion feeds the activation record; the activation record feeds the billing cycle.
Connecting Work Order Completion to Provisioning and Billing
A work order system that operates in isolation from provisioning and billing creates a gap. Field teams close jobs; the back office re-enters data to activate service and start billing. That gap introduces errors, delays, and revenue leakage.
In an integrated BSS/OSS, work order completion is a system event, not just a status flag. Thanks to COS Business Engine’s integrations, services are automatically activated once the CPE is installed. Customers choose and activate services directly through the customer portal, without manual handling from the network or service providers.
Scheduling and planning integrates with the network management system, enabling automatic updates and synchronization across network elements and provisioning tasks. This reduces manual intervention, minimizes errors, and improves efficiency, ensuring smoother and faster deployments.
Billing follows the same logic. When provisioning confirms service is live, the billing cycle starts. No manual trigger, no lag between activation and first invoice. The work order that began with a deployment trigger ends with a live, billing-active service at the address.
Frequently Asked Questions: Work Order Management for Fiber
What is a work order in a fiber network?
A work order in a fiber network is a structured task record assigned to a technician or crew for a specific job at a specific address. It contains sub-tasks, required documentation, and status checkpoints for activities such as fiber drop installation, ONT setup, light level testing, and service activation. In BSS/OSS platforms like COS Business Engine, work orders are generated automatically when an address moves into deployment status.
How are work orders generated automatically in fiber BSS/OSS platforms?
When an operator sets an address or project area to In Deployment status in the BSS/OSS, the platform creates a work order automatically against that object. The work order inherits the applicable template, pre-populates sub-tasks, and queues for scheduling. No manual order entry is required. COS Business Engine uses this trigger-based approach to connect customer orders directly to field dispatch.
What is the difference between a work order and a field service management system?
A work order is a single record defining what needs to be done at a location. A field service management system is the platform that creates, schedules, dispatches, tracks, and closes work orders at scale. FSM adds skill-based routing, route optimization, real-time status visibility, and mobile access for technicians on top of the underlying work order structure.
Can work orders be assigned to contractors as well as internal crews?
Yes. Work order tasks can be split across multiple assignees. Internal technicians and external contractors can each hold different sub-tasks within the same work order. This is standard in FTTH deployments where operators use a mix of their own crews and subcontractors for drops, ONT installation, and network testing.
What documentation is captured when a work order is completed?
At completion, technicians log light level measurements, speed test results, photos, and task sign-off directly from a mobile device. COS Business Engine stores this as a permanent installation record tied to the address. This record is available for future troubleshooting, SLA verification, and network audits.
How does work order completion trigger service provisioning?
In an integrated BSS/OSS, completing the relevant work order task triggers automatic ONT provisioning. The service defined in the customer’s order is activated without a manual step from the network operations center. COS Business Engine handles this integration with provisioning vendors including Adtran, Nokia, and Calix.
How does work order management differ in open access fiber networks?
In open access networks, a single work order may relate to infrastructure the network owner installs, while service activation is handled by the ISP. The BSS/OSS must track status across both layers — physical installation by the network operator and logical service activation per ISP — without conflating the two. COS Business Engine and COS Wholesale Engine are both designed to manage this separation cleanly.
COS FSM and COS Business Engine manage work orders, field dispatch, and provisioning in a single integrated platform. See how fiber operators use COS to automate the full installation chain.
Book a Demo
COS Business Engine Integrates with IQGeo Network Manager Telecom
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.