InnerWeb
Skip to main content

Splitting roles in a rollout: partner, manufacturer and client

When an authorised partner runs the rollout and the manufacturer grants the licence, the client needs to know whom to contact about the network, server, configuration, training and faults. Below are implementation notes: stages, pitfalls and the order of decisions.

3
parties and three contracts in the partner model
Source: InnerWeb partner model
99.5%
sample availability per month in the maintenance agreement
Source: InnerWeb partner model

Three parties, three contracts, one responsibility for the whole

The partner model consists of three contracts: the licence, which the client signs with the manufacturer, and the maintenance and implementation contracts with the partner. This structure separates the software rights from responsibility for implementation and maintenance, but it requires each party in the project to know what belongs to it.

The table below describes the recommended split. Every plant has its own conditions, so it is worth recording the split in an annex to the implementation agreement.

Who is responsible for what

The split is described by the areas where disputes most often arise.

Software manufacturer

Responsible for the product, the licence and the guarantee of operational continuity set out in the licence agreement, for supplying the industrial beacon (industrial design, CE declaration, ATEX construction for zones 2/22), and for training and implementation support for the partner. Other equipment, such as active cards, multi-chargers, the watch, the radio, readers and kiosks, is purchased and integrated separately.

Implementation partner

Responsible for installation, configuration, implementation and maintenance. Performs the maintenance agreement with response and repair times and availability of 99.5%. Invoices everything: implementation, maintenance and, during the pilot, the licences as well.

Client

Responsible for access to the facility, network and server resources, appointing coordinators and decisions on scope and acceptance. Decides who on the client side receives reports from employees and passes them on to the partner.

Repair time in the SLA by fault category

Repair time in the SLA by fault categoryBar chart: repair 8, 24 and 168 hours for categories A, B and C050100150200hoursCategory A: 8 hours8 hoursCategory ACategory B: 24 hours24 hoursCategory BCategory C: 168 hours168 hoursCategory C
Source: Sample SLA categories (B: 1 day, C: 7 days); the values are set by the maintenance agreement

Fault reports: categories and times

The SLA parameters (availability, response and repair times) are set in the maintenance agreement, for example availability of 99.5% per month. Faults are split into categories. For example, category A: response in 12 hours, repair in 8 hours; category B: response the next day, repair within 1 day; category C: repair within 7 days. The specific values and the way the parties settle them are recorded in the maintenance agreement, matched to the plant.

The first line is the partner. If the problem concerns the product, the partner escalates it to the manufacturer. The client does not need to work out who the right addressee is, but should know the reporting number or channel and the category that is assigned to the report.

Pitfalls in splitting roles

The most common pitfalls lie where the boundaries of responsibility meet. It is worth agreeing them at the start, because changes are harder to make once the system is live.

  • network and server: who provides them, who configures ports and access, who is responsible for backups
  • integrations with the client's systems: who issues the API keys and who rotates them
  • licences: who counts active users (accounts with at least one login in a month)
  • training: who runs the first sessions and who runs the follow-up sessions for new employees
  • configuration changes after acceptance: who orders them and who approves them

Order of decisions before the start

We recommend the following order: first the licence agreement and the choice of package, then the implementation scope, then the maintenance terms with the SLA, and only at the end the schedule. This order avoids a situation in which the date is fixed but the scope is not yet defined.

Indicative ranges from rollouts in 2025-2026 for a typical implementation are from PLN 12,600 to PLN 34,000 net as a one-off payment, and the fixed package of 50 licences costs PLN 2,500 net per month; each quote is individual. Manufacturer prices are without the integrator's mark-up, which is added on the partner's side.

Video

Frequently asked questions

Whom does the client report a fault to?

To the partner, which is the first line under the maintenance agreement. The partner escalates product problems to the manufacturer.

Who is responsible for the network and the server?

The scope is recorded in the implementation agreement. Usually the client provides the resources and the partner configures the system.

Is the manufacturer a party to the contract with the client?

Yes, in respect of the licence. The licence agreement is concluded directly with the client and does not depend on how long the cooperation with the partner lasts.

Let's agree the split of roles before the start

We will provide a template annex with the split of responsibility. Book a conversation or a demo.

Let's talk