Industrial automation
A solution from MCS Grup
Experienced automation engineers for new software, migrations and extensions — by the task or by the month.
We provide engineering capacity for Siemens controller, panel and visualisation software — for a single task or as a fixed block of days per month. We work on your hardware and to your plant standard, and you settle with a Polish company on a contract in Polish.
The most common jobs are taking a project over from a previous supplier, adding a station or a recipe to a running line, tidying up alarms and operator messages, and writing up the changes before an audit. Each of them ends with the sources handed over and a description of what was changed — and why.
The S7-300 is out of production and spare parts come from stock and refurbishment, which turns a few hours of downtime after a CPU failure into a few days. We run the migration in four steps. Inventory: hardware, Step 7 version, blocks, communication links and what is actually in service. Conversion: moving the program into TIA Portal, rewriting the blocks the converter will not handle, checking addressing and data types. Test: a run on a stand-in rig with simulated signals, so the errors surface before the shutdown rather than during it. Swap: the CPU and modules are replaced in the planned window, then commissioned and handed over.
More usually stays than people expect. The field side — sensors, drives, wiring — is untouched, ET 200M distributed stations can stay on Profibus or move to Profinet, and replacing the controller does not force a mechanical rebuild. When the panel, the drives and the safety circuits have to move as well, it becomes production line modernisation.
Programming, rig testing and diagnostics are done remotely, over a connection set up with your IT department, with access limited to named devices and every session logged. Commissioning, acceptance tests and training happen on site. The offer always states which work is remote and which needs someone on the shop floor, how many visits are planned and who covers travel. Residence formalities and the posting of engineers from outside the European Union are handled by the manufacturer and are built into the lead time. The rules we follow for secure service access — control-network segmentation, named accounts, session logging — are set out in the knowledge base.
Two models. A fixed-scope task: you hand over the program, the schematics and a description of the expected behaviour, and we give a fixed price and date. A monthly block: you reserve a number of engineering days and agree the tasks with the lead engineer as you go — this works for migrations and seasonal peaks. The quote follows a review of the material; without sight of the program and the documentation no number would be honest. Formally: contract in Polish, VAT invoice in PLN, an NDA before any code changes hands. Both models deliver the same thing: the project sources, a description of the changes made and updated schematics — so the next company, including one that is not us, can carry on without archaeology.
New motion applications are built on S7-1500T in TIA Portal: technology objects describe axis synchronisation without a separate motion controller and the whole machine stays in one project. Existing Simotion installations we service and extend — in a plant where a proven application runs, replacing the platform rarely pays for itself, so we say so instead of proposing a rewrite. If the change covers not only the program but the panel and the commissioning of a whole machine, start from industrial automation.
Knowledge base
How to size your spare-part exposure, decide between a 1:1 swap and a redesign, and move to S7-1500 and TIA Portal inside one downtime window.
Read 2026-09-29OT network segmentation, a VPN versus a remote-service platform, per-session approval and logging, and the access clauses your integrator contract needs.
ReadQuestions and answers
Yes. If you have block libraries, a naming convention or a documentation template, we take them as the starting point. If you do not, we propose one and hand it over with the project, so the next change does not have to start from scratch.
Your IT department sets up the connection. Access is limited to the devices you name, accounts are personal rather than shared, sessions are logged and access expires when the task closes. Where you use SINEMA Remote Connect we work inside it.
Not necessarily. The controller can be replaced on its own; panels and drives are replaced when they are out of support or when the mechanics change. We state in the inventory what has to go and what can stay for another few years.
A copy of the project (a Step 7 or TIA Portal archive), the schematics, a signal list, a description of the expected behaviour and the shutdown windows available. We sign an NDA first if you prefer.
You do. The contract transfers the rights to the software written for your machine and you receive the sources together with the as-built documentation.
Tell us what you need. You will get an answer within one business day.