2010 IEEE 15th Conference on Emerging Technologies &Amp; Factory Automation (ETFA 2010) 2010
DOI: 10.1109/etfa.2010.5641250
|View full text |Cite
|
Sign up to set email alerts
|

Design patterns for Failure Management in IEC 61499 Function Blocks.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2011
2011
2019
2019

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 15 publications
(6 citation statements)
references
References 12 publications
0
6
0
Order By: Relevance
“…For IEC 61499-based applications (IEC, 2011), common solutions and guidelines were proposed for hierarchical automation solutions (Zoitl and Prähofer, 2013), failure management (Serna et al, 2010) and portable automation projects (Dubinin and Vyatkin, 2012). Even software design patterns for IEC 61499 programs, e.g., Distributed Application, Proxy and Model-View-Controller, were defined (Christensen, 2000) and evaluated (Strömman et al, 2005).…”
Section: State Of the Artmentioning
confidence: 99%
“…For IEC 61499-based applications (IEC, 2011), common solutions and guidelines were proposed for hierarchical automation solutions (Zoitl and Prähofer, 2013), failure management (Serna et al, 2010) and portable automation projects (Dubinin and Vyatkin, 2012). Even software design patterns for IEC 61499 programs, e.g., Distributed Application, Proxy and Model-View-Controller, were defined (Christensen, 2000) and evaluated (Strömman et al, 2005).…”
Section: State Of the Artmentioning
confidence: 99%
“…As it has been previously indicated, a component has failure management inputs and outputs. Following the Failure Zone design pattern established by the authors [26], components can notify failures to each other, in order to transit to the failure, degraded or warning operation stages and perform their response actions. Later, a new notification allows recovery and the return to the normal operation.…”
Section: Cosme Component Modelmentioning
confidence: 99%
“…Operation modes are not tied up to any specific element, but they are scattered into all of them. • Failure Management: Figure 1 shows a box named "Failure Management", conceived according to the design pattern presented in a previous work from the authors [8]. Once the possible fault conditions are identified, characterized and classified, the appropriate response actions are mapped (degraded operation, nonscheduled stop, notification, etc.).…”
Section: Generic Functionalitymentioning
confidence: 99%