The document discusses key considerations for designing reliable automation systems for the process industry. It emphasizes the importance of minimizing downtime through fault-tolerant design, including: restricting the effect of failures, enabling rapid fault detection and repair, using redundancy when appropriate, and segmenting networks. The total cost of a system over its lifetime, including maintenance and lost production from downtime, far exceeds initial procurement costs. Certified training in system design principles can help engineers optimize availability and maintainability.
This presentation examines the fundamental principles of good network design for process automation systems. The presentation will discuss the main factors that should be considered at the design stage of a project and how these can impact on the reliability and availability of the plant. Practical examples will show how facilities for health checking, fault-finding and maintenance can have a crucial impact. The presentation will also examine how properly thought out network monitoring and engineering access facilities can drastically affect plant up-time and thus profitability.
This presentation looks at the tools and techniques that are available for engineering activities such as health checking and fault finding. In particular the presentation will explore some of the devices that are now available for automated network condition monitoring. These devices can provide 24/7 remote monitoring of your networks to provide rapid reporting of network problems and provide indication of performance degradation and give pre-warning of impending failure. The presentation will include a practical demonstration of some of the available tools.
The number of installed PROFINET nodes is growing and growing. In this presentation we will discuss the use of PROFINET in process industry applications and compare its use to PROFIBUS which is a strong performer in the process industry.
PROFIBUS is a very reliable and cost effective technology.
It is common to find extensive installations comprising thousands of PROFIBUS devices operating on complex networks which are connected together via industrial Ethernet.
The reliable operation of these networks is essential to maintaining plant productivity.
So, what can go wrong? And how do you find out? And avoid recurrance?
It is widely accepted that the most important decisions are made at design stage of a project. This presentation examines the fundamental principles of good network design for PROFINET systems, although many of the ideas are applicable to PROFIBUS and other networking systems. The presentation will discuss the main factors that must be considered at the design stage of an automation system. Practical examples will show how facilities for health checking, fault-finding and maintenance can have a crucial impact on plant availability. The presentation will also examine how properly thought out network monitoring and redundancy can drastically affect plant up-time and thus profitability.
This presentation will discuss the basics of how we should approach a safety-related control project and discuss how networking supports the implementation of the safety system using PROFIsafe as an example of a black channel safety-related control solution.
The Process Industry has quite different requirements from
Factory Automation.
Generally, we are dealing devices that are exposed to the
environment.
Requires higher IP ratings.
Hazardous environments (explosive atmospheres) are common.
Requires Intrinsic Safety.
We are often dealing with extensive systems with thousands of
devices.
Requires high availability.
High speed operation is not normally required.
Production cannot normally be stopped, so engineering
activities such as maintenance and device replacement must
have minimum impact.
PROFIBUS Characteristics
PROFIBUS is a bi-directional digital communication network for field devices.
Multi-drop network, many devices on one cable
communicates not only process values but also diagnostics, device parameters, calibration and performance data etc.
The data can represent analogue values and/or discrete (on/off) values.
But all data is digitally encoded and transmitted.
PROFIBUS is extensively specified.
All PROFIBUS devices are interoperable.
• Multi vendor systems are easily constructed.
• Best of breed devices can be selected.
• Common set of tools for maintenance and engineering.
This presentation examines the fundamental principles of good network design for process automation systems. The presentation will discuss the main factors that should be considered at the design stage of a project and how these can impact on the reliability and availability of the plant. Practical examples will show how facilities for health checking, fault-finding and maintenance can have a crucial impact. The presentation will also examine how properly thought out network monitoring and engineering access facilities can drastically affect plant up-time and thus profitability.
This presentation looks at the tools and techniques that are available for engineering activities such as health checking and fault finding. In particular the presentation will explore some of the devices that are now available for automated network condition monitoring. These devices can provide 24/7 remote monitoring of your networks to provide rapid reporting of network problems and provide indication of performance degradation and give pre-warning of impending failure. The presentation will include a practical demonstration of some of the available tools.
The number of installed PROFINET nodes is growing and growing. In this presentation we will discuss the use of PROFINET in process industry applications and compare its use to PROFIBUS which is a strong performer in the process industry.
PROFIBUS is a very reliable and cost effective technology.
It is common to find extensive installations comprising thousands of PROFIBUS devices operating on complex networks which are connected together via industrial Ethernet.
The reliable operation of these networks is essential to maintaining plant productivity.
So, what can go wrong? And how do you find out? And avoid recurrance?
It is widely accepted that the most important decisions are made at design stage of a project. This presentation examines the fundamental principles of good network design for PROFINET systems, although many of the ideas are applicable to PROFIBUS and other networking systems. The presentation will discuss the main factors that must be considered at the design stage of an automation system. Practical examples will show how facilities for health checking, fault-finding and maintenance can have a crucial impact on plant availability. The presentation will also examine how properly thought out network monitoring and redundancy can drastically affect plant up-time and thus profitability.
This presentation will discuss the basics of how we should approach a safety-related control project and discuss how networking supports the implementation of the safety system using PROFIsafe as an example of a black channel safety-related control solution.
The Process Industry has quite different requirements from
Factory Automation.
Generally, we are dealing devices that are exposed to the
environment.
Requires higher IP ratings.
Hazardous environments (explosive atmospheres) are common.
Requires Intrinsic Safety.
We are often dealing with extensive systems with thousands of
devices.
Requires high availability.
High speed operation is not normally required.
Production cannot normally be stopped, so engineering
activities such as maintenance and device replacement must
have minimum impact.
PROFIBUS Characteristics
PROFIBUS is a bi-directional digital communication network for field devices.
Multi-drop network, many devices on one cable
communicates not only process values but also diagnostics, device parameters, calibration and performance data etc.
The data can represent analogue values and/or discrete (on/off) values.
But all data is digitally encoded and transmitted.
PROFIBUS is extensively specified.
All PROFIBUS devices are interoperable.
• Multi vendor systems are easily constructed.
• Best of breed devices can be selected.
• Common set of tools for maintenance and engineering.
Most system designers and project managers look at the
project procurement, installation and deployment costs when
they price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, faultfinding
and health-checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
PROFIBUS is a very reliable and cost effective
technology.
It is common to find extensive installations
comprising thousands of PROFIBUS devices
operating on complex networks which are connected
together via industrial Ethernet.
The reliable operation of these networks is essential
to maintaining plant productivity.
So, what can go wrong?
The document discusses monitoring and preventative maintenance of PROFIBUS networks. It notes that wiring faults are the most common problem but intermittent faults can be difficult to diagnose. It recommends integrating health checking tools to permanently monitor network health and automatically report failures. New permanent monitoring tools allow 24/7 monitoring of PROFIBUS and PROFINET networks from a single connection point.
System designers and project managers look at the project
procurement, installation and deployment costs when they
price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, faultfinding and health-checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
PROFIBUS is a very reliable and cost effective
technology.
It is common to find extensive installations
comprising thousands of PROFIBUS devices
operating on complex networks which are connected
together via industrial Ethernet.
The reliable operation of these networks is essential
to maintaining plant productivity.
So, what can go wrong?
The document provides an agenda for a presentation on commissioning and maintaining PROFIBUS networks. The presentation covers PROFIBUS essentials, common faults, preparation for fault finding, tools needed, expected network quality, preventative maintenance, and steps for commissioning including using a test master to check connections and device configuration.
1) The document discusses device configuration tools and standards including EDDL, FDT, and FDI.
2) It provides a history of device configuration and the roadmap that led to cooperation between groups to develop a single common standard.
3) The goals of the cooperation were to develop a solution that is applicable to all device communication technologies, network topologies, and is compatible with existing device descriptions while becoming an international standard.
What do we mean by “Safety”
“The condition of being safe; freedom from danger, risk, or injury.”
In the UK (and Europe) this can cover many areas and industries, for example:
Supply of Machinery (Safety) Regulations
Electromagnetic Compatibility Regulations
Electrical Equipment (Safety) Regulations
Pressure Equipment Regulations
Simple Pressure Vessels (Safety) Regulations
Equipment and Protective Systems Intended for Use in Potentially Explosive Atmospheres
Regulations
Lifts Regulations
Medical Devices Regulations
Gas Appliances (Safety) Regulations
The document discusses monitoring the health of PROFIBUS networks. It states that wiring faults, interference, and power supply failures are the most common network problems. While PROFIBUS is robust, communication errors can be hidden until they reach a critical threshold. The document emphasizes the importance of system health checking to find non-critical and intermittent faults before they become issues. It presents several permanent monitoring tools that can provide 24/7 network monitoring.
This presentation will introduce the concept of profiles and in
particular the PA profile, which is mandatory for all PROFIBUS
PA devices.
The presentation will briefly explain the structure of the PA
profile and show the benefits that this can bring when working
with extensive and complex plants.
We will include a practical demonstration showing
manufacturer independent remote device access for device
which provides functions for commissioning, maintenance,
calibration and monitoring.
What do we mean by “Safety”?
“The condition of being safe; freedom from danger, risk, or injury.”
In the UK (and Europe) this can cover many areas and industries, for example:
Supply of Machinery (Safety) Regulations
Electromagnetic Compatibility Regulations
Electrical Equipment (Safety) Regulations
Pressure Equipment Regulations
Simple Pressure Vessels (Safety) Regulations
Equipment and Protective Systems Intended for Use in Potentially Explosive Atmospheres Regulations
Lifts Regulations
Medical Devices Regulations
Gas Appliances (Safety) Regulations
A short journey to explain the IoT The Internet of Things, IIoT The Industrial Internet of things, IND4.0 from IND1.0 and Big Data. How PROFINET is placed as the ideal Industrial Fieldbus to fulfil the above, how its implemented and why you should consider it. Some of the myths explained.
PROFIBUS is a very reliable and cost effective technology.
It is common to find extensive installations comprising thousands of PROFIBUS devices operating on complex networks which are connected together via industrial Ethernet.
The reliable operation of these networks is essential to maintaining plant productivity.
So, what can go wrong? And how do you find out? And avoid recurrance?
The modern world means that control systems are being integrated together within the plant with the aim of integrating everything into the MES and IT system. This step change is due to IIoT and Industry4.0 but does bring other considerations to the table. What should we think about in relation to network design and security?
Global Trends / Industry 4.0
How PROFINET provides increased flexibility, efficiency, and performance
Merging of automation and IT
OT Vs IT:
Location – Rough environment
Installation – Plant maintenance
Topology – Plant specific, varied
Availability – Network downtimes <300mS
Device density – Low, switches with few ports
Network monitoring – Part of plant monitoring
Design Summary:
§ Zoning and Security are essential
§ VLANs
§ Layer 3 switches
§ ACL
§ Bandwidth reservation
§ Network redundancy
§ Protection of safety-related systems
§ OT team & IT Team cooperation
PROFINET Security Concept:
§ Network Architecture – Security Zones
§ Trust Concept – within Zones
§ Perimeter Defence – Firewall/VPN
§ Provision of Confidentiality and Integrity
§ Transparent Integration of Firewalls
A practical session that allows attendees to get hands-on with real devices on a real network.
Featuring a DP+PA network consisting of two DP segments and a PA segment with monitoring devices from several leading manufacturers including Softing, Procentec and Pepperl+Fuchs, the network will also have a wireless switch into which a number of monitoring devices will connect and there will be several laptops with wireless comms spread around the room so that people can interact with the monitors.
The Workshop will start with a general introductory presentation on communication and peripheral faults, fault diagnosis and network monitoring. This will include coverage of permanent network monitoring devices and an explanation of the physical setup so people know what they are doing.
This document provides an overview of PROFINET, including:
- PROFINET uses Ethernet standards to provide industrial communications over an Ethernet network at speeds up to 100Mbit/s.
- PROFINET is compatible with PROFIBUS but is not simply PROFIBUS over Ethernet.
- PROFINET supports different update rates, priorities, and IT services for various applications on the same network.
- Commissioning and qualification of a PROFINET network involves testing the installation, topology, device identification, network loads, and more to ensure proper functioning.
Although PROFIBUS can provide robust, long lasting network reliability and resilience, special tools are recommended to check on the quality of each new installation and to help with the long term maintenance of the originally achieved levels of performance. In this talk we outline what can be expected of such tools, how and when they should be used and the important network performance indicators that can be checked. These tools are recommended for use during commissioning of new systems, before new system acceptance and on a regular basis thereafter in order to help ongoing reliability and successful operation. Collection and logging of comprehensive network performance reports from the test tool, at or soon after first system acceptance, can then provide an extremely valuable benchmark against which to compare all future measurements in the years ahead.
Facilities for health checking and fault finding on PROFIBUS
systems are essential.
Access points must be provided on every segment of every
network. (Piggy-back sockets).
Tools and accompanying training are essential.
Network layout should allow devices to be replaced without
shutting down the network or disturbing other devices on the
network.
Replacement of devices should, if possible, not require reconfiguration of the system.
Health checking should be carried out at regular intervals to
detect degradation of performance, deteriorating
communications and developing problems.
Although Factory Automation widely uses Industrial Ethernet as the main Fieldbus, in Process Automation plants PROFIBUS is still the number one communication system. Karsten will show, why this is not an issue, how users can benefit from PROFINET today and how PI keeps developing PROFINET to meet all needs and requirements of PA including a new Physical Layer (APL) for Ethernet in hazardous areas.
PROFIBUS - the world's most successful fieldbus:
easy, flexible, consistent
PROFINET - the leading Industrial Ethernet Standard:
open, versatile, safe
IO-Link - the new standard in the lower field level:
Universal, smart, easy
Most system designers and project managers look at the
project procurement, installation and deployment costs when
they price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, faultfinding
and health-checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
PROFIBUS is a very reliable and cost effective
technology.
It is common to find extensive installations
comprising thousands of PROFIBUS devices
operating on complex networks which are connected
together via industrial Ethernet.
The reliable operation of these networks is essential
to maintaining plant productivity.
So, what can go wrong?
The document discusses monitoring and preventative maintenance of PROFIBUS networks. It notes that wiring faults are the most common problem but intermittent faults can be difficult to diagnose. It recommends integrating health checking tools to permanently monitor network health and automatically report failures. New permanent monitoring tools allow 24/7 monitoring of PROFIBUS and PROFINET networks from a single connection point.
System designers and project managers look at the project
procurement, installation and deployment costs when they
price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, faultfinding and health-checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
PROFIBUS is a very reliable and cost effective
technology.
It is common to find extensive installations
comprising thousands of PROFIBUS devices
operating on complex networks which are connected
together via industrial Ethernet.
The reliable operation of these networks is essential
to maintaining plant productivity.
So, what can go wrong?
The document provides an agenda for a presentation on commissioning and maintaining PROFIBUS networks. The presentation covers PROFIBUS essentials, common faults, preparation for fault finding, tools needed, expected network quality, preventative maintenance, and steps for commissioning including using a test master to check connections and device configuration.
1) The document discusses device configuration tools and standards including EDDL, FDT, and FDI.
2) It provides a history of device configuration and the roadmap that led to cooperation between groups to develop a single common standard.
3) The goals of the cooperation were to develop a solution that is applicable to all device communication technologies, network topologies, and is compatible with existing device descriptions while becoming an international standard.
What do we mean by “Safety”
“The condition of being safe; freedom from danger, risk, or injury.”
In the UK (and Europe) this can cover many areas and industries, for example:
Supply of Machinery (Safety) Regulations
Electromagnetic Compatibility Regulations
Electrical Equipment (Safety) Regulations
Pressure Equipment Regulations
Simple Pressure Vessels (Safety) Regulations
Equipment and Protective Systems Intended for Use in Potentially Explosive Atmospheres
Regulations
Lifts Regulations
Medical Devices Regulations
Gas Appliances (Safety) Regulations
The document discusses monitoring the health of PROFIBUS networks. It states that wiring faults, interference, and power supply failures are the most common network problems. While PROFIBUS is robust, communication errors can be hidden until they reach a critical threshold. The document emphasizes the importance of system health checking to find non-critical and intermittent faults before they become issues. It presents several permanent monitoring tools that can provide 24/7 network monitoring.
This presentation will introduce the concept of profiles and in
particular the PA profile, which is mandatory for all PROFIBUS
PA devices.
The presentation will briefly explain the structure of the PA
profile and show the benefits that this can bring when working
with extensive and complex plants.
We will include a practical demonstration showing
manufacturer independent remote device access for device
which provides functions for commissioning, maintenance,
calibration and monitoring.
What do we mean by “Safety”?
“The condition of being safe; freedom from danger, risk, or injury.”
In the UK (and Europe) this can cover many areas and industries, for example:
Supply of Machinery (Safety) Regulations
Electromagnetic Compatibility Regulations
Electrical Equipment (Safety) Regulations
Pressure Equipment Regulations
Simple Pressure Vessels (Safety) Regulations
Equipment and Protective Systems Intended for Use in Potentially Explosive Atmospheres Regulations
Lifts Regulations
Medical Devices Regulations
Gas Appliances (Safety) Regulations
A short journey to explain the IoT The Internet of Things, IIoT The Industrial Internet of things, IND4.0 from IND1.0 and Big Data. How PROFINET is placed as the ideal Industrial Fieldbus to fulfil the above, how its implemented and why you should consider it. Some of the myths explained.
PROFIBUS is a very reliable and cost effective technology.
It is common to find extensive installations comprising thousands of PROFIBUS devices operating on complex networks which are connected together via industrial Ethernet.
The reliable operation of these networks is essential to maintaining plant productivity.
So, what can go wrong? And how do you find out? And avoid recurrance?
The modern world means that control systems are being integrated together within the plant with the aim of integrating everything into the MES and IT system. This step change is due to IIoT and Industry4.0 but does bring other considerations to the table. What should we think about in relation to network design and security?
Global Trends / Industry 4.0
How PROFINET provides increased flexibility, efficiency, and performance
Merging of automation and IT
OT Vs IT:
Location – Rough environment
Installation – Plant maintenance
Topology – Plant specific, varied
Availability – Network downtimes <300mS
Device density – Low, switches with few ports
Network monitoring – Part of plant monitoring
Design Summary:
§ Zoning and Security are essential
§ VLANs
§ Layer 3 switches
§ ACL
§ Bandwidth reservation
§ Network redundancy
§ Protection of safety-related systems
§ OT team & IT Team cooperation
PROFINET Security Concept:
§ Network Architecture – Security Zones
§ Trust Concept – within Zones
§ Perimeter Defence – Firewall/VPN
§ Provision of Confidentiality and Integrity
§ Transparent Integration of Firewalls
A practical session that allows attendees to get hands-on with real devices on a real network.
Featuring a DP+PA network consisting of two DP segments and a PA segment with monitoring devices from several leading manufacturers including Softing, Procentec and Pepperl+Fuchs, the network will also have a wireless switch into which a number of monitoring devices will connect and there will be several laptops with wireless comms spread around the room so that people can interact with the monitors.
The Workshop will start with a general introductory presentation on communication and peripheral faults, fault diagnosis and network monitoring. This will include coverage of permanent network monitoring devices and an explanation of the physical setup so people know what they are doing.
This document provides an overview of PROFINET, including:
- PROFINET uses Ethernet standards to provide industrial communications over an Ethernet network at speeds up to 100Mbit/s.
- PROFINET is compatible with PROFIBUS but is not simply PROFIBUS over Ethernet.
- PROFINET supports different update rates, priorities, and IT services for various applications on the same network.
- Commissioning and qualification of a PROFINET network involves testing the installation, topology, device identification, network loads, and more to ensure proper functioning.
Although PROFIBUS can provide robust, long lasting network reliability and resilience, special tools are recommended to check on the quality of each new installation and to help with the long term maintenance of the originally achieved levels of performance. In this talk we outline what can be expected of such tools, how and when they should be used and the important network performance indicators that can be checked. These tools are recommended for use during commissioning of new systems, before new system acceptance and on a regular basis thereafter in order to help ongoing reliability and successful operation. Collection and logging of comprehensive network performance reports from the test tool, at or soon after first system acceptance, can then provide an extremely valuable benchmark against which to compare all future measurements in the years ahead.
Facilities for health checking and fault finding on PROFIBUS
systems are essential.
Access points must be provided on every segment of every
network. (Piggy-back sockets).
Tools and accompanying training are essential.
Network layout should allow devices to be replaced without
shutting down the network or disturbing other devices on the
network.
Replacement of devices should, if possible, not require reconfiguration of the system.
Health checking should be carried out at regular intervals to
detect degradation of performance, deteriorating
communications and developing problems.
Although Factory Automation widely uses Industrial Ethernet as the main Fieldbus, in Process Automation plants PROFIBUS is still the number one communication system. Karsten will show, why this is not an issue, how users can benefit from PROFINET today and how PI keeps developing PROFINET to meet all needs and requirements of PA including a new Physical Layer (APL) for Ethernet in hazardous areas.
PROFIBUS - the world's most successful fieldbus:
easy, flexible, consistent
PROFINET - the leading Industrial Ethernet Standard:
open, versatile, safe
IO-Link - the new standard in the lower field level:
Universal, smart, easy
Recently, a new phenomenon has appeared during the search for the causes of network failures. It has been noted data communication issues are becoming more frequent in situations where conventional network analysers do not reveal any weak points.
It was the investigation of shield currents on industrial data communication lines that prompted the usual diagnostic approach to take a completely new turn. It soon became clear that the bus itself was in perfect condition, but was being affected by external influences that are generally referred to as “EMC interference“. Further extensive measurements, both in the bonding system and in the shielding connections of bus lines, revealed an association between high leakage currents (mostly of higher frequency) and bus failures.
This presentation will explain the theory behind the measurements, the tools used to perform them and will provide limits against which all industrial networks should be checked against.
With an installed base approaching 4 million nodes IO-Link is THE protocol for communication down to the sensor and actuator level. This presentation will be covering what a typical IO-Link solution consists of, how it interfaces to the control system and the benefits that can be derived from this increased level of communication with IO-Link devices. These include: easier handling of measurement signals, remote and automatic device parameterisation, smart sensor diagnostic functions, safety over IO-Link whilst also being an enabler for Industrial IoT and Industry 4.0 strategies.
PROFIBUS - the world's most successful fieldbus. Easy, flexible, consistent.
PROFINET - the leading Industrial Ethernet Standard. Open, versatile, safe.
IO-Link - the new standard in the lower field level. Universal, smart, easy.
Most system designers and project managers look at the
project procurement, installation and deployment costs when
they price a project.
However, the costs of an automation system spread over the
whole life cycle of the plant and should include costs of system
failures, maintenance, health-checking etc.
Perhaps most important is the cost in terms of loss of plant
function should faults develop during the lifetime of the plant.
Spending a little more at procurement time can repay many
times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
The document discusses the need for an accredited PROFIBUS System Design course. It notes that many errors found in networked control systems are due to poor design decisions made early on. While existing courses cover installation and maintenance, there is a need to train those who specify, plan and design such systems. The document outlines a proposed new Certified PROFIBUS System Design course that would cover topics like network planning, component selection, reliability measures, documentation standards, and design best practices. Feedback is requested on the course proposal.
Good quality PROFIBUS and PROFINET training has been widely available for installers, maintenance technicians and engineers for many years. Unfortunately, key decision makers – managers, system designers and system integrators are quite often less well trained than others who are involved in the engineering. Many of the mistakes that can be seen in installations are traceable to fundamental design decisions that were taken at the early stages of the project.
This presentation explores the key considerations in PROFIBUS and PROFINET system design. Aspects such as system performance and maintainability of different designs and layouts are examined together with overall project costs. The presentation will also try to shed some light on the often asked question should I use PROFIBUS or PROFINET?
Finally, an overview will be presented of proposed PROFIBUS and PROFINET System Design courses.
IRJET- An Efficient Hardware-Oriented Runtime Approach for Stack-Based Softwa...IRJET Journal
This document discusses an efficient hardware-oriented runtime approach for detecting stack-based buffer overflow attacks during program execution. The approach automatically archives and compares the original and modified information of static variables in the program to detect any changes from the compiler-generated object code. This is done transparently to programmers without requiring any source code modifications. By leveraging the hardware of the CPU pipeline, the approach can identify buffer overflows during runtime to prevent security vulnerabilities from being exploited. The approach aims to provide protections against runtime attacks while having low performance and memory overhead.
The Software Engineering Profession SWE311The Software Enginee.docxssusera34210
The Software Engineering Profession SWE311
The Software Engineering Profession SWE311-1503A-01 7/27/2015
Antoine Sims
Table of Contents
Project Outline 2
Overview 2
IT Infrastructure 3
Software Engineering Practices 4
Methodology 4
Software Engineering Standards 7
Standards 7
Software Engineering Communications 9
Communication 9
Software Engineering Ethics and Roles 12
TBD 12
Software Engineering Issues 13
TBD 13
References 14
Phase 3. Repurposed: “This task contains portions of material that were originally submitted during the phase 3 discussion board The Software Engineering Profession in SWE311 with Professor Tricic
Project Outline
Overview
Bungie.net is a company that serves as a community role for online gamers that have been around since 1996. Gamers continue to use the site as a place to gather information about news, events and technical information on upcoming games and projects. The primary function of the site is to serve as a community hub for anything that is Bungie Studios related. Any game or project that Bungie has is available for discussion through forums. Online gamers can also track there stats for games that they play. The site also serves as a means for Bungie to get feedback about gaming experience before issuing out updates to the latest gameplay updating.
“Bungie.net leverages the Microsoft .NET Framework running on Microsoft Windows 2003 and Microsoft SQL 2000 Servers to serve up over 3 million page views per day and accumulating over 300 GB of data a month of online game statistics from the almost 1 million online games played every day. Not only is Bungie.net built to scale, but its design and inventive features have not gone unnoticed, since it was rated as the "Most Innovative Design" by IGN Entertainment. The site also exceeds a 99 percent up-time ratio even through peak usage periods such as the week of the Halo 2 release. Clearly, the release of the Bungie.net site defines a new milestone in the era of online game play. This case study provides insight into this accomplishment” (Microsoft Corporation, 2005).
IT Infrastructure
Bungie has two IT department consists of two separate entities. One of those entities is an IT department that maintains the Bungie.net website and the other is its engineering department. The engineering department is the department where Bungie creates its software for the video game that they develop. In the IT Department or Operations there are several positions such as IT engineer, IT support/server specialist, and datacenter operations specialist. These people maintain the online gaming data and the website. They deal with the servers keeping them up and running. The Engineering Department has a host of position that incorporate it such as database engineers, infrastructure/platform engineers, mobile engineers, leads, online engineers, tools engineers, game server tools engineers, engine programmers, game service engineers, activities engineers, graphics pr ...
Peter Zimmerer - Evolve Design For Testability To The Next Level - EuroSTAR 2012TEST Huddle
EuroSTAR Software Testing Conference 2012 presentation on Evolve Design For Testability To The Next Level by Peter Zimmerer . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Software process methodologies and a comparative study of various modelsiaemedu
This document provides a summary of different software process methodologies including the waterfall model, iterative model, extreme programming (XP), ISO standards, CMMI, Six Sigma, formal methods, and agile model. It compares these methods and discusses where each is best applied based on factors like project type, risk, and industry. The waterfall model is described as the traditional sequential approach while agile methods embrace adaptive planning and iterative development.
Design for Testability: A Tutorial for Devs and TestersTechWell
Testability is the degree to which a system can be effectively and efficiently tested. This key software attribute indicates whether testing (and subsequent maintenance) will be easy and cheap—or difficult and expensive. In the worst case, a lack of testability means that some components of the system cannot be tested at all. Testability is not free; it must be explicitly designed into the system through adequate design for testability. Peter Zimmerer describes influencing factors (controllability, visibility, operability, stability, simplicity) and constraints (conflicting nonfunctional requirements, legacy code), and shares his experiences implementing and testing highly-testable software. Peter offers practical guidance on the key actions: (1) designing well-defined control and observation points in the architecture, and (2) specifying testability needs for test automation early. He shares creative and innovative approaches to overcome failures caused by deficiencies in testability. Peter presents a new, comprehensive strategy for testability design that can be implemented to gain the benefits in a cost-efficient manner.
Today, electronic work instructions soft-ware is instrumenta.docxedwardmarivel
Today, electronic work instructions soft-
ware is instrumental to the shop floor. And
market leaders are investing in the integra-
tion of electronic work instructions (EWIs)
with 3D visualization and simulation soft-
ware, so operators aren’t just following
along with instructions, they’re able to view
animations of each step and sometimes even
improve things right on the spot.
Here’s what you need to know about
the past, present, and future of electronic
work instructions in manufacturing opera-
tions management, as well as discuss eight
ways they’re transforming the shop floor.
From paper-based to next-generation
It’s vital that you have clear and
repeatable instructions for every manu-
facturing process. Traditionally, shop-
floor workers would hang laminated
pieces of paper on the wall with dia-
grams and explanations of each step.
The shortcomings of this are obvious,
particularly when an engineering change
order (ECO) was required and those
changes needed to be sent to engineer-
ing, revamped, sent back to manufactur-
ing, reprinted, relaminated, and so on. If
we’re talking about a global operation,
this becomes even more of a challenge.
The more complex something you’re
building is, generally the more com-
plex those instructions have to be, and
a paper-based approach can be limiting.
But computer technology on the shop
floor wasn’t always as easily accessible
and widespread as it is today.
Since document control software has
become widely adopted, however, EWIs
have made their way into the manufactur-
ing environment. EWIs have improved
the way supervisors and operators build
products, and the way they interact with
engineers and maintenance personnel.
The technology enables a centralized,
standardized, and automated document
management system, and can be found on
most modern manufacturing shop floors.
In addition to improving communica-
tion and collaboration on the shop floor,
streamlining EWIs mitigates many of the
traditional risks associated with changing
a work order. In the past, an engineering
change may have been ordered, but never
completed or at least never communi-
cated to the appropriate personnel once
completed. With automated workflows,
notifications can be triggered to ensure
the process is completed and the appro-
priate personnel are notified. Workflows
can also ensure that the right instructions
are being followed on time and in the
context of the manufacturing process.
As the use of simulation and 3D visual-
ization software becomes more prevalent,
moving from engineering onto the shop
floor, EWIs are becoming an even more
effective tool. By integrating EWIs with
this technology, an operator can watch each
step of a process played out via animations.
In some cases, operators and supervisors
are trained to actually make changes and
improvements to these processes in real
time rather than waiting for an ECO.
With the continuous advancement
of technology, ...
Here is an example operations list for a medical enteral pump system:
1. Power on pump
2. Navigate main menu
1. Set patient details
2. Set feeding program
1. Select feeding mode (continuous, intermittent)
2. Set feeding rate
3. Set feeding duration
3. Start/stop feeding
4. View feeding history
5. Adjust alarm settings
3. Acknowledge/silence alarms
4. Power off pump
This list was developed by walking through the menu structure and identifying the key operations a user could perform with the pump system. The numbering indicates sub-operations under main operations.
Most system designers and project managers look at the
project procurement, installation and deployment costs when
they price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, faultfinding
and health‐checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
The document discusses Effektives Consulting's performance engineering portfolio, which includes user experience and web performance management, cloud-based commerce recommendations, zero-touch deployments, and emerging augmented reality applications. It focuses on web performance management, covering infrastructure capacity planning, a two-stage performance testing approach using both on-premise and cloud-based resources, application profiling, and reporting.
Designing a data storage infrastructure for high availability requires the selection of the most reliable hardware components, coupled with intelligent storage services software to ensure continuous access to critical business data in the face of equipment and facility outages, as well as ongoing expansion and upgrades.
This paper outlines the design techniques employed to achieve enterprise-class high availability by combining the robust hardware and software in the Lenovo Storage S3200
storage array with synchronous mirroring and remote replication from the DataCore SANsymphony-V Software-defined Storage platform.
Best Practices for Microsoft-Based Plant Software Address Reliability, Cost, ...ARC Advisory Group
Use of Microsoft technology in plant floor systems is now a given, with further
horizontal and vertical penetration likely to continue. Automation end
users, suppliers, SIs, and OEM machine builders recognize this inevitability
and its potential value proposition in plant floor applications, particularly
the leveraging of economies of scale inherent in
lower-cost COTS technology. Most also realize
that this migration must take place with primary
consideration given to the reliability, costeffectiveness,
and supportability issues that are
paramount in plant floor applications, plus the necessity
of implementing and maintaining these
systems using the traditional plant floor skill set. OMAC’s Microsoft User
Group has issued a Best Practices document that highlights key aspects of
Microsoft’s architecture that impact these issues and provides options for
manufacturers to consider when applying these Best Practices in your own
plants.
Agile and continuous delivery – How IBM Watson Workspace is builtVincent Burckhardt
Journey and transformations that we have been taking at IBM to implement Cloud Native application. Covers culture, architecture and pipeline changes. This presentation was given at IBM Connect 2017 in San Francisco in Feb 2017.
This document discusses cloud testing, including its benefits, limitations, and challenges. Some key points:
- Cloud testing allows testing to be outsourced to third parties, reducing costs and allowing for scalability and flexibility. However, security, lack of standards, and dependency on internet connectivity pose challenges.
- Different forms of cloud testing include functional testing (unit, integration, user acceptance) and non-functional testing (availability, scalability, security, performance).
- Benefits include lower costs, scalability, availability of live production replicas, customizability, and improved time management. However, selection of providers, infrastructure requirements, and layer testing limitations remain challenges.
Test environments are important for project success and require upfront organization and proactive management to minimize downtime. Ensuring test environments are stable, maintainable, accurate and accessible can save significant costs by reducing defects, maintaining project schedules, and maximizing development and testing time. Key questions to address include what the environment will be used for, its technical structure, who will access it, and how many environments are needed to minimize downtime.
This document discusses GSS Infotech's automated approach to migrating organizations from older versions of Windows to Windows 7. It begins by outlining the challenges of large-scale Windows migrations. The approach involves 4 steps: 1) Analysis and planning to understand user environments and applications, 2) Engineering including automated compatibility testing to determine if applications will work, 3) Deployment using imaging and automation to minimize downtime, 4) Ensuring steady state like training and support after migration. Automation is key to efficiently handling large migrations with minimal human intervention.
Top-Down Network Design
Analyzing Technical Goals and Tradeoffs
Copyright 2010 Cisco Press & Priscilla Oppenheimer
Technical GoalsScalabilityAvailabilityPerformanceSecurityManageabilityUsabilityAdaptabilityAffordability
Scalability: How much growth a network design must support.
Availability: The amount of time a network is available to users, often expressed as a percent uptime, or as a mean time between failure (MTBF) and mean time to repair (MTTR). Availability goals can also document any monetary cost associated with network downtime.
Security: Goals for protecting the organization's ability to conduct business without interference from intruders inappropriately accessing or damaging equipment, data, or operations. Specific security risks should be documented.
Manageability: Goals for fault, configuration, accounting, performance, and security (FCAPS) management
Usability: Goals regarding the ease with which network users can access the network and its services, including goals for simplifying user tasks related to network addressing, naming, and resource discovery.
Adaptability: The ease with which a network design and implementation can adapt to network faults, changing traffic patterns, additional business or technical requirements, new business practices, and other changes.
Affordability: The importance of containing the costs associated with purchasing and operating network equipment and services.
ScalabilityScalability refers to the ability to growSome technologies are more scalableFlat network designs, for example, don’t scale wellTry to learnNumber of sites to be addedWhat will be needed at each of these sitesHow many users will be addedHow many more servers will be added
AvailabilityAvailability can be expressed as a percent uptime per year, month, week, day, or hour, compared to the total time in that periodFor example:24/7 operationNetwork is up for 165 hours in the 168-hour weekAvailability is 98.21%Different applications may require different levelsSome enterprises may want 99.999% or “Five Nines” availability
Availability
Downtime in Minutes
4.32
1.44
.72
.01
30
10
5
.10
1577
99.70%
526
99.90%
263
99.95%
5
99.999%
Per Hour
Per Day
Per Week
Per Year
.18
.06
.03
.0006
.29
2
105
99.98%
.012
99.70% availability sounds pretty good, but it could mean that the network is down for 0.18 minutes every hour. This is 11 seconds. If those 11 seconds were spread out over the hour, nobody would notice possibly. But if there were some bug, for example, that caused the network to fail for 11 seconds every hour on the hour, people would notice. Users these days are very impatient.
Notice that 99.70% availability also could mean one catastrophic problem caused the network to be down for 1577 minutes all at once. That’s 26 hours. If it were on a Saturday and the network was never down for the rest of the year, that might actually be OK. So, you have to consider time frames with percent availability numbers.
Consider t ...
IO-Link Safety is a new standard that allows for functionally safe components and communication over IO-Link. It will meet the requirements of IEC 61784-3 and can be used in safety applications up to SIL3/PLe. IO-Link Safety uses FS-Masters and FS-Devices to enable safety functions over standard IO-Link infrastructure. It will be standardized internationally as IEC 61139-2. The presentation provided an overview of IO-Link Safety and its standards, as well as its integration with fieldbus systems using functional safety communication profiles.
The document discusses integrating PROFINET with Time Sensitive Networking (TSN). It covers TSN features like time synchronization, scheduled traffic, and frame preemption that enable standard Ethernet to be real-time capable. The integration defines device models for PROFINET end stations and bridges based on TSN standards. This allows PROFINET to utilize TSN's quality of service mechanisms for converged industrial networks.
The document discusses the challenges that manufacturers face with increasing use of industrial robots from different suppliers in their production lines. This includes needing specific expertise for each robot manufacturer, high engineering costs, and lack of data transparency. It introduces the Standard Robot Command Interface (SRCI) as an innovative solution to program robots through the PLC using a common language. This would allow uniform operation of robots from multiple vendors and reduce costs and errors compared to needing separate programming for each type of robot.
Richard Wilson is the Head of Operational Security at GCC. His resume outlines his experience in operational security, mitigation against physical attack vectors, emerging cyber threats to vehicles, and the UK's public sector cyber security community. Key challenges include the increasing lines of code in vehicles, lack of standards to assess cybersecurity products, and implementing recent standards like ISO/SAE 21434 for automotive cybersecurity engineering.
This document discusses OPC UA (Open Platform Communications Unified Architecture) and how it can be used with Profinet in industrial automation networks. OPC UA is an interoperability standard that allows for the secure exchange of data between devices from different vendors. It defines interfaces for browsing device data, reading and writing data values, subscribing to data changes, and calling methods on devices. When used with Profinet, OPC UA can enable vertical communication throughout the industrial automation hierarchy from sensors and controllers to cloud applications.
The document discusses Advanced Physical Layer (APL), a new Ethernet technology that enables Ethernet communication over a two-wire cable for use in hazardous industrial environments. APL will allow Profinet to extend to field devices by overcoming Ethernet's limitations of only operating up to 100 meters and not being intrinsically safe. APL uses a two-wire cable to transmit power and data that can operate over distances up to 1000 meters, meeting functional safety requirements to operate in hazardous areas where Ethernet currently cannot. This will allow Ethernet networking throughout industrial plants, including hazardous zones, enabling greater connectivity for field devices and digital transformation of process automation.
This document discusses operational technology (OT) cyber security. It begins by explaining why OT networks need security due to the merging of IT and OT networks, which has exposed OT assets to compromise. It then describes the differences between IT and OT approaches, with OT prioritizing control, availability, integrity and confidentiality over just data. Several common attack paths for OT networks are outlined, including social engineering, malware from removable devices, and internet-connected components. The document advocates for a multi-layered protection concept including security awareness training, firewalls, physical protection and network monitoring. It stresses that security should be considered from the initial design phase.
This document discusses the PA DIM (Process Automation Device Information Model) presentation. It introduces PA DIM as a standardized information model for accessing device data via OPC-UA. PA DIM is based on NAMUR requirements and reuses interfaces from the OPC UA Device Integration model. It allows mapping device information contained in packages like FDI to OPC-UA clients, providing access to signals, functions and health of devices nearly independently of the physical communication protocol. The presentation also provides an overview of common device driver types like EDD, FDT/DTM and FDI and how OPC-UA supports information modeling and both client-server and publish-subscribe communication mechanisms.
The document discusses PROFIBUS & PROFINET International (PI), an organization that supports the use of PROFIBUS and PROFINET automation technologies worldwide. PI has over 50 competence centers and training centers located across Europe, North America, Asia, and other regions. The document outlines PI's membership categories and training opportunities. It also describes PI's role in driving enabling technologies for digital transformation, including information modeling, security, and communication standards like TSN and 5G. In closing, it thanks the reader for their time.
The document outlines the agenda for a PI UK event on PROFIBUS and PROFINET. It includes presentations on topics such as the current lifecycle of PROFIBUS, the Advanced Physical Layer for PROFIBUS, the Standard Robot Command Interface, PROFINET Time Sensitive Networking, the Process Automation Device Information Model, PROFINET Cyber Security, IO-Link safety, and OPC UA. There will also be opportunities for questions and answers as well as interactions with exhibitors at table tops from companies like Siemens, Turck Banner, Phoenix Contact, HMS, and Parmley Graham. Safety information about fire alarms and toilets is also provided.
The document discusses the process of certifying a PROFINET network and diagnostics. It describes various test types including verification, qualification, and certification tests to assess the network according to standards. Cable verification ensures accurate wiring while qualification testing identifies data transmission performance. Network acceptance tests check the inventory, topology, packet loss rate, and load. Designers are responsible for port numbers, cable labels, device names, and locations. Troubleshooting examines common issues like wiring faults, interference, configuration errors, and device failures.
1) PROFINET uses switched Ethernet topology that follows the production process layout. It uses separate channels for IO data and TCP/IP to avoid needing an extra network.
2) PROFINET supports star, tree, line and ring topologies using various cable types. Topology is based on the system design.
3) Network planning tools are used to simulate network utilization for PROFINET IO data and other traffic like TCP/IP. They validate designs and identify potential overloads.
This document discusses PROFINET gateways and how they facilitate communication between PROFINET networks and other industrial networks like PROFIBUS, AS-I, IO-Link, and IIoT. It explains that gateways appear as an IO device on the PROFINET side and act as a master on the sub-network side. The document provides examples of configuration steps needed for different gateway types, such as adding their GSD/GSDML files to hardware configurations and mapping input/output channels. It also demonstrates a new PROFINET to PROFIBUS DP gateway product that allows a PROFINET controller to control PROFIBUS slaves.
This document discusses device configuration tools and the history of EDDL and FDT standards. It provides an overview of the Field Device Integration (FDI) cooperation, which aims to create a single, unified solution for device configuration that combines the advantages of EDDL and FDT. The document also includes examples of how different device types can be configured using FDI and FDT/DTM technologies.
Derek Lane presented on PROFINET for IoT, IIoT, and Industry 4.0. He discussed how PROFINET and the PROFINET of Things supports the IIoT through data access, uptime, and open standards. PROFINET provides connectivity from the enterprise level to the field level and supports data transfer through various application profiles and proxies. Security is also important for IIoT and PROFINET complies with necessary security measures. PROFINET is moving towards Industry 4.0 through technologies like TSN that enable high determinism and real-time communication over converged networks.
The document discusses Ethernet-APL, a new physical layer specification that enables Ethernet connectivity in process plants. Ethernet-APL uses a two-wire cable setup to allow Ethernet networks to extend into hazardous areas and overcome limitations of traditional Ethernet like speed and distance. It standardizes technologies like 10BASE-T1L and 2-WISE to ensure interoperability. Ethernet-APL helps digital transformation by providing a single high-speed network for all plant components and seamless data access.
For people responsible for the design, commissioning and support of PROFINET networks, explaining how to integrate existing PROFIBUS DP and PROFIBUS PA devices into that network. The webinar took the form of a presentation with demonstrations to aid understanding.
For people responsible for the commissioning and support of PROFIBUS networks. The webinar took the form of a presentation with demonstrations to aid understanding.
This webinar presentation provides information on diagnosing PROFINET networks. It discusses various diagnostic tools that can be used, including those within IO controllers, switches, and third-party hardware and software. Specific tools covered are active and passive diagnostic devices, Ethernet frame analyzers, port mirroring, and Ethernet taps. The presentation emphasizes the importance of proper network design and qualification to ensure issues can be identified and supported. Control Specialists offers various PROFINET training courses.
More from PROFIBUS and PROFINET InternationaI - PI UK (20)
Hierarchical Digital Twin of a Naval Power SystemKerry Sado
A hierarchical digital twin of a Naval DC power system has been developed and experimentally verified. Similar to other state-of-the-art digital twins, this technology creates a digital replica of the physical system executed in real-time or faster, which can modify hardware controls. However, its advantage stems from distributing computational efforts by utilizing a hierarchical structure composed of lower-level digital twin blocks and a higher-level system digital twin. Each digital twin block is associated with a physical subsystem of the hardware and communicates with a singular system digital twin, which creates a system-level response. By extracting information from each level of the hierarchy, power system controls of the hardware were reconfigured autonomously. This hierarchical digital twin development offers several advantages over other digital twins, particularly in the field of naval power systems. The hierarchical structure allows for greater computational efficiency and scalability while the ability to autonomously reconfigure hardware controls offers increased flexibility and responsiveness. The hierarchical decomposition and models utilized were well aligned with the physical twin, as indicated by the maximum deviations between the developed digital twin hierarchy and the hardware.
We have compiled the most important slides from each speaker's presentation. This year’s compilation, available for free, captures the key insights and contributions shared during the DfMAy 2024 conference.
6th International Conference on Machine Learning & Applications (CMLA 2024)ClaraZara1
6th International Conference on Machine Learning & Applications (CMLA 2024) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of on Machine Learning & Applications.
Harnessing WebAssembly for Real-time Stateless Streaming PipelinesChristina Lin
Traditionally, dealing with real-time data pipelines has involved significant overhead, even for straightforward tasks like data transformation or masking. However, in this talk, we’ll venture into the dynamic realm of WebAssembly (WASM) and discover how it can revolutionize the creation of stateless streaming pipelines within a Kafka (Redpanda) broker. These pipelines are adept at managing low-latency, high-data-volume scenarios.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
Adaptive synchronous sliding control for a robot manipulator based on neural ...IJECEIAES
Robot manipulators have become important equipment in production lines, medical fields, and transportation. Improving the quality of trajectory tracking for
robot hands is always an attractive topic in the research community. This is a
challenging problem because robot manipulators are complex nonlinear systems
and are often subject to fluctuations in loads and external disturbances. This
article proposes an adaptive synchronous sliding control scheme to improve trajectory tracking performance for a robot manipulator. The proposed controller
ensures that the positions of the joints track the desired trajectory, synchronize
the errors, and significantly reduces chattering. First, the synchronous tracking
errors and synchronous sliding surfaces are presented. Second, the synchronous
tracking error dynamics are determined. Third, a robust adaptive control law is
designed,the unknown components of the model are estimated online by the neural network, and the parameters of the switching elements are selected by fuzzy
logic. The built algorithm ensures that the tracking and approximation errors
are ultimately uniformly bounded (UUB). Finally, the effectiveness of the constructed algorithm is demonstrated through simulation and experimental results.
Simulation and experimental results show that the proposed controller is effective with small synchronous tracking errors, and the chattering phenomenon is
significantly reduced.
HEAP SORT ILLUSTRATED WITH HEAPIFY, BUILD HEAP FOR DYNAMIC ARRAYS.
Heap sort is a comparison-based sorting technique based on Binary Heap data structure. It is similar to the selection sort where we first find the minimum element and place the minimum element at the beginning. Repeat the same process for the remaining elements.
PROFIBUS and PROFINET system design for the process industry - Andy Verwer
1. System Design
for the Process
Industry
Andy Verwer,
Verwer Training
& Consultancy
Ltd
Accredited PI
Training Centre
Practical Aspects of
PROFIBUS and
PROFINET in
Process. Held at
Endress+Hauser
Manchester, 30th
March 2017
2. System Design, Andy Verwer, page 2Practical Aspects of PROFIBUS/NET, March 2017
Process Industry Requirements
The Process Industry has quite different requirements from
Factory Automation.
Generally, we are dealing devices that are exposed to the
environment.
Requires higher IP ratings.
Hazardous environments (explosive atmospheres) are common.
Requires Intrinsic Safety.
We are often dealing with extensive systems with thousands of
devices.
Requires high availability.
High speed operation is not normally required.
Production cannot normally be stopped, so engineering
activities such as maintenance and device replacement must
have minimum impact.
3. System Design, Andy Verwer, page 3Practical Aspects of PROFIBUS/NET, March 2017
System costs
Most system designers and project managers look at the
project procurement, installation and deployment costs when
they price a project.
However, the costs of an automation system spread over the
life cycle of the plant and should include maintenance, fault-
finding and health-checking.
Perhaps most important is the cost in terms of loss of
production should faults develop during the lifetime of the
plant. Spending a little more at procurement time can repay
many times over.
Good fault tolerant design need not be more expensive.
Sometimes fault tolerance can be achieved with just a little
thought at no additional cost.
4. System Design, Andy Verwer, page 4Practical Aspects of PROFIBUS/NET, March 2017
Life cycle costs
The procurement,
installation,
commissioning
costs are only
incurred at the start
of the project.
There will also be
burn-in failures.
Costs from device
failures due to
burn-out increase
as equipment gets
older.
The total cost is the
sum of the two.
5. System Design, Andy Verwer, page 5Practical Aspects of PROFIBUS/NET, March 2017
Control system design
Control system design normally proceeds by building on the
experience obtained from previous designs.
But, designs which are based on badly designed systems will be
bad!
Only by using experience from operations and maintenance
staff can we develop good system designs.
In my experience it is rare for such feedback mechanisms to be
present. Particularly when design is carried out by sub-
contractors.
Designers need to know about mistakes that have been made
in the past.
Feedback from operations and maintenance is essential.
6. System Design, Andy Verwer, page 6Practical Aspects of PROFIBUS/NET, March 2017
Cost of failures
The parts of a control system
will fail whilst in service.
The consequences of failures
are often predictable, but the
failures themselves are
unpredictable.
The design of a reliable
control system is not simple.
… and should be accompanied
by analysis of how parts fail
and of the consequences of
these failures.
7. System Design, Andy Verwer, page 7Practical Aspects of PROFIBUS/NET, March 2017
Reliability and availability
Reliability is a measure of how a component, assembly or
system will perform its intended function without failure.
Availability is a measure of reliability indicating the fraction of
time in which a device or system is expected to operate within
specification.
It is important to remember that
reliability and availability are statistical
measures: they will not predict when a
particular device or system will fail,
only the expected rate based on
average performance of a batch of test
devices or on past performance.
8. System Design, Andy Verwer, page 8Practical Aspects of PROFIBUS/NET, March 2017
System costs
Maximising plant availability is critical in reducing the total
costs of the system. It is essential that the System Designer
understands:
That minimising plant down time when faults inevitably
occur (i.e. maximising plant availability) is a key
requirement.
The impact of the network layout on plant reliability.
That the incorporation of network health checking and
fault finding facilities are essential.
How to appropriately use features such as redundancy and
network monitoring and rapid fault location and repair to
improve plant availability.
9. System Design, Andy Verwer, page 9Practical Aspects of PROFIBUS/NET, March 2017
Minimising the failure footprint
There are three basic ways to minimise the impact of faults:
1. Make failures less likely – Minimise the Fault Frequency.
2. Restrict the Fault Effect when failures inevitably occur.
3. Minimise the Fault Duration – Provide for rapid fault location
and repair.
A good network design will minimise the effect on production
when inevitable failures occur.
We can speak of minimising the “failure footprint”.
Fault
frequency
Fault
effect
Fault
duration
10. System Design, Andy Verwer, page 10Practical Aspects of PROFIBUS/NET, March 2017
Minimising the failure footprint
Understand and implement the design and installation rules.
Use only certified Installers.
Improve reliability - use good quality well tested (certified) and
reliable devices, connectors and network components.
Use manufacturers who carry out burn-in testing on devices.
1. How can we minimise Fault Frequency?
Fault Frequency
11. System Design, Andy Verwer, page 11Practical Aspects of PROFIBUS/NET, March 2017
Minimising the failure footprint
2. How can we minimise the Fault Effect?
Analyse the effects of failures on plant operation.
Use well thought out network layout and design.
Think about:
Using separate networks and/or different controllers
(distributed control),
Adopt a layout that can isolate faults in one plant area from
the rest of the network.
How to deal with common cause failures.
Fault
Effect
12. System Design, Andy Verwer, page 12Practical Aspects of PROFIBUS/NET, March 2017
Minimising the failure footprint
3. How can we minimise the Fault Duration?
Provide facilities in the design for rapid fault diagnosis and
fault location.
Provide in the design for device hot swapping without
reconfiguration.
Use designs that allow for a quick fix.
Provide redundancy when appropriate. Needs to be well
thought out!
Use standardised, vendor independent solutions rather
than being locked into manufacturer specific solutions.
Fault
Duration
13. System Design, Andy Verwer, page 13Practical Aspects of PROFIBUS/NET, March 2017
Reliability and availability
Reliability is a measure of how a component, assembly or
system will perform its intended function, without failure, for
the required duration when installed and operated correctly in
a specified environment.
Availability is a measure of reliability indicating the fraction of
time in which a device or system is expected to operate
correctly.
It is important to remember that reliability and availability are
statistical measures: they will not predict when a particular
device will fail, only the expected rate based on average
performance of a batch of test devices or on past
performance.
14. System Design, Andy Verwer, page 14Practical Aspects of PROFIBUS/NET, March 2017
Some definitions
Mean Time Between Failures (MTBF) is the expected or
average time that a device will be free of failure.
Typical MTBF for a well designed and manufactured electronic
device might be 10 to 20 years.
Mean Time To Repair (MTTR), is the time taken to repair a
failed device.
In an operational system, MTTR generally means time to
detect the failure, diagnose and locate the problem and
replace the failed part.
15. System Design, Andy Verwer, page 15Practical Aspects of PROFIBUS/NET, March 2017
Availability
MTTRMTBF
MTBF
ty,Availabili
+
=A
Availability can be calculated from MTBF and MTTR:
Remember that availability is a statistical measure and
represents an average probability of being in operation.
There is little point in trying to be accurate with these figures
since actual failures are unpredictable.
Availability is typically specified in “nines notation”. For
example 3-nines availability corresponds to 99.9%
availability. A 5-nines availability corresponds to 99.999%
availability.
16. System Design, Andy Verwer, page 16Practical Aspects of PROFIBUS/NET, March 2017
Availability and downtime
Availability, A D = (1-A) Downtime
0.9 = 90% (1-nine) 0.1 (10-1) 36.5 days/year
0.99 = 99% (2-nines) 0.01 (10-2) 3.7 days/year
99.9% (3-nines) 0.001 (10-3) 8.8 hours/year
99.99% (4-nines) 0.0001 (10-4) 53 minutes/year
99.999% (5-nines) 0.00001 (10-5) 5 minutes/year
99.9999% (6-nines) 0.000001 (10-6) 5 minutes/10years
99.99999% (7-nines) 0.0000001 (10-7) Not feasible!
99.999999% (8-nines) 0.00000001 (10-8) Impossible!
Downtime is an alternative way of understanding the
availability:
MTTRMTBF
MMTR
AD
+
=−= )1(Downtime,
Normalrange
forautomation
17. System Design, Andy Verwer, page 17Practical Aspects of PROFIBUS/NET, March 2017
Availability and downtime
Note that the availability of a device or system can be
improved by decreasing the MTTR.
This can be accomplished in several ways:
Faster detection and location of faults. (Accomplished by
diagnostic reporting facilities, availability of fault finding
tools and training of maintenance personnel).
Faster repair of the fault. (Accomplished by availability of
spares and all of the above).
Fault tolerant design.
18. System Design, Andy Verwer, page 18Practical Aspects of PROFIBUS/NET, March 2017
Example
Consider a device with a MTBF of 10 years.
When the device fails, it could take several days to
recognise, diagnose and locate the fault. And then, if not
held as a spare, several more days to obtain a replacement.
The MTTR could be one week, giving an availability of:
998.0
73650
3650
736510
36510
=
+
=
+×
×
=
+
=
MTTRMTBF
MTBF
A
That is approximately 3-nines availability, or a downtime of
about 16 hours/year.
Consider the availability when the MTTR is reduced to ½ day:
0.99986
5.036510
36510
=
+×
×
=A
The availability is now 4-nines and the downtime has reduced
to about 1hour/year.
19. System Design for the Process Industry, Andy Verwer, page 19Practical Aspects of PROFIBUS and PROFINET in Process, 30 March 2017
Design for minimum fault impact
Use pluggable devices that can be removed/replaced without
impinging on network operation.
For PROFIBUS PA this normally means using tee boxes and
spur lines:
M12 socket
for spur line
Multi-way spur boxes often incorporate
segment protection and/or redundancy options.
20. System Design, Andy Verwer, page 20Practical Aspects of PROFIBUS/NET, March 2017
Design for minimum fault impact
For PROFIBUS DP we can use hubs which provide isolated
segments for sections of the network:
Some of these also provide network health monitoring
facilities and/or redundancy.
21. System Design, Andy Verwer, page 21Practical Aspects of PROFIBUS/NET, March 2017
Other ways to improve availability
We can perhaps use a network layout that allows critical plant
operation to continue in the event of cable/connector failure
or device replacement.
In particular, can we organise the network so that selected
parts can be independently shut down for maintenance
without affecting the remaining production?
A simple example of this is seen with streamed production.
A stream can be taken out of service without affecting the
other stream. But only if the system design allows this.
Process 1 Process 2 Process 3
Stream A
Process 1 Process 2 Process 3
Stream B
22. System Design, Andy Verwer, page 22Practical Aspects of PROFIBUS/NET, March 2017
Automation islands or units
The concept of dividing the plant into Automation Islands or
Automation Units is well established. (See the PI design
guides.)
Each automation unit is considered as being functionally
separated from the rest of the plant so allowing it to operate
(and to be shut down) independently.
A good network design will facilitate the isolation of these
automation units using:
• Different controllers;
• Different networks or subnetworks;
• Segmentation.
Careful choice of various architectures for automation units is
a key stage in the design process which can impact on the
overall reliability and maintainability of the control system.
23. System Design, Andy Verwer, page 23Practical Aspects of PROFIBUS/NET, March 2017
Reliability modelling
The system designer must understand the methods of
modelling and analysis of reliability and availability in systems.
In particular how system availability can be predicted from the
individual parts.
Also understand how standby systems, redundant solutions
and common cause failures impact the overall system
reliability.
We often find that redundancy is inappropriately used and
sometimes results in no real improvement in system
availability.
Careful network layout can have a major effect on the fault
footprint and significantly improve the overall availability of
the plant.
24. System Design, Andy Verwer, page 24Practical Aspects of PROFIBUS/NET, March 2017
Standby and redundant systems
We often see standby or redundant systems used to try to
improve plant availability.
Here we have two or more devices working in parallel.
Should a fault occur in the operational device then the standby
device can take over.
The switch over can be manually activated or can be
automatic. The switching time should be considered when
estimating the overall system availability.
This scheme achieves high availability because the system
function is maintained whilst repairing the failed device.
25. System Design, Andy Verwer, page 25Practical Aspects of PROFIBUS/NET, March 2017
Slave with
integrated
redundancy
Y
Slave 4
Slave
3A
Slave
3B
Mechanically
combined outputs
Redundant
slaves
Wired OR
outputs
Slave
2A
Slave
2B
Y
Redundant
masters
Master
B
Y
Redundancy solutions for PROFIBUS
Properly designed redundant
solutions can provide robustness
against a wide selection of faults
and conditions.
Master
A
Redundant cables
PSU A
PSU B
Redundant
power
supplies
Y
Slave
1
Redundant
links or hubs
Y
26. System Design, Andy Verwer, page 26Practical Aspects of PROFIBUS/NET, March 2017
Device replacement
When a device fails, it must be replaced.
As we have seen, simple and fast device replacement can have a major
impact on the plant availability.
For PROFIBUS devices, this generally means that the replacement
must be of the same type and version.
The device must be given the same address as the device it is
replacing.
However, suppose that the replacement is a newer version or perhaps
even a device from a different manufacturer?
Normally we would need to stop the controller and change the
network configuration to include the different device.
The current PROFIBUS PA profile incorporates a nice feature which
allows PA devices use generic “profile” configuration and thus allows
devices to be exchanged without reconfiguration.
But the initial system must be configured to use these profile GSD files
rather than the manufacturer specific GSD.
27. System Design, Andy Verwer, page 27Practical Aspects of PROFIBUS/NET, March 2017
PA Device Replacement
Process Control System
Temperature transmitter configured using
The Profile GSD: “PA139700.GSD”
Temperature transmitter
manufacturer ID = 089A
Alternate profile ID = 9700
Temperature transmitter
manufacturer ID = 1523
Alternate profile ID = 9700
Failed device Replacement device
Replacement device
automatically adapts to the
configured ID
28. System Design, Andy Verwer, page 28Practical Aspects of PROFIBUS/NET, March 2017
Certified System Design course
A fully accredited Certified PROFIBUS System Design course
has been developed in the last few years. This qualification is
recognised world-wide.
This 3-day training course is suitable for managers, designers
and engineers who are involved in the planning, specification,
design and procurement of PROFIBUS systems.
The course covers the optimum design both DP and PA
systems for availability and maintenance.
The 1-day Certified PROFIBUS Installer course is an essential
pre-requisite which is normally run together with the design
course making 4-days of training.
The course is also available for cost-effective on-site delivery
for between 6 and 12 people.
29. System Design, Andy Verwer, page 29Practical Aspects of PROFIBUS/NET, March 2017
Training
Certified PROFIBUS and PROFINET training including the
Certified PROFIBUS System Design course is available from the
UK’s accredited training centres:
PROFIBUS International Competence Centre
Manchester Metropolitan University.
in Manchester, or a location of your choice.
(www.sci-eng.mmu.ac.uk/ascent/).
PROFIBUS International Training Centre
Verwer Training & Consultancy Ltd
In Manchester or on-site.
(www.VerwerTraining.com)