IT outage
#341
Can’t find crew pickup
Joined APC: Jun 2021
Posts: 2,231
I’m not defending, these are actual questions I want to know the answers to that I’ll likely never get.
#342
Gets Weekends Off
Joined APC: Jan 2007
Position: 30 West
Posts: 421
If this was Delta's first trip down the path of abject failure to reset in a reasonable amount of time I'd give them a pass, but it is not. There needs to be big pain inflicted in the "C Suite" by the BOD for this disaster. Black Swan events do happen and seems like with ever more frequency. The amount this is going to cost Delta dwarfs the cost of having the resources in place to recover quickly and protect the goodwill of the most important stakeholders of the operation. The customers. There is no acceptable excuse or explanation for not being prepared.
#343
TLDR: https://dal-jetstream.my.site.com/pilots/s/
The Crew Assist "app" on your EFB is really no such thing--it's essentially just a shortcut to Safari (running in its own sandbox), with its own icon, etc. Same as, say, the @Rest "app" on the EFB (among many others).
The link above is the main page that the "app" displays, all other links work from there. I've found it doesn't play well with ad blockers & other anti-tracking extensions, so you may need to either allow it to bypass those or set up a different browser for this (and similar websites with that issue), which is my solution. Works fine* on a personal iPhone (no knowledge of Android one way or the other)....
EDIT: *(albeit with some jacked up screen spacing)
Last edited by Jughead135; 07-26-2024 at 07:12 AM. Reason: clarification on iPhone efficacy
#344
Details, please? (Nothing personally identifiable, of course--just the nature of the claim.)
I have trouble believing this in the context as stated. As others have already stated, making a fraudulent claim (say, for an expense not actually incurred) is worlds away from a denied claim (which is determined, rightly or wrongly, not to qualify for reimbursement). I'll be interested to hear if the OP got his Uber ride to SAV paid (I personally hope so, but I have to doubt it). So long as he didn't label it falsely ("hotel in ATL"), there's no possibility of fraud, IMO....
I have trouble believing this in the context as stated. As others have already stated, making a fraudulent claim (say, for an expense not actually incurred) is worlds away from a denied claim (which is determined, rightly or wrongly, not to qualify for reimbursement). I'll be interested to hear if the OP got his Uber ride to SAV paid (I personally hope so, but I have to doubt it). So long as he didn't label it falsely ("hotel in ATL"), there's no possibility of fraud, IMO....
#345
Gets Weekends Off
Joined APC: Jul 2023
Posts: 206
You're not going to get any details, because the details don't fit his narrative. There's no way they just straight up fired someone because they denied an expense claim. There's far more to the story than that.
#346
Gets Weekends Off
Joined APC: Jan 2023
Posts: 1,510
(see bolded part) - The two are dovetailed. As we brought up each system (desktop, server, gate agent terminals, baggage tracking systems, ticket agent terminals, customer support terminals etc) we then had to begin to sync the systems with reality. We really couldn't get it fully caught up until all the servers and systems were patched - which was a manual intensive process requiring many reboots and tech savvy. Again, I don't think many here understand the depth of how our systems are interconnected with one another. It is what has given us advantages over UAL and AAL. That's why, up until July 19th, we were very efficient and operationally very effective. As I posted earlier, I was surprised we got the systems up and running and synched back up as quickly as we did.
Someone asked about why UAL and AA were able to recover faster. It was simple, they run simpler and less complex systems for their operations. They are inefficent and manpower intensive. They are bootstrapped off of circa 2000 airline systems. Basically the backbone of their systems is very archaic, they use some newer UIs to make it more friendly but the backbone (akin to our iCrew) of their systems is light years behind ours. That' why under normal operations we clean their clocks with our operation.
Once again, the largest issue faced was figuring out where our crews where. As we rebuilt the tracker, it was a tough process. As RA said many years ago, we have to fix our ability to communicate with our crews efficiently and effectively during these meltdowns. That has yet to be addressed. Yes, maybe pilot assist chat is a step in the right direction, but it's not the solution. We need to better staff our tracking and scheduling teams. That's a start. I hope that this comm issue doesn't get swept under the rug again. It was one the main reasons why it took us 4-5 days to get the operation back in sync.
#347
Gets Weekends Off
Joined APC: Feb 2007
Position: Big ones
Posts: 773
The Crowd Strike bug that nuked pretty much all our operational systems was the catalyst.
(see bolded part) - The two are dovetailed. As we brought up each system (desktop, server, gate agent terminals, baggage tracking systems, ticket agent terminals, customer support terminals etc) we then had to begin to sync the systems with reality. We really couldn't get it fully caught up until all the servers and systems were patched - which was a manual intensive process requiring many reboots and tech savvy. Again, I don't think many here understand the depth of how our systems are interconnected with one another. It is what has given us advantages over UAL and AAL. That's why, up until July 19th, we were very efficient and operationally very effective. As I posted earlier, I was surprised we got the systems up and running and synched back up as quickly as we did.
Someone asked about why UAL and AA were able to recover faster. It was simple, they run simpler and less complex systems for their operations. They are inefficent and manpower intensive. They are bootstrapped off of circa 2000 airline systems. Basically the backbone of their systems is very archaic, they use some newer UIs to make it more friendly but the backbone (akin to our iCrew) of their systems is light years behind ours. That' why under normal operations we clean their clocks with our operation.
Once again, the largest issue faced was figuring out where our crews where. As we rebuilt the tracker, it was a tough process. As RA said many years ago, we have to fix our ability to communicate with our crews efficiently and effectively during these meltdowns. That has yet to be addressed. Yes, maybe pilot assist chat is a step in the right direction, but it's not the solution. We need to better staff our tracking and scheduling teams. That's a start. I hope that this comm issue doesn't get swept under the rug again. It was one the main reasons why it took us 4-5 days to get the operation back in sync.
(see bolded part) - The two are dovetailed. As we brought up each system (desktop, server, gate agent terminals, baggage tracking systems, ticket agent terminals, customer support terminals etc) we then had to begin to sync the systems with reality. We really couldn't get it fully caught up until all the servers and systems were patched - which was a manual intensive process requiring many reboots and tech savvy. Again, I don't think many here understand the depth of how our systems are interconnected with one another. It is what has given us advantages over UAL and AAL. That's why, up until July 19th, we were very efficient and operationally very effective. As I posted earlier, I was surprised we got the systems up and running and synched back up as quickly as we did.
Someone asked about why UAL and AA were able to recover faster. It was simple, they run simpler and less complex systems for their operations. They are inefficent and manpower intensive. They are bootstrapped off of circa 2000 airline systems. Basically the backbone of their systems is very archaic, they use some newer UIs to make it more friendly but the backbone (akin to our iCrew) of their systems is light years behind ours. That' why under normal operations we clean their clocks with our operation.
Once again, the largest issue faced was figuring out where our crews where. As we rebuilt the tracker, it was a tough process. As RA said many years ago, we have to fix our ability to communicate with our crews efficiently and effectively during these meltdowns. That has yet to be addressed. Yes, maybe pilot assist chat is a step in the right direction, but it's not the solution. We need to better staff our tracking and scheduling teams. That's a start. I hope that this comm issue doesn't get swept under the rug again. It was one the main reasons why it took us 4-5 days to get the operation back in sync.
#348
Not at Delta, but I can’t imagine your CBA requires you to be contactable by the company on days off. I don’t believe any of my friends there would stand for it either.
#349
Gets Weekends Off
Joined APC: Feb 2008
Posts: 19,588
Details, please? (Nothing personally identifiable, of course--just the nature of the claim.)
I have trouble believing this in the context as stated. As others have already stated, making a fraudulent claim (say, for an expense not actually incurred) is worlds away from a denied claim (which is determined, rightly or wrongly, not to qualify for reimbursement). I'll be interested to hear if the OP got his Uber ride to SAV paid (I personally hope so, but I have to doubt it). So long as he didn't label it falsely ("hotel in ATL"), there's no possibility of fraud, IMO....
I have trouble believing this in the context as stated. As others have already stated, making a fraudulent claim (say, for an expense not actually incurred) is worlds away from a denied claim (which is determined, rightly or wrongly, not to qualify for reimbursement). I'll be interested to hear if the OP got his Uber ride to SAV paid (I personally hope so, but I have to doubt it). So long as he didn't label it falsely ("hotel in ATL"), there's no possibility of fraud, IMO....
#350
Gets Weekends Off
Joined APC: Feb 2008
Posts: 19,588
If you submit a claim you know is fraudulent they will fire you. It's not a game of catch me if you can.
Thread
Thread Starter
Forum
Replies
Last Post