Enter MTA Program Data
Enter MTA Program Data
How To Use This Site
Each page in this pathway presents a wealth of curated knowledge from acquisition policies, guides, templates, training, reports, websites, case studies, and other resources. It also provides a framework for functional experts and practitioners across DoD to contribute to the collective knowledge base. This site aggregates official DoD policies, guides, references, and more.
DoD and Service policy is indicated by a BLUE vertical line.
Directly quoted material is preceeded with a link to the Reference Source.
Reference Source: DoDI 5000.80, Paragraph 4.1.f
CAEs will ensure that MTA program names and budget reporting clearly and discretely indicate the scope of the effort being conducted under the MTA pathway, especially when the MTA program is a subprogram of a larger program or is a program spiral, increment, or block upgrade.
USD(A&S) will maintain the authoritative list of MTA programs for the Department.
Reference Source: Guidance from OUSD(A&S)
When naming MTA programs, do not use the larger parent program name for the MTA effort. The Mission and Description section should focus primarily on what the MTA effort is planning to achieve, especially if part of a larger parent program. MTA programs should only enter program identification data (PID) for the MTA effort (i.e. if the MTA program start is Nov 2020 and the estimated MTA program completion date is Jul 2023, then programs should only enter budget position data for FY21, FY22, and FY23. They should NOT include any budget information in FY20 or FY24).
OUSD(A&S) leverages two tools to appropriately track MTA program documentation and data. DOD components may also leverage their own processes & tools to track MTA program data and documentation appropriately, however, the authoritative list of MTA programs is listed in the DAVE repository.
Acquisition Information Repository (AIR)
Acquisition Information Repository (AIR) is a repository where MTA documentation can be uploaded. AIR is accessible via the Defense Acquisition Visibility Environment (DAVE) portal at: https://dave.acq.osd.mil/capabilities [Note: CAC required for access].
Defense Acquisition Visibility Environment (DAVE)
Defense Acquisition Visibility Environment (DAVE) [Note: CAC required for access] is the authoritative source for acquisition document and program identification data (PID) for declared Middle Tier of Acquisition (MTA) programs. The MTA capability in DAVE provides DoD Component Acquisition Executives (CAEs) a means to ensure Rapid Prototyping and Rapid Fielding program identification data is available across the Department.
Note that DAVE also includes a link to AIR, but they are currently hosted on separate platforms.
DAVE MTA Program Data Element Process (See the DAVE MTA PID and Program Creation User Guides for step-by-step information):
Step 1) DAVE Registration: An active DAVE account is required to view program information and access DAVE capabilities.
Step 2) Data Entry Access: A user with appropriate permissions at the PMO, PEO or CAE level may request access to create, edit and review MTA program data under his or her organizational purview.
Step 3) MTA Program Registration: An authorized user with access may register a declared MTA program under his or her organizational purview and create or modify its program attributes.
Step 4) MTA Program Status: An authorized user with access to a declared MTA program may create a PID submission for a program under his or her organizational purview.
See the image below for how to navigate within DAVE to the MTA Submissions for PID.
The required PID data elements are listed below:
Helpful Hints for Manual Entry of MTA Program into AIR and DAVE
- Users must register separately for DAVE and AIR.
- The MTA Program must be entered first in DAVE before documentation can be entered into AIR. See the DAVE MTA PID and Program Creation User Guides for step-by-step information.
- Please refer to the MTA POCs if you have questions or need further assistance.
[Note: CAC required for access]
[Note: CAC required for access]