InnerWeb
Skip to main content

FAQ: deployment from inquiry to acceptance

Purchasing and the plant manager ask three questions before ordering a system: how long the road from the first conversation to the start takes, when and for what they pay, and who on the client side has to get involved. Below we have collected answers based on our offers and past deployments, with figures that can be entered into a schedule and a budget.

30–90 days
from the meeting to the order
100%
of pilots moved on to full deployment
50/50
payment split in the two-stage variant (%)

How long does the whole road from the meeting to the order and pilot take?

From the first meeting to the order usually takes 30–90 days. This time comes mainly from the plant's purchasing process: defining the scope, comparing offers, budget approval and signatures, and not from the work of the software vendor.

If the plant chooses a pilot before the full deployment, the pilot usually lasts 3–6 months. All pilots we have run so far moved on to full deployment (100%), which is an important argument for the purchase: a pilot is not an experiment without a follow-up, but the first stage of the same configuration.

It is worth distinguishing two timelines. The first is the purchasing path (meeting, site visit, offer, order). The second is the deployment path from the order to acceptance. For the two-stage variant the second timeline lasts 2 months, for the shortened one 6 weeks.

How long does the deployment itself take after the order?

It depends on the chosen schedule variant. The two-stage variant consists of two stages of 4 weeks each, closed by acceptance and production launch after 2 months. The three-stage variant spreads the same scope over three months, and each month ends with a tangible result to accept. The shortened variant lasts 6 weeks in three stages of 2 weeks each, every one with an acceptance.

The difference is not that the shorter variant is poorer, but that it requires faster decisions and readiness from the plant: appointing administrators, providing the naming of locations and dates for acceptances. That is why, when choosing a variant, the plant manager should ask not how many days it takes, but how much time for decisions is realistically available.

  • Two-stage variant: 2 stages of 4 weeks, production launch after 2 months.
  • Three-stage variant: 3 months, with a tangible result to accept after each month.
  • Shortened variant: 6 weeks, 3 stages of 2 weeks, each with an acceptance.

Deployment time after the order by variant

Deployment time after the order by variantHorizontal bar chart: shortened variant 6 weeks, two-stage variant 8 weeks, three-stage variant 12 weeks.02.557.51012.5weeksShortened variantShortened variant: 6 weeks6Two-stage variant (2 months)Two-stage variant (2 months): 8 weeks8Three-stage variant (3 months)Three-stage variant (3 months): 12 weeks12
Source: month converted to about 4 weeks

What happens in the individual stages?

In the two-stage variant, stage one (weeks 1–2) covers launching the instance, configuring zones, gates and roles, and importing the data of external companies. Weeks 3–4 bring the training module with tests and language versions, as well as the legal package and the cooperation rules.

Stage two covers permit templates, the full set of especially hazardous work, admission matrices and approval paths. At the end, security posts at the gates are installed, cards are printed and security and HR training is carried out.

What does the plant receive in the shortened variant?

In the first stage a separate server, accounts and permissions are created, together with teams responsible for areas and about 500 locations in the plant's naming. Acceptance of the second stage means a passed test training and an issued test permit with a PDF printout; in this stage up to 80 risks and hazards with protective measures are prepared, together with 2 print templates.

Final acceptance means the production launch and the first external companies admitted by the system at the gatehouses, after training of administrators, supervisors and employees.

When and how much is paid for the deployment?

In the two-stage variant the deployment payment is 50% at the order and 50% after the production launch. The purchaser therefore sees two installments tied to specific events: the signature and the start. The second installment does not depend on further negotiations, only on the fact that the system is working at the gatehouses.

The amounts depend on the scope, the number of locations and modules. We do not give the price of a single quotation in the FAQ, because without assumptions it would be misleading; a calculation with explicit assumptions is presented in the offer. When the plant considers a pilot, the monthly rate covers the server, the instance, the licences and access to 12 modules, which we describe separately on the page about the costs of the pilot and the full deployment.

When comparing offers, check whether each quotation contains the same list: server, instance, licences, training, language versions, print templates and SLA. A price difference is often the result of a difference in scope, not of margin.

What is mandatory on the client side?

The plant must provide at least 2 administrators, one per location, and a weekly status meeting lasting about 10–15 minutes. This is a small but essential contribution: the administrator knows the plant's rules, decides on the naming of locations and accepts the deliveries.

The meeting is deliberately short. Three matters are discussed: what has been done, what blocks the next step and which decision is needed by Friday. This way the schedule does not drift because of a single unresolved matter.

The client's scope when mounting beacons is broader and we describe it separately, in the implementation notes on the client's scope. It concerns indicating the mounting places, power supply of the nodes, the network, addressing and access to the premises.

Do you have to buy transmitters to start?

No. Entry into the system can be made without transmitters: deploying the Mobile Work Permits module alone is a complete first step, and localization comes at a later stage. A plant that wants to quickly organize permits and the admission of external companies does not have to wait for the beacon layout project.

This order makes most sense especially with a limited budget for the first year. First the digital flow of permits and training, then, once the team gets used to the system, the location of people and the SOS alarm on the map.

What does acceptance look like and how does it differ from the production launch?

Stage acceptance is confirmation that the agreed result works: for example an instance with the map, a passed test training or an issued test permit with a printout. In the three-stage variant each month ends with a tangible result: a working training module and an instance with the map, then an issued and accepted test permit with documentation, and finally tests on live traffic of external companies and the production launch.

The production launch is the moment when the system starts handling real traffic. In our schedules the final acceptance and the production launch coincide in one point, because it is the first external companies admitted by the system that prove the deployment is complete.

Video

Frequently asked questions

Can the pilot be shortened below 3 months?

A typical pilot lasts 3–6 months, because the system needs to see a full cycle of the plant's work in that time. A shorter period is possible when the scope is narrow, but the conclusions of the pilot are then less representative.

Is the second installment paid before the production launch?

No. In the two-stage variant the second part, 50%, is payable after the production launch, that is, after the system is working at the gatehouses.

Are 2 administrators the minimum for a plant with one location?

We require at least 2 administrators, one per location. A plant with one location should nevertheless name a deputy, so that a holiday does not stop the acceptance.

What if the plant does not manage its decisions in time in the shortened variant?

In that case it is more sensible to choose the two-stage or three-stage variant. The deadline depends on the pace of the plant's decisions, so it is better to choose a schedule that can be kept.

Want to calculate the schedule for your plant?

Describe the scope and the number of locations to us, and we will prepare a schedule in the chosen variant together with the split of payments. We will invite you to a short conversation or a demo.

Let's talk