Aber Systems

~/support

Support and maintenance

A helpdesk for the people, monitoring for the machines, and updates applied on a plan. For systems we built or set up, and for ones we take over after a review.

Scope
Helpdesk, monitoring, updates and routine maintenance.
Starts with
A review of the systems to be supported and a written agreement.
Runs as
Tracked requests, automatic checks and a regular maintenance routine.
Leaves you with
A record of every request and change, in plain language.

01 Coverage

Three kinds of care for systems in daily use

Support is what happens when someone asks for help. Maintenance is what happens so that they need to ask less often. A support agreement states which systems are covered and to what extent.

A / helpdesk

Helpdesk

One place for your staff to ask for help with computers, accounts, software and the systems we look after.

  • Requests logged and tracked from report to resolution
  • Remote assistance for day-to-day problems
  • Account changes for new starters and leavers
  • Help with the software we built or maintain for you
  • A written note of cause and fix for each request

B / monitoring

Monitoring

Automatic checks on servers, services and backups, so problems are noticed by us before they are discovered by you.

  • Availability of servers, websites and applications
  • Disk space, load and service health
  • Results of backup jobs
  • Expiry of certificates and domains
  • Alerts reviewed and acted on, not just collected

C / updates

Updates

Operating systems, applications and custom software kept current on a schedule, with a way back if an update misbehaves.

  • Operating system and security patches
  • Application and dependency updates for custom software
  • Firmware for network equipment
  • Staged or tested first where the risk justifies it
  • A change log of what was updated and when

02 Requests

How a support request is handled

Every request follows the same five steps, whether it is a forgotten password or a server that will not start. Only the urgency changes.

  1. Report

    You describe what is wrong, who is affected and what you were trying to do. A screenshot or the exact error message helps.

  2. Log and acknowledge

    The request is recorded so it cannot get lost in an inbox, and you are told that it has been picked up.

  3. Triage

    We set the priority by impact: one person inconvenienced is different from a whole team unable to work.

  4. Fix or work around

    We resolve it remotely where that is possible. If a full fix will take longer, we look for a workaround so work can continue, and tell you what happens next.

  5. Confirm and record

    We check with the person who reported it that the problem is solved, then record the cause and the fix.

aber@systems: ~/support

aber ticket open "Shared drive unreachable since this morning"

loggedreported by the office manager · affects the whole team

aber ticket triage

priorityhigh: work is blocked for several people

aber ticket work

foundfile server volume full after a large export

workaroundspace freed, drive reachable again

fixstorage alert added to monitoring

aber ticket close

resolved · confirmed with the reporter · cause and fix recorded

Illustrative example of a request, not a real ticket.

03 Maintenance

The routine that keeps requests rare

Most outages are announced in advance by a disk filling up, a certificate nearing expiry or a backup that quietly stopped. Routine maintenance is the habit of looking. How often each task runs is set in your support agreement.

TaskWhat is doneWhat you receive
Updates and patches Operating systems, applications and firmware are updated on the agreed schedule. A change log of what was updated.
Backup checks Backup results are reviewed and a restore is tested periodically. Confirmation that a restore worked, or a note of what had to be fixed.
Monitoring review Alerts and trends are read through: disks filling, services restarting, certificates nearing expiry. Issues raised before they turn into outages, each with a recommendation.
Accounts and access Accounts are compared with your current staff list and unused access is flagged. A list of accounts to confirm or remove.
Renewals Domains, certificates and subscriptions are tracked against their expiry dates. A reminder before anything lapses.
Summary The period's requests and maintenance work are summarised in plain language. A short report: what happened, what was done, and what we suggest next.

04 Questions

Common questions about support

If yours is not here, ask it directly: contact@vatutuexa.site.

Can you support systems you did not build or set up?

Yes, after a review. We need to understand a system before we can be responsible for it. The review produces the missing documentation and a list of anything that looks risky.

How do we send a request?

By email to contact@vatutuexa.site, unless another channel is agreed in your support agreement. Say who is affected, what you were doing and what the error message says.

How quickly do you respond?

Response arrangements are agreed individually and written into the support agreement, based on how critical each system is to your work. We do not publish a blanket promise here, because the honest answer depends on what is being supported.

What if a request turns out to be a new feature?

We say so. Small changes are handled within support if your agreement covers them. Larger ones get their own scope and estimate, the same way a new project would.

Do you work on site?

Many problems can be solved remotely. For work that needs hands on the equipment, tell us where you are and we will say plainly what can be arranged.

What happens to the documentation if we stop?

The terms for changing or ending support are set out in the agreement. The documentation of your systems is written so that another administrator could pick it up.

05 Next step

Tell us what needs looking after.

List the systems, say how many people depend on them, and mention anything that has been going wrong. We will reply with questions and a suggestion for the review.

aber@systems: ~/contact

mail contact@vatutuexa.site

systemscomputers, servers, cloud services, custom software

peoplehow many depend on them

todaywho looks after things now, if anyone

troublewhat keeps going wrong