MIL-HDBK-502 - Barringer and Associates, Inc.

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICSThe functional decomposition of requirements continues to the lowestlogical breakdown of a performance function. At this point the top-downdesign becomes a bottom-up build. Synthesis of the physical design beginswhen hardware items are selected to provide identified functions and arearranged in a physical relationship with one another. During this stage ofthe design’s development, analysis is used to verify adherence to eachsuccessively higher level of requirement. Estimates and projections arerefined and verified through demonstrations and tests.ProcessInputRequirementsAnalysisModelingRequirementsLoopSystem LevelTradeoffsFunctional Analysis/AllocationSystem Analysisand Control(Balance)EquipmentLevelTradeoffsSimulationDesignLoopVerificationTestingSynthesisProcessOutputFigure 4-3. Systems Engineering Process FlowSystem analysis and control activities in a program serve as a basis forevaluating alternatives, selecting the best solution, measuring progress, anddocumenting design decisions. These activities include:• Trade-off studies among requirements, design alternatives, and othercost, schedule and performance related issues.• Risk management that, throughout the design process, identifies andevaluates potential sources of technical risks based on the technologybeing used, the design, manufacturing, test and support processes beingused, and risk mitigation efforts.• Configuration management to control the system products, processesand related documentation. The configuration management effortincludes identifying, documenting, and verifying the functional andphysical characteristics of an item; recording the configuration of anitem; and controlling changes to an item and its documentation. Itprovides a complete audit trail of decisions and design modifications.4-13
MIL-HDBK-502: ACQUISITIONALOGISTICS4.3.1 Supportability• Data management to capture and control the technical baseline(configuration documentation, technical data, and technical manuals),provide data correlation and traceability, and serve as a ready referencefor the systems engineering effort.• The establishment of performance metrics to provide measures of howwell the technical development and design are evolving relative to whatwas planned and relative to meeting system requirements in terms ofperformance, risk mitigation, producibility, cost, and schedule.• The establishment of interface controls to ensure all internal andexternal interface requirement changes are properly recorded andcommunicated to all affected configuration items.• Structured program review to demonstrate and confirm completion ofrequired accomplishments and their exit criteria as defined in programplanning.Determining the best set of planned logistic resources for a system is thefunction of the acquisition logistics discipline of systems engineering. It isaccomplished through analysis of those design characteristics whichgenerate a need for, or are associated with, providing operational supportto the total system. These design characteristics are developed by manydifferent disciplines pursuing a wide range of systems engineering activities.Individually they may be viewed as either hardware, software, or supportsystem design characteristics. Collectively they represent the“supportability” of a total system.Supportability is the degree to which system design characteristics andplanned logistics resources meet system peacetime and wartimerequirements. Supportability is the capability of a total system design tosupport operations and readiness needs throughout the system’s service lifeat an affordable cost. It provides a means of assessing the suitability of atotal system design for a set of operational needs within the intendedoperations and support environment (including cost constraints).Supportability characteristics include many performance measures of theindividual elements of a total system. For example: Repair Cycle Time is asupport system performance characteristic independent of the hardwaresystem. Mean Time Between Failure and Mean Time to Repair arereliability and maintainability characteristics, respectively, of the systemhardware, but their ability to impact operational support of the total systemmakes them also supportability characteristics.Supportability characteristics of the total system interrelate thecharacteristics of the individual designs to provide a top-level assessmentof the balance in a total system’s design. Operational availability (A o ) andlife cycle cost are generally accepted as measures of total system4-14
Page 3: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 76 and 77:
MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
show all

MIL-HDBK-502 - Barringer and Associates, Inc.

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

Delete template?

Save as template?