In MD SysML the technique illustrated here must be supplemented by <<BlockPackage>>/<<BlockModel>> concept, since (consistent with the UML2.1.2 spec.) MD SysML does not permit the ownership of InstanceSpecifications by a block, and so a <<ValueSlice>> block can't own the <<Values>> InstanceSpecifications it "manages". It turns out this has some benefits; it makes sense to package all engineering data, and even icons and images, together with the owned <<Block>>. This scales well to <<TimeSlicePackage>> for a <<TimeSlice>> block, and to a <<ConfigurationPackage>> for a <<Configuration>> block.
Note that in the diagram below the <<Values>> are indicated as being under shared aggregation by their <<ValueSlice>> Block, although they must actually be owned by the <<ValueSlicePackage>> that also owns the <<ValueSlice>> Block. This emphasises that the <<ValueSlice>> manages the <<Values>> and applies them to the root part (the Block usage) and that Block's deeply nested parts, although the <<Values>> are owned by a BlockModel or BlockPackage.
Thanks are due to Nerijus Jankevicius, Alain Isoz and the MD SysML Team for input and collaboration on this evolving proposal.
