Using NX log files als aid for billing

[hoolito]

Hi,

I normally bill clients on a time and materials basis.
As I work alone, I manually fill a timesheet for each project and this requires the discipline to do it as regularly as possible, in order to not forget what I was doing on each time slot.

In order to be more accurate (and relaxed I was wondering if I could use some of the logging NX does.
I would actually ONLY need the history of start and stop timestamps of which part was "workpart".
Does anyone knows whether NX keeps track of this now?
Or does anyone have an idea of how could this be logged?

In a search prior to posting this I came across this: thread561-281254
But I don't think is the applicable. It is nevertheless too old.

Thanks for any ideas!!

Julian

 

[jerry1423]

Info -> part -> part history
should give you a good general idea on how much time you spent on a project
but if you go into
Info -> part -> modifications -> specify object types
you may be able to decipher more of what was done to the file
as far as help -> Log File goes
there may be things in there for you, but not much for billing purposes

Jerry J.
Milwaukee Electric Tool

http://www.milwaukeetool.com/

 

[hoolito]

Thank you Jerry,

"Part history" lists the save times for one part, and that is not in correlation of how much you worked on that part. Maybe you do a Save All from time to time, but you work mostly on one part. Granted: an unmodified part will not be saved.
It does give you a pretty good idea, but if I were to use this, I would need to check every part of every assembly of every project. (Same problem for "Info -> part -> modifications", and I don't need that granularity)
I get the same data (aggregated) currently from the events log of Dropbox, since I have my working folder synched there. For any given day you see every save of each part in one list.

Ideally I would get this from NX in txt file from where I could parse the data to a spreadsheet. There I could easily group all the times a part has been "work part" and sum all those time slots to a "total time worked per part" on a given time. Handy for billing but also to analyse development times per part.
This total would of course include the time your system open on a part and went eating, but hey.. you can't have it all