How to Plan Private 5G/LTE in a Metallic Manufacturing Environment

Manufacturing plants combine reflective materials, moving equipment, indoor and outdoor areas, and services with different radio requirements. An RF planning workflow for a factory or manufacturing plant that considers only signal level can therefore leave important questions unanswered: where does the signal come from, what happens under load, and can the network meet the requirements of a specific service?

A robust planning workflow should combine advanced propagation modelling, unified indoor/outdoor analysis and Effective Service Areas. It should also make the assumptions and outputs clear enough for technical review and project handoff.

How should reflections and diffraction be modelled in a factory?

Atoll One private wireless planning software supports ray tracing with up to three reflections, horizontal and vertical diffraction, and cross-floor or inter-floor diffraction. These settings allow the planning team to represent more of the propagation paths that can occur around steel structures, machinery and other reflective objects.

The model can be adjusted during the design process. A team may begin with a simpler setting, then enable additional reflections and diffraction as the design is refined. The result can be inspected through several complementary views:

• Compare predictions with no reflections and with additional reflections.
• Use a difference map to show the change between prediction results.
• Inspect propagation path types, including line-of-sight, non-line-of-sight, diffracted and reflected paths.
• Identify whether a location is influenced by a first-, second- or third-order reflected path.
   

In a hangar and adjoining office area, the predicted difference is not uniform. The office area in the example is more affected by additional reflections and diffraction. This illustrates why a change in propagation settings should be evaluated spatially rather than reduced to a single overall result.

Can indoor and outdoor networks be planned together?

Yes. Indoor and outdoor planning can be brought together in one project rather than treating the building as isolated from its surroundings. This matters because a manufacturing campus may include outdoor yards, parking areas and roads, while external transmitters may also penetrate indoor spaces.

A practical workflow separates the questions before bringing them together:

1. Evaluate outdoor penetration. Run a prediction using the outdoor transmitters to identify signal entering the building.
2. Design the indoor system. Model indoor small cells, active or passive DAS, radiating cables, repeaters or other planned infrastructure.
3. Compare dominance. Use a combined view to identify whether outdoor or indoor cells are dominant in each area.

Indoor dominance may cover much of a hangar while outdoor signal becomes dominant in some areas. This challenges the assumption that a metal-clad building automatically blocks all outdoor signal. The planning question is not only whether a signal exists; it is also which system is serving the location and what that means for quality and interference.

How can a planner test whether a manufacturing service is available?

Effective Service Area analysis combines several criteria into a single service-oriented result. These criteria are coverage, quality, downlink and uplink capacity, and latency.

This differs from checking each KPI independently. A location may pass a signal threshold and a latency threshold but fail a quality or capacity requirement. Effective Service Areas show whether the defined service conditions are met together.

The analysis can be used with the following network configurations:

• 4G/LTE
• 5G Standalone
• 5G Non-Standalone
   

An AGV/AMR service on 5G SA can be assessed with shadowing margin and traffic load included. Its service requirements can include seamless mobility and high uplink capacity. The resulting service-area view is therefore tied to the AGV/AMR definition rather than to a generic coverage layer.

Why can device characteristics change the result?

A service result depends on the assumed device and radio conditions, not only on the transmitter layout. Mission-critical video on a 5G RedCap wearable can produce a different result from another terminal type in the same building and with the same radios.

In the demonstrated configuration, coverage and latency pass in some areas but quality fails because there is no MIMO gain. This is a useful technical distinction: a building map that looks acceptable for one terminal type should not automatically be treated as valid for another. Device assumptions, service properties and prediction criteria need to remain visible in the analysis.

Which manufacturing services should be modelled?

A private manufacturing network may need to support multiple six use cases, each with a different service type and set of requirements:

• Cobots and motion control
• AGV and AMR fleets
• Computer vision and edge AI
• Worker devices
• IIoT sensors
• Mission-critical push-to-talk

These use cases correspond to URLLC, eMBB and mMTC traffic characteristics in different combinations. The design challenge is that these traffic types share the same network and spectrum. Atoll also supports network slicing concepts in which different percentages of spectrum can be assigned to different traffic types; the detailed treatment of slicing is outside the scope of this article.

For technical teams, the correct sequence is to define the service requirements first, then select the relevant prediction criteria and load conditions. A generic downlink coverage map cannot substitute for that process.

What outputs support design handoff?

Several reports and exports can be generated from the planning workflow:

• Link budget
• Bill of materials and antenna report
• Coverage predictions
• Wiring report
• Connection report
• PIM and intermodulation report
• EMF compliance report
• Open IFC export

IFC export can pass the RF design and included equipment into a building information modelling workflow. The broader data-ownership principle is to maintain projects and designs in an open, exportable format rather than treating the planning database as the only place where the design can be used.

A practical technical workflow

For a manufacturing venue, the planning sequence is:

1. Build the indoor and outdoor venue model.
2. Define relevant materials and propagation settings.
3. Define services and their required criteria.
4. Add outdoor and indoor transmitters.
5. Compare propagation results and inspect path types.
6. Run Effective Service Area analyses under the relevant network configuration and load.
7. Produce reports and open-format design outputs for the next project stage.

This workflow does not remove the need for valid building data, equipment parameters, service assumptions or field validation. It provides a way to expose those assumptions and test their effect within the design.

Seven questions to ask of a planning tool

Before selecting a tool for a private wireless venue design, ask whether it can:

• Enable multiple reflections and both horizontal and vertical diffraction.
• Model indoor and outdoor networks together, including their interaction.
• Define various services and terminal devices
• Show service availability rather than only signal level.
• Map multiple venue locations across a wider geography.
• Export designs to IFC and provide wiring and open-data outputs.
• Scale through scripting, database queries or API integration when more plants are added.

Atoll One connects propagation analysis, service validation and design handoff for private wireless manufacturing environments.

Next steps: Explore Atoll One for private mobile networks, the manufacturing use case, and Atoll propagation modelling. Watch the webinar replay to see the propagation comparisons, indoor/outdoor analysis and Effective Service Area workflows demonstrated.