The process for the EGS-CC definition of the procedure exchange format language

1. Nieves Salor Moral - Vitrociset Belgium
ESAW 2015 –Darmstadt, June 2015
APPLICATION OF AUTOMATION KNOW-HOW
WITHIN THE EGS-CC PROJECT

2. ƎAUTOMATION?
PRIOR EGS-CC
YES
SO…WHAT’S THE PROBLEM

3. ISSUES IN PROCEDURE INTEROPERABILITY
3
FCP
OBCP
PLUTO
JAVA
TOPE
MOIS
OTX

4. ƎAUTOMATION?
BEFORE EGS-CC
YES
SO…WHAT’S THE PROBLEM?
AND LESSONS LEARNED?

5. EXPERIENCE IN AUTOMATION (I)

6. EXPERIENCE IN AUTOMATION (II)

7. • Prepare the Automation Procedure Exchange Language of the EGS-
CC:
All stakeholders
• Common for
All phases
• Design and develop the Automation Execution Engine of the EGS-CC
• Supporting execution/debugging of Automation Procedures
• Supporting execution/debugging of Automation Scripts
EGS-CC AUTOMATION TARGET

8. AP CONSTRAINTS

9. AP DEFINITION PROCESS
1
2
3
4
Start new Sprint
• Implement new features
• Changes of the RIDs
Internal meetings
during Sprints
At the end of each sprint:
• Delivery to the SET
At the end of each sprint:
• SET Review
• Meeting with the SET to
discuss RIDs
Total: 3 Sprints + Final Delivery

10. AP EXCHANGE FORMAT
• Principles:
• Supports E-32 requirements !
• Java Inheritance of an abstract Procedure class
• Mandatory BODY method containing lambda
expression steps
• Steps are java methods

11. AP EXCHANGE FORMAT
Annotation Applicability Description
@McmParameter(String path) Parameter<T
extends
Quantity<T>>
Annotation for the MCM Parameter with:
 The absolute or relative path (the second one has to start with a dot)
@McmActivity(String path) McActivity Annotation for the MCM Activity with:
 The absolute or relative path (the second one has to start with a dot)
@McmElement(String path) MCElement Annotation for the MCM Element with:
 The absolute or relative path (the second one has to start with a dot)
@McmEvent(String path ) Event Annotation for the MCM Event with:
 The absolute or relative path (the second one has to start with a dot)
@McmActivityArgument(String
name, String activity)
Argument Annotation for the MCM Activity Argument with:
 The name of the procedure argument
 The activity of the argument. This attribute is optional and it is used to
specify if the declared attribute belongs to the current procedure (then it is
considered optional) or it is an argument associated to another activity
invoked inside the procedure.
Subsys1
Subsys2
Subsys3
Subsys4
System
Activity4.1
Activity4.2
Param 4.1
Subsys5
This is changed in the latest version!!

12. AP EXCHANGE FORMAT: STATEMENTS

13. AP EXCHANGE FORMAT: ACTIVITY MNGT
Activity
Def
Act
Occur
Act
Occur
Act
Occur
Act
Occur
Activity
invocation

14. AP EXCHANGE FORMAT: ERROR HANDLING
• Exceptions can be managed at step level
using standard Java means
• The AbortException raised by the abort()
method must never be catch by the
programmer.
• If exceptions are not handled at step level:
• they can be managed at body method
level using standard Java means.
• If exceptions are not handled by the
procedure programmer, they will be
caught by the execution environment
and will cause the procedure to be
aborted.

15. AP EXCHANGE FORMAT
• Principles:
• Expose functionality of other EGS-CC
components
• Transparent to the user
• Non-complex code
• Access to functionality shall be static to
avoid instantiation
• To be scalable.
• Current Functionality
• Packets, Monitoring Checks, Calibrations,
Global Variables.
• Log and File Support
• Date management

16. AP EXCHANGE FORMAT
• Principles:
• Expose functionality of other EGS-CC
components
• Transparent to the user
• Non-complex code
• Access to functionality shall be static to
avoid instantiation
• To be scalable.
• Current Functionality
• Packets, Monitoring Checks, Calibrations,
Global Variables.
• Log and File Support
• Date management

17. EXAMPLES OF PROCEDURES

18. • Possibility of code generation of Monitoring and Control Referenced Data
• New process not foreseen.
• Impact on development of several components of the EGS-CC
• Communication between Automation Component and most of the EGS-CC
L0 components
• Need to assess the exposed services interfaces provided/consumed by
AUT
• Need to assess the data flow between components
• Need to modify/de-scope requirements due to AP format
modifications/stakeholder needs
• The importance of Support Libraries is bigger than expected:
• Has produced Change Request in other components
ISSUES RAISED DURING AP FORMAT DESIGN

19. Any Question?
19