Perhaps, some clarification.
While the functionality is called "Time-Aware Modelling", it is just (such a simple word!) linked clone management.
We were about to create our own cloning technology when Sparx provided this. Now, one might argue that the problem has been misunderstood (from a Time-Aware point of view), the underlying technology implemented by Sparx seemed sufficiently close to what we had intended to create that it was worth investigating.
Once you "get your head around" what Sparx have actually implemented (as usual, Sparxians and humans think a bit differently), it is quite usable (at least in our usage). BTW, we had previously "hijacked" the version field for a specialised use, but Sparx's use of the field for cloning purposes actually allowed us to continue to use it for our original purposes and yet mesh in with the cloning use. We use ONLY textual versions, related to the location of the item in the repository.
So, we ran some tests and it seemed to be OK to use in production. So, we're piloting it in production and apart from the two issues I've noted (so far) it's working quite well.
In our usage, the clones are (principally) project specific clones of enterprise objects, which are changed as required. We will later merge any useful changes back to the source.
Since the notion of multiple instances of the same notional object wasn't built in to EA, this is probably as good as it's going to get.
Paolo
