InnerWeb
Skip to main content

Plant readiness checklist before the deployment start

A week before the deployment starts, the plant director and the IT department can confirm with one list whether everything on the client's side is ready. A single missing item usually delays the whole stage, so it is better to check it on Monday than to discover it on Wednesday. Below is the list with a comment on where each item comes from.

min. 2
administrators on the plant's side (one per location)
about 500
locations in the plant's naming in the first stage of the shortened variant

Why check readiness a week in advance?

The deployment has a rigid schedule of stages: in the two-stage variant two stages of 4 weeks each, in the shortened one 6 weeks in three stages of 2 weeks each. With stages this short, one missing element on the plant's side, for example an administrator not appointed or a network not available, immediately extends the schedule.

The checklist below is not a set of formalities for the supplier. It is a list of decisions and preparations that the plant makes internally and which then allow us to start work on the first day without downtime.

People and responsibilities

The first block concerns people. On the plant's side at least 2 administrators are required, one per location, together with the person or persons for acceptances. The administrator knows the plant's rules, decides on the naming of locations and accepts the results of the stages.

It is also worth appointing deputies. If an administrator is on holiday in the week of acceptance, the lack of a deputy will hold up the acceptance of the stage and thus the next stage.

  • At least 2 administrators have been appointed, one per location.
  • A person for acceptances and their deputy have been named.
  • The date and participants of the weekly status meeting (about 10–15 minutes) have been set.

Time of mandatory meetings and training on the plant's side

Time of mandatory meetings and training on the plant's sideHorizontal bar chart: status meeting up to 15 minutes, entry point training 60 minutes, classroom training 180 minutes.050100150200minutesStatus meeting weekly(maximum)Status meeting weekly (maximum): 15 minutes15Entry point training oninstallation dayEntry point training on installation day: 60 minutes60Classroom training, one dateClassroom training, one date: 180 minutes180
Source: and; hours converted to minutes

Server, network and infrastructure

The second block is infrastructure. For the mounting of beacons, only the LoRa nodes and gateways require power and network: PoE power and network. The client's scope covers the 230 V supply and LAN network for the nodes, IP addressing and the mounting places.

Beacons are battery-powered and need no power supply or cabling, so their number does not affect the demand for sockets. However, the number of nodes and gateways that require the network determines how many points have to be prepared before the crew arrives.

  • Access to the server or environment for the instance has been confirmed (separate server, accounts and permissions).
  • 230 V sockets and LAN network have been prepared at the mounting places of the nodes and gateways.
  • IP addressing for the nodes and gateways has been set.
  • The IT department knows the scope: the system is an independent supplement to the plant's systems (access control, time and attendance, HR, ERP).

Locations, access and data

The third block concerns the plant's data. In the first stage of the shortened variant about 500 locations in the plant's naming are created, so the plant should have a ready list of names: halls, gates, zones, warehouses. Without the list, it has to be created during the deployment, which costs time.

In addition there is access to the premises in which the devices will be mounted, and the indication of the mounting places. If the works require permits according to the plant's rules, the client launches them in advance.

It is also worth preparing a list of external companies that will be imported into the system in the first stage, together with the data needed for their admission.

  • A ready list of the plant's location names (halls, gates, zones, warehouses).
  • Mounting places indicated and access to the premises confirmed.
  • Work permits for the mounting planned.
  • A list of external companies prepared for import.

Training and gatehouses

The last block concerns the people who will operate the system. Entry point training on the day of installation covers up to 5 people and lasts about 1 hour. Classroom training takes place on two dates, about 3 hours each, in groups of up to 12 people.

For the director the important question is: can people be released from work for the training? Two dates make it possible to cover all shifts, but they must be entered in the schedule in advance.

  • Up to 5 people designated for the entry point training on the day of installation.
  • Two classroom training dates of about 3 hours each, in groups of up to 12 people, planned.
  • Care taken that the dates cover all the working shifts of security.

Checklist

Video

Frequently asked questions

What if the plant does not yet have a list of location names?

The deployment can start, but the list is created during the work, which extends the first stage. It is better to prepare it before the start, based on existing plans and the naming used in the plant.

Does IT have to switch off anything in the plant's network?

The system is an independent supplement to the plant's existing systems, so it does not require replacing them. IT prepares mainly the network and the addressing for the nodes and gateways.

How many people must the plant train at the start?

At the workstation up to 5 people for about an hour, and in a classroom in groups of up to 12 people on two dates. The specific staffing is agreed with the head of security.

Let us check readiness together

We will go through this checklist with you in a short conversation before the start and indicate what is worth closing earlier. We invite you to get in touch or to a demo.

Let's talk