Azure Jane Lunatic (azurelunatic) wrote,
Azure Jane Lunatic
azurelunatic

  • Location:
  • Music:

Warrior/Disciple

Dear LJ,

I have co-workers who should not be trusted to drive a spreadsheet without crashing it into things. I've spent an hour just going "wtf", which is not the best time management, but ... ow. My brains.

Love, Loonie


Dear Team With The Bad Hours Charts,

I noticed some issues with this weekend’s hours charts. I understand there may be new people learning the hours chart, so some mistakes are only to be expected. It would be greatly appreciated by everybody if someone who is more experienced with the hours chart takes a look over it to catch any issues before it is printed and submitted as the official hours chart for the shift.

While the importance of having correct totals on the hours charts may decrease with the advent of $SYSTEM-based $CHART hours, we are not there quite yet. For the moment, it is still important to only charge the same hours as a positive one time, but to make sure to charge them as positive hours. I say this because I got an impressive number of errors on this weekend’s hours charts. There was an hours chart that had a positive total and a positive subtotal, which should not happen, and then those hours were entered in the same fashion to the evening hours chart, compounding the error. I also got an hours chart with Inbound hours charged as negative, with nary a positive in sight. I got an hours chart with $SPECIFIC downtime charged positive for one job and negative for another. I got an hours chart with negative italic hours of $TYPE Downtime, but no positive number charged in $PHONEGOON Downtime. All of these things may provide an accurate total for the absolute value of the hours charged to the job, but they do not provide an accurate number of total hours for the team. The hours charts in question were corrected and re-printed. When using the +/- column to remove program downtime for a job, make sure that it's sort of negative on the right line, rather than adding hours to both the dialing and to the downtime by having it positive in both places.

The hours chart works by adding up only the positive numbers into the total hours at the bottom. It ignores all negative numbers. Make sure that for any hours that you are charging to jobs, that there is a positive total there somewhere.

Some jobs (like $SPECIFIC downtime or any inbound application) have only positive hours. Other jobs have a positive total (or two positive totals, if there are temps dialing on it) and subtotals (type of $THINGY, $REGION, or other subtotals). Make sure that any subtotal is charged as negative. Since the way the $OTHER_SIDE_LANGUAGE_SPECIFIC hours on the $CHART are kept has changed, I changed the way the hours were tracked on the hours chart in an attempt to make it relatively painless to keep the hours in such a way that very little has to be done in order to break them down for the $CHART. It seems that this has caused some confusion. Currently the hours chart has the total hours between the two $OTHER_SIDE_LANGUAGE_SPECIFIC jobs as a positive, and the individual jobs, and the dialer type, all as negative italic subtotals. If this is too confusing, it can be changed back to two separate jobs, even though that is not how it is tracked on the $CHART.

If a positive is entered on the negative italic subtotal lines, this will screw up the total hours. If a negative is entered on a bold total line, it will screw up the total hours. Try not to screw up the total hours, please?

Thanks,
A. Lunatic
Supervisor
Direct Telephone (602) XXX-XXXX
E-mail: azure.lunatic@example.com
Subscribe
Comments for this post were disabled by the author