<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Aptos;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#96607D;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Aptos;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.E-MailFormatvorlage19
{mso-style-type:personal;
font-family:Aptos;
color:windowtext;}
span.E-MailFormatvorlage20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1593778129;
mso-list-type:hybrid;
mso-list-template-ids:321408878 67567617 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:2091924263;
mso-list-template-ids:781470822;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="#467886" vlink="#96607D">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hello Guillermo,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">below the notes on what I found when implementing the changes in the testbed and the prototype. In addition to the open topics, the points are mainly two different
types:<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Error paths of list input fields. Our prototype previously didn’t implement this correctly. I noticed it
because you corrected it for some tests with the last version. <o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Input validation order. In some tests, you try to raise an operation error (e.g. update failed) with an
invalid status of the plan. But because the input is invalid as well, an invalid error is thrown before the operation error is reached. I didn’t notice this earlier because I accidentally threw an operation error when the ref was invalid.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marvin<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">PDS<o:p></o:p></span></u></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PDS_007_PQ7: Expect to return P6 (correct in notes).<o:p></o:p></span></li></ul>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">PES<o:p></o:p></span></u></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_005_3: Expect error code to be 1.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_005_4: Expect error code to be 2.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_006_1: Currently throws invalid error because IED1 does not exist on P5 and input validation is performed
before plan status checks.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_006_3: Expect error code to be 1.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_006_4: Expect error code to be 2.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_008_2: Currently throws an invalid error because AU1 does not exist on P5 and input validation is
performed before plan status checks.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_009_2: Currently throws an invalid error because EU1 does not exist on P5 and input validation is
performed before plan status checks.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_011_2: Currently throws an invalid error because RU1 does not exist on P5 and input validation is
performed before plan status checks.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_011_3: I’d expect additionally error path 2.1 since the resource is unknown as well.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_012_2: Currently throws an invalid error because RU1 does not exist on P5 and input validation is
performed before plan status checks.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_012_3: I’d expect additionally error path 2.1 since the resource profile is unknown as well.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">PECS<o:p></o:p></span></u></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_001_P0:
<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: I’d expect
the error path to be “1.10” with error code “UNDEFINED” (?) and path “1.5.6” with “BAD_TIME” because the validity end is before the start. Should only the end date be invalid, or also the start?
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">GB</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: I have updated
to 1.9,4 and 1.10,4.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Maybe I
got something wrong here. Could you explain why you would expect 1.9 and 1.10 with BAD_TIME as an error code? Field nine of a plan is “isAlternate” and field ten is “status”. I’d expect field 1.5.6 to be BAD_TIME or INCONSISTENT since the end time of the plan
information is before the start time. Additionally, the status is invalid since TERMINATED plans may not be accepted by the execution system according to the plan-state diagram. I’m not quite sure which secondary error fits bets here. Maybe UNDEFINED or OUT_OF_RANGE?
Otherwise one could also say that the input validation passes and the new SUBMIT_FAILED error is thrown later. Should be the same behavior as P2, however a validation error should be thrown in any case due to the invalid time.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_003_1:
<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: My understanding
is that P2 is rejected initially when submitted because it is TERMINATED and should therefore be unknown to PECS. In that case, P2 should be removed from input and expected output.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">GB</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Not fully
sure. This is getPlanStatus. A terminated plan, even if rejected initially on the submission, may be kept in the provider DB showing it was a terminated plan. It is an interesting question for the group.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: As I understand
it, the plan was never in the dataset of the execution system since it was rejected due to an invalid status. The getPlanStatus operation of PECS should only return the status of known plans if I understand it correctly.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_003_P0: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_004_P0: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_005_3: Expect the error path to be 2.1 for the first element of the second parameter.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_008_P0: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_011_2:<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: If I understand
the BB correctly, then all activities were unloaded in T_PECS_008 since an activity was already executed in T_PECS_006. This results in no monitor notification since the plan has no activity instances.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">GB</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: I do not
agree. I believe a subplan is a collection of Activity Instances, and they may belong to different plans. The fact that one is terminated does not mean that a subplan cannot be called and activated. Still a valid question for the WG. There is no connection
of a subPlan to a Plan, nor a way to submit a subPlan.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: The subplan
activation is not the problem but rather the expected monitor notification. My understanding is that the plans, which are under monitoring, do not contain any activity instance anymore due to T_PECS_006 and therefore do not trigger a notification.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_011_4: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_012_2:
<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: If I understand
the BB correctly, then all activities were unloaded in T_PECS_008 since an activity was already executed in T_PECS_006. This results in no monitor notification since the plan has no activity instances.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">GB</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: I do not
agree. I believe a subplan is a collection of Activity Instances, and they may belong to different plans. The fact that one is terminated does not mean that a subplan cannot be called and activated. Still a valid question for the WG. There is no connection
of a subPlan to a Plan, nor a way to submit a subPlan.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: The subplan
activation is not the problem but rather the expected monitor notification. My understanding is that the plans, which are under monitoring, do not contain any activity instance anymore due to T_PECS_006 and therefore do not trigger a notification.<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_012_subPlan0: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_013_subPlan0: Expect the error path to be 1.1 since it is the first element in the list.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_016_P0:
<o:p></o:p></span>
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Expect error
codes (1.5.6, BAD_TIME) and (“1.10”, UNDEFINED) since status is TERMINATED <o:p>
</o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">GB</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: See my question
in T_PECS_008. If P0 passed on a service is an UNKNOWN we should be consistent. Which plan is Terminated? I apply same logic as there, and use UNKNOWN. However, if we assume that the execution engine knows about P0, then indeed we need to enter into inner
error codes. <o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level2 lfo4"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">MW</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">: The status
of P0 is TERMINATED. This is indeed the same as P_PECS_001_2. My understanding is that the execution system only accepts plans that are RELEASED. I take this from the plan-state ULM diagram. Not sure which Secondary error fits best here.<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoListParagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE"> Guillermo
Buenadicha <Guillermo.Buenadicha@esa.int> <br>
<b>Gesendet:</b> Montag, 13. </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">Januar 2025 21:51<br>
<b>An:</b> Wittschen, Marvin <marvin.wittschen@dlr.de>; Dominik Marszk <Dominik.Marszk@esa.int>; Peter Van Der Plas <Peter.van.der.Plas@esa.int>; Cesar Coelho <Cesar.Coelho@ext.esa.int>; Lenzen, Christoph <Christoph.Lenzen@dlr.de>; Wörle, Maria Theresia <Maria.Woerle@dlr.de>;
luke.berry@gmv.com; Rachel Jenkins <rjenkins@gmv.com>; Ferguson, Eric W (US 3970) <eric.w.ferguson@jpl.nasa.gov>; geoff.lochmaier@nasa.gov; David Frew <David.Frew@esa.int>; olly.page@cgi.com; clement.hubin-andrieu@cnes.fr<br>
<b>Cc:</b> Guillermo Buenadicha via MOIMS-MP <moims-mp@mailman.ccsds.org><br>
<b>Betreff:</b> MPS: Test Case specification V19<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">Dear Marvin:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">Thanks for your inputs to the V18, that have resulted in a V19, available in the GDrive and also attached here.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">In orange you may see some questions/doubts I have on some of the tests, I would like to raise these to the attention of the WG. See that in the Notes section.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">As reported in the meeting today, I will proceed to a version 20 implementing the changes of the BB post Agency review, kindly compiled by Peter (thanks!!!). Since this will be a heavy work, if
you find something in between or we could get clarification to my points that would indeed help. Some of the existing test steps will be waived by the BB, and some service implementation or data elements will change, but at least I would like to have the logic
of the services clear.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><br>
Regards!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">G<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">-----------------------------------------------------------------------------</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Guillermo Buenadicha, SCI-S</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">O</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">E</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Euclid SOC
</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Operations Coordinator<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">SCO-02 Technical Responsible</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">European Space Astronomy Centre (ESAC) ESA </span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Villanueva de la Cañada, Madrid, SPAIN</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Phone (34)
</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">686 50 52 68</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><a href="mailto:guillermo.buenadicha@esa.int" title="mailto:guillermo.buenadicha@esa.int"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#0563C1;mso-ligatures:none;mso-fareast-language:EN-GB">guillermo.buenadicha@esa.int</span></a><span lang="EN-GB" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-family:"Arial",sans-serif;color:black;mso-ligatures:none;mso-fareast-language:EN-GB">----------------------------------------------------------------------------</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected
content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data
privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">dpo@esa.int</span></a><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">).
<o:p></o:p></span></p>
</div>
</body>
</html>