| #1 | |||||
|
|
ERAM
Posted: 02-16-2010, 10:53 PM is there any news on eram, have they tried running it anymore at salt lake?
|
||||
|
|
|
| #2 | |||||
|
|
Re: ERAM
Posted: 02-16-2010, 11:01 PM Good blog about the testing going on, which has now moved to ZMP due to the Olympic traffic effecting Seattle Center.
ATC Freqs ? Observations of an FAA Air Traffic Controller: Some things reported as work arounds/ problems (from the blog): Here are a few of the items on the ZLC Mitigation List with the workarounds 1. An interim altitude prevents an auto handoff to a TRACON facility ? manual handoff required 2. Mode C altitude may not replace a reported altitude ? manually enter altitude 3. PVD data blocks sent to adjacent facilities and that are redirected to another sector will not display ? manually coordinate 4. Intra-facility (in-house) interim altitudes can be changed without track control (after handoff) without override (/OK) 5. Interim altitudes cannot be entered on your own data blocks ? make override entry (/OK) to get data block control, or handoff the data block to adjacent sector, then have them hand back to you to get data block control 6. Under certain circumstances handoffs to adjacent facilities will not handoff to the proper sector ? manually direct handoff to proper sector 7. Data blocks may be missing 8. Failures of display when invoking preference settings when the display has empty constant range readout (CRR) groups 9. Display failures when modifying existing annotations made using draw function - create new drawings instead of modifying existing one 10. Adjacent sector boundaries are not displayed The ZMP ERAM Problem Report (PR) list includes the following notables: 1. PAR (Preferential Arrival Routes) don?t apply properly 2. Data blocks way behind (70-170 miles) the route of flight 3. Random Unsuccessful Transmission Messages (UTMs) to previous facility or facilities near flight plan route 4. Bad Route from template or trial plan 5. UTMs on flight plans transitioning from ZMP to Chicago Center (ZAU) and then back to ZMP, ZAU unable to handoff data block 6. Auto-delete drops data block and remove strip (RS) on flight plan while flight still in sector 7. Incorrect route processing 8. Flight plan route off by 30 miles laterally resulting in dual track control between ZMP and Kansas City Center (ZKC) 9. Data block auto-delete when trying to take track control 10. Inconsistent track control assignment 11. Delay in remove strip (RS) processing ? can take 39 minutes 12. General Information (GI) message reprints 10 days later |
||||
|
|
| #3 | |||||
|
|
Re: ERAM
Posted: 02-16-2010, 11:57 PM By far my favorite. And by favorite I mean, most horrifying:
Quote:
|
||||
|
|
| #4 | |||||
|
|
Re: ERAM
Posted: 02-19-2010, 09:30 AM
You'd get altitude info, as it would still display as a limited data block.
|
||||
|
|
| #5 | |||||
|
|
Re: ERAM
Posted: 02-19-2010, 12:42 PM Well, it sounds like ERAM is a resounding success.
|
||||
|
|
| #7 | |||||
|
|
Re: ERAM
Posted: 02-19-2010, 11:25 PM |
||||
|
|