Sec. 801. Open systems approach to acquisition of systems containing information technology
746 words·~3 min read·
/bill/113/s/2410/pcs/section-801·A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
Except as provided in paragraphs
(2)and (3), each Major Defense Acquisition Program and Major Automated Information System, and each other acquisition program the primary purpose of which is the acquisition of an information technology system, that enters concept development after January 1, 2016, shall use an open systems approach in development to achieve agility, rapid capability enhancement, interoperability, increased competition, and lower costs over the life cycle of the program. The requirement under paragraph
(1)shall not apply to an acquisition program if a business case analysis conducted at a point in development where there is sufficient design information to conduct an independent life-cycle cost estimate demonstrates that an open systems approach is more expensive or is not practically achievable. The requirement under paragraph
(1)does not apply to acquisition programs that consist primarily of commercial off-the-shelf
(COTS)end items and systems or modified COTS systems. Systems acquired pursuant to urgent or emergent operational need statements shall not be subject to the requirement in paragraph
(1)unless a decision is made to transition the program to a program of record. In the event of such a transition, a business case analysis shall be conducted to consider the life-cycle costs of the program and determine whether to migrate the system to an open systems architecture. Not later than January 1, 2016, the Secretary of Defense shall take the following actions: Identify computing environments within the Department of Defense that are sufficiently distinct to justify the development of specific Technical Reference Architectures and associated standards necessary to support an open systems approach to the development of systems utilizing those computing environments. Identify each mission and functional domain within the Department of Defense that is sufficiently distinct to justify the development of domain-specific services and associated standards necessary to support an open systems approach to the development of systems that will operate in that mission or functional domain. Pursuant to section 12(d) of the National Technology Transfer and Advancement Act of 1995 (Public Law 104–113; 110 Stat. 783; 15 U.S.C. 272 note) and Office of Management and Budget Circular Number A–119, form or use voluntary, consensus-based standards bodies to establish the standards required for each of the Technical Reference Architectures and each set of domain-specific services to support open systems approaches. Ensure, in carrying out the actions set forth in paragraphs
(1)through (3), that there are not duplicative or competing Technical Reference Architectures, domain-specific services, or standards or standards bodies related to such architectures and services across the Department of Defense. Not later than July 1, 2015, the Director of Cost Assessment and Program Evaluation shall issue guidelines for business case analyses as they apply to decisions regarding the adoption of an open systems approach, including requirements for comparative life-cycle costs and opportunities for competition and capability upgrades. Not later than November 1, 2015, the Under Secretary of Defense for Acquisition, Technology, and Logistics shall submit to the congressional defense committees a report— identifying all closed systems that are in development, production, or deployed status as of January 1, 2016, that are or were Major Defense Acquisition Programs or Major Automated Information Systems; outlining a process for establishing the priority of migrating each such system and program to an open system; and including a schedule to review the top half of the prioritized list, conduct a business case analysis on each program, and develop plans where appropriate to migrate such programs to an open system within 10 years. In this section: The term domain-specific services means the decomposition of functions and operations in specific mission domains into common services that systems operating in those domains would utilize. The term information technology has the meaning given the term in section 11101(6) of title 40, United States Code. The term open systems approach means an integrated business and technical strategy that— employs a modular design, and uses widely supported and consensus-based standards for its key interfaces; is subjected to successful validation and verification tests to ensure the openness of its key interfaces; and uses an open system architecture allowing components to be added, modified, replaced, removed, or supported by different vendors throughout a program's life-cycle in order to afford opportunities for enhanced competition and innovation while yielding significant cost and schedule savings and increased interoperability. The term Technical Reference Architecture means a system architecture template for a particular computing environment that provides a common vocabulary for implementations to promote consistency and commonality of interfaces and interactions between architectural layers.
Connectionstraces to 1
Traces to 1 document
2 references not yet in our index
- Pub. L. 104-113
- 110 Stat. 783
Citation graph
cites case law
Sec. 801
Open systems approach to acquisition of systems containing information technology
Pub. L.Pub. L. 104-113
Stat.110 Stat. 783
Cites 3Cited by 0 across 0 sources