InnerWeb
Skip to main content

Maintenance and development costs of OHS software

The annual cost of maintaining safety software is more than a subscription fee: it also includes transmitters, mobile devices, acceptance work after updates and development of features. We show the structure of these items, a sample calculation on explicit assumptions, and the places where a plant can lower the cost without losing control.

3-6 mo.
pilot before full rollout
2-2.5 h
full end-to-end test run
480
hours of manual acceptance per year in the sample calculation
Source: sample calculation

What the annual cost consists of

The system is offered on a subscription basis with a one-time implementation fee, and the pilot runs for 3 to 6 months before full rollout. After deployment the annual cost consists of several items, which are worth separating in the budget, because each has a different owner and a different way of being optimised.

The documentation lists the maintenance options: server and licences with SLA, maintenance of transmitters including battery replacement as part of the service, and rental of mobile devices, all billed as a monthly subscription. On top of that come two items on the plant's side: staff time for acceptance after updates, and orders for the development of the plant's own features.

  • Server and licences with SLA: the subscription fee, usually the largest fixed item.
  • Transmitter maintenance: battery replacement as part of the service, so the plant does not plan it separately.
  • Mobile devices: rental billed monthly instead of purchase.
  • Acceptance after updates: hours of the plant's own staff, often invisible in the budget.
  • Custom development: one-off projects, priced individually.

Indicative ranges and the pricing rule

We publish prices only as rounded ranges: indicative ranges from 2025-2026 deployments, with individual pricing. We do not attribute figures to recognisable entities, and the final amount depends on the number of users, the floor area, the number of transmitters and the scope of the SLA.

In talks with the vendor it is worth asking what is included in the subscription and what is extra. The difference between a subscription with battery replacement and one without can shift the bill after the third year, when batteries begin to run down.

What does a plant save if it does not replace readers?

InnerWeb is the producer of software that integrates with the client's existing systems, so an update on the InnerWeb side does not replace readers or cards. This means no cost of access control hardware in the update cycle, which is a real budget argument for larger plants.

Acceptance hours per year: manual and automated

Acceptance hours per year: manual and automatedBefore and after chart: 480 hours of manual acceptance per year against 120 hours with automation-based acceptance.0100200300400500hoursManual: Acceptance after updates: 480 hours480 hoursManualWith automation: Acceptance after updates: 120 hours120 hoursWith automation
Source: Sample calculation based on the assumptions in the Calculation section

Where the plant can reduce the cost

The largest saving potential lies in acceptance after updates. The full browser test package takes about 2 to 2.5 hours and runs automatically at midnight on weekends, so people do not have to repeat the same scenarios by hand after every release.

The second area is reducing noise in reports. Exceptions that describe invalid input are excluded from reporting as non-failures, and event limits prevent a flood of reports from one loop. Less noise means less IT time spent working out which report is real.

The third area is custom development. An acceptance criterion written as a test scenario reduces the number of fixes after rollout, because acceptance rests on a test rather than on an eyeball judgement.

Sample calculation and conclusions

The calculation below shows only one item: the time of the plant's own staff spent on acceptance after updates. The assumptions are explicit and the plant can substitute its own values. The other items (subscription, transmitters, devices) are priced individually.

The practical conclusion: a plant should calculate the cost of maintenance over three years, not per year, and compare a version with manual acceptance against a version with acceptance based on automation.

Example calculation

Staff time for acceptance after updates

Assumptions
ParameterValue
Updates per year12 releases
Manual acceptance of one release40 hours
Automated acceptance of one release10 hours

Result: Manual: 12 x 40 = 480 hours per year. With automation: 12 x 10 = 120 hours per year. Difference: 360 hours per year, which the plant can convert at its own hourly rate.

Note: Sample calculation based on the assumptions of the page author, not a measurement in a specific plant. The plant substitutes its own number of releases and hours.

Video

Frequently asked questions

Is the cost of transmitter battery replacement included in the subscription?

The documentation lists transmitter maintenance with battery replacement as part of the service, billed as a monthly subscription. The scope is confirmed in the individual pricing.

Does an update generate a cost of replacing readers?

No. An update on the InnerWeb side does not replace the client's readers or cards, because the system integrates with the existing access control.

How long is the pilot and is it paid separately?

The pilot runs for 3 to 6 months before full rollout. Terms are set in the individual pricing.

Calculate the maintenance cost in your plant

We will prepare an individual quote with a breakdown into subscription, transmitters, devices and development. Book a conversation with InnerWeb.

Let's talk