<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:"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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoToc1, li.MsoToc1, div.MsoToc1
{mso-style-priority:39;
margin-top:6.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;
text-transform:uppercase;}
p.MsoToc1CxSpFirst, li.MsoToc1CxSpFirst, div.MsoToc1CxSpFirst
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:6.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;
text-transform:uppercase;}
p.MsoToc1CxSpMiddle, li.MsoToc1CxSpMiddle, div.MsoToc1CxSpMiddle
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;
text-transform:uppercase;}
p.MsoToc1CxSpLast, li.MsoToc1CxSpLast, div.MsoToc1CxSpLast
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;
text-transform:uppercase;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
{mso-style-priority:39;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc2CxSpFirst, li.MsoToc2CxSpFirst, div.MsoToc2CxSpFirst
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc2CxSpMiddle, li.MsoToc2CxSpMiddle, div.MsoToc2CxSpMiddle
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc2CxSpLast, li.MsoToc2CxSpLast, div.MsoToc2CxSpLast
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
{mso-style-priority:39;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc3CxSpFirst, li.MsoToc3CxSpFirst, div.MsoToc3CxSpFirst
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc3CxSpMiddle, li.MsoToc3CxSpMiddle, div.MsoToc3CxSpMiddle
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
p.MsoToc3CxSpLast, li.MsoToc3CxSpLast, div.MsoToc3CxSpLast
{mso-style-priority:39;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
mso-add-space:auto;
mso-para-margin-top:.02gd;
mso-para-margin-right:0in;
mso-para-margin-bottom:0in;
mso-para-margin-left:2.0in;
mso-para-margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Arial",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1527864073;
mso-list-type:hybrid;
mso-list-template-ids:1931484188 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A">Dear Data Ladies and Gentlemen,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A">In preparation for today’s ATS Wind Web Conference, the following inputs have been received from Rochelle Perera (The Boeing Company), Dr. Christine Haissig (FAA Consultant) and
Tom McGuffin (Honeywell).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A">The WebEx conference invitation can be found at the end of the email string below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"Arial",sans-serif;color:#44546A">These inputs for Draft 3 of Supplement 5 to
<b>ARINC Specification 622 -</b> </span><i><span style="font-family:"Arial",sans-serif">ATS Data Link Applications over<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif">ACARS Air-Ground Networks
</span></i><span style="font-family:"Arial",sans-serif;color:#44546A">will be discussed during today’s web conference, when we plan to further develop the draft 3 strawman.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">…Multiple FIMS makes it more complex.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you are going to define multiple FIMs then you need to define how to determine which one is the master. It needs to be standardized so every CMU uses the same logic and works with every FIM.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Similar to the FMS logic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Do we really need three FIMS?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Suggested changes to section titles to improve consistency<o:p></o:p></span></p>
<p class="MsoToc1" style="margin-left:1.0in;mso-add-space:auto"><a href="#_Toc466637557">6.0<i><span style="font-family:"Calibri",sans-serif;color:windowtext;text-transform:none">
</span></i>Air Traffic Services Wind<i><span style="color:windowtext">.. 50</span></i></a><span style="font-family:"Calibri",sans-serif;text-transform:none"><o:p></o:p></span></p>
<p class="MsoToc2CxSpFirst" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637558">6.1<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Notional Architecture<i><span style="color:windowtext">. 50</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc2CxSpLast" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637559">6.2<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Air Traffic Services Wind <span style="color:red">Uplink </span>Message Types<i><span style="color:windowtext">. 50</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc3CxSpFirst" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637560">6.2.1<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Uplink Wind Data for FMS (PWI)<i><span style="color:windowtext"> 50</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc3CxSpLast" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637561">6.2.2<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Uplink Wind Data for FIMS (PWF):<i><span style="color:windowtext"> 51</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc2" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637562">6.3<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i><i><span style="font-family:"Calibri",sans-serif;color:red">Air Traffic Services</span></i><i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i><i><span style="font-family:"Calibri",sans-serif;color:red">Wind </span>
</i>Downlink Message Types<i><span style="color:windowtext">. 51</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc3CxSpFirst" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637563">6.3.1<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Responses for PWI Uplink<i><span style="color:windowtext">. 52</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoToc3CxSpLast" style="mso-margin-top-alt:.2pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;mso-add-space:auto">
<a href="#_Toc466637564">6.3.2<i><span style="font-family:"Calibri",sans-serif;color:windowtext">
</span></i>Responses for PWF Uplink<i><span style="color:windowtext">. 52</span></i></a><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in"><a href="#_Toc466637565">6.4<i><span style="color:windowtext">
</span></i>Air Traffic Services Wind Uplink Message Routing<i><span style="color:windowtext"> 52</span></i></a><span style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"Arial",sans-serif;color:#548DD4">Tom McGuffin</span></b><span style="font-family:"Arial",sans-serif;color:#548DD4"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#548DD4">Honeywell Aerospace - Electronic COE<br>
Datalink System Engineer<br>
<br>
</span><span style="font-family:"Arial",sans-serif;color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><b>From:</b> Perera, Rochelle E [<a href="mailto:Rochelle.E.Perera@boeing.com">mailto:Rochelle.E.Perera@boeing.com</a>]
<br>
<b>Sent:</b> Tuesday, November 29, 2016 5:09 PM<br>
<b>To:</b> Christine Haissig <<a href="mailto:christine.haissig@ix.netcom.com">christine.haissig@ix.netcom.com</a>>; Nguyen, Dung Q <<a href="mailto:dung.q.nguyen@boeing.com">dung.q.nguyen@boeing.com</a>><br>
<b>Cc:</b> Jose Godoy <<a href="mailto:jose.godoy@sae-itc.org">jose.godoy@sae-itc.org</a>><br>
<b>Subject:</b> RE: Comments/Questions on Latest Draft of ARINC 622 for ATS Winds<span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Christine,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Thanks for reviewing it. I was out on vacation so didn’t get a chance to respond till now. I have some comments below and have attached a working copy with the updates mentioned below. We can discuss this
tomorrow. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">Rochelle Perera</span></b><span style="color:#1F497D">
<br>
</span><span style="color:gray">Flight Management Systems</span><span style="color:#1F497D">
</span><span style="color:gray">| The Boeing Company<br>
Datalink<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:gray">Phone: 425.237.6306 <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:gray"><a href="mailto:rochelle.e.perera@boeing.com">rochelle.e.perera@boeing.com</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Rochelle/Dung:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I was reviewing the latest draft of ARINC 622 in preparation for the meeting on the 30<sup>th</sup> and have a few comments/questions<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I noticed that the version that Jose sent out via e-mail reverted to the older version of Figure 6.1, where we don’t show PWI going into the FIMS. I know there was a version at one time with the figure that Rochelle updated. We’ll want
to make sure that we have the updated figure in the version that goes forward.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">REP>> You’re correct, it seems to have an older version of the picture. I updated it in the attached copy.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>I noticed that PWF is not defined in Appendix A Acronyms and Glossary.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">REP>> Good catch! I updated this as well.
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Section 6.2.1 describes the PWI uplink for the FMS and Section 6.2.2 describes the PWF uplink for FIMS. Neither section addresses the PWI uplink for FIMS. It seems that we need some text describing that piece. Do you recommend modifying
Section 6.2.1 to discuss PWI for both FMS and FIMS? Or modifying Section 6.2.2 to add PWI for FIMS? Or something else? Similarly, section 6.3.1 discusses the responses to the PWI uplink assuming that it is received by the FMS but does not cover responses
to the PWI uplink by the FIMS.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">REP>> I added the PWI IMI to the FIMS section. For the response section, I just changed the titles to Responses from the FMS and Responses from the FIMS. The basic difference in response sets really isn’t tied
to the IMIs, it’s tied to the systems since they will process the winds slightly differently.
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>It isn’t clear to me how the ground system will specify whether the PWI is intended for the FMS or FIMS and how the CMU/CMF will know whether the PWI uplink is intended for the FMS or FIMS. <o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">REP>> The ground system will address this via the label/sublabel. The active route winds going to the FMS will have an IMI of PWI but a label/Sublabel of HI/MD. The active route winds going to the FIMS
will also have an IMI of PWI but a label/sublabel of HI/ID. So when the uplink gets to the CMU/CMF, it won’t see the IMI portion, it’ll just see the label/sublabel and will route it accordingly. Then the end system (either the FMS or FIMS) will be the one
that processes the IMI and the data associated with it. <o:p></o:p></span></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>In section 6.3.2 describing the responses to the PWF Uplink, I suggest modifying RESPWF/AK to specifically state traffic winds, as in “ATS traffic winds acknowledge……”. Similarly for RESJPWF “ATS traffic winds rejection by FIMS”.<o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:#1F497D">REP>> I modified this section to include the active winds for the FIMS. Basically I added the words “active route” for those associated with PWI and “target route” for those associated with PWF. Since
we have used the terminology of “target route” previously in document I’d like to keep it consistent and use those words for PFW here too. Let me know what you think.
<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>In section 6.5.2, the first bullet says “PWI: Wind message for active route in FMS”. Suggest modifying this to make clear PWI is used for both the FMS and FIMS, such as “PWI: Wind message for active route in FMS and in FIMS.”<o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">REP>> I changed it to say “PWI: Wind message for active route”. That way it applies to all current (and any future) systems which may want to use active winds without specifying just
the FMS. Since we’ve noted in other sections that the PWI IMI could go to the FIMS, I think this should cover all our bases but leave it generic enough for any future uses.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">8.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>In section 6.6.2, the first bullet says “PWI: Used for active route”. Suggest modifying this to make clear PWI is used for both the FMS and FIMS, such as “PWI: Use for active route in FMS and in FIMS.”<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="color:#1F497D">REP>>I made some slight adjustments but it agrees with the changes in section 7 (basically took out any reference to which system/application hosts the active/target routes. This will
fit whatever architecture or implementation people come up with. <o:p></o:p></span></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">I’d appreciate your thoughts on the items I’ve listed, especially items 3 and 4. I don’t have good insight on the best way to specify PWI for FMS versus PWI for FIMS.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">Thanks,<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">Christine<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS";color:#336699">Dr. Christine M. Haissig<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS";color:#336699">FAA Surveillance Broadcast Systems Support<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"Comic Sans MS";color:#336699">Christine Haissig Consulting LLC<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS";color:#336699"><a href="mailto:christine.haissig@ix.netcom.com"><span style="color:#336699">christine.haissig@ix.netcom.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS";color:#336699">612 208 5430 (mobile)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS";color:#336699">952 474 0318 (land line</span><span style="font-family:"Comic Sans MS";color:#264D73">)</span><span style="font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:18.0pt;font-family:"Calibri",sans-serif;color:#44546A">You are invited to attend the following AEEC Web Conference:</span></b><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#44546A"><br>
<br>
Supplement 5 to ARINC Specification 622 (add ATS Winds)</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"><br>
Wednesday, November 30, 2016 <br>
11:00 am | Eastern Standard Time (New York, GMT-05:00) | 2 hrs <br>
<br>
JOIN WEBEX MEETING <br>
<a href="https://sae.webex.com/sae/j.php?MTID=m1578f97861473592159debd80cce27e1" target="_blank">https://sae.webex.com/sae/j.php?MTID=m1578f97861473592159debd80cce27e1</a>
<br>
Meeting number: 621 088 235 <br>
Meeting password: 20Nov2016 <br>
<br>
JOIN BY PHONE <br>
1-866-469-3239 Call-in toll-free number (US/Canada) <br>
1-650-429-3300 Call-in toll number (US/Canada) <br>
Access code: 621 088 235 <br>
<br>
Global call-in numbers: <br>
<a href="https://sae.webex.com/sae/globalcallin.php?serviceType=MC&ED=501346057&tollFree=1" target="_blank">https://sae.webex.com/sae/globalcallin.php?serviceType=MC&ED=501346057&tollFree=1</a>
<br>
<br>
Toll-free dialing restrictions: <br>
<a href="https://www.webex.com/pdf/tollfree_restrictions.pdf" target="_blank">https://www.webex.com/pdf/tollfree_restrictions.pdf</a>
<br>
<br>
Add this meeting to your calendar (Cannot add from mobile devices): <br>
<a href="https://sae.webex.com/sae/j.php?MTID=ma2cfe4eef3d856d61f0a3c39a2dfa38f" target="_blank">https://sae.webex.com/sae/j.php?MTID=ma2cfe4eef3d856d61f0a3c39a2dfa38f</a>
<br>
<br>
</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:#833C0B;letter-spacing:.25pt">José Godoy<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#005195">ARINC Industry Activities (IA)</span></b><span style="font-size:11.0pt;color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#005195">An SAE-ITC Industry Program</span></b><span style="font-size:11.0pt;color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#616365">cell</span></b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">
</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#616365">+1 443-534-</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">8925<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">Ref:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">From:
<a href="mailto:Moin.Abulhosn@faa.gov">Moin.Abulhosn@faa.gov</a> [<a href="mailto:Moin.Abulhosn@faa.gov">mailto:Moin.Abulhosn@faa.gov</a>]
<br>
Sent: Tuesday, November 29, 2016 4:03 PM<br>
To: Jose Godoy <<a href="mailto:jose.godoy@sae-itc.org">jose.godoy@sae-itc.org</a>>;
<a href="mailto:Eldridge.Frazier@faa.gov">Eldridge.Frazier@faa.gov</a><br>
Subject: RE: Supplement 5 to ARINC Specification 622 (add ATS Winds)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">Jose, Can you please send me an invite or a telecom number to call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">Moin Abulhosn, Aerospace Engineer AIR 132<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">FAA AFSCME Local 1653 AVS VP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A">(202) 267 8571.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#44546A"><o:p> </o:p></span></p>
</div>
<br>
<br>
Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may
contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message
in error, please contact the sender and delete it from your computer.
</body>
</html>