Systems Development

You are an acquisition lieutenant learning that the Army buys things the same way it does everything else: with regulations, briefings, and someone senior asking why it is taking this long.

You arrive at your first Program Executive Office (PEO) or Program Management Office (PMO) after commissioning — possibly through the Acquisition Corps accessed branch-detail pathway, ROTC Advanced Camp, or a USMA elective track that fed you into FA51. Your days are structured around the Defense Acquisition System: attending Integrated Product Team (IPT) meetings, writing program documents (Acquisition Strategy, System Engineering Plan, Test and Evaluation Master Plan excerpts), coordinating with industry partners under the oversight of your PM and contracting officer, and learning the regulatory stack — DoDI 5000.02, DoD 5000.02-M, AR 70-1 — well enough to contribute to the briefs your PM delivers to the Milestone Decision Authority. The unglamorous center of the job is document production and staffing: tracking Action Items from IPT meetings, chasing signature pages through the Pentagon and PEO headquarters, and learning that the Army buys a $2 billion system with the same bureaucratic patience required to buy a $200 piece of furniture. Field time is rare; the action is in the office, the conference room, and the secure video teleconference.

• 01Read and apply DoDI 5000.02 (Operation of the Adaptive Acquisition Framework) to identify the correct acquisition pathway for a given program — Major Capability Acquisition, Middle Tier of Acquisition, Software Acquisition, or Other Transaction.
• 02Draft and staff acquisition program documents — Acquisition Strategy, Program Protection Plan, Test and Evaluation Master Plan (TEMP) sections — to the PM's standard and the MDA's format.
• 03Conduct requirements tracing from the Joint Capabilities Integration and Development System (JCIDS) Initial Capabilities Document (ICD) and Capability Development Document (CDD) through the program's system specifications.
• 04Brief program status, schedule, and risk to a PM-level audience using an Earned Value Management System (EVMS) or an Integrated Master Schedule (IMS) read.
• 05Coordinate with a Defense Contract Management Agency (DCMA) representative and the contracting officer on contract performance issues without wandering into the unauthorized-commitment minefield.
• 06Complete DAU foundational coursework — ACQ 101 (Fundamentals of Systems Acquisition Management), ACQ 201A/B (Intermediate Systems Acquisition) — on schedule before your first IPT lead assignment.

• —DoDI 5000.02 — Operation of the Adaptive Acquisition Framework (the governing instruction for all DoD acquisition programs; read it first).
• —AR 70-1 — Army Acquisition Policy (the Army implementation of the DoD 5000 series; the PMO SOP references it on every key decision document).
• —DAU iCatalog (icatalog.dau.edu) — the Defense Acquisition University course catalog; ACQ 101, ACQ 201A/B, and the Engineering and Technical Management (ETM) series are the LT foundation.
• —DoD 5000.02-M — Defense Acquisition System Procedures (the manual companion to the instruction).
• —AR 73-1 — Test and Evaluation Policy (the Army reg governing TEMP development and the T&E reporting chain).
• —DA PAM 600-3 — Officer Professional Development (chapter on Acquisition Corps FA51, career progression, and the Acquisition Corps membership criteria).

• —DAWIA (Defense Acquisition Workforce Improvement Act) certification: Acquisition Corps membership requires a baccalaureate degree, 24 semester hours in business/related fields, and completion of DAU core coursework for the acquisition career field. Verify current DAWIA implementation under DoDM 5000.03.
• —FAC-C (Federal Acquisition Certification in Contracting) or equivalent credential track — many FA51 billets in contracting-adjacent roles require or strongly prefer the certification; the PM will tell you on day one.
• —Program Management Level I certification (DAU) before the O-3 board if your billet is PM-coded; the certification timeline drives course-slot requests through your command's Defense Acquisition Workforce requirements tracking.
• —OER profile from the first KD assignment that names measurable program outcomes — milestone decision supported, contract award executed, test event supported without program-level Nunn-McCurdy breach — not vague leadership metrics.

• —Wandering outside your contracting-officer relationship lane — even casually discussing a technical requirement or cost-range with an industry rep without the CO present is an unauthorized commitment risk under FAR 1.602.
• —Treating IPT Action Item lists as optional. The item you did not close before the next meeting is the item your PM has to explain to the MDA briefer, and it has your name on the tracker.
• —Staffing a program document before checking AR 70-1 and the program's acquisition category (ACAT) level for signature authority. An ACAT-I document that goes to the wrong decision level comes back with a note you do not want attached to your first OER.
• —Conflating the program schedule (Integrated Master Schedule) with the contract's period of performance — two separate documents, two separate risks, and confusing them in a brief is the fastest way to lose the PM's confidence in front of the MDA staff.

The good acquisition lieutenant closes Action Items before the next IPT, drafts program documents the PM does not rewrite three times, and asks the contracting officer his questions privately before the industry meeting rather than discovering the lane boundaries in front of the contractor. By the end of the first KD assignment his PM is naming him as the officer who supported a key milestone or contract award, and his OER bullets translate government acquisition outcomes — not leadership generics.

You are the program. Not the system, not the contract — the program. Every budget cycle, every Nunn-McCurdy watch, every MDA briefing, every contractor overrun starts and ends with your name on the program documentation.

You return to DAU for the Advanced Program Manager's Course (PMT 401, the flagship PM development course) and are assigned to a Program Manager or Deputy Program Manager seat at a Program Executive Office (PEO) — PEO Soldier, PEO Ground Combat Systems, PEO Aviation, PEO Command Control and Communications-Tactical (C3T), PEO Enterprise Information Systems (EIS), PEO Missiles and Space, PEO Ammunition, PEO STRI (Simulation, Training, and Instrumentation), or the Army Contracting Command (ACC). The KD seat for a captain or major is usually an Assistant Program Manager (APM) chair — you own a line of effort within a program (APM for Systems Engineering, APM for Test and Evaluation, APM for Production and Quality Assurance, APM for Contracting) or you run a smaller program as PM in your own right under a PEO. Your day is a mix of contractor oversight (Contractor Performance Assessment Reporting System — CPARS — inputs, EVMS status reviews, Integrated Baseline Reviews), program-document production (Acquisition Decision Memoranda, Program Deviation Reports, Nunn-McCurdy certifications when required), Congressional budget justification support (Program Element Code justifications, R&D appropriation narratives), and MDA preparation. You will learn more about Congressional appropriation cycle — the President's Budget (PB), the NDAA markup process, the continuing resolution math — than any maneuver officer will ever know. The unglamorous center: the Action Item tracker, the staffing chase, and the PowerPoint deck the MDA staff will tell you is too long after you have already shortened it twice.

• 01Manage an Integrated Master Schedule (IMS) and an Earned Value Management System (EVMS) read — identify Cost Performance Index (CPI) and Schedule Performance Index (SPI) trends, brief the variance analysis, and translate the data into a risk-adjusted program narrative for the MDA.
• 02Lead an Acquisition Strategy (AS) development or update — program approach, contract strategy, competition considerations, make/buy analysis, competition exclusions, and the paragraph the Under Secretary of Defense for Acquisition and Sustainment (USD A&S) staff will red-line.
• 03Prepare and defend a program through a Milestone Decision Authority review (Milestone A, B, or C, or a Nunn-McCurdy certification review) — the documentation package, the critical program information, the affordability analysis, and the Should-Cost versus Will-Cost narrative.
• 04Execute CPARS contractor performance assessments — document performance against contract requirements, coordinate the contractor's response, and defend the rating at the evaluation review if the contractor contests it.
• 05Navigate a Nunn-McCurdy unit cost breach — identify the breach, calculate the percentage threshold, draft the breach notification, support the certification package, and brief the Congressional staff if the breach meets the significant/critical threshold under 10 USC 4374.
• 06Make the career branch-versus-FA decision honestly: whether to pursue the Acquisition Corps membership long-term, the civilian GS-1101/1102 transition path post-service, or a return to the basic branch for battalion command consideration. DA PAM 600-3 and the HRC OPMD are the only honest sources on the math.

• —DoDI 5000.02 — Operation of the Adaptive Acquisition Framework; DoD 5000.02-M — Defense Acquisition System Procedures.
• —AR 70-1 — Army Acquisition Policy; AR 73-1 — Test and Evaluation Policy.
• —DAU iCatalog — PMT 401 (Advanced Program Manager's Course), ACQ 310 (Intermediate Program Management), and the Program Management Body of Knowledge (PMBOK) alignment modules.
• —10 USC 4171–4375 — Acquisition and procurement statutes codifying Milestone review authorities, Nunn-McCurdy breach thresholds, and the MDA authority chain.
• —FAR (Federal Acquisition Regulation) and DFARS (Defense Federal Acquisition Regulation Supplement) — the contracting framework your program lives inside; know the parts that govern source selection, contractor performance assessment, and contract modification authority.
• —DA PAM 600-3 — Officer Professional Development (Acquisition Corps chapter); AR 600-8-29 — Officer Promotions (promotion-zone math the DOPMA governs).

• —DAWIA Program Management Level II or III certification (depending on ACAT level of assigned program) before the first key-developmental OER cycle; the PM will ask about certification status in the in-brief.
• —Successful key-developmental OER — Assistant PM or PM — with senior rater bullets tied to measurable program outcomes: milestone decision supported, EVMS variance held within threshold, CPARS submitted on time, Nunn-McCurdy breach avoided or certified cleanly.
• —ILE / CGSC completion (resident or non-resident / Blended Seminar) before the major's board — standard field-grade requirement across all Army officer career fields.
• —JDAL (Joint Duty Assignment List) credit — Acquisition Corps field-grades who slate to DASD-level, USD(A&S) staff, AAPC (Army Acquisition Policy and Contracting), or JROC/JCIDS joint-billet positions get joint-credit value; the path is narrower than for maneuver branches but real.
• —For the centralized command and major's board: pull the current OPMD board release under AR 600-8-29 — the Acquisition Corps promotion-zone math and the field-grade selection percentages are the only authoritative source.

• —Treating the program schedule as a marketing document. Integrated Master Schedule integrity is the foundation of EVMS credibility; a program that is briefing green-green-green while the IMS shows red-amber-red is the program the MDA audits at the next Milestone review.
• —Approving a contract modification without coordinating with the contracting officer and confirming no Nunn-McCurdy threshold impact. Out-of-scope modifications and undisclosed cost growth are the two fastest ways to convert a normal Milestone review into an unplanned Congressional notification.
• —Letting the CPARS cycle slip because the contractor's performance was average and the conversation is uncomfortable. Incomplete CPARS documentation is a source-selection fairness vulnerability — the next competing contractor's protest cites incomplete assessments routinely.
• —Hiding a program risk at the MDA briefing because "we're working the mitigation." The MDA staff learns about the risk at the next Quarterly Program Status Review, not the Milestone. That is the program — and the PM — that USD(A&S) puts on the watch list.
• —Skipping the Should-Cost analysis on the assumption that the contractor's cost proposal is the starting point. The Should-Cost methodology is an affordability discipline tool specifically to drive program efficiency — the program office that treats Should-Cost as a paperwork requirement produces estimates the Pentagon auditors use against you in the next budget cycle.

The good acquisition captain or major runs a program the MDA can brief to Congress with no surprises in the month before the hearing. His EVMS is real — the variances are documented, the root causes are named, and the recovery plans are funded. His CPARS cycle is current, his contractor knows where the contract stands on every deliverable, and his program documentation is staffed to the right signature authority before the MDA suspense arrives. His senior rater OER bullet reads "supported two milestone decisions and a Nunn-McCurdy certification without program-level cost breach" — the kind of measurable acquisition outcome that the OPMD board can defend. The major who finishes a KD with a clean program file and a post-command-equivalent OER profile is the major the PEO nominates for the next PM seat or the joint-acquisition-staff tour that builds the field-grade record for battalion command consideration.