Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.

Slides:



Advertisements
Similar presentations
© 2004 Flashline Inc. The Seven Faces of Reuse Enterprise Architect Summit June 8, 2004 Charles Stack Founder and CEO Flashline, Inc. © 2004 Flashline.
Advertisements

Trusted Computing in Government Networks May 16, 2007 Richard C. (Dick) Schaeffer, Jr. Information Assurance Director National Security Agency.
Supporting New Business Imperatives Creating a Framework for Interoperable Media Services (FIMS)
Technology Drivers Traditional HPC application drivers – OS noise, resource monitoring and management, memory footprint – Complexity of resources to be.
Open Architecture: A Small Business Perspective Defense Daily Open Architecture Summit November 2011 Thomas Conrad.
Panel 5: The Latest in OA Innovation and C4ISR 4 November, 2014 Mike Rice President / Senior Systems Engineer R2E Inc.
Lecture 8 ISM- © 2010 Houman Younessi Information Systems Spring 2011 Convener: Houman Younessi
A Navy Business Initiative Defense Daily OA Summit 12 November 2013 Nickolas H. Guertin, PE Director for Transformation DASN RDT&E
1 Systems Engineering Part 2 Product Architectures.
Distributed Systems 1 Topics  What is a Distributed System?  Why Distributed Systems?  Examples of Distributed Systems  Distributed System Requirements.
Inc. User Requirements Presentation DoD Automatic Test Systems Michael Malesich DoD ATS R&D IPT Chair.
Advanced Processing Systems Honeywell Proprietary1 12/04/2003 Honeywell UF HCS & Honeywell DSES Opportunities Presented by Advanced Processing Systems.
Achieving Affordable, Capable Systems through Open Architecture Dr. Adam Razavian Deputy Major Program Manager Above Water Sensors Directorate PEO IWS2.0.
Unlocking Potential 1 Understanding the Open Business Model The value proposition for the government – Learning from industry DISTRIBUTION STATEMENT A.
Trusted Hardware: Can it be Trustworthy? Design Automation Conference 5 June 2007 Karl Levitt National Science Foundation Cynthia E. Irvine Naval Postgraduate.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Sami Aly Issues in Telecommunications3 February 2002 Development Plan 1.Product & Releases, evolution (Time line) 2.Features roll out 3.System.
SOA Architecture Delivery Process by Dr. Robert Marcus SRI International 1100 Wilson Boulevard Arlington, VA
02/12/00 E-Business Architecture
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Avionics Software Challenges Briefing to the DoD Software Engineering Science & Technology Summit Los Angeles, CA 7 August, 2001 Don C. Winter Manager.
Open Source WGISS 39. Definition of Open Source Software (OSS)  Open source or open source software (OSS) is any computer software distributed under.
Architecture Description Markup Language (ADML) What does it mean? Why should a tools vendor care?
© 1998 Concept Five Technologies Enterprise Application Integration Capability Maturity Model.
SOA – Development Organization Yogish Pai. 2 IT organization are structured to meet the business needs LOB-IT Aligned to a particular business unit for.
C4ISR via OA Mike Danjczek November, 2014 Copyright GTS 2014.
Who Are We? An open, international ecosystem containing 70+ organizations each working in their own self-interest while collaborating toward a common industry.
Lessons Learned in Smart Grid Cyber Security
4.x Performance Technology drivers – Exascale systems will consist of complex configurations with a huge number of potentially heterogeneous components.
1. 2 IT innovations in specialized areas where competitors will have difficulty copying Excellence in design of processes and activities and how they.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
. Traffic Flow Management System Benefits Flexibility for Future Growth: TFMS provides a modern software architecture to meet future growth and support.
Software Component Technology and Component Tracing CSC532 Presentation Developed & Presented by Feifei Xu.
Future Airborne Capability Environment (FACE)
0 is Changing Open Architecture Solutions The Way We Build Bill Ott, Vice President Open Architecture Summit.
ASSETT provides innovative engineering solutions focused on high reliability, low cost, state of the practice technologies that ensure the ability to upgrade.
May 17, USB Semiconductor IP How to Integrate USB into Your Design Eric Huang inSilicon Corporation.
Collaborative Open Source Software Utilization in Competitive Advantage Creation Author: Erkko Anttila Supervisor: Heikki Hämmäinen, Professor Instructor:
Service Oriented Architecture (SOA) at NIH Bill Jones
MDS Global IT Strategy Discussion July 7, Agenda  IntroductionErnest  Strategic directionsGanesh  DiscussionAll  Next stepsErnest.
1 The Benefits of an SOA in the Contact Center Brian Garr Program Director, IBM Speech Solutions.
IND Architecture Modernization, Deep Space Information Services Architecture (DISA), A Business Case for SOA-Based Modernization Mike Kolar, Integrated.
Process: A Generic View
ANKITHA CHOWDARY GARAPATI
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
ATIS’ Service Oriented Networks (SON) Activity Andrew White, Nokia Siemens Networks DOCUMENT #:GSC15-PLEN-81r1 FOR:Presentation SOURCE:ATIS AGENDA ITEM:PLEN.
Focus Area Forum: Sensor Open Systems Architecture (SOSA) Colonel Michael Schmidt Program Executive Officer for ISR and SOF August 4, 2015 Good morning,
GP Confidential GlobalPlatform’s Modular Approach to its Compliance and certification.
03/20/021 Spaceport Vision Team Members Organizations that contributed: Air Force NASA NCSS FAA Industry University Etc.
Open Source Software in Federal Acquisitons Acquiring Maximum Agility: Beyond Open Standards TCO and Best Value Revisited.
8a Certified. About Us  Headquarters in Vienna, VA  Service Disabled Veteran-owned Small Business  SBA 8(a) program participant  Small Disadvantaged.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
HP Network and Service Provider Business Unit Sebastiano Tevarotto February 2003.
© 2006 Epiance, Inc. Confidential and Proprietary 1.
April 15, 2013 Atul Kwatra Principal Engineer Intel Corporation Hardware/Software Co-design using SystemC/TLM – Challenges & Opportunities ISCUG ’13.
ABOUT COMPANY Janbask is one among the fastest growing IT Services and consulting company. We provide various solutions for strategy, consulting and implement.
1 Integration of Process Initiatives And Assessments Common Process Framework Integration of Management System Standards and Initiatives (QMS/CMMI/Lean/PMBP)
Making Choice Possible in the Acquisition of Machinery Control Systems Program Executive Office Integrated Warfare Systems (PEO IWS)
to Help Meet Interoperability Standards for the
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
Multi-Purpose Reconfigurable Training System (MRTS) Overview
Single Point of Entry (SPOE)
Sonata Accelerated Upgrade Assessment
Software Reuse Objectives
JOINED AT THE HIP: DEVSECOPS AND CLOUD-BASED ASSETS
Enterprise Architecture at Penn State
HCL Application Modernization Services
Introduction to SOA Part II: SOA in the enterprise
Requirements Development in CMMI
Presentation transcript:

Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and Data Rights Cross-Platform Reuse 9 November 2011 Mr. Bob McCaig ASSETT, Inc Manassas, Va

The Power of Modularity Modularity Brings: – Well defined system segments that encourage upgrades and competition Publish interfaces Isolate SW, HW and OS Isolate proprietary components – Re-usable software components – Interoperable applications – The Potential for Additional contractors capable of providing innovative solutions To Be Successful – Modularity Must Address – Not just published interfaces but well understood and widely used interfaces – Functionality that is commonly recognized and used across systems and platforms – Technology trends – modularity may migrate over time – Life cycle support Defense Daily Open Architecture Summit2

Open Architecture Characteristics of Open Architecture – Exposes interfaces to data and information that is used elsewhere in the system or supports competition Exposing Interfaces that have limited use elsewhere does not constitute “open” – Implements widely accepted standards Software development standards to ensure maintainability Interfaces that eliminate the need for proprietary design – Provides capabilities that can be re-used across systems and platforms Common system functions such as system monitoring, and time synchronization Common applications such as contact tracking, and navigation – Executes on widely used common hardware elements No unique hardware design – Requires a business model on both the customer’s and contractor’s side that ensures competition, maintenance/supportability and the protection of intellectual property Defense Daily Open Architecture Summit3

Open Architecture Example Defense Daily Open Architecture Summit4 Display Processing System Monitoring Reconfiguration Control Navigation Peripheral Interface Management Adapter Ethernet Peripheral A Peripheral B Peripheral C Peripheral D Peripheral N Command and Control Processing Peripheral New

Open Architecture Example (Levels of Modularity) Defense Daily Open Architecture Summit5

Business Model DoD and the commercial markets are different – Size of the customer set – Emphasis on information assurance – Need to access data and information at different levels Business model must – Facilitate technology insertion cycles Address migration of standards (e.g obsolescence – modern OS’s don’t have drivers to support) Open source code incorporates more capabilities and eliminates less used capabilities not managed by the DoD contractors – DoD needs to keep pace – Protect intellectual property Life line of small business – Define and maintain the role of the integrator Manage Risk Maintain System Level Configuration Control – Enable market penetration Horizontal integration – Product lines vs stovepipes Competition Defense Daily Open Architecture Summit6

Summary Open Architecture has proven to provide a significant reduction in cost while expanding system capabilities – Opening the door to small business brings innovative ideas for the solution of complex problems – Leveraging commercial industry research and development maintains DoD technological advantage while minimizing costs Maintaining the advantages in OA requires: – Tracking technology trends and the migration of standards – Defining the role of the integrator – Ensuring market penetration by “newcomers” through competition and the definition of product lines – Protecting intellectual property Defense Daily Open Architecture Summit7