5 Ways Atoll One Simplifies Private Wireless Network Planning for System Integrators

No two RF planning jobs look the same. One month it's a distribution centre, the next a water treatment site, then a factory floor being reconfigured while the survey is still under way. Every client arrives with its own building data, its own equipment preferences, its own view of what the network is actually for.

An agency working across mixed environments tends to accumulate a method instead of designing one: an indoor tool for in-building work, something else for outdoor and backhaul, a subcontractor for any RF modelling that's unfamiliar, a spreadsheet at the end to turn it all into an equipment list. Every handover in that chain is a place where data gets rebuilt by hand, where two engineers reach different answers on the same site, and where a client question that should take ten minutes takes a day.

Atoll One wasn't built for a single site type. It runs on the same platform mobile operators use to plan live carrier networks, installed on a project engineer's laptop, and it covers LTE, 5G NR, Wi-Fi and microwave backhaul in one place. That combination affects a project in five specific ways.

1. One project for indoor, outdoor and backhaul

Sometimes the networks you're asked to design aren't purely indoor or purely outdoor. A warehouse comes with a yard. A campus comes with the ground between buildings. A plant has a control room inside and infrastructure outside, and something has to carry traffic between the two.

Plan those parts separately, and the boundary between them becomes the space nobody modelled — exactly where handheld devices and automated vehicles lose connection. Atoll One holds the entire site in a single project, on one data structure:

• Indoor floors, outdoor terrain and the transitions between them modelled together, not joined afterwards
• Microwave backhaul planned in the same project as the radio design, not as a separate exercise
• Multi-building campuses treated as one site, so coverage stays consistent from building to building
• One set of predictions to review with the client, instead of several that have to be reconciled first

2. Client building data goes in as-is

Clients rarely hand you data in the shape an RF engineer would like. They send what their architects and facilities teams already hold, and on most projects that's a BIM model or a set of CAD drawings.

Rebuilding that model inside a planning tool is billable time spent reproducing something the client already owns, and the version you end up with is always a simplification of the one you started from. Walls, floors and structural elements come through as generic surfaces carrying default attenuation values, rather than the steel frame, reinforced concrete and partition types the original model specifies. The prediction is then computed against an assumed building rather than the real one. Atoll One imports the client's data as it stands:

• Open IFC and BIM import for structural models
• AutoCAD DWG import for floor plans and site drawings
• Materials and geometry retained, so propagation is modelled against the real structure
• Existing data reused as a site changes, rather than rebuilding the model each time

3. Design data comes back out, including the bill of materials

An RF design that only exists inside the planning tool creates work for everyone downstream. Installation needs something to build from, the client needs something to review, and procurement needs a list they can order against.

Agencies lose time because they assemble outputs by hand from a design that already contains everything needed. Atoll One treats the project database as something other systems can use:

• A bill of materials generated from the validated design rather than compiled separately
• A project database that can be read and written externally, for reporting, handover and asset records
• Design data that can flow back to BIM workflows through IFC
• Site and equipment records that stay aligned with a client's inventory or GIS system, instead of drifting from it

One RF engineer on a small-cell offload project described building cloud systems and maps directly on the Atoll database and syncing it with inventory management, treating it as the authoritative record of site, physical and antenna information. That's only possible when the data is genuinely accessible from outside the tool.

4. Every cable and equipment connection is visible

Two designs for the same building can specify identical radios, antennas and passive components and still behave differently once installed, because of how each element is connected and what feeds it. An equipment schedule won't show that. It lists what's installed, not what connects to what, so the difference tends to surface during commissioning rather than during design.

Atoll One's connection analysis view traces every connection visually across the whole project: which unit feeds which, through which cable route, indoor and outdoor together. For an integrator whose designs are reviewed by someone else, a reviewer can follow the design without reconstructing it, a client can see exactly what they're approving, and an installation team gets something unambiguous.

5. The software bends to your process, not the other way round

Systems integrators already have a method: the equipment they favour, how they structure a project, the outputs a given client expects, the checks they run before anything gets signed off. A tool that can't accommodate that method will impose its own, which is how two engineers at the same agency can end up producing work that doesn't look like it came from the same place.

Atoll One is configurable where it counts:

• Reusable station and prediction templates, so a validated approach can be applied to the next project
• Custom fields and equipment types, so your own catalogue and conventions fit
• Configurable data structures, so project organisation follows your practice
• Add-ins for the steps you repeat often enough to be worth automating

Propagation models are tunable against measurement data, and the settings that control them are reachable from the interface rather than buried in configuration files. Configurability only helps if engineers can actually get to it.

What it adds up to

Together, these 5 points change how a system integrator's time is used. Less time is spent rebuilding data or reconciling separate designs and assembling outputs by hand, and more is spent on the engineering the client is actually paying for.

Because Atoll is widely used across the industry, a contractor or new hire brought in mid-project is likely to have worked with it already, and can start producing designs rather than learning a tool that only your firm uses.