The WiFi network billing system will be used for several years, and schools will consider changing the new system because it is ageing, not functioning enough, and not being supported by suppliers. The switch system is not a simple loading to move user data, billing records, account status to the old system, while ensuring that users are insensitively switched, billing data are not lost, networks are not disrupted. This process is called slicing, which is the most risky link in the WiFi network charge system. Cutting programmes are poorly designed, with large user complaints, heavy counting data missing, network paralysis for days.
Data count and clean-up prior to migration
WiFi network billing system is moved from the old platform, first of all, not to guide data, but to do a data inventory. How many users, how many accounts, how much billing records, how many configuration strategies are used in the old system, and these numbers need to be clearly identified.——The number of dead bodies that have been dormant for years, the unknown number of abnormal accounts, the duplicated test account, and the configured but never used strategy. If this data is not cleared up, the new system will inherit a pile of garbage data, which takes a lot of time to process later shipments. Data clean-up will be graded: clear deactivated, manually confirmed by an unidentified mark, and kept.
The migration of account balances and billing records is a high-risk element
The highest risk link in WiFi network billing system migration is the migration of account balances and billing records. Users have not spent $50, and this balance must be accurate when migrating to the new system. The billing records are used for audit and dispute retroactive and complete after relocation.——Old system"Balance"Fields corresponding to which field of the new system, old system"Flows"Record which field corresponds to the new system.——Fields are different types, accuracy and coded differently. Each discrepancy is manually confirmed and cannot be automatically guessed.——The balances of the old system are equal to the balances of the new system, the records of the old system are equal to those of the new system and discrepancies above thresholds must be checked.
Select and prepare to cut the time window
WiFi network billings select the window that will affect users least. The minimum use of the network is 2 to 6 a.m. in school settings, and it is the best window for cutting. But cutting at dawn is risky.——The solution is to cut the data in a phased manner: first import the data into the new system for interconnection testing, then confirm the correctness and then select one weekend morning for formal cutting.——The information can be provided through a more frequent channel.——Text messages, Apps and the boarding hall are posted.
Design of dual system running periods
WiFi network billing system cut, not recommended"One night switch."——The old system is off Friday night, the new system gets on-line Saturday morning. This way it's hard to get back if there's a problem with the new system. It's safer for two systems to run in parallel.——The old system continues to be a billing master system, the new one is a shadow system, while receiving authentication and billing data without actual costing. Parallel periods are usually 2-4 weeks, when matching data with those of both systems. If differences are acceptable, gradually switch the new system to the main system. The cost of parallel dual systems (both systems maintained) is high but risks low. Schools recommend this approach if budget allows; and, if budgets are tight, at least do sufficient PoC tests before cutting, simulations of real flows verify the stability and accuracy of the new system.
Refund pre-emptive is an essential part of the cut.
The WiFi network billing system cut-backs are as important as the return pre-releases. If a serious problem with the new system is detected during the splitting, it must be quickly returned to the old system. Re-retrieval pres will have several points to be clear: when a refund triggers a retreat (e.g. a failure rate of more than 5% for certification and a fee data deviation of more than 10%), the backup operational step (how the old system was restored, how the new system was processed), the re-retrenched notification process (how the user was notified of the recovery). Retretency pre-does not until the time of the cutting can find that there is bug in the operation. This exercise is not expensive, but it can save lives at a critical time. Without the cutbacks, the problem is hard landing and the impact will last for days.
Post-clicted observation period and problem handling
The completion of WiFi network billing does not mean the project is finished, but there will be an observation period.——Validate success rates, accuracy of billing data, user complaints, and indicators of systemic performance.——The data migration integrity, user experience changes, system comparability, and legacy list. Assessments are really done by cutting.
User communication through the slit process
WiFi web billing system cut is a change for users.——The authentication page may have changed, the operating process may have changed, and the name of the package may have changed."Why can't it be used?"The user communicates throughout the process.——The communication channels are diverse.——Text messages, App-pubs, residential building posters, certified page announcements. User communication seems soft, but in cutting off such high-risk projects it directly affects the number of complaints and user perceptions.