Skip to content

Technical operations and support

Installation is the beginning of running a service, not the end. Dependable support turns free software into a workable environment for everyday teaching.

Who looks after the service once it is installed?

Initial setup is followed by recurring tasks: installing updates, managing accounts and backing up data. When something fails, teachers need accessible help so lessons can continue. That work needs to be organised regardless of the software’s licensing model. Open code allows different arrangements for that work: internal expertise, shared support or a service provider. It does not remove the tasks. Even software without licence fees requires time, people and an operating budget.

Protecting knowledge and recovery

Contacts, cover for absences and maintenance windows should be agreed before launch. Clear documentation helps when the person who knows the system best is unavailable. It needs to explain real procedures, not merely collect configuration files. Backups and recovery belong together. Testing the route back establishes whether data, access and services can be restored after a failure. This less visible work determines how dependable the chosen system will be.

Sources and further information

Related reading