Jane, we are in the process of generating best practice "Model Branching" work instructions . Branching creates a separate copy typically for Development. Branching provides the ability to merge the changes back into a/the original main (i.e. Production) branch. The benefit we see for this is that concurrent development can occur in both the main branch and the "Development" branch. As I mentioned we are working on best practice for CDM's, and EAM's for a specific data realm production environment (i.e. current state), and the future state environment (i.e. a "Development" branch) that is being implemented via a Project work effort. Once the Project is elevated to Production, the "Development" Project branch would be merged back into the Production main branch. As I said, we are in the process of vetting this and running out use case scenarios to ensure it meets our needs. Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.