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

More documents

Recommendations

Info

MIL-HDBK-502: ACQUISITIONALOGISTICSforce structure and support posture. The output of this initial segmentshould be an integrated Operational Requirements Document (ORD) whichreflects an operational and support concept that the user finds acceptable.Following this initial segment, the primary focus of supportability analysesshould be on examining the user’s operational and readiness requirementsusing guidance provided in the Mission Needs Statement and the ORD.The output of the Requirements Analysis segment should identify keyissues or supportability “factors” that should be considered whenoperational needs are later translated into supportability requirements.Supportability factors are those operational needs which, by their nature,impose requirements on the support system and thus affect systemsupportability. Supportability factors may include deployment, mobility,mission frequency and duration, human capability and limitations, andanticipated service life.During the Functional Analysis/Allocation (FA/A) segment, these factorsand other operational needs which affect supportability should be analyzedto establish initial supportability constraints.DeploymentMobilityPlanned deployment scenarios establish the geographical and environmentalconditions in which a system must be operated and sustained. Differentoperating environments impose different design characteristics on aproduct. These characteristics directly affect the types of support requiredand the environmental conditions under which the support must beprovided. For example, just as planned deployment to an arcticenvironment will require a product design which can function underconditions of extreme cold, maintenance and operational support activitiessuch as repair or refueling will have to be performed under the sameconditions. Product designs should reflect the operational need to performsupport functions in environmentally suitable clothing (e.g., arctic clothing,chemical protective clothing, etc.).A unit’s mobility requirements establish planned modes of transport andtime constraints which must be accommodated by the transportabilitycharacteristics of a product. A product which is to be transported byspecific modes of transport such as rail, sea, or air, and within each mode,by specific means (C130, C5A, European rail carriers, etc.) must beevaluated to ensure that it’s design characteristics allow transport by theplanned mode or means. Time constraints, such as 24-hour rapiddeployment, impose further considerations to ensure that the product canbe prepared for transport within the established time. If, for example, aproduct must be sectionalized for transport by a designated means such asa C130 aircraft, then the product must be capable of sectionalization, and5-3
MIL-HDBK-502: ACQUISITIONALOGISTICSthe support system must have the required support items (tools, supportand handling equipment, personnel, containers, etc.) to sectionalize theproduct, prepare each section for transport, and move the sections to thedesignated point of embarkation. Additionally, at the point of debarkation,all of the sectionalization and transport preparation will have to bereversed, meaning the receiving end must have the capability to restore,and verify, the product’s operational state.Mission frequency and durationFrom an operations support standpoint, mission frequency and durationdefine the support resources needed to sustain operations. This factorwould include rearm/refuel, emplacement/displacement, mission profilechanges—in short, those activities which are conducted as a normal part ofoperations. Meeting turn-around time intervals within the anticipatedmission frequencies imposes performance requirements on the supportsystem requiring it to respond to the projected operational demands of theproduct.Quantification of support resource requirements is directly related to thecharacteristics of a product’s design and the frequency and duration of themissions which it performs. Mission frequency and duration and thereliability of the product provide the initial basis for determining the rangeand quantity of support resources that will be required.Human systems integrationHuman beings are an integral part of the performance characteristics of thetotal system. The ease or difficulty of operating and maintaining a productwith acceptable results imposes specific requirements on the product,software, and support system designs. A product which is difficult tooperate by virtue of the complexity of its mission requirements or its designcharacteristics requires individuals with greater cognitive or manualdexterity skills than one which is less complex. The same is true ofsoftware and support. The existing force structure and supportinfrastructure into which the product will be introduced have available acomplement of human capabilities and limitations. For the designs of thetotal system components to minimize their impact on the existinginfrastructure, human capabilities that are available and the limitations thatexist must be identified so that these considerations are included in theanalysis of design alternatives.Anticipated service lifeThe planned service life of a product will have significant impact on thetotal system design alternatives considered and the life cycle costassociated with each. If the program is for a major system and makes a5-4
Page 3: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 9 and 10: MIL-HDBK-502: ACQUISITIONALOGISTICS
Page 84 and 85:
MIL-HDBK-502: ACQUISITIONALOGISTICS
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.

Create successful ePaper yourself

Delete template?

Save as template?