members like us who come from the PLM and PDM world are used to version and revision control. For drawings there can be several versions but the published version is revision controlled. This is where we ensure that form fit and function is taken care of for backward compatibility etc. In aris we have version control. In the workspace if multiple working versions are present for the same process model (activity level) then how do you manage it?
I was wondering if we start think about seperating version and revision control.
Pinaki Ghosh Author on
adding some more details
In any manufacturing organization there are several set of changes which do on like Engineering Change Order which can lead to Manufacturing Change Order and Product Change Order. These are all handled within the PDM or PLM tools using complex methods to accommodate various enterprise wide data synchronization process (including materials management, cut-off). The 2 most common concept are version control and revision control – which are treated separately and differently. In the Engineering world there can be many versions of a drawing but there is only one published “live” revision which actually drives the product and manufacturing change if necessary. I see a similar analogy for ARIS models. There can be multiple versions of a ARIS model based on the waves of “go-live”. There should be only one revision which should drive the product change – which means the next wave of go-live for the IT Products. This can be different from the current “live” model with an effective date matching the go-live date. The current ARIS version control does not seem to be geared towards that but this can be achieved through multiple nested group structure. I was wondering if anybody had any experience of developing such a model.