Open Architecture Machinery Control System
Total Page:16
File Type:pdf, Size:1020Kb
Dr. Norbert Doerry, Tim Scherer, Jeff Cohen, Nick Guertin U.S. Navy: NAVSEA, NAVSSES, NAVSSES, PEO-IWS Open Architecture Machinery Control System commercial markets by various control ABSTRACT system suppliers who tailor their products to Machinery Control Systems are currently meet the customer’s specifications and individually crafted for each class of ship. Just frequently utilize existing technologies as the combat systems community is improving based on their experience on other ship performance while reducing cost through an platforms. As the result, the installed MCS open architecture approach, an opportunity products have a variety of Commercial-Off- exists to develop and field an open architecture The-Shelf (COTS) flavors and in many machinery control system for use on all naval cases proprietary software and hardware ships. This paper proposes a business and components. Because MCS suppliers have technical approach to developing an Open been able to leverage existing product Architecture Machinery Control System hardware, software, and development (OAMCS) common across all classes of ships. investment, customers typically get Once adopted this approach would provide competitively package pricing during initial commonality across the fleet while preserving system procurement. However, it becomes competition and a viable industrial base. This more costly to obtain and replace MCS commonality facilitates user training, improved components as the systems age and require maintenance, and regular software and hardware maintenance or upgrading due to the updates. specialized nature of each supplier’s products. Furthermore, the propagation of The technical approach includes a description of different vendor-specific products in a the open standards needed both within the particular fleet requires extra effort and cost boundaries of the MCS and between the MCS to train the operation and support and the user equipment. A description of the personnel." activities required during ship design and acquisition is also described. To address the supportability issues of the current approach to developing machinery INTRODUCTION control systems for shipboard applications, increase access to innovation, and reduce both The views expressed herein are the personal development and life-cycle cost, the authors opinions of the authors and are not necessarily propose that the Navy invest in developing an the official views of the Department of Defense open architecture approach. or any military department thereof. As described by Nguyen et al.: OPEN ARCHITECTURE "Machinery Control Systems (MCS) on both APPROACH commercial and military platform have Open Architecture is a collection of best evolved into multi-layer distributed and practices, technical and business, when redundant control systems that provide combined with a willing corporate culture, can versatile and reliable control and monitoring result in a highly effective life cycle strategy of ship HM&E equipment. Ship equipment where total cost of ownership is minimized and typically includes propulsion plant, electric capabilities to the warfighter are maximized. plant, damage control or safety equipment, and a host of auxiliary systems that support As defined by the Open Systems Joint Task the operation of the previous three major Force (OSJTF), an open system "employs systems. There is a wide-range of MCS modular design, uses widely supported and product offerings for the military and consensus based standards for its key interfaces, and has been subjected to successful validation MAY 25, 2011 APPROVED FOR PUBLIC RELEASE; 1 DISTRIBUTION IS UNLIMITED and verification tests to ensure the openness of 4. Enhanced transparency of system its key interfaces." An open architecture design through open peer reviews; "employs open standards for key interfaces within a system." Open standards "are widely 5. Competition and collaboration used, consensus based, published and through development of alternative maintained by recognized industry standards solutions and sources; organizations." An important objective of an 6. Analysis to determine which open system is to enable any competent supplier to provide modules or elements conforming to components will provide the best the standards that can be easily and successfully return on investment (ROI) to integrated into a working system meeting open…i.e., which components will customer requirements. Furthermore, the owner change most often due to technology of the system can take advantage of competitive bids among suppliers seeking to provide each upgrades or parts obsolescence and module. have the highest associated cost over The Navy has extended the work of the Modular the life cycle. Open Systems Approach (MOSA) work Achievement of these six principles requires performed by the DoD Open Systems Joint Task an affirmative answer to a fundamental Force (OSJTF) to more comprehensively question: achieve those desired goals as a part of the Can a qualified third party add, Naval Open Architecture (NOA) effort. NOA is modify, replace, remove, or provide defined as the confluence of business and support for a component of a system, technical practices yielding modular, based only on openly published and interoperable systems that adhere to open available technical and functional standards with published interfaces. It is the goal of the Naval Open Architecture effort to “field specifications of the component of common, interoperable capabilities more rapidly that system? at reduced costs”. In order to successfully permit a third party to add, modify, replace, remove or provide Guertin and Clements (2010) addressed the support as noted in the question above, the following core principals of the Open Navy must follow these business and Systems Architecture approach: technical elements as the program foundation 1. Modular designs with loose Foundational Business Elements of Open coupling and high cohesion that Systems Architecture: allow for independent acquisition of system components Government strategic use of Data 2. Continuous design disclosure and appropriate use of data rights rights to support competition; allowing greater visibility into an Periodic and strategic competition unfolding design and flexibility in throughout the life cycle; acquisition alternatives; 3. Enterprise investment strategies Increased capability to the warfighter that maximize reuse of system on a faster development timeline; designs and reduce total ownership Reduced life cycle costs; costs (TOC); MAY 25, 2011 APPROVED FOR PUBLIC RELEASE; 2 DISTRIBUTION IS UNLIMITED Shared risks with other programs a. A published objective architecture specific to real-time systems like MCS that provides through strategic alignment; industry standard design patterns that provide Minimized duplication for for hardware independent software development, virtualization to reduce vendor dependant technology development solutions, and isolation of proprietary design elements to maximize acquisition flexibility. investments, shared life cycle costs; b. An industry/Government consortia based and processing architecture and data model. Establish best fit solutions through c. Development kits and test harnesses that ensure software portability, consistency of open peer reviews. implementation, risk reduction for system Foundational Technical Elements of integration, and ability to field subsets of the system for zonal platform module shipboard Open Systems Architecture: construction and integration testing. Modular designs with low coupling These documents provide the enabling and high cohesion based on open environment that is needed to support the standards and published interfaces; development an open technical system and associated open business practices for design, Separation of hardware and software integration and certification processes, and to prevent hardware obsolescence technologies to successfully implement the complexities; strategy. Maximized reuse of assets to limit The Navy's previous success in implementing open architecture in the Acoustic Rapid COTS program unique development; Insertion (ARCI) program is well known and Full Design disclosure; documented by Boudreau (2006). Similarly, the Aegis Open Architecture program is currently Limited use of proprietary being implemented as part of the ongoing components, but establish well- Cruiser and Destroyer modernization programs. defined open system interfaces In June 2009, U.S.S. Bunker Hill (CG 52) was where those solutions perform the the first cruiser to complete the modernization best value; work including the Aegis Open Architecture Use of Modular Open Systems Guidance for incorporating the open architecture Approach (MOSA) and OSA- approach can be found at https://acc.dau.mil/oa. specific compliance metrics. Products available at this site include the "Naval Open Architecture Contract Guidebook for The confluence of these business and Program Managers", the Open Architecture technical foundational elements will support Assessment Tool and other items issued by the Naval Open Architecture Enterprise Team and the achievement of Office of the Secretary the DoD OA Team. of Defense Acquisition, Technology & Logistics (OSD AT&L)’ Better Buying Power efficiency initiative. The next innovation in the NOA transformation is to establish Open Product Line methods (Guertin, Clements 2010). These changes should embody the next evolution of MCS and include: MAY 25, 2011 APPROVED FOR PUBLIC RELEASE; 3 DISTRIBUTION IS UNLIMITED OPEN