InnerWeb
Skip to main content

Scaling from one hall to the whole plant: scenario

A plant director producing machinery starts with one hall, but immediately asks what will happen to the map and names when more buildings join. Below is a conceptual scenario, not a description of a delivered project: how to shape the location structure during the pilot so that expansion means adding, not rebuilding.

100%
of pilots converted into deployments (20 deployments and pilots)
Source: InnerWeb company data
25–50
transmitters for a 5,000 m² hall
Source: sample calculation: 1 transmitter per 100–200 m²

Starting point: a concept for an agricultural machinery plant

We consider an agricultural machinery plant belonging to a global group. The pilot covers one assembly hall: an isometric map, transmitters, hot work permits built from templates, and risks assigned to places. The plant has several other buildings, however, and the decision to expand will only be made after the pilot is assessed.

This is a conceptual scenario. It does not describe a completed deployment, only a way of thinking that reduces the cost of the next steps. Our reference point is company experience: across 20 deployments and pilots we recorded a 100% conversion of pilots into deployments, but every expansion requires order in the structure.

How the system organizes a plant: from view to location

The plant structure has successive levels: plot, view (division), building, line and location. In the large-facility plant mode, the editor path is View, Building, Line, Location. Understanding these levels is the condition for a calm expansion.

What a hall means in the data model

The level called a hall in everyday conversation is, in the data model, a view, meaning a plant division, not a single building. Buildings are areas inside a view. If we name the view after one hall during the pilot, a second building will create a naming conflict: the division's view will be taken by the name of a single block.

Single-storey and multi-storey buildings

Floor levels and the multi-level marker are created only for buildings with more than one level. A building with ground floor only does not get a floor row, because the level panel would show other buildings' floors. In an expansion scenario this is an important hint: a new single-storey warehouse is added without floors, while a two-storey assembly department gets its floors.

Number of transmitters in a 5,000 m² hall by placement density

Number of transmitters in a 5,000 m² hall by placement densityBar chart: 25, 33 and 50 transmitters in a 5,000 m² hall depending on placement density.01020304050pcs1 per 200 m²: 25 pcs25 pcs1 per 200 m²1 per 150 m²: 33 pcs33 pcs1 per 150 m²1 per 100 m²: 50 pcs50 pcs1 per 100 m²
Source: Sample calculation: 5,000 m² area divided by the rule of 1 transmitter per 100–200 m² in a building

Stage 1: pilot one hall with the next ones in mind

In the pilot we place transmitters according to the company documentation rule: one transmitter per 100–200 m² inside a building, and plant roads are covered at intervals of about 100 m. For a hall of 5,000 m² this gives between 25 and 50 transmitters, depending on the density of machines and the required accuracy. The position is calculated from signals of several transmitters, averaged on the map, and works without GPS.

At this stage we create three elements at once that will not be changed during the expansion: the plant view with georeferencing, the building inside the view, and the lines as disjoint fields. This way the pilot is not an island, but the first leaf of the target tree.

  • The view name matches a division or part of the plant, not a single hall.
  • Georeferencing (anchor point, rotation, scale) and the orthophoto belong to the view and are set once.
  • Lines inside a building have disjoint fields, with no overlap on the same level.

Stage 2: adding further buildings

Once the pilot is positively assessed, we add the next buildings in the same view. Building children fit inside the outline reduced by the wall thickness: in the documentation example, 1 m from each side. The consistency gate requires zero lines extending beyond the footprint, so a drawing error is caught before saving.

New hot work permits, risks and documents do not need separate configuration for each hall. Risks are assigned to locations at every level of the hierarchy, and documents, audio and video recordings are inherited down the tree. A safety video assigned to the view therefore applies in a newly added building from the first day.

The same OHS checklist can be run across many facilities, and the results are comparable between facilities and periods. The plant director therefore gets a picture of the whole in the same layout in which the single-hall pilot was viewed.

Stage 3: the whole plant and one picture of the situation

After the buildings are added, the dispatcher sees SOS and no-movement events from many halls on one map, and the OHS manager compares checklist results. The system works as an independent layer complementing the plant's existing systems (access control, time and attendance, HR, ERP) and offers 18 modules on one platform, so expansion does not mean buying more tools, only enabling modules in areas that already have a map.

The expansion does not touch access readers. InnerWeb does not manufacture or replace them: card swipe events arrive from the plant's existing access control system, regardless of the number of halls on the map.

Conclusions for the plant director

First, the location structure is designed once, during the pilot, at the level of the whole plant. Second, the single-hall pilot is the first leaf of the tree, not a separate project. Third, the cost of expansion depends mainly on the number of transmitters in the new buildings and on the work of drawing outlines, not on rebuilding what already works.

  • Pilot: a plant view with georeferencing, one building, disjoint lines.
  • Expansion: new buildings and lines in the same view, floors only where floors exist.
  • Whole: reports and checklists in one format for all halls.

Video

Frequently asked questions

Does the map of the plant have to be rebuilt after the pilot?

No, provided the plant view with georeferencing and the split into buildings and lines were designed from the start. Further buildings are added in the same view.

Does every building need floors?

No. Floors are created only for buildings with more than one level. A building with ground floor only does not get a floor row.

Does expansion require replacing card readers?

No. InnerWeb does not manufacture or replace access control readers. It receives swipe events from the plant's existing access control system.

Let's plan the expansion together

Let's talk about a location structure that will hold further halls. We will show it on the map of a plant similar to yours.

Let's talk