A university network is not a large school's network

Student numbers alone do not tell you the capacity needed

In a school, many of the devices may belong to the school itself and be managed under a common policy. Pupils also tend to stay in fairly predictable spaces, and activity is organised around set timetables.

At a university the situation is different. The students are adults and mostly use their own equipment. One person may carry a laptop, a mobile phone, a tablet and a watch, with several of them connected at the same time even if they are actively using just one. This means the number of concurrent devices can be far higher than the number of students in the building.

That is why enrolment figures tell you the size of the institution, but not how to size the Wi-Fi directly. The really useful information comes from analysing the network itself: how many devices connect simultaneously, where they are concentrated, how long they stay connected and how that behaviour changes over the academic year.

In this environment, the user's identity also becomes far more important than the device. If the institution does not manage the student's laptop, the network needs to know who is connecting in order to assign them the right permissions and services.

The network should recognise the person, not rely on a shared password

On a campus it is impractical to manage access with a single Wi-Fi password known to thousands of people. The password ends up being passed around, it does not allow different profiles to be told apart and it makes withdrawing access extremely complicated when someone leaves the institution.

An identity-based model lets each person connect with their own credentials and the network automatically determine what level of access they should have. A student can receive one set of policies, a researcher another, administrative staff another and an outside supplier completely different access, without having to create a separate Wi-Fi network for each case.

This approach also makes it easier for access to follow users when they move between buildings. A student can attend a lecture in one faculty, study in the library afterwards and finish the day in another building without having to learn different passwords or change network manually. It is precisely one of the scenarios where solutions such as PenwinIn add value: authentication depends on each person's identity and not on a generic password passed around the whole campus.

A library is not sized like a large lecture theatre

Higher education has many spaces whose behaviour has no direct equivalent in a school. A large lecture theatre can hold hundreds of people for a relatively short period. They arrive and leave almost at the same time, and device density can shoot up during a talk or a presentation. A library, by contrast, keeps users connected for several hours at a stretch, and usage stays steady for long periods.

Cafés, courtyards and outdoor areas are not simply places people pass through either. Many students work there on their laptops, make video calls or follow a class online. Labs may have their own equipment connected to the network and needs that are completely different from those of an ordinary classroom.

This means each area has to be studied according to how it is actually used. A space where two hundred people stay for four hours should not be designed on the same basis as one where two hundred people come in for twenty minutes.

At a university, the most demanding period can last for weeks

One important difference is that the load on the network changes a great deal over the academic calendar. During enrolment, thousands of users may access the same platforms simultaneously. At that point the main problem may not be Wi-Fi coverage, but internet capacity or the authentication systems.

Exam season creates another pattern. Libraries and study rooms may stay full for many hours, extend their opening hours and hold far more devices than usual. An infrastructure that works perfectly for most of the year can show its limitations precisely in the weeks when it is needed most.

Sizing for a normal week is therefore not enough. You need to identify the most demanding points in the calendar and check that the infrastructure has enough headroom for them.

The research network needs to be kept separate

A university campus may also include something that changes the architecture completely: research groups with their own servers, scientific instruments, computing equipment and data subject to special confidentiality requirements. That environment should not share the same network segment as everyday student traffic. Keeping the two worlds apart makes it possible to control who can access each resource, limit the impact of any incident and apply security policies suited to the level of risk.

There is also scientific equipment that cannot always be maintained like an ordinary computer. Some instruments depend on old control systems that are not easy to update because a new version could affect how they work, their calibration or the manufacturer's support. In these cases the answer does not necessarily lie in updating, but in isolating the equipment properly and controlling very carefully what it can communicate with.

This shows why network segmentation is not just an organisational matter. It can become a vital part of research security.

Halls of residence have completely different needs

When the campus includes a hall of residence or a colegio mayor (a type of Spanish university hall of residence), the network is no longer purely academic. For residents, that connection is also their home internet.

At night, televisions, games consoles, speakers, video calls and streaming services appear. The usage pattern shifts towards evenings, nights and weekends, precisely when activity in the faculties may have died down.

There is also a particularly interesting technical requirement. On a student network it is common to isolate devices from one another for security. In a hall of residence, however, each user may want their laptop to find their own television or speaker, but not the devices in the room next door. In other words, the system must allow some communication within each resident's own environment while keeping it isolated from everyone else.

This means the hall of residence has to be treated as a service in its own right and not as a simple extension of the classroom Wi-Fi. And it has another important consequence: the connection is part of the accommodation service the resident receives, so availability and support carry even more weight.

Guest access is no longer the exception

A school may have guests now and then. On a university campus, visitors may be constant: conferences, seminars, visiting lecturers, examination panels, recruitment processes, partner companies or entrance exams.

That means guest access should not be handled each time with a password written on a piece of paper. It has to be a service capable of generating access in an orderly way, limiting how long it lasts and supporting hundreds of users when necessary.

The system should also show who created each access and how long it will remain active. Ease of use is important, but it should not mean losing control over who is using the institution's network.

eduroam should be taken into account from the design stage

For many universities, eduroam comes into the picture: the academic roaming service that lets members of participating institutions connect using their own organisation's credentials when they visit another institution. In Spain the service is coordinated by RedIRIS and, according to data from eduroam.es, more than 180 organisations take part in the country and the service is available in more than a hundred countries. If a university already uses eduroam or wants to add it, this is a decision that needs to be considered from the start, because it affects the authentication model and how access to the network is structured.

It should not be treated as an add-on bolted on after the roll-out is finished. It is part of the campus identity and mobility strategy.

Nor is a business school exactly a university

Business schools share some features with universities: adult students, personal devices and the need for high availability. But they have characteristics of their own.

One of them is the large number of international students. Many participants come for programmes lasting a few months, use equipment bought in different countries and need to be connected from day one. This makes it particularly important for the process of joining the network to be simple and for the access documentation to be available in English as well.

The calendar changes too. Much executive education may be concentrated on Friday afternoons, Saturdays or intensive weeks. The right time for maintenance can no longer be assumed: work on a Saturday morning may go practically unnoticed in a school and yet disrupt one of the most important sessions at a business school.

Then there are hybrid classrooms. When part of the group is connecting remotely, download speed is not the only thing that matters. Connection stability, upload traffic and the quality of the audio and video systems become fundamental. And many students use corporate laptops connected to their companies' VPNs, which adds another layer to take into account. That is why the network infrastructure and the audiovisual equipment in these classrooms should be planned as a single whole, not as separate projects.

Mobility has to work between buildings and sites

At a large university, users may move constantly between faculties, libraries, labs and other buildings. The experience should be the same in all of them.

Students should not have to wonder what the password is for the faculty they happen to be in. Nor should researchers lose their level of access when they move to another building. The network has to recognise identity and apply the relevant policies wherever on campus the person connects from.

This becomes even more important in institutions with several sites, affiliated centres or buildings spread across different locations. A collection of independent networks may seem simpler at first, but over time it multiplies the administration, the issues and the differences between buildings. Central management allows the whole institution to work to the same criteria even if it is physically spread across many locations.

Monitoring has to understand the campus calendar

A university network also needs a support strategy suited to its real hours. A university with a library open until very late, or a business school with activity on Saturdays, cannot automatically assume that the best maintenance window is the same as in a school.

You also need to know what is happening before the issues come in. Continuous monitoring makes it possible to detect access points that are down, links with problems or unusual increases in use, and to relate them to the campus's normal patterns.

It is not just a matter of receiving alerts. Experience is what lets you interpret whether what you are seeing is really an anomaly. A library full during exam season may see its usual number of devices multiply without there being any problem; the same increase on an ordinary Tuesday in November may well be worth investigating.

Designing for a campus means knowing how it works

A university, a business school and a colegio mayor have different technology needs from one another, even though they all belong to the education sector. Knowledge of one environment should not be transferred mechanically to another.

At PenwinEdu we design, roll out and maintain networks for schools, universities, business schools, vocational training centres, halls of residence and colegios mayores. As well as the Wi-Fi infrastructure, we handle authentication through PenwinIn and provide 24/7 monitoring of the networks we manage, with a support service that offers a response in under four working hours.

Our experience in education allows us to start every project with the right question: how does that institution actually use technology? On a campus, that means understanding the enrolment and exam weeks, the labs, the libraries, the guests, movement between buildings, the halls of residence and the executive education timetables before deciding how many access points are needed.