To: Ramius
Yeah...at the college we did monitor bandwidth. If someone had an obvious need for more bandwidth, we let 'em get away with a lot - the TV folks, for example. Anyone else, we would speak to.
But detailed monitoring for content...just seems like a waste of resources to me. And I figure it's not as though IT would be likely to find out something that direct coworkers didn't already know. If someone is really not getting their job done, most likely it's already obvious why.
Power trippin'. And maybe a bit of voyeurism.
To: RosieCotton
What a lot of imasu. Tell 'em "Ai! Bag that shite!"
sorry, i'll quit now
6,150 posted on
02/13/2007 6:36:50 PM PST by
ExGeeEye
(To destroy your enemies, to see them driven before you, and to hear the lamentation of the women.)
To: RosieCotton
Voyeurism-- that's the word I was looking for. And you know, I've done that sort of monitoring before, back when I thought it was just what we were supposed to do. But I have to admit to learning things about co-workers that I really wish I didn't know. There are things you just can't un-see.
In our policy docs we do make clear that we (IT) reserve the right to do pretty much whatever we want. We have done some investigations and monitored traffic of certain people, but in reality they were already well on the way to getting fired, and all we did was back up that decision.
Our policy even says that we ~assume~ that some personal use of computers will occur, and that as long as it is reasonable and doesn't burden our systems, it's up to each supervisor to set and enforce standards for their people.
6,153 posted on
02/13/2007 6:59:30 PM PST by
Ramius
([sip])
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson