# Six-Gear Roadmap towards the Smart Factory
## 5 The Six-Gear Roadmap
### Gear 3: Integration
There are number of key challenges associated with the integration stage. They include: (i) interoperability (breaking down the silos in the factory floor machines and equipment's that speak different languages depending on the communication protocols set by the vendors); (ii) data security (privacy issues with external sources and third parties in the horizontal integration as it requires data to be kept secured and accessed on a need to know basis); (iii) scalability (easily scaling the IT infrastructure by shifting IT systems operation to the cloud when data volume and velocity significantly increase with time); and (iv) adopting cost-effective IT applications (with strong orchestration capability to handle the integration complexity as well as providing end-to-end visibility with robust tools for data analytics to be performed) [38; 70; 76]. The IT technology market is already providing solutions to overcome the complexities of IT and OT integration to solve the challenges of interoperability (using open and multiple standards and protocols for communication), data security (using best practice CS standards and protocols) and scalability (via cloud ready solution) [54; 62; 74; 75; 76]. Table 15 in the Appendix A shows a list of leading Industry 4.0 ready IT platforms used in the manufacturing industry that use best practices connectivity and integration architecture that combine elements of IIoT and MOM/MES. These platforms do not completely replace or rebuild long established systems but acts as a new layer to the infrastructure orchestrating the new way of Industry 4.0 in smart manufacturing. This involves sourcing data from anywhere with minimal connectivity and integration costs together with having analytical capabilities to deliver insights via digital dashboards that can be accessed from anywhere including mobile devices, augmented and virtual reality displays. Manufacturing companies should carefully consider when implementing an IIoT system whether to buy off-the-shelf solutions or build an in-house solution taking into account the skills needed to build the technology stack, the scalable capability of solution, the availability of resources, technical skills and time [4; 77]. Industrial research reports find that most successful IIoT projects use off-the-shelf solution as the basis of their operation can get a quick ROI on the technology implementation [4; 77; 74]. A strategy should be in place for choosing an IIoT solution to suite the company's appetite. Some of the considerations include the additional capability of the platform, the additional IT infrastructure and hardware needed, the cost of using the platform, the customization flexibility, the technical skills required to use and manage the platform and the ability to scale in the future. IIoT platforms with built-in MOM/MES applications are a viable option. They are capable to seamlessly integrate with enterprise and industrial automation applications [73] and are accompanied with the elements of the IIoT stack (e.g., analytics tools, IIoT gateways connectivity, cloud scalability) [8]. Case studies in [78; 79] shows examples of manufacturers implementation of such option. Other option combines industrial code-less IT systemswith built-in software bridges, modules and communication protocols that are capable of connecting and integrating data across the manufacturing operation layers [62]. Examples of such IT systems are OPC Router [80] and Keyserver [81]. Another option is to adopt a full-fledged IIoT platform to seamlessly connect and integrate all layers of the manufacturing operation, enhanced with additional manufacturing operation apps [68]. Case studies in [82; 83] shows manufacturers implementation of such option. Embracing an ecosystem of solutions that work in harmony enable a successful system level integration [74]. All three strategies have the potential to combine data from different manufacturing operation levels enabling capabilities to move to the next stages of the roadmap.