The situation: paper and circulating cards
The company operates energy sites where the work order (PnP) and the switching and protection card (KPZ) circulate between the issuer, the approvers, the admitting officer and the team. The current state is known only to the person holding the paper. Actions from the field reach the register only after the return to the office, which means double entry and paper–register discrepancies.
With several jobs on one system, the person withdrawing a safeguard cannot be sure whether anyone is still working. An external firm learns about hazards from an oral briefing, and after an event the evidence has to be assembled from scattered documents. The company is an essential entity under NIS2, so the purchase of a tool that touches work safety and data must go through supplier assessment.
The RFI: exactly what was asked
The request had 13 points and an answer limit of 5–10 pages plus any technical annexes. It concerned the whole process: issuing, approvals, hazards and protective measures, contractors, the work zone, admission, electronic confirmations, interruption and resumption, completion and the archive. Separate questions covered switching cards and the coordination of PnP with KPZ, contractors working in a browser, tablets in the work zone, integrations and on-premise deployment without a connection to the vendor.
The buyer also asked about security mechanisms: single sign-on (SSO), multi-factor authentication (MFA), roles, encryption, an operations log, signing of actions, integration with a security operations centre and certificates. The last group of questions concerned scaling to many plants and a licence model chosen from 9 variants.
Size of the RFI answer
The answer: structure and honest limitations
The answer was built in the order of the RFI points, so that the reader could compare it with others: a cover with a summary, a description of the solution, PnP handling in 13 steps, KPZ and coordination, a tablet in the work zone with an offline queue, contractors in a browser, architecture and deployment models, security, integrations, scaling, a pilot schedule, indicative costs and a licence model. The whole fitted into 10 A4 pages, and a 17-slide presentation was prepared in addition.
The most important editorial decision concerned limitations. Switching and protection cards were described as a configuration of the order engine (preparatory tasks with a signature and an admission block), and elements requiring an extension were identified for separate quotation. The same applied to integration with the user directory and the maintenance system: the scope was defined as an element of the production version to be agreed with the IT department. The buyer asked about limitations, so hiding them would have been a tactical error and evidence of a lack of integrity.
- A compliance table divided into standard, configuration and extension.
- An explicit list of what the pilot does not cover.
- Questions for the buyer: number of orders per year, number of users, current system, KPZ template, preferred identity provider.
A pilot at one location
The recommendation in the answer was simple: start at one site, on a separate server, and copy the process template to further locations. The pilot scenario assumed 50 workstations, a period of 3–6 months and a procedure reproduced one to one from the current PnP and KPZ forms, so that the medium changes and not the instruction. Until the last safeguard on the card is confirmed, admission of the team is blocked and the contractor sees a waiting status.
For further sites the time from workshop to start was estimated at 4–6 weeks (an estimate, depending on location and integrations). The process pattern built in the pilot is treated as a group standard with local specifics: the location tree, functional roles and print templates.
Pilot period in the scenario
Lessons for buyers and suppliers
For the buyer: an RFI with numbered points and a page limit forces comparability. It is worth asking at once about limitations and about what is standard and what is an extension. For the supplier: answer in the order of the questions, attach a compliance table and do not claim references you do not have. For both sides: the RFI result is an input to the tender specification (OPZ), not a substitute for it; the rules for writing an OPZ are described in a separate guide.
Video
Frequently asked questions
How does an RFI differ from a request for quotation?
An RFI is used to gather market and scope intelligence and does not bind the buyer or the supplier. On its basis the tender specification (OPZ) is prepared, and only then the request for quotation.
Are switching and protection cards a separate module?
In the case described, KPZ were reproduced by configuring the order engine: preparatory tasks with an order, a responsible person and a signature. Elements that configuration does not cover are quoted separately before implementation.
Why were limitations stated in the answer?
Because the RFI asked about them, and a hidden limitation comes out in the pilot. An open division into standard and extension shortens negotiations and builds credibility.
Sources
Gathering an RFI for a work order system?
We will help organise the points of the request and prepare an answer or a demonstration on your own procedures.
Let's talk