InnerWeb
Skip to main content

Partner checklist before the first implementation at a plant

The first visit to a plant decides whether the project starts smoothly or gets stuck on missing access and unclear roles. The checklist below collects what the partner should have ready before entering the site: from agreements and the quote, through roles and the network, to administrator training.

3
agreements to separate before the visit
Source: InnerWeb partner model
1,200 PLN
training module, first site, net
Source: indicative ranges from 2025-2026 implementations; individual pricing applies

Documents and quote

Before the visit the partner should have a clear layout of the three agreements: the licence agreement with the producer, and the maintenance and implementation agreements with the partner. The customer should know which agreement is with whom, and have an offer with separated items: licences, implementation, options and maintenance.

The quote is based on the number of active users, not on people entering the site. Plant employees and coordinators of external companies are counted, while guests, employees of external companies and drivers are not. Producer prices carry no integrator markup, so the partner markup must be stated explicitly.

Roles, permissions and security

Roles in the system and the permissions matrix make it possible to configure access for administrators, security, health and safety staff and coordinators of external companies without code changes. The partner should come with a proposal of the role table and a list of people the customer must name before configuration starts.

The security panel scans a QR badge or an RFID card and gives a verdict on whether the person may be on the plant, based on valid trainings, qualifications and permits. It is worth agreeing with the head of security what data security will see at the gate and who updates the lists.

Partner preparation areas: number of checkpoints

Partner preparation areas: number of checkpointsHorizontal bar chart of checkpoints in four preparation areas0123pointsAgreements and quoteAgreements and quote: 3 points3Roles and securityRoles and security: 3 points3Network and integrationsNetwork and integrations: 3 points3Training and acceptanceTraining and acceptance: 2 points2
Source: Number of checkpoints in the checklist on this page

Network, server and integrations

The customer's IT department should receive in advance a description of the requirements: application access, ports, server requirements and the integration method. The platform provides a REST API (versions 1 and 2, JWT authentication) and webhooks to the automation platform, which the partner can use to integrate with the customer's systems.

If the customer's network blocks all outbound traffic from the application host, alarm webhooks are persisted in a queue, and an external poller receives them over an inbound channel and forwards them. The alarm is not lost, but the partner must agree in advance who runs the poller and where.

Training and acceptance

Training of the customer's administrators is part of the implementation, not an extra. The partner agrees the date, the list of participants and the scope: roles, templates, alarm handling, reports. The training module costs 1,200 PLN net for the first site and 600 PLN for each additional one.

Acceptance is based on an audit trail, which records changes to selected data together with the author and the time. This is proof of the configuration performed. It is worth attaching it to the acceptance protocol.

Checklist

Video

Frequently asked questions

When should the partner give the customer's IT department the requirements?

Before the first visit to the site. Early information about access, ports and integrations shortens implementation, because the IT department has time for decisions and approvals.

Does the partner need its own server?

It depends on the model agreed with the customer and the producer. The partner should describe in its offer where the application runs and who is responsible for its maintenance.

How does the partner prove the configuration was performed?

With an audit trail that records changes to selected data together with the author and the time. It can be attached to the acceptance protocol.

Let's prepare the first implementation together

We will go through the checklist with you on a specific plant and fill any gaps before the visit.

Let's talk