Narrative:

We were testing eram (en route automation modernization). Aircraft X departed bend oregon requesting VFR services; I gave him a code and it tracked up where as his data block was in conflict with his own VFR data block. For a moment; it was a confusing situation where as I thought aircraft X had traffic at the same altitude. This takes my attention away from other duties that I would normally not have to worry about. Recommendation; eram is not ready for live traffic. Too many distractions that make our job more complex. There are so many unknown issues that are associated with eram; that we are finding out for the first time; every time we plug in. Delay the implementation of eram until all of the critical and high issues have been fixed.

Google
 

Original NASA ASRS Text

Title: ZSE Controller described an event during ERAM testing when a target conflicted with itself suggesting implementation of ERAM should be delayed until critical equipment anomalies have been fixed.

Narrative: We were testing ERAM (En Route Automation Modernization). Aircraft X departed Bend Oregon requesting VFR services; I gave him a code and it tracked up where as his data block was in conflict with his own VFR data block. For a moment; it was a confusing situation where as I thought Aircraft X had traffic at the same altitude. This takes my attention away from other duties that I would normally not have to worry about. Recommendation; ERAM is not ready for live traffic. Too many distractions that make our job more complex. There are so many unknown issues that are associated with ERAM; that we are finding out for the first time; every time we plug in. Delay the implementation of ERAM until all of the critical and high issues have been fixed.

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.