This reality means that any new project to be implemented must have a part of the scope that covers the interconnection between the two or more systems involved.<\/strong> Here begins the problem.<\/p>\n Any end-user or integrator who has faced this knows that achieving information exchange between two systems<\/strong> without embedding a driver developed by the manufacturer will require, in the best of cases, hours of in-house development and specific resources for it. A typical case may be how to communicate a BI system with production data<\/strong>. For this, it will be necessary to set up a development that saves the contextualized data<\/strong> of the production in an intermediate database (typically in a separate VM) where the BI will consult through specific queries. And this is the simplest case. <\/p>\n In summary, there is a real problem<\/strong> where, to achieve the interdependence of systems with a fluid exchange of information, a large number of development hours by experts in the field is needed.<\/p>\n At Logitek, in recent months we have encountered three manufacturers of machinery and devices with the same problem.<\/strong> They have complemented their offer with a solution for the acquisition and study of the data generated by their own product, and although this software solution was technically very complete, they have not finished deploying it at the rate that was considered, seeing the potential it had. The reason? This solution was closed, and integrating it with the other solutions used by its client required a development effort that was too costly and difficult to maintain. <\/p>\n![\"industrial](\"https:\/\/becolve.com\/wp-content\/uploads\/2023\/04\/interdependencia.jpg\")
<\/p>\n