IT standardisation in education
Shared IT requirements can make schools easier to support. Meaningful choice depends on whether different solutions can meet those requirements.
Describing requirements and comparing solutions
Shared requirements save schools from solving the same operational questions repeatedly. They can specify quite different things, however: a function, an interface or a particular product. Assessing an alternative starts with understanding which kind of requirement applies in the situation at hand. Security, integration and support can only be compared transparently when the requirements are specific. Open standards may allow different implementations; that is not the same as specifying one product.
Establishing the applicable conditions
The education ministry’s IT-standardisation information provides a starting point. Before changing a system, the school and its responsible IT staff should clarify which requirements apply and who assesses a departure from them. A trial therefore needs to demonstrate more than successful installation. Administration, connections to existing systems and available support matter too. A blanket claim that free alternatives are permitted or excluded everywhere would overlook these differing conditions.
Sources and further information
- BMB: Free and open-source software (opens in a new tab)
Further reading: the ministry’s overview of free software in education.
- BMB: IT infrastructure standards (opens in a new tab)
Background: official infrastructure requirements. The practical considerations in this article are editorial guidance, not a quotation of these requirements.
- OSOS Austria (opens in a new tab)
Further reading: the association’s aims and perspective.

