Three-stage timeline
The sample deployment scope is divided into three stages of two weeks each, with an acceptance at the end of each. The first is the server and the map, the second is the trainings and permits, the third is the security posts at the gatehouses. Data must be ready before the stage it concerns, because the acceptance depends on its completeness.
The payment for the deployment is split into 50% at the order and 50% after go-live. The sample pricing is 13,000 PLN net for one site and 21,000 PLN net for two. Delays in data move the acceptance date, which shortens the time the system is used in the first year.
Data for stage 1: server and map
Starting the server and the map requires the site plan in digital format, the indication of zones and buildings, and a decision on where the installation is hosted: locally without a connection to the producer or in the cloud. The plant also names at least two administrators who will manage the system after the start.
Good practice is to hand over the plan with the entrances, routes and high-risk zones marked. The more accurate the plan, the fewer corrections after the first acceptance.
Duration of the deployment stages
Data for stage 2: trainings and permits
The second stage requires the list of external companies working on site, the templates of work permits and training materials: presentations, videos and instructions. The plant also informs external companies about the obligation to register workers in the system before the trainings begin.
The list of companies should contain their names, the scope of work and the named coordinator. The permit templates should be up to date and approved by the safety team. The training of the entry point on the day of installation covers up to 5 people (about 1 hour), and classroom training is held on two dates of about 3 hours each, in groups of up to 12 people.
Data for stage 3: gatehouses
The third stage launches the security posts at the gatehouses. It requires the list of posts, the working hours of the security shifts and the indication of the people who will operate the system. The plant confirms who from security will receive an account, because all users of the plant who logged in during the month are counted toward the license count.
After the stage closes, the final acceptance takes place and the second part of the deployment is paid. For a comparison of the whole budget it is worth looking at the calculation of the first 12 months.
Most common gaps and how to avoid them
The most common gap is an outdated site plan that does not show new halls and changed entrances. The second is a list of external companies without named coordinators, which blocks registration in advance. The third is permit templates in several versions, none of which is marked as the one in force. We recommend that one week before the start the person responsible on the plant side goes through the whole list and confirms that it is complete in one sentence in a message to the deployment team. This practice shortens stage 2 and makes it possible to fit into six weeks.
Checklist
Video
Frequently asked questions
What happens if the list of companies is late?
The acceptance of stage 2 will be postponed. That is why the list of companies and the permit templates are collected before the rollout begins.
Does the plant need its own server?
The system works locally without a connection to the producer or in the cloud, as the plant decides.
Who should accept the stages?
The person named by the plant, usually from the safety team, together with the system administrators.
Let us prepare the data before the start
We will send a checklist with deadlines for each stage and indicate the people responsible on the plant side.
Let's talk