B-01 / OPERATION WATCH
Managed Network Watch
The first routine on the bench is the quiet one. We place a continuous watch over the office network so that a degrading link, a saturated uplink or a switch that has quietly rebooted is seen while it is still a footnote rather than a Monday crisis. Access points, switches, routers and the internet hand off are polled through the working day, and each device is judged against a known-good baseline that we recorded when the office was calm.
When something flaps, we do not simply raise an alarm and walk away. The event is written into the batch log with a timestamp, the affected devices are grouped to the users who touch them, and a decision is made: reset now, schedule a replacement, or keep watching. Most faults are closed before a single user notices. When a fault needs a part, we note the part and the lead time so the office knows what comes next.
The watch also covers the boring essentials that quietly matter. We track whether the firewall is still receiving updates, whether the guest network is still separated from the work network, and whether the oldest access point in the building has started dropping clients at the edge of its range. If wireless coverage has drifted out of shape since the last move, we map the dead corners and propose a small fix rather than a wholesale replacement. Watch is the routine that keeps the other five from being needed.
B-02 / OPERATION RUN
Backup and Restore Runs
A backup that has never been restored is not a backup, it is a hope with a schedule attached. Our second routine treats the restore as the real product. We design the backup set against what the office would actually miss: the finance files, the client folders, the mail store and the line of business database. Then we schedule the nightly run, confirm the job report each morning, and keep enough versions that a file deleted last Tuesday can still be returned on Friday.
Verification is deliberate and repeatable. Once a month we hold a restore drill on real files drawn at random from the set, timed so we know how long a recovery would take and not merely that it works in theory. If a backup window is colliding with the working day, we move it. If a mailbox has outgrown the job, we split it. If a laptop is the only place a set of files lives, we bring it into the routine and take it out of the danger zone.
We also write the recovery plan down. The plan names the order in which systems come back, who calls whom, and where the spare media and keys are kept. An office that has never rehearsed a recovery tends to freeze on the day it needs one; an office with a rehearsed plan simply works through a list. For firms preparing for an audit or a client review, the signed restore drill log is often the simplest evidence that their data is genuinely protected.
B-03 / OPERATION CLOSE
Helpdesk Queue Care
Tickets arrive by phone, by email to hello@otratech.buzz, and by a walk to the bench. Our third routine is to take every one of those channels and fold them into a single queue so nothing is lost between them. Each ticket gets a clear owner, a plain description of the fault, and a next step that the next person can read without asking around the office.
We triage by impact rather than by who shouted first. A printer that is down for one desk and a server that is down for the whole floor are not the same problem, and the queue says so. Quick fixes such as a stuck session or a full mailbox are closed the same working day. Longer work such as a failing disk or a software compatibility issue is scheduled but never left silent, because each open ticket carries a written update at least once a day while it stays open.
The queue is also where we learn. Patterns across tickets show a router that needs replacing, a training gap that keeps generating the same password reset, or a shared drive that is being used in a way it was not built for. We read those patterns back to the client in plain language and recommend a change before the queue numbers start climbing again. Queue Care is not only about closing tickets quickly; it is about closing the sources that keep creating them.
B-04 / OPERATION SETUP
Office System Setup
When a firm moves desks, opens a second floor or starts from an empty unit, the setup work decides how calm the next year will be. We plan the office as a system before the furniture lands: where the sockets run, where the wireless access points need to sit, how the shared drives are named, and how printers are shared so that no one is printing to a device two rooms away by accident. The plan is drawn so the owner can see the trade-offs in cost and effort before committing.
On the day we build it, every cable is labelled at both ends, every device is recorded with its address and owner, and the rack is dressed so that a stranger could trace a lead. Internet service, firewalls, mailboxes and file shares are brought up in an order that lets us test each layer before adding the next. New starters are not left to guess which drive is the live one or which printer is the colour one.
Setup ends with a short handover, not a long manual. We leave a one page guide that names the shared drives, the support address, the password process and the way to raise a ticket. The aim is that the office can run its first ordinary week without calling us for anything, and that when they do call, we already know the room because we drew it. A well finished setup is the cheapest foundation any later routine can stand on.
B-05 / OPERATION TIDY
Server Room Tidy-Ups
Dust, unlabelled cables and a warm corner are how most outages quietly begin. This routine opens the cupboard or the small server room, maps every lead, and rebuilds the space so it can be reasoned about again. We trace each cable to its device, replace the patch leads that have gone stiff, label both ends, and separate power from data so the room stops behaving like a knot.
Alongside the cabling we service the hardware that is easy to forget. Filters and vents are cleaned, the failing fan is swapped before it stops, and any disk showing early warnings is scheduled for replacement. Battery units are tested so a short power cut does not take down the rack, and the temperature and airflow are checked so the equipment is not cooking in a closed cabinet. We photograph the finished room and file the photos with the rack plan.
The result is more than tidiness. A clean, labelled room cuts the time it takes to fix a fault, makes a warranty visit possible without a long explanation, and turns a place that everyone avoids into a place that can be serviced at speed. For firms that have inherited an office from a previous tenant, a tidy-up is often the single most useful first job, because it removes hidden risk before any new plan is built on top of it.
B-06 / OPERATION ROLLOUT
Software Rollout Support
A new accounting package, an operating system update or a line of business tool should not stop the office for a week. Our sixth routine carries a change from pilot to every desk with a rollback plan in the drawer. We stage the software on two or three controlled machines first, test the workflows that the team actually uses, and only then begin the wider push during quiet windows rather than in the middle of a deadline.
Rollout support includes the unglamorous parts that decide whether a change is welcomed or resented. We check licence counts and activation, prepare the data migration so records arrive intact, and confirm that printers, scanners and shared drives still work after the upgrade. Users get a short note explaining what has changed and what they need to do, and the helpdesk queue is briefed in advance so the first few questions are answered without delay.
We keep a rollback path open until the change has settled. If a vital tool turns out to be incompatible after all, we can step the affected desks back to the previous state and try again on a better plan. Once the rollout is stable, we fold the new software into the watch routine so it is patched and monitored like everything else. Change handled this way stops being an event that the office dreads and becomes an ordinary line in the batch log.