Multifunction Phased Array Radar

1. Multifunction Phased Array Radar MPAR Concept of Operations (CONOPS)

2. MPAR CONOPS • Being developed in response to MPAR Working Group Action Item # 2007-1.1 “Using NGATS CONOPSas a model, develop an MPAR CONOPS rough draft”

3. MPAR CONOPS Working Group • Chair • Mark Weadon, OFCM • Members • Bob Saffle, NWS • Daniel Melendez, NWS • Garth Torok, FAA • Bob Blasewitz, FAA • May require participation by subject matter experts across disciplines (weather, Surveillance, defense)

4. CONOPS Influence What Drives Cost? Concept of Operations (CONOPS) Drives Operational Requirements (User Needs) Drives Performance Requirements (Characteristics) Scale Drives Radar System Architecture & Design MPAR Cost Drives

5. CONOPS - Decision Paths • Document content and organization considerations • Evaluated multiple CONOPS examples • NGATS CONOPS • NGATS Weather CONOPS • Surveillance and Broadcast Services CONOPS (i.e., ADS-B) • Future Terminal Area CONOPS (i.e., DTASS) • CONOPS and Operational Requirements for WSR-88D Dual Polarization • Business Continuity Plan En Route Services CONOPS • NAS CONOPS • Others • Explored different templates • FAA Operational Concept Template, Version 1.0 (May 1999) • FAA NAS Systems Engineering Manual • NWS Operations and Services Improvement Process (OSIP) Concept of Operations and Operational Requirements Template

6. FAA’s System Engineering Manual (SEM) - CONOPS Hierarchy Where does the MPAR CONOPS fall? Answer: Tailored hybrid of CONOPS and CONUSE

7. FAA’s System Engineering Manual (SEM) - CONOPS Hierarchy • CONOPS (Service-Level) • Provides conceptual insight into a particular service of the integrated operational environment (e.g., nav, surv, comm) • Identifies current shortfalls and future needs • Identifies capabilities required for a specific service (without identifying specific technologies) • May use Operational Scenarios to illustrate desired operational concept • Provides a user perspective • Not system specific • CONUSE • Extension of CONOPS with emphasis on specific system and its operating environment • Describes functional characteristics (i.e., stakeholder’s needs) of a proposed system from a user perspective • Tells a story using visual forms (diagrams, illustrations, graphs) and storyboards • Describes the user’s general system goals, mission, function, and components • MPAR CONOPS • Hybrid of a CONOPS and CONUSE

8. Concept Document Outline Describes current problem space (operational situation and shortfall) 1. Introduction 1.1 Service or System Identification 1.2 Document Overview 1.3 Service or System Overview 1.4 References 2. Operational Need 2.1 Current Service or System 2.2 Current Support Environment 2.3 Operational Problems 2.4 Objectives and Scope 2.5 Capability Shortfalls 2.6 Existing Operations Requiring Change 2.7 Constraints 2.8 User 3. Service or System Justification 3.1 Potential Benefit of New or Modified Service 3.2 Description of Desired Change 3.3 Change Priorities 3.4 Assumptions and Constraints 4. Proposed Service or System 4.1 Objectives and Scope 4.2 Proposed Service or System Description 4.3 Proposed Support Environment 4.4 Modes of Operation 4.5 User 4.6 Operational Policies and Constraints 5. Operational Scenarios 6. Impacts 6.1 Impact on Current Operations 6.2 Organizational changes Required Appendix A – Glossary and Acronyms Appendix B – OSED (Oper. Serv. and Envir. Descr.) Provides description of the new system and the benefit it will provide Provides description of the proposed system and its characteristics Operational Scenarios to help better describe concept Provides description of impact to operations and the organization

9. Operational Scenarios

10. DST DST DST NUMERICAL WEATHER PREDICTION Flow of Radar Data/Environmental Data Records (EDRs) Control of Radar Scanning DATA ASSIMILATION Feedback Loop 7 5 7 1 6 RADAR CONTROL, LOGIC & PROCESSING 1A 4-FACE MPAR ANTENNA RADAR DISPLAY 4 2 3 8 SWIM GIG ENTERPRISE SVC AUTOMATION SYSTEM (ADS-B Track correlation) 8 8 1. SIGNAL TO ANTENNA ADAPTING SCAN PATTERN 1A. DATA FROM ANTENNA IS PROCESSED INTO EDRs 2. AIRCRAFT POSITION INFO TO ADS-B FOR CORRELATION WITH COOPERATIVE REPORTED TRACKS 3. AIRCRAFT MISMATCHES FLAGGED TO MPAR AS “TARGETS OF INTEREST” 4. PROCESSED RADAR DATA (AC AND WEATHER) SENT TO USERS VIA NETWORK SYSTEMS 5. RADAR DATA TO NWP FOR INGESTION VIA DATA ASSIMILATION 6. DATA TO DISPLAY FOR HUMAN INTERPRETATION 7. RESULTS FROM NWP FED BACK TO CONTROLLERS FOR MANUAL/AUTOMATIC ADJUSTMENT OF SCAN STRATEGY 8. PROCESSED DATA FED THROUGH ENTRPRISE SERVICES TO DECISION SUPPORT TOOLS (HUMAN OR MACHINE)

11. Working Group Tasks • Define Document scope, organization, and outline • Develop Operational Scenarios and other visual forms to facilitate understanding of MPAR operation • Identify agency mission shortfalls that should be addressed by this solution • Expect MPAR CONOPS to be a “living” document • Working Group Meeting tentatively scheduled for July • Baseline organization of document • Finalize initial operational scenarios • Begin assigning sections to individuals/agencies

12. Issues/Decision Points • How should the document be bound? • What capability is the solution required to deliver? • Need to identify additional agency SMEs (e.g., DHS, DOD, etc.) to provide input

13. Milestones/Dates