In the AcV-1 Acquisition Clusters diagram, you model how acquisition projects are grouped. This view can help you improve your management of interoperability between projects, and highlight program dependencies.
The goal is to populate the hierarchy of acquisition clusters and programmes with projects that integrate together or are highly dependent upon each other, so as to improve your ability to manage this integration or dependency. You can define the best acquisition structure to support multiple projects under analysis.
This view would serve useful to those who are responsible for programmes of acquisition projects.
The AcV-1 diagram is a hierarchical diagram. These symbols are available:
▪Project Symbol: Indicates a plan or scheme for a task that takes place over a period of time.
▪Resource Type (aka System Entity): Describes the systems that the project works on. This was previously called System Entity in prior versions of MODAF, but is called Resource Type in MODAF 1.2.
▪Actual Organisation (aka Organisational Unit): The part of an organisation responsible for the project.
▪Owns Line: An Organizational Unit can be connected to a Project with this line.
▪Implements Line: Resources (previously called System Entities) can be connected to a Project with this line.
When building the AcV-1, you generally model the following:
▪all of the acquisition projects delivering systems, or systems of systems, in the acquisition programme under consideration
▪other systems, and systems of systems, which may have a bearing on the architecture
▪how the systems will be best integrated into acquisition clusters
▪how the acquisition clusters can be composed of other clusters, forming a hierarchy.
