Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2003

    Any standard for charging for System Admin time?

    Just wondered how people generally charge for system admin time. For things like fixing small bugs, upgrading apache then I just charge for the hour and thats it. However in the following setup how would you charge?

    I'm diagnosing a server that crashes randomly so I login at say 7am and logout at 11am so I was logged in for 4 hours. In that time I only did say 55 minute or work as the rest of the time top was running to see what was going on. Now I would charge for 1 hour but do people normally charge the full 4 hours or somewhere in between?

    Russ Foster - Industry Curmudgeon

  2. #2
    Join Date
    Feb 2005
    A good equation for the server admin time would be the time spent on troubleshooting or actually working on the problem.

    So even if you are logged in for 4 hours, but have worked only for 55 minutes, then it can be counted as only 55 minutes of work performed (i.e 1 hour).

    That is what we do and that is what fair from customers point of view. I dont think it is right charging any client based on your login time

  3. #3
    Join Date
    Jun 2001
    Denver, CO
    I actually tend to disagree with this. If you have to sit on a server for a number of hours and are constantly keeping an eye on top or some other diagnostic output, you are reducing your overall productivity, and inhibiting you from pursuing other tasks (be it business or personal) at 100%. Even though you are not 'actively' doing work on the server for a large percentage of the time, I believe that the passive work involved is billable. In certain situations, you may be completely justified in billing for 4 hours of your time - if the work is outside of normal hours or if during these 4 hours your client is constantly messaging / calling you to check on the status of things, effectively making it impossible for you to carry on with any other productive tasks. In other situations, you might bill for less time, but this would be based largely on your relationship with your customer, your hourly rate, and your ability to conduct other revenue generating activities.

    Additionally, I also believe that any other clients you have during this 4 hour period will suffer simply because you will always be distracted by this other issue. Let's say that you work 30 minutes initially on this issue, and then you monitor the box for 45 minutes. At this time, the box flips out and you have to spend another 10 minutes on it. Meanwhile, in the previous 45 minutes you started something for another client, and now his project is disrupted. If you're billing him by the hour as well, you're faced with having to keep track of many work stop / start times, which further reduces overall productivity.

    I actually don't like to bill for projects by the hour because of these issues, particularly when high level technical skills are required for troubleshooting intermittent issues, server migrations, etc. I've found that these types of projects require a large time commitment in terms of general availability, but not necessarily for doing active work. Because of this we either charge clients a monthly retainer for a standard set of services (monitoring, maintenance, software upgrades, etc) and then we provide more time consuming services on a per project based fee schedule.
    Jay Sudowski // Handy Networks LLC // Co-Founder & CTO
    AS30475 - Level(3), HE, Telia, XO and Cogent. Noction optimized network.
    Offering Dedicated Server and Colocation Hosting from our SSAE 16 SOC 2, Type 2 Certified Data Center.
    Current specials here. Check them out.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts