Who this list is for and when to use it
The list is intended for the implementation manager on the client side and for the integrator. You use it after the configuration is finished and before the day on which the staff log in to the system. Each point has a clear answer: met or not met. An unmet point holds back the start until it is corrected. It is not recorded as a note for later.
The list relies on the fact that the next plant benefits from the experience of the previous one. The pattern of structure, roles and reports is already known, so the scope of the check is short. Record each ticked point in the note of the plant's start-up.
Area 1: plant structure
The plant structure has successive levels: plot, view (division), building, line and location. In the large-facility mode the path in the editor is view, building, line, location. The check consists of confirming that the new plant maps it in line with the group's shared standard.
Walk through a few objects at each level and confirm that the names follow the standard, and that a level named hall means a division or view, not a single building. Also check that the georeferencing of the view (anchor point, rotation, scale) is set, because without it the objects on the map will not match the plan.
Number of checklist points per area
Area 2: roles and permissions
Permissions follow from roles with inheritance, a scope matrix and a ladder for granting roles. Before the start, check who holds the Secretariat, Administrative employee and Inviter roles, and whether the scope matches the tasks of each person. Remember that no one can grant a role higher than their own, so the order of granting matters: higher-level roles first, lower ones afterwards.
If the group creates its own roles, also verify their names: no role name may contain another role name as a substring, because searching by role relies on text matching.
Area 3: reports and the integration area
Periodic reports are configured with rules for each product, with a daily, weekly or monthly cadence. For the new plant, check whether it has its own rules, whether the recipients are right, and whether the group headquarters receives the consolidated summary. The scope of locations and recipients is set separately for each rule, so it is easy to make a mistake when copying a configuration from the previous plant.
In the integration area, confirm that InnerWeb works as a system complementing the plant's existing systems: access control, time and attendance, HR and ERP. Check that events from the access control system reach the platform and that data from ERP or HR matches the structure of the new plant. Every client has an isolated instance, so verify that the new plant works on the correct database and not on the database of the previous plant.
Who takes the decision to go live
The decision to open the system is taken by the implementation manager after going through the whole list. For a group it is worth establishing that the start of a plant requires confirmation by the group's BHP manager, who checks compliance with the standard. A record of this decision, together with the ticked list, is the evidence for an audit that the plant was started up according to the same procedure as the previous ones.
Checklist
Video
Frequently asked questions
Does the list apply only to plants similar to the first one?
No. The areas are fixed, but the scope of the check in each area is matched to the plant, for example to the number of buildings or the systems to integrate.
Who ticks off the list?
The implementation manager on the client side, together with the integrator. In a group it is worth adding the confirmation of the group's BHP manager.
What do we do when a point is not met?
Hold back the start, correct the configuration and return to that point. An unmet point is not a note for later.
Starting up another plant?
We will go through the checklist with your team and confirm that the plant is ready before the system opens to its staff.
Let's talk