SAP, Hilscher and Pepperl+Fuchs
The digital twin
The basis of a successful Industry 4.0 strategy is a standardized data platform. All players involved in the value creation of a factory must be able to act on the basis of identical data. SAP, Hilscher and Pepperl+Fuchs are working on implementing such an approach.
Industry 4.0 marks a paradigm shift; the classic automation pyramid has had its day. Instead, networks of autonomously operating cyber-physical systems are emerging - intelligent, interconnected systems, components, modules and machines that control themselves. In addition, business and production-related IT processes are merging.
As part of this transformation, companies are faced with the task of seamlessly coordinating their processes and devices. A highly efficient process, data and monitoring cycle can only be created if the machines, modules and components of the various manufacturers are in harmony with each other.
The platform dilemma
Plant and component manufacturers in particular are currently developing their own Industry 4.0 platforms. For operators, this means that they receive their own IT platform from each provider. However, these are not compatible with each other, which prevents comprehensive monitoring of all systems and a standardized operating and maintenance process. An example: A manufacturer offers 'predictive maintenance' for one of its machines. However, the structures for this machine are mapped both in the manufacturer's service system and in the operator's maintenance system - and differently in each case. In addition, both deviate from the actual physical form of the system. This is fatal. After all, in order to exploit the added value of predictive maintenance, it must be possible to clearly identify patterns. In the event of a fault, it must also be clear which component is affected and how it can be replaced. This requires establishing correlations - between the time series and structural data, between the pattern and the spare part. Identical data is therefore required in the operator's maintenance system and in the manufacturer's service system.
Top premise: Standardize
All participants in the value chain require the same data in their various production-related IT systems - the plant operator for its maintenance, the manufacturer for its service, the supplier for its components and the service provider for installations, maintenance and repairs. The biggest challenges arise in maintenance and at the automation level.
Problem area maintenance: Manufacturers still usually maintain their systems manually, and they are often not linked to each other. For example, if a service technician wants to replace a component and does not have the right spare part with him, he often replaces it with another component with the corresponding function. The change is not recorded in the system; the system and its digital image are no longer identical. This lack of transparency makes end-to-end Industry 4.0 processes more difficult.
Problem area automation: Device manufacturers are obliged to support a wide range of communication standards - depending on the regional location or industry, different serial fieldbuses and Ethernet-based real-time systems prevail. Certification is carried out by fieldbus organizations. This can pose problems, for example if evaluations are based on subjective judgments or criteria that are not clearly defined. In fact, the spectrum ranges from certification regulations that are rather remote from practice to plug tests that are used to check interoperability in production-related operations. The influence of the relevant control system manufacturers through their technical characteristics and competitive positioning also has a strong impact on the communication systems.
In addition, different standards have to be taken into account when designing components and therefore also different performance data and functionalities. Depending on the standard, the display of device diagnostics varies enormously. This delays maintenance and therefore has a direct impact on the overall effectiveness of the system.
Ethernet communication is a matter of course when commissioning new systems. However, existing fieldbuses must be taken into account in the company-wide rollout of Industrial Internet of Things (IIoT) and Industry 4.0 concepts. And for the foreseeable future, the majority of these will still be based on serial communication. The costs of configuring, servicing and maintaining field devices such as sensors or actuators are largely determined by the engineering tools available for this purpose. Because the relevant standards have so far been defined by the control system manufacturer, the presentation and description of the components in the respective tools differ. In addition, device or component manufacturers cannot access their devices installed in the field themselves, which significantly restricts their ability to position their own software products.
Industry 4.0 also requires a rethink in terms of semantics: at all levels of the reference architecture, it is necessary for the companies involved in value creation to agree on the semantics to be used. The operational data from sensors and actuators must be supplemented with information and made available. In future, product development will therefore have to provide more than just the documentation available today at the level of engineering tools and PLM systems.
Simplified, open collaboration models are also needed throughout the entire IT/OT ecosystem. Only then can genuine cooperation develop from the product supplier or machine manufacturer through the integrator to the plant operator.
A solution approach
How can the aforementioned challenges faced by operators and manufacturers be overcome? One solution is emerging in the form of end-to-end value creation networks: SAP, for example, offers a value creation network for assets, i.e. for the assets on the store floor, in the form of the 'SAP Asset Intelligence Network'. The network links all business partners and their business processes and systems. Cooperation with Hilscher and Pepperl+Fuchs also makes it possible to connect the SAP Asset Intelligence Network with the automation level. This means that no complex, selective integrations are required.
In this case, networking between the store floor level and the SAP Asset Intelligence Network is handled by the 'Hilscher netIOT Edge Gateway'. Information can be transmitted bidirectionally between the sensor level and the virtual representation in the network via this gateway. The interconnected bus participants are automatically 'scanned' and their corresponding virtual twins are generated or kept up to date. In addition, each device can be controlled from the network during operation and supplied with configuration or other data.
New paradigm in manufacturing
Business and automation levels are increasingly converging. The SAP Asset Intelligence Network acts as a data hub. But even though both levels share a common network, they still have different requirements. Real-time data from the store floor must be further consolidated at the sensor and edge gateway level in order to be usable for today's business processes.
The role of the CPS
Cyber-physical systems (CPS) will change the classic automation pyramid in the future. CPS-based automation is emerging, supported by intelligent components and devices at sensor level. What exactly is a cyber-physical system? It is a machine or system that links its aggregated store floor data to the assigned business processes within a service-oriented architecture using domain-specific semantics.
Within such an IP-capable, networked architecture, the sensor system as an Industry 4.0 component can serve both synchronous and asynchronous services via a physical interface. Support for asynchronous services - such as diagnostics and parameterization - is in turn an essential prerequisite for integrating a plant into the SAP Asset Intelligence Network.
End-to-end networking
Value creation begins with the design process at the plant manufacturer. A production plant is usually developed and operated using engineering and configuration tools.
The digital twin in the cloud: this is where the data technology threads of the production system will come together in the future.
© SAPIt is crucial that the digital twin accurately depicts the configuration of both parts - and not just the general model information. To achieve this, all relevant data must be recorded in the value creation process.
The responsible suppliers therefore enter all safety and function-relevant aspects of their components in the network - including specific properties and special features in the manufacturing process and quality inspection. The system manufacturer then links the component to the system. At the latest when the production of the plant is complete, the corresponding plant structures, the special features in the production process (e.g. test protocols) and the complete plant documentation (including plant-specific maintenance and servicing instructions) are published in the SAP Asset Intelligence Network.
Finally, the system is delivered and installed at the end customer's premises. It is important to record the actual installed structure.
The Herculean task: all data relevant to the value creation process of the plant must be recorded and kept up to date.
© SAPIf service providers are responsible for the installation, maintenance or repair of the system, they must also maintain the data accordingly.
The constantly updated digital twin in the SAP Asset Intelligence Network and the standardized structure enable operators and manufacturers to track every component of a system in detail. This allows weak points to be identified and production performance to be continuously improved. The prerequisite for this is that all relevant components of a plant are recorded. This does not mean every screw. But in any case, all components that are safety-critical and therefore relevant for monitoring.
In order for components to be recorded, it is essential that they are clearly identified.
The administration shells of the RAMI model of the Industry 4.0 platform play a key role in the digital twin model.
© SAPThis is the only way to clearly assign data and components to each other. Identification can take place either through active communication with the component itself or passively by scanning barcodes or RFID tags attached to the components. During the installation of a system, the Edge Gateway identifies all relevant components and stores them with the associated description data in the SAP Asset Intelligence Network. This means that the components can also be clearly assigned during subsequent replacement processes and the digital twin of the system always remains up-to-date.
The Edge Gateway is then responsible for synchronizing the electronic components actually used and the entire structure with their digital twin. This corresponds to the approach of the reference architecture for Industry 4.0 (RAMI 4.0). This architecture includes the Industry 4.0 component, which provides a standardized model for the description of devices and components. Creating this component corresponds to storing the virtual entity in the SAP Asset Intelligence Network.
The advantages of the approach
The integrated solution approach leads to higher availability of the production system. Spare parts can be procured more quickly. Because their respective structure and geometry are available, they can also be repaired more quickly. The bottom line is that there are fewer unplanned downtimes. For replacement and repair, the SAP Asset Intelligence Network makes it possible, among other things, to download the firmware that is currently required. In addition, manual entry of changes to the system is almost completely eliminated. This reduces costs.
How can the automation system be technically connected to such a network? As a bus participant (slave), the Edge Gateway evaluates the communication of the real-time network and thus determines the current topology. As each participant logs on with its own ID, the type and instance of the component can be determined in the network or - if not yet available - the instance can be created. The type information and the instances of the components and machines must be registered in the network. The type or model information comes from specific backend areas, such as engineering tools, PLM or CRM systems. Depending on the individual release processes in product development, this data becomes the type information, which then serves as the basis for generating the respective instance models in the network.
The voluntary exchange of data is crucial to the success of the concept. Ultimately, the operating data belongs to the operators who generate the data. That is why they also decide what information the manufacturers are allowed to see. In order to give them an incentive to release the data, manufacturers must provide their customers with real added value and corresponding services based on this data. It is already possible to implement the technology on the basis of existing standards. The Industry 4.0 platform is the prerequisite for semantic standards and protocols that enable plants to be mapped virtually in the SAP Asset Intelligence Network in an open architecture.
Authors:
Timothy Kaufmann works in Business Development 'Internet of Things' at SAP Germany;
Armin Pühringer is Business Development Manager at Hilscher;
Benedikt Rauscher is Development Group Manager Industry 4.0/Industrial Internet Solutions in the Factory Automation division at Pepperl+Fuchs.
















