Andrew Biss Systems Engineer Sensis Corporation 3 rd Annual Open Architecture Summit Business Approaches to OA.

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

October 10-13, 2006 San Diego Convention Center, San Diego California VoIP/SOA Integration Impact on IT Apps, Processes, & Overall Business.
Presentation Title | Date | Page 1 Extracting Value from SOA.
IBM Corporate Environmental Affairs and Product Safety
Enterprise Architecture Rapid Assessment
How to commence the IT Modernization Process?
Prescriptive Process models
Optimize tomorrow today. TM Cost and Affordability approach at Development Planning stage 1.
Incremental Commitment Spiral Model, Expedited Engineering, and Kanban Jo Ann Lane and Alexey Tregubov USC CSSE Rich Turner Stevens University.
Test Automation Success: Choosing the Right People & Process
JUNE 2007 page 1 EDS Proprietary Applications Modernization Services Modernizing the Applications Portfolio.
BENEFITS OF SUCCESSFUL IT MODERNIZATION
Chapter 15: Packaged Software and Enterprise Resource Planning
Lecture # 2 : Process Models
Alternate Software Development Methodologies
ITIL: Service Transition
Office of the Secretary of Defense Defense Microelectronics Activity (DMEA) Defense Microelectronics Activity (DMEA) Doug Casanova Defense Microelectronics.
Inc. User Requirements Presentation DoD Automatic Test Systems Michael Malesich DoD ATS R&D IPT Chair.
Achieving Affordable, Capable Systems through Open Architecture Dr. Adam Razavian Deputy Major Program Manager Above Water Sensors Directorate PEO IWS2.0.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Copyright © 2002 by Lockheed Martin Corporation All Rights Reserved This material may be reproduced by or for the U. S. Government pursuant to the copyright.
SE 464: Industrial Information systems Systems Engineering Department Industrial Information System LAB 02: Introduction to SAP.
Fundamentals of Information Systems, Second Edition
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Enterprise Architecture
Effective Methods for Software and Systems Integration
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Design with Reuse l Building software from reusable components.
Information Systems Planning
Nurjana Technologies Company Presentation. Nurjana Technologies (NT) is a small business enterprise founded in 2012 and operating in Aerospace and Defence.
Chapter 2 The process Process, Methods, and Tools
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
EENG 1920 Chapter 1 The Engineering Design Process 1.
The Challenge of IT-Business Alignment
. Traffic Flow Management System Benefits Flexibility for Future Growth: TFMS provides a modern software architecture to meet future growth and support.
Naval Open Architecture Military Aviation Architecture Conference
Future Airborne Capability Environment (FACE)
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
New Generation Core Banking System For Sustained Growth
0 is Changing Open Architecture Solutions The Way We Build Bill Ott, Vice President Open Architecture Summit.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Systems Analysis and Design in a Changing World, Fourth Edition
Catawba County Board of Commissioners Retreat June 11, 2007 It is a great time to be an innovator 2007 Technology Strategic Plan *
Fundamentals of Information Systems, Second Edition 1 Systems Development.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
25 April Unified Cryptologic Architecture: A Framework for a Service Based Architecture Unified Cryptologic Architecture: A Framework for a Service.
ITIL VS COBIT 06 PLM - Group 9
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
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.
MEASURING BPM SOFTWARE ROI AND ITS BENEFITS IN RISK MANAGEMENT PROCESS AUTOMATION Contact us at | Web : | Tel: 1.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Chapter 2: The Process. What is Process? Software Engineering Process is the glue that holds the technology layers together and enables rational and timely.
Process 4 Hours.
ITIL: Service Transition
Plan and Safeguard Service Package for SAP S/4HANA
Software Life Cycle “What happens in the ‘life’ of software”
Presented by Munezero Immaculee Joselyne PhD in Software Engineering
Critical Factors in Managing Technology
Pertemuan 22 Materi : Buku Wajib & Sumber Materi :
FDA Objectives and Implementation Planning
Chapter 13 Building Systems.
Presentation transcript:

Andrew Biss Systems Engineer Sensis Corporation 3 rd Annual Open Architecture Summit Business Approaches to OA

2 The Need for Open Architecture To avoid spiraling costs and ensure supportability, the USN has adopted OA core principles Building a fleet that is interoperable and affordable To be competitive Sensis recognizes the benefits of OA Reducing Time-to-Market and Increasing Cost Savings Not always a driving requirement for our customers, but a driving requirement from our internal stakeholders This has lead to Sensis completing 5 successful SW programs built on OA principles with 3 iterations of OA design Sensis and the USN have come to the same conclusion from complementary, but different vantage points

3 Open Technology Development in Sensis Processes As part of embracing the OA principles, OTD is embedded in our formal processes for development Standard Operating Procedures and Work Instructions exist specific to ensuring OA is incorporated in SW and HW Sensis SOP OTD states that the benefits of an OTD strategy are: 1. Enhancing agility to rapidly adapt and modify to user needed capabilities 2. Enhancing competitiveness by lowering cost and minimizing program execution risk 3. Encouraging decentralized innovation, shared discovery and forward- looking design 4. Leveraging external and existing solutions, taking intelligent risk for substantial gains, and factoring in life cycle cost advantages 5. Enabling ease of changes, upgrades, or technology insertion 6. Enabling joint integrated architectures and interoperability with other systems Sensis requires OA in our development process to be competitive

4 Sensis Radar Upgrade Product Line OTD starts before the program begins Product Specification is evaluated for capability gaps at proposal stage Drives re-use starting at the top-level requirements/architecture Benefits of previous development programs are inherent Architecture based upon OA Core Principles Key external and internal interfaces are isolated and well-defined  Individual components can be modified without impacting total architecture Component designs are based upon life-cycle affordability and modularity  COTS components for servers, comms, and frequency synthesis Reusable application software  SW components are written to allow adaptability Demonstrated 2D/3D S- and L-Band signal processing and AESA components applicable to multiple radar platforms The result is a system that is adaptable and reconfigurable to address a variety of customer needs

5 SW OA Product Approach Characteristics of the Open approach to SW Products include Platform independence  All Software is built on middleware  All software should be capable of “desktop-development” rather than requiring the host platform  Strong APIs with a threading architecture Component-Level Publish/Subscribe  Increases product reuse and configurability through loose coupling of components Isolation of algorithms/functions into configurable libraries  Allows algorithm development and improvement without impacting transport and application framework OA software approach allows software products to be developed and refreshed independent of HW platform

6 Legacy Systems OPEN German Luftwaffe Hughes Air Defense Radars HADR-2000S 3D, S-Band Civil/Military Air Surveillance Phased Array PSR integrated with Monopulse SSR Installation October 2009 UK NATS Watchman SPE D, S-Band Civil Air Surveillance 3 Sites Commissioned by UK CAA as of 2010 Canadian DND ASR ASR-3 SPS and TX 2D, L-Band Civil/Military Air Surveillance Dual Redundant System with a Solid-State Transmitter Installation July 2010 An OA Radar Signal Processor has been developed that is applicable to Legacy as well as State-of-the-Art systems Signal Processor Evolution Modern Mobile AESA Radar CLOSED State-of-the-Art Global Legacy Rotating Radars

7 Minimizing SW Development Risk Striving for widely supported, open source technologies as SW components and SW platforms reduce the impact during technology upgrades Long-Term Supportability is correlated to Relative Openness Allows the HW components of the product to be refreshed without major impact to the SW components Choosing Open Source technologies increases supportability and reduces risk in Total Ownership Cost

8 Quantifying Openness Assessing SW/FW Reuse Sensis Work Instruction defines a concrete, repeatable, and consistent method for evaluating the level of reuse of a given component for a given program within Sensis Develops a “Reuse Level” that is equivalent to a effort factor to be used in estimating development costs A series of measurement factors are used to evaluate the modifications required to estimate the level of reuse Software, Pedigree, Requirements, Personnel aspects are included in the evaluation Working with current customer for developing a methodology to evaluate total OA based on specific metrics Sensis is proactively and continuously reviewing our practices and new innovation

9 New L1 L2 L3 3-D L-Band Mobile Radar Monopulse Range-Ambiguous Digital Beamforming Single scan hit-to-firm track Embedded SBCs, VxWorks Practiced OA Radar A 3-D S-Band Fixed-Site Radar Sequential lobing Range-Unambiguous Analog Beamforming Multi-scan hit-to-firm track COTS Servers, Linux Radar B High-level of reuse is quantifiable and achievable with a configurable, building-block architecture

10 HW OA Product Approach Characteristics of the Open approach to HW Products include: Leverage commercial advancements for technology agility Afford future growth options in functionality and performance without disruptive and costly redesigns Accommodate ready substitution for obsolete components Employ commonly used standards for key interfaces All like units interchangeable No specialized tools or equipment to perform field service Outcome is validated low production costs for Sensis Open Technology approach for T/R Units Derived Open Technology L-Band T/R Unit costs for pilot and full production runs Detailed bottoms-up costings based on Bill of Materials Formal Quotations received from all suppliers – identified opportunities for cost take-outs Benchmarked against an independently derived production cost for a conventional T/R Unit prototyped to the same Specification Control Document Open Technology T/R Unit implementation is fully 1/3 lower in production cost than its conventional design counterpart

11 Open Technology T/R Units Sensis has employed Open Technology for the production of Transmit/Receive (T/R) units Major component of a phased array radar antenna Architected to deliver high performance while being operationally flexible  Demonstrated specification compliant performance  Product line philosophy with the Unit and its constituents being advantageous for multiple systems Reduction in T/R unit production costs by at least a third  Quotations on competing approaches support this claim  Significant as the T/R units represent 50 to 70% of the array cost, which itself is 60 to 80% of the system cost Reduction in operational and sustainment costs of up to 50%  Support system operational life-spans in excess of 20 years Sensis asserts that to fully realize the promise of Open Architecture the principles must extend internal to the Units External form/fit/function/interface interchangeability at the unit level is insufficient Sensis has validated the production cost-savings of OTD for HW components while avoiding vendor-lock and obsolescence

12 Resulting Product Characteristics Sensis capabilities for radar are distinguished by: Multi-mission capability  Operational flexibility, adaptable, scalable State-of-the-Art performance  Performance isn’t sacrificed by implementing OA principles Open Technology for software and hardware configuration items  Modular, platform independent, product line elements Affordable, sustainable  Low development, acquisition, and support costs. Low technical risk. Reliable operation  High availability with low mean time to repair Efficient operation  Low overhead power consumption Sensis has embraced Open Architecture principles for high performance radar systems – legacy and next generation

13 Benefits of an Open Architecture, Product Line Approach Within the paper “Comparing Acquisition Strategies: Open Architecture vs. Product Lines” 1, the following benefits of an OA and Product Line approach are given: Cost Time to Delivery Elimination of Duplicate Effort Higher Quality For Industry these translate internally to the following macro-level benefits: Expanding Capability Increasing Reuse Reducing Time to Delivery Development Cost Savings [1] Guertin, N., Clements, P., “Comparing Acquisition Strategies: Open Architecture vs. Product Lines” Sensis has realized the benefits that the Navy desires