2012
DOI: 10.1002/sys.21214
|View full text |Cite
|
Sign up to set email alerts
|

Contracting processes and structures for systems‐of‐systems acquisition

Abstract: Acquisition of a system‐of‐systems can be an all new acquisition of multiple systems that are intended to operate together as a system‐of‐systems. Much more common in the U.S. Department of Defense (DoD) is acquisition of one or more new systems that are intended to interoperate with existing systems as a system of systems (SoS) with new capabilities. In either case, successful SoS acquisition necessarily depends on effective contracting structures and processes for SoS acquisition. In this paper, a set of iss… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2014
2014
2022
2022

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(6 citation statements)
references
References 24 publications
0
6
0
Order By: Relevance
“…142 In turn, those contracting practices may not follow actual DOD policy (known as "policy without practice") and may be fueled by soft factors such as a lack of trust between the DOD and major contractors. 143 For example, speeding up ship repair timelines depends on the DOD fixing its own routines for coordinating with contractors or fixing suboptimal relationships with contractors. 144 While bureaucratic constraints do exist among the Big Six, given the DOD's byzantine bureaucratic routines, it is likely that the binding constraint typically lies on the DOD side.…”
Section: Evolution Of the Mws Innovation Systemmentioning
confidence: 99%
“…142 In turn, those contracting practices may not follow actual DOD policy (known as "policy without practice") and may be fueled by soft factors such as a lack of trust between the DOD and major contractors. 143 For example, speeding up ship repair timelines depends on the DOD fixing its own routines for coordinating with contractors or fixing suboptimal relationships with contractors. 144 While bureaucratic constraints do exist among the Big Six, given the DOD's byzantine bureaucratic routines, it is likely that the binding constraint typically lies on the DOD side.…”
Section: Evolution Of the Mws Innovation Systemmentioning
confidence: 99%
“…The US Coast Guard’s Deep-water System and the Joint Tactical Radio System, for example, involved the integration of a legacy system and a new software radio system under development. The integration faced serious challenges such as budget overruns and failure to meet cost, schedule and performance objectives (Rendon et al , 2012). Such integration requires not only the alignment of different systems but also collaboration and consistency in the evaluation and the contract administration processes.…”
Section: Literature Reviewmentioning
confidence: 99%
“…However, careful planning is almost impossible if IT systems have critical technologies that are not fully mature or well defined at the start of the contracting process. By the time the technology is fully developed, the total acquisition cost is considerably higher and the acquisitions experience significant schedule overruns and performance shortfalls (Rendon et al , 2012).…”
Section: Literature Reviewmentioning
confidence: 99%
“…Contracting processes and structures for SoS acquisition are studied in Rendon et al [] to identify effective contracting structures for the purpose of increasing the probability of SoS acquisition success. A web‐based collaborative system is proposed in Huynh et al [2011] to facilitate collaboration among individual system programs in SoS acquisition.…”
Section: Contracting and Negotiationmentioning
confidence: 99%
“…SoS engineers often assume that SoS participants will exhibit nominal behavior but deviation from nominal behavior leads to complications and disturbances in system behavior [Dauby and Upholzer, ]. One of the leading problems in SoS acquisition is identified as the lack of collaboration between individual systems and the SoS program management [Huynh, Osmundson, and Rendon, 2011; Rendon, Huynh, and Osmundson, ]. This is especially a major problem in acknowledged SoS where there is a designated SoS manager and SoS Engineering team but the manager/team does not have complete authority over the constituent systems.…”
Section: Introductionmentioning
confidence: 99%