ValueTypeValueRange appears when you have a collapsed reference mode pattern on an EntityType. In this case, there are two collapsed locations where you can attach a ValueRange. The first location is on the far identifying role and is controlled by the ValueRange property. The second location is on the ValueType itself. This is the location associated with the ValueTypeValueRange property. The goal is to let you control whether the value ranges are applied as a RoleValueConstraint (applies only to the values used in the existential predicate) or to the ValueType (applies to anyone using that ValueType).
NORMA displays the role value constraint with a collapsed EntityType, but we wanted to give you a way to control and view the ValueType range as well.
Note that for the popular reference mode pattern, the ValueType is generally attached to the existential predicate only, so it doesn't really matter where you put the constraint. For example, if you limit Gender(.code) to 'M', 'F', then it doesn't matter much if you apply the constraint to the far role of the existential FactType or the Gender_code ValueType itself. However, if you have PersonHeight(cm:), then you don't want to limit the cmValue ValueType--which is used by any other entity with a cm: reference mode--to 250, you want to limit the role. So, in the unit-based and general reference mode cases it does matter whether you set the ValueRange or the ValueTypeValueRange properties.
You can see more of what is going on by setting the ExpandRefMode property on the EntityTypeShape to true.