Narrative:

Aircraft X was routed via an RNAV arrival. A large force exercise was in place with multiple hot airspaces covering over half of the sector. Because of this; aircraft were being rerouted via unusual routes and getting opposite direction routes from adjacent facilities around the airspace and along an adjacent sector. Aircraft X was initially on a vector around the airspace and then direct to a fix where he would have needed a point out to an adjacent sector.however; the radar data block flashed at that sector and I took it back. This; of course; puts a carrot symbol in the time shared block next to the computer identification (cid); but I did not think about it at the time. I pointed out the aircraft to the sector at some point after that. Shortly thereafter; aircraft X violated a sectors airspace in the next facility. The handoff position trainee on sector took a call from the facility and informed me to ship the aircraft to them. The handoff position trainer noticed the aircraft was not handed off. I then handed the data block of the aircraft to the next facility and transferred communications. I was simply busy and did not notice the carrot in the data block (evidently neither did the training team).partly this was just a missed handoff. However; I do take issue with the new placement of the carrot (^) next to and time shared in the en route automation modernization (eram) data block. I haven't had an event like this to voice my concern; but the new placement is much harder to discern and easy to miss; particularly when it is time shared with an 'right.' when busy; it is easy to see any character in the data block and mistake a '^' for an 'right.' it has happened to me frequently since the change. The carrot above the call sign was much easier to see and much more salient.

Google
 

Original NASA ASRS Text

Title: ZMP Center Controller reported an aircraft had not been handed off to the adjacent facility due to new symbology in Center radar data tags.

Narrative: Aircraft X was routed via an RNAV Arrival. A large force exercise was in place with multiple hot airspaces covering over half of the sector. Because of this; aircraft were being rerouted via unusual routes and getting opposite direction routes from adjacent facilities around the airspace and along an adjacent sector. Aircraft X was initially on a vector around the airspace and then direct to a fix where he would have needed a point out to an adjacent sector.However; the radar data block flashed at that sector and I took it back. This; of course; puts a carrot symbol in the time shared block next to the Computer Identification (CID); but I did not think about it at the time. I pointed out the aircraft to the sector at some point after that. Shortly thereafter; Aircraft X violated a sectors airspace in the next facility. The Handoff position trainee on sector took a call from the facility and informed me to ship the aircraft to them. The Handoff position trainer noticed the aircraft was not handed off. I then handed the data block of the aircraft to the next facility and transferred communications. I was simply busy and did not notice the carrot in the data block (Evidently neither did the training team).Partly this was just a missed handoff. However; I do take issue with the new placement of the carrot (^) next to and time shared in the En Route Automation Modernization (ERAM) data block. I haven't had an event like this to voice my concern; but the new placement is much harder to discern and easy to miss; particularly when it is time shared with an 'R.' When busy; it is easy to see any character in the data block and mistake a '^' for an 'R.' It has happened to me frequently since the change. The carrot above the call sign was much easier to see and much more salient.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.