A year after the school network billing system was online, many schools entered."The transport is on a daily basis, and the problem comes up."The system runs, that's the end of most projects. If you want to do better, this is the point of a year."Look back."♪ The good times ♪——The system has run through a full school year, with peaks of the start-up, end-of-cycle and graduation seasons, and accumulated data for one year, sufficient to make a meaningful retrace. Looking back is not a prick but a smoother run over the next three to five years.
Users 'Record
After a year of operation, the school network billing system starts with a review of user usage data: total number of users throughout the school; number of active users per month; distribution of users (student/teacher/outside guests); distribution of traffic consumption; peak time-time characteristics; excess user ratios; and number of arrears accounts. These data reflect the real use of the system and are the basis for subsequent strategy adjustments. For example, 70% of traffic is found to be concentrated on 20% of users, indicating that there may be problems in the flow allocation strategy; the fact that outstanding account accounts are concentrated on several colleges, demonstrating that the Institute’s account management process has improved space. The data recovery disk is intended to form documents as input into the next phase of work.
Categorization analysis of complaints data
Draw up the user complaints records for a year to be sorted and analysed: What are the settings in which complaints are concentrated? The certification, billing, payment and UI issues each have a percentage? Which complaints are recurring? Which complaints are excessive? Which are underlying system design problems and which are user use problems?"Gold mine"Because users vote with their feet to tell you what's wrong. After a classification analysis, an improved plan for HF complaints can be eliminated by 80% of the HF complaints in one year.
Completeness check of financial reconciliations
Financial reconciliations for the school network billing system are checked on a monthly basis——The billing system accounts and campus card accounts are consistent? How many differences? Why the difference is distributed? A long-term small discrepancy may be a large number."How much money did the system get online and how many traffics did you save?"The basis for this management issue.
Review of systemic performance indicators
The technical indicators also need to be reviewed in a comprehensive manner: RADIUS authentication response time, CKEDITOR content loading speed, database query performance, backup recovery time, disk space usage, CPU and memory usage rates. One year after running, some of the indicators may already be close to thresholds.——For example, the database files are growing more and more time to back up, and the search is becoming slower. These problems do not have a major impact if they are not addressed immediately, but they may become system bottlenecks after two years of accumulation.
Evaluation of the effectiveness of strategies
Some strategies were reasonable when they were formulated, but they were no longer applied after user behaviour changed. For example, the flow of certain categories of students (design and video) was high, with a clear shortfall in original free amounts; some periods were at peaks but few real flows allowed for adjustments to be made.
Optimizing the transport process
The system should be mature in a year, but it still has room for optimization. For example: Is the SOP clear on common problems? Is the shift going smoothly? Has the emergency response process been rehearsed? Are the DMS updated in time? Is the DIV tool available? The actual DV experience of one year is best input?
Planning for phase 2
One year after the school network billing system is online, it should be considered that a second phase will be built. One may cover only dormitories and some teaching buildings, while the second phase will include libraries, laboratories, administrative offices. The first phase may support simple monthly packages, the second one will support more flexible traffic packs, and the combined package. The second stage may have to be based on basic charges, while the second part will need to be fine-tuned flow integrator, application recognition, behavior analysis.——You can do better with one year of data and experience. One step in the pit, two step out.