SCCI Tomahawk Systems Engineering Program Management Review (PMR) - PowerPoint PPT Presentation

scci tomahawk systems engineering program management review pmr n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
SCCI Tomahawk Systems Engineering Program Management Review (PMR) PowerPoint Presentation
Download Presentation
SCCI Tomahawk Systems Engineering Program Management Review (PMR)

play fullscreen
1 / 54
SCCI Tomahawk Systems Engineering Program Management Review (PMR)
555 Views
Download Presentation
magda
Download Presentation

SCCI Tomahawk Systems Engineering Program Management Review (PMR)

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SCCITomahawk Systems EngineeringProgram Management Review (PMR) N00178-02-C-2003 Option I 7 April 2004

  2. Agenda • Introduction Rob Crowder • Technical • Advanced Concepts Mary Feltis • System Requirements Larry Graybeal • Security Engineering Jim Valdivia • C4I Engineering Errol Richards • Software Requirements Paul Leiss • Software Design Regina Wilkerson • Lifecycle Engineering Dawn Carter • Financial • Financial Performance Rob Crowder • Closing

  3. Introduction

  4. SCCI Locations • Corporate Office • Frederick, MD • Systems Engineering Division • Fredericksburg, VA • Crystal City, VA • Dahlgren, VA • Escondido, CA • Washington, DC • Technical Services Division • Austin, TX • Boulder, CO • Dam Neck, VA • San Diego, CA

  5. SCCI Corporate Organization Chairman of the BoardLeo Harris President / CEOEdward Jackson Business Development / VP C. Carey Faison Human Resources / Sr. VP Lorie Morrell Controller Kathy McLaughlin Director of Contracting Richard Wagner Technical Support Division Division Manager Tom Brandt Systems Engineering Division Division Manager Edward Jackson (Acting) Systems Engineering Division Deputy Division Manager Rob Crowder Quality Assurance Manager Dick Hagenlocker Program Manager Rob Crowder QA Support Pat Zaccagni

  6. SCCI Technical Organization Program ManagerRob Crowder Advanced Concepts System Engineering Software Engineering Logistics Support Berge, Jerry Feltis, Mary Love, Randy Weaver, John Dowell, Bridget Graybeal, Larry Lamb, Shirley Richard, Gary Richards, Errol Shea, George Valdivia, Jim Zaccagni, Pat Cumberland, Laura Hagenlocker, Dick Leiss, Paul Roof, Pat Wilkerson, Regina Carter, Dawn Farrell, John Quinn, Tim

  7. Advanced Concepts Mary Feltis

  8. Advanced ConceptsResponsibilities • Our mission is to • Survey technology • Leverage outside technology development programs • SBIR and ONR • Develop and demonstrate new concepts • Support the transition of technology to support PMA-282 identified technology needs • In support of this mission, our work focus is on the following areas • Identifying & evaluating technology • Demonstrating technology • Transitioning technology

  9. Advanced ConceptsAccomplishments • Identifying and Evaluating Technology • One new SBIR topic funded in 2nd cycle of FY04 • All Phase I SBIR topics moved to Phase II • Kicked off two Phase I topics with new TPOC’s and five companies • Decision Support for TTWCS Operations • Demonstrating Technology • Developed Domain, Role & Task Models for Trainer Support • Completed Task Analysis used to develop Presentation Layer Demo • Conducted User Evaluations of the Presentation Layer HSI Prototype • Supported the development and use of the Presentation Layer Rapid Prototype Year End Operability Test • Designed and conducted the test plan for the NGTLAN prototype system • Successfully connected the NGTLAN system into the TTWCS EDM2 Suite as part of the year end “proof of concept “ demo • Conducted testing of the TTIMR prototype with 42 subjects at Norfolk and UVA • Interviewed Tomahawk Fleet personnel to obtain design information • Prototype representative task for the Mobile Maintenance Tool

  10. Advanced ConceptsAccomplishments, continued • Transitioning Technology • SCCI is participating in the transition of the ATTD (K71/SPAWAR/PMA-282) project into the HSI for TTWCS v5 &v6 • TTWCS v6 Task Analysis Effort has started • Supporting TTWCS v6 Presentation Layer Team • Preparing two SBIR topics transition to Phase III • Working with UVA to integrate TTIMR prototypes to conduct team analysis

  11. Advanced ConceptsFuture Tasks • Task Analysis for TTWCS v6 building on the Phase I ATTD work • Taking SA diagrams to Visio then making swim lanes • On the User Performance & Task Analysis Teams • Member of the following agile teams • Training • Decision Support • Task Manager • Continuing development and demonstration of prototypes • NGTLAN • RPT • Mobile Maintenance Tool (PDA) • TTIMR • TTIMR Team Testing at UVA • Mobile Maintenance Tool Exploratory Review • Preparing FY05 SBIR Cycle 1

  12. System Requirements Larry Graybeal

  13. System RequirementsResponsibilities • Generate Tomahawk Requirements • Requirements Tracing • Resolve issues • Review / analyze • Support • Process Improvement

  14. System RequirementsAccomplishments • Generate Tomahawk Requirements • Developed changes for Tactical Tomahawk system level requirements documents including • TWS Operational Requirements Document (ORD) • TWS SSDD (JCM-2142) • Segment Specification for Submarine Combat Control Systems (JCM-2166) • TTWCS System / Segment Specification (SSS) • Decomposed SSS into Level 1 requirements • Allocated Mission Critical level to requirements in SSS • Generated and delivered an updated TTWCS Algorithm Requirements document (JCM-2231/2) • Wrote Interface Issue Reports (IFIR) against 3900/146 • Working on TTWCS v6 candidate definition

  15. System RequirementsAccomplishments • Requirements Tracing • Generated / maintained requirements tracing in DOORS between the ORD, JCM 2142, JCM 2166, TTWCS SSS, AWCS SS, and OD 61988 • Importing the Fleet Requirements for the Tactical Tomahawk Training Device (T3D) into DOORS to be used as a source for traceability of the TTWCS ITA v5 SSS requirements • Migrated from DOORS 4/5 to DOORS 7 • Coordinating generation of the Test Verification Matrix • Allocated SSS and Level 1 requirements to various Test Levels and Verification Methods • Resolve Issues • Research / resolve TTWCS Problem Reports, Requirements Change Requests and IDR / SDR Action Items • Write CRs as necessary to resolve requirements / tracing issues

  16. System RequirementsAccomplishments • Review / Analyze • Reviewed and supplied comments on ICNs against JCM-2015, JCM-2038, 3900/114, 3900/146, WS-19708, WS-20931, and WS-20932 • Reviewed and provided comments and wrote changes against SSS, Level 1 Requirements, System Requirements Specifications, System Architect elements, the HCI Design Specification, Employment Concept Document and User Workflows • Support • Supported Engineering Review Board, Change Review Board, System Requirements Management Board, Configuration Control Board, TTWCS Technical Exchange Meetings, and Design Review Board • Supported C4I Working Group, Tomahawk Strike Coordination Working Group, Information Assurance Working Group, and SEI&V IPT meetings • Participated in 3900/114 and 3900/146 working groups • System Design Review and IDR • Process Improvement • Wrote Job Instructions • Requirements Development and Management Plan Participated in the Level 1 TC2 development Reviewed TC2 V5 CDDs and attended TEMs and ERBs Participated in TC2 CM inspections and ERBs

  17. System RequirementsUpcoming Plans • Maintain links from SSS to JCM-2142, JCM-2166, AWCS SS, and OD 61988 in DOORS • Develop SSS and Level 1 changes for TTWCS v6 • Develop TTWCS v6 changes to JCM-2142 • Maintain Verification Matrix • Maintain and update JCM-2231/2 • Participate in IDS-8, 3900/114 and 3900/146 IWGs • Review and comment on assigned documents • Participate in all TEMs and ERBs for SSDD, SRS, and SSS Participate in the V6 candidate review with the Fleet (May 4-5)

  18. Security Engineering Jim Valdivia

  19. Security EngineeringResponsibilities • Serve as lead engineer for Information Assurance (IA) to ensure all Twcs products achieve and maintain security accreditation in accordance with latest DoD/DON regulations • Support efforts to ensure that IA and associated security engineering practices are integrated early on into the planning, management, and direction of Twcs • Support Twcs Test Group preparations for Security Test & Evaluation • Maintain close and frequent liaison with SPAWAR 07-IA (aka PMW-161), which is the NAVY INFOSEC Office and our Certification Authority • Provide Security Engineering expertise to assist in resolving IA issues and actions, providing impact assessments, and identifying options • Participate in as many early morning telcons as possible

  20. Security EngineeringAccomplishments - ATWCS • Successfully completed C&A for ATWCS 1.7.2 • Completed all tailored DITSCAP tasks • Completed SSAOM (JCM-2226) – approved • Completed SSAA – approved • DAA and SPAWAR 07-IA – approved accreditation • ATWCS 1.7.2 is the last of the ATWCS line • Over the last ten years the entire ATWCS family has been through the C&A process – even as the process itself was changing • And all variants were successful – with no restrictions applied

  21. Security EngineeringAccomplishments – TTWCS v4 • Successfully completed C&A for TTWCS v4 phases A and B • Completed DITSCAP tasks, SSAOM (JCM-2246), and SSAA • Coordinated reviews, resolution of issues, and final approvals • Conducted multiple briefs with SPAWAR 07-IA and NSA • Responded to COTF User Rep IA issues and questions • DAA and SPAWAR 07-IA – approved accreditation • Enclave Gateway (EG) and NSA / DISA TABI Review • The EG required NSA and DISA assessment for operational use • Completed arduous process to get this done • NSA / CDTAB and DISA / DSAWG granted the EG a rating of “low” risk, issuing an Interim Authority To Connect (IATC) for 6 months • Completed “Top Secret / Secret System Classification Coordination” CONOPS and included it in the SSAOM delivered to each ship • Assisted in resolving COTF concerns regarding Signal Vulnerability Assessment for TTWCS and ATWCS – NSGAP letters received • Provided input to the Clinger-Cohen Act response

  22. Security EngineeringAccomplishments – TTWCS v5 • Defined appropriate set of security requirements and then decomposed them to develop SSDD requirements • Defended security requirements and necessary system IA attributes during TEMs and ERBs • Developed first draft of TTWCS v5 SSAA • Provided C&A schedule to complete accreditation by OTRR • TTWCS v5 and ITA • ITA can have significant influence on v5 C&A • Joined ITA WG to provide IA assessment of training features • Assisted in early draft of ITA CONOPS • SSGN / AWCS • Served as TTWCS IA rep on AWCS IA Focus Team • Assisted in initial draft of SSAA and subsequent reviews • Provided review / assessment of PNOCs to various program Coordination Drawings

  23. Security EngineeringAccomplishments - Miscellaneous • TTWCS v6 • Reviewed proposed candidate list for security impacts • Supported CR fest for potential v6 candidates and made recommendation to reassign a couple of candidates • Assigned as a reviewer for all v6 Candidate “White Papers” • Completed review of OVL05 • Developed the first draft C&A schedule • TTWCS v7 • Provided review of Technology Refresh Plan • Evaluating proposed enhancements to determine scope of C&A effort • DD(X) • Reviewed proposed security architecture for NSWCDD and PMA-282 • Provided assessment during kick-off meeting

  24. Security EngineeringFuture Plans • TTWCS v4 • Conduct a brief to NSA/DISA on penetration testing conducted on the EG in order to achieve full Approval To Connect (ATC) • Obtain final type-accreditation (Approval To Operate) from NAVAIR CIO for IA (the new DAA) • Update SSAA to reflect IA Controls iaw DoDD 8500.1 & 8500.2 • TTWCS v5 • Complete SSAA for Phase 1 DITSCAP and start SSAA Phase 2 • Start drafting SSAOM • Independent task analysis for IA impact • UWFs, SSS, Level 1, and Level 1 Allocation Modules

  25. Security EngineeringFuture Plans • TTWCS v6 • Support normal SE tasks • TTWCS v7 • Support normal SE tasks • Potential to require a lot of C&A work • DD(X) • Provide support as directed • Other • Update PMA-282 Master CM Plan (JCM-2206) and PMA-282 Software CM Process (JCM-2207) to reflect the IA Vulnerability Management (IAVM) and NISTISSP-11 programs, as required by current security directives

  26. Security EngineeringTechnical Issues • Penetration testing of AWCS on SSGN • TTWCS to Classified LAN interface on submarine • Need to see documented plan and IA “tool” selection • Need to preserve the integrity of TTWCS C&A • AWCS (TS / GENSER) and TS / SCI data • Various discussions and email identify activity and actions to investigate the impact of intentionally allowing AWCS and peripherals to be contaminated with SCI data • Also being discussed is a contingency plan to return the “system” back to normal by swapping out disks • It’s not that easy • If this initiative is real, then at some point it needs to get into a formal, unbiased process of evaluation

  27. C4I Engineering Errol Richards

  28. C4I EngineeringResponsibilities • Resolving Twcs C4I technical issues with SPAWAR • PMW 156, 157, 165, 179, and NCTSI • Twcs Testing and Installation coordination • Lead coordination of MOAs, ICDs, IRS, etc. • System Engineering Teleconference support • Participate in pertinent C4I Forums and Conferences • Facilitate NSWCDD TEMs with SPAWAR

  29. C4I EngineeringAccomplishments • PMW 156 • Participated in meetings • NAVSSI Integrated Process Team Mtgs (April) • Report issues and priorities to NSWCDD • Identified key delivery dates of NAVSSI Software • Hosted PMA 282 / PMW 156 summit meetings (Aug 03, Jan 04 ) • Achieved Documentation Acceptance • JCM 2241 IDD signed by SPAWAR Mar 04 • NAVSSI ICD – A / B switch removal • PMW 157 • Twcs Representative at Core Engineering Meetings • Report GCCS-M build updates / issues to NSWCDD • Helped document GCCS-M interface to Tomahawk • JCM 2241 GCCS-M IDD signed 13 Jan 04 • Provided GCCS-M Installation Coordination • Install Team Coordination for platforms getting GCCS 3.1.2.1 • Participate in monthly Installation Telcon • Hosted PMA-282 / PMW 157 Summit meetings (Jan, Aug) • Supported Testing and Evaluation • GCCS-M 4x backward compatibility to ATWCS (April)

  30. C4I EngineeringAccomplishments, continued • PMW 165 • Acquired Documentation Acceptance • Oversaw TTWCS / ISNS MOA meetings and ensured signed agreement between Program Offices • Managed process to ensure ATWCS 1.7.2.2 build approved for System/Sub-System Interface List (SSIL) • Hosted PMA-282 / PMW 165 Summit meetings (March, Aug) • Hosted PHD / PMW 165 meeting (Jan) • PMW 179 • Acquired Documentation Acceptance • NCR-ADNS-03-003 TCOMMS to ADNS connection • Drafted PMA-282 to PMW 179 MOA • Technical representation • TCOMMS bandwidth questions • Hosted PMA-282 / PMW 179 meetings ( Aug,March ) • Hosted PHD / PMW 179 meeting (Jan 04)

  31. C4I EngineeringAccomplishments, continued • NCTSI • Supported Testing and Evaluation • Provided NCTSI government test rep with Twcs technical support documentation • Oversaw ATWCS 1.7.2.2 extension of authority to operate • Oversaw TTWCS I6 (6.3.5) interop certification • Supported Meetings • Participated in Operational Interoperability Requirements Group (OIRG) mtgs (Oct 03) • Participated in Technical Interface Support Group (TISG) mtgs (Jul/Oct 03) • PMA-282/NCTSI meetings (Aug, March) • ATWCS • Supported Technical Review Board (TRB) • Assigned Lead for C3I and JMCIS STRs • Performed SE assessments • Supported ATWCS SE mtg • Resolved multiple ATWCS issues with SPAWAR • ATWCS 1.7.2.2 Certification

  32. C4I EngineeringAccomplishments, continued • TTWCS • Supported v5 SSS reviews • Assigned GCCS-M, ACMS, TCOMMS, Track Data • Completed SSS inspections • Supported TTWCS SE&IPT mtg • Resolved multiple TTWCS issues with SPAWAR • Supported Software Certifications • TWCS 6.3.5 Certification • Supported SPAWAR testing • GCCS-M 4x backwards compatibility to ATWCS • TTWCS DCFF • Held DCFF CONOPS meetings • Hosted DCFF Conference at FCTCPAC (25 Aug 03) • Participated in Land Attack CONOPS WG (Dec 03) • Drafted TTWCS JVMF ICP • Work closely with NCTSI VMF reps • Coordinating with NFCS, AFATDS, TLDHS program offices • Briefings • Briefed DCFF ICPs to Tsewg (Sep 03) • Briefed TTWCS DCFF at NCTSI TISG (Nov 03) • Briefed JVMF Sub Group on TTWCS DCFF (Feb 04)

  33. C4I EngineeringFuture Plans • Implement TTWCS JVMF message requirements into Military Standard • Help refine Capstone Land Attack CONOPS • Provide technical liaison to SPAWAR and TTWCS SEs and installers as Tomahawk SME in support of NSWCDD SE Team • Support interface testingand certification of TTWCS v5 • Help coordinate NAVSSI – TTWCS Interoperability tests • Support Twcs System Engineering meetings as required

  34. Software Requirements Paul Leiss

  35. Software RequirementsResponsibilities • Develop and maintain Software Requirements Specifications (SRS) • Combat Control System (CCS) Simulator (SIM) • Launch Control System (LCS) SIM • Missile Manager (MM) Main • Missile (MSL) SIM • Navigation Sensor System Interface (NAVSSI) SIM • Vertical Launching System (VLS) SIM • Weapons Control Module (WCM) SIM • Weapons System Navigation (WSN) SIM • Weapon Control System (WCS) SIM • Develop and support System Requirement artifacts • System Segment Specification (SSS) • System Segment Design Document (SSDD) • Interface documents • White papers • Design studies • Support the development of System Design artifacts • Support the development of Formal Qualification Test artifacts

  36. Software RequirementsAccomplishments – Software Requirements • Developed, inspected, ERB’d, and delivered the following SRSs

  37. Software RequirementsAccomplishments, continued • System Engineering Support Activities • Supported CRBs • Supported SRMBs • Generated over 60 CRs • Supported TEMs, ERBs, and other formal and informal reviews of System Artifacts • Supported the development of new system level requirements • Supported Level 1 diagram development

  38. Software RequirementsFuture Plans • Software Requirements • Develop, inspect, ERB, and deliver Build 5.3 driven changes for the CCS SIM, LCS SIM, MM Main, MSL SIM, NAVSSI, VLS SIM, WCM SIM, WCS SIM, WSN SIM, and Weapon Control System (WCS) SIM SRSs • System Engineering Support Activities • Support CRBs • Support SRMB • Generate and assess CRs • Support the development of new system level requirements • Support Level 1 diagram development • Software Design Support • Support Software Design Document (SDD) inspections • Formal Qualification Testing • Support in Formal Qualification Testing (FQT) inspections

  39. Software Design Regina Wilkerson

  40. Software DesignResponsibilities • Develop and maintain the Software Design Documents (SDDs) • Launch Control (LC) • Missile Manager (MM) • Support the development of Formal Qualification Test (FQT) artifacts • Support the development of Software Requirement Specifications (SRSs)

  41. Software DesignAccomplishments • SDD Development • ATWCS • Launch Control (LC) • LC 4.9 • TTWCS • V5.x • MM (Surface) • I6 • UK • SSGN • Cruiser Conversion • Common Build • CAIV Space • MM (US Submarine) • I6 • Seawolf / VA Class • Traceability links to SRS

  42. Software DesignAccomplishments, continued • SDD Inspections • Fagan Peer Review Inspections held • SRS / FQT / Code Representatives present to review SDD • SDD Updates • V5.x • Weekly SDD Configuration Management (CM) • Data Management (DM) to track changes • Implement change package revisions • ATWCS / UK TTWCS / I6 TTWCS • Baseline documents • New builds • Software Design Support • Review packages and provide comments for Fagan inspections • System Engineering • Software Requirements • Formal Qualification Tests • Member of Design Piglet for Process Improvement

  43. Software DesignFuture Plans

  44. Lifecycle Engineering Dawn Carter

  45. Lifecycle EngineeringResponsibilities

  46. Lifecycle EngineeringAccomplishments – ATWCS / TTWCS • Provide direct support to ILS Manager for V6 and V7 • Delivery schedules for ILS products • Inputs for defining ILS Tasks for FY05 • Provide direct support to SPT Co-Chair • Conduct ATWCS Hardware Lab Configuration Audit and maintain status • Provide briefings at ATWCS test readiness reviews on status of lab hardware • Maintain Logistics Issues Tracking System (LITS) Database • Upgraded to include TTWCS Issues • Added product owner comments to ATWCS and TTWCS “open” data sheets • Developed a LITS product owner response tracking system • Provided LITS input for PMA-282 POW • Develop and maintain Training Deficiency Tracking System (TDTS) • Provided briefings at TTWCS CTDT’s for the training community • Develop shipboard briefing books • Provided pertinent data for shipboard visits by PMA-282 • Develop Battle Group (BG) matrices • Providing system configuration compatibility • Maintain Memorandum Of Agreement (MOA) Quad Charts • “Quick References” providing logistics requirements and general information on I/F MOAs

  47. Lifecycle EngineeringAccomplishments – ATWCS / TTWCS, continued • Update to Joint Cruise Missile (JCM)-2157 System Segment Design Document (SSDD) front matter development • Coordinating receipt of technical concurrence for Draft TWS/ATWCS BFTT Interface MOA from PEO IWS IE (formerly PMS 430) for PMA-282 • Update to JCM-2240 – ATWCS-BFTT IRS • ICN Change • Review technical documentation and assess for logistics impacts • Review and analyze build definitions for ILS product impacts • Provide lab checkout and review of ILS products • Perform STR analysis for ILS impacts and provide assessments in TIMES • Develop new charter for TTWCS SPT (formerly OSPT and MSPT) • Act as secretariat for TTWCS SPT

  48. Lifecycle EngineeringAccomplishments – ATWCS / TTWCS, continued • Participate in Human System Integration (HSI) and Human Computer Interface (HCI) working group meetings • Participate in Deployment and Support (D&S) IPT and Logistics and Fleet Support weekly telecons • Provide membership to Integrated Training Architecture WG • For development of ITA TTWS Requirements and an ITA TTWS CONOPS • Participate in ATWCS System Engineering Staff Meetings and document reviews • Monitored several weekly technical telecons and reported items of interest to the logistics community members • Support TTWCS Interface for Monitoring and Retargeting (TTIMR) Project at NSWC DD, FCTCLANT and University of Virginia • Participate and support on-going development of Text to Speech Project

  49. Lifecycle EngineeringAccomplishments – ATWCS / TTWCS, continued • Established and maintained TTWCS TTB binders at the NSWC DD Facility • Developed a “History of Tomahawk Training Devices” for PMA-282 in support of ongoing Integrated Training Architecture (ITA) initiatives • Supported “Decomposition” of TTWCS v4 SSS to SSDD level 1 requirements utilizing “User Work Flows” • Developed combined Charter incorporating TTWCS and ATWCS MSPT and OSPT into Twcs SPT • Develop and provide weekly meeting summary reports • Integral in development of alerts process for incorporation in ISS

  50. Lifecycle EngineeringAccomplishments – UK ATWCS / TTWCS • Track Commercial-Off-The-Shelf (COTS) Obsolescence items • Survey banned material and provide findings • Survey UK unique items • Validate and Verify Technical Documentation – • Program Assembly Installation Document (PAID) • Provides very detailed step-by-step procedures to load UK software • Software User’s Manual (SUM) • Provides the operator with complete description of start-up procedures • Verify Start-Up and Diagnostic (SD) on the UK Suite • Verify the Start-Up and Diagnostics Stand-Alone (SDSA) Version 2.0 on the UK Suite