Originally Posted by Sunvox

I agree with Golfer's sentiment. There is some element of a learning curve involved, but I feel the larger issue is the difference in philosophy shown in CCS. As an example I will point out 4 issues that have come to my attention right away, not that these issues are unsolvable nor that others might have run into different issues, but simply as an example of the frustration some people may be feeling.

First, I can not access another pilots current schedule or pairing. Second, when Monthly Preferencing is complete I must look through hundreds of pages of data to see what others were able to bid where previously I could pull that up in a simple line summary format only a few pages long. Third, bidding individual pairings was easy because a pairing summary was available in 9 pages rather than hundreds. Lastly, training managers were able to see each instructors schedule by simply hovering over their name on a data base, but now they have to print out several poster sized sheets to get the same information. Information that they use daily to meet the scheduling challenges they face when people call in sick or there are broken sims etc. In short, CCS appears, at first blush, to have much less functionality from the UAL perspective. It may be that in time we will learn how better to get what we want from CCS, but so far it seems CCS is intentionally designed to restrict pilot access to system wide information.