NATCA Bookshelf

• ER 183395 Changes to FALCON: The team continued the discussion of the use case, and the desired behavior is to bring FALCON up to date with current ERAM CHI and keep it current as new ERAM changes are implemented. The task team will be updating the use case for further team discussion. • A190040 EDST Toolbar and A190175 EDST Display Offset: The awareness items for these issues were discussed and reviewed. All sites transitioning from an EAD to an EAE system will need to use the steps in both awareness items and follow SSM-ERAM-261. Once both channels are on an EAE release the situation no longer occurs. Due to only being a one-time event, it was decided to abandon a software fix. • STARS Enhancement 2: The team discussed and agreed to changes for the 4 th Line use case and functionality. A matrix capturing Point Out behavior was reviewed. The intent of the matrix is to ensure that the STARS and ERAM behavior in all instances of Point Outs is captured. Additional work is still needed, and the final solutions will be reviewed by the user team. • PDRR/ABRR § A briefing on the status of PDRR/ABRR was given. All sites are ABRR-enabled, and all but two sites are PDRR-enabled. § ER 176378 2, flights with the same route show different protected segments: A task team is working on the issue and the use case will be presented next month. § ER 187546, Invalid ABRR Reroute Uplink: Is being reassigned to the DataComm team for input and direction. § ER 187829: Applying TFM reroute past divergent fix causes AM change destination menu to appear and is being reassigned to Typing Buffer task team for solutions. § ER 185287, Cyan Coding: The team discussed and reached consensus on the problem statement, "Its desired behavior is if there is a TFMS-generated reroute that extends beyond the ERAM bounding box, TFMS should reject the reroute." The problem statement will be sent to SLE for processing. § ER 184496, ABRR/PDRR Restricted Airspace: The team discussed the current version of the use case. Its desired behavior is to provide the capability via adaptation to designate adapted routes that are never overridden by PDRR/ABRR-protected segments. The use case was sent to the team for review and will be discussed during the next team telcon. • System Enhancement § ER 195554, AHI and Point Outs: The draft problem statement was discussed and, the desired behavior is to insert an AHI (Auto Handoff Inhibit) for an aircraft from an initiating sector to the receiving sector after the receiving sector has approved an automated point out. An updated version of the problem statement will be discussed at the next meeting.

• Cover