Describe what the system needs to do.
A clear sequence, functional requirement or description of the existing issue helps define the work. We discuss the control platform, robot or PLC involved, how the application interacts with other equipment and what information or access is available. Platform suitability is confirmed during scoping.
New applications and defined changes.
A programming package may cover an agreed part of a new application or a specific change to existing software. Rather than leaving the task open-ended, we identify the intended behaviour, responsibilities, dependencies and acceptance requirements. Existing backups, documentation and permissions are important inputs when work involves equipment already in use.
Verification and handover are part of the conversation.
Before work begins, we agree how the programmed behaviour will be reviewed and what outputs you need. Depending on the scope, these can include software files, backups, supporting notes and defined verification activities. Simulation, on-site testing and commissioning are included only where agreed, with access and delivery dates arranged in advance.
Bring the information you have.
For an initial enquiry, tell us the platform, application, change required and target timing. An existing functional specification, sequence description, software version information and details of connected equipment can help. We will agree how to share project files and any sensitive technical information after the first conversation.
A programming partner, or a wider automation partner.
You can engage Automation X for programming alongside your own engineering team or combine it with design, control panel build and integration. We coordinate specialist support where the scope requires it. Based in Telford, we work with businesses across the UK and Europe, with the delivery approach and any site attendance agreed for each project.