From Contractor to Operator

The Reactive Model and Its Limits

The first cairn in this trail described the emergency callout lifecycle: a fiber cut happens, a NOC detects it, an OSP contractor gets dispatched to fix it. That’s the reactive model — the contractor is on standby until something breaks, then they roll a crew. The reactive model dominates the industry because most carrier-contractor relationships are structured around it. The carrier owns the network, monitors it through their NOC, and calls the contractor when something goes wrong. It’s simple, well-understood, and leaves the carrier in control.

For many carrier-contractor relationships, the reactive model is the whole story. The contractor maintains an on-call rotation, keeps splice trucks stocked, and waits for the phone to ring. Their operational sophistication lives in the field — fast response times, clean splices, accurate documentation — but the coordination layer between them and the NOC remains phone calls, pagers, and manual status updates.

But there’s a different model emerging, one that changes the contractor’s role fundamentally.

Operations & Maintenance: A Different Relationship

An Operations & Maintenance (O&M) agreement transforms the relationship between a network owner and an OSP contractor. Instead of dispatching crews on a per-incident basis, the network owner contracts the OSP firm to take ongoing responsibility for the health of the fiber network.

Under an O&M agreement, the contractor’s responsibilities typically include:

• Preventive maintenance and monitoring — regular patrol of fiber routes, scheduled testing, condition assessments of optical equipment and supporting infrastructure
• Emergency restoration — repair of fiber cuts and outages within an agreed Mean Time To Restore (MTTR), with all materials, labor, and equipment provided by the contractor
• Documentation and reporting — incident reports with splice loss readings, before-and-after documentation, material usage tracking, and as-built updates
• Compliance — adherence to federal, state, and local regulations, utility locate coordination (811), and industry safety standards

The shift is significant. In the reactive model, the contractor is a vendor you call when things break. Under O&M, the contractor is a partner responsible for keeping things running. Their incentives change — they’re measured on network uptime and MTTR, not just on showing up when paged. O&M agreements are common in large-scale fiber deployments where the network owner lacks local field crews. Hyperscale cloud providers, for instance, may build metro fiber networks connecting data centers but rely on regional OSP contractors for ongoing physical maintenance.

The Multi-Tier NOC Chain

The reactive model has a simple dispatch topology: one NOC, one contractor, one phone call. O&M agreements introduce layers.

Consider how an O&M arrangement works for an AWS Metro Fiber network. AWS monitors the fiber route from its central Network Operations Center — a sophisticated operation spanning millions of kilometers of fiber globally, with automated alarm correlation, self-healing network management, and in-house optical transport technology. AWS operates one of the world’s largest fiber networks — over nine million kilometers of fiber-optic cabling connecting its regions and availability zones. Their metro fiber uses 400 Gigabit Ethernet with in-house DWDM optical transponder technology, and their automated tools resolve over 96% of network events without human intervention.

When an issue requires physical intervention — a cable cut that no amount of automated rerouting can fix — the callout doesn’t go directly to the field contractor. It routes through Irby Construction, a Quanta Services affiliate that operates as a 24/7 sub-NOC. Irby takes the call from AWS, triages it, and dispatches it to the O&M operator responsible for that segment of the network.

graph LR
    A[AWS Central NOC] -->|detects issue| B[Irby — Sub-NOC]
    B -->|routes callout| C[O&M Operator]
    C --> D[Field Crew]

Three organizations. Two NOC layers. One fiber cut that needs fixing at 2 AM.

Each layer adds coordination overhead — but also adds value. AWS brings global network visibility and automated detection. Irby brings 24/7 availability and triage expertise across a portfolio of networks. The O&M operator brings local knowledge, field crews, and the physical ability to fix the problem. The question is whether the coordination between these layers can keep pace with the urgency of the outage.

Phasing In a NOC

The three-tier model works, but it has an obvious optimization: what if the O&M operator ran their own NOC?

For an OSP contractor operating under an O&M agreement, standing up a NOC is a logical evolution. They already have the field crews, the local knowledge, and the contractual responsibility for network health. Adding monitoring and dispatch capability closes the loop — they can detect issues, triage them, and dispatch their own crews without waiting for an intermediate NOC to route the callout.

But you don’t stand up a 24/7 NOC overnight. It requires staffing three shifts, building monitoring infrastructure, establishing escalation procedures, and — critically — earning the trust of the network owner that you can handle the responsibility. The practical path is phased: start with one shift, prove the capability, add coverage incrementally until you reach 24/7.

graph TD
    subgraph Current
        A1[AWS Central NOC] --> B1[Irby — Sub-NOC]
        B1 --> C1[O&M Operator Field Crew]
    end

    subgraph Transitional
        A2[AWS Central NOC] --> B2[O&M Operator NOC — Partial Coverage]
        A2 --> B2b[Irby — Off-Hours]
        B2 --> C2[Field Crew]
        B2b --> C2
    end

    subgraph Target
        A3[AWS Central NOC] --> B3[O&M Operator NOC — 24/7]
        B3 --> C3[Field Crew]
    end

During the transition, the coordination platform needs to support both the three-tier and two-tier models simultaneously — routing callouts to the operator’s NOC during their covered shifts and falling back to the intermediate NOC for off-hours. This isn’t a future state to design for later; it’s the operational reality during the transition. The phased NOC approach mirrors how many small carriers and municipal networks built their operations — starting with limited monitoring hours and expanding coverage as the subscriber base (and revenue) justified the investment. The difference here is that the OSP contractor is making the investment proactively, ahead of the revenue curve.

The Legal Foundation: Becoming a Carrier

Operating a fiber network isn’t just an operational decision — it’s a regulatory one. You can’t provide telecommunications services in the United States without the appropriate legal authority.

The Telecommunications Act of 1996 deregulated the local exchange market and created the framework for Competitive Local Exchange Carriers (CLECs) to compete with incumbent providers. Before the Act, local telephone service was a monopoly. After it, any qualified company could obtain certification to provide service — if they met the regulatory requirements. The Telecommunications Act of 1996 was the first major overhaul of U.S. telecommunications law in nearly 62 years. Its primary goal was fostering competition in local telephone markets that had been served by monopoly providers since the breakup of AT&T.

In Texas, the Public Utility Commission (PUCT) established two certification paths for companies providing local telecommunications services:

Both certifications require demonstrating technical, managerial, and financial viability to the PUCT. Certificate holders must file tariffs or price sheets before commencing service and submit annual reports. The PUCT maintains a public directory of all certificated CLECs operating in Texas.

This is the regulatory machinery that enables an OSP contractor to cross the line from building networks to operating them. Without a COA or SPCOA, you can trench conduit and splice fiber all day — but you can’t legally provide telecommunications services over that infrastructure.

The All Photonic Network

The specific network that brings this story together is an All Photonic Network (APN) in Floydada, Texas.

An All Photonic Network represents an advanced approach to fiber infrastructure — one that maintains signals in the optical domain end-to-end, minimizing the electrical-to-optical conversions that introduce latency and consume power in traditional networks. Where conventional fiber networks convert light to electricity at each switching point, an APN keeps the signal as photons throughout, enabling lower latency, higher capacity, and improved energy efficiency. The IOWN Global Forum — a collaboration between NTT, Intel, Sony, and others — has been driving the Open APN architecture, which defines standards for end-to-end optical wavelength paths. The technology promises latency reduction to one two-hundredth of current levels, 100x improvement in power efficiency, and 125x higher transmission capacity.

The Floydada APN is where the abstract concepts in this cairn become concrete. This is the first network to be operated and managed under the O&M model described above — with AWS monitoring the route, Irby handling 24/7 call routing as a sub-NOC, and the O&M operator providing field response and working toward standing up its own NOC capability.

Floydada is a small city in Floyd County, Texas — the kind of community that federal broadband expansion programs are designed to serve. The fact that an APN is being deployed and operated there, rather than in a major metro area, says something about where the fiber industry is heading. Advanced network technology and professional O&M operations aren’t just for dense urban markets anymore.

What This Means for Emergency Coordination

Everything described in this cairn — O&M agreements, multi-tier NOC chains, phased NOC buildouts, CLEC licensing — changes the requirements for emergency coordination tooling.

The first cairn in this trail described the coordination gap: NOCs and OSP contractors using different tools, with phone calls as the integration layer. The O&M model doesn’t eliminate that gap — it makes it more complex. Now there are potentially three organizations that need shared visibility into an ECO’s lifecycle, with routing rules that change based on time of day and which NOC tier is covering which shift.

A coordination platform in this world needs to handle:

• Multi-tier dispatch routing — callouts flowing through intermediate NOCs before reaching the field contractor, with each tier having visibility appropriate to their role
• Flexible topology — supporting both three-tier and two-tier models simultaneously during the NOC transition, without requiring reconfiguration every time a shift boundary changes
• O&M-specific workflows — preventive maintenance scheduling, MTTR tracking, and compliance documentation that go beyond reactive ECO management
• Multi-party visibility — the network owner, the sub-NOC, and the O&M operator all need real-time status, but not necessarily the same view of it

These requirements don’t invalidate the reactive ECO workflow described in the first cairn — they extend it. The emergency callout is still the atomic unit of coordination. But the organizational topology around it is more complex, and the platform needs to reflect that complexity without imposing it on users who don’t need to see it.

Summary

1. O&M agreements transform the contractor-carrier relationship — from reactive, per-incident dispatch to ongoing responsibility for network health, with preventive maintenance, MTTR commitments, and compliance obligations.
2. Multi-tier NOC chains are the natural result — network owners, intermediate NOC providers, and O&M operators each contribute capabilities, but the coordination between them adds complexity that phone calls can't scale.
3. Phased NOC buildouts require flexible coordination — the transition from three-tier to two-tier dispatch is gradual, and the coordination platform must support both models simultaneously.
4. CLEC licensing is the legal prerequisite — the Telecommunications Act of 1996 created the COA and SPCOA certification paths that enable OSP contractors to legally operate networks, not just build and repair them.
5. The Floydada APN is the concrete example — an All Photonic Network in rural Texas, operated under an O&M agreement with a multi-tier NOC chain, representing both advanced network technology and the contractor-to-operator transition.

Discussion Prompts

• What organizational and cultural shifts does an OSP contractor face when transitioning from reactive dispatch to proactive network operation — and how does tooling either enable or hinder that transition?
• The phased NOC buildout assumes a gradual transfer of responsibility. What would trigger an acceleration of that timeline, and what would force it to slow down?
• As more OSP contractors obtain CLEC authority and stand up their own NOCs, how does the competitive landscape for emergency coordination platforms change?

References

1. Telecommunications Act of 1996 — The federal legislation that deregulated local exchange markets and created the CLEC framework, enabling competitive entry into telecommunications service provision.
2. Texas PUCT — CLEC Certification — The Public Utility Commission of Texas's resource for COA and SPCOA certification, including application requirements, rules (§26.111), and the directory of certificated carriers.
3. Irby Construction — Telecommunications Services — Quanta Services affiliate providing telecommunications construction, NOC services, and broadband network operations — the sub-NOC layer in the multi-tier dispatch model.
4. AWS Global Infrastructure — Network — Overview of AWS's fiber optic network infrastructure, including metro fiber interconnections, 400GbE technology, and automated network management capabilities.
5. IOWN Global Forum — All-Photonics Network — The Open APN architecture specification for end-to-end optical communication, including transceiver, gateway, and interchange component definitions.
6. FCC — Telecommunications Act of 1996 (Full Text) — The complete text of the federal act, including Section 251 (interconnection requirements) and Section 253 (removal of barriers to entry) that enabled CLEC competition.