Wireless Portal is used for years, and the most worrying thing about a full-scale school when it's upgraded. We have seen a cutover on weekends, so half of the people who start school on Monday are not online, and the phone calls are blown off. The switch is not so simple as a new software, but a whole school bottom seat, which has to be managed as a staged, pre-emptive project, rather than a weekend action.
New and old systems running in parallel.
The surest thing is that the old system continues to serve for a couple of parallel periods, and the new system runs real traffic next to it. We usually suggest two to four weeks in parallel, feeding the real terminal, real peaks, to the new system, and confirming that no problem can be solved. Parallel listening costs resources, but much safer than rolling back and forth when one cut goes down.
Account number and strategy migration validation
The most easy thing to do is account number and strategy migration: old system accounts, terminal bindings, regional strategies, moving to the new system cannot be lost. We suggest that the relocation should be fully exported before it is moved, tested for category-by-category verification, student accounts can be checked out, strategies are effective, logs are continuous. One key shift by a non-constituent firmer will be verified on our own.
Greyscale Switches Not Full
Cut the flow one by one, according to regional greyscale: cut a building first, observe a day no problem then cut another dormitory area last. We usually leave the dormitory area last because it is the most sensitive and the highest. Greyscale keeps the problem localized and does not blow together. Each slice, looking at the curve of a day's success rate, is anomalous.
Backrolling plans must be real.
We suggest that we get the real scene drills back to work before switching. We don't want a plan lying in the file. Roll back, and we can do it when you switch. Many schools are afraid to go back, practice back, and then get back to life.
Mistakes and reconciliation of accounts
To change the actions to leave or late at night, as much as possible, and to reduce disruptions for students in use. If the old system is billed, reconciliations are performed when replacements: old balances, relocation amounts, three pairs of transactions from the new system confirm that there are no student balances that are lost. We suggest a daily reconciliation report during the first week after the replacement. The wrong peak plus reconciliation is a minimum of two matters, none of which is true.
Early communication is more important than technology.
Before the change, a notice was given to students and teachers that they could be short-lived, with problems finding anyone, and complaints falling by half. We saw good technology but no communication, and students blew up little Caton when they met it. Communication is not redundant, it is part of a replacement project. Better management of expectations, less pressure on changing the day's customer service, and less abuse in network centres.
Data ownership is written into the contract.
The most appropriate early confirmation is that all data on the Internet are owned by the school and must be exported in their entirety. We suggest that the contract should include a form of attribution and export, without being tied to the private structure of the manufacturer. Many schools did not write it, and at the time of the change they found that the history logs were untied, either paid for the conversion or simply lost.
Toggle Convergence Duty
On the day of the official switch, we suggested that the network centre and the manufacturer should be together. The success curves were watched at critical times, so problems could be dealt with immediately. Don't throw the switch away to automate.
Change the disk
Switching to smooth completion is not the end point. We suggest a copy of the document: which presets are useful, which floors are most easy to get and how fast next time. The disk settles down, re-uses it directly without stepping on it. Many schools have been replaced, experience has spread in several people's memories, and tuition will be paid again.
Clear user notification
The new circular says, "Whatever day, may be short-lived, who has problems." We've seen the notice three screens, and students don't look at it at all, but they're even more panicking.
Data backup is verified first
Before changing, you must do a full backup and make sure it's restored. We don't wait until we have problems before finding the backup is bad. We eat this loss, the backup file is damaged early, and it's stupid to roll back. Backup can be restored and we can cut it.
Wireless Portal changes people’s lives by seven steps: parallel, migration verification, greyscale, rollback, faulty peaks, reconciliation, and communication. It is a phased, pre-emptive project that will be managed instead of a weekend move to make the transition smooth.