Requirements for Testing and Validating the Industrial Internet of Things VVIoT RUI PINTO Västerås – Sweden 09 April 2018
Outline • Advance Manufacturing Systems • Industrial Internet of Things • Five Layer IoT Architecture • Cyber-Physical Systems • CPPS Validation • Requirements • Testing • Challenges • Use Case Scenario • Conclusion & Future Work 2
Industry 4.0 ADVANCE MANUFACTURING SYSTEMS 3
Industry 4.0 Technology: ► Digital networking production facilities ► Fast pace of technological change and innovative technologies Customers: ► Customised solutions ► Wide diversity of customers and markets ► New services People: ► Demographic development ► Training and qualifications ► Interaction between human beings and technology 4
Advanced Manufacturing Systems Digitisation and networking ü Vertical integration (in a factory) ► Vertical integration of hierarchical subsystems leads to smarter factories ► Supports horizontal integration through value Reconfiguration� • � Lot� size� 1� • � Apps� • � Constant� change networks Ë Horizontal integration ► End-to-end digital integration of engineering. ► Based on this global collaboration network, the consumers, design activities, manufacturing, and logistics can interact above the cloud Value� chain� • � Life� cycle� costs� • � Customized� products 5
Advanced Manufacturing Systems 6
IIoT CYBER-PHYSICAL PRODUCTION SYSTEMS 7
Five Layer IoT Architecture 8
Cyber-Physical Systems 9
CPPS Validation REQUIREMENTS FOR CPPS TESTING 10
CPPS Testing Requirements Security & Timing & Scalability Reliability Privacy Determinism Safety Recovery Interoperability Reconfigurability 11
1. Scalability a) Increase number of network nodes, i.e. , number i. Associated latency. of physical devices to monitor. ii. Cost of acquiring devices and upgrading more b) Increase available data, i.e. , increase loads of resources. traffic volume, by adding more sensors. iii. Constrained data processing methods. c) Increase Cloud data services availability, such as storage, data analytics, user interface, etc. 12
2. Reliability a) Long term execution of the CPS. i. Relationship between anomaly and corresponding generated failures. b) Anomaly injection to generate failures in the physical equipment, network infrastructure or ii. Difficulty to implement code verification Cloud platform. methods in such complex systems, in order to identify faults, anomalies or software bugs. c) Submit CPS components to extreme environment conditions, such as temperature, humidity, air quality, etc. d) Overall counting of received/sent packages that are transferred using the network infrastructure. 13
3. Security & Privacy a) Cyber attack injection, which will affect the i. Unavailability to inject zero-day attacks, since it integrity of the information and devices. is impossible to simulate unknown attacks. b) Stealing sensitive data. ii. Simulate the behaviour of known attacks, such as physical attacks, DoS, Sibling attacks, c) Security resources, such as anti-virus, firewalls malware, etc. and cryptographic systems, are up and running. iii. Lack of expertise in cyber security methods, specially the group of methods that are suited to be used in CPS. 14
4. Timing & Determinism a) Guarantee cycle time of industrial process, i.e. , i. Identify which CPS component introduces delay guarantee that the implementation of CPS to the industrial process. doesn´t jeopardize product quality and process ii. Evaluate environmental impact over the process, parameters. i.e. , understand if delay is caused by external b) Test equipment process with varying parameters, uncontrollable factors or by the CPS itself. in order to identify product quality degradation. 15
5. Safety a) Simulation of safety process parameters, both in i. Knowing the accident’s cause, i.e. , identifying if controlled and relevant environment. it was caused by human or machine error. b) Counting number of physical accidents in the ii. Reliable safety process parameters simulation shop-floor, i.e. , events that caused harm to while in simulated and controlled environment. human operators. iii. Availability of relevant environment to test, i.e. , shop-floor cell for introducing failures and accidents. 16
6. Recovery a) Evaluate continuous operation of the system i. Identify the damage level that prevents system’s when some of its parts are shut-down, i.e. , recovery and partial operation. system compensate functionalities of ii. Identify what is the previous state of the system. compromised components. iii. Identify the acceptable time of rebooting. b) Maintain previous state after rebooting, both individual node or global system. c) Analyse time of reboot. 17
7. Interoperability a) Send messages with non matching semantics or i. Communication API with legacy entities does undefined ontology between different nodes or not exists. modules in the same node. ii. Non compatibility between existing APIs or b) Integration with 3rd party platforms (legacy when communication protocols are not the entities). same. 18
8. Reconfigurability a) Analyse time of reconfiguration, i.e. , duration of i. Verify success reconfiguration in complex altering the network topology. system. b) Verify system reconfiguration when changing ii. Identify acceptable time of reconfiguration. communication routing between nodes. c) Verify system reconfiguration when a node is added. 19
Cobots USE CASE SCENARIO 20
Kinect Sensor Robot Manipulator Screw’s Pool BITalino Board Area Box 1 Area Box 3 Area Box 2 21
Testing Collaborative CPPS Scalability Reliability Security & Privacy Timing & Determinism • Add biometric sensors. • Hamper BITalino data (increase • Break into network gateway • Command execution by robot is TEMP and HUM levels) & firewall. within acceptable time. • Add new data analytic services. Kinect’s performance (increase • Still biometric sensor data. • Evaluate process performance LUM levels). with several stress/fatigue • Corrupt messages sent to • Introduce Random faults: combinations. robot. unplug sensor power and send malformed messages. • Count message drop in network Safety Recovery Interoperability Reconfigurability • Vary BITalino parameters for • Forcing reboot of sensors and • Validate success • Change network topology, from board overeating or battery Cloud. communication while star to peer-to-peer. explosion. integrating with legacy ERP. • Evaluate if reboot is within • Evaluate network self- • Overflow the robot with acceptable time and previous • Send unexpected messages to organization when adding new actuation commands. state is maintained. Cloud or robot. sensors. 22
Wrap-Up Up CONCLUSION & FUTURE WORK 23
Conclusions & Future Work i. Growing usage of IIoT platforms and CPPS i. Implement a framework for automatic CPPS demands requirement validation and testing. test. ii. Trial and error techniques are the primary ii. Implement and test the collaborative CPPS debugging methods by CPS developers. presented in a industrial relevant scenario. iii. Simulators often fail to represent correctly process parameters. iv. This work proposes 8 CPPS requirements, which are fundamental for the correct operation of the CPPS. v. Most of the requirements involve end-to-end testing regarding the CPPS architecture. 24
Thanks! Any questions? You can find me at: rpinto@fe.up.pt 25
Recommend
More recommend
