1 / 12

Mr. Gerry Doyle Chief, Systems Engineering Center August 3, 2006 Unclassified

A Thought Piece on EW SE Achieving NetCentric Operations. Mr. Gerry Doyle Chief, Systems Engineering Center August 3, 2006 Unclassified. Assessment of EW SE Status What’s Not Working?.

tab
Download Presentation

Mr. Gerry Doyle Chief, Systems Engineering Center August 3, 2006 Unclassified

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Thought Piece on EW SE Achieving NetCentric Operations Mr. Gerry Doyle Chief, Systems Engineering Center August 3, 2006 Unclassified

  2. Assessment of EW SE StatusWhat’s Not Working? • Not providing the value-added needed by the Components’ GIG programs and initiatives via the current approach • Limited involvement of key Component representatives, and on-going initiatives not being sufficiently leveraged • EW issues being addressed are not coupled to critical forthcoming program decisions • Depth of analysis being performed is not credible • There is no integrating architecture for characterizing the GIG technical baseline • Technical baseline doesn’t relate to incremental GIG capabilities • Lack of relationship between the technical baseline and operational capabilities • No means of determining the minimum set of requirements needed to define the GIG • Some critical EW SE activities and processes have not yet begun • Current experimentation and M&S activities are not integrated or mature • Key products needed to drive systems analysis have not been initiated (e.g., Decision Opportunity Roadmap) • “Crisis-driven” approach is not sustainable, burns out staff, and does not result in best products • Current implementation lacks application of standard systems engineering technical and risk management processes

  3. What Do We Need To Do? Way Ahead • Orchestrate and leverage on-going efforts of the Service/Agency/COCOM community • Come to community consensus on issues and their priority to maximize impact • Develop key SE products to guide decisionmaking • Assign responsibility for action required to resolve issues • Establish an executable schedule • Define deliverables needed to drive program decisions • Standardize Systems Engineering Toolset • Consider a Joint Enterprise Wide Systems Engineering Organization

  4. Re-structured Approach to Maximize Community Involvement NII Governance Policies Vision Strategies Funding SSEB DISA EW SE MGMT Capability Portfolio Managers Technical Baseline (NCIDs) GIG System Architecture Experimentation Plans Decision Opportunity Roadmap Mission Area Portfolio Managers Segment WGs Segment WGs GIG EW SE Integrated Project Team (IPT) DISA EWSE Team DISA EWSE Team DISA EWSE Team DISA EWSE Team DISA EWSE Team DISA EWSE Team DISA EWSE Team DISA EWSE Team Army SE SE Navy SE MC AF SE SE J/S & COCOMs SE DISA NSA SE SE Intel E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E E Cross-Initiatives COI(s) Service Systems Engineers Service Program Engineers E SE

  5. New Issues and Analysis Prioritization Approach MS C Inc 2 Field Upgrade Adopt Solution Field Upgrade Fielding Decision MS B Inc 3 MS B Inc 2 MS C Inc 3 CDR RFP Issued CDD Decision Opportunity Roadmap Technical Baseline Capability Gap Analysis (Notional) EWSE View Mission Area Portfolio View Capability Portfolio View Program View GIG Inc #3 Capabilities 06 07 08 09 10 11 GIG Inc #2 Capabilities Prog A NCIDs Tech Baseline Prog B GIG Inc #1 Capabilities Gap Gap Prog C BA JNO FL JCC Prog n Capability Portfolios Prioritized Issues

  6. Key SE Products/Activities • GIG EW SE IPT- Involve key stakeholders • Decision Opportunity Roadmap - Develop consolidated milestone schedule • GIG Systems Engineering Plan - Define and document key EW SE processes • GIG System Architecture - Develop integrated system architecture • Info-sharing Environment - Establish integrated environment for collaboration and data-sharing • NCIDs - Describe time-phased GIG technical baseline • Enterprise Document Framework- Maintain configuration control and content management of GIG documentation • Experimentation Plan - Create plan to verify and validate GIG interoperability and performance

  7. Activity/Product Details (1 of 2) New New • GIG EW SE IPT • Purpose: Involve key stakeholders in defining EW SE processes and critical GIG EW issues and sharing lessons learned and best practices • Approach: Host periodic meetings involving Army, Air Force, Navy, Marine Corps, NSA, DISA, NII, AT&L, Joint Staff, Intel, portfolio managers • Benefits: Facilitates community buy-in; enables more robust and operationally-relevant products • Decision Opportunity Roadmap • Purpose: Develop consolidated milestone schedule to include dependencies between major GIG programs • Approach: Leverage existing products (e.g., TCA Effectivities, GIG convergence efforts, GIAP roadmap, JBMC2 roadmap.) • Benefits: Drives task scheduling and issue prioritization decisions New New • GIG Systems Engineering Plan • Purpose: Define and document key EW SE processes, including configuration management, risk management, issues prioritization, capability-level trade studies, requirements management, decisionmaking, baseline control, technical reviews, program compliance assessments • Approach: Tailor AT&L’s system of systems SE Plan outline for GIG net-centric paradigm • Benefits: Reduces risks by enforcing structured decisionmaking, requirements management, configuration control, and review processes • GIG System Architecture • Purpose: Develop integrated system architectures to describe GIG capability increments • Approach: Leverage existing products and methodologies (e.g., GIG architecture, NCOW-RM, GIG IA architecture, GIG programs’ architecture products, Convergence Master Plan, NCOE) • Benefits: Provides construct for documenting GIG increments and capabilities and forms the basis for performing GIG EW trade studies

  8. Activity/Product Details (2 of 2) Enhance Re-scope • Info-sharing Environment • Purpose: Establish integrated, protected environment for collaboration and data-sharing among the EW SE community • Approach: Leverage existing products (e.g., DISR, GES Portal, D-Net), ensuring compliance with DoD Data Strategy and net-centricity tenets • Benefits: Empowers community by making data available, searchable, and re-usable. Allows collaboration to support decisionmaking • NCIDs • Purpose: Describe time-phased GIG technical baseline and associated requirements • Approach: Analyze issues based on event-driven timelines based on the needs of the Decision Opportunity Roadmap and GIG capability gap analysis; re-scope WG roles and responsibilities • Benefits: Provides implementation requirements for GIG programs based on EW trades Ongoing New • Enterprise Document Framework • Purpose: Maintain configuration control and content management of GIG documentation in accordance with the framework • Approach: Establish flexible requirements database and work with document owners to ensure consistency of GIG documents • Benefits: Ensures requirements traceability and compliance • Experimentation Plan • Purpose: Create plan and schedule for verifying and validating GIG interoperability and performance • Approach: Leverage existing tools and capabilities (e.g., GIG-EF, FDCE (“sandbox”), NETWARS) • Benefits: Describes capabilities needed to adequately demonstrate interoperability, performance, and operational utility

  9. Notional FY07 EW SE Implementation Schedule 1QFY07 2QFY07 3QFY07 4QFY07 GIG EW SE IPT Meeting GIG EW SE Strategy and Governance GIG EW DO Roadmap v1.0 GIG EW DO Roadmap v1.1 GIG EW SEP v0.5 GIG EW SEP v1.0 GIG EW SEP v0.1 EDF Phase 3 EDF Phase 4 GIG Increment Description v1.1 GIG Increment Description v1 Capabilities Gap Analysis GIG Capability Definition and Evolution Capabilities Gap Analysis Prioritize analyses Prioritize analyses GIG Analysis NCID v3.0 Release NCID v3.1 EDFWG Release Develop NCID v4.0 Develop and Maintain EW M&S Document Management and Control Enhanced Info-sharing environment Enhanced Info-sharing environment Enhanced CM Plan Execute CM Program Compliance Management CONOPs for Component Liaison Teams Annual Reports from Component Liaison Teams Experimentation and GIG Characterization Plan to leverage existing tools/capabilities EW Experimentation and M&S Plan GIG EW System Architecture Sys Architecture Products v1.0 Sys Architecture Products v0.1 Plan to leverage existing products/methods Define toolset/use cases Establish GIG Sys Arch CCB Operational Support Establish DISA EW SE Liaison Teams Deploy DISA EW SE Liaison Teams

  10. Notional Joint EW Systems Engineering Organization Joint EW SE Office NII EW SE On-Site Liaison Other DISA Liaisons • Standards • TE • JITC • M&S Planning and Process Management GIG Analysis • Integrated Master Schedule • Decision Opportunity Roadmap • GIG SE Plan • Risk Management Plan • Information-sharing environment Documentation Analysis Component Liaison Teams • Army • Navy • Air Force • Marine • Jt Staff/COCOMs • DISA • NSA • Intel • GIG systems architecture • Engineering analysis • R&D • M&S • Prototyping • Program compliance • NCIDs • EDF • Experimentation Plan

  11. Summary • This approach would link engineering efforts to programs to leverage ongoing work • Orchestrate and leverage on-going efforts • Find community consensus on issues • Develop key SE products • Assign responsibility for action • Establish an executable schedule • Define deliverables needed • Standardize SE Toolset • Joint Enterprise Wide Systems Engineering Organization

  12. www.disa.mil

More Related