Path: utzoo!attcan!uunet!ssbell!mcmi!amperif!unocss!mlewis From: mlewis@unocss.UUCP (Marcus S. Lewis) Newsgroups: comp.misc Subject: Re: "comp time" Summary: comp time Message-ID: <804@unocss.UUCP> Date: 17 May 89 22:20:09 GMT References: <18397@cup.portal.com> Organization: U. of Nebraska at Omaha Lines: 35 In article <18397@cup.portal.com>, Tom_G_Madden@cup.portal.com writes: > Opinions please > --------------- > 1. Is hour for hour fair (i guess so) but does it cause scheduling problems > when the user goes to take the owed time. > > 2. Should their be a maximum of how much time can be "banked" ? > > 3. A threshold where some overtime (like 4 hours a week) is given to the company > and THEN hour for hour > > 5. Have the time put toward vacation weeks which might make project scheduling > easier. We operate 7-days/24-hours with two operators. This does require occasional overtime from the programming staff - it's really not as bad as it sounds. Our weekend processing can be done in a single 16-hour stretch, so our programmers (and I) rotate weekends. We are allowed two days off either the week before or the week after, or split, based on backup people. My operators also share the weekends, but they get paid overtime. Our upper management choked on the comp-time, but allowed as how they couldn't keep people without SOME compensation. They DID choke on "saving" comp-time. So if one of us needs a day off (like for a job interview), we re-schedule the weekend chores and take the time as allowed. Our month-end processing requires two 16-hour shifts, which is a little tougher, especially if the machine croaks. Last year I babysat a dead disk for a 40-hour weekend. And was in on time Monday AM for the installation of the new drive. I DID get a pat on the back for that... Marc -- Es Brillig war. Die schlichten Toven | Internet: cs057@zeus.unl.edu Wirrten und wimmelten in Waben. | UUCP: uunet!btni!unocss!mlewis Und aller-muemsige Burggoven | Bitnet: CS057@UNOMA1 Die mohmem Raeth' ausgraben. | (go for it!)