Many schools have decided to go to the campus network Authentication & Billing, often starting with a student complaint, a web-based Caton work order or year-end audit requirements retroactively. The most easy mistake before actually doing it is to make the most obvious mistake."Buy a system."As a target, the school's own network is not clear. The system can be found in half of the software itself and half of it has been misjudged in the early stages.
We'll have to clear the existing network exports and topsup.
The first thing is not to select a manufacturer, but to draw up the network structure of the school for several years. The export is a single commercial broadband or multi-operator conglomerate, what is the core switch brand type, whether the dormitories, teaching areas, office areas are the same network, wireless coverage is centralized or fragmented. This determines which floor NATSHEL_AUTH_BILLING system will be attached and whether it will actually be managed to the end. We have seen two separate networks in high-level jobs, dormitories and teaching districts, with the result that they are designed on a single web basis, and that no cost strategy can be found until implementation, and the costs of back-work are higher than the system itself.
Make sure the size of people and terminals is real, not a head shot.
Authentication & Billing system pressure is not on peak bandwidth, but on the scale of the certificate and account. Separates the number of students in school, the number of teaching staff, temporary visitor peaks, and superimposes the reality of a multi-end. A student hangs up a machine, flatbed, notebooks, and it's common in his dormitory to add a gamer and smart sound box, which will be far more than imagined. If you can estimate this data, then there will be a loss of authentication services that will be filled with page cards."About 10,000 people."- Go get it.
Confirm whether the existing certification system can be reused
Many schools have long had a common identity or Internet accreditation predecessor, some with Radius, some with portals, some with simple restrictions on the gateway. Whether the new system is going to work through these old systems, it is necessary to punctuate at the project stage. Reuse them to avoid keeping two sets of accounts and two sets of tubes in the back. It is impossible to re-use them and to make clear the relocation programme well in advance.
Think about it."Charges"What the hell is that?
The campus network Authentication & Billing"Charges"Some schools just want to run traffic statistics and fair speed limits, not really collect money from students; some have to consolidate the accommodation network fees into a single settlement; others have to be paid monthly and extra. If we don't match this with business, then demand files will fight each other before we add it up. We suggest that we pull three sides of the finance, science workers, network centers to a table."Who's to receive it? How?"Let's talk about technology.
Write compliance and log retention requirements into the boundary first
The education industry has a hard-line requirement for online logbooks and real names, which is the bottom line that Authentication & Billing cannot bypass. The project design phase will have to identify log retention cycles, access rights, audit calibres, etc. items before they are accepted back by security services. This involves, in particular, student personal information, what fields exist, how long they exist, who can check them, and the need to pre-empt and school data compliance tables, which cost far more than one set of software.
The bottom line is on paper, not in the head.
The first few, if only discussed during the meeting, will be different when bidding is required. It would be more prudent to produce an internal status note that makes clear the five types of network capping, account size, list of old systems, model positioning for billing, and compliance requirements as a basis for follow-up requests and acceptance standards. This does not start from scratch even if someone else follows them. Whether the campus network Authentication & Billing system can work well, often looks unsettled on the ground before it is created.
Synchronize the mapping findings to finance and academic staff, building a cross-sectoral consensus
The five items of network-plating, account size, old system, billing and compliance requirements are eventually turned into documents recognized by all three departments. The network centres care about how to manage the accounts, how to make financial accounts clear, and how students’ feelings and complaints are taken into account by their learners. If they remain in technical units, the needs are written separately.
Don't ignore the bottom of wireless coverage blind areas and old equipment.
NATHHELL_AUTH_BILLING"Accessed"But students often complain from"I can't get it."The mapping process should be combined with the wireless signal strength, dead end, old exchange-set hardware versions of each region. These are not directly regulated by a billing system, but they determine that students cannot feel it when they are online. We suggest that a separate list of blind areas be included in the current period, and that decision-making levels be informed that this is another budget.