Narrative:

ZMP was scheduled for eram (en route automation modernization) testing. The event occurred while the facility was in the middle of transitioning from darc/ebus (direct access radar channel/enhanced back-up surveillance) to eram. During the transition; I witnessed air carrier X flashing at me with FL370 in the flight plan; but FL350 in the mode C readout. I was busy switching back and forth between eram and ebus affecting other transition tasks. When I next looked at air carrier X; it was now in my airspace; still flashing me; with the same mismatched altitude information in the data block. At this point; because we were transitioning; it didn't occur to me that this was a deviation. Instead; I attempted to /ok the data block so I could account for the aircraft as part of the transition process. Because eram has slightly different functionality; the normal entry for /ok didn't work. I had to make several attempts; and ask the eram sme in the area how to /ok. I accomplished that; put FL350 in the data block; and moved on to other transitional activities. A couple minutes later; I confirmed that air carrier X was not yet on my frequency; and called sector 29 to have them transfer communications again. The aircraft arrived on my frequency; and the event was over. Recommendation; the primary cause of this deviation was the eram transition. Too many things were going on; and we were switching back and forth between systems and were distracted from the traffic flow. That said I do not believe safety was compromised because the aircraft were always displayed. In the future; eram transitions should be limited to periods of low traffic rather than during moderate traffic levels.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP controller described air space incursion event during ERAM testing.

Narrative: ZMP was scheduled for ERAM (En Route Automation Modernization) testing. The event occurred while the facility was in the middle of transitioning from DARC/EBUS (Direct Access Radar Channel/Enhanced Back-Up Surveillance) to ERAM. During the transition; I witnessed Air Carrier X flashing at me with FL370 in the flight plan; but FL350 in the Mode C readout. I was busy switching back and forth between ERAM and EBUS affecting other transition tasks. When I next looked at Air Carrier X; it was now in my airspace; still flashing me; with the same mismatched altitude information in the data block. At this point; because we were transitioning; it didn't occur to me that this was a deviation. Instead; I attempted to /OK the data block so I could account for the aircraft as part of the transition process. Because ERAM has slightly different functionality; the normal entry for /OK didn't work. I had to make several attempts; and ask the ERAM SME in the area how to /OK. I accomplished that; put FL350 in the data block; and moved on to other transitional activities. A couple minutes later; I confirmed that Air Carrier X was not yet on my frequency; and called Sector 29 to have them transfer communications again. The aircraft arrived on my frequency; and the event was over. Recommendation; the primary cause of this deviation was the ERAM transition. Too many things were going on; and we were switching back and forth between systems and were distracted from the traffic flow. That said I do not believe safety was compromised because the aircraft were always displayed. In the future; ERAM transitions should be limited to periods of low traffic rather than during moderate traffic levels.

Data retrieved from NASA's ASRS site as of April 2012 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.