RosterBuster and LogTen

Subscribe
1  2  3 
Page 2 of 3
Go to
RosterBuster and LogTen
Quote: iCrew > Pay/hours > Flight Time log > copy/paste future trips into the import feature on logten.

Ok thanks, I’ll try that. Then is there a time a way to import that into LogTen?
Reply
Quote: Pilots took a huge L when Delta starting treating excellent tools like Rosterbuster and Sabre WidgetWorks as "security threats". Rosterbuster had excellent Google and iCal Calendar sync functionality and WidgetWorks had opentime time alerts.
I agree but just a couple of clarifications.

Widget Works open time alerts were great. However I don't believe that DAL shut them down. Widget Works/Flightline Data Services were the only ones who had legal access to Delta's data, dating back many years to when they were owned and run by the Delta pilot and his IT-guru brother. However Sabre bought them years ago for their Flica scheduling software (highly regarded, although Delta never bought it). Over the years Sabre got tired of supporting software that was increasingly only used by a shrinking number of Delta pilots. They shut it down a few months ago.


But as for Roster Buster, icrewmax (which I used for years) etc you are correct. I understand why DAL doesn't allow access to it's proprietary info to third parties. What I don't understand is why DAL cannot (or will not) provide functionality to its crew force that others created years ago. To be fair, miCrew is a great product that keeps improving, but there is lots of room for more improvement.

And I think you meant to say "Delta lack of IT strikes again."
Reply
Quote: Ok thanks, I’ll try that. Then is there a time a way to import that into LogTen?
What do you mean?
Reply
Quote: What do you mean?

Can I use the steps you described to download my schedule in some sort of format that can then be uploaded into LogTen? Just looking for a workaround since we can’t use RosterBuster.
Reply
Quote: Can I use the steps you described to download my schedule in some sort of format that can then be uploaded into LogTen? Just looking for a workaround since we can’t use RosterBuster.
Yes. When you go on the Mac version of LogTen and copy that excerpt into the import feature, it's smart enough to know what is what. You can also further customize the output and train it to recognize what to look for. Hard to describe without images, I started using it the other day.
Reply
Quote: Can I use the steps you described to download my schedule in some sort of format that can then be uploaded into LogTen? Just looking for a workaround since we can’t use RosterBuster.
Yes, you can, quickly and with ease. And as myrkridia said, you don’t need RosterBuster to do it. LogTen has a great import tool. *Edit* just reread the OP, didn’t process you are trying to do this on an iPad.

But I’ve always wondered why would someone want to import before the trip? After, yes, but before? Every single time will change. And with all the reroutes these days, it’s likely the city pairs will too. To each their own, I guess.

IMO, It would be better if that function were set up to import after the trip. I always have to change the import fields for “Scheduled Out/In” to “Out/In”. Mildly annoying, and the default fields for import can’t be changed.
Reply
Quote: I agree but just a couple of clarifications.



Widget Works open time alerts were great. However I don't believe that DAL shut them down. Widget Works/Flightline Data Services were the only ones who had legal access to Delta's data, dating back many years to when they were owned and run by the Delta pilot and his IT-guru brother. However Sabre bought them years ago for their Flica scheduling software (highly regarded, although Delta never bought it). Over the years Sabre got tired of supporting software that was increasingly only used by a shrinking number of Delta pilots. They shut it down a few months ago.





But as for Roster Buster, icrewmax (which I used for years) etc you are correct. I understand why DAL doesn't allow access to it's proprietary info to third parties. What I don't understand is why DAL cannot (or will not) provide functionality to its crew force that others created years ago. To be fair, miCrew is a great product that keeps improving, but there is lots of room for more improvement.



And I think you meant to say "Delta lack of IT strikes again."
Thanks for the clarification on those issues. Agree 100%

Sent from my SM-S908U using Tapatalk
Reply
Quote: I agree but just a couple of clarifications.

Widget Works open time alerts were great. However I don't believe that DAL shut them down. Widget Works/Flightline Data Services were the only ones who had legal access to Delta's data, dating back many years to when they were owned and run by the Delta pilot and his IT-guru brother. However Sabre bought them years ago for their Flica scheduling software (highly regarded, although Delta never bought it). Over the years Sabre got tired of supporting software that was increasingly only used by a shrinking number of Delta pilots. They shut it down a few months ago.


But as for Roster Buster, icrewmax (which I used for years) etc you are correct. I understand why DAL doesn't allow access to it's proprietary info to third parties. What I don't understand is why DAL cannot (or will not) provide functionality to its crew force that others created years ago. To be fair, miCrew is a great product that keeps improving, but there is lots of room for more improvement.

And I think you meant to say "Delta lack of IT strikes again."
This is all good info. The other takeaway is that FDS software used a fundamentally different way to access the data it needed than just about everything else would today.

FWIW, NWA was a bit less uptight about IT back in the day, but to be fair, there was less to worry about. There were 3rd party programs that would check non-rev listings, book jumpsuits and whatnot. There was an fNWA guy who ran a site called "EZOPENBOARD", which did many of the same things that the FDS software did. He did try to port his site over to DBMS, and, as the story goes, he did it the right way, and ran all the way up the chain of command. He got all "yeses" until the final stop, and they said nope, and for him, the hassle was no longer worth it. Point is that anyone who wants to go that route will probably be disappointed.
Reply
Quote:
But I’ve always wondered why would someone want to import before the trip? After, yes, but before? Every single time will change. And with all the reroutes these days, it’s likely the city pairs will too. To each their own, I guess.

IMO, It would be better if that function were set up to import after the trip. I always have to change the import fields for “Scheduled Out/In” to “Out/In”. Mildly annoying, and the default fields for import can’t be changed.
Because it’s a way to double check for rotation violations and use that feature of LogTen.

As for after, it takes two seconds to create a new flight entry and add your times. Prefill before departure and all you have is your IN time after you land.
Reply
Quote: Because it’s a way to double check for rotation violations and use that feature of LogTen.
.
Not a log ten user, but what type of violations is it checking for? FAR 117?

You are going to have WAY more PWA violations with regards to double 23K, illegal re-routes, etc, that I'm sure LogTen knows nothing about.
Reply
1  2  3 
Page 2 of 3
Go to