Working only 40 hours is not lazy! In fact if you are forced to work more
than 40 hours you are probably working for an outfit that is too cheap to
buy the full array of resources you need or they are understaffed. Either
way you probably don't want to be working for that kind of a show. There
are of course times when a business' hours need to be accomodated but they
should be few and far between and not difficult or time consuming because
you will have time to plan your procedures.
Maintenence of a network does not and should not require any overtime,
changes should be well planned and thoroughly investigated to avoid
interruptions, and as such, with a good contingent backout plan, usually be
able to be implemented during normal hours...emergencies not included.
Initial rollout/upgrades may require some extra curricular hours but this
would only be in the event of having to reuse some of the existing
equipment, which is unusual because generally the reason you are there is to
replace old underpowered equipment with better stuff. In the event you are
rolling out all new equipment, there is no reason you cannot build and test
your new network thoroughly before switching over to it. The switch over
however, often requires a weekend. ISP's often require 24/7/365 uptime but
they should generally have enough redundancy to allow you adequate time to
make your changes.
The most common reason for working overtime is because of impromptu changes
which need to be made or an emergency has arisen which cannot wait for
planning. Good planning and design should minimalize the former.
Unfortuanately, the nature of the beast means there will always be the
latter, but even those can have minimal impact with good planning and
monitoring practices in place.
Bottom line: 40 hours weeks are normal. Rotating the staff roster, two or
three additional weekends a year should be max.
----- Original Message -----
From: Oz <[EMAIL PROTECTED]>
To: Cisco Study Group <[EMAIL PROTECTED]>
Sent: Tuesday, August 01, 2000 5:44 AM
Subject: Re: Working hour
> It really depends
>
> Some corps work a 35 hour week some a 40 hour week. Also if you are
> staff it makes a difference also.
> I average a 55 hour week and have worked 80 hour weeks ..
> generally speaking staff will work more hours than contractors on a the
same
> site simply because the contractors get paid for every hour where a staff
> gets paid a flat rate ..
> OTOH I worked on a site where it was the exact opposite as the staff
were
> very lazy and once the 40 hours were up they went home and left the
> resulting mess for the contractors to clean up.
>
> I would figure my average would be in the 55 hour range not including
the
> call in the missle of the night etc.
> The biggest difference I see is when rolling out a site versus
maintaining
> a site . During the rollout the hours can be very very long but once the
> site is done and after the debugging is done then things calm down a
little
> ( sometimes)
> Oz
> http://www.mcseco-op.com/helpfull_links.htm
> What is the normal working hour per week in each country?
>
> and what is the normal working hour per week for NETWORK ENGINEER have
> to work per week?
>
> I just want to know roughtly what to expect
>
>
> ___________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
