Fact-checked by Grok 2 weeks ago

Open systems architecture

Open systems architecture (OSA) is a design for complex systems that leverages consensus-based open standards to foster modularity, , and high among components, allowing for the seamless of elements from multiple vendors. This approach emphasizes the publication of key interfaces and design disclosures to enable competition, rapid technology insertion, and cost-effective system upgrades throughout the lifecycle. In essence, OSA promotes the use of (COTS) products and standardized interfaces to avoid proprietary lock-in, making systems more adaptable to evolving requirements. The origins of OSA trace back to the mid-1990s in the U.S. (), where a 1994 directive from the Under Secretary of Defense for Acquisition, Technology, and Logistics mandated the use of open systems specifications and standards in weapon systems acquisition to combat rising costs and integration challenges. This led to the establishment of the Open Systems Joint Task Force (OSJTF) to oversee implementation across programs. By 2003, Directive 5000.1 further reinforced the adoption of a modular open systems approach (MOSA) where feasible, evolving OSA into a structured strategy for defense acquisitions. The concept gained statutory backing in the 2017 , which required MOSA for major defense acquisition programs to ensure affordability and adaptability. At its core, OSA is guided by principles such as , where systems are composed of severable, replaceable components connected via well-defined, standards-based interfaces. This allows individual modules to be developed, tested, and upgraded independently, while maintaining overall system cohesion and . Key benefits include significant cost savings through competition among suppliers, accelerated technology refresh cycles, enhanced mission integration across platforms, and improved sustainment by mitigating risks. For instance, MOSA as the DoD's of OSA supports an open that encourages and , ultimately reducing lifecycle expenses and enabling faster deployment of innovations. OSA finds primary application in and domains, particularly through initiatives like MOSA, which is mandated for major programs under Title 10 U.S.C. § 4401. Notable examples include the Navy's Acoustics-Rapid COTS Insertion initiative in the , which demonstrated multi-vendor integration for submarine systems, and the more recent Future Airborne Capability Environment (FACE) , involving over 80 companies to standardize . Domain-specific standards such as Sensor Open Systems Architecture (SOSA) for systems and Weapon Open System Architecture (WOSA) further exemplify OSA's role in promoting plug-and-play modularity in sensors, weapons, and command systems. Beyond defense, OSA principles influence commercial sectors like via standards such as , underscoring its broader utility in achieving scalable, evolvable systems of systems.

Fundamentals

Definition

Open systems architecture (OSA) is a approach for developing systems that are modular, , and based on publicly available standards, interfaces, and specifications, allowing components from diverse vendors to integrate seamlessly without reliance on technologies. This methodology emphasizes the creation of systems composed of loosely coupled modules, where internal implementations are hidden behind well-defined, open interfaces that conform to consensus-based standards, ensuring verifiable and reducing dependency on single suppliers. Core attributes of OSA include , which enables the decomposition of complex systems into cohesive, independent components that can be developed, tested, and upgraded separately; , facilitating growth and adaptation through standardized expansion points; and vendor neutrality, promoting competition among providers by avoiding lock-in to specific solutions. Key terms in this context encompass "loosely coupled modules," referring to components that interact via minimal, well-specified dependencies; "open interfaces," which are publicly documented and adhere to industry-wide protocols; and "conformance to public standards," ensuring that interfaces meet established, accessible specifications for broad compatibility. In contrast to closed systems architecture, which relies on proprietary hardware, software, or interfaces that restrict integration to approved vendors—such as a fully integrated, vendor-specific ecosystem like early mainframe computers—OSA prioritizes standardized interfaces that allow plug-and-play functionality across heterogeneous components, exemplified by the use of common protocols in personal computing hardware versus bespoke, non-interoperable designs.

Core Principles

Open systems architecture (OSA) is fundamentally guided by the principle of modularity, which emphasizes designing systems as collections of independent, replaceable modules connected through well-defined interfaces. This approach ensures that each module is cohesive, encapsulated, and self-contained, allowing for the isolation of internal complexities while enabling easy substitution or upgrades without disrupting the overall system. A core tenet is , achieved by employing standardized protocols and application programming interfaces () that facilitate seamless of components from multiple vendors. These standards, often consensus-based and widely supported, promote net-centric operations and system-of-systems by decoupling dependencies and ensuring compatibility across diverse hardware and software elements. Layered architecture forms another essential principle, involving the separation of system concerns into distinct abstraction layers—such as , , , and —to enable independent evolution and maintenance. Key interfaces between layers are designated as open and stable, while non-key interfaces allow flexibility for , thereby supporting and reducing the risk of . Open documentation is a mandatory requirement, mandating that specifications, interfaces, and standards be publicly available without restrictive barriers. This transparency, often aligned with registries like the Standards Registry, fosters competition, reuse, and broad adoption by providing clear, accessible guidelines for developers and integrators. Finally, and extensibility serve as design imperatives, ensuring that new components can integrate with legacy elements while allowing for future enhancements. permits the addition, removal, or replacement of modules throughout the system lifecycle without major rework, whereas extensibility supports incremental development and technology insertion through modular, open interfaces. These principles are exemplified in defense applications, such as the Modular Open Systems Approach (MOSA), where they enable adaptable military systems.

Historical Development

Origins in Computing and IT

The concept of open systems architecture in computing and information technology emerged prominently in the 1970s through the development of the Unix operating system at Bell Laboratories, which emphasized and portability to enable software to run across diverse hardware platforms. Unix, initially created in 1969 by and later rewritten in by 1973, facilitated this portability by separating from specific hardware dependencies, allowing implementations on various minicomputers like the and later systems. By the mid-1970s, Unix's distribution under AT&T's licensing model further promoted collaborative development and among academic and research institutions, laying groundwork for open standards. In the , this foundation evolved with the (Portable Operating System Interface) standards, which formalized interfaces to ensure across different vendor implementations. Developed through efforts by the IEEE and adopted as IEEE 1003.1 in 1988, provided a common baseline for operating system services, including file systems, processes, and networking, reducing and enabling cross-platform application development. These standards addressed the fragmentation caused by proprietary Unix variants from companies like and , fostering an ecosystem where applications could operate seamlessly on heterogeneous hardware. Parallel to these developments, the and early protocols served as key precursors to open systems by demonstrating network-agnostic communication. Launched in 1969 by the U.S. Department of Defense, introduced packet-switching to connect disparate computers, evolving into a broader network with the adoption of TCP/IP in 1983, which standardized data transmission across multiple linked networks without proprietary constraints. TCP/IP's connectionless datagram model, designed by and , enabled transparent among heterogeneous systems, influencing later principles by prioritizing practical, vendor-neutral protocols over rigid standards like the . By the 1990s, industry consortia such as The Open Group accelerated the standardization of IT interfaces, building on Unix and to promote widespread adoption of open systems. Formed in 1996 through the merger of X/Open Company and the , The Open Group published the , which extended with additional APIs for networking and graphical interfaces, certifying compliant products from major vendors to ensure consistent IT environments. This effort standardized core system interfaces, enabling modular software integration and reducing dependency on single vendors in enterprise computing. A pivotal event in formalizing open systems architecture within U.S. government IT contexts was the publication of Federal Standard 1037C in 1996, which included glossary definitions supporting open systems concepts like abstract syntax notation for interoperable protocols. Issued by the (NTIA), the standard provided a comprehensive reference for terms, including those related to open systems interconnection and architecture, to guide federal procurement and system design toward non-proprietary solutions. This period also marked a broader shift in computing from proprietary mainframe systems, exemplified by IBM's dominance in the 1960s and 1970s, to open standards in personal computing. IBM's System/360 family in 1964 introduced compatibility across its lineup but remained largely , while the 1981 launch of the Personal Computer (PC) adopted an with off-the-shelf components and specifications that competitors could reverse-engineer, spurring the rise of compatible clones and industry standards. This transition democratized access to power, emphasizing interchangeable and software interfaces over closed ecosystems.

Evolution in Defense and Aerospace

Following the end of the , the U.S. Department of Defense () sought to address escalating acquisition costs and over-reliance on proprietary vendor systems by mandating open systems architectures in defense programs. In November 1994, the Under Secretary of Defense for Acquisition and Technology established the Open Systems Joint Task Force (OSJTF) to sponsor and accelerate the adoption of open systems in weapon systems electronics. In 1996, Directive 5000.1 established policy for the Defense Acquisition System, explicitly requiring an open systems approach for all system elements—including mechanical, electrical, and software components—in new developments to the maximum extent feasible, aiming to enhance competition, reduce lifecycle costs, and mitigate . This directive marked a pivotal shift toward and in military systems, driven by budgetary pressures and the need for more agile acquisition processes in a post- environment. Concurrently, the Clinger-Cohen Act of 1996 played a key role in facilitating the transition of federal practices to defense applications, emphasizing improved management of IT investments across government agencies, including the . The act required agencies to adopt performance-based acquisition strategies and capital planning for IT, which influenced efforts to integrate commercial open standards into defense IT systems, bridging civilian and military architectures to accelerate innovation and cost efficiencies. Building on these foundations, the formalized the Modular Open Systems Approach (MOSA) in 2004 as an integrated business and technical strategy for weapon systems development. MOSA emphasized designing systems with modular, loosely coupled components that leverage open standards and non-proprietary interfaces, enabling incremental upgrades, competition among suppliers, and easier technology insertion without full system redesigns. This approach was detailed in the DoD's Program Manager's Guide to Open Systems, which provided practical guidance for implementing modularity in acquisitions to lower ownership costs and enhance system adaptability. The concept received statutory support in the for 2017 (NDAA), which required the use of MOSA for major defense acquisition programs to ensure affordability and adaptability. A notable illustration of this evolution is the transition from closed, federated architectures in legacy aircraft like the F-15 Eagle, which relied on proprietary, tightly integrated subsystems limiting upgrades, to the open architecture in the F-35 Joint Strike Fighter. The F-35's design incorporates MOSA principles through a common open mission systems framework, allowing for separable modules, standardized interfaces, and rapid integration of new capabilities such as sensors and software updates, thereby supporting multirole operations across air, ground, and naval domains. Internationally, adoption advanced with the establishment of the Future Airborne Capability Environment (FACE) standard by The Open Group in 2010, targeting portability and reuse across military platforms. FACE defines a layered for software components, including portable components, conformance profiles, and operating environments, to promote vendor-neutral development and reduce integration costs in airborne systems for U.S. and allied forces. Further specialization occurred in 2017 with the formation of the Sensor Open Systems Architecture (SOSA) Consortium under The Open Group, focusing on open standards for ground-based systems in defense applications. SOSA builds on MOSA by specifying , software, and requirements for modular processing, enabling among , electro-optical, and systems while facilitating competition and swift technology refreshes. As of 2025, MOSA continues to evolve with updated guidance, including the DoD's MOSA Guidebook released in February 2025, and recent Tri-Service directives reinforcing its application across acquisition programs.

Applications

Military and Aerospace Systems

In military and aerospace systems, the Modular Open Systems Approach (MOSA) has been implemented in U.S. programs such as the (FVL) and the modernization of helicopter platforms like the UH-60V, enabling interchangeability through standardized interfaces and modular components. This approach supports the 's Program Executive Office for Aviation strategy, allowing for scalable integration of sensors and mission systems across rotorcraft ecosystems. The Sensor Open Systems Architecture (SOSA) provides standardized hardware modules for and (EW) systems, facilitating rapid sensor swaps and in defense platforms. SOSA defines plug-in cards and interfaces that unify architectures for modalities including , EW, and , reducing times for multi-channel systems. Similarly, Open Mission Systems (OMS) enables in unmanned aerial vehicles (UAVs), as demonstrated in Northrop Grumman's flights on the Global Hawk, where OMS-compliant interfaces allowed ground operators to command payloads via communications. In naval applications, open systems architecture underpins the Zumwalt-class destroyers' Total Ship Computing Environment Infrastructure (TSCEI), which uses standardized, open hardware and software for distributed management of combat and command s. This supports across ship subsystems, including the Mk 57 vertical launch . Within Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance () s, MOSA promotes continuous upgrades and , such as through the Vehicular for (VICTORY) architecture, which standardizes data exchange for EW and . In the 2020s, the Department of Defense has emphasized and integration via open APIs in programs like (JADC2), leveraging MOSA to connect sensors across domains for accelerated decision-making. For example, in February 2024, the DoD announced the delivery of the initial CJADC2 minimum viable capability, advancing MOSA-based multi-domain operations. employs modular open architectures to incorporate / for from diverse sources, enhancing multi-domain operations while adhering to directives on open standards.

Telecommunications

In telecommunications, open systems architecture (OSA) is fundamentally structured around hierarchical layering, adapting the Open Systems Interconnection (OSI) model's seven layers—physical, data link, network, transport, session, presentation, and application—to enable modular, interoperable network designs. This layered approach, formalized in ITU-T Recommendation X.200, allows independent evolution of each layer, ensuring that changes in one do not necessitate overhauls across the entire system. The OSI framework, originally developed in the late 1970s and adopted by ITU-T (then CCITT) in the 1980s through recommendations like X.200 (first published in 1984), provided the basis for open telecom architectures by standardizing interfaces for global interconnection of diverse equipment from multiple vendors. This modularity has been central to telecom infrastructure since the 1980s, promoting vendor neutrality and scalability in evolving networks. A key example of OSA's application is the transition from copper-based to fiber-optic physical layers without requiring system-wide redesigns, as higher OSI layers (e.g., network and application) remain unaffected by underlying changes. In passive optical networks (PON), fiber deployment upgrades bandwidth in the while preserving compatibility with existing protocols in upper layers, facilitating evolution for telecom operators. Similarly, 5G networks leverage open RAN standards, where the O-RAN Alliance—founded in 2018 by major operators—defines disaggregated base stations with open interfaces between radio units, distributed units, and central units, enabling multi-vendor integration based on specifications. Open interfaces further exemplify OSA in telecom through migrations like SS7 (Signaling System No. 7) to (Session Initiation Protocol), where legacy circuit-switched signaling transitions to IP-based systems without disrupting service continuity. SS7, standardized by in the 1980s, has been interworked with —defined in IETF RFC 3261 (2002)—via gateways that map signaling functions, supporting the shift to next-generation networks (NGN). Virtualization via (NFV), initiated by in 2012, decouples network functions (e.g., firewalls, routers) from proprietary hardware onto standard servers, fostering open, software-based architectures that enhance interoperability in multi-vendor environments. These principles yield significant maintenance benefits, such as isolated upgrades in specific layers; for instance, (SDN) allows centralized control of the network layer via programmable interfaces like , enabling rapid reconfiguration without impacting physical or application layers. SDN, promoted by the Open Networking Foundation since 2011, has been widely adopted in telecom for dynamic resource allocation in cores, reducing operational complexity while maintaining openness. Overall, OSA in telecommunications ensures resilient, evolvable infrastructures that support global connectivity demands.

Information Technology

In , open systems architecture (OSA) emphasizes the use of standardized interfaces and protocols to enable seamless across heterogeneous environments, allowing organizations to mix components from various vendors without constraints. This approach promotes and in systems, particularly in where hybrid multi-vendor setups are common. For instance, platforms like (AWS) and provide open APIs that support , enabling data and application portability between clouds. AWS's multicloud tooling, including services like AWS Outposts and AWS Wavelength, facilitates the extension of AWS infrastructure to on-premises and edge locations while integrating with other providers, thus avoiding in hybrid environments. Similarly, Azure's architecture supports cross-cloud workflows through open standards, allowing enterprises to orchestrate resources across AWS and Azure for enhanced flexibility and resilience. In software ecosystems, OSA is realized through architectures combined with technologies such as and , which decouple applications into independent, portable services. Docker containers package with their dependencies, ensuring consistency across development, testing, and production environments regardless of the underlying infrastructure. , as an open-source orchestration platform, automates the deployment, scaling, and management of these containers, fostering vendor-neutral ecosystems where services from different providers can interoperate via standardized . This setup aligns with OSA principles by enabling rapid iteration and integration in distributed systems, as seen in .NET applications where supports resilient, loosely coupled architectures. Data management under OSA relies on open formats and standards to ensure among databases and storage systems. SQL, as an ANSI/ISO standard, defines a common language for querying and manipulating relational data, allowing databases from vendors like , , and to exchange information without custom adapters. This standardization facilitates and integration in enterprise IT, where disparate systems must share structured data for and . By adhering to SQL standards, organizations achieve greater flexibility in migrating or federating data across platforms, reducing the costs associated with proprietary lock-in. Modern trends in IT further exemplify OSA through and (IoT) integrations, as well as practices. In , the protocol—an open standard—enables lightweight, publish-subscribe messaging for devices, allowing real-time data exchange between sensors, gateways, and cloud services in resource-constrained environments. MQTT's broker-based architecture supports scalable device integration across vendors, processing data closer to the source to minimize latency in applications like industrial monitoring. Complementing this, methodologies incorporate continuous integration/continuous delivery () pipelines to automate software lifecycles, using open tools like Jenkins or CI to standardize builds and deployments across multi-vendor stacks. These pipelines ensure consistent, reproducible processes that enhance in dynamic IT landscapes. A notable case of OSA in practice is the adoption of Linux-based systems in server environments, which leverage compliance to replace proprietary operating systems. , an IEEE standard defining portable interfaces for systems, ensures that distributions such as and support consistent application behavior across hardware and vendors. This compliance allows enterprises to transition from closed systems like those from or to open alternatives, achieving cost savings and broader hardware compatibility in data centers. For example, 's specifications for file systems, processes, and threading enable seamless of legacy applications to servers, supporting scalable IT infrastructures.

Advantages and Challenges

Benefits

Open systems architecture (OSA) offers substantial practical advantages across various domains by promoting modularity, interoperability, and openness in system design. These benefits stem from the ability to integrate components from multiple vendors using standardized interfaces, which contrasts with proprietary closed systems that limit adaptability. As outlined in Department of Defense (DoD) guidance, OSA facilitates cost-effective development and maintenance while enhancing overall system resilience and evolution. One primary benefit is , achieved through increased among suppliers and the reuse of existing modules and components throughout the acquisition lifecycle. By avoiding proprietary dependencies, OSA lowers both initial acquisition costs and long-term sustainment expenses, with strategies emphasizing significant savings via open and technology insertion. For instance, the Modular Open Systems Approach (MOSA), a implementation of OSA principles, promotes cost avoidance by enabling the of severable modules from diverse sources, reducing overall program expenditures. Flexibility and upgradeability represent another key advantage, allowing systems to incorporate new technologies rapidly without necessitating complete overhauls. This is enabled by loosely coupled modules that can be swapped or updated incrementally, supporting reconfiguration to meet evolving requirements. reports highlight how such designs facilitate technology refresh cycles, ensuring operational adaptability without disrupting core system functionality. OSA also mitigates risks associated with and disruptions by diversifying sourcing options and standardizing interfaces. This open distributes dependency across multiple providers, reducing the vulnerability to single-vendor failures or monopolistic pricing. According to acquisition strategies, this approach maximizes asset reuse and shares development risks, thereby enhancing system reliability over time. Furthermore, OSA accelerates innovation by fostering collaboration through open standards, which encourage broader participation from and . Competitive modular designs invite diverse contributions, speeding up the of cutting-edge technologies and improving overall system performance. DoD initiatives underscore this by promoting MOSA to drive innovation in defense systems via accessible interfaces and shared architectures. Finally, OSA extends system lifecycles by enabling seamless of components with modern upgrades, allowing platforms to remain viable for decades. This adaptability supports sustained operations and incremental modernization, as evidenced in sustainment strategies that leverage OSA for long-term affordability and relevance.

Limitations

Despite adherence to open standards, achieving true in open systems architecture (OSA) often encounters significant challenges, such as inconsistencies in implementations across vendors, which necessitate custom adapters or emulation software to bridge gaps. For instance, variations in component behaviors in (COTS) products can lead to compatibility issues requiring additional , complicating system assembly. These issues are exacerbated in complex environments like defense systems, where modifying COTS components risks and recertification, potentially delaying deployment. Open interfaces in OSA designs heighten risks by increasing the through greater interconnectivity, allowing potential cyber threats to exploit standardized access points that were intended for . Unclear or evolving cybersecurity requirements across stages further compound vulnerabilities, as open architectures may lack formalized "security licenses" to enforce protections consistently. In applications, this connectivity can enable intruders to target shared interfaces, underscoring the need for robust strategies beyond mere standards . The initial development overhead for OSA is substantial, involving higher upfront costs for , extensive documentation, and management of rights, which can strain resources compared to approaches. Heterogeneous software licenses in open-source components, with dozens of variants complicating legal , add to this burden, often requiring dedicated processes for build, release, and deployment . Sustainment accounts for 60-70% of lifecycle costs, and while supports long-term vendor neutrality, the immediate in curation and baseline management can increase these expenses if not planned effectively. Performance trade-offs in OSA arise from loosely coupled components, where standardized abstractions and interfaces introduce latency unsuitable for real-time applications, unlike the optimized integrations in closed systems. For example, in supervisory control and systems, open protocols may lack guaranteed message delivery in high-volume scenarios, impacting low-latency responses. High transaction volumes in relational databases integrated via open architectures often necessitate costly memory-resident alternatives to maintain performance. Adoption barriers to OSA include resistance from legacy vendors protective of proprietary ecosystems and the shortage of skilled personnel versed in standards compliance, slowing marketplace availability of compatible products. Competing standards and evolving business models, such as subscription-based licensing for open components, create uncertainty and increase intellectual property negotiation hurdles. In defense sectors, these factors demand strategic alignment between government and industry to overcome data rights risks, further impeding widespread implementation. As of 2025, a U.S. Government Accountability Office report highlighted DoD's insufficient planning and metrics for MOSA, which could undermine anticipated benefits like cost savings and faster upgrades if not addressed.

Standards and Implementations

Key Standards

Open systems architecture relies on a set of foundational and domain-specific standards that promote , , and portability across diverse systems. These standards define interfaces, frameworks, and reference models essential for integrating components from multiple vendors while ensuring long-term and reduced . The X.200 recommendation establishes the basic reference model for Open Systems Interconnection (OSI), providing a for network functions to enable communication between diverse systems through standardized protocols. This model divides system interactions into seven layers, from physical transmission to application services, serving as a cornerstone for open networking architectures. Complementing this, ISO/IEC/IEEE 42010 specifies requirements for architecture descriptions in systems and , outlining how to create, analyze, and sustain architectural views using frameworks, viewpoints, and models. It emphasizes the use of architecture description languages and viewpoints to represent concerns, facilitating the documentation and evolution of open systems. In , the (Portable Operating System Interface) standard, defined by IEEE Std 1003.1, establishes a common , , and utilities for operating systems to ensure across compliant platforms. Adopted widely since its initial 1988 publication, POSIX supports open systems by standardizing system calls for processes, files, and I/O, enabling applications to run without modification on diverse environments. For defense applications, the Modular Open Systems Approach (MOSA), mandated by the U.S. of , is an integrated business and technical strategy that promotes modular designs with well-defined open interfaces to enhance competition, affordability, and upgradeability in weapon systems. MOSA requires programs to identify and implement open standards for hardware and software modules, reducing lifecycle costs through non-proprietary integrations. Building on MOSA, the Sensor Open Systems Architecture (SOSA) Technical Standard 1.0, developed by The Open Group, provides a modular framework for sensor systems in and , specifying open interfaces for hardware like OpenVPX slots and profiles to enable rapid technology insertion and . SOSA aligns with standards for form factors, ensuring sensor components from different vendors can integrate seamlessly in platforms such as and unmanned systems. In , the Future Airborne Capability Environment (FACE) standard, also from The Open Group, defines a technical and business approach for portable software components in , segmenting applications into portable components, operating system layers, and data models to foster reuse and reduce integration costs. FACE Edition 3.2, released in 2023, refines safety-critical profiles and conformance testing to support open avionics environments across platforms. In , the O-RAN (Open ) specifications, developed by the O-RAN Alliance and aligned with standards, introduce open interfaces such as the O2 interface for service management and the E2 interface for near-real-time control, disaggregating RAN functions to allow multi-vendor deployments in networks. These interfaces promote flexibility by enabling intelligent RAN controllers and virtualized components, with over 100 specifications published to date for enhanced network scalability.

Notable Examples

The F-35 Lightning II exemplifies open systems architecture in defense applications, where the U.S. Department of Defense () implemented an open mission systems framework starting in the 2000s to facilitate modular upgrades. This architecture enables software enhancements and capability insertions without requiring full hardware overhauls, as demonstrated by the Tech Refresh-3 (TR-3) upgrade introduced in 2024, which integrates open mission systems to support Block 4 enhancements like advanced and capabilities. In , Open (Open RAN) deployments by major U.S. carriers illustrate the disaggregation of hardware and software components to promote vendor and innovation. has deployed over 170,000 Open RAN radios across more than 22,900 sites by early 2025, enabling scalable coverage through multi-vendor integration in commercial networks. Similarly, AT&T achieved a milestone in October 2025 with the first live Open RAN call using third-party radios on its production Standalone (SA) network, part of a broader $14 billion with , announced in 2023, to transition from proprietary systems to open architectures. Kubernetes, an open-source container orchestration platform originally developed by , represents a landmark in enterprise for managing distributed systems at scale. By 2023, it had been adopted by 71% of Fortune 100 companies as the primary tool for automating deployment, scaling, and operations of containerized applications, a trend that continued into 2025 with widespread use in cloud-native environments to enhance portability and efficiency across hybrid infrastructures. The European Space Agency's (ESA) OPS-SAT mission showcases open systems architecture in through a compact, reconfigurable platform launched on December 18, 2019, designed for in-orbit software experimentation. OPS-SAT features a modular NanoSat MO Framework for orchestrating open-source applications, allowing third-party developers to test AI-driven and satellite control techniques rapidly without proprietary constraints, thereby accelerating innovation in space operations. IBM's strategic pivot to -based servers in the early overcame challenges by embracing open-source operating systems on its portfolio, including mainframes. This shift, formalized in 2000 with broad support across server lines, enabled customers to achieve substantial cost reductions, such as up to 50% through discounted bundles and avoidance of proprietary licensing fees in the , while maintaining capabilities.

References

  1. [1]
    Open Systems Architecture | www.dau.edu
    A characteristic of a system which uses a technical architecture that adopts consensus based standards supporting a modular, loosely coupled, and highly ...
  2. [2]
    Architecting Approaches for Systems of Systems - SEBoK
    May 23, 2025 · Open Systems Architecture (OSA). Open Systems Architectures is a particular approach to standards that seeks to enable commercial ...
  3. [3]
    Open System Architectures: When and Where to be Closed
    Oct 19, 2015 · By definition, an OSA is any system (or software) architecture that exhibits the following three beneficial characteristics: It is modular ...
  4. [4]
    A Naval Perspective on Open-Systems Architecture
    Jul 11, 2016 · Guertin has a long history with open systems, both for U.S. Navy OSA initiatives and broader DoD initiatives. Based on his experiences over ...
  5. [5]
    Perspective: The MOSA Approach in Defense Acquisition
    Feb 1, 2004 · The latest DoD Directive 5000.1, dated May 12, 2003, requires that A modular, open systems approach shall be employed, where feasible. MOSA ...
  6. [6]
    [PDF] Modular Open Systems Approach - incose
    Jul 1, 2020 · The main driver for MOSA adoption in new acquisitions stems from the congressional mandate within the 2017 National Defense Authorization Act to ...
  7. [7]
    Modular Open Systems Approach
    A Modular Open Systems Approach (MOSA) is an integrated business and technical strategy to achieve competitive and affordable acquisition and sustainment ...
  8. [8]
    DSP :: MOSA - Defense Standardization Program
    What is MOSA. A Modular Open Systems Approach (MOSA) can be defined as a technical and business strategy for designing an affordable and adaptable system.
  9. [9]
    Government Reference Architectures - DTO Digital Guide
    Dec 18, 2022 · Sensor Open Systems Architecture (SOSA). Owning Organization: The Open Group; AF Contact Information: aflcmc.xz.oamo@us.afmil. Scalable Payload ...<|control11|><|separator|>
  10. [10]
    [PDF] TCP/IP V4 Networking Fundamentals - OSTI.GOV
    Nov 8, 2009 · Open System Interconnection Model (OSI). • 1980, ISO developed a network reference model to help vendors create interoperability. • Used 7 ...<|control11|><|separator|>
  11. [11]
    Modular Open Systems Approach (MOSA) - AcqNotes
    May 12, 2023 · An open system is a system that employs modular design tenets, uses widely supported and consensus-based standards for its key Interfaces, and ...
  12. [12]
    [PDF] mosa-pocket-guide.pdf
    Mar 29, 2022 · The PEO Aviation EA is the highest level governing principles to implement MOSA while designing, developing, and fielding of open systems. The ...<|control11|><|separator|>
  13. [13]
    http://www.catb.org/esr/writings/taoup/html/ch02s01.html
  14. [14]
    Origins and History of Unix, 1969-1995 - catb. Org
    The original Unix was a third system. Its grandfather was the small and simple Compatible Time-Sharing System (CTSS), either the first or second timesharing ...
  15. [15]
    The UNIX System -- History and Timeline
    UNIX began in 1969 at Bell Labs, was rewritten in C in 1973, and became widely available in 1975. It was first publicly released in 1982.
  16. [16]
    POSIX.1 Backgrounder - The Open Group
    By standardizing an interface like one in an historical implementation; for example, directories. By specifying an interface that is readily implementable in ...
  17. [17]
    The Base Specifications Issue 7
    The adoption of the 1988 and 1990 IEEE system interface standards, the 1992 IEEE shell and utilities standard, the various Open Group (formerly X/Open) ...
  18. [18]
    Transcending POSIX: The End of an Era? - USENIX
    Sep 8, 2022 · Unix was the first operating system written by programmers for programmers, and POSIX enables developers to write portable applications that run ...Missing: origins | Show results with:origins
  19. [19]
    A Brief History of the Internet & Related Networks
    The objective was to develop communication protocols which would allow networked computers to communicate transparently across multiple, linked packet networks.Missing: interoperability | Show results with:interoperability
  20. [20]
    OSI: The Internet That Wasn't - IEEE Spectrum
    Jul 29, 2013 · How TCP/IP eclipsed the Open Systems Interconnection standards to become the global protocol for computer networking.
  21. [21]
    The UNIX® Standard | www.opengroup.org
    To address this, vendors and users joined together in the 1980s to create the POSIX® standard and later the Single UNIX Specification.
  22. [22]
    [PDF] Technical Standard System Interfaces and Headers Issue 5
    Published in the U.K. by The Open Group, February 1997. Any comments relating to the material contained in this document may be submitted to: The Open Group.Missing: standardizing | Show results with:standardizing
  23. [23]
    [PDF] Ex.-1008-Federal-Standard-1037C-2.pdf - Dr. Tal Lavian
    Aug 7, 1996 · This document provides Federal departments and agencies a comprehensive source of definitions of terms used in telecommunications and directly ...
  24. [24]
    Federal Standard 1037C - ITS
    ITS was tasked to update the standard to revision C and published Federal Standard 1037C in 1996. Federal Standard 1037C was superseded in 2001 by American ...
  25. [25]
    Timeline of Computer History
    IBM´s 7000 series of mainframe computers are the company´s first to use transistors. At the top of the line was the Model 7030, also known as "Stretch." Nine of ...Missing: shift | Show results with:shift
  26. [26]
    How the IBM PC Won, Then Lost, the Personal Computer Market
    Jul 21, 2021 · Rivals figured out that IBM had set the de facto technical standards for PCs, so they developed compatible versions they could bring to market ...Missing: shift open
  27. [27]
    [PDF] DODD 5000.1 DoD 5000.2-R - DTIC
    Mar 15, 1996 · 4.3.4 Open Systems Design. An open systems approach shall be followed for all system elements (mechanical, electrical, software, etc.) in ...
  28. [28]
    [PDF] The Clinger Cohen Act of 1996 - DoD CIO
    To enforce accountability for IRM and IT investments, OMB may (1) influence IRM budgets, (2) use administrative controls to restrict agency funds, and (3) ...
  29. [29]
    [PDF] A 21st-century Concept of Air and Military Operations
    Jul 23, 2008 · 13 The F–35's open architecture allows this fly- ing combat system to become the focal point of three core activities: air-to-air, air-to ...<|separator|>
  30. [30]
    Sensor Open Systems Architecture™ / SOSA® Consortium
    It defines architectural modules (containing functions and behaviors) with defined open interfaces, enabling the development of capabilities made up of common ...Events · Join · Members · Published Documents
  31. [31]
    PEO Aviation's Modular Open Systems Approach | Article - Army.mil
    Jun 3, 2024 · Modular Open Systems Approach (MOSA) is an important element of the PEO Aviation strategy and extends into all of our Project Offices.
  32. [32]
    Future Vertical Lift - Aircraft - Northrop Grumman
    At its core is a Modular Open Systems Approach (MOSA) architecture. The Army is flying Northrop Grumman's MOSA today on its UH-60V helicopter. illustration ...
  33. [33]
    Leveraging the Sensor Open Systems Architecture (SOSA) for radar ...
    Feb 11, 2022 · The SOSA Technical Standard is targeting five sensor modalities: electro-optical/infrared (EO/IR), electronic warfare (EW), radar, and signals intelligence ( ...
  34. [34]
    Sensor Open Systems Architecture (SOSA) – Taking EW Systems to ...
    Oct 20, 2021 · The SOSA Reference Architecture facilitates these objectives by providing a definition of SOSA modules, hardware elements (for example, plug-in ...
  35. [35]
    Northrop Grumman Successfully Flies Open Mission Systems ...
    Jun 17, 2015 · This flight confirmed the ability for ground operators to send OMS payload commands and receive OMS subsystem status responses over a Ku SATCOM ...
  36. [36]
    DDG 1000 Zumwalt-class Guided Missile Destroyers, US
    Jun 25, 2024 · The combat system is based on the total ship computing environment, utilising open architecture, standardised software and commercial-off-the- ...
  37. [37]
    Naval Systems: Zumwalt's Get 'Any Role, Any Station' Control
    ... Open Architecture initiative. The environment will permit highly distributed management and monitoring of all ship systems, including combat, command and ...
  38. [38]
    Modular Open System Architecture allows continuous weapon ...
    Nov 28, 2023 · With MOSA, the Pentagon can incrementally and continually upgrade weapons systems at the pace of technological advancement.
  39. [39]
    [PDF] Summary of the Joint All-Domain Command and Control Strategy
    Mar 17, 2022 · JADC2 developed capabilities will leverage Artificial Intelligence and Machine Learning to help accelerate the commander's decision cycle ...Missing: 2020s | Show results with:2020s
  40. [40]
    Creating Truly Open Architectures Using MOSA - Booz Allen
    JADC2 demands a modular open-system approach (MOSA) that keeps up with evolving threats. Modular approaches and flexible, open-system architectures allow system ...Missing: ML integration
  41. [41]
    X.200 : Information technology - Open Systems Interconnection - Basic Reference Model: The basic model
    ### Summary of Recommendation X.200 and Its Relation to Open Systems Interconnection
  42. [42]
    [PDF] The ISO Model of Architecture for Open Systems Interconnection
    In July 1979 the specifications of this architecture, established by SC16, were passed under the name of “OSI. Reference Model” to Technical Committee 97 “Data ...Missing: history | Show results with:history
  43. [43]
    Say Goodbye to Copper Telecom Networks - Boston Consulting Group
    Oct 13, 2021 · For telecom companies, shifting to fiber-optic networks, which outpace copper ones in each of these critical areas, is inevitable.
  44. [44]
    O-RAN ALLIANCE e.V
    O-RAN ALLIANCE is Transforming Radio Access Networks towards Open, Intelligent, Virtualized and Fully Interoperable RAN.O-RAN Map · O-RAN Certification · O-RAN Ecosystem · OTICs Open Testing and...
  45. [45]
    Open RAN - 3GPP
    Jan 20, 2021 · Open RAN is made possible through standardized open network interfaces, defined in 3GPP, O-RAN Alliance, IEEE, and other SDOs and industry fora.<|control11|><|separator|>
  46. [46]
    RFC 3261: SIP: Session Initiation Protocol
    Below is a merged response summarizing RFC 3261 on SIP, consolidating all information from the provided segments into a single, comprehensive summary. To retain maximum detail and clarity, I will use a table in CSV format for structured data (e.g., sections, details, and URLs) and provide a narrative summary for overarching points. The response avoids any "thinking" tokens as per the system constraint and focuses solely on presenting the information.
  47. [47]
    Network Functions Virtualisation (NFV) - ETSI
    Founded in November 2012 by seven of the world's leading telecoms network operators, ETSI ISG NFV became the home of Network Functions Virtualisation (NFV).
  48. [48]
    Software-Defined Networking (SDN) Definition
    SDN lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write ...
  49. [49]
    Multicloud on AWS
    We deliver a depth and breadth of tooling and capabilities to help you build, migrate, and operate with greater ease and speed, wherever your workloads reside.Multicloud On Aws · Freedom To Innovate... · Customers
  50. [50]
    Azure for AWS Professionals - Azure Architecture Center
    Feb 11, 2025 · This article introduces a series of articles that help Amazon Web Services (AWS) experts understand the basics of the Microsoft Azure platform, accounts, and ...Missing: vendor | Show results with:vendor
  51. [51]
    Microservices Architecture | Atlassian
    While Docker is a container runtime, Kubernetes is a platform for running and managing containers from many container runtimes. Learn about Kubernetes and ...Kubernetes vs. Docker · How to build microservices · Microservices tools
  52. [52]
    .NET Microservices. Architecture for Containerized .NET Applications
    Mar 21, 2023 · This guide is an introduction to developing microservices-based applications and managing them using containers.Designing a microservice... · Docker container · Microsoft Ignite · Domain model
  53. [53]
    What Is Interoperability? - Oracle
    May 20, 2024 · Interoperability is achieved through adherence to standards, protocols, and technologies that permit data to flow between different systems.
  54. [54]
    Revolutionizing Edge Computing with MQTT: Benefits, Challenges ...
    Aug 13, 2024 · As a lightweight communication protocol, MQTT plays a key role in edge computing in order to address those challenges. Introduction to MQTT.
  55. [55]
    Leveraging Open Standards like MQTT to Manage Data at ... - HiveMQ
    Rating 9.1/10 (64) Oct 22, 2024 · MQTT is a lightweight messaging open standard protocol used in IoT for data movement and is designed for efficient communication between devices.
  56. [56]
    What Are CI/CD And The CI/CD Pipeline? - IBM
    The CI/CD pipeline allows DevOps teams to write code, integrate it, run tests, deliver releases and deploy changes to the software collaboratively and in real- ...
  57. [57]
    A Guide to POSIX | Baeldung on Linux
    Mar 19, 2025 · POSIX stands for Portable Operating System Interface. It's a family of standards specified by IEEE for maintaining compatibility among operating systems.
  58. [58]
    [PDF] Implementing a Modular Open Systems Approach in Department of ...
    MOSA integrates technical requirements with contracting mechanisms and legal considerations to support a more rapid evolution of technologies and capabilities ...Missing: JADC2 AI
  59. [59]
    Modular Open Systems Approach (MOSA) | www.dau.edu
    To prepare DoD for a MOSA future, OSD established the Modular Open Systems Working Group (MOSWG) and three MOSA Tiger Teams (Standards, Implementation Guidance ...
  60. [60]
    MOSA | NAVAIR
    MOSA is an integrated business and technical strategy designed to achieve competitive and affordable acquisition and sustainment over the system life cycle.Host · Oms · Navair<|control11|><|separator|>
  61. [61]
    [PDF] Benefits, problems, and issues in open systems architectures
    These challenges include increased software maintenance costs, increased capital expenditures, integration difficulties, and increased documentation and ...Missing: security | Show results with:security
  62. [62]
    [PDF] Modular Open Systems Approach - Implementation Challenges and ...
    Oct 16, 2023 · Sixty to seventy percent of a system's life cycle cost occurs in sustainment. ... (4) Innovation, and (5) Cost Avoidance/Cost Savings. Most ...
  63. [63]
    A Discussion on Open-Systems Architecture
    Nov 23, 2015 · This SEI Blog post presents highlights of a discussion on open systems architecture (OSA) approaches and their integration in DoD system ...Missing: savings | Show results with:savings
  64. [64]
    (PDF) Issues in development and maintenance of open architecture ...
    Aug 6, 2025 · This article identifies and describes six emerging issues that affect the engineering of open architecture software systems that integrate ...Missing: limitations | Show results with:limitations
  65. [65]
    X.200 : Information technology - Open Systems Interconnection - ITU
    Jul 1, 1994 · X.200 is a basic reference model for open systems interconnection in information technology, approved in 1994.
  66. [66]
    ISO/IEC/IEEE 42010:2011 - Architecture description
    ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions.
  67. [67]
    The Open Group Base Specifications Issue 7
    POSIX.1-2008 defines a standard operating system interface and environment, including a command interpreter (or “shell”), and common utility programs.
  68. [68]
    Future Airborne Capability Environment® (FACE) - The Open Group
    Jun 10, 2025 · The Open Group FACE® Consortium collaborates on developing open software standards to innovate processes and practices, and accelerate FACE adoption.Upcoming Events · Consortium Member... · Member List · FAQs
  69. [69]
    O-RAN Specifications
    O-RAN specifications are being adopted by regional standardization institutions - ATIS, ETSI, and TTA. Transposition of O-RAN specifications into regional ...
  70. [70]
    Block 4 Capabilities Sharpen the F-35's Edge - F-35 Lightning II
    Aug 1, 2024 · Tech Refresh-3 (TR-3), which enables Block 4, introduces open mission systems architecture, a new integrated core processor with greater ...Missing: II | Show results with:II
  71. [71]
    https://www.opengroup.org/face
  72. [72]
    Verizon claims to operate 170,000 open RAN radios - Light Reading
    As of early 2025, Verizon has over 170,000 O-RAN radios and over 22,900 V-RAN site locations in service in markets across the country. These deployments are ...Missing: AT&T pilots 2018-2025
  73. [73]
    Pushing Forward on Open RAN
    Oct 24, 2025 · AT&T has achieved another major milestone by completing the first Open RAN call using third-party radios over AT&T's commercial network.Missing: Verizon pilots 2018-2025
  74. [74]
    https://www.dote.osd.mil/Portals/97/pub/reports/FY2024/dod/2024f-35jsf.pdf
  75. [75]
    Kubernetes Project Journey Report | CNCF
    Jun 8, 2023 · It is the second largest open source project in the world after Linux and is the primary container orchestration tool for 71% of Fortune 100 ...
  76. [76]
    https://about.att.com/blogs/2025/pushing-forward-on-open-ran.html
  77. [77]
    GSTP funded OPS-SAT launch a success - European Space Agency
    OPS-SAT enables innovative new software, applications and techniques in satellite control to be tested in orbit, at almost no cost.Missing: modular | Show results with:modular
  78. [78]
    [PDF] NanoSat MO Framework: Enabling AI Apps for Earth Observation
    The OPS-SAT mission was launched on the 18th of. December 2019 and it uses the NanoSat MO Framework as its main software orchestration system. Figure 1: OPS-SAT ...
  79. [79]
    IBM slashes Linux mainframe prices to boost declining revenue
    Aug 17, 2009 · IBM has cut in half prices for some specialty Linux processors, according to a report in the Channel Register. The vendor has also released ...<|control11|><|separator|>
  80. [80]
    IBM boosts Linux with strategy shift - CNET
    Apr 21, 2000 · The move is part of IBM's effort to increase the use of Linux across its already broad server line, an effort that has helped to legitimize ...