flight identification) (FIM target aircraft recommended changes and will take routing) TERMINATE AT (position ATW) this back to the FIM Tiger Team. ASSIGNED SPACING INTERVAL PENDING Given the deletion of a number of “EXPECT” messages due to their of operational use’, ‘lack is there really any perceived use for this message element? I can’t really see any controller going through the effort of constructing this message when it is just an expectation… Table A5-15 47 AW IMMEDIATELY Duplicate Closed [Editors 21 – comment with cmt#33? Suggest delete this proposed message element. Its only real use appears to be to append it to a It can be completely transparent for the small number of message elements (e.g. controller depending of the CLIMB TO [level]) to create a message similar implementation. Concatenations could to a deleted message element be and proposed by “pre-formatted” CLIMB TO [level]”!!! the system according to the operational “IMMEDIATELY context. However the aspect is lost “immediately” when you consider the extra time required to [OPLINKP WG/WHL/4 21 – find the little used March]: “IMMEDIATELY” message element to append to the CLIMB TO Agree with Editors above. See also [level] element! status of Comment 32. There can be no automation associated with the IMMEDIATELY message element, whereas there couple potentially be with an IMMEDIATELY CLIMB TO [level] message element
flight identification) (FIM target aircraft routing) TERMINATE AT (position ATW) ASSIGNED SPACING INTERVAL PENDING Given the deletion of a number of “EXPECT” messages due to their ‘lack of operational use’, is there really any perceived use for this message element? I can’t really see any controller going through the effort of constructing this message when it is just an expectation… recommended changes and will take this back to the FIM Tiger Team. Table A5-15 47 AW IMMEDIATELY Suggest delete this proposed message element. Its only real use appears to be to append it to a small number of message elements (e.g. CLIMB TO [level]) to create a message similar to a deleted message element “IMMEDIATELY CLIMB TO [level]”!!! However the “immediately” aspect is lost when you consider the extra time required to find the little used “IMMEDIATELY” message element to append to the CLIMB TO [level] element! There can be no automation associated with the IMMEDIATELY message element, whereas there couple potentially be with an IMMEDIATELY CLIMB TO [level] message element [Editors – 21 Duplicate comment with cmt#33? It can be completely transparent for the controller depending of the implementation. Concatenations could be “pre-formatted” and proposed by the system according to the operational context. [OPLINKP WG/WHL/4 – 21 March]: Agree with Editors above. See also status of Comment 32. Closed
OPLINKPWGWHL-4-APR.docx