CUVX Design Report - the AOE home page - Virginia Tech

More documents

Recommendations

Info

CUVX Design – VT Team 2 Page 36OMORHierarchyAHPOMORWeightsOMORFunctionRequirements andconstraints for alldesignsProbabilitiesandConsequencesMissionDescriptionROCsMOPs,Goals &ThresholdsMAVTDPsVOPFunctionsCostModelRisk IndexTentativeScheduleOMOEHierarchyAHPMOPweightsOMOEFunctionFigure 21. OMOE and OMOR Development Process3.5.1 Overall Measure of Effectiveness (OMOE) (Appendix D.1 CUVX Ship Synthesis Model, Module 11)Figure 21 illustrates the process used to develop the CUVX OMOE and OMOR. Important terminology usedin describing this process includes:• Overall Measure of Effectiveness (OMOE) - Single overall figure of merit index (0-1.0) describing shipeffectiveness over all assigned missions or mission types• Mission or Mission Type Measures of Effectiveness (MOEs) - Figure of merit index (0-1.0) for specificmission scenarios or mission types• Measures of Performance (MOPs) - Specific ship or system performance metric independent of mission(speed, range, number of missiles)• Value of Performance (VOP) - Figure of merit index (0-1.0) specifying the value of a specific MOP to aspecific mission area for a specific mission type.There are a number of inputs which must be integrated when determining overall mission effectiveness in anaval ship: 1) defense policy and goals; 2) threat; 3) existing force structure; 4) mission need; 5) mission scenarios;6) modeling and simulation or war gaming results; and 7) expert opinion. Ideally, all knowledge about the problemcould be included in a master war-gaming model to predict resulting measures of effectiveness for a matrix of shipperformance inputs in a series of probabilistic scenarios. Regression analysis could be applied to the results todefine a mathematical relationship between input ship MOPs and output effectiveness. The accuracy of such asimulation depends on modeling the detailed interactions of a complex human and physical system and its responseto a broad range of quantitative and qualitative variables and conditions including ship MOPs. Many of the inputsand responses are probabilistic so a statistically significant number of full simulations must be made for each set ofdiscrete input variables. This extensive modeling capability does not yet exist for practical applications.An alternative to modeling and simulation is to use expert opinion directly to integrate these diverse inputs,and assess the value or utility of ship MOPs in an OMOE function [1]. This can be structured as a multi-attributedecision problem. Two methods for structuring these problems dominate the literature: Multi-Attribute UtilityTheory and the Analytical Hierarchy Process. In the past, supporters of these theories have been critical of eachother, but recently there have been efforts to identify similarities and blend the best of both for application in Multi-Attribute Value (MAV) functions. This approach is adapted here for deriving an OMOE.The process described in Figure 21 begins with the Mission Need Statement and mission description presentedin Chapter 2. Required capabilities (ROCs) are identified to perform the ship’s mission(s) and measures ofperformance (MOPs) are specified for those capabilities that will vary in the designs as a function of the shipdesign variables (DVs). Each MOP is assigned a threshold and goal value. Capability requirements and constraintsapplicable to all designs are also specified. Table 23 summarizes the ROCs, DV and MOPs definition for CUVX.An Overall Measure of Effectiveness (OMOE) hierarchy is developed for the MOPs using the Analytical HierarchyProcess (AHP) to calculate MOP weights and Multi-Attribute Value Theory (MAVT) to develop individual MOPvalue functions. The result is a weighted overall effectiveness function (OMOE) that is used as one of threeobjectives in the multi-objective optimization. In the AHP, pair-wise comparison questionnaires are produced tosolicit expert and customer opinion, required to calculate AHP weights. Value of Performance (VOP) functions
CUVX Design – VT Team 2 Page 37(generally S-curves) are developed for each MOP and VOP values are calculated using these functions in the shipsynthesis model. A particular VOP has a value of zero corresponding to the MOP threshold, and a value of 1.0corresponding to the MOP goal.Figure 22 illustrates the OMOE hierarchy for CUVX derived from Table 23. Separate hierarchies aredeveloped for each mission or condition (pre-conflict, conflict and post-conflict) for CUVX. MOPs are groupedinto six categories (ship combat, sustainability, mobility, vulnerability, susceptibility and airwing combat) undereach mission. MOP weights calculated using expert opinion are compared in Figure 23. The CUVX VOP curve forsustained speed (MOP 15) is illustrated in Figure 24. Other VOP curves and functions are similar. MOP weightsand value functions are finally assembled in a single OMOE function:OMOE = g VOP[ ( MOP )] = w VOP ( MOP )ii∑iiiiFigure 22. OMOE HierarchyWeight0.140.120.10.080.060.040.020SEAD - MOP30ISR - MOP31Seakeep - MOP16AAW - MOP1RCS - MOP26Mine - MOP34Acoustic - MOP24Hull - MOP20DC - MOP22DamStability - MOP18ASW - MOP32ASuW - MOP33Strike - MOP28Air Fuel - MOP12Figure 23. MOP WeightsAir Weapons - MOP11IR - MOP23Stores Duration - MOP10CBR - MOP21Redundancy - MOP19Reliability - MOP13Range - MOP9Repair - MOP14Speed - MOP15Figure 24. Value of Performance Function for Sustained Speed
Page 1: CUVX Design ReportUnmanned Combat A
Page 5 and 6: CUVX Design - VT Team 2 Page 54.12
Page 7 and 8: CUVX Design - VT Team 2 Page 7feasi
Page 9 and 10: CUVX Design - VT Team 2 Page 92 Mis
Page 11 and 12: CUVX Design - VT Team 2 Page 11ROC
Page 13 and 14: CUVX Design - VT Team 2 Page 13cata
Page 15 and 16: CUVX Design - VT Team 2 Page 15powe
Page 17 and 18: CUVX Design - VT Team 2 Page 17much
Page 19 and 20: CUVX Design - VT Team 2 Page 19Tabl
Page 21 and 22: CUVX Design - VT Team 2 Page 21requ
Page 23 and 24: CUVX Design - VT Team 2 Page 23a hi
Page 25 and 26: CUVX Design - VT Team 2 Page 25AAG
Page 27 and 28: CUVX Design - VT Team 2 Page 273.2.
Page 31 and 32: CUVX Design - VT Team 2 Page 31Figu
Page 33 and 34: CUVX Design - VT Team 2 Page 33chec
Page 35: CUVX Design - VT Team 2 Page 35Requ
Page 39 and 40: CUVX Design - VT Team 2 Page 39ROCA
Page 43 and 44: CUVX Design - VT Team 2 Page 43one
Page 49 and 50: CUVX Design - VT Team 2 Page 494 Co
Page 51 and 52: CUVX Design - VT Team 2 Page 51Hang
Page 55 and 56: CUVX Design - VT Team 2 Page 55The
Page 65 and 66: CUVX Design - VT Team 2 Page 65Endu
Page 67 and 68: CUVX Design - VT Team 2 Page 67Fuel
Page 71 and 72: CUVX Design - VT Team 2 Page 71spee
Page 73 and 74: CUVX Design - VT Team 2 Page 73were
Page 75 and 76: CUVX Design - VT Team 2 Page 75Medi
Page 77 and 78: CUVX Design - VT Team 2 Page 77acce
Page 79 and 80: CUVX Design - VT Team 2 Page 79bolt
Page 87 and 88:
CUVX Design - VT Team 2 Page 87Figu
Page 89 and 90:
CUVX Design - VT Team 2 Page 89Figu
Page 91 and 92:
CUVX Design - VT Team 2 Page 91Modu
Page 93 and 94:
CUVX Design - VT Team 2 Page 935 Co
Page 95 and 96:
CUVX Design - VT Team 2 Page 95Refe
Page 97 and 98:
CUVX Design - VT Team 2 Page 97b. M
Page 99 and 100:
CUVX Design - VT Team 2 Page 99Appe
Page 101 and 102:
CUVX Design - VT Team 2 Page 101exc
Page 103 and 104:
CUVX Design - VT Team 2 Page 1038.
Page 105 and 106:
CUVX Design - VT Team 2 Page 105NSF
Page 107 and 108:
CUVX Design - VT Team 2 Page 107row
Page 109 and 110:
CUVX Design - VT Team 2 Page 109V D
Page 111 and 112:
CUVX Design - VT Team 2 Page 1111.0
Page 113 and 114:
CUVX Design - VT Team 2 Page 113The
Page 115 and 116:
CUVX Design - VT Team 2 Page 115i17
Page 117 and 118:
CUVX Design - VT Team 2 Page 117+ P
Page 119 and 120:
CUVX Design - VT Team 2 Page 11912.
Page 121 and 122:
CUVX Design - VT Team 2 Page 121D.3
Page 123 and 124:
CUVX Design - VT Team 2 Page 123Equ
Page 125 and 126:
CUVX Design - VT Team 2 Page 125D.4
Page 127 and 128:
CUVX Design - VT Team 2 Page 127LAU
Page 129 and 130:
CUVX Design - VT Team 2 Page 129too
show all

CUVX Design Report - the AOE home page - Virginia Tech

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?