The campus network certification system takes three or five years, sooner or later. Old systems manufacturers don't maintain, old functional structures fail to hold up, or school integration is a common incentive. But the most fear of upgrading is that they will not be able to do so."To upgrade the Internet, we're all paralyzed."The certification system connects everyone, and a little careless change is a school-wide educational accident. How to keep the promotion quiet and the teacher/pupil almost unconscious is the core of such projects.
Think about whether it's a replacement or an evolution.
The first step of the change is to distinguish: are you completely changing a new system or upgrading it on the original system? The two risks are quite different. A complete replacement means that data, strategy, and all dockings have to move. There's a big problem; version evolution usually fits old configurations and smoothness. Many schools listen."Change"I think of a reversal, but if the original manufacturer is still there and the structure can be expanded, evolution is often a more stable option."Can you do it?"Ask, don't pick the most radical options at once. The level of discipline in the promotion begins with restraint.
The number and data migration is a top priority.
The key assets are accounting numbers and strategic data. Teachers and students' Internet accounts, binding relationships, custom strategies, which must be fully moved to the new system, any missing items will be an accident. We suggest that we do full-scale export and verification before moving, confirm that the number of lines, fields, status are right, then import it into the new system. And migration cannot only move data, but also move data."Meaning": What kind of account in the old system corresponds to rights, and whether it is the same logic in the new system. The data are out of order, not semantic, and worse than not. Moving this big thing is faster.
Switch risk to parallel gyro
The switch determines the impact on students and teachers. The surest thing is that old and new systems are going to be used in parallel: new systems first take part of traffic or parts of buildings, verify the correct amount then gradually cut back, and old systems can be retained back. This way, even if there are problems with new systems, the effects are local and they can be returned at any time."One night, one night, all cut.", because if there is a hidden problem with the new system, the whole school will have a massive breakdown and it won't be possible to retreat. It takes a lot of effort to run in parallel, but it turns uncontrollable into manageable.
We need to re-read the interface.
The old system is often forgotten."Darkly". It's a protocol with the unified identity, how it interacts with the billing system and what goes with the wireless controller, which may not be used as it is. We saw the upgrade before we found that the visitor's access was broken because the new system defaulted not to open the interface. So, before upgrading, you have to list all the dockings, re-check them by item, instead of assuming that they are done."I think so."The connection is invisible, the problem is most hidden and must be tested.
Selecting to do the key action at the low peak.
Even in parallel, some actions can cause instant interruptions, such as switching the authentication core and cutting data. These key steps are to be placed in a window at the bottom of the school-wide Internet, like early morning holidays, with advance notice. At the same time, prepare for retirement: if it is not done, how long will it take to return to the teacher/student without reconnecting."How do we get the worst?"You're not going to panic when you want to get ahead. The dignity of the promotion comes from respect for the time at the bottom and a plan to withdraw.
Leave a period of observation and announce the completion.
The switch to completion does not mean the end of the project. We suggest that we keep at least one or two weeks of observation, with a view to confirming the success rate, synchronization and abnormal login, confirming that the new system is stable and officially shut down. The old system remains in a state of retreat during the period of observation, which is a safety net for the new system. Many schools dismantle the old system on the second day, and as a result, a compatibility problem arises on the third day.
The real cost of the replacement is more than just software money.
The most easy way to calculate the replacement budget is hidden costs: data migration requires manual, parallel operation requires multiple resources and retreats are not in software offers. We've seen schools buy only systems, move and co-opt without budgets, compress steps, cut lines, overtime and compensation after an accident."You can use it when you're done."The optimistic estimates are scheduled.
Tell the teacher and student in advance.
Even if the promotion is smooth, there may be a short shake in the switch moment. Send an advance notice to tell you which time may be short and longer than being later complained of."Know what's gonna happen."We've seen the same little shakes, and the number of early notification complaints drops a lot. This small communication is a watershed in the sense of a different person, it takes 10 minutes to write a notice and save countless explanations.