Architecture Modeling Approach for Net-Centric Enterprise Services

Transcription

1 Architecture Modeling Approach for Net-Centric Enterprise s (C4ISR/C2 Architecture Track, Paper #60) Yun-Tung Lau, Ph.D.*, Michelle TJ King (SAIC) Walter J. Okon and David Kye (DISA/NE) June, 2005

2 NCES Mission Threads Architecture Modeling Approach Sample: Time Sensitive Targeting Summary Outline 2

3 Purposes of Mission Threads Demonstrate that NCES Core Enterprise s can support Department of Defense missions. Validate NCES capabilities (requirements) for mission threads Develop Executable Architecture Models to validate NCES -Oriented Architecture. 3

4 Summary of Approach 1. Formulate activity models for a mission thread. 2. Map the activities to NCES and existing systems. 3. Develop logical deployment architecture with NCES included. 4. Develop logical data models. 5. Construct executable architecture models. 4

5 Time-Sensitive Targeting Activity Model Find Fix Activity Diagram (OV-5): TST Develop ISR Plan / TST Criteria Prioritize Not a Target Discard Collect ISR NonTST Target Locate Target Confirm / PID TST Determine if Target is TST Probable TST Update TST Manager Tool Correlate & Fuse Data The TST Manager is updated continuously as new information becomes available. Determine if Target is TST Track Unable to Confirm Maintain Track Continuity Update Situational Awareness Determine Time Available Confirmed Monitor Window of Vulnerability Validate Target Determine Available Attack Assets Formulate Weapon Target Pairing Target Select TST Attack Option Formulate Engagement Options Submit Combat Assessment Requirements Order TST Engagement Engage Attack TST Acquire Target Monitor Engagement Collect Assessment Data Correlate & Fuse Data Assess Determine Effects Objective Not Achieved Recommend Restrike Objective Achieved Remove From Target List 5

6 Operational Activity Descriptions ( Find Phase) Only First Three Activities Shown Here Activity Develop ISR Plan/TST Criteria Collect ISR Determine if Target is TST Description Based on JFC TST guidance and initial preparation of battlespace (IPB), develop an Intelligence, Surveillance and Reconnaissance (ISR) plan to deploy sensors to identify potential TSTs. Use all available sensor data to identify, locate, and prioritize emerging targets. Use further ISR to determine if emerging target is a TST. The final decision is made by the TST Cell Chief. 6

7 Operational Activity to System Function (SV-5) Core Enterprise s & Existing Systems Activities in the Six Phases Only Part of the Table is shown 7

8 Notional System Interface Description (SV-1) Notional To-Be Systems Interface (SV-1) For TST Browser / Thin Client CoI Portal COI Portal Workstation / Thick Client HTTP(S) Interface TST Portlet Search Portlet Clients TST CoI TST COI TST Manager TST Data Server Track Data Provider Data Providers Core Enterprise s CES Customer Collaboration Messaging Mediation Discovery RTL Data Provider Foundational Weather Data Provider IA / Security Enterprise Managment Storage Application User Assistance 8

9 Notional Event-Trace Description (SV-10c) Systems Event-Trace Description (SV-10c) For TST: Discovery Core Enterprise TST COI Component Commander via Thin Client COI Portal CES Discovery Messaging Track Data Provider TST COI TST Manager Clients 2 Signal New Info Update TST Data Update TST Data 1 5 Initiate Content Search Retrieve Notification Message 3 Match Info to Subscriber Profile Trigger Notification 4 Send Notification Via Request Content Discovery Return Content Results 6 Send Content Query Return Content Results Return Content Results Initiate Person Search Request Person Search 7 Search Persons Return Person Results Return Person Results 9

10 Executable Architecture Model for TST TST Guidance Only First Three Activities Shown Here Develop ISR Plan / TST Criteria Collect ISR TST Data Non-TST Target Determine if Target is TST Not a Target Probable TST 10

11 TST Activities Model Execution Timeline (example) TST.1 Develop ISR Plan / TST Criteria TST.2 Collect ISR data TST.3 Determine if Target is TST TST.5 Fix through Assess Phases TST.5.1 Locate Target TST.5.2 Correlate & Fuse Data TST.5.3 Confirm / PID TST TST.5.6 Dertermine Time Available TST.5.7 Track Phase Active activities TST Maintain Track Continuity on the TST TST Monitor Window of Vulnerability TST Update SItuational Awareness TST.5.8 Target Phase TST Validate Target TST Determine Available Attack Assests TST Formulate Weapon Target Pairing TST Formulate Engagement Options TST Submit Combat Assessment Requirements TST Select TST Attack Option TST.5.9 Engage Phase TST Order TST Engagement TST Monitor Engagement TST Acquire Target TST Attack TST TST Initiate Assessment TST.5.10 Assess Phase TST Collect Assessment Data TST Correlate & Fuse Data -Assess TST Determine Effects TST Remove From Target List TST.7 Update TST Manager Tool 11

12 Operational Mission Threads Warfighter Mission Areas: Time Sensitive Targeting (USJFCOM/SPAWAR/USA G-6) Focused Logistics/Deployment (USJFCOM/USTRANSCOM) Joint Close Air Support (USJFCOM) Global Strike (USAF/USSTRATCOM) Blue Force Tracking (USA) Business Mission Area: Personnel/Military Pay (HRM Domain) 12

13 Usage of Core Enterprise s Mission Threads TST Flog/D JCAS GS BFT MilPay/D Subtotal Messaging s Discovery s Collaboration s Mediation s User Assistant s Application s IA/ Security s Enterprise s Mgmt Storage s Shaded area for foundational services Average number of activities using a service 13

14 Architecture Modeling Methodology Conops Picture OV-1 Operational Scenario / Activity Diagrams OV-5 Activity-Function/ Mapping OV-6c SV-5 Logical / Deployment / Network Architecture SV-10c Sequence Diagrams SV-1 SV-2 OV-7 Logical Data Model Interface Definition Data Schema SV-6 SV-11 Functions/s SV-4 System Requirements Executable Architecture Model SV-7 Performance Model & Results 14

15 End of Presentation 15