Consideration of the CONOPS as Part of the System Development Tradespace



Similar documents
System Concept of Operations: Standards, Practices and Reality

3SL. Requirements Definition and Management Using Cradle

NAVAL SEA SYSTEMS COMMAND STRATEGIC BUSINESS PLAN

THE STAR MODEL JAY R. GALBRAITH

U.S. Defense Priorities OSD PA&E

PROJECT RISK MANAGEMENT

THE OPEN UNIVERSITY OF TANZANIA FACULTY OF SCIENCE TECHNOLOGY AND ENVIRONMENTAL STUDIES BACHELOR OF SIENCE IN DATA MANAGEMENT

Name Chapter 1: Introduction to Project Management Description Instructions

Socio technical Systems. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 2 Slide 1

Requirements Management John Hrastar

Project Management Plan Template

TYPOLOGY 13 MONEY LAUNDERING THROUGH CASINOS APPROVED BY THE DECISION OF THE GOVERNOR OF THE CENTRAL BANK OF ARMENIA NO 1/41A FROM JANUARY 24, 2014

Statement Of Objectives (SOO) Information Guide

GUIDANCE FOR ASSESSING THE LIKELIHOOD THAT A SYSTEM WILL DEMONSTRATE ITS RELIABILITY REQUIREMENT DURING INITIAL OPERATIONAL TEST.

CARVER+Shock Vulnerability Assessment Tool

Management Efficiency Assessment on Aviation Activities in the USDA Forest Service. Executive Summary

Managing IT Projects. Chapter 2 The PMI Framework

Practiced Questions. Chapter 20

U.S. Dept. of Defense Systems Engineering & Implications for SE Implementation in Other Domains

Project Communications Planning

Develop Project Charter. Develop Project Management Plan

WWII by the Numbers Charting and Graphing D-Day and WWII Data

Project Management for the Professional Professional Part 4 - Stakeholder Analysis. Michael Bevis, JD CPPO, CPSM, PMP

Organizational Requirements Engineering

Certification in Humanitarian Supply Chain Management (CHSCM) Competence Model. Final Version 2007

Correlation between competency profile and course learning objectives for Full-time MBA

Automated Contact Resistance Tester CR-2601

Annual Assessment Report, College of Business Administration Sharyn Gardner, Assessment Director

THE STAR MODEL JAY R. GALBRAITH

Operating Instructions for Plastic Flow Meter. Model: KSK

Recommended Best Practices for the Design of Secure Multi-Domain KVM and Video Routing Systems

Recognizing and Mitigating Risk in Acquisition Programs

Investment Analysis using the Portfolio Analysis Machine (PALMA 1 ) Tool by Richard A. Moynihan 21 July 2005

CHAIRMAN OF THE JOINT CHIEFS OF STAFF INSTRUCTION

MDHearingAidAIR Diagram

The problem with waiting time

Zoonotic Disease Symposium US Army Veterinary Service

Risk Management Framework

HQMC 20 Aug 04 E R R A T U M. to MCO B OPERATIONAL RISK MANAGEMENT (ORM)

PROJECT MANAGEMENT PLAN CHECKLIST

QUAD CHARTS IN SOFTWARE PROJECT MANAGEMENT *

Project Time Management

Office of Inspector General Department of Defense FY 2012 FY 2017 Strategic Plan

Organization for Security and Co-operation in Europe

Leading Indicators for Project Management

SERC Security. By Jennifer Bayuk

Socio-Technical Systems

Operationally Critical Threat, Asset, and Vulnerability Evaluation SM (OCTAVE SM ) Framework, Version 1.0

IT Baseline Management Policy. Table of Contents

Turning Portfolio Management into Decisions

Assessment of natural hazards, man made hazards, technical and societal related risks and associated impact.

Terms concerned with internal quality control procedures

Project Management Body of Knowledge (PMBOK) (An Overview of the Knowledge Areas)

Services we provide. Tel:

Thermal Flow Sensor Die

Engineering a EIA - 632

Implementing Program Protection and Cybersecurity

EXERCISE 1: HR System Implementation

BI Requirements Checklist

4. Project management triangle The Project Management Triangle (called also Triple Constraint or the Iron Triangle) is a model of the constraints of

Frequently Asked Questions in Project Management

BUSINESS OCR LEVEL 3 CAMBRIDGE TECHNICAL. Cambridge TECHNICALS BUSINESS PROJECT MANAGEMENT CERTIFICATE/DIPLOMA IN K/502/5459 LEVEL 3 UNIT 18

Integration Mgmt / Initiating Process Group 4.1 Develop Project Charter

Lecture 7: the Feasibility Study. Content of a feasibility study

JOURNAL OF OBJECT TECHNOLOGY

KEYWORDS: Risk Assessment, Competitive Intelligence, National Security, Web Security, Defense, Information Security

Time Management. Herb Pollard III

Concept of Operations for the Capability Maturity Model Integration (CMMI SM )

DATA PD SV13.., SV14.. Levelling Valves. Product. Function. Technical Features. Range Overview

Integrating Continuity of Operations (COOP) into the Enterprise Architecture

PROJECT AUDIT METHODOLOGY

Open Access Research on Application of Neural Network in Computer Network Security Evaluation. Shujuan Jin *

Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs

System Requirements Specification (SRS) (Subsystem and Version #)

ICH guideline Q10 on pharmaceutical quality system

From Chaos to Clarity: Embedding Security into the SDLC

Design Verification The Case for Verification, Not Validation

ZIMBABWE SCHOOL EXAMINATIONS COUNCIL. COMPUTER STUDIES 7014/01 PAPER 1 Multiple Choice SPECIMEN PAPER

Management Efficiency Assessment of the Interagency Wildland Fire Dispatch and Related Services. Executive Summary

What is Linear Programming?

Architecture Evaluation Methods: Introduction to ATAM

PROJECT SCOPE MANAGEMENT

Introduction to the ITS Project Management Methodology

DEFENCE INSTRUCTIONS (GENERAL)

PeopleSoft Program Management

FOUNDATION: Material Solution Analysis Is More Than Selecting an Alternative

Quality Risk Management The Pharmaceutical Experience Ann O Mahony Quality Assurance Specialist Pfizer Biotech Grange Castle

Qi3 Insight: Diversification by Defence Companies into Civil Markets

System Development and Life-Cycle Management (SDLCM) Methodology. Approval CISSCO Program Director

Performance Indicators for Disaster Recovery

MBA Data Analysis Pad John Beasley

Transcription:

Applied Systems Thinking (ASysT) Institute 2900 S. Quincy St. Suite 800 Arlington VA 22206 Office. 703.416.2000 Fax. 703.416. 3072 ASysT is a research institute of Analytic Services Inc. and ANSER Consideration of the CONOPS as Part of the System Development Tradespace Jaime Frittman & Robert Edson Jaime.Frittman@anser.org Robert.Edson@anser.org ABSTRACT Tradespace is the region within which modifications to achieve the maximum balance between cost, performance, and schedule reside. This space, however, is not always sufficiently broad to achieve the required, or optimal, system balance. When tradeoffs must be found and cost, schedule and performance can not be changed, what other system characteristics can be used as a tradeoff variable? This research explores use of the system s concept of operations () as a new dimension of the tradespace. Specifically explored is why, when, and how the can be used as a tradespace variable. In addition, several DoD systems are presented as case studies of CONOP use with trade assessments. Our research indicated that to remain within the tradespace, the must continue to fulfill its intended role in the developmental process, and to function under specific constraints. Three distinct, but related elements serve as the upper limit of the tradespace. These elements include: mission, system capability, and operational scenarios.

Tradespace Traditional Tradespace Max Max Traditionally, tradespace includes cost, schedule, & performance. These elements can be illustrated as slide bars. Changes can be made along any of the slide bars as long as the change is within the parameters of: desired and maximum cost, desired and maximum schedule, and minimum and desired performance. Min Cost Schd Perf Tradespace The Tradespace Max Max? When traditional elements are at their thresholds, can tradespace expand to include? If so, what would the parameters of the CONOPS tradespace look like? Min? Cost Schd Perf

Assessing Parameters To assess tradespace a modified context diagram tracking direct and indirect relationships was constructed Needs Missions Military Concepts Stakeholders Cost This task provided clues to which relationships were most significant Tasks System Requirements / Performance CBAs Schedule Capability System Operational Scenarios Relationship Thread Threads (as shown to the right) are traced as follows: Needs Missions Military Concepts Stakeholders Military Concepts describe missions Cost Missions are achieved using systems Systems are described in support achievement of Military Concepts Tasks CBAs System Requirements / Performance Schedule Capability System Operational Scenarios

System Recognition The context diagram was translated into a block diagram. Viewed as block diagram it became evident that we were looking at a system, with inputs, outputs, transformations, and constraints. Inputs, Outputs Transformations For the system to function properly, each input must have an output and visa-versa. At each step consistency must be maintained between and among inputs and outputs. Strategy Consistency required between inputs and outputs All functions must support and be within the scope of the mission Threat Higher order concept Mission Consistency required among outputs (Capability must match scenario and vice versa) System & Operator tasks System Capability Environmental Conditions input transformation output In other words, as we make the change to the environment we must also make changes to the operational scenarios. Operational Scenarios System Design

Because of the nature of, the tradespace parameters are far more subjective than traditional tradespace elements. It is important to note that tradeoffs in the can potentially change the ranges of the other three tradespace elements. In an effort to quantify the subjective parameters we identified 3 system characteristics that must remain in balance in order for the to function effectively; namely: inputs, outputs, and constraints. These 3 characteristics serve as the parameters of the tradespace. Tradespace Max Max Min Cost Schd Perf?? Consistent Consistent Supports Operational Scenarios Must be consistent with mission set Must be consistent with system capability description Mission Must describe a system that supports achievement of a valid mission Inconsistent Scenarios Inconsistent Capability No-Support Mission System Capability Description Must describe capabilities that support the mission Must describe capabilities consistent with operational scenarios From a slide bar stand point, the slide bar consists of three elements. The parameters of these are best described in a go/no-go manner.

Go/ No-go based Decision Flow Chart A simple flow chart can enable the decision process by identifying trades outside or within the tradespace. Tradeoffs where the impact is unknown are considered outside the tradespace. Start Possible tradeoff identified es Does system support valid mission? es Are operational scenarios consistent with mission & described capability? es Is described capability consistent with scenarios and mission? es Change falls within tradespace End No/Unk No Change exceeds tradespace or is not suggested No/Unk End

A decision matrix can be used to evaluate if a proposed change is within or outside a system s tradespace. In this situation a military Service is short on money and time and cannot reduce system performance. Changes to the are considered as a means of achieving the cost, schedule, and performance goals. A notional decision matrix documenting alternatives is provided. Each alternative is compared for its consistency with identified missions, system capabilities, and operational scenarios. In this example, alternatives 1 and 3 fall within the tradespace. Alternate 3: 4-12 hour shifts (12 on/12 off for 24 hour total)in contaminated environment. Get contaminated, get new ensemble from asset pool. Service member retains & wears 1 ensemble and pools the other ensemble describe a system that supports a valid mission? describe operational scenarios consistent with the identified mission set & described capabilities? describe system capabilities appropriate for the identified operational scenarios? Alternate 1: 4-12 hour shifts (12 on/12 off for 24 hour total) in contaminated environment. Contamination on installation = get new ensemble from personal bag up to 4 times for total 96 hours. Service member retains all ensembles Support Functional Concept for Personnel Protection Alternative 1 Alternative 2 Alternative 3 No Change (4 Per): All personnel change suit from personal stock upon attack Change: (Issue 2 sets per person). All personnel change suit from personal stock upon attack Change: (Issue 2 suits per person) Only change when contaminated & Pool assets Support Combat Operations Scenario perform 96 hours continuous operations N 4-24 shifts (12 hours on/12 hours off) Change suit every 24 hours N Operate in contaminated environment providing 24 hours of liquid protection providing 24 hours Alternate 2: 4-12 hour shifts (12 on/12 vapor protection off for 24 hour total) in contaminated System allows for operations (comfort, fit) environment. Contamination on installation = get new ensemble from personal bag up to 2 times for total 96 hours. Service member retains all ensembles

Conclusions The study provides a framework from which to understand how to incorporate into a systems developmental tradespace. The Framework provides sound options; not solutions Tradespace options must be compared to assess best option Additional Cases OTH-B Radar describe a system that supports a valid mission? describe operational scenarios consistent with the identified mission set & described capabilities? describe system capabilities appropriate for the identified operational scenarios? References Bahill, A. & Henderson, S. (2004). Requirements, Development, Verification, and Validation Exhibited in Famous Failures. Systems Engineering 8(1). Mahal, D. (1995). The Space Shuttle Challenger Accident. Available from: http://www.mahal.org/ articles/space/1995/12/the-spaceshuttle-challenger-accident/page/1 Alternative 1 Does Alternative the 2 No Change Change describe Mission a system that supports a valid mission? Defeat Soviet Threat N describe operational scenarios consistent with Detect hostile aircraft the identified mission set approaching U.S. & described capabilities? airspace Relay detection information detecting aircraft outside US airspace signaling an aircraft is detected transferring information describe system capabilities appropriate for the identified operational scenarios? USAF. (2008). Memorandum. Basis of Issue (BOI) Study for United States Air Force CBRN Individual Protective Equipment. Alternative 1 Alternative 2 No Change Change Mission Win the war on drugs N Detect hostile aircraft approaching U.S. airspace Relay detection information detecting aircraft outside US airspace signaling an aircraft is detected transferring information