Analysis Techniques For Man-Machine Systems Design

Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design

ai.eecs.umich.edu
from ai.eecs.umich.edu More from this publisher
11.07.2015 Views

N ATO UN CLA .3 -c,,i! EAC/243(Panel-g)TR17- 4 -analyses are often conducted well before the project is initiated. by a scparate agency, and the results may not bedisseminated to either the project management or the performing agency, due to their security classification.Analyses conducted for other systems engineering studies can provide much of the information required for missionand scenario analysis. Recommended approaches to systems engineering (US Defense Systems Management College,1990, US Department of the Army. 1979) stress the need to conduct mission analyses to derive the systemrequirements and define the operational environment and the constraints on the system. These mission analysesprovide a link between the human factors/buman engineering analyses and other system engineering activities.For example, on a recent project to study crew workload in a tactical helicopter it was discovered that detailedoperational missions had been prepared and evaluated to identify the loading on the helicopter rotor system. It wascomparatively easy to take those analyses and revise them to show operator activity, since changes in rotor loadingimplied pilot input and tactical decisions. The resulting human engineering analyses were an excellent starting pointfor the crew workload studies.Types of analysis availableThere are two basic types of analysis in this category. Narrative mission descripions provide a written or point tormdescription of a mission, and graphic mission profiles provide the mission information in graphic form.Table 1.1:Applicability of mission and scenario analysis techniquesto different projectsTechnique Simple system (e.g. Medium complexity High complexity Complex multi-manrifle, hand-held radio) system (e.g., 1-man system (e.g., 1-place system (e.g.. shipradar consoie) attack aircraft) combat centre)1.1 Narrative mission high high high mediumdescription1.2 Graphic mission not recommended not recommended high highprofilesReferences and Bibliography1. Meister, D. (1985). Behavioral analysis and measurement methods. New York: Wiley Interscience.2. US Department of Defense (1987). Human engineering nrocedures iude. Washington D.C.: DoD-HDBK-76 3 .3. US Department of the Army (1979). System engineering. Washington D.C.: Headquarters, Dcpt. of the Army.FM 770-78.4. US Defense Systems Management College (1990). System engineering management guide. Washington D.C.:U.S. Government Printing OfficeNATO UNCLASSIFIED-4 -

NATO UNCLASSIFIED. 5 AC/243(Panel-8)TR/7Volume 2:ge, 1.1 NARRATIVE MISSION DESCRIPTIONSaWhat the technique doesNarrative mission descriptions (sometimes called "Mission Scenarios") describe the events of a mission in detail. Thedescription should be sufficiently detailed to permit identification of the major mission phases, the major systemfunctions, the time-scale of activities, and the "external" events which dictate the activities of the system. Wheremultiple missions are to be performed by a system, each should be described or a "composite" mission descriptionshould be developed which identifies all of the unique mission activities, avoiding repetition of common activities.Examples of the technique have been published by Ddring (1976), Lindquist, Jones & Wingert (1971), and Linton,Jahns & Chatelier (1977).I1Inputs to the techniqueInformation is required from the operational analyses usedto identify the operational requirement (Mission NeedDocument, in NATO). Required information includes thesystem missions, required capability, operationalenvironment, and system dynamics and constraints. Theanalysis should draw on any Monte Carlo simulationsthat may have been run to develop mission time lines.Input from subject matter experts with experience ofsimilar missions or similar equipment is essential.Outputs of the techniqueThe descriptions document the characteristics, sequencesand times of mission events. mission constraints andenvironmental conditions. A description may be in ahighly structured, point-by-point form, or a free-flowingnarrative. It may describe several missions, or missionsegments, or one composite mission. The outputs of thetechnique should be sufficiently detailed to identify theupper level functions performed by the system (seeSection.2 Function Analysis).When to useThe technique should be used at the outset of the human engineering analyses conducted during the conceptdevelopment phase. The work may be re-iterated in greater detail at the start of the preliminary design phase.The analysis is a necessary precursor to all human engineering analyses, unless the information is available from theanalysis of identical systems.Related techniquesNarrative mission descriptions are related to the mission descriptions and early performance parameter studies carriedout to establish Mission Need Documents, or as part of the system engineering activities.Resources requiredThe advice of experts with operational experience of similar missions and systems is essential to the preparation ofthe analysis. Access to documentation on similar systems and to the system requirements analysis is extremelyuseful. No significant technical resources are required.NATO UNCLASSIFIED-5-

NATO UNCLASSIFIED. 5 AC/243(Panel-8)TR/7Volume 2:ge, 1.1 NARRATIVE MISSION DESCRIPTIONSaWhat the technique doesNarrative mission descriptions (sometimes called "Mission Scenarios") describe the events of a mission in detail. Thedescription should be sufficiently detailed to permit identification of the major mission phases, the major systemfunctions, the time-scale of activities, and the "external" events which dictate the activities of the system. Wheremultiple missions are to be performed by a system, each should be described or a "composite" mission descriptionshould be developed which identifies all of the unique mission activities, avoiding repetition of common activities.Examples of the technique have been published by Ddring (1976), Lindquist, Jones & Wingert (1971), and Linton,Jahns & Chatelier (1977).I1Inputs to the techniqueInformation is required from the operational analyses usedto identify the operational requirement (Mission NeedDocument, in NATO). Required information includes thesystem missions, required capability, operationalenvironment, and system dynamics and constraints. Theanalysis should draw on any Monte Carlo simulationsthat may have been run to develop mission time lines.Input from subject matter experts with experience ofsimilar missions or similar equipment is essential.Outputs of the techniqueThe descriptions document the characteristics, sequencesand times of mission events. mission constraints andenvironmental conditions. A description may be in ahighly structured, point-by-point form, or a free-flowingnarrative. It may describe several missions, or missionsegments, or one composite mission. The outputs of thetechnique should be sufficiently detailed to identify theupper level functions performed by the system (seeSection.2 Function <strong>Analysis</strong>).When to useThe technique should be used at the outset of the human engineering analyses conducted during the conceptdevelopment phase. The work may be re-iterated in greater detail at the start of the preliminary design phase.The analysis is a necessary precursor to all human engineering analyses, unless the information is available from theanalysis of identical systems.Related techniquesNarrative mission descriptions are related to the mission descriptions and early performance parameter studies carriedout to establish Mission Need Documents, or as part of the system engineering activities.Resources requiredThe advice of experts with operational experience of similar missions and systems is essential to the preparation ofthe analysis. Access to documentation on similar systems and to the system requirements analysis is extremelyuseful. No significant technical resources are required.NATO UNCLASSIFIED-5-

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!