Ace update?

Subscribe
8  14  15  16  17  18 
Page 18 of 18
Go to
Quote: I don't think it's primarily to avoid "bogging down" the scheduling committtee. Addressing pay problems with the company first will have that impact as a byproduct, but that's not the primary factor.

It's making sure the company has some ownerhip and invests the man-hours necessary into fixing their own violations/processes before using dues dollars (in the form of ALPA scheduling volunteers) to fix it. Also, we'll get paid quicker if we can get it resolved with the company rather than wait for a dispute to be processed.

It would be great if the company actually paid their pilots on time, transparently, and without intervention...like every other Fortune 100 company seems to have figured out. Despite Gumm's "sincere" assurances, that appears nowhere close to fruition.

The ideal end state I think we can agree would be the company finally producing a modern, automatic pay system (perhaps verified by a violation-identifying watchdog software from DALPA) adequately robust and transparent enough to dramatically decrease the number of pay disputes/PWA violatoins, and thereby reducing the manning and expenditures required in the scheduling committee.
pay software the company could use is unironically called “rainmaker.” Was used at Pinnacle/Mesaba/Colgan. Works great lasts long time.
Reply
Quote: pay software the company could use is unironically called “rainmaker.” Was used at Pinnacle/Mesaba/Colgan. Works great lasts long time.
I think the problem is that Rainmaker was designed to work with Sabre. If that is indeed the case, outside a few majors, who have their own proprietary systems, just about everyone contracts with Sabre for their crew management, so it's easy to port over.

Not so easy when you have a totally proprietary system like OSS/DBMS.
Reply
Quote: I think the problem is that Rainmaker was designed to work with Sabre. If that is indeed the case, outside a few majors, who have their own proprietary systems, just about everyone contracts with Sabre for their crew management, so it's easy to port over.

Not so easy when you have a totally proprietary system like OSS/DBMS.
The larger problem is that even if the rainmaker software were somehow plug and play into each airline’s system exclusive of Sabre, Delta’s desire for an in-house solution would trump its selection.
Reply
Quote: If ACE did have the ability to auto notify the company, then it would have been nice to know before the alert email telling us ACE was going away.

How long has (was) that capability a thing? Because every conversation with my Reps and every Sched Alert I can remember reading said you *must* contact scheudler to stop the clock (crew assit pay case was later added as official mechanicsm to stop the clock becuase it was being submited to the company), then CPO, then ACE to get sched committee involved.
8/10/23 it started auto notifying the company for any report submitted.
Reply
Quote: 8/10/23 it started auto notifying the company for any report submitted.

First mention of ACE I found after the 8/10/23 date you mentioned was the 31 Aug MEC Alert Email and regarding ACE it said:

"Before submitting your report, the Delta MEC asks that you contact your Delta Crew Scheduler and try to get your issue or question answered. If you've made contact, and the Company was unable to answer your question or resolve your issue, you can then submit your ACE report.

If you have submitted an ACE report, but have not contacted the Company about the incident, please contact crew scheduling or your chief pilot immediately and send a message in your ACE report with the date you contacted the Company. The RLA grants 120 days from the incident, and this stops that clock."


This message was repeated in the 7 Sept MEC Email, and 14 Sep, and 28 Sept, and 5 Oct, and 12 Oct...

So was the intent not to tell the pilots in order to make sure they kept calling schedulers directly in hope they would fix the errors at lowest possbile level (and get paid the fastest), and just let the auto notify function run in the backround as a backup just in case the pilots forgot to call?

Or was there a memo telling pilots to stop calling and I missed the memo?
Reply
Quote: First mention of ACE I found after the 8/10/23 date you mentioned was the 31 Aug MEC Alert Email and regarding ACE it said:

"Before submitting your report, the Delta MEC asks that you contact your Delta Crew Scheduler and try to get your issue or question answered. If you've made contact, and the Company was unable to answer your question or resolve your issue, you can then submit your ACE report.

If you have submitted an ACE report, but have not contacted the Company about the incident, please contact crew scheduling or your chief pilot immediately and send a message in your ACE report with the date you contacted the Company. The RLA grants 120 days from the incident, and this stops that clock."


This message was repeated in the 7 Sept MEC Email, and 14 Sep, and 28 Sept, and 5 Oct, and 12 Oct...

So was the intent not to tell the pilots in order to make sure they kept calling schedulers directly in hope they would fix the errors at lowest possbile level (and get paid the fastest), and just let the auto notify function run in the backround as a backup just in case the pilots forgot to call?

Or was there a memo telling pilots to stop calling and I missed the memo?
Most likely it was a call the company because it's thier problem instruction. The only way to get resources on it from the company's end was to make it a big enough problem i.e. overwhelm the schedulers.
Reply
Quote: First mention of ACE I found after the 8/10/23 date you mentioned was the 31 Aug MEC Alert Email and regarding ACE it said:

"Before submitting your report, the Delta MEC asks that you contact your Delta Crew Scheduler and try to get your issue or question answered. If you've made contact, and the Company was unable to answer your question or resolve your issue, you can then submit your ACE report.

If you have submitted an ACE report, but have not contacted the Company about the incident, please contact crew scheduling or your chief pilot immediately and send a message in your ACE report with the date you contacted the Company. The RLA grants 120 days from the incident, and this stops that clock."


This message was repeated in the 7 Sept MEC Email, and 14 Sep, and 28 Sept, and 5 Oct, and 12 Oct...

So was the intent not to tell the pilots in order to make sure they kept calling schedulers directly in hope they would fix the errors at lowest possbile level (and get paid the fastest), and just let the auto notify function run in the backround as a backup just in case the pilots forgot to call?

Or was there a memo telling pilots to stop calling and I missed the memo?
If we published to the pilot group, no one would try to contact the company first and solve the issue with the company....which is what is technically required....but it stopped the clock for you in case you didn't contact the company.
Reply
Quote: ]If we published to the pilot group, no one would try to contact the company first and solve the issue with the company[/b]....which is what is technically required....but it stopped the clock for you in case you didn't contact the company.
such a true statement
Reply
8  14  15  16  17  18 
Page 18 of 18
Go to