Project Delay

customization

(Dave Dortman) #1

We are looking for a way to track project delays in Epicor. As in, a customer doesn’t make a required progress payment, then we have a “customer delay” and don’t work on the projects. We added a custom drop-down menu to the project entry.

This tells us what the delay is, but I would like to track how long each delay happens for. Eventually be able to report on the different type of delays across projects. “Projects over $100,000 on average have 2 weeks of customer delays” for example.

I don’t see anything pre-built in the system for this, so looking for ideas!

Thanks,
Dave


(Brandon Anderson) #2

I don’t have a lot of experience with tasks, but could you create a task that is called customer delay? I think that they have start and end dates related to them, and you could add up the time there. Again, we don’t use tasks here as we’ve found the task system too difficult to work with, but it’s just an idea.


(Dave Dortman) #3

Agree. We have tried tasks but doesn’t quite have the functionality we are looking for.


(Brandon Anderson) #4

another idea you could try, would be to turn on the logging for that field. You might be able to go through the list and determine start and end dates for when statuses change.


(Ernie Lowell) #5

If your Status field is a custom dropdown, then any logic you want attach to it will also have to be custom. This one looks like it can get complicated pretty quickly, as you might have multiple status changes on a particular project, and with each change you’ll need to do date math to add to your “delay days” bucket. If all you need is the total number of days when the Status equals “delay”, you can probably do that with another couple of UD fields on the Project table, but if you want to actually track each individual status change you’ll probably need a child UD table.


(Mark Wonsil) #6

I still like Brandon’s idea but how about with a Delay Phase? It will still have a start, end, and completion date. You can assign people (Finance) tasks to complete to get the payment made. Same for engineering approvals. Someone should still manage the delay. Now you have a phase for each delay and the duration of that delay. You could also make the phase a sub-phase of the waiting phase to show which phases are getting held up the most.

Mark W.


(Dave Dortman) #7

Brandon Anderson, Mark_Wonsil

Agree, Delay Phase is probably the simplest and easiest to implement. As we progress, I will post updates.

Thanks all for the ideas!