QIK /SHARES migration

[InternationalShannon]

I'm talking about on the jetbridge with 2 minutes to get the door closed. She was allowed to bring that "steamer trunk" down to the a/c. Then when it would not fit, they were checking it on the jetbridge with handwritten claim checks. No computer there to check her actual destination. Have to take the passenger's word for where they were going.

So, when she got to STL to make her connection to SPI, she expected someone from AA to go out to baggage claim, identify which bag was hers, and get it re-checked to SPI.

ooooaahhhhhhhhhh i seeee.....i bet that happens a lot!

 

[john john]

And now comes word that frontline users lose access to native DECS. DECS will now be accessed via QIK! Wanna bet that OCC will still able to use the native system? But "surely" IT has learned from any mistakes and the transition to QIK/DECs will be smooth as silk. And everthing that DECS has will be avalable in via QIK with sundry "CTL this F that" handy dandy keystrokes.

On the QIK/SHARES front, the June enhancements promise some much needed improvements (along with some functions that SABRE had). Lets all hope they will work as advertised.
But I fear it will be more lipstick on the proverbial big. (Sorry PHX___IT)

THIS IS A BIG MISTAKE DECS AND ITS PRESENT FORM IS A BIG PART AND A ESSENTIAL TOOL IN EVERY DAY AGENT WORK
Agent’s use DECS to track and get real flight data on every flight in USAirways system. It is a directly link to ACARS therefore it provides the tool for the agent to DO there jobs efficiently

 

[phx___it]

... agent to due there jobs efficiently

FYI, You spelled "efficiently" correct.

 

[InternationalShannon]

FYI, You spelled "efficiently" correct.

:blink:
for someone who paints himself the victim around here, you sure have an easy time being a smartbutt. I dont mean that in a mean way. I'm just saying....

watch out for the poor IT guy, because he sure gets snarky if you spell something wrong...haha

 

[sharktooth]

The kiosk has that functionality to book misconx to a later flight.
It has to be turned on by the airport manager though and I suspect that the aitport manager doesn't know about that feature. We need more training.
I checked out who is using it and it turns out that no one is using it. What a shame.

That is a Tempe failure and not an airport manager failure.

Blaming others is an exercise for kindergardeners.

 

[Dont call me Shirley]

.

Unless the responses are mature and civil, there won't be anymore replies.

phx_it,
I am sorry about the "shoot the messenger" stuff going on and truly appreciate your postings. Postings that are more informative and forthcoming than much of "official" pablum about QIX/SHARES issues. I detest QIK/SHARES as much as anyone else on this board, but anger at the shortcomings about the system should not be directed at you.

This stuff about unused capacity to rebook is astounding. But, at the risk of being a naysayer, could it be that this feature is not used beacuse it does not work properly?

 

[EastUS]

QUOTE (phx___it @ May 21 2008, 09:11 PM)
FYI, You spelled "efficiently" correct."

:blink: for someone who paints himself the victim around here, you sure have an easy time being a smartbutt. I dont mean that in a mean way. I'm just saying....
watch out for the poor IT guy, because he sure gets snarky if you spell something wrong...haha

Wee-yall... ifn's ya'll want's git' all picky an' all...'dat remark shudda' bin' par-seed out an' spay-uld as "correct(ly)" in eeny case Whadda' I know tho'...I ain't no geeenie-us workin' with all them 'puters...

Honestly though; After Shares/etc? I admire anyone from IT for even "showing up" and taking the reasonable heat around here...not to mention actually providing us all with some better understanding of what's going on/etc.

 

[phx___it]

phx_it,
I am sorry about the "shoot the messenger" stuff going on and truly appreciate your postings. Postings that are more informative and forthcoming than much of "official" pablum about QIX/SHARES issues. I detest QIK/SHARES as much as anyone else on this board, but anger at the shortcomings about the system should not be directed at you.

This stuff about unused capacity to rebook is astounding. But, at the risk of being a naysayer, could it be that this feature is not used beacuse it does not work properly?

I can't say for sure, but I think you have much more insight than you think. There's a good chance that it doesn't work.

About being the spelling scrutinizer. My apologies. My attempt at humor fell short.

About that "civil and mature" thing was actually me looking for an out. A public blog is not the place to air our dirty laundry. Well, not for employees anyway.
There must be better communication channels than this. Guess what, it doesn't seem like there is very much communication.
Which is so important after a merge. Again, this is as PineyBob says "The cost of being cheap".
I have to admit I came here very naive about the anger out there. I know now and think it's justified.

Thanks for the last 2 posts, it restored a bit of my faith in humanity

 

[Dont call me Shirley]

I can't say for sure, but I think you have much more insight than you think. There's a good chance that it doesn't work.

Oh, about being the spelling scrutinizer. My apologies. My attempt at humor fell short.

Thanks for the compliment. And I'm glad you're still around.

BTW, have you heard the reasoning behinf native DECs being made unavaible, forcing the use of QIK/DECS? I doubt is could be cost since US will be paying Sabre for DEC, whether access via native of QIK.

 

[phx___it]

Thanks for the compliment. And I'm glad you're still around.

BTW, have you heard the reasoning behinf native DECs being made unavaible, forcing the use of QIK/DECS? I doubt is could be cost since US will be paying Sabre for DEC, whether access via native of QIK.

I'm not part of the QIK group. I'll ask them tomorrow.

 

[tadjr]

I'm not part of the QIK group. I'll ask them tomorrow.

Also please try to find out why they are taking on implementing ANOTHER system (DECS) into QIK when it works perfectly fine in its native form, when (you would think) more pressing matters like getting the customer service side of the operations to work right on QIK. I can only imagine the time/effort/energy to get DECS working right on QIK that could have been spent on getting several identified issues with the current res system corrected. Quit spreading QIK too thin and focus on getting the system we've been promised to work!

 

[crusher]

Has anyone had this problem? Try and FLIFO a flight and the first response is the flifo like the ac never left or schedule . Then having to reenter and redo the whole process to get an accurate flifo time. Does qik/shares do ANYTHING WELL? It can't even flifo without having to do it twice!

 

[Dont call me Shirley]

Does qik/shares do ANYTHING WELL? It can't even flifo without having to do it twice!

IMHO, no it doesn't do anything well. But having to aiting 5 seconds for flifo is one the lesser problems. I would love to see a true quantative analysis of how long transaction time is in QIK/SHARES vs. Sabre. For that matter, QIK/SHARS v native SHARES. Even just printing a BP takes longer in QIK?SHARES than Sabre.


Tad brings up a great point in questioning why IT is devoting its scarce resources in forcing QIK/DECS when native DEC works just fine. They could be doing other, more important, things.

 

[jimcfs]

And Senior Executives of US Airways.

Gee Piney, I think you've hit why they act as they do... they used All I Really Need To Know I Learned In Kindergarten as their management reference manual.

 

[phx___it]

BTW, have you heard the reasoning behinf native DECs being made unavaible, forcing the use of QIK/DECS? I doubt is could be cost since US will be paying Sabre for DEC, whether access via native of QIK.

The only sign of native DECs being retired is from some training modules.
QIK will only support a fraction of DECs in the near future and plans to implement much more are still very far off.
In other words I think native DECs will be around for a while.