InnerWeb
Skip to main content

Framework agreement for OHS software: recommendations for procurement

A procurement department buying OHS software for a group of plants usually starts with a framework agreement, while the first plant orders separately. Below are eight clauses worth enforcing before the first order, with reasoning based on the parameters InnerWeb uses in its offers.

99.5%
availability of the server part per month
Source: price list
14 days
retention of daily backups
Source: price list
50% + 50%
split of the implementation payment
Source: price list

Who these recommendations are for

We address these recommendations to the procurement department that orders the system for at least two plants or plans to expand after a pilot. For a single plant the same set can be applied in a simplified form. The starting point is separating three things that often end up in one unclear line item: implementation, licences and maintenance.

In the InnerWeb model, implementation is billed by a separate order, independently of the maintenance agreement, and payment is split 50% at ordering and 50% after go-live. Licences come from the software producer. Such a structure helps procurement, because each part can be assessed, compared and, if needed, terminated separately.

Recommendation 1: implementation and maintenance as separate items

Enforce a clause that implementation is a one-off order with its own schedule and acceptance, and maintenance is a separate agreement. Reasoning: the cost of implementation depends on the number of sites (in the sample quote 13,000 PLN net for one and 21,000 PLN net for two), while the cost of maintenance depends on the number of active users and the scope. Mixing both items makes budget control impossible when the system is expanded.

Also arrange the payment split: 50% at ordering and 50% after go-live is a structure in which the second part is tied to the result. If the supplier proposes another split, require an acceptance criterion written into the agreement.

First 12 months: cost of one and two sites

First 12 months: cost of one and two sitesBar chart: 37,000 PLN, 52,200 PLN and 72,600 PLN net for the first 12 months in three configurations.020,00040,00060,00080,000PLN net1 site, 10 users: 37,000 PLN net37,0001 site, 10 users2 sites, 10 users: 52,200 PLN net52,2002 sites, 10 users2 sites, 50 licences: 72,600 PLN net72,6002 sites, 50 licences
Source: Illustrative calculation: one-off implementation plus 12 months of maintenance, indicative ranges from 2025-2026 rollouts; individual quote

Recommendation 2: licences counted from active users

Demand a definition of an active user in the agreement, together with the counting rule. In the InnerWeb model licences are counted only from active users, meaning accounts with a login in the calendar month, and workers of external companies, drivers and visitors are not included in the counter.

Also check whether the price list takes scale into account. The flexible licence costs 80 PLN net per user per month with a minimum of 10 users. The fixed package is 50 licences for 2,500 PLN net per month, or 100 for 4,000 PLN net. Procurement should know from what number of active people the package becomes cheaper: about 30.

Recommendation 3: SLA parameters written as numbers

Availability and response times must be numbers, not descriptions. In the InnerWeb maintenance agreement, availability is 99.5% per calendar month for the server part of the instance, and in the event of a strategic failure the response takes 12 hours and the repair 8 hours from taking the case on.

Procurement should convert availability into time: 99.5% in a 30-day month means at most about 3.6 hours of unavailability. If the plant's process needs less, this must be agreed before signing, not after the first outage.

Recommendation 4: backups, retention and service windows

Demand a clause on backup frequency and retention time. In InnerWeb offers backups are daily with 14-day retention, and service windows last up to 5 hours per month with notice of at least 5 working days. It follows that in the worst case data from one day can be lost.

Procurement should consult these parameters with the plant's IT manager and record them as a minimum requirement. We describe the details of this conversation in a separate page on service windows and backups.

Recommendation 5: what is covered by the maintenance fee

Enforce in the agreement a list of items covered by the fee. The InnerWeb maintenance fee includes: a dedicated instance, licences, the training module without a limit, backups, updates and security fixes, and support without billing of working hours.

The reason is budgetary: support billed by the hour makes cost forecasting difficult. If the supplier has an hourly rate for additional work, record it and exclude ordinary support and fixes from it.

Recommendation 6: term and termination

Demand the option of a maintenance agreement for an indefinite period with monthly termination. This protects the plant from being tied for years to a supplier whose service no longer meets its needs, and at the same time does not force annual negotiations.

Check the installation lead time too. In InnerWeb offers it is 2 to 10 weeks from the order, depending on scope, so procurement should include it in the project schedule, including the order deadlines for the group.

Recommendation 7: extension to further plants without renegotiation

A framework agreement only makes sense if further plants join on set terms. Record the price of the entry point (5,000 PLN net per point in the offers), the rule of counting licences jointly for sites, and separate billing of the training module for each facility.

The sample cost of the first 12 months shows this: 37,000 PLN net for one site and 10 users, and 52,200 PLN net for two sites and 10 users. The difference of 15,200 PLN is the cost of the second plant, which procurement can enter in the plan in advance.

Recommendation 8: a clause on phased rollout and acceptance

Require a schedule with acceptance stages. In the sample scope the rollout takes 6 weeks in three stages of two weeks each: server and map, training and permits, and gatehouse workstations, and each stage ends with acceptance.

Staged acceptance lets procurement hold the second half of the payment until go-live and avoids paying for a rollout that does not work. It is also the simplest way to compare offers from different suppliers.

Video

Frequently asked questions

Must a framework agreement cover all plants at once?

No. It is enough that it sets the terms for further plants: the price of the entry point, the way licences are counted and the billing of the training module. Orders are placed separately.

What if the supplier refuses to put the SLA into the agreement?

Treat this as a red flag. The parameters of 99.5%, 12 h response and 8 h repair should be part of the maintenance agreement, because only then can their fulfilment be enforced.

Do licences have to be bought in advance?

Not under the flexible model: only active accounts are billed, with a minimum of 10 users per month. The fixed package pays off only at about 30 active people.

Let's prepare a framework agreement template

We will give your procurement team a set of parameters to write into the agreement. Book a meeting with InnerWeb.

Let's talk