Domain-Specific Language Architecture for Automation Systems: An - - PowerPoint PPT Presentation

Institut for Technical Informatics

www.ITI.TUGraz.at

Domain-Specific Language Architecture for Automation Systems: An Industrial Case Study

1

Christopher Preschern 03.07.2012

Christopher Preschern Andrea Leitner Christian Kreiner

Institut for Technical Informatics

www.ITI.TUGraz.at

Agenda

• My field of Research
• Motivation of the Paper
• What is PISCAS?
• PISCAS Demo

2

Christopher Preschern 03.07.2012

• PISCAS Demo
• PISCAS Architecture
• Results
• Conclusion

Institut for Technical Informatics

www.ITI.TUGraz.at

My field of research

• Embedded System Architectures

– Safety – Security

• Architectural Patterns

3

Christopher Preschern 03.07.2012

• Architectural Patterns

– Effect on Safety/Security Certification

this paper is based on results on results of my master‘s thesis

Institut for Technical Informatics

www.ITI.TUGraz.at

Motivation

• Suggest design decisions on how to easily

develop DSLs for automation systems

• Show the application and the consequences
• f these design decisions

4

Christopher Preschern 03.07.2012

• f these design decisions

Institut for Technical Informatics

www.ITI.TUGraz.at

What is PISCAS?

• PISCiculture Automation System
• www.piscas.eu
• Product Line approach to develop fish farm

automation systems

5

Christopher Preschern 03.07.2012

automation systems

– MetaEdit+ for DSL development – B&R automation devices

Institut for Technical Informatics

www.ITI.TUGraz.at

What is PISCAS?

6

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Demo

• Documentation
• Automation Software
• Web Portal

7

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

Fish farm automation domain description

• Elements: Feeders, oxygen level control,

water level supervision + alarm system

• Fish farms mostly differ in their

8

Christopher Preschern 03.07.2012

• Fish farms mostly differ in their

arrangement/amount of devices

• Device types change rather often
• Main functionality stays the same

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Architecture

9

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Architecture

10

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Architecture

11

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Design Decisions

• Abstract Object / Abstract Relationship
• Elements connected in Pipes&Filters style
• Direct representation of physical automation

devices as Objects

12

Christopher Preschern 03.07.2012

devices as Objects

• Explicit modeling of I/O modules

Institut for Technical Informatics

www.ITI.TUGraz.at

Benefits of the PISCAS Architecture

• Easy generation of documentation,

visualization and automation software mapping

• Intuitive modeling for automation domain

13

Christopher Preschern 03.07.2012

expert and fish farm expert

Institut for Technical Informatics

www.ITI.TUGraz.at

Final Remarks

• Provide guidelines for automation DSL

development

– benefits for visualization/documentation generation – benefits for application modeling – benefits for automation system maintenance

14

Christopher Preschern 03.07.2012

– benefits for automation system maintenance

• Two PISCAS systems in operation

– hardware installation plan was very useful – low software maintenance effort

Institut for Technical Informatics

www.ITI.TUGraz.at

Thank you very much for your attention Any questions?

15

Christopher Preschern 03.07.2012

Any questions?

Institut for Technical Informatics

www.ITI.TUGraz.at

PISCAS Application Modeling

16

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

DSL Complexity

17

Christopher Preschern 03.07.2012

Institut for Technical Informatics

www.ITI.TUGraz.at

Code Generator Dependance

18

Christopher Preschern 03.07.2012