// common questions

FAQ

Common questions about PLC Automator — PLC tag extraction from electrical schematics, data handling, IP and the controlled pilot workflow.

[01]questions

Common questions

[01]

Does PLC Automator replace controls engineers?

No. The product produces a draft data pack — extracted tags, alarms and documentation — that a qualified engineer reviews and approves before it's used. It is a workflow tool, not a replacement for engineering judgement.

[02]

Can the AI make a mistake?

Yes. The model output is treated as a draft — uncertain or conflicting items are flagged for engineer review, never auto-accepted. And if you need help, we go above and beyond: responsive customer service is our strongest feature.

[03]

What drawing types and systems are supported?

A pilot starts with one agreed drawing type and export. Universal support for every format, vendor or system is not claimed; each workflow is agreed and demonstrated before it is relied on.

[04]

What happens with messy, incomplete or ambiguous drawings?

Those items are surfaced as review exceptions. They are not hidden or auto-completed. An engineer inspects the source evidence and decides how to proceed.

[05]

Are our drawings confidential?

Yes. All data you upload is treated as confidential and remains customer-owned. Processing runs on AI models hosted by default in our private AWS environment. For more information, see security and data handling.

[06]

Can we discuss a private or customer-controlled processing route?

Yes. Private AWS processing and customer-controlled environments can be discussed under planned higher-assurance options. The architecture, data residency, access controls, retention and responsibilities must be agreed before deployment.

[07]

Who owns the drawings, outputs and product configuration?

You do. The customer retains all rights to project drawings, project information and project-specific outputs. PLC Automator staff can only access your project data with your prior approval. Product and company IP are covered by the applicable agreement.

[08]

Is customer data used to train AI models?

No — never. Your drawings and project data are not used to train, fine-tune or improve any AI model. They are processed only to produce the agreed engineering outputs for your project.

[09]

Does the product access live PLC/SCADA/OT systems?

No. The product processes authorised engineering files. It does not connect to, monitor or deploy changes to live OT systems.

[10]

How does this work with our tag naming rules, templates and exports?

We load the customer’s naming rules, templates and export formats before processing. The output is a draft data pack that matches the agreed rules, demonstrated for the specific workflow.

[11]

Does this reduce our billable work?

It reduces manual data entry. Under strict time-and-materials contracts, actual labour should still be recorded. The value is in capacity, quality and faster delivery — more time for high-quality review, not fabricated labour.

[12]

Can we export our data and avoid lock-in?

Yes. Outputs are delivered in the vendor format your workflow needs — customer-owned files, no proprietary dependency.

[13]

Can you configure or co-develop a workflow for our company?

Absolutely. Our engineers love working with customers to improve the efficiency of their control-systems processes. Get in touch and we'll work to your needs — if you want it and we can do it, we'll make it happen.

[14]

What does a controlled pilot involve?

A guided, view-only trial on one agreed drawing package — we process your schematics and walk through the tags, exceptions, code and documentation with you. For more information, see controlled pilot page.