Is anyone using CA PPM on demand 15.2 with MSP successfully?
We are facing a showstopper in our transition rollout in using CA PPM, because whenever we try to save a schedule into Clarity with Remaining work, in CA PPM when you view the ETC By Period for the task in a weekly time scale, CA PPM has the total Remaining work correct, but the weekly view does not match the Time Scale view in MSP.
We have tested with:
We get mixed results based on the work contour as well in MSP.
I find it very hard to believe that no other clients are facing this issue! This is a huge show stopper for us.
We were not aware that there were so many existing issues with CA PPM and Microsoft Project.
https://communities.ca.com/message/241787088 - There is a thread in CA community which is almost of same kind of issue as same as we have. vtleogal2
We have been using MSP 2010 with CA PPM for several years and have experienced a wide variety of challenges using the two applications together. If you are using the CA PPM weekly timesheet to capture actual work on project assignments as we are, the scheduling environment becomes even more complex due to team member time reporting behavior.
We are currently on CA PPM v15.2 and use the legacy connector with MSP 2010. I have not seen the specific issue you describe with time scale view differences in weekly ETC, but here are a few things we have done to overcome some of the challenges we’ve experienced using MSP with CA PPM:
Loading patterns also influence how MSP schedules tasks, and we use recommended “Uniform” loading pattern in CA PPM which maps to Flat in MSP. If you use a Fixed loading pattern (Contoured in MSP), MSP will change the loading pattern back to Uniform/Flat if there is a gap between actual work and remaining work. There is a KB article about modifying the registry setting to force MSP to retain the Fixed/Contoured loading pattern, but we have not tested it and hesitate to control MSP scheduling behavior at the registry level. Also, each time the CA PPM connector to MSP is reinstalled, the registry setting is over-written and you will to need modify it again. To further complicate the scheduling landscape, we often have multiple people who download and update project schedules, so this registry setting must be changed on every machine. You can see where this is going… a lot of extra work for your IT support team and an increased potential that it will be missed when you upgrade.
I hope this information is helpful.
Katie Fears, Clarity PPM Team Lead
California State Teachers' Retirement System
Can you try with Uniform loading pattern and one of these combinations?
15.2 + new driver has a hard requirement of at least February 2016 patch, but November 2017 has already been validated and fixes some earlier defects in the MSP tool:
Release Notes (On Premise) - CA PPM - 15.2 - CA Technologies Documentation
How do Microsoft Project monthly patches impact CA PPM?
Countour has different implications in PPM than in MSP. Each software has its own business logic and MSP will rearrange it according to his own; PPM won't unless you do autoscheduling from the PPM Gantt. Also, regardless of that, MSP is a scheduling tool and the way the integration is built around it requires automatic scheduling, see: How to Configure Default Settings in Microsoft Project to use with PPM. We recommend using only one tool (either PPM, MSP or OWB) when scheduling projects.
MSP is also expected to move around some dates in certain circumstances when using the new driver, as this is the way MSP autoschedules:
If you create a task in CA PPM that is not pinned through a dependency, and the task does not start on the project start date, define a constraint. The Microsoft Project Interface does not automatically put a constraint on a task and move the date.
Manage Projects with Microsoft Project (MSP) - CA PPM - 15.2 - CA Technologies Documentation
we dropped MSP. We are only using OWB and doing well with it.. thanks!