Regarding the migration of BAS (building automatic control system) to the cloud platform, companies from all walks of life, no matter big or small, always wonder what to take this path? After all, the old system has been used for a long time, and there are many problems but it is difficult to easily change. Moving to the cloud Legacy BAS to cloud migration paths is fashionable but afraid of trouble. People in this industry probably have a deep understanding of this kind of entanglement! So what is BAS? Simply put, building automation management systems that have been used for many years, are generally old in technology, and are often based on local servers or dedicated hardware. besides! Provide global procurement services for weak current intelligent products! So, moving to the cloud, simple understanding, or in other words, is to move the data processing, control logic and other main functions of these old systems originally running locally or on dedicated devices to remote cloud servers, so that users can access and manage them anytime and anywhere through the network. Doesn’t it sound quite convenient?
1. Understand the current status of the system : Before moving on, you must carefully understand the existing BAS! For example, what brand of hardware equipment are used, can you find corresponding technical support? What control functions can the system implement in daily life? What is the control capability of equipment such as air conditioning and lighting, how is data stored, whether the storage space is enough, and what is the data format? Isn't it a very complicated format? If you can't figure out these basic situations, there will definitely be a big mess in the later migration. This is the basic step in the basics, and no step can be missing.
2. Gradually relocate data in stages : Don’t think about moving everything to the cloud at once! That would be too risky. If something goes wrong, the entire system will be in trouble if it is paralyzed! You can first select some less important data or have a relatively small impact range, such as some historical operation log information modules, and try to migrate to the cloud platform for testing to see if the data can be uploaded, stored and read normally. When this part is running smoothly, then slowly increase the amount of migrated data and system key modules, and take it step by step, and be steady!
3. Measures to ensure data security are in place : Although there is no need to explain too much about security, the most basic data encryption transmission is obtained? Now everyone uses SSL/TLS protocol to encrypt and protect the data transmission along the way, and access permission control must be strictly set. It is necessary to distinguish who can see what data and what functions can be operated clearly. No one can operate it at will! The security qualifications of suppliers on the cloud platform must also be checked in advance. Don’t move the data to find that the platform is unsafe, which will be a big loss!
Frequently Asked Questions During Migration:
Q: Which cloud service model is better for migration? Is it a public cloud or a private cloud? Oh, right, there is also a hybrid cloud
Answer: Actually, it is absolutely better to say which one is not generalized! Public clouds are generally cheaper and save trouble when maintaining them, without having to manage server hardware by themselves, but the data is shared with others; private clouds have relatively higher security, and many companies will choose this for fear of core data leakage, but the price is usually more expensive, and they have to find a special team to maintain them. If you want to balance it, then choose hybrid cloud! Put sensitive or critical data on private clouds where it is absolutely safe, put ordinary data or data that needs to be shared on public clouds, and choose the most suitable one according to your company's situation.
Let’s summarize the different migration paths: First, retain the original control logic and only migrate part of the data to the cloud . This method will have little interference to the operation of the current system, but the powerful functions of the cloud platform may not be able to be much; Second, after reconstructing the system business logic , this can better adapt to the cloud platform, and it will be very convenient to upgrade and expand in the future, but it will cost a lot of money, technology and time; Third, buy some cloud interfaces or gateway boxes that can connect with the old system and gradually replace the original old functional modules. This compatibility is quite good, but it is necessary to ensure that the interface and the old system can run steadily and reliably without conflicts! Some users also reported that the gateway is frequently offline in the third part, which is usually not related to the selection. Please insist on replacing the core components! Cloud migration is particularly friendly to small and medium-sized enterprises, especially cost-sensitive enterprises. Some cases even show that 17% of related operation and maintenance and labor costs can be saved in one year after the migration! Therefore, it is recommended that you plan a migration blueprint or roadmap as soon as possible. All the difficulties encountered during the migration process can be solved through the previous methods and experiences. Don’t be afraid to try it. After all, how can you know how much efficiency can be improved after the migration of your system? As long as the preliminary preparations are done in a solid manner and the migration is patiently followed step by step, most of the BAS migrations to the cloud platform can be successfully completed and used!
Leave a Reply