To complete mission engineering, I need to be able to :

• Bind measurement sets to conditions
• Decompose measurement sets between multiple levels of fidelity (ie, measurement sets of 'parent' elements to measurement sets of 'child' elements)
• Associate measurement sets to system behaviors performed in context
• Associate conditions elements to context of the mission engineering thread
• Calculate multiple values of a measurement set and bind those values to other measurement values
• Map a single measurement instance back to multiple measurement values
  Current "measurement set def" and "Actual measurement Set" don't meet these needs. I can show the example to demonstrate where UAF 1.3 is lacking. We may be able to use the "Variant" element in UAF v2 to meet many of these needs.

In dtc-24-11-03, Figures 9:51 and 9:52 show Opportunity related to Challenge via a PresentedBy relation. This contradicts the textual description of the PresentedBy relation as "A tuple denoting that a Challenge must be overcome for addressing a Driver." PresentedBy should not appear at all in Figure 9:51 and, in Figure 9:52, "Driver" should replace "Opportunity" and the role end name should also be updated. This will align the DMM with the descriptions on pages 60-61 of the UAFML (dtc-24-11-01).

Note that these issues are also present in the v1.2 spec (different page numbers).