The illustrates the relationship between these technical

The distinction between
‘effectiveness’ and ‘performance’ shows that MOEs and MOPs are formulated from
different viewpoints. An MOE refers to the effectiveness of a solution and is
independent of any particular solution; an MOP refers to the actual performance
of an entity selected solution. The MOE refers to the stakeholders’
intention, whereas the MOP is concerned with actual performance of the
supplier’s solution, which may be quite divorced from the stakeholders’
intentions. Thus, an MOE can be used to validate that the system meets the
users’ intended needs, and an MOP can be used to verify the system meets the
users’ stated requirements. This in turn enables the requirements to be
validated to meet the users’ intended needs.


After the solution
alternative has been selected, the TPMs then provide a lower level view of
specific aspects of the performance of the solution. The lower level measures
(MOPs and TPMs) should be defined with the higher-level measures (MOEs and
MOPs) in mind in order to ensure the measures can be aggregated to provide the
necessary insight for system and operational decisions.


Figure 1 illustrates the
relationship between these technical measures and KPPs 6. It shows the
concept of TPMs being derived from MOPs, and MOPs from MOEs. It also shows that
KPPs are generally derived from (but not limited to) MOEs and are a primary
influence on the selection of the MOPs. As we move from MOEs to MOPs and then
to TPMs, the fidelity of the technical insight and ability to get more frequent
insight increases.

Literature Survey

The NASA Systems
Engineering (SE) Handbook 6 identifies MOEs, MOPs and TPMs as technical
measures which are required as inputs for technical assessment of a
program/project. MOE is measure by which a stakeholder’s expectations will be
judged in assessing satisfaction with products or systems produced and
delivered in accordance with the associated technical effort.