Many school systems run off and suddenly have large areas to connect, and then look back at the success rate of certifications a week ago. When we built our system, we kept saying that daily targeting was meant to stop before problems became complaints. This is about the number of places that should be counted in the day-to-day accommodation, and what each count means.
The certification success rate is the first warning.
The most important thing to see every day is the success rate of certification, which is the proportion of real success in trying to land. Normality should be more than nine-nine percent, and when it falls to ninety-five percent, something happens. It may be because the authentication server has tight resources, an AP line goes off, or the interfaces are overtime. We suggest that we make a curve, take a look at each day, then go down and check it immediately.
And the number of combs and the excess capacity must be buffered.
The certified server and export bandwidth are capped. It is still far from the current limit for daily monitoring. In general, only 30% of the excess is used, but the peak of the dormitories can reach 80% at night, which is thin. We suggest that a minimum of 30% of the capacity be kept at the peak, which is below this level. Many schools usually do not look at it, start school or test week tops to fill up the building.
Bill reconciliations cannot stay overnight.
The billing system collects money on the same basis as the channel of payment, which is the bottom line for finance. Daily inspections are to look at reconciliations and amounts, ideally zero, with one or two entries that need to be checked on the day they occur. We only saw schools fail to match thousands by the end of the month, take three days to trace, and then start auditing. It is recommended that reconciliations run automatically every day, differences list passed to finances, minor discrepancies were processed on the spot, big differences were immediately stopped. Reconciliations are not at the end of the month, but daily.
The account sync delay is a concern.
If the billing and dormitories systems are connected, then look at the delay in data synchronization on both sides. The normal thing is a minute level, when it becomes several hours, the problem arises when the transferred student is unable to certify in the new room, the person who leaves the place is still paying for the fee. We suggest that inspections see the final time of the simultaneous mission and the number of failures, and the failed task reruns on the day it fails. Synchronization links are invisible, usually invisible, and it is important to know. Synchronization takes one mark on the checklist, so that complaints are not forgotten.
Trends in bandwidth use
The trend in the use of the bandwidth for the accommodation export is a forward signal of expansion. If the peak utilization rate increases at night for months, it means that the bandwidth is up and six months ahead of the budget to be used for temporary repairs. We suggest a monthly stretching of the bandwidth curve to see if the peaks are rising or if there are new high-energy applications."Quick!"The inspection also takes the bandwidth trends with it, and the wiring is a full picture of the experience.
The unusual account list is over every week.
As mentioned earlier, daily inspections are required: to draw a list of accounts that are unusual and excessive, often cross-story lines, and carry the same one every week, confirming that they are shared or limited. We suggest that this be done in a routine manner, with little but no hard-on cases. The threshold for an exception is separated from normal multi-equipment equipment, so that it does not get hurt.
The inspection must be in rhythm.
The indicators are called " inspection ", and no one looks at them. We suggest that the inspections be set to rhythm: success rates, capacity, reconciliation differences are cleaned daily; simultaneous delays and bandwidth trends are reviewed every week; unusual account lists pass by; monthly rolls are carried out once a month. Each person assigned to it is responsible for looking, looking for anyone who is abnormally, writing an entry guidebook. We have seen schools with big screens, but nobody stares, and the indicator has been red for three days. The value of the inspections is not that they are good tools, people are watching action on time.
Alerts are more aggressive than reports.
The inspection cannot rely on people looking at the statements daily; key indicators are subject to a threshold alert, success rates are dropped, reconciliations are over and systems automatically push those responsible. Warnings turn passively into active knowledge, and people can be woken before computers.
The daily check of the system for online billing in accommodations captures certified success rates, excess capacity, reconciliation discrepancies, synchronous delays, bandwidth trends and unusual accounts. The indicators are not much. These indicators are not needed, the system is basically smooth for a year without major disruptions.