Human Systems Integration (HSI)

Similar documents
United States Air Force (USAF) Human Systems Integration (HSI) Concept of Execution (CONEX)

Defense Acquisition Guidebook Systems Engineering Chapter Update

Department of Defense INSTRUCTION

JITC Joint Interoperability Test, Evaluation, and Certification Overview

Mission-Based Test & Evaluation Strategy: Creating Linkages between Technology Development and Mission Capability

UNCLASSIFIED R-1 ITEM NOMENCLATURE

Acquisitions and Contracting Basics in the National Industrial Security Program (NISP)

Technical Data (an Output of Systems Engineering) in the Context of the LCMC

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE A: Biometrics Enabled Intelligence FY 2012 OCO

Air Force Research Laboratory

The Four-Element Framework: An Integrated Test and Evaluation Strategy

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

UNCLASSIFIED UNCLASSIFIED

UNCLASSIFIED UNCLASSIFIED. EXHIBIT R-2, RDT&E Budget Item Justification RESEARCH DEVELOPMENT TEST & EVALUATION, NAVY / BA-7

CAD/PAD Qualification and Second Source Processes

UNCLASSIFIED R-1 ITEM NOMENCLATURE PE F: KC-10S. FY 2011 Total Estimate. FY 2011 OCO Estimate

Common Range Integrated Instrumentation System (CRIIS)

Joint Operational Effects Federation (JOEF) Briefing to CBIS

DoD Analysis Update: Support to T&E in a Net-Centric World

UNCLASSIFIED FY 2016 OCO. FY 2016 Base

An Independent Perspective From a former PM & PEO. NDIA 13th Annual Systems Engineering Conference 26 Oct 10

AMRDEC. Core Technical Competencies (CTC)

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

Department of Defense Cyber Workforce Initiatives. April 2017

UNCLASSIFIED FY 2017 OCO. FY 2017 Base

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 15 R-1 Line #232

Department of Defense INSTRUCTION

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 8 R-1 Line #156

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Development Planning Working Group Update

UNCLASSIFIED. FY 2011 Total Estimate

COMMON AVIATION COMMAND AND CONTROL SYSTEM

Test and Evaluation of Highly Complex Systems

Cybersecurity United States National Security Strategy President Barack Obama

UNCLASSIFIED. Cost To Complete Total Program Element Continuing Continuing : Physical Security Equipment

Vacancy Announcement

Using the Systems Engineering Method to Design A System Engineering Major at the United States Air Force Academy

Integrating the Systems Engineering "V" in a Systems of Systems

This is definitely another document that needs to have lots of HSI language in it!

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 6 R-1 Line #62

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

Advanced Explosive Ordnance Disposal Robotic System (AEODRS)

UNCLASSIFIED UNCLASSIFIED

Inspector General FOR OFFICIAL USE ONLY

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE F: Requirements Analysis and Maturation. FY 2011 Total Estimate. FY 2011 OCO Estimate

Headquarters U.S. Air Force

Department of Defense (DoD) Trusted Microelectronics

2016 Major Automated Information System Annual Report

Army IAMD Modular Open Systems Approach

UNCLASSIFIED R-1 ITEM NOMENCLATURE FY 2013 OCO

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

UNCLASSIFIED. UNCLASSIFIED Air Force Page 1 of 8 R-1 Line #90

Combat Hunter Curriculum Design

UNCLASSIFIED R-1 ITEM NOMENCLATURE

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

US Department of Defense Systems Engineering Policy and Guidance

UNCLASSIFIED. UNCLASSIFIED Office of Secretary Of Defense Page 1 of 7 R-1 Line #73

Joint Operational Effects Federation (JOEF) Program Overview

UNCLASSIFIED. UNCLASSIFIED Navy Page 1 of 7 R-1 Line #16

Mission Command. Lisa Heidelberg. Osie David. Chief, Mission Command Capabilities Division. Chief Engineer, Mission Command Capabilities Division

UNCLASSIFIED UNCLASSIFIED

Exhibit R-2, RDT&E Budget Item Justification

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED R-1 ITEM NOMENCLATURE

New DoD Approaches on the Cyber Survivability of Weapon Systems

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

FedBizOps Sources Sought

UNCLASSIFIED. UNCLASSIFIED Defense Information Systems Agency Page 1 of 12 R-1 Line #203

Small Diameter Bomb Increment I (SDB I) Precision Strike Association Annual Program Review

ARMY RDT&E BUDGET ITEM JUSTIFICATION (R-2 Exhibit)

Innovations in elearning Symposium. Integrating Engineering and the SEA Warrior Process. Greg Maxwell NAVSEA 03 7 JUNE 2005

UNCLASSIFIED. FY 2016 Base FY 2016 OCO. Quantity of RDT&E Articles Program MDAP/MAIS Code: 468

Report on Feasibility, Costs, and Potential Benefits of Scaling the Military Acuity Model

Software Sustainment: Continuous Engineering to

When and Where to Apply the Family of Architecture- Centric Methods

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

U.S. Air Force Electronic Systems Center

US Army/AMRDEC S&T Overview

UNCLASSIFIED. FY 2017 Base FY 2017 OCO

4 TRAINING DESIGN AND PLANNING

An Approach to Achieving Digital Interoperability for the DoD: A discussion of the Joint Staff J6 Coordinated Implementation Methodology

Air Force Science & Technology Strategy ~~~ AJ~_...c:..\G.~~ Norton A. Schwartz General, USAF Chief of Staff. Secretary of the Air Force

UNCLASSIFIED. FY 2016 Base FY 2016 OCO

UNCLASSIFIED. R-1 Program Element (Number/Name) PE F / NAVSTAR Global Positioning System (User Equipment) (SPACE) Prior Years FY 2013 FY 2014

DoD Cloud Computing Strategy Needs Implementation Plan and Detailed Waiver Process

UNCLASSIFIED R-1 ITEM NOMENCLATURE. FY 2014 FY 2014 OCO ## Total FY 2015 FY 2016 FY 2017 FY 2018

UNMANNED GROUND VEHICLES UPDATE

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

Reduction of procedure time by 17% with Philips Azurion

UNCLASSIFIED. FY 2017 Base FY 2017 OCO. Quantity of RDT&E Articles Program MDAP/MAIS Code: 493

2016 Major Automated Information System Annual Report

System Simulation, Software & Integration Directorate Realignment

UNCLASSIFIED R-1 ITEM NOMENCLATURE

UNCLASSIFIED. FY 2017 Base FY 2017 OCO

T&E in a Time of Risk and Change

Intelligence. Intelligence. Workload forecasting with Cerner Clairvia. Workload forecasting with Cerner Clairvia

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

Cryptologic & Cyber Systems Division Contract/Acquisition Forecast

Transcription:

Human Systems Integration (HSI) Human-System Metrics Applied to Optimize AF Warfighter Capability 13 March 2018 Integrity Service Excellence NDIA Human Systems Conference Ms. Sarah Orr Human Systems Integration Directorate 711 th Human Performance Wing

Overview 711 HPW/HP - AF HSI Analysts o Providing support across AF o Other/joint efforts HSI -related requirement activities o During early system concept development o Throughout the product lifecycle o Human-System Requirements Methodology Measures and Verification Metrics Example: application of HSI-related requirements in emerging domains: autonomy, human augmentation, and cyber 2

Human Systems Integration Directorate 711HPW/HP Mission Optimize warfighter capability through a human-centric approach to system development, acquisition, and sustainment 3

HSI Analysts Optimize total system performance the relative and combined performance human + software + hardware trade offs Optimize total life cycle costs projecting sustainment costs over 30-70 years (adds up)! Enable the users to effectively complete the mission HSI analysts work to ultimately reduce overall program risk 4

HSI the Means JCIDS: Capabilities Development Planning Tech Transition Requirements Development Requirements on contract Product / Process Development Testing/Training Fielded system Sustainment 5

Human-System Requirements System level HSI-related requirements: Are performance based. A performance-based requirement states how well a function must be performed. The performance is usually indicated by a measurable value. Source: USAF HSI in the SRD Guidebook, SURVIAC, 2012 Are accompanied by verification methodology Are often accompanied by SOW tasking for associated analyses, modeling and sim, and formative evaluations 6

Human-System Requirements Measures versus Metrics: Measure is used here for more concrete attributes Metric is higher-level; a standard of measurement Metrics can be used to benchmark and measure performance against. Metrics are measures collected over time for the purpose of seeing trends and forecasting program progress to plan. - DAG Chapter 3 7

Human-System Requirements Basic Requirement Statement: <System D> shall provide <F> feedback within <E> seconds. Measure: a clear and measureable pass / fail criterion Source: USAF HSI in the SRD Guidebook, SURVIAC, 2012 8

HSI Involvement Contractor Government Levels of Requirements Levels of HSI Requirements and Verification JCIDS CDD Level KPP-Survivability SRD Level Emergency Egress: Passengers and crew shall be able to exit in less than 90 sec. Verify by Demonstration SRD is AF equivalent of Guidebook focus System Performance Specification is at this level System Level (placed on contract) Functional Baseline (SRR) System Spec Level Emergency Egress: Passengers and crew shall be able to exit in less than 90 sec. Verify by Demonstration Allocated Baseline (PDR) Sub-System Spec Level The Emergency Door shall be able to be removed by <X number of> passengers or crew in less than 5 seconds. Verify by Demonstration In the event of power loss, the system shall provide a visual means to assist with emergency egress of passengers and crew for <Y amount of time>. Verify by Demonstration Product Baseline (CDR) Design Level Exit door sizes must be A x B Verify by Inspection Emergency floor lighting shall consist of product XXX-YYY. Verify by Inspection JCIDS = Joint Capabilities Integration and Development System; SRR = System Requirement Review; PDR = Preliminary Design Review; CDR = Critical Design Review. Source: USAF HSI in the SRD Guidebook, SURVIAC, 2012 Distribution A. Approved for public release: distribution unlimited. PA PA Case Number: 88ABW-2018-0509. 88AW-2018-0509. Date cleared: 05 Feb 2018 9

Requirements Development Methodology 10

Target Audience Description Operators Maintainers Support Team Other e.g., Trainers? e.g., Passengers, Other FoS Users, Bystanders 11

Mission Task Analysis Part of the overall systems engineering process a team effort Decompose mission capabilities into functions and tasks Mission Analysis Function Analysis Task Analysis Consider the human as part of the overall system Human capabilities and limitations factored into the design EARLY MIL-STD-46855A 12

Mission Task Analysis Mission Analysis Commercial off the shelf or transitioning technologies Function Analysis Allocate functions to hardware, software, and/or human Factors into Systems Engineering top down requirements decomposition process Task Analysis Empowering the human to excel in tasks that they do better than machines Designing hardware and software to assist humans when machines can do tasks better 13

Example Notional example: Security Forces need assistance patrolling military bases and apprehending threats. The following capabilities will be acquired to augment the existing forces: Security Forces Bot (SFB) - Autonomous, mobile patrolling of perimeters of military bases - Sense and detain airborne intruders (UAVs) - Sense and detain intruders on foot - Work as a team with other SFBs and also with [human] security forces 14

Example Total system performance the relative and combined performance of humans and systems Empowering the human to excel in tasks that they do better than machines Designing hardware and software to assist humans when machines can do tasks better 15

Example Military Satellites Net-centric Ops Air Traffic Control High Level Operational View = Security Forces Bot Military Base Threats Cyber UAV, other airborne Intruders on Foot Command & Control Ground-Based 16

Example Methodology: Begin with the Target Audience Description Operators Maintainers Support Personnel Other 17

Example Operational View - With Humans Military Satellites Net-centric Ops Air Traffic Control Other Military Base Security Forces Base Housing Threats Cyber UAV, other airborne Intruders on Foot Command & Control Ground-Based Friendly intruders children, adults, pets, wildlife 18

Example Consider the following areas of focus: Cyber Augmentation Autonomy 19

Example Command and Control (C2) Operator Cyber C2 Interface Human- System requirements might address: Alerting/notification of cyber threats o Software-related o Hardware-related o Overall system o Individual SFB cyber issues Decision-aiding o Responding to cyber threats o Understanding the impact/scope of cyber threats Ability to easily update system to respond to new emerging threats 20

Example Cyber Human- System requirements might address: Alerting/notification of cyber threats o Software-related o Hardware-related o Overall system C2 Interface o Individual SFB cyber issues Decision-aiding o Responding to cyber threats o Understanding the impact/scope Command and The C2 Interface of cyber threats Control shall (C2) provide recommended courses of action to avert <type A> threat to the C2 Operator within <D> seconds of detection. Ability to easily Verify update by demonstration. system to respond to new emerging threats 21

Example Augmentation Human- System requirements might address: SF Interface Security Forces (SF) Operator Teaming Communication Decision-aiding Override of automation Training Socialization/trust Safety Survivability Maintainability 22

Example Augmentation Human- System requirements might address: SF Interface Security Forces (SF) Operator Teaming Communication Decision-aiding Override of automation Training Socialization/trust Safety Survivability Maintainability The SF Interface shall allow the trained SF Operator to override autonomous operation of a single SFB to manual control within <C> seconds. Verify by demonstration. 23

Example Human-Systems requirements might address: System protected from unauthorized users Easy changes to software modules (by authorized users) command, control, and teaming rules Communication Decision-aiding Safety IFF/Survivability Friendly intruders children, adults, pets, wildlife Maintainability- diagnostics Sustainment- # of people required to support and sustain over the lifetime of the system Training- understanding evolution of changes to SFB Autonomy 24

Example Human-Systems requirements might address: System protected from unauthorized users Easy changes to software modules (by authorized Autonomy users) command, control, and teaming rules Communication Decision-aiding Safety IFF/Survivability Friendly intruders children, adults, pets, wildlife Maintainability- diagnostics Sustainment- # of people required to support and The sustain SFB software over the shall lifetime be capable of the system of field updates for <teaming rules> performed by trained Training- SF Maintainers understanding within evolution <D> minutes. of changes Verify to SFB by demonstration. 25

Postured to Optimize Warfighter Capability 711 HPW/HP - AF HSI Analysts - Postured to optimize warfighter capability within current and emerging technologies HSI Lab Anthropometrics Task Analysis Usability Exoskeleton augmentation Expanding talented HSI analyst workforce Cyber SMEs Engineers Acquisition professionals Doctors Physiologists 26

Contact Information HP workflow: 711HPW.HPWorkflow@us.af.mil 27