We've taken over a number of school wireless Portal projects, and we have never done anything to touch the pits. The school says we're going to do a wireless certification, ask how it is, and answer it well. And then we get on the line, find that access is old, there are not enough bandwidth, there are many end types, and the authentication system has been carrying a lot of things that it shouldn't be doing.
We'll have to get the current wireless overlay first.
The first thing to do is figure out what the WiFi campus covers, what type of access points are, which buildings are distributed and how many terminals each has. Many schools think that full coverage, with actual basements and old buildings blind, and students connected to their own cellular hot spots. Wireless Portal can't save itself from covering it. We usually need a list of access points and signal heat attempts to cover gaps before we talk about certification.
Terminal type and quantity statistics
The terminal structure of the different schools is very different, with a lot of desktops in the physical training rooms of vocational colleges, a lot of mobile flats for private college students, art dorms and smart sound boxes and games machines. The end-loading strategy of wireless Portal must be based on real structures. We take several buildings to sample them, and we measure the ratio of single terminals. This number directly determines the density of the server ' s capacity and access points, the size of the head shot, which is the line that's laying mine.
Inventory of existing authentication methods
Some schools used broadband dialling, some with simple passwords and others without authentication. The current method determines the complexity of migration: from code to uniform identity relative smoothing, and from dialling to end configuration. We suggest that we should look at existing authentication methods, account numbers, and whether or not to common identity, and export a status sheet. This table is the basis for later requests and bid parameters.
Bandwidth and return to the bottom.
The request for authentication is sent back to the server, and the bandwidth and quality of this return journey directly affects the experience. We have seen the school core switch running through years, and the request for certification is lined up, as it does with WiFi. When you look at the core, you check the balance of the building's return, and the authentication server is set on which floor. This data school often doesn't measure itself.
How do you build the peak model?
The bottom-scree is not just average, but peaks. We usually pull a month's traffic log to find special periods like late dormitory peaks, interteaching peaks, and examination weeks, building a web model. Wireless Portal has a capacity that is 1.3 to 1.5 times the maximum model. Many schools buy capacity on average per day, and they crash at night, without peak models.
Mapping of outputs
The end of the mapping is done with three things: a status map, terminal and flow models, and a list of bottlenecks. These three are all set up so that the needs books can be hard and the manufacturer’s offers can be comparable. We have seen schools skip the touch bidding, and the winning formula is designed on average capacity, and the line falls, and the cost of getting back to work is 10 times more expensive than the bottom.
Do you want to change the old account data?
If the school had an old certification, it would have to evaluate whether or not the old account was moving. If the student is used to the old account, a forced change of number could cause a wave of discomfort; but if the old account system is confused, this one will clean up. We suggest that we take a separate chapter in the report and give recommendations for relocation or reconstruction, and not wait until the line is closed. The account policy is set early, and the rest of the matching and switching are smooth.
The mapping report is evidence to the leader.
The mapping is not a network center for self-recreation, and its output must be reported to the leadership, which supports the budget. We usually use the mapping report as an graphic version, covering heat attempts, end distributions, bottlenecks lists, so that the leader knows why it is spent. Many schools do it, but they don't know, and budgets are in the reporting chain.
The touch is not a one-off.
The campus network changes every year, the endpoints change, applications change, buildings add up and the tweaking is over. We suggest that a re-evaluation be done once a year, especially before large-scale enrolment or new building becomes operational. The low cost of re-testing allows the program to remain true.
The web mapping is the most easy to save but the least in the wireless Portal project. Coverage, terminals, certification status, return journeys, peak models, five samples, are the foundation of the program. It is a stand-alone phase that controls the mapping, gives clear results and bottlenecks, and then the selection and solicitation process does not run out. This step is lazy, with each step being paid back.