Open systems architecture: Difference between revisions

Revision as of 22:03, 26 January 2020

Latest revision as of 23:37, 15 September 2024

(29 intermediate revisions by 9 users not shown)

Line 1:

{{Short description|System design objective}}

{| class="wikitable"

{{Use dmy dates|date=April 2020}}

| colspan="2" |

{| class="wikitable"

|

= OPEN SYSTEMS ARCHITECTURE (OSA) - Source United States Navy Fact File =

|-

|

|-

|'''Description'''An Open Systems Architecture (OSA) approach integrates business and technical practices that yield systems with severable modules which can be competed. A system constructed in this way allows vendor-independent acquisition of warfighting capabilities, including the intentional creation of interoperable Enterprise-wide reusable components. Successful OSA acquisitions result in reduced total ownership cost and can be quickly customized, modified, and extended throughout the product life cycle in response to changing user requirements. For more information, visit the Naval OSA website at <nowiki>https://acc.dau.mil/osa</nowiki>.

|-

|

|-

|'''Features'''The essence of OSA is organized decompositions of complex systems, using carefully defined execution boundaries, layered onto a framework of software and hardware shared services, and a vibrant business model that facilitates competition. It requires publishing of key interfaces within the system and design disclosure. A key enabler for OSA is the adoption of an open business model which requires doing business in a transparent way that leverages the collaborative innovation potential of numerous participants across the enterprise, permitting shared risk, maximized asset reuse, and reduced total ownership costs.

OSA yields modular, interoperable systems which more easily support component addition, modification, or replacement by different vendors throughout the lifecycle, driving opportunities for enhanced competition and innovation. OSA is composed of five fundamental principles:

1. Modular designs based on standards, with loose coupling and high cohesion, that allow for independent acquisition of system components;

2. Enterprise investment strategies, based on collaboration and trust, that maximize reuse of proven hardware system designs and ensure we spend the least to get the best;

3. Transformation of the life cycle sustainment strategies for software intensive systems through proven technology insertion and software product upgrade techniques;

4. Dramatically lower development risk through transparency of system designs, continuous design disclosure, and Government, academia, and industry peer reviews; and

5. Strategic use of data rights to ensure a level competitive playing field and access to alternative solutions and sources, across the life cycle.<br />

|-

|

|-

|'''Background'''Following an Executive Committee Meeting (EXCOMM), the Assistant Secretary of the Navy for Research, Development, and Acquisition (ASN (RDA)) published an Open Architecture (OA) Policy on 5 August 2004 which established a cross-Warfare Domain OA Enterprise Team with clear goals for establish OA principles consistently throughout the Naval Enterprise. In November 2012, ASN (RDA) signed out the Naval Open Systems Architecture Strategy (<nowiki>https://acc.dau.mil/adl/en-US/637265/file/69101/OSABrochure-2013.pdf</nowiki>), which calls for an iterative set of business and technical changes pointing to an end state where affordable, open platforms easily accommodate open modules.

In April 2013, the Under Secretary for Defense, Acquisition, Technology and Logistics (USD(AT&L)) specifically referred to OSA in Better Buying Power 2.0 (<nowiki>http://bbp.dau.mil</nowiki>). The initiative to Promote Effective Competition calls for enforcing increased use of OSA across the Department of Defense.

|-

|

|-

|'''Point Of Contact'''Office of Corporate Communication (SEA 00D)

Naval Sea Systems Command

Washington, D.C. 20376

|}

|}

{{Multiple issues|

{{unreferenced|date=March 2009}}

{{notability|date=March 2009}}

{{context|date=June 2018}}}}

'''Open systems architecture''' is a system design approach which aims to produce [[system]]s that are inherently interoperable and connectable without recourse to retrofit and redesign.{{Sfnp|Sage|1992|p=168}}

'''Open systems architecture''', in [[telecommunication]], is a standard that describes the layered hierarchical structure, [[computer configuration|configuration]], or model of a [[information transfer|communications]] or distributed [[data processing]] [[system]] that:

* Enables system description, design, development, installation, operation, improvement, and [[repair and maintenance|maintenance]] to be performed at a given [[Abstraction layer|layer]] or layers in the hierarchical structure

* Allows each layer to provide a set<!--non-technical use, don't link--> of accessible functions that can be controlled and used by the functions in the layer above it

* Enables each layer to be implemented without affecting the implementation of other layers

* Allows the alteration of system performance by the modification of one or more layers without altering the existing equipment, procedures, and protocols at the remaining layers

==Concept==

Open systems architecture may be implemented using the [[OSI Model]] as a guide while designing the [[system]] to meet performance requirements.

[[Systems design]] is a process of defining and engineering the architecture, methods, and interfaces necessary to accomplish a goal or fulfill a set of requirements. In open systems architecture, the design includes intentional provisions to make it possible to expand or modify the system at a later stage after initial operation. There is no one specific universal OSA, but it is essential the specific OSA applicable to a system is rigorously defined and documented.{{Sfnp|Sage|1992|pp=168–169}} For example, in information technology and telecommunication, such design principles lead to [[open system (computing)|open systems]].

==Telecommunications==

== Examples of independent alterations ==

In [[telecommunications]], open systems architecture (OSA) is a standard that describes the layered hierarchical structure, [[computer configuration|configuration]], or model of a [[information transfer|communications]] or distributed [[data processing]] [[system]]. It enables system description, design, development, installation, operation, improvement, and [[repair and maintenance|maintenance]] to be performed at the [[abstraction layer]]s in the hierarchical structure. Each layer provides a set of accessible functions that can be controlled and used by the functions in the layer above it. Each layer can be implemented without affecting the implementation of other layers. The alteration of system performance by the modification of one or more layers may be accomplished without altering the existing equipment, procedures, and protocols at the remaining layers.{{Sfnp|General Services Administration|1991}}

* Converting from wire to optical fibers at a [[physical layer]] without affecting the [[data link layer]] or the [[network layer]] except to provide more [[throughput|traffic capacity]]

* Altering the operational protocols at the [[telecommunications network|network]] level without altering the physical layer

*Examples Convertingof independent alterations include the conversion from wire to optical fibersfiber at a [[physical layer]] without affecting the [[data link layer]] or the [[network layer]], except to provide more [[throughput|traffic capacity]], and the altering of the operational protocols at the [[telecommunications network|network]] level without altering the physical layer.{{Sfnp|General Services Administration|1991}}

== See also ==

*[[Hardware Open Systems Technologies]]

*[[Architecture of Interoperable Information Systems]]

*[[Architectural pattern]]

*[[Enterprise architecture]]

*[[OSI model]]

*[[Open-system environment reference model]]

==References==

*{{FS1037CReflist}}

===Sources===

* {{Cite web|author=General Services Administration|date=1991|title=Federal Standard 1037C

|url=https://www.its.bldrdoc.gov/fs-1037/fs-1037c.htm|website=Institute for Communication Science}}

* {{Cite report|last1=Guertin|first1=Nickolas|last2=Hurt|first2=Thomas|date=1 October 2013

|title=DTIC ADA608725: DoD Open Systems Architecture Contract Guidebook for Program Managers: A Tool for Effective Competition

|publisher=Defense Technical Information Center|url=https://archive.org/details/DTIC_ADA608725}}

* {{Cite book|last=Sage|first=Andrew P.|date=1992|title=Systems Engineering

|publisher=Wiley-interscience|___location=New York|isbn=0471536393|oclc=473169047}}

{{FS1037C}}

[[Category:Telecommunications standards]]

[[Category:Systems architecture]]

{{tech-stub}}