<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:x="urn:schemas-microsoft-com:office:excel" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
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;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
span.Notelevel1Char
{mso-style-name:"Note level 1 Char";
mso-style-link:"Note level 1";}
p.Notelevel1, li.Notelevel1, div.Notelevel1
{mso-style-name:"Note level 1";
mso-style-link:"Note level 1 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:56.9pt;
text-align:justify;
text-indent:-56.9pt;
line-height:14.0pt;
font-size:10.0pt;
font-family:"Times New Roman",serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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:126359431;
mso-list-template-ids:-1249323868;}
@list l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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 l0: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;}
@list l1
{mso-list-id:1121456203;
mso-list-template-ids:1848834088;}
@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;}
@list l2
{mso-list-id:1228607539;
mso-list-template-ids:1460855346;}
@list l2: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 l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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;}
@list l3
{mso-list-id:1642493118;
mso-list-template-ids:-239936508;}
@list l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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>
</head>
<body lang="EN-GB" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Dear Marvin:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Thanks as usual. Please, see my comments to your comments, with color codes (green accepted and implemented, red discrepancy, orange for discussion, if you wish on Monday or through
email before, as your wish).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Regards!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:dotted windowtext 3.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal">PDS<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#4EA72E">T_PDS_007_PQ7: Expect to return P6 (correct in notes).<o:p></o:p></span></p>
<p class="MsoNormal">PES<o:p></o:p></p>
<p class="MsoNormal">T_PES_005_3: Expect error code to be 1. <span style="color:red">
(disagree. Error code is 1 (INVALID) and the extra info is the field number (1) and the reason (0, unkown)<o:p></o:p></span></p>
<p class="MsoNormal">T_PES_005_4: Expect error code to be 2. <span style="color:red">
(disagree. Error code is 1 (INVALID) and the extra info is the field number (2) and the reason (0, unkown)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">T_PES_006_1: Currently throws invalid error because IED1 does not exist on P5 and input validation is performed before plan status checks.
<span style="font-family:Wingdings;color:#4EA72E"></span><span style="color:#4EA72E"> Event instance EI1 added to P5 as well. This also changes T_PDS_007_PQ11, now P1 and P5 returned.<o:p></o:p></span></p>
<p class="MsoNormal">T_PES_006_3: Expect error code to be 1. <span style="color:red">
(disagree. Error code is 1 (INVALID) and the extra info is the field number (1) and the reason (0, unkown)</span><o:p></o:p></p>
<p class="MsoNormal">T_PES_006_4: Expect error code to be 2. <span style="color:red">
(disagree. Error code is 1 (INVALID) and the extra info is the field number (2) and the reason (0, unkown)</span><o:p></o:p></p>
<p class="MsoNormal">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.
<span style="font-family:Wingdings"></span> <span style="color:red">Disagree. The operation fails with UPDATE_FAILED since the P5 is terminated. AI1 exists in P5, so an activity update should not be rejected as invalid or unkown. Added information on the
failure error codes.</span><o:p></o:p></p>
<p class="MsoNormal">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.
<span style="font-family:Wingdings"></span> <span style="color:#4EA72E">Since EU1 is now added to P5, it works. Added information on the failure error codes.<o:p></o:p></span></p>
<p class="MsoNormal">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.
<span style="font-family:Wingdings"></span> <span style="color:#4EA72E">RI1 added to P5, so it works. I believe this does not have impact on any other test (i.e. Plan Filters)<o:p></o:p></span></p>
<p class="MsoNormal">T_PES_011_3: I’d expect additionally error path 2.1 since the resource is unknown as well.
<span style="font-family:Wingdings"></span> <span style="color:#4EA72E">Added, it is 2,0. I use the comma to separate the Extra info index and secondary code. The dot is used in the index to refer to complex structures.
</span><span style="color:#FFC000">Question, P0 now exists as a plan, though with erroneous elements as validity fields. Shall we flag it as invalid due to its own errors?<o:p></o:p></span></p>
<p class="MsoNormal">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.
<span style="font-family:Wingdings"></span> <span style="color:#4EA72E">Should work now, RI1 is added to P5.<o:p></o:p></span></p>
<p class="MsoNormal">T_PES_012_3: I’d expect additionally error path 2.1 since the resource profile is unknown as well.
<span style="font-family:Wingdings"></span> <span style="color:#4EA72E">Added, it is 2,0.
</span><span style="color:#FFC000">Question, P0 now exists as a plan, though with erroneous elements as validity fields. Shall we flag it as invalid due to its own errors?<o:p></o:p></span></p>
<p class="MsoNormal">PECS<o:p></o:p></p>
<p class="MsoNormal">T_PECS_001_P0:<o:p></o:p></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal">GB: I have updated to 1.9,4 and 1.10,4.<o:p></o:p></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal"><span style="font-family:Wingdings;color:#4EA72E"></span><span style="color:#4EA72E"> This is an interesting point. Indeed, the validityStart and validityEnd are the 5<sup>th</sup> and 6<sup>th</sup> fields of the Plan information, what
is the 5<sup>th</sup> field of the Plan. I guess the error is on validityEnd, that is the 6<sup>th</sup> element, being the one not being after validityStart.<o:p></o:p></span></p>
<p class="MsoNormal">T_PECS_003_1:<o:p></o:p></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal">GB: 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></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal"><span style="font-family:Wingdings;color:red"></span><span style="color:red"> The P2 is changed to Terminated in T_PDS_005, so it is assumed that it is a plan available to the system. I have no problem to follow your logic, but I cannot
see within the PECS test where the plan is rejected. And since plans are distributed with PDS, this sets the test criteria. We agree to validate the different service areas uncorrelated, so we should not make assumptions either way,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red"><o:p> </o:p></span></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><span style="font-family:Wingdings"></span> <span style="color:#FFC000">
My former question applies: Should we use the error code 1 with extra info 1.5.6, 4 in any instance of P0?</span><o:p></o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><span style="font-family:Wingdings"></span> <span style="color:#FFC000">
My former question applies: Should we use the error code 1 with extra info 1.5.6, 4 in any instance of P0?</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">T_PECS_005_3: Expect the error path to be 2.1 for the first element of the second parameter.<o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:Wingdings"></span> <span style="color:#FFC000">
My former question applies: Should we use the error code 1 with extra info 2.5.6, 4 in any instance of P0?</span><o:p></o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><span style="font-family:Wingdings"></span> <span style="color:#FFC000">
My former question applies: Should we use the error code 1 with extra info 1.5.6, 4 in any instance of P0?</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">T_PECS_011_2:<o:p></o:p></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal">GB: 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></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal"><span style="font-family:Wingdings;color:#FFC000"></span><span style="color:#FFC000"> I believe you mean T_PECS_008. Still, there only P1 is deactivated. However, the subPlan1 contains AI7 that belongs to P6, that at the time is released.
So my assumption is that the subPlan1 is activated with this operation. Please, see page 3-44 section 3.7.5.13:<o:p></o:p></span></p>
<p class="Notelevel1"><span style="color:#FFC000">NOTE – The status of SubPlans is independent to that of Plans and a change in their activation status has no impact on the status of the Plan. It may impact the status of individual ActivityInstances,
which can be observed using the monitorPlanExecutionDetail operation.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><span style="color:#FFC000">Not sure what is 011_4, but if this for the subPlan0, this indeed does not exist. So it is correctly 1 and Extra info 1,0. Unless you assume that a subplan id is the first element of its list, then would be 1
with ExtraInfo 1.1, 0. Is a subplan a plan structure? If so, then it is the later. Even 1.1.2, 0 (see later) if we assume the second element of identity to be the affected one.<o:p></o:p></span></p>
<p class="MsoNormal">T_PECS_012_2:<o:p></o:p></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal">GB: 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></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal"><span style="font-family:Wingdings;color:#FFC000"></span><span style="color:#FFC000"> See my comments above. Let’s discuss Monday 17<sup>th</sup>.<o:p></o:p></span></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><span style="color:#FFC000">See comment before, agree if considered a plan as composite structure. In this case the passed element should be the identify (domain, key, version) and the failure shall be on key, so should be 1.1.2<o:p></o:p></span></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#FFC000">See comment before, agree if considered a plan as composite structure. In this case the passed element should be the identify (domain, key, version) and the failure shall be on key, so should be 1.1.2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">T_PECS_016_P0:<o:p></o:p></p>
<p class="MsoNormal">MW: Expect error codes (1.5.6, BAD_TIME) and (“1.10”, UNDEFINED) since status is TERMINATED<o:p></o:p></p>
<p class="MsoNormal">GB: 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></p>
<p class="MsoNormal">MW: 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></p>
<p class="MsoNormal"><span style="font-family:Wingdings;color:#FFC000"></span><span style="color:#FFC000"> Let’s address this on the 17ht teleconf.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="DE" style="font-size:12.0pt;color:black">From:
</span></b><span lang="DE" style="font-size:12.0pt;color:black">marvin.wittschen@dlr.de <marvin.wittschen@dlr.de><br>
<b>Date: </b>Monday, 3 February 2025 at 18:29<br>
<b>To: </b>Guillermo Buenadicha <Guillermo.Buenadicha@esa.int>, Dominik Marszk <Dominik.Marszk@esa.int>, Peter Van Der Plas <Peter.van.der.Plas@esa.int>, Cesar Coelho <Cesar.Coelho@ext.esa.int>, Christoph.Lenzen@dlr.de <Christoph.Lenzen@dlr.de>, Maria.Woerle@dlr.de
<Maria.Woerle@dlr.de>, luke.berry@gmv.com <luke.berry@gmv.com>, Rachel Jenkins <rjenkins@gmv.com>, eric.w.ferguson@jpl.nasa.gov <eric.w.ferguson@jpl.nasa.gov>, geoff.lochmaier@nasa.gov <geoff.lochmaier@nasa.gov>, David Frew <David.Frew@esa.int>, olly.page@cgi.com
<olly.page@cgi.com>, clement.hubin-andrieu@cnes.fr <clement.hubin-andrieu@cnes.fr><br>
<b>Cc: </b>moims-mp@mailman.ccsds.org <moims-mp@mailman.ccsds.org><br>
<b>Subject: </b>AW: Test Case specification V19<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hello Guillermo,</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><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:</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><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. </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><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,</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marvin</span><span lang="DE" style="font-size:12.0pt"><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</span></u><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo2"><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).</span><span lang="DE" style="font-size:12.0pt"><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</span></u><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_005_3: Expect error code to be 1.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_005_4: Expect error code to be 2.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_006_3: Expect error code to be 1.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PES_006_4: Expect error code to be 2.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l3 level1 lfo3"><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.</span><span lang="DE" style="font-size:12.0pt"><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</span></u><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_001_P0:
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<ul style="margin-top:0cm" type="disc">
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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?
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_003_1:
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<ul style="margin-top:0cm" type="disc">
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_011_2:</span><span lang="EN-US" style="font-size:12.0pt">
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<ul style="margin-top:0cm" type="disc">
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_012_2:
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<ul style="margin-top:0cm" type="disc">
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
</ul>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 level1 lfo4"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">T_PECS_016_P0:
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
<ul style="margin-top:0cm" type="disc">
<ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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 </span>
<span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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. </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l2 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></li></ul>
</ul>
<p class="MsoListParagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"> </span><span lang="DE" style="font-size:12.0pt"><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 lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> 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">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</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Marvin:</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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.
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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.</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
Regards!</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">G</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">-----------------------------------------------------------------------------</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Guillermo Buenadicha, SCI-S</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">O</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">E</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Euclid SOC
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Operations Coordinator</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">SCO-02 Technical Responsible</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">European Space Astronomy Centre (ESAC) ESA </span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Villanueva de la Cañada, Madrid, SPAIN</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Phone (34)
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">686 50 52 68</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span lang="DE" style="font-size:12.0pt"><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">guillermo.buenadicha@esa.int</span></a></span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">----------------------------------------------------------------------------</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">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><span lang="DE" style="font-size:12.0pt"><a href="mailto:dpo@esa.int"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">dpo@esa.int</span></a></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">).
</span><span lang="DE" style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
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 (dpo@esa.int).
</body>
</html>