Skip to Content
0

RevTrac clean up activity in Dev environment. Please help answer questions highlighted in bold.

Jan 26 at 03:52 AM

19

avatar image
Former Member

We're using RevTrac for TR management and change control. I'm in a situation where we have a lot dead RevTracs (i.e. RTs with transports tagged to it but not used for more than 6 months and year) in our DEV environment. I'm planning to clean these RTs (~500 in numbers) from DEV. This clean up activity would be a project itself because we got to unlock the components manually from each TR of each RT. Some of questions w.r.t. this activity I've in my mind is that:

1. How do I accurately estimate the effort required to get rid of 500 dead RTs?

One way is to get the no. of TRs (workbench and Customizing) in each RT. Unlocking/deleting components from customizing TR would generally involve less effort that freeing components from a workbench TR. Depending on the no. of components locked, we can roughly determine a manually effort required (say 2 hours for customizing and 5-8 hours for workbench request. Could you advise other approach to get to an estimation.


2. What are the advantages and disadvantages of this exercise.

Some disadvantages I can think of is, this exercise may hold the progress of other projects which are being done in the same DEV environment. Could you advise more on advantages and disadvantages.

3. Is there an efficient way to do this clean up activity?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers