Military Admin & Personnel Acronyms

The submarine engineering department division responsible for the non-nuclear auxiliary mechanical systems of the boat — staffed by Machinist's Mates (not nuclear-qualified — the "A-Gang" mechanics rather than MMN) — owns the diesel generator, hydraulics, atmosphere control (oxygen generator, CO2 scrubber, atmosphere analyzers), refrigeration and air conditioning, sanitary systems, and the trim-and-drain and other non-nuke mechanical systems forward of the engine room.

"A-Gang — Auxiliary Division, the non-nuke MMs who run hydraulics, atmosphere, diesel."

A-Gang is the non-nuke engineering division — Machinist's Mates without the nuclear qualification, running the non-nuclear auxiliary mechanical systems forward of the engine room: the emergency diesel generator, hydraulics (the hydraulic plants that drive control surfaces, rudders, planes, periscopes), atmosphere control (the oxygen generator that splits seawater into oxygen, the CO2 scrubber, the atmosphere analyzers), refrigeration and air conditioning, sanitary systems, trim-and-drain. The A-Gang culture on a submarine is distinct from the nuke culture — A-Gangers don't go through Charleston, don't live the ORSE cycle, and their identity inside the engineering department is "the non-nukes who keep everything else running." The split between nuke and A-Gang inside the same department is one of the more interesting cultural dynamics on a submarine.

Arms, Ammunition, and Explosives (AA&E) — the joint and service-doctrinal category covering all weapons, ammunition (small-arms through artillery), and explosive ordnance subject to strict accountability, secure storage, and chain-of-custody requirements under DoD physical security regulations, with category designations (I, II, III, IV) driving the level of security and reporting required.

"The bucket term for weapons, ammo, and explosives — the most-tracked category in the inventory."

AA&E is the category every armorer, ammo handler, and EOD tech lives inside — the master class of property where losing a single item triggers a CID investigation and a unit-wide shakedown. The category drives everything: how your arms room is constructed, how the rounds get drawn and turned in at the range, how the demo block is signed for at the train-up, how the EOD response is launched when a round shows up in a contractor's scrap pile. Categories I and II (man-portable missiles, explosives) get the heaviest controls; Category IV (non-lethal small arms components) gets less. The acronym shows up everywhere from arms room SOPs to range safety briefings to base entry control point rules — if you've ever signed a hand receipt for a weapon, you've been inside the AA&E system.

Activity Address Code (AAC) — a six-character alphanumeric code assigned by the Defense Logistics Agency to uniquely identify a DoD unit, activity, or organization for the purpose of routing requisitions, shipments, billing, and other logistics transactions through the Defense Logistics Management System.

"The six-character code that identifies your unit to the supply system."

AAC is the routing number the supply system uses to know who you are — every requisition, every shipment, every push-to-customer line of accounting touches an AAC. To a unit supply NCO, the AAC is the thing they verify on the 1348-1, the thing that has to match the DODAAC on the document, and the thing that mis-routes a critical part to a unit on the other side of the country when it's wrong. To everyone else, AAC is invisible plumbing — until a Class IX part doesn't arrive and the supply sergeant traces the document through the AAC and DODAAC chain to find out where it landed. If you're ever in S-4 or G-4, AAC and DODAAC become your daily vocabulary.

The Department of Defense acquisition policy structure, established in the 2020 rewrite of DoDI 5000.02, that defines six distinct acquisition pathways (Major Capability Acquisition, Middle Tier of Acquisition, Software Acquisition Pathway, Defense Business Systems, Acquisition of Services, and Urgent Capability Acquisition) tailored to different program types and timelines, replacing the prior one-size-fits-all approach.

"The DoD acquisition policy that defines six tailored pathways instead of a single MDAP process."

AAF is the institutional acknowledgment that the traditional Milestone A/B/C MDAP framework was the wrong fit for the majority of acquisition work — IT systems, software, services, urgent operational needs, and prototypes were forced through a structure designed for ships and aircraft. The six pathways now coexist under DoDI 5000.02, each with its own policy issuance, decision authorities, and reporting cadence. Programs select a pathway based on what they are buying; some programs use multiple pathways across components or phases. The framework's success depends on Program Office discipline in actually using the streamlined authorities rather than re-importing MDAP overhead.

Allied Administrative Publication (AAP) — a NATO-standard category of administrative publications produced under the NATO Standardization Office that establishes common administrative procedures, terminology, and reference data used across NATO member nations to support multinational interoperability, with AAP-6 (NATO Glossary of Terms and Definitions) being the most widely referenced example.

"NATO's administrative publication series — the standardization documents you'll see in any allied op."

AAP is the NATO-standardization counterpart to the US joint publication system — administrative and reference documents that establish common terminology and procedures so that a Polish battalion and a US battalion mean the same thing when they say "phase line" or "limit of advance." AAP-6 (the NATO Glossary) is the one most often referenced in practice; AAP-15, AAP-19, and others cover specialized terminology. To a US officer working in a NATO billet, on a multinational exercise, or in a coalition headquarters, AAP references show up next to JP and ATP references and have to be cross-walked. The Dictionary lists it because joint and combined doctrine repeatedly cites AAPs for terminology, and US service members need to know what the abbreviation means.

After-Action Report and After-Action Review (AAR) — joint and Army doctrinal terms for the structured analysis of a completed operation, training event, or mission, capturing what was planned, what actually happened, what worked, what did not, and what to sustain or improve; the term also refers separately to air-to-air refueling (AR), the in-flight transfer of fuel from a tanker aircraft to a receiver aircraft.

"The structured review after every training event — and separately, in-flight refueling."

AAR in the ground-force world is the cornerstone of how the Army learns — every CTC rotation, every gunnery, every field problem ends with an AAR led by an O/C (observer-coach) or by the unit's own leadership, using the "what was planned / what happened / why / what to sustain or improve" framework codified in ATP 6-22.1. A senior NCO who can run a good AAR is force-multiplier valuable; one who turns it into a hotwash blame session destroys learning for an entire formation. The Dictionary lists the term twice because "AAR" also means air-to-air refueling — the boom or drogue transfer of fuel from a tanker to a receiver in flight. Context tells you which one a briefer means: if they're talking about C-17s and KC-46s, it's the second; if they're talking about a training event, it's the first.

The Department of the Army's civilian-led board with authority to correct errors and remove injustices in Army military records, including discharge upgrades, medical retirement adjustments, and removal of adverse paperwork.

"The Army's highest administrative remedy for record corrections."

ABCMR considers thousands of cases per year and grants relief in a meaningful minority of them. Strong cases include new evidence (medical diagnoses post-service, command climate evidence), procedural error in the original action, or material injustice. Board files are public after redaction — read prior decisions in your category before submitting.

The Department of Defense classification system that categorizes acquisition programs by dollar threshold, complexity, and program risk into ACAT I, II, and III levels, determining the decision authority level (Milestone Decision Authority), the oversight intensity, and the documentation requirements for the program.

"The DoD program tier classification that determines decision authority and oversight."

ACAT determines who runs the program approval — ACAT I programs are MDAPs (the largest), with Milestone Decision Authority at the OSD level (or a designated CAE for ACAT IC); ACAT II programs are major-system acquisitions with service-level MDA; ACAT III programs are smaller, with PEO or program-level MDA. The category drives the documentation load (an ACAT I program produces a much larger document portfolio than an ACAT III) and the reporting requirements (SAR for MDAPs is required by statute).

Automated Cargo Documentation (ACD) — the joint and Air Force-side digital systems and processes used to capture, validate, and transmit cargo documentation (manifests, hazardous materials declarations, weights and balances, load plans) through the Defense Transportation System, replacing legacy paper-based documentation and feeding upstream movement planning and downstream reception systems.

"The digital cargo paperwork system replacing the old paper manifests."

ACD is the umbrella term for the digital systems (GATES, CMOS, TC-AIMS II, and successors) that have replaced the binder of paper manifests every unit movement officer used to carry — capturing weights, dimensions, hazardous materials data, and ownership for every piece of cargo and feeding it into the broader Defense Transportation System. To a UMO or a 88N transportation NCO, ACD is the daily workflow — getting the manifests right before the pallet moves, because a bad manifest means a pallet either won't board the aircraft or will get bounced off at the APOE. To everyone else, ACD is invisible until something goes wrong; when it does, the resulting paperwork drill is exactly as painful as the paper era it replaced.

Allowable Cabin Load (ACL) — the maximum payload (passengers, cargo, or combination) that a specific aircraft can carry on a specific mission given the runway, weather, fuel load, range, and operating environment constraints, calculated by the aircraft commander and air mobility planners to determine how many people and how much cargo can actually fly on a given sortie.

"The actual usable payload of an aircraft on a specific mission — almost always less than its max."

ACL is the number that a unit movement officer and an air mobility planner argue over before every airlift mission — the actual usable payload of a given aircraft for a given mission, after accounting for hot/high airfield performance, runway length, fuel needed to reach the destination, and reserve fuel. A C-17 has a published max payload; its ACL on a mission into a 6,000-foot dirt strip in the mountains is significantly less. The maneuver commander wants to send the whole company; the ACL determines whether two chalks become three. To a 88N or a 1C0 (Air Force aerial port), ACL is the working number; to the rifle company commander whose vehicles get bumped to a later chalk, it's the source of the headache.

Acquisition and Cross-Servicing Agreement (ACSA) — a bilateral agreement authorized under 10 USC 2342 between the United States and an eligible foreign government or international organization that authorizes the reciprocal acquisition and provision of logistic support, supplies, and services (food, fuel, transportation, billeting, ammunition, medical services, communications, base operations support) on a reimbursable, replacement-in-kind, or equal-value-exchange basis during combined exercises, training, deployments, and operations.

"The legal authority that lets US forces trade fuel, food, and services with an allied military."

ACSA is the unsung legal scaffolding that makes coalition operations actually function — without it, a US battalion can't legally pump Polish diesel into its HMMWVs, eat at a German DFAC, or sleep in a Japanese barracks without somebody back at the comptroller's office having a stroke. Every theater logistics officer (90A) and contracting officer in a coalition headquarters has ACSA on a sticky note next to their screen because it's the authority that lets the transaction happen. The agreement governs reimbursement: cash, replacement-in-kind, or equal-value exchange. Most service members never hear the acronym, but they live inside it any time they're fueled, fed, or housed by a partner force on exercise or deployment.

A Reserve and Guard activation status for short-term active-duty tours supporting specific missions, training, or augmentation requirements. Voluntary; orders issued by the gaining unit.

"Short-term active-duty orders supporting specific missions."

ADOS is the most flexible Reserve activation tool — tours can range from days to multiple years. Under longer ADOS orders, members accrue active-duty benefits (Tricare, BAH at the duty location), but transitions in and out of ADOS status often create gaps in pay and benefits that take months to fix. Track your orders, in/out dates, and DEERS status yourself; do not assume the gaining unit's S-1 caught everything.

Army Doctrine Publication (ADP) — the top-tier category of Army doctrine, providing the fundamental principles, tenets, and overarching concepts that guide the Army's operations (ADP 3-0 Operations, ADP 6-0 Mission Command, ADP 1 The Army, etc.); each ADP is paired with an ADRP (Army Doctrine Reference Publication) that elaborates the principles in greater detail. Automated Data Processing (ADP) — the legacy term for computer-based data processing systems used across DoD, surviving in fiscal categories, security classifications (ADP categories I/II/III), and acquisition documents.

"Either the Army's top-level doctrine publication, or the legacy term for IT systems — context tells you which."

ADP is a context-dependent acronym. In a doctrine review session or an OES classroom, ADP means Army Doctrine Publication — the top-tier short books (ADP 3-0 Operations, ADP 6-0 Mission Command, ADP 7-0 Training) that lay out the fundamentals every Army leader is expected to know. In a security clearance investigation or an IT job announcement, ADP means Automated Data Processing — the legacy DoD term that still drives ADP-I, ADP-II, ADP-III sensitivity categories for federal IT positions and the suitability adjudications behind them. To a captain at CGSC, ADP is the first reading; to a security manager, ADP is the position-sensitivity table. Both meanings are alive in current documents.

Army Doctrine Reference Publication (ADRP) — the elaborating reference publication paired with each top-tier Army Doctrine Publication (ADP), providing the detailed doctrine, terminology, and explanatory content that supports the principles set forth in the parent ADP (e.g., ADRP 3-0 Operations pairs with ADP 3-0); the ADP/ADRP pair is the foundation of the Army's post-2012 doctrine architecture.

"The detailed reference doctrine that pairs with each top-level ADP."

ADRP is the longer, more detailed companion to each ADP — where ADP 3-0 lays out the principles of unified land operations in about 30 pages, ADRP 3-0 elaborates them across 100-plus pages with the terminology, examples, and supporting doctrine that the captain on the staff actually needs to write an OPORD. The ADP/ADRP architecture replaced the older FM-based system in 2012 and is the framework every officer education course teaches from. To a CGSC student or a major writing a campaign plan, ADRP is the bookshelf reference; to a battalion S-3, ADRP is the document they grep when they need the exact doctrinal language to put in a paragraph. (Note: a 2019 doctrine reorganization renamed several ADRPs back to FMs, so older soldiers sometimes use the term loosely — but the Dictionary still lists it.)

Arms Export Control Act (AECA) — the US statute (22 USC 2751 et seq.) that governs the export of defense articles and defense services to foreign governments and international organizations, providing the legal authority for the Foreign Military Sales (FMS) program, controlling the licensing of direct commercial sales of US Munitions List items through the State Department, and conditioning sales on end-use monitoring and human rights considerations.

"The federal law that governs every US arms export — FMS sales, FMF grants, and DCS licenses."

AECA is the statute that runs the entire US arms-export apparatus — the Foreign Military Sales (FMS) program managed by DSCA, the Foreign Military Financing (FMF) grants administered by State, and the Direct Commercial Sales (DCS) licenses approved by the State Department's DDTC. To a security cooperation officer (FAO or 38B/M), AECA is the legal backbone of every Letter of Offer and Acceptance (LOA) they help build. To a contracting officer at a US defense firm, AECA's licensing regime determines whether their product can be sold to a particular ally. The statute also sets human-rights conditions and end-use monitoring requirements that have generated political contestation across multiple administrations, particularly around sales to specific Middle Eastern customers — surface the framework, surface the decision points, talk to a JAG if it gets close to a particular case.

The Air Force form used to request, approve, and authorize leave (annual, emergency, advance, terminal, convalescent, and other categories) for active-duty Airmen and Guardians, signed by the requesting member and the approving authority, processed through the squadron CSS or unit personnel section.

"The Air Force leave request and authorization form."

AF Form 988 is what every Airman has signed dozens of copies of — block-and-tackle leave paperwork for everything from a four-day pass converted to leave to a 30-day block of summer leave to terminal leave before separation. The form has migrated through several digital workflow systems over the years (LeaveWeb, then various myFSS-era replacements), but the form itself is the same document. The interaction with the LES — leave balance reduction, leave-sell limits, the use-or-lose accumulation cap (currently 60 days for most members) — is where most leave-management questions actually live.

The Department of the Air Force's civilian-led board for correcting errors and removing injustices in Air Force and Space Force records.

"The record-correction body for the Air Force and Space Force."

Procedurally similar to ABCMR and BCNR. The board takes its strongest cues from documented procedural error and from new medical or behavioral health evidence connecting the service event to a diagnosed condition. The Hagel Memo and Kurta Memo direct boards to give "liberal consideration" to PTSD, TBI, MST, and other behavioral-health-related discharge upgrade requests.

Air Force Doctrine Annex (AFDA) — a subordinate doctrinal publication issued by the LeMay Center for Doctrine Development and Education that expands on a specific functional area of Air Force doctrine (e.g., personnel recovery, agile combat employment, counterair), supplementing the higher-level Air Force doctrine publications with detailed how-we-think guidance for airmen.

"A focused Air Force doctrine document covering one functional area in depth."

AFDA is the "go-deep" companion to the broader Air Force doctrine publications — when an airman needs the doctrinal answer on how the Air Force thinks about personnel recovery, agile combat employment, or counter-air, the AFDA in that lane is the working document. The annexes live on the LeMay Center site and get rewritten on a multi-year cycle as the service updates its thinking; reading the current AFDA for your functional area is how a captain at AFSC or a major at SAASS demonstrates they actually know the doctrine and not just the slogans. To a non-air-force joint planner, AFDAs are the source documents you cite when you want to argue from Air Force doctrine; to an airman, they're the answer to "what does the service actually say."

Air Force Doctrine Document (AFDD) — the historical numbering series for Air Force doctrinal publications (AFDD 1, AFDD 2-0, AFDD 3-series) issued by the LeMay Center, largely superseded by the current Air Force Doctrine Publications and AFDA annex structure but still cited in older documents and in joint publications that reference legacy versions.

"The legacy Air Force doctrine document series — still cited in older joint pubs."

AFDD is the previous-generation label for Air Force doctrinal publications — the AFDD 1 (Air Force Basic Doctrine), AFDD 2-0 (Operations and Planning), and the 3-series functional documents that an Air Force captain in the early 2010s lived inside. The service has since restructured around Air Force Doctrine Publications (AFDPs) and AFDA annexes, but the AFDD acronym still appears in older joint documents, older ATPs, and any reference list that pre-dates the changeover. A staff officer working a joint problem will occasionally chase an AFDD citation, find it superseded, and have to cross-walk to the current AFDP/AFDA — the kind of friction that comes with any doctrinal taxonomy shift.

Air Force Handbook (AFH) — a class of Air Force publication that provides operational, technical, or procedural guidance in handbook (rather than directive) form, used to assist airmen in performing a task or understanding a process without carrying the regulatory force of an Air Force Instruction (AFI) or Air Force Manual (AFMAN).

"A non-directive Air Force publication — guidance, not regulation."

AFH is the "here is how to do this thing" publication category — handbooks that explain a process, a system, or a task without the regulatory weight of an AFI. When a CCAF curriculum, a career-field study guide, or a how-to-write-EPRs reference is published, it's typically an AFH. The distinction matters in the legal-administrative sense: an AFI tells you what you must do; an AFH tells you how to do it. To a TSgt prepping for promotion testing, the AFH lane is where the actual study material lives; to an inspector grading a unit, the AFI lane is where the failure points live. Most airmen learn the difference by the time they pin on E-4.

Air Force Instruction (AFI) — a directive Air Force publication that establishes mandatory procedures, responsibilities, and standards for accomplishing an Air Force mission or function, carrying regulatory force on Air Force personnel and units; the most commonly referenced category of Air Force directive publication.

"The directive Air Force publication — if it says AFI, it's mandatory."

AFI is the workhorse of Air Force regulatory publications — the thousands of documents that govern how an airman wears the uniform (AFI 36-2903), how a squadron runs fitness assessments (AFI 36-2905), how an awards package is built, how a flight commander writes EPRs, how a unit handles a security incident. "What does the AFI say" is the first question asked in any compliance inspection, any first-sergeant office call, any commander's call about a corrective action. To a young airman, the AFI is the ground truth; to a seasoned commander, the AFI is the floor, with squadron-specific guidance on top. The acronym is so universal in the Air Force that "AFI" gets used as a verb — "have you AFI'd this yet."

Air Force Joint Instruction (AFJI) — a jointly-issued Air Force publication that has been co-signed with one or more other services as a joint instruction, establishing common procedures or responsibilities across the participating services on a matter of joint concern, sitting alongside (and frequently cross-walked with) the corresponding Army Regulations or Navy/Marine Corps publications.

"An Air Force instruction co-signed by another service — joint procedure with regulatory force."

AFJI is the multi-service version of an AFI — same regulatory force, but co-signed with the Army, Navy, or Marine Corps so that all participating services are bound by the same procedure. The AFJI 11-204 (joint airborne and air transportability training) is the classic example — every service that drops paratroopers from Air Force aircraft is regulated by the same document, with the AFJI/AR/MCO/SECNAVINST suite of cross-references on the cover page. To a UMO or an air mobility planner working a joint deployment, AFJI is the document that survives the friction between services because all of them signed it. The acronym shows up in airborne operations, joint personnel recovery, and any other domain where the services have to operate against a common standard.

Air Force Manual (AFMAN) — a directive Air Force publication that provides detailed procedural instructions for accomplishing a specific task or operating a specific system, sitting alongside the AFI series with similar regulatory force but typically more technical and procedural in nature (e.g., AFMAN 31-201 series for security forces, AFMAN 36-2032 for military recruiting).

"A directive Air Force technical or procedural manual — same force as an AFI."

AFMAN is the procedural and technical cousin of the AFI — same regulatory weight, but typically organized as a step-by-step how-to for a specific system, task, or career-field practice. The line between AFI and AFMAN gets blurry at the edges, but in general if an airman needs to know exactly how to perform a specific job task, the relevant AFMAN is where to look. AFMANs are also where service members find the long technical annexes that an AFI might cross-reference at a high level. To a senior NCO running a duty section, the AFMAN is the daily working reference; to an inspector, both AFI and AFMAN are mandatory and a unit can fail compliance against either.

The US Air Force major command, headquartered at Wright-Patterson Air Force Base, Ohio, responsible for the research, development, test, evaluation, acquisition, sustainment, and depot maintenance of Air Force weapons systems and the management of Air Force test, range, and depot infrastructure across the Air Force enterprise.

"The Air Force major command for materiel research, acquisition, and sustainment."

AFMC is the Air Force counterpart to AMC — the materiel command that owns the depots (Tinker AFB Air Logistics Complex, Robins ALC, Hill ALC), the test infrastructure (Edwards AFB, Eglin AFB), and the major weapon system Program Executive Offices. AFMC structure changed in 2012 (the Air Force Sustainment Center, Air Force Test Center, Air Force Research Lab, and Air Force Life Cycle Management Center reorganization) to flatten the command. AFMC works closely with USAF Program Executive Officers and the Air Force Acquisition Executive structure.

Air Force Office of Special Investigations Manual (AFOSIMAN) — the AFOSI-specific publication series that provides procedural and operational guidance to Air Force Office of Special Investigations agents and units on conducting criminal investigations, counterintelligence operations, and protective service operations within the Air Force, sitting alongside the broader AFI and AFMAN series with AFOSI-specific applicability.

"The Air Force OSI manual series — internal procedural guidance for AFOSI agents."

AFOSIMAN is the AFOSI-internal publication suite that governs how OSI special agents actually conduct their craft — the criminal investigation procedures, the counterintelligence operations, the protective service details for senior officials and visiting dignitaries. The AFI series sets the broad regulatory framework that AFOSI operates inside; the AFOSIMAN series gets into agent-level tradecraft, evidence handling, source operations, and the procedural detail that the bag-toting special agent needs. To an airman outside AFOSI, the manual series is invisible; to an OSI agent or to a 71S (Special Investigations) officer, the relevant AFOSIMAN is the bible of how the job is done.

The major Air Force organization, headquartered at Joint Base San Antonio-Randolph, Texas, responsible for managing the careers, assignments, evaluations, promotions, and records of all Air Force and Space Force officer and enlisted personnel.

"The Air Force command running personnel management for the Air Force and Space Force."

AFPC is the Air Force counterpart to HRC and BUPERS — it runs Air Force assignment management, evaluation policy, promotion-board administration, and the personnel data systems behind it. Since the Space Force established its own service in 2019, USSF personnel management has been mostly handled through AFPC infrastructure during the transition, with USSF developing its own talent-management systems over time. AFPC at Randolph is the institutional center of gravity for AF career questions; the Career Field Managers in functional staff offices handle the field-specific decisions.

Air Force Policy Directive (AFPD) — the senior-most Air Force directive publication, signed by the Secretary of the Air Force or Chief of Staff, that establishes Air Force policy on a major functional area and provides the policy basis from which the supporting AFI and AFMAN publications are derived; the apex of the AFI/AFMAN/AFPD hierarchy.

"The senior Air Force policy publication — the apex above AFI and AFMAN."

AFPD is the top of the Air Force publication pyramid — a policy directive signed at the Secretary or Chief of Staff level that establishes Air Force policy on a major area (security forces, personnel management, intelligence, operations) and provides the policy basis that the implementing AFIs and AFMANs flow down from. AFPDs are short documents — usually 5-10 pages — and they don't tell an airman what to do day-to-day; the AFIs derived from them do that. But when a service-level policy fight happens, the AFPD is the document the lawyers and the Pentagon staffers go to first. To a wing-level airman, AFPDs are invisible until a SECAF or CSAF re-signs one and the implementing AFIs cascade into rewrite cycles.

The Air Force major command that commands the federal Air Force Reserve, organized to provide trained units and qualified individual airmen to augment the Regular Air Force in time of war or national emergency.

"The Air Force major command for the federal Air Force Reserve."

AFRC operates as a Major Command and as the Chief of the Air Force Reserve in dual-hat — the Commander of AFRC is also the Senior Reserve Component Advisor. The command flies a substantial inventory (fighters, tankers, transport, special operations, ISR) under the same operational reserve model as ANG. Headquarters at Robins AFB, Georgia. AFRC and ANG together represent the Air Force's reserve component; both have been heavily used since 2001.

A five-character code identifying an Airman or officer's job specialty in the Air Force and Space Force, equivalent to the Army/USMC MOS or the Navy rate-plus-NEC system.

"AFSCs are how the Air Force identifies and tracks job specialties."

An AFSC is more than a job code — it is the basis for every assignment, school slot, retraining decision, and bonus you receive. Cross-training (CJR / CAREERS retraining) is competitive and depends on shortages in target AFSCs. Knowing your CFETP (Career Field Education and Training Plan) is how you advance within an AFSC; not knowing it is how you stagnate.

Air Force Tactics, Techniques, and Procedures (AFTTP) — the Air Force publication series, often co-published as joint or multi-service TTP documents, that captures the detailed tactical-level "how-we-fight" procedures for specific Air Force or joint missions (e.g., AFTTP 3-1 series for combat employment, AFTTP 3-3 series for combat operations and training), sitting below the doctrinal AFDA/AFDP level and serving as the working tactical reference for aviators and operators.

"The Air Force TTP series — tactical how-we-fight below the doctrinal level."

AFTTP is where the tactical-level how-we-actually-fight gets written down for airmen — the AFTTP 3-1 weapons employment volumes that fighter, bomber, and ISR crews live inside, the 3-3 training-and-mission-employment volumes that drive currency and qualification, and the joint TTPs (often co-signed with other services) that govern things like joint personnel recovery or close air support. AFTTPs are typically classified or restricted-access — the unclassified summary lives in doctrine, the actual TTPs live behind the SIPR fence and on the aviator's flight planning system. To a wing weapons officer or a B-course instructor, AFTTPs are the daily reference; to a doctrine writer, AFTTPs are the empirical base that informs the next AFDP rewrite.

A Department of the Air Force innovation organization, headquartered at Air Force Research Laboratory, Wright-Patterson Air Force Base, with offices in Austin and elsewhere, that connects Air Force and Space Force operators with commercial and academic innovators through the AFWERX Challenge program, SBIR/STTR Open Topics, and partnership initiatives — a co-located service equivalent to DIU.

"The Air Force innovation organization connecting operators with commercial innovators."

AFWERX runs the most successful service-level SBIR Open Topic program — by some metrics putting more dollars into more small commercial firms than any other service innovation program. The AFWERX Challenge format poses operationally-derived problem statements to industry; AFWERX SBIR Phase II awards turn promising responses into prototypes. The transition-to-program-of-record challenge is the same one DIU faces: prototype success is the easier half. AFWERX programs serve as a feeder into Air Force and Space Force PEO portfolios when transitions work.

A program in which Reserve and National Guard members serve full-time on active duty in support of their Reserve Component, typically in administrative, training, recruiting, or readiness positions.

"Full-time active duty serving the Guard or Reserve."

AGR is full-time active duty pay, benefits, and obligations — but the chain of command is the Reserve Component, not the active force. Promotions, retention boards, and assignments follow Reserve-Component policies. AGR retirements are calculated on Reserve points formulas in some cases and active-duty formulas in others depending on the years served in each status. It is a distinct career track; understand which timeline you are on.

Automated Global Force Management Tool (AGT) — a Joint Staff information system that supports the global force management (GFM) process by tracking the assignment, allocation, and apportionment of joint forces to combatant commanders, automating the workflow for force generation orders, rotational force planning, and the Global Force Management Allocation Plan (GFMAP).

"The Joint Staff system that automates global force management and rotational planning."

AGT is the Joint Staff's answer to "how do we keep track of which units are deployed where, which are scheduled to deploy, and which COCOM gets which capabilities in the next ARFORGEN cycle" — the automated system that handles the global force management workflow, the GFMAP-related approvals, and the rotational force planning that drives every unit's deployment calendar. To a service force-providers section (FORSCOM G-3/5, NAVFOR plans), AGT is the tool the request-for-forces validation and the deployment orders move through; to a battalion S-3 who just got told "you're on the AGT cycle for the next FY," it's the upstream machinery that decided their next 18 months. The system has had multiple names over the years and remains the backbone of the GFM process.

The Army's online platform, operated through Human Resources Command, that implements market-based assignment processes by allowing officers (and increasingly other populations) to view available billets, communicate with gaining commands and assignment officers, indicate preferences, and complete the assignment matching cycle in a transparent, structured environment.

"The Army's online marketplace for officer assignment preferences and matching."

AIM 2 is the operationalization of Army talent-management reforms — replacing the older opaque assignment process with a marketplace where officers see available billets and gaining commands see candidate officers. The matching process (Army Talent Alignment Process, ATAP) runs on a recurring cycle (twice yearly for most populations). Officers compete by ORB content and assignment-officer dialogue; commands compete by billet attractiveness. The system is still maturing; outcomes vary by branch, year-group, and specific market. Career managers at HRC still play a significant role behind the marketplace.

Annual Joint Assessment (AJA) — the recurring joint-staff and combatant-command assessment process in which each geographic and functional combatant commander reports to the Chairman of the Joint Chiefs of Staff and the Secretary of Defense on the state of the command, force readiness, posture, mission accomplishment, and the resource and policy issues that affect future operations, feeding the broader Joint Strategic Planning System.

"The yearly combatant command assessment that feeds the joint strategic planning system."

AJA is the annual report card a combatant commander writes about their command — readiness, posture, mission risk, resource gaps — that goes up to the CJCS and SECDEF and feeds the next round of the JSPS (Joint Strategic Planning System) and the GFMAP. To a J-5 staff at a COCOM, the AJA is months of work, dozens of inputs, and a brief that the four-star personally walks through. To an action officer in OSD or the Joint Staff, the stack of AJAs is the raw material for trans-COCOM decisions about force allocation. The acronym is bureaucratic but the document is consequential — it's where a COCOM signals "I need more, I need different, or I am running out of capacity."

Allied joint doctrine (AJD) — the body of NATO-agreed doctrinal publications, developed under the NATO Standardization Office through the Allied Joint Operations Doctrine Working Group (AJODWG), that establishes common operational concepts, terminology, and procedures used by NATO and partner nations during multinational joint operations, parallel to but distinct from US joint doctrine.

"NATO's body of agreed-upon joint doctrine — the alliance version of US JPs."

AJD is the NATO answer to "where is the doctrine that an alliance of 30+ militaries actually agrees on" — the body of Allied Joint Publications (AJPs) that grew up alongside US joint doctrine and gets cross-walked against it every time the alliance updates a document. To a US officer working in a NATO billet, on the SHAPE staff, or in a NATO HQ, AJD is the working doctrinal vocabulary; JP references get translated to AJP references and vice versa. The Dictionary lists the umbrella term because joint doctrine and combined operations planning constantly reference AJD by name, and US staff officers need to recognize the alliance side of the bookshelf.

Allied joint publication (AJP) — a NATO-standardized doctrinal publication within the Allied joint doctrine series, developed and maintained by the Allied Joint Operations Doctrine Working Group (AJODWG), that establishes common operational doctrine across NATO nations; AJP-01 is the capstone (Allied Joint Doctrine), with subordinate AJPs covering operations, logistics, intelligence, and other functional areas paralleling the US JP series.

"NATO's numbered joint publication series — the alliance counterpart to US JPs."

AJP is the numbered NATO doctrinal series that runs in parallel to the US JP series — AJP-01 (capstone Allied joint doctrine), AJP-3 (operations), AJP-3.2 (land operations), AJP-4 (logistics), AJP-5 (planning), and so on. To a US officer working in a NATO HQ, an AJP is the doctrinal authority for what the alliance agrees on; to a US joint doctrine writer, the AJPs are the documents your JPs get cross-walked against to keep terminology aligned. The Dictionary lists the term because joint publications and combined operations planning routinely cite AJPs alongside JPs, and a staff officer needs to read both.

Available-to-load date (ALD) — the joint-doctrinal movement-planning data element that specifies the date a deploying unit's personnel and equipment will be available at the port of embarkation, ready for loading onto strategic lift (sealift or airlift), used by movement planners to build the time-phased force and deployment data (TPFDD) and to align lift assets against deployment requirements.

"The date a unit and its gear will be ready at the port to load onto strategic lift."

ALD is the single most-fought-over number in a unit's deployment timeline — the date the planners say your formation, your vehicles, and your CONEXes will physically be at the APOE or SPOE ready to load. If the ALD is wrong, the TPFDD gets blown up downstream; if the unit slips its ALD, the ship sails without them or the next chalk gets bumped. To a brigade S-4, a UMO, or a transportation officer, the ALD is the milestone they manage to with a hawk-eye, because slipping it has cascade effects across the whole movement plan. The Dictionary lists it because it's a foundational TPFDD data element — every deploying unit lives inside the date they put in this field.

Alert order (ALERTORD) — a standardized joint message and crisis-action planning order, issued by the President, Secretary of Defense, or Chairman of the Joint Chiefs of Staff through the National Military Command Center, that directs supported and supporting combatant commanders to begin or continue detailed planning for a possible operation, signaling a higher level of preparation than a warning order but short of a deployment order.

"The joint planning order that tells commanders to start serious planning for a possible operation."

ALERTORD is the second step in the joint crisis-action planning ladder — after the WARNORD says "something might happen, start thinking about it," the ALERTORD says "the boss is taking this seriously, build the detailed plan." It's issued through the NMCC, signed at the SECDEF/CJCS level, and triggers a specific set of planning products and force-readiness reviews at the supported COCOM. To a joint planner in a COCOM J-5 or a service-component plans shop, an ALERTORD means the next several weeks are written off — the staff goes into 24/7 planning cycle, OPLANs get pulled off the shelf, and the TPFDD gets refined. The acronym is procedural but the operational tempo it triggers is significant.

Acquisition, logistics, and technology (ALT) — the consolidated functional area, most prominently in the Army (Assistant Secretary of the Army for Acquisition, Logistics, and Technology — ASA(ALT)), that combines the acquisition workforce, the logistics enterprise, and the science-and-technology portfolio under a single senior civilian or military principal responsible for the equipping and sustainment of the force.

"The combined acquisition/logistics/technology functional area — the bucket above PEOs."

ALT is the umbrella the Army uses for its acquisition workforce, its logistics enterprise, and its S&T portfolio — embodied in ASA(ALT), the Senate-confirmed civilian under whom every PEO (Program Executive Office), the Army Materiel Command, and the science-and-technology research line ultimately roll up. To an Army officer in the acquisition corps (FA51), ALT is the world they live in; to a PEO project officer, the ALT principal is the senior who signs off on milestone decisions. The other services use slightly different terminology (Navy uses ASN(RDA), Air Force uses SAF/AQ), but ALT is the established Army shorthand. The acronym shows up in every Army equipping discussion, every POM cycle, and every congressional defense subcommittee mark.

The 2017 law (Veterans Appeals Improvement and Modernization Act, Pub. L. 115-55) that restructured VA appeals into three "lanes": Higher-Level Review, Supplemental Claim, and Board appeal. Effective February 19, 2019.

"A modernized appeals system designed to give veterans faster decisions and more options."

The AMA system is genuinely faster than the legacy "Statement of the Case → Form 9" path it replaced — but only if you choose the right lane for your case. Higher-Level Review (HLR) reviews the same evidence with a senior reviewer; Supplemental Claim adds new and relevant evidence; Board appeal goes to a Veterans Law Judge. Different lanes have different timelines and different downstream options. Strategy here matters.

The US Army major subordinate command of Army Materiel Command, headquartered at Redstone Arsenal, Alabama, responsible for the materiel acquisition, sustainment, supply chain management, and depot maintenance of US Army aviation systems, missile systems, and unmanned aircraft systems.

"The Army materiel command for aviation, missiles, and unmanned aircraft systems."

AMCOM at Redstone is the institutional home of Army aviation and missile sustainment — the Aviation Center of Excellence (training) is at Fort Novosel, but the materiel-acquisition and life-cycle-sustainment authority sits at Redstone. The command covers everything from the AH-64 Apache and UH-60 Black Hawk through the Patriot missile system to the RQ-7 Shadow and similar unmanned platforms. Corpus Christi Army Depot (helicopter depot) and Letterkenny Army Depot (missile depot) sit within AMCOM's sustainment chain. Aviation Class IX flow runs through AMCOM's wholesale layer.

Agency mission-essential task list (AMETL) — the mission-essential task list developed by a DoD agency or field activity (e.g., DLA, DCMA, DTRA) that identifies the mission-essential tasks (METs) the agency must be able to perform to meet its title 10 and assigned-mission obligations, paralleling the unit-level METL used by operational forces and the joint mission-essential task list (JMETL) used by combatant commands.

"The MET list for a DoD agency — parallel to a unit METL but for a combat support agency."

AMETL is the agency-level version of the METL every operational unit publishes — the same "what we have to be able to do" task list, but written by and for a combat support agency like DLA, DTRA, DCMA, or DISA instead of a brigade or wing. The AMETL drives the agency's training, exercise participation, and readiness reporting in DRRS-Strategic, just like a unit METL drives DRRS-Army or DRRS-Marine Corps. To a joint planner who needs to know whether DLA can actually surge fuel into a theater, or whether DCMA can ramp up contractor oversight in a contingency, the AMETL is the source document; to an agency staffer, the AMETL is the document their training plan and budget submission have to support.

The complete official personnel record of an Army officer or enlisted member, maintained electronically by Human Resources Command, containing the documents (orders, evaluations, awards, schools, qualifications, administrative actions) that constitute the soldier's official record, replacing the previous Official Military Personnel File (OMPF) system in 2014.

"The complete official Army personnel record, maintained electronically by HRC."

AMHRR is the official record (replacing the older OMPF designation) — the document repository that promotion boards review, that supports record corrections through ABCMR, and that controls administrative actions. Officers and senior NCOs should periodically review their own AMHRR through HRC online services to verify that documents are filed correctly. Records errors are common — missing evaluations, miscoded awards, schools not posted — and the time to catch them is before a board, not after. Permanent record correction requires a formal application.

Automated Mail Postal System (AMPS) — the Department of Defense electronic system used by military post offices (MPOs) and aerial mail terminals (AMTs) to process, track, and account for official and personal mail moving through the Military Postal Service Agency network, including registered, accountable, and APO/FPO traffic.

"The DoD postal system that tracks military mail from APO to recipient."

AMPS is the software backbone of the Military Postal Service — the system that scans the APO/FPO bag tags, tracks the registered and accountable mail, and tells the postal clerk at Camp Humphreys or RAF Lakenheath which box your package is sitting in. To a deployed soldier or sailor waiting on a package from home, AMPS is invisible but everywhere; to a postal clerk (MOS 42R, NEC PS, or AF 8M0X1), it's the whole job — scanning, sorting, and answering "where is my mail" questions on a 12-hour shift. When the system goes down, mail backs up in pallets at the AMT, the FPO line stretches around the block, and the unit's morale dips a notch.

Aerial Mail Terminal (AMT) — a Military Postal Service Agency facility at a major aerial port that receives, sorts, and forwards official and personal mail moving by air to and from overseas military post offices (MPOs), serving as the air-mobility chokepoint for the APO/FPO mail network.

"The aerial port mail facility that sorts and forwards deployed-unit mail."

AMT is the postal yard inside the aerial port — pallets of mail bags piled to the ceiling, postal clerks running flat-sorters and bag scanners, and a 24-hour rhythm of in-bound and out-bound mail flights. Every package you ever sent to a deployed family member passed through an AMT (the big ones at JFK, San Francisco, Ramstein, Dubai), got rebagged onto the next chalk, and rode an AMC bird to the downrange MPO. To a postal clerk on the receiving end, the AMT is "the place the pallets come from"; to families back home, it's invisible. When mail throughput collapses — usually around Christmas and at the start of a major deployment — the AMT is where the backlog physically lives.

The Air National Guard of the several states, territories, and the District of Columbia — a reserve component of the Air Force that maintains a dual federal-state status, organized under state authority for state missions and federalized for Air Force missions under specified authorities.

"The Air Force's state-organized federal reserve component."

ANG flies and maintains a substantial share of the Air Force inventory — fighters, tankers, transport, ISR, special operations, and space — under the same dual-status model as ARNG. ANG fighter units perform much of the day-to-day CONUS air sovereignty alert mission under NORAD. The state mission tilts more toward Title 32 air-mobility, airlift, and aerial firefighting; the federal mission tilts toward overseas deployments and CONUS air defense.

American National Standards Institute (ANSI) — the private, non-profit organization that coordinates the development and use of voluntary consensus standards in the United States and represents U.S. interests in international standards organizations; ANSI-accredited standards are referenced extensively in DoD contracting, safety, and interoperability documentation.

"The U.S. civilian standards body whose specs DoD references for safety and interoperability."

ANSI shows up in military contracts and safety documents constantly — ANSI Z87.1 for ballistic eye protection, ANSI/ASSE Z359 for fall protection, ANSI standards for electrical safety, lifting equipment, hearing protection. To a unit safety NCO or a contracting officer, "ANSI-compliant" is the magic phrase that tells you a piece of commercial gear meets a referenced standard the Army or Air Force agreed to honor. ANSI is not a DoD organization — it's a civilian consensus body — but DoD references hundreds of its standards because rewriting them all as MIL-SPECs would be a waste. When somebody asks if your safety glasses are "rated," they mean ANSI-rated.

An analytic comparison of the operational effectiveness, suitability, and life-cycle cost of alternative materiel solutions intended to satisfy a validated capability gap, conducted during the Materiel Solution Analysis phase and supporting the Milestone A decision, typically led by an independent Cost Assessment and Program Evaluation (CAPE) or service-equivalent organization.

"A study comparing material solution options for a validated capability gap."

The AoA is the structured comparison that follows ICD validation — analysts (typically from CAPE or a service cost-analysis organization) compare multiple potential solutions, including the "status quo" alternative, on effectiveness and life-cycle cost. The AoA result informs the Milestone A decision and the path into the Technology Maturation and Risk Reduction phase. AoAs that are tightly scoped to a preferred solution are a well-known pattern; AoAs that genuinely consider alternatives have a tradition of surfacing surprises about which solutions are most cost-effective.

A US Army program, conducted in cooperation with the Navy Joint Oil Analysis Program (JOAP), that analyzes lubricating oil samples from Army equipment (engines, transmissions, hydraulic systems, gearboxes) to identify wear patterns, contamination, and incipient failures through spectrometric, ferrographic, and physical-property tests.

"An Army oil-analysis program detecting wear and contamination through sample testing."

AOAP is the predictive-maintenance backbone for Army engines and gear systems — sampled lubricants are sent to JOAP laboratories, analyzed for metallic wear particles and physical-property changes, and produce condition trending that lets units catch problems before catastrophic failure. The program is mature, scalable, and one of the cleaner condition-based maintenance success stories. Effective AOAP participation is one of the lower-cost actions a unit can take to drive readiness; ignored AOAP recommendations is one of the recurring patterns in catastrophic engine failures.

A Department of Defense acquisition pathway, governed by DoDI 5000.74, for the acquisition of services rather than goods — including professional services, knowledge-based services, electronics and communications services, equipment maintenance services, facility-related services, and other service categories — with policy emphasis on performance-based outcomes and competitive sourcing.

"The DoD acquisition pathway for service contracts rather than physical goods."

Acquisition of Services covers the enormous DoD spend on contracted services — far larger than many people realize, often exceeding hardware acquisition spending in aggregate. The pathway emphasizes Performance Work Statements (PWS) over traditional SOW, structured competition, and outcome measurement. The pathway has its own decision authorities and review process. Areas under intense scrutiny include service-contract conversion (when a contracted function should be performed by federal civilians or military instead), inherently governmental function tests, and small-business utilization.

Animal and Plant Health Inspection Service (APHIS) — the U.S. Department of Agriculture agency responsible for protecting the health of U.S. agriculture from foreign pests and diseases, regulating the importation of animals and plants, and conducting inspections of personnel, equipment, and cargo returning from overseas; APHIS coordinates closely with DoD on inspection of redeploying forces and equipment.

"The USDA agency that inspects your gear for foreign dirt and pests when you redeploy."

APHIS is the agency every redeploying soldier and Marine has met at the wash rack — the USDA inspectors who certify that your boots, your vehicles, your containers, and your gear are clean enough to come back into the United States without bringing foreign soil-borne pests or diseases. The standard is strict: every speck of mud has to go before APHIS will release the load. To a unit redeploying from Europe, the Middle East, or anywhere with foot-and-mouth or African swine fever risk, the APHIS inspection is the gate between "in country" and "on the ship home" — and a failed inspection sends you back to the wash rack at 0200. The interagency relationship matters: APHIS and the U.S. Customs and Border Protection inspection at the SPOD are the choke points between contingency and the homeland.

Army Post Office (APO) — a U.S. Military Postal Service Agency post office located outside the United States supporting Army (and joint) personnel overseas, with addressing using APO AA (Americas), APO AE (Europe), or APO AP (Pacific) and a five-digit ZIP code; counterpart designations are FPO (Fleet Post Office) for Navy/Marine and DPO (Diplomatic Post Office) for State Department.

"Your overseas military mailing address — APO AE/AP/AA plus a five-digit ZIP."

APO is the mailing address every overseas soldier and airman has memorized — APO AE 09xxx for Europe, APO AP 96xxx for the Pacific, APO AA 340xx for the Americas, plus the five-digit ZIP that routes the mail to the right MPO. To a deployed troop, APO is how the wife sends the care package, how the supply system pushes the small Class IX part that didn't rate AMX, and how the IRS finds you for your refund. The system is older than the email account on your CAC and still moving real mail every day. Marines and sailors get FPO instead — same plumbing, different prefix. Families learning to send a deployment care package learn three things: APO/FPO, customs form, and "no liquids."

The total procurement cost of an acquisition program divided by the planned procurement quantity, expressed in then-year and base-year dollars and reported on each MDAP's Selected Acquisition Report, used as one of the primary cost metrics for tracking program cost growth and for Nunn-McCurdy breach analysis.

"The average procurement cost per unit of an acquisition program."

APUC is one of the two cost-per-unit metrics that drive Nunn-McCurdy tracking — total procurement cost (the buys, not the R&D) divided by planned quantity. When APUC growth exceeds the Nunn-McCurdy thresholds (15% for "significant," 25% for "critical" against the current baseline, with higher thresholds against the original baseline), the breach machinery activates. APUC growth comes from cost overruns, quantity cuts (the same total cost spread over fewer units), and inflation; the breach calculation makes the distinction important.

A US Army force-generation model, in effect from approximately 2006 through 2016, that organized Army active and reserve component units into a structured cycle of reset, train/ready, and available phases, intended to provide predictable deployment availability and dwell time — superseded by the Sustainable Readiness Model (SRM) and subsequent updates as Army force-management approach evolved.

"The 2006-2016 Army cycle model organizing units into reset, train, and available phases."

ARFORGEN was the OEF/OIF-era response to the unsustainable operational tempo of the early war years — a structured cycle (reset, then train/ready, then available for deployment) that promised predictability and dwell time. The model had real successes (deployment forecasting improved) and real limits (it presumed steady-state demand that didn't always match reality, and it strained at peak demand periods). ARFORGEN was retired in favor of Sustainable Readiness around 2016 as the Army transitioned to a "be ready always" rather than "rotate through readiness" approach. The vocabulary persists in some operational contexts.

The Army National Guard of the several states, territories, and the District of Columbia — a reserve component of the Army that maintains a dual federal-state status, organized under state authority for state missions and federalized for Army missions under specified authorities.

"The Army's state-organized federal reserve component."

ARNG units belong to governors under Title 32 USC for state missions (hurricane response, civil disturbances, wildfires) and can be federalized under Title 10 for Army missions. The dual-status is fundamental to Guard identity — soldiers swear oaths to both the United States and the state they serve. Over half a million soldiers serve in the ARNG across the fifty states, three territories, and the District of Columbia; deployed ARNG units have been a major share of the operational Army since 2001.

A two-character code appended to an MOS that identifies an additional specialized skill (more granular than an SQI), typically awarded after specific schools or training.

"ASIs identify additional specialized skills within an MOS."

ASIs are how the Army tracks the niche skills it actually needs to fill billets — language, equipment-specific qualifications, special programs. An ASI can make you the only qualified Soldier in your unit for a specific billet (career-helpful) or pull you into the same billet at every assignment (career-stalling, depending on the ASI). Be deliberate about which ones you pursue.

The list of repair parts, consumable items, and other supply items authorized for stockage at a Supply Support Activity (SSA, typically at the brigade-support-battalion level for an Army brigade combat team), based on the supported units' demand patterns and the operational requirements for forward stockage to reduce response time.

"The SSA-level repair-parts stockage authorized for forward distribution."

ASL is the next layer in from PLL — the brigade-level SSA stocks items that the supported units' PLLs don't hold but that have enough demand to justify forward stockage. When a PLL doesn't have a part, the unit orders it from the SSA, which fills from the ASL when stocked. ASL composition reflects the brigade's mission set, equipment mix, and historical demand patterns. ASL accuracy, completeness, and turn rate are major readiness-driver metrics; an inaccurate or incomplete ASL produces "I have to order it from depot" experiences that drive mission-capable timeline issues.

The Army's structured talent-management process that operates through the AIM 2 platform, running on a recurring cycle to match officers and gaining commands, allowing both parties to rank-order preferences and using a market-clearing algorithm to produce assignments — replacing the older centrally directed assignment process for most populations.

"The Army's structured talent-matching process running on AIM 2."

ATAP is the process; AIM 2 is the platform. The market runs on a recurring cycle (formerly twice yearly for active officers; cycle structure has evolved); officers indicate preferences, gaining units indicate preferences, and an algorithm produces matches. The shift away from centrally directed assignments was a major cultural change for the Army — assignment officers now serve as advisors and constraint-managers rather than as decision-makers. Officers who actively engage with gaining commands during the cycle generally achieve better outcomes than those who treat ATAP as a passive process.

Allied Tactical Publication (ATP) — a NATO-standard tactical-level publication that establishes common tactics, techniques, and procedures for allied land, maritime, or air forces. Army Techniques Publication (ATP) — the US Army's techniques-level doctrinal publication series, below field manuals (FMs) in the doctrinal hierarchy, providing the specific techniques and procedures by which Army units execute the doctrine codified in FMs.

"Either a NATO allied tactical pub, or an Army techniques pub — context tells you which."

ATP is one of those acronyms where the meaning depends entirely on who is talking — when a US Army officer says "go read the ATP," they mean an Army Techniques Publication (ATP 3-21.8 on the infantry platoon and squad, ATP 3-09.32 for JFIRE, ATP 6-22.1 on AARs, etc.) in the layered ADP/FM/ATP doctrinal hierarchy. When a NATO planner says ATP, they mean an Allied Tactical Publication (ATP-3.2.1, ATP-3.4.4.1, etc.) ratified by the NATO Standardization Office. Both flavors live on the shelf next to JPs, ADPs, FMs, and STANAGs in any serious shop — and a smart staff officer learns to ask "which ATP?" before pulling the wrong one off the shelf. The Dictionary lists both because both meanings appear in joint and combined doctrine.

Army Tactics, Techniques, and Procedures (ATTP) — a legacy Army doctrinal publication category, used during the doctrine 2015 transition period to consolidate older field manuals and TRADOC pamphlets into combined tactics/techniques/procedures documents; subsequently largely superseded by the layered ADP/ADRP/FM/ATP structure but the acronym still appears in older orders, references, and historical documents.

"The legacy Army doctrinal series that bridged the old FMs and the modern ATP/ADP layered system."

ATTP is a doctrinal artifact you will still see on the shelf and in references — a transitional publication category the Army used around 2010-2015 to bridge between the old huge field-manual library and the modern layered ADP/ADRP/FM/ATP structure. ATTP 3-06.11 (Combined Arms Operations in Urban Terrain) is the one a lot of NCOs remember. Most ATTPs have been rescinded or rolled forward into ATPs by now, but legacy OPORD references, professional military education reading lists, and citations in older studies still point to them. To a current Army officer or NCO, ATTP shows up as a "wait, is that still current?" moment — usually the answer is no, and the modern ATP/FM equivalent is what you actually want.

A joint resolution of Congress, typically responding to a specific national-security circumstance, that authorizes the President to use the United States Armed Forces in a particular manner or against a particular adversary — distinct from a constitutional Declaration of War, though with similar substantive effect for the operations the AUMF authorizes.

"A congressional authorization for specific military use, distinct from a Declaration of War."

AUMF is the congressional authorization that has substituted for formal Declarations of War in the post-WWII era. The 2001 AUMF (PL 107-40) authorized force against those responsible for the 9/11 attacks and continues to be cited as authority for counterterrorism operations against affiliated organizations decades later. The 2002 Iraq AUMF (PL 107-243) authorized the Iraq invasion. AUMFs do not have automatic sunsets; the 2001 AUMF's continued use to justify operations against organizations not in existence in 2001 has been the subject of recurring congressional debate but no repeal. New AUMFs (or amendments / repeals of existing ones) are the central legal question for any major new military operation.

Berthing and Loading Schedule (BALS) — a sealift and amphibious operations planning product that establishes the sequence and timing for ships to berth at a port or anchorage and to load personnel, equipment, and cargo, used to synchronize port-side reception, marshalling, and loading operations during deployments, redeployments, and amphibious operations.

"The port-side schedule that sequences which ships berth when and load what."

BALS is the port-operations equivalent of an air mobility flow plan — the document that says "USNS Bobo berths at Pier 4 at 0600 on D+2, loads the cavalry squadron between D+2 and D+4, sails D+5; USNS Watson follows on the same pier" for an entire deployment. To an SDDC battalion or an SPOE/SPOD movement team at Beaumont, Charleston, or Pohang, the BALS is the working schedule for weeks; a missed BALS slot costs millions of dollars in port demurrage and weeks of downstream schedule slip. To an amphibious planner, BALS is part of the embarkation cycle that determines whether the MEU sails on time. The acronym is a logistics-planner artifact that rarely surfaces outside the transportation community but governs the rhythm of every major sealift deployment.

A punitive discharge that can only be imposed by a special or general court-martial. Reflects a federal criminal conviction; severely limits VA benefits.

"A discharge handed down by court-martial for serious misconduct."

A BCD is a federal conviction with lifelong consequences: typically no VA disability or healthcare except for service-connected conditions, federal firearms restrictions in most jurisdictions, and major employment barriers. Upgrade requests can go to DRB (within 15 years) and BCMR. The conviction itself follows you regardless of any discharge characterization upgrade.

A civilian-led board within each service department empowered to correct errors or remove injustices in a military record. The highest administrative remedy short of federal court.

"A way to fix mistakes in your military record after the fact."

BCMR is your remedy when no other process can fix what is in your file. Each service has its own (ABCMR Army, BCNR Navy/USMC, AFBCMR Air Force). Filing windows can be three years from discovery, but boards routinely consider untimely cases for good cause. Free help is available from VSOs and law school veterans clinics. Lawyers help — boards take well-organized petitions more seriously.

The Navy and Marine Corps civilian-led board for correcting errors and removing injustices in Naval Service records.

"The Navy and Marine Corps record-correction body."

Same general framework as ABCMR. Filing typically uses DD Form 149. Free assistance is available from Marine Corps and Navy legal assistance offices and from VSOs. Strong petitions present the timeline, the alleged error or injustice, the evidence, and the specific relief requested — boards are not investigators; they decide on the record submitted.

A formal challenge by an offeror or interested party to a procurement decision — usually a contract award or proposed award — filed at the agency, GAO, or the US Court of Federal Claims.

"A formal way for offerors to challenge procurement decisions."

A protest is a serious step. The grounds matter (improper evaluation, biased evaluation, agency conducted unauthorized discussions, the awardee did not meet a stated requirement) — generic disagreement is not a protest. GAO's timelines are tight (10 days from debrief in most cases). Protests reshape procurements: agencies often take corrective action mid-protest rather than litigate, recompeting or reevaluating in ways favorable to the protester.

A policy framework, established for the Reserve Component, that sets the ratio of mobilized time (Boots on Ground or BOG) to home-station time (Dwell) — for example, a 1:5 ratio means one year mobilized followed by five years at home before the next mobilization — used to manage the operational tempo and sustainability of the reserve force.

"A policy ratio managing reservist mobilization frequency."

BOG:Dwell was formalized after the early post-9/11 years showed unsustainable Reserve Component mobilization rates. The current DoD goal is 1:5 for the Reserve Component (one year mobilized, five years dwell) — the active component goal is 1:3 by parallel construction. Actual ratios vary by component and specialty. Falling below the BOG:Dwell ratio triggers waiver requirements and visibility at OSD level; it is the policy lever for limiting how heavily DoD can lean on the reserve force.

The provision of facilities, services, and infrastructure support to an installation, including utilities, environmental services, security, fire and emergency services, public works, and family and quality-of-life services — as defined in the DoD Dictionary of Military and Associated Terms.

"The enterprise of services that keeps a military installation running."

BOS is the bucket that holds every installation service that isn't directly the operational mission — utilities, custodial, security, fire, environmental, family services, the commissary and exchange interface, the IT infrastructure, the lawn outside the headquarters. For a soldier at brigade level, BOS is invisible until it breaks (water main on the WLC barracks, power out on the COF, a snow day that doesn't actually close anything). For a garrison commander, it's most of the job — the garrison directorate (DPW, DES, DFMWR, DHR) is largely a BOS-delivery organization. The contracting structure underneath BOS at a joint base is the BOS-I (BOS-Integrator) arrangement, which is why that distinction matters in the next entry.

The designated Service or component responsible for integrating and providing base operating support services across the tenant units of a joint base or shared installation, including coordination of contracts, services, and infrastructure across multiple Services and other DoD components, as defined in the DoD Dictionary of Military and Associated Terms.

"The lead Service that runs BOS for a joint base with multiple tenants."

BOS-I is the designation that answers "which Service runs the garrison" at a joint base. Joint Base Lewis-McChord (Army BOS-I for both McChord AFB and Fort Lewis), Joint Base San Antonio (Air Force BOS-I), Joint Base Pearl Harbor-Hickam (Navy BOS-I), Joint Base Andrews (Air Force BOS-I), Joint Base Anacostia-Bolling (Navy BOS-I) — each one was a 2005 BRAC product where two installations merged under one BOS-I Service. For tenant units, BOS-I matters because the contracting authority, the housing policy, the gate guard standard, the recycling rules, and the snow-removal SLA all come from the lead Service's playbook — even if you're an Air Force squadron sitting on an Army-led joint base. The friction is real; the doctrine is the framework that resolves it.

A simplified method of filling anticipated repetitive needs for supplies or services by establishing "charge accounts" with qualified sources of supply.

"A standing arrangement for small, repetitive purchases."

BPAs are streamlined and fast — they fill the gap between Government Purchase Card buys and full IDIQs. They are not contracts (despite the name) until a call is placed against them. Misuse is a chronic audit finding: ordering officials confusing BPAs with sole-source authority, or placing calls that exceed simplified-acquisition thresholds. Know the threshold; document the competition; do not split orders to evade thresholds.

The foundational portion of a joint operation plan that describes the operational concept, assumptions, mission, commander's intent, concept of operations, and command relationships — to which subsequent annexes, appendices, tabs, and exhibits attach to provide the full operational document, as defined in the DoD Dictionary of Military and Associated Terms and JP 5-0.

"The core narrative section of a joint operation plan, before all the annexes."

BPLAN is the prose-and-graphics core of an OPLAN — the actual narrative of "what we are going to do, why, with what assumptions, and how" — to which the alphabet soup of annexes attaches (Annex A Task Organization, Annex C Operations, Annex D Logistics, Annex E Personnel, and so on). For a staff officer in a J3, J5, or J33 future-operations cell on a combatant command staff (INDOPACOM, EUCOM, CENTCOM, AFRICOM, SOUTHCOM, NORTHCOM, STRATCOM, CYBERCOM, SPACECOM, TRANSCOM, SOCOM), most of the JOPP cycle is about producing or updating a BPLAN and the annexes that hang off it. JPP, Mission Analysis, COA Development, COA Comparison — all roads lead to a published BPLAN with annexes that subordinate commands branch into their own supporting plans.

The major Navy organization, headquartered at Millington, Tennessee, responsible for managing the careers, assignments, evaluations, promotions, and records of Navy officer and enlisted personnel, operating through detailer offices organized by rate and designator that manage the assignment process.

"The Navy organization that runs personnel management and detailing."

BUPERS at Millington is the Navy counterpart to HRC and AFPC — the institutional home of detailers (the assignment officers for each rate and designator), the Bureau of Naval Personnel Online (BUPERS Online, the personnel-data portal that Navy members use), and the policy promulgation functions. The detailer call is a Navy career institution — sailors negotiate orders with their detailer on a recurring cycle, and the strength of the relationship affects assignment outcomes within the constraints of needs-of-the-Navy. The Career Counselors at unit level help with the BOL interactions.

The administrative tribunal within the VA that decides appeals of regional office decisions. Composed of Veterans Law Judges (VLJs) who issue final agency decisions. Further appeal is to the US Court of Appeals for Veterans Claims.

"The independent board that hears veterans' appeals."

BVA appeals can take a year or more depending on docket type (direct review, evidence submission, hearing). Hearing requests add time but allow oral testimony. Hire counsel for BVA cases when possible — accredited attorneys can charge fees only on past-due benefits if they win, so the financial risk is bounded. The BVA grant rate is meaningfully higher when claimants are represented by attorneys versus unrepresented.

The complete VA file containing a veteran's service treatment records, claim documents, decisions, exam results, and correspondence. Now maintained electronically as the eFolder.

"Your complete VA record, organized for review."

Your C-File is your case. Request a complete copy as a Privacy Act / FOIA request — free, takes time, but worth it. Read it. Mistakes (missing service records, wrong dates, lost lay statements) are common and only get corrected when someone notices. Carrying a complete copy to every VA appointment and appeal is the difference between citing your evidence and hoping it is on file.

US Government and contractor personnel who are authorized to accompany the US armed forces in contingency operations — generally falling under contractual provisions, deployment policies, and (where applicable) status-of-forces agreements that define their rights, responsibilities, and legal status in the operational area, as defined in the DoD Dictionary of Military and Associated Terms and DoDI 3020.41.

"The category of contractors authorized to deploy with US forces in a contingency."

CAAF is the formal status that defines contractor deployment alongside US forces in a contingency — covering everything from KBR cooks running DFACs at Bagram and Camp Arifjan, to the LOGCAP and AFCAP III contractors maintaining base operations, to the technical-rep field service engineers keeping specific weapons systems running, to language interpreters embedded with maneuver units. CAAF status drives the SRP requirements, the GTC card requirements, the CAC issuance, the personnel-accountability reporting (SPOT-ES), the medical clearance, and the legal-jurisdiction picture (MEJA, UCMJ Article 2 in declared war, host-nation status under SOFA). The DoDI 3020.41 framework is the policy backbone; the CCMD-specific OPORD or FRAGO sets the theater-specific rules. For a uniformed service member working alongside CAAF personnel, knowing the framework matters for command authority, accountability, and rules-of-conduct enforcement.

A DoD-issued smart card that serves as identification, building access, and the cryptographic credential for accessing DoD networks and systems.

"Your CAC is your military ID and your computer login — one card, everywhere."

Your CAC will fail at the worst possible moment. The chip wears out, the photo dates, and the CAC office at most installations is open limited hours with a long wait. If yours expires or breaks during a PCS, plan for a half-day at the new ID card facility before you can sign onto a DoD computer or pick up your dependents' new IDs.

A five-character alphanumeric code assigned by the Defense Logistics Agency to identify a specific entity (commercial company, government activity, or non-profit) doing business with the US government.

"A unique code identifying contractors and government activities."

CAGE codes show up on contracts, item identification plates, and inside catalog records as a source-of-supply identifier. When you are troubleshooting a part with the contracting officer or DLA — "who manufactured this serial number" — the CAGE code resolves the question. Contractors register through the SAM.gov system; foreign entities get NCAGE codes through the equivalent NATO process.

Contractor-Acquired, Government-Owned (CAGO) — a property classification under the Federal Acquisition Regulation and DoD contracting policy applied to material a contractor purchases under contract authority but to which legal title passes to the United States Government; the contractor manages the property under the contract's government property clauses and is accountable for it on government property reports.

"Stuff a contractor buys with contract money but the government actually owns."

CAGO is the property-accountability category that catches a lot of GWOT-era kit — the laptops, the test equipment, the spare engines, the office furniture a contractor bought on a government contract and then has to report on as government property until it's turned in, transferred, or disposed of. To a uniformed property book officer or a contracting officer's representative, CAGO is the line in the contract that says "remember, this isn't the contractor's stuff, it's ours" — and the audit risk that comes with it. To the contractor employee on the ground, CAGO is why the laptop has the yellow government property sticker on it and why the contractor PM cares so much when somebody loses a power supply. The category exists because the alternative — pretending the government doesn't own things contractors bought for it — got the Pentagon into trouble multiple times.

The US Army organization at Fort Leavenworth, Kansas — a directorate of the Combined Arms Center — that captures, analyzes, and disseminates Army operational and training lessons learned through observation, post-exercise analysis, and post-deployment debriefs, publishing handbooks, newsletters, and bulletins for the Army at large.

"The Army's lessons-learned organization at Fort Leavenworth."

CALL at Fort Leavenworth has been the institutional home of Army lessons learned for decades — observers travel to CTCs, deployments, and exercises, capture observations, and produce publications (the CALL Handbook series, newsletters, bulletins) that the Army can use. CALL feeds JLLIS at the joint level. The publications range from tactical-level handbooks (e.g., dismounted patrol techniques) to broader operational analyses. The challenge — common to all lessons-learned programs — is institutional adoption beyond the units immediately exposed to the lesson.

CAT has three principal DoD Dictionary readings: Category (used in classifying personnel, equipment, or threats by tier); Civil Affairs Team (the company-level four- to five-Soldier tactical CA element that engages with the civil populace at the maneuver-battalion level); and Crisis Action Team (the temporary headquarters cell stood up to manage a specific crisis or no-notice contingency, supporting the commander's decision cycle and external coordination).

"Three meanings — a personnel/threat category, a four-soldier Civil Affairs team, or a crisis-response staff cell."

CAT is one of the DoD Dictionary entries that collapses three unrelated meanings into one slug and forces the reader to disambiguate by context. In personnel and equipment talk, CAT is a tier ("Category 1 / 2 / 3" — used for personnel security, mobilization tiers, weapon-system criticality). In Civil Affairs talk, a CAT is the four-to-five-soldier tactical CA team attached to a maneuver battalion — the team that walks into the village mayor's office, runs the assessment, runs the engagement. In a crisis, a CAT is the temporary staff cell a higher headquarters stands up — the 24/7 watch with reps from every staff section, the SECDEF gets briefed off the CAT's products during a no-notice contingency. Three meanings, one slug, and a tip of the hat to the writer who has to pick the right reading from context.

Customs and Border Clearance Program (CBCP) — a Department of Defense program that establishes policy, procedures, and training for the customs and agricultural clearance of US military personnel, equipment, and cargo redeploying to or transiting through the United States and host nations; ensures compliance with US Customs and Border Protection, US Department of Agriculture, and host-nation requirements during military movements.

"The DoD program that gets units, gear, and mail through customs without breaking laws or fields."

CBCP is the program nobody thinks about until a unit is redeploying and discovers that the trailers full of CONEX boxes can't enter the United States until somebody certifies the mud has been pressure-washed off the vehicles and the wood pallets are heat-treated. The program trains military customs inspectors, sets the procedures for the redeployment customs lane at the SPOD or APOD, and coordinates with CBP, USDA APHIS, and host-nation customs authorities so that a brigade rotating home doesn't bring back the agricultural pests of wherever it deployed to. Most service members see CBCP exactly twice — at outbound customs clearance and at inbound customs clearance during a deployment cycle. Those who run installation customs cells or who serve as unit customs inspectors live in it.

Contingency Basing Executive Council (CBEC) — an OSD-led senior body that provides DoD enterprise oversight, policy guidance, and resourcing direction for the establishment, management, transfer, and closure of contingency bases across the combatant commands; coordinates standards for base operating support, life support, and contingency construction.

"The OSD senior council that sets the rules for how contingency bases get stood up, run, and closed."

CBEC is the OSD-level body that exists because the GWOT-era experience of building 800-plus bases in Iraq and Afghanistan, running them for years, and then closing them surfaced a long list of policy gaps — base standards, life support contracts, environmental remediation, transfer agreements, what happens to the contractor-owned generators when the base closes. CBEC sets the enterprise rules so that the next contingency doesn't repeat every mistake. To a forward-deployed engineer or a J4 planner at a CCMD, CBEC is invisible most of the time; you feel it when a contingency basing policy update lands and changes how you write the base support plan. The council is one of the quieter institutional reforms to come out of the post-2014 retrospective work on contingency operations.

CBP has two distinct DoD Dictionary readings: Capabilities-Based Planning (a strategic planning methodology that identifies required military capabilities to address a range of future threats rather than building forces against a single specified threat); and US Customs and Border Protection (the Department of Homeland Security agency responsible for securing US borders and ports of entry, with which DoD coordinates for homeland defense and counter-narcotics missions).

"Two meanings — capabilities-based planning methodology, or the DHS border agency DoD coordinates with."

CBP is another DoD Dictionary collision — context tells you which. In strategic planning conversations, CBP means Capabilities-Based Planning — the methodology that became the institutional language of the 2001 QDR and after, where forces are built against a range of plausible future threats rather than one specified threat (the alternative is "threat-based planning"). In homeland-defense and counter-narcotics conversations, CBP is the DHS agency — the Border Patrol agents, the CBP Air and Marine Operations P-3s and helicopters, the officers at ports of entry — that DoD partners with at JIATF-South, AMOC, CAMOC, and on the southwest border. Most service members hit the homeland-security CBP first; planners and analysts at OSD and the Joint Staff hit the capabilities-based-planning CBP more often.

Contingency Contract Administration Services (CCAS) — Defense Contract Management Agency (DCMA) services provided in a contingency operating environment to administer contracts awarded by deployed contracting offices and supporting contracting commands; includes quality assurance surveillance, property administration, payment recommendations, and contractor performance management for contingency contracts.

"DCMA contract administration in a deployed theater — the people watching the contractors so the contracts deliver."

CCAS is the DCMA piece of the contingency contracting machinery — the contracting officer representatives, quality assurance specialists, and property administrators DCMA deploys to a theater so the millions of dollars of contracts the deployed contracting office is awarding actually get administered (inspected, measured against the statement of work, paid correctly, and closed out properly). Without CCAS, a contracting officer at a forward base would have to write the contract and watch it execute at the same time, which is a recipe for fraud, waste, and accidental non-compliance. CCAS personnel live in some of the worst places in the theater because that's where the contractors are building things; their work is unglamorous but it is the difference between a contingency contracting effort that survives a future GAO audit and one that doesn't.

Consolidated Counterdrug Database (CCDB) — a US Government interagency database, managed by JIATF-South and supporting partners, that consolidates information on detected and monitored narcotics-related air, maritime, and land movements; used to track interdiction events, support analytic assessments of trafficking trends, and inform interagency and partner-nation counterdrug operations.

"The interagency database that tracks every monitored drug-trafficking event — feeds the bigger interdiction picture."

CCDB is the database JIATF-South and the broader counterdrug interagency uses to track every detected and monitored trafficking event — the go-fast boats spotted by maritime patrol aircraft, the aircraft tracks that fit the trafficking profile, the seizures, the interdictions, the post-interdiction analysis. The dataset feeds the recurring "estimated transit and seizure rates" the interagency briefs to Congress and the public, and analysts mine it for pattern-of-life work on trafficking organizations. CCDB inclusion has policy meaning: an event has to meet specific intelligence-confidence thresholds to count, which is why the published figures lag and why the methodology is itself a recurring debate. To a CBP P-3 crew or a USCG MH-65 flight, CCDB is the system the post-mission report eventually feeds; to an analyst at JIATF-South, it is the day-job dataset.

Combatant Commander Initiative Fund (CCIF) — a flexible appropriated funding authority, authorized under Title 10 U.S. Code §166a, that provides the Chairman of the Joint Chiefs of Staff with funds to be allocated to combatant commanders for unforeseen requirements supporting joint exercises, force training, contingency activities, military education exchanges, and related joint priorities not funded through service appropriations.

"A small Title 10 pot CJCS controls — CCDRs use it for unforeseen joint requirements outside service budgets."

CCIF is the small but flexible Title 10 funding authority the Chairman of the Joint Chiefs holds to push money to CCDRs for things that don't fit cleanly into a service appropriation — a no-notice exercise add-on, a foreign-officer education exchange, a contingency training event, a humanitarian-assistance project that emerged inside the year of execution. The fund sits at 10 USC §166a and is congressionally watched but operationally important; it gives CCMDs the maneuver room to do small things quickly without going through the multi-year PPBE cycle. To a J5 plans officer at a CCMD, CCIF is one of the funding lines they propose against when a CCDR initiative needs money this fiscal year; the approval lives at the Joint Staff. Most service members never touch CCIF; those at CCMD staffs see it cycle through every year.

A dual-use joint term: (1) central control officer — the officer responsible at an aerial port of embarkation or debarkation for the central control of cargo, passenger, and aircraft movement; (2) container control officer — the unit officer designated to manage Service-owned and DoD-controlled intermodal containers, account for them, and track them through the Defense Transportation System, per joint logistics doctrine.

"Two CCOs — one runs the APOE/APOD floor, one is your unit's container tracker."

CCO is one of those acronyms the DoD Dictionary lists twice on the same line because two different communities use it. The aerial-port CCO is the officer on the tarmac side of an APOE/APOD who synchronizes cargo, passenger, and aircraft flow — air mobility tempo, frustrated cargo, the whole movement picture. The Container Control Officer is the unit-level additional duty (usually a lieutenant or captain stuck with it) who is responsible for the unit's 20- and 40-foot containers — getting them, accounting for them, redeploying them, and not losing them in the Defense Transportation System where containers go to die. The two jobs share no skill set; the only thing they share is an acronym. If someone says they're the CCO, ask which one before you assume.

A joint force command-level board chartered by the commander to provide oversight of operational contract support — reviews contract performance, contractor accountability, and the integration of contracted capabilities into the operation — established in joint operational contract support doctrine to ensure the commander has visibility on the contracted portion of the force.

"The commander's board for checking that operational contractors are doing what they're paid to do."

CCORB is the governance body a joint force commander stands up to keep eyes on the contracted portion of the force — Operational Contract Support (OCS) has been a major share of the deployed footprint since Iraq and Afghanistan, and the commander needs a recurring forum to look at whether contractors are performing, where the dependencies are, and what would break if a contract were terminated or a country denied entry to a workforce. The CCORB pulls in the J4, the J8, the contracting support brigade or theater contracting command, the OCS integration cell, and the staff judge advocate. It's the kind of board that produces decision briefs, not warfighter excitement — but the lesson from twenty years of expeditionary contracting is that the force breaks fast if the contracted piece isn't actively managed at the commander's level.

A Department of Defense organization established in June 2022 by the Deputy Secretary of Defense, with statutory codification in subsequent NDAA provisions, that integrates the functions of the former Joint Artificial Intelligence Center (JAIC), Defense Digital Service (DDS), and the Advana enterprise data analytics platform, serving as the DoD-level office for digital and AI capability strategy, policy, and select capability delivery.

"The DoD office leading digital and AI strategy, formed by merging JAIC, DDS, and Advana."

CDAO was the institutional consolidation move — JAIC, DDS, and Advana had been three separate offices with overlapping mandates and varying success records. CDAO brought them under one organization with one Chief Digital and AI Officer reporting near the Secretary level. The office sets DoD-level digital and AI policy, runs the Advana data platform, manages AI ethics policy, and operates select AI capability programs. Whether the consolidation produces the coherence DoD needs in this area is one of the recurring institutional questions.

The Joint Capabilities Integration and Development System requirements document that establishes the operational performance attributes — including Key Performance Parameters and Key System Attributes — that a proposed material capability must demonstrate at Initial Operational Capability, validated by the JROC (for joint programs) or service requirements authorities, and required for Milestone B approval.

"The JCIDS requirements document validated at Milestone B with the KPPs the system must meet."

The CDD is where the requirements firm up — the KPPs (must-have) and KSAs (significant-but-tradeable) move from concept to firm program targets. Industry quotes the CDD when proposing solutions; the Program Office tracks against it; later cost growth often traces back to a CDD requirement that was ambitious at validation and proved expensive to deliver. Changes to a CDD after Milestone B require formal staffing back through JCIDS, which is why programs prefer to live with the CDD they have rather than reopen it.

A technical milestone where the program's detailed design is reviewed against requirements to verify it is mature enough to proceed to fabrication, demonstration, and test. Typically held during Engineering and Manufacturing Development (EMD).

"A formal review confirming the design is ready for fabrication and test."

CDR is the gate between detailed design and metal-cutting. A successful CDR triggers significant contractor work-share and contractual commitments. A failed or weak CDR ("conditional CDR") usually means redesign and schedule slip. The trade studies, requirements traceability, and risk register reviewed at CDR are the program's technical record — programs in trouble can usually trace the trouble to a thin CDR.

A list, attached to a Department of Defense contract using DD Form 1423, of the data items (technical data, reports, drawings, software documentation, test results, and similar items) that the contractor is required to deliver to the government, with each item linked to a Data Item Description (DID) that specifies the content and format requirements.

"The contract attachment listing required contractor data deliverables."

CDRL is what tells the contractor what data, documents, drawings, software artifacts, and other non-hardware deliverables they have to produce and hand over to the government — keyed to the Data Item Descriptions (DIDs) that prescribe format and content. CDRL items range from trivial (monthly status reports) to enormously consequential (technical data packages that enable the government to compete future work, software source code escrow, configuration management baselines). What is on the CDRL — and what is not — drives whether the government can maintain, repair, and recompete the system for decades.

The US Army major subordinate command of Army Materiel Command, headquartered at Aberdeen Proving Ground, Maryland, responsible for the materiel acquisition, sustainment, supply chain management, and depot maintenance of US Army communications, electronics, intelligence, electronic warfare, sensor, and information technology systems.

"The Army materiel command for communications, electronics, intelligence, and IT systems."

CECOM at Aberdeen handles the Army's communications and electronics layer — tactical radios, command-and-control systems, network infrastructure, electronic warfare systems, sensors, and intelligence platforms. Tobyhanna Army Depot (electronics depot) is the central CECOM sustainment activity. The command relocated to Aberdeen as part of BRAC 2005. As the Army has shifted toward network-centric warfare, CECOM's footprint has grown both in scope and in connection to broader DoD cyber and command-and-control modernization efforts.

Commander's Emergency Response Program (CERP) — a Department of Defense program, authorized in annual National Defense Authorization Acts since 2004, that gives commanders the authority to obligate appropriated funds for urgent humanitarian relief and reconstruction projects within a designated theater of operations; managed through a project-nomination and approval chain, with execution by uniformed personnel and contracting officers, and assessed for compliance through internal and IG review.

"A commander-controlled cash program for urgent reconstruction and humanitarian projects in theater."

CERP was the program that put real money in the hands of battalion and brigade commanders in Iraq and Afghanistan — generators for a clinic, repairs to a school, a microgrant to a local sheikh, condolence payments to a family whose home was damaged in a raid — under a nomination, approval, and disbursement chain that uniformed personnel ran with contracting officer support. To a Civil Affairs team or a maneuver-battalion S5/S9, CERP project files were the operational deliverable; to a TF commander, the CERP budget was a counterinsurgency weapon. The program drew significant IG and GAO scrutiny over the years for documentation and accountability gaps, and the post-OIF/OEF authorities have narrowed considerably. Veterans of the surge years carry strong feelings about CERP — some about the projects that worked, more about the ones that did not.

A senior officer or civilian, designated by the service, who manages the strategic-level policies, training, and force structure of a specific officer career field or enlisted occupational specialty — distinct from the assignment officer or career manager who manages individual personnel actions within the field.

"The senior manager setting strategic policy for an officer career field or enlisted specialty."

CFM is the field-level steward — sets the training pipeline, the school requirements, the special-pay eligibility, the force-structure footprint, and the strategic direction of the career field. Officers and senior NCOs interact with the CFM on policy questions ("Why does this MOS have such-and-such training requirement?") rather than individual assignment questions. The CFM is also typically the senior representative of the field at service-staff discussions about force structure and modernization. The CFM and the CME / assignment-officer chain are distinct functions; field policy is CFM, individual personnel actions are CME.

Code of Federal Regulations (CFR) — the codification of the general and permanent rules and regulations published in the Federal Register by the executive departments and agencies of the federal government; organized into 50 titles representing broad subject areas (Title 10 Armed Forces is statutory, while DoD regulations appear in Title 32 National Defense), with each title divided into chapters, subchapters, parts, and sections.

"The CFR — where federal agency regulations live, cited as Title-CFR-Part.section in DoD writing."

CFR is the regulatory body of work that DoD policies cite when they reference federal rules — Title 32 (National Defense) is where DoD-published regulations live, Title 5 (Administrative Personnel) covers civilian personnel issues, Title 38 (Pensions, Bonuses, Veterans' Relief) is the VA regulatory home, and a dozen other titles touch military life (Title 14 for the Coast Guard's Department of Homeland Security regulations, Title 41 for federal acquisition, others). To a JAG, a IG, or any staff officer writing policy, "32 CFR 199" (Civilian Health and Medical Program / TRICARE regulations) or "32 CFR 60" (entrance processing) is the source citation; the underlying statute is in the US Code, but the implementing regulation is in the CFR. Veterans dealing with disability ratings end up reading 38 CFR Part 4 (Schedule for Rating Disabilities) at some point. Talk to a JAG or a VSO before you act on what the CFR seems to say.

An installation-level supply activity that issues, exchanges, and turns in organizational clothing and individual equipment (OCIE) for soldiers assigned to or processing through the installation.

"The Army facility that issues organizational clothing and individual equipment."

CIF is the warehouse where soldiers draw rucksacks, sleep systems, IOTV (body armor), cold-weather gear, and the long list of OCIE that follows them through their career. Turn-in at PCS or ETS is famously stressful: every item must be returned (or a statement of charges generated for missing pieces), in the condition tracked on the hand receipt. Photographing your CIF issue before signing the receipt is one of those small acts of self-protection that experienced soldiers learn.

An Army installation-level facility responsible for issuing, exchanging, and reclaiming Organizational Clothing and Individual Equipment (OCIE) — operates under Army Materiel Command and the Installation Management Command — every soldier signs for OCIE through CIF on arrival to a duty station and clears CIF on PCS, ETS, or retirement, with financial liability for any unreturned or unserviceable items.

"The Army facility where soldiers draw and turn in field gear — every PCS goes through CIF."

CIF is the building on the installation where the soldier draws and returns OCIE — the field gear that's issued at unit expense and signed for individually. Every soldier visits CIF on arrival to a new duty station (or to an initial-entry posting), signs out a long list of items, and is responsible for them through the entire tour; PCS, ETS, and retirement all require clearing CIF, which means physically returning every item or paying for the difference. The line-by-line accountability is the part most soldiers remember — the lost canteen, the unserviceable rucksack frame, the missing duffel bag that turns into a financial liability statement of charges. The CIF experience is one of the rites of passage of Army service, and "clearing CIF" is shorthand for the broader experience of transitioning out of a unit or out of the Army.

Collaborative Issue Resolution Tool (CIRT) — a DoD information system used by combatant commands, the Joint Staff, and OSD to track, route, and resolve cross-organizational issues, action items, and tasker assignments through a structured workflow; one of several JCS-managed action-tracking systems alongside JSAP and related taskers.

"A DoD action-item tracker used to push issues across CCMDs and OSD until they close out."

CIRT is one of the action-tracker systems that runs the joint-staff and combatant-command action machine — a tasker comes in, it gets a control number, it routes to the responsible action officer at the right echelon, and it gets pushed and pulled until somebody signs off that it's closed. To the new action officer it's the system you learn the first week ("your CIRT is overdue, brief the boss") and curse for the next two years. To the staff principals it's how cross-organizational friction gets into a queue instead of dying on a phone call. Like JSAP, JCRMB, and the other JCS tooling, CIRT is one of those systems whose value is mostly invisible until you try to run a major issue across three CCMDs and seven OSD offices without it.

Chairman of the Joint Chiefs of Staff Instruction (CJCSI) — a directive issued by the Chairman of the Joint Chiefs of Staff that establishes policy, assigns responsibilities, and provides procedures for matters within the Chairman's statutory authorities and the joint force; CJCSIs are the principal joint policy issuances and remain in effect until rescinded or superseded.

"A formal directive from the Chairman of the Joint Chiefs — joint policy and assigned responsibilities."

CJCSI is one of the two principal forms (with CJCSM, the Chairman's manuals) in which joint policy actually gets written down — when something has to be the same across all the Services and combatant commands, somebody at the Joint Staff writes a CJCSI and the Chairman signs it. Examples that joint officers know by number: CJCSI 3170 (the JCIDS process for capability requirements), CJCSI 3500 series (joint training), CJCSI 5711.01 (action processing — the system that runs CIRT and the rest of the tasker tooling). The numbering system is hierarchical (3000 series for operations, 5000 for management, etc.); the document length is usually short policy followed by long enclosures. Action officers who write CJCSI updates spend their lives in the Joint Staff coordination drill.

Chairman of the Joint Chiefs of Staff Manual (CJCSM) — a directive issued by the Chairman of the Joint Chiefs of Staff that provides detailed procedures, formats, and guidance to implement the policies established in companion CJCSIs; the CJCSM is the procedural sibling to the CJCSI's policy, and the two are often referenced in pairs.

"The procedural companion to a CJCSI — detailed how-to for implementing joint policy."

CJCSM is the procedural manual that sits next to a CJCSI — where the instruction sets the policy and assigns responsibility, the manual gives the format, the timelines, the staffing process, the templates, the worked examples. The pair model means a Joint Staff action officer often references both numbers in the same sentence (CJCSI 3170 / CJCSM 3170 for JCIDS, for example). For somebody writing a joint capability document, a joint training plan, or a deliberate-planning product, the CJCSM is the source of truth for how the document actually has to look and what enclosures it must contain. Manuals run long, are unglamorous to read, and are the documents that keep joint processes from drifting into Service-specific habits.

One of the ten classes of supply, comprising subsistence — all food, including operational rations (MREs, UGRs, T-Rations), bulk dining-facility provisions, water, and related items — sourced and distributed through the Defense Logistics Agency Troop Support directorate and the service supply chains.

"The supply class for food, rations, and subsistence."

Class I covers everything the force eats — dining facility provisions, field rations, water purification, the works. The DLA Troop Support directorate handles much of the bulk procurement; service supply chains push to units. Class I is also one of the supply classes most visible to individual service members (everyone eats), which is why dining-facility quality complaints surface in BAH discussions and why MRE quality stories travel far. The class also produces the operational stockage planning that any deployment requires.

One of the ten classes of supply, comprising petroleum and related fluids — bulk fuels (JP-8, JP-5, gasoline, diesel), packaged petroleum products (motor oil, hydraulic fluids, greases), and operational lubricants — sourced through the Defense Logistics Agency Energy directorate and distributed through service fuel handling units.

"The supply class for fuels, oils, and lubricants."

Class III is fuel and everything that lubricates — bulk fuel for vehicles and aircraft, packaged oils and greases, hydraulic fluids. JP-8 has historically been the single battlefield fuel for the US joint force (replaced JP-4 and is the operational equivalent of commercial Jet A-1); the move to JP-5 in some Navy and Marine contexts reflects shipboard safety requirements. DLA Energy is the wholesale provider; service fuel handlers (Army Petroleum and Water Distribution units, Air Force fuels teams, Navy oilers) operate the distribution. Class III consumption is one of the largest single line items in deployed operations.

One of the ten classes of supply, comprising repair parts and components used to maintain, repair, and overhaul military equipment — including end items, modules, sub-assemblies, electronic components, hardware, and consumables — managed through the service materiel commands and depots with PLL/ASL stockage at the user and SSA levels.

"The supply class for repair parts."

Class IX is the maintenance lifeblood — every part that goes into keeping equipment running. The class is enormous (millions of NSNs across all services and equipment types), managed through the service materiel commands (AMCOM for aviation/missile, TACOM for ground combat vehicles, CECOM for communications-electronics, etc.) and stocked at user-level PLL, SSA-level ASL, and depot levels above. Class IX availability — does the part exist, is it in stock somewhere reachable, can it be delivered in time — is the binding constraint on most mission-capable readiness reporting.

One of the ten classes of supply, comprising ammunition of all types — small arms, mortar and artillery, missile and rocket, demolition, pyrotechnic, and air-delivered munitions — managed under stringent accountability and safety requirements separate from other classes of supply, with explosive safety constraints and detailed inventory controls.

"The supply class for all types of ammunition."

Class V is its own world — separate facilities, separate handling procedures, separate accountability requirements, and explosive safety quantity-distance (Q-D) rules that constrain everything from storage to transportation. Joint Munitions Command and the service ammunition commands run the wholesale layer; unit-level ammunition NCOs handle the retail accountability. Live-fire training Class V demand drives a large share of training budgets. Combat operations Class V demand drives the most consequential strategic-stockage and industrial-base questions in DoD — wartime munitions production capacity is a contemporary policy focus.

One of the ten classes of supply, comprising medical materiel of all types — pharmaceuticals, surgical supplies, medical equipment, blood products, dental supplies, and veterinary supplies — sourced through the Defense Logistics Agency Troop Support medical division and distributed through service medical supply chains under separate medical-materiel accountability requirements.

"The supply class for all medical materiel."

Class VIII covers everything medical — DLA Troop Support handles much of the bulk procurement; service medical commands (Army MEDCOM, Navy BUMED, AF medical) handle the operational distribution. Class VIII has separate accountability requirements (some items are controlled substances under strict tracking; vaccines and biologicals have cold-chain requirements; blood products have time-and-temperature constraints) and separate audit and inspection regimes. Forward-deployed Class VIII stockage is one of the most operationally consequential logistics planning factors — running short of antibiotics, pain medications, or surgical supplies in a forward area is a life-or-death deficiency.

A discrete contract line identifying specific supplies or services to be delivered, with associated price, quantity, and delivery terms.

"Each CLIN identifies one specific deliverable or service in a contract."

CLINs are how contract money is actually tracked. A program with funding problems often has the right total dollars but the wrong CLIN structure — money cannot move freely between CLINs without a modification. SLINs (sub-CLINs) and ELINs (exhibit line items) add granularity. If you are reading a contract for the first time, the CLIN schedule is the first place to look — it tells you what the contract is really buying.

A subdivision within the Army Human Resources Command, organized by branch, that serves as the management point of contact for officers in the branch — providing assignment-officer support, school-selection guidance, promotion-board mentoring, and career-planning advice through assigned career managers.

"The branch-specific career management office in HRC for Army officers."

The CME is where an Army officer's assignment officer sits — the branch CME (Infantry CME, Signal CME, Adjutant General CME, etc.) at HRC Fort Knox, with assigned career managers for each year group within the branch. Officers communicate with their assignment officer on assignment cycles (now operationalized through AIM 2 and ATAP), school applications, special-program eligibility, and career-trajectory questions. The relationship with the assignment officer is one of the practical career-management responsibilities; engaged officers get better service than passive ones.

A US Air Force automated information system for tracking, documenting, and managing cargo movement through the Defense Transportation System — the system of record used by Air Mobility Command terminals, aerial ports, and supporting transportation organizations to document cargo manifests, track shipments, and generate movement documentation against airlift missions.

"The Cargo Movement Operations System — the Air Force's cargo-tracking system at aerial ports."

CMOS is the Air Force cargo-tracking and management system at aerial ports and transportation terminals — the system aerial port (2T2X1) and traffic management (2T0X1) airmen use every day to build manifests, generate movement documentation, and account for cargo flowing through the air mobility system. The system is unloved by users (the interface predates modern web standards by a long way and the workflow has been bolted together over decades), but it is the system of record for cargo through Air Force terminals and connects into the broader Defense Transportation System data architecture. Aerial port operations cannot run without CMOS, and the modernization story (multiple replacement efforts have started and stalled) is a familiar pattern in the joint logistics IT space.

The senior enlisted member of the United States Air Force, occupying a unique grade above E-9 (E-9 Special), serving as the principal enlisted advisor to the Secretary of the Air Force and the Chief of Staff of the Air Force on enlisted-related matters.

"The senior enlisted member of the US Air Force and principal enlisted advisor to the CSAF."

CMSAF is the Air Force counterpart to SMA, MCPON, SgtMajMC, MCPOCG, and CMSSF — a single position, with a single appointed Chief Master Sergeant serving as the senior enlisted voice of the service to the Secretary, the Chief of Staff, and the broader force. The CMSAF participates in service-level decisions on enlisted policy, force structure, professional development, and modernization. The position has been held by Chief Master Sergeants from a wide range of AFSCs across the decades; the institutional rotation among the service core competencies is itself a signal.

The senior enlisted member of the United States Space Force, occupying a unique grade above E-9 (E-9 Special), serving as the principal enlisted advisor to the Secretary of the Air Force and the Chief of Space Operations on enlisted-related matters.

"The senior enlisted member of the US Space Force and principal enlisted advisor to the CSO."

CMSSF is the Space Force counterpart to CMSAF — a single Chief Master Sergeant serving as the senior enlisted voice of the new service. The Space Force was established in December 2019 and is the most recent of the services to develop its own senior-enlisted position and supporting infrastructure. The CMSSF participates in CSO and SECAF-level decisions on Space Force enlisted policy, force structure, and the still-developing service culture. As the Space Force grows and matures, the CMSSF role is evolving from "establish the position" to "shape an enduring institutional voice."

A formal policy directive issued by the Chief of the National Guard Bureau, establishing policies, procedures, and guidance applicable to the National Guard Bureau, its joint staff, and (where authorities apply) the Army and Air National Guard — analogous to a Department of Defense Instruction (DoDI) but issued under National Guard Bureau authorities.

"A Chief National Guard Bureau Instruction — the NGB's version of a DoDI policy directive."

CNGBI is the formal-policy-directive series issued by the National Guard Bureau — the NGB's equivalent of a Department of Defense Instruction, governing the policies and procedures that apply to the NGB joint staff and (where the authorities run that direction) the Army and Air National Guard. National Guard officers and senior enlisted soon learn to navigate the CNGBI series alongside DoDIs, Army Regulations, and Air Force Instructions — the document hierarchy that governs Guard service has more layers than active-component service because Guard authorities live at the intersection of federal Title 10 status, state Title 32 status, and state active duty. Pulling up the relevant CNGBI is part of the routine work of any NGB action officer or Guard policy analyst.

A contracting arrangement in which a contractor owns and operates the facility, equipment, or capability that delivers a service to the government — as distinguished from government-owned, contractor-operated (GOCO) and government-owned, government-operated (GOGO) arrangements — typically used for services where the contractor's ownership of the underlying asset is an integral element of the service delivery.

"Contractor-owned, contractor-operated — the contractor owns and runs the facility, not the government."

COCO is the contracting arrangement where the contractor owns the asset (the facility, the airplane, the satellite, the IT system) and operates it on the government's behalf — as distinct from GOCO (government-owned, contractor-operated, common for government-owned facilities like ammunition plants run by industry) and GOGO (government-owned, government-operated, the default for organic capability). The COCO model is used where the underlying asset is too specialized for the government to own (commercial satellite imagery, certain ISR feeds), where commercial markets exist outside the government use (commercial space launch services), or where the contractor's asset ownership is structurally necessary to the service. Contracting officers and program managers spend a lot of time on the COCO-vs-GOCO-vs-GOGO trade space — the answer changes acquisition strategy, cost structure, and government flexibility.

A VA-issued document confirming a veteran's eligibility for a specific benefit — most commonly the VA home loan guaranty or GI Bill education benefits.

"Your COE confirms what you're eligible for and is required for use of the benefit."

COEs are now mostly automated through eBenefits / VA.gov, but legacy cases (pre-1980 service, lost records, dependent transfers) can require manual processing that takes weeks. For a VA loan, your lender can pull the COE directly in most cases. For Ch 33, your COE shows how many months of benefit remain — check it before enrolling, because reported months and actual VA records sometimes diverge.

Commandant Instruction — the US Coast Guard's directive-series numbering convention for policy and procedure issuances signed under the authority of the Commandant of the Coast Guard, equivalent to the Army's AR (Army Regulation), Navy's OPNAVINST (Chief of Naval Operations Instruction), Air Force's AFI (Air Force Instruction), and Marine Corps's MCO (Marine Corps Order) series.

"The Coast Guard regulations naming convention — like AR/AFI/OPNAVINST for USCG."

COMDTINST is what the Coast Guard calls its regulations — Commandant Instructions, the directive series signed under the Commandant's authority. Every Coast Guard activity is governed by a stack of COMDTINSTs the way Army activities are governed by ARs and Navy activities by OPNAVINSTs. COMDTINST M1000.6 (Personnel Manual) and COMDTINST M16114.32 (Marine Safety Manual) are typical examples — the numeric prefix M indicates a manual, and the number system follows a subject-coding convention. For joint personnel rotating into Coast Guard billets or partnering with the Coast Guard on maritime homeland-security operations, learning to navigate the COMDTINST series is part of the orientation. The Coast Guard is part of DHS (except in wartime when it can be transferred to the Navy), which adds an additional regulatory layer on top of the COMDTINSTs.

Computerized Movement Planning and Status System — a US Transportation Command (USTRANSCOM) information system used for time-phased force and deployment data (TPFDD) development, movement planning, and in-transit visibility of forces and equipment moving through the Defense Transportation System — one of several JOPES (Joint Operation Planning and Execution System) family applications supporting joint deployment planning.

"A USTRANSCOM movement planning system — TPFDD and in-transit visibility."

COMPASS is one of the joint movement-planning information systems in the USTRANSCOM stack — supporting TPFDD development and in-transit visibility for forces and equipment moving through the Defense Transportation System. Joint planners building a contingency operation generate a TPFDD that sequences which units move when, by what mode (air, sea, rail, road), through which ports of embarkation and debarkation, and arrive at the operational area in the priority order the operational concept requires. COMPASS and related JOPES systems (GCCS-J components, JFAST, TC-AIMS II at the unit level) provide the data-management infrastructure that makes joint deployment planning executable rather than aspirational. The systems are notoriously complex and the deployment-planning specialists (Army 88M Motor Transport Operator with movement-planning additional skill identifiers, the broader TC-AIMS workforce) carry the institutional knowledge.

Commander, Military Sealift Command Instruction — the directive-series numbering convention for policy and procedure issuances signed under the authority of the Commander, Military Sealift Command, governing MSC operations, ship-board administration, and Civil Service Mariner administration — equivalent to the Navy's OPNAVINST and Coast Guard's COMDTINST series in scope and function.

"The MSC instruction naming convention — like OPNAVINST/COMDTINST for MSC."

COMSCINST is the directive series MSC uses for its policies and procedures — Military Sealift Command Instructions, signed under the Commander MSC's authority, governing how MSC ships are operated and how Civil Service Mariners and the small military detachments aboard MSC ships do business. The series sits underneath the broader Navy OPNAVINST and SECNAVINST hierarchy, applying Navy-wide policy through MSC-specific implementation. For mariners new to MSC and for joint personnel working with MSC support (Navy strike groups, Marine prepositioning programs, Army strategic sealift coordination), learning the relevant COMSCINSTs is part of the orientation. The series number system follows a subject-coding convention similar to OPNAVINST and COMDTINST.

A single-letter code assigned to military materiel that describes its serviceability and disposition — including A (serviceable, issuable without qualification), B (serviceable, issuable with qualification), C (serviceable, priority issue), D (unserviceable, reparable), F (unserviceable, reparable, condemned), and additional letters for special conditions — used across the DoD supply system to control disposition.

"The A-H letter code describing a piece of equipment's serviceability and disposition."

Condition codes are the single-letter shorthand that controls how a piece of equipment moves through the supply system — Code A is good to go; Code D needs repair; Code H is condemned. The codes drive where the item ships when a unit turns it in, what funding source pays for any work, and whether the item can be re-issued, repaired, or disposed of. The full code set runs through the alphabet with specific sub-codes. Anyone working in unit supply, motor pool maintenance, or the larger logistics system learns the codes quickly; the difference between Code D and Code F can be the difference between a few hundred dollars of repair and condemnation.

A promotion granted under the condition that the member complete a specified professional military education course or other prerequisite within a defined period after pin-on, with failure to complete the requirement resulting in administrative removal of the promotion and revert to the prior grade.

"A promotion conditional on completing a required course or prerequisite after pin-on."

Conditional promotion is the institutional way of saying "we're promoting you now, but you must finish that course we're holding you accountable for, or we'll revoke." The conditions are typically PME courses (BLC for E-5, ALC for E-6, SLC for E-7, or officer career-course equivalents) that the member is enrolled in or scheduled for but has not yet completed. The promotion is real (new grade, new date of rank, new pay) but reversible if the condition fails. Members under conditional promotion need to actively manage their course completion to avoid the revert action.

Continental United States — the 48 contiguous states and the District of Columbia, excluding Alaska, Hawaii, and US territories — the foundational geographic distinction used in joint and Service personnel, pay, and deployment policy (CONUS vs OCONUS, Outside the Continental United States) to differentiate locations and authorities.

"The lower 48 plus DC — the foundational CONUS/OCONUS distinction for pay and deployment."

CONUS is the 48 contiguous states plus DC — the geographic distinction that drives a long list of personnel, pay, and deployment policies. CONUS vs OCONUS (Outside the Continental United States — Alaska, Hawaii, US territories, and overseas) affects entitlement to overseas allowances (COLA, OHA), permanent-change-of-station entitlements (the OCONUS PCS is a different process than a CONUS PCS), deployment counting (OCONUS deployments accrue toward various entitlements differently from CONUS station changes), tax treatment (residency rules), and many other administrative dimensions. Service members get used to seeing CONUS and OCONUS in every personnel and finance document. The distinction is bureaucratic rather than operational — geography matters for a lot of administrative functions even when the operational distinction is minimal (a service member at JBER Alaska is technically OCONUS, but the operational tempo and family-life profile is similar to many CONUS installations).

The official with the statutory or regulatory authority to convene a promotion selection board, special selection board, or other selection or review board — typically the Secretary concerned for major boards under 10 USC 611, with delegations to service Chiefs and lower officials for component-specific boards.

"The official with authority to convene a promotion or selection board."

Convening Authority is the formal originator of the board — the Secretary, the service Chief, or the designated delegated official who issues the board convening order, the board instruction (the written guidance to the board members), and the authority to promulgate or modify the results. The convening authority sets the criteria and the constraints; the board operates within them. Convening authority can also be the authority to recall a board or to disapprove the board's results, which is a rare but real check on the board outcome.

The JCIDS requirements document that establishes the performance attributes the program must demonstrate for Full Operational Capability and production decision, refined from the Capability Development Document based on the results of the Engineering and Manufacturing Development phase, and required for Milestone C approval.

"The JCIDS requirements document validated at Milestone C with the production-decision KPPs."

The CPD is the production-decision version of the requirements — refined after EMD testing has shown what is actually feasible at the program's cost and schedule. KPP thresholds may have moved (within statutory and policy limits) from CDD to CPD; some attributes that looked nice in the CDD have been recharacterized or dropped. Milestone C is the production-decision gate, and the CPD is the requirements document that has to be validated to support the production decision.

Per the DoD Dictionary, Contingency Planning Guidance — the Secretary of Defense's written guidance to the Chairman of the Joint Chiefs of Staff and combatant commanders that establishes planning priorities, assumptions, and direction for the development of contingency plans across the joint planning system.

"The SecDef's written priorities for what the combatant commands plan against."

CPG is the SecDef-signed document that tells the combatant commands what to plan for and roughly how much priority each scenario gets. It's classified, it changes with administrations and threat assessments, and the actual planners at the COCOM J5 shops live and die by it because it's what gives their plans bureaucratic legitimacy and a programmatic claim on forces. For most service members the CPG is invisible — but every CONPLAN, OPLAN, and theater campaign plan you'll ever see referenced traces back to language inside it. When the CPG shifts (e.g., the post-2018 pivot toward great-power competition), the entire joint planning enterprise re-paginates over the following two to three years.

Per the DoD Dictionary, centralized receiving and shipping point — a theater-level sustainment node, typically established by a sustainment brigade or theater sustainment command, where multiclass cargo is received from strategic lift, broken down, reconsolidated, and onward-shipped to tactical units, providing in-transit visibility and surge capacity for distribution.

"The theater RSP — where strategic-lift cargo gets broken down and pushed forward."

CRSP is where the strategic-pipeline cargo coming off ships and planes actually gets sorted, palletized for the right unit, and pushed onto the tactical distribution network — usually run by a sustainment brigade, with contracted material handling equipment and a large MHE/forklift footprint. If you've worked a yard at Bagram, Camp Arifjan, or one of the European APODs you've seen one: rows of containers, ITV tags, the manifest desk, and the recurring fight over who actually owns the cargo while it sits there. CRSPs are where the in-transit-visibility "win" or "lose" actually happens — when the system breaks down, this is where pallets disappear.

The senior enlisted member of a major military command (a Combatant Command, a service major command, a Joint Task Force, or a similar formation) — serving as the senior enlisted advisor to the commander, providing the enlisted-force perspective on operational and personnel matters, and serving as the senior enlisted representative of the command to subordinate units and external partners.

"The senior enlisted advisor to a major command or joint task force commander."

CSEL is the operational and command-level counterpart to the service senior-enlisted positions — every major command (Combatant Commands like CENTCOM, INDOPACOM, EUCOM; service major commands; joint task forces; major operational commands) has a Command Senior Enlisted Leader. The CSEL at a Combatant Command (the COCOM Senior Enlisted Leader) is a four-star-equivalent-staff enlisted position, often pulled from a different service than the commander, deliberately mixing service perspectives at the senior enlisted level. CSELs travel the AOR, mentor subordinate senior enlisted, and serve as institutional voice for enlisted matters.

A streamlined competitive procurement authority, codified at 10 USC 3458 (originally established as a pilot in Section 880 of NDAA FY 2017 and made permanent in subsequent NDAAs), that allows DoD to acquire innovative commercial solutions or research outside the FAR/DFARS framework through a market-research-based solicitation and selection process, with awarded efforts typically running as either purchase orders or as Other Transactions.

"A streamlined procurement authority for innovative commercial solutions outside FAR."

CSO is one of the streamlined procurement authorities that DIU, AFWERX, SOFWERX, NavalX, and similar innovation organizations use to bring in commercial technology quickly — bypassing the long FAR-driven solicitation cycles in favor of a problem-statement-and-pitch model. Vendors respond with proposals; selected vendors receive prototypes or direct awards. The follow-on Phase III commercialization pathway, when used in conjunction with SBIR or OTA awards, lets selected innovations move to scale. The OUSD(A&S) class deviation defines the operating rules in detail.

Per the DoD Dictionary, combat service support automation management office — a brigade-level office responsible for installation, maintenance, and user support of the standard Army Management Information Systems (STAMIS) that run sustainment functions (supply, maintenance, transportation, ammunition), including GCSS-Army terminals, networking, and account management for sustainment users.

"The brigade IT shop for logistics computers — GCSS-Army help desk, basically."

CSSAMO is the team that keeps the brigade's logistics IT actually working — GCSS-Army boxes, the network connectivity that lets units order parts and report maintenance, account creation for new soldiers, and the recurring fight to get the right SIPR/NIPR connectivity from the signal company. For the supply sergeant and the motor sergeant the CSSAMO is who you call when the system is down at 0200 the day a LOGSTAT is due. The shop is small (a handful of soldiers and contractors typically), the workload is constant, and the role gets invisible until something breaks — at which point the whole brigade can't order parts.

Per the DoD Dictionary, CTS has multiple authorized expansions including commodity tracking system — a logistics in-transit-visibility application that tracks specific commodity classes through the distribution network — and contingency tracking system — a personnel deployment-accountability application used to track DoD military and civilian personnel into and out of contingency operations, supporting personnel accountability and entitlement determinations.

"CTS — the commodity-tracking logistics system, or the contingency-tracking personnel system."

CTS is one of those acronyms that means different things to the logistics shop and the personnel shop. On the logistics side, the Commodity Tracking System variants are part of the in-transit-visibility ecosystem — RFID tags, satellite-tracked transponders on key cargo, and the dashboards that let a J4 see where ammunition or critical parts physically are. On the personnel side, the Contingency Tracking System has historically been the accountability spine for deployment status, hostile-fire-area entitlements, combat-zone tax exclusion eligibility, and family separation pay — a downstream pay-and-benefits matter that depends on the deployment record being accurate. If your CZTE didn't kick in correctly, CTS is usually the system that was wrong.

The threshold value (typically a numerical score or a list position) that separates selects from non-selects in an enlisted promotion cycle or, by extension, the position on a promotion-list line-number sequence at which actual promotions stop within a given execution period.

"The score or list position separating selects from non-selects in a promotion cycle."

Cut line is most concretely the Army enlisted cutoff score — each month, HRC publishes the EPPW point cutoffs by MOS, and members at or above the cut promote; members below it wait another cycle. The term is also used loosely about officer promotion list line numbers ("I'm above the cut for this fiscal year" meaning your line number will be reached for actual promotion within FY). Cut-line mechanics shift with force-structure needs; cutoffs can drop sharply when the Army needs more E-6s in a shortage MOS, or rise sharply when retention exceeds expectations.

Goods and services obtained from commercial sources (private contractors, vendors, service providers) under contracts or other acquisition instruments in support of military operations — the broad category that includes contractor logistics support, base operating support contracts, contracted linguist services, commercial transportation services, and many other contractor-provided functions across the joint force.

"Commercial vendor services — the umbrella category for contractor-provided support to the force."

CVS is the umbrella category for the enormous range of services that the joint force buys from commercial vendors rather than providing organically — from base operating support (housing, food service, facilities maintenance, MWR) to contractor logistics support on weapons systems, contracted linguists in deployed environments, commercial transportation services, and many specialty contracted functions. The post-Cold-War shift toward contracted support changed the operational landscape: deployed units now operate alongside contractors at roughly the same headcount as uniformed personnel in many theaters, and the contracting officer's representative role (COR) became a key uniformed function. CVS as a category lives in joint logistics doctrine but the everyday experience is the LOGCAP and similar large-scale support contracts that run base life-support across the COCOMs.

The total elapsed time, measured in days, between a customer's requisition for a Class IX repair part or other supply item and the customer's receipt of the item — a principal joint-logistics performance metric reported through the Logistics Functional Area Services (LOGFAS) and Defense Logistics Agency systems, used to evaluate supply chain responsiveness across the Services.

"Customer wait time — the elapsed-days metric for how long a supply requisition takes to arrive."

CWT is the standard joint-logistics responsiveness metric — the elapsed days from when a unit submits a requisition for a repair part or supply item to when the unit actually receives it. The number gets briefed at every level of the logistics chain from the Defense Logistics Agency down through Service supply systems to the unit supply room, and it drives readiness reporting because waiting on a Class IX repair part is one of the most common drivers of non-mission-capable (NMC) equipment status. CWT is a useful metric but a partial one: it doesn't capture the workaround economy (cannibalizing a deadlined vehicle for a part, calling sister units for borrowed parts, expediting through the bench-stock side channel) that supply sergeants and maintenance NCOs run when official CWT is too long for the operational tempo. The metric is honest about the steady state and silent about the desperation.

The maintenance level performed at Department of Defense depots and authorized commercial facilities, comprising the most complex maintenance — major rebuild, overhaul, modification, and modernization of weapon systems — using specialized facilities, equipment, and personnel beyond the capacity of unit-level or intermediate-level maintenance organizations.

"The depot-level major rebuild, overhaul, and modernization maintenance."

D-Level is where weapon systems go for major work — Anniston Army Depot for combat vehicles, Corpus Christi Army Depot for helicopters, Tobyhanna for electronics, the Naval Shipyards for ships and submarines, the Air Logistics Complexes for aircraft. Work scope: complete teardown and rebuild, structural and major-component overhaul, modernization to current configuration. Depots run on industrial-scale workflows; turnaround times are months to years depending on system. The 50/50 rule (10 USC 2466) requires at least 50% of depot maintenance funding to go through public (military) depots versus private contractors.

A formal written justification, signed by an authorized official, supporting a specific contracting action that requires such justification under the Federal Acquisition Regulation (FAR) or Defense FAR Supplement (DFARS) — common D&F categories include sole-source justifications, justification for other than full and open competition, and similar acquisition-decision documents that establish the legal and policy basis for the contracting action.

"Determinations and findings — the contracting officer's written justification document."

D&F is the contracting world's formal written justification — the document where a contracting officer or higher authority lays out the factual findings and legal determinations that support a particular contracting action. The most common D&Fs are sole-source justifications (the contracting officer explaining why only one vendor can satisfy the requirement, despite the default rule of full-and-open competition), justifications for other-than-full-and-open competition under the FAR, and similar acquisition-decision documents. D&Fs get reviewed by lawyers (contract counsel) and the agency's competition advocate, and an inadequate D&F is one of the most common protest grounds when a losing bidder challenges an award at GAO. The acronym is unremarkable; the document is where acquisition decisions live or die.

The US Army form (or the corresponding electronic record in GCSS-Army) used at the operator level to record the results of PMCS (Preventive Maintenance Checks and Services), identify deficiencies, and document the status of equipment between scheduled service events — historically a hardcopy form, now largely supplanted at the operator level by the DA Form 5988-E electronic worksheet.

"The Army operator's form for recording PMCS results and equipment deficiencies."

DA Form 2404 has been the Army's PMCS workhorse for decades — the operator runs through the system-specific Technical Manual checklist, marks the deficiencies, signs the form, and the unit maintenance section uses the result to schedule the work. The electronic successor (DA 5988-E) runs in GCSS-Army; many units still maintain a paper trail in addition. The form's status (clean / deadlining faults / awaiting parts) is the unit's real-time readiness picture and rolls into the formal NMC/NMCS/NMCM reporting.

The US Army monthly equipment readiness report (or its electronic equivalent in GCSS-Army) that aggregates the materiel condition status of all reportable equipment in a unit, providing the formal readiness reporting that rolls up through brigade, division, corps, and HQDA-level readiness reporting systems.

"The Army monthly equipment readiness report rolled up to HQDA-level."

DA 2406 is what battalion S-4s and unit motor sergeants spend significant time getting right each month — the formal materiel condition status report that captures every reportable end item's NMC/PMC/FMC status, the reason for any non-mission-capable status (supply vs maintenance), and the trend over time. Rolled up, the 2406 data is what drives HQDA-level readiness reporting and what generates the Army's strategic readiness picture. Accurate 2406 reporting is a basic command discipline; gamed 2406 reporting is a recurring institutional concern.

The Army form used to request, approve, and authorize leave (ordinary, emergency, advance, terminal, convalescent, and other categories) for active-duty soldiers, signed by the requesting soldier and the approving authority, processed through the unit S1 and integrated into the soldier's leave record.

"The Army leave request and authorization form."

DA Form 31 is the Army's version of the leave paperwork ritual — block the dates, sign the request, route through the unit chain of command to the approving authority (typically company commander or higher for longer periods). The form has migrated to IPPS-A's digital workflow for most active-component units, but the DA 31 document itself is still what generates and the soldier still signs in (or e-signs). Leave balance management — accumulating, using, losing at end of FY past the 60-day cap unless on contingency-operation exception — happens in the background between DA 31 submissions and the LES.

The Army hand-receipt form used to record temporary custody of property between accountable individuals, establishing pecuniary liability for the property listed.

"The Army hand-receipt form."

The DA-2062 is the paper (or electronic, inside GCSS-Army) proof that you have signed for an item. Hand-receipt chains run primary (the property book officer) → secondary (the company commander) → sub-hand-receipt (the platoon leader, the squad leader, the soldier holding the rifle). The soldier at the bottom of the chain is the one whose pay is at risk when an item walks; read what you sign, inventory what you take, and re-inventory before you sign over.

The electronic equipment inspection and maintenance worksheet used in Army units to record faults found during PMCS, parts ordered to correct them, and the maintenance work performed.

"The electronic Army form for documenting maintenance work."

The 5988-E is what a mechanic fills out during PMCS — faults found, faults corrected, parts ordered against the fault, and operator-versus-mechanic responsibility on each line. It runs inside GCSS-Army; the paper DA Form 2404 still exists as the backup when systems are down. Falsifying a 5988-E (signing without doing the inspection, closing a fault that was not fixed) is the kind of small dishonesty that becomes very visible after a deadlined vehicle gets investigated.

The authority granted by SecDef to combatant commanders under 10 USC §164 to issue directives to subordinate commands, including theater Service component commanders, on logistics matters necessary to execute the combatant commander's assigned missions — typically used to direct cross-Service common-user logistics, reallocate logistics resources within the AOR, and integrate Service-specific logistics into theater operations.

"Directive authority for logistics — the COCOM's SecDef-delegated authority to direct logistics across Services in the AOR."

DAFL is the SecDef-delegated authority that lets a combatant commander direct logistics actions across the Service components in the commander's AOR — the institutional answer to the problem that each Service has its own logistics chain but joint operations require cross-Service common-user logistics, reallocation of constrained resources, and integrated theater logistics. DAFL is exercised through the combatant command J-4 (logistics directorate) and through the Theater Sustainment Commands, MARFOR logistics elements, fleet logistics elements, and Air Force component logistics elements that work the theater logistics architecture. The authority is established under 10 USC §164 and detailed in JP 4-0 (Joint Logistics). DAFL is one of the cleaner pieces of joint authority — clear delegation, clear chain, and the everyday operating mechanism by which combatant commanders shape logistics in theater.

A Department of Defense agency, established in 1958 (originally as ARPA) under DoDD 5134.10, that funds and manages high-risk, high-payoff research projects across a broad range of scientific and engineering fields, focused on breakthrough technology for national security applications, with a portfolio managed through program managers serving fixed-term tours.

"The DoD agency funding high-risk, high-payoff breakthrough research."

DARPA's institutional bet is on the program manager — fixed-term hires (typically four to six years) who run portfolios of high-risk technology projects with deliberate "DARPA-hard" goals that may or may not pay off but that, when they do, produce capabilities the rest of the defense and commercial world catches up to. Internet, GPS-precision navigation, stealth, drones, mRNA vaccines (BARDA / DARPA-adjacent), Bayesian network applications — the historical hit list is impressive. The cultural distance from typical DoD R&D is deliberate; the program-manager turnover prevents institutional ossification.

A statute originally enacted in 1990 and now codified at 10 USC 4101-4103, establishing certification, education, and career development requirements for members of the Department of Defense acquisition workforce, including required Defense Acquisition University coursework, experience requirements, and continuous learning requirements by career field and certification level.

"A statute setting certification and education requirements for the DoD acquisition workforce."

DAWIA is the workforce-development framework for the acquisition career fields — Engineering, Contracting, Program Management, Test and Evaluation, Logistics, Cost Estimating, and several others. Each career field has certification levels (originally Levels I/II/III; more recently a Foundational/Practitioner/Advanced structure under the 2022 DAWIA modernization). Certification requires DAU coursework, experience, and continuous learning points to maintain. DAWIA certification gates which acquisition positions members and civilians can hold; the modernization made the system more skill-based.

A standardized form completed by an examiner during a C&P exam that translates a veteran's clinical findings into the elements the VA uses to rate the disability.

"A standardized form that ensures conditions are rated consistently."

The DBQ is what the rater actually reads — not the veteran's claim narrative, not the lay statements, the DBQ. Veterans can also obtain DBQs from private providers (the VA accepts them when properly completed) for some conditions, which can supplement or rebut a problematic VA exam. A private DBQ from a treating specialist often carries weight on appeal.

A Department of Defense acquisition pathway, governed by DoDI 5000.75, for the acquisition of business systems (financial management, human resources, logistics business systems, contract management, and similar enterprise IT capabilities), structured around a Business Capability Acquisition Cycle (BCAC) that emphasizes commercial off-the-shelf adoption and business-process re-engineering ahead of system development.

"The DoD acquisition pathway for enterprise business IT systems."

DBS is the pathway for the financial, personnel, logistics, and similar enterprise IT systems that don't fit the SWP model (typically because they're large COTS-based ERP deployments rather than custom development) and don't fit MCA (because they're not platform hardware). The pathway emphasizes business-process re-engineering before system selection — the historical pattern of "automate the existing broken process" being a known failure mode. Programs like the various service ERPs (LMP, GFEBS, IPPS-A, MyNavy HR) have traveled this pathway.

A historical series of intelligence community directives issued by the Director of Central Intelligence prior to the 2004 Intelligence Reform and Terrorism Prevention Act, which replaced the DCI position with the Director of National Intelligence (DNI) and the DCID series with the Intelligence Community Directive (ICD) series — older DCIDs remain in force where not superseded and continue to govern legacy intelligence community processes.

"DCID — legacy IC directives from before the DNI replaced the DCI in 2004."

DCID is the legacy series of intelligence community directives that the Director of Central Intelligence used to issue before the 2004 Intelligence Reform and Terrorism Prevention Act split the CIA Director role from the IC Director role and created the Director of National Intelligence. The DNI replaced DCIDs with the Intelligence Community Directive (ICD) series going forward — but older DCIDs that haven't been superseded are still in force, and intelligence professionals who came up in the legacy system reference DCID numbers from memory. DCID 6/3 (information system security) and DCID 6/9 (physical security standards for SCIFs) are two of the more frequently cited surviving DCIDs. The series is a piece of IC organizational archaeology that still shows up in day-to-day work.

A formal recommendation, submitted under joint capability development processes, that a specific gap in joint capability be addressed through changes in Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, or Policy (DOTMLPF-P) — typically generated through Capability-Based Assessments (CBAs) and processed through the Joint Capabilities Integration and Development System (JCIDS).

"DCR — DOTMLPF-P change recommendation, the joint-capability-gap response document."

DCR is the formal mechanism for proposing a non-materiel solution to a joint capability gap — when a Capability-Based Assessment identifies a gap, the resulting recommendation might be a new materiel program (an Initial Capabilities Document leading to acquisition) or a DCR that changes doctrine, training, organization, leadership and education, personnel structure, facilities, or policy without buying new equipment. The acronym DOTMLPF-P (the older DOTMLPF before Policy was added in the 2010s) is the framework that organizes capability development thinking; DCRs are the institutional artifacts that translate framework analysis into recommended changes. Most joint capability work doesn't result in a new program of record — most of it results in DCRs that adjust how the existing force fights, trains, or organizes.

The most punitive discharge characterization, imposed only by a general court-martial. Reserved for offenses considered inconsistent with continued service in the armed forces.

"Reserved for the most serious court-martial convictions."

A DD is the worst administrative outcome of military service. It bars almost all VA benefits, federal employment, and federal firearms ownership. Upgrade is theoretically possible through BCMR but exceptionally rare. If you are facing potential DD-track charges, civilian counsel with court-martial experience is worth the cost.

A multi-purpose Department of Defense form used to requisition, issue, ship, or transfer property and materials, particularly for transactions that do not fit the MILSTRIP 1348 format.

"A multi-purpose form for non-MILSTRIP property transactions."

The 1149 covers the cases the 1348 does not: hand-to-hand transfers of accountable property between activities, non-standard issues, and shipping documents for property moves that lack a standard NSN. It is the form you use when the system will not let you cleanly use a 1348 — including for excess property turn-ins to DLA Disposition Services in some cases.

The standard MILSTRIP-formatted document used to record a single line item of requisition, issue, receipt, or transaction within the Defense Logistics Management System.

"The standard DoD requisition document."

The "1348" is what a supply transaction looks like on paper. The 1348-6 is the manual requisition; the 1348-1A is the issue release/receipt document that travels with the part. Most service members do not touch the form directly anymore — GCSS-Army and equivalents render it electronically — but every supply transaction in DoD ultimately resolves to a MILSTRIP 1348 record. The supply clerks and warehouse personnel are the ones who handle the printed copies.

The Department of Defense form used to record the facts and circumstances surrounding the loss, damage, or destruction of government property, and to document the resulting financial liability determination.

"The form that opens an investigation into lost or damaged property."

A DD-200 starts the FLIPL — the formal investigation that traces lost or damaged property back to a hand-receipt holder and assesses financial liability. If your signature is on the hand receipt and the item walks, the investigator will get to you; pay garnishment can run up to one month's basic pay (or actual cost, whichever is less, under most circumstances). The investigation also generates a counseling and a paper trail that follows you, so read what you sign and inventory what you take.

The Department of Defense form issued at separation from active duty, documenting service dates, awards, training, characterization of service, narrative reason for separation (SPD code), and reenlistment eligibility (RE code).

"Your DD-214 is the document that proves your service."

The DD-214 is the single most important document of your military life after you separate. Every VA, employment, education, and federal benefit claim depends on it. Keep multiple certified copies (free from the National Archives at archives.gov/veterans). The "long form" includes the SPD code and characterization narrative — most benefits applications require the long form, not the short form. Errors in the DD-214 (missing awards, wrong dates, wrong characterization) can be corrected through DD Form 215 (minor) or BCMR (substantial).

The standard form used to document inspection and acceptance of supplies or services delivered under a federal contract, providing the formal record by which the government acknowledges receipt and accepts the deliverable.

"The form that documents government acceptance of contracted goods."

Signing the acceptance block on a DD-250 commits the government to having received the goods; the contractor cannot get paid without it (or its electronic equivalent in WAWF/iRAPT). Signing wrong — accepting items that do not meet the spec, missing quantity discrepancies — starts a paperwork chain that is hard to walk back. Quality assurance personnel inspect, the COR or KO accepts; the line between the two roles matters when something turns out to be defective later.

The formal joint resolution of Congress, exercised under Article I Section 8 Clause 11 of the United States Constitution, declaring that a state of war exists between the United States and a named adversary — last invoked in June 1942 against Bulgaria, Hungary, and Romania, and not invoked in any military operation since World War II.

"A formal congressional declaration of war under the Constitution."

Congress has formally declared war 11 times across 5 conflicts: the War of 1812, the Mexican-American War, the Spanish-American War, World War I, and World War II. Every major US conflict since WWII has been conducted under presidential authority, AUMF, or treaty obligations — Korea (UN mandate), Vietnam (Gulf of Tonkin Resolution), Iraq 1991 (UN mandate plus PL 102-1 authorization), and the entire post-2001 counterterrorism period (2001 AUMF and 2002 Iraq AUMF). The substantive question of whether a Declaration of War is constitutionally required for major sustained operations remains unresolved in practice.

The DoD database of all active-duty, Reserve, retired service members, their dependents, and other eligible beneficiaries. Source of truth for ID card issuance, Tricare eligibility, and benefit entitlements.

"DEERS keeps your benefits and family eligibility up to date."

If DEERS is wrong, your benefits are wrong. Marriages, divorces, births, and deaths must be updated within strict windows — failure to update creates billing surprises with Tricare, denied prescriptions, and dependents locked out of base. Check your record at every PCS and every life event. The system will not call you when something breaks.

The process of releasing Reserve Component members from active duty after mobilization, including the medical, administrative, and benefits processing required to transition the member back to reserve or civilian status.

"The process of releasing reservists from active duty after mobilization."

Demob is the back end of mobilization — the medical, administrative, financial, and benefits processing that closes out the active-duty period and transitions the member back to reserve status (or to retirement, separation, or continued active service depending on the case). Reverse SRP, LOD finalization for any conditions arising during mob, post-deployment health assessment and reassessment (PDHA/PDHRA), and the family of benefits decisions all happen in the demob window. Doing demob carelessly creates years of follow-on VA and benefits problems.

The structured process by which a Reserve Component unit returns from active duty to Reserve Component status, including medical and dental out-processing, separation from active duty entitlements, transition of personnel records, equipment reset, and the formal release from Title 10 orders back to Title 32 or SAD status, conducted at designated demobilization stations.

"The Reserve Component return-from-active-duty process."

Demobilization is the bookend to mobilization — RC units returning from deployment process through the demobilization station, complete post-deployment health assessments, transition their records, account for equipment, and formally return to RC status. The PDHA (Post-Deployment Health Assessment) and PDHRA (Post-Deployment Health Reassessment, conducted months later) are key components — the institutional response to the medical and mental health issues that emerge in the months after return from deployment. Demobilized members retain TRICARE coverage for a limited transition period.

A Department of Defense program established under 10 USC §2701 to identify, investigate, and clean up environmental contamination at active DoD installations, formerly used defense sites (FUDS), and Base Realignment and Closure (BRAC) properties — covering hazardous substances, unexploded ordnance, building demolition and debris, and other environmental hazards resulting from past DoD operations — funded through Service-specific Environmental Restoration accounts.

"DERP — the DoD environmental cleanup program for contaminated installations and former sites."

DERP is the DoD program that pays to clean up the environmental legacy of past military operations — the program that funds investigation and remediation of contaminated soil, groundwater, unexploded ordnance, and demolition debris at active installations, formerly used defense sites, and properties that went through Base Realignment and Closure. Service members rarely hear the acronym directly, but if a base they're stationed on has a remediation project (a fenced-off area where contractors are testing groundwater, a UXO clearance team on a former range, a building demolition with asbestos abatement), DERP is usually the funding source. The program lives under 10 USC §2701 and is one of DoD's standing obligations under federal environmental law (CERCLA, RCRA). The political contention is mostly about pace and scope — the legal obligation itself is settled.

The DoD-specific supplement to the FAR, codified at 48 CFR Chapter 2, adding DoD requirements and policies on top of the FAR.

"DoD-specific rules layered on top of the FAR for defense contracting."

DFARS is where DoD adds counterintelligence requirements (DFARS 252.204-7012 cyber), country-of-origin restrictions, and the long tail of program-protection clauses. Defense contracts are FAR-plus-DFARS; whichever is more restrictive wins. The DFARS Procedures, Guidance, and Information (PGI) is the implementation guidance most program offices actually use.

A Defense Intelligence Agency-managed program that coordinates analytic production responsibilities across the defense intelligence enterprise — assigning primary analytic responsibility for specific countries, regions, functional topics, and adversary capabilities to DIA, the Service intelligence centers (NGIC, MCIA, ONI, NASIC), combatant command joint intelligence operations centers, and other defense intelligence components — preventing duplication of effort and ensuring analytic coverage of the full defense intelligence problem set.

"DIAP — the DIA-managed program that assigns who in defense intelligence covers what."

DIAP is the division-of-analytic-labor program for defense intelligence — the DIA-led process that decides which defense intelligence component (DIA, NGIC, MCIA, ONI, NASIC, COCOM JIOCs) has primary analytic responsibility for which countries, regions, functional topics, and adversary capabilities. The program matters because without it the defense intelligence enterprise would either duplicate effort (multiple components writing the same assessment) or leave gaps (no one owning a topic until it becomes urgent). For analysts, DIAP determines which target list their unit owns and which they support; for managers, it determines headcount and program funding allocations. The construct has been adjusted multiple times as the threat picture has shifted — the China-and-Russia great-power-competition pivot of the late 2010s and 2020s drove significant DIAP rebalancing across the Service intelligence centers.

The date a member first entered into a military service status, used to determine the retirement system the member falls under (Final Pay, High-3, REDUX, or the Blended Retirement System) and various legacy retirement and benefit calculations, distinct from PEBD which governs pay-table longevity.

"The date that determines which retirement system the member falls under."

DIEMS is what determines which retirement plan applies — members with DIEMS before 8 September 1980 are under Final Pay; 8 September 1980 to 31 July 1986 are High-3; 1 August 1986 to 31 December 2017 had a choice between High-3 and REDUX (with the CSB bonus); from 1 January 2018 onward, members entered the Blended Retirement System (BRS) or could opt in if their DIEMS qualified. DIEMS never changes — even with breaks in service, the initial-entry date determines retirement system. PEBD can move; DIEMS cannot.

The United States Coast Guard's integrated personnel and pay system, operated by Coast Guard Personnel Service Center, providing self-service access for active-duty, Reserve, and civilian Coast Guard personnel to pay records, orders, evaluations, leave, and other personnel transactions.

"The Coast Guard personnel and pay system."

Direct Access is the Coast Guard's single integrated system — uniquely, both personnel and pay live in the same platform, which is the kind of integration the Army is fighting toward with IPPS-A. Coast Guard members use Direct Access for orders, e-resume updates that feed assignments, evaluation tracking, leave submission, and the LES is generated and viewable directly. The Coast Guard sits under DHS rather than DoD, but coordinates with DFAS for cross-system reciprocity in joint billets. For Coasties, the all-in-one approach has its own pain points but avoids the personnel-vs-pay seam that the DoD services run into.

A coordination authority granted by a commander or headquarters that permits a subordinate or external organization to communicate and coordinate directly with another organization on specified matters without routing communications through the granting headquarters — enabling operational agility while preserving overall command authority by establishing the scope and limits of the direct liaison — commonly used between joint task force components, between combatant commands and Service components, and between US and partner-nation forces.

"DIRLAUTH — formal permission to coordinate directly with another organization without going through higher."

DIRLAUTH is the procedural authorization that lets a unit talk directly to another unit without routing through higher headquarters — without DIRLAUTH, formal communications between organizations at different parts of the chain of command are supposed to go up to a common superior and back down, which is slow and bureaucratic. With DIRLAUTH, a JTF logistics directorate can talk directly to TRANSCOM, a brigade S-3 can coordinate directly with an adjacent Service component, and partner-nation liaison officers can coordinate with US units on specified matters. The scope and limits are spelled out: DIRLAUTH is always on specified matters, not a blanket authorization. The construct shows up constantly in operations orders and coordination instructions; it's one of the everyday institutional mechanisms that makes joint operations procedurally workable.

A Department of Defense organization, headquartered in Mountain View, California (with offices in Boston, Austin, Chicago, Washington DC, and elsewhere), that accelerates the adoption of commercial technology by DoD through prototype contracts under Other Transactions Authority, working directly with commercial technology firms (often non-traditional defense vendors) on focused capability problems.

"The DoD organization in Silicon Valley accelerating commercial technology adoption."

DIU (originally DIUx, the "experimental" suffix dropped in 2018) is the institutional bet that DoD has to meet commercial technology firms where they are rather than asking them to navigate the FAR — physically located in Mountain View, structured around commercial-engagement norms, and operating primarily through OTA prototype contracts with rapid evaluation cycles. The portfolio spans AI, autonomous systems, cyber, energy, human systems, and space. Phase III commercial scaling is the open challenge: many prototypes succeed, but transition to production buys through service program offices remains the harder step.

A formal Department of Defense logistics policy and procedural publication, issued under the authority of the Under Secretary of Defense for Acquisition and Sustainment, prescribing standard procedures for logistics functions across the Department — covering supply, transportation, maintenance, and related logistics business processes that span Service boundaries.

"DLM — DoD-level logistics manuals that set the rules across all Services."

DLM is the publication series that sets DoD-wide logistics policy and procedures — the documents that tell every Service how the joint logistics business processes work, where data interchange standards apply, what coding schemes are mandatory, and how cross-Service support obligations work. The DLMs are the source documents that get translated into Service-specific regulations (Army AR 700-series, Navy NAVSUPINST series, Air Force AFI 23-series), and disputes between Services over logistics support obligations get resolved by pointing at the relevant DLM. For supply, transportation, and maintenance professionals at the policy level, the DLMs are the source of truth; for everyone downstream at the unit level, they are felt indirectly through Service implementing regulations and the DLMS data exchange standards.

The Department of Defense business-system architecture and data-exchange standard for logistics operations across the Services and Defense Logistics Agency, providing standardized electronic data interchange (EDI) transactions, common data definitions, and process integration for supply, transportation, finance, contracting, and maintenance functions — superseding the legacy MILSTRIP/MILSTRAP/MILSTAMP standards.

"DLMS — the EDI standard that lets Army, Navy, Air Force, and DLA systems talk to each other."

DLMS is the data-exchange backbone of joint logistics — the EDI standard that replaces the legacy MILSTRIP (supply requisitioning), MILSTRAP (stock accounting), MILSTAMP (transportation) message formats with modern X12-based transactions that move between Service supply systems, the Defense Logistics Agency, contractors, and finance systems. For program managers, system owners, and developers building or sustaining a logistics system, DLMS compliance is non-negotiable: a system that doesn't speak DLMS can't exchange data with the rest of the joint logistics enterprise. The transition from the legacy formats to DLMS has been a multi-decade modernization that is still not fully complete, which is why supply professionals occasionally still have to deal with hybrid environments where both standards coexist.

A Department of Defense organization, located at Seaside, California, that operates the Defense Enrollment Eligibility Reporting System (DEERS) as the authoritative source of personnel and benefits eligibility data, and provides identity management, manpower analysis, and data services across DoD.

"The DoD office that owns DEERS and authoritative personnel records."

DMDC is the keeper of DEERS — the single source of truth for who is in the military, who their dependents are, what benefits they're entitled to, and what their identity is for CAC and ID-card production. Every Tricare eligibility check, every CAC certificate issuance, every MilConnect login, every base-access transaction ultimately queries DMDC systems. When DEERS shows a spouse as un-enrolled and the spouse can't get on base or fill a prescription, that is a DMDC data issue the member fixes at a RAPIDS site. DMDC is invisible to most service members until it isn't — and then it's everywhere.

The DoD's acquisition policy publications — DoDD 5000.01 (The Defense Acquisition System), DoDI 5000.02 (Operation of the Adaptive Acquisition Framework), and related instructions covering specific acquisition pathways.

"The DoD's acquisition policy library."

The 5000-series is acquisition's constitutional law. DoDI 5000.02 introduced the Adaptive Acquisition Framework with six tailored pathways (Urgent Capability, Middle Tier, Major Capability, Software Acquisition, Defense Business Systems, Acquisition of Services). Which pathway a program uses dramatically changes the reviews, milestones, and reporting it has to clear. Pick the pathway deliberately; switching mid-program is expensive.

The senior tier of Department of Defense policy issuance — a Directive establishes policy, assigns responsibilities, delegates authority, and provides general guidance for the Department — issued by the Secretary of Defense (or by the Deputy Secretary on the Secretary's behalf) and remaining in effect until rescinded or superseded.

"DODD — the top-tier DoD policy document that sets policy and assigns responsibilities."

DODD is the top tier of the DoD policy stack — Directives are the documents that set Department-wide policy, define who is responsible for what, and grant the authorities under which the rest of the institution operates. Below DODDs in the hierarchy are DODIs (Instructions, which implement Directives with procedural detail) and DODMs (Manuals, which provide the granular how-to). For action officers in OSD, the Joint Staff, or a Service headquarters who are writing or revising policy, knowing which tier a piece of guidance belongs in is fundamental: a Directive that should be an Instruction will be over-engineered and a procedural rule that needs to be a Directive will lack the authority weight it needs. The DoD Issuances website is the authoritative source; the lifecycle from draft through coordination through signature is long, sometimes years.

The authoritative Department of Defense regulation governing financial management policies and procedures — issued by the Under Secretary of Defense (Comptroller) — covering accounting, budgeting, disbursement, military pay, civilian pay, contractor payments, travel pay, and the financial controls under which the Department executes appropriated funds.

"DODFMR — the DoD-wide financial management regulation governing every dollar."

DODFMR is the regulation that comptrollers, finance officers, disbursing officers, and travel pay technicians actually live in — a massive multi-volume document organized by topic that prescribes how the Department accounts for money, pays its people, pays its contractors, and audits itself. The Comptroller (USD-C) owns it. For the service member dealing with a finance issue (an erroneous BAH stoppage, a travel voucher dispute, a survivor benefits calculation), the relevant DODFMR volume and chapter is the rulebook the finance office is following, and citing it correctly in an inquiry tends to produce faster and better answers than emotional escalation. For comptroller-track officers and enlisted finance specialists, mastery of the DODFMR is essentially the entire career skill.

The implementing tier of Department of Defense policy issuance — an Instruction provides procedures to implement a policy established in a Directive, assigns specific responsibilities, prescribes procedures, and includes the detail needed for execution — issued by the Office of the Secretary of Defense Principal Staff Assistants under authority delegated by the Secretary.

"DODI — the procedural document that implements a higher-level DoD policy."

DODI is the tier of DoD policy that does the actual work for action officers and program managers — Instructions translate the broad policy in a Directive into specific procedures, responsibilities, timelines, and reporting requirements that programs can execute against. Where a DODD might say "the Department will ensure cybersecurity of all systems," a DODI tells you what categories of system, what controls, who certifies, on what schedule, and what to do when something fails. For action officers, finding the right DODI is the first move on almost any task; for compliance professionals, demonstrating conformance to the relevant DODI is the daily work. The DoD Issuances site indexes them by number, and the numbering scheme (e.g., 5000-series for acquisition) groups related issuances.

The procedural detail tier of Department of Defense policy issuance — a Manual implements a Directive or Instruction by prescribing detailed procedures, technical guidance, or operating standards — typically issued by an OSD Principal Staff Assistant under authority delegated by the Secretary, providing the granular how-to that supports Directive policy and Instruction procedure.

"DODM — the detailed how-to manual that supports a higher-level Instruction."

DODM is the bottom tier of the DoD policy stack — Manuals provide the granular procedural detail, technical guidance, or operating standards that implement an Instruction. Where a DODI might say "the program will conduct annual reviews using the procedure in the corresponding Manual," the DODM is where the procedure is actually laid out. For compliance officers, security managers, training developers, and any specialist whose work depends on following standardized procedures, the relevant DODM is the working document. The DODM tier is also where DoD-wide forms, checklists, and structured-data definitions tend to live. The full Directive-Instruction-Manual hierarchy means that any major DoD policy is documented across all three tiers, and an action officer drafting policy has to decide what belongs in each tier.

The federal law enacted as Public Law 96-513 and codified primarily at 10 USC 611-651, that established a uniform framework across the active components for officer appointment, promotion, separation, and retirement, including the up-or-out promotion structure, statutory promotion zones, and tenure limits for active-duty commissioned officers below flag and general officer rank.

"The 1980 statute creating the active-component officer up-or-out promotion framework."

DOPMA is the load-bearing wall under the active-component officer career — it sets the up-or-out structure (promotion zones, fail-of-selection consequences, mandatory retirement points), the statutory authorized strength of each grade, and the procedures for promotion boards. The framework is forty-plus years old and has been a perennial target of reform proposals; meaningful changes have been made at the margins (talent-management reforms, modified board procedures) but the basic architecture remains. Officers who fail of selection for promotion under DOPMA are subject to involuntary separation per the statutory structure.

In joint logistics, "days of supply" — a measure of on-hand stocks of a class of supply expressed as the number of days the stockage will sustain operations at planned consumption rates, used for both stockage objective calculations and operational sustainment assessments. Separately, "DOS" also refers to the United States Department of State — the executive department responsible for foreign policy and diplomatic relations, with which DoD coordinates on virtually all overseas operations.

"DOS — either "days of supply" in logistics planning or "Department of State" in foreign relations."

DOS is one of the dictionary entries where the same acronym carries two unrelated meanings, and which one is meant depends entirely on context. In logistics shops, DOS is "days of supply" — the measure that tells a commander how long the on-hand stock of a particular class will last at the planned burn rate, the metric that drives reorder triggers, sustainment risk assessments, and the war reserve materiel stockage objectives. In policy and operational documents, DOS is the Department of State — the State Department, the institutional partner DoD coordinates with on every overseas deployment, every status-of-forces agreement, every security cooperation activity, and every embassy interaction. The DoD Dictionary lists both meanings together because both are legitimate joint usage; the reader has to disambiguate from context. Misreading "DOS" in a logistics annex as State, or vice versa, has happened more than once.

The Joint Capabilities Integration and Development System (JCIDS) construct identifying the seven domains across which a capability gap can be addressed — used as the analytic lens for capability solutions before a materiel program is initiated, with DOTMLPF-P adding Policy as an eighth domain in current usage — the framework that ensures capability gaps are examined for non-materiel solutions before defaulting to acquisition programs.

"DOTMLPF — the seven domains every capability gap gets examined against before buying something."

DOTMLPF is the analytic checklist that JCIDS uses to make planners look at every domain before recommending the Army or any Service buy a new thing — the idea being that a lot of capability gaps are actually doctrine problems, training problems, or organizational problems, not materiel problems. The construct has been the gatekeeper at the front end of the acquisition process for years; the current form is usually written DOTMLPF-P with Policy added as an eighth domain. For people inside the requirements process, DOTMLPF is the framework you cite when arguing that a problem can be solved without a new program of record — and that's also why it has a reputation as the bureaucratic obstacle that programs work to clear before they can actually start. The construct is one of the most-cited acronyms in Pentagon staff work.

A Department of Commerce-administered program (15 CFR Part 700) that allows DoD and certain other federal agencies to place priority-rated contracts (DO-rated and DX-rated) ahead of unrated commercial orders in the industrial base — the principal regulatory mechanism for ensuring that defense contracts receive industrial base priority during peacetime and surge conditions.

"DPAS — the rating system that lets DoD contracts jump the queue in the industrial base."

DPAS is the regulatory authority that lets a DoD contracting officer put a DO or DX rating on a contract and require the supplier to prioritize it ahead of unrated commercial orders — the mechanism by which a defense program can get an industrial-base supplier to deliver a critical component on time even when the supplier has other paying customers. DO-rated orders take precedence over unrated; DX-rated orders take precedence over both, and are limited to programs with explicit DX authority. The system is one of the quiet structural supports of the defense industrial base — most contracting officers use it routinely, most suppliers know how to read the ratings, and most service members never hear about it. DPAS authority traces to the Defense Production Act.

Two distinct DoD usages: (1) the Deception Planning Cell, the small compartmented team within a joint or component headquarters operations directorate that plans military deception operations in support of the commander's scheme of maneuver; and (2) the Defense Pricing and Contracting office under the Under Secretary of Defense for Acquisition and Sustainment, providing DoD-wide contracting policy and pricing oversight.

"DPC — either the deception planning cell on the staff, or the OSD contracting policy office."

DPC is one of the DoD Dictionary entries where the same three letters carry two completely different meanings depending on context. In an operational headquarters, DPC is the Deception Planning Cell — the compartmented planners who build the MILDEC plan that feeds into DOWG coordination. In the acquisition world, DPC is Defense Pricing and Contracting, the OSD office that owns contracting policy across the department. The two never overlap in conversation: deception planners are in a SCIF, DPC contracting policy people are in the Pentagon E-Ring, and you'll know from the room you're in which DPC is being referenced. The DoD Dictionary captures both because both are doctrinally established.

In joint intelligence terminology, the staff officer or organization responsible for managing the dissemination of intelligence products to authorized consumers — controlling the flow of intelligence reporting, ensuring appropriate classification and foreign disclosure controls, and managing the architecture by which finished intelligence reaches its intended audience across the joint force and interagency partners.

"DPM — the intel staff officer who runs how intelligence products get pushed to consumers."

DPM is the dissemination side of the intelligence cycle — the planner who decides which products go to which consumers, in what format, at what classification, with what foreign disclosure markings. The work is unglamorous: every finished intelligence product has consumers who need it and consumers who shouldn't see it, and the DPM is the staff officer who runs the actual mechanics of getting reports onto the right networks at the right releasability. In a joint task force J-2, the DPM coordinates with the foreign disclosure officer, the security manager, and the J-6 communications staff. For consumers downstream, the DPM's work is invisible until something doesn't arrive — at which point the DPM is the person who can explain why.

The Department of Defense Web-based system, operated by US Transportation Command's Surface Deployment and Distribution Command, that service members and DoD civilians use to manage household-goods shipments during a PCS — including counseling, shipment scheduling, transportation service provider selection, packing/pickup/delivery tracking, and claims submission.

"The DoD portal for managing PCS household goods shipments."

DPS (move.mil) is the system every PCSing service member curses at while trying to get their household goods scheduled — entitlements counseling, packout date selection, TSP (transportation service provider) coordination, shipment tracking, weight ticket submission, claims for items damaged in transit. The DPS user experience has been the subject of multiple GAO and IG reviews; the rollout of GHC (Global Household Goods Contract, an effort to consolidate moves under a single managed-services contractor) is the structural attempt to fix the experience. PCS season (May-September) is when DPS slowness, unavailable packout dates, and dropped TSP commitments are most acute.

A service-specific board with authority to upgrade or change the characterization of service for veterans discharged within the past 15 years (excluding discharges resulting from general court-martial). Less powerful than BCMR but faster and more accessible.

"A way for veterans to seek an upgrade to their discharge characterization."

DRB is the first stop for most discharge upgrade requests. It cannot review GCM-imposed discharges and cannot consider applications outside the 15-year window. The Hagel Memo (2014) and Kurta Memo (2017) direct boards to give liberal consideration to upgrades involving PTSD, TBI, military sexual trauma, and other behavioral health conditions related to the service. Free representation is available through VSOs and law school clinics — use it.

The Defense Logistics Agency component responsible for the receipt, accountability, demilitarization, reutilization, transfer, donation, and sale of surplus and excess Department of Defense property; renamed DLA Disposition Services in 2010.

"The DoD activity that handles surplus and excess property."

DRMO is the end of the supply chain — turn-in for surplus, broken, or no-longer-needed property. The name officially changed to DLA Disposition Services in 2010 but the legacy term sticks because everyone trained pre-2010 used it. Doing a turn-in properly is how a unit closes hand receipts cleanly; doing it wrong leaves ghosted property on the books that the next change-of-command inventory has to track down. Demilitarization codes on items determine whether they can be sold, donated, or only destroyed.

A Service-level or OSD-level staff officer responsible for managing requirements documentation and the requirements review process within a department, ensuring that capability requirements are properly documented (Initial Capabilities Document, Capability Development Document, Capability Production Document) and properly staffed through the JCIDS process before becoming programs of record.

"DRO — the department requirements officer who manages capability documents through JCIDS."

DRO is the staff position that does the unglamorous paperwork of requirements management — keeping the ICD, CDD, and CPD documents organized, tracking the staffing process through the JCIDS review cycle, and being the institutional memory for why a particular requirement was written the way it was. The work is what makes the difference between a clean acquisition baseline and a program that has unclear requirements three years later. For an O-4 or O-5 detailed to a Service requirements shop or an OSD requirements office, DRO is the title that often comes with the assignment. The role is one of the structural backbones of the capability development system; it is also one of the assignments that looks routine on paper but quietly shapes major programs.

The Department of Defense's authoritative system for reporting unit readiness, established under DoD Directive 7730.65, in which commanders report their unit's ability to execute the missions for which it was organized — assessed across personnel, equipment on-hand, equipment serviceability, and training — for visibility from the unit level up through the Joint Chiefs and Office of the Secretary of Defense.

"The DoD system where commanders report unit readiness."

DRRS is where the "C-rating" of every unit gets reported up the chain — C-1 (fully capable) through C-5 (programmed not-ready), with separate ratings for personnel (P-level), equipment on hand (S-level), equipment serviceability (R-level), and training (T-level). Commanders own the call but the data feeding it comes from across the unit staff, and the temptation to round up is constant — explaining a C-3 to the brigade commander is harder than explaining a C-2 with a footnote. DRRS visibility goes up to the JCS and OSD; the assessment is consequential for force allocation decisions and for what the unit gets prioritized for in resourcing. Service-specific versions (DRRS-A, DRRS-N) feed the joint DRRS-S.

The Department of Defense enterprise readiness reporting system at the strategic level, providing the integrated readiness picture for OSD, the Joint Staff, and senior decision-makers across the joint force — successor and complement to the legacy Status of Resources and Training System (SORTS) and the broader DRRS family that includes Service-specific variants (DRRS-Army, DRRS-Navy, DRRS-MC, DRRS-AF) feeding strategic-level rollups.

"DRRS-S — the strategic-level DoD readiness reporting system, OSD/Joint Staff rollup."

DRRS-S is the strategic-level readiness reporting layer that OSD, the Joint Staff, and senior leaders use to see the integrated picture of joint force readiness across Services and combatant commands. Each Service feeds its own DRRS variant (DRRS-Army, DRRS-Navy, etc.) up to DRRS-S, with unit-level commanders providing the source data through commander's assessments. For a battalion or wing commander, DRRS reporting is the monthly grind of assessing your unit's readiness against the DRRS criteria — and the words you put in the commander's narrative travel up the chain to where senior leaders make resourcing and employment decisions. The system replaced SORTS and continues to evolve; the doctrinal basis is in CJCSI 3401.

A Department of Defense information system for tracking and reporting on individuals held in DoD detention facilities — the system of record for detainee accountability, capturing the detainee's identification, capture circumstances, processing actions, current status, and movements through the detention enterprise in compliance with the Geneva Conventions and DoD detention policy.

"DRS — the DoD system of record for detainee accountability and reporting."

DRS is the system the detention enterprise uses to keep accountability of every person held in DoD custody — capture data, identification including biometrics, processing actions through the detention facility, status changes (interrogation, release, transfer, repatriation), and the data feeds that go to ICRC for Geneva Conventions compliance reporting. For a 31E internment/resettlement specialist, MP working a detention facility, or detainee operations officer, DRS is the daily workspace. The system's lineage runs from the post-Abu Ghraib reforms that drove detention accountability infrastructure forward and the broader detention policy framework in JP 3-63. Detainee operations is one of those mission sets that has to be done meticulously because failures generate strategic-level consequences.

A Service-level prescriptive readiness construct that assigns specific readiness levels to specific units at specific times to align readiness production with anticipated employment demand — the modern evolution of the legacy "tiered readiness" construct, now used to drive resourcing priorities, training cycles, and modernization investments across a Service's force.

"DRT — the table that tells Service planners which units need to be at what readiness when."

DRT is the construct that translates anticipated employment demand into prescriptive readiness levels by unit and time — telling the Army (or Navy, or Air Force) which units need to be in which readiness state for which window. The construct replaced the older tiered-readiness approach and is used to allocate scarce training resources, sustainment funding, and modernization investments across the force. For a brigade or wing commander, DRT is the institutional pressure that determines how much training capacity, ammunition, and parts your unit gets for a given window — and the rotation of which units carry the high-readiness designation is part of how Services manage the force generation cycle. The construct is one of the structural mechanisms of the modern readiness enterprise.

Engineering-led testing during system development to verify that a system meets contract specifications and is technically mature enough to proceed to operational test.

"Engineering testing to confirm a system performs as designed."

DT&E findings shape the technical baseline of a program. Failure during DT&E can delay milestone decisions, trigger redesign, or expose contract change requirements. The reports are typically program-internal until rolled up to milestone reviews. Programs that try to compress DT&E typically pay for it in OT&E, when an operational test finds problems engineering testing should have caught.

A Department of Defense organization, located at Fort Belvoir, Virginia, that serves as the central repository for Department of Defense scientific and technical information, providing access to research reports, journal articles, and other technical documents to authorized users within DoD, federal agencies, and the broader defense research community.

"The DoD central repository for scientific and technical research information."

DTIC is where DoD-funded research reports and technical literature live — a research library that lets cleared researchers and engineers find prior work, avoid reinventing wheels, and build on existing technical foundations. The collection runs into the millions of documents across decades. Public-release versions of many reports are available to anyone; restricted-distribution versions require credentials. For program offices, DTIC is the place to start when scoping a new technical effort: most problems have prior research, and DTIC is where to find it.

A Department of Defense policy instrument issued by the Office of the Secretary of Defense to direct DoD-wide action ahead of the formal DoD Directive (DoDD) or DoD Instruction (DoDI) issuance process — provides immediate policy authority for matters requiring action faster than the formal directive-development timeline allows — typically incorporated into a DoDD/DoDI within a defined time window (commonly one to three years) or formally extended.

"DTM — the OSD policy memo that directs DoD action faster than a formal directive can be issued."

DTM is how OSD makes binding policy when the formal DoDD or DoDI process would take too long — the Secretary or Deputy Secretary signs a memorandum that directs immediate DoD-wide action, with a built-in expectation that it will get rolled into a formal directive within a specified window (often one to three years, sometimes extended). For the Services and components, a DTM has the same compliance weight as a directive but lives outside the regular DoDD/DoDI numbering system, which means tracking it requires watching the DTM library separately. The instrument has been used for fast-moving topics — pandemic response, new technology rules, personnel-policy adjustments — where waiting for the multi-year directive process would mean operating without guidance.

The Defense Transportation Regulation (DoD 4500.9-R), a multi-part regulation issued by US Transportation Command (USTRANSCOM) governing the movement of cargo, personnel, household goods, and mortuary affairs across the Defense Transportation System — comprises Part I (Passenger Movement), Part II (Cargo Movement), Part III (Mobility), Part IV (Personal Property), Part V (Department of Defense Customs and Border Clearance Policies and Procedures), and Part VI (Defense Personal Property Program).

"DTR — USTRANSCOM's transportation regulation; governs every PCS move, every cargo lift, every mortuary case."

DTR is the USTRANSCOM regulation that governs movement across the Defense Transportation System — every PCS household-goods move (Part IV), every passenger booking (Part I), every cargo container heading to a port (Part II), every mortuary case home from overseas (Part V customs procedures interact). The regulation is enormous (thousands of pages across the parts) and most service members never read it directly; they encounter it through transportation officers, household goods counselors, and the JTR rules that intersect with it. For TMOs (Transportation Management Offices), PPSOs (Personal Property Shipping Offices), and the contractors who handle cargo and household goods, DTR is the daily reference. The Defense Personal Property Program changes (HomeSafe Connect / Global Household Goods Contract rollout) have been driven by DTR Part IV and Part VI revisions.

The DoD-wide enterprise travel management system used by service members and civilians to plan, authorize, book, and settle official travel under the Joint Travel Regulations.

"The DoD-wide travel management system."

DTS is the application every service member learns to hate eventually — authorizations, reservations, vouchers, and reimbursement all run through it for TDY (and many PCS) moves. The interface is older than many of its users; the workflow is unforgiving (a single typo on a flag drops the authorization back to the originator); and the rules are governed by the Joint Travel Regulations, which are themselves not a model of brevity. SAP/Concur components are the technology under the hood. Plan to spend more time on DTS than on the trip itself the first few times.

A Department of Defense financial-management information system used to manage the accounting and financial reporting for Defense Working Capital Fund (DWCF) activities — the revolving-fund mechanism through which DoD support functions (depot maintenance, supply, transportation, base operating support) charge their customers (Service operating forces, other DoD components) for services rendered — providing the ledger underneath the fee-for-service business model that funds much of DoD's industrial and support enterprise.

"DWAS — the back-office ledger for DoD's revolving working-capital fund."

DWAS is the back-office accounting system that runs Defense Working Capital Fund activities — the revolving-fund mechanism through which depot-level maintenance providers (Tobyhanna, Anniston, Letterkenny, etc.), DLA supply chains, MSC sealift, and base operating support providers charge their Service and component customers for goods and services. The fund recovers its costs from those customer payments rather than from direct appropriation each year, which means the accounting integrity that DWAS provides is what keeps the model honest. For comptrollers and resource managers working DWCF activities, DWAS is the system of record; for everyone else, it's invisible plumbing that nonetheless determines whether a unit's O&M budget is sufficient to actually cover the support services it consumes.

The submarine engineering department division responsible for the ship's service electrical generation and distribution systems — staffed primarily by Electrician's Mates (Nuclear) (EMN) — owns the turbine generators, motor generators, ship's service electrical distribution, electrical breakers and switchgear, battery, shore power connections, and the electrical infrastructure that the reactor plant feeds.

"E Division — ship's service electrical, the EMN home division."

E Division is the electrical division — the EMNs who own the ship's service electrical generation (the turbine generators that the reactor's steam drives), the motor generators, the electrical distribution and breakers, the battery, and the shore-power connection that powers the boat in port. On submarines, E Division also owns the high-voltage systems that propulsion electrical drives (the main motor circuits depending on hull class). The division is smaller than ML in headcount but operationally consequential — every system on the boat needs electrical, and the casualty response for electrical faults (ground faults, generator trips, distribution failures) is heavy and time-pressured. EMNs in E Division stand the engine-room electrical watches and qualify EWS like other senior nukes.

A formal plan that defines emergency-response procedures, decision authorities, evacuation routes, and crisis communications for a specific facility, unit, or mission — at US embassies and consulates, the EAP is owned by the Emergency Action Committee (EAC) and defines mission response to security incidents, natural disasters, NEO triggers, and political crises; analogous EAPs exist at DoD installations, deployed units, and combatant commands.

"EAP — the emergency action plan; every embassy, installation, and major unit has one."

EAP is the plan that defines what happens when things go wrong — at an embassy, it's the EAC-owned document that governs evacuation triggers, safe-haven procedures, and NEO coordination; at a DoD installation, it's the plan that covers active-shooter response, severe-weather sheltering, hazmat events, and force-protection escalation; at a deployed unit, it's the plan that covers attack response, mass-casualty events, and emergency-evacuation procedures. EAPs are not glamorous documents but they are the difference between an organized response and a chaotic one when the alarm sounds. For action officers tagged with EAP maintenance, the work is mostly bureaucratic — keeping rosters current, exercising the plan annually, updating contact information — until the day it matters operationally.

The Marine Corps term for the date a Marine's active-duty enlistment contract ends. EAS is the Marine Corps equivalent of the Army, Air Force, and Space Force "ETS." Separation processing, terminal leave, and administrative separation timelines are governed by MCO 1900.16 (Marine Corps Separation and Retirement Manual) under the framework of DoDI 1332.14.

"Your contract has a clear end date."

EAS is real until the Corps decides it is not — stop-loss has been used in living memory, mission requirements can hold a Marine past the printed date, and unit outprocessing pace decides whether you actually walk on time. Marines who PCS within months of EAS get caught in the "two clocks" problem (PCS report date vs EAS terminal leave), and the wrong call here can mean an unplanned reenlistment or a paperwork scramble. Plan terminal leave deliberately — count the days you have, count the days the command needs you on station, and work backward. Do not sign a civilian lease, accept a job start date, or move a family until orders are cut and the I&I or RS has the final-out checklist running. The printed EAS is the goal, not the guarantee.

The Veterans Benefits Administration line of business, organized within VBA as the Education Service, responsible for administering all VA-administered education benefits — including the Post-9/11 GI Bill (Chapter 33), the Montgomery GI Bill (Chapter 30), Survivors' and Dependents' Educational Assistance (Chapter 35), Chapter 31 VR&E benefits, and related programs — primarily processed at four Regional Processing Offices.

"The VBA line of business that processes GI Bill and related education claims."

The Education Service (often referred to loosely as the "Education Benefit Administration") is the VBA line of business that owns GI Bill processing — Post-9/11 Chapter 33, Montgomery Chapter 30, Survivors' and Dependents' Chapter 35, plus interfaces with the Chapter 31 VR&E side of the house. Most processing concentrates at four Regional Processing Offices (RPOs) — Buffalo, Atlanta, Muskogee, and St. Louis. The Veteran-facing portal is the GI Bill Comparison Tool and the education-claim status visibility on VA.gov; the school-facing portal is the WEAMS/VA-ONCE infrastructure that certifying officials use. Veterans dealing with delayed GI Bill housing allowances, kicker disputes, or transfer-of-entitlement issues are dealing with this organization — the SCO at the school is the front-line interlocutor, and a VSO can help when the issue escalates.

A formal environmental assessment of a site, conducted prior to use or transfer, to document existing environmental conditions including soil and groundwater contamination, hazardous materials presence, regulated wastes, and other environmental factors — used by DoD before establishing operations at a foreign or domestic site, before transferring a site to another party, and at the conclusion of operations to support cleanup determinations and liability scoping.

"EBS — the environmental snapshot before DoD moves onto a site or hands it back."

EBS is the formal environmental snapshot that documents what was already at a site before DoD started using it — and matched against the closeout EBS at the end of operations, it determines what contamination DoD caused vs. what was pre-existing, which determines who pays for what cleanup. The work is procedurally heavy: site walkthroughs, soil and groundwater sampling, historical-records research, regulatory consultation, formal documentation that survives the eventual base-closure or site-transfer dispute. For Naval Facilities Engineering Systems Command and Army Corps of Engineers personnel who execute EBSes, the surveys are the institutional memory that protects DoD from picking up other parties' environmental liabilities — or from leaving the government on the hook for cleanups it shouldn't own. The product matters most years later, when the dispute happens.

A formal proposal, submitted to a Department of Defense program office by a contractor or originating activity, that proposes a change to an item's configuration, performance, or documentation — including the technical rationale, cost and schedule implications, and operational impact — for review and approval through the configuration management process, governed by MIL-STD-973 (legacy) or current contractor configuration management standards.

"A formal proposal to change an item's configuration, performance, or documentation."

ECP is the formal mechanism that change requests flow through — a contractor (or government engineering activity) identifies that a change is needed, prepares the ECP with technical details and impact analysis, and routes through the program office's configuration control board for review and approval. Approved ECPs become the basis for the modification, the contract change, and the technical-data update. ECPs are classified by class (I or II depending on impact), priority (routine through emergency), and type. Configuration drift in fielded equipment without proper ECP discipline is a recurring sustainment headache.

A formal study of environmental conditions at a site, conducted to inform basing decisions, site-development planning, or operational planning — typically encompasses climate, terrain, hydrology, flora and fauna, soils, regulated species, cultural and archaeological resources, and other environmental factors that affect facility siting and use — distinct from but related to the Environmental Baseline Survey (EBS) which focuses on contamination conditions.

"ECS — the environmental conditions study that informs DoD basing and site-development decisions."

ECS is the broader environmental-conditions study that DoD basing and facility-planning offices commission to inform decisions about where to put new infrastructure — climate patterns, terrain, hydrology, wetlands, regulated species (Endangered Species Act and migratory-bird considerations), soils, archaeological and cultural-resource constraints, and the broader environmental envelope of a candidate site. ECS is distinct from EBS (which is focused on contamination) and from the NEPA environmental-impact analysis process (which is procedural and decision-supporting), but the three intersect on most major facility decisions. For NAVFAC, USACE, and Service civil-engineer planners, ECSes are the front-end work that determines whether a candidate site is even viable; the unfortunate sites get rejected before NEPA scoping ever begins. The work is invisible to operational forces but underlies the basing decisions they live with.

The structured electronic exchange of business documents (purchase orders, invoices, shipment notices, transportation manifests) between organizations using standardized formats — the DoD logistics, finance, and contracting backbone that moves transactional data between commands, between DoD and industry partners, and between DoD and other federal agencies under DLA, DFAS, and Service-level systems.

"How DoD moves business transactions electronically between commands and contractors."

EDI is the plumbing under DoD logistics, contracting, and finance — the standardized electronic exchange of purchase orders, invoices, shipment notices, and the rest of the transactional document flow that keeps the supply system moving. Most service members never touch EDI directly; what they experience is the downstream effect (the part shows up, the contract gets paid, the requisition closes out). When EDI breaks — bad mapping between trading partners, a corrupted batch, a system migration — the visible symptom is parts that don't arrive, contracts that don't close, and the supply NCO spending a week on the phone with DLA. The DoD has been migrating off legacy EDI formats toward modern APIs for years; the transition is incremental and the legacy traffic is still substantial.

A specific Title 10 USC §127 (and Service-equivalent) authority that permits the SECDEF and Service Secretaries to spend funds for confidential, emergency, or extraordinary purposes that would not normally be charged to regular appropriations — operates under restricted reporting requirements and is subject to congressional oversight.

"Special funding authority for confidential or emergency expenses outside normal appropriations."

EEE is the special-authority fund line the SECDEF and Service Secretaries use for things that can't go through normal appropriation channels — confidential payments, emergency response that outruns ordinary contracting, and a narrow set of extraordinary expenses authorized under 10 USC §127. The dollar amounts are small relative to the overall defense budget, but the authority matters because it's how the Department handles obligations that would otherwise be stuck waiting for normal acquisition cycles. EEE spending is subject to congressional oversight and reporting requirements; the authority is not a blank check. Most service members will never encounter EEE; the comptrollers and the OGC lawyers at the Pentagon are the ones who actually administer it.

A formal performance review process for DoD civilian employees in selected positions (not to be confused with Service-specific enlisted evaluation reports like the Air Force EPR/AFCEP, the Navy EVAL, or the Coast Guard EER which is the Coast Guard Enlisted Employee Review for enlisted members) — codified in the DoD Dictionary as a defined term for the civilian-personnel system.

"Enlisted Employee Review — formal performance review (and confusingly shares letters with multiple Service systems)."

EER in the DoD Dictionary sense is the formal civilian-personnel review process — but the three letters are massively overloaded across the Services. The Coast Guard calls its enlisted evaluation an EER (Enlisted Employee Review). The Air Force used to call its enlisted performance report the EPR and now uses the AF Form 910 / CFETP / AFCEP construct. The Navy uses EVAL and CHIEFEVAL. The Army uses NCOER. So if someone says "your EER is due," your first job is to figure out which system they mean — the Coast Guard enlisted Sailor, the DoD civilian, or one of the cross-talk variants. The actual review mechanics differ across systems but the career-impact dynamic is the same: this is the document that drives promotion, retention, and assignment.

The date from which entitlement to a VA disability compensation award is calculated, generally set under 38 CFR §3.400 as the later of the date entitlement arose or the date the claim was received by VA — with the principal exception that an initial claim received within one year of separation from service generally takes the day after the date of separation as the effective date.

"The date entitlement begins for a VA disability award, driving back pay."

The effective date is the second-most-important number in a disability award, after the rating percentage itself — it determines how far back pay runs from the date the rating is granted. The default rule is later of "date entitlement arose" or "date claim received," with the one-year-post-separation rule being the most consequential exception: a claim filed within twelve months of the DD-214 separation date generally gets an effective date of the day after separation. Intent to File submissions preserve an earlier effective date while the full 526EZ is being prepared. Supplemental Claims filed within one year of the prior decision generally preserve the original effective date under continuous-pursuit rules. Talk to a VSO before accepting an effective date that seems too late — the substance is in 38 CFR §3.400 and the body of M21-1 guidance, and errors are appealable.

A discharge given to a service member separated within the first 180 days of active duty, characterized as "uncharacterized" rather than honorable, general, or other-than-honorable.

"A clean break for those who don't complete the early days of training."

ELS sounds neutral but the "uncharacterized" status complicates VA benefits — most are not available without an honorable or general discharge. If your separation is approaching the 180-day mark, the difference between ELS and a characterized discharge can be significant. If the separation is for your medical condition or unit-side problems rather than your conduct, request honorable characterization in writing.

A congressionally ratified mutual-aid agreement among the fifty states, the District of Columbia, Puerto Rico, the US Virgin Islands, Guam, and the Northern Mariana Islands that allows states to share resources during emergencies and disasters, including the deployment of National Guard forces from one state to another under the requesting state's authority.

"A state-to-state mutual aid compact that allows Guard forces to cross state lines."

EMAC is how Guard forces from one state legally and quickly deploy to another state to assist with hurricanes, wildfires, civil disturbances, and other emergencies — under the requesting governor's authority, with the sending state retaining administrative control of its forces but with operational direction shifted to the requesting state. The compact was ratified by Congress in 1996 and has been used in every major domestic emergency since. EMAC missions are still Title 32 (state) status, not Title 10 (federal), which preserves the Guard's flexible legal posture.

The acquisition life-cycle phase between Milestone B and Milestone C during which the system is engineered, fabricated, integrated, and tested to demonstrate operational effectiveness, operational suitability, and producibility, in preparation for the production decision at Milestone C.

"The acquisition phase between Milestone B and Milestone C for engineering, fab, and test."

EMD is the build-and-test phase — the period when prototypes become production-representative articles, when the system flies, sails, drives, or runs, and when developmental and operational testing happens. Cost growth in EMD is the classic acquisition-failure pattern; the difference between the cost estimate at Milestone B (Approved Acquisition Program Baseline) and actual EMD cost at Milestone C is one of the metrics tracked in SARs and that triggers Nunn-McCurdy breach evaluations.

The Army's legacy active-component personnel management system, fielded in 2003 to replace the field SIDPERS system, providing personnel action processing, strength accounting, and reporting capability at the battalion S1 level — being progressively replaced by IPPS-A across the force.

"The Army's legacy active-component personnel system, being replaced by IPPS-A."

eMILPO was the workhorse of every active-component battalion S1 shop from 2003 until the IPPS-A transition — strength reports, personnel action requests, MOS updates, transfers in and out, leaves and passes recorded in the system. It worked, sort of, the way enterprise government IT systems of its era worked: ugly interface, brittle workflows, but consistent. Personnel NCOs trained on eMILPO have to relearn IPPS-A's PeopleSoft workflow, and the muscle memory friction shows up in error rates during cutover. Once a unit is fully on IPPS-A, eMILPO read-only access remains for historical lookups.

A facility — physical or virtual — that serves as the central coordination point for emergency management activities during incidents, exercises, or contingencies — operated at federal, state, local, tribal, territorial, and military installation levels, with DoD installation EOCs activating for severe weather, mass-casualty events, force-protection incidents, hazardous-material releases, and other emergencies — staffed by representatives of relevant functional areas (security, medical, engineering, public affairs, legal, communications).

"EOC — the room everybody runs to when the installation has an emergency, joint civil-military."

EOC is the room that activates when something has gone wrong — a hurricane bearing down on the installation, an active-shooter incident, a hazardous-material release at the fuel farm, a mass-casualty event in housing. The standing structure has seats for security forces, medical, engineering, public affairs, legal, comms, and the chain of command; when the EOC stands up, those seats fill and the installation runs through that room until the situation is back inside garrison-normal parameters. For installation leadership, EOC drills are a recurring fact of life because activation muscle memory atrophies quickly; for the people on the seats, real activations are when the gap between the exercise SOP and the actual chaos becomes obvious. The same EOC concept scales — joint task force EOCs, COCOM emergency centers, FEMA-coordinated multi-agency EOCs — but at every level the function is the same: a single room where the right people can make coordinated decisions in real time.

A reference publication used at installation or facility level to organize emergency-management planning — typically covering hazard identification, response procedures, notification and recall procedures, mutual-aid agreements, evacuation planning, and continuity-of-operations procedures — supports the broader emergency-management framework that installation EOCs activate during incidents.

"EPH — the installation emergency planning handbook, the reference behind every EOC activation."

EPH is the installation-level reference that organizes emergency-management planning into a single working document — the hazards the installation faces (severe weather, mass-casualty events, hazmat releases, force-protection incidents), the response procedures for each, the notification and recall chains, mutual-aid agreements with off-installation responders, evacuation routes, and continuity-of-operations procedures for when normal installation operations have to suspend. The handbook is the reference behind the EOC activation runbook — when the EOC stands up for a real event, the staff is working from the EPH framework even when the situation diverges from the rehearsed plan. For installation emergency managers, keeping the EPH current is the recurring administrative work; for the leadership and the EOC seats, the EPH is the institutional memory that makes the activation orderly.

The Army worksheet used to compute the promotion-point total for soldiers in the semicentralized promotion population (SGT and SSG promotion), aggregating points from awards, civilian and military education, weapons qualification, physical fitness, height/weight, and other categories under the schedule established in AR 600-8-19.

"The Army worksheet computing promotion points for SGT and SSG promotion."

EPPW is how an Army E-4 promotes to E-5 (SGT) and how an E-5 promotes to E-6 (SSG) — the soldier accumulates promotion points across categories (awards, military and civilian education, weapons qualification, AFC physical fitness, board appearance, and others), and the resulting total determines whether they meet the monthly cutoff score for their MOS. The cutoff scores are published by HRC and vary monthly by MOS based on Army needs. Soldiers manage their own EPPW with their unit S1; errors in posting can cost months of promotion timing.

The Air Force's periodic performance evaluation for enlisted Airmen (E-1 through E-9), reviewed by promotion boards and selection processes.

"EPRs document performance and support promotion through the enlisted ranks."

EPRs (now in transition under recent Air Force evaluation changes) drive enlisted promotion alongside test scores (PFE/SKT for some grades). Top blocks have been historically inflated; bullets and stratification statements are what distinguish records. Read every draft. A weak EPR can be appealed before signing; once filed, correction is a long boards process.

The DoD Dictionary message-format abbreviation for "engineer" — used as a short-code in joint message traffic, requirements documents, task-organization slides, and personnel-coding fields where the longer form would be unwieldy; not to be confused with Service-specific engineer officer designators (the Army CMF 12 engineer branch, the Navy CEC Civil Engineer Corps, the USAF civil engineer career field) which use their own coding schemes.

"ERT — the joint shorthand for engineer in message traffic and task-org slides."

ERT is one of those one-line entries in the DoD Dictionary that exists because somebody has to standardize the three-letter abbreviation that appears in five thousand staff products a day. In practice nobody says "ERT" out loud — they say "engineer" or "engineers" or "sappers" depending on Service — but the abbreviation lives in message-format fields, in slide footers labeling task organization, in the requirements documents that flow from a J-staff to a Service component. The lesson for a new joint-staff officer is just that when the field calls for ERT, it means engineer, full stop. For the actual engineer career fields and force structure, see the Service-specific entries (CMF 12, CEC, USAF Civil Engineer career field).

The Department of Defense readiness reporting system that aggregates unit-level data on personnel, equipment on hand, equipment serviceability, and training proficiency into the standardized C-rating (C-1 through C-5) construct — the enhanced successor to the legacy SORTS Status of Resources and Training System — feeds into the Joint Force Readiness Review and into the broader Defense Readiness Reporting System (DRRS) architecture.

"ESORTS — the DoD readiness reporting system behind every unit C-rating roll-up."

ESORTS is the readiness reporting system every unit commander knows because they sign the monthly readiness report — personnel strength, equipment on hand, equipment serviceability, training proficiency, all rolled into the C-rating (C-1 fully ready, C-5 not ready / undergoing maintenance or training reset). The data feeds upward into the Joint Force Readiness Review and into DRRS, which is how the Joint Staff and the Service Chiefs answer the SECDEF question of how ready the force actually is. ESORTS is the enhanced successor to the legacy SORTS that operations officers and admin warrants spent decades wrestling with. The system is consequential because it shapes resource allocation, deployment sourcing, and the public narrative on military readiness — and because every commander knows the gap between the C-rating their unit reports and the readiness they actually believe they have.

Two distinct constructs sharing the abbreviation: (1) Engineer Support Plan — an annex or supporting plan in the Joint Operation Planning Process that defines engineer task organization, construction priorities, real-estate requirements, environmental considerations, and engineer logistics for a campaign or operation; and (2) Estimating Supplies Program — a computational tool that generates Class I (subsistence), Class III (POL), Class V (ammunition), and other class-of-supply consumption estimates for force packages over a planning horizon.

"ESP — same abbreviation, two planning worlds: engineer support annex or supplies consumption estimator."

ESP is one of those abbreviations where context decides the meaning. In a J5/J7 planning shop, ESP is the Engineer Support Plan — the annex that walks through which engineer units do what work, where the airfield repair priorities are, what real estate the force needs, and which environmental constraints apply. In a J4 logistics shop, ESP is the Estimating Supplies Program — the tool the staff uses to generate Class I (food and water), Class III (POL fuels), Class V (ammunition) and other class-of-supply consumption estimates that drive force-flow and resupply planning. Both are normal parts of campaign planning and both will appear in the same operations order, just in different annexes. Staff officers learn to read which ESP a paragraph is talking about by the words that surround it.

A joint and Service planning product that identifies the specified, implied, and essential tasks derived from mission analysis, mapped against the units or staff elements responsible for each task — a foundational output of the Joint Planning Process and the Military Decision Making Process (MDMP) — used to ensure tasks are assigned, tracked, and resourced across the operational planning effort.

"ETM — the matrix that captures essential tasks from mission analysis and assigns each to a responsible element."

ETM is one of the staff products that comes out of mission analysis and that anyone who has been through a planning conference knows by sight — the matrix that lists every specified, implied, and essential task derived from the higher headquarters' order, mapped against who in the command is responsible. The matrix is the artifact that prevents tasks from falling through the cracks during execution; if a task isn't on the ETM with an owner, it doesn't get done. For the staff officer building the matrix, the work is genuinely valuable — translating a multi-paragraph order into discrete, assignable tasks — even though the product itself looks like a spreadsheet. The ETM is one of those tools that distinguishes a planning shop with good staff process from one that runs on personality.

The date on which a service member's current enlistment contract ends and they may separate, reenlist, or extend. ETS is the standard Army, Air Force, and Space Force term; the Marine Corps uses EAS and the Navy uses Soft EAOS/EAOS. Separation processing and timelines are governed by AR 635-200 (Army) and parallel service regulations under the framework of DoDI 1332.14.

"Your contract has a clear end date. You will know exactly when you are done."

The ETS date is real until it is not. Stop-loss is on the books and has been used in living memory; mission requirements can extend you under involuntary measures; your unit's outprocessing pace and the SRP/medical/dental/clearance lanes decide whether you walk on time. Plan as if you will leave on your ETS — but do not sign a civilian lease, accept a job start date, or move a family before the orders are cut and the final-out checklist is complete. Terminal leave is the lever most people use to get off the books early; understand how much you have accrued and how the days count before you build a transition plan around it.

A contracting and acquisition mechanism authorized under specific statutory provisions that allows the government to exchange property, services, or other consideration of approximately equal value with a contractor or partner — used in narrow circumstances (in-kind property exchanges, swap arrangements for installation services, certain real-estate transactions) — distinct from the standard appropriated-funds purchase model that dominates DoD contracting.

"EVE — the narrow contracting authority for equal-value exchanges of property or services instead of cash."

EVE is one of those contracting authorities that most Service members never encounter directly, but that contracting officers and installation real-estate offices know well. It allows the government to trade something of value (a parcel of installation real estate, a piece of equipment, a service) for something of approximately equal value from a contractor or partner, without the standard appropriated-funds purchase mechanism. The authority is narrow and tightly bounded by statute — it is not a way around the Federal Acquisition Regulation — but in the right circumstance it lets a base swap an underutilized piece of property for a needed service or facility upgrade in a way a normal contract could not. For 1102 contracting officers, EVE is one of the niche tools that occasionally solves a problem nothing else can; for everyone else, it lives in the policy footnotes.

A project management system, required on most Department of Defense contracts above specified dollar thresholds, that integrates the project work scope, schedule, and cost into a single performance measurement framework, comparing budgeted cost of work performed (BCWP, or "earned value") against budgeted cost of work scheduled (BCWS) and actual cost of work performed (ACWP) to produce schedule and cost variance and forecast metrics.

"A contract-required performance measurement system tracking cost, schedule, and scope."

EVMS is the standard cost-and-schedule control system on major DoD contracts — the contractor maintains an EVMS-compliant system, reports monthly Contract Performance Reports (CPRs), and the government uses the data to forecast cost at completion and to identify program problems early. The metrics (CPI, SPI, CV, SV, EAC, TCPI) are universal across EVMS programs. Industry compliance with EVMS standards (EIA-748) is itself a certification process. EVMS is often criticized as paperwork-heavy and gameable, but remains the standard.

A formal joint or DoD order issued by the Secretary of Defense (typically through the Chairman of the Joint Chiefs) directing a combatant command to execute a specific military operation — distinct from a Warning Order (WARNORD, prepare to act) and a Planning Order (PLANORD, develop a plan) — the EXORD contains the authorities, rules of engagement, force allocation, and operational constraints under which the named operation will execute.

"EXORD — the formal SECDEF order to execute a military operation, the document that turns plans into action."

EXORD is the order that turns planning into execution — the formal directive from the Secretary of Defense (signed by the Chairman and transmitted through the Joint Staff to the combatant command) that says: execute the named operation, under these authorities, with these rules of engagement, with these forces, subject to these constraints. The sequence usually runs WARNORD (warning), PLANORD (plan it), EXORD (do it), but in fast-moving contingencies the EXORD can come without a preceding PLANORD if the planning is already done. For combatant command planning shops, the EXORD is the single most operationally consequential document — every constraint in the EXORD, every named ROE, every approved force list, defines what the force can and cannot do. Junior J5 / J3 staffers learn fast that reading the EXORD carefully (and the supporting CJCS DEPORD that flows below it) is not optional.

The maintenance level performed by support maintenance organizations (in Army nomenclature, the Brigade Support Battalion's maintenance company, or the Sustainment Brigade; in Air Force nomenclature, the Maintenance Squadron; in Navy nomenclature, the Intermediate Maintenance Activity) that exceeds the user unit's capability but does not require depot-level facilities — including more complex troubleshooting, component repair, and limited rebuild.

"The intermediate-level maintenance: more complex repair than O-level, less than depot."

F-Level (Army; combines older "Direct Support" and "General Support" levels) or I-Level (Air Force; "Intermediate") is the middle tier — support-maintenance organizations with more tools, parts (ASL), specialized test equipment, and certified-skill personnel than the user unit, but without the depot facilities. Work scope: subassembly repair, complex troubleshooting, calibration, and limited rebuild of selected components. The line between F-level and D-level evolves with technology — modular Line Replaceable Units have pushed more work to D-level depots and less to F-level organizations as systems modernize.

A numerical priority code (I through V, with I highest) assigned to a unit, organization, or activity that defines its priority in supply support, depot maintenance, transportation, and other logistics services — combined with the Urgency of Need Designator (UND) at the requisition level to produce the Priority Designator (PD) that determines order processing speed within the Defense Logistics Management System.

"F/AD — the I-through-V force priority code that drives supply, maintenance, and transportation priority."

F/AD is the priority code that decides whose supply requisitions and maintenance jobs jump the line and whose wait. The Force/Activity Designator runs I (highest, deployed combat forces, presidential support, etc.) through V (lowest, certain Reserve Component and support activities), and it combines with the requisition's Urgency of Need Designator (UND) to produce the Priority Designator (PD) that flows through the Defense Logistics Management System. Every supply NCO, every maintenance warrant, and every property book officer knows their unit's F/AD and what it means for how fast Class IX parts arrive and how their MILSTRIP requisitions get prioritized. The system is one of the older and more enduring pieces of joint logistics infrastructure — it predates much of the modern DoD ERP landscape and continues to govern the priority flow underneath it.

A Roman-numeral classification (I through V) assigned to a unit indicating its relative mission criticality, combining with the Urgency of Need Designator to produce the Priority Designator for supply transactions.

"A code expressing a unit's relative mission criticality."

Combat and forward-deployed units get the lower (higher-priority) FADs; training and support activities get the higher numbers. FAD plus UND equals the Priority Designator (1-15), which drives the order in which the supply system processes requisitions. A unit's FAD is assigned by Joint Staff and the components; it is not something a battalion changes on its own when it wants its parts faster.

A joint staff product used in the Global Force Management (GFM) process that arrays force-allocation decisions across combatant commands and time periods, supporting the Secretary of Defense's decisions on rotational force allocation, named-operation force sourcing, and emergent force requirement adjudication — feeds into the Global Force Management Allocation Plan (GFMAP) and the named-operation execution orders that actually flow forces to combatant commanders.

"FADM — the Joint Staff matrix that lays out force-allocation decisions for SECDEF approval."

FADM is the staff product the Joint Staff and the Services use to lay out force-allocation decisions before the Secretary of Defense signs off — the matrix that maps which units go to which combatant commands for which periods, where the gaps are, what the tradeoffs look like when one COCOM's requirement competes with another's. The output feeds into the GFMAP (Global Force Management Allocation Plan) and into the named-operation execute orders that actually flow forces. For Service force-providers, the FADM is one of the most consequential staff products of the year because it determines deployment tempo and unit sourcing decisions that drive the next 12-24 months of force employment. The Joint Staff J35 / J5 and the Service operations deputies are the principal players; the process is rigorous, contested, and often the place where rotational deployment math gets settled.

The primary regulation governing the acquisition of goods and services by all executive branch agencies of the US government, codified at 48 CFR Chapter 1.

"A unified set of rules that ensures fair, transparent federal procurement."

The FAR is the rulebook everyone in federal contracting cites and almost no one reads cover-to-cover. It is also the source of every "we cannot do that" answer that contracting officers give — sometimes correctly, sometimes as a shield. Knowing the FAR Part number that governs your question (15 for negotiated, 16 for vehicles, 33 for protests, 52 for clauses) gets faster, more correct answers than "the FAR says no."

The FAR section governing negotiated contracts — typically for complex requirements where price alone is not sufficient to select the offeror. Includes source selection processes, technical evaluations, and discussions with offerors.

"The framework for complex negotiated federal contracts."

FAR Part 15 source selections are where the largest, most contested contracts live — and where most bid protests originate. The evaluation criteria stated in the solicitation are the only criteria the agency can use; deviating gets sustained at GAO. Best-value tradeoffs (versus LPTA) are the most flexible but also the most appeal-prone. Read the solicitation's Section M (Evaluation Factors) before reading Section L (Instructions to Offerors) — Section M tells you what actually wins.

The federal statute (10 USC §2734 and supplementing regulations) under which the Department of Defense compensates inhabitants of foreign countries for personal injury, death, or property damage caused by noncombat activities of US military personnel or by certain combat activities of forces overseas — the principal authority for foreign claims commissions and the legal framework under which a claims judge advocate adjudicates host-nation claims.

"FCA — the law that lets DoD pay foreign nationals for damage caused by US military operations."

FCA is the law a deployed judge advocate learns in detail the first time a host-nation farmer arrives at the gate with a slaughtered goat, a broken-down wall, or a story about a relative killed in an incident. The Foreign Claims Act authorizes Foreign Claims Commissions to investigate, evaluate, and pay claims by foreign nationals for noncombat damage and certain combat damage caused by US forces — vehicle accidents, weapons mishaps, demolition damage, livestock loss, property destroyed in operations. Claims judge advocates run the commissions; investigations involve site visits, witness interviews, and local market valuations. The payments are typically small in absolute terms but operationally significant — they're the institutional acknowledgment that the US accepts responsibility for the harm its forces cause, and they're the line between an aggrieved community and an enemy recruitment pool.

A standing analytic body within the Joint Requirements Oversight Council structure, organized by functional area (Force Protection, Force Support, Force Application, Logistics, Battlespace Awareness, Net-Centric, Building Partnerships, Corporate Management and Support, and similar designations), that staffs and recommends action on JCIDS documents and joint capability proposals in its functional area.

"A JROC-supporting board that staffs capability documents by functional area."

FCBs are where the staff-level review of JCIDS documents happens before JROC sees the package — each FCB is co-chaired by Joint Staff and service representatives, organized around a functional area, and produces the recommendation that JROC then accepts, modifies, or sends back. The FCB layer handles the bulk of the actual analytic and equity-resolution work; JROC validates the result. Programs spend significant Program Office time staffing through FCBs, often months per document round.

A documented plan, required for single-parent service members, dual-military couples with dependents, and certain other categories of service members with sole-care responsibility for family members, designating short-term and long-term caregivers and identifying the legal, financial, medical, and logistical arrangements for the care of dependents during deployment, training, or other absences.

"A required care plan for single and dual-mil parents."

A Family Care Plan is mandatory paperwork for service members in covered categories — short-term caregiver (typically within driving distance, ready to receive children on short notice), long-term caregiver (named for the duration of any extended absence), and the legal documents (powers of attorney, medical authorizations, financial arrangements) that let the caregiver actually function. Reviewed annually and on major life events (PCS, change in family status, change in caregiver availability). Failure to maintain a valid FCP can result in administrative actions up to separation; the consequences are not theoretical. The plan is filed with the unit; the legal documents go with the caregiver.

The Defense Logistics Agency's catalog query application providing access to the Federal Logistics Information System (FLIS) data — item characteristics, references, management data, and supersession history.

"The standard government catalog look-up tool."

FEDLOG (Web-FEDLOG is the current portal) is where you search by NSN, NIIN, part number, CAGE, or item name to find what an item actually is and who manages it. It is also where you find supersession chains when an NSN has been replaced. Older offline-disk versions are still kicking around in motor pools that lost network connectivity; if you are reading this from a maintenance shop, you have probably opened it today.

Property of the US government located in a foreign country that has been determined excess to the needs of the federal agency holding it, available for transfer to foreign governments under foreign assistance authorities or for disposal under DoD foreign excess property disposition procedures — the broader category that includes foreign excess personal property (FEPP) as the personal-property subset.

"FEP — US government property abroad declared excess, available for foreign-assistance transfer or disposal."

FEP is the broader bucket of US government property overseas that has been declared excess to mission needs and is available for disposition. The category encompasses real property (land, buildings) and personal property (vehicles, equipment, supplies); the personal-property subset is the more operationally significant FEPP. The reason FEP exists as a category is the recurring problem of US forces accumulating equipment overseas — base buildup during a contingency, equipment beyond drawdown needs, supplies that exceed redeployment lift — and the institutional pathways to either transfer that property to a foreign government as security assistance, gift it under specific authorities, sell it through Foreign Military Sales, or dispose of it without simply leaving it for the host nation to inherit by default. The administrative discipline matters; uncontrolled FEP disposition has historically created accountability problems.

The personal-property subset of foreign excess property — US government movable property (vehicles, equipment, supplies, parts, materiel) located in a foreign country and determined excess to federal agency needs, available for transfer to foreign governments under foreign assistance authorities (including 22 USC §2557 grant authority for excess personal property to foreign governments) or for disposal under DoD foreign excess property disposition procedures.

"FEPP — US movable property abroad declared excess, grantable to foreign governments under security cooperation authorities."

FEPP is the personal-property side of the excess-overseas-equipment story and the more operationally significant piece because vehicles, weapons, ammunition, and equipment are what tends to accumulate during contingency operations and drawdowns. The 22 USC §2557 authority allows the President to grant FEPP to foreign governments in support of US foreign policy objectives; the practical pathway runs through the Defense Security Cooperation Agency and the in-country security cooperation organization. Equipment that would otherwise have to be packed and shipped home — or, worse, abandoned — can instead build partner capacity in the country where it's already located. The discipline is in the accountability and authorization paperwork; the strategic argument is that FEPP transfers can be one of the higher-return security cooperation tools per dollar of US government cost.

The periodic performance evaluation for Navy and Marine Corps officers and senior enlisted (E-7 and above for Navy; E-5 and above for Marines), reviewed by promotion and selection boards.

"FITREPs are how the Navy and Marine Corps recognize your performance."

FITREPs are scored against the rest of the reporting senior's group, so your number depends on who you are reported with. Two outstanding officers reported under the same boss compete for the same top slot. Know who your peers are in the reporting group, and have a candid conversation with your reporting senior at the start of the cycle, not the end.

An Army investigation into the loss, damage, or destruction of government property, used to determine whether a soldier should be held financially liable.

"An investigation when government property is lost or damaged, to determine responsibility."

A FLIPL can take real money out of your pay, capped at one month's base pay for soldiers (different rules for officers and civilians). The standards are negligence and proximate cause — both must be established. You have the right to review the investigation, submit a rebuttal, and request reconsideration. Do all three. JAG legal assistance handles FLIPL rebuttals and the standard rebuttal often reduces or eliminates liability.

A legacy DoD-developed automated legal-research system that provided federal statutes, regulations, case law, and legal opinions in electronic form to military and federal legal communities — predecessor to commercial legal research services and now superseded by commercial Westlaw / LexisNexis subscriptions and the Library of Congress electronic resources used across the JAG corps.

"FLITE — the DoD's original computerized legal research system, since superseded by commercial tools."

FLITE is one of those acronyms that survives in the DoD Dictionary largely as a doctrinal artifact — the federal-legal-information-through-electronics system was the early DoD attempt at computerized legal research in the era before Westlaw and LexisNexis became the standard tools across the JAG corps and the federal legal community. The lived reality for a judge advocate, paralegal, or trial defense services attorney today is that legal research runs on commercial subscription services plus the Library of Congress and federal court electronic resources, not on a DoD-internal database. FLITE is worth knowing for two reasons: the acronym still appears in older doctrinal documents and historical case files, and the underlying point — that legal research access is a real readiness issue for deployed legal teams operating on degraded bandwidth — has not gone away. The bandwidth question for legal reachback is a real planning factor in deployed operations.

The DoD-wide manpower tracking and reporting system used by the "Fourth Estate" — the defense agencies and field activities outside the Military Departments (DoD-level agencies including DISA, DLA, DCSA, DTRA, DCAA, and the Office of the Secretary of Defense components) — to manage authorized manpower, civilian and military fills, and personnel reporting across the OSD-controlled portion of the Department.

"FMTS — the manpower-tracking system for DoD agencies outside the Services (the "Fourth Estate")."

FMTS is a back-office DoD personnel system most service members never touch but that controls the manpower architecture of the defense agencies. "Fourth Estate" is Pentagon shorthand for the chunk of DoD outside the four Services — the defense agencies (DISA, DLA, DCSA, DTRA, DCAA, MDA, and the rest), the field activities, and the Office of the Secretary of Defense components — which collectively employ a six-figure civilian and military workforce. FMTS is the system of record for authorized manpower in those organizations, used to manage civilian billets, military fills against joint duty assignment requirements, and personnel-strength reporting up to OSD Personnel and Readiness. A service member on a joint tour at DISA, DLA, or one of the other Fourth Estate agencies is in FMTS; the system rarely makes itself visible until somebody's position description, billet authorization, or PCS orders need to be reconciled against it.

The process by which an officer is selected for promotion to the grade of rear admiral (lower half) or above in the Navy or Coast Guard — beginning with a service selection board recommendation, requiring Secretary of Defense and Presidential approval, and subject to Senate confirmation under 10 USC 624 and the constitutional Appointments Clause.

"The selection and confirmation process for Navy and Coast Guard flag officers."

FO selection is the Navy and Coast Guard counterpart to GO selection — same statutory architecture (10 USC 624, the Appointments Clause), same Senate-confirmation pathway, same OSD-centralized position-fill above the service decision. The Navy's flag-officer detailing community is small and tightly managed; assignments are matched against specific flag billets, with assumption of command and ceremony scheduled around the confirmation. Coast Guard flag-officer numbers are statutorily limited and the community is correspondingly small.

The modern US Army framework for managing the readiness and availability of operational forces, replacing ARFORGEN, organized around continuously maintained readiness across the force rather than cyclic surge-and-reset, with units expected to maintain high readiness states for routine availability rather than cycling through dedicated availability windows.

"The post-ARFORGEN Army framework for continuously maintained force readiness."

The Sustainable Readiness Model is the current Army framework — the institutional shift from "cycle units through readiness" to "maintain readiness continuously." The model recognizes that the operational demand of the post-OEF/OIF period (regular deployment to multiple theaters, continuous engagement) doesn't fit the ARFORGEN cycle assumption. Force generation under SRM puts more individual unit responsibility on sustained training, with FORSCOM managing the validation and sourcing pieces. The model continues to evolve; the FY24 and beyond Army force management approach reflects further refinement.

The VA form a claimant uses to formally appoint a Veterans Service Organization (VSO) as their accredited representative in matters before VA, granting the VSO authority to access the claim file, file documents on the claimant's behalf, and communicate with VA on the claim — distinct from VA Form 21-22a, which appoints an individual accredited attorney or claims agent.

"The form that appoints a VSO as your accredited representative."

VA Form 21-22 is how a veteran formally hands the keys to a VSO — DAV, VFW, American Legion, state department of veterans affairs, or any other VA-accredited service organization. Once filed, the VSO can pull the C-file, file evidence and forms on the veteran's behalf, and represent in any review or appeal short of the U.S. Court of Appeals for Veterans Claims (which requires an accredited attorney). 21-22a is the sibling form for appointing an individual accredited attorney or claims agent. Filing one of these forms before submitting a 526EZ is generally the highest-leverage move a veteran can make on a disability claim — VSO representation costs nothing, and a good VSO catches procedural and substantive issues a self-represented veteran will miss.

The standard VA application form used by veterans to claim disability compensation and related compensation benefits, including initial claims, claims for increased evaluation of established service-connected conditions, and claims for secondary service connection — filed electronically through VA.gov or in paper form through a VA Regional Office or accredited representative.

"The VA disability compensation application form."

VA Form 21-526EZ is the form every disability claim runs through — initial claim after separation, claim for an increased rating on a condition that has worsened, claim for secondary service connection when one SC condition causes another. Filed online through VA.gov is faster than paper; either way, the date the claim is received generally sets the effective date for any award (with the one-year-from-separation rule for initial post-separation claims being the most important exception to know about). The Intent to File pathway lets a veteran lock in a potential effective date while gathering evidence to complete the 526EZ. Talk to a VSO before filing the form itself — the way conditions are listed, which DBQs are attached, and which presumptive frameworks are invoked all affect how the claim is adjudicated.

The US Army major command, headquartered at Fort Liberty, North Carolina (formerly Fort Bragg), responsible for training, equipping, and providing combat-ready Army forces (including all conventional active-component, Army Reserve, and Army National Guard forces in the continental United States) to combatant commanders — the Army's force provider.

"The Army major command providing combat-ready forces to combatant commanders."

FORSCOM is the Army's force provider — every Army Combatant Command-bound force packages through FORSCOM-managed sourcing, FORSCOM-validated readiness, and FORSCOM-coordinated deployment. The command oversees the operational Army in CONUS plus the Reserve Component force generation cycle. FORSCOM is the institutional counterpart of AMC (which equips), TRADOC (which trains the individual), the schools (which educate), and the CTCs (which validate at scale). The four-star FORSCOM commander is one of the Army's most senior operational positions.

A Navy and Marine Corps military post office address designator used to route mail to Service members and family members aboard ships, deployed units, and overseas Navy and Marine installations — administered through the Military Postal Service Agency in conjunction with the US Postal Service, with FPO addresses formatted as a CONUS-equivalent address routed through a regional fleet mail center.

"FPO — the military mail address that gets letters and packages to sailors and Marines at sea or overseas."

FPO is the military mail address that lets a sailor on a destroyer in the Mediterranean, a Marine on Okinawa, or a family member of a deployed Marine receive mail without the sender paying international postage. The FPO address looks like a domestic US address — FPO AE 09xxx for Atlantic and Europe, FPO AP 96xxx for Pacific — and gets routed through a fleet mail center to the deployed unit. APO (Air/Army Post Office) is the Army and Air Force equivalent; FPO is the Navy and Marine version. The lived reality for a deployed sailor or Marine is that mail call still matters more than the technology suggests — the rate of packages from home into FPO addresses spikes around major holidays, the deployed unit's mail clerk is one of the more visible members of the crew, and a family's ability to send a care package at domestic-postage rates is a small but real morale anchor.

A formal authorization, granted by the Secretary concerned or designated official, permitting a selected officer to wear the insignia of and assume the title of the next higher grade prior to the actual pin-on of the promotion, typically used to align grade with assignment requirements (joint billets, command positions) when the line number sequence would otherwise delay the actual promotion.

"An authorization to wear the next grade's insignia and title before actual pin-on."

Frocking gives the appearance and authority without the pay or the date of rank — useful when the officer's assignment requires the grade (a joint billet that calls for an O-6 but the officer is line-number deep on the O-6 list, a command-team transition that requires the colonel rank). The officer is "frocked colonel" until pin-on; once the line number is reached, the actual promotion follows and the date of rank is set at the actual pin-on date, not the frocking date. Frocking has no retroactive pay or seniority effect.

The four-digit numeric code at the beginning of an NSN that classifies the item by group and class of supply (e.g., 1005 = Guns through 30mm, 5310 = Nuts, Screws, and Washers, 6135 = Batteries, Primary).

"A four-digit grouping that classifies items by type."

FSCs make the catalog browsable — when you do not have an NSN but know what kind of part you need, the FSC is how you narrow the search. Class managers at DLA buy and stock for their FSCs; if the part you need falls outside DLA's wheelhouse and into a service-managed class, expect longer lead times and different procurement routes. The FSG (Federal Supply Group, the first two digits of the FSC) gives a coarser bucket if you do not know the class.

A unique identifier assigned to a unit, force element, or capability within the joint deployment and distribution system to enable tracking through the time-phased force and deployment data (TPFDD) and related deployment information systems — links a specific unit or capability to its movement, equipment, and personnel data across the deployment process.

"FTN — the unique unit identifier that ties a force element to its TPFDD line and movement data in the deployment system."

FTN is the identifier that lets the joint deployment system keep track of who is going where, on what lift, with what equipment. Every unit and force element in a TPFDD (time-phased force and deployment data) gets an FTN; that number carries the unit's manifest, its equipment list, its required delivery date, its port of embarkation, its port of debarkation, and its onward movement requirements through the joint operation planning and execution system. For an S-4 or a deploying unit movement officer, the FTN is the line they argue about at the SDDC mobility conference — getting the right lift assigned to the right FTN at the right date is the difference between deploying on schedule and missing the window. The system has had multiple generations of supporting software and the operators learn each iteration; the FTN concept survives across versions.

A statutory authority codified at 10 USC 12301(a) that permits the President, in time of war or national emergency declared by the Congress, to involuntarily order to active duty any member of the Ready Reserve, the Standby Reserve, or the Retired Reserve, without numerical cap or time limit during the period of the war or declared national emergency.

"A congressionally authorized callup of all Reserve members for the duration of war or declared national emergency."

Full Mobilization requires a Congressional act (declaration of war or declaration of national emergency) and unlocks the entire Reserve Component force — no numerical cap, no time limit, including the Standby and Retired Reserve populations that the lower-tier authorities don't reach. Full Mobilization has not been invoked since the Cold War era and is the authority that would underpin a major-power conflict response. The personnel infrastructure for managing a Full Mobilization at scale (mobilization stations, demob processing, dependent support) exists but has not been exercised at the scale Full Mobilization would require in living memory.

The broad category of misuse of government resources covered by Inspector General oversight, audit, and investigation — fraud as intentional deception for unlawful gain, waste as extravagant or careless use of resources beyond what is reasonable, and abuse as improper or excessive use of authority or resources — reportable through the DoD Hotline and Service IG channels with whistleblower protections under 10 USC §1034 and related statutes.

"FWA — the IG-owned reporting framework for fraud, waste, and abuse, with whistleblower protections in statute."

FWA is the institutional category every service member learns about during in-processing briefings and the framework the Inspector General owns end-to-end. Fraud is intentional — somebody falsified a travel voucher, padded a contract, or claimed entitlements they didn't earn. Waste is reckless — somebody let perishable supplies expire, ran an exercise twice the size it needed to be, or burned through funds on something that didn't need to be done. Abuse is misuse of authority — somebody assigned a soldier to mow their lawn, used a government vehicle for personal errands, or retaliated against a subordinate for reporting a problem. The DoD Hotline and the Service IG channels take reports; 10 USC §1034 and related statutes provide whistleblower protections that, in theory, shield the reporter from reprisal. In practice the system works inconsistently — talk to a JAG, a TDS attorney, or a military whistleblower advocate before relying on the protections alone.

In the DoD Planning, Programming, Budgeting, and Execution (PPBE) system, the current fiscal year — the year of execution for currently appropriated funds — the first year in the five-year PPBE window (FY1 through FY5) that the Future Years Defense Program (FYDP) covers.

"FY1 — the current fiscal year, the year of execution for currently appropriated DoD funds."

FY1 is the year DoD is executing — the appropriations that have been passed (or operating under continuing resolution), the funds the comptrollers are moving, the contracts being executed, the operations being conducted. In the PPBE construct that runs DoD resource management, FY1 is the first year of a five-year window that runs FY1 through FY5; the Future Years Defense Program covers all five. For a budget officer at a major command, the FY1 fight is the daily fight — moving funds, executing programs, resolving shortfalls, managing year-end closeout. For a deployed unit, FY1 is the year the money showing up in your O&M account was appropriated for. The fiscal year runs October 1 to September 30 — a peculiarity inherited from the 1976 fiscal year transition that everybody on the budget side internalizes early.

In the DoD Planning, Programming, Budgeting, and Execution (PPBE) system, the budget year — the fiscal year for which the President's Budget submission to Congress is being developed and submitted — the second year in the five-year PPBE window — the year DoD is asking Congress to appropriate funds for in the current budget cycle.

"FY2 — the budget year, the fiscal year DoD is asking Congress to appropriate funds for in the current cycle."

FY2 is the fight inside the Pentagon and on Capitol Hill — the budget year for which the President's Budget is being shaped, defended, and submitted. The budget calendar runs roughly two years ahead of execution: the FY2 budget submission goes to OMB in the late summer of FY1, gets a Passback in November-December, lands at Congress in February with the President's Budget, gets marked up by the four defense committees (HAC-D, SAC-D, HASC, SASC) through the spring and summer, and either gets enacted before October 1 of FY2 (rare in recent years) or operates under a continuing resolution until enactment. For action officers across DoD, FY2 is the year of testifying, justifying, defending, and negotiating; for the troops, FY2 is the year the comptroller starts pre-positioning for.

In the DoD Planning, Programming, Budgeting, and Execution (PPBE) system, the program year — the third year in the five-year PPBE window — the year for which programmatic decisions are being made through the Service program objective memorandum (POM) and the DoD Program Decision Memorandum (PDM) process — the principal year of programming activity.

"FY3 — the program year where Service POMs and DoD program decisions are being made."

FY3 is the year the programmers fight over. The POM (program objective memorandum) cycle is where the Services and the combatant commands try to lock in resources for new programs, modernization initiatives, force-structure decisions, and capability investments two years before they show up in a President's Budget. A Service POM gets built in the spring, defended through the Office of the Secretary of Defense Program/Budget Review in the summer, and translated into Program Decision Memorandums and ultimately into the President's Budget submission. For an action officer working a new program — a vehicle modernization, an aviation buy, an unmanned systems capability — the FY3 POM cycle is where the money either gets programmed in or doesn't. Once a program misses a POM cycle, it slips two years; in DoD that's often the difference between fielding on time and falling behind the threat.

In the DoD Planning, Programming, Budgeting, and Execution (PPBE) system, an out year — the fourth year in the five-year PPBE window — a year beyond the budget year for which programming is being projected but for which neither current execution nor active budget formulation is occurring — included in the Future Years Defense Program (FYDP) for planning consistency across the program.

"FY4 — an out year in the PPBE window, projected but not actively budgeted, included in the FYDP for program consistency."

FY4 is the first of the out years — the years beyond the budget year that the FYDP carries for programming consistency but that nobody is actively budgeting yet. The out years matter institutionally because the FYDP is the public commitment of where DoD intends to take its program: capability buys, force structure end-state, modernization phasing. A program shown in FY4 of the FYDP has institutional intent behind it even if no FY4 dollars have been appropriated. The catch is that out-year projections are notoriously elastic — Congressional marks, threat shifts, technology surprises, and administration changes can move FY4 numbers significantly between the POM that programmed them and the budget year that actually appropriates them. Programmers learn to read out-year numbers with calibrated skepticism; the press releases that announce big numbers in FY4 are not the same as appropriated dollars.

In the DoD Planning, Programming, Budgeting, and Execution (PPBE) system, an out year — the fifth and final year in the five-year PPBE window — the furthest projection year in the Future Years Defense Program (FYDP) — projected but neither actively budgeted nor in current execution.

"FY5 — the furthest out year in the PPBE window, the final year of the FYDP projection."

FY5 is the back wall of the five-year PPBE window — the furthest forward year the FYDP projects, and the most elastic year in the program. Major modernization programs and force-structure transitions often have their peak buys planned in FY5 of a given POM cycle because the out-year wedge is where the analytical and political constraints loosen. The corollary is that FY5 numbers move the most between POM cycles: the FY5 of the FY2026 POM looked very different from the FY5 of the FY2024 POM, and so on. For action officers, the discipline is to look at trend lines across multiple POM cycles rather than a single FY5 number. The five-year window itself is bounded by the legal structure of the PPBE process; longer-range planning happens outside the FYDP in the Defense Planning Guidance and the strategic guidance documents that feed the next cycle.

The Department of Defense planning, programming, and budgeting database that aggregates the Secretary of Defense-approved resource allocation for the prior fiscal year, the current fiscal year, the budget year, and the next four out-years (a six-year window), structured by Program Element and Service, providing the integrated long-range view of planned DoD activity and funding.

"The DoD six-year resource allocation plan organized by Program Element."

FYDP is the master spreadsheet of DoD plans — every Program Element, every service, every appropriation type, every year out to BY+4. Programs that "live in the FYDP" have funding lines through the planning horizon; programs that "fall out of the FYDP" lose their planned funding. POM build and program review are FYDP-rebuilding exercises. Industry watches the unclassified FYDP excerpts (and pays for the classified versions through cleared analysts) to forecast future business.

A legacy DoD financial management information system used for accounting, funds control, disbursement, and financial reporting — historically a foundational system across the Department for general ledger and accounting operations — superseded across portions of the Department by successor systems including the Defense Agencies Initiative (DAI), the General Fund Enterprise Business System (GFEBS), and other Service ERP financial systems.

"GAFS — a legacy DoD accounting and finance system, largely superseded by GFEBS, DAI, and other ERP financial systems."

GAFS is the kind of system name that lives mostly in the institutional memory of the financial management community now. A 36B Army financial management technician, a Navy disbursing clerk, or an Air Force financial services specialist with twenty years in remembers GAFS as one of the older financial systems they had to work with before the modern ERP wave. The Department has spent multiple decades and substantial money trying to consolidate dozens of legacy financial systems into modern enterprise resource planning platforms — GFEBS in the Army, the Defense Agencies Initiative across the defense agencies, Navy and Air Force equivalents — and the migrations have been politically contested across audit cycles. The DoD financial audit story is in significant part the story of legacy systems like GAFS and the long process of replacing them. Most service members never touch GAFS directly; the comptrollers know exactly which systems still depend on it.

A legislative-branch agency that audits federal programs, investigates allegations of illegal or improper activities, and issues reports to Congress. In contracting, GAO is the principal forum for bid protests.

"Congress's independent investigative and audit agency."

GAO bid protests are the most-used formal protest forum (alternatives are agency-level protests and the US Court of Federal Claims). A timely protest stays performance on most contracts until decision (the automatic stay), giving protesters real leverage. GAO sustains a meaningful share of protests on the merits, and corrective actions by agencies (re-evaluation, recompetition) resolve many more. Filing fees are low; legal costs can be significant.

A US Department of Defense (Naval Facilities Engineering Systems Command-managed) standing indefinite-delivery, indefinite-quantity construction contract vehicle providing pre-competed contract capacity for rapid contingency construction worldwide — designed to compress the time from contingency requirement to construction execution by avoiding the months-long acquisition timeline of a full source-selection on each project — used for natural disaster response, contingency basing, and other rapid-construction requirements.

"GCCC — the standing NAVFAC IDIQ contract for rapid contingency construction."

GCCC is the pre-competed construction contract vehicle that NAVFAC keeps on the shelf so the joint force can build things fast when a contingency hits — a natural disaster response, a new expeditionary basing requirement, a hurricane-recovery construction surge, a humanitarian operation needing real infrastructure. The vehicle is an indefinite-delivery, indefinite-quantity (IDIQ) contract competed up front with multiple awardees on standing capacity; when a requirement emerges, the contracting team issues a task order against the existing contract rather than running a multi-month source-selection from scratch. The capability matters because construction acquisition is normally slow; GCCC compresses the timeline from months to weeks or days. The vehicle pairs with GCSC (the services-side counterpart) and the broader contingency-contracting toolkit that DLA, NAVFAC, AFCEC, and USACE bring to a contingency.

A US Naval Facilities Engineering Systems Command standing multiple-award contract for contingency construction services — the multiple-award successor and complement to the original Global Contingency Construction Contract, providing additional awardee capacity and competition at the task-order level for contingency construction projects worldwide — used in parallel with GCCC for surge construction requirements.

"GCCMAC — the multiple-award contingency construction contract that runs alongside GCCC."

GCCMAC is the multiple-award flavor of the contingency construction contract toolkit — same NAVFAC ownership as GCCC, same compress-the-timeline purpose, but with the multiple-award structure that lets contracting officers run a fast competition among the awardee pool at the task-order level. The pool of awardees competes for individual task orders rather than the single-award model; the structure is meant to give the government better pricing and capacity than a sole-award contract while still preserving the speed advantage of having the contract on the shelf in advance. GCCMAC and GCCC are the standing construction vehicles a joint task force planner counts on when a contingency needs real infrastructure built fast. The acronym is one of the more obscure ones in joint doctrine but it is real and it gets used.

A US Department of Defense standing indefinite-delivery, indefinite-quantity contract vehicle for contingency services worldwide — the services-side counterpart to the GCCC construction vehicle, providing pre-competed contract capacity for base operating support, life support, transportation, and other services required to stand up and sustain a contingency operation without running a full source-selection on each requirement.

"GCSC — the standing IDIQ services contract for contingency life support and BOS."

GCSC is the services-side companion to GCCC — the pre-competed indefinite-delivery, indefinite-quantity contract vehicle a joint task force or component reaches for when a contingency stands up and the standing force needs base operating support, dining facility services, transportation, fuel handling, billeting management, laundry, and the whole spectrum of services that make a contingency base livable. The vehicle compresses the timeline from months of source selection to days of task-order issuance against the existing contract. The capability matters because contingency basing rises and falls faster than ordinary acquisition timelines can accommodate; without standing vehicles like GCSC, every contingency basing decision would face a multi-month services-contracting tail. The contract is one of the workhorses of contingency contracting, alongside LOGCAP on the Army side.

A US Department of Defense standing multiple-award contract for contingency services worldwide — the multiple-award analog to GCSC, providing additional awardee capacity and task-order-level competition for contingency services requirements — used in parallel with GCSC and other contingency-contracting vehicles such as LOGCAP to support contingency operations and basing.

"GCSMAC — multiple-award services contract that runs alongside GCSC and LOGCAP."

GCSMAC is the multiple-award services flavor in the same family as GCSC (single contract), GCCMAC (multiple-award construction), and GCCC (single construction). The structure gives contracting officers an awardee pool to compete among at the task-order level — better pricing and capacity than a single award, faster execution than building a new contract from scratch. Joint task force contracting and the supporting service components reach for GCSMAC, GCSC, LOGCAP (Army), AFCAP (Air Force), and the broader contingency-services toolkit when a contingency operation stands up. The four vehicles together (GCCC, GCCMAC, GCSC, GCSMAC) are the NAVFAC and joint contingency contracting backbone for construction and services; the LOGCAP / AFCAP family is the Service-component counterpart. The acronyms are unloved but they keep contingency operations supported.

The Army's enterprise resource planning system for tactical sustainment functions, integrating supply, maintenance, property accountability, and financial transactions on a single SAP-based platform.

"The current Army logistics enterprise system."

GCSS-Army subsumed ULLS-G, SARSS, PBUSE, and SAMS-E into one SAP-backed web system. When the servers are up, it is the single window for ordering parts, posting maintenance, tracking property, and reconciling funds. When they are down, motor pools revert to paper and the supply NCOs work nights to catch up. The workflow conventions — masters, ZPARK, ZMM, transaction codes — are the everyday vocabulary of the modern Army supply NCO.

In contracting usage, equipment in the possession of or directly acquired by the government and subsequently furnished to a contractor for performance of a contract — distinguished from contractor-acquired equipment by the funding stream that paid for it and by the property-accountability obligations that follow with it — defined in the Federal Acquisition Regulation (FAR) and Defense FAR Supplement (DFARS) Part 45.

"GFE — equipment the government furnishes to a contractor for contract performance."

GFE is one of the workhorse terms of defense contracting — equipment the government already owns or acquires directly and then furnishes to a contractor to perform a specific contract, rather than having the contractor buy it on the contract and bill the government for it. For a contracting officer the GFE distinction matters because the government retains title (the equipment is still government property), the contractor accepts property-accountability obligations (per the FAR/DFARS Part 45 contract clauses), and the contract pricing reflects the government providing the equipment rather than the contractor providing it. Service members run into GFE-vs-CFE distinctions all the time in equipment-fielding contracts: the government-furnished radio set goes to the contractor for integration; the contractor-furnished cable assembly does not. The distinction shapes the entire contract structure.

In contracting usage, property in the possession of or directly acquired by the government and subsequently delivered to or otherwise made available to a contractor — the broader property-class category that includes government-furnished equipment (GFE) plus government-furnished material (GFM) and other property classes — defined in the Federal Acquisition Regulation (FAR) and Defense FAR Supplement (DFARS) Part 45.

"GFP — the broader property category that includes GFE and GFM furnished to a contractor."

GFP is the broader contracting-property umbrella that includes GFE (government-furnished equipment) and government-furnished material (GFM) along with other property classes — basically anything the government owns and provides to a contractor for contract performance, rather than having the contractor acquire and bill it. The FAR/DFARS Part 45 property-management clauses define the contractor's obligations for accountability, maintenance, use, and disposition of the GFP. For a contracting officer the GFP-vs-CAP (contractor-acquired property) distinction is fundamental to contract structure and to the property-accountability audit chain. The acronym shares letters with the unrelated Global Force Posture-style usages — context tells you which. For property-accountability NCOs and contracting officers, GFP is daily vocabulary.

The process by which an officer is selected for promotion to the grade of brigadier general or above in the Army, Air Force, Marine Corps, or Space Force — beginning with a service selection board recommendation, requiring Secretary of Defense and Presidential approval, and subject to Senate confirmation under 10 USC 624 and the constitutional Appointments Clause.

"The selection and confirmation process for Army/Air Force/Marine/Space Force general officers."

GO selection is a different process from O-1 through O-6 promotion — once a colonel is selected by a GO board, the nomination travels from the service to OSD to the White House to the Senate Armed Services Committee for confirmation hearing and Senate floor vote. Holds at the SASC level have stalled large pools of GO nominations on multiple occasions in recent years for reasons unrelated to the individual officers. GO position-fill is centralized in OSD; the service is the recommendation source, not the decision authority. The PCS, command-assignment, and ADSO mechanics are also non-standard at the GO level.

A federal-employee or service-member-issued credit card used to make authorized micro-purchases of supplies and services under the simplified-acquisition threshold, under the GSA SmartPay program and DoD GPC policy.

"A government credit card for micro-purchases."

The GPC is excellent for buying urgent low-cost items that would otherwise require a months-long requisition cycle — and abused regularly enough that GPC misuse cases appear in IG and audit reports every year. The most common findings are split purchases (breaking a single requirement into several card transactions to evade the micro-purchase threshold), buying personal items, and using the card outside delegated authority. Every cardholder takes mandatory annual training; every transaction is reviewed by an Approving Official.

A DoD-wide information system (Global Status of Resources and Training System) through which units report unit-readiness data — personnel, equipment on-hand, equipment serviceability, and training — generating the C-level (C-1 through C-5) readiness ratings that roll up to senior leaders and combatant commanders as the formal readiness picture.

"The DoD readiness reporting system — generates the C-level ratings up to the COCOMs."

GSORTS is the system every Army battalion S3, every Navy ship XO, every Air Force squadron operations officer dreads filling out and yet has to keep current — the unit-readiness reporting tool that takes personnel strength, equipment on-hand percentages, equipment serviceability percentages, and training-status indicators, and rolls them into a C-rating (C-1 fully ready through C-5 not ready). Those C-ratings aggregate up through service chains and become the readiness picture that COCOMs use to source contingencies and that the senior leadership reviews monthly. The system is consequential — a unit's C-rating affects what missions it gets sourced for, how it's portrayed in readiness testimony, and how its commander is judged — and it's also widely understood to be imperfect, because the inputs are necessarily subjective and the categories don't fully capture modern multi-domain readiness questions.

A government-sponsored, individually-billed credit card issued to service members and civilians who travel on official business, used to pay for transportation, lodging, meals, and incidental expenses on authorized official travel.

"A government credit card used for official-travel expenses."

GTCC is the card you use on official travel, and the card whose late payment can hurt your security clearance. It is individually billed (you pay the card; the government reimburses you through DTS) — so if you delay your voucher, you carry the balance personally. Misuse cases (personal purchases, cash advances beyond travel-related limits) appear in IG reports regularly. The GTCC for PCS moves is a more recent addition and helps members not float thousands in moving expenses on personal cards.

A dual-meaning DoD Dictionary entry: (1) head of a contracting activity, the senior official within a DoD organization who has overall responsibility for managing contracting authority delegated by the Service Acquisition Executive; and (2) humanitarian and civic assistance, the statutory authority (10 USC 401) under which US forces may provide assistance to populations as an incidental benefit of training and operations.

"Either the senior contracting authority in a command or the 10 USC 401 H&CA authority."

Two distinct meanings. Head of a Contracting Activity is the senior leader (often a flag officer or SES) who owns the contracting warrant authority for a major command — every service Service Acquisition Executive delegates HCA authority downward, and the HCA is who contracting officers ultimately answer to within their organization. Humanitarian and Civic Assistance (10 USC 401) is the legal authority that lets US forces conduct medical, dental, veterinary, basic construction, and well-drilling activities for a host-nation population as an incidental benefit of training the deployed unit — it is what authorizes the school-build during a Beyond the Horizon or Pacific Partnership exercise. Context disambiguates instantly: an acquisition shop means the first; a civil affairs or J9 shop means the second.

An AMA appeal lane in which a senior VA reviewer re-examines a decision based on the same evidence in the file at the time of the decision. No new evidence is permitted; the reviewer can identify clear and unmistakable errors and difference-of-opinion issues.

"A senior VA reviewer takes another look at your decision."

HLR is fast (typically months, not years) but the rules are strict — no new evidence. If you have new evidence, the Supplemental Claim lane (not HLR) is the correct path. HLR is best for cases where the decision misapplied law to existing evidence. The optional informal conference with the reviewer is worth requesting; it is the only chance to verbally walk a senior reviewer through your argument.

The senior US representative (head of delegation) designated to lead a US team in negotiations, treaty discussions, multinational planning conferences, or other formal bilateral or multilateral engagements — the HOD holds delegation authority within parameters set by the National Command Authorities, State Department, or relevant DoD principal.

"The senior US lead in a formal negotiation, treaty talk, or multinational conference."

HOD is who has the chair when the US sits across the table — a treaty arms control round, a status-of-forces negotiation, a multinational exercise planning conference. The role carries real authority within the negotiating parameters: the HOD can commit US positions, request caucus, and signal flexibility or hard lines. In DoD contexts the HOD is often a flag officer or senior SES with a delegation of authority letter spelling out exactly what they can and cannot agree to without referring back. For staff officers in the supporting role, HOD prep is its own ritual — read-aheads, talking points, fallback positions, and the inevitable "what if they raise X" workshopping the night before.

The senior US official (head of mission) at a US Embassy or other formal diplomatic post, typically the Ambassador or Chargé d'Affaires, holding presidential authority over all US Government personnel and activities under chief-of-mission authority within the host country — to whom Defense Attachés and DoD elements in country report through the COM framework.

"The Ambassador or COM equivalent — senior US official in a country."

HOM is who runs the US presence in a country, and for DoD personnel assigned to embassies (defense attachés, the Office of Defense Cooperation / OSC, MILGROUP staff, ODCs of various flavors) the HOM is a real boss in a legal and operational sense. Chief-of-mission authority means the Ambassador can pull a uniformed officer out of country if they choose, and that any DoD activity in the host nation gets staffed through the embassy country team. The relationship between the geographic combatant command, the Ambassador, and the host nation is where most theater security cooperation friction lives; smart DoD personnel learn to work the country team rather than around it. The combatant commander commands forces; the HOM commands the country presence.

A staff officer or organizational position (headquarters commandant) responsible for the administration, security, life support, and physical operation of a military headquarters — handles billeting, dining facility, motor pool, force protection, and the everyday running of the headquarters compound so the operational staff can focus on the warfighting function.

"The officer who runs the headquarters compound so the staff can run operations."

HQCOMDT is the position no one notices when it is done well and everyone curses when it isn't. The headquarters commandant runs the physical headquarters — billeting plan, dining facility hours, generator fuel, ECP staffing, motor pool dispatch, the lost-and-found, where the new TOC tents pitch, what gets done about the broken HVAC. At a deployed JTF headquarters or a stateside division HQ this is a major captain or junior major billet that punches above its rank in scope. The role is one of the proving grounds for officers who are going to be effective S4s, XOs, and eventually battalion commanders, because it forces the kind of unglamorous logistics-and-people problem-solving that combat-arms career tracks otherwise skip.

The major Army command, headquartered at Fort Knox, Kentucky, responsible for managing the careers, assignments, evaluations, promotions, and records of all Army officer and enlisted personnel, including the operations of the Officer Record Brief, the Army Military Human Resource Record, and the assignment process through AIM 2.

"The Army command that runs officer and enlisted personnel management."

HRC is where Army careers happen administratively — the assignment officers (career managers for each branch and AOC), the promotion-board secretariats, the records-management functions, and the systems (AIM 2, ATAP, AMHRR) that operationalize Army talent management. HRC moved to Fort Knox from Alexandria in 2011 as part of BRAC. Officers and senior NCOs interact with HRC throughout their careers; junior enlisted typically interact through their unit S1 with HRC operating in the background. The institution's reputation among the workforce shifts with cycle of reform; the data systems it runs are the operative truth on most career questions.

A category of presidential directive (homeland security presidential directive) issued by the President to direct executive branch implementation of homeland security policy — foundational HSPDs include HSPD-5 (Management of Domestic Incidents, establishing NIMS), HSPD-7 (Critical Infrastructure Identification, Prioritization, and Protection), HSPD-8 (National Preparedness), and others.

"A presidential directive category establishing homeland security policy frameworks."

HSPD is the homeland-security cousin of the National Security Presidential Directive (NSPD) and the more recent National Security Presidential Memorandum (NSPM) format — a presidential directive issued specifically to govern homeland security policy implementation across the federal executive branch. The foundational HSPDs from the 2003-2008 era set up much of the architecture that still operates today: HSPD-5 created the National Incident Management System (NIMS) that every emergency manager works inside, HSPD-7 framed critical infrastructure protection, HSPD-8 established the National Preparedness Goal. For DoD personnel involved in DSCA, the HSPDs are the policy baseline that NORTHCOM and NORAD operations sit on top of. Later administrations have layered on top with NSPM and PPDs but the HSPD architecture remains in force.

A widely-used military administrative shorthand meaning "in accordance with," used to cite the regulation, instruction, or authority under which a particular action is taken or directed.

"A shorthand citing the authority for an action."

IAW is the workhorse of military writing — every memo, order, and email of any formality cites IAW some regulation. "IAW AR 600-8-22, this soldier is awarded..." "IAW JP 5-0, the planning process is..." The convention forces the writer to point at the authority for what they are asserting, which can be either rigorous (when the citation is real and accurate) or theatrical (when "IAW current guidance" is doing a lot of work without anchoring to anything specific). Read the citation; do not just nod at it.

The first formal capability requirements document in the Joint Capabilities Integration and Development System (JCIDS), describing the gap between current and required joint warfighting capability and proposing a path forward through doctrine, organization, training, materiel, leadership, personnel, facilities, or policy changes (the DOTMLPF-P spectrum), governed by CJCSI 5123.01.

"The first JCIDS document that identifies a capability gap and proposes a path forward."

The ICD is the start of the JCIDS pipeline — a sponsor documents the capability gap, proposes one or more material or non-material approaches, and routes the document through the Functional Capabilities Board to JROC for validation. ICD validation triggers the Analysis of Alternatives (AoA) and feeds the Materiel Solution Analysis phase. The ICD does not specify the solution; it characterizes the gap and what an acceptable solution would need to do. Mismatch between the ICD framing and what the program later delivers is one of the most common cost-growth and schedule-slip patterns.

A category of US intelligence community funding (Intelligence Contingency Funds) authorized for unforeseen intelligence requirements that cannot be programmed in the normal budget process — provides DoD intelligence elements and the broader intelligence community with flexible, accountable funding for time-sensitive operational needs, with strict reporting and oversight requirements.

"The flexible intelligence funding line for unprogrammed time-sensitive requirements."

ICF is the intelligence community's answer to "we cannot wait two budget cycles to fund this" — a designated funding line for operational intelligence needs that arise inside the planning horizon. The funds are tightly scoped, have strict reporting requirements (the relevant congressional intelligence committees see the executions), and are not a slush fund despite the loose-sounding name. For a service member, ICF is invisible — what you see is that a particular collection capability, a particular partner-nation engagement, or a particular technical solution got funded faster than the normal acquisition or O&M timeline would suggest. The category exists because intelligence operations sometimes turn on speed, and the trade-off between speed and the normal budget controls is managed through the specific oversight mechanisms attached to ICF.

A standard staff usage (in coordination with) appearing on orders, plans, and tasking documents to indicate that a designated task or action is to be executed by a primary actor with active coordination with named supporting or affected parties — distinguished from "in support of" (which implies a supported-supporting command relationship) and "in collaboration with" (which implies a more equal working relationship).

"The orders shorthand for "do this with active coordination with these other parties.""

ICW is the three letters that show up in operations orders and planning documents to specify that a tasked unit has to coordinate actively with named other units, agencies, or partners while executing its task. It is not a command relationship like supported/supporting — it is a coordination obligation. For a junior officer reading a paragraph 3 task assignment that ends with "ICW [unit] for [function]," the practical meaning is: pick up the phone, build the staff-to-staff connection, and do not surprise the named party with your execution. ICW is one of the small doctrinal vocabularies that distinguish people who have read the order from people who only skimmed it. Failing to ICW when ordered to is the kind of staff oversight that turns into a deficient OPORD execution review.

A contract type providing for an indefinite quantity of supplies or services during a fixed period, with individual task or delivery orders issued against the contract as needs arise.

"A flexible contract vehicle for repetitive needs over time."

IDIQs are how DoD avoids running a new procurement every time something is needed. The basic IDIQ award establishes which vendors can compete; task orders fill the actual need. Single-award IDIQs limit competition to one vendor; multi-award IDIQs preserve competition at the task-order level. Ceiling values (the maximum total dollars over the contract life) are often huge and rarely fully used — a $1 billion IDIQ might obligate $200 million.

A DoD program (installation emergency management) that integrates all-hazards preparedness, mitigation, response, and recovery functions on military installations — covers natural disasters, industrial accidents, active shooter events, CBRN incidents, and mass-casualty events — executed under installation commander authority through emergency operations centers, mass-warning systems, and mutual-aid agreements with surrounding civilian jurisdictions.

"The base-level emergency management program — all-hazards prep, response, and recovery."

IEM is the apparatus that gets stood up when the hurricane is bearing down on Tyndall, when a tanker truck rolls on the post highway, when a shooter is reported in the BX, or when a tornado tracks toward family housing. The program lives in the garrison emergency manager's shop, runs the installation emergency operations center, owns the Giant Voice mass-warning system, and coordinates with the surrounding county and state emergency management agencies through mutual-aid agreements. For most service members IEM shows up as the quarterly active-shooter drill, the AtHoc notification on the workstation, or the shelter-in-place call over the loudspeaker. The post-2018 emphasis on installation resilience (Tyndall destruction by Hurricane Michael, Offutt and Camp Lejeune flooding) elevated the program from a back-shop compliance function to a commander-priority readiness issue.

Two distinct uses in the DoD Dictionary: (1) integrated financial operations, the synchronized employment of finance and resource management capabilities across operational phases to support deployed force sustainment and contingency contracting payment; and (2) intermediate fuel oil, a maritime fuel classification (heavier than marine diesel, lighter than residual fuel oil) used by certain naval auxiliaries and commercial vessels under sealift charter.

"Either integrated financial operations (finance/RM in ops) or intermediate fuel oil (maritime fuel grade)."

IFO has two unrelated meanings in the DoD Dictionary that disambiguate easily from context. Integrated financial operations is the doctrinal concept for how finance and resource management capabilities — comptrollers, finance detachments, contingency contracting officers, paying agents — get pulled into operational planning so that deployed forces can actually pay vendors, host nation contractors, and other beneficiaries in the operating environment. The function got institutional attention after the Iraq and Afghanistan experience where bag-of-cash payments and uneven financial controls became a recurring issue. Intermediate fuel oil is a maritime fuel classification heavier than marine diesel but lighter than the residual heavy fuel oil that older commercial ships burn; certain naval auxiliaries and commercial sealift vessels operate on IFO. The two uses are unrelated and live in different doctrinal worlds (joint sustainment vs. maritime logistics).

An independent office within each service responsible for inspections, investigations, complaints, and assistance, with protected reporting channels for service members.

"If something is wrong, you can go to the IG and your complaint is protected."

IG complaints are confidential in policy. In practice, in a small unit, the source is often guessable. The IG does not adjudicate every complaint — many are referred back to command. For protected disclosures involving fraud, waste, abuse, or reprisal, know the difference between the IG and the DoD Hotline before filing.

A member of the Selected Reserve assigned to an active component or Selective Service System position, in which the reservist trains during peacetime to be ready to mobilize into the assigned position in time of war or national emergency.

"A reservist trained to fill a specific active-duty position upon mobilization."

IMAs are individual reservists pre-assigned to specific active-duty billets — they train periodically at the active unit they would mobilize into, building familiarity that would otherwise have to be created during the crisis. The Navy Reserve, USAR, USAF Reserve, and MARFORRES all have IMA programs. IMA service is structured to fit professional and civilian career patterns more flexibly than traditional SELRES drilling unit assignments.

A DoD logistics management approach (integrated materiel management) that assigns a single materiel manager (typically a Defense Logistics Agency commodity activity or a service-component item manager) responsibility for an item across the joint force — covers cataloging, requirements determination, procurement, distribution, maintenance support, and disposal — eliminates redundant materiel management across services for common items.

"Single-manager materiel management — one DLA or service activity owns an item joint-wide."

IMM is the management construct that puts a single activity in charge of a given item across the joint force — typically DLA for commodity items (medical supplies, subsistence, fuel, clothing, construction materials), or a service activity for service-unique items, with the integrated materiel manager owning the cataloging, requirements forecasting, procurement, distribution to retail-level supply activities, and disposal. The construct exists because before IMM, the same nut-and-bolt could be procured and stocked separately by each service, with no visibility across the joint force — the resulting inefficiency drove the consolidation that became DLA in 1961 and the broader IMM framework. For an end-user supply sergeant or supply officer, IMM is invisible — you requisition through your unit's supply system and the back-end IMM structure routes the requirement. For a logistics professional, IMM is the basic organizing principle of joint materiel management.

Two distinct uses in the DoD Dictionary: (1) information management plan, a unit or command-level plan that defines how information will be managed during an operation — collection, processing, storage, dissemination, and disposition — typically authored by the J6/G6/N6 information management officer; and (2) inventory management plan, a logistics document that defines how a specific item or class of items will be managed across its life cycle — stock levels, replenishment rules, distribution priorities.

"Either an information management plan (J6/G6 product) or an inventory management plan (logistics)."

IMP has two unrelated meanings that resolve from context. The information management plan is the J6/G6/N6 staff product that defines how a unit or headquarters will manage information during an operation — what gets collected, where it lives, who can access it, how it's disseminated, when it's destroyed or transferred to records management — and is part of the broader information management discipline that supports decision-making in complex operations. The inventory management plan is the logistics document that defines management approaches for specific items or item classes: what stock levels to maintain, when to replenish, how to prioritize distribution. The two uses live in different staff worlds (J6 communications vs. J4 logistics) and rarely collide. For most service members IMP shows up indirectly, as the rules you're working under rather than as a document you read directly.

The federal statute, codified at 10 USC 251-255, that authorizes the President to deploy active-duty military forces (and federalized National Guard forces) within the United States to suppress an insurrection, enforce federal law, or protect constitutional rights — providing the principal statutory exception to the Posse Comitatus Act restriction on domestic military law enforcement.

"The federal statute permitting presidential use of military forces for domestic emergencies."

The Insurrection Act is the principal exception to Posse Comitatus — when the President invokes it (by formal proclamation), active-duty forces and federalized Guard can enforce federal law, suppress insurrection, or protect constitutional rights domestically. Historical invocations include enforcement of school desegregation orders (1957 Little Rock, 1962 University of Mississippi), response to the 1992 Los Angeles riots, and Hurricane Hugo response. The political and constitutional weight of an Insurrection Act invocation is substantial; the political pressure typically pushes governors to use Title 32 / SAD Guard forces first to avoid the federal-active-duty domestic deployment.

The Army's authoritative electronic repository for the official military personnel file of every soldier — active, reserve, and Guard — providing digitized storage and retrieval of evaluations, awards, orders, training records, and other documents that comprise the Army Military Human Resource Record.

"The Army's digital file cabinet for every soldier's personnel record."

iPERMS is where every soldier's OMPF (Official Military Personnel File) actually lives — every NCOER and OER ever signed, every award orders, every PCS orders, every school certificate, every reduction memo. Uploads from the field can take days to weeks to surface in the record, which becomes painful during promotion-board season when an evaluation needs to be in iPERMS by the cutoff date and the S1 says it's submitted but iPERMS says it isn't. The "missing documents" report soldiers run before a board is its own minor career-management ritual. iPERMS access goes through AKO/Army365 single-sign-on and CAC authentication.

A modern, integrated Army-wide system, fielded in waves across the active component, Army Reserve, and Army National Guard, that consolidates personnel actions and military pay onto a single platform — replacing eMILPO, RLAS, SIDPERS, and parts of the legacy personnel and pay landscape with a unified PeopleSoft-based system.

"The Army's unified personnel and pay system replacing the legacy stack."

IPPS-A is the long-running, painful, finally-fielded consolidation of Army personnel and pay into one place — Release 3 went live for the active component in early 2023 after years of delays and a deeply rocky Guard/Reserve rollout. The migration pain has been significant: pay drops during cutover, promotion actions stuck in workflow approvals, S1s rebuilding muscle memory from the eMILPO/RLAS world to PeopleSoft navigation, and a steady stream of help-desk tickets. The promise is real (one system, member self-service, pay-and-personnel finally talking to each other); the execution has been the kind of enterprise IT transition where the people doing the work bear the cost of the seams.

A scheduled review of a plan, program, project, or operation while it is in execution — providing the responsible commander or decision-maker an opportunity to assess progress, approve continuation, adjust direction, or terminate — applied across acquisition, exercise planning, OPLAN development, and program management — listed in the DoD Dictionary of Military and Associated Terms (November 2021).

"The IPR — in-progress review, the checkpoint meeting where the boss sees where things stand."

IPR is the checkpoint meeting that virtually every staff product, exercise, OPLAN, or acquisition program runs through — the in-progress review where the responsible commander or program manager sees the status, makes decisions, and either approves continuing on the current azimuth or directs changes. Junior officers and senior NCOs spend large amounts of staff time preparing for IPRs (the slides, the backup data, the rehearsal). The discipline matters because IPRs are the natural decision points in a multi-step process — the gap between IPRs is the place where work happens, and IPRs are where the work gets visibility. The number of IPRs in a process (IPR1, IPR2, IPR3 for an exercise; multiple for an OPLAN; many across an acquisition program) is part of the planning baseline.

A category of the Ready Reserve consisting of trained individuals, formerly serving on active duty or in the Selected Reserve, who are not currently drilling but remain subject to recall to active duty in time of war or national emergency.

"A pool of trained Soldiers available for recall in emergencies."

IRR Soldiers do not drill, are not paid, and have no current unit — but they remain in the pool. Recall happens (notably during the post-9/11 wars). IRR members must keep DEERS and contact information current; failure to respond to recall can result in administrative action. The "muster" — periodic in-person verification — is a real obligation that travels with you to whichever address DEERS has on file.

Two meanings in the DoD Dictionary (November 2021): (1) individual Service augmentee — an individual military member assigned to augment a joint task force, combatant command, or other joint organization from their parent Service, providing specific skills or capacity outside the normal Service rotation; (2) international standardization agreement — a multilateral document (NATO STANAG and similar) establishing standardized procedures, equipment, or doctrine across allied forces.

"ISA — individual Service augmentee (joint billet) or international standardization agreement (allied doctrine)."

ISA carries two very different meanings depending on personnel-management context versus interoperability context. The individual Service augmentee meaning is the joint-manpower term for a service member who fills a JTF or combatant command billet outside their normal Service rotation — typically a non-deployable home-station billet that suddenly needs deployment manning, filled by the parent Service identifying an individual. The international standardization agreement meaning is the interoperability vocabulary — NATO STANAGs and similar multilateral agreements that establish standardized procedures, equipment, or doctrine across allied forces. Both meanings appear regularly in joint doctrine; context usually disambiguates. ISAs (the personnel meaning) experienced significant volume during the OIF/OEF mobilization era when joint and combatant-command manning often required individual augmentation outside Service rotations.

An EFMP component developed for service members and families with special-needs dependents, identifying the medical, educational, and support services needed and tracking those needs in PCS assignment decisions.

"A plan that tracks special-needs services to inform PCS assignments."

The ISP is what makes EFMP useful — it is the document that tells the assignments office what services your family needs at the next station. ISPs are only as accurate as the family's documentation; outdated ISPs result in PCS to locations that cannot deliver the required services. Update before every PCS, every diagnosis change, and at the annual review. Push back if the EFMP coordinator declines to update; the assignments office cannot match what the ISP does not say.

The installation-level office responsible for managing official-travel transportation, personal property (household goods) movement, and unit transportation support for the installation's assigned and tenant units.

"The installation office that manages official travel and household goods."

The ITO (sometimes called Personal Property Shipping Office, or rolled into the LRC at consolidated installations) is who you talk to before a PCS — household goods scheduling, weight allowance questions, claims if something breaks in transit. The Defense Personal Property System (DPS, also rebranded as MilMove) is the digital front-end most members use now; the ITO is the human help when DPS does not solve the problem.

A standing or ad hoc intelligence coordination body (intelligence working group) convened at the joint task force, combatant command, or interagency level to synchronize intelligence support to a specific mission, target set, or contingency — typically chaired by the J2 or a designated representative and includes service intelligence components, national-agency liaisons, and partner-nation intelligence representatives.

"A standing or ad-hoc intel coordination meeting — J2 chairs, gets everyone in the room."

IWG is the formal recurring meeting at which a joint task force or combatant command J2 pulls together every intel element supporting the mission — the service component intel reps, the NGA, NSA, DIA, and CIA liaisons, the targeting officers, the cyber and SIGINT cells, and any partner-nation intel representatives — and synchronizes everybody's collection plans, requests for information, and analytic production around a common priority list. For the senior intel NCO at a JTF, IWG is the meeting you brief intel updates at, where you fight to get your unit's RFIs against the national-level collection assets, and where the intel-support-to-targeting integration actually happens. The IWG is also where the friction between service intel ("we need tactical product right now") and national intel ("we're working a strategic priority") gets adjudicated.

The functional directorate structure of the Joint Staff, used in parallel across combatant command staffs and other joint headquarters: J-1 Personnel, J-2 Intelligence, J-3 Operations, J-4 Logistics, J-5 Strategic Plans and Policy, J-6 Command, Control, Communications, and Computers/Cyber, J-7 Joint Force Development, and J-8 Force Structure, Resources, and Assessment.

"The standard functional directorates on a joint staff."

The J-codes structure repeats at every joint headquarters — Joint Staff, combatant command, joint task force, joint expeditionary unit. The numbering also tracks with the service equivalents: G-codes (Army), N-codes (Navy), A-codes (Air Force), S-codes (Marine Corps/below division). If you are reading an order from "J-3 OPSO" you know it is from the Joint Staff Operations Directorate's operations section; the same person at a CCMD is the CCMD/J-3 OPSO. Within DoD the directorate structure is one of the few things that travels universally.

The Department of Defense organization established in 2018 by the Deputy Secretary of Defense to accelerate the adoption of artificial intelligence across the Department, focused on Joint Common Foundation infrastructure, AI capability delivery for selected national mission initiatives, and AI policy and ethical-use guidelines — subsumed in 2022 into the Chief Digital and Artificial Intelligence Office.

"The 2018-2022 DoD AI office subsumed into CDAO in 2022."

JAIC was DoD's 2018 institutional bet on AI — a dedicated organization with funding and authorities to deliver AI capability across the Department, organized around National Mission Initiatives (intelligent business automation, predictive maintenance, etc.) and the Joint Common Foundation. The office produced concrete deliverables but also drew critique that it functioned more as another R&D office than as an AI-adoption accelerator. The 2022 consolidation into CDAO reflected the conclusion that an integrated digital-and-AI office under a near-Secretary-level Chief was a stronger structural answer.

A standardized DoD taxonomy (joint capability areas) that organizes the joint force's capabilities into a hierarchical structure of nine top-tier categories (force support, battlespace awareness, force application, logistics, command and control, net-centric, protection, building partnerships, and corporate management and support) used for capability portfolio management, programming, and analytic purposes.

"The DoD capability taxonomy — nine top-tier categories for capability portfolio management."

JCA is the taxonomy DoD uses to organize "what the joint force can do" into a structured hierarchy that programmers, analysts, and capability portfolio managers can talk about consistently — nine top-tier areas (force support, battlespace awareness, force application, logistics, command and control, net-centric, protection, building partnerships, corporate management and support), each decomposed into Tier 2 and Tier 3 subordinate capabilities. For an action officer in the Joint Staff J8, OSD Cost Assessment and Program Evaluation (CAPE), or a service force-management shop, JCA codes are the way you tag programs and capabilities to support portfolio-level analytic work. Most uniformed personnel never touch the JCA taxonomy directly, but it's the backbone of how the building's requirements and budget processes structure capability discussions.

A joint capability assessment process (joint combat capability assessment) that the Joint Staff and the combatant commands use to evaluate readiness and capability of joint forces against the demands of operation plans — provides senior leadership with a current picture of force capability shortfalls, risk, and capability gaps to inform programming, force-allocation, and operational planning decisions.

"The Joint Staff capability assessment — readiness and gap analysis against OPLAN demands."

JCCA is part of the Joint Staff and OSD apparatus for assessing whether the joint force can actually do what the operation plans (OPLANs) and contingency plans ask of it — pulls together the GFM (Global Force Management) picture, the Defense Readiness Reporting System (DRRS) inputs, the OPLAN demands, and the analytic work to produce a current assessment of capability shortfalls and risk. The process feeds the Chairman's Risk Assessment, the Quadrennial Defense Review/National Defense Strategy review cycles, and combatant command capability planning. For an action officer in J3/5/8 at the Joint Staff or in a COCOM J5, JCCA-related products are the staffing fodder for senior-leader engagements on force-allocation and capability-priority questions.

The DoD process by which warfighter capability requirements are identified, validated, and prioritized. Manages the validation of requirements documents (ICDs, CDDs, CPDs) that drive acquisition programs.

"The process that turns warfighter needs into validated requirements for acquisition."

JCIDS is the "what do we actually need to buy" process — and it is famously slow. A capability gap identified today can take years to produce a validated requirement; the requirement then takes longer to fund and contract. Programs that move fast often do so by sidestepping or shortcutting JCIDS through OTA, urgent operational needs, or middle-tier acquisition pathways.

The joint process and organizational apparatus (joint container management) that tracks, manages, and accounts for intermodal containers (ISO containers) used to move military equipment, supplies, and ammunition through the strategic mobility lanes — coordinates with USTRANSCOM, the Surface Deployment and Distribution Command (SDDC), commercial container operators, and the broader Joint Deployment and Distribution Enterprise to maintain container fleet visibility.

"The joint container fleet management process — ISO container visibility across deployment lanes."

JCM is the joint apparatus that keeps track of the ISO containers (the standard 20-foot and 40-foot intermodal boxes you see on container ships, rail cars, and trucks) that move through the joint deployment and distribution enterprise — DoD owns some containers (the Container Express System and broader DoD-owned container fleet), leases others from commercial operators (Maersk, MSC, and other carriers), and has continuous accountability challenges with the fleet because containers get diverted, lost, retained at destinations, and otherwise become uncontrolled. For SDDC and USTRANSCOM movement planners, JCM is the framework for trying to maintain container visibility and accountability in a system that has structural incentives toward leakage. The "where are my containers" problem is a recurring complaint at deployed sustainment headquarters across every campaign.

A staff coordination forum (joint contracting support board) at the COCOM or JTF level that integrates operational contract support across the joint force — synchronizes contracting authorities, sets theater contracting policy, deconflicts requirements across components, and integrates contracting effort with Lead Service contracting (LSCC) arrangements during operations.

"JCSB — joint board synchronizing contracting support across the joint force."

JCSB is the meeting where the joint force figures out how it's actually going to buy stuff in theater without each component bidding against each other on the same vendor base, paying wildly different prices for the same local services, or creating contracting situations that the Inspector General will be unraveling for the next decade. The board sets theater contracting policy, deconflicts component requirements, designates Lead Service for Contracting in particular regions or commodity areas, and ensures the contracting officer corps across services is operating off the same operational picture. For a contingency contracting officer (CCO) deploying into theater, JCSB decisions show up as the theater business clearance procedures, the synchronized vendor approval lists, and the joint-acquisition-instruction guidance for the operation.

The function (joint doctrine distribution) within the Joint Staff J-7 that publishes, distributes, and maintains access to approved joint doctrine — primarily executed today through the Joint Doctrine, Education, and Training Electronic Information System (JDEIS) and the publicly-accessible Joint Electronic Library.

"JDD — the J-7 function for publishing and distributing approved joint doctrine."

JDD is the function inside J-7 that makes sure approved joint doctrine actually gets to the people who need to use it — publishing newly-approved JPs, updating the electronic distribution channels, ensuring the indexes and cross-references are current. The function is today largely executed electronically through JDEIS (the access-controlled system for the broader doctrine, education, and training documentation) and the Joint Electronic Library (the publicly-accessible portion). For a joint planner trying to find the current version of JP 3-30, JP 5-0, or any other joint publication, JDD's work is what makes the document actually available at the desktop. The function gets occasional attention when a new flagship publication releases; otherwise it's invisible infrastructure that the joint doctrine community depends on.

The formal schedule (joint doctrine development and assessment schedule) maintained by the Joint Staff J-7 that tracks every joint publication through its development, revision, and assessment cycle — identifies which publications are in initial drafting, which are in revision, which are due for assessment, and the projected timeline for each.

"JDDAS — the J-7 schedule tracking every JP through its development and revision cycle."

JDDAS is the master schedule the J-7 maintains that shows where every joint publication sits in its development, revision, or assessment cycle — the JPs that are being drafted from scratch, the JPs in revision because doctrine has evolved or operational lessons demand change, the JPs that are due for the formal periodic assessment to determine whether they still reflect current practice. For a service doctrine writer or a COCOM lead-agent, JDDAS is the planning document they look at to understand when their publication is due, what coordination windows are coming, and how their work fits into the broader joint-doctrine production calendar. The schedule is part document, part workflow tool, part institutional commitment to keeping the joint doctrine library current.

A recurring forum (Joint Doctrine Planning Conference) chaired by the Joint Staff J-7 that brings together joint doctrine stakeholders from every service, combatant command, and major joint headquarters to coordinate the joint doctrine development program — sets priorities, reviews the JDDAS, and synchronizes the lead-agent and coordination community across the doctrine library.

"JDPC — recurring J-7 conference synchronizing the joint doctrine community."

JDPC is the recurring J-7-chaired conference where the joint doctrine community gets together to coordinate the program — services, COCOMs, and major joint headquarters all send doctrine representatives, the JDDAS schedule gets reviewed, the priority list gets adjusted, the lead-agent assignments get socialized, and the coordination community surfaces the issues that need to be worked between the formal staffing windows. For a doctrine writer at a service or COCOM, JDPC is one of the principal venues to track what's coming, raise issues with the J-7, and coordinate with peer doctrine offices on cross-publication implications. The conference is the institutional connective tissue of joint doctrine development — without it, the program would fragment into disconnected lead-agent projects with no synchronization.

The official DoD repository (joint electronic library) for joint doctrine, the JP-series publications, and supporting doctrinal products — hosted by the Joint Staff J7 and accessible through the joint doctrine portal — the authoritative source for the current edition of every joint publication and for retired editions that staffs and historians need to reference.

"The DoD online library where every JP-series publication lives."

JEL is where you go when somebody on staff says "what does JP 3-30 say about the JFACC?" — the Joint Staff J7-hosted online library that holds the current and historical editions of every joint publication. The portal is the authoritative source: if the JEL says the publication is signed and in effect, that's the version that controls; if a draft is in coordination, that's flagged. Every joint staff officer has the JEL bookmarked. The library replaced the old paper-and-CD distribution of joint pubs and lives on the NIPR side for most products with classified annexes available through the appropriate channels. The cousin organization JEDD writes the doctrine; JEL is where the doctrine lives once it's published.

A joint task force or joint force command staff body (joint environmental management board) that integrates environmental considerations — hazardous waste, water quality, air quality, cultural and natural resources protection, and compliance with host-nation and international environmental law — into joint operations planning and execution, particularly during sustained operations and base camp lifecycle management.

"The joint board that keeps environmental compliance from torpedoing the operation."

JEMB is the staff body that exists because expeditionary operations generate large amounts of waste, fuel spills, water consumption, and cultural-property exposure — and because the host nation, international law, and post-deployment liability mean those issues cannot be ignored without consequence later. The board pulls together the J4 environmental engineer, the J3 operations representative, the staff judge advocate, the surgeon, and the host-nation liaison to make decisions about waste streams, contractor compliance, water sources, and base-camp closure. For most operators JEMB is invisible until the burn pit lawsuit lands on the desk twenty years later; for engineer and medical staff it's a routine working group that keeps the operation from leaving a problem behind.

A DoD planning and execution information system (joint engineer planning and execution system) used by joint and service engineer staffs to develop, coordinate, and track theater engineering plans — covers base camp lifecycle planning, theater construction programs, lines of communication development, and reach-back to USACE and Naval Facilities Engineering Command — integrates with the broader Joint Operation Planning and Execution System (JOPES).

"The joint engineer planning system — base camps, theater construction, LOC development."

JEPES is the planning tool joint and service engineer staffs use to actually run the theater engineering program — base camp lifecycle (siting, construction, sustainment, closure), theater construction projects, lines of communication (roads, airfields, port facilities), and the reach-back to USACE and NAVFAC for technical support. For an engineer staff officer JEPES is where the construction priority list lives, where the contractor footprint gets tracked, and where the funding allocations get reconciled with the JFC's priorities. For most operators JEPES is invisible — the system shows up as "the new dining facility is on the master plan" or "the base camp closure timeline is on the engineering schedule." The integration with JOPES is the doctrinal pathway by which engineering planning ties into the broader operational plan.

A USTRANSCOM-operated transportation analysis and modeling system (joint flow and analysis system for transportation) used by combatant command and Joint Staff planners to model strategic deployment flows — analyzes airlift, sealift, and surface transportation feasibility for operation plans, time-phased force and deployment data (TPFDD) development, and contingency response planning.

"The USTRANSCOM modeling tool for strategic deployment flow analysis."

JFAST is the modeling tool USTRANSCOM and joint planners use to figure out whether a given deployment plan is actually executable with the airlift, sealift, and surface transportation available — feeds in the TPFDD (the time-phased force and deployment data that says what unit moves when, from where to where), runs the flow analysis, and produces the picture of where the strategic mobility shortfalls are. For an operational planner JFAST is where the plan meets the mobility reality: "we need this brigade in theater by C+30" turns into "given current C-17 availability and sealift cycles, the brigade gets there at C+34 unless we accept this risk to that other movement." The tool has driven force-design conversations about strategic mobility shortfalls for years.

A designated officer or organization (joint functional manager) responsible for joint-wide planning, programming, and policy oversight of a specific joint function — examples include joint functional managers for specific capability areas, support functions, or readiness domains — serves as the institutional lead for that function across the joint force.

"The joint-wide manager for a specific function — planning, programming, policy oversight."

JFM is the joint construct for "someone has to be in charge of this function across the entire joint force, not just in one service or one COCOM" — the joint functional manager owns the planning, programming, and policy work for a specific function (capability area, support function, readiness domain) at the joint-wide level. The role provides the institutional continuity that lets a function be managed across services, across COCOMs, and across program cycles. For an operator the JFM is usually invisible; for a programmer or capability developer working a joint function, the JFM is the institutional partner whose buy-in shapes whether the function gets resourced and how it evolves. The term is used flexibly across joint doctrine and varies by the function being managed.

A joint postal operations facility (joint fleet mail center) typically operated by Navy postal personnel at a major fleet or expeditionary hub that consolidates incoming mail, accountability mail (registered, certified, insured), and outbound mail for ships, units, and personnel in the supported area — provides the postal-throughput function that enables sustained sea-based and forward-deployed operations.

"The Navy-operated joint mail hub for fleet and expeditionary forces — sorting and throughput."

JFMC is the joint mail throughput hub for fleet and expeditionary operations — typically operated by Navy postal personnel at a major hub (Bahrain, Guam, Sigonella, Yokosuka) where mail for ships, units, and personnel in the supported region gets consolidated, sorted, accountability-managed, and pushed forward to the receiving units. For sailors deployed on ships and service members deployed forward, the JFMC is the reason mail actually arrives — care packages, official correspondence, accountability mail (registered, certified) — at a tempo that makes deployment livable. The postal mission is unglamorous and continuously demanding; the JFMC is where the work happens at scale. The operation interfaces with USPS, military postal service agency, and the broader joint sustainment apparatus.

A quarterly Chairman of the Joint Chiefs of Staff assessment of the readiness of the joint force to execute the National Military Strategy, integrating Service readiness reports, combatant command readiness assessments, and the Defense Readiness Reporting System data to produce a joint-level readiness picture briefed to senior leaders — the JFRR informs force-management, resourcing, and risk decisions across the Department of Defense.

"The Chairman's quarterly joint readiness brief — Services plus COCOMs roll up into one readiness picture."

JFRR is the Chairman's quarterly readiness brief — the deliverable that takes the Services' monthly readiness reports, the geographic and functional COCOMs' assessments, and the DRRS data feeds, and rolls them up into one joint-level picture for the Secretary of Defense and senior leaders. For a Joint Staff J-3 readiness analyst, JFRR is the production cycle that owns your calendar: data calls go out 60 days before the brief, Service inputs come in at 45 days, the analytical narrative gets drafted, slides get murder-boarded, and the Chairman gets the final read with associated risk recommendations. JFRR is one of the principal mechanisms by which "readiness" stops being a Service term and becomes a joint term that drives resourcing and risk conversations.

A Joint Staff assessment process that examines whether the programmed and projected joint force is sufficient to execute the National Defense Strategy across the range of military operations and against the prioritized threats — informs Chairman's Program Recommendation, Chairman's Program Assessment, and the broader Defense Planning Guidance and PPBE processes.

"The Joint Staff assessment of whether we have enough force to execute the National Defense Strategy."

JFSA is the analytical workstream that asks the awkward question: is the force we have, and the force we're programming to have, actually enough to do what the National Defense Strategy says we're going to do? Joint Staff J-8 and J-5 own significant pieces of it. The output feeds the Chairman's Program Recommendation (CPR) and Chairman's Program Assessment (CPA), which are the formal mechanisms by which the Joint Staff influences the budget process and tells the Secretary "here is where the strategy and the force diverge." For an action officer, JFSA work is the long-cycle analytical project where you build force-on-force models, run COCOM-by-COCOM demand signals, and produce the brief that nobody wants to look at but everyone needs to see.

A joint board established by a joint force commander or subordinate commander to evaluate and reconcile component requests for real estate, use of existing facilities, inter-Service support, and construction to ensure the most efficient and effective use of available facilities in the joint operations area — typically chaired by the J-4 engineer with representation from each component.

"The joint board that adjudicates who gets which buildings, real estate, and construction priority in theater."

JFUB is the joint board that decides who gets the building. When a JTF stands up in theater and four components plus the host nation plus the contractors all need real estate, office space, ramp space, billeting, and construction priority, the JFUB is the venue where those competing requests get reconciled. The J-4 engineer typically chairs it, with each component sending a representative. For an Air Force civil engineer or an Army facilities planner at a deployed location, JFUB is the meeting where you fight for your unit's housing allocation, your hardstand priority, or your inter-Service support relationship — and where the other components do the same. The board exists because the alternative is every component standing up their own contracting and facilities effort in parallel, which is even worse than the JFUB process.

A Department of Defense public affairs activity that distributes news, photo, and video products about individual Service members to local civilian media outlets in the member's hometown community — operated under the Defense Media Activity, JHNS produces and distributes hometown news releases (HTNRs) on promotions, deployments, awards, training milestones, and other newsworthy events.

"The DoD service that sends "local boy/girl deploys" stories back to your hometown newspaper."

JHNS is the activity that produces the "Local Service Member Deploys to" stories your hometown newspaper sometimes still prints. Run under the Defense Media Activity, JHNS distributes Hometown News Releases — short, formatted blurbs about promotions, deployments, awards, and training milestones — to civilian media outlets in the Service member's home of record. For most Service members, JHNS is something they encounter once: the public affairs shop pushes a release when they graduate basic, hit a promotion board, or deploy somewhere notable, and an aunt back home cuts it out of the paper. The reach has shrunk as local print media has shrunk, but the mechanism still runs and is one of the small ways DoD invests in the connection between the force and the communities Service members come from.

A joint board established by a joint force commander to develop, coordinate, and oversee information management policy and procedures for the joint force — addresses the policies, standards, and practices for managing information across the joint headquarters, including records management, knowledge management, information sharing across components and coalition partners, and the broader information-environment governance.

"The joint board that sets information management policy across a joint force."

JIMB is the board that owns information management policy at the joint-force level — records management, knowledge management, naming conventions, file-share architectures, classification handling, releasability marking, and the broader question of "how does this headquarters manage its information." For a J-6 information-management officer or a knowledge-management officer at a joint headquarters, JIMB is the venue where policy gets coordinated across components and where the chronic information-management problems (everyone has their own SharePoint, no one can find the latest version of the FRAGO, the coalition partner can't see the document because it's marked NOFORN) get adjudicated. The board rarely produces glamorous deliverables, but the information-management practices it sets shape how effectively the headquarters runs.

A Department of Defense process for planning the mobilization of the US industrial base to surge defense production in response to major contingencies, large-scale combat operations, or sustained operations exceeding peacetime industrial capacity — JIMPP integrates Service-level industrial base planning with joint requirements, identifies critical supply chain vulnerabilities, and informs the broader National Defense Industrial Base policy framework.

"The joint process for planning how to surge the defense industrial base in a major contingency."

JIMPP is the joint planning process that asks the question nobody wants to answer in peacetime: if we get into a real fight that lasts more than a few weeks, can the industrial base produce the missiles, the munitions, the spare parts, the vehicles, and the ammunition fast enough to keep the force in the fight. The peacetime industrial base is sized for peacetime production rates; surge production requires identifying which prime contractors can ramp, which second- and third-tier suppliers are single-points-of-failure, which raw materials and components have foreign-sourced dependencies, and which production lines have been cold for years. JIMPP is one of the institutional answers to industrial mobilization planning, working alongside the DPA (Defense Production Act) authorities and the broader National Defense Industrial Base policy framework.

A joint board established by a joint force commander or subordinate joint force commander to coordinate logistics across the components and provide the commander with recommendations on joint logistics priorities, sustainment requirements, distribution, and inter-Service support — typically chaired by the J-4 with component logistics representatives, and is the principal venue for adjudicating logistics priorities across the joint force.

"The joint logistics board — where component logistics priorities get adjudicated under the J-4."

JLB is the joint board where logistics priorities get adjudicated across components — the J-4-chaired venue where the Air Force component logistics chief, the Army component G-4, the Navy component, the Marine component, and the SOF component bring their priorities, their shortfalls, and their requests for inter-Service support, and the board recommends to the JFC how to allocate scarce sustainment capacity. For a deployed J-4 action officer, JLB prep is a regular rhythm: data calls go out, components submit their inputs, the agenda gets built, the board runs, and the decisions go out as part of the broader logistics scheme of support. The JLB exists because joint logistics is inherently a competition for finite throughput (port capacity, lift, fuel, ammunition stocks) and somebody has to adjudicate.

The control center established during Joint Logistics Over-the-Shore (JLOTS) operations to plan, coordinate, and control the employment of lighterage assets (causeways, warping tugs, Lighter Amphibious Resupply Cargo vessels, Improved Navy Lighterage System craft, and other watercraft) used to move cargo from offshore ships to the beach when fixed-port facilities are unavailable or inadequate — typically established under the Navy Tactical-Logistics Group commander.

"The JLOTS lighterage control center — coordinates causeways and lighter craft moving cargo ship-to-shore."

JLCC is the control center that runs lighterage during a Joint Logistics Over-the-Shore operation — the rare-but-doctrinally-essential capability to move cargo from offshore strategic sealift ships to the beach when there is no fixed port (because the port doesn't exist, has been destroyed, or has been denied). The lighterage assets include the Improved Navy Lighterage System (INLS) modular causeway sections, the Lighter Amphibious Resupply Cargo (LARC) vessels, warping tugs, and the broader watercraft inventory. For a JLOTS-trained Army Transportation officer or a Navy ATF logistics officer, JLCC is the operational nerve center during a JLOTS exercise or contingency — scheduling lighter runs, deconflicting ship-to-shore movement, managing the beach interface, and reporting throughput. JLOTS capacity has been a chronic readiness concern across joint logistics for years.

The Department of Defense system, operated by the Joint Staff J-7 Joint and Coalition Operational Analysis directorate, that captures, analyzes, and disseminates lessons learned from joint and combined operations, exercises, and experimentation — providing the searchable database that future planners and commanders draw on to inform their preparation.

"The DoD database capturing and disseminating joint operational lessons learned."

JLLIS is where joint and combined lessons learned live as an authoritative repository — exercise observations, deployment after-action reviews, experimentation results, and post-operation analyses. Joint Staff J-7 owns the program; service equivalents (CALL for Army, MCCLL for Marines, NLLP for Navy) feed in and draw from the joint system. The lessons-learned community has a recurring challenge: capturing observations is easier than acting on them. JLLIS lessons rarely get implemented without an institutional sponsor and an authority chain.

Per the DoD Dictionary, a joint legal support element — the joint judge advocate organization that provides legal services to a joint force, including operational law, law of armed conflict, rules of engagement, fiscal law, contracting law, military justice, claims, and legal assistance, drawn from Service component judge advocate general (JAG) personnel under the joint force commander.

"The joint JAG cell — operational law, ROE, fiscal law, and military justice across a joint force."

JLSE is the joint-force version of the JAG office — a few judge advocates and paralegals from Army JAG Corps, Navy JAG Corps, Air Force JAG Corps, and Marine Corps SJA pulled together to support a joint task force or combined joint task force. The work is mostly operational law (does the ROE allow this strike, does this target meet collateral-damage estimates, is this legally a hostile force or a hostile act), fiscal law (can the JTF spend O&M money on this or does it need a different appropriation), and law-of-war questions that the J3 desk needs answered before a decision goes to the commander. Military justice for in-theater incidents and claims work for damage to civilian property round out the load. The lead JLSE judge advocate is usually a senior O-5 or O-6 and reports directly to the joint force commander as their senior legal advisor.

Per the DoD Dictionary, a joint manning document — the personnel requirements document that identifies the billets required to staff a joint force headquarters or joint task force, including position title, grade, Service, military occupational specialty or designator, and required clearances and qualifications, used to source personnel from the joint manpower pool and Service components.

"The JTF's billet roster — every position by Service, grade, MOS, and clearance."

JMD is the document that tells you exactly which billets a joint headquarters needs and what kind of person fills each one — O-6 Navy SWO with TS/SCI in the J3 ops chief seat, O-4 Air Force intel officer with current TS in the J2 indications and warning lead, E-7 Army 25 series at the J6 helpdesk. The JMD is what J-1 (manpower and personnel) works to source through the Joint Force Provider process and the Service component manpower systems. For a service member, ending up "on a JMD" means you got tasked to a joint billet — usually 6 to 24 months, often unaccompanied if it's downrange, and you're working for a joint chain even though you're still in your Service's lane for evaluations, promotions, and paychecks. JMDs grow and shrink across phases of an operation.

Per the DoD Dictionary, a joint mission-essential equipment list — the consolidated list of equipment that a joint force or joint task force has determined is essential to accomplish its assigned mission-essential tasks, derived from Service mission-essential equipment lists and used to prioritize maintenance, sourcing, and readiness reporting.

"The joint "what we cannot do this mission without" equipment list."

JMEEL is the joint version of every Service's "what equipment we absolutely need" list — and it's the document a JTF or joint headquarters uses to fight for repair parts, maintenance priority, and replacement when something breaks in theater. If a system is on the JMEEL and it goes red, the readiness report goes to the JFC and the staff actually does something about it; if it's not on the JMEEL, it competes with everything else for attention and usually loses. The list is built backwards from the JMETL (the task list) — what tasks must we be able to do, what equipment do we need to do those tasks, what's essential vs. nice-to-have. JMEELs get more honest under operational stress; in garrison they tend to be aspirational.

Per the DoD Dictionary, the joint manpower program — the process by which joint manpower requirements are validated, prioritized, and sourced across the Department of Defense, including establishment and revision of joint manning documents, joint duty assignment management, and resourcing of joint and combatant command billets through the Service components.

"The joint manpower process — validates, prioritizes, and sources joint billets."

JMP is the staff process behind every JMD — the workflow through which combatant commands, joint headquarters, and JTFs justify the billets they're asking for, get them validated by the Joint Staff J-1 and the Office of the Secretary of Defense, and then sourced by the Services through the joint manpower allocation process. The JMP is also where joint duty assignment (JDA) credit gets adjudicated — which billets count toward joint qualification under the Goldwater-Nichols statutory framework, what credit a service member earns from a tour, and how that ties to joint qualification levels and O-6/flag promotion. For an action officer working a joint manpower issue, the JMP is mostly forms, briefing slides, and waiting for the joint manpower validation board to convene. For the service member, the JMP is invisible right up until the Service tells them they're going on orders to a joint billet.

Per the DoD Dictionary, a joint military postal activity — the joint or Service military postal organization responsible for processing official and personal mail to and from deployed and overseas military personnel, including Army/Air Force Postal Service (AAPS), Navy Postal Service, and Marine Corps Postal Service operations under the framework of the Military Postal Service Agency (MPSA).

"The military post office — APO and FPO mail in and out of theater."

JMPA is the joint side of military mail — every APO and FPO box that lets a deployed service member get a care package from home or send a birthday card to their kid. Under the hood it's a Military Postal Service Agency framework with Army/Air Force Postal Service running most APO operations and Navy/Marine Corps postal handling FPO afloat. The military postal system uses the civilian USPS rate structure (a CONUS-priced first-class letter to an APO is treated as a domestic letter), and that subsidy is one of the small but real quality-of-life programs. In a deployed environment, the JMPA-coordinated mail run is its own operational thread — flights getting mail forward, postal clerks sorting in the dust, the bag tagged for a specific FOB that needs the next convoy or rotary lift to actually get there. For service members, the day mail catches up is a real day.

Joint Personnel Accountability Reconciliation and Reporting (JPARR) is the joint process and supporting systems used to track, reconcile, and report the location and status of all DoD personnel in a designated area — used principally after natural disasters, mass casualty events, and other incidents requiring confirmation that every person assigned to or transiting an area is accounted for.

"The joint personnel accountability process — track everybody after a disaster."

JPARR is the system that gets exercised after a hurricane hits a base, after a major incident in theater, or after any event where the chain of command needs to confirm that every assigned and transiting person is accounted for. The process pulls together unit-level musters, contractor reporting, dependent accountability, and TDY/transient personnel into a single reconciled picture. For a service member, JPARR shows up as the post-incident accountability check — call your chain of command, log in to ADPAAS, confirm your location and status, and don't go off-grid until your unit has accountability. The Army Disaster Personnel Accountability and Assessment System (ADPAAS) is the joint backbone tool. Failure to muster after an event triggers the search-and-recovery process, which is expensive to spin up unnecessarily.

The Joint Public Affairs Support Element (JPASE) is the Joint Staff-controlled deployable joint public affairs capability that provides public affairs augmentation to joint force commanders — capable of supporting JTF establishment with media operations, command information, and community-relations capability — based at Fort Meade and operating under the Joint Staff Public Affairs.

"The deployable joint PA team — JTF media ops and command information."

JPASE is the joint deployable public affairs team — the Joint Staff PA capability that surges to a joint task force when it stands up and the JTF needs PA capacity beyond its organic staff. The element runs media operations (press conferences, embedded media, releases), command information (internal communications to the joint force), and community relations as needed. JPASE deploys with broadcast and print production capability, social-media reach, and PA officers with joint experience. The unit is based at Fort Meade and trains continuously to be ready to push forward on short notice. For a JTF commander spinning up, JPASE is one of the early-arriving capability augmentations that lets PA function before the JTF organic PA staff is fully formed.

A joint postal cell (JPC) is the joint force commander's postal operations staff element — coordinates the movement, processing, and delivery of official and personal mail within the joint operations area, working with the Military Postal Service Agency, the components, and the Service postal organizations to maintain the mail link between deployed personnel and home.

"The joint postal coordination cell — keeps the mail flowing to the deployed force."

JPC is the joint shop that makes sure the mail keeps flowing — coordinating with the Military Postal Service Agency, the component postal staffs (Army postal companies, Air Force postal squadrons, Navy postal clerks at fleet mail centers), and the broader postal infrastructure to keep official and personal mail moving into and out of the joint operations area. For a deployed service member, JPC is invisible — you just notice when mail gets slow or when packages start backlogging at the APO/FPO. The cell deals with the predictable surges (the holiday-card season is brutal), the unpredictable disruptions (a downed contract aircraft can delay mail for weeks), and the policy questions (what can ship in mail to and from a deployed location, which depends on country, command policy, and changing customs rules).

A Joint Personal Effects Depot (JPED) is the joint mortuary affairs facility responsible for receiving, processing, inventorying, and returning the personal effects of deceased and missing service members to their next of kin — operating under the joint mortuary affairs program with Army Mortuary Affairs as the executive agent and the JPED located historically at Dover Air Force Base in association with the Air Force Mortuary Affairs Operations.

"The joint depot that processes personal effects of deceased service members."

JPED is the depot that handles the personal effects — the wallet, the watch, the photographs in the rucksack, the letters from home, everything that was on or with a service member who died or went missing in service. The depot inventories and processes those items with significant care because for the families they're the last tangible connection. JPED operates under the joint mortuary affairs program (Army is the executive agent) and historically has been collocated with Air Force Mortuary Affairs Operations at Dover AFB. For a service member, JPED is one of those organizations you hope you never need to know about; for casualty assistance officers and the families they support, JPED is one of the most consequential pieces of the joint personnel system.

The joint personnel status and casualty report (JPERSTAT) is the standardized daily personnel report submitted by joint task forces and component commands to higher headquarters — providing assigned, present-for-duty, leave, hospitalized, missing, captured, and casualty numbers across the force — the principal joint-level instrument for tracking personnel strength and casualty status during operations.

"The daily joint personnel and casualty roll-up — assigned, PFD, hospitalized, casualties."

JPERSTAT is the daily report somebody on the J1 staff is producing every morning during operations — the roll-up of how many people are assigned, how many are present for duty, how many are on leave or TDY, how many are hospitalized, how many are missing, captured, or casualties. The report flows from unit personnel sections up through component personnel staffs to the JTF J1, and from there to the supported combatant command and back to the Joint Staff and the Services. For a soldier or airman, JPERSTAT is invisible — you're a line in a spreadsheet somewhere — but the report drives replacement requests, casualty notifications, and a great deal of higher-headquarters situational awareness. When the casualty count goes up, JPERSTAT is where the data first appears.

A Joint Personnel Operations Center (JPOC) is the joint task force or combatant command personnel operations center — the J1 staff element responsible for day-to-day personnel operations coordination, casualty processing, personnel accountability, and the interface between the joint force commander's personnel staff and component personnel organizations.

"The J1 personnel ops center at a JTF — casualty processing and accountability."

JPOC is the J1 watch floor at a joint task force or combatant command — the operations center for personnel matters, running 24/7 during contingency operations to process casualty reports, push accountability data, coordinate replacements, handle emergency leave and red-cross messages, and manage the broader personnel operational tempo. For a J1 staff officer, JPOC duty is the personnel parallel to the J3 JOC watch floor: the same operational rhythm, the same battle-rhythm meetings, the same fight to get accurate and timely information through the system. JPOC also coordinates with the supporting Services' personnel commands for personnel actions that exceed JTF authority (separations, promotions, awards staffing).

A joint personnel processing center (JPPC) is the joint facility or function responsible for in-processing and out-processing personnel into and out of a theater of operations — handling deployment readiness verification, theater-specific briefings, identification cards, mobilization actions, and the administrative processing required to move individual augmentees and units into and out of the operational area.

"The theater personnel processing center — in/out processing for deployers."

JPPC is the line you stand in when you arrive in theater and when you leave — the joint personnel processing center where deployment readiness gets verified (SRP-equivalent items, theater-specific medical, briefings, ID card updates, mobilization paperwork for Reserve Component, demobilization paperwork on the way home). For an individual augmentee or a unit that's flowing in or out, JPPC is a half-day to a full-day stop somewhere on the deployment path — Kuwait CRC equivalent, the in-country reception center, or a CONUS demobilization site. The functions vary slightly by theater but the principle is the same: catch deployment-readiness shortfalls before people get pushed to units, and clean up administrative loose ends before they go home.

The senior joint flag-officer body, chaired by the Vice Chairman of the Joint Chiefs of Staff with service vice chief members, that validates joint capability requirements under the JCIDS process and provides recommendations to the Secretary of Defense and Chairman of the Joint Chiefs on capability matters.

"The joint flag-officer body that validates joint capability requirements."

JROC is where capability requirements documents (ICD, CDD, CPD) for joint and major programs get validated — the Vice Chairman of the Joint Chiefs chairs, the service vice chiefs sit as principals, and a permanent staff (the J-8) does the analytic and document-management work. JROC validation is statutorily required for MDAPs and for joint-equity programs; programs that fail JROC validation generally cannot proceed past the relevant Milestone. The body has gained and lost influence with successive administrations and has been criticized at various times as either too prescriptive or too rubber-stamp.

A board convened to review and validate operational requirements at the joint level, providing senior-level oversight of requirements proposed for joint endorsement, joint integration, or joint funding (DoD Dictionary, November 2021).

"The JRRB — board where joint requirements get a senior-level look."

JRRB is one of the requirements-validation boards the joint staff and combatant commands use to keep Service-sponsored requirements honest at the joint level — does this thing actually need to exist, does it duplicate something already in the program, does the requirement statement match the operational problem. The JRRB sits inside the broader joint requirements oversight architecture (JROC at the top, working groups beneath, JRRBs and similar review boards as the senior-level scrub). Operationally, a JRRB is the kind of meeting an O-6 program lead spends two months building a read-ahead for; the slides get rewritten three times the week prior. The decision out the back is either "endorsed," "endorsed with conditions," or "send it back."

The Joint Staff's electronic workflow system and process for staffing actions, papers, and decisions through the Joint Staff for the Chairman of the Joint Chiefs of Staff and senior leaders, providing tasking, coordination, approval routing, and archival of joint-level decision documents (DoD Dictionary, November 2021).

"JSAP — the Joint Staff's electronic workflow for routing papers up to the Chairman."

JSAP is the electronic system through which a paper gets staffed from a J-directorate action officer up through the Director Joint Staff and to the Chairman or the Secretary — the joint-staff equivalent of the Army's DARTS or the Navy's TWMS workflow. An action gets a JSAP number, gets coordinated through the relevant J-directorates and Services, gets routed through the Director, and gets signed out. For an O-4 or O-5 action officer on the Joint Staff, JSAPs are the day-to-day vocabulary of work — "I owe a JSAP by COB" means a paper is past due on the workflow. The system also creates the archival trail that lets the next action officer pull up what was decided two years ago and why.

The Joint Staff directorate designated as the lead office for development, maintenance, and revision of a specific joint publication, providing senior-level sponsorship, coordination across Services and combatant commands, and final endorsement of the publication for Chairman approval (DoD Dictionary, November 2021).

"JSDS — the Joint Staff directorate that owns a specific joint publication."

JSDS is the bureaucratic answer to "who owns this JP?" — every joint publication has a Joint Staff sponsor (a J-directorate) and a lead agent (often a Service or combatant command). The JSDS provides senior-level continuity across the multi-year development and revision cycle, keeps the lead agent honest, coordinates the staffing across Services, and presents the publication for Chairman signature. The relationship matters because joint publications get rewritten every few years; without a stable sponsor, doctrine drifts in directions nobody intended. For an action officer working a JP rewrite, the JSDS is the person who tells you when it is ready to go to coordination and when it is not.

The primary system through which the Chairman of the Joint Chiefs of Staff carries out statutory responsibilities for strategic planning under Title 10 USC, providing the framework for the National Military Strategy, Chairman's Risk Assessment, Joint Strategic Campaign Plan, and related joint strategic planning documents (DoD Dictionary, November 2021).

"JSPS — the Chairman's system for strategic planning and risk assessment."

JSPS is the formal framework through which the Chairman of the Joint Chiefs discharges the Title 10 strategic-planning responsibilities — the architecture under which the National Military Strategy, the Chairman's Risk Assessment, the Joint Strategic Campaign Plan (and its predecessor documents), and the related global integration outputs get produced. The system has evolved across editions of CJCSI 3100 series guidance; the documents themselves get rewritten every few years as the strategic environment shifts. For a Joint Staff strategist (J5 directorate, J7 in some lanes), JSPS is the doctrinal name for the workflow that produces the documents the Chairman signs and the SECDEF takes to the President. The everyday work is reconciling Service positions, COCOM positions, and OSD positions into language a Chairman can defend.

A senior-level board chaired by the Vice Chairman of the Joint Chiefs of Staff to resolve transportation prioritization conflicts among combatant commanders and to allocate strategic transportation assets when demand exceeds USTRANSCOM capacity, providing joint-level adjudication of competing lift requirements (DoD Dictionary, November 2021).

"JTB — the Vice Chairman's board for resolving strategic lift conflicts."

JTB is the board that exists for the moments when strategic lift demand exceeds USTRANSCOM's ability to provide it — the Vice Chairman chairs it and brings the combatant command J3/J4 leads to the table to fight over who gets the airframes and the sealift. The board is not convened lightly; routine lift prioritization runs through USTRANSCOM and the JTCC. The JTB comes into play when the demand picture is so saturated that COCOMs are actively trading off — INDOPACOM needs the C-17s for a deterrence move, CENTCOM needs them for a rotation, EUCOM needs them for a contingency. The Vice Chairman's vote breaks the tie and the outputs become DoD-wide priorities for the cycle.

A manning document that specifies the authorized personnel structure of a joint organization or activity by position, grade, Service, and specialty, providing the joint equivalent of a Service-specific Table of Distribution and Allowances (TDA) for joint billets and joint manpower management (DoD Dictionary, November 2021).

"JTD — the manning document for joint billets, joint equivalent of a TDA."

JTD is the manning document for a joint organization — the joint equivalent of an Army TDA or a Navy manning document, specifying which positions exist, what grade and Service and specialty each requires, and where they sit in the org chart. Joint Staff billets, combatant command billets, joint task force billets, and joint activity billets all run off JTDs. For an officer or NCO showing up to a joint billet, the JTD is the document that defines the position you're filling and the seat you sit in. For a joint manpower planner, the JTD is the lever for adding, removing, or restructuring joint positions — and changes to JTDs are politically expensive because every Service watches its joint-billet count and every COCOM watches its JTD growth.

A consolidated joint planning document showing the mobilization and distribution requirements for personnel, equipment, and units across the joint force, used to coordinate Service mobilization activities and joint force generation in support of operational plans (DoD Dictionary, November 2021).

"JTMD — the joint table of who and what mobilizes and goes where."

JTMD is one of the joint planning documents that crosswalks Service mobilization tables into a joint picture — who mobilizes (which Reserve Component units, which Individual Mobilization Augmentees, which retiree recall categories), what equipment moves with them, where they go. The document gets used in OPLAN execution and in the broader Total Force generation process. For a planner on a Service component staff or the Joint Staff J-3/J-5, JTMD entries are the input to TPFDD building and Time Phased Force Deployment List development. The "; Joint" tail on the DoD Dictionary entry indicates this acronym also collides with a second related Joint planning artifact (the Dictionary deliberately captures both senses).

The single, joint regulation governing travel and transportation allowances for uniformed Service members and DoD civilian employees, issued by the Per Diem, Travel and Transportation Allowance Committee under DoDI 5154.31 Volume 5, with continuous updates published online.

"The single regulation governing military travel and transportation allowances."

The JTR is the rulebook for everything PCS, TDY, dependent travel, household goods, per diem, allowances during travel, and a long list of related entitlements. It absorbed the older JFTR (uniformed) and JTR (civilian) into a single document in 2014. It is exhaustive, regularly updated, and most finance and travel decisions can be sourced back to a specific JTR chapter. Members fighting a denied entitlement at the travel office should get the JTR citation and the date — the JTR is the answer book, not the travel clerk's interpretation of it.

A capability requirement identified by a combatant commander as inadequately resourced and necessary to meet a validated, urgent operational requirement — processed through an expedited validation and resourcing pathway through the Joint Staff and the Office of the Secretary of Defense to field a solution faster than the deliberate acquisition cycle would permit (DoD Dictionary, November 2021).

"JUON — the joint expedited acquisition path for an urgent combatant command need."

JUON is the expedited requirements pathway a combatant command uses when an urgent operational gap cannot wait for the deliberate JCIDS process — the validated need goes through the Joint Staff J-8 and OSD on an accelerated clock and gets resourced through whatever acquisition lane is fastest (Service rapid acquisition cells, the JRAC Joint Rapid Acquisition Cell, DoD reprogramming). The MRAP procurement during Iraq was driven through JUON/JEON channels (along with congressional supplementals); counter-UAS capability has been a major JUON driver in the 2020s. The path is faster than normal acquisition but not free — the postwar question of what to do with all the JUON-procured equipment when the urgency passes is one of the harder force-design questions of the post-OIF/OEF era.

A staff element established at a joint headquarters or operational location to coordinate the visit of senior leaders, congressional delegations, distinguished visitors, and foreign liaisons — managing protocol, transportation, scheduling, briefing support, and security coordination throughout the visit (DoD Dictionary, November 2021).

"JVB — the visitors bureau that handles SecDef, CODELs, and DV visits."

JVB is the protocol shop at a joint headquarters or deployed location — the people who run the schedule, the windshield tour, the briefing rotation, the meals, and the security coordination when the Secretary of Defense, a four-star, a CODEL (congressional delegation), or a foreign distinguished visitor comes through. For an O-3 or O-4 detailed to JVB, the assignment is part protocol, part logistics, part stage management; the work is unglamorous but consequential because a visit gone sideways is the kind of thing that gets remembered. Every COCOM headquarters has a JVB; deployed joint task forces stand them up as needed. The art is making a sixteen-hour visit feel both informed and unrushed.

An ad hoc or standing group of subject-matter experts and staff representatives from multiple joint or interagency organizations, convened to develop products, recommendations, or solutions on a specific joint problem set — typically chaired by an O-5 or O-6 with membership drawn from relevant J-directorates and Service components (DoD Dictionary, November 2021).

"JWG — the standard joint working group construct used across J-staff problems."

JWG is the generic name for the kind of cross-J-directorate working group that does the staff-level analytic and product-development work behind almost every joint decision — an O-5 or O-6 chair, action officers from the relevant J-directorates, Service component representatives, and sometimes interagency or coalition partners. Every JFC headquarters runs dozens of JWGs simultaneously (targeting, intelligence, sustainment, fires, information, cyber, IO, the list is long). For an action officer, JWG attendance is the daily currency of joint staff work — show up with read-ahead consumed, brief your equity, take the taskers, deliver the product. The JWG output feeds the JTWG, JTCB, JCB, or whatever higher decision board owns the issue.

A performance attribute in a JCIDS capability requirements document considered so significant that failure to meet the threshold value would cause the concept or system to be reevaluated or the program to be reassessed or terminated, with each KPP including both a threshold (minimum acceptable) value and an objective (desired) value, codified at 10 USC 3022.

"A must-have performance attribute in a capability requirements document."

KPPs are the firm requirements — failure to meet threshold means program reevaluation, which in practice means either a requirements change or program termination. Each program has a small number of KPPs (typically five to ten) plus a larger number of KSAs and other attributes. The Net-Ready, Survivability, Sustainability, Force Protection, Training, and certain other KPPs are mandatory across JCIDS programs; others are domain-specific (range, speed, payload). KPP shaping at the CDD stage drives much of the subsequent cost and schedule.

A performance attribute in a JCIDS capability requirements document considered important but not so critical that failure to meet threshold would trigger reevaluation of the program — that is, an attribute below the KPP threshold of criticality, used to communicate significant performance characteristics that the program should meet but where some trade space exists.

"A significant-but-tradeable performance attribute in a capability document."

KSAs occupy the middle layer between KPPs (must-have, reevaluation if missed) and lower-tier attributes (nice to have, full trade space). The KSA framing was added to JCIDS to give the requirements community a way to communicate "this matters but we are not going to terminate the program if you miss it." In practice, the line between KPP and KSA at the CDD stage is one of the most contested negotiations between the requirements sponsor, the program office, the FCB, and the JROC.

A US Treasury financial account established at a financial institution outside the United States to facilitate disbursement of US Government funds for overseas operations — providing a controlled mechanism for cash management, foreign currency disbursement, and contracted services payment in operational environments (DoD Dictionary, November 2021).

"LDA — Treasury depository account for overseas operational disbursements."

LDA is the Treasury-side mechanism that gives a deployed disbursing officer the ability to operate a depository account at a foreign bank to handle cash, foreign currency disbursement, and contracted services payment in an operational environment — the financial-management plumbing that makes overseas operations possible without flying pallets of cash everywhere. The accounts are tightly controlled by the Department of the Treasury and Defense Finance and Accounting Service (DFAS), with audit and reconciliation requirements. For a deployed finance officer (FA branch in the Army, or Service equivalent), LDA management is one of the daily realities of operational financial management. The vocabulary is dense and the audit trail is unforgiving.

The Service component designated by the joint force commander to lead the integration of environmental considerations into joint operations within a specific operational area — including environmental compliance, hazardous materials management, waste handling, environmental restoration, and coordination with host-nation environmental authorities (DoD Dictionary, November 2021).

"LEC — the Service component lead for environmental considerations in joint operations."

LEC is the joint construct for designating one Service component as the lead for environmental considerations in a joint operation — environmental compliance with US and host-nation law, hazardous materials and waste management (the burn pit lesson learned from Iraq and Afghanistan continues to drive policy), environmental restoration before redeployment, coordination with host-nation environmental authorities. The lead-component model is used because environmental management requires consistent standards, audit trails, and host-nation interface — running parallel Service-unique programs creates seams. The Army is most often the LEC in land-heavy operations; the Navy or Marine Corps in maritime-heavy operations. For environmental personnel (74A in the Army, Service equivalents), LEC designation is the basis of the operational environmental plan.

A sequential numerical position on a promotion list, established when the Secretary concerned approves the list produced by a promotion selection board, that determines the order in which selected officers are actually promoted (frocked or pinned) over the course of the promotion list's execution year, with lower numbers promoting first.

"A sequential number on the promotion list determining order of actual pin-on."

Line numbers are how a "promotion list" turns into actual promotions over time — the list is approved with each select assigned a sequential line number, and authorizations to actually promote (vacancy authorizations, fiscal-year accounting) release line numbers over the course of the promotion-list execution year. An officer with line number 1 promotes quickly after list approval; an officer with line number 500 may not pin on for many months. Frocking authority lets officers wear the next-grade insignia early without the actual pay-and-record promotion; line number drives the pay-and-record date.

Logistics Metrics Analysis Reporting System — a Defense Logistics Agency system providing performance metrics, customer wait time data, and reporting on the supply chain performance of DLA-managed materiel across the Department of Defense (DoD Dictionary, November 2021).

"LMARS — DLA's metrics and reporting system for supply chain performance."

LMARS is the Defense Logistics Agency's metrics and reporting backbone — the system where customer wait time, requisition fill rate, backorder status, and the broader DLA supply chain performance data lives for the J-staff and Service logistics communities to query. The day-to-day relevance is that a brigade or wing logistics officer trying to figure out why a Class IX repair part is taking forever to arrive will pull LMARS data to see whether the problem is the requisition, the source of supply, the wholesale stock position, or the transportation leg. LMARS is one of the joint logistics analytic systems that sits alongside IGC, the Logistics Functional Area Services, and the broader joint logistics common operating picture toolset. The data quality fights between Service logistics systems feeding LMARS are a perennial sustainment-staff irritation.

The US Army's wholesale logistics enterprise resource planning system, based on the SAP commercial ERP platform, providing financial accounting, supply chain management, maintenance planning, and acquisition support for the depot-level and national-level Army logistics enterprise — distinct from GCSS-Army, which handles the retail (unit-level and brigade-level) layer.

"The Army's wholesale-level logistics ERP system at the depot and national level."

LMP is the Army's "behind the warehouse" wholesale logistics system — the depots, the national-level supply system, the financial accounting for Army equipment. GCSS-Army is the retail counterpart that the supply rooms and motor pools see; LMP is what the depots see. The two systems have to talk to each other, and the integration has been a recurring source of friction over the years. SAP under the hood means commercial-ERP behavior, with all the configuration complexity that implies. Programs that fight LMP / GCSS-Army integration usually lose.

Letter of instruction — a directive issued by a commander to subordinate commanders or staff, providing detailed guidance, intent, planning factors, and specific instructions for the conduct of an operation, exercise, or activity (DoD Dictionary, November 2021).

"LOI — commander's letter giving detailed guidance for an operation or exercise."

LOI is one of the standard staff products commanders use to issue detailed guidance for an operation, exercise, ceremony, or significant event — somewhere between an order (which is a directive in the OPORD/FRAGORD lineage) and a memo (which is information only). The LOI typically lays out the commander's intent, the planning factors subordinates need, specific instructions on coordination and reporting, and the end state. Staff officers who write the LOI know the audience is busy subordinate commanders and their staffs — the document needs to be clear, complete, and short. A "no-shit LOI" with the salient guidance up front in two pages is good staff work; a forty-page LOI with everything-and-the-kitchen-sink is the kind of staff product subordinates ignore in favor of finding a peer who knows what is actually expected.

A source-selection method in which the award goes to the offeror with the lowest evaluated price among those meeting all minimum technical requirements — without tradeoffs against higher-rated technical or past-performance proposals.

"A source selection that awards to the lowest price meeting the requirements."

LPTA is appropriate for commodities and clearly-specified services. It is widely abused for complex services — IT, engineering, professional services — where it predictably awards to inexperienced contractors with thin teams. Congress and DoD have tightened LPTA use in recent NDAAs; the Section 880 restrictions limit it for services contracts above thresholds. If you see LPTA on a complex services requirement, ask why a tradeoff would not be more appropriate.

The Army installation-level organization, under Army Materiel Command through the Army Sustainment Command structure, that provides centralized logistics support to all Army units on the installation — including supply, maintenance, transportation, and food service.

"The Army's installation-level logistics organization."

The LRC is the one-stop logistics shop at most major Army installations — supply support activity (SSA) operations, installation maintenance, transportation motor pool, central issue facility, and ammunition issue all sit under the LRC. The Director is typically a senior civilian. Units on the installation interact with the LRC daily for parts, equipment turn-in, and motor-pool services. The model consolidated functions that were once unit-organic but became inefficient as the operational tempo dropped.

Logistics response time — the total elapsed time between the submission of a requisition for supply or service support and the receipt of that supply or service by the requesting unit, used as a key performance metric for the joint logistics enterprise (DoD Dictionary, November 2021).

"LRT — total time from requisition submitted to cargo received."

LRT is the headline metric the joint logistics community uses to measure how long it takes for a unit's requisition to actually result in cargo on the receiving dock — the total time from "order placed" to "supply received," not just the transportation leg. LRT includes requisition processing, source of supply selection, stockage check, picking and packing at the depot, transportation from depot to SPOE, sealift or airlift to SPOD, and onward distribution to the requesting unit. The metric drives a lot of supply chain optimization decisions — where to position prepositioned stocks, how much surge airlift capacity to fund, where to expand depot operations. The unit-level lived reality is the maintenance officer pulling LRT data through LMARS to brief the commander on why the deadlined vehicle has been NMCS for three weeks.

Logistics support analysis (also logistics supportability analysis) — the structured analytical process applied during the acquisition lifecycle of a defense system to identify, define, and document the logistics support requirements (parts, manuals, training, support equipment, facilities, personnel) needed to operate and maintain the system across its service life (DoD Dictionary, November 2021).

"LSA — the acquisition-phase analysis of what it takes to support a system in service."

LSA is the structured analysis that program offices and acquisition logisticians conduct during the development of a defense system to figure out everything required to actually support that system after fielding — spare parts list, technical manuals, training requirements, special tools and test equipment, facilities, personnel and MOS requirements, depot maintenance plans. The work is dry but consequential: a system fielded without a sound LSA is a system whose maintenance reality catches the operating force by surprise (the Service members discover at the third unit that the part isn't in the supply system, the manual doesn't exist, the MOS hasn't been trained). LSA products feed the Integrated Logistics Support plan that goes with the system through its service life. The discipline runs across DoD 5000-series acquisition policy and is one of the load-bearing pieces of supportability engineering.

Lead Service for contracting — the Service designated by the joint force commander to plan and execute common contracting support to the joint force in a specified operational area, providing unified contracting authority across the joint force for designated commodities and services (DoD Dictionary, November 2021).

"LSC — the Service designated as lead for contracting support to the joint force."

LSC is the joint-contracting construct that designates one Service as the lead for buying common goods and services on behalf of the entire joint force in an operational area — instead of every Service component running its own contracting shop and bidding against each other for the same local fuel, water, food, lodging, and labor, the JFC designates an LSC and that Service's contracting officers serve everyone. The LSC is one of the principal joint-contracting tools alongside the LSCC (Lead Service for Contracting Coordination, the lower-intensity coordination role) and the Joint Theater Support Contracting Command construct. The Service member lived reality of LSC is the contracting officer from one Service handling the LOGCAP-style task orders for the entire JFC AOR; the staff fights about which Service gets designated LSC are real, because the workload is significant and the authorities carry real responsibility.

Lead Service for contracting coordination — the Service designated by the joint force commander to coordinate (but not execute) contracting support across the joint force in a specified operational area, providing visibility and deconfliction of Service-component contracting activities without unified execution authority (DoD Dictionary, November 2021).

"LSCC — Service designated to coordinate (not execute) joint contracting."

LSCC is the lower-intensity sibling of LSC — instead of one Service executing contracting for the whole joint force (LSC), the LSCC merely coordinates and deconflicts the Service components' own contracting shops so they don't bid against each other and don't exhaust local economies. The JFC chooses between LSC and LSCC based on operational tempo, scale of the contracting demand, and the political and logistic complexity of the operating area. In a small-footprint operation LSCC may be sufficient; in a large-scale contingency the JFC typically pushes to LSC for unified execution authority. The Service member lived reality of LSCC is the contracting officers from each Service component coordinating through a weekly LSCC working group and a shared awareness dashboard, but each component contracting officer retains execution authority.

The systematic process of collecting, analyzing, and reporting information on the implementation and outcomes of programs, operations, and activities — used across security cooperation, foreign assistance, stability operations, and other lines of effort to assess whether the activity is achieving the intended effect and to inform adjustment of the approach (DoD Dictionary, November 2021).

"M&E — the assessment process that says whether a program is actually working."

M&E is the discipline that exists because the alternative is spending years on a security cooperation program or a stability line of effort without ever knowing whether it's producing the intended effect. The monitoring side tracks inputs and outputs (advisors deployed, equipment delivered, partner units certified); the evaluation side asks whether the outputs are producing the outcomes the program was supposed to produce (partner capability that changes the security environment, governance that holds, instability that drops). The discipline came over from international development practice and now lives across DSCA programs, the State INL/IO portfolio, and DoD stability assessments. The honest version of M&E surfaces programs that aren't working; the dishonest version reports outputs as if they were outcomes. Which version a command runs depends on the senior leader's appetite for hearing bad news.

A formerly statutory category of major information technology acquisition program, established by Public Law 105-261, that triggered enhanced oversight requirements similar to but distinct from MDAP — repealed in the FY2017 National Defense Authorization Act, with replacement IT program oversight handled through other authorities including the Software Acquisition Pathway and BCAT (Business Capability Acquisition Cycle) constructs.

"A legacy major IT acquisition category, replaced by newer software pathway authorities."

MAIS is the legacy IT-program tier — established in the late 1990s, it required separate Major Automated Information System Annual Reports (MAIS Annual Reports, distinct from SARs) and had its own MDA chain. The category was repealed in 2017 NDAA Section 833 as part of broader acquisition reform; current IT-program oversight runs through the Software Acquisition Pathway, the Business Capability Acquisition Cycle, or — for programs that meet MDAP thresholds — the standard MDAP machinery. Historical documents and ongoing programs still reference MAIS terminology.

A major subdivision of the Air Force or Space Force that is assigned a major part of the service mission, directly subordinate to Headquarters Air Force or Headquarters Space Force.

"A top-level subdivision of the Air Force or Space Force."

MAJCOMs are the Air Force's equivalent of Army Commands (ACOMs) or Navy systems commands — the top organizational tier under Headquarters Air Force. Examples include Air Combat Command (ACC), Air Mobility Command (AMC), Air Education and Training Command (AETC), Air Force Special Operations Command (AFSOC), Air Force Global Strike Command (AFGSC), Pacific Air Forces (PACAF), US Air Forces in Europe — Air Forces Africa (USAFE-AFAFRICA), and the Space Force equivalent Field Commands. MAJCOM lineage is a real identity marker for airmen.

The federal reserve component of the United States Marine Corps, headquartered in New Orleans, Louisiana, organized to provide trained units and qualified individual Marines to augment the Regular Marine Corps in time of war or national emergency.

"The Marine Corps' federal reserve component."

MARFORRES is structured around the 4th Marine Division, 4th Marine Aircraft Wing, 4th Marine Logistics Group, and Force Headquarters Group — the reserve mirror image of the active force. Reserve Marines have been heavily integrated into operational deployments since 2001, with reserve infantry battalions and aviation squadrons rotating into both Iraq and Afghanistan operations. The Marine Corps has the smallest reserve component proportionally of any service.

The Department of Defense information system used to report, track, and document the recovery, identification, processing, and disposition of remains under the Joint Mortuary Affairs Program — administered by the Joint Mortuary Affairs Office and used across Service component mortuary affairs operations (DoD Dictionary, November 2021).

"MARTS — the DoD information system tracking remains from recovery through disposition."

MARTS is the system that keeps the mortuary affairs chain accountable from the moment remains are recovered through identification, processing, evacuation, and return to families. Every record in MARTS is a person whose family is waiting; the data discipline is therefore strict — recovery location, condition, identification status (visual, biometric, dental, DNA confirmation), routing through each MACP and MAA, and ultimate disposition. The system is administered through the Joint Mortuary Affairs Office and feeds Dover Port Mortuary operations when remains return to CONUS. For the mortuary affairs Soldier or Marine on the ground, MARTS is the documentary trail that lets the system tell a family member, years later, exactly where their loved one was found and how the chain of custody was maintained.

The traditional Department of Defense acquisition pathway, governed by DoDI 5000.85, used for the development and production of major capability systems — Major Defense Acquisition Programs (MDAPs) and similar large platform-type programs — and structured around the Milestone A, B, and C decision points with JCIDS-validated requirements.

"The traditional MDAP-style acquisition pathway for major capability systems."

MCA is the "default" pathway most familiar to anyone who has worked acquisition over the past four decades — the Milestone A/B/C structure, JCIDS requirements documents (ICD/CDD/CPD), Selected Acquisition Reports, Nunn-McCurdy oversight, and the heaviest documentation load. It remains the right pathway for major hardware programs (ships, aircraft, ground vehicles, missile systems). Critics argue that even MCA programs would benefit from more spiraling and less front-loading; defenders argue that the discipline is necessary for the dollar values and operational consequences involved.

The US Marine Corps subordinate command, headquartered at Albany, Georgia, responsible for the supply chain management, depot-level maintenance, and prepositioned-stocks management for the Marine Corps — including Marine Corps Logistics Base Albany and Marine Corps Logistics Base Barstow (the two principal Marine depots).

"The Marine Corps command for logistics, depot maintenance, and prepositioned stocks."

MCLC is the Marine Corps counterpart to AMCOM/TACOM/CECOM at the wholesale level — fewer separate commands by equipment type, given the smaller Marine equipment portfolio, but the same essential functions. Marine Corps Logistics Base Albany and MCLB Barstow are the two principal Marine depot facilities. The Marine Corps Prepositioning Program (MPP) — afloat (Maritime Prepositioning Force) and ashore (Norway, Diego Garcia, Korea) — falls within MCLC's management chain. The command supports Marine Air-Ground Task Forces wherever they deploy.

The senior enlisted member of the United States Coast Guard, occupying a unique grade above E-9 (E-9 Special), serving as the principal enlisted advisor to the Commandant of the Coast Guard on enlisted-related matters and as the institutional representative of the Coast Guard's enlisted force.

"The senior enlisted member of the Coast Guard and principal enlisted advisor to the Commandant."

MCPOCG is the Coast Guard counterpart to the other services' senior enlisted positions — a single Master Chief Petty Officer serving as the Commandant's principal enlisted advisor and the institutional voice of the Coast Guard's enlisted force. The Coast Guard sits under DHS in peacetime (unlike the other services under DoD) but the senior-enlisted role has the same fundamental shape: advise the senior service leader, travel the force, participate in policy decisions affecting the enlisted population.

The senior enlisted member of the United States Navy, occupying a unique grade above E-9 (E-9 Special), serving as the principal enlisted advisor to the Secretary of the Navy and the Chief of Naval Operations on enlisted-related matters.

"The senior enlisted member of the US Navy and principal enlisted advisor to the CNO."

MCPON (pronounced "mick-pon") is the Navy counterpart to SMA, CMSAF, and SgtMajMC — a single Master Chief Petty Officer serving as the senior enlisted voice of the service. The MCPON travels the fleet, meets with sailors at all grades, participates in CNO and SECNAV-level decisions on personnel policy, and serves as the institutional representative of the Navy's enlisted force in Washington and beyond. The position has been held by Master Chiefs from across the Navy's rate communities.

The designated official with the authority to approve entry of an acquisition program into the next phase at each Milestone (A, B, and C) — for ACAT I programs typically the Under Secretary of Defense for Acquisition and Sustainment, for ACAT IC programs the service Component Acquisition Executive, for ACAT II the Component Acquisition Executive, and for ACAT III a Program Executive Officer or designated lower-level official.

"The designated official authorized to approve acquisition Milestone decisions."

MDA designation flows from ACAT designation — the higher the ACAT, the higher the MDA. The MDA reviews the Milestone documentation, presides over the Defense Acquisition Board (DAB) for ACAT I programs, and signs the Acquisition Decision Memorandum (ADM) that authorizes the program's next phase. The MDA term is also overloaded — note this is distinct from the Missile Defense Agency. Program Office personnel often refer to "the MDA" without specifying which they mean; context disambiguates in practice.

A Department of Defense acquisition program that meets statutory dollar thresholds for total expenditure on research, development, test, and evaluation, or for procurement, established in 10 USC 4201, and therefore subject to the most stringent oversight, reporting, and approval requirements, including Selected Acquisition Report submission to Congress and Nunn-McCurdy cost-growth tracking.

"A statutorily defined major acquisition program with the strictest oversight."

MDAP is the top tier — a program that meets the statutory thresholds for total RDT&E or total procurement spend gets MDAP designation, which triggers the heaviest oversight machinery. Thresholds are inflation-adjusted periodically; recent thresholds have been in the range of hundreds of millions for RDT&E or over one billion for procurement (the exact thresholds in current law are the controlling figures). MDAP status pulls in OSD-level Milestone Decision Authority, mandatory SAR reporting to Congress, Nunn-McCurdy breach tracking, and the full DoDI 5000.85 process.

A DoD joint-service facility, operated by the United States Military Entrance Processing Command (USMEPCOM), where applicants for enlistment complete medical examination, ASVAB aptitude testing, background screening, job counseling, and the enlistment oath prior to shipping to initial entry training. MEPS processing is governed by USMEPCOM regulations including USMEPCOM Reg 40-1 (Medical Processing) and USMEPCOM Reg 601-23 (Enlistment Processing).

"One day at MEPS and you are on your way. Quick medical, paperwork, and you are sworn in."

It is rarely one day. Most applicants stay in the contracted hotel the night before, line up at 0400, and spend the day in some combination of cattle-call medical screening, the ASVAB if not already taken, a credit and background check, and the job counselor's computer that displays what is actually open this week. By the time you reach the counselor's desk you are hungry, sleep-poor, and being pressured to sign documents you did not draft. Read every line, including the enlistment option annexes that specify the actual job, the bonus, and the contract length. You can re-test the ASVAB later, but the contract you sign at MEPS governs your next four to six years and is much harder to change once you raise your hand.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a Defense Standardization Program document that establishes uniform engineering and technical requirements for military-unique or substantially modified commercial processes, procedures, practices, and methods — examples include MIL-STD-810 (environmental testing), MIL-STD-461 (electromagnetic interference), and MIL-STD-1553 (data bus).

"A military standard — the engineering and process specs for military-unique materiel."

MIL-STD is a Defense Standardization Program document that sets uniform engineering and technical requirements for military-unique processes and materials. The famous ones include MIL-STD-810 (environmental testing — how a radio survives shock, vibration, temperature, humidity, salt fog, immersion, the rest), MIL-STD-461 (electromagnetic interference and compatibility), and MIL-STD-1553 (the avionics data bus that runs through nearly every military aircraft built since the 1970s). The 1994 Perry Memo started the shift toward commercial standards where possible and MIL-STDs only where military-unique requirements demanded them; the result is that MIL-STD has gotten more selective and more important. When a procurement document says "tested to MIL-STD-810G" or "compliant with MIL-STD-461F," that is shorthand for hundreds of specific test conditions and engineering practices.

A DoD appropriation category funding major construction at military installations — new buildings, infrastructure, family housing. Distinct from O&M repair-and-maintenance and from base realignment funding.

"The funding category for major military construction projects."

MILCON dollars are tied to specific projects authorized line-by-line in the annual NDAA, then appropriated separately. A MILCON project takes years from need identification to ribbon cutting. Bases needing new facilities (housing, training ranges, dining facilities) compete with each other through the planning process; political and strategic priorities (the Pacific pivot, Army Forces Generation requirements) shape which projects move first.

The Defense Manpower Data Center self-service web portal that provides service members, retirees, and family members with online access to DEERS enrollment status, ID card sponsorship and appointment scheduling, Tricare plan enrollment, beneficiary updates, transfer of post-9/11 GI Bill benefits to dependents, and other personnel and benefit administrative actions.

"The DMDC portal for DEERS, ID cards, and benefit transfers."

MilConnect (milconnect.dmdc.osd.mil) is the front end for the DEERS layer — where you check whether your spouse is actually enrolled, schedule the RAPIDS appointment for a renewed dependent ID, initiate a Transfer of Education Benefits for the GI Bill, manage SGLI beneficiaries through SOES, and pull the various benefit verification letters that civilian institutions sometimes demand. It is the sibling to MyPay — MyPay does pay, MilConnect does identity and benefits — but service members regularly bounce between the two trying to figure out which one owns the thing they're trying to fix. The CAC-reader requirement on the desktop version drives a lot of people to the mobile app.

The Department of Defense acquisition-program decision point at which the Milestone Decision Authority approves entry into the Technology Maturation and Risk Reduction (TMRR) phase, based on an Analysis of Alternatives, a Materiel Development Decision, and the determination that one or more materiel approaches warrant further development effort.

"The acquisition decision point approving entry into TMRR after MSA."

Milestone A authorizes the program to move from "studying alternatives" into "maturing the technology of the chosen approach" — TMRR funding, prototype contracts, technology demonstrations, and the early systems-engineering work. The decision is based on the AoA, the Materiel Development Decision documentation, and an evaluation of technical risk. Milestone A is typically less visible to the public than Milestone B (the production-investment commitment) but commits real funding to one or more candidate approaches.

The Department of Defense acquisition-program decision point at which the Milestone Decision Authority approves entry into the Engineering and Manufacturing Development (EMD) phase, based on a validated Capability Development Document, satisfactory technology maturity, an approved acquisition strategy, an approved cost estimate, and the commitment of program funding for the EMD phase.

"The acquisition decision point approving entry into EMD with the validated CDD."

Milestone B is the most consequential decision for most programs — it commits the program to building the system the CDD describes, on the program baseline of cost, schedule, and performance approved at the milestone. After Milestone B, the program has a Program of Record, an Acquisition Program Baseline against which Nunn-McCurdy breaches are computed, and an MDAP-class oversight machinery if applicable. The work between Milestone B and Milestone C — the EMD phase — is where most schedule slip and cost growth historically occurs.

The Department of Defense acquisition-program decision point at which the Milestone Decision Authority approves entry into the Production and Deployment (P&D) phase, based on a Capability Production Document, demonstrated operational effectiveness and suitability through developmental and initial operational test and evaluation, and an approved Low-Rate Initial Production (LRIP) or Full-Rate Production decision.

"The acquisition decision point approving entry into production with the CPD."

Milestone C is the production decision — either a Low-Rate Initial Production (LRIP) authorization (a limited initial production buy while operational testing continues) or a Full-Rate Production decision (committing the full production buy). The decision rests on the CPD, the test results, and an updated cost and schedule baseline. The LRIP intermediate step exists specifically to avoid the historical pattern of committing to full production before testing revealed major problems; the LRIP-to-FRP transition is its own decision point.

The Air Force's legacy personnel records system, used by Military Personnel Flights and AFPC for managing assignment actions, promotion processing, evaluations, awards, and other personnel transactions for active-duty Airmen — interfacing with separate Air Force pay systems run through DFAS.

"The Air Force personnel records system at MPF and AFPC."

MILPDS is the Air Force's answer to eMILPO — the personnel-side system at the MPF (Military Personnel Flight) where assignments get cut, EPRs get tracked, promotion ineligibility flags get applied. It is text-based and old, and the Air Force has been working on a replacement under the broader AFPC modernization effort (myFSS the self-service front end, ARCNet the consolidated back-end vision). For now, MILPDS is what the personnel office actually transacts in; airmen interact with it indirectly through their assignments officer or through the myFSS portal. Pay sits separately at DFAS, which is the source of the seam that IPPS-A is trying to fix for the Army.

A formal numbered Army announcement, published through HRC, that conveys personnel policy, procedural guidance, selection results, board announcement and convening dates, or other authoritative personnel information to the field, with each MILPER carrying a year-and-sequence number and serving as the citable reference for the action it announces.

"A numbered Army personnel announcement covering policy, selection, or procedural guidance."

MILPER messages are how Army personnel actions become official to the field — board results published, application windows opened, policies revised, special-program eligibility announced. Officers and senior NCOs reference specific MILPER numbers when discussing recent changes ("the MILPER says..."). The publication numbering runs by year and sequence (e.g., MILPER 25-093). Many MILPER messages have parallel implementing instructions in unit S1s and HRC web pages; the MILPER itself is the citation.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a Defense Standardization Program document that describes the essential technical requirements for purchased materiel that is military-unique or substantially modified commercial — distinct from MIL-STD (which addresses processes and methods) in that MILSPEC addresses the materiel item itself.

"A military specification — the technical requirements document for a military-unique item."

MILSPEC is the materiel-side companion to MIL-STD — where MIL-STD covers processes and methods (testing, documentation, manufacturing practices), MILSPEC covers the specific technical requirements of an item being purchased. The cultural moment when something is said to be "MILSPEC" is shorthand for "built to the explicit military requirement document, not the consumer-grade commercial variant." Like MIL-STD, MILSPEC went through significant reform after the 1994 Perry Memo pushed the Department toward commercial item specifications where possible; the surviving MILSPECs cover items where commercial alternatives genuinely cannot meet military requirements (specific ammunition types, certain electronics, specialized chemicals). Acquisition documents reference MILSPECs by number — MIL-PRF-X or MIL-DTL-X under the modern numbering system.

The DoD-wide standard procedures and document codes governing the movement of cargo by surface, air, and water within the Defense Transportation System.

"The DoD-wide standard procedure for moving cargo."

MILSTAMP is the transportation counterpart to MILSTRIP — Transportation Control Numbers (TCNs), shipment status messages, in-transit visibility, the whole machinery that gets a pallet from the depot to the unit and back. When a Transportation Movement Request goes sideways, MILSTAMP is the rulebook the movement officer is reading from. Most service members never touch MILSTAMP directly; transportation Soldiers, Sailors, Marines, and Airmen live in it.

The DoD-wide standard procedures and document codes governing the format, content, and routing of requisitions, issues, cancellations, follow-ups, and related supply transactions across military and federal supply systems.

"The DoD-wide standard procedure for supply transactions."

MILSTRIP is the language every DoD supply transaction speaks underneath — the document identifier codes (A0_ requisitions, A5_ cancellations, AS_ shipment status), the routing identifier codes, the priority designators, the formatted 80-column legacy record layout. Service members rarely touch MILSTRIP directly anymore, but every transaction through GCSS-Army, NALCOMIS, and the rest ultimately renders down to a MILSTRIP record on the way to and from DLA.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a planning document that addresses the information management requirements supporting mobilization of Reserve Component forces — specifying the data, systems, and processes required to manage Reserve Component mobilization, deployment, employment, redeployment, and demobilization across the joint mobilization enterprise.

"The Mobilization Information Management Plan — the data and systems plan for RC mobilization."

MIMP is the planning instrument that addresses the information management side of Reserve Component mobilization — what data flows where, which systems of record (DRRS, RCMS, eMILPO, and the rest) authoritatively hold which fields, and how mobilization, deployment, and redemobilization information gets reconciled across the joint enterprise. For RC service members, MIMP shows up indirectly as the reason an orders error in one system propagates or fails to propagate to another; for RC unit administrators and the active-component RSCC staff that supports mobilization, MIMP is the architecture they live inside. Joint mobilization is hard for many reasons and information-system disconnects are consistently among them — MIMP is the document that tries to address that.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a military interdepartmental purchase request — the DD Form 448 funding instrument used to transfer funds from one DoD activity or federal agency to another to acquire goods or services on the requesting unit's behalf.

"The MIPR — the form units use to push funds to another DoD activity to buy what they need."

MIPR is the funding instrument every staff officer eventually learns to hate. When your unit needs another command — Corps of Engineers, a depot, another Service's contracting shop, or a federal agency — to buy something for you, the comptroller cuts a MIPR (DD Form 448) that transfers the dollars and obligates the receiving activity to deliver. In practice this is how engineering work, IT services, training contracts, and inter-Service support actually get paid for at the unit level. The pain points are familiar to anyone who has worked an S4 or S8 desk: MIPRs that get rejected for the wrong line of accounting, MIPRs that sit unfunded at fiscal year end, MIPRs that the receiving activity insists need to be "accepted" before they will start work. If your project is stuck, the answer is almost always "where is the MIPR".

The submarine engineering department division responsible for the mechanical engineering systems of the reactor plant and propulsion plant — staffed primarily by Machinist's Mates (Nuclear) (MMN) — owns the reactor coolant pumps, steam generators, main steam, turbines, reduction gear, condensers, main seawater, lube oil, and other mechanical systems — typically the largest engineering division by headcount.

"ML Division — mechanical engineering systems, the MMN home division."

ML is the mechanical division — typically the largest engineering division by headcount, owning the mechanical systems of the propulsion plant from the reactor coolant pumps through the steam generators through the turbines through the reduction gear through the condensers and back. The MMNs in ML stand the engine-room watches that aren't the RO or the EM watches — the throttle station, the engine room upper level watches, the engine room lower level watches, the roving watches that physically tour the plant. ML has the broadest mix of qualified watches, the most parts of the plant to know, and the broadest range of work — operator maintenance, scheduled maintenance, casualty response, system rounds. The ML chief runs what is often the most operationally consuming division on the engineering team.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a munitions list item — an item designated on the United States Munitions List (USML) under the International Traffic in Arms Regulations (ITAR) as a defense article subject to export control by the Department of State.

"A USML munitions list item — defense articles export-controlled under ITAR."

MLI is the export-control label that puts an item on the United States Munitions List under ITAR, which means State Department licensing controls its export, re-export, and even technical data sharing with foreign persons. For a working program office or contractor, MLI status is the difference between sending a brief over normal email and routing every page through a designated empowered official with an export license on file. It also touches everyday operations: a foreign exchange officer in your unit cannot necessarily see your ITAR-controlled tech data, even though they have a SECRET clearance and a US billet. The recurring frustration is that the line between MLI/USML and the Commerce Control List (CCL) under EAR shifts as items get reclassified — what was tightly controlled five years ago may be CCL today, and vice versa.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a military mail terminal — a Department of Defense facility that serves as the interface between the United States Postal Service and the Military Postal Service for the receipt, processing, and dispatch of military mail to and from overseas locations.

"The military mail terminal — the USPS-to-MPS handoff for overseas military mail."

MMT is the unglamorous but operationally significant node where bulk mail crosses from the US Postal Service into the Military Postal Service system that runs the APO/FPO/DPO addresses forward. The major MMTs at JFK, San Francisco, and Miami sort and dispatch the inbound and outbound military mail flow to overseas commands, ships, and contingency operations. For a deployed soldier or sailor, the MMT is the reason a package mailed in Ohio shows up six weeks later in Kuwait with a customs form taped to it. For the postal community, MMT operations are the link between US domestic logistics and the deployed MPS infrastructure, and the choke point where holiday mail surges have to be absorbed without breaking the system. The 1st Human Resources Sustainment Center and the postal augmentation companies are what makes the system run.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a written agreement between parties (departments, agencies, services, or organizations) that documents specific reciprocal obligations and responsibilities — generally more binding than a memorandum of understanding and used when the parties intend to formally commit to a defined arrangement.

"A memorandum of agreement — written interagency or interservice deal with reciprocal obligations."

MOA is the workhorse interagency and interservice agreement document — used when the Army and Navy need to formalize who pays for what on a shared range, when DoD and State Department need to spell out the Marine Security Guard relationship, when a combatant command and a service component need to nail down support arrangements. The MOA is generally treated as more binding than an MOU because it documents specific reciprocal obligations rather than a general understanding. The line between MOA and MOU varies by agency, and the staff officers who actually draft these things spend real time arguing about which document type applies. Either way, when an MOA exists, it is the citation that resolves "who owes whom what" when the question comes up.

The act of assembling and organizing national resources to support national objectives in time of war or other emergencies, including the bringing of Reserve Component members to active duty under statutory authority.

"The process of bringing reservists to active duty for contingency operations."

Mobilization runs under different statutory authorities depending on the urgency and scope: Full Mobilization (10 USC 12301(a), upon declaration of war), Partial Mobilization (10 USC 12302, up to one million for up to 24 months — used heavily post-9/11), Presidential Reserve Call-up (10 USC 12304, up to 200,000 for up to 365 days), and others. Each authority has its own caps, duration limits, and reporting requirements. The right authority for the right situation is a routine staff judgment with real consequences for the mobilized member.

A designated US Army installation responsible for receiving, processing, training, validating, and deploying Reserve Component units called to active duty, providing the personnel administration, medical screening, training certification, and force-projection infrastructure for mobilization throughput — with the principal mobilization stations including Fort Bliss, Fort Hood (Cavazos), Fort Carson, Fort Liberty, and others.

"An Army installation processing Reserve Component units from mobilization through deployment."

Mobilization stations are where Reserve Component units transition from RC status to deployable Title 10 force — receiving the unit, completing medical and dental screening, validating training and equipment, conducting pre-deployment training and validation, and pushing the unit forward to the theater. The processing flow can take weeks or months depending on unit type and theater. The mobilization station network is the institutional backbone of any Reserve mobilization at scale; demobilization runs the same flow in reverse at the end of the deployment.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a standardized report used to provide mobilization status information from Reserve Component units and supporting organizations — including unit readiness for mobilization, personnel and equipment status, training status, and projected timelines from mobilization order to deployment-ready posture.

"The mobilization report — Reserve Component unit status from alert to deployment-ready."

MOBREP is the periodic standardized reporting that Reserve Component units submit through their chains of command to track mobilization status — where the unit sits against its required strength, equipment fill, training certification, and projected timeline to be ready for the actual deployment. For a battalion or brigade S-3 in the Army Reserve or National Guard, MOBREP is one of the recurring requirements that consumes staff time during a mobilization cycle. The report feeds into the broader Force Generation and Sustainment models that the Joint Staff and the service component commands use to predict when reserve forces will actually be available. The 90-day, 120-day, and 365-day MOBREP cycles are part of how alerted reserve formations move through the mobilization process visible to higher headquarters.

Per the DoD Dictionary of Military and Associated Terms (November 2021), Ministry of Defense refers to the national civilian government department responsible for defense in most foreign nations (the US equivalent is the Department of Defense); modification refers to an authorized change to a contract, plan, or system configuration that alters its terms, scope, or technical specification.

"Ministry of Defense — most allied nations' equivalent of the DoD; or a contract modification."

MOD is one of those acronyms that covers two completely different domains. In security cooperation and partner-nation engagement, the MOD is the foreign nation's civilian defense ministry — the UK MOD, the Polish MOD, the Korean MOD, the partner-nation interlocutor that an attache or security cooperation officer engages on behalf of OSD Policy or a geographic COCOM. In acquisition and contracting, a MOD is a contract modification — the authorized change to terms, scope, period of performance, or technical specification of a contract or program of record. Both are everyday vocabulary; the context disambiguates. The DoD-to-MOD relationship is the diplomatic-defense interface; the contract MOD is the daily reality of program management.

The Marine Corps' Web-based personnel self-service portal, operated by Manpower and Reserve Affairs, providing active-duty and Reserve Marines with access to fitness reports, leave and earnings records, OMPF documents, professional military education tracking, and other administrative functions.

"The Marine Corps personnel self-service portal."

MOL (Marine Online — mol.tfs.usmc.mil) is the Marine equivalent of MyNavyHR or myFSS — the front end for the Marine's own personnel record. Where leave requests get routed, where the FITREP draft preview lives, where the OMPF documents can be reviewed (slug as `mol-marine` to disambiguate from other MOL meanings in DB). The CAC requirement and the older interface mean a lot of Marines use it only when they have to, but everything that flows to HQMC for promotion or assignment passes through MOL or its back-end at some point. Pay sits separately at DFAS; the seam between personnel and pay is the same one all services live with except (eventually) the Army on IPPS-A.

A code identifying the specific job a service member is trained and qualified to perform. The Army and Marine Corps use MOS; the Navy uses Rates and NECs; the Air Force uses AFSCs; the Space Force uses USSFs.

"Pick a job. Get trained for it. Build skills that translate to civilian work."

The MOS you sign for at MEPS is not always the MOS you end up with — needs of the service can reclassify you. The MOS you train in is not always what you do at your unit — you will be a shooter, mover, and floor-buffer first. Civilian translation depends on the MOS, the credentialing, and the documentation you walk away with.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a written agreement between parties that documents a mutual understanding of intentions, responsibilities, or general arrangements — generally less binding than a memorandum of agreement and used when the parties intend to express common intent without committing to specific reciprocal obligations.

"A memorandum of understanding — the looser cousin of the MOA, expresses common intent."

MOU is the looser interagency and international agreement document — used when two organizations want to document mutual intent without committing to the specific reciprocal obligations that an MOA carries. The Marine Security Guard relationship between DoD and State is governed by MOU-level instruments; international standardization arrangements often start at MOU and graduate to formal agreements; many joint base support relationships ride on MOUs. The practical difference between MOU and MOA varies by agency and is sometimes a matter of style rather than legal effect, but the working rule is "MOU expresses intent, MOA documents obligation." Either way, when a question of "who owes whom what" comes up, the existing MOU or MOA is the first document anyone pulls.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a postal facility operated by the Department of Defense to provide mail service to military personnel and authorized civilians at military installations and deployed locations — including Army-Air Force Post Office (APO) addresses, Fleet Post Office (FPO) addresses, and Diplomatic Post Office (DPO) addresses operated under the Military Postal Service Agency.

"A military post office — the APO/FPO/DPO facilities serving deployed and overseas personnel."

MPO is the doctrinal umbrella term for the actual postal facilities that run the APO, FPO, and DPO mail system for deployed and overseas military and authorized civilian personnel. An MPO at an overseas installation or a forward operating base is where a service member's family mail, online order shipments, and official correspondence actually get handled — sorting, distribution, customs processing for outbound, and the surprisingly complex logistics of moving mail through military channels. The MPO experience varies enormously: a mature APO at a permanent overseas base feels like a regular post office, while an MPO in a deployed environment is a tent, a connex, and a couple of postal clerks doing remarkable work with limited infrastructure. The mail still arriving is one of the small things that holds morale together.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the Department of Defense agency responsible for the management and operation of the Military Postal Service — including the APO, FPO, and DPO mail systems, postal operations at overseas installations and deployed locations, and the interfaces with the US Postal Service and host-nation postal authorities.

"The Military Postal Service Agency — runs APO/FPO/DPO and the broader military postal system."

MPSA is the joint agency that runs the entire military postal enterprise — the APO and FPO addresses that move family mail and packages to and from deployed and overseas service members, the DPO addresses that serve State Department and other diplomatic mission personnel, the interfaces with the US Postal Service that keep DoD mail flowing through the civilian postal system, and the policies that govern what can ship through the military mail system. The agency lives under the Defense Logistics Agency. For service members, MPSA is invisible most of the time — until it isn't, when a shipment is held up in customs or a deployed location loses postal service and morale takes the hit. The work is consequential precisely because mail to and from home is one of the few constants in deployment.

The first phase of the Department of Defense acquisition life cycle, following ICD validation, during which an Analysis of Alternatives is conducted, the preferred materiel solution is selected, and the program is prepared for Milestone A approval to enter the Technology Maturation and Risk Reduction phase.

"The first acquisition phase, between ICD validation and Milestone A."

MSA is the phase between the requirements sponsor validating the capability gap (ICD) and the program committing to a chosen materiel approach (Milestone A entering TMRR). The dominant analytic event is the AoA. The phase is meant to be relatively short and analytic, not production-committing, though programs sometimes find themselves stuck in MSA for years waiting on requirements clarity or technology readiness. The Materiel Development Decision (MDD) opens the phase.

A Department of Defense acquisition pathway, authorized at 10 USC 3201 (originally enacted as Section 804 of the FY 2016 NDAA) and governed by DoDI 5000.80, that provides for Rapid Prototyping and Rapid Fielding outside the traditional MDAP process, with a five-year nominal program length and streamlined documentation, intended for programs that can be fielded or prototyped within the period.

"A streamlined acquisition pathway for rapid prototyping or fielding within five years."

MTA is the most-used non-traditional pathway since its 2016 authorization — Section 804 of the FY16 NDAA, codified at 10 USC 3201, with implementing policy at DoDI 5000.80. Programs use it to escape the Milestone A/B/C overhead for prototyping or rapid fielding work that fits the five-year envelope. Critics note that the streamlined documentation can hide cost growth and that some MTA programs end up looking quite like MDAPs anyway; defenders point to genuinely faster fielding for the right kinds of programs. The pathway has expanded into a meaningful share of total DoD acquisition activity.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a board convened to evaluate and accept (or reject) military technical equipment, systems, or capabilities against established performance and acceptance criteria — typically at the conclusion of developmental or operational test events.

"The board that signs off when a new piece of military kit is technically acceptable."

MTAB is the formal acceptance gate between developmental testing and fielding — the body that reviews test reports, evaluates whether the system meets the contracted technical requirements, and either accepts the equipment, accepts it with conditions, or sends it back to the contractor. For a program manager this is one of the milestones that turns a prototype into a fielded system; for the operator it is invisible except that the kit shows up at the unit afterward with a tech manual that says "Accepted." When an MTAB rejects a delivery the resulting renegotiation can push fielding by months or years, which is why the boards quietly have outsized influence on what the force actually receives.