InnerWeb
Skip to main content

How to write an RFP for a plant safety system

An amendment to the Polish National Cybersecurity System Act (KSC) has applied since 3 April 2026, and the first obligations for essential entities fall due on 3 April 2027. A well-written request for proposals (RFP) for a plant safety system shortens the tender, limits disputes at acceptance and contains from the start the evidence an auditor will ask for. Below is an RFP structure in eight blocks, with sample wording.

13
points in a typical RFI for a digital work order system
5–10
pages of supplier response in this RFI
12 mo.
deadline for chapter 3 obligations under the KSC Act (until 3 April 2027)
Source: Dz.U. 2026 poz. 252

Start with the purpose and boundaries of the order

An RFP that opens with a list of features ends with bids that cannot be compared. Start with a sentence on purpose: which risk is to be reduced, which process replaced and what evidence the system should produce. Example: "The system is to manage permits and work orders from issue to archive, link them to contractor qualifications and provide a record of actions for audit."

Then set the boundaries. State which systems the order covers and which you are not touching (SCADA, the control system, the existing HR system). Define the number of sites in the first stage, the number of users on the plant side and whether external companies use the system at no additional charge. Missing these numbers is the most common reason bids differ by a factor of two.

RFP structure in eight blocks

A proven document layout helps both the supplier and the tender committee find the requirements. Each block should end with a statement of how the requirement will be verified: by a document, a test, a demonstration or a pilot.

  • 1. Purpose, context and scope (processes covered, sites, users).
  • 2. Functional requirements described by outcome, not by screen name.
  • 3. Cybersecurity requirements (authentication, roles, operation log, backups, vulnerabilities).
  • 4. Architecture and deployment model (a server at the plant or a dedicated cloud server, operation without a connection to the vendor).
  • 5. Integrations (user directory, maintenance management system, API).
  • 6. Pilot: purpose, period, success criteria, transition to rollout.
  • 7. Maintenance, SLA and billing model.
  • 8. Bid evaluation criteria and scoring method.

Timeline of the KSC amendment from entry into force

Timeline of the KSC amendment from entry into forceBar chart: entry into force at 0 months, chapter 3 obligations after 12 months, first audit and penalties after 24 months.0510152025monthsEntry into force: 0 months0 monthsEntry into forceChapter 3 obligations: 12 months12 monthsChapter 3 obligationsAudit and penalties: 24 months24 monthsAudit and penalties
Source: Dz.U. 2026 poz. 252, art. 33, 35

Functional requirements: describe the outcome

Instead of "the system has a permit module", write what the plant should be able to do and what should be recorded. Example from the permit-to-work process: a permit moves through preparation, main work and closure phases, the system checks the dates and qualifications of the assigned employees, and approval of particularly dangerous work is reserved for a user on the plant side. Such wording gives the supplier a clear goal and the committee a simple test: show me this in a demonstration.

For every function that matters for safety, add an evidence requirement: who changed what and when, whether the history of a permit can be reconstructed and whether the record has an audit trail of changes. This element supports meeting the documentation requirement; it is not a promise of regulatory compliance.

Mark the functions without which the order makes no sense as mandatory. Write the rest as scored options. This way the bidder does not have to guess whether the lack of a periodic report will disqualify the bid.

Sample wording to copy and adapt

Phrase requirements so they can be checked: "The system allows a person on the plant side to be designated as the approver of particularly dangerous work and prevents approval by a user of an external company." "The system records the author and time of every permit change and makes the change history available to the administrator."

Cyber requirements: what follows from the law

The amendment to the KSC Act (Journal of Laws 2026, item 252) transposes the NIS2 Directive and entered into force on 3 April 2026. For entities that met the criteria on the date of entry into force, the obligations under chapter 3 (information security management system, documentation, incident procedures) have a deadline of 12 months, that is 3 April 2027. The first audit of an essential entity falls after 24 months, and financial penalties can in principle be imposed from 3 April 2028. The Act requires, among other things, ICT supply chain security, so the supplier of a safety system is part of your risk assessment.

In the RFP, translate this into supplier requirements: multi-factor authentication, roles and a permission matrix, operation logging, backups with a described recovery procedure, and a process for handling vulnerabilities and reporting incidents within 24 and 72 hours. Detailed recommendations for the wording are in a separate article on cyber requirements in an RFP.

Parameters of an RFI for a digital work order system

Parameters of an RFI for a digital work order systemHorizontal bar chart: 13 RFI points, 9 licence models, a maximum of 10 response pages.051015countRFI pointsRFI points: 13 count13Licence modelsLicence models: 9 count9Max. response pagesMax. response pages: 10 count10
Source: InnerWeb

On-premise, pilot and evaluation criteria

State clearly where the system is to run: on a server at the plant or on a dedicated cloud server, and whether it must work without a connection to the vendor. Require a description of service windows, backups and the update method. The question about operation without a vendor connection appears regularly in market surveys, so it is better to answer it in the document.

Write the pilot as a stage of the order with a purpose, a period (usually 3–6 months), measurable success criteria and the right to move to rollout without an annex. In InnerWeb pilots to date, 100% of pilot-to-rollout transitions happened precisely because the criteria were written down before the start.

Split the evaluation criteria into total price for 12 months, quality of responses to requirements, security, and the result of the pilot or demonstration. Scoring by licence price alone, without implementation, hosting and external company costs, favours bids with hidden fees.

Market survey before the RFP

If you are unsure about the scope, run a market survey (RFI) first. In energy-sector practice, an RFI for a digital work order system had 13 points, and the response was limited to 5–10 pages. This format forces suppliers to be specific and gives you material to complete the RFP: differences in licence models, limitations, integration methods. Only then do you write the binding requirements.

Video

Frequently asked questions

Must an RFP name a specific product?

No. Describe the requirements and the verification method, not a product name. Naming a brand in public procurement is restricted by law, and in a private purchase it narrows competition without need.

How many pages should a good RFP have?

Usually from a dozen to a few dozen pages. Verifiability matters more than length: every requirement has a stated verification method.

Can a pilot be written into the RFP?

Yes, as a stage with a purpose, a period, success criteria and the right to move to rollout. You should also state who bears the cost of the pilot and what happens to the data after it ends.

Sources

Have an RFP draft to review?

Let us talk about scope, cyber requirements and pilot criteria. In a demonstration we will show how RFP wording looks in a working system.

Let's talk