Dropping whole month
#51
What is your aversion to Arcos for white slips? I actually find it tolerable as it is for green slips. If they would start using the details tab to actually show the trip information, that would be very helpful...or they could include it in the email.
I think we can all agree that logging into icrew is unnecessarily painful. Particularly for out of base stuff, though, it is essential to identify deviate from deadhead opportunities (among other details one considers when contemplating acceptance). Having this in ARCOS would make me a fan, as long as viewing something in ARCOS never constitutes acknowledgement.
I think we can all agree that logging into icrew is unnecessarily painful. Particularly for out of base stuff, though, it is essential to identify deviate from deadhead opportunities (among other details one considers when contemplating acceptance). Having this in ARCOS would make me a fan, as long as viewing something in ARCOS never constitutes acknowledgement.
Denny
#52
Gets Weekends Off
Joined APC: Sep 2014
Posts: 4,905
I totally agree. But that's not an ARCOS problem, it's an implementation problem. We just need to restrict WS issuance to one at a time (as I think GS should be done presently as well).
#53
What is your aversion to Arcos for white slips? I actually find it tolerable as it is for green slips. If they would start using the details tab to actually show the trip information, that would be very helpful...or they could include it in the email.
I think we can all agree that logging into icrew is unnecessarily painful. Particularly for out of base stuff, though, it is essential to identify deviate from deadhead opportunities (among other details one considers when contemplating acceptance). Having this in ARCOS would make me a fan, as long as viewing something in ARCOS never constitutes acknowledgement.
I think we can all agree that logging into icrew is unnecessarily painful. Particularly for out of base stuff, though, it is essential to identify deviate from deadhead opportunities (among other details one considers when contemplating acceptance). Having this in ARCOS would make me a fan, as long as viewing something in ARCOS never constitutes acknowledgement.
#54
That is not going to happen. The only reason they are paying ARCOS is to reduce the work load and speed up coverage. One at a time just defeats the purpose.
#55
Gets Weekends Off
Joined APC: Sep 2014
Posts: 4,905
I disagree. The system could be programmed to contact in succession instead of a simultaneous batch. As soon as the first pilot declines, the second is contacted. The scheduler would just flick the first domino and be notified when they had an acceptance. No workload increase from GS on ARCOS, although not quite as fast.
#56
I disagree. The system could be programmed to contact in succession instead of a simultaneous batch. As soon as the first pilot declines, the second is contacted. The scheduler would just flick the first domino and be notified when they had an acceptance. No workload increase from GS on ARCOS, although not quite as fast.
This is not going to be on our terms unless...
#57
Gets Weekends Off
Joined APC: Sep 2014
Posts: 4,905
1. Via a user-friendly GUI, let me enter global slips that last in perpetuity if I want them to, with an easy on/off toggle for each and a global for all. When I go on vacation, start drinking, think I'm about to get laid or even all three, I can suspend or snooze them for a defined time or indefinitely.
2. Let me enter all the same parameters into green, white and yellow slips that I can in PBS.
The system as it stands is cluttered with slips that rarely yield trip acceptance. I know this, because I myself have a ton of in- and out-of-base green and whites because 1 out of 20 might be a trip that works for me. I have to do it that way because I don't have the granularity to define what I'll actually take, and/or in some cases I won't take the hours (literally) it would take EVERY MONTH to input green slips that limit calls to what I know I can fly. I'd be happy to do it right if I didn't have to do it every month, for every base, with an interface from 1990. With what we have now, I (and thousands of others) just have blankets in and count on assessing every call that comes in (or ignoring it, helping no one).
If I'm NYC73NB living in NYC, does it make sense to have an out of base green for 2-day LAX trips reporting in 2 hours worth only 10+30? Not usually... until a trip pops up that's DH LAX to JFK, fly JFK-BOS, layover, and DH home to LAX. So, the NYC guy currently has his blanket OOBGS in with no limitations sitting in the system, because... why not?! With a better system that retains the work he does making slips for months or years, and which lets him suspend slips as desired, he instead inputs OOBGS for LAX with no minimum time to report if the first leg is DH and first day is DH only, to airports XYZ, if it doesn't encroach on more than one RES day (devaluing GS when reserve), departing on any day but Friday. 2-day LAX trips LAX-SEA-LAX reporting in 3 hours never go to him because he doesn't want them and doesn't ask for such parameters.
With more powerful slip generation, better precision and more dynamic control of them, you free everything up for greater trip assignment efficiency. Pilots (theoretically) accept 90% of trips they're offered, because neither they nor the company want to bother with contact that isn't fruitful. They also get their notification earlier with more time to get ready/travel/commute.
Give me a toggle on/off switch for slips I've entered and I will no longer garbage up the machine when I'm drinking or otherwise not willing/able to work.
#58
There aren't too many places for mutual benefit. I think this could be one, if done right. I'm happy to give up the old way of doing business if it is mutually beneficial to do so. Small increments in IT could (if done properly) improve qol and drastically reduce the clutter of slips clogging the system.
1. Via a user-friendly GUI, let me enter global slips that last in perpetuity if I want them to, with an easy on/off toggle for each and a global for all. When I go on vacation, start drinking, think I'm about to get laid or even all three, I can suspend or snooze them for a defined time or indefinitely.
2. Let me enter all the same parameters into green, white and yellow slips that I can in PBS.
The system as it stands is cluttered with slips that rarely yield trip acceptance. I know this, because I myself have a ton of in- and out-of-base green and whites because 1 out of 20 might be a trip that works for me. I have to do it that way because I don't have the granularity to define what I'll actually take, and/or in some cases I won't take the hours (literally) it would take EVERY MONTH to input green slips that limit calls to what I know I can fly. I'd be happy to do it right if I didn't have to do it every month, for every base, with an interface from 1990. With what we have now, I (and thousands of others) just have blankets in and count on assessing every call that comes in (or ignoring it, helping no one).
If I'm NYC73NB living in NYC, does it make sense to have an out of base green for 2-day LAX trips reporting in 2 hours worth only 10+30? Not usually... until a trip pops up that's DH LAX to JFK, fly JFK-BOS, layover, and DH home to LAX. So, the NYC guy currently has his blanket OOBGS in with no limitations sitting in the system, because... why not?! With a better system that retains the work he does making slips for months or years, and which lets him suspend slips as desired, he instead inputs OOBGS for LAX with no minimum time to report if the first leg is DH and first day is DH only, to airports XYZ, if it doesn't encroach on more than one RES day (devaluing GS when reserve), departing on any day but Friday. 2-day LAX trips LAX-SEA-LAX reporting in 3 hours never go to him because he doesn't want them and doesn't ask for such parameters.
With more powerful slip generation, better precision and more dynamic control of them, you free everything up for greater trip assignment efficiency. Pilots (theoretically) accept 90% of trips they're offered, because neither they nor the company want to bother with contact that isn't fruitful. They also get their notification earlier with more time to get ready/travel/commute.
Give me a toggle on/off switch for slips I've entered and I will no longer garbage up the machine when I'm drinking or otherwise not willing/able to work.
1. Via a user-friendly GUI, let me enter global slips that last in perpetuity if I want them to, with an easy on/off toggle for each and a global for all. When I go on vacation, start drinking, think I'm about to get laid or even all three, I can suspend or snooze them for a defined time or indefinitely.
2. Let me enter all the same parameters into green, white and yellow slips that I can in PBS.
The system as it stands is cluttered with slips that rarely yield trip acceptance. I know this, because I myself have a ton of in- and out-of-base green and whites because 1 out of 20 might be a trip that works for me. I have to do it that way because I don't have the granularity to define what I'll actually take, and/or in some cases I won't take the hours (literally) it would take EVERY MONTH to input green slips that limit calls to what I know I can fly. I'd be happy to do it right if I didn't have to do it every month, for every base, with an interface from 1990. With what we have now, I (and thousands of others) just have blankets in and count on assessing every call that comes in (or ignoring it, helping no one).
If I'm NYC73NB living in NYC, does it make sense to have an out of base green for 2-day LAX trips reporting in 2 hours worth only 10+30? Not usually... until a trip pops up that's DH LAX to JFK, fly JFK-BOS, layover, and DH home to LAX. So, the NYC guy currently has his blanket OOBGS in with no limitations sitting in the system, because... why not?! With a better system that retains the work he does making slips for months or years, and which lets him suspend slips as desired, he instead inputs OOBGS for LAX with no minimum time to report if the first leg is DH and first day is DH only, to airports XYZ, if it doesn't encroach on more than one RES day (devaluing GS when reserve), departing on any day but Friday. 2-day LAX trips LAX-SEA-LAX reporting in 3 hours never go to him because he doesn't want them and doesn't ask for such parameters.
With more powerful slip generation, better precision and more dynamic control of them, you free everything up for greater trip assignment efficiency. Pilots (theoretically) accept 90% of trips they're offered, because neither they nor the company want to bother with contact that isn't fruitful. They also get their notification earlier with more time to get ready/travel/commute.
Give me a toggle on/off switch for slips I've entered and I will no longer garbage up the machine when I'm drinking or otherwise not willing/able to work.
I like your fantasy world though, I wish I lived in it. I must be a jaded old man. I wish I had youthful optimism. Now I’m bringing my inner Eor!
#60
Gets Weekends Off
Joined APC: Sep 2014
Posts: 4,905
I agree with your optimistic new system but you realize that ARCOS is a call out system designed for lineman and road crews, right? A system that automatically logs you out without notice after 14 days and has absolutely nothing to do with slip requests. If what you’re describing is even feasible, it won’t be ARCOS and will probably be an in house Delta app or an add on for MiCrew. The likelihood of this new system being for our benefit is not very likely and will be a product of Delta IT. For customer facing tech, they are great, for the pilot group...
I like your fantasy world though, I wish I lived in it. I must be a jaded old man. I wish I had youthful optimism. Now I’m bringing my inner Eor!
I like your fantasy world though, I wish I lived in it. I must be a jaded old man. I wish I had youthful optimism. Now I’m bringing my inner Eor!
I think the low hanging fruits are an on/off toggle for slips, and an ability to copy slips from one month to the next. With no changes to ARCOS itself, those improvements would cut the clutter immensely and help everyone involved. The need for large batch size would itself be diminished and head fakes could dwindle.
On the ARCOS side (not knowing the architecture), I wonder if there might not be a way to repurpose the "ineligible" designation. I have seen this status for others in the pool with me and don't fully understand why they're in the pool to begin with. But if I could self-designate as ineligible, I would in effect have my toggle off feature and not be bothered by ARCOS notification.
Thread
Thread Starter
Forum
Replies
Last Post