InnerWeb
Skip to main content

How to prepare a request for a system deployment so the offers can be compared

A request for a quotation for a plant system is usually too general: suppliers answer different questions, and purchasing compares offers that cannot be compared. This guide shows how to describe the scope, the areas, the client's responsibilities and the acceptances, so that every offer answers the same questions and can be placed in a single table.

about 110
points with PoE and network for about 2,000 beacons in a large plant
about 2 weeks
acceptance of the layout design by the client

Why does the request decide the quality of the offers?

An offer is only as good as the question. When the request speaks only about a system for the plant, the supplier fills in the assumptions on its own: the number of locations, the scope of training, the type of acceptances. Two suppliers will assume two different things, and purchasing gets two prices that cannot be compared.

A good request does not have to be long. It should, however, answer five questions: what is to be done, where, within what time, who provides what on the client's side and how it will be accepted. Each of them is discussed below.

Step 1: describe the functional scope and the areas

Start with a list of the processes the system is to handle, for example admission of external companies, permit templates, training, guest registration, localization of people. For each process write who uses it and at which gates or areas of the plant.

Do not ask the supplier to guess the number of locations. In the shortened variant our first stage covers about 500 locations in the plant's naming; if your plant is of a different scale, state it in the request, because it affects the time and the scope. If you do not know the number, say so in the request and ask for a site visit as part of the offer.

Separate the mandatory scope from the optional one. Entry into the system can be made without beacons: the work permit module alone, with localization coming later. The request should indicate whether localization is in the scope or is an option for the next stage.

Points requiring power and network in a large plant

Points requiring power and network in a large plantDonut chart: about 110 points with power and network against about 2,000 battery beacons.LoRa nodes and gateways with PoE and network: 110 pieces (5.2%)Battery beacons without cabling: 2000 pieces (94.8%)2110piecesLoRa nodes and gateways with PoE andnetwork110 pieces (5.2%)Battery beacons without cabling2000 pieces (94.8%)
Source: (about 110 points for about 2,000 beacons)

Step 2: count the beacons on the basis of assumptions, not a number from the supplier

If the request covers localization in a hall, do not enter the number of beacons from a previous project. The exact number depends on assumptions about floors and walls, so it is counted from scratch for the given facility and not filled up to a fixed figure.

For a preliminary estimate, the rules help: in a building 1 beacon per 100–200 m², on plant roads a beacon about every 100 m. The system works without GPS. State in the request the floor areas of the halls, the number of floors and the length of the roads, and the supplier will count the number and justify it.

  • Floor areas of the buildings and the number of floors.
  • Length of the plant roads on which localization is needed.
  • Explosion-hazard zones, if present (ATEX execution required for zones 2/22).
  • Places where drilling or mounting is not allowed without a work permit.

Step 3: define the client's responsibilities

The most frequent source of delays is unclear responsibility for who prepares what. The client's responsibilities for the installation cover indicating the mounting places, the 230 V supply and LAN network for the nodes, IP addressing, access to the premises and the people for acceptances.

The beacons are battery-powered and need no power supply or cabling. Only the LoRa nodes and gateways require PoE and network connections; in a large plant this is about 110 points for about 2,000 beacons. Enter in the request who prepares these points and by what date.

Do not leave this for negotiation after the supplier is chosen. Preparing the power and network points is installation work that has to be planned in time before the crew arrives.

Step 4: describe the schedule and the acceptances

Ask each supplier for a schedule in the same form: stages, their duration and a tangible result to accept at the end. For example, the two-stage variant consists of two stages of 4 weeks with an acceptance, and production launch after 2 months, while the shortened variant is 6 weeks in three stages of 2 weeks.

For large localization deployments the schedule has a different structure: the contract and site visit with propagation measurements and the layout design, then the server and the LoRa network, installation and calibration zone by zone, and finally accuracy tests, training and acceptance. Ask whether the supplier foresees acceptance of the layout design by the client (for us about 2 weeks) and how many crews will work.

State in the request that payments are to be linked to acceptances. The two-stage variant has a split of 50% at the order and 50% after the production launch; ask each supplier to indicate its own split.

Step 5: require the same cost table

Attach to the request a table to be filled in, in which the supplier enters: server, instance, licences, training, language versions, print templates, SLA, equipment and installation. Each row in a separate column: one-off price and monthly price.

Ask for a pilot as an option. For purchasing it is a way to reduce risk: from the meeting to the order usually takes 30–90 days, and a pilot lasts 3–6 months. Ask for the monthly rate and the scope of the pilot (number of users, beacons, modules), so that it can be compared with a one-off deployment.

Checklist

Video

Frequently asked questions

Should the request state the number of beacons?

It is better to provide the data needed to calculate it: floor areas, floors and roads. The supplier will count the number from scratch and justify it, which gives comparable offers.

Should a site visit be part of the request?

Yes, if the scope covers localization. A site visit with propagation measurements makes it possible to establish the layout design, whereas before that the offer is only an estimate.

How to compare a pilot with a deployment?

Ask for the monthly pilot rate with its scope and for the deployment quotation in the same table. Compare over the same number of users and modules.

We will help you formulate the request

Send us a short description of the plant and we will help you organize the scope and the cost table, so that offers from all suppliers can be compared. We invite you to a conversation or a demo.

Let's talk