Clarity

  • 1.  Changing Over Workbench to Microsoft Project (Pitfalls, Lessons Learned, Transitional Advice)

    Posted Apr 16, 2015 09:00 PM

    Hi All,

     

    It's becoming increasingly likely in our business that we'll be changing over from Open Workbench to Microsoft Project simply due to the preference of our Project Managers. I have heard that it's not recommended to change over which software is being used for in-flight projects, which means I know there will be a transitional period. Not sure if this true - does anyone know the specifics on this?

     

    I was also wondering if anyone else has been in a situation in their work where they've lead a transition from one to the other, and if they identified any issues or ran into anything unexpected during the transitional period. I know it's as easy as changing the Project Scheduler attribute, but I want to make sure there's not a lot more to it trying to get projects (we have over 100 active) changed over.

     

    Thanks for any helpful advice or comments!

     

    Matthew



  • 2.  Re: Changing Over Workbench to Microsoft Project (Pitfalls, Lessons Learned, Transitional Advice)
    Best Answer

    Posted Apr 17, 2015 04:31 AM

    You can check these -

     

    How do we switch from OWB to MSP in a SAAS environment

    https://communities.ca.com/message/97449391#97449391

     

    Can a schedule created in OWB be opened in MSP?

    https://communities.ca.com/message/107134671#107134671

     

    MSP versus OWB - Clarity PPM User Group Meeting _ CANADA.pdf

    https://communities.ca.com/docs/DOC-14632625

     

    Compare MSP vs OWB with Clarity.pdf

    https://communities.ca.com/docs/DOC-15227494

     

    NJ



  • 3.  Re: Changing Over Workbench to Microsoft Project (Pitfalls, Lessons Learned, Transitional Advice)

    Posted Apr 17, 2015 07:17 AM

    Have you analysed how MSP manages resources of a master project and its sub projects compared to OWB?

    There is an enhancement raised with CA for plugin to take care of an issue reported.



  • 4.  Re: Changing Over Workbench to Microsoft Project (Pitfalls, Lessons Learned, Transitional Advice)

    Posted Apr 19, 2015 06:09 PM

    Thanks for this NJ. I did a couple searches on the community and didn't bring those threads up. Weird. I appreciate the search around for me. I'll have a read through these documents and see how it ends up. Thanks!

     

    Matthew



  • 5.  Re: Changing Over Workbench to Microsoft Project (Pitfalls, Lessons Learned, Transitional Advice)

    Posted Apr 20, 2015 03:29 AM

    Welcome, Matthew

     

    NJ