Plant line, 24/7 +1-555-0164[email protected]

§1 FAQQuestion register / Reviewed Oct 2026

26 questions in five groups, from the first walk to the last window.
Sample answers, fictional firm

Floor questions.Plain answers.

These are the questions plant managers and controls leads ask us most, in their words. Start with the group you need, or ring the plant line and ask an engineer.

Rules we sign before a visit, R1 to R4
4
No scans, no agents, no change outside a window, no reboot without your name.

§2 Before you buy5 questions

Before you buy

What we do, which plants we fit, and what stays as it is.

2.1What does Wardline actually do?

We secure control networks at plants that cannot stop. We listen to the network passively, draw it into zones and conduits, and make every change inside a window your plant manager signed.

2.2Do you only work on the control side?

Yes. Mail, laptops and the office network stay with your IT team. We agree the boundary at the plant DMZ and write it down.

2.3Which plants do you fit?

Plants that run long shifts and cannot stop on demand: power, water, pipelines, manufacturing, and food and drink. Industries shows the rules we map to for each.

2.4Do we have to replace old controllers?

No. We work with what is installed, including units nobody can patch. Where a fix is not possible, we shield the device with zone rules instead.

2.5Can we read a site report before we buy?

Yes. Site report SR-214 is on this site. The client is fictional. The format is the one you would get.

§3 Plant incidents5 questions

Plant incidents

Who answers, who decides, and what lands on your desk afterwards.

Something running wrong now?
Skip this page and call. An engineer answers, day and night.
3.1Who answers the plant line?

An engineer on the plant line rota, day and night. No menu and no call centre.

3.2What is the first thing you ask?

Whether anyone is at risk, and whether the process is in a safe state. The network comes after that, every time.

3.3Will you isolate a line in the night?

Not without your operations lead. We say what we see and what we would do, and they decide. A safe process comes before a contained network.

3.4What do we get afterwards?

A note to your shift lead the same night, then the full report: timeline, findings, what we did, who approved it and what to do next.

3.5Can you help if we are not a client?

Call the line. We will tell you what we can do, and scope any paid work before it starts.

§4 On your floor6 questions

Engineer kneeling with a clipboard at a network cabinet in a plant room

On your floor

What we touch, what we never touch, and who stands beside us when we do.

4.1Do you run scans on our network?

No active scans on a live line. We learn the network from a copy of its traffic, so old controllers never see us. That is rule R1.

4.2Do you install anything on controllers?

No. Nothing goes on a PLC, drive or safety system, so your vendor support stays intact. The sensor sits on a mirror port or a hardware tap.

4.3Does the sensor install need an outage?

No. It goes on a mirror port in under two hours, with no outage. That is a sample figure for one switch.

4.4Who has to be there when you visit?

Your controls lead walks with us the whole time. We follow your site induction and safety rules, and we bring a printed plan.

4.5What if a change needs a restart?

It goes in a window with a date, a rollback and an owner from your team. Operations signs it and stands beside us for the restart.

4.6What if a window runs late?

The rollback starts at the agreed time, whatever is left undone. Unfinished work moves to the next window.

§5 Monitoring and data6 questions

Monitoring and data

What the sensor hears, where it stays, and whose it is.

5.1What does the sensor read?

Modbus TCP, EtherNet/IP, PROFINET, DNP3 and OPC UA. It receives and cannot send: it puts zero packets on the control network.

5.2What does it tell us?

New devices, new routes, and firmware or logic changes. Night alerts go to your shift lead with the next step in plain words.

5.3Where does the traffic copy stay?

On the sensor at your site. Only alerts and summaries leave it, through the plant DMZ.

5.4Who owns the asset list?

You do. It stays yours whether or not you keep monitoring with us.

5.5Who at Wardline can see our data?

Named engineers on your site team. Every look is logged, and you can ask for that log.

5.6What happens if we stop?

Asset list, drawings and reports stay with you. We remove the sensor in a signed window and confirm deletion in writing.

§6 Standards and paperwork4 questions

Standards and paperwork

6.1Which standards do you work to?

IEC 62443 for zones, conduits and security levels, and the Purdue reference model for levels. Each sector adds its own, see Industries.

6.2Will you make us compliant?

Nobody can promise that. We give you the drawings, logs and signed windows an auditor asks for, and say plainly what is still open.

6.3How is the work charged?

A site assessment is a fixed scope for one site. Passive monitoring is charged monthly, per site. Plans has the details.

6.4Do you work with our machine vendors?

Yes. Vendors keep their support terms. They get one timed and logged gateway in place of their own remote tools.

Engineer and depot supervisor in a hi-vis vest at a control desk, trucks in the yard
Rules R1 to R4, signed by

Plant manager

Client

Site safety lead

Client

Site lead

Wardline

§7 End of register26 questions / Reviewed Oct 2026

Not on the list? Ask an engineer.

Plant line, 24/7