Naval Open Architecture Military Aviation Architecture Conference 21 September 2010 Mr. Nickolas Guertin Director, Naval Open Architecture PEO IWS 7B Distribution Statement A: Distribution is unlimited.

Agenda Introduction To Open Architecture Intellectual Property Rights And Competition Contracts Avoiding Vendor Lock Product Lines Wrap-up

What is Naval Open Architecture? Government Asserts IP Rights Acquires All Design Artifacts Enterprise Collaborates on Reuse Peer Reviews Held for Consistency OA Contract Language Used Transparent Across Enterprise Build Systems Of Components Publish Interfaces Excise Proprietary IP Choose Standards Over Custom Reuse Components Business Practices Technical Practices Naval Open Architecture (OA) is the confluence of business and technical practices yielding modular, interoperable systems that adhere to open standards with published interfaces. Interfaces are important, because we test to those interfaces. They become more “standards” that we follow, and give us a foundation to build on. When people ask how do you implement OA it is important to remember that OA is not a “thing” that we buy. OA is a change in how we do business today – a new business model. It is not a methodology or a product you buy. It is a lifestyle / cultural change. Adopting the sum of the business and technical practices, leads to having a fully open system where the Navy can compete out components of the architecture to rapidly upgrade our systems when new requirements or threats emerge.

Competition and Innovation Important Concepts Competition and Innovation Rapidly Fielding and Upgrading Systems Software and Hardware Design Reuse Open Architecture (OA) is an enterprise-wide, multifaceted strategy for acquiring and maintaining National Security Systems through joint interoperable systems that adapt and exploit open-system design principles and architectures Elements of the OA strategy include increasing opportunities for: competition and innovation, enabling rapidly fielded and upgradeable systems, and optimizing software asset reuse

Acquiring Intellectual Property Rights (IPR) Disclose Designs Early and Often Reuse Previously Procured Components Enhance Interoperability Re-issue Contracts for Systems via Full and Open Competitions Enhance Life-cycle Affordability Acquiring and exercising the appropriate intellectual property rights (IPR) enables the Navy to implement the NOA principles:

Contract Competitions Agility Cost-effectiveness Strategic Reuse Reduces Development Less Testing Faster Fielding to War Fighter Produces Higher Quality Products Maintenance And Support Costs are Reduced Program Managers will utilize a Data Management Strategy that Asserts the most favorable Intellectual Property Rights under law to design, manufacture and sustain the system as well as to support full and open competition for production, sustainment, replacement or upgrade

Naval OA Contract Guidebook Recommended For All OA Contracts Language Should Be Tailored When Needed Five Key Chapters (C, H, L, M, And Incentive Plans) Nine Appendices To help achieve this goal, the Open Architecture Enterprise Team (OAET) developed the Naval OA Contract Guidebook for Program Managers Statement A version available at https://acc.dau.mil/NOAGuidebook

The OA Contract Guidebook and Vendor Lock Vendor Lock – Business Options Constrained Assert And Manage IPR Compete Regularly Remove Prime’s Incumbent Advantages Government Manages Architectures And Interfaces Compete Severable System Components Regularly Vendor Lock – no business options Contractor retains a proprietary hold on the system First Key – Securing and Managing needed IPR Create a Data Management Strategy Unlimited/Government Purpose/Limited Rights (e.g. SBIR) Licensing, when properly designed, can add flexibility to programs Enforce data rights when reviewing and accepting deliverables Second Key – Compete Regularly and Level the Playing Field Use the OA Contract Guidebook for evaluation criteria Segregated, separated, and priced components of limited rights Make all design information available early All GFE lab equipment must be on the table and mobile The Government must control system architectures and design, including component interfaces Regular competition of severable system components Have a two- to three-year cycle – plan ahead to level the playing field

Escape Vendor Lock -- Existing Systems Press Injection of OA Technical and Business Practices Assert Intellectual Property Rights Conduct Periodic Competition Of System Components Third-party (3P) Entrants Get Access To The Following: Program Plan Technical Documentation Architectures Software Development Kits Interface Description Documents Level The Playing Field Remove Prime’s Size Advantages Assert 3P Access to Labs with GFE OA technical or business practices early on, not always an option e.g. in-service systems Securing IPR is still the key Frequent competition of severable system components Determine those components that will be updated most often or that have critical mission performance implications – these will yield the largest OA return on investment (ROI) NAVAIR’s Key Open Sub-System (KOSS) Tool can help Maintaining a two- to three-year plan will provide ample opportunity to plan ahead for re-competes Third-party entrants must still have access to the following: Program Plan Reading Room of Program Documentation (Use OA Contract Guidebook as a starting point -- architectures, interfaces, etc.) Level Playing Field (insider knowledge should not be an unfair advantage to the incumbent)

Today’s Challenge: Buying the Same Thing Over and Over The Enterprise Must Work Together as a Team to Improve Government To Government – Reuse Must Become SOP Government to Business – Change Our Relationship Technical Underpinnings For Success Product Lines will drive re-use Product Line Markets must have protected budgets Program Managers must release control to gain savings and re-use Requirements will be managed differently with Product Lines A product line is a superset of all requirements for the market it serves Because we don’t pay again for the same product – business relationships are different As we mature, Product Line Managers will appear and evolve How Do We Get There?

Naval Open Architecture & Product Lines Are Complementary How Cost Savings Are Generated Open Architecture Competition – Lower Costs Tech Refresh of Hardware Fast Delivery of Capability to Fleet Product Lines Manage Feature Variations for Different Target Platforms Low Defect Rates Reuse Savings are Inherently Demonstrable OA PLs How Cost Savings Are Generated Open Architecture Competition – Lower Costs Tech Refresh of Hardware Fast Delivery of Capability to Fleet Product Lines Manage Feature Variations for Different Target Platforms Low Defect Rates Reuse Savings are Inherently Demonstrable

To implement OA, it is crucial that the Naval Enterprise speak with one voice, consistently using OA Tools and Resources Open Architecture Enterprise Team (OAET) https://acc.dau.mil/oa NOA 101 Continuous Learning Module Software Reuse Continuous Learning Module Open Architecture Assessment Tool (OAAT) Version 3.0 Key Open Sub-Systems (KOSS) tool SHARE II / NESI asset repositories OA Implementation Guide (forthcoming) OA Contract Guidebook for Program Managers, Version 2.0

For further information: Wrap-Up For further information: Naval OA Website: https://acc.dau.mil/oa Nick Guertin: nickolas.h.guertin@navy.mil