Narrative:

At XA30; ZBW transitioned to the back-up system called 'east-bus.' this is a new all software tracking program that's been recently introduced to the operational environment. Just before XB00; air carrier X departed pwm. (ZBW operates pwm airspace on this shift.) air carrier X was pre-loaded into the 'flight list' when the back-up system was activated. However; we were unable to track air carrier X because of a 'bug' in the software that caused us to be locked out of using pre-loaded call signs and codes. Meaning that every aircraft we need to initiate a track on needs a new code and a modified call sign in order to get the computer to track the code. Air carrier X (abc XXXX) became air carrier X (abd XXXX). Not exactly accurate. This problem presented an enormous distraction because normal inputs did not work. The problem repeated when air carrier Y from montreal center approached united states airspace. The NAS operations engineer came down to the area to see if he could troubleshoot the problem; but quickly realized this is yet another 'bug' as he called it. I asked why this system (that he refuses to certify; by the way) is allowed to operate in the live ATC environment without being adequately tested. The answer is typical government -- somebody at or near the top is pushing this 'all software' back-up system and; therefore; it is becoming a reality with no proven track record. This is the system that runs in the backgnd of the host computer. If host ever fails at an FAA center; there's no telling what might happen.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW CTLR EXPRESSED CONCERN REGARDING THE NEWLY DEPLOYED 'E-BUS' HOST SOFTWARE BACK-UP SYS AND SEVERAL INSTANCES OF INCORRECT CALL SIGNS.

Narrative: AT XA30; ZBW TRANSITIONED TO THE BACK-UP SYS CALLED 'E-BUS.' THIS IS A NEW ALL SOFTWARE TRACKING PROGRAM THAT'S BEEN RECENTLY INTRODUCED TO THE OPERATIONAL ENVIRONMENT. JUST BEFORE XB00; ACR X DEPARTED PWM. (ZBW OPERATES PWM AIRSPACE ON THIS SHIFT.) ACR X WAS PRE-LOADED INTO THE 'FLT LIST' WHEN THE BACK-UP SYS WAS ACTIVATED. HOWEVER; WE WERE UNABLE TO TRACK ACR X BECAUSE OF A 'BUG' IN THE SOFTWARE THAT CAUSED US TO BE LOCKED OUT OF USING PRE-LOADED CALL SIGNS AND CODES. MEANING THAT EVERY ACFT WE NEED TO INITIATE A TRACK ON NEEDS A NEW CODE AND A MODIFIED CALL SIGN IN ORDER TO GET THE COMPUTER TO TRACK THE CODE. ACR X (ABC XXXX) BECAME ACR X (ABD XXXX). NOT EXACTLY ACCURATE. THIS PROB PRESENTED AN ENORMOUS DISTR BECAUSE NORMAL INPUTS DID NOT WORK. THE PROB REPEATED WHEN ACR Y FROM MONTREAL CTR APCHED UNITED STATES AIRSPACE. THE NAS OPS ENGINEER CAME DOWN TO THE AREA TO SEE IF HE COULD TROUBLESHOOT THE PROB; BUT QUICKLY REALIZED THIS IS YET ANOTHER 'BUG' AS HE CALLED IT. I ASKED WHY THIS SYS (THAT HE REFUSES TO CERTIFY; BY THE WAY) IS ALLOWED TO OPERATE IN THE LIVE ATC ENVIRONMENT WITHOUT BEING ADEQUATELY TESTED. THE ANSWER IS TYPICAL GOV -- SOMEBODY AT OR NEAR THE TOP IS PUSHING THIS 'ALL SOFTWARE' BACK-UP SYS AND; THEREFORE; IT IS BECOMING A REALITY WITH NO PROVEN TRACK RECORD. THIS IS THE SYS THAT RUNS IN THE BACKGND OF THE HOST COMPUTER. IF HOST EVER FAILS AT AN FAA CTR; THERE'S NO TELLING WHAT MIGHT HAPPEN.

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