PV-2 Project TimelinesAdd to favorites
The PV-2 “Project Timelines” provides a timeline perspective on programs. The PV-2 is intended primarily to support the acquisition and fielding processes including the management of dependencies between projects and the integration of DoD Directive 5000.1 “Defense Acquisition System” policies to achieve a successfully integrated capability. The PV-2 is not limited to the acquisition and fielding processes.
The intended usage of the PV-2 includes:
- Project management and control (including delivery timescales)
- Project dependency risk identification
- Management of dependencies
- Portfolio management
The PV-2 provides an overview of a program or portfolio of individual projects, or initiatives, based on a timeline. Portfolios, Programs, Projects, and Initiatives may be broken into work streams to show the dependencies at a lower-level. For capability-based procurement, these work streams might conveniently be equated with JCA. Sometimes, however, it is more appropriate to consider these acquisition projects in their own right.
Where appropriate, the PV-2 may also summarize, for each of the projects illustrated, the level of maturity achieved across the DoDD 5000.1 policies at each stage of the Defense Acquisition System lifecycle, and the interdependencies between the project stages.
The PV-2 is intended primarily to support the acquisition and fielding processes including the management of dependencies between projects and the integration of DoDD 5000.1 policy to achieve a successfully integrated capability. However, the PV-2 is not limited to the acquisition and fielding processes. The information provided by the Model can be used to determine the impact of either planned or unplanned programmatic changes, and highlight opportunities for optimization across the delivery program. The inclusion of the DoDD 5000.1 policy information allows areas of concern that are outside the immediate scope being considered. Areas of concern identified across the DoDD 5000.1 Defense Acquisition System policies, e.g., a shortfall in training resource, can be coordinated across a program or group of projects, each of which require additional activity to be initiated for successfully delivery according to the project/program schedule.
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal
- Website: DoDAF Meta Model (DM2)
- Website: DoD Information Enterprise Architecture
- Website: OMB Enterprise Architecture Assessment Framework (EAAF)