1.- to Improve, You Have to Measure.<\/strong><\/h4>\nAlthough highly repeated, it is no less true. If you do not know the facility that you intend to improve, you will not know how. This implies not only at the level of sensors or similar, but that any new system or subsystem that is implemented \u2013 automatic doors, presence control, etc. \u2013 data must be able to be acquired<\/strong> from it in order to cross it with what is considered appropriate, even if it is not clear whether it will be needed or not. No more isolated or closed systems. <\/p>\n2.- Upload the Information, Download the Intelligence.<\/strong><\/h4>\nAn facility manager<\/strong> should not be blinded by the benefits of information in the ‘Cloud’. Obviously, uploading the information to the repositories \u2013 in the cloud or not \u2013 is necessary to be able to integrate it and exploit it to extract the value, however, that does not imply that the real world only serves to channel the information upstream. To avoid losses of local control, critical points or security problems \u2013 among others -, it is always advisable that the automatic intelligence is as close to the field as possible<\/strong>. This entails the use of controllers for infrastructures \u2013 called RTUs -, which collect the field information, contextualize it, filter it, concentrate it and communicate it in an optimal way. In this way, control at a low level is ensured. The higher systems what they should do is parameterize the RTUs<\/strong>, that is, indicate action schedules, priorities or manual orders, for example. The decision-making in the usual operation is decided by the programming of the RTU. ![\"digitalization](\"https:\/\/becolve.com\/wp-content\/uploads\/2023\/04\/smart-facilitie.jpg\")
<\/p>\n3.- Expand your Network of Partners.<\/strong><\/h4>\nNew fields of knowledge require new experts. Classic construction companies are not yet used to working in the digital environment,<\/strong> on the contrary, the environment from industrial and infrastructure automation has been carrying out projects of this type for years. There is no supplier that is the greatest expert in the entire necessary value chain \u2013 technologies, execution or maintenance -. Even so, unless you want to live with a justified risk, you should always try:<\/strong> <\/p>\n\n- Differentiate the technology provider from the provider of the execution and\/or maintenance service of the project<\/strong>. In this way, you avoid depending on a single company with which, if you want to change it, there would be great exit barriers. <\/li>\n
- Can easily interoperate with the rest of the systems of the installation<\/strong>, or in other words, be open and use standards at all levels.<\/li>\n
- You have to assess the future risks of the project<\/strong>, this implies not only dangers related to cybersecurity, but also to the scalability or ease of updating the product\/solution.<\/li>\n
- Avoid custom systems<\/strong>. Although they are very suggestive solutions at first, their very nature implies that any new implementation or new functionality that is intended to be added requires a specific development for it, with the risks and delays that this entails. Having a generalist solution, but with flexibility and adaptation, allows you to avoid this problem without losing personalization of the solution. <\/li>\n<\/ul>\n
4.- Work Teams Must also Evolve.<\/strong><\/h4>\nThe evolution of technology has not only made it more powerful, it has also made it more accessible. Currently there are multiple ways to provide field teams with tools that interact with the control or monitoring systems<\/strong> deployed, either through mobile devices or fixed touch screens, for example. This will mean that many manual control functions necessary<\/strong> in the day to day that needed to involve engineering, can also be carried out by maintenance or field operations teams. You should always opt for technology with high capabilities, but with access capacity for the personnel that will be deployed by the facility. <\/p>\n5.- the Criterion is the Great Value<\/strong><\/h4>\n
2.- Upload the Information, Download the Intelligence.<\/strong><\/h4>\nAn facility manager<\/strong> should not be blinded by the benefits of information in the ‘Cloud’. Obviously, uploading the information to the repositories \u2013 in the cloud or not \u2013 is necessary to be able to integrate it and exploit it to extract the value, however, that does not imply that the real world only serves to channel the information upstream. To avoid losses of local control, critical points or security problems \u2013 among others -, it is always advisable that the automatic intelligence is as close to the field as possible<\/strong>. This entails the use of controllers for infrastructures \u2013 called RTUs -, which collect the field information, contextualize it, filter it, concentrate it and communicate it in an optimal way. In this way, control at a low level is ensured. The higher systems what they should do is parameterize the RTUs<\/strong>, that is, indicate action schedules, priorities or manual orders, for example. The decision-making in the usual operation is decided by the programming of the RTU. <\/p>\n3.- Expand your Network of Partners.<\/strong><\/h4>\nNew fields of knowledge require new experts. Classic construction companies are not yet used to working in the digital environment,<\/strong> on the contrary, the environment from industrial and infrastructure automation has been carrying out projects of this type for years. There is no supplier that is the greatest expert in the entire necessary value chain \u2013 technologies, execution or maintenance -. Even so, unless you want to live with a justified risk, you should always try:<\/strong> <\/p>\n\n- Differentiate the technology provider from the provider of the execution and\/or maintenance service of the project<\/strong>. In this way, you avoid depending on a single company with which, if you want to change it, there would be great exit barriers. <\/li>\n
- Can easily interoperate with the rest of the systems of the installation<\/strong>, or in other words, be open and use standards at all levels.<\/li>\n
- You have to assess the future risks of the project<\/strong>, this implies not only dangers related to cybersecurity, but also to the scalability or ease of updating the product\/solution.<\/li>\n
- Avoid custom systems<\/strong>. Although they are very suggestive solutions at first, their very nature implies that any new implementation or new functionality that is intended to be added requires a specific development for it, with the risks and delays that this entails. Having a generalist solution, but with flexibility and adaptation, allows you to avoid this problem without losing personalization of the solution. <\/li>\n<\/ul>\n
4.- Work Teams Must also Evolve.<\/strong><\/h4>\nThe evolution of technology has not only made it more powerful, it has also made it more accessible. Currently there are multiple ways to provide field teams with tools that interact with the control or monitoring systems<\/strong> deployed, either through mobile devices or fixed touch screens, for example. This will mean that many manual control functions necessary<\/strong> in the day to day that needed to involve engineering, can also be carried out by maintenance or field operations teams. You should always opt for technology with high capabilities, but with access capacity for the personnel that will be deployed by the facility. <\/p>\n5.- the Criterion is the Great Value<\/strong><\/h4>\n
<\/p>\n3.- Expand your Network of Partners.<\/strong><\/h4>\nNew fields of knowledge require new experts. Classic construction companies are not yet used to working in the digital environment,<\/strong> on the contrary, the environment from industrial and infrastructure automation has been carrying out projects of this type for years. There is no supplier that is the greatest expert in the entire necessary value chain \u2013 technologies, execution or maintenance -. Even so, unless you want to live with a justified risk, you should always try:<\/strong> <\/p>\n\n- Differentiate the technology provider from the provider of the execution and\/or maintenance service of the project<\/strong>. In this way, you avoid depending on a single company with which, if you want to change it, there would be great exit barriers. <\/li>\n
- Can easily interoperate with the rest of the systems of the installation<\/strong>, or in other words, be open and use standards at all levels.<\/li>\n
- You have to assess the future risks of the project<\/strong>, this implies not only dangers related to cybersecurity, but also to the scalability or ease of updating the product\/solution.<\/li>\n
- Avoid custom systems<\/strong>. Although they are very suggestive solutions at first, their very nature implies that any new implementation or new functionality that is intended to be added requires a specific development for it, with the risks and delays that this entails. Having a generalist solution, but with flexibility and adaptation, allows you to avoid this problem without losing personalization of the solution. <\/li>\n<\/ul>\n
4.- Work Teams Must also Evolve.<\/strong><\/h4>\nThe evolution of technology has not only made it more powerful, it has also made it more accessible. Currently there are multiple ways to provide field teams with tools that interact with the control or monitoring systems<\/strong> deployed, either through mobile devices or fixed touch screens, for example. This will mean that many manual control functions necessary<\/strong> in the day to day that needed to involve engineering, can also be carried out by maintenance or field operations teams. You should always opt for technology with high capabilities, but with access capacity for the personnel that will be deployed by the facility. <\/p>\n5.- the Criterion is the Great Value<\/strong><\/h4>\n
- \n
- Differentiate the technology provider from the provider of the execution and\/or maintenance service of the project<\/strong>. In this way, you avoid depending on a single company with which, if you want to change it, there would be great exit barriers. <\/li>\n
- Can easily interoperate with the rest of the systems of the installation<\/strong>, or in other words, be open and use standards at all levels.<\/li>\n
- You have to assess the future risks of the project<\/strong>, this implies not only dangers related to cybersecurity, but also to the scalability or ease of updating the product\/solution.<\/li>\n
- Avoid custom systems<\/strong>. Although they are very suggestive solutions at first, their very nature implies that any new implementation or new functionality that is intended to be added requires a specific development for it, with the risks and delays that this entails. Having a generalist solution, but with flexibility and adaptation, allows you to avoid this problem without losing personalization of the solution. <\/li>\n<\/ul>\n
4.- Work Teams Must also Evolve.<\/strong><\/h4>\n
The evolution of technology has not only made it more powerful, it has also made it more accessible. Currently there are multiple ways to provide field teams with tools that interact with the control or monitoring systems<\/strong> deployed, either through mobile devices or fixed touch screens, for example. This will mean that many manual control functions necessary<\/strong> in the day to day that needed to involve engineering, can also be carried out by maintenance or field operations teams. You should always opt for technology with high capabilities, but with access capacity for the personnel that will be deployed by the facility. <\/p>\n
5.- the Criterion is the Great Value<\/strong><\/h4>\n
- Can easily interoperate with the rest of the systems of the installation<\/strong>, or in other words, be open and use standards at all levels.<\/li>\n