ISM as consolidated model?

In our office, often we find ourselves with multiple engineers working on each project.  One engineer may be responsible for the lateral systems, one may be responsible for concrete joists, and a third may be responsible for steel (penthouse, mechanical levels etc).  Further we may have an engineer responsible for coordinating slab edges with architects. With so many people in a model, making daily changes (and backups) things quickly become fragmented.

This leads to a fundamental problem with RAM Structural System that I'm wondering if ISM is capable of mitigating.   My thought is that at the outset of a project, a RAM model is built, then pushed to and ISM repository.  Then, each engineer could maintain their own RAM model split from the original, using update to/from  ISM to stay up to date.  Is this a functional workflow?  Are there potential pitfalls associated with this idea?

If I'm reading this link correctly, then Rebar for concrete elements could be written to the ISM repository, but not read back into RAM models? Is this feature on the development map in the near future?

I'm looking forward to any words of wisdom and/or experience with this idea.