If your organization is interested in what broader open-access adoption and stronger interoperability across the ecosystem can unlock for the industry, it should be at the table.
Across North America, ATIS’ groundwork is enabling a shift in how internet infrastructure gets built and shared. Open-access networks, where a single network owner leases infrastructure to multiple competing internet service providers (ISPs), have the potential to dramatically accelerate broadband deployment and increase consumer choice. But realizing that potential requires more than capital, fiber optic cable, copper cables, radio waves (wireless), and satellites. It requires the industry to agree on how to actually do it.
ATIS is central to accelerating this progress. Through its Open Access Network Forum (OANF), ATIS is convening ISPs, open-access infrastructure providers (OAPs), and their technology partners to develop the standards, architectures, and commercial frameworks needed to make open-access networks deployable at scale. The goal is practical and concrete: reduce integration friction, align technical and operational practices, and produce guidance that accelerates adoption across the North American market.

OANF will help bring greater consistency to how open-access networks are designed, integrated, and operated, making it easier for service providers to launch and expand services for end users across the North American market. This initiative is another way ATIS is advancing ICT industry transformation by helping simplify service enablement in open-access environments.
The Forum is now organized into six working groups, each laying the groundwork for what comes next:
Network Architecture
Define L2 NNI connectivity standards and ONT handoff to ISP. Coordinate with Broadband Forum to adapt existing standards to open access requirements.
Initial ISP/OAP Onboarding
Define processes and integrations for new ISP/OAP partnerships, including NNI build expectations and BSS/OSS configuration for connecting the two parties.
Common Interface Requirements
Establish shared vocabulary and requirements for all interface design — covering API versioning, error recovery, idempotency, and security beyond base TM Forum standards.
Field Services
Identify use cases and define dispatch processes for ISP-initiated field visits to customer addresses — where no OAP network changes are required.
Common Data Interchange
Normalize and align data exchange including address information, build status and polygons, product catalog, and catalog update processes.
Customer Provisioning
Map the full customer journey from prospect to active service, covering self-install, field tech installation, and customer overtaking scenarios.
If your organization is interested in shaping the critical groundwork for open-access network deployment, contact ATIS Vice President – Innovation Carroll Gray-Preston at cgray-preston@atis.org.