RTC Formal Planning showing incorrect load and tasks at wrong place
I have a client who is using formal planning process in RTC version 6.0.5. I have following team structure
One answer
In my experience over the years the problem was more often than not the (wrong) configuration of RTC rather than a defect in RTC. From the description, I don't know what could be the reason here. One factor I am aware of that can cause "more available hours than expected" is that some users specify "parallel" iterations. e.g. an iteration Milestone 1 from Feb 1 to March 3 and another iteration ReleaseTest from Feb 1 to March 6. This would cause more than double of the time counted. I would also carefully check where each resource is really assigned and with what percentage. Maybe test this out in a small test system with only few members.
Also be aware what bars and data is shown e.g. load and progress https://jazz.net/library/article/586
Your second symptom: too few data available. If you see stuff where it is not supposed to be I would check the owners in the plans and the plan configuration.
Comments
We do have parallel iterations in the project area.
We have a project concept for which we have project teams and project iterations. Each project iteration has its own timeline that can be in parallel to other project iterations. The project plans owner are project team and iteration is one of the project iteration.
For routine work we have a complete organization hierarchy and each team in that hierarchy has plan owned by that team and iteration as quarter iteration. Quarterly iterations are parallel to project iterations.
A resource can be part of multiple teams and the resource allocation is done each quarter by using the date ranges and the percentages in the plan.
Timelines can be parallel. What is not supported is defining overlapping iterations within one timeline. Within a timeline iterations of each level must partition the interval they specify.