InnerWeb
Skip to main content

Scope of a location system in an Ex zone: practices

An offer for locating people in an Ex zone is honest when the reader knows what works today, what depends on a third party and what the system does not do. Sales staff and the solution architect can achieve this with one document structure. Below are the practices that organise it.

13 s
refresh interval of the evacuation list
Source: feature card
6
groups of people on the evacuation list
Source: feature card

Why the functions should be split into three groups

A client in an Ex zone makes decisions on which people's safety depends. An offer that puts everything into one table of functions creates the impression that everything is available from day one. When it turns out otherwise, the sales person, the plant and the whole project lose trust.

Three groups solve the problem: functions that work today, functions that depend on a third party, and functions out of scope. Every function in the offer goes into exactly one group, and an item without an assignment is a signal that the description is incomplete.

Group 1: what the system does today

The first group contains what works without the participation of other suppliers. The phone receives signals from several transmitters at once and sends them every few seconds, and the position is averaged on the map. The system shows the list of people and the last known position. The stillness alarm works in two parts: the phone analyses the sensors, the server independently measures time, and the full alarm starts only when both agree.

When the stillness threshold is exceeded, the system sends push and email notifications, creates a permit for the alarm from the ALARM template, marks the alarm on the map and can trigger an external webhook. The evacuation list is one screen showing who is on site now. It refreshes every 13 seconds and divides people into six groups, with a one-page printout per group for coordinators at the assembly point.

Sample split of offer functions into three groups (number of functions)

Sample split of offer functions into three groups (number of functions)Pie chart: five functions work today, two depend on a third party, two are out of scope.Works today: 5 functions (55.6%)Depends on a third party: 2 functions (22.2%)Out of scope: 2 functions (22.2%)9functionsWorks today5 functions (55.6%)Depends on a third party2 functions (22.2%)Out of scope2 functions (22.2%)
Source: Sample calculation: illustrative layout, five functions from this page work today, two depend on a third party and two are out of scope

Group 2: what depends on a third party

The second group contains the integration of gas readings from detectors. It depends on the protocol of the detector manufacturer and is a topic for a meeting, not a standard feature. The sales person should not record it as available until the detector manufacturer releases the protocol and the scope is agreed.

This group also includes certification for zones 1 and 21. InnerWeb ATEX transmitters are approved for zones 2 and 22. Certification for zones 1 and 21 is arranged for the client's installation, without a promise of a date, and the scope of zones is verified against the plant's zone classification design.

Group 3: what is out of scope

An evacuation route and an assembly point are not functions of the system. The system supplies the list of people and the last known position, while the plant sets the route and the assembly point in its own procedures. Writing this into the offer prevents a situation in which the client expects the phone screen to show the escape route.

Similarly, the system does not replace the classification of zones or the assessment of explosion risk. It provides proof of position and time, not a decision to permit work in a zone.

How to record it on the implementation card

The implementation card for the architect should have three sections with fixed headings and an identical layout in every project. This lets the client compare projects and gives the implementation team one working template.

For each item in group 2, record the owner of the dependency and its status: contact established, protocol available, protocol not available. This leaves no room for guesses, and the status can be refreshed at project meetings.

Checklist

Video

Frequently asked questions

Is the evacuation a system function?

Partly. The system shows the list of people and the last known position, and the evacuation list divides people into six groups for printing for coordinators. The route and the assembly point remain on the plant side.

How does the stillness alarm work?

The phone analyses the sensors, and the server independently measures time. The full alarm starts only when both agree.

What happens after a stillness alarm?

The system sends push and email notifications, creates a permit for the alarm from the ALARM template, marks the alarm on the map and can trigger an external webhook.

Is there a date for certification of zones 1 and 21?

There is no promise of a date. Certification is arranged for the client's installation.

Let us build an implementation card with three groups

We will help you split the functions into those that work today, those that depend on a third party and those out of scope. Book a call.

Let's talk