hexagon logo
Register Sign in
  • Replies 16 replies
  • Subscribers 224 subscribers
  • Views 177 views
  • Users 0 members are here
Options
Related

How do you estimate / quote programming times?

hoju6886
Hey, all!

I am looking for a very simple answer to a very complicated question. I have a TON of work ahead of me and my boss wants to know how long it will take to complete.

I have a very broad spectrum of parts that are all quite different from each other. I have heard that a general rule of thumb is you can apply "five minutes per touch". I have, at the end of a program, counted how many touches the CMM takes, and I can look at how long it took to me to program the part, and this rule of thumb, isn't that far off.

The problem is BEFORE programming, or putting in too much work, I would like a quick and easy method to arrive at a ballpark guess at programming time. I have lots of experience, and I can look at a part and give a ballpark estimate, but my boss wants a layman or someone who is not a CMM programmer to be able to look at a model of a part, and by feature count or some other metric, be able to determine how long it would take a CMM programmer to write a program. (approx.)

Anyone out there know a trick or rule of thumb that could help me out here? Thanks in advance!

TheWhiteSpider
PC-DMIS 2013
offline CAD++
NX/Unigraphics into .IGES files
Parents
  • I do all my programming offline and I always try to have a really fleshed out idea of the set-up before hand. I try to spend all my time up front, so when we get the actual part in our hands, we don't spend too much time on the proveout.

    Typically, I will go through a print, however many pages, and highlight what I think can go on the CMM and what can't, and what I will try to get, and all the datum features. From there, I can usually make a pretty good guess how long it will take, (then I double it! ;-) ) But, I guess AndersI has the right idea.

    "Note how long it takes you to create programs, tabulate this against feature count, dimension count, touch point count, number of tip angles, whatever... and try to find some usable correlation.

    The results will probably differ wildly from person to person..."

    The trick is, my boss or someone ELSE would like to look at the feature count or dimension count, and come up with a ballpark programming estimate.

    Thanks!
Reply
  • I do all my programming offline and I always try to have a really fleshed out idea of the set-up before hand. I try to spend all my time up front, so when we get the actual part in our hands, we don't spend too much time on the proveout.

    Typically, I will go through a print, however many pages, and highlight what I think can go on the CMM and what can't, and what I will try to get, and all the datum features. From there, I can usually make a pretty good guess how long it will take, (then I double it! ;-) ) But, I guess AndersI has the right idea.

    "Note how long it takes you to create programs, tabulate this against feature count, dimension count, touch point count, number of tip angles, whatever... and try to find some usable correlation.

    The results will probably differ wildly from person to person..."

    The trick is, my boss or someone ELSE would like to look at the feature count or dimension count, and come up with a ballpark programming estimate.

    Thanks!
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement