A halted line gets counted in minutes rather than days. The works order stops reaching the floor, the label printer rejects a code, the production database goes quiet: operators stand about, a bay backs up, and the lost hour is paid for on the following order. Servers, the ERP and the network are kept alive from our desks, office traffic is walled off from production traffic, and calls are taken from every shift including the one that starts at ten at night. Nobody from Apply walks through your workshop, because it is almost never the answer.
Configuration, systems, data exchange and security. Cabling, cabinets and the terminals beside a machine remain the province of your maintenance department, or of the electrician who already comes in: they follow a written procedure of ours, with an engineer watching on video.
Zones get drawn, filtering rules written, and both applied without anyone travelling, so that a controller, an operator panel or a line-side computer talks to precisely what it needs and nothing further. The outcome is documented in the shape a NIS2 file wants, following what ANSSI publishes about industrial systems.
Sage, Cegid, Divalto, Odoo, SAP Business One or Business Central, whether on iron you own or on rented capacity: the machine, the database, the copies, the patching and the permissions are ours to hold. Work slots get negotiated with whoever implemented the system, and they never land in closing week or on the first day of a production campaign.
Orders travel out to the production planning application or the MES, while completions, scrap and material consumption return. Building those exchanges and then watching them removes the ritual of copying numbers off a tally sheet at the end of a shift. Example: a machining workshop that used to key its times twice now reads them straight from the terminals.
Switches, firewalls, servers and backup jobs stay under observation with nobody asleep at the console. Lose the connection to the finished goods store at twenty to three, and the duty engineer is already looking at it while the shift leader is still on the other side of the building.
A supplier's service desk has to reach its own equipment, and nothing resembling your accounts department. Rather than a remote-control tool that has squatted on a PC since 2019, we grant an account bounded in time, confined to a single segment, recorded, and closed again without anyone remembering to do it.
Under our round-the-clock support service, a ticket raised at three in the morning inherits the same reaction target as one raised mid-morning. Saturdays, Sundays and worked bank holidays are treated no differently.
Anything touching the production network is scheduled around stoppages you have already planned and around preventive maintenance. Nothing gets switched while an order is on the machine.
Discovery across the network, a proper read of the firewall rules, an inventory of the ERP environment, and a conversation with production about what must not stop even for ten minutes.
What lands on your desk is a division between office and plant, the crossings that will be permitted, the machines wanting isolation first, and dates pinned to stoppages already in the calendar.
Configuration goes in remotely, one workshop or one line at a time. Where a cable has to move port, your technician does it against a checklist while we watch the effect live on the console.
Monitoring, patches inside agreed windows, a periodic review of rules and supplier logins, and support hours drawn up to match how your shifts actually rotate.
Ransomware arrives through the purchasing inbox far more often than through a lathe. Which is why separating the two networks remains the best value protection a plant can buy. With the crossings kept tight, an attack stalls at the boundary: production keeps turning while the office estate is rebuilt from copies.
Quite possibly. A number of manufacturing activities fall inside the scope, and whether yours is caught turns on what you make and how large the company is. That determination belongs to your legal adviser, whom we supply with the technical facts. Our half comes next: risk management, access control, incident handling and a documented way of reporting to CERT-FR.
No. Ladder logic, recipes and commissioning stay with whoever built the line, or with your own automation staff. Network, access, servers, the ERP, data exchange and the security wrapped around them are ours. Writing that boundary into the contract means nobody wastes twenty minutes guessing who to ring when something stops.
Almost everything here is configuration and software, and a secure remote session covers that completely. For the rare physical job, swapping a failed switch or moving a patch lead, your maintenance team follows a numbered procedure with our engineer listening. In most weeks that is faster than a technician sitting in traffic on the ring road.
Upgrading is frequently impossible, since the supplier's software will not run on anything newer. Fencing them off is the practical answer: their own segment, nothing routed towards the internet, only the exchanges the machine truly uses, USB blocked, and a disk image kept somewhere safe. On those terms they can serve out their years until a supported version exists.
The opposite, it usually helps. Modules, reports and user training stay with them; hardware, database, copies, performance and logins come to us. Putting that split in writing means a version upgrade arrives with everyone clear on who readies the environment and who runs the installer, instead of two suppliers waiting for each other.
Start opens at EUR 690/month excl. VAT covering up to ten users, Business sits at EUR 1,490/month excl. VAT, and Premium begins at EUR 2,900/month excl. VAT. Work taken outside a plan is charged at EUR 95/hour excl. VAT. Choosing between them comes down to how many machines are in scope, which hours need covering and how quickly production has to be back.
Describe the workshops, name the ERP, and say how the shifts rotate. Within one working day we answer with a sensible place to begin separating the networks.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.
