InnerWeb
Skip to main content

CHP plant: digital work orders and switching and protection cards

A combined heat and power plant of an energy group, an essential entity under NIS2, runs work orders (PnP) and switching and protection cards (KPZ) on paper. A pilot at 50 workstations reproduces the current procedure one to one and blocks admission of the team until the last safeguard on the card is confirmed. The medium changes, not the instruction.

50
workstations in the pilot on the site side
3
order phases: preparation, main work, closure
3–6 mo.
duration of the pilot

Starting point

The site is a combined heat and power plant belonging to an energy group, classified as an essential entity under NIS2. Work on electrical and thermal systems is carried out by in-house services and by external firms, and each job requires a work order and a switching and protection card. The company decided on a pilot at one site, intending to copy the pattern to further CHP plants.

The scale of the pilot is 50 workstations, that is people on the site side who log in to the system: issuers, approvers, admitting officers, security and administrators. External firms, their employees and visitors are not counted in this number. The pilot is planned for 3–6 months.

The problem: only the person holding the paper knows the state of the work

The order and the card circulate on paper between the issuer, the approvers, the admitting officer and the team. The current state is known only to the person holding the right copy. Actions carried out in the field reach the register only after the person returns to the office, which means double data entry and discrepancies between paper and register.

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. Interruptions and resumptions get lost between shifts, and after an event the evidence has to be assembled from scattered documents. For a site covered by NIS2 there is also the requirement to demonstrate access control and accountability of actions in critical zones.

Pilot duration: short and long variant

Pilot duration: short and long variantBar chart: the pilot lasts from 3 to 6 months.0246monthsShort variant: 3 months3 monthsShort variantLong variant: 6 months6 monthsLong variant
Source: pilot of 3–6 months

The solution: the same procedure, a different medium

The premise of the project is not to change the services' instruction. The procedure, roles, approvals and print templates are set up in workshops on the basis of the current PnP and KPZ forms. The system reproduces them one to one, and the order passes through three phases: preparation, main work and closure. Each phase is a list of tasks assigned to roles from the site procedure, and a task requiring a signature can be closed only by an authorised person.

The order is assigned to a location from the site tree (building, floor, device). When issuing, the system shows other active orders in the same location, which solves the problem of unawareness of parallel work. The contractor works in a browser, without installing an application, and sees only their own orders. In the work zone a tablet with an offline queue operates, so the lack of a network does not stop the recording of actions; when connectivity returns the system replays them without duplicates.

The switching card as ordered tasks

The KPZ items, that is switching, disconnection, securing against reclosing, earthing, marking and checking for absence of voltage, are preparatory tasks with a defined order, a responsible person and a signature. This is a configuration of the order engine, not a separate module. Site-specific elements that cannot be captured by configuration are quoted separately as an extension, before implementation.

Admission block

Until the last safeguard on the card is confirmed, admission of the team is blocked. The contractor sees a waiting status instead of consent to work. The green colour and the words "You are working" appear only after admission to the main work, and a team that has joined and is waiting for preparatory tasks sees an amber call to action.

Suspension and closure

Suspending work does not remove safeguards. An additional disconnection during the works is a new task that conditions resumption. Closure requires confirmation that the zone has been cleared and that safeguards have been withdrawn in the reverse order to that in which they were applied.

Effect: what the pilot is meant to prove

The pilot is a decision stage, so its effects are measured on data from the site, not on promises. The measures adopted are: no discrepancy between the register and the state in the field, the time from confirmation of the last safeguard to admission of the team, the number of resumptions after interruptions recorded without gaps, and the completeness of the record after an event. Every action has an author and a time, without copying from paper.

From the NIS2 point of view the pilot provides audit evidence in the area of access control and accountability: who admitted the team, when and on what basis. This does not replace risk assessment or the cyber protection of control systems, but it complements them with a layer of physical access to equipment.

Lessons for other energy sites

First, start with one site on a separate server and only then copy the process template. The pattern built in the pilot is treated as a group standard with local specifics: the location tree, the functional roles and the print templates.

Second, combine PnP, KPZ and the contractor in one process, so that the system does not let an order move to the next phase until the blocking actions are confirmed. Third, start with workshops attended by the services that issue and admit today, because they verify the fidelity of the reproduction.

Video

Frequently asked questions

Does the system change the site's PnP and KPZ instruction?

No. The site's forms and procedure are reproduced one to one in workshops, and only the medium changes. Roles, approvals and print templates come from the services' current documents.

How does the admission block work?

KPZ items are tasks with an order and a signature. Until the last safeguard is confirmed, admission is blocked, and the contractor sees a waiting status instead of consent to work.

Does an external firm have to install an application?

No. The contractor works in a browser and sees only their own orders. External firms and visitors are not counted in the number of workstations.

What about work in a place without coverage?

Actions are queued locally on the device and replayed when the network returns. The system recognises repeats, so resending does not create duplicates.

Sources

Reproduce your site's PnP and KPZ procedure

We will show on your own forms what the admission block and the contractor view look like. Book a conversation or a demo.

Let's talk