Confidential drawings deserve a controlled workflow
Engineering drawings can include client IP, operational context and sensitive project information. PLC Automator is designed to keep the processing route visible: what files are used, where they are processed, who can access them, how long they are retained and how outputs are reviewed.
Your engineering data remains yours
For each controlled pilot, we agree the permitted drawings, processing route, authorised users and retention period before work begins. We process only the information authorised for the agreed workflow. Pilot material is not used for public demonstrations, unrelated development or model training without your express written permission.
Who owns the drawings and outputs?
The customer retains ownership of drawings, project information and project-specific outputs. PLC Automator receives only the limited right needed to provide the agreed service.
What information is processed?
Only the agreed project material and rules required for the specified workflow.
Where is it processed?
The processing route and region are documented for the applicable pilot or plan.
Who can access it?
Authorised customer users and limited product roles. Any content support access should be exceptional, authorised, restricted and recorded.
Is it used to train a model?
Customer project data is not used for model training by default. Any exception requires explicit written permission and a processing route/configuration that supports it.
Does the product connect to live control systems?
No. The product processes authorised engineering files; it does not connect to or deploy changes to live OT systems.
How long is it retained?
Retention periods for source files, derived outputs, logs and backups are agreed for the applicable service.
Planned higher-assurance processing options
For customers with higher assurance requirements, PLC Automator can discuss an agreed private AWS processing environment. A self-hosted model can be configured to start only when an authorised drawing job is queued, access material approved for that job, produce candidate data for engineer review and shut down when processing is complete. The available architecture, data residency, access controls, retention, support process and responsibilities must be agreed before deployment.
This is not a security certification or a promise that every deployment has the same architecture. We describe the processing route and implemented controls for the selected service.
Security principles
Protected transfer and storage
Encryption while files travel and while they are stored, where implemented.
Private project access
Authorised users and project-scoped access.
Defined retention
Agreed file-retention/deletion approach.
Bounded processing
No arbitrary browsing, email, command execution or live OT access for the drawing processor.
Engineer approval
Candidate data is reviewed before use.
Transparent data route
Processing, access and support arrangements are discussed before a pilot/deployment.