Identical kits
The same models and one pre-prepared system image everywhere. Loan stock, spares and instructions become common to the whole network.
The value here is not in the hardware itself but in its sameness. It makes support cheaper and noticeably shortens the time to open the next location.
The same models and one pre-prepared system image everywhere. Loan stock, spares and instructions become common to the whole network.
The private links to head office are built to one scheme, and every location has a backup connection.
Permissions are granted by the same rules regardless of city and revoked from one place when someone leaves.
Requests from every address go to one number with the same deadlines. A salesperson in another city does not need to remember the local technician's phone number.
Local contractors work to our instructions and under our supervision, but the request still goes through the shared line.
It shows at once where most requests come from and which location it is time to invest in.
Redoing everything at once is expensive and pointless. The template applies to new addresses, and existing ones catch up as hardware is replaced on schedule.
We gather what is installed in each city, who repairs it, what contracts there are with providers and when the licences expire.
We write down the contents of the kit, the connection scheme and how permissions are granted. From then on the document applies to every address.
We rebuild one location and use the result to correct the scheme before it spreads across the whole network.
We bring addresses on stream to a calendar. New ones are built to the template straight away; existing ones convert as equipment is replaced.
A mixed estate costs dearly not at purchase but afterwards. Five addresses with five different routers give five sets of instructions, five spare parts kits and an engineer who has to recall the settings afresh each time. A common template starts paying off by the third location, and by the fifth the difference is plain to see.
Usually one of them stays as hands on site, but now works to our instructions and under our supervision. What changes is the chain of responsibility: a request goes to the shared desk with a common deadline rather than straight to a person you cannot always reach.
No, and we would not suggest it. The template starts applying at new addresses and during planned refreshes. Working hardware serves out its life; it is just that future purchases follow one common list. The transition stretches over a couple of years and is barely visible in the budget.
Считаем по суммарному количеству компьютеров во всех городах, как для единой компании. Наценки за сам факт филиала нет, но запасные каналы и выезды в регионы попадают в расчёт. В пересчёте на одно место сеть обычно выходит дешевле, чем те же точки по раздельным договорам.
Requests by address, deadline compliance, recurring patterns and open risks. From it you can see, for example, that a third of all tickets come from one city, and instead of expanding support you can go and deal with the cause.
Напишите, сколько точек, в каких городах и кто их сейчас чинит. Соберём опись и предложим образец вместе с планом перехода.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.