InnerWeb
Skip to main content

Input data for the hall map: checklist

Before the configuration of the hall map starts, the plant should give the integrator five groups of data: the hall plan, the floors, the list of locations, the transmitter layout and the alarm templates. A complete package shortens the configuration and reduces corrections after the first test in the hall. The list below explains what to collect and why.

5
groups of data to give the integrator
Source: sample calculation
30-60
transmitters for a 6,000 m2 hall
Source: sample calculation

Hall plan and buildings

The basis of the map is the hall plan. The online map shows the plant in an isometric 2.5D view with buildings, vehicles, workers and places of work, so the integrator needs a plan that shows the outline of the building, the partitions and the main workstations. The more accurate the plan, the fewer corrections after the first start-up.

Include information about the area of the hall and about which parts of the building are to be covered by the system. For the concept of an assembly hall of 6,000 m2, the area is the starting point for estimating the number of transmitters, so an imprecise value immediately distorts the purchasing plan.

Floors and labels

The 3D map editor describes buildings, floors and labels. Provide the number of floors if the hall has mezzanines or office floors, and the names that the workers use. Labels on the map should match the vocabulary of the workforce, because the dispatcher and the shift supervisor talk about workstations the way they are named on the hall floor.

Agree one list of names and do not change it during configuration. Changing the naming after the map is built means corrections to labels, locations and templates, and in an extreme case also to permits that have already been issued.

Transmitters for three example halls

Transmitters for three example hallsBar chart: a 3,000 m2 hall needs 15-30 transmitters, a 6,000 m2 hall 30-60, and a 9,000 m2 hall 45-90 transmitters020406080100pcs1 per 200 m2 (3,000 m2): 15 pcs15 pcs1 per 100 m2 (3,000 m2): 30 pcs30 pcs3,000 m21 per 200 m2 (6,000 m2): 30 pcs30 pcs1 per 100 m2 (6,000 m2): 60 pcs60 pcs6,000 m21 per 200 m2 (9,000 m2): 45 pcs45 pcs1 per 100 m2 (9,000 m2): 90 pcs90 pcs9,000 m2
  • 1 per 200 m2
  • 1 per 100 m2
Source: Sample calculation: area divided by 200 and by 100 m2 per transmitter

Locations and assigned templates

The list of locations covers the levels of the hierarchy: hall, area, line, place. Risks with the required protective measures are assigned at these levels, and the course of a permit follows the template linked to the location, configured in the installation data without changes to the code. The list of locations is therefore also a list of places that need permit templates.

Attach to the list which locations are to be linked to alarm templates. The immobility alarm and SOS appear on the map only when the location is linked to an alarm template: ALARM for immobility, SOS for SOS. Without this, the alarm exists only in the memory of the system.

Transmitter layout

The position of a worker comes from the signals of several BLE transmitters averaged on the map and works without GPS. For buildings a density of 1 transmitter per 100-200 m2 is assumed, which for a 6,000 m2 hall gives 30-60 units in a sample calculation. The integrator proposes a layout based on the plan, but the plant knows the obstacles that are not on the drawing: racks, tall machines, temporary partitions.

Mark on the plan places of particular importance, such as the welding shop, the permit issuing zone or places where workers are sometimes alone. Denser coverage makes more sense in these places than in a component store.

  • Building outline and hall area.
  • Obstacles affecting the signal.
  • Places requiring more precise location.
  • Places with limited access for mounting transmitters.

The starting package and who collects it

Input data is usually collected by the security manager together with the IT department and the maintenance department. It is worth preparing one package and giving it to the integrator once, rather than completing it in successive e-mails. For the concept of a machine plant, where the hall map with transmitters is the basis for permits, SOS and the dispatcher, such a package is the first step of the implementation scenario.

InnerWeb is an independent system that complements the client's existing systems, so the package does not require changes to other systems. It does require consistency of plans and names between departments, which is most often the biggest challenge.

Checklist

Video

Frequently asked questions

Can the configuration start without a hall plan?

A conversation and an estimate can start, but the map configuration requires a plan. The area from the plan also decides the number of transmitters.

Why a list of locations when the map already shows them?

Risks, permit templates and alarm templates rely on the locations. An alarm without an attached template will not appear on the map.

Is changing the naming after configuration a problem?

Yes, because it requires corrections to labels, locations and templates. It is better to agree one list of names before the start.

Let us collect the data for your hall map

We will send you a data list tailored to your plant and discuss who on your side prepares it. We welcome a conversation.

Let's talk