Human Factors and Model Based Systems Engineering Chris Vance Head of Human Factors MBDA This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Overview • Why worry about the End User? • Case Studies • Human Factors and Systems Engineering • Human Factors and MBSE • Modelling the User/s • Conclusions Ref.: Page 2 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Quote: “The most volatile part of a system is its users’ ????? behaviour” From “The Object Advantage” by Ivar Jacobson (Systems Engineering guru and one of the Founding Fathers of UML) Ref.: Page 3 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Humans are a major performance driver • Humans have a major impact on system safety • Humans are a major cost driver through life Ref.: Page 4 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: Physical • Single Role Mine Hunters • Unit retrieval from the sea too difficult due to pitch and role of the ship, particularly in high sea states • Manual handling problem underestimated during development • To rectify, ship modifications included a better crane, operator platform, additional recovery hook and pole • Estimated cost of design changes £1.9 million Ref.: Page 5 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: Personnel • M1 Battle Tank • HFI was applied to the M1 series of battle tanks. The earlier M60 tanks showed that performance correlated with user intellect. • An Early Comparability Analysis (ECA) showed clearly that, by redesigning for a range of crew abilities, high system performance could still be achieved and now any M1 crew out-performs the best M60 crew. *AFQT - Armed Forces Qualification Test Ref.: Page 6 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: Cognitive / Organisational • Minx • Replacement for mine laying equipment • Training Requirements • Authority levels • Would require all NCO’s and no ‘Sappers Ref.: Page 7 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: Environment • MLRS • Environmental considerations -Reload time 8 times longer for trained service personnel in the field than when demonstrated by the contractor on hard standing • Understanding of the system -35% more reliability achieved when demonstrated by contractors, than when used by service personnel Ref.: Page 8 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: Ergonomics / Health Hazards • Stinger • System Complexity -18 steps required for operating weapon -Temporal aspects of the task • Emits high levels of Hydrogen Chloride when fired. Gunner must close eyes and hold his breath for 2 seconds after firing • Weighs 35lbs compared with the 30lbs recommendation • Hit Probability -Designed performance: 0.6 -Actual performance: 0.306 Ref.: Page 9 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Why worry about the End User? • Case Study: System Safety • Airbus A320 – Alsace • Herald of Free Enterprise • Boeing 737 – Kegworth • USS Vincennes • Chernobyl Ref.: Page 10 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors and Systems Engineering • In simple terms, HF aims to answers these questions: . . . Can This Person . . . . . . . With This Training . . . . . . . Do These Tasks . . . . . . . . To These Standards . . . . . . . Under These Conditions? • Goal of HF: • “To ensure that we design systems which match the needs and abilities of the users” Ref.: Page 11 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors and Systems Engineering Human Factors Integration (HFI) is the MOD process by which the Human Factors Integration People Component of Capability is considered during Capability Delivery It is a systematic process for People Technology identifying, tracking and resolving Capability human-related concerns ensuring a balanced development of both technologies and human aspects of Capability. Processes It aims to optimise the overall system performance by balancing Environment human capabilities and characteristics with those of the hardware and software Ensure the human component of the system is effectively included in the trade-off process Ref.: Page 12 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors and Systems Engineering • HFI involves the identification and trade-off of people-related aspects that could impact Capability development and delivery. This is facilitated by a framework of 7 Domains: Ref.: Page 13 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors and Systems Engineering Software Engineering Capability R&M Analysis Engineering Aeronautical Training Engineering Human Factors Human Manufacturing Systems Factors Engineering Engineering Integration Engineering Electrical Safety Engineering Engineering Mechanical Logistics Engineering Engineering Test Engineering Ref.: Page 14 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors and Systems Engineering • HFI Process Decisions on Requirements Decisions on Definition Decisions on Implementation ESTABLISH THE UNDERSTAND DESIGN & DEFINE DEVELOP ASSESS SYSTEM VIEWPOINTS SYSTEM SYSTEM SYSTEM REQUIREMENTS System System System Viewpoint Definition Implementation Requirements Objectives This may look like the System Engineering Process. HFI IS part of the System Engineering Process!! Ref.: Page 15 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors within MBSE • Model-based systems engineering (MBSE) is formalised application of modelling to support : • System requirements • System design • System analysis • System verification and validation. • MBSE should support these activities from the Concept phase and continue throughout Development and later life cycle phases. (INCOSE definition) Ref.: Page 16 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Human Factors within MBSE • Management Activities ensure that relevant questions are asked • Technical Activities ensure that these questions are answered Define Problem & Understand Context Agree System System Requirements Validation Assessment – Define Trade Studies System Functional & Supporting Verification Architecture Processes Define Element Physical Integration Architecture Develop System Ref.: Page 17 - This document and the information contained herein is proprietary information of MBDA and shall not be disclosed or reproduced without the prior authorisation of MBDA. MBDA 2011.
Recommend
More recommend
