Modeling System of Systems Acquisition Nil Kilicay Ergin Paulette - PowerPoint PPT Presentation

Modeling System of Systems Acquisition Nil Kilicay ‐ Ergin Paulette Acheson John Colombi Cihan Dagli Penn State University P St t U i it Missouri University of Mi i U i it f Ai F Air Force Institute of I tit t f Mi Missouri University of i U i it f PA, USA Science & Technology Technology Science & Technology MO, USA OH, USA MO, USA

Outline • Introduction • Background Background • Research Objectives • Research Methodology • Generic Model Generic Model • Next Steps • Questions 2

Introduction • SoS Architecting – Collaborate with individual systems to leverage y g individual system functionalities – Assumption: SoS participants exhibit nominal Assumption: SoS participants exhibit nominal behavior • Deviation from nominal behavior leads to • Deviation from nominal behavior leads to complications and disturbances in system behavior – Necessary to capture behavioral dimension of SoS – Necessary to capture behavioral dimension of SoS architecting to improve SoS acquisition 3

Background • Wave Model for SoS Acquisition 4

Research Objective • Model SoS acquisition based on the Wave Process Model • Impact of individual system behavior on SoS development • How do the systems, systems’ interactions, SoS initial characteristics, and other agents affect: – Capabilities Actually Developed vs Planned Capabilities – Capabilities Actually Developed vs. Planned Capabilities – Duration of the SoS development • Strategies for improving acquisition effectiveness g p g q – Decision framework – Test rules of engagement Test rules of engagement 5

Research Methodology • Agent ‐ based modeling – Environment • Rules of engagement • Opportunities Opportunities • Threats – Agents – Agents • Autonomous • Internal behavior • Internal behavior – Interactions 6

Generic Model Assumptions Assumptions • – Agents represent systems – The system agents embody themselves and the people (individual stakeholders) responsible for them stakeholders) responsible for them – Model applies to acknowledged SoS • Specific agent responsible for the SoS and for coordinating the individual system agents – Initial SoS mission is determined – Initial baseline SoS architecture is available • Functional and physical architecture • Key performance parameters 7

Overall Model SoS Acquisition Environment •National priorities •Funding Funding SoS Agent SoS Agent •Threat assessments Own Process Cooperation Control Management Agent Interaction Management System Agent 1 S t A t 1 System Agent System Agent 2 n Agent Own Process Interaction te act o C Control l Management 8

SoS Agent Behavior 1. Initiate SoS 2 Conduct SoS Analysis 2. Conduct SoS Analysis 3. Develop and Modify Architecture 4. Plan SoS update 5 Implement SoS architecture 5. Implement SoS architecture 6. Continue SoS analysis First Wave 9

SoS Agent Behavior Environment Environment Own Process Control O P C t l C Cooperation Management ti M t Initiate SoS Conduct SoS analysis Plan SoS update Develop and modify architecture Implement SoS architecture Agent Interaction Management 10

Individual System Behavior 1. Receive connectivity request from SoS agent 2 E 2. Evaluate request based on motivation l b d i i 3. Reply back to SoS agent p y g 11

Individual System Behavior Environment Agent Interaction Management Own Process Control Receive SoS request Evaluate SoS request Reply back to SoS agent 12

Next Steps: Case Study ISR Mission /RPA SoS Case Study ‐ ISR Mission /RPA SoS • Individual systems – Remotely Piloted Aircraft – Datalink (Link 16)/ SATCOM,… – Ground Control Station(s),… – Sensors (Wide Area Search – Gorgon Stare), … ( g ), – Targeting pod – Weapon(s) – Hellfire, JDAM, … p ( ) , , 13

Next Steps • Map generic model to Airborne ISR/RPA SoS development p • Identify and abstract Airborne ISR/RPA SoS – Measures of performance M f f – Individual system motivations – Events, rules of engagement 14

Acknowledgment This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Systems Engineering Research Center (SERC) under Contract H98230 ‐ 08 ‐ D ‐ 0171. SERC is a federally funded University Affiliated Research Center managed by Stevens Institute of Technology. y g y gy Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United States Department of Defense. 15

16 Questions Questions

SoS Environment External Factors/Variables: E  E f f ( ( National National priorities priorities , changes changes in in SoS SoS funding funding , threats threats ) ) 0 Changes in external environment at time T:  T External factors/variable at time T:   E E T 0 T SoS Environment 17

Initiate SoS Simulation time: t Wave interval: Epoch Wave rhythm time: T T= Epoch . t SoS desired capabilities: SoS desired capabilities:  SoS . C ( C , C ,..., C ) i 1 2 n Weighted value for SoS capability:  SoS . w ( w , w ,..., w ) i 1 2 n SoS desired performance parameters:   SoS SoS . P P ( ( P P , P P ,..., P P ) ) S S A SoS Agent t i 1 2 n Initial SoS Measures:     SoS . M [ a ] where a SoS . C , a SoS . P , a SoS . w  0 ij n 3 i 1 i i 2 i i 3 i 18

Conduct SoS Feasibility Analysis Identify set of individual systems to satisfy the target SoS measures: Identify set of individual systems to satisfy the target SoS measures:   SoS . M System . S ( S , S ..., S ) 0 i 1 2 n Allocate SoS capabilities to individual systems For i=1..n For j=1..n    SoS . Callocated ( C , S S ) where S S and S S i i i , j i j i j Deadline for each allocated SoS capability: i  SoS . d ( d , d ..., d ) 1 2 3 Funding for each allocated SoS capability: Funding for each allocated SoS capability: i  SoS . f ( f , f ..., f ) 1 2 3 Initial baseline SoS Architecture:   SoS . A [ a ] where a ( SoS . Callocated )  0 ij n n ij i SoS Agent SoS Request for individual systems:  SoS SoS . R R f f ( ( SoS SoS . A A , SoS SoS . f f , SoS SoS . d d ) ) i i 0 0 i i i i 19

Develop and Modify Architecture • Receive information from individual systems: (cooperation, availability, performance, capability) System . Informatio n i • Update SoS baseline architecture Architecture update factor: Beta  f ( System . Informatio n ) T i SoS architecture at time T:   SoS . A SoS . A Beta T 0 T SoS Agent 20

Plan SoS Update At time T: • Adjust/Update SoS Measures SoS Measures at time T: Capability update factor:  0  S S SoS . M M SoS S S . M M SoS S S . Alpha Al h      SoS . C ( C , C ,..., C ) T T i 1 2 n Performance update factor: • Adjust wave rhythm interval:          S S SoS . P ( ( P , P ,..., P ) ) Epoch  i 1 2 n f ( E , SoS . Gap ) T T   SoS . C f ( E , SoS . Gap ) i t T     SoS SoS . P P f f ( ( E E , SoS SoS . Gap Gap ) ) • Adj Adjust budget/schedule for b d / h d l f i t T SoS Measures update factor: allocated capabilities  SoS . Alpha [ a ]  where  SoS . d f f ( ( E , SoS . Gap p ) ) T ij n 2 i i T T T T      a SoS . C and a SoS . P SoS . f f ( E , SoS . Gap ) i 1 i i 2 i i T T SoS Agent At T=0  SoS SoS . Alpha Alpha 0 0 T T 21

Implement SoS Architecture • Evaluate current SoS architecture against initial baseline Architecture At ti At time T: T Gap Analysis:   SoS S S . G Gap f f ( ( S S SoS . M M SoS S S . M M ) )  T T T 1 SoS Agent 22

Evaluate SoS Request Individual System: System . S i System performance: System . p i S stem capabilit System capability: S System . c i Willingness to cooperate: System . willingnes s i Ability to cooperate: y p System . System . ability ability i i Receive request from SoS agent: SoS . R i Evaluate SoS request:  System . coop f ( System . willingnes s , System . ability , SoS . R ) i i i i i i i i  1 if cooperate   System . coop Individual System i  0 if not cooperate 23

Reply back to SoS Agent  If System . coop 1 i  System . Informatio n ( System . c , System . p , System . av ) i i i i i i i i  where system availability at time T= System . av P ( SoS . R ) i i else time to cooperate:   System . cooptime t where t SoS . d i i Individual System 24