The first month of the WiFi network billing system in the dormitory is the most vulnerable time for the project. The device was tested normally, so that thousands of students used it at the same time, and the problem of hiding in the corner came out. We followed a number of schools through this period, drawing up a few pits that were almost always drawn. Knowing what they looked like would at least make you feel better when you woke up in the morning, knowing where to look first.
First pit: Batch registration for start-up
The most typical day is the first few days. Thousands of new students get their accounts at the same time, log in for the first time at the same time, authenticated pages, tied payments at the same time, certified servers and billing gateways go several times as far as design peaks. We have seen systems that do not line and limit flow, register interfaces go directly avalanches, and students line up to brush the page. The response is to press the registration peak with analog data before they get online, queue the registration interface and, if necessary, open it by way of building.
Second pit: the balance and billings are not matched
The first week on the line, the finance is most likely to detect a failure of matching bills and receipts. There are three common reasons: payment of refunds has been lost, students have paid but not received confirmation by the system; the change in set and billing cycles was miscalculated at the beginning of the month; reimbursement and arrears offset logic is flawed. We suggest that we draw a daily reconciliation report for the current and billing bill for one month and look at it manually for a week. Not until the end of the month, tens of thousands of missing copies of the financial closure will be missed, and the vouchers will be difficult to track.
Third pit: speed-limit strategy error is normal.
Speed limits are the most easy to flip. Some schools limit single devices too low for bandwidth, resulting in students having a video-teleconference card and complaining that the network is back 10 years ago. Others use an online device to limit the total speed of the equipment, with four units per dormitory, each in a bad way. We generally recommend that the fastest order be set at a set of meals, not the hard cut of the equipment, and leave enough security rates to watch the video.
Fourth pit: authentication page page compatibility issues
The equipment used by students is a variety of, Andre, Apple, Old Flat, even smart TV. If the authentication page is not compatible, some devices open with a code or button and do not move, the student cannot access the network. We'll go over the authentic pages before we get online, especially apples, window-and-winding and Andrew's certification. During the first month, the passenger service equipment was offline, and there are 89 certified pages compatible, not really broken.
Fifth pit: fee-for-blank network triggers a chain complaint
The system automatically defaults the network, which is not logical, but it can be easily misdirected. Students forget to charge and suddenly break the net in the middle of the night, first reacting not by filling it, but by beating customers to say that the network is broken. We suggest that the net breaks are preceded by reminders, grace limits, and then a channel with only access to the page, so that students can recover the fee at one time. The first month makes the alarm and the width logic smoothing, leaving a large gap between complaints. The automatic breakup is what the system should do, but it is hard to make itself feel bad.
Someone's gonna be watching the scene in the first month.
After all, the first month on the line cannot be thrown into the system. We usually recommend that schools arrange for a combination of network centres and manufacturers to re-examine the customer service records and alerts every day for the previous two weeks, classify recurring problems, fix them on the same day. After learning starts and the first fee cycle, the system is stable, and the system is at stake.
You have to prepare your guest speech.
The first month on the line, the customer service is faced with a lot of repetitive questions: how to fill it, why to break the net, and what to do with the password. We suggest that we prepare a standard voice and self-help outlet guide in advance, which will be distributed to building managers and life committees so that students can help themselves. When you have a uniform voice, answer the question and keep the simple question in front of the guest service.
The Greyscale building will test the water first.
If the system supports it, do not push through the system and pick one or two buildings for a week, verify their peaks, bill reconciliations, speed limits and extend to the whole school. The grey scale can kill most of them on a small scale, and the real problem is less. We've seen a whole school run down with a maximum start-up date, and we've been able to get a full-time break.
To help solve the problem, we need to sort it out.
When you reset the first month, not just by recording the phenomenon, but by sorting out the problem: capacity, connection, strategy or compatibility. The drug is taken from the disease before it is finished, or tomorrow is taken. We are used to building a question desk, each recording, cause, repair, and whether it is repeated. A month down, the bill is the most valuable experience of the next system and the basis for determining who should be held responsible when we settle with the manufacturer.