基于OPC UA Part 100的设备和更新管理.pdf

1、OPC Day International 2024June 17th 21st,2024Dr.Andreas WrgerTechnology Manager at Phoenix Contact Electronics GmbHOPC Day International 2024June 17th 21st,2024MotivationPLCnext EcosystemSoftware Update Specification within the DI-StandardConcrete realization of the Device Update Model Update Proces

2、s within the realizationConcrete Device and Update Management solutionDevice and Update Management architecture User Interface of the solutionCurrent boundaries regarding vendor independenceSummary and benefitsOPC Day International 2024June 17th 21st,2024When developing a new automation platform and

3、 ecosystem,security was identified as a fundamental future market requirement.IEC 62443 had to be fulfilled using a secure and future proof update method and a common interface.Today,firmware and security updates are usually made available on the product website.A manual and fragmented approach on s

4、ite with multiple tools and insecure methods was not only recognized as a security risk,but above all as non-functional in terms of efficiency and system availability.All connected devices need to be centrally monitored,managed and updated!OPC Day International 2024June 17th 21st,2024The PLCnext Eco

5、system includesthe PLCnext Control Hardware,the extensive runtime system,the PLCnext Store concept for easy provisioning,distribution and purchasing of software and the PLCnext Community.OPC Day International 2024June 17th 21st,2024OPC UA is represented in the PLCnext Ecosystem as integrated client

6、in the runtime,integrated PubSub in the runtime,integrated server in the runtime and Various documentation,sample code and open source tools.The structure of the address space of the server is not only vendor specific,but the OPC UA specification Part 100:Devices(DI)has been adopted here.This enable