60 likes | 217 Views
Defense Daily Open Architecture (OA) Summit 18 November 2010 Marty Meyer Director, Requirements & Architectures Division Office of Technology Innovation and Acquisition. CBP Foundational Technology Interests. Two Main Focus Areas:
E N D
Defense Daily Open Architecture (OA) Summit18 November 2010Marty MeyerDirector, Requirements & Architectures DivisionOffice of Technology Innovation and Acquisition
CBP Foundational Technology Interests • Two Main Focus Areas: • Connectivity – The ability for components (e.g. sensors, people) on a network to communicate with one another, and the ease (speed) with which they can communicate • Open Architecture • Increased ability to insert cutting edge technology as it evolves • Improved ability to adjust to changes in mission needs • Improved ability to reuse components among systems • Increased ability to leverage commercial investment • Expected reductions in acquisition cycle time Flexibility – Robustness – Agility – Affordability
Open Architecture Vision • Adopt and institutionalize open architecture principles and processes • Interfaces, modularity, non-proprietary solutions • Smaller-scale demonstration prior to procurements • Objective: Deliver more capability to the agents and officers in the field faster and at reduced costs • Transform CBP information flow and support for operations • Enable technology insertions required to stay in front of ‘the threat’ • Encourage environment of competition and innovation • Large, medium, small companies alike
Open Architecture Principles • Encourage modular designs and data disclosure • Competition and collaboration • Interoperable applications and web services • Reusable applications • Selected through open competition of ‘best of breed’ candidates • Reviewed by subject matter expert peers • Based on data-driven analysis and experimentation • Ensure life cycle affordability
Open Architecture Ground Rules • No development • Industry has asserted they have OA systems now • We are prepared to test select solutions • If we believe a solution can meet our needs • OA does not mean paying repetitively for integration • We want to specify interface requirements • We expect new capabilities to work when we “plug” them in • If you have a product that meets our needs: • We want to hear from you