InnerWeb
Skip to main content

Plant-side requirements before the implementation starts: implementation notes

The rollout of a system starts earlier than the installation, with decisions and data on the plant side. We describe five success conditions, a six-week schedule in three stages, and the traps that most often delay the start: a single administrator, a late list of external companies and no plant plan.

2
minimum number of administrators on the plant side
Source: price list
6 weeks
sample rollout time in three stages
Source: price list
2-10 wks
installation time from the order
Source: price list

Five success conditions on the plant side

The success of the rollout depends on five things that the plant must deliver regardless of the supplier: at least two administrators, a timely list of external companies, training materials, permit templates and a plant plan, and informing external companies about the duty to give notice in the system.

Each of these conditions has a concrete effect when it is missing. Below we describe them in the order in which they usually block the rollout.

Stage 0: appointing at least two administrators

Two administrators is the minimum, because one person on leave or after changing jobs stops all administration. They should be people in different roles, for example from the OHS department and from security, so that both perspectives have a representative.

Reserve time in their calendars for training and for the first weeks of work. An administrator who has one hour a week for the system will not manage to answer the questions of external companies during the start-up period.

Sample rollout schedule: weeks to stage acceptance

Sample rollout schedule: weeks to stage acceptanceHorizontal bar chart: stage acceptance after 2, 4 and 6 weeks from the start of the rollout.0246weeks from startStage 1: server and mapStage 1: server and map: 2 weeks from start2Stage 2: training and permitsStage 2: training and permits: 4 weeks from start4Stage 3: security workstationsStage 3: security workstations: 6 weeks from start6
Source: Price list: rollout of the sample scope takes 6 weeks in three stages of 2 weeks each

Stage 1: list of external companies and notice of the duty to announce

The list of external companies working on the plant site is the input data for notifications. Collect it before the start: the company name, the scope of work and the named coordinator who will announce workers and submit declarations in the system. Without the list, the first weeks will go to manual data entry.

In parallel, external companies must be informed of the duty to announce in the system. Do it in writing and in advance, because the coordinator needs time to set up an account and learn the process. Information sent on the day of the start causes queues at the gate.

Stage 2: training materials, permit templates and the plant plan

The training module works on the plant's materials, so they must be provided: films, presentations, OHS instructions. Permit templates for work are the second set of data that goes into the system. The third is the plant plan, because the map and the security workstations are built on it.

The plan is a critical element: without it the first stage, that is the server and the map, cannot start. Prepare the plan in a readable form with buildings, entrances and zones marked, even if it is not perfect. Refining the plan can continue during the rollout, provided the basics are available from the start.

Schedule: 6 weeks in three stages

In the sample scope the rollout takes 6 weeks in three stages of two weeks each, and each stage ends with acceptance. Stage one is the server and the map, stage two is training and permits, stage three is the security workstations at the gatehouses. Installation takes from 2 to 10 weeks from the order, depending on scope.

Data provided by the plant is needed at specific moments: the plant plan in week zero, training materials and permit templates before stage two, the list of external companies and the notice of the duty to announce before stage three. A delay in any of these deliveries pushes back the acceptance of the next stage.

Stage acceptance

Each stage has its own acceptance, so the plant knows on an ongoing basis what is ready. Acceptance is not a formality: it checks whether the map matches the plan, whether permits go through the full cycle and whether the gatehouse handles entries. The payment for the implementation is split 50% at ordering and 50% after go-live.

Traps that most often delay the start

The first trap is one administrator instead of two: in case of absence nobody can approve changes. The second is a list of companies sent halfway through the rollout, when the map and permits are ready but there is nobody to announce people. The third is a plant plan in a form that cannot be used, for example an old drawing without markings.

The fourth trap concerns communication: external companies learn about the duty to announce in the system from security at the gate. Then the first day of the rollout becomes a day of conflict, not a day of go-live. Send the information in advance and name a contact person.

Video

Frequently asked questions

Why are at least two administrators needed?

One person is a single point of failure: leave or a change of job stops administration. Two administrators from different departments ensure continuity and approval of changes.

Does the plant plan have to be perfect at the start?

No, but it must be readable and show buildings, entrances and zones. Refinement can continue during the rollout, provided the basics are available from the start.

When should external companies be informed about the notice duty?

In advance, in writing, before the stage of security workstations. The coordinator of each company needs time to set up an account and learn the process.

Let's get your plant ready for the start

We will send the list of data the plant should prepare before installation. Book a meeting with the InnerWeb team.

Let's talk