ABAD Acquisition Rules: Contracting Desk Guide

Evidence through: 2026-10-04; edition-specific limits are stated below. Audience: USAF contracting personnel supporting USAFE/EUCOM air-base defense.

Executive summary

The central acquisition question joins the applicable authority, requirement, funding, competition route, security restrictions, contract action and place of performance. A lawful procurement does not establish authority to transmit, fly, collect personal information or employ a counter-UAS effect. Those questions need their own applicable authorities. The 2024 edition of the DoD counter-UAS statute must also be read with its FY2026 NDAA amendment. 10 U.S.C. 130i, annual edition, P.L. 119-60, section 1707, German spectrum law.

Three findings should shape daily use of this collection. First, active DoD overhaul deviations can direct use of text different from the codified baseline. Second, Acquisition.gov labels its DAFFARS material as archived and points to the DAF Contracting Compass. Third, implementation instructions can expressly reach existing contracts, making transition review essential for options and modifications. DoD deviation register, archived DAF Part 5301 and Compass pointer.

This guide supplies a repeatable route through those questions. It contains no actual contract documents and makes no determination about any existing vehicle, order, product or vendor.

Research question

Which authorities and applicability distinctions should a USAF contracting officer supporting USAFE/EUCOM resolve when acquiring or administering sensors, effectors and C2? The analysis treats funding authority, contracting authority, technical approval and host-nation permission as distinct questions. The organizational chain helps identify responsible offices; a particular approval still requires the relevant written delegation.

Start with the action and the governing version

Open the searchable library, choose an action, and search by topic, equipment or citation. Each record separates the requirement, applicability conditions, suggested documentation, exceptions, source and version limits. A sourced record means its bounded statement has support; it does not establish that the statement applies to a particular action.

For a new award or order, first identify the current agency implementation of the relevant FAR part. For an existing-contract question, distinguish the law governing the contemplated action from the edition of a clause already incorporated and from an instruction expressly requiring a change. Read the signed deviation, its attachments and its transition language together. Do not substitute a model deviation page for the agency's adoption instrument. FAR overhaul FAQs, FAR 1.108 baseline conventions.

DAF-specific gap: the public DAFFARS pages are marked ARCHIVE with a 2026-03-18 label. Their historical legal-review thresholds and approval routes should not be presented as current Compass requirements. The official Compass link is retained in RULE-0095; its actual contents and the signed supersession instructions remain unresolved. The responsible command and contracting offices provide navigation context; approval authority requires a current written delegation. Official DAF archive.

Buying sensors, drones and C2

Radar and passive detection: assess the actual product architecture. An RF receiver, transmitting radar, camera, hosted analytics service and integrated counter-UAS detector do not present identical legal questions. The September 2026 defense security attachment specifically addresses certain foreign-made UAS detection/identification systems, in addition to UAS and specified components. Therefore, searching only for restrictions on purchasing drones can miss a relevant detector restriction. Start with RULE-0096 and its exact definitions and exceptions. DFARS 240.7008 attachment.

Cameras and video analytics: review equipment and service restrictions, personal-data processing, data transfers and hosting. The defense attachment also contains a restriction on transfers of covered individually identifiable DoD employee data. GDPR's own scope provisions and national law must be assessed against the actor and activity; neither “Europe” nor “military use” settles every privacy question. RULE-0098 source, GDPR Articles 2–3.

Drones and effectors: separately address acquisition-source restrictions, flight/test authorization and the authority for the intended effect. The American Security Drone Act baseline includes rules affecting extensions and renewals; defense-specific UAS restrictions are a separate research track. Do not treat an exemption for a qualifying research activity as an exemption for every DoD purchase. Baseline FAR 40.202, EO 14307, section 9.

Section 1707 of the FY2026 NDAA adds contractors to the persons the Secretary may authorize under 10 U.S.C. 130i, changes the Title 18 override and revises safeguards. This is not a direct authorization for every contractor or installation. Two related pilots also have different scopes: section 1088 expressly selects Air Force installations in the United States, while section 1089 uses its own covered-facility, determination and coordination conditions. Neither title alone establishes USAFE participation. P.L. 119-60, sections 1707, 1088 and 1089.

C2, software and integration: specify both the deliverables and the rights necessary to use, modify, maintain and compete support. The adopted 2026-O0036 text requires delivery schedules, acceptability provisions and identification of restrictions for covered noncommercial data/software. Commercial software generally follows its license; additional required rights must be negotiated and documented. Payment, delivery of code and license rights are distinct. Program pathway selection also remains separate from authority to use a particular contracting instrument. 2026-O0036, DFARS 227.7103-1/-3 and 227.7202-1/-3.

Spectrum review also reaches changes after award. DAFI 17-220's 2021 edition calls for early spectrum-supportability assessment and approval before changes outside assigned frequency-authorization parameters. Host-nation coordination is a separate part of that process. The cited edition supports this distinction; current theater supplements and later revisions still require confirmation. DAFI 17-220, paragraphs 2.2.9, 2.2.13 and 3.2.

For program testing, DoDI 5000.98 expressly supersedes the operational and live-fire T&E information in DoDI 5000.89. This subject-matter replacement should be reflected when selecting responsibilities and evidence. Program T&E and contractual inspection/acceptance remain separate analyses. DoDI 5000.98, purpose and section 1, FAR Part 46.

Conventional ammunition, warheads and SMCA review

SMCA concurrence is a procurement-planning gate. The adopted September 2, 2026 text requires the acquisition plan for covered conventional-ammunition procurement to be submitted for SMCA review and prohibits proceeding until written concurrence is provided. The review addresses retention of national technology and industrial-base capabilities; the requirement does not itself assign contract execution to a particular Service. The submission route is JPEO Armaments and Ammunition, ATTN SFAE-AA, at Picatinny Arsenal, with the published mailbox in PGI 207.103-70(d). SMCA resolves non-concurrence with the Army Office of the Executive Director for Conventional Ammunition. 2026-O0020 Revision 1, DFARS and PGI 207.103-70(d), PDF pp.3 and 10.

For acquisition planning, distinguish four decisions: whether the item is conventional ammunition; whether management is assigned to SMCA or retained by a Service; whether the procurement has written SMCA concurrence; and which organization may execute it. Paragraph (d) states no dollar threshold or Service-managed exception. Funding origin, a contracting warrant and access to an existing vehicle do not establish an exemption. For later orders, options or modifications acquiring ammunition, a practical control is to confirm that the contemplated item and scope are covered by the plan and concurrence. The reviewed provision does not establish a requirement to obtain fresh concurrence for every administrative modification. DFARS 207.103-70(d).

The FY2026 NDAA creates a specific version question for one-way armed/attack UAS. Section 817(a) updates the section 806(c) definition reference to include a successor directive or instruction. Section 817(b) orders review of DoDI 5160.68 within 180 days of enactment, assessment of whether to include one-way lethal or non-lethal armed/attack unmanned aerial vehicles and systems, and an instruction update if the Secretary determines it appropriate. The report is due December 31, 2026. This conditional review is not itself an automatic classification of every such system; passage of the review deadline does not establish the outcome. P.L. 119-60, section 817(a)-(c), 139 Stat. 953-954.

For an acquisition involving a guided effector and a separately purchased conventional warhead, analyze the actual end item and components separately, while preserving the complete procurement's scope. That is an analytical recommendation, not authority to divide a purchase to avoid SMCA review. Obtain the governing item-management and execution determination before concluding that the Air Force may execute the buy or that the complete effector falls outside any requirement. The exact current DoDI component/warhead categories, retained-item exclusions, transition rules, execution exceptions and any section 817 implementation remain unresolved. The adopted DFARS still references DoDD 5160.65, making instruction succession part of this determination. No named product is classified by this guide. DFARS 207.103-70(d); DoDI 5160.68, current instruction reference; P.L. 119-60, section 817.

Purchase cards: distinguish buying, ordering and paying

The April 14, 2026 release of the DoD GPC Guidebook revises section 5.5.1 and removes the UAS purchase prohibition from Appendix C. This change establishes a conditional route, not unrestricted card authority. Section 5.5.1(a) directs compliance with Service/Agency policy for Blue-listed UAS/components, or for non-listed Group 1–2 UAS/components used for testing and training with written O-6 commander/equivalent approval. The foreign-source restrictions in paragraphs (c) and (d) remain separate. The original Guidebook effective date of March 1, 2025 should not be assigned to every later amendment. GPC Guidebook, cover and section 5.5.1.

For a non-listed UAS/component, DPCAP's FAQs direct separate checks of SAM FASCSA orders and the Commerce Consolidated Screening List route to FASC covered foreign entities. They state that SPRS displays FASCSA orders but does not currently display the FASC entity list. A single supplier-risk screen therefore does not answer every drone-source question. The written testing/training approval also has a specific retention requirement: unclassified/non-CUI records go in the bank's electronic attachment system, while classified/CUI records require the approved alternative system. These are acquisition and recordkeeping requirements; they do not establish flight, spectrum, host-nation or mitigation permission. DPCAP FAQs 40–42, Guidebook section 5.5.1(b).

The transaction method matters for small C2, camera and integration purchases. Ordinary open-market micro-purchase authority does not cover a statement of work or agreement to terms beyond price and delivery. A software license, hosting agreement or integration requirement may require a suitable contract instrument and warranted authority. An authorized Contract Ordering Official can use the distinct existing-vehicle route within its stated limits. A Contract Payment Official has a payment role; the Guidebook requires full funding, prohibits progress finance payments and requires controls against duplicate obligations. A card payment does not replace the contract's award, ordering or funds-control requirements. Guidebook sections 4.6, 4.7.6, 4.7.8 and 5.4.

Administration continues after the purchase. Section 6.5 applies Component cyber and supply-chain controls to COTS IT regardless of the purchase method, expressly including cameras, software and network equipment. Section 6.9 requires proof of delivery and receipt documentation; its contract-payment provisions specify WAWF receiving reports and the CRCARD payment-office code. Apply the current adopted FAR/DFARS text alongside these Guidebook instructions, especially where the Guidebook retains older numbering. Guidebook sections 6.5 and 6.9–6.9.1.1.

Version differences remain material. GPC 2025-01 describes an older prohibition and exception-form scheme, while training item 3OP049 still says an implementing memorandum is being developed. Neither should displace the actual April 2026 Guidebook text. Complete predecessor rescission, current Component implementation and exact product clearance require their own evidence. Historical GPC 2025-01, DPCAP training item 3OP049.

Cybersecurity and existing requirements

Class Deviation 2026-O0025 Revision 3, issued September 3, 2026, directs revised FAR 40/DFARS 240/PGI 240 text. Its memorandum addresses CMMC self-assessments, suspension of the November 2026 Phase 2 transition, continuing NIST SP 800-171 Rev. 2 compliance, and changes to affected solicitations and existing contracts. Read the exact scope and timing before selecting baseline CMMC clauses or planning an option action. It does not mean all cybersecurity requirements disappear. Signed memorandum, pages 1–4.

Keep contractor information-system requirements distinct from government system authorization and technical acceptance. Current RMF issuance applicability remains unresolved in this analysis. The library therefore cannot establish an ATO or an approved system configuration.

Cloud services introduce specific acquisition and administration requirements. Under 2026-O0024, the relevant offering generally needs DISA provisional authorization at the appropriate level before award. The stated private, on-premises exception still requires authorization before operational use. Commercial terms need legal and mission review, and IT-service prescriptions include commercial acquisitions. For covered Government data outside DoD premises, overseas storage requires the authorizing-official route and written CO notification. An overseas place of performance does not itself authorize offshore hosting. 2026-O0024, DFARS 239.7602-1/-2, 239.7604 and PGI 239.7602-2.

After award, a contractor that originally represented it did not anticipate cloud use needs CO approval before introducing it; the PGI requires requiring-activity approval and verification of the offering's authorization. Data transfer formats, disposition confirmation, incident preservation and applicable subcontract duties also belong in administration and closeout planning. Assess the actual incorporated clause and any additional security requirements. 2026-O0024, 252.239-7010(b), (d)-(l), PGI 239.7603.

The older options attachment in 2026-O0027, effective February 1, 2026, contains CMMC certificate wording at DFARS 217.204-170. It must be read with the later security memorandum rather than treated as a self-contained current answer. The material question is which checks and changes remain required under the applicable transition instructions. Options attachment, page 8, later security memorandum, pages 2–3.

Funding: follow the appropriation, not just the sponsor

USAFE, EUCOM or another sponsor identifies a funding relationship; it does not alone establish legal availability. Identify the appropriation, fiscal year, purpose, period of availability and amount, then check any specific restrictions and applicable financial-management instructions. Purpose, documentary support and Antideficiency Act constraints are separate tests. 31 U.S.C. 1301, 31 U.S.C. 1501, 31 U.S.C. 1341.

For service periods crossing fiscal years, establish whether the service is severable and whether the statutory authority and implementing conditions apply. The September 2026 FMR Volume 3 bases severability on the terms and circumstances, potentially at line-item level. For interagency work, identify the actual authority; not every funding arrangement is an Economy Act order. 10 U.S.C. 3133, FMR Volume 3, section 8.5, 31 U.S.C. 1535.

The September 2026 FMR structure separates policy volumes, supplemental procedures and authoritative guidance. The directory identifies Volume 2 and 3 supplements as forthcoming and continues to direct users to superseding policy memoranda. Old chapter citations therefore need a version check. FPM23-02, for example, contains FY2023 language and an express endpoint tied to updating its corresponding chapter; its continued listing alone does not settle its force after the reorganization. FMR directory, FMR transition alert, FPM23-02.

Three funding distinctions are particularly relevant to integrated sensors and C2. FY2026 appropriations section 8039 permits covered O&M investment-item purchases up to $350,000; its $500,000 condition requires the specified Secretary determination for a named contingency operation overseas. The September 2026 IT policy separately treats a complete system costing $350,000 or more as procurement investment within its stated scope. These are a statutory permission and an implementing policy, so the exact boundary and scope matter. The IT system cost includes components that function together, including integration, engineering and software. Development, major upgrades, routine maintenance and annual software fees receive different treatment. P.L. 119-75, Division A section 8039, FMR Volume 2, sections 2.1.17-2.1.18.

For procurement, full funding generally concerns the complete usable end item, subject to the stated exceptions. Financial-statement capitalization thresholds answer a separate accounting question and should not be substituted for appropriation-selection policy. FMR Volume 2, sections 2.1.2.2 and 2.1.3, FPM26-04 capitalization memorandum.

For FY2027 CR-funded actions, Public Law 119-103 supplies a concrete starting point. Division A continues specified activities under referenced FY2026 conditions. Section 106 ends that authority at the earliest specified event, including December 11, 2026. Sections 102 and 104 restrict specified new starts and production changes; section 110 limits funding action to continuation purposes. Check named anomalies, subsequent enactments and the actual account, apportionment and allotment. An existing vehicle does not itself avoid these restrictions, and a newly awarded contract is not automatically a prohibited new start. P.L. 119-103, Division A, sections 101–110 and 126–128.

The CR incorporates the FY2026 defense appropriations act, whose account headings and section 8003 distinguish availability periods. Separately, Class Deviation 2026-O0044 expressly concerns FY2026 excepted activities in advance of funds. Continued listing in a deviation register does not expand that instrument to FY2027. P.L. 119-75, Division A, 2026-O0044.

For direct-cite orders, FPM25-05 requires PRDS transmission by July 31, 2026 and discontinues DD448/448-2 for that route. It preserves the IAA requirement and separately routes reimbursable funding, including relevant administrative fees, through G-Invoicing/FIDS. These procedures do not create funding authority. Economy Act orders must also satisfy their statutory conditions and cannot extend fund availability; unused balances require the specified reconciliation and deobligation. FPM25-05, FMR Volume 11, sections 4.1-4.8.4.2.

The general fiscal-law records still identify the 2024 annual U.S. Code edition. Full statutory consolidation, account-specific riders, current DAF technical procedures and parts of the FMR transition remain limitations. No finding here establishes available funds for an individual obligation.

Pricing data, TINA Lite and continuing reporting duties

The October 1, 2026 supplier-transparency policy preserves the pricing-data hierarchy. Start with competition, market, sales and other available information; establish why additional data is needed. Its actual-cost direction excludes COTS items and retains the statutory limits for commercial products and services. Where certified data is not required and available evidence cannot establish a fair and reasonable price, request sufficient data other than certified cost or pricing data. The memorandum references FAR 52.215-21 for modifications in contracts containing that clause; it does not insert that clause into every existing contract. DPCAP transparency memorandum, pp.1-2.

Requests should generally use records in the form the contractor already maintains. Asking for data does not itself create CAS coverage, require a cost-reimbursement contract, or establish new records-access rights. Refusal to provide statutorily required certified data triggers immediate DCAA coordination under the memorandum; other denials must follow the applicable PGI process. For an existing contract with delinquent CSDR deliverables, issue the directed demand for submission within 30 days. Withholding depends on an applicable contract term. This is an administration requirement for delinquent required reports, not a new reporting requirement for every sensor or C2 purchase. DPCAP transparency memorandum, pp.1-2.

The policy separates current directions from future implementation. Automated ERP/API participation, if pursued, must be voluntary and cannot become an award condition, evaluation factor or responsibility consideration. Sector-specific profit benchmarks inform objectives without becoming caps; new clauses, formats and revised DFARS profit policy require formal rulemaking. The September 14 attachment also imposes a conditional written USW(A&S) acquisition-strategy approval before issuing a solicitation expected to bring a business unit newly under full CAS coverage, pending the specified Board action. That approval does not determine CAS applicability, grant a waiver or permit omission of required clauses. Later CASB action and implementing issuances must be checked. DPCAP transparency memorandum, pp.2-3; September 14 attachment, combined PDF pp.7 and 9.

For recurring large purchases, the July 22, 2026 standing TINA Lite program uses tailored certified data; it does not waive certification. First determine whether a certified-data exception applies. Otherwise, qualifying actions must exceed $50 million and meet the recurring-requirement and reliable-actual-cost conditions. HCA approval cannot be delegated. The current version 1.1 guide distinguishes this program from the July 8 planning preview and the former pilot, including its historical critical-munitions approval. An existing contract or vehicle ceiling alone does not establish eligibility. 2026-O0048 Revision 1, DFARS 215.403-72, TINA Lite Guide v1.1, pp.5-13%208.10.2026.pdf).

An approved TINA Lite action needs a defined data request, treatment of new work and subcontractors, and the prescribed provision or modification clause. DFARS 252.215-7988 and 252.215-7989 require specified historical data and a tailored certificate; additional required data needs the stated solicitation or modification-RFP amendment. Certification follows price agreement and precedes award, subject to the unpriced-action exception. Historical actuals still require analysis of changed scope, non-recurring costs, quantity effects and estimates to complete. These pricing procedures do not supply scope or funding authority. 2026-O0048 Revision 1, DFARS 215.110-70(i)-(j), 252.215-7988(c)-(e), 252.215-7989(b)-(d) and PGI 215.403-72(b).

Standing-program notification is due to DPCAP within 10 days of contract award with the information specified by PGI 215.403-72(b)(3). Existing pilot participants retain their separate reports at three months after action award and completion of performance. Closure to new pilot entry therefore does not cancel continuing reporting duties. 2026-O0048 Revision 1, PGI 215.403-72(b)(3)-(c), TINA Lite Guide v1.1, p.6 and footnote 1%208.10.2026.pdf).

Orders, changes, options and administration

Funding review continues through changes and closeout. FMR Volume 3 links scope changes to new-obligation analysis, distinguishes expired accounts from closed accounts, and specifies approval/notification rules for certain adjustments. Its expired-fund replacement route requires a continuing need, qualifying termination circumstances, the same size/scope and timely action. A remaining balance or convenience termination alone does not establish that route. FMR Volume 3, sections 8.6 and 9.1-9.8.

COR oversight from award through closeout

The August 5, 2026 Part 201 deviation makes COR planning an award and administration responsibility. Adopted PGI 201.404-70(e)(1) requires designation within three business days of award for all service contracts, including firm-fixed-price contracts, and supply contracts with cost-reimbursable line items, including awards by another federal agency on behalf of DoD. The stated service-contract exemption requires all three conditions: simplified acquisition procedures, a noncomplex requirement, and a written CO explanation of why a COR is unnecessary. Tailor surveillance to value and complexity; geographically dispersed contracts with multiple task orders may warrant multiple or alternate CORs with distinct duties. The text does not say an option or modification restarts the designation clock. 2026-O0002 Revision 1, PDF pp.22-23.

A COR must be an eligible military or civilian government or partner employee; contractor personnel cannot serve as CORs. DFARS 201.404-71 prescribes clause 252.201-7000 when appointment is anticipated, including commercial solicitations and contracts. The written designation tells the contractor what the COR can do; it does not permit the COR to change price, quality, quantity, delivery or other terms. For an existing contract, establish the incorporated clause and delegation before treating technical direction as authorized. 2026-O0002 Revision 1, DFARS 201.404-70/71 and 252.201-7000, PDF pp.9-10.

The adopted PGI identifies DoDI 5000.72 as the certification-policy source and says its standards should inform requirements development, solicitation and surveillance. It separately identifies the COR Guidebook as guidance. Detailed instruction and Component qualification, training and waiver requirements require their own applicability assessment; the PGI cross-reference does not establish a particular qualification or local appointment authority. 2026-O0002 Revision 1, PGI 201.404-70(b)-(c), PDF p.22.

Components must use PIEE's Joint Appointment Module for COR nominations, appointments, terminations and training certifications, and Surveillance and Performance Monitoring for other surveillance actions. Maintain the written designation in JAM or SPM and an SPM surveillance file for each assigned contract, including duties and actions under the delegation. For supply contracts with cost-reimbursement line items, allocate retained, COR and DCMA surveillance activities without delegating the same activity to both COR and DCMA. Before closeout, the COR must ensure the surveillance file is complete and available to the CO. 2026-O0002 Revision 1, PGI 201.404-70(d)-(f), (i), PDF pp.22-23.

Calendar CO review of COR files within six months of contract award and annually thereafter, with results recorded in SPM. Risk, complexity and value can justify more frequent later reviews. Within 30 days after a review, provide the required supervisory performance feedback and discuss inadequacies with the COR. Reconcile older timetables with this adopted text before applying them to a continuing contract. 2026-O0002 Revision 1, PGI 201.404-70(g)-(h), PDF p.23.

COR financial disclosure and continuing ethics training

Financial-disclosure coverage depends on an employee's duties and the applicable agency determination. For covered U.S. employees, significant procurement judgment exercised personally and substantially without substantial supervision/review is one route to confidential filing; the regulation also permits conflict-based designation. An exclusion requires the agency head's or designee's determination, and an alternative reporting procedure requires prior written OGE approval. These decisions belong in the staffing analysis for both new acquisitions and continuing contract oversight. 5 CFR 2634.904(a)(1), (b) and 2634.905. The signed 2015 DoD instruction-announcement memo likewise explains that COR status does not necessarily make every COR an OGE Form 450 filer, and directs questions to ethics counsel. Its historical explanation must be read with the current regulations and current department implementation. DPAP memorandum, March 30, 2015, p.1.

Filing dates follow the covered position and service, rather than the contract's funding source or option anniversary. The general new-entrant deadline is 30 days after assuming the position, with agency authority to require earlier filing. Covered incumbents serving more than 60 days during the calendar year generally file by February 15 of the next year. Transfer, prior-filing, short-service, departure and SGE provisions require separate attention. Good-cause extensions require the authorized reviewing official; the special emergency-service extension cannot be inferred from a permanent overseas assignment. Confidential filers do not submit a termination report merely because they leave the filing position. 5 CFR 2634.903(a)-(b), (d)-(e).

Confidential reports and their contents must remain nonpublic except under the specified legal release provisions. As an acquisition-management practice, use the authorized ethics process to establish required compliance status while keeping financial contents out of public references and general surveillance products. 5 CFR 2634.901(d).

Annual ethics training is a separate continuing obligation for employees covered by 5 CFR 2638.307, including required annual confidential filers and the referenced contracting officers, unless governed by the separate public-filer provisions. Training must be completed before calendar-year end; the agency provides one hour of duty time for interactive training and written materials. The required topics and completion records, and the DAEO's narrow format exceptions, must be addressed. A COR certification or waiver does not, by itself, establish compliance with this separate rule. 5 CFR 2638.307(a)-(f).

These findings do not establish an individual filing determination, an appointment, a local delegation or the complete DoDI/DAF COR training and waiver scheme. The full current COR certification instruction and Component implementation remain necessary to resolve those additional requirements.

Consumption-based services and enterprise software

The Anything-as-a-Service pilot can support a technology capability delivered through software, equipment, data and services, but its defining conditions are metered actual usage at fixed-price units and measurable outcomes. Agreements must require comparison of cost and delivery speed with non-XaaS processes at customary intervals. For an ABAD acquisition, the practical starting point is a defined consumption measure and outcome requirement, followed by DPCAP/Contract Policy approval. A software subscription or existing C2 contract does not qualify merely by being called a service. The initial PSC categories cover SaaS, DaaS and narrowly defined temporary, non-exclusive commercial coworking; additional PSCs require consideration by the pilot officials. P.L.118-31, section 809(a)-(b), (g); DPCAP Revision 1 memorandum, pp.1-2; PSC attachment, Revision 1.

Pilot scheduling requires distinct approval, notice and award decisions. The memo permits posting after approval, requires at least 60 days for proposals, and requires a justification for each pilot contract posted 60 days before award. The statute calls for agreement within 100 days of the participation notice to the extent practicable; the memo refers to synopsizing or posting the justification. These are qualified scheduling rules, not automatic approval or a compressed award entitlement. The memo's older FAR references and its initial-contract justification instruction must be reconciled with current adopted procedures and the statute, whose express competition exemption concerns qualifying modifications. Section 809(c)-(e); Revision 1 memorandum, p.2.

Certified cost or pricing-data relief does not remove price-reasonableness analysis. The memo identifies possible individual deviations under agency procedures and expressly limits that deviation to new awards, excluding modifications. A later modification therefore requires a separate pricing analysis and resolution of the statutory and implementing-policy relationship. The competition exemption is also narrow: it concerns a modification adding new features or capabilities to a pilot agreement in an amount no greater than 25 percent of its total value. The reviewed text does not define an original-award baseline or a cumulative calculation. Those questions require resolution before reliance; no recurring 25-percent allowance or general conversion of existing contracts is established. Section 809(e); Revision 1 memorandum, pp.1-2.

Commercial software sourcing remains an independent decision. The pilot attachment retains ESI procedures, and the adopted March 2026 DFARS/PGI text requires checking DoD inventory first. Available inventory must satisfy the requirement; where an ESA is available, the buyer reviews its terms, conditions and prices under applicable source-selection rules and uses it when it provides best value. ESI does not choose the required product. These requirements also reach applicable service and interagency purchases and, where practicable, system upgrades. 2026-O0049, DFARS 208.7400-.7403 and PGI 208.7403(1)-(4), PDF pp.11-12 and 33; XaaS PSC attachment.

When an ESA does not provide best value, the software product manager must first receive the specific concerns and an opportunity to offer the same or better value. Within three working days the SPM must update the ESA, give an estimated update date or state that no change will be made. The prescribed no-change, nonresponse and no-adjustment-within-90-days conditions permit other means; a separate waiver route belongs to the designated department/agency management official after the specified steps. An unavailable website does not establish an absent agreement, an SPM nonresponse or a waiver. For a renewal, order or modification, existing instrument scope, funding, license, cyber and approval requirements still need action-specific assessment. 2026-O0049, PGI 208.7403(5), PDF p.33.

The XaaS statute is established here from the enacted text and corroborated by a compilation amended through December 18, 2025. Post-compilation amendments require confirmation before action; proposed later legislation is not applied. Current DAF ESI waiver designations and individual ESA availability are not established. The adopted deviation also contains an unresolved contractor-use clause-number conflict between 208.105-2(c) and its included clause heading; those provisions are not converted into an instruction to insert a particular clause. Section 809; 2026-O0049, PDF pp.3 and 14.

Engineering plans, system changes and open interfaces

Engineering planning depends on the acquisition program and category. DoDI 5000.88 requires an SEP for MDAP and ACAT II/III programs unless the applicable authority waives it; other programs are recommended to use one as a best practice. For covered major program phases, approval precedes RFP release and the plan is included in the RFP. The buying office should establish the program category and approval route before treating this as a solicitation gate. The November 2020 instruction identifies different authorities for ACAT ID, IB/IC and other programs; organizational affiliation alone does not establish a delegation. DoDI 5000.88, paragraphs 1.2(b) and 3.4(a)(1)-(2), pp.4 and 11-12.

For an integrated ABAD system, engineering planning connects required interfaces, technical data, deliverable formats, reporting intervals and review entry/exit criteria. The SEP also addresses the IP/data-rights plan and interprogram dependencies. The acquisition package must translate applicable needs into enforceable contract terms, with separate analysis of data delivery and license rights. An engineering plan does not itself create an unlimited license or change a contractor's obligations. DoDI 5000.88, paragraph 3.4(a)(3)(b),(h),(j)-(m),(r)-(s), pp.12-14.

Postaward engineering control requires an identified baseline and traceable changes. The instruction places initial product-baseline Class I change control with the PM at completion of system-level critical design review, with Class I defined by the program configuration-management plan. Configuration management addresses cost, schedule, functional, physical and performance effects and maintains an audit trail. Technical approval must be coordinated with the CO's independent scope, pricing, funding and modification decisions. The integrated plan and schedule must also account for reviews, contracted tasks and dependencies; a government program office acting as systems integrator retains the stated system-level responsibility. DoDI 5000.88, paragraphs 3.4(b)-(d), pp.14-15.

The December 17, 2024 tri-Service memorandum directs commitment to the five MOSA pillars: modular design, designated interfaces, consensus open standards, an enabling environment and conformance certification. Guidance must establish appropriate verification methods and timing. The SAE must ensure MOSA is implemented to the extent practical and review compliance with MDAPs at systems-engineering technical, gate and program reviews. The named interface standards are examples rather than a universal shopping list. For a sensor or C2 increment, the practical acquisition question is which interfaces, evidence and rights are needed to implement the applicable approach. The memo's historical 60-/120-day SAE tasks do not demonstrate that current DAF implementation guidance was issued. Tri-Service MOSA memorandum, pp.1-2.

The September 2026 Systems Engineering Guidebook recommends engineering participation in statements of work/objectives, performance work statements, CDRLs and incentive design. Objective review criteria matter because incentives tied to technical-review completion can encourage premature closure. These are recommendations in a flexible reference guide, not a mandatory checklist or independent contract authority. Its subcontract-delegation recommendation does not remove applicable consent requirements. Systems Engineering Guidebook, preface p.viii and section 4.6 p.49.

Implementation limits remain action prerequisites. DoDI 5000.88 paragraph 3.4(a)(2)(b) uses the wording “at least 120 days after contract award or 30 days before the next technical review, whichever comes first” for the substantive-change SEP update; the approving/policy authority should clarify that wording before it is turned into a calendar deadline. Current Service guidance, waiver/delegation evidence and the current statutory MOSA provisions need separate confirmation. The full DoDI 8330.01 requirements remain pending, so engineering-plan or MOSA compliance must not be treated as interoperability certification. DoDI 5000.88, paragraph 3.4(a)(2)(b), p.12; tri-Service memorandum.

Cyber testing in contracts and lifecycle administration

The February 25, 2026 cyber developmental test-and-evaluation manual makes cyber evidence a lifecycle acquisition responsibility. It reaches multiple acquisition pathways and sustainment or postproduction systems when specified changes occur, including software releases, architecture or baseline changes, component replacement and changes in interfaces or supply chains. For an ABAD upgrade, the program and cyber test team should establish the applicable evidence and resources before the CO determines how any additional work fits the instrument. The manual is not an automatic amendment to an existing contract. DoWM 5000.103, paragraphs 3.1(a), 3.2(a)(13)-(14), pp.8 and 11; FAR Part 43.

The program lead identifies the cyber lead and charters the cyber working group at the stated initiation and precontract/RFP points. That group works with the CO to place test requirements in CDRLs, data item descriptions and terms aligned with the FAR, DFARS or other applicable agreements. Relevant subjects include contractor qualifications, government observation and access, support, remediation, supply-chain data, design information, test plans/results and evidence of corrective action. The express qualifier on source-code delivery or reverse-engineering rights is “if applicable”; a policy need does not itself create a license or facility-access right. DoWM 5000.103, paragraphs 3.5(a)(2),(6),(8)-(10), 3.5(b)(10), 4.2(b), pp.15-17 and 25-26.

Government acceptance cyber testing informs acceptance decisions for delivered systems and intermediate software releases or increments. It validates specified cyber performance and in-scope security controls, includes the appropriate contractor/government participants and supply-chain risk office, and informs the program lead's action on remediation recommendations. Contractual acceptance, correction, retesting and payment consequences still depend on the governing terms and authorized officials. This testing is neither a receipt stamp nor an ATO. DoWM 5000.103, paragraphs 3.2(b), 3.5(a)(7), 4.2(b)(1)(k), pp.12, 16 and 26; FAR Part 46.

RMF and cyber DT&E complement each other. RMF does not replace the manual's procedures, and current test results must reach the authorizing official for every ATO decision. Paragraph 3.3(d) has a specific closed-loop test-range provision concerning IATT, ATO, certification attestations and certified/accredited cyber red teams. It does not establish a general authorization exemption for a connected or fielded system. Actual environment eligibility and the cited DoDI 8510.01/8585.01 implementation remain separate determinations. DoWM 5000.103, paragraphs 2.7(f), 3.3(a)-(f), pp.7 and 14.

Commercial IT services have their own Plan, Develop and Execute sequence in section 5.7 and Table 10. Cyber test requirements belong in each RFP and contract during Develop and receive required updates during Execute. Resources, test infrastructure, reporting and sustainment planning also have stage-specific entries. The table distinguishes required activities, required updates and recommended/program-specific activities; for example, the Execute-stage MBCRA entry is not a universal mandatory mark. These service-pathway provisions should be assessed independently of XaaS pilot eligibility or cloud approval. DoWM 5000.103, section 5.7(a) and Table 10, pp.50-51.

During administration, track required reports, deficiencies, remediation evidence and contractor data deliveries. Program leads and test teams preserve evidence for authorized users and decision authorities, with appropriate handling and records management. Contract transition or closeout planning should reconcile deliverables and government custody without inventing a retention period or report deadline absent the governing implementation and contract. Current DAF approval, qualification and reporting details, full mission-critical supply-chain rules and remaining RMF requirements are not established by these selected provisions. DoWM 5000.103, paragraphs 2.7(e)(3), 3.5(a)(15)-(19), 4.6(a)-(e), pp.7, 16-17 and 31.

Frequency-authorization duties in the contract

The frequency-authorization clause assigns specific performance duties in addition to the program's broader spectrum responsibilities. Both Basic and Alternate I of DFARS 252.235-7003 require the contractor to obtain the radio-frequency authorizations needed to support the contract. When appropriate allocation has not been made, paragraph (b) requires technical operating characteristics for the proposed radiating device during the initial planning, experimental or developmental phase of performance. This is not a universal preaward deadline, and delivering an application or technical data does not itself provide permission to transmit. 2026-O0014, Attachment A1, 252.235-7003(a)–(b), printed pp.10–11/PDF pp.12–13.

Basic places responsibility on the CO to furnish authorization procedures; Alternate I instead specifies contractor use of DD Form 1494. Adopted DFARS 235.176(c)(1)–(2) ties that selection to agency procedures. Paragraph (c) lists development, production, construction, testing and operation of a device requiring authorization. The section's introductory line refers to indemnification, creating a drafting conflict with the separate frequency prescription. Policy clarification is needed for a disputed inclusion or omission; the text supports neither silently repairing that introduction nor inventing an indemnification-based spectrum exemption. 2026-O0014, Attachment A1, 235.176 introduction and (c), printed p.3/PDF p.5; 252.235-7003(c), printed pp.10–11/PDF pp.12–13.

Both variants require the full clause, including its flow-down paragraph, in all subcontracts meeting the device/activity condition. For an existing sensor or C2 contract, a new radio link or changed subcontract task should therefore trigger review of the governing terms, technical data, applicable authorizations and flow-downs. Contract changes, acceptance and payment remain subject to their own terms and authorities; this clause does not create new government rights to direct subcontractors or new withholding remedies. 2026-O0014, Attachment A1, 252.235-7003(d), printed pp.10–11/PDF pp.12–13; FAR Part43.

The December 18, 2025 deviation took effect February 1, 2026 and directs use of its attached DFARS/PGI in place of codified text. Its frequency prescription is 235.176(c), while the codified clause page still cites 235.072(b). Current complete spectrum and electromagnetic-environmental-effects instructions, applicable DAF/theater submission procedures and host-nation permissions remain separate requirements to establish. The selected clause provisions do not determine equipment certification, compatibility, safe employment or a local approval delegation. 2026-O0014, memorandum pp.1–2 and selected attachment provisions.

Privacy terms for camera and C2 services

Privacy review begins with the planned data and work. A system of records involves agency-controlled records retrieved by a person's name or assigned identifying particular; the definition of a record can include a photograph, fingerprint or voiceprint. A camera purchase alone does not determine that status. For covered design, development or operation work serving an agency function, the CO identifies the specific system and work in the contract statement, provides agency implementing rules, and includes FAR 52.224-1 and 52.224-2. DoD adopted this Part 24 text effective February 1, 2026, and DFARS 224.103(b)(2) identifies the departmental privacy instruments to provide. RFO FAR 24.101–24.104; 2026-O0009, memorandum pp.1–2 and Attachment A1, PDF p.3.

The Privacy Act clause carries separate subcontract duties. Paragraph (a)(2) requires the notification in qualifying subcontract solicitations and awards, including awards without solicitation; it uses the words redesign, development or operation. Paragraph (a)(3) requires the full clause, including the flow-down paragraph, for qualifying design, development or operation work. Preserve those conditions when reviewing changed analytics, hosting or support tasks. The clause's treatment of contractors for Privacy Act purposes does not create government employment for every purpose or direct government privity with a subcontractor. FAR 52.224-2(a)–(c).

Privacy training uses a broader, separate trigger. Contractor employees handling personally identifiable information on the agency's behalf can trigger FAR 52.224-3 even when the work does not establish a covered system of records. Covered employees need initial training and annual training thereafter. Basic requires role-based training, foundational and advanced content, knowledge testing and the stated minimum subjects; agency-developed or agency-conducted training satisfies those content elements. When the agency accepts only its own training, Alternate I replaces paragraph (c) with agency-provided initial and annual training for the contract duration. RFO FAR 24.302; FAR 52.224-3(a)–(c), Alternate I.

During performance, the contractor must prevent covered access or handling until the required training is complete, retain completion documentation, and provide it to the CO on request. The substance of the training clause, including its flow-down paragraph, belongs in subcontracts meeting the listed employee-activity conditions. These duties remain under Alternate I. They support review when personnel, data uses or subcontract tasks change, but establish neither a fixed retention period nor a new payment or closeout condition. FAR 52.224-3(b), (d)–(f), Alternate I.

Contract terms and training do not themselves authorize imagery collection, processing or disclosure. Establish applicable privacy-impact assessment, system notice, records-retention, breach-response and host-nation requirements with the responsible privacy officials. Part 24's definition of an individual does not settle every PII or overseas privacy question; the system-of-records clauses, training trigger and national legal regimes have distinct scopes. RFO FAR 24.101–24.104 and 24.302; FAR 52.224-3(c)(1)(iii)–(vi); Regulation (EU) 2016/679, Articles 2–3.

First-article testing, production risk and approval

First-article testing is a decision about demonstrating that a contractor can supply a conforming product. It is relevant to follow-on procurement when specifications or processes change, production has stopped for an extended period, or an earlier product developed problems. Before requiring it, weigh delivery and cost effects, the risk of foregoing it and less costly quality methods. Normally excluded categories include R&D, preaward-qualified products, products normally sold commercially and products with complete detailed specifications, subject to the stated novel-or-exacting qualification for the last category. These provisions do not cancel other testing or acceptance duties. DoD adopted the revised Part 9 effective February 17, 2026. 2026-O0042, pp.1–2; RFO FAR 9.301–9.304.

A first-article solicitation must make the approval criteria and testing requirements explicit; contractor testing also needs specified report data. Address the article's relation to production quantity, schedule, manufacturing-standard status and the applicable evaluation conditions. A waiver may be requested for identical or similar supplies previously furnished by the offeror and accepted by the Government; it is discretionary. Provide the eligible alternative-offer route and supporting contract-number information. Where earlier delivery follows a waiver and the Government requires it, that schedule difference cannot become an award evaluation factor. The separate rule against materially unbalanced first-article/test pricing remains relevant; its displayed Part 15 cross-reference must be reconciled with current adopted pricing text for the action. RFO FAR 9.306(a)–(j); RFO 52.209-3(h) and 52.209-4(i).

Select the contractor-testing clause, 52.209-3, or government-testing clause, 52.209-4, as prescribed; cost-reimbursement forms are substantially similar adaptations. Fill the quantities, notice periods, facility/address and response deadlines rather than assuming a standard number of days. The administration office coordinates the forthcoming article or report with the laboratory, which recommends the decision. The CO issues written approval, conditional approval or disapproval and provides the administration office a copy. Approval accepts the test results; specifications and the rest of the contract still apply. An approved article counts toward the delivery quantity only under the clause's acceptance, nonconsumption and contract conditions. RFO FAR 9.301, 9.307–9.308; RFO 52.209-3(a)–(b), (e) and 52.209-4(a)–(b), (e).

Allow time after approval to obtain materials and produce the balance. Under the Basic clauses, early acquisition or production of that balance is at the contractor's sole risk, with costs excluded from the specified progress-payment and convenience-termination calculations. The prescribed Alternate II permits limited written CO authorization for identified early work needed for the delivery schedule. Until approval, first-article and authorized costs are the allocable costs for those two purposes; this does not establish an automatic payment right. Deviations revealed in testing still require correction or replacement under the alternate without changing contract price. Alternate I separately requires production and the first article at the same facility when prescribed. RFO FAR 9.305 and 9.308; RFO 52.209-3(g), 52.209-4(h) and their Alternates I–II.

Track both contractor delivery/report deadlines and government decision deadlines. The clauses provide for requested repeat tests after disapproval, the stated contractor cost responsibility and government adjustment rights. They link late delivery or disapproval to the contract's Default-clause delivery language; they do not themselves terminate the contract. A missed government decision deadline can require a Changes-clause equitable adjustment upon a timely written contractor request. For government testing, also administer operating and maintenance instructions, spare-parts support, repair and the stated removal/disposal responsibilities. Changes in drawings, designs or specifications remain contract changes. RFO 52.209-3(c)–(f) and 52.209-4(c)–(g); RFO FAR 9.307(b).

For an existing contract or proposed order, use these requirements to examine the incorporated terms, clause variants, technical baseline and permitted change route. A new policy text does not alone amend the instrument. First-article approval, production acceptance, program T&E and operational authorization remain separate decisions. Current DAF/command procedures, including the unresolved AFMCI 23-110 requirements, must also be established for the action; the user's contracting chain or funding source supplies no exception. RFO FAR 9.301, 9.307–9.308; RFO FAR Part 43.

Laser procurement and exemption controls

A laser sold as military exempt requires more than a marketing label. Identify the applicable product standard, intended use and governing written exemption before relying on a departure from radiation-safety requirements. The general government-use exemption process and the standing DoD military-laser exemption are different routes. Under 21 CFR 1010.5, the FDA CDRH Director may grant a performance-standard exemption on application when the stated criteria are met; government funding or ownership does not itself grant one. The regulation recommends early consultation when procurement specifications need to conflict with a standard and retention of requirements compatible with the special use. 21 CFR 1010.5(a)–(c), (e)(1).

FDA's July 12, 2002 Laser Notice 52 explains the standing DoD route: the manufacturer obtains a product-specific letter from an authorized DoD procuring agency before sale and retains it for subsequent DoD sales. The letter may limit quantity, Service or time. Appropriate DoD laser safety representatives evaluate the product's compliance. The standing exemption addresses exclusive DoD use for the stated combat, combat-training or classified purposes; the broader purposes eligible for an application under 1010.5 do not automatically expand it. Notice 52 is expressly nonbinding guidance describing the exemption; the regulations and actual written conditions remain controlling. Its historical contact list does not establish a current DAF delegation. FDA Laser Notice 52, disclaimer, Background and Guidance; FDA exemption approval letter.

Existing-contract management needs a separate check when the product, intended use or radiation-control procedures change. Section 1010.5(d) requires the applicant to request an amendment in advance when a change makes the original radiation-safety information incorrect, and to request an extension, if needed, at least 60 days before the FDA exemption expires. Notice 52 separately explains that subsequent manufacturer modifications to a military-exempt laser require a new DoD letter. Neither a contract modification nor an option exercise substitutes for either document. FDA may amend or withdraw its grant on the written notice's effective date, or immediately to prevent an imminent health hazard. 21 CFR 1010.5(d)–(e); Laser Notice 52, Guidance.

Translate the applicable exemption conditions into specifications and delivery evidence with safety and quality officials. The regulation requires permanent, legible and accessible identification unless the exemption prescribes another manner. The DoD grant retains practicable radiation-safety provisions, adequate alternative controls and identification conditions. Use the actual grant's terms; a manufacturer cannot infer permission to omit identification or controls. Delivery documentation supports contractual verification, while acceptance and operational safety approval remain separate decisions. 21 CFR 1010.5(b), (e)(1), (f); FDA approval letter, specification and identification conditions.

Plan the records and disposition route before closeout or transfer. The original grant calls for permanent records of exempt-product status and ultimate disposition, and advance FDA authorization for excess/surplus disposal. The March 18, 1986 amendment removes the exemption-specific annual report effective September 1, 1985, while retaining the underlying information for verification. That relief does not remove all reporting duties; the grant expressly preserves 1002.20. Notice 52 explains that an exempt system cannot be sold, surplused or distributed outside DoD without full FDA-standard compliance, certification and reporting. Apply that guidance together with the actual exemption, property rules and any required FDA authorization. These are exempt-product records, not a newly prescribed retention period for every contract file. FDA original grant; FDA March 18, 1986 amendment; Laser Notice 52, final Guidance paragraph.

Current full DoD/DAF laser safety procedures, authorized issuing offices, the detailed product standards and host-nation requirements remain necessary for an action. The general regulation and FDA guidance do not establish a system's operating authorization, a local exemption delegation or export permission. Determine the territorial and transaction scope for overseas acquisitions rather than assuming either universal application or a blanket exemption. The historical FDA grant's letter date and issuance reference differ; use the exemption number and authoritative agency record when establishing a particular approval. 21 CFR 1010.5; FDA Laser Notice 52.

Government property across awards and support contracts

For ABAD hardware, the property plan needs to connect the acquisition decision, contract terms, custody records and eventual transfer or disposition. DoD's September 9, 2026 Revision 1 supersedes the original 2026-O0046 deviation and adopts the RFO FAR Part 45 and revised DFARS/PGI 245. Its nontraditional-contractor exception concerns the property-management-system clause; the revision retains separate property reporting and attachment requirements. Software and intellectual property are excluded from the Part 45 property framework and need their own licensing and data-rights analysis. 2026-O0046 Revision 1, memo and DFARS 245.107, RFO 45.000–45.101.

Before furnishing equipment. Contractors ordinarily supply the resources needed to perform. The Government must document the applicable benefit, administration and disposal costs, risk and necessity considerations for furnishing its own equipment. The requiring activity supplies the decision basis, and the contracting officer addresses the required findings in the contract file. Read exceptions precisely: FAR 45.102(d) covers repair, maintenance, overhaul and modification for its four-part test, while PGI 245.103-70(1) separately lists repair, modification and overhaul for its requiring-activity documentation exception. Those provisions do not waive every property requirement. RFO 45.102, Revision 1, PGI 245.103-70.

Attachments and changes. Anticipated GFP requires a solicitation and award attachment identifying the applicable property and required data. Changes to mandatory fields, additions or deletions, substitutions, transfers, accepted CAP retained for use and withdrawal of use authority require both a contract modification and an updated consolidated attachment. The ordinary attachment route uses PIEE; a classified attachment uses a separate document with similar data. Classification of the contract alone does not remove the attachment requirement. Revision 1, DFARS 245.103-72 and PGI 245.103-72/-74.

Follow-on contracts and CAP. Property is accountable to one contract at a time, although separately authorized use on other contracts can be permitted. Transfer requires a firm requirement under the gaining contract and SF30 modifications to both contracts, using the GFP attachment and adding required clauses where absent. A DD1149 shipping document does not accomplish that contractual transfer. CAP follows an additional step: direct transfer as CAP is prohibited; the item must be delivered under a line item before transfer as GFP. Delivered and accepted CAP retained by the contractor becomes GFP. Unanticipated CAP may require an NSP delivery line with the specified identifiers. The incorporated capitalization threshold governs a stated delivery-timing condition, rather than appropriation selection. Government title may precede delivery, so title, acceptance, custody and accountability must each be identified. RFO 45.106, Revision 1, PGI 245.102(2), 245.103-71 and 245.402-71.

Administration and sustainment. The January 2024 reporting clause uses the GFP module for specified transactions and requests. Its default seven-business-day deadline applies to receipt, transfer, shipment and incorporation status changes under paragraph (b)(1)(i)–(iv), unless the contract specifies otherwise. Other events retain their own requirements. Completed-repair shipments use the specified WAWF route; subcontractor possession does not eliminate reporting. Sustainment inventory requires an actual reporting schedule and the requiring activity's applicable CDRL: semiannual is typical, not an invariant interval. Performance-based deliverables also need appropriate hardware delivery lines where the arrangement requires property delivery. DFARS 252.245-7005(a)–(c), Revision 1, PGI 245.103-73/-74.

Clause selection and limits. DoD requires FAR 52.245-1 for repair, maintenance, overhaul and modification purchase orders regardless of the property's unit acquisition cost. The September revision excludes eligible nontraditional defense contractors from 252.245-7003 unless the exemption is waived; it does not express blanket relief from 252.245-7005, attachments or other property duties. Current eligibility and waiver authority must be established from the applicable implementation. Full DoDI 5000.64 and DAF accountability implementation, complete underlying clauses, specialized-property controls and overseas requirements remain unresolved. Existing contracts require assessment of their actual terms and lawful modification authority. Revision 1, memo and DFARS 245.107.

Data warranties and overseas repair support

Support data can remain defective after hardware has been accepted. The applicable data-warranty clause can preserve correction and other remedies, but coverage depends on the actual contract, data line, clause edition and alternate. The February 2026 adopted form is 252.246-7998; the standard March 2014 252.246-7001 remains a separate reference when reviewing older incorporated terms. The signed deviation does not, by itself, establish which text an existing contract contains. 2026-O0035, 246.710(1), PDF pp.12–13 and clause pp.17–22; standard 252.246-7001.

Selection and approval. Obtain a technical-data warranty when practicable and cost effective, considering intended repair/maintenance use, cost and enforceability. The adopted prescription applies when 252.227-7989 is included and greater protection or duration is needed. Basic serves contract types other than firm-fixed-price or fixed-price-incentive; Alternate I serves fixed-price-incentive and Alternate II firm-fixed-price. Extended liability requires consideration of inadequate ordinary remedies and deterrence, together with the applicable warranty-approval requirement. These provisions do not mandate a warranty for every manual or system. 2026-O0035, 246.703-1, 246.708 and 246.710(1), PDF pp.11–13.

Documentation and software differ. The incorporated technical-data definition includes software documentation but excludes software itself. Under the selected noncommercial implementation, software within a weapon system or major subsystem should be covered by the system warranty. A non-weapon-system software warranty requires CO approval, consideration of FAR 46.703 factors and tailored terms. These requirements do not establish commercial license rights or blanket cloud-service warranties. 2026-O0036, 227.7103-14(c), PDF p.30; 252.227-7989(a), PDF p.46.

Calendar and enforce the actual promise. The data warranty addresses conformity at delivery despite inspection and acceptance. Its period extends three years after completion of delivery of the relevant DD Form 1423 data line, or longer if specified. A contractor discovering a breach during that period must immediately notify the CO in writing; Government notice must be written and within the warranty period. After qualifying notice, the CO has the stated reasonable-time correction/replacement or price/fee-adjustment choices. Contractor refusal or failure supports the follow-on correction-at-contractor-cost or adjustment remedies. The clause applies anew to the corrected or replaced portion furnished under paragraph (d)(1)(i). This is a reason to preserve data-line and notice records through administration, payment and closeout; it does not create a universal closeout hold. 2026-O0035, 252.246-7998(b)–(e), PDF pp.17–22.

Additional damages have distinct limits. Alternate I uses a cap of 75 percent of target profit; Alternate II uses 10 percent of total contract price for their additional-liability provision. Both contain equipment-subcontractor limits and exceptions for enumerated drawing/SIE data meeting stated quality conditions, and for defects the contractor discovers and reports before Government discovery. These are not blanket caps on correction costs or exemptions from all warranty remedies. Apply the actual alternate, named specification editions and subcontract facts. 2026-O0035, Alternate I/II(d)(3), PDF pp.19–22.

Plan overseas repair before award. Warranty value depends on defect reporting, responsibility tracing, distance, storage and practical enforcement. If returning, replacing or moving equipment for repair is foreseeably impractical, FAR 46.706(b)(2)(iii) says the warranty should provide for repair in place. When Government repair is contemplated, the contract must provide the specified contractor parts/material and instructions. Transportation liability generally starts from the contractual place of delivery; returns from elsewhere or alternate remedies do not create unlimited shipping liability. For fixed-price-incentive warranties, consider costs in target/ceiling and final pricing, with later warranty compliance at no additional Government cost after final-price establishment. Adopted RFO FAR 46.703, 46.706(b)(2) and 46.707.

Unresolved implementation. The signed 246.705(a) cost-reimbursement exception still says 252.246-7XXX, while its prescription and clause say 252.246-7998. The signed Part 227 warranty paragraph still references 252.246-7001. Those inconsistencies require authoritative reconciliation for the action; they are not silently corrected here. Current DAF approval/delegations, complete product-support instructions, commercial warranty rules and the underlying data/license rights remain separate limitations. See GAP-027 and RULE-0242–0247. 2026-O0035, PDF p.12; 2026-O0036, PDF p.30.

Ordering and accepting technical data and software

Data delivery, acceptance, license rights and warranty protection require separate decisions. Buying a radar or C2 integration service does not by itself establish what supporting data must be delivered, when the Government may order it, or how it may be used. The selected adopted Part 227 provisions provide delivery and acceptance controls; actual incorporated terms and authorized changes govern an existing action. 2026-O0036, 227.7103-6, -8 and -14(b), PDF pp.20,23,29–30.

Distinguish ordering from deferred delivery. Adopted 252.227-7995 addresses a potential need without a firm preaward requirement for a particular data item. It reaches data/software generated in contract or subcontract performance, with compensation for conversion into the prescribed form, reproduction and delivery. Section 227.7103-8 provides the three-year period after acceptance of all items other than data/software or contract termination, whichever is later. Technical data for a subcontractor item have a separate endpoint three years after contractor acceptance of that item's final delivery. Use rights remain governed by the incorporated rights clause. The standard April 1988 252.227-7027 is a separate existing-term reference. 2026-O0036, 227.7103-6(h), -8 and 252.227-7995, PDF pp.20,23,86–87; standard 252.227-7027.

The older April 1988 252.227-7026 instead covers data/software identified in the contract as deferred delivery and uses two-year prime-contract and subcontract-item periods. The adopted attachment marks 7026 reserved. An existing incorporated two-year term is not automatically enlarged to three years; identify the actual clause, deferred items and any authorized modification. These periods also differ from the data-line warranty clock. Standard 252.227-7026; 2026-O0036, PDF p.86.

Define acceptance and assess each deliverable. The contract must specify technical-data, documentation and software acceptability requirements. The CO or authorized representative determines conformity. Apply the inspection/remedy clause; the policy's fallback, if that clause is absent, refers to FAR 46.407(c)–(g). Ordinary nonconformance calls for correction/replacement or the stated equitable-price-reduction alternative when correction is impractical or not in the Government's interest. Markings as the sole defect follow a distinct procedure. Equipment receipt or shipment release alone does not establish data/software acceptance. 2026-O0036, complete 227.7103-14(b), PDF pp.29–30.

Use withholding within its limits. Under incorporated 252.227-7996, the CO may withhold ten percent of total contract price/amount, or the lesser amount specified, for late or deficient required technical data until acceptance. Section 227.7103-14(b)(2) addresses a fixed amount or percentage up to ten percent, considering the data's value and importance. The clause bars withholding and other action under paragraph (a) when the failure is beyond contractor control and without its fault or negligence. Withholding or later payment does not waive Government rights. This technical-data remedy includes qualifying documentation but does not independently cover software code. The March 2000 standard 7030 clause has different rights-clause references and must be matched to actual existing terms. 2026-O0036, 227.7103-14(b)(2),(4) and 252.227-7996(a)–(b), PDF pp.29,87–88; standard 252.227-7030.

Separate marking format from disputed rights. A nonconforming marking uses unauthorized form/content; an unjustified marking has an authorized form but incorrectly states rights. Clause 7989(i)(2) provides a CO notification and sixty-day correction sequence for nonconforming format. Substantive justification goes through the 7997 validation procedure referenced by 7989(i)(1), unless an applicable agreement route is established under the policy. Delivery or an assertion alone does not establish a right to strip markings or disclose the material. Full challenge, appeal and third-party-release procedures require separate assessment. 2026-O0036, 227.7103-12(a)–(b) and 252.227-7989(i), PDF pp.24–25,56.

Use prior-delivery information to assess rights. Under the selected prescription, 252.227-7028 requires an offer attachment identifying intended restricted data/software deliveries identical or substantially similar to material previously produced for, delivered to or owed to the Government. Required fields identify the production contract; the latest/future delivery contract and recipient organization; and use/disclosure limitations, including earliest applicable expiry. This identifies the evidence needed in the protected acquisition file; prior delivery alone does not confer unlimited rights. 2026-O0036, 227.7103-6(f) and 252.227-7028(a)–(c), PDF pp.20,87.

Two signed-text inconsistencies remain material. The 7996 introduction points to 227.7103-6(g)(2), while the actual withholding prescription is (g)(3). Policy 227.7103-12(a)(2) literally starts its sixty-day period at the person's receipt of the data/software; clause 7989(i)(2) instead describes notification and failure to correct within sixty days. GAP-028 preserves both for authoritative reconciliation before applying the affected remedy. Current complete DoDI 5010.44 and DAF IP implementation, commercial licenses and full rights-validation procedures also remain unresolved. FLOW-37 connects these decisions with RULE-0248–0253; none establishes a local delegation or blanket payment/closeout hold. 2026-O0036, PDF pp.20,25,56,87–88.

Funding validation, recording and IDIQ minimums

A funded purchase request is not the last funding check. Drafting can change descriptions and line-item structure. Under the September 2026 FMR, certifying officials must perform automated pre-award validation with the issuing organization that committed funds remain available and suitable for the draft award. Preserve accounting and procurement line-item traceability through obligation and payment, and separate items requiring different accounting treatment. The Global Exchange tool is an available option, not a mandatory system for every action. This applies to the actual appropriation and requirement; a USAFE or EUCOM funding source alone supplies no exception. FMR Volume 3, §§8.1–8.2, p.15. See RULE-0254.

The incurring office must transmit the obligating document within five calendar days; the recording office has five calendar days after receipt. The outer limit is ten calendar days following incurrence, and every obligation must be recorded in the same calendar month. Keep documentary support; reduce an authorized verbal agreement to writing before recording. If the amount cannot feasibly be determined, retain the basis of the best estimate. These recording limits do not extend appropriation availability or authorize backdating. Late items need the applicable correction process. FMR Volume 3, §§8.3–8.4, pp.15–16. See RULE-0255.

During administration, the funds holder validates transactions and quarterly reconciles the period's obligations to the general ledger and contracting records or obligating documents. Investigate and document differences; FM determines adjustments. Bulk estimated obligations need monitoring and are prohibited for the specified DLMS/MILSTRIP materiel requisitions. Within the responsible FM office, separate obligation recording and order acceptance from receiving reports and acceptance/payment certification. If management finds segregation impractical, it must implement additional Volume 5 controls. This is a defined management determination, not an assumed local waiver. FMR Volume 3, §8.17, pp.23–24. See RULE-0256; GAP-016 retains supplemental and local implementation needs.

For an IDIQ, document the supported minimum and distinguish it from the ceiling and per-order limits. Current model FAR 16.504-1 requires a minimum above nominal value that should not exceed what the Government is fairly certain to order; 16.504-2 addresses known kinds/minimum needs and ongoing repeated requirements. Section 16.504-5 requires the minimum, maximum, ordering period and last delivery date in the contract. The Department adopted this model through the signed July 15, 2026 Revision 1; the model page alone is not the adopting instrument. RFO FAR 16.504-1/-2/-5, 2026-O0045 Revision 1, pp.1–2. See RULE-0257.

GAO explains that a guaranteed minimum creates a liability at execution and must reflect a bona fide need at that time. B-318046's $500 FEDLINK conclusion was specific to its circumstances; it is not an ABAD minimum or a percentage rule. B-321640 found that SBA's annual-fund minimums lacked the supported need required by the circumstances. A general equipment replacement cycle did not establish the amount, and changing later-order funding did not cure the unsupported initial guarantee. Treat these decisions as legal interpretation, with their facts and dates preserved. GAO B-318046, July 7, 2009, GAO B-321640, September 19, 2011, pp.3–6.

Before a year-end or option-period minimum increase, document the specific need, amount, appropriation period and legal obligation, then assess later orders separately. B-321640 addressed annual FY2009/2010 funds; it did not prohibit all year-end awards, later deliveries or properly supported inventory purchases. Inventory replenishment was not advanced as the justification in that case. Existing lead-time and severability analysis remains relevant, and no-year/multiyear funds or statutory exceptions need their own analysis. Use FLOW-38 and RULE-0258 with the existing funding rules; the action's terms and current implementation still matter. GAO B-321640, pp.3–6 and footnote5.

Assisted acquisition and non-Economy Act administration

An assisted acquisition needs a clear allocation of responsibilities before it becomes a contract-management problem. For covered assisted actions, the requesting and servicing agencies sign their agreement before solicitation, identify applicable unique requirements and retain the agreement in both files. The order needs the specified description, delivery, funds, payment and statutory authority. The servicing agency prepares acquisition justifications and determinations, except the requesting agency’s Economy Act determination. The direct-acquisition exception in 17.502-1(a)(2) is limited to that paragraph’s agreement requirement; financial agreements and funding routes still require their own analysis. Apply the model’s scope with DFARS 217.500, including its more-specific-statutory-authority qualification. Adopted model FAR 17.500, 17.502-1(a) and 17.503, signed 2026-O0027, pp.1–2, 11 and 48. See RULE-0259.

For direct or assisted use of a non-DoD contract above the applicable simplified acquisition threshold, document review and approval, customer requirements, schedule, cost effectiveness, administration and oversight. Confirm the vehicle’s scope and appropriation limits. A provider using another agency’s vehicle must disclose that route and all direct and indirect fees; continuing with the arrangement requires a rationale informed by the total fees. An existing vehicle is not itself authority for a new requirement or a modification. DFARS 217.600/.601/.670 and PGI 217.670(a)(3), signed 2026-O0027, pp.12–13 and 48. See RULE-0260.

Covered nondefense acquisitions above the applicable threshold require the relevant fiscal-year certification or an applicable written waiver. GSA’s signed letter certifies its assisted acquisitions for FY2027; it does not approve a particular ABAD order, another agency or a later fiscal year. The thirty-day certification-submission requirement is not an automatic grace period for uncertified acquisitions. Preserve the narrow intelligence-community joint-program exception and the actual route and scope. Model FAR 17.600–17.603, GSA FY2027 certification, p.1. See RULE-0261.

A certification waiver needs its own written authority and determination. The published 2011/2018/2019 delegation chain reaches Component Senior Procurement Executives and permits redelegation no lower than HCA. It does not establish a current DAF redelegation or a FY2027 waiver. The 2011 memorandum’s $100,000 threshold is historical, and its continuation clause depends on absence of rescission or statutory repeal/modification. Verify the current chain, signer, acquisition categories and fiscal year before relying on it. Model FAR 17.603(e), signed delegation bundle, pp.1–4. See RULE-0262 and GAP-029.

A non-Economy Act order requires a specific alternative statutory authority, a definite requirement and a supported funding package. The September 2026 supplement expressly requires DoW-warranted CO review for orders greater than $500,000 before the funds-certifier or FS 7600A/B issuance step. Keep that printed trigger distinct from other duties expressed in terms of the applicable SAT. Include delivery/performance, proper fund citation, payment and any advance-payment authority, DODAAC, fees, competition and DoD-unique requirements. Use the applicable exact funding statement in Supplemental 18.1.2.6 or 18.1.2.7. The requesting official certifies time, purpose and availability; all binding-obligation criteria must be met before recording. An agreement cannot preserve expiring money for a later need. FMR Volume 11 policy, §§18.1–18.8, pp.83–86, Volume 11 Supplemental, §§18.1–18.5 and Figure 18-1, pp.72–74 and 77. See RULE-0263.

During performance, determine the goods or service category before deciding which balances must return. The goods provisions allow specified timely-request and justified lead-time or unforeseen-delay circumstances; they do not provide a general exception for readily available COTS or excessive delay. Under the stated severable-service route, performance begins while the customer funds are available and lasts no more than one year; annual funds cannot support performance entirely in the next fiscal year. Nonseverable contracts are fully funded with appropriations available for new obligations at award, with excess returned when identified. Reconcile balances and apply the specific return and deobligation requirements rather than assuming every non-Economy Act statute has the Economy Act’s statutory rule. Volume 11 Supplemental, §18.6, pp.74–75. See RULE-0264.

The requesting official retains oversight. Above the applicable SAT, establish and execute quality surveillance plans addressing contract administration, receiving reports, invoice review and reconciliation, and documented acceptance. Monitor funds, confirm open balances and perform the referenced dormant-account review and attestation. Every completed non-Economy Act order needs fiscal closeout, including review of outstanding invoices and excess or expired balances and coordination of returns and deobligations. Fiscal closure of that interagency order does not establish completion of the underlying contract’s separate closeout requirements. Volume 11 Supplemental, §18.7 and the repeated §18.3 heading “Non-Economy Act Order Close-Out,” pp.75–76. See RULE-0265 and FLOW-39.

GAP-029 preserves implementation questions that affect these decisions. The published model and supplement contain inconsistent cross-references; the supplement repeats section numbers and identifies FS 7600A in its written-obligation criteria. Do not infer that general terms alone create a binding funding obligation. FMR form/system transition wording and PGI DD448 language require reconciliation with the G-Invoicing implementation policy and the direct-cite PRDS requirements. Treasury’s public page states that current 7600A/B forms and instructions moved to MFA-protected Intralinks. Obtain those instructions and applicable local implementation through authorized channels. Neither an overseas assignment nor USAFE/EUCOM funding establishes an exception. FMR Volume 11, §§2.1.3 and 18.6, Supplemental §§18.1.1 and 18.5.2.2, FPM25-05, pp.1–3, Treasury IGT resources.

Contract scope and option extensions

An existing vehicle does not answer the scope question by itself. GAO compares the proposed order or modification with the original competition: the circumstances of procurement, work, performance period, cost and notice given to potential offerors. The central question is whether they reasonably could have anticipated the added work. Read the contract as a whole, including its customer, mission, product/service, duration and value provisions. Prepare that comparison before selecting the competition route; assess appropriation and funding scope separately. A broad title or remaining ceiling is insufficient by itself. Rice Services, B-424208 et al., April 9, 2026, pp.6–9. See RULE-0266 and RULE-0134.

The drone-specific Red Cat decision illustrates why the actual terms matter. GAO found the order within the SOETLSP contract’s scope after considering its customer/mission coverage, permitted delivery flexibility and value structure. The protester did not dispute that drone products could fall within the covered categories. That result supplies neither a general percentage safe harbor nor eligibility for any other logistics or IT vehicle. Its brand-name challenge was dismissed because the supplier did not hold the IDIQ; that procedural outcome does not approve every brand-name restriction. Vehicle-selection allegations were also dismissed, not converted into an exemption from otherwise applicable mandatory sources or program rules. Red Cat Holdings, B-424397/B-424397.2, July 10, 2026, pp.4–12 and footnotes9–10. See RULE-0267.

Keep underlying-contract scope, individual-order scope and protest standing separate. A change outside the competed IDIQ can implicate a new competition; an order-level change within the IDIQ presents a different fair-opportunity question. Network Designs dismissed a nonholder’s challenge to an order modification without deciding its merits. Rice expressly distinguishes that situation from an underlying-contract scope protest. Network’s footnote4 leaves unresolved whether the modification increment or whole order value controls jurisdiction. These opinions therefore do not replace current jurisdiction research or prove compliance merely because one supplier cannot protest. Network Designs, B-423525/B-423525.2, August 8, 2025, pp.3–5, Rice, pp.4–6 and footnote4. See RULE-0268.

For extensions, separate the option’s original evaluation from its exercise price. Major Contracting Services sustained a challenge to an unevaluated service extension; Army—Reconsideration rejected the argument that including52.217-8 and evaluating base/option-year rates was equivalent to evaluating the extension. A determinable price did not satisfy the separate evaluation requirement. The initial decision also rejected the sole-source justification where inadequate advance planning and other capable firms undermined the claimed need to use only the incumbent. Plan continuity early and establish an applicable competition or justification route when an extension was unevaluated. Historical thresholds, notice periods and FAR17.207(f) numbering in those decisions are not current universal rules. Major Contracting Services, B-401472, September 14, 2009, Discussion, Army—Reconsideration, B-401472.2, December 7, 2009, pp.3–6. See RULE-0269.

The adopted model now places evaluation in17.202 and the evaluation/price competition prerequisites in17.204-1(b)(3)(vi). Its rare exception for evaluation of option quantities requires a written decision, approval at least one level above the CO and filing; it does not itself waive competition at exercise. The signed DoD deviation adopts the linked model effective February1,2026 until rescinded or incorporated. Apply the governing version and actual terms to the action; this does not automatically rewrite an existing contract. Model FAR17.202 and17.204-1, 2026-O0027, pp.1–2.

Before exercise, check contract limits and timing, available funds, continuing need, required synopsis or exemption, SAM exclusions, acceptable performance, current-market pricing and Government interest. Assess any requested economic price adjustment first. Distinguish advance written intention notice from the actual exercise mechanism in the contract. Subpart17.2 has specified real-property, architect-engineer and R&D service exclusions subject to agency regulations; those are not generic equipment exemptions. Add the applicable defense security checks already identified in RULE-0114, with unresolved transition questions in GAP-015. Model FAR17.200,17.201-2 and17.204-1. See RULE-0270 and FLOW-40. GAP-013 remains open for wider case law; no opinion establishes a particular ABAD contract’s scope, local ordering authority, funding exception or permission to operate a drone/counter-drone system.

Contract-file closeout and final records

Contract-file closeout requires its own completion evidence, administrative reconciliation and final records. Start after evidence of physical completion and review funds status. Under Table 4-2, simplified acquisitions close with evidence of receipt and final payment unless agency regulations provide otherwise. Other firm-fixed-price contracts have a six-month target after the date the CO receives physical-completion evidence; contracts requiring indirect-cost settlement use 36 months of that month, and other contracts use 20 months of that month. These are “should” time standards. Litigation, appeal and unfinished termination actions expressly prevent closure. Confirm the applicable physical-completion criteria instead of importing an older section number. Adopted model FAR 4.308-2 and Table 4-2. DoD adoption is effective February 17, 2026 under 2026-O0043, pp.1–2. See RULE-0271.

Before the completion statement, assign and resolve all fifteen administrative items in 4.308-1: classified disposition; patent and royalty reports; value-engineering proposals; plant and property clearance; cost, price and subcontract settlement; indirect rates; termination and audit actions; the closing statement; final invoice submission; and funds review. Submission of an invoice does not prove payment. A missing patent report has a specific notice and patent-counsel/agency-procedure route, rather than an automatic waiver of intellectual-property obligations. Preserve actual property, data, warranty and payment duties when documenting completion. Model FAR 4.308-1(a)–(c). See RULE-0272 and the related property/data records.

DoD procedures allocate completion dates, statements and distribution between the procuring and administering offices. Use the required DD 1594/1597 or authorized equivalents and EDA/financial-system routing. An ACO unable to meet the applicable period must notify the PCO within 45 days after it expires, explain the delay and provide a new target; another missed target requires a renewed notice. The specific block-5 completion-statement procedure permits deobligation without a modification upon distribution, with a comptroller copy for ledger reconciliation. For contracts paid solely by GPC, no final invoice is required for closeout, but the completion statement must show the final acceptance date. That exception does not remove acceptance or other completion duties. 2026-O0043, PGI 204.308-170, 204.308-171, 204.308-2 and 204.308-270, pp.97–100. See RULE-0273 and RULE-0160.

Three expedited routes have different purposes and conditions:

| Route | Selected limit | Additional conditions | | --- | --- | --- | | Automated closeout | Contract value of $500,000 or less | Only firm-fixed-price line items, none of eleven excluded clauses, and applicable Component restrictions. BOAs, BPAs and indefinite-delivery contracts require all orders closed and the ordering period expired. | | Quick-closeout cost settlement | DoD unsettled direct and indirect costs of $2 million or less, regardless of contract/order value | Physical completion, risk assessment and agreement on a reasonable allocable-cost estimate. The separate route without a dollar/percentage limit is expressly for DCMA ACOs. | | Residual-balance waiver | Mutually agreed residual of $1,000 or less | Applicable 252.204-7022 clause, all applicable closeout actions complete, and no tax or law/regulation-violation amounts. Offsets must be independently lawful. |

The automated exclusions are 52.211-11, 52.216-7, 52.227-9, 52.227-11, 52.227-13, 52.232-16, 52.232-29, 52.232-30, 52.232-32, 52.245-1 and 52.248-1. A listed clause prevents use of this automated route; it does not necessarily prevent ordinary closeout. The $500,000 figure is not an interchangeable reference to the simplified acquisition threshold. 2026-O0043, PGI 204.308-170(a)(6), pp.97–98; residual prescription 204.308-70, p.11; clause 252.204-7022, p.25. See RULE-0274 and RULE-0276.

For quick closeout, DoD replaces the model’s lesser-of-$1-million/10-percent test. The wider DCMA ACO provision cannot be assumed from a USAFE/AFICC assignment, a funding sponsor or an organizational relationship. Assess contractor-system and auditor concerns and other relevant risks, agree the estimate, and preserve the settlement’s boundary: it is final for the specific contract, does not shift under- or over-recoveries to other contracts, and does not establish binding rates for them. The signed adoption is effective March 16, 2026 until rescinded or incorporated. Read actual incorporated payment terms alongside the current procedure. Model FAR 42.507(a)–(c), 2026-O0050, cover pp.1–2 and DFARS 242.507, p.7. See RULE-0275.

The separate aged/unreconcilable-contract exception requires further statutory and implementation confirmation before reliance. Its printed 204.308-170(c)(2) points to a nonexistent (3)(ii)(B), and (c)(4) points to PGI (c)(iv), while the selected PGI waiver routing appears in (b). These cannot be silently repaired to support cross-contract offsets or a waiver. GAP-030 preserves those issues and current statutory amendments, written authority and local procedures. 2026-O0043, DFARS 204.308-170(c), pp.9–11, and PGI 204.308-170(b), p.98.

Administrative closure is also distinct from records disposal. Ordinary Government contract and related records have a six-year period after final payment, with longer holds for investigations, litigation, protests or enforcement when required. Mixed program files and other listed classes use their applicable schedules. Selected defense text adds initial office retention/staging and pricing-review periods; its older GRS 3/6 and FAR numbering need reconciliation with current records guidance. EDA is accessible to multiple parties and excludes classified or overly sensitive material and impractical attachments; it is not a public-file designation. Confirm the current DAF/NARA schedule, legal holds and authorized repository before disposal. Contractor retention duties are separate. Model FAR 4.309 and Table 4-3, 2026-O0043, DFARS 204.309-70 and 204.705-70, pp.11–12. See RULE-0277 and FLOW-41.

Export controls through award and overseas support

Export authorization is a separate decision in an ABAD acquisition. A contract, an overseas delivery address or USAFE/EUCOM funding does not establish every condition of an export exemption. First determine the jurisdiction and classification of the hardware, software, technical data or service, the parties and intended use, and the authorization needed for each transfer. DFARS 225.7901 preserves independent contractor compliance and prescribes 252.225-7048 in all solicitations and contracts; the clause requires its substance, including the flowdown requirement, in all subcontracts. Existing orders, options and modifications require attention to the governing contract terms; a new prescription does not silently amend them. 2026-O0041 Revision 1, 225.7901 and 252.225-7048. See RULE-0278.

The CO should identify and route export issues without taking over the contractor’s interpretation of compliance requirements. PGI 225.7901-2 identifies DTSA for Government acquisition questions and directs contractor ITAR/EAR compliance and registration questions to State or Commerce and the applicable clause. Registration and its exceptions require their own assessment. Fundamental research is not a statutory escape from controls when controlled items are used or generated. Adopted PGI 225.7901-2, PDF pp.260–263. See RULE-0279.

Australia and UK Defense Trade Cooperation Treaty procedures require specific eligibility evidence. For potentially eligible solicitations/contracts, the PM must provide written identification of the treaty scope and qualifying articles before solicitation and before award, plus applicable excluded-technology terms for line items. The CO applies the 7046/7047 prescriptions and fills the designated clause information. Approved-community status, permitted purpose and eligible technology must all be established; procurement nationality rules do not establish export eligibility. Existing license terms continue until an approved transition. Current treaty lists, full State implementing provisions and complete clause terms must be checked before reliance. DFARS 225.7902-4/-5 and PGI 225.7902-2/-4. See RULE-0280.

For transfers made by a Government agency, 22 CFR 126.4(a) has separate official-use, agreement, assistance/sales and security-cooperation grounds. The contracted official-use provision requires both activity within the contract’s scope and a specified condition: a Government-controlled facility, an empowered and responsible Government employee preventing diversion and limiting use to the contract scope, or the stated DDTC Deputy Assistant Secretary authorization at an agency’s request. Its technical-data restriction concerning 126.1 countries also applies. The agency cannot rely on paragraph (a) merely as a private firm’s transmittal agent. Other approvals and legal controls continue. 22 CFR 126.4(a). See RULE-0281.

For another person acting for an agency, identify the recipient. Paragraph (b)(1) covers a transfer to the Government at its request. Paragraph (b)(2) addresses a non-Government recipient at an agency’s written direction or under an international agreement/arrangement, for an activity authorized by (a)(1)–(4). Retaining the Government request is a useful contract-file practice; the express written-direction language belongs to the stated (b)(2) route. Establish the authority of the directing/requesting official rather than inferring it from a warrant or organizational relationship. 22 CFR 126.4(b). See RULE-0282.

The authorization must remain valid through support and disposition. Section 126.4(c) permits the described return to the agency or original exporter only with the required export and subsequent-transfer history. Paragraph (e) requires EEI at export except for the specified Government transport/pouch routes, with instructions if electronic filing is unavailable. Paragraph (f) requires DDTC approval for changes of end use/user outside the section’s authorization; (a)(7) preserves its specific qualification for exports under (a)(1) or (3) while those terms continue. Repairs, loans, property transfers and modifications must therefore be assessed against the continuing conditions. 22 CFR 126.4(c), (e), (f) and (a)(7). See RULE-0283.

Screen restrictions early enough to cover proposals and communications as well as shipments. Section 126.1 addresses designated countries/persons, certain conveyances and qualifying proposals; paragraph (e) also imposes an immediate notification duty for the transactions it describes. The September 23, 2026 correction restored specified Government-transfer exceptions in (a)(2)–(3). Identify the exact exception and its limits, reconcile 126.4(d), and check the applicable country provisions and other sanctions. Neither a general embargo label nor a Government recipient alone resolves every legal condition. Current 22 CFR 126.1(a)–(e); operative correction, 91 FR 60299. See RULE-0284.

Use FLOW-42 to assemble these decisions across a new purchase or an existing contract’s performance. GAP-031 preserves unresolved classification, registration, current treaty/EAR implementation, cited policy and agency-authority questions. Foreign-country import permissions, customs relief, accountable-property duties and operating authority remain separate prerequisites. The current provisions above do not determine eligibility for a particular ABAD transaction.

Procurement routes and contract management in Germany

Identify the applicable treaty, sending state, territory and implementing agreement before selecting a procurement route. NATO SOFA Article IX(2) normally routes locally sourced subsistence goods through receiving-state military purchasing authorities; it is not a general rule for every radar, camera, software or effector purchase. Paragraph (3) addresses accommodation and services subject to existing/future agreements. Paragraph (7) requires prompt local-currency payment for the specified requirements, subject to financial arrangements, while paragraph (8) grants no tax or duty exemption by reason of Article IX itself. Relief under other instruments must be established separately. NATO SOFA Article IX. See RULE-0285.

Germany’s Supplementary Agreement provides a more specific goods/services route. Article 47(3) permits direct procurement or procurement through appropriate German authorities after prior agreement. Direct purchases may use the force’s normal procedures while respecting the German public-procurement principles reflected in competition, preferred-tenderer and public-contract price regulations. Article 47(4)(b) requires notice of the order’s subject, size, supplier and price except for minor orders. The reviewed text does not define minor orders by a U.S. acquisition threshold. Establish the actual implementation and notification procedure before treating an order as excepted. Article 47(1)–(4), PDF pp.53–54. See RULE-0286.

The German-authority route has distinct contract-management responsibilities. Provide detailed requirements, technical specifications and special delivery/payment conditions in time. German authorities contract with the supplier under German public-contract rules and retain exclusive competence in relation to that supplier. The force participates to protect its interests: no award or modification occurs without its written consent, and acceptance is joint unless otherwise agreed. An official’s participation or consent therefore does not itself authorize direct instructions to the supplier. Apply the actual administrative agreement throughout delivery, changes and acceptance. Article 47(5)(a)–(c), (g), PDF pp.54–55. See RULE-0287.

Plan the related funding and reconciliation before performance. Article 47(5)(d) specifies reimbursable German expenditures, with consent conditions for out-of-court settlements and ex gratia payments and a separate emergency-cost category. Funds must arrive in time for payment due dates; payment-document audit proceeds in an agreed manner. Re Article 47 requires administrative agreements to include funds-availability certification in the written consent. Preserve those records through reconciliation and closeout. The treaty does not supply a U.S. appropriation, waive fiscal restrictions or delegate payment authority. Article 47(5)(d)–(g) and Re Article 47, PDF pp.54–55. See RULE-0288.

Disputes require a separate agreement check. Article 44 provides cooperation, notice, consultation, agreement on ending disputes and qualified cost responsibilities. Its direct-procurement default identifies German courts or independent arbitration, but paragraph (6)(b) expressly gives agreements between Germany and the sending state precedence. Obtain the applicable U.S.–German agreement and contract terms before deciding the forum or replacing a disputes procedure. Counsel and responsible funding officials must address the distinct judgment, settlement, appeal and advance-agreement cost conditions. Article 44, PDF pp.49–51. See RULE-0289.

Classify personnel separately from the procurement route. NATO SOFA Article IX(4) subjects its local civilian labor category to receiving-state employment conditions and excludes those workers from force/civilian-component status. Article I(1)(b) separately defines the civilian component and its excluded categories. Neither provision makes all contracted technicians civilian-component members or establishes that all contractor employees are local labor. German labor and contractor-status provisions require further review. Articles I(1)(b) and IX(4). See RULE-0290.

Use FLOW-43 for new purchases and existing-contract administration in Germany. GAP-032 retains current U.S.–German implementation, minor-order meaning, bilateral dispute arrangements and actual delegations. The cited UK-hosted compilation identifies the 1959 agreement amended through March 1993, effective March 29, 1998; it is not certified as a fully current consolidation. Its stale labor-protocol status note is outside the provisions adopted here. The German Foreign Office’s August 28, 2026 explanation continues to identify the 1959/1993 framework and distinguishes permission for presence from the rights and obligations during presence. This country entry remains partial, and tax/customs, export, spectrum, flight, privacy and effector permissions remain separate. German Foreign Office explanation.

Overseas application

The country profiles follow the 50 countries named in EUCOM's regional groups. Each has the same eight research topics so missing coverage remains visible. Listing a country is not a finding that performance there is authorized or that all national rules have been collected. EUCOM regional list.

Treat treaty applicability, contractor status, spectrum, flight, privacy and import/tax rules as separate questions. NATO or EU membership alone does not decide each one. NATO SOFA arrangements require attention to the persons, activity and receiving state involved; contractor status is not automatic. NATO SOFA.

Revised DFARS/PGI 225.770 requires attention to foreign-country performance conditions and points Germany contractor privileges to bilateral agreements. The deployed-contractor section has additional operation/designation conditions. Neither provision makes every overseas purchase an identical case. 2026-O0041 Revision 1, sections 225.770 and 225.771.

The overseas vendor-threat deviation is directly relevant to acquisition and administration. It prescribes clauses 252.225-7962 and 252.225-7975 for the stated overseas performance, including commercial acquisitions. Their requirements include subcontractor diligence and records access. The threat-mitigation clause specifies SAM checks before subcontract award and at least monthly thereafter. Covered procurement actions require the memorandum's HCA process and notice/review protections. Current EUCOM implementation remains a separate question. 2026-O0051, memorandum and attachments.

EUCOM is also named in the temporary rapid-contracting deviation 2024-O0011. Use depends on a qualifying covered operation and the command/HCA request and approval process; EUCOM funding alone does not activate it. The instrument states a September 30, 2028 endpoint unless earlier rescinded. 2024-O0011, paragraphs A–C and final paragraph.

Germany illustrates the distinction: TKG §91 addresses frequency assignment, LuftVG §30 addresses military aviation exceptions, and BDSG §4 addresses certain public-space video surveillance. These provisions begin the analysis; they do not resolve a particular U.S. installation, contractor or equipment configuration. The UK radio-licensing record likewise retains unresolved military/visiting-force applicability. TKG §91, LuftVG §30, BDSG §4, UK section 8.

For German VAT, the BMF's UStH 2024 guidance makes relief depend on the procurement route, eligible use, price treatment and evidence. Receipt/payment certification and invoicing therefore matter during performance as well as award. Confirm the applicable NATO/offshore route and later amendments; this dated guidance does not establish an individual exemption. UStH 2024 Annex 6, paragraphs 8, 13-17, 28-31 and 66-69.

Additional examples show why a blanket military exemption is unreliable. UK Data Protection Act section 26 has a necessity condition and retains specified lawfulness requirements. Spain's RD 517/2024 expressly excludes military UAS/activity from its civil regime, which does not itself grant flight permission. Poland's 2020 EDCA defines contractor categories and separately addresses professional licensing and conditional official-purchase tax relief. Each still needs its relevant scope and implementation analysis. UK section 26, Spain articles 1, 3 and 35, Poland EDCA, articles 2, 10 and 19.

Equipment delivery and return through USEUCOM customs

The September 30, 2026 DTR chapter makes customs planning relevant to acquisition and sustainment. Duty-free treatment depends on exclusive U.S.-forces use, the recipient and the applicable treaty/host-nation arrangements. Eligible goods include contract-performance material and goods delivered to supporting contractors acting for U.S. forces; that does not confer personnel SOFA status. DoD cargo remains outside EU free circulation. Establish the intended use and route before award or order, and revisit them when a modification, repair return or disposition changes the shipment. DTR Part V, Chapter 510, A.1 and A.3, p.1.

Paragraph A.2 prescribes the U.S. Form 302 route, with limited exceptions, and requires DoD Components to consult HQ USEUCOM before complying with host-nation demands for additional documents or automated EU submissions. Contractors should raise these demands with their CO or COR. A.4 states the commercial customs declaration, ENS/ICS2 and six-digit HS-code exemptions for shipments accompanied by Form 302. The same chapter retains country-form and tariff-information references. Resolve the applicable route through the stated consultation process rather than treating either set of statements as unconditional. These provisions state DoD procedure; country law and the underlying EU instruments remain separate applicability questions. Chapter 510, A.2/A.4, P.2.c-d and Q.1.a.(1), pp.1 and 9–11.

Separate customs issuance, cargo receipt and contract acceptance. An appointed Customs Clearance Officer signs and stamps issued Form 302 documents. The receipt categories include contractors providing services directly to U.S. forces, while commercial transportation-provider representatives are expressly excluded from receiving and clearing this cargo on Form 302. A CO warrant or COR appointment does not establish customs authority. For acquisition planning, identify the actual shipper, issuing officer and eligible recipient, and carry those responsibilities into delivery and support arrangements. Chapter 510, E.2.c-e and P.2.d.(4)-(5)/e.(4), pp.3 and 10.

Specific descriptions and shipment support matter during performance. Surface-shipment requests require written follow-up and supporting documents; a generic description such as electronic parts is insufficient. Customs reconciliation is due within 30 days of shipment, with quarterly reporting and annual file closure; completed customs files have a minimum six-full-calendar-year retention rule. These duties belong to the customs program and supplement the contract administration evidence trail without replacing contract-file requirements. Chapter 510, E.2.f/E.3-7, M.2.b.(3),(5)-(7), Q.1.a.(1)-(2), pp.3–4, 7 and 11.

For repair, warranty or disposition shipments to or through CONUS, arrange agricultural inspection before boxing, pallet buildup or container loading. The shipper must correct deficiencies and obtain the required signed/stamped DD Form 2855; absent that label, departure cargo is refused or held at the shipper's expense. DD Form 2855 does not itself clear U.S. customs. A practical acquisition implication is to allocate cleaning, inspection, packaging and return-shipment duties before performance, using an authorized change when existing terms must change. The detailed ECM 4002.01 standards and other transport/export requirements still need separate review. Chapter 510, C.1, pp.2–3 and Figure 510-2, p.61.

UK suppliers, furnished equipment and repair returns

The UK customs route turns on the transaction and recipient. The DTR identifies contractor repair/calibration followed by return outside the UK, production exports and furnished material incorporated into exported products among movements that do not qualify for U.S. visiting-force customs actions. Eligible U.S.-forces goods remain bonded; subsequent movement outside the UK requires customs entry. Detailed descriptions and coordination with USAFE-UK Transportation and Customs belong in delivery planning. These UK-specific limits must accompany the general theater eligibility analysis. DTR Chapter 510, SSS.1.a-b/c, pp.58 and 60.

For UK contractor exports, purchase and support arrangements must assign export declarations and the exporter-of-record role to the contractor, including new equipment, repaired items and GFE incorporated into a product. Shipping documents identify that contractor as origin. DCMA transportation administration is a separate consideration. For imports destined to a UK contractor, use the actual recipient rather than a U.S. Forces DoDAAC; the visiting force cannot import and transfer those goods as a substitute for the required customs route. The specified military-airlift process withholds release until the consignee's customs declaration is presented. These requirements affect solicitation terms, orders and administration; correcting existing obligations still requires an authorized contract action. Chapter 510, SSS.1.b.(1)–(3), pp.58–59.

Equipment already imported serviceable for U.S. Forces use in the UK has a separate repair-release condition. Before handing it to a UK repair facility, the receiving contractor must complete the necessary customs actions, usually inward processing relief, and USAFE-UK Transportation and Customs must hold the required documentation. Plan this prerequisite with property and contract-administration staff, including for warranty and sustainment work. Customs clearance does not replace property accountability or contract acceptance. Chapter 510, SSS.1.b.(4), pp.59–60.

HMRC separately distinguishes eligible military movements from commercial transactions and requires a full declaration for controlled or special-procedure movements. A third party needs written authority for an extended Crown Exemption. This guidance does not establish a particular licence waiver. HMRC, eligibility and licensing sections.

These findings provide partial UK customs coverage. Complete USAFE-AFAFRICA/USAFE-UK instruction requirements, current contracting delegations, harmonized Form 302 copy routing, underlying UK statutory analysis and full VAT treatment remain unresolved. Apply the current source-specific conditions to the actual destination and transaction.

Quality planning, acceptance and warranty administration

The adopted quality-assurance rules connect preaward requirements to postaward evidence. The contracting office must coordinate quality changes with its quality activity. Except for contracts using simplified acquisition procedures, it must document whether a surveillance plan is needed; this does not require a plan on every contract. Contract-specific inspection instructions must support, and stay within, the agreed requirements. They cannot repair missing contract terms or impose additional inspection obligations. For ABAD purchases and modifications, define measurable deliverables and acceptance evidence with technical staff before relying on surveillance to establish conformity. 2026-O0035, DFARS 246.103/.401 and PGI 246.103(2).

Source inspection has its own gate. Below $400,000, government QA at source requires a DoD regulatory mandate, an acquiring/administration-agency agreement, or the CO's determination satisfying the specified technical, product and contractor conditions. The separate provision for actions at or below the simplified acquisition threshold also refers to those criteria. Neither rule removes contractual quality or acceptance requirements. When another NATO government will perform QA, STANAG 4107 and its reservations apply; relevant country agreements may also matter. NATO membership does not itself assign acceptance authority. DFARS 246.402, .404 and .406.

Shipment release, inspection and acceptance have distinct effects. Inspection stamps do not establish acceptance. Alternative contractor shipment release requires written administration-office authorization, specified quality/production conditions and shipping certification, and is unavailable for FMS contracts. DFARS 246.471 and PGI 246.472(a)(iii). Acceptance follows the contract's terms and the CO's or assigned administration office's authority; its timing and documentation must be identified expressly. Adopted RFO FAR 46.501–.502.

For defects discovered after acceptance, distinguish enforceable contract remedies from the narrow fallback after warranty expiry. Where apparent contractor fault exists and no other contractual remedy remains, the CO must give written notice and request correction without government cost; consideration may be accepted if offered. That request does not itself create a debt or compel free work. Additional inspection/retest costs have a separate clause-based procedure requiring a QAR recommendation, a CO determination, consideration of cause/frequency/recovery expense, written notice and the referenced payment-demand process. DFARS 246.407-70(a) and 246.470-1.

Warranty planning should resolve approval and data delivery before award. The chief of the contracting office approves warranties unless a specified category exception applies, and approval requires expected benefits to exceed cost. Where the item-identification clause and anticipated serialized-item warranty conditions apply, prescribed tracking and repair-source attachments establish distinct award and receipt milestones. The UII may follow award but is due by presentation for receipt and/or acceptance; repair-source instructions share that deadline. The CO must ensure completed attachments reach EDA. DFARS 246.703-1, 246.710(3) and PGI 246.710-70.

These provisions support acquisition and contract administration; they do not establish an AFMC, AFIMSC or AFICC delegation or permission to buy a particular C-sUAS system. Full current AFMCI 23-110 and command procurement-policy requirements remain unresolved. Existing-contract action requires review of incorporated terms and the applicable change authority. Full international QA agreements and debt-collection implementation require additional analysis. Selected technical-data warranties are addressed above; clause cross-references and wider sustainment implementation remain unresolved in GAP-027.

Findings, implications and limitations

Use the library as an authority map and decision-preparation aid. Begin each action with its applicable version and keep acquisition, funding and operating permissions distinct. Preserve a clear reason for each selected requirement, exception and coordination route.

The most consequential remaining gaps are current DAF Compass content, applicable command policy/delegations, complete amended statutory text, account-specific funding/riders, unresolved FMR transition procedures, full current DAF budget and cyber/software issuances, follow-on CASB and pricing-reform implementation, services-acquisition and detailed COR instruction requirements, detailed national-law coverage, and technology-specific safety/operational implementation. The FY2027 CR, selected NDAA amendments and September 2026 financial policies narrow these gaps without resolving every authority or applicability question. Most country topics remain open. This is an expanding authority collection, not a complete statement of every law applicable to an acquisition.

References

References are linked beside each substantive finding. The public source register provides stable source IDs, original URLs, review dates and source status. The rule register provides the exact provision locators and version relationships used by this guide.