Making Choice Possible in the Acquisition of Machinery Control Systems Program Executive Office Integrated Warfare Systems (PEO IWS)

UNCLASSIFIED Making Choice Possible Introduction  Open Architecture (OA)  Business Decisions for Implementing OA  Product Line Development  Product Line Acquisition Approaches Maximizing Choice using OA and Product Lines Application  Combat Systems  Machinery Control Systems Closing Remarks

UNCLASSIFIED Naval Open Architecture Naval Open Architecture (OA) An OA strategy includes competition and innovation, enabling rapidly fielded and upgradeable systems, and optimizing software asset reuse. Page 3

UNCLASSIFIED Maximizing Choice using OA and Product Lines Benefits  Application  Cost  Time to Delivery  Duplication of Effort  Product Quality

UNCLASSIFIED Open Architecture Business Decisions Decision #1: Hardware Vendor Independence Decision #2: Design Disclosure Decision #3: Strategic Reuse Decision #4: Peer Review Decision #5: Competition Naval Open Architecture: A multifaceted business and technical strategy

UNCLASSIFIED Combat Systems OA + Product Lines DDG1000 Integration New ship class Integration Aegis Integration Carrier / Amphib Integration SSDS Update Shared Components Shared Components Shared Components for Future Applications and Available for Backfit

UNCLASSIFIED Combat Systems Hardware Operating System Middleware Display Track Mgmt Command & Control Sensor Mgmt Weapon Mgmt Vehicle Control Decouple Hardware from Software Platform Independent Applications TI-XX Computing Environment

UNCLASSIFIED Combat Systems Update Cycles ACB / TI Notional Model Requires transition to COTS computing via initial TI Each ACB builds on prior ACBs while adding new capabilities Transitioned ships receive new ACB every 2 years Every ship receives every other TI

UNCLASSIFIED MCS Example of Current Situation SHIP CLASS CGDDGLCSLHDLPDCVN SYSTEMSSYSTEMS Controller technology Workstation GT controller 1233 Core switch Operating system Software language HMI software

UNCLASSIFIED Capability A Capability B Capability C Capability D Identification of Common Capability Multiple Development Activities Platform 1 Platform 2 Platform 3 X X X X X XX X

UNCLASSIFIED Product Line Management $$ Requirements Engineers Req Design Models Architects Models Source Code Developers Code Test Cases Testing & Validation Cases Shipclass ‘A’ Shipclass ‘B’ Shipclass ‘C’ Reusable Core Assets

UNCLASSIFIED Active, strong Systems Engineering Assigned Leads: Chief Engineer – Systems Engineering Chief Engineer – Software Overall Architecture Government System Architect and IPTSystem Integrator and IPT OCI Industry Damage Control Potable Water Electrical Propulsion Navigation Data Acquisition Network Management Processing & Display Services Infrastructure Tech Data Architecture Open, Published TrainingDisplay and Control

UNCLASSIFIED Percentage of the same data acquisition function Function specific to gas turbines Function specific to diesel Function specific to steam

UNCLASSIFIED 14 Traditional System MFOP Enabled System Target System System Platform Shore Support Target System Trained Maintainer OBRP Kit OBRP Kit On-Shore Training Tech Support Distance Support Organic Spares Infrastructure Embed OBRPs Provide Auto Failover Eliminating At Sea Maintenance Reduces Training and Sparing Infrastructure A Commercial Distance Support Model Replaces The Organic Maintenance And Logistics Infrastructure Auto Failover To Reserve Hardware Improves Availability MFOP –=Reducing TOC and Improving Availability Life Cycle Savings Life Cycle As Usual Modern COTS Based IT Technology and The Navy’s Network Infrastructure Are Underutilized Relative To Life Cycle Support Acquisition Programs Continue To Specify Logistics Elements Geared To “Fix On Failure” Principles The Need to Be Connected

UNCLASSIFIED Defining a Framework for Choice  Naval Open Architecture  Proven Principles and Practices  Product Lines  Proven low-risk methods and measurable results  Commonality across the Naval Enterprise  Applicable to real-time safety critical systems