Narrative:

This is being filed not only for this flight, but all flts this morning on this sector that received reroute to ord. The routing was from various vors to J134, J105 to bdf, per ATC advisory 040. Using flight planning software this was not possible and never is possible. Also, it did not accept the SID from las, the AACES2 SID which we are to use. I notified flight planning, it people, and mr X, came down and sat with me and was surprised the system did not work with the routing, nor does itaccept sids and or a combination of any NAVAID, jetway, and or intersection. I had to have computer assistance person build me the route for each route, since flight planning was not capable and continues to be incapable of allowing me to file an advisory route or any route that we need to file. Flight planning system needs to be dynamic enough to allow us to build a route with any of the airway system navaids, intxns, sids, and stars that we use as an airline, and do it correctly. This sector has approximately 63 releases in an 8 hour period, and with the additional problems from flight software, this is unacceptable. When sector xx has any type of reroute, ATC delay, or any problem, it becomes an operational control issue. The other duties of flight following, monitoring station WX, and all other dispatcher duties and requirements become jeopardized or neglected from the shear amount of flts on the sector.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR DISPATCHER IS NOT ABLE TO FLT PLAN PROPERLY DUE TO EXCESSIVE RELEASE WORKLOAD AND A FLT PLANNING COMPUTER THAT WILL NOT ACCEPT SIDS, STARS, AND JET AIRWAY ROUTING.

Narrative: THIS IS BEING FILED NOT ONLY FOR THIS FLT, BUT ALL FLTS THIS MORNING ON THIS SECTOR THAT RECEIVED REROUTE TO ORD. THE ROUTING WAS FROM VARIOUS VORS TO J134, J105 TO BDF, PER ATC ADVISORY 040. USING FLT PLANNING SOFTWARE THIS WAS NOT POSSIBLE AND NEVER IS POSSIBLE. ALSO, IT DID NOT ACCEPT THE SID FROM LAS, THE AACES2 SID WHICH WE ARE TO USE. I NOTIFIED FLT PLANNING, IT PEOPLE, AND MR X, CAME DOWN AND SAT WITH ME AND WAS SURPRISED THE SYS DID NOT WORK WITH THE ROUTING, NOR DOES ITACCEPT SIDS AND OR A COMBINATION OF ANY NAVAID, JETWAY, AND OR INTXN. I HAD TO HAVE COMPUTER ASSISTANCE PERSON BUILD ME THE RTE FOR EACH RTE, SINCE FLT PLANNING WAS NOT CAPABLE AND CONTINUES TO BE INCAPABLE OF ALLOWING ME TO FILE AN ADVISORY RTE OR ANY RTE THAT WE NEED TO FILE. FLT PLANNING SYS NEEDS TO BE DYNAMIC ENOUGH TO ALLOW US TO BUILD A RTE WITH ANY OF THE AIRWAY SYS NAVAIDS, INTXNS, SIDS, AND STARS THAT WE USE AS AN AIRLINE, AND DO IT CORRECTLY. THIS SECTOR HAS APPROX 63 RELEASES IN AN 8 HR PERIOD, AND WITH THE ADDITIONAL PROBS FROM FLT SOFTWARE, THIS IS UNACCEPTABLE. WHEN SECTOR XX HAS ANY TYPE OF REROUTE, ATC DELAY, OR ANY PROB, IT BECOMES AN OPERATIONAL CTL ISSUE. THE OTHER DUTIES OF FLT FOLLOWING, MONITORING STATION WX, AND ALL OTHER DISPATCHER DUTIES AND REQUIREMENTS BECOME JEOPARDIZED OR NEGLECTED FROM THE SHEAR AMOUNT OF FLTS ON THE SECTOR.

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