140 likes | 267 Views
Sub-group Status report Comments review OSA & OPA. Plenary #9 THU 14 Dec09 Kathy de Vito/Wim Brondsema. OSA Comments review. CPDLC 4DTRAD. CPDLC-OSA. New comment for ENV. CPDLC - OSA Comment 139: Inconsistency btwn msgs/sector hr in OSA and ENV section/Table 3-2. Conclusion:
E N D
Sub-group Status reportComments review OSA & OPA Plenary #9 THU 14 Dec09 Kathy de Vito/Wim Brondsema
OSA Comments review CPDLC 4DTRAD
New comment for ENV • CPDLC - OSA Comment 139: • Inconsistency btwn msgs/sector hr in OSA and ENV section/Table 3-2. • Conclusion: • Problem is in ENV/Table 3-2: # of ATC Comms transactions/service Hr wrongly calculated from “OSA-Sector Density” slides (John) • Action: KdV to make new comment on ENV • Also understood that flight duration in TMA has changed to 8.4 min? Impacts OSA • Plenary agreed to use flight duration of 5.1 min. • Action: KdV to write new commenton ENV
Issue Latency Time Check (LTC) • Setting of ‘LTC-value’ (air & gnd): Safety critical SR LTC-value for AC and Gnd is a local issue for AC, LTC-value uplinked as system msg • Assurance of LTC value reception to be provided to ATCO • Proposed to use LACK Agreed by Plenary. • Q: What if LACK has not been received? • Use a default value, set in AC system at power up? Or • Resending of the system msg (max 3 attemtps) • Plenary agreed to go with a default value of 40s in AC system at power up, which is modified during the flight, using the sys msg. • Action Fred: Put 40s as starting value in INTEROP
OPA Comments review CM, CPDLC, 4DTRAD, DOTIS
Showstopper comment 101 • Comment related to ENV/OSD/OPA • Before validation, some guidance needed on use of RCP types/TTs times against ATS Function in different Oper Env (APT, ER, TMA). • Discussed in OPA/OSA SG drafted some Guidance • TBD, where to incorporate the guidance best: • ENV section? • Plenary agreed: Temporarily leave it in OPA
Summary • Happy with the result: • Good discussions • For all difficult comments resolution is known: Processing off-line • Open cmnts (new + existing) easy to solve: Processing off-line • Comment round resulted in a more robust SPR • Actions: • Solve remainder of comments and work out resolutions in OSA & OPA • 2 Telcons scheduled in 1st/2nd wk Jan ’10 • Line up work with format used in GOLD as much as possible • Extract SRs & PRs for integration into OSDs of ISPR-vH • Final integration into SPR-vH during Editor’s meeting: 2nd wk Jan’10