Aligning force planning and systems acquisition. Issue 1 (2014)

• Record Type: Journal Article
• Authors: Thaba, James; Benade, Siebert
• Is Part Of: INCOSE International Symposium. Volume 24:Issue 1(2014)
• Page Start: 514
• Page End: 527
• Publication Date: 2014
• Subjects: Systems engineering -- Congresses; Systems engineering -- Periodicals; 620.0011
• DOI: 10.1002/j.2334-5837.2014.00037.x
• Languages: English
• ISSNs: 2334-5837

Abstract

<abstract abstract-type="main"> <title>Abstract</title> <p>With the dawn of democracy in South Africa, there was a general shift in paradigm in the utilisation of the defence force. The formation of Joint Operations Division signalled a new era for the SANDF and a drive towards jointness in operations, which meant joint planning for the future. Acquisition in the SANDF is governed by Defence Acquisition Policy (DAP) 1000 based on sound System Engineering principles. This policy defines eight levels of the system hierarchy. This is important to distinguish between the various levels of employment and complexity. This study focusses on the interface between systems levels 5, 6 and 7.</p> <p>The ROC is drafted by arms of services with Joint Operations division (which specifies capability requirements) only involved in its approval process. This in turn creates a gap between force planning and acquisition of product systems. In assessing the alignment of future defence objectives and prospective acquisition programs, the efforts to assess this gap has four areas to deal with, namely, implementation of Capability‐based planning (CBP), assessment of the link between capability requirements and acquisition programs, the link between technology planning and capability development and lastly the engineering concept required to take over from System of System Engineering from Level 7. Survey and case study methods were used for this research to assess whether there exists a gap between capability development and systems engineering as it is done in the SANDF and devise proposals to deal with the gap should it be found to exist.</p> </abstract>