opti.glass

2 min read

Moving the server out of the workshop back room

When the machine in the back room fails the work stops and nobody knows about the backup. Here is what browser based working changes on the floor.

In glass workshops the software usually has a room of its own. A computer in a dusty corner, a program installed on it, a lock device beside it and an external disk underneath. As long as that machine is on, everything runs. The day it stops, the work stops with it, because the data is on that disk, the program is in that installation, and nobody knows exactly when the last backup was taken. The arrangement works for years and then one day it does not, usually in the busiest week.

The first answer browser based working gives to this is that installation disappears. There is no program to install, no licence file to carry over and no lock device to plug in. The computer in the office, the old laptop next to the bench and the machine at home all reach the same address and see the same data. Adding a device is no longer an installation task but a permission task. It also means swapping machines carries no risk; a broken computer stops being a crisis.

The second answer is where the data lives. Data is kept on our own server in Turkey and is not transferred abroad. An automatic backup is taken every night and backups are kept for seven days. What matters here is that the backup depends on a process with a duty rather than on a habit. The trouble with backups taken by hand is not that they are forgotten but that the omission is discovered a week later. A business's data stays its own; it can be exported even without a subscription.

The third is access. Glass work does not sit at a desk: the same information is needed while measuring, while talking to a customer or during dispatch. A screen opened in a browser asks for no separate setup. The fact that network coverage in a workshop is not always the same quality is taken into account too; when the scanning terminal loses its connection it queues the scans and processes them in order once the connection returns. The operator does not think about the connection and carries on.

The side of this move that usually gets overlooked is updating. With installed programs every update is an event: who installed it, which machine still runs the old version, which report broke. Working on a shared server means everyone sees the same version, and the oddities born of version differences disappear. Two people seeing the same screen differently is one of the hardest kinds of fault to resolve.

You do not have to move everything in one day. Starting to enter new orders on screen while leaving the old arrangement beside it for a while is enough. A few weeks later the question of what the old machine is still switched on for comes up by itself. What changes is not the work; it is the number of places the work can get lost.