View MODAF:AcV-2 Programme Timelines View



The AcV-2 Programme Timelines View is part of the MODAF Acquisition Viewpoint and one of the 47 MODAF views*.

Version & Date

Version 1.2.004.

* =  changed at 1.2.004

+ =  new at 1.2.004

The change history is derived from the definition of each MODAF view within the The MODAF Acquisition (AcV) Viewpoint viewpoint document from

See MODAF Release History.


From The MODAF Acquisition (AcV) Viewpoint p4:

The AcV-2 provides a time-based perspective of programmes.

Subject to Crown Copyright


From The MODAF Acquisition (AcV) Viewpoint p4:

The AcV-2 is primarily intended to support the acquisition process across multiple projects or programmes, including the management of dependencies between projects and the integration of all the Defence Line of Developments to achieve a successfully integrated military capability.

Use of AcV-2 should support the management of capability delivery and be aligned with the StV-3, Capability Phasing.

Subject to Crown Copyright


From The MODAF Acquisition (AcV) Viewpoint p4:

The AcV-2 provides an overview of a set of individual projects (e.g. within a given programme), based on a time-line. Projects may be broken into threads (work streams) to show the dependencies at a lower level. For capability-based acquisition, these threads could conveniently be equated with MOD’s Defence Lines of Development (DLODs) – though MODAF does not mandate the use of DLODs.

Where appropriate, the AcV-2 may also summarise the level of maturity achieved across the threads at given milestones in each project.

The information provided by the AcV-2 can be used to determine the impact of either planned or unplanned programmatic changes, and highlight opportunities for optimisation across the delivery programme. The inclusion of the DLOD information enables the Delivery Team to identify potential delays which impact on the delivery of capability. Action to address areas of concern identified in one or more thread, (e.g. a shortfall in training resource) can be co-ordinated across a programme or group of projects. In particular, the knowledge of the dependencies between project milestones can quickly inform a programme manager when a slippage in one project is likely to cause delays in other projects.

Subject to Crown Copyright

Data Objects

From The MODAF Acquisition (AcV) Viewpoint p4:

The data in an AcV-2 can include:


Subject to Crown Copyright


From The MODAF Acquisition (AcV) Viewpoint p4:

  • Timeline View
  • Augmented Gantt Chart

Subject to Crown Copyright

From The MODAF Acquisition (AcV) Viewpoint p5 and p6:

The presentational format for an AcV-2 Product is a Gantt chart optionally augmented with symbols that show the status of each thread at given milestones, and the dependencies between them.

Where AcV-2 differs significantly from a standard Gantt chart is in its use of project thread status indicators. The architect can identify a set of standard threads that run through all projects – e.g. the DLOD. For each of these threads, there can be a status indicator at any given project milestone. This is usually achieved using colour-coding so that stakeholders can tell, at a glance, the status of a given project at different points in time.

AcV-2 does not mandate a standard set of colour codes or even standard threads or statuses; however, it is likely that UK MOD acquisition projects will use the DLODs.

Subject to Crown Copyright

Configuration History

Originally named Acquisition Programmes


The AcV-2 is a useful view for depicting dependencies between projects. The danger is that because it is a familiar Gantt view it gets used for (or confused with) project management diagrams from dedicated project management tools: project information and status is constantly changing and enterprise architecture tools are not best suited to nor the master source for project information so care is needed.

Other Frameworks

See also:


Category:Framework -> View
Category:MODAF -> View



© 2010 Eclectica Systems Ltd.