Summary of the First Meeting Special Committee 227 ... - RTCA

concern that we don’t have momentum yet and think a 2 nd meeting soon is appropriate before we
go to a 3 month cycle. (JamesN) (General agreement that this is a good suggestion.)
concern that Europe may need some time to get new scope added to WG85 to support joint
activities. (Sylvain)
SC214 Plenary meetings this year are June 4-8 and Dec 10-14. (MikeJ)
Meeting a 15 month cycle will be a lot of work. This is our big chance to open up the box and fix
it, and we don’t want to miss the chance. Mark H suggested the committee go to 5 day meetings.
The end date is chosen mainly to allow interaction and influence to the other active standards, in
particular SC214 and SC186. The nav standard publication may be able to be delayed some, but
we must work to ensure the collaboration with SC214 and SC186 occurs before they publish.
(Jarrett)
The committee agreed to 5 day meetings to support the current document due dates. In light of the plan to
have a harmonized activity with a re-tasked WG85, meetings will also be planned in European venues.
When this will take place will depend on the speed in which EUROCAE changes to the WG85 terms of
reference are approved and navigation system specialists and experts can be found to participate in
WG85.
2 nd meeting May 7-11, after that a three month interval as well as meetings in Europe is likely.
3 rd meeting July 30 – Aug 3, tentatively, possibly Toulouse.
Part of our charter from the ATMAC/NAC is to find and resolve gaps in the other activities. We need to
study the operational concepts they are working towards and buy in to them or take issue with them. The
TOps Concept of Use contained in the JPDO Aircraft WG’s Avionics Roadmap will be used on the US
side.
Dave re stated that the committee has 2 main tasks, fixing what is there, and adding new capabilities (4D
TBO). But, we need to be careful about splitting into sub-groups to ensure that we keep a critical mass of
expertise working on both aspects. For now we will plan to stay as one group. How this affects the
current Terms of Reference is not clear. However, what is clear is that for now the June 13 date is firm
for the efforts for trajectory operations with regard to navigation function, data and interfaces associated
with SC214 and SC186. The MASPS update/fix effort remains consistent with the terms of reference as
well and will continue. The magnitude of updates may lead to a different end date. However, until we
know better, i.e. at the next meeting, it is hard to say what it will be. The committee agreed that we will
stay with the current TORs for now.
A question was raised with regard to FMS specification efforts at AEEC for ARINC 702A. It was
pointed out that the ARINC characteristic contains a lot of installation and interface oriented guidance
and requirements. And there are areas that appear to set design/implementation that overlap what is
contained in the MASPS. For now the focus is with the MASPS/MOPS and coordination with AEEC
will follow as appropriate.
Sam: SAI has deferred opening up ARINC 702 because it was too much to be done to do now. Their
focus will be on 660A.
A number of the committee members commented on the need for broader subject matter expertise for this
activity, which proved to be part of the reason for the success and acceptance of the SC-181/WG-13
MASPS. In particular, air traffic control was mentioned. Jarrett L will coordinate in the FAA to
identify experts who will participate and support this effort. There will be outreach to other areas as well.
19