Control of total ownership cost (TOC) is a continuing initiative to manage costs over the entire life cycle of a weapon system. There are several major categories of costs that contribute to Total Ownership Cost but the principal categories are (1) R&D, (2) Production, (3) Operating and Support, and (4) Disposal.System TOC is the same as Life Cycle Cost (LCC) and must be planned and controlled from requirements definition, system development, and sustainmentfocusing on affordability, and cost to achieve required operational availability. The Program Manager (PM) is responsible for managing system TOC, with input from key stakeholders, such as the sponsor and users. This paper updates our work in 2003, addressing initiatives to control cost, congressional pressure to control cost, leadership guidance, controls, and incentives that can be employed to encourage emphasis on system affordability. There is some discussion of metrics to control life cycle cost and the requirements for databases to assist in estimating and comparing life cycle costs. The growing cost of software supportability and its impact on system TOC is also discussed, along with methodologies for reducing these costs.
To implement the capabilities conceptualized in Joint Vision 2020, complex, secure networks of weapon systems, intelligence platforms, and command and control mechanisms must be seamlessly integrated and maintained over time. Accurate and timely information will enable Joint Vision 2020 key tenets: Dominant Maneuver, Precision Engagement, Focused Logistics, and Full Dimensional Protection. These networks are central warfighting platforms in the information age.As these capabilities are developed over time in an evolutionary manner, interoperability on the Net-Centric Warfare (NCW) networks is essential, and both hardware and software systems must be designed in an Open-systems Architecture (OA) fashion to accommodate the vast number of changes anticipated. Professional Program Management will be needed to successfully develop these key warfighting platforms.Materiel Developers will need to recognize the relatively immature nature of the software engineering domains and actively compensate for this immaturity. System software performance capabilities must be much more detailed than typical hardware-centric systems, as the current state of software engineering disciplines is unlikely to satisfy implied, yet critical performance requirements. Essential OA performance characteristics including Maintainability, Upgradability, Interfaces/Interoperability, Reliability, Safety and Security (MUIRSS) must be fully analyzed and clearly communicated to the software developer to ensure the DoD obtains the flexibility and longevity desired from NCW systems.Keywords: Net-Centric Warfare, Interoperability, Open Systems Architecture, Software Requirements, System of Systems, Family of Systems
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports,
No abstract
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.