hexagon logo

Reporting time

Management wants to create a load board for our quality department, so that they can see what we spend our time on and if we are worth keeping around. Lol so do you guys have to do something like this? If so how do you go about reporting? They have been trying to estimate how long it will take to create a program and measure parts based on size
Parents
  • For clarification, the timer I designated above was for program run time.
    How long it takes the program to run might change, though probably very little, depending; I use it simply as a way to report it.
    As stated above; there's no "one size fits all" determination for how long it would take someone to program, however you can evaluate how long it takes you to. If most of your parts are nearly identical, averaging out how long it takes for each one might give you results with a certain margin of error.

    I'd recommend:

    Say you write ten programs.
    Each of them takes between 2 and 5 days to complete, however they have relatively the same complexity.

    Give them a week, on average, per program.
    Then most of your bases are covered, and you won't have mgmt barging in every 3 days to see "why is this time slower than last time?"

    Be generous with how long it takes, because it will only make life easier for you, and I promise they will be able to work with whatever number you give them (as long as it's reasonable, obviously).
    Plus, if you tell them a week per program, but at the end of the week you have 2 or 3, you look a little betterSunglasses
  • I think they will catch on, I imagine they would start to expect 2 or 3 programs a week
Reply Children
No Data