Starting point: two sites and one procedure
The production plant with two sites had the same problem at each of them: external contractors entered the premises on the basis of paper permits, and the completeness of their training was checked at the gate only on a spot basis. Management wanted one procedure, one register and proof of who was admitted to work, when and on what terms.
The system supplier proposed a two-stage schedule: two months in total, split into two blocks of 4 weeks each. The split was not accidental. The first block builds the foundation, meaning the instance, the plant structure and the knowledge a contractor must have before entering. The second block launches the admission process itself and the control points at the gates.
When both stages are finished, acceptance and production go-live follow. In this scenario the whole cycle, from the order to the first admission of a contractor through the system, fits into about 2 months.
Stage one: weeks 1-4, foundation and knowledge
In weeks 1-2 the supplier launches a separate system instance for the plant, configures zones, gates and roles, and imports the data of contractors who already work with the plant. Thanks to the import, administrators work on a real list of contractors from day one, not on test data.
In weeks 3-4 the training module is built, with tests and language versions, together with the legal package containing the terms of cooperation. This is an important element, because the introductory training and the terms are the first documents a contractor accepts before seeing the site.
- weeks 1-2: instance, zones, gates, roles, import of contractor data
- weeks 3-4: training module with tests, language versions, legal package and terms
- stage acceptance: a working instance with the plant structure mapped and training running
Payment split in the two-stage variant
Stage two: weeks 5-8, permits and gates
The second stage starts with permit templates, the set of especially hazardous work types, admission matrices and approval paths. The admission matrix answers the question which qualifications and training a person must hold to perform a given type of work, and the approval path states who approves a permit and in what order.
Next, the supplier configures guard posts at the gates, prints cards and trains the guards and the plant staff. The guards receive a tool that shows on screen whether a contractor company and a specific person hold valid training and a permit, without calling the OHS department.
What the guard at the gate receives
The guard post works on the ready data from stage one: the list of companies, their employees, training and roles. For this reason stage two does not require entering data again, only matching it with permits and control points.
What the plant must deliver on its side
The schedule holds only if the plant names specific people. At least 2 administrators are required, one per site, together with a weekly status huddle lasting about 10-15 minutes. The administrator decides on the structure of zones and roles, accepts document templates and is responsible for the contractor data.
The most common cause of delay in rollouts of this kind is a lack of decisions, not a lack of functions: who approves permits for work at height, which site has which gate, how the zones are named. The huddle is there to close such questions in the week they appear.
Payment and acceptance: why 50/50
In the two-stage variant the payment is split into 50% at the order and 50% after production go-live. The plant therefore pays the second half only when the system actually admits external contractors. This split moves part of the risk to the supplier and encourages both sides to keep to the stage two deadline.
Two acceptances, after week 4 and after week 8, give the plant two decision points. If after stage one the zone structure needs changes, they are made before the permits are configured, not after.
Conclusions for plants with several sites
Two stages of 4 weeks work well when the plant has at least two sites and needs shared knowledge (training, terms) before local processes start. If the availability of administrators is limited, it is worth considering a longer or shorter variant, described on the page about choosing the schedule.
Whatever the variant, the rule is the same: each stage ends with an acceptable result that can be checked on screen, not with a description of work. The system is independent of the plant's existing solutions and complements them, so the rollout does not require replacing readers or other devices.
Video
Frequently asked questions
Does the two-stage rollout require stopping the gate?
No. Stage one takes place on the system instance and data, and the guard posts are configured in stage two. The gate works in its existing mode until production go-live.
When do external contractors start using the system?
The training module works after stage one, that is after 4 weeks. Admission through the system at the gates starts after production go-live at the end of stage two.
Do the access control readers have to be replaced?
No. InnerWeb is a software producer and integrates with the plant's existing access control system without replacing it.
Plan the rollout for your plant
Tell us about your sites and external contractors, and we will prepare a schedule with stage acceptances.
Let's talk