CAATS Winnipeg
Moderators: North Shore, sky's the limit, sepia, Sulako
- invertedattitude
- Rank 10
- Posts: 2353
- Joined: Tue Jul 06, 2004 1:12 pm
CAATS Winnipeg
Curious how CAATS is working in Winnipeg?
Any UL people here, is the CAATS going ahead on Dec 9th?
Any UL people here, is the CAATS going ahead on Dec 9th?
- invertedattitude
- Rank 10
- Posts: 2353
- Joined: Tue Jul 06, 2004 1:12 pm
-
- Rank (9)
- Posts: 1130
- Joined: Thu Sep 21, 2006 3:03 pm
Re: CAATS Winnipeg
Improves efficiency for high level, due to the "hello"/"goodbye" nature of high level control. It is a living hell at times for low level, and has permanently increased their workload, requiring extra staff. So much for progress.av8rpei wrote:Curious how CAATS is working in Winnipeg?
Any UL people here, is the CAATS going ahead on Dec 9th?
Would have been more effective if all the programmers and analysts who worked on the system were not afflicted with Down Syndrome.
- invertedattitude
- Rank 10
- Posts: 2353
- Joined: Tue Jul 06, 2004 1:12 pm
High level aircraft typically fly from one airport to another, with little change in the flight while airborne with the exception of direct routings and altitude changes (both of which are easily entered into CAATS). Also, in YWG all high level aircraft are within radar coverage.av8rpei wrote:Interesting, why exactly does it increase the workload so much for low level than before implementation?
The problem in low level is that aircraft are much more likely to request destination changes en route, as well as being issued different routes for separation purposes (i.e. airways vs. direct) and it's also not uncommon to have 2-4 strips on a single aircraft. So whereas before all you had to do to enter a route change is write it on the strips, now you have to go into the aircrafts flight plan, type all the changes in, to which the printer will print out entirely new strips, which then have to be sorted and replaced. If the aircraft then requests an altitude change, again it has to be entered into CAATS and the printer will again spit out entirely new strips. Then the system will get a radar hit on the aircraft, update the time by three minutes, and print out yet another full set of strips.
To top it all off, the system has been unreliable with non-radar estimates, so all times must be checked manually and passed to the next controller for non-radar flights.
Really what it means in that when you start to get busy, you get overwhelmed by strips printing out and bogged down with data entry into the system.
no caats in december, that's for sure... it is still sad that they "found out" last week that they were not compatible... we had ground speeds of near M2.0 on the nards!
braun, i would expect your class to get more delays than if caats would have run as scheduled.... sorry about that!
braun, i would expect your class to get more delays than if caats would have run as scheduled.... sorry about that!
I'm intercontinental when I eat french toast
it will be a go fix nards thing, but not as jerricho says. DSC's in YUL found out that QM, QX and WG "workarounded" too many functions, and now they are stuck with resolving them in order to get caats compatible all around the country, in the event that YZ, EG and VR get connected.Alex YCV wrote:MCA: Is that a "full pull" or just a "go fix nards" deal?
I'm intercontinental when I eat french toast
Darn, howcome more?MCA wrote:no caats in december, that's for sure... it is still sad that they "found out" last week that they were not compatible... we had ground speeds of near M2.0 on the nards!
braun, i would expect your class to get more delays than if caats would have run as scheduled.... sorry about that!
because with that delay, we will have to train again in the sim, just before it goes on, which will delay the class before you, and consequently, your class as well.. those who finished the generic class in november are already off for 2 months, and i suppose it will increase. you might do the generic portion as planned, but be prepared to be sent home for a considerable time before you can start specific sub-unit training.Braun wrote: Darn, howcome more?
I'm intercontinental when I eat french toast
- invertedattitude
- Rank 10
- Posts: 2353
- Joined: Tue Jul 06, 2004 1:12 pm
The thing is, for high level controllers CAATS is gold.Braun wrote:Was the old system that bad? I just keep hearing bad things about this!
And even for low level controllers, it's not THAT bad. (With a couple of exceptions.)
Round-robin training flights and practice approaches confuse the hell out of the system, and destination/significant route changes are a lot more work now that they have to be entered into the system.
The thing is, CAATS was never meant to be used the way it is being used now. CAATS is and was designed as an entirely paper-less system. Well into the process, someone did a study and found that since the system was so radically different than anything the controllers were currently using, it would take each controller 30 days of training to be capable of using the new system.
This was obviously a huge problem since there is no way of putting that many controllers through that much training and still maintain the operation. After CAATS was delivered to Nav Canada, it then had to be adapted so as to only require 5 days of training per controller. As a result, most of the functionality was stripped out, and they adapted the software to print paper strips.
95% of the problems with CAATS are strip-printing related, and since that was never an origional design function, it's not suprising that there are this many problems.
-
- Rank (9)
- Posts: 1130
- Joined: Thu Sep 21, 2006 3:03 pm
I hope that you are making that statement as a low-level controller yourself? Over time you get used to the irritants. However, it has permanently increased staffing requirements. When a system produces the exact opposite of what was intended, as CAATS has, it means some severely retarded people were in charge of the development and modifications.Pygmie wrote:The thing is, for high level controllers CAATS is gold.
And even for low level controllers, it's not THAT bad. (With a couple of exceptions.)
And why that would seem to have been a reasonable course of action to whomever made that decision is a giant mystery. Any idiot should know that you cannot reverse engineer a "paperless" system to work with paper unless you start again from scratch.Pygmie wrote:As a result, most of the functionality was stripped out, and they adapted the software to print paper strips.
95% of the problems with CAATS are strip-printing related, and since that was never an origional design function, it's not suprising that there are this many problems.
Next on their list is probably to suggest using permanent markers on white boards, because they won't smear as much...