1 / 12

Integration and Interoperability Test and Evaluation 05 May 2011

Integration and Interoperability Test and Evaluation 05 May 2011. Mike Spencer Deputy Chief Engineer, Space and Naval Warfare System Command. Presented to: The San Diego Chapter of ITEA Courtyard by Marriott 8651 Spectrum Center Boulevard San Diego, CA 92123.

noah
Download Presentation

Integration and Interoperability Test and Evaluation 05 May 2011

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. Integration and InteroperabilityTest and Evaluation05 May 2011 Mike Spencer Deputy Chief Engineer, Space and Naval Warfare System Command Presented to: The San Diego Chapter of ITEA Courtyard by Marriott 8651 Spectrum Center Boulevard San Diego, CA 92123 Statement A: Approved for public release, distribution is unlimited (5 MAY 2011)

  2. Establishment of the SPAWAR I & I Director • Established the office and appointment of the director of I & I at SPAWAR • Serve as a point of entry and coordinator. • Work along side other Navy warfare centers • Engage with CNO’s Office, ASN RD&A, PEO, and OPTEVFOR • Define Navy policy and processes creating integrated warfighting capabilities

  3. CNO I & I Summit • Get agreement that we need to sharpen our focus on creating Integrated Warfighting Capabilities, vice just delivering products to our Fleet • Recognize that a formal governance approach is needed for creating Integrated Warfighting Capabilities. • Increase awareness that we already have much of the capabilities to create Integrated Warfighting Capabilities. These capabilities (people and facilities) reside largely in our Warfare Centers. That while industry plays a vital role, what we are addressing in the area of I&I is inherently governmental. • Get agreement that we need to adjust some of our acquisition processes to emphasize interoperability requirements

  4. Integration and Interoperability • From the 09 December 2010 Integration and Interoperability (I&I) Summit, six major action items were documented. • Action 1: Identify Effect chains of interest- Through close coordination with USFF/CPF/5th Fleet, twelve effect chains have been identified crossing critical Air, Surface and Undersea warfare areas to include C2. • Action 2: Establish SYSCOM Force Level I&I Leads- Mr. Scott O’Neil (NAVAIR), Mr. Carl Siel (NAVSEA/NSWC Dahlgren) and Mr. Paul Lefebvre (NAVSEA/NUWC) and Mr. Mike Spencer (SPAWAR) have been identified by their respective commands • Action 3: COTF baseline critical warfighting capabilities identified by USFF/CPF- COTF has established a Warfare Capability Baseline Team (WCB) from a diverse list of critical stakeholders to include; SYSCOM Mission Engineers (ME), Principal Investigators (PI), COTF Mission Integrators and Warfare Centers of Excellence (WCOE) representatives. • Action 4: Establishment of Capability Management Teams (CMTs) and process for capability management- CMTs are envisioned to be the mechanism for bridging the WCOE operational expertise of warfighting capability with the SYSCOM/Warfare Center technical expertise of warfighting capability. • Action 5: I&I Governance construct- This action is in work with discussions on-going with OPNAV N8 and ASNRDA. • Action 6: Convene a CNO Executive Board chaired by VCNO (CEB-V) to provide an update on I&I progress and summit actions- This CEB-V is scheduled for 20 April 2011

  5. Surface Ship Naval Warfare Systems Certification Task Force Lead by RDML Tom Wears Commander Naval Undersea Warfare Center Deputy Commander, Undersea Technology (SEA 073)

  6. Tasking & Proposed Approach • Tasking: “Using DDG-104 as a Case Study, review procedures used to plan, resource, develop, integrate, and certify warfare systems on US Navy Ships.” • Develop Findings and Provide Recommendations Regarding: • Sufficiency of existing requirements, standards and certification processes used in Warfare System certifications • Existence and applicability of metrics to support decisions supporting and/or leading to certification decisions • Use and applicability of Objective Quality Evidence in supporting certification decisions • Clear accountability for all decisions supporting and/or leading to certification decisions • Technical authority structure supporting Warfare Systems certification process

  7. Future focus Mission TA Need cross SYSCOM TA at this level Seam Issues Expand TA roles here Today’s TA focus Naval Warfare Systems Certification Task Force Levels of TA Mission Warfare Systems Systems Elements Force Platform MCSys CombatSystems C4I/IT Aviation

  8. The “main issue” is the immaturity of or breakdown of Technical Authority across system boundaries. Five Pillars Platform Certification Combat Systems C5IMP Planning and Resourcing Interoperability Technical Authority. Conclusions (Themes) Surface Warfare fleet won’t accept substandard products anymore Inconsistent Certification Std’s. Multiple: Resource Sponsors PEO’s SYSCOMS Excessive Risk Transferred to Fleet TA for the most part ineffective Fleet not involved until system fielding Naval Warfare Systems Certification Task Force (some of the key details) • Warfare System Certification model must be matured. • Interoperability improvements require capabilities based approach • A culture change is required

  9. Test and Evaluation

  10. Major Programs Supported • Other Programs: • NNWC Operational Determination Accreditation Authority (ODAA) • Navy Certification Authority (CA) • CYBERFOR – Fleet Readiness Certification Board (FRCB) • Submission Maturity Assessment/Accreditation Recommendation • FAA/NTIA – • Link 16 EMC/SPECTRUM CA Team SPAWAR • Systems Engineering Technical Review (SETR) • TE&C TAE • Navy ERP • PEO-C4I/PEO-EIS Support • CANES - OA preps 160 • NMT IOTE preps 170 • GCCSM IOTE 150 • DCGS-N Inc 2 OA preps 120 • CSRR FOTE 770 • Centrix M IOTE 160 • CBSP IOTE 170

  11. C4I Certification Process Baseline Definition PMW Development Testing and Documentation Completed. PMW submits Package to PEO boards C4I Platform Baseline ECR Stage I / Risk Assessment C4I Platform Baseline ECR Stage II / Risk Assessment C4I Platform Baseline ECR Stage III / Risk Assessment Test/Cert Artifacts: IA Cert OTA Cert JITC Link Qual Tests SOVT Etc PGB E2C Event Decision Point Med/Low Risk Interfaces High Risk Interfaces Capability Assessment Distributed Lab Environment Assessment By Demonstration (E2C SoS T&E) Assessment By Analysis (Using TE&C Artifacts) Assessment Data to Engineering Risk Assessment Certification Decision Re-Work No NWSCP WSCA/D (A-8/E-1) Cert Criteria Met? 5.0 TD Signature For Authorization/ Certification Approval 5.0 Technical Authority Review Board, review results Yes Other Cert Rqmnt TBD Cross SYSCOM Coordination

  12. Questions ?

More Related