detailed manufacturing time tracking

glassexp · **Joined:** Thu Mar 31, 2011 4:35 am **Posts:** 118

The float_time widget does not cater for seconds.
I think it is a good idea to have seconds.
This is from https://bugs.launchpad.net/openobject-client-web/+bug/548932

Code:

+def float_time_convert(float_val):
+        hours = math.floor(abs(float_val))
+        mins = round(abs(float_val)%1+0.01,2)
+        if mins >= 1.0:
+            hours = hours + 1
+            mins = 0.0
+        else:
+            mins = mins * 60
+        float_time = '%02d:%02d' % (hours,mins)
+        return float_time
+

Maybe you can add seconds to this

mihai · **Joined:** Tue Jan 18, 2011 5:16 pm **Posts:** 236

Please vote on this:
http://feedback.openerp.com/forums/7745 ... ork-center

primax · **Posted:** Tue Aug 09, 2011 3:44 pm

it is possible to set time of cycle as you need. In routing attached to bom you have efficiency that factor multiply number of cycles in time for one cycle defined in work center.
example
form work center time per cycle 1 sec
no cycles 1 cycle
it means 1 cycle per second
in routing efficiency =2

it will calculate 2 cycles per 1 sec

hope it help

zfirst · **Joined:** Wed Aug 10, 2011 8:39 pm **Posts:** 1

To set work center for rates less than 1 minute; have you tried setting the "capacity per cycle" to the quantity per minute or hour. i.e. if the machine produces 1 per second enter 60 in the capacity per cycle and :01 for the cycle time. I have not tried this but it should work.

steffi · **Posted:** Wed Aug 10, 2011 9:08 pm

I did not try as well - but just thinking of this idea: wouldn't it make more sense to set the unit "readable"? If an operation takes 12 seconds I would like to get this information at first sight when I open a routing.....

mihai · **Joined:** Tue Jan 18, 2011 5:16 pm **Posts:** 236

@primax

I cannot test your scenario as I cannot set

Quote:

form work center time per cycle 1 sec

That is my main problem.

@zfirst

I will try your suggestion as it seems to give some good values

@steffi
I would love to see only one kind of time representation, HH:MM:SS.
Not decimal hours somewhere and time format 24 hours other places, is just confusing.

Thank you all.

mihai · **Joined:** Tue Jan 18, 2011 5:16 pm **Posts:** 236

@loops

I like your idea. Is even more elegant and flexible.
Is now about which one is simpler to implement:
- increase decimal precision
- add UOM for Value.

I have no great knowledge of python, but seems that decimal precision would be simpler.
I just want to have it usable as soon as possible. Either way.

Thanks