For school authorities and municipalities
Plan school IT across multiple sites.
Supporting several schools means coordinating different systems and requirements. We help school authorities and municipalities make clear technical decisions while planning for ongoing operations.
Planning across sites
Plan together. Keep local differences visible.
Shared requirements help guide the work. Local conditions remain part of the plan.
Equipment at each site
Record devices, platforms and network areas, taking existing documentation into account.
Local usage
Consider applications, room usage and recurring difficulties at each institution.
Shared requirements
Agree configurations and responsibilities. Document justified exceptions.
The result is a set of technical priorities and an agreed sequence for the pilot, deployment and ongoing support.
Build an overview of your sites
Existing documentation, product support status and planned changes help identify the next technical tasks. We include this information in the assessment of the current environment.
Local needs matter just as much: which applications are required, who maintains individual systems and where do problems recur? A shared overview helps distinguish urgent work from longer-term replacement plans.
Define standards and justified exceptions
Consistent configurations can make administration across several institutions easier. We help agree technical requirements for networks, endpoints and platforms. Site-specific differences remain part of the plan.
One building may need different Wi-Fi measures from another, while a specialist classroom may require particular software. These differences are documented early, rather than being discovered during installation or everyday use.
Plan replacement and rollout in stages
A project spanning several sites needs a practical sequence. We consider dependencies between networks, servers, devices and applications, and agree the pilot, rollout and changeover windows.
Technical planning helps prepare purchases and replacements: which components are needed, which prerequisites must be met and which existing systems will remain in use? Decisions and changes are documented for ongoing support.
Clarify operational responsibilities
Schools, authorities and external support providers carry out different tasks. We agree access, points of contact and change procedures with those involved. A clear handover makes it easier to manage new devices, software and faults later.
Ongoing support covers agreed administration and maintenance. Servers, backups and security components are considered together, so responsibilities account for the connections between individual products.
Working together
Agree who contributes what.
These roles provide a starting point for planning ongoing support.
Schools
Contribute needs and recurring problems from everyday use.
The school authority
Establish priorities and decision-making routes.
thiwico
Prepare and carry out the agreed technical tasks.
Responsibilities and access are agreed with everyone involved. The allocation can differ between organisations and projects.
Questions about planning across sites
Can different existing environments be included?
Yes. We start with the systems already in place and assess shared requirements and justified differences. This does not automatically mean replacing everything.
Does deployment have to happen at every school at once?
The sequence depends on technical dependencies and available changeover windows. A pilot and phased rollout can help apply lessons before deployment at further sites.
Several sites, one clear plan.
An overview of your institutions, existing systems and planned changes provides the basis for shared technical priorities.