Configuration & version control

Alison Walton

My company is starting to use ProVision and Knowledge Exchange for documenting business processes. I am setting up the environment and guidelines for use of the tools and am looking at how we should handle configuration control and versioning.

 

Our processes are currently documented in individual Word documents and versioning is controlled at the document level – when there is a change to a process definition document, the process is assigned a new version number.

 

With PV & KE, we will have notebooks of the processes at various stages (development, release etc). I would be interested to know how others have addressed configuration control and versioning of processes (in particular, handling issues like processes sharing objects and models and modellers being able to update objects in KE without necessarily checking them out).

 

Thanks for any help.

Alison

John Grygorcewicz

You may want to look at dimensions for this. Dimensions can be at the model level or the object level so that you would need to develop a modeling standard as to which you would use for what purpose. In this way you can deploy a specific version of a model but still have the ability to change the individual versions of objects on that model.

 

Cheers

John