[ { "id": "RULE-0001", "title": "FAR overhaul: agency implementation and deviations", "citation": "FAR overhaul FAQs", "issuer": "FAR Council", "instrument_type": "Guidance", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Use the agency-issued deviation and its instructions to establish applicability; model overhaul text alone is not an agency implementation decision.", "applies_when": "An acquisition action touches a rewritten FAR part.", "required_action": "Identify the agency adoption instrument, revision, effective date, transition instructions, and applicable supplement.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR overhaul FAQs", "source_ids": [ "RSRC-0001" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0002", "title": "DoD overhaul deviation register", "citation": "DARS RFO class deviations", "issuer": "DoD DARS", "instrument_type": "Source register", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "This official register identifies DoD overhaul deviations and attachments. Read the signed deviation and attachments together.", "applies_when": "A FAR/DFARS baseline provision is being used for a DoD action.", "required_action": "Check the relevant part, latest revision and attachment; retain historical clause identifiers for existing-contract research.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DARS RFO class deviations", "source_ids": [ "RSRC-0002" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0003", "title": "Archived DAF reference: DAF contracting supplement and mandatory procedures", "citation": "DAFFARS", "issuer": "SAF/AQC", "instrument_type": "Regulation", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The public DAFFARS pages are labeled ARCHIVE (03/18/2026). This record preserves historical navigation; obtain current DAF Contracting Compass and policy instructions before relying on its procedures or thresholds.", "applies_when": "Historical research or tracing predecessor procedures. Current applicability has not been established.", "required_action": "Use the current DAF Contracting Compass and signed policy/delegation instructions; do not carry forward archived legal-review thresholds automatically.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DAFFARS", "source_ids": [ "RSRC-0003" ], "limitations": "Public archive label and successor pointer reviewed; actual Compass contents and rescission scope were not accessed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current source discovery route", "target": "RULE-0095" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Archived; current successor contents unavailable" }, { "id": "RULE-0004", "title": "Archived DAF reference: Contracting authority and legal coordination", "citation": "DAFFARS 5301.602-2", "issuer": "SAF/AQC", "instrument_type": "Regulation", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The public DAFFARS pages are labeled ARCHIVE (03/18/2026). This record preserves historical navigation; obtain current DAF Contracting Compass and policy instructions before relying on its procedures or thresholds.", "applies_when": "Historical research or tracing predecessor procedures. Current applicability has not been established.", "required_action": "Use the current DAF Contracting Compass and signed policy/delegation instructions; do not carry forward archived legal-review thresholds automatically.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DAFFARS 5301.602-2", "source_ids": [ "RSRC-0004" ], "limitations": "Public archive label and successor pointer reviewed; actual Compass contents and rescission scope were not accessed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current source discovery route", "target": "RULE-0095" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Archived; current successor contents unavailable" }, { "id": "RULE-0005", "title": "Procurement reform executive direction", "citation": "EO 14275", "issuer": "President", "instrument_type": "Executive order", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Directs reform of the FAR; implementing regulations and agency deviations must be traced to the action.", "applies_when": "Planning under the procurement reform initiative.", "required_action": "Distinguish executive direction, model text, proposed rules and effective agency implementation.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "EO 14275", "source_ids": [ "RSRC-0005" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-04-15", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0006", "title": "Drone industrial-base and acquisition direction", "citation": "EO 14307, especially section 9", "issuer": "President", "instrument_type": "Executive order", "topic": "Drone policy", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Directs action supporting U.S. drone production and military access; implementing measures must be checked.", "applies_when": "Acquiring UAS or reviewing domestic-source and program-policy requirements.", "required_action": "Locate the implementing department policy, applicable source restrictions and approval authority; do not treat policy acceleration as a competition waiver.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Sections 3 and 9", "source_ids": [ "RSRC-0006" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-06-06", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0007", "title": "American airspace sovereignty executive direction", "citation": "EO 14305", "issuer": "President", "instrument_type": "Executive order", "topic": "Counter-UAS authority", "equipment": [ "Drone", "Counter-UAS", "Radar", "Camera" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Directs federal counter-UAS and airspace actions within applicable law.", "applies_when": "Assessing U.S. domestic detection or mitigation policy.", "required_action": "Separate domestic policy from overseas host-nation permissions and actual delegated mitigation authority.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "EO 14305", "source_ids": [ "RSRC-0007" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-06-06", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0008", "title": "Federal Acquisition Regulations System", "citation": "FAR Part 1", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Authority, deviations and applicability of FAR changes.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Identify effective-date rules, deviations, warrant limits and written COR delegation. A COR cannot modify contract terms.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 1.108, 1.4, 1.6", "source_ids": [ "RSRC-0008" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Current COR implementation", "target": "RULE-0172" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Codified FAR Part 1 baseline; 2026-O0002 Revision 1 directs adopted RFO FAR/DFARS/PGI Part 1/201. Selected COR implementation is in RULE-0172 through RULE-0177." }, { "id": "RULE-0009", "title": "Improper Business Practices and Personal Conflicts of Interest", "citation": "FAR Part 3", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Integrity", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Procurement integrity and conflicts safeguards.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Protect source-selection information and assess prohibited conduct and personal conflicts in covered contractor functions.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 3.104 and 3.11", "source_ids": [ "RSRC-0009" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "separately reviewed ethics requirement", "target": "RULE-0196" }, { "type": "separately reviewed ethics requirement", "target": "RULE-0199" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0010", "title": "Administrative Matters", "citation": "FAR Part 4", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Supply chain and security", "equipment": [ "Camera", "C2", "Software", "Drone" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Administrative, registration and security requirements.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Screen baseline telecom/video, software and supply-chain prohibitions, and compare the adopted RFO security text before selecting clauses.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 4.11, 4.19–4.23", "source_ids": [ "RSRC-0010" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0277" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0011", "title": "Competition Requirements", "citation": "FAR Part 6", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Competition", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Competition and statutory exceptions.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine whether Part 6 governs the action; identify authority and approval requirements for an exception. Urgency is not a blanket waiver.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 6.1–6.3", "source_ids": [ "RSRC-0011" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0012", "title": "Acquisition Planning", "citation": "FAR Part 7", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Planning", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Acquisition planning and governmental functions.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Document acquisition planning, government responsibilities and contractor-role boundaries.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 7.1, 7.5", "source_ids": [ "RSRC-0012" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0206" }, { "type": "related requirement", "target": "RULE-0207" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0013", "title": "Required Sources of Supplies and Services", "citation": "FAR Part 8", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Required sources and schedule ordering.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Check required sources and the applicable ordering rules; compare RFO transition and agency implementation.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 8.002 and 8.4", "source_ids": [ "RSRC-0013" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "separately reviewed software requirement", "target": "RULE-0204" }, { "type": "separately reviewed software requirement", "target": "RULE-0205" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0014", "title": "Contractor Qualifications", "citation": "FAR Part 9", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Integrity", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Responsibility, exclusions and organizational conflicts.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Check responsibility, current exclusions and actual or potential organizational conflicts, including integrator roles.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 9.1, 9.4, 9.5", "source_ids": [ "RSRC-0014" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "selected first-article requirement", "target": "RULE-0225" }, { "type": "selected first-article requirement", "target": "RULE-0226" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0015", "title": "Market Research", "citation": "FAR Part 10", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Planning", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Market research supporting requirements and strategy.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Record research suited to the action, commercial availability, competition and integration constraints.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 10.001–10.002", "source_ids": [ "RSRC-0015" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0016", "title": "Describing Agency Needs", "citation": "FAR Part 11", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Planning", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Requirements and brand-name restrictions.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Use performance requirements where practicable and document support for restrictive or brand-name specifications.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 11.002 and 11.104–11.105", "source_ids": [ "RSRC-0016" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0017", "title": "Acquisition of Commercial Products and Commercial Services", "citation": "FAR Part 12", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Commercial acquisition procedures and terms.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Establish commerciality and applicable terms; commercial status does not eliminate statutory security restrictions.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 12", "source_ids": [ "RSRC-0017" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Additional current pricing implementation", "target": "RULE-0161" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0018", "title": "Simplified Acquisition Procedures", "citation": "FAR Part 13", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Simplified purchasing and competition.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine current thresholds, special authority conditions and competition/documentation requirements; do not split requirements to avoid thresholds.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 13", "source_ids": [ "RSRC-0018" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0019", "title": "Contracting by Negotiation", "citation": "FAR Part 15", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Negotiated acquisition and pricing support.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Select evaluation approach and obtain the required cost or price support, including the basis for any exception.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 15.3 and 15.4", "source_ids": [ "RSRC-0019" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Additional current pricing implementation", "target": "RULE-0168" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Codified baseline reference; 2026-O0048 Revision 1 directs adopted RFO FAR/DFARS/PGI Part 15 text. See RULE-0168-0171 for selected implementation." }, { "id": "RULE-0020", "title": "Types of Contracts", "citation": "FAR Part 16", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Orders and contract types", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Contract-type selection and indefinite-delivery ordering.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Check vehicle scope, ordering period, ceiling, authorized users, order type and competition rules. Distinguish single-award from multiple-award ordering.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 16.3, 16.5, 16.6", "source_ids": [ "RSRC-0020" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "See later or focused research", "target": "RULE-0113" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0021", "title": "Special Contracting Methods", "citation": "FAR Part 17", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Options and interagency", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Options and interagency acquisitions.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Check option conditions and timeliness, funds, price and need; identify the authority for interagency support.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 17.2 and 17.5", "source_ids": [ "RSRC-0021" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "See later or focused research", "target": "RULE-0114" }, { "type": "related requirement", "target": "RULE-0259" }, { "type": "related requirement", "target": "RULE-0260" }, { "type": "related requirement", "target": "RULE-0261" }, { "type": "related requirement", "target": "RULE-0262" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0022", "title": "Emergency Acquisitions", "citation": "FAR Part 18", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Emergency acquisition flexibilities.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Identify the actual emergency authority, activation conditions and documentation; retain requirements not expressly changed.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 18", "source_ids": [ "RSRC-0022" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0023", "title": "Small Business Programs", "citation": "FAR Part 19", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Competition", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Small-business planning and subcontracting.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine territorial and action-specific applicability, set-aside obligations and subcontracting-plan requirements.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 19", "source_ids": [ "RSRC-0023" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0024", "title": "Application of Labor Laws to Government Acquisitions", "citation": "FAR Part 22", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Labor requirements and territorial limits.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Distinguish U.S. labor-clause scope from host-nation employment rules and overseas personnel status.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 22", "source_ids": [ "RSRC-0024" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0025", "title": "Foreign Acquisition", "citation": "FAR Part 25", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Supply chain and security", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Foreign acquisition and restrictions.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Assess the acquisition, product origin, place of use, agreements and exceptions; foreign manufacture is not one universal pass/fail test.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 25.1, 25.4, 25.7, 25.8", "source_ids": [ "RSRC-0025" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0026", "title": "Patents, Data, and Copyrights", "citation": "FAR Part 27", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Data and software rights", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Data and software rights.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Identify deliverables and license rights; coordinate with DFARS treatment and distinguish delivery from license scope.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 27", "source_ids": [ "RSRC-0026" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0027", "title": "Bonds and Insurance", "citation": "FAR Part 28", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Insurance including overseas work.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine Defense Base Act and other insurance applicability and any authorized waiver; do not infer exemption from country alone.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 28.3", "source_ids": [ "RSRC-0027" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0028", "title": "Taxes", "citation": "FAR Part 29", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Federal and foreign taxes.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Identify tax treatment, exemptions and supporting documentation rather than assuming all overseas purchases are tax-free.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 29.4", "source_ids": [ "RSRC-0028" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0029", "title": "Contract Cost Principles and Procedures", "citation": "FAR Part 31", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Cost administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Cost allowability and allocability.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Assess reasonableness, allocability, applicable cost principles and contract terms; distinguish allowable cost from negotiated fee.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 31.2", "source_ids": [ "RSRC-0029" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0030", "title": "Contract Financing", "citation": "FAR Part 32", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Funding, financing and payments.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Establish funds availability and applicable funding clauses; assess payment and financing rules for the selected contract type.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 32.7, 32.9", "source_ids": [ "RSRC-0030" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0031", "title": "Protests, Disputes, and Appeals", "citation": "FAR Part 33", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Protest and disputes procedures.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Identify the governing process, deadlines and responsible officials; preserve records supporting the decision.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 33.1–33.2", "source_ids": [ "RSRC-0031" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0032", "title": "Construction and Architect-Engineer Contracts", "citation": "FAR Part 36", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Installation", "equipment": [ "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "Construction classification and procedures.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine whether work includes construction or A-E services; do not treat site work as incidental equipment merely to avoid applicable rules.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 36", "source_ids": [ "RSRC-0032" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0033", "title": "Service Contracting", "citation": "FAR Part 37", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Services", "equipment": [ "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Services acquisition and personal-services boundaries.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Define measurable outcomes, performance surveillance and permissible contractor roles.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 37.1, 37.6", "source_ids": [ "RSRC-0033" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Current COR implementation", "target": "RULE-0172" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0034", "title": "Acquisition of Information Technology", "citation": "FAR Part 39", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Cybersecurity", "equipment": [ "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "IT acquisition requirements.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Determine IT-specific acquisition requirements and coordinate cyber, accessibility and system integration obligations.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 39", "source_ids": [ "RSRC-0034" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0035", "title": "Contract Administration and Audit Services", "citation": "FAR Part 42", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Administration, audits, performance and closeout.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Establish administration responsibilities, audit support, performance evaluations and closeout prerequisites.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 42.1, 42.3, 42.15", "source_ids": [ "RSRC-0035" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "See later or focused research", "target": "RULE-0116" }, { "type": "Additional current pricing implementation", "target": "RULE-0164" }, { "type": "Current COR implementation", "target": "RULE-0177" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0191" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0192" }, { "type": "related requirement", "target": "RULE-0224" }, { "type": "related requirement", "target": "RULE-0273" }, { "type": "related requirement", "target": "RULE-0274" }, { "type": "related requirement", "target": "RULE-0275" }, { "type": "related requirement", "target": "RULE-0276" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0036", "title": "Contract Modifications", "citation": "FAR Part 43", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Written modifications and authorized changes.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Establish authority, scope, funding and pricing before direction; separate bilateral agreements from authorized unilateral changes.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 43.1–43.2", "source_ids": [ "RSRC-0036" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Read active deviation", "target": "RULE-0086" }, { "type": "Additional current pricing implementation", "target": "RULE-0170" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0188" }, { "type": "separately reviewed software requirement", "target": "RULE-0203" }, { "type": "related requirement", "target": "RULE-0208" }, { "type": "selected first-article requirement", "target": "RULE-0227" }, { "type": "selected first-article requirement", "target": "RULE-0228" }, { "type": "selected first-article requirement", "target": "RULE-0229" }, { "type": "related laser exemption requirement", "target": "RULE-0232" }, { "type": "related laser exemption requirement", "target": "RULE-0233" }, { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0237" }, { "type": "related requirement", "target": "RULE-0266" }, { "type": "related requirement", "target": "RULE-0268" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0037", "title": "Subcontracting Policies and Procedures", "citation": "FAR Part 44", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Subcontract consent and purchasing-system oversight.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Check whether consent is required and what supporting information is necessary. Consent does not establish subcontract cost allowability.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 44.2–44.3", "source_ids": [ "RSRC-0037" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0220" }, { "type": "related requirement", "target": "RULE-0222" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0038", "title": "Government Property", "citation": "FAR Part 45", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Government-furnished and contractor-acquired property.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Define ownership, accountability, maintenance, reporting and disposition responsibilities.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 45", "source_ids": [ "RSRC-0038" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0235" }, { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0237" }, { "type": "related requirement", "target": "RULE-0238" }, { "type": "related requirement", "target": "RULE-0239" }, { "type": "related requirement", "target": "RULE-0240" }, { "type": "related requirement", "target": "RULE-0241" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0039", "title": "Quality Assurance", "citation": "FAR Part 46", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Inspection, acceptance and warranties.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Set inspection and acceptance criteria and authorized acceptance roles; distinguish acceptance from operational authorization.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 46.4–46.7", "source_ids": [ "RSRC-0039" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Additional public GPC guidance", "target": "RULE-0160" }, { "type": "Current COR implementation", "target": "RULE-0176" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0188" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0189" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0193" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0194" }, { "type": "selected current quality-assurance implementation", "target": "RULE-0195" }, { "type": "selected first-article requirement", "target": "RULE-0225" }, { "type": "selected first-article requirement", "target": "RULE-0227" }, { "type": "related laser exemption requirement", "target": "RULE-0233" }, { "type": "related requirement", "target": "RULE-0238" }, { "type": "related requirement", "target": "RULE-0242" }, { "type": "related requirement", "target": "RULE-0247" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0040", "title": "Termination of Contracts", "citation": "FAR Part 49", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Termination procedures.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Select the legally applicable termination process and coordinate notices, settlement and property actions.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 49", "source_ids": [ "RSRC-0040" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0041", "title": "Solicitation Provisions and Contract Clauses", "citation": "FAR Part 52", "issuer": "FAR Council", "instrument_type": "Regulation", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Clause prescriptions, versions and incorporation.", "applies_when": "The action falls within the cited part; check agency deviations and territorial, dollar and contract-type conditions.", "required_action": "Use the prescription and actual applicable edition; distinguish a clause text from the rule requiring its inclusion.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR Part 52", "source_ids": [ "RSRC-0041" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0042", "title": "American Security Drone Act restrictions", "citation": "FAR 40.202; Pub. L. 118-31 §§1821–1833", "issuer": "Congress / FAR Council", "instrument_type": "Regulation", "topic": "Supply chain and security", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The baseline text restricts covered-entity UAS procurement and operation and addresses extensions/renewals; it includes exemptions and waiver procedures.", "applies_when": "A UAS, associated control elements or UAS operating service is acquired or federally funded.", "required_action": "Check the current FASC list, proposal contents, agency implementation and documented exemption/waiver; compare adopted RFO Part 40.", "exceptions": "Research/testing exemptions have specific conditions and decision authorities; do not assume that every DoD buy is exempt.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "FAR 40.202; Pub. L. 118-31 §§1821–1833", "source_ids": [ "RSRC-0042" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": "2028-12-22", "verified_on": null, "relationships": [ { "type": "Compare numbering and text", "target": "RULE-0043" }, { "type": "Additional public GPC guidance", "target": "RULE-0153" } ], "date_note": "Expiration stated in retained baseline FAR 40.202; later statutory amendments must be checked.", "version_state": "Baseline numbering; compare RFO and DoD implementation" }, { "id": "RULE-0043", "title": "Overhauled security framework", "citation": "RFO FAR Part 40", "issuer": "FAR Council", "instrument_type": "Model deviation text", "topic": "Supply chain and security", "equipment": [ "Drone", "Radar", "Camera", "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The model security part consolidates security requirements. Agency adoption determines its use.", "applies_when": "A security provision is being selected or compared with a legacy identifier.", "required_action": "Read the adopted DoD deviation and supplements; trace telecom, video surveillance, UAS and information-security requirements to their current prescriptions.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "RFO FAR Part 40", "source_ids": [ "RSRC-0043" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Implemented by", "target": "RULE-0084" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0044", "title": "Lead system integrator limitations", "citation": "DFARS 209.570", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Integrity", "equipment": [ "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Special statutory restrictions can apply to contractors acting as lead system integrators.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Determine whether the statutory definition and covered acquisition apply; do not label every integration contractor a covered LSI.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 209.570", "source_ids": [ "RSRC-0044" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0209" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0045", "title": "Buy American and Balance of Payments", "citation": "DFARS 225.1", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Supply chain and security", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD domestic-source and overseas balance-of-payments rules require their own applicability review.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Evaluate end-product, component, place-of-use and exception requirements.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 225.1", "source_ids": [ "RSRC-0045" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0046", "title": "Balance of Payments Program", "citation": "DFARS 225.75", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Supply chain and security", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Overseas end-product procurement can trigger Balance of Payments Program requirements.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Check the applicable exceptions, evaluation rules and clauses.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 225.75", "source_ids": [ "RSRC-0046" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0047", "title": "Export Control", "citation": "DFARS 225.79", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Defense export-control requirements affect contract performance and transfer.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Determine export authorization and contractor responsibilities before overseas delivery or technical-data access.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 225.79", "source_ids": [ "RSRC-0047" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related requirement", "target": "RULE-0278" }, { "type": "related requirement", "target": "RULE-0279" }, { "type": "related requirement", "target": "RULE-0280" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0048", "title": "Rights in Technical Data", "citation": "DFARS 227.71", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Data and software rights", "equipment": [ "Radar", "Camera", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DFARS provides specialized technical-data rights procedures.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Determine development funding, asserted restrictions, deliverables, markings and rights needed for competition and sustainment. For the adopted overhaul text, use RULE-0147 and RULE-0148 and retain the applicable existing-contract clause/license edition.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 227.71", "source_ids": [ "RSRC-0048" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related-current-record", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0248" }, { "type": "related requirement", "target": "RULE-0249" }, { "type": "related requirement", "target": "RULE-0252" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Codified baseline; compare adopted 2026-O0036 provisions effective 2026-02-01" }, { "id": "RULE-0049", "title": "Rights in Computer Software and Computer Software Documentation", "citation": "DFARS 227.72", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Data and software rights", "equipment": [ "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DFARS distinguishes commercial and noncommercial software rights.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Review license terms, noncommercial funding basis, documentation and interface deliverables. For the adopted overhaul text, use RULE-0147 and RULE-0148 and retain the applicable existing-contract clause/license edition.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 227.72", "source_ids": [ "RSRC-0049" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "related-current-record", "target": "RULE-0147" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Codified baseline; compare adopted 2026-O0036 provisions effective 2026-02-01" }, { "id": "RULE-0050", "title": "Safeguarding covered defense information and cyber incident reporting", "citation": "DFARS 252.204-7012", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The legacy clause addresses covered information protection, incident reporting and flowdown.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Check the applicable clause edition and RFO mapping, covered information, systems and required subcontract treatment.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 252.204-7012", "source_ids": [ "RSRC-0050" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0051", "title": "Cybersecurity Maturity Model Certification", "citation": "DFARS 252.204-7021", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "CMMC contracting requirements must be evaluated with implementation timing and required assessment level.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Verify current prescription, phase-in, required level and status; compare RFO clause numbering.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 204.7504 (prescription); referenced 252.204-7021 clause and 32 CFR 170.5", "source_ids": [ "RSRC-0051" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" }, { "type": "Current CMMC transition instructions", "target": "RULE-0084" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0052", "title": "Limitation of Government Obligation", "citation": "DFARS 252.232-7007", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "This clause addresses incremental funding for covered fixed-price contracts.", "applies_when": "The prescription and action-specific conditions apply; verify active deviations.", "required_action": "Check prescription and authorized funding arrangement; do not use it interchangeably with cost-reimbursement funding clauses.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DFARS 252.232-7007", "source_ids": [ "RSRC-0052" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Check agency implementation", "target": "RULE-0002" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Baseline text; check adopted overhaul deviation" }, { "id": "RULE-0053", "title": "Appropriations purpose", "citation": "31 U.S.C. 1301", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Appropriations are applied to their legally authorized objects.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Identify the appropriation and purpose authority; a funding sponsor alone does not establish availability.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "31 U.S.C. 1301", "source_ids": [ "RSRC-0053" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0054", "title": "Antideficiency limits", "citation": "31 U.S.C. 1341", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Obligations and expenditures are limited by available appropriations and statutory authority.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Confirm funds and authority before obligation or direction that could create a government liability.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "31 U.S.C. 1341", "source_ids": [ "RSRC-0054" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0055", "title": "Bona fide needs and period of availability", "citation": "31 U.S.C. 1502", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Fixed-period appropriations have time-of-availability limits.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Determine the legitimate need, performance period and applicable exception.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "31 U.S.C. 1502", "source_ids": [ "RSRC-0055" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0135" }, { "type": "related requirement", "target": "RULE-0257" }, { "type": "related requirement", "target": "RULE-0258" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0056", "title": "Recording obligations", "citation": "31 U.S.C. 1501", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Obligations require qualifying documentary support.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Establish the obligation basis and evidence required by the statute.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "31 U.S.C. 1501", "source_ids": [ "RSRC-0056" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0254" }, { "type": "related requirement", "target": "RULE-0255" }, { "type": "related requirement", "target": "RULE-0256" }, { "type": "related requirement", "target": "RULE-0257" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0057", "title": "Economy Act", "citation": "31 U.S.C. 1535", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Interagency orders under the Economy Act have statutory conditions.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Identify the actual interagency authority and required determination; do not assume every assisted acquisition uses the Economy Act.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "31 U.S.C. 1535", "source_ids": [ "RSRC-0057" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0137" }, { "type": "related-current-record", "target": "RULE-0139" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0058", "title": "Severable services crossing fiscal years", "citation": "10 U.S.C. 3133", "issuer": "Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Specified defense severable-service contracting authority permits performance across fiscal years within statutory limits.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Check duration, funds availability and agency implementing rules.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "10 U.S.C. 3133", "source_ids": [ "RSRC-0058" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0133" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0059", "title": "DoD counter-UAS protection authority", "citation": "10 U.S.C. 130i", "issuer": "Congress", "instrument_type": "Statute", "topic": "Counter-UAS authority", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD has a conditioned statutory authority to protect certain facilities and assets from UAS threats.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Identify designated facilities/assets, authorized personnel, current delegations and geographic applicability; a purchase is not an employment authorization.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "10 U.S.C. 130i", "source_ids": [ "RSRC-0059" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately. P.L. 119-60 §1707 contains material later amendments; this snapshot is not the complete current text.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0117" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; read the FY2026 NDAA §1707 amendment in RULE-0117" }, { "id": "RULE-0060", "title": "Prototype other transactions", "citation": "10 U.S.C. 4022", "issuer": "Congress", "instrument_type": "Statute", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Prototype transaction authority has eligibility, approval and follow-on conditions.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Verify prototype purpose, participants, competition and follow-on requirements; do not treat OT authority as a general procurement shortcut.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "10 U.S.C. 4022", "source_ids": [ "RSRC-0060" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0061", "title": "Commercial solutions openings", "citation": "10 U.S.C. 3458", "issuer": "Congress", "instrument_type": "Statute", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Competitive selection authority for innovative commercial products and services has defined conditions.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Check the current statutory and implementing scope and documentation.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "10 U.S.C. 3458", "source_ids": [ "RSRC-0061" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0062", "title": "Defense acquisition competition", "citation": "10 U.S.C. 3201", "issuer": "Congress", "instrument_type": "Statute", "topic": "Competition", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Defense procurement competition has statutory requirements and exceptions.", "applies_when": "The action falls within this statute; apply implementing rules and amendments.", "required_action": "Read this authority with applicable FAR/DFARS procedures and the action-specific competition regime.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "10 U.S.C. 3201", "source_ids": [ "RSRC-0062" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. GovInfo redirect may provide a historical annual edition; later amendments and current OLRC text must be checked separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2024 annual U.S. Code snapshot; current amendments unresolved" }, { "id": "RULE-0063", "title": "Spectrum supportability", "citation": "DoDI 4650.01", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Spectrum", "equipment": [ "Radar", "Drone", "Counter-UAS", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Spectrum-dependent acquisition requires spectrum-supportability consideration.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Identify certification, frequency assignment and host-nation coordination requirements early; equipment approval and operational frequency permission are distinct.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DoDI 4650.01", "source_ids": [ "RSRC-0063" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0219" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0064", "title": "Risk Management Framework", "citation": "DoDI 8510.01", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Radar", "Camera" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD system cybersecurity uses an authorization and risk-management process.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Define system boundary, authorizing official and required cybersecurity deliverables; contractor certification does not establish a system ATO.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DoDI 8510.01", "source_ids": [ "RSRC-0064" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0143" }, { "type": "related requirement", "target": "RULE-0215" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0065", "title": "Cybersecurity in acquisition", "citation": "DoDI 5000.90", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Radar", "Camera" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Acquisition cybersecurity must be addressed through the lifecycle.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Integrate cyber requirements, testing and sustainment responsibilities into the acquisition plan.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0065" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2020-12-31", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0212" }, { "type": "related requirement", "target": "RULE-0213" } ], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0066", "title": "Intellectual property acquisition and licensing", "citation": "DoDI 5010.44", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Data and software rights", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD policy addresses acquisition and licensing of intellectual property.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Plan rights and delivery requirements against integration, sustainment and future competition needs.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0066" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2019-10-16", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0067", "title": "Test and evaluation", "citation": "DoDI 5000.89", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD test and evaluation policy establishes lifecycle responsibilities.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Use RULE-0120 for the later OT&E/LFT&E policy; determine remaining applicability of 5000.89 and other current test issuances.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0067" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. Reconcile DoDI 5000.98 operational/live-fire T&E and newer development/cyber T&E issuances before selecting current responsibilities.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2020-11-19", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0120" } ], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "2020 retained edition; OT&E/LFT&E information superseded by DoDI 5000.98 (RULE-0120)" }, { "id": "RULE-0068", "title": "Product support management", "citation": "DoDI 5000.91", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Services", "equipment": [ "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoD product-support policy addresses lifecycle sustainment.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Determine support strategy, responsibilities, technical data and sustainment resources.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0068" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2021-11-04", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0069", "title": "Software acquisition pathway", "citation": "DoDI 5000.87", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Acquisition pathways", "equipment": [ "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The software acquisition pathway has tailored policy and governance.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Confirm pathway designation and required decisions; the pathway is not itself a contracting authority.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0069" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2020-10-02", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0070", "title": "Middle tier of acquisition", "citation": "DoDI 5000.80", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Middle-tier policy addresses rapid prototyping and rapid fielding.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Confirm eligibility and approval; separately select and support the contracting instrument.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0070" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2024-11-25", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0071", "title": "Urgent capability acquisition", "citation": "DoDI 5000.81", "issuer": "DoD", "instrument_type": "Department policy", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Urgent capability policy provides a defined acquisition process.", "applies_when": "The issuance applies to the program, system or acquisition pathway.", "required_action": "Verify urgent-need validation, delegated decisions and continuing contracting requirements.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Cover/purpose; applicability and policy sections", "source_ids": [ "RSRC-0071" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2019-12-31", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0110" } ], "date_note": "Effective date of retained edition/change, not proof that no later issuance exists.", "version_state": "Retained official PDF; live currency unresolved" }, { "id": "RULE-0072", "title": "DoD financial management regulation", "citation": "DoD FMR, Volumes 2A, 3, 5, 10, 11A and 14", "issuer": "DoD Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The FMR organizes budget, funds-control, payment, reimbursable and administrative-control requirements.", "applies_when": "Selecting funds or administering financial obligations.", "required_action": "Use the September 2026 policy directory, separate supplemental procedures, authoritative guidance and policy memoranda; begin with RULE-0128 and the subject-specific records.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DoD FMR, Volumes 2A, 3, 5, 10, 11A and 14", "source_ids": [ "RSRC-0072" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0128" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Navigation source; September 2026 reorganization addressed in RULE-0128" }, { "id": "RULE-0073", "title": "Current enactments and appropriations research", "citation": "Congress.gov public laws", "issuer": "Congress", "instrument_type": "Source register", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Use enacted law and the relevant fiscal year to establish appropriation-specific restrictions.", "applies_when": "An action depends on annual NDAA, appropriations, continuing resolution or transfer authority.", "required_action": "Locate the enacted instrument and exact provision; confirm dates and restrictions. This directory is not a determination that FY2027 funding is available.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Congress.gov public laws", "source_ids": [ "RSRC-0073" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0074", "title": "Export administration regulations", "citation": "15 CFR Parts 730–774", "issuer": "Commerce BIS", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The EAR governs covered exports, reexports and transfers.", "applies_when": "Equipment, software or technology is subject to the EAR.", "required_action": "Classify the item, destination, end use and end user and determine authorization requirements; exemptions require their own support.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "15 CFR Parts 730–774", "source_ids": [ "RSRC-0074" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related laser exemption requirement", "target": "RULE-0234" }, { "type": "related requirement", "target": "RULE-0278" }, { "type": "related requirement", "target": "RULE-0279" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0075", "title": "International Traffic in Arms Regulations", "citation": "22 CFR Parts 120–130", "issuer": "State DDTC", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "Effector", "Radar", "C2", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "ITAR controls covered defense articles, technical data and defense services.", "applies_when": "The item or service is ITAR-controlled.", "required_action": "Determine jurisdiction, authorization, recipients and transfer limits before performance.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "22 CFR Parts 120–130", "source_ids": [ "RSRC-0075" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related laser exemption requirement", "target": "RULE-0234" }, { "type": "related requirement", "target": "RULE-0281" }, { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0283" }, { "type": "related requirement", "target": "RULE-0284" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0076", "title": "Sanctions programs", "citation": "OFAC sanctions programs and country information", "issuer": "Treasury OFAC", "instrument_type": "Source register", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Sanctions are program-specific and change over time.", "applies_when": "The transaction, party, destination or payment may be covered.", "required_action": "Check the actual current program and licenses; country coverage in this library is not permission to transact.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "OFAC sanctions programs and country information", "source_ids": [ "RSRC-0076" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0077", "title": "NATO status of forces agreement", "citation": "NATO SOFA, Articles II, III, VII, IX and XI", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Treaty-specific", "summary": "Defines status-related arrangements between parties, including respect for receiving-state law and customs matters.", "applies_when": "The parties, persons, territory and activity fall within the treaty and implementing arrangements.", "required_action": "Establish applicability and supplemental agreements; do not assume all contractors are members of the civilian component.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "NATO SOFA, Articles II, III, VII, IX and XI", "source_ids": [ "RSRC-0077" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0149" }, { "type": "Selected current USEUCOM customs implementation", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0285" }, { "type": "related requirement", "target": "RULE-0286" }, { "type": "related requirement", "target": "RULE-0289" }, { "type": "related requirement", "target": "RULE-0290" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0078", "title": "Partnership for Peace SOFA framework", "citation": "PfP SOFA", "issuer": "NATO", "instrument_type": "Guidance", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Treaty-specific", "summary": "Explains the PfP status-of-forces framework.", "applies_when": "Considering status arrangements outside NATO membership.", "required_action": "Verify ratification, entry into force, parties and applicable agreements using the actual treaty instruments.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "PfP SOFA", "source_ids": [ "RSRC-0078" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0079", "title": "Germany contractor personnel procedures", "citation": "AEA Regulation 715-9", "issuer": "USAREUR-AF", "instrument_type": "Command policy", "topic": "Overseas execution", "equipment": [ "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany", "summary": "Addresses covered contractor personnel status in Germany.", "applies_when": "Contractor personnel seek status under the relevant Germany arrangements.", "required_action": "Review categories and procedures with DOCPER and the supported service; do not assume Army publication means automatic exclusion or inclusion for a USAF action.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "AEA Regulation 715-9", "source_ids": [ "RSRC-0079" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0111" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0080", "title": "European data protection scope", "citation": "Regulation (EU) 2016/679, Articles 2, 3, 6 and 9", "issuer": "European Union", "instrument_type": "Regulation", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "EU scope assessment", "summary": "GDPR contains material and territorial scope rules and lawful-processing conditions.", "applies_when": "Camera or C2 data involves identifiable people and processing falls within the regulation.", "required_action": "Determine actor, purpose, jurisdiction and exemptions; national-security exclusions do not justify assuming every contractor processing activity is exempt.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Regulation (EU) 2016/679, Articles 2, 3, 6 and 9", "source_ids": [ "RSRC-0080" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. Original publication is retained; use EUR-Lex consolidated versions and national implementation for a current determination.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0123" }, { "type": "related requirement", "target": "RULE-0221" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original EU instrument; check consolidated amendments" }, { "id": "RULE-0081", "title": "European aviation military/state-aircraft boundary", "citation": "Regulation (EU) 2018/1139, Article 2", "issuer": "European Union", "instrument_type": "Regulation", "topic": "Aviation", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "EU scope assessment", "summary": "The aviation framework distinguishes covered civil aviation from specified state activities and aircraft.", "applies_when": "Assessing European UAS flight requirements.", "required_action": "Determine civil/state status and national rules; do not impose civil drone rules universally on military activity.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Regulation (EU) 2018/1139, Article 2", "source_ids": [ "RSRC-0081" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. Original publication is retained; use EUR-Lex consolidated versions and national implementation for a current determination.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0124" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original EU instrument; check consolidated amendments" }, { "id": "RULE-0082", "title": "European civil UAS operation framework", "citation": "Implementing Regulation (EU) 2019/947", "issuer": "European Union", "instrument_type": "Regulation", "topic": "Aviation", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "EU scope assessment", "summary": "Establishes rules for covered UAS operations.", "applies_when": "The operation falls within the civil UAS regime.", "required_action": "Check category, authorization and national geographical zones; separately resolve state-aircraft and defense exceptions.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Implementing Regulation (EU) 2019/947", "source_ids": [ "RSRC-0082" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. Original publication is retained; use EUR-Lex consolidated versions and national implementation for a current determination.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original EU instrument; check consolidated amendments" }, { "id": "RULE-0083", "title": "European radio equipment market-access boundary", "citation": "Directive 2014/53/EU, Article 1", "issuer": "European Union", "instrument_type": "Directive", "topic": "Spectrum", "equipment": [ "Radar", "C2", "Drone" ], "stages": [ "New acquisition", "Existing vehicle/order" ], "jurisdiction": "EU scope assessment", "summary": "Radio-equipment market-access rules contain scope exclusions, including specified defense and state-security activities.", "applies_when": "Placing relevant radio equipment on the market or procuring mixed civil/defense products.", "required_action": "Check national implementation and product scope; CE marking does not establish permission to transmit on a host-nation frequency.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Directive 2014/53/EU, Article 1", "source_ids": [ "RSRC-0083" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated. Original publication is retained; use EUR-Lex consolidated versions and national implementation for a current determination.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original EU instrument; check consolidated amendments" }, { "id": "RULE-0084", "title": "DoD security overhaul signed deviation", "citation": "Class Deviation 2026-O0025, Revision 3", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Directs use of revised FAR 40, DFARS 240 and PGI 240. It also directs action on CMMC requirements in new and existing solicitations/contracts; see the memorandum before using baseline CMMC prescriptions.", "applies_when": "An action is within the deviation scope and transition instructions.", "required_action": "Read the signed applicability and implementation instructions with DFARS and PGI attachments.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Memorandum pages 1–4; attached DFARS/PGI text", "source_ids": [ "RSRC-0084" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Operative attachment", "target": "RULE-0085" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0085", "title": "DoD security overhaul attachment", "citation": "2026-O0025 Rev. 3, Attachment 1: DFARS 240", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Supply chain and security", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Contains the operative defense security text accompanying the signed deviation.", "applies_when": "The signed deviation applies to the action.", "required_action": "Use exact clause prescriptions and applicability conditions; compare legacy citations rather than assuming identical numbering.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "2026-O0025 Rev. 3, Attachment 1: DFARS 240", "source_ids": [ "RSRC-0085" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0086", "title": "DoD modifications overhaul signed deviation", "citation": "Class Deviation 2026-O0034, Revision 1", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Directs revised FAR 43/DFARS 243 procedures and implements treatment of unilateral insertion of an executive-order clause as a change under FAR 52.243-4.", "applies_when": "The action is subject to its effective-date and applicability instructions.", "required_action": "Read the signed deviation and 10 U.S.C. 3862(c) applicability before unilateral insertion of executive-order clauses; assess changes and equitable-adjustment requirements.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Memorandum pages 1–2; attachment DFARS 243 and 252.243-7001", "source_ids": [ "RSRC-0086" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0134" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0087", "title": "Germany frequency assignment", "citation": "TKG §91", "issuer": "German legislature", "instrument_type": "Statute", "topic": "Spectrum", "equipment": [ "Radar", "Drone", "Counter-UAS", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany", "summary": "German telecommunications law generally requires prior frequency assignment unless otherwise provided.", "applies_when": "Frequency use in Germany; evaluate military arrangements and statutory exceptions.", "required_action": "Resolve the relevant assignment route and military spectrum coordination before transmission; procurement alone does not confer spectrum rights.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "TKG §91", "source_ids": [ "RSRC-0087" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0088", "title": "United Kingdom radio licensing", "citation": "Wireless Telegraphy Act 2006, section 8", "issuer": "UK Parliament", "instrument_type": "Statute", "topic": "Spectrum", "equipment": [ "Radar", "Drone", "Counter-UAS", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom", "summary": "Section 8 addresses radio licensing and exemptions.", "applies_when": "Installing or using radio apparatus within the provision’s scope.", "required_action": "Determine licensing/exemption and Crown/visiting-force treatment with the relevant authority; do not apply civilian licensing assumptions universally.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Wireless Telegraphy Act 2006, section 8", "source_ids": [ "RSRC-0088" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0089", "title": "Germany video surveillance", "citation": "BDSG §4", "issuer": "German legislature", "instrument_type": "Statute", "topic": "Privacy", "equipment": [ "Camera", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany", "summary": "The provision addresses video surveillance of publicly accessible areas subject to specified conditions.", "applies_when": "The actor and processing fall within the national provision; assess GDPR and special defense/status arrangements.", "required_action": "Assess purpose, necessity, notice, retention and applicable legal regime before specifying camera analytics or recording.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "BDSG §4", "source_ids": [ "RSRC-0089" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0090", "title": "Germany military aviation exceptions", "citation": "LuftVG §30", "issuer": "German legislature", "instrument_type": "Statute", "topic": "Aviation", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany", "summary": "German aviation law provides specified treatment for military and other state aviation, including conditions for foreign forces.", "applies_when": "UAS flight or testing in Germany potentially relies on military exceptions.", "required_action": "Verify the actual permission and conditions; neither civil drone permission nor military ownership alone settles all flight requirements.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "LuftVG §30", "source_ids": [ "RSRC-0090" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0091", "title": "US statutory drone procurement restriction", "citation": "FY2020 NDAA §848, Pub. L. 116-92", "issuer": "Congress", "instrument_type": "Statute", "topic": "Supply chain and security", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 848 established a defense procurement restriction on specified foreign UAS and components, with exceptions and waiver provisions.", "applies_when": "DoD procurement of UAS or components within the provision as amended.", "required_action": "Read the enacted section, subsequent amendments and current implementing policy separately from the American Security Drone Act.", "exceptions": "Original enactment is historical evidence; current amended requirements remain to be reconciled.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Section 848", "source_ids": [ "RSRC-0091" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Amended DoD implementation", "target": "RULE-0085" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original enactment; use amended implementation for current action" }, { "id": "RULE-0092", "title": "Covered telecommunications and video surveillance statute", "citation": "FY2019 NDAA §889, Pub. L. 115-232", "issuer": "Congress", "instrument_type": "Statute", "topic": "Supply chain and security", "equipment": [ "Camera", "C2", "Radar", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 889 established procurement and contractor-use restrictions involving covered telecommunications and video-surveillance equipment or services.", "applies_when": "A covered acquisition or contractor-use condition under implementing rules.", "required_action": "Distinguish equipment supplied to Government from contractor-use restrictions, exceptions and waiver conditions; check current implementation.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Section 889", "source_ids": [ "RSRC-0092" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current FAR security framework", "target": "RULE-0043" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Original enactment; use amended implementation for current action" }, { "id": "RULE-0093", "title": "CMMC program regulation", "citation": "32 CFR Part 170", "issuer": "DoD", "instrument_type": "Regulation", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The program regulation defines CMMC assessment and related requirements.", "applies_when": "A contract action requires a CMMC level under the applicable acquisition prescription.", "required_action": "Read program requirements and phase-in alongside the current DFARS/deviation prescription.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "32 CFR Part 170", "source_ids": [ "RSRC-0093" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Acquisition implementation may differ", "target": "RULE-0084" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Retrieved edition; confirm amendments and applicability" }, { "id": "RULE-0094", "title": "Expense versus investment interim policy", "citation": "FMR policy memoranda: Volume 2A", "issuer": "DoD Comptroller", "instrument_type": "Source register", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The official FMR memorandum directory identifies expense/investment and other interim policy. The September 2026 reorganization requires review of both new policy volumes and each memorandum’s scope/sunset.", "applies_when": "Selecting appropriation treatment for equipment or systems.", "required_action": "Follow RULE-0128 through RULE-0142 for selected current financial-policy findings; reconcile historical FPM23-02 and annual legislation before using a threshold.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Official policy-memoranda directory, Volume 2A/3/4 listings", "source_ids": [ "RSRC-0094" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0128" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Directory reviewed 2026-10-03; not blanket current applicability of every listed memo" }, { "id": "RULE-0095", "title": "DAF Contracting Compass access route", "citation": "DAF Contracting Compass Part 1 (official pointer)", "issuer": "SAF/AQC", "instrument_type": "Source register", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The archived public DAF page links to the Contracting Compass on Air Force Contracting Central. The successor contents were not accessed.", "applies_when": "A current DAF contracting instruction or approval route is needed.", "required_action": "Use the official Compass link and obtain the applicable current signed instructions through authorized channels; this library records the gap.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DAF Contracting Compass Part 1 (official pointer)", "source_ids": [ "RSRC-0095" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Successor pointer only; contents unavailable" }, { "id": "RULE-0096", "title": "DoD foreign UAS and detection-system restrictions", "citation": "RFO DFARS 240.7008; 252.240-7993/-7994", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Supply chain and security", "equipment": [ "Drone", "Counter-UAS", "Radar", "Camera", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised defense text covers certain foreign UAS/components, detection or identification systems, and contracting with entities operating specified equipment.", "applies_when": "An acquisition falls within the definitions and prohibition at 240.7008.", "required_action": "Review origin of components, software, connectivity/storage, detection-system manufacture, contractor operation and the prescribed representation/clause.", "exceptions": "Use the specific exceptions/waivers in the clause and statute; a general statement of NDAA compliance is insufficient.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Attachment 1, 240.7008 and clause 252.240-7994", "source_ids": [ "RSRC-0085", "RSRC-0084" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Read signed implementation instructions", "target": "RULE-0084" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "September 2026 DoD deviation; check later changes" }, { "id": "RULE-0097", "title": "CMMC changes reaching existing contracts", "citation": "2026-O0025 Rev. 3, memorandum paragraph (b)", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Cybersecurity", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The memorandum suspends the November 2026 Phase 2 transition, permits specified self-assessments, preserves baseline NIST SP 800-171 Rev. 2 compliance and directs corresponding solicitation/contract changes.", "applies_when": "An action or existing requirement is affected by the referenced CMMC suspension instructions.", "required_action": "Coordinate with requiring activities and follow the memorandum’s amendment/modification timing, including before the next option or scheduled administrative modification.", "exceptions": "Read the memorandum and underlying CIO instruction; this is not removal of all cybersecurity obligations.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Signed memorandum pages 2–3", "source_ids": [ "RSRC-0084" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Read signed implementation instructions", "target": "RULE-0084" }, { "type": "See later or focused research", "target": "RULE-0114" }, { "type": "related-current-record", "target": "RULE-0151" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "September 2026 DoD deviation; check later changes" }, { "id": "RULE-0098", "title": "DoD employee-data transfer restriction", "citation": "RFO DFARS 240.374; 252.240-7992", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised defense security text restricts contractor transfers of covered individually identifiable DoD employee data to third parties.", "applies_when": "Data and activity fall within the defined coverage.", "required_action": "Evaluate analytics, hosted services and subcontract data flows; check the prescribed clause and authorized transfer basis.", "exceptions": "Exceptions include transfers necessary to perform the contract, authorized waiver, or other legally authorized circumstances.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Attachment 1, 240.374 and 252.240-7992", "source_ids": [ "RSRC-0085" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Read signed implementation instructions", "target": "RULE-0084" }, { "type": "related requirement", "target": "RULE-0223" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "September 2026 DoD deviation; check later changes" }, { "id": "RULE-0099", "title": "Covered semiconductor supply-chain prohibition", "citation": "RFO DFARS 240.7007; 252.240-7998/-7999", "issuer": "DoD DARS", "instrument_type": "Class deviation", "topic": "Supply chain and security", "equipment": [ "Radar", "Camera", "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised text implements a restriction on covered semiconductor products/services from companies knowingly providing covered products/services to Huawei.", "applies_when": "The contemplated procurement meets the defined coverage.", "required_action": "Apply definitions, representation and clause prescriptions rather than assuming every electronic component is prohibited.", "exceptions": "Check the exact statutory and implementing waiver provisions.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Attachment 1, 240.7007", "source_ids": [ "RSRC-0085" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-03", "effective_date": "2026-09-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Read signed implementation instructions", "target": "RULE-0084" } ], "date_note": "Issuance date from official DARS index; signed memorandum states effective immediately and remains in effect until rescinded or incorporated.", "version_state": "September 2026 DoD deviation; check later changes" }, { "id": "RULE-0100", "title": "Military drone acquisition policy memorandum", "citation": "Unleashing U.S. Military Drone Dominance, 2025-07-10", "issuer": "Secretary of Defense", "instrument_type": "Policy memorandum", "topic": "Drone policy", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Department implementation memorandum addressing military drone acquisition and use.", "applies_when": "The platform and acquisition are within its scope.", "required_action": "Read the signed memorandum, subsequent changes, approved-source process and delegated authority; do not infer blanket approval from the title.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "Unleashing U.S. Military Drone Dominance, 2025-07-10", "source_ids": [ "RSRC-0096" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Additional public GPC guidance", "target": "RULE-0152" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Discovered source; review pending" }, { "id": "RULE-0101", "title": "DAF integrated life-cycle management", "citation": "DAFI 63-101/20-101", "issuer": "Department of the Air Force", "instrument_type": "Department policy", "topic": "Planning", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DAF policy addresses acquisition-program and lifecycle management, including system modifications.", "applies_when": "The program/activity falls within the instruction and applicable pathway.", "required_action": "Distinguish program approval, system modification and sustainment responsibilities from the contracting instrument; check attached guidance memoranda.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DAFI 63-101/20-101", "source_ids": [ "RSRC-0097" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "open", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Discovered source; review pending" }, { "id": "RULE-0102", "title": "DAF spectrum management", "citation": "DAFI 17-220", "issuer": "Department of the Air Force", "instrument_type": "Department policy", "topic": "Spectrum", "equipment": [ "Radar", "C2", "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The retained 2021 DAF instruction assigns spectrum-management responsibilities, with focused acquisition and modification provisions linked below.", "applies_when": "The system needs spectrum support or host-nation frequency coordination.", "required_action": "Obtain the current instruction and applicable theater procedures; confirm equipment certification and frequency authorization separately.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "2021-06-08 edition, cover and ¶¶1.3, 2.2.9, 2.2.13, 3.1-3.2", "source_ids": [ "RSRC-0098" ], "limitations": "Live e-Publishing download unavailable. Retained edition supports these bounded propositions; it does not establish current theater permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2021-06-08", "effective_date": "2021-06-08", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0121" }, { "type": "See later or focused research", "target": "RULE-0122" }, { "type": "related requirement", "target": "RULE-0218" } ], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "2021-06-08 official retained edition; live currency and supplements unresolved" }, { "id": "RULE-0103", "title": "DoD non-overhaul class deviations", "citation": "DARS class deviations register", "issuer": "DoD DARS", "instrument_type": "Source register", "topic": "Authority and versions", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The general deviation register complements the separate overhaul collection.", "applies_when": "A special authority, fiscal-year measure or acquisition exception may affect the action.", "required_action": "Check the current register and signed instrument, including expiration and supersession; a listed deviation does not automatically apply.", "exceptions": "Check the cited provision and applicable implementing procedures; no blanket exception is asserted.", "approval_authority": "See the cited rule and current written delegation; no local delegation has been established by this library.", "locator": "DARS class deviations register", "source_ids": [ "RSRC-0099" ], "limitations": "Initial research summary. Recheck the official text, amendments, and agency deviations before use. No contract or acquisition action has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Unknown dates are not inferred from retrieval or website update dates.", "version_state": "Official active-deviations register reviewed 2026-10-03; each instrument has its own limits" }, { "id": "RULE-0104", "title": "FY2027 continuing resolution: availability period", "citation": "P.L. 119-103, Division A §§101, 103, 106, 108", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The FY2027 CR continues specified FY2026 activities under referenced authorities and conditions. Section 106 ends that availability at the earliest listed event, including December 11, 2026.", "applies_when": "The contemplated obligation uses funds provided by this continuing resolution.", "required_action": "Identify the covered account, incorporated conditions, enacted amendments, apportionment and allotment. Check the two earlier-termination events; December 11 is not an unconditional funding guarantee.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Division A §§101(3), 103, 106(1)-(3), 108", "source_ids": [ "RSRC-0101" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-02", "effective_date": "2026-10-01", "expiration_date": "2026-12-11", "verified_on": null, "relationships": [ { "type": "Related funding restrictions", "target": "RULE-0105" }, { "type": "Incorporates specified FY2026 conditions", "target": "RULE-0106" }, { "type": "See later or focused research", "target": "RULE-0107" }, { "type": "Related authority", "target": "RULE-0053" }, { "type": "related-current-record", "target": "RULE-0129" } ], "date_note": "Enacted 2026-09-02; FY2027 begins 2026-10-01. Section 106 can terminate availability earlier.", "version_state": "FY2027 enacted CR; original P.L. 119-103 text" }, { "id": "RULE-0105", "title": "FY2027 CR: DoD new starts and production limits", "citation": "P.L. 119-103, Division A §§102, 104, 109-110", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The CR restricts new production, production-rate increases and unfunded prior-year projects; section 110 limits funding actions to continuation purposes.", "applies_when": "A purchase, option or modification would obligate CR-provided funds.", "required_action": "Assess the funded program/activity and statutory exception. A new award is not automatically a new start, and an existing vehicle does not by itself avoid a new-start restriction.", "exceptions": "Specific enacted anomalies and section 106 conditions require account/program-specific review; do not generalize a named exception.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Division A §§102(a)-(b), 104, 109-110; inspect named anomalies such as §§126-128", "source_ids": [ "RSRC-0101" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-02", "effective_date": "2026-10-01", "expiration_date": "2026-12-11", "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0104" }, { "type": "Related authority", "target": "RULE-0030" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "FY2027 enacted CR; earlier termination and amendments must be checked" }, { "id": "RULE-0106", "title": "FY2026 defense appropriations: account and availability conditions", "citation": "P.L. 119-75, Division A, Titles II-IV and §8003", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Defense appropriations distinguish O&M, procurement and RDT&E accounts and their availability; section 8003 supplies the default fiscal-year limit unless expressly extended.", "applies_when": "Research concerns FY2026 balances or the FY2026 conditions incorporated by the FY2027 CR.", "required_action": "Read the actual account heading and applicable riders together. Identify separately the legal authority for any carryover or FY2027 CR obligation.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Division A: Operation and Maintenance, Air Force; procurement/RDT&E account headings; §8003", "source_ids": [ "RSRC-0111" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0104" }, { "type": "related-current-record", "target": "RULE-0129" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "FY2026 enactment; relevant conditions may be incorporated by the FY2027 CR" }, { "id": "RULE-0107", "title": "FY2026 lapse deviation does not establish FY2027 authority", "citation": "Class Deviation 2026-O0044; DFARS 252.232-7998", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "This deviation addresses excepted activities in advance of FY2026 funds and requires authorized bilateral contract actions. It does not extend its fiscal-year scope to FY2027.", "applies_when": "Research concerns an action using this FY2026 deviation or whether it can support a later-year obligation.", "required_action": "Check fiscal year, excepted-activity authority, required authorization and bilateral agreement. Locate separate current-year authority if needed.", "exceptions": "The memorandum excludes actions using existing appropriations available for obligation and liquidation. It remains in effect until rescinded but its stated subject remains FY2026.", "approval_authority": "Department/component guidance; if none, authorization no lower than HCA under memorandum p. 2.", "locator": "Memorandum pp. 1-2; attachment p. 3", "source_ids": [ "RSRC-0104" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-02", "effective_date": "2026-02-02", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Different fiscal-year authority", "target": "RULE-0104" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Expressly FY2026-limited despite continued register listing" }, { "id": "RULE-0108", "title": "Vendor-threat clauses for overseas performance", "citation": "2026-O0051; DFARS 252.225-7962 and 252.225-7975", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The deviation prescribes both vendor-threat mitigation and additional records-access clauses for performance outside the United States and its outlying areas, including FAR Part 12 acquisitions.", "applies_when": "Solicitations and contracts will be performed outside the United States and its outlying areas.", "required_action": "Apply both prescriptions and their subcontract provisions; identify the relevant combatant-command VTM requirements. Do not infer authority to terminate or void without the stated HCA process.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Covered procurement actions are non-delegable HCA authority on the specified notification; notice and administrative-review protections apply.", "locator": "Memorandum p. 1, paragraphs (b)-(d); attachments pp. 6-9", "source_ids": [ "RSRC-0103" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-06-11", "effective_date": "2026-06-11", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0109" }, { "type": "Related authority", "target": "RULE-0099" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0109", "title": "Vendor-threat duties during subcontract performance", "citation": "2026-O0051; DFARS 252.225-7962(c)-(d), 252.225-7975", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration", "Modification or option" ], "jurisdiction": "United States", "summary": "The prescribed clause requires subcontractor SAM checks before award and at least monthly, immediate notification of covered activities, and the specified overseas subcontract flowdowns.", "applies_when": "The applicable VTM clauses govern the performance being researched.", "required_action": "Identify required contractor diligence, reports and records access. Route exclusion/termination/voiding through the memorandum’s procedures and notice protections.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "HCA for covered procurement actions; CO written approval governs the specified continuation of a restricted subcontract.", "locator": "Attachment 1 paragraphs (c)(3)-(4), (d), PDF pp. 7-8; attachment 2 p. 9", "source_ids": [ "RSRC-0103" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-06-11", "effective_date": "2026-06-11", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Administration of prescribed clauses", "target": "RULE-0108" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0110", "title": "Rapid contracting authority can support qualifying EUCOM operations", "citation": "Class Deviation 2024-O0011; FY2024 NDAA §843", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Acquisition pathways", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "EUCOM is a named command in a temporary authority for approved rapid responses to covered operations. EUCOM sponsorship alone does not satisfy those conditions.", "applies_when": "A time-sensitive or unplanned situation meets the covered-operation definition and a covered acquisition is approved.", "required_action": "Establish the commander’s written request/determination, funds attestation, HCA approval route, instrument-specific thresholds and reporting requirements before using the flexibility.", "exceptions": "Only the covered contracts/operations defined in this deviation; earlier rescission remains possible.", "approval_authority": "HCA approval, not delegable below the senior contracting official; written combatant-commander request/determination required.", "locator": "Memorandum (A)-(C), pp. 1-4", "source_ids": [ "RSRC-0105" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2024-04-15", "effective_date": "2024-04-15", "expiration_date": "2028-09-30", "verified_on": null, "relationships": [ { "type": "Separate pathway/contracting authority", "target": "RULE-0071" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Temporary deviation through 2028-09-30 unless earlier rescinded" }, { "id": "RULE-0111", "title": "Overseas performance and Germany contractor privileges", "citation": "2026-O0041 Rev 1; DFARS/PGI 225.770", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised foreign-acquisition text requires overseas performance considerations; Germany contractor logistics support and base privileges depend on bilateral agreements.", "applies_when": "Services or supplies require performance or delivery outside the United States.", "required_action": "Address applicable host-country and operational-area conditions, support relationships and contractor status. Do not treat a U.S. award as automatic base privileges.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "DFARS 225.770, attachment 1 p. 18 (PDF p. 20); PGI 225.770", "source_ids": [ "RSRC-0106" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-01", "effective_date": "2026-07-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "National implementation remains open", "target": "RULE-0079" }, { "type": "Related authority", "target": "RULE-0025" }, { "type": "Selected current USEUCOM customs implementation", "target": "RULE-0180" }, { "type": "related requirement", "target": "RULE-0286" }, { "type": "related requirement", "target": "RULE-0287" }, { "type": "related requirement", "target": "RULE-0288" }, { "type": "related requirement", "target": "RULE-0289" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0112", "title": "Deployed-contractor rules have a defined operational scope", "citation": "2026-O0041 Rev 1; DFARS 225.771-1", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised provision addresses contractor personnel supporting forces in specified contingency, humanitarian/peacekeeping or designated military operations/exercises.", "applies_when": "Contractor personnel support deployed U.S. forces and the operation meets 225.771-1.", "required_action": "Determine the relevant operation/designation and support conditions before selecting deployed-contractor requirements.", "exceptions": "Overseas location alone does not establish this operational designation.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "DFARS 225.771-1 through 225.771-3, attachment 1 pp. 18-19", "source_ids": [ "RSRC-0106" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-01", "effective_date": "2026-07-01", "expiration_date": null, "verified_on": null, "relationships": [], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0113", "title": "Current defense ordering and fair-opportunity cross-references", "citation": "2026-O0045 Rev 1; DFARS 216.506-70, 216.507", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Orders and contract types", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised ordering provisions address SPRS risk, non-DoD ordering controls, fair opportunity and defense debriefing requirements.", "applies_when": "A task or delivery order is contemplated under the relevant contract authority.", "required_action": "Use the adopted FAR 16 text and DFARS 216 together; check SPRS, applicable fair-opportunity exceptions and debriefing prescriptions. The codified 16.505 citation is not the complete current navigation route.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Memorandum p. 1; attachment 1 DFARS 216.506-70 and 216.507", "source_ids": [ "RSRC-0108" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-15", "effective_date": "2026-07-15", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current implementation of baseline part", "target": "RULE-0020" }, { "type": "See later or focused research", "target": "RULE-0115" }, { "type": "Related authority", "target": "RULE-0002" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0114", "title": "Options: current cross-references and later CMMC instructions", "citation": "2026-O0027; DFARS 217.204-170; 2026-O0025 Rev 3", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Options and interagency", "equipment": [ "All" ], "stages": [ "Modification or option" ], "jurisdiction": "United States", "summary": "The options attachment adds SAM identity and SPRS checks. Its older CMMC certificate wording requires reconciliation with the later security deviation’s transition instructions.", "applies_when": "An option is being considered under the adopted FAR 17 framework.", "required_action": "Read FAR 17.204-1 and DFARS 217.204-170 together with 2026-O0025 Rev 3 before deciding which cybersecurity checks and modifications are due.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "DFARS 217.204-170, attachment 1 p. 8 (PDF p. 10); later security memo pp. 2-3", "source_ids": [ "RSRC-0109", "RSRC-0084" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current implementation of baseline part", "target": "RULE-0021" }, { "type": "Later CMMC transition instructions", "target": "RULE-0097" }, { "type": "related requirement", "target": "RULE-0269" }, { "type": "related requirement", "target": "RULE-0270" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "February 2026 options implementation; later September 2026 security instructions are material" }, { "id": "RULE-0115", "title": "DoD ordering periods and performance beyond them", "citation": "2026-O0027; DFARS 217.201-270", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Orders and contract types", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The specified 10 USC 3403 ordering-period framework separates contract ordering duration from performance of an order extending beyond that duration.", "applies_when": "The contract is within DFARS 217.201-270(a), not one of paragraph (b)’s excluded categories.", "required_action": "Check statutory basis, ordering-period limits and exceptions. Evaluate the separate senior-procurement-executive approval for specified performance beyond the limit.", "exceptions": "Paragraph (b) excludes specified other-authority, advisory/assistance, definite-quantity, schedule and multi-agency contracts; do not generalize to every vehicle.", "approval_authority": "Head of agency for the exceptional longer ordering period; senior procurement executive for the specified extended order performance.", "locator": "Attachment 1 pp. 7-8 (PDF pp. 9-10), paragraphs (a)-(c)", "source_ids": [ "RSRC-0109" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Related ordering rules", "target": "RULE-0113" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0116", "title": "Contract administration and questioned direct costs", "citation": "2026-O0050; DFARS/PGI 242.302-70", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Cost administration", "equipment": [ "All" ], "stages": [ "Contract administration", "Modification or option" ], "jurisdiction": "United States", "summary": "The revised administration rules allocate functions and require coordination between the procuring and administrative contracting offices for questioned direct costs.", "applies_when": "Administration delegation or incurred-cost settlement is being researched.", "required_action": "Identify the assigned function, permitted delegation, supporting records and required coordination before settling or adjusting costs.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "DFARS 242.302-70(b)(2), attachment 1 pp. 4-5; PGI 242.302-70", "source_ids": [ "RSRC-0107" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-03-06", "effective_date": "2026-03-16", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Current implementation of baseline part", "target": "RULE-0035" }, { "type": "Related authority", "target": "RULE-0029" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0117", "title": "FY2026 amendment to DoD counter-UAS authority", "citation": "P.L. 119-60 §1707 amending 10 U.S.C. 130i", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Counter-UAS authority", "equipment": [ "Counter-UAS", "Drone", "Effector", "Radar", "Camera", "C2" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 1707 adds contractors to the persons the Secretary may authorize, narrows the Title 18 override to enumerated provisions, and adds or revises safeguards.", "applies_when": "Research relies on 10 USC 130i for personnel, information collection or protection authority.", "required_action": "Read this amendment with the underlying statute and current implementing guidance. Contractor inclusion does not itself authorize any contractor, purchase or particular site.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "§1707(1)-(6), 139 Stat. 1215-1217", "source_ids": [ "RSRC-0110" ], "limitations": "Focused amendment analysis; complete current consolidated statutory text and delegations remain unresolved.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2025-12-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Amends the underlying statute after the 2024 snapshot", "target": "RULE-0059" }, { "type": "Related authority", "target": "RULE-0119" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "2025 enacted amendment; 2024 Code snapshot alone is insufficient" }, { "id": "RULE-0118", "title": "Air Force sensor-network pilot is expressly domestic", "citation": "P.L. 119-60 §1088", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Acquisition pathways", "equipment": [ "Radar", "Camera", "C2", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The Air Force civilian-sensor-network counter-UAS pilot directs selection of at least two military installations located in the United States.", "applies_when": "Section 1088 is cited as a basis for a sensor-data or C2 integration requirement.", "required_action": "Check the pilot’s purposes, location condition and program selection. Do not infer USAFE installation eligibility from its Air Force base-defense title.", "exceptions": "This record addresses the statutory pilot’s geography, not eligibility under a different authority.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "§1088(a)-(b), 139 Stat. 1059-1060", "source_ids": [ "RSRC-0110" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2025-12-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Separate statutory pilots", "target": "RULE-0119" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0119", "title": "Counter-UAS deployment pilot and readiness requirements", "citation": "P.L. 119-60 §1089", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Counter-UAS authority", "equipment": [ "Counter-UAS", "Effector", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 1089 directs a JIATF-401-led deployment pilot and specified administrative, training and sustainment steps for qualifying covered facilities/assets.", "applies_when": "A requirement is linked to this statutory pilot or its readiness direction.", "required_action": "Establish the required Secretary determination, program selection and section 130i coordination. A statutory direction does not establish local selection or completion.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "§1089(a)-(c), 139 Stat. 1060-1062", "source_ids": [ "RSRC-0110" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2025-12-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0118" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Official instrument reviewed for the cited provisions on 2026-10-03" }, { "id": "RULE-0120", "title": "OT&E and live-fire policy supersedes part of DoDI 5000.89", "citation": "DoDI 5000.98, purpose and §§1.1-1.2", "issuer": "DoD DOT&E", "instrument_type": "Department policy", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "DoDI 5000.98 expressly supersedes the OT&E/LFT&E information in DoDI 5000.89 and addresses testing across its stated system and pathway scope.", "applies_when": "The acquisition falls within the issuance’s applicability and needs operational or live-fire T&E planning.", "required_action": "Use the applicable 5000.98 responsibilities with the test organization; distinguish program T&E from contractual inspection and acceptance.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Cover/purpose; §§1.1-1.2, PDF pp. 1 and 4-5", "source_ids": [ "RSRC-0102" ], "limitations": "Partial subject-matter supersession; no claim that all of 5000.89 is rescinded. Later policy amendments remain to be checked.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2024-12-09", "effective_date": "2024-12-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Supersedes OT&E/LFT&E subject matter", "target": "RULE-0067" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "2024-12-09 official retained edition; live currency not established" }, { "id": "RULE-0121", "title": "DAF spectrum risk in design and procurement", "citation": "DAFI 17-220 (2021), ¶¶1.3, 3.1-3.2", "issuer": "Department of the Air Force", "instrument_type": "Department policy", "topic": "Spectrum", "equipment": [ "Radar", "C2", "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The 2021 instruction calls for spectrum supportability risk assessment early enough to affect spectrum-dependent system design and procurement.", "applies_when": "A radar, radio, drone link or other spectrum-dependent system is being acquired or developed.", "required_action": "Coordinate spectrum supportability and required certification/assignments with the spectrum office; establish the host-nation route for overseas use.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "¶1.3 and chapter 3; retained PDF pp. 2, 12-14", "source_ids": [ "RSRC-0098" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2021-06-08", "effective_date": "2021-06-08", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Focused spectrum acquisition provision", "target": "RULE-0102" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "2021-06-08 retained edition; current supplements and later revisions unresolved" }, { "id": "RULE-0122", "title": "Spectrum-dependent modifications need a separate review", "citation": "DAFI 17-220 (2021), ¶¶2.2.9, 2.2.13", "issuer": "Department of the Air Force", "instrument_type": "Department policy", "topic": "Modifications", "equipment": [ "Radar", "C2", "Drone", "Counter-UAS" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The instruction requires spectrum-manager approval before system/antenna changes outside assigned authorization parameters and routes host-nation coordination through that office.", "applies_when": "A modification changes the spectrum-dependent configuration or needs host-nation coordination.", "required_action": "Identify whether the contemplated change departs from the frequency authorization and coordinate before implementation; a contracting modification does not grant frequency authorization.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Retained PDF p. 12, ¶¶2.2.9 and 2.2.13", "source_ids": [ "RSRC-0098" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2021-06-08", "effective_date": "2021-06-08", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Focused spectrum modification provision", "target": "RULE-0102" }, { "type": "Related authority", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0219" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "2021-06-08 retained edition; current supplements and later revisions unresolved" }, { "id": "RULE-0123", "title": "UK defence data-protection exemption is conditional", "citation": "Data Protection Act 2018 §26", "issuer": "UK Parliament", "instrument_type": "National law", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom", "summary": "Section 26 exempts listed provisions only where required for national security or defence purposes; specified lawfulness requirements remain outside that exemption.", "applies_when": "UK GDPR applies to the personal data and a national-security or defence exemption is proposed.", "required_action": "Identify the controller, processing, specific provision and necessity for exemption; examine section 28 and other applicable provisions separately.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "§26(1)-(2), especially §26(2)(a)(i)-(iii)", "source_ids": [ "RSRC-0112" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2018-05-23", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Different jurisdictional privacy framework", "target": "RULE-0080" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Latest revised section displayed on 2026-10-03; outstanding changes must be checked" }, { "id": "RULE-0124", "title": "Spain civil UAS rules and military-use exclusion", "citation": "Real Decreto 517/2024, arts. 1, 3, 35", "issuer": "Spain BOE", "instrument_type": "National law", "topic": "Aviation", "equipment": [ "Drone", "Counter-UAS" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Spain", "summary": "The decree governs the stated civil UAS activities; article 3(2)(c) excludes military UAS and military activities/services. Covered civil operations also have equipment obligations.", "applies_when": "A drone demonstration, test or service would occur in Spanish sovereign territory or airspace.", "required_action": "Determine the operator/activity classification and applicable military or civil approval route. Exclusion from this civil decree is not a flight authorization.", "exceptions": "Article 3 includes other exclusions and applies specified duties to civil/military aerodrome managers as affected; consult the full text.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "Arts. 1, 3(1)-(2), 35; official consolidated Spanish text", "source_ids": [ "RSRC-0113" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2024-06-05", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Related EU/military scope distinction", "target": "RULE-0081" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "BOE consolidated reference reviewed 2026-10-03; English summary is a paraphrase" }, { "id": "RULE-0125", "title": "Poland treaty definitions limit contractor categories", "citation": "Poland-U.S. EDCA (2020), Article 2(e)-(g)", "issuer": "Poland official journal", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Poland", "summary": "The agreement distinguishes contractors, U.S. contractors and U.S. contractor employees using defined status conditions.", "applies_when": "A Polish treaty benefit depends on one of those categories.", "required_action": "Establish the applicable definition and implementing arrangements before applying a benefit; a U.S. contract alone is insufficient.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "English text, official journal PDF pp. 69-70", "source_ids": [ "RSRC-0116" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-12-03", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "See later or focused research", "target": "RULE-0126" }, { "type": "See later or focused research", "target": "RULE-0127" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Original 2020 treaty text; later amendments/implementation unresolved" }, { "id": "RULE-0126", "title": "Poland professional-license provision for covered personnel", "citation": "Poland-U.S. EDCA (2020), Article 10", "issuer": "Poland official journal", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Poland", "summary": "Article 10 provides a professional-license rule for covered persons serving the specified recipients in their official or contractual duties.", "applies_when": "The person, service and recipient meet Articles 2 and 10.", "required_action": "Confirm the category and duty; do not extend this provision to unrelated operating or business permissions.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "English text, official journal PDF p. 80", "source_ids": [ "RSRC-0116" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-12-03", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Defined personnel categories", "target": "RULE-0125" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Original 2020 treaty text; later amendments/implementation unresolved" }, { "id": "RULE-0127", "title": "Poland official-purchase VAT and excise provisions", "citation": "Poland-U.S. EDCA (2020), Article 19(1)-(4)", "issuer": "Poland official journal", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Poland", "summary": "Official import and purchase tax exemptions have use, documentation and implementation conditions; their procedures differ.", "applies_when": "Goods or services are acquired by or for U.S. forces for the treaty’s specified purposes.", "required_action": "Check the appropriate U.S.-forces certification and implementing forms/procedures; do not assume automatic tax relief.", "exceptions": "Read the stated scope, exclusions and any later amendments; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; this library establishes no local delegation.", "locator": "English text, official journal PDF p. 92", "source_ids": [ "RSRC-0116" ], "limitations": "Bounded proposition only. Confirm the governing version and action-specific facts; no contract has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-12-03", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "Treaty context", "target": "RULE-0125" }, { "type": "Related authority", "target": "RULE-0028" } ], "date_note": "Publication identifies the instrument edition; check the stated effective conditions and later implementation.", "version_state": "Original 2020 treaty text; implementing arrangements and amendments unresolved" }, { "id": "RULE-0128", "title": "September 2026 FMR policy and procedure navigation", "citation": "FMR September 2026 directory and transition alert", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The reorganized FMR separates policy volumes, supplemental procedures and authoritative guidance. The directory still directs users to superseding policy memoranda.", "applies_when": "Research relies on old Volume 2A/3 chapter citations or needs the currently posted financial-management route.", "required_action": "Start with the current volume and check its supplemental guidance, policy memoranda and authoritative references. Do not assume an older chapter number still locates current text.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Directory headings for Volumes 2, 3 and 11; September 2026 alert", "source_ids": [ "RSRC-0122", "RSRC-0134" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "current-policy-route", "target": "RULE-0072" }, { "type": "read-with-memoranda", "target": "RULE-0094" }, { "type": "related-current-record", "target": "RULE-0142" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "September 2026 reorganization; Volume 2/3 supplements listed as forthcoming" }, { "id": "RULE-0129", "title": "FY2026 statutory investment-item ceiling and contingency condition", "citation": "P.L. 119-75, Division A §8039", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 8039 permits covered O&M appropriations to purchase investment items costing not more than $350,000 per unit; the $500,000 ceiling needs the stated Secretary determination for a named contingency operation overseas.", "applies_when": "The action uses funds governed by §8039, including assessment of FY2026 conditions incorporated by the FY2027 CR.", "required_action": "Identify the applicable appropriation and implementing policy. Confirm the special determination before using $500,000; EUCOM sponsorship alone is insufficient. Keep the statutory ceiling distinct from the IT policy breakpoint in RULE-0130.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Secretary determination for the higher ceiling as specified in §8039; no such determination established.", "locator": "P.L. 119-75 Division A §8039; P.L. 119-103 Division A §§101(3), 103", "source_ids": [ "RSRC-0111", "RSRC-0101" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-03", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "provision-detail", "target": "RULE-0106" }, { "type": "CR-incorporation-check", "target": "RULE-0104" }, { "type": "related-current-record", "target": "RULE-0130" }, { "type": "related-current-record", "target": "RULE-0142" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "FY2026 enactment; assess FY2027 CR incorporation and subsequent legislation" }, { "id": "RULE-0130", "title": "IT system cost includes integration and software", "citation": "FMR Volume 2 (September 2026), §§2.1.17-2.1.18.2", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "C2", "Camera", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "For the stated IT/automated-system scope, the policy treats acquiring and deploying a complete system costing $350,000 or more as procurement investment. Aggregate the components that function together to meet the documented requirement.", "applies_when": "A C2, camera analytics or related IT acquisition falls within the non-embedded IT policy scope.", "required_action": "Identify the complete system, equipment, integration, engineering and software costs. Apply the separate upgrade-cost rule for modernization and address the exact $350,000 boundary with FM under the governing policy.", "exceptions": "Not a universal threshold for every sensor, centrally managed item, weapon-embedded IT or revolving-fund purchase. Section 2.1.18 has separate cases.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 13-14, §§2.1.17.1-3 and 2.1.18.2", "source_ids": [ "RSRC-0123" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "policy-and-statutory-boundary", "target": "RULE-0129" }, { "type": "related-current-record", "target": "RULE-0131" }, { "type": "related-current-record", "target": "RULE-0132" }, { "type": "related-current-record", "target": "RULE-0141" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "September 2026 IT policy: $350,000 or more; statutory permission uses not more than" }, { "id": "RULE-0131", "title": "C2 development, maintenance and annual software fees", "citation": "FMR Volume 2 (September 2026), §§2.1.18.1-2.1.18.3", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "C2", "Software", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "IT development and major performance upgrades follow the stated RDT&E rules. Routine software maintenance and minor improvements can follow O&M treatment; proprietary software financed by annual fee has separate expense treatment.", "applies_when": "The requirement combines software development, integration, licenses, support or updates.", "required_action": "Describe the purpose of each task and objective-system requirements. Distinguish engineering/testing needed to reach the objective system from ordinary maintenance; a COTS label alone does not settle funding.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 13-14; §§2.1.17.3, 2.1.18.1.1-3, 2.1.18.2.2 and 2.1.18.3.1-2", "source_ids": [ "RSRC-0123" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-IT-funding", "target": "RULE-0130" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0132", "title": "Procurement full funding concerns a usable end item", "citation": "FMR Volume 2 (September 2026), §2.1.3", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The full-funding policy generally requires the complete military-usable end item cost in the year procured, subject to the stated advance-procurement and other exceptions.", "applies_when": "A sensor, effector or integrated system is being financed as procurement.", "required_action": "Identify the complete usable end item and all acquisition costs. Establish any applicable statutory/policy exception before structuring increments across fiscal years.", "exceptions": "Specific advance-procurement, EOQ and other stated exceptions require their own conditions; no general incremental procurement authority is inferred.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 4-5, §2.1.3.1-2", "source_ids": [ "RSRC-0123" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "read-with-complete-end-item", "target": "RULE-0130" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0133", "title": "Service severability and bona fide need under current FMR", "citation": "FMR Volume 3 (September 2026), §8.5", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The policy distinguishes severable from nonseverable services by the terms and circumstances, potentially at line-item level, and requires a bona fide need within the appropriation availability period.", "applies_when": "Support, integration, testing or subscriptions cross fiscal years or rely on delivery lead time.", "required_action": "Identify the actual service/result and period, then the authority for crossing fiscal years. Record the need and lead-time basis; do not equate a one-year option with automatic funding availability.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 16-17, §§8.5.1-8.5.2", "source_ids": [ "RSRC-0124" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "statutory-service-authority", "target": "RULE-0058" }, { "type": "related requirement", "target": "RULE-0258" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0134", "title": "Modification scope also controls funding analysis", "citation": "FMR Volume 3 (September 2026), §8.6", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The CO must apply FAR/DFARS, scope law and financial rules. The policy treats added major-item quantities generally, and additional deliverable services, as scope changes.", "applies_when": "A modification would add sensors, integration work, deliverable services or quantities.", "required_action": "Assess scope and the funds legally available for any new obligation before selecting modification authority and funding. Read this fiscal policy together with the governing acquisition rules.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 17-18, §§8.6.1-4", "source_ids": [ "RSRC-0124" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "contract-modification-authority", "target": "RULE-0086" }, { "type": "related requirement", "target": "RULE-0266" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0135", "title": "Expired funds differ from closed accounts", "citation": "FMR Volume 3 (September 2026), §§9.1-9.3, 9.5-9.8", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Expired accounts remain available for obligations properly chargeable to that account until closure. Closed-account payments and specified contract-change adjustments have separate requirements.", "applies_when": "Administration involves an upward adjustment, claim, closeout or expired/canceled appropriation.", "required_action": "Establish the underlying obligation, account status and adjustment type; apply the relevant approval, notification and current-account limits. An unspent expired balance is not general new-award authority.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 24-26; especially §§9.1, 9.3, 9.5-9.8", "source_ids": [ "RSRC-0124" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "time-availability", "target": "RULE-0055" }, { "type": "related-current-record", "target": "RULE-0136" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0136", "title": "Replacement contracts using expired funds are conditional", "citation": "FMR Volume 3 (September 2026), §9.7", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Contract administration" ], "jurisdiction": "United States", "summary": "Expired-fund replacement requires continuing need, a good-faith original award, a qualifying termination circumstance, unchanged size/scope and execution without undue delay.", "applies_when": "A replacement award is contemplated after termination of an earlier contract.", "required_action": "Test every replacement condition and applicable approval/notification limit. If conditions fail, identify appropriate current-year funds; do not treat all convenience terminations as qualifying.", "exceptions": "Only the termination circumstances and other conditions stated in §9.7 support this route; no individual replacement is approved.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF p. 26, §9.7", "source_ids": [ "RSRC-0124" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "conditional-replacement-route", "target": "RULE-0135" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0137", "title": "Direct-cite purchase requests: PRDS transition deadline", "citation": "FPM25-05, New Procedures for Direct Cite Orders", "issuer": "DoD Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The memo requires PRDS for direct-cite purchase-request transmission by July 31, 2026 and discontinues DD448/448-2 for that route. The requiring activity line of accounting continues through subsequent contract actions.", "applies_when": "A requiring activity asks another contracting activity to execute a direct-cite action.", "required_action": "Use the applicable PRDS exchange and preserve accounting traceability. Confirm current implementing instructions and local system capability; do not extend this direct-cite instruction to every reimbursable order.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Memorandum pp. 1-2", "source_ids": [ "RSRC-0127" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-09-11", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "separate-funding-authority-check", "target": "RULE-0057" }, { "type": "related-current-record", "target": "RULE-0138" } ], "date_note": "Issued 2025-09-11 according to official directory; implementation deadline 2026-07-31.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0138", "title": "Direct-cite IAA and reimbursable funding routes remain distinct", "citation": "FPM25-05, pp. 2-3", "issuer": "DoD Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "PRDS does not replace the required interagency agreement. The memo routes reimbursable funding, including applicable administrative fees, through G-Invoicing/FIDS; a later PRDS transaction may still support award.", "applies_when": "An assisted action combines direct-cite funding, reimbursable services or fees.", "required_action": "Identify each funding route, retain the governing agreement and coordinate the required order, receipt and invoice exchanges. Do not assume a purchase-request format supplies legal authority.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "FPM25-05 pp. 2-3; FMR Volume 3 §8.10, PDF p. 19", "source_ids": [ "RSRC-0127", "RSRC-0124" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-09-11", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "distinct-funding-routes", "target": "RULE-0137" }, { "type": "related requirement", "target": "RULE-0259" }, { "type": "related requirement", "target": "RULE-0263" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0139", "title": "Economy Act prerequisites and limits", "citation": "FMR Volume 11 (September 2026), §§4.1-4.6", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Economy Act orders require available funds and the statutory determinations, with a D&F where required. They cannot extend fund availability or evade legal and regulatory restrictions.", "applies_when": "The identified interagency/intra-agency order authority is the Economy Act.", "required_action": "Confirm the authority, required determinations, performing capability and acquisition conditions. Separately research any claimed non-Economy Act authority.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 27-28, §§4.1, 4.3, 4.5-4.6", "source_ids": [ "RSRC-0125", "RSRC-0057" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "current-FMR-implementation", "target": "RULE-0057" }, { "type": "related-current-record", "target": "RULE-0140" }, { "type": "related requirement", "target": "RULE-0263" }, { "type": "related requirement", "target": "RULE-0264" }, { "type": "related requirement", "target": "RULE-0265" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0140", "title": "Economy Act order reconciliation and deobligation", "citation": "FMR Volume 11 (September 2026), §4.8.4.2", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration", "Modification or option" ], "jurisdiction": "United States", "summary": "Economy Act balances must be reconciled and deobligated to the extent the servicing activity has not provided the goods/services or incurred the qualifying obligation within the ordering funds availability period.", "applies_when": "An Economy Act order has unused balances or approaches the end of its appropriation availability.", "required_action": "Establish performance and downstream obligation status with the servicing activity and coordinate both sides of deobligation. Accepted orders cannot merely hold funds for later requirements.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "PDF pp. 30-31, §4.8.4.2", "source_ids": [ "RSRC-0125", "RSRC-0057" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "administration", "target": "RULE-0139" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0141", "title": "Financial-statement capitalization is a different threshold", "citation": "FPM26-04; FMR Volume 2 §2.1.2.2", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "FPM26-04 sets financial-statement capitalization thresholds by fund and asset type. Volume 2 separately distinguishes appropriation-selection criteria from accounting definitions.", "applies_when": "An accounting capitalization amount is offered as the reason O&M can buy equipment or installation work.", "required_action": "Use the appropriation-selection authority for funding and the applicable accounting policy for asset treatment. Do not import a financial-statement capitalization number into the expense/investment test.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "FPM26-04 single-page memo/table; Volume 2 PDF p. 4, §2.1.2.2", "source_ids": [ "RSRC-0128", "RSRC-0123" ], "limitations": "The memo is visually reviewed. No conclusion about a specific property record, exemption or appropriation follows from it.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-05-18", "effective_date": "2026-05-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "different-purpose-threshold", "target": "RULE-0130" }, { "type": "related requirement", "target": "RULE-0238" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0142", "title": "2023 expense/investment memo has a stated sunset condition", "citation": "FPM23-02, both pages", "issuer": "DoD Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The memo implements FY2023 legislation, excludes the stated centrally managed procurement-budgeted items, and says it remains effective until the corresponding FMR chapter is updated.", "applies_when": "An older $350,000/$500,000 memo is being used for a current funding decision.", "required_action": "Check current annual authority and September 2026 FMR policy before relying on the historical memo. Resolve its transition status and any command-specific higher-threshold determination.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Memo pp. 1-2; September 2026 FMR directory", "source_ids": [ "RSRC-0126", "RSRC-0122", "RSRC-0123" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2023-03-22", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "current-annual-authority", "target": "RULE-0129" }, { "type": "transition-check", "target": "RULE-0128" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Historical FY2023 memorandum; continuing force after FMR reorganization not established" }, { "id": "RULE-0143", "title": "Cloud service approval and clause prescriptions", "citation": "2026-O0024; DFARS 239.7602-1 and 239.7604", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Cybersecurity", "equipment": [ "C2", "Camera", "Software", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The adopted text generally requires DISA provisional authorization at the appropriate level before cloud-service award and prescribes 252.239-7009/7010 for IT services, including commercial acquisitions.", "applies_when": "C2, analytics, hosting or integration includes cloud computing services.", "required_action": "Verify the actual provider offering and level, obtain required data descriptions and review commercial terms. Apply the exact exceptions and clause prescriptions.", "exceptions": "DoD CIO waiver or qualifying private on-premises service from U.S. Government facilities; the latter still needs provisional authorization before operational use.", "approval_authority": "DISA provisional authorization or stated DoD CIO waiver; neither substitutes for system authorization.", "locator": "Combined PDF pp. 10-11; DFARS 239.7602-1(a)-(c), 239.7604", "source_ids": [ "RSRC-0132" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "system-authorization-separate", "target": "RULE-0064" }, { "type": "related-current-record", "target": "RULE-0144" }, { "type": "related-current-record", "target": "RULE-0145" }, { "type": "related-current-record", "target": "RULE-0151" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0144", "title": "Overseas cloud data storage needs its own authorization", "citation": "2026-O0024; DFARS/PGI 239.7602-2", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Overseas execution", "equipment": [ "C2", "Camera", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "For covered Government data not physically on DoD premises, storage outside the United States/outlying areas requires the authorizing-official route and written CO notification to the contractor.", "applies_when": "An overseas requirement proposes offshore cloud storage of Government data.", "required_action": "Establish the data and hosting location. Obtain written AO authorization before CO authorization, apply the SRG and issue the required written notification; overseas performance alone is insufficient.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Authorizing official written authorization followed by CO written notification.", "locator": "Combined PDF pp. 11, 27; DFARS 239.7602-2 and PGI 239.7602-2(b)", "source_ids": [ "RSRC-0132" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "overseas-hosting", "target": "RULE-0143" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0145", "title": "Adding cloud services after award requires approval", "citation": "2026-O0024; 252.239-7010(b)(1); PGI 239.7603-1(b)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Modifications", "equipment": [ "C2", "Software", "Integration" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "A contractor that originally did not anticipate cloud use must obtain CO approval before introducing it. PGI requires requiring-activity approval and verification of the relevant provisional authorization.", "applies_when": "The applicable clause governs and a contractor proposes cloud use after award following a negative cloud representation.", "required_action": "Resolve the requiring-activity approval, authorized service offering, data location, security and any contract changes before use.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Combined PDF pp. 18, 27; clause (b)(1) and PGI 239.7603-1(b)", "source_ids": [ "RSRC-0132" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "postaward-change", "target": "RULE-0143" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0146", "title": "Cloud delivery, disposition and subcontract duties", "citation": "2026-O0024; 239.7602-1(c); 252.239-7010(i)-(l)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Administration", "equipment": [ "C2", "Software", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The cloud text requires data-delivery/disposition terms, confirmation of disposition at closeout, specified Government access and flowdown to subcontracts that involve or may involve cloud services.", "applies_when": "The applicable cloud clause governs hosting, sustainment, transition or closeout.", "required_action": "Specify usable transition formats and delivery/disposition requirements before award; administer confirmation, access and applicable subcontract duties through performance and closeout.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Combined PDF pp. 11, 19-20; 239.7602-1(c)(2)-(4), clause (i)-(l)", "source_ids": [ "RSRC-0132" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "rights-and-handover", "target": "RULE-0147" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0147", "title": "Commercial C2 software rights come from the license", "citation": "2026-O0036; DFARS 227.7202-1 and 227.7202-3", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Data rights", "equipment": [ "C2", "Software", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Commercial software is normally acquired under customary public licenses that satisfy law and user needs. Additional required rights are negotiated and documented in the contract license.", "applies_when": "A C2 or analytics deliverable is commercial computer software/documentation.", "required_action": "Identify required users, integration, modification, support and transfer rights. Review the actual license and negotiate missing rights; payment alone does not establish source-code or unlimited rights.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Combined PDF p. 39, §§227.7202-1(a)-(d), 227.7202-3(a)-(c)", "source_ids": [ "RSRC-0133" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related-current-record", "target": "RULE-0146" }, { "type": "adopted-overhaul", "target": "RULE-0049" }, { "type": "Additional public GPC guidance", "target": "RULE-0156" }, { "type": "separately reviewed software requirement", "target": "RULE-0200" }, { "type": "separately reviewed software requirement", "target": "RULE-0204" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0148", "title": "Noncommercial data/software delivery and restrictions", "citation": "2026-O0036; DFARS 227.7103-1 and 227.7103-3", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Data rights", "equipment": [ "Radar", "Camera", "C2", "Software", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The revised provisions jointly address noncommercial technical data, software and documentation: delivery schedules, acceptability, separately priced deliverables where practicable, and identification of asserted restrictions.", "applies_when": "Noncommercial data/software is needed for sensor integration or continuing support.", "required_action": "Specify deliverables and acceptance criteria, identify asserted restrictions before award and resolve validity questions. Keep acquisition of the data/software distinct from acquisition of the necessary rights.", "exceptions": "Private-expense restrictions and the listed statutory exceptions remain material; this does not authorize demanding every vendor right.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Combined PDF pp. 10-11, §227.7103-1(a)-(f), §227.7103-3(a)", "source_ids": [ "RSRC-0133" ], "limitations": "Bounded provision-level analysis; no actual contract, funding document, vendor or system has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "adopted-overhaul", "target": "RULE-0048" }, { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0210" }, { "type": "related requirement", "target": "RULE-0248" }, { "type": "related requirement", "target": "RULE-0250" }, { "type": "related requirement", "target": "RULE-0253" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0149", "title": "Germany NATO VAT relief: procurement route and conditions", "citation": "BMF letter 2004-12-22, UStH 2024 Annex 6, ¶¶8, 13-17", "issuer": "German Federal Ministry of Finance", "instrument_type": "National administrative guidance", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany", "summary": "The guidance conditions relief on an authorized procurement route, eligible use, price reduction and proof. It distinguishes the NATO supplementary agreement and U.S. Offshore Tax Agreement routes.", "applies_when": "German VAT relief is claimed for a covered purchase.", "required_action": "Establish the applicable route, eligible recipient/use and procurement-office authority before relying on relief.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Annex 6 ¶¶8, 13-17", "source_ids": [ "RSRC-0131" ], "limitations": "Selected German primary-source reader excerpts; no individual exemption established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2004-12-22", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "national-implementation", "target": "RULE-0077" }, { "type": "related-current-record", "target": "RULE-0150" }, { "type": "related requirement", "target": "RULE-0285" }, { "type": "related requirement", "target": "RULE-0286" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "2004 BMF letter reproduced in UStH 2024; later amendments unresolved" }, { "id": "RULE-0150", "title": "Germany VAT evidence and invoicing during performance", "citation": "BMF letter 2004-12-22, UStH 2024 Annex 6, ¶¶28-31, 66-69", "issuer": "German Federal Ministry of Finance", "instrument_type": "National administrative guidance", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration", "Modification or option" ], "jurisdiction": "Germany", "summary": "The guidance calls for documentary/accounting proof, generally an Abwicklungsschein with the procurement order, and invoices reflecting the exemption and proper recipient.", "applies_when": "A covered German purchase uses this VAT-relief route.", "required_action": "Coordinate receipt/payment certification and invoice evidence, including correction of VAT wrongly shown.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Annex 6 ¶¶28-31, 66-69", "source_ids": [ "RSRC-0131" ], "limitations": "Conditional relief; verify applicable exceptions and current implementation.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2004-12-22", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "performance-evidence", "target": "RULE-0149" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "UStH 2024 guidance; current forms and amendments need confirmation" }, { "id": "RULE-0151", "title": "Cloud incident preservation and CO notification route", "citation": "2026-O0024; 252.239-7010(d)-(h), (j); PGI 239.7603-2/-3", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Administration", "equipment": [ "C2", "Software" ], "stages": [ "Contract administration" ], "jurisdiction": "United States", "summary": "The clause requires reporting covered cloud incidents, preserving specified images/monitoring data for at least 90 days, and notifying the CO of third-party data-access requests. PGI assigns onward coordination.", "applies_when": "A covered cloud incident or third-party request arises under the applicable clause.", "required_action": "Follow the clause reporting/preservation duties and the PCO/ACO/requiring-activity notification route; coordinate data-access requests with the mission/data owner.", "exceptions": "Read the cited scope and any specific exception; no blanket exception is established.", "approval_authority": "Apply the cited authority and current written delegations; no local delegation is established here.", "locator": "Combined PDF pp. 19-20, 27-28; clause (d)-(h), (j), PGI 239.7603-2/-3", "source_ids": [ "RSRC-0132", "RSRC-0135" ], "limitations": "This clause text does not supply a 72-hour deadline. Separate incorporated security clauses may impose additional reporting duties; assess them separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "incident-administration", "target": "RULE-0143" }, { "type": "separate-security-requirements", "target": "RULE-0097" } ], "date_note": "Edition is identified in the citation; no day is invented for a month-only publication date.", "version_state": "Selected official provisions reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0152", "title": "Use the April 2026 GPC UAS policy, with predecessor limits", "citation": "DoD GPC Guidebook (2026-04-14), cover and 5.5.1", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Authority and versions", "equipment": [ "UAS", "C2", "Camera", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "The release notice updates UAS section 5.5.1 and removes the UAS purchasing prohibition from Appendix C. Conditional purchase, source and approval requirements remain.", "applies_when": "Research relies on GPC 2025-01, a historical purchase form or a general statement that GPC drone purchases are prohibited.", "required_action": "Read the current Guidebook and Component implementation. Reconcile predecessor forms and training material with the revised section before using them.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF cover and pp.58-59 (printed 5-5/5-6); predecessor GPC 2025-01 pp.1-2; training item 3OP049", "source_ids": [ "RSRC-0139", "RSRC-0137", "RSRC-0140", "RSRC-0138" ], "limitations": "Removal of a Guidebook prohibition is not repeal of UAS statutes. The training page still describes a pending memorandum; it is not proof no Guidebook change occurred. Complete predecessor rescission and local implementation remain unresolved.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0153" }, { "type": "related requirement", "target": "RULE-0100" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0153", "title": "Conditional GPC route for Blue UAS and testing/training drones", "citation": "DoD GPC Guidebook 5.5.1(a), (c)-(d); DPCAP FAQ 40", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "UAS acquisition", "equipment": [ "UAS", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "Section 5.5.1 permits GPC UAS purchases subject to Service/Agency policy: listed Blue UAS/components, or non-listed Group 1-2 UAS/components for testing and training with written O-6 commander/equivalent approval. Foreign-source restrictions remain separate.", "applies_when": "A proposed GPC purchase includes a UAS or UAS-related component.", "required_action": "Identify the exact configuration, current list status, purpose, Component policy and required written approval. Check source prohibitions and any actual statutory exception before purchasing.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF pp.58-59 (printed 5-5/5-6), 5.5.1(a),(c)-(d); FAQ 40", "source_ids": [ "RSRC-0139", "RSRC-0136" ], "limitations": "The non-listed route is specifically for Group 1-2 testing/training. An O-6 approval or a Blue-list reference does not establish flight, spectrum, host-nation or mitigation authority. No actual product clearance is verified here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0042" }, { "type": "related requirement", "target": "RULE-0096" }, { "type": "related requirement", "target": "RULE-0154" }, { "type": "related requirement", "target": "RULE-0155" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0154", "title": "Screen UAS sources using the distinct FASCSA and FASC lists", "citation": "DPCAP GPC FAQs 40-42", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Supply chain and security", "equipment": [ "UAS", "Integration", "Software" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "For non-Blue-list UAS/components, the FAQs direct checks of SAM FASCSA orders and the Commerce Consolidated Screening List route to FASC covered foreign entities. SPRS displays FASCSA orders but does not currently display the FASC entity list.", "applies_when": "A cardholder proposes a non-listed UAS/component purchase or relies on a supplier-risk report as the only drone-source screen.", "required_action": "Check each applicable official list and the controlling restriction/exception. Preserve the action-date result and follow Component procedures; do not equate an SPRS search with every required source check.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "FAQ 40 fourth bullet and note; FAQ 41", "source_ids": [ "RSRC-0136" ], "limitations": "Undated official web guidance. Lists and coverage can change. Section 5.5.1(c) and (d) have separate wording; this summary does not broaden a particular exemption or treat all consolidated-list entries as identical prohibitions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0153" }, { "type": "related requirement", "target": "RULE-0042" }, { "type": "related requirement", "target": "RULE-0096" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0155", "title": "Retain the written GPC testing/training approval in the correct system", "citation": "DoD GPC Guidebook 5.5.1(b); DPCAP FAQ 40", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Administration", "equipment": [ "UAS", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "The non-listed testing/training approval must be retained as an electronic attachment in the card bank system for unclassified/non-CUI material, or an approved compensating-control system for classified/CUI material.", "applies_when": "A purchase uses the written O-6/equivalent approval route in 5.5.1(a)(ii).", "required_action": "Record the approval and store it through the applicable authorized recordkeeping route. Keep approval retention distinct from the eligibility and source-screening decisions.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF p.58 (printed 5-5), 5.5.1(b); FAQ 40 second bullet", "source_ids": [ "RSRC-0139", "RSRC-0136" ], "limitations": "Selected April 2026 Guidebook provisions. Check later policy and current adopted FAR/DFARS text; no local delegation, product approval or individual-contract determination is established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0153" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0156", "title": "C2 licenses and statements of work may require a separate contract instrument", "citation": "DoD GPC Guidebook 4.6 and 5.4", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Contracting methods", "equipment": [ "C2", "Software", "Camera", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "Open-market micro-purchase card authority is limited to the specified fixed-price supplies/services with no statement of work or terms beyond price and delivery. Additional terms require an appropriate contract instrument signed by an official with the necessary warrant authority.", "applies_when": "A small sensor, software, cloud or integration purchase contains a license agreement, statement of work or additional vendor terms.", "required_action": "Review terms with the contracting office, verify the cardholder designation and limits, and select a suitable vehicle. Do not split an aggregate requirement to avoid an applicable threshold.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF p.46 (printed 4-5), 4.6; p.58, 5.4", "source_ids": [ "RSRC-0139" ], "limitations": "A payment card does not by itself grant authority to agree to licenses or other contract terms. An authorized ordering role is distinct from ordinary micro-purchase authority. Current thresholds must be established from applicable rules.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0147" }, { "type": "related requirement", "target": "RULE-0143" }, { "type": "related requirement", "target": "RULE-0157" }, { "type": "related requirement", "target": "RULE-0158" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0157", "title": "GPC ordering authority on an existing vehicle has its own conditions", "citation": "DoD GPC Guidebook 4.7.6 and 4.7.6.1", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Ordering and options", "equipment": [ "All" ], "stages": [ "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "The Contract Ordering Official designation covers authorized purchases against specified existing instruments with firm fixed prices and prearranged terms, when the awarding warranted CO authorizes the cardholder to order. Authority may not exceed the SAT.", "applies_when": "A cardholder will order sensors, support or supplies through an existing contract, BOA or BPA.", "required_action": "Verify the designation, awarding-CO authorization, vehicle terms, amount limit, training, reporting and WAWF procedures. Establish scope and ordering conditions separately.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF pp.48-49 (printed 4-7/4-8), 4.7.6 and 4.7.6.1", "source_ids": [ "RSRC-0139" ], "limitations": "This is a bounded Guidebook summary, not independent authority to order against any BOA/BPA. Vehicle formation, scope, competition and the currently applicable SAT remain separate requirements.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0020" }, { "type": "related requirement", "target": "RULE-0113" }, { "type": "related requirement", "target": "RULE-0160" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0158", "title": "GPC contract payment requires full funding and controls against duplicate obligations", "citation": "DoD GPC Guidebook 4.7.8 and 4.7.8.1", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "The Contract Payment Official role is a payment authority. The Guidebook requires contracts paid by GPC to be fully funded, prohibits progress finance payments, and requires separation of duties and controls against duplicate obligations.", "applies_when": "The GPC is selected as the payment method under an existing or newly awarded contract.", "required_action": "Confirm contract payment terms/contractor acceptance, the designated payment role, full funding, receiving procedures and accounting controls. Do not create a second obligation for the same contract payment.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF p.50 (printed 4-9), 4.7.8 and 4.7.8.1(a)-(e)", "source_ids": [ "RSRC-0139" ], "limitations": "Payment authority is distinct from award/ordering authority. The Guidebook statement about contract-payment value is not a removal of cardholder, bank, funds-control, warrant or contract limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0030" }, { "type": "related requirement", "target": "RULE-0132" }, { "type": "related requirement", "target": "RULE-0160" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0159", "title": "Card purchases of cameras and COTS IT retain cybersecurity review", "citation": "DoD GPC Guidebook 6.5", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Cybersecurity", "equipment": [ "Camera", "C2", "Software", "Radar", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Contract administration" ], "jurisdiction": "United States", "summary": "Component cyber and supply-chain controls apply to COTS IT regardless of purchase method. The Guidebook expressly includes cameras, software and networking equipment and requires compliance with local IT purchasing policy.", "applies_when": "A GPC action acquires a network-capable sensor, camera, software or related commercial service.", "required_action": "Coordinate IT/security approvals and required vehicle use with the requiring and contracting offices. Preserve applicable accountability and supply-chain requirements through ordering and acceptance.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF pp.64-65 (printed 6-5/6-6), 6.5 before 6.5.1", "source_ids": [ "RSRC-0139" ], "limitations": "The Guidebook recommends an existing contract vehicle for COTS IT in the stated circumstances; that recommendation alone is not a universal mandatory vehicle. Later security deviations and current Component requirements remain controlling.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0092" }, { "type": "related requirement", "target": "RULE-0097" }, { "type": "related requirement", "target": "RULE-0143" }, { "type": "related requirement", "target": "RULE-0156" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0160", "title": "GPC payment does not replace receipt and contract acceptance records", "citation": "DoD GPC Guidebook 6.9, 6.9.1 and 6.9.1.1", "issuer": "DoD DPCAP", "instrument_type": "Guidance", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "United States", "summary": "Cardholders must retain proof of delivery and identify the receiving official and independent receipt confirmation. The Guidebook requires WAWF receiving reports for contracts paid by GPC and identifies CRCARD as the payment-office code.", "applies_when": "Sensors, software or services are delivered under a GPC transaction or a contract using card payment.", "required_action": "Arrange independent receipt and acceptance records, retain supporting documents, and follow the applicable WAWF and payment-office procedures for a contract/order.", "exceptions": "Follow each cited provision and any applicable statutory/regulatory exception; a GPC designation or O-6 approval is not a blanket waiver.", "approval_authority": "Use the current written cardholder designation, warranted authority and Component policy; the O-6 route applies only to the stated testing/training case.", "locator": "PDF p.68 (printed 6-9), 6.9 through 6.9.1.1", "source_ids": [ "RSRC-0139" ], "limitations": "The cited Guidebook distinguishes contract payments from open-market micro-purchases. Read applicable adopted DFARS/PGI and Component procedures; this record does not determine acceptance for a specific delivery.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0157" }, { "type": "related requirement", "target": "RULE-0158" }, { "type": "related requirement", "target": "RULE-0273" } ], "date_note": "Guidebook release dated 2026-04-14; original 2025-03-01 effective date does not establish when each later revision took effect. Undated web guidance has no inferred effective date.", "version_state": "April 14, 2026 Guidebook and selected public guidance reviewed 2026-10-03; confirm subsequent changes" }, { "id": "RULE-0161", "title": "Request supplier cost data only after the pricing-data hierarchy", "citation": "DPCAP, Implementation of Supplier Cost and Pricing Transparency (2026-10-01), pp.1-2; September 14 appendix p.3", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The October policy permits necessary actual-cost requests at prime and supplier levels, excludes COTS items from this cost-information direction, and retains the statutory hierarchy and limits for commercial products and services. Where certification is not required and available competition, market, sales or other-source information cannot establish price reasonableness, the CO must request sufficient data other than certified cost or pricing data.", "applies_when": "Pricing a sensor, effector, software, support or integration purchase, follow-on action or modification with inadequate existing price evidence.", "required_action": "Document why available price information is insufficient, identify the minimum lawful data needed, and apply commercial/COTS and other statutory limits. For modification requests, verify the contract includes the applicable clause; the memo specifically references FAR 52.215-21 in contracts containing it.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "Contracting officer within applicable authority; use the cited escalation or approval route where required.", "locator": "PDF pp.1-2, Cost Information When Needed / Other Than Certified Cost or Pricing Data; p.11, first paragraph", "source_ids": [ "RSRC-0146" ], "limitations": "Bounded reading of the signed September/October 2026 policy package. No individual-contract determination or completion of directed future rulemaking is established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0017" }, { "type": "related requirement", "target": "RULE-0019" }, { "type": "related requirement", "target": "RULE-0162" }, { "type": "separately reviewed software requirement", "target": "RULE-0202" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0162", "title": "Use existing business records without creating CAS coverage or new access rights", "citation": "DPCAP cost/pricing transparency memorandum (2026-10-01), pp.1-2; September 14 memorandum p.1", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "COs should generally request cost information as immediately available and regularly maintained, accepting ERP data where practicable. The policy requires no new accounting system or special data format. A data request alone creates neither a cost-reimbursement contract, CAS coverage, nor access rights beyond the contract.", "applies_when": "The Government requests supplier financial information during proposal evaluation, negotiations or administration.", "required_action": "Identify existing records and lawful access. Distinguish data from CAS-covered systems from GAAP records for firms not subject to CAS, protect proprietary information, and do not impose an accounting-system conversion through an information request.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "Contracting officer within applicable authority; use the cited escalation or approval route where required.", "locator": "PDF p.1 final paragraph; p.2 opening paragraph and Other Than Certified Cost or Pricing Data; p.6", "source_ids": [ "RSRC-0146" ], "limitations": "Bounded reading of the signed September/October 2026 policy package. No individual-contract determination or completion of directed future rulemaking is established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0161" }, { "type": "related requirement", "target": "RULE-0165" }, { "type": "related requirement", "target": "RULE-0167" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0163", "title": "Escalate pricing-data denials through the applicable route", "citation": "DPCAP cost/pricing transparency memorandum (2026-10-01), p.2", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "For an acquisition subject to TINA, refusal to provide statutorily required certified cost or pricing data requires immediate CO coordination with DCAA to initiate a Truth in Negotiations Audit. The memorandum separately directs use of DFARS PGI 215.403-70 for contractor data denials.", "applies_when": "A contractor refuses a lawful pricing-data request after the applicable requirement and exceptions have been established.", "required_action": "Record the request, legal basis, missing information and denial. Distinguish certified-data refusal from other-data issues, coordinate with DCAA when the stated trigger applies, and use the current PGI escalation procedure.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "CO, DCAA and the management chain specified by the current PGI.", "locator": "PDF p.2, Certified Cost or Pricing Data and Escalation", "source_ids": [ "RSRC-0146" ], "limitations": "The request must first be legally required or justified. This entry does not grant a new audit/access right, permit demands despite an exception, or establish that a particular refusal is noncompliant.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0161" }, { "type": "related requirement", "target": "RULE-0162" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0164", "title": "Enforce overdue CSDR deliverables through contract-supported remedies", "citation": "DPCAP cost/pricing transparency memorandum (2026-10-01), p.2, CSDR", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Cost administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "United States", "summary": "For a contract with delinquent Cost and Software Data Reporting deliverables, the CO must immediately issue a formal demand for submission within 30 days. If the contractor does not comply, the memorandum calls for enforcing applicable contract terms, including withholds where the contract provides for them.", "applies_when": "An existing contract has an applicable CSDR requirement and an overdue report.", "required_action": "Confirm the reporting requirement, due date and delinquency; issue the required demand through official contract administration; assess only remedies supported by the contract and governing authority. Preserve the earlier reporting history.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "Contracting officer within applicable authority; use the cited escalation or approval route where required.", "locator": "PDF p.2, Cost and Software Data Reporting; attached August 18 memo pp.4-5 for the earlier direction", "source_ids": [ "RSRC-0146" ], "limitations": "This is not a universal reporting requirement for every ABAD purchase or independent authority to withhold payment. The memorandum describes general CSDR coverage; exact applicability and any prior overdue deadline require separate analysis.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0029" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0165", "title": "Supplier ERP/API cost-data participation is not an award condition", "citation": "DPCAP cost/pricing transparency memorandum (2026-10-01), pp.2-3; September 14 appendix p.3", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Data rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The Department will study secure push-only cost-data channels and use formal rulemaking for an ERP/API initiative. If pursued, participation must be voluntary, without nonparticipation penalties or use as an award condition, evaluation factor or responsibility consideration.", "applies_when": "An acquisition team considers automated access to a supplier financial system.", "required_action": "Do not make an unimplemented API initiative mandatory. Establish any authorized access and security protections separately; keep voluntary automated participation distinct from otherwise lawful contractual data requirements.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "Contracting officer within applicable authority; use the cited escalation or approval route where required.", "locator": "PDF p.2 final paragraph continuing on p.3; p.11, first paragraph", "source_ids": [ "RSRC-0146" ], "limitations": "Future initiative and express constraints, not an implemented technical interface or new access right. The September attachment requires express contractual authorization and applicable security protections for automated access.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0162" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0166", "title": "Use sector-specific profit benchmarks without treating them as caps", "citation": "DPCAP cost/pricing transparency memorandum (2026-10-01), p.3", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Policy memorandum", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The memorandum recommends profit objectives informed by the relevant commercial sector, risk, investment, efficiency and performance; benchmarks are not caps. It distinguishes hardware, software/IT and services/sustainment, encourages tiered profit sharing for sole-source or long-term production, and requires similar terms for key suppliers when that mechanism is used with the prime.", "applies_when": "Negotiating profit objectives for hardware, software, integration or sustainment.", "required_action": "Document the relevant sector and risk/investment basis. If considering profit sharing, establish lawful terms and required supplier treatment with pricing/policy support. Track formal DFARS implementation before treating proposed clauses or data formats as implemented requirements.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "Contracting officer within applicable authority; use the cited escalation or approval route where required.", "locator": "PDF p.3, Modernized Profit Policy and Commercial Sector Alignment", "source_ids": [ "RSRC-0146" ], "limitations": "The sector approach and profit-sharing encouragement are guidance; conditional supplier treatment is stated expressly. New clauses/data formats and revised DFARS policy are to use formal rulemaking. No percentage, profit cap or existing-contract price adjustment is inferred.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-10-01", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0019" }, { "type": "related requirement", "target": "RULE-0029" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0167", "title": "Check the approval gate before bringing a business unit under full CAS", "citation": "Deputy Secretary, Fostering One Strong Industrial Base (2026-09-14), p.2 and appendix p.1", "issuer": "Deputy Secretary of War", "instrument_type": "Policy memorandum", "topic": "Planning", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Pending the specified CAS Board action, a solicitation that would bring a business unit newly under full CAS coverage requires written USW(A&S) acquisition-strategy approval. The appendix states that this approves the strategy only; it does not decide CAS applicability, grant a waiver or permit omission of a required clause.", "applies_when": "Planning a solicitation expected to create new full-CAS coverage for the performing business unit while the memorandum condition remains applicable.", "required_action": "Check current CASB action and implementation first. Where the gate applies, address competition, commercial or competed fixed-price approaches, exemptions and waiver authority in the strategy request. Preserve separate CAS applicability and clause determinations.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "USW(A&S), in writing for the acquisition strategy; statutory/CASB authority remains separate.", "locator": "Combined PDF pp.7 and 9 (September 14 memorandum p.2 and appendix p.1)", "source_ids": [ "RSRC-0146" ], "limitations": "Conditional instruction in the September 14 attachment. Later CASB implementation has not been comprehensively reviewed; GAP-019 preserves that issue. The memo does not itself abolish CAS or prove this approval is required for every acquisition.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-14", "effective_date": "2026-09-14", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0162" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0168", "title": "TINA Lite requires an eligible action over $50 million and nondelegable HCA approval", "citation": "2026-O0048 Rev 1, DFARS 215.403-72(a); TINA Lite Guide v1.1, II.A", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Class deviation", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The July 2026 standing program permits HCA approval, without delegation, for actions exceeding $50 million involving recurring requirements with reliable actual costs and price reasonableness grounded primarily in prior DoD purchases of the same or similar products. The guide first checks whether a certified-data exception already applies.", "applies_when": "A qualifying follow-on acquisition or contract action is being considered for tailored certified pricing data.", "required_action": "Establish action value, applicable exceptions, recurring scope, reliable actuals and contractor-system considerations; obtain HCA approval before using the TINA Lite provisions. Use the standing-program implementation and version 1.1 guide rather than the July 8 preview or the historical munitions pilot approval.", "exceptions": "If a certified-data exception applies, use that exception. TINA Lite is a tailored certified-data method, not a waiver. Subcontract eligibility and approved flowdown are separately governed.", "approval_authority": "Head of the contracting activity; DFARS 215.403-72(a) expressly forbids delegation.", "locator": "Deviation PDF pp.1-2 and 26-27; guide pp.5-7 and 10-13; historical issuance memos p.1", "source_ids": [ "RSRC-0145", "RSRC-0143", "RSRC-0142", "RSRC-0144", "RSRC-0147" ], "limitations": "The threshold concerns the qualifying contract action, not a blanket entitlement based on a vehicle ceiling or program size. Approved business systems are stated as should in the deviation. Individual eligibility and later changes remain to be established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-22", "effective_date": "2026-07-22", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0019" }, { "type": "related requirement", "target": "RULE-0169" }, { "type": "related requirement", "target": "RULE-0170" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0169", "title": "Separate recurring actual costs from new work and subcontract data", "citation": "2026-O0048 Rev 1, PGI 215.403-72(b)(1)-(2); TINA Lite Guide v1.1, III-IV", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Class deviation", "topic": "Pricing", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "A TINA Lite request must explain commonality and planned subcontract flowdown. Pricing analysis separates prior recurring costs, one-time costs, quantity effects and changed requirements. Incomplete prior work needs dated actuals plus estimates to complete; historical adjustments must be identified and new work adequately supported.", "applies_when": "Structuring an approved TINA Lite data request for a new action or modification.", "required_action": "Identify the historical lots/actions and data needed, remove obsolete or non-recurring work from projections, account for fixed/variable costs, specify the subcontract approach and refresh relevant data for negotiations. Do not request certified data below the applicable threshold or where an exception applies.", "exceptions": "Subcontracts lacking approved TINA Lite flowdown remain under their otherwise applicable certified-data rules. Lower-value or excepted items are not automatically subject to certified-data demands.", "approval_authority": "CO within the HCA-approved program approach; subcontract participation and data obligations must be specified.", "locator": "Deviation PDF pp.82-84, PGI 215.403-72(b); guide pp.14-21", "source_ids": [ "RSRC-0145", "RSRC-0143" ], "limitations": "Guide recommendations do not override controlling prescriptions or later cost-information policy. Historical actual costs are evidence to analyze, not proof that the same cost is reasonable for the current scope.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-22", "effective_date": "2026-07-22", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0168" }, { "type": "related requirement", "target": "RULE-0170" }, { "type": "related requirement", "target": "RULE-0162" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0170", "title": "TINA Lite solicitations and modifications need tailored provisions and certification", "citation": "2026-O0048 Rev 1, DFARS 215.110-70(i)-(j), 252.215-7988 and 252.215-7989", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Class deviation", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "New acquisition", "Modification or option", "Existing vehicle/order" ], "jurisdiction": "United States", "summary": "For approved actions, the deviation prescribes 252.215-7988 for solicitations and 252.215-7989 for modifications in place of the specified ordinary provision/clause. The CO must identify the requested data and relevant prior purchases. Additional required data needs an amendment to the solicitation or modification RFP, and the tailored certificate remains required.", "applies_when": "Issuing a solicitation or pricing a modification under an approved TINA Lite approach.", "required_action": "Apply the exact prescription, complete the data lists and subcontract treatment, and use the applicable tailored Certificate of Current Cost or Pricing Data. Obtain certification after price agreement and before award, subject to the stated unpriced-action exception. Distinguish scope and funds authority from this pricing method.", "exceptions": "The prescribed replacement applies to approved program actions. Exemptions from certification, unpriced actions and unapproved subcontract portions retain their distinct treatment.", "approval_authority": "CO implementing the HCA-approved TINA Lite approach.", "locator": "Deviation PDF p.15; pp.61-63, 252.215-7988(c)-(e); pp.64-68, 252.215-7989(a)-(d)", "source_ids": [ "RSRC-0145" ], "limitations": "No authority to expand contract scope, change funding, remove unrelated clauses or require unlisted certified data without the specified amendment is created. Existing contract clause incorporation must be evaluated separately.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-22", "effective_date": "2026-07-22", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0168" }, { "type": "related requirement", "target": "RULE-0169" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0171", "title": "TINA Lite award notification and legacy pilot reports remain distinct", "citation": "2026-O0048 Rev 1, PGI 215.403-72(b)(3)-(c); TINA Lite Guide v1.1, I.B.2", "issuer": "DPCAP / OUSW(A&S)", "instrument_type": "Class deviation", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "United States", "summary": "The standing program requires DPCAP notification within 10 days of contract award, including the contracting activity, CO and approval authority, program, action value, and contractor name/location. HCAs should monitor time and dollars saved. Existing pilot participants retain their pilot reporting duties.", "applies_when": "An approved standing-program action is awarded or an existing pilot action remains in performance.", "required_action": "Plan and document the applicable notification/reporting route. For legacy pilot actions, preserve reports three months after the action award and at completion of performance as stated in the guide; do not treat closure to new pilot entry as cancellation of existing reporting.", "exceptions": "Apply the governing statutory exceptions, commercial/COTS limits, current adopted regulations and incorporated contract terms; the memorandum does not waive them.", "approval_authority": "CO for notification; HCA monitoring under the cited PGI.", "locator": "Deviation PDF p.84, PGI 215.403-72(b)(3)-(c); guide p.6 and footnote 1; pricing topics TINA Lite section", "source_ids": [ "RSRC-0145", "RSRC-0143", "RSRC-0142" ], "limitations": "This library records the requirement and sends no official notice. The precise legacy pilot instrument and Component process must be checked for the actual action.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-22", "effective_date": "2026-07-22", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0168" }, { "type": "related requirement", "target": "RULE-0169" } ], "date_note": "Dates identify the cited instrument, not a retroactive change to every existing contract. Check current implementation and clause editions.", "version_state": "Selected authoritative provisions reviewed 2026-10-03; subsequent implementation and action-specific applicability require confirmation" }, { "id": "RULE-0172", "title": "Designate a COR within three business days unless the stated exemption applies", "citation": "2026-O0002 Revision 1, PGI 201.404-70(e)(1)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The adopted PGI requires COR designation within three business days of award for all service contracts, both fixed-price and other types, and supply contracts with cost-reimbursable line items, including awards by another federal agency on behalf of DoD. Its service-contract exemption requires simplified acquisition procedures, a noncomplex requirement, and a written CO explanation of why a COR is unnecessary.", "applies_when": "Awarding covered sensor/C2 support services or a supply contract with cost-reimbursable line items.", "required_action": "Plan the designation before award and track the three-business-day deadline. Apply all three conditions before using the service exemption. For geographically dispersed large contracts with multiple task orders, consider multiple or alternate CORs with distinct regional or task duties.", "exceptions": "The stated service-contract exemption is conditional; fixed-price, commercial or overseas status alone is not listed as an exemption.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF pp.22-23; Attachment 2 pp.12-13, PGI 201.404-70(e)(1)(i)-(iii)", "source_ids": [ "RSRC-0150" ], "limitations": "The rule is keyed to contract award and does not state that an option or modification restarts the clock. Determine the designation arrangement for the actual vehicle/order. No particular award or exemption has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0033" }, { "type": "related requirement", "target": "RULE-0173" }, { "type": "related requirement", "target": "RULE-0174" }, { "type": "related requirement", "target": "RULE-0176" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0173", "title": "Keep COR eligibility and written authority separate from contractor direction", "citation": "2026-O0002 Revision 1, DFARS 201.404-70/71; 252.201-7000", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "A COR must be a military or civilian employee of the U.S. Government, a foreign government, or a NATO or coalition partner; contractor personnel must never serve as CORs. When a COR appointment is anticipated, use the prescribed clause, including in commercial solicitations/contracts. The contractor receives the written designation, which defines the COR authority and forbids changes affecting price, quality, quantity, delivery or other contract terms.", "applies_when": "Selecting a COR, issuing a solicitation, or distinguishing technical monitoring from an authorized contract change.", "required_action": "Confirm personnel eligibility and applicable appointment requirements. Use the prescribed clause when required, issue the written designation and communicate its limits. Route changes to contract terms through the authorized contracting process rather than COR direction.", "exceptions": "The text permits specified government/partner employees but creates no automatic appointment, security access or command delegation. Contractor personnel are expressly excluded.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF pp.9-10; Attachment 1 pp.7-8, DFARS 201.404-70(b), 201.404-71 and 252.201-7000(a)-(b)", "source_ids": [ "RSRC-0150" ], "limitations": "The August 2026 clause prescription must be distinguished from the clause actually incorporated in an existing contract. The research does not authorize unilateral clause insertion or any contract change.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0172" }, { "type": "related requirement", "target": "RULE-0175" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0174", "title": "Use the DoDI 5000.72 certification policy reference for COR qualifications", "citation": "2026-O0002 Revision 1, DFARS 201.404-70(a); PGI 201.404-70(b)-(c)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The adopted DFARS directs use of the PGI for COR designation, assignment, qualifications and responsibilities. The PGI identifies DoDI 5000.72 as the source of certification standards tied to requirement complexity and performance risk, and says those standards should be considered during requirements development, solicitation and surveillance. The COR Guidebook provides appointment/duties guidance.", "applies_when": "Planning surveillance staffing and selecting qualified COR personnel for a new or continuing requirement.", "required_action": "Obtain the current applicable certification instruction and Component implementation; establish the risk-appropriate qualifications before appointment. Keep binding policy, minimum standards and guidebook advice distinct.", "exceptions": "The PGI uses should for considering standards through the acquisition stages; it does not reproduce the complete qualification or training scheme.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF p.9, DFARS 201.404-70(a); p.22, PGI 201.404-70(b)-(c)", "source_ids": [ "RSRC-0150" ], "limitations": "This record is a reviewed cross-reference and planning requirement, not a completed review of DoDI 5000.72. RSRC-0149 and GAP-020 retain that access limit. It asserts no COR-specific course list, certification type, training hours or waiver. Separate OGE financial-disclosure and annual ethics-training requirements are addressed in RULE-0196-0199.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0172" }, { "type": "related requirement", "target": "RULE-0175" }, { "type": "separately reviewed ethics requirement", "target": "RULE-0196" }, { "type": "separately reviewed ethics requirement", "target": "RULE-0197" }, { "type": "separately reviewed ethics requirement", "target": "RULE-0199" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0175", "title": "Maintain COR appointments and surveillance records in JAM and SPM", "citation": "2026-O0002 Revision 1, PGI 201.404-70(d), (e)(3), (f), (i)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "Components must use PIEE JAM to track COR nominations, appointments, terminations and training certifications, and SPM for other contract-surveillance actions. Each assigned contract needs an electronic COR surveillance file containing the designation/duties and actions under the delegation. Before closeout, the COR must ensure those files are complete and available to the CO.", "applies_when": "Establishing, transferring or terminating a COR assignment, conducting surveillance, or preparing closeout.", "required_action": "Keep the written designation in JAM or SPM as specified, maintain the SPM file throughout performance, and complete the closeout handoff. Use the Government systems for actual contract records; this public rules library is only a reference.", "exceptions": "These provisions prescribe the systems and minimum records; they do not authorize disclosure of contract information on a public site.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF pp.22-23; Attachment 2 pp.12-13, PGI 201.404-70(d), (e)(3), (f)(1)-(2) and (i)", "source_ids": [ "RSRC-0150" ], "limitations": "These provisions do not determine implementation under a specific Component procedure or the scope of an actual delegation.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0173" }, { "type": "related requirement", "target": "RULE-0177" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0176", "title": "Allocate cost-reimbursement supply surveillance without duplicating COR and DCMA duties", "citation": "2026-O0002 Revision 1, PGI 201.404-70(e)(2)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "For supply contracts with cost-reimbursement line items, the CO must retain surveillance activities or delegate them to a COR or DCMA. Both may receive duties on the same contract, but the same surveillance activities must not be delegated to both.", "applies_when": "A sensor, radar, camera or C2 supply contract includes cost-reimbursement line items and requires a surveillance arrangement.", "required_action": "Identify each surveillance activity and its responsible official or organization. Document retained and delegated duties, ensure coverage, and reconcile this allocation with the designation requirement in paragraph (e)(1).", "exceptions": "The allocation provision does not establish a blanket exemption from the separate COR-designation paragraph.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF p.23; Attachment 2 p.13, PGI 201.404-70(e)(2), read with (e)(1)", "source_ids": [ "RSRC-0150" ], "limitations": "A DCMA assignment does not by itself establish acceptance authority, a COR delegation, or cancellation of another duty. This entry does not evaluate a specific administration agreement.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0172" }, { "type": "related requirement", "target": "RULE-0175" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0177", "title": "Review COR files within six months, annually thereafter, and give timely feedback", "citation": "2026-O0002 Revision 1, PGI 201.404-70(g)-(h)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United States", "summary": "The CO must review COR files for accuracy and completeness within six months of contract award and annually thereafter, with results documented in SPM. More frequent later reviews may be used based on risk, complexity and value. Within 30 days after review, the CO must provide the specified supervisory performance feedback and discuss inadequacies with the COR.", "applies_when": "A contract with an assigned COR remains in administration.", "required_action": "Calendar the initial and annual reviews from the actual award and review history, record findings in SPM, and complete supervisory feedback and any discussion of inadequacies within the 30-day period.", "exceptions": "Six months and annual reviews are the stated minimum schedule; risk can justify more frequent later reviews.", "approval_authority": "Contracting officer within the cited authority; no local delegation or appointment is established by this library.", "locator": "PDF p.23; Attachment 2 p.13, PGI 201.404-70(g)-(h)", "source_ids": [ "RSRC-0150" ], "limitations": "Do not substitute an older instruction, guidebook or codified PGI timetable without reconciling the adopted August 2026 text. The complete DoDI certification review remains open; this timetable is sourced directly to the current deviation.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-08-05", "effective_date": "2026-08-05", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0175" } ], "date_note": "Revision 1 is signed August 5, 2026 and effective immediately; remains in effect until rescinded or incorporated. An administrative policy does not itself rewrite an existing contract clause.", "version_state": "August 5, 2026 adopted DFARS/PGI Part 201; selected provisions reviewed 2026-10-03" }, { "id": "RULE-0178", "title": "Establish exclusive-use eligibility before claiming duty-free cargo treatment", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), A.1 and A.3", "issuer": "USTRANSCOM / DoD; includes USEUCOM guidance", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "USEUCOM AOR; applicable treaty and host-nation scope", "summary": "Qualifying shipments must be for exclusive use of U.S. forces and accompanied by Form 302. Exclusive use includes goods for ultimate U.S.-forces use, goods used or consumed in performing a contract with or for U.S. forces, and material incorporated into their articles or facilities. Eligible delivery may be to a supporting contractor acting for U.S. forces. DoD cargo remains non-Community goods and is not in EU free circulation.", "applies_when": "Importing, transiting or exporting ABAD equipment, spares or contract-performance material through the applicable USEUCOM customs regime.", "required_action": "Document intended use, recipient and supporting contract/order purpose; coordinate eligibility and the route with the customs/transportation office. Reassess these facts when an order, modification, repair or final disposition changes the movement.", "exceptions": "Treaty, bilateral agreement, territory and shipment facts remain necessary; U.S. award, NATO/EU membership or EUCOM funding alone does not establish eligibility.", "approval_authority": "Supporting customs authorities and appointed Customs Clearance Officer (CCO); no appointment or delegation is inferred.", "locator": "PDF/printed p.1 (V-510-1), A.1 and A.3", "source_ids": [ "RSRC-0153" ], "limitations": "This is the DTR statement of the applicable DoD procedure, not an independent determination under national law. Contractor cargo eligibility does not confer personnel SOFA status, base privileges or permission to operate a sensor or effector.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0077" }, { "type": "related requirement", "target": "RULE-0111" }, { "type": "UK-specific applicability and limits", "target": "RULE-0183" } ], "date_note": "September 30 is the current chapter edition, confirmed by the official index and change register; a separate initial effective date is not established. A policy update does not itself modify an existing contract.", "version_state": "September 30, 2026 chapter; selected provisions reviewed October 3, 2026. RSRC-0154 records amendment context." }, { "id": "RULE-0179", "title": "Use the Form 302 route and elevate additional customs-document demands", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), A.2 and A.4; P.2.c-d; Q.1.a.(1)", "issuer": "USTRANSCOM / DoD; includes USEUCOM guidance", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "USEUCOM AOR; applicable treaty and host-nation scope", "summary": "With limited exceptions, the U.S. version of NATO Form 302 (AE302) is the prescribed customs document for U.S. cargo entering, transiting and leaving NATO allies and participating non-NATO/PfP nations. DoD Components must consult HQ USEUCOM before complying with host-nation demands for additional documents or automated EU submissions. Contractors should contact their CO or COR. For shipments accompanied by Form 302, A.4 states the EU commercial declaration, ENS/ICS2 and six-digit HS-code exemptions.", "applies_when": "A qualifying Form 302 shipment or a carrier/host-nation request for extra customs documents, codes or automated submissions.", "required_action": "Set the intended clearance route with transportation/customs officials and provide a CO/COR escalation contact. Apply A.2 consultation before accepting additional-document or system-submission demands; obtain a route-specific determination where the chapter also describes country forms or tariff information.", "exceptions": "A.2 expressly retains limited exceptions. A.4 is tied to shipments accompanied by Form 302, not every commercial shipment, private demonstration or contractor import.", "approval_authority": "DoD Component consultation with HQ USEUCOM; contractor route is the CO/COR, who may consult HQ USEUCOM.", "locator": "PDF/printed p.1, A.2 and A.4; pp.9-11, P.2.c-d and Q.1.a.(1)", "source_ids": [ "RSRC-0153" ], "limitations": "The chapter retains general and country references to additional forms and tariff information. Do not resolve that tension by assuming a universal exemption or automatically supplying extra documents. Follow the HQ USEUCOM consultation route. Underlying EU legislation and individual country procedures require separate review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0077" }, { "type": "UK-specific applicability and limits", "target": "RULE-0187" } ], "date_note": "September 30 is the current chapter edition, confirmed by the official index and change register; a separate initial effective date is not established. A policy update does not itself modify an existing contract.", "version_state": "September 30, 2026 chapter; selected provisions reviewed October 3, 2026. RSRC-0154 records amendment context." }, { "id": "RULE-0180", "title": "Distinguish Form 302 issuing authority from authorized cargo receipt", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), E.2.c-e; P.2.d.(4)-(5) and P.2.e.(4)", "issuer": "USTRANSCOM / DoD; includes USEUCOM guidance", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "USEUCOM AOR; applicable treaty and host-nation scope", "summary": "An appointed, authorized Customs Clearance Officer signs and stamps issued Form 302 documents. Separately, the DTR lists persons who may receive duty-free cargo and acknowledge receipt to close customs clearance, including contractors providing services directly to U.S. forces. Commercial transportation-service-provider contractor representatives cannot receive and clear U.S.-forces duty-exempt cargo on Form 302.", "applies_when": "Planning delivery, warehouse receipt or customs closure for equipment and spares, including contractor-supported locations.", "required_action": "Identify the appointed issuing CCO and an eligible receiving person before shipment. Distinguish a direct-support contractor consignee from the commercial carrier or freight provider, and verify the actual receiving arrangement with customs officials.", "exceptions": "Receipt categories are those expressly listed in P.2.d.(4); the commercial-TSP exclusion remains express. A CO warrant or COR designation alone is not a customs appointment.", "approval_authority": "Appointed CCO for issuance; eligible receiving categories under P.2.d.(4), subject to the express TSP exclusion.", "locator": "PDF/printed p.3, E.2.c-e; p.10, P.2.d.(4)-(5) and P.2.e.(4)", "source_ids": [ "RSRC-0153" ], "limitations": "Signing for customs receipt does not establish contract inspection or acceptance authority. March 10 change-register references use prior paragraph numbering; the current paragraph is P.2.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "UK-specific applicability and limits", "target": "RULE-0185" } ], "date_note": "September 30 is the current chapter edition, confirmed by the official index and change register; a separate initial effective date is not established. A policy update does not itself modify an existing contract.", "version_state": "September 30, 2026 chapter; selected provisions reviewed October 3, 2026. RSRC-0154 records amendment context." }, { "id": "RULE-0181", "title": "Keep shipment descriptions, customs evidence and reconciliation aligned", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), E.2.f and E.3-7; M.2.b.(3),(5)-(7); Q.1.a.(1)-(2)", "issuer": "USTRANSCOM / DoD; includes USEUCOM guidance", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "USEUCOM AOR; applicable treaty and host-nation scope", "summary": "Surface-shipment customs requests require specific cargo descriptions, written follow-up and supporting shipping/purchase documents; generic descriptions such as electronic parts are insufficient. Customs documents must be supported, signed by the appointed CCO and accounted for. E.6 requires reconciliation within 30 days of shipment and a quarterly report; completed customs files are closed annually and retained for at least six full calendar years under M.2.b.(7).", "applies_when": "Preparing deliveries or maintaining customs records for orders, modifications, spares, returns and other covered shipments.", "required_action": "Plan accurate item descriptions and traceable shipment support; route changes through the CCO rather than altering forms. Coordinate reconciliation and discrepancy correction with the customs custodian, and preserve the applicable shipping/receipt evidence through contract administration and closeout.", "exceptions": "Country procedures can differ; read additional-document and tariff references with A.2/A.4 and HQ USEUCOM consultation. Investigation and disciplinary files remain open until action is completed under the M.2.b.(7) note.", "approval_authority": "Appointed CCO and Service-component customs records program; CO/COR coordinates contract and shipment evidence within their own authority.", "locator": "PDF/printed pp.3-4, E.2.f and E.3-7; p.7, M.2.b.(3),(5)-(7); p.11, Q.1.a.(1)-(2)", "source_ids": [ "RSRC-0153" ], "limitations": "These are customs-program responsibilities and retention periods, not a replacement for contract-file retention or a new CO delegation. The suggested acquisition documentation is an analytical implementation aid.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0179" }, { "type": "related requirement", "target": "RULE-0180" } ], "date_note": "September 30 is the current chapter edition, confirmed by the official index and change register; a separate initial effective date is not established. A policy update does not itself modify an existing contract.", "version_state": "September 30, 2026 chapter; selected provisions reviewed October 3, 2026. RSRC-0154 records amendment context." }, { "id": "RULE-0182", "title": "Plan agricultural preclearance before equipment returns to the United States", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), C.1.a-g; Figure 510-2", "issuer": "USTRANSCOM / DoD; includes USEUCOM guidance", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "USEUCOM AOR; applicable treaty and host-nation scope", "summary": "For DoD cargo moving from USEUCOM to or through CONUS, the shipper must arrange agricultural preclearance and correct deficiencies. Inspection occurs before boxing, pallet buildup or container loading. The agent signs and stamps DD Form 2855 for compliant cargo. Cargo arriving for departure without the required signed/stamped label is not accepted for movement and may be returned or held in bond at the shipper's expense.", "applies_when": "Returning sensors, radar, cameras, C2 hardware or other DoD cargo to or through CONUS for repair, warranty work, relocation or disposition.", "required_action": "Coordinate with the supporting Movement Control Team/Transportation Officer and the customs agricultural preclearance office before packaging. Identify the shipper and allocate cleaning, inspection, packaging, label and delay responsibilities in acquisition planning or an authorized contract change.", "exceptions": "The reviewed process is the CONUS return/transit process. DD Form 2855 is agricultural preclearance; Figure 510-2 states that it does not clear U.S. customs.", "approval_authority": "Shipper, supporting MCT/Transportation Officer and authorized military customs border-clearance agent as specified in C.1.", "locator": "PDF/printed pp.2-3, C.1.a-g; p.61, Figure 510-2", "source_ids": [ "RSRC-0153" ], "limitations": "ECM 4002.01 detailed standards remain unreviewed. Customs, export-control, hazardous-material, transportation and contract-acceptance requirements are separate questions. No actual contract is changed by this research.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0181" } ], "date_note": "September 30 is the current chapter edition, confirmed by the official index and change register; a separate initial effective date is not established. A policy update does not itself modify an existing contract.", "version_state": "September 30, 2026 chapter; selected provisions reviewed October 3, 2026. RSRC-0154 records amendment context." }, { "id": "RULE-0183", "title": "Screen UK contractor repair and production movements for visiting-force eligibility", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), SSS.1.a-b and SSS.1.c", "issuer": "USTRANSCOM / DoD; USAFE-UK customs implementation", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom; action and recipient-specific", "summary": "The UK section excludes specified movements from U.S. visiting-force customs actions: contractor repair/calibration followed by return outside the UK, production exports, imports of government-furnished material for incorporation into exported products, and specified FMS, loan and transfer movements. Qualifying exclusive-use shipments remain bonded and require customs entry for each movement outside the UK. Generic cargo descriptions are insufficient.", "applies_when": "Choosing a UK supplier, repair/calibration source, delivery route or GFE processing arrangement for ABAD equipment.", "required_action": "Identify the transaction, final recipient and destination before choosing customs treatment. Obtain USAFE-UK Transportation and Customs instructions; describe the actual goods and use. Screen changed destinations, repair returns and GFE movements again during orders, modifications and administration.", "exceptions": "The exclusion concerns the listed nonqualifying movements; it is not a finding that every contractor-supported shipment is ineligible for every relief.", "approval_authority": "USAFE-UK Host Nation Coordination Cell / Transportation and Customs, with the responsible recipient and customs authorities.", "locator": "PDF/printed pp.58 and 60, SSS.1.a-b and SSS.1.c", "source_ids": [ "RSRC-0153" ], "limitations": "USAFEI 24-401 is a referenced but unreviewed instruction (RSRC-0157). This DTR-based finding does not establish all UK duties, VAT, contractor status or licensing rules.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0179" } ], "date_note": "Current chapter edition, not an independently established original effective date. The UK text is SSS; older amendment-register entries use RRR. New research does not itself amend an existing contract.", "version_state": "September 30, 2026 DTR; selected UK provisions reviewed October 3, 2026" }, { "id": "RULE-0184", "title": "Place UK contractor export responsibilities in purchase and support terms", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), SSS.1.b.(1) and SSS.1.b.(2)(a)-(b)", "issuer": "USTRANSCOM / DoD; USAFE-UK customs implementation", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom; action and recipient-specific", "summary": "Contracts and other purchase arrangements must make the UK contractor responsible for export declarations for every transport mode, including new goods, repaired goods and GFE incorporated into a product. Terms must place the exporter-of-record role with that contractor, and shipping documents must identify it as origin. DCMA transportation administration is a consideration, not a transfer of exporter-of-record responsibility.", "applies_when": "Buying from a UK contractor or arranging export after repair, calibration or incorporation of furnished equipment.", "required_action": "Check exporter-of-record, export-declaration and shipping-document responsibilities in the solicitation, order and support terms. For an existing contract, compare its terms with the actual movement and use the authorized change process if obligations need correction. For the specified road routes, identify responsibility for resulting transit-document closure.", "exceptions": "The export rules distinguish UK contractor and British Forces origin. Considering DCMA as transportation administrator does not make DCMA the exporter of record.", "approval_authority": "Contracting officer for authorized terms; UK contractor for the stated export role; receiving unit and host-nation customs for applicable transit closure.", "locator": "PDF/printed pp.58-59, SSS.1.b.(1) and SSS.1.b.(2)(a)-(b)", "source_ids": [ "RSRC-0153" ], "limitations": "This is a prescribed responsibility allocation, not permission to export controlled items or a determination of contract scope, consideration or authority to modify.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0183" }, { "type": "related requirement", "target": "RULE-0036" } ], "date_note": "Current chapter edition, not an independently established original effective date. The UK text is SSS; older amendment-register entries use RRR. New research does not itself amend an existing contract.", "version_state": "September 30, 2026 DTR; selected UK provisions reviewed October 3, 2026" }, { "id": "RULE-0185", "title": "Consign UK contractor imports to the actual recipient and obtain customs entry", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), SSS.1.b.(3)(a)-(b)", "issuer": "USTRANSCOM / DoD; USAFE-UK customs implementation", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom; action and recipient-specific", "summary": "Shipments destined for UK contractors or British Forces must name that recipient; a U.S. Forces DoDAAC cannot be substituted. U.S. Forces in the UK may not import and transfer these goods as a workaround, including loan equipment, GFE and DoD repair-return property. At the specified military-airlift entry route, goods cannot be released until the customs import declaration is raised and presented to USAFE-UK Transportation and Customs.", "applies_when": "Sending sensors, effectors, C2 hardware or GFE to a UK contractor, including repair-and-return shipments.", "required_action": "Use the contractor/recipient address or appropriate identifier and arrange its customs instructions before dispatch. Keep contractor-destined goods separate where the specified sealift procedure requires it, and plan evidence of customs entry before release through the military-airlift route.", "exceptions": "The cited rule concerns UK contractor/British Forces recipients and specifies different commercial and military-airlift arrangements.", "approval_authority": "Actual consignee and its customs arrangements; USAFE-UK Transportation and Customs for the specified military-airlift release process.", "locator": "PDF/printed p.59, SSS.1.b.(3)(a)-(b)", "source_ids": [ "RSRC-0153" ], "limitations": "DoD ownership or a U.S. contract does not convert the recipient into a U.S. Forces customs consignee. No importer-of-record appointment, contractor personnel status or tax exemption is established here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0180" }, { "type": "related requirement", "target": "RULE-0183" } ], "date_note": "Current chapter edition, not an independently established original effective date. The UK text is SSS; older amendment-register entries use RRR. New research does not itself amend an existing contract.", "version_state": "September 30, 2026 DTR; selected UK provisions reviewed October 3, 2026" }, { "id": "RULE-0186", "title": "Complete UK customs actions before releasing previously imported equipment for repair", "citation": "DTR 4500.9-R Part V, Chapter 510 (September 30, 2026), SSS.1.b.(4)", "issuer": "USTRANSCOM / DoD; USAFE-UK customs implementation", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom; action and recipient-specific", "summary": "For goods previously imported serviceable for U.S. Forces use in the UK and later sent to a UK repair facility, release must wait until the receiving contractor completes the required customs actions, usually inward processing relief. USAFE-UK Transportation and Customs must be contacted so supporting copies are on file before release. The provision also conditions transfers to British Forces on eligibility and completed customs actions.", "applies_when": "Administering a repair, warranty, calibration or support action involving covered equipment already held by U.S. Forces in the UK.", "required_action": "Establish the customs release prerequisite with property, transportation and contract-administration staff before handing equipment to the repair contractor. Plan the documentation, responsible parties and return arrangement in new work or authorized changes to continuing work.", "exceptions": "This specific repair rule addresses goods previously imported serviceable for U.S. Forces use in the UK; other imports follow their applicable route.", "approval_authority": "Receiving UK contractor for required customs actions; USAFE-UK Transportation and Customs for coordination and file evidence.", "locator": "PDF/printed pp.59-60, SSS.1.b.(4)", "source_ids": [ "RSRC-0153" ], "limitations": "The DTR says inward processing is usual, not automatic. Customs completion does not replace property accountability, contract inspection/acceptance or export-control analysis.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-30", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0185" }, { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0182" } ], "date_note": "Current chapter edition, not an independently established original effective date. The UK text is SSS; older amendment-register entries use RRR. New research does not itself amend an existing contract.", "version_state": "September 30, 2026 DTR; selected UK provisions reviewed October 3, 2026" }, { "id": "RULE-0187", "title": "Check UK Form 302 eligibility and licensing separately", "citation": "HMRC Military mobility: Who can use NATO form 302; Licensing (February 5, 2026)", "issuer": "HM Revenue & Customs", "instrument_type": "Guidance", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "United Kingdom; confirm territorial and transaction scope", "summary": "HMRC limits Form 302 to eligible military movements and excludes commercial transactions, including purchases, sales and transfers between military authorities. Out-of-scope, licensed or special-procedure movements require a full CDS declaration. Extending Crown Exemption to a third party requires written Export Control Joint Unit approval.", "applies_when": "Assessing the UK clearance route for equipment or contractor-supported movements.", "required_action": "Confirm eligibility, licensing and written exemption authority with the responsible customs and export-control offices.", "exceptions": "A carrier moving eligible military equipment for a force is not automatically conducting an excluded commercial equipment transaction.", "approval_authority": "Export Control Joint Unit for the stated third-party exemption; relevant customs authorities for clearance.", "locator": "Who can use NATO form 302; Licensing", "source_ids": [ "RSRC-0156" ], "limitations": "Guidance, not statutory text; underlying regulations and case-specific permissions remain unreviewed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-05", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related UK implementation", "target": "RULE-0183" }, { "type": "related UK implementation", "target": "RULE-0184" }, { "type": "related UK implementation", "target": "RULE-0185" } ], "date_note": "The guidance page and update history identify February 5, 2026; no independent statutory commencement is inferred.", "version_state": "Official guidance published/updated February 5, 2026; reviewed October 3, 2026" }, { "id": "RULE-0188", "title": "Coordinate quality changes and keep inspection instructions within the contract", "citation": "2026-O0035: DFARS 246.103 and 246.401; PGI 246.103(2)", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "The contracting office must coordinate with the quality-assurance activity before changing any quality requirement. Except for simplified-acquisition-procedure contracts, each contract must address and document the need for a quality assurance surveillance plan. Technical inspection instructions must remain contract-specific and within contracted requirements.", "applies_when": "Planning inspection or changing specifications, test criteria or surveillance for equipment or support services.", "required_action": "Coordinate proposed changes with the responsible quality activity; document the QASP-need assessment where required. Use specific, minimum technical instructions and periodically reassess them with the administration office.", "exceptions": "DFARS 246.401 says the CO should prepare a QASP for services and should address its need for supplies; it does not mandate a QASP for every acquisition. The stated SAP exception is to the QASP-need documentation rule.", "approval_authority": "Contracting office and responsible technical/quality-assurance activity; contract administration office receives inspection instructions.", "locator": "Attachment A1 pp.1,3-4 (PDF pp.3,5-6); attachment A2 pp.1-2 (PDF pp.36-37)", "source_ids": [ "RSRC-0159" ], "limitations": "PGI instructions cannot cure incomplete contractual quality requirements, impose greater inspection than the contract, demand all characteristics without specificity, or continue inspection unnecessarily when statistically sound sampling suffices. This is not authority for a COR to change the contract.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0173" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0189", "title": "Apply the specific limits on government inspection at source", "citation": "2026-O0035: DFARS 246.402 and 246.404", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "Source government quality assurance is prohibited for contracts or delivery orders below $400,000 unless mandated by DoD regulation, required by an acquiring/administration-agency agreement, or justified by the CO under all three specified technical, product and contractor criteria. Actions at or below the simplified acquisition threshold also must meet 246.402 criteria.", "applies_when": "Deciding whether to require government quality assurance at a supplier or production location.", "required_action": "Identify the applicable value test and record the qualifying regulation, agreement or CO determination. For the determination route, establish significant technical requirements; critical characteristics, specific features or acquisition concerns requiring source QA; and a manufacturer/producer or necessary and feasible verification at a nonmanufacturer.", "exceptions": "The $400,000 test is below that value; the SAP provision covers at or below its applicable threshold. This source-QA threshold does not define the simplified acquisition threshold.", "approval_authority": "Contracting officer for the specified determination; responsible agencies for their agreement.", "locator": "Attachment A1 p.4 (PDF p.6), 246.402(1)-(3)(i)-(iii) and 246.404", "source_ids": [ "RSRC-0159" ], "limitations": "A limit on government QA at source is not permission to omit contractual quality requirements, destination inspection or authorized acceptance. Apply the actual action value and current threshold rules.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0188" }, { "type": "related requirement", "target": "RULE-0039" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0190", "title": "Use the applicable international agreement for foreign-government quality assurance", "citation": "2026-O0035: DFARS 246.406(1)-(3)", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "Departments and agencies must follow STANAG 4107 when requesting QA from a NATO member or performing QA requested by a NATO member or organization. Ratification reservations matter. Country MOUs should be checked for reciprocal-QA annexes.", "applies_when": "An overseas purchase or support arrangement proposes government inspection by, or for, a foreign government.", "required_action": "Route the request through responsible QA and contracting offices; obtain the applicable STANAG terms, reservations and country agreement before assigning the work.", "exceptions": "For non-NATO international military sales, agencies perform QA under the contract or agreement, inform participants about QA publications and delegate to the host government when satisfactory services are available.", "approval_authority": "Responsible department/agency and QA/administration officials under the applicable agreement; no local delegation inferred.", "locator": "Attachment A1 pp.4-5 (PDF pp.6-7), 246.406", "source_ids": [ "RSRC-0159" ], "limitations": "The full STANAG, Allied Quality Assurance Publications and country MOU annexes remain unreviewed. NATO membership alone supplies no contracting, acceptance, payment or operational authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0189" }, { "type": "related requirement", "target": "RULE-0193" }, { "type": "related requirement", "target": "RULE-0178" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0191", "title": "Request a remedy for qualifying defects discovered after acceptance and warranty expiry", "citation": "2026-O0035: DFARS 246.407-70(a)", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "When a defect is discovered after acceptance, appears to be the contractor’s fault, any warranty has expired and no other contractual remedy remains, the CO must notify the contractor in writing and request repair, replacement or service at no government cost. The CO may accept consideration if offered.", "applies_when": "All four conditions in 246.407-70(a) are satisfied after delivery or completed service.", "required_action": "Establish acceptance, apparent responsibility, warranty status and remaining remedies; issue the required written notice and request, and record any offered consideration.", "exceptions": "If a warranty or another contractual remedy is available, this narrow fallback is not the governing basis for that remedy.", "approval_authority": "Contracting officer; coordinate disputed facts and available remedies with technical and legal advisers.", "locator": "Attachment A1 p.5 (PDF p.7), 246.407-70(a)(1)-(3)", "source_ids": [ "RSRC-0159" ], "limitations": "The provision requires a request. It does not itself compel free corrective work, revive an expired warranty or create a debt. Referenced refund procedures in subpart 242.71 are outside this review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0194" }, { "type": "related requirement", "target": "RULE-0195" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0192", "title": "Use the clause-based procedure for additional inspection and retest costs", "citation": "2026-O0035: DFARS 246.470-1; FAR 52.246-2 reference", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "Under FAR 52.246-2, a QAR who considers additional costs warranted must recommend action and an amount to the CO. If the CO agrees, written notice and a payment demand using FAR 32.6 collection procedures are required.", "applies_when": "Delay, reinspection or retesting potentially supports additional costs under an applicable Inspection of Supplies—Fixed-Price clause.", "required_action": "Verify the contract clause and facts; evaluate frequency under current and prior contracts, cause, and recovery expense. Use the applicable agency, foreign military sale or public rate at the time of the delay, reinspection or retest; document the QAR recommendation and CO decision.", "exceptions": "This provision is tied to FAR 52.246-2; do not transplant its remedy into contracts governed by different inspection terms without an applicable basis.", "approval_authority": "QAR recommends; contracting officer decides and issues the written notice/demand.", "locator": "Attachment A1 p.6 (PDF p.8), 246.470-1(a)-(c)", "source_ids": [ "RSRC-0159" ], "limitations": "No automatic assessment or offset is established. Full FAR 32.6 debt-collection procedure and every clause exception were not independently reviewed here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0191" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0193", "title": "Distinguish shipment release and inspection stamps from acceptance", "citation": "2026-O0035: DFARS 246.471; PGI 246.472(a)(iii); adopted RFO FAR 46.501-.502", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "Government inspection stamps do not establish acceptance. Ordinarily acceptance is documented by an authorized certificate and remains the CO’s responsibility unless assigned to a contract administration office or another agency. Source-inspected shipment release has a separate authorization procedure.", "applies_when": "Releasing, receiving or accepting source-inspected equipment, including shipments under an existing order.", "required_action": "Identify who holds acceptance responsibility and the contract’s timing and evidence requirements. For alternative contractor release, obtain written CAO authorization, require the prescribed signed shipping statement and process the authorized receiving report.", "exceptions": "Alternative contractor shipment release is unavailable for FMS contracts. It requires that government signing/stamping interferes with or consumes too much QA time, production continuity supports ongoing evaluation, and contractor quality including shipment preparation is satisfactory. Withdraw authorization in writing when there is an indication those conditions no longer exist.", "approval_authority": "Contract administration office authorizes alternative shipment release; CO or the assigned administration office/agency has acceptance responsibility.", "locator": "Attachment A1 pp.6-8 (PDF pp.8-10); attachment A2 p.5 (PDF p.40); RFO FAR 46.501-.502", "source_ids": [ "RSRC-0159", "RSRC-0160" ], "limitations": "Acceptance timing and retained rights remain subject to the contract and applicable exceptions. Shipment release, customs clearance and inspection marking are not interchangeable with acceptance.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0178" }, { "type": "related requirement", "target": "RULE-0191" }, { "type": "related requirement", "target": "RULE-0214" }, { "type": "selected first-article requirement", "target": "RULE-0227" }, { "type": "related requirement", "target": "RULE-0250" }, { "type": "related requirement", "target": "RULE-0251" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0194", "title": "Obtain warranty approval unless a specified exception applies", "citation": "2026-O0035: DFARS 246.703-1", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "The chief of the contracting office must approve use of a warranty unless one of four stated acquisition categories applies, and may approve only when expected benefits outweigh cost.", "applies_when": "Selecting warranty coverage for a new award, order or authorized change to support terms.", "required_action": "Identify the acquisition category and document the approval route and expected benefit/cost basis. Align the resulting coverage, duration and remedy with the contract.", "exceptions": "Exceptions: commercial products/services; technical data unless extended liability is provided; fixed-price supplies/services with QA provisions referencing higher-level quality requirements; and construction supplies/services using warranties in federal, military or construction guide specifications.", "approval_authority": "Chief of the contracting office for the stated approval. Organizational membership does not identify the person holding that authority.", "locator": "Attachment A1 pp.9-10 (PDF pp.11-12), 246.703-1(1)-(2)", "source_ids": [ "RSRC-0159" ], "limitations": "An approval exception is not a waiver of all warranty, pricing or contracting requirements. Selected data-warranty and extended-liability provisions are addressed in RULE-0242 through RULE-0246; GAP-027 preserves unresolved cross-references and implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0191" }, { "type": "related requirement", "target": "RULE-0195" }, { "type": "related requirement", "target": "RULE-0242" }, { "type": "related requirement", "target": "RULE-0246" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0195", "title": "Complete serialized-item warranty attachments at the correct milestones", "citation": "2026-O0035: DFARS 246.710(3); PGI 246.710-70(1)-(6)", "issuer": "DoD / DPCAP", "instrument_type": "Class deviation", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. defense acquisition; overseas applicability depends on the action and agreement", "summary": "When a solicitation includes 252.211-7003 and serialized-item warranties are anticipated, 246.710(3) prescribes warranty tracking and repair-source attachments and clause 252.246-7006. Warranty-tracking fields are due at award except the UII, which is due by presentation for receipt and/or acceptance; repair-source instructions are due by that same presentation milestone.", "applies_when": "Both the item-identification clause and anticipated serialized-item warranty conditions are met.", "required_action": "Use the official electronic attachment formats. If government-specified, obtain requiring-activity warranty terms by line item before solicitation. Use 252.246-7005 when government terms are not specified and offeror data is required. Complete the UII and repair-source data by receipt/acceptance and ensure completed attachments are uploaded to EDA.", "exceptions": "The tracking attachment’s UII field may follow award; its other fields cannot use that extension. Before solicitation, government-specified warranty terms must include at least one starting event, usage, duration or fixed expiration date for each warranted item.", "approval_authority": "CO manages prescribed terms, clauses and EDA upload; requiring activity supplies specified terms; contractor supplies the prescribed UII and repair-source information.", "locator": "Attachment A1 p.11 (PDF p.13), 246.710(3); attachment A2 pp.6-7 (PDF pp.41-42), PGI 246.710-70(1)-(6)", "source_ids": [ "RSRC-0159" ], "limitations": "This conditional prescription does not require warranties on every serialized or COTS item. Full 252.211-7003 applicability and every warranty-clause term require separate action-specific review; no automatic amendment of an existing contract is inferred.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0193" }, { "type": "related requirement", "target": "RULE-0194" }, { "type": "related requirement", "target": "RULE-0247" } ], "date_note": "Signed January 20, 2026; mandatory use begins February 1, 2026. Continues until rescinded or incorporated; no fixed expiration is stated.", "version_state": "2026-O0035, January 20, 2026; selected provisions checked October 3, 2026 against the current official RFO index" }, { "id": "RULE-0196", "title": "Assess COR financial-disclosure status from duties and authorized criteria", "citation": "5 CFR 2634.904(a)(1), (b); 2634.905; DPAP memorandum March 30, 2015 (historical context)", "issuer": "U.S. Office of Government Ethics", "instrument_type": "Regulation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. executive-branch personnel within the cited coverage; includes covered overseas personnel", "summary": "For employees in the covered pay/grade categories, confidential filing depends on agency findings about personal and substantial participation, significant judgment, and lack of substantial supervision/review in procurement or other specified actions; an agency may also require filing to address real or apparent conflicts. COR designation alone does not resolve the determination.", "applies_when": "Selecting or changing the duties of covered U.S. Government personnel who will oversee sensor, effector or C2 acquisition or performance.", "required_action": "Coordinate the position/duties assessment with contracting and the ethics office. Confirm the applicable filer category, agency decision and any authorized exclusion. Use an alternative to OGE Form 450 only under a procedure with prior written OGE approval.", "exceptions": "The agency head or designee may exclude an individual or class, in whole or part, when position duties make a real or apparent conflict remote. Substantial supervision affects one criterion but does not eliminate the independent conflict-based designation route. Public filers, special Government employees and supplemental reports require their separate rules.", "approval_authority": "Agency determines coverage; agency head/designee grants the cited exclusion; OGE approves alternative procedures. The 2015 DoD memo calls for CO judgment under Title 5 and referral of questions to local ethics counsel.", "locator": "2634.904(a)(1)(i)-(ii), (b); 2634.905; signed DPAP memo p.1, first substantive paragraph", "source_ids": [ "RSRC-0162", "RSRC-0161" ], "limitations": "The 2015 memo is historical explanatory policy, not a substitute for current regulations or the inaccessible full instruction. No particular COR is designated or exempted, and foreign-government/NATO eligibility to serve as a COR does not itself establish U.S. employee ethics-rule coverage.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2018-07-18", "effective_date": "2019-01-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0009" }, { "type": "related requirement", "target": "RULE-0173" }, { "type": "related requirement", "target": "RULE-0174" }, { "type": "related requirement", "target": "RULE-0197" } ], "date_note": "Published revision 2018-07-18, effective 2019-01-01; current eCFR text displayed through October 1, 2026. No fixed expiration is stated. The title-wide update date is not a section amendment date.", "version_state": "Current eCFR selected provisions, displayed through 2026-10-01 and reviewed 2026-10-03; authoritative but unofficial electronic edition" }, { "id": "RULE-0197", "title": "Calendar confidential filing from appointment and covered service", "citation": "5 CFR 2634.903(a)-(b), (d)-(e)", "issuer": "U.S. Office of Government Ethics", "instrument_type": "Regulation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. executive-branch personnel within the cited coverage; includes covered overseas personnel", "summary": "A covered new entrant generally files within 30 days of assuming the position; an agency may require pre-service filing. A covered incumbent serving more than 60 days during the calendar year generally files by February 15 of the next year. Confidential filers do not file termination reports.", "applies_when": "A covered employee enters, continues, temporarily fills or leaves a COR or other procurement-related filing position.", "required_action": "Determine the correct filer category and agency deadline before assignment; track service days, acting assignments, changes of duties and approved extensions with the ethics office. For the non-SGE short-service exception, reassess actual service and file within 15 calendar days after day 60 if the threshold is crossed.", "exceptions": "New-entrant exceptions include a qualifying covered-position transfer within 30 days with prior reporting satisfied, a report already filed for the appointment, or a DAEO/delegate determination that non-SGE service is not expected to exceed 60 days in 12 months. Incumbent filing is not required if the filer leaves government or the covered position before the due date. SGEs and supplemental confidential reports have separate provisions. For good cause, the agency reviewing official may grant extensions totaling no more than 90 days; 2634.903(d)(2) separately covers qualifying emergency-related service/hospitalization.", "approval_authority": "Agency for earlier entry filing; DAEO/delegate for the short-service determination; agency reviewing official for good-cause extensions.", "locator": "2634.903(a), (b)(1)-(3), (d)(1)-(3), (e)", "source_ids": [ "RSRC-0162" ], "limitations": "Use the agency calendar and applicable special rules. USAFE/EUCOM funding or a permanent overseas duty station does not by itself establish the emergency-related extension. These are confidential-report rules, not the public-report termination regime.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2018-07-18", "effective_date": "2019-01-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0196" }, { "type": "related requirement", "target": "RULE-0198" }, { "type": "related requirement", "target": "RULE-0199" } ], "date_note": "Published revision 2018-07-18, effective 2019-01-01; current eCFR text displayed through October 1, 2026. No fixed expiration is stated. The title-wide update date is not a section amendment date.", "version_state": "Current eCFR selected provisions, displayed through 2026-10-01 and reviewed 2026-10-03; authoritative but unofficial electronic edition" }, { "id": "RULE-0198", "title": "Keep confidential financial reports and their contents nonpublic", "citation": "5 CFR 2634.901(d)", "issuer": "U.S. Office of Government Ethics", "instrument_type": "Regulation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. executive-branch personnel within the cited coverage; includes covered overseas personnel", "summary": "Confidential financial disclosure reports and their contents must be withheld from the public. The regulation identifies limited court-order, Privacy Act/records-system and specially required statutory-release circumstances.", "applies_when": "Handling financial-disclosure information associated with procurement or COR duties, including coordination of appointment and continuing oversight.", "required_action": "Use authorized ethics reporting and records channels. As an implementation practice, coordinate required status evidence without copying financial contents into a public acquisition reference or general surveillance product; resolve any disclosure request with the responsible ethics/privacy office.", "exceptions": "Release may occur under the specified federal-court order or applicable Privacy Act and records-system provisions. Where a statute separately requires public reporting of particular information collected on the same form, only that statutory information may be released under that statute.", "approval_authority": "Agency personnel handling the reports under applicable ethics, privacy and records authorities; no independent CO public-release authority is inferred.", "locator": "2634.901(d)", "source_ids": [ "RSRC-0162" ], "limitations": "This public library contains the rules only. It does not collect completed disclosures or determine every permitted internal disclosure, retention schedule or FOIA response.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2018-07-18", "effective_date": "2019-01-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0196" }, { "type": "related requirement", "target": "RULE-0197" }, { "type": "related requirement", "target": "RULE-0175" } ], "date_note": "Published revision 2018-07-18, effective 2019-01-01; current eCFR text displayed through October 1, 2026. No fixed expiration is stated. The title-wide update date is not a section amendment date.", "version_state": "Current eCFR selected provisions, displayed through 2026-10-01 and reviewed 2026-10-03; authoritative but unofficial electronic edition" }, { "id": "RULE-0199", "title": "Track annual ethics training independently of COR certification", "citation": "5 CFR 2638.307(a)-(f)", "issuer": "U.S. Office of Government Ethics", "instrument_type": "Regulation", "topic": "Contract oversight", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. executive-branch personnel within the cited coverage; includes covered overseas personnel", "summary": "Covered non-public-filer employees must complete annual ethics training by calendar-year end. Coverage includes required annual confidential filers, specified contracting officers and other designated categories. Agencies must provide one hour of duty time for interactive training and written-material review, and completion must be recorded.", "applies_when": "Planning and tracking continuing ethics training for covered contracting staff and CORs during contract performance.", "required_action": "Confirm coverage with the ethics office, schedule completion before year-end and preserve the approved completion record. Training must address financial conflicts, impartiality, misuse of position and gifts, with the specified written materials or access instructions and ethics-office contact information.", "exceptions": "The annual-confidential-filer category excludes employees who cease that status before year-end; independent coverage may still apply. Public filers follow separate requirements. A DAEO impracticability determination permits written materials only for qualifying SGEs expected to work no more than 60 days/year or uniformed-service officers on active duty no more than 30 consecutive days.", "approval_authority": "DAEO determines appropriate content, applicable narrow format exceptions and confirmation procedures; employee completes training; agency supplies duty time.", "locator": "2638.307(a)(1)-(4), (b)-(f)", "source_ids": [ "RSRC-0163" ], "limitations": "One hour is required duty time, not a new minimum course-duration rule. Presenter knowledge or approved automated tracking may satisfy the confirmation procedure. This regulation does not establish the full DoDI/DAF COR certification curriculum or authorize a certification waiver to displace ethics requirements.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2016-11-02", "effective_date": "2017-01-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0174" }, { "type": "related requirement", "target": "RULE-0196" }, { "type": "related requirement", "target": "RULE-0197" } ], "date_note": "Published revision 2016-11-02, effective 2017-01-01; current eCFR text displayed through October 1, 2026. No fixed expiration is stated. The title-wide update date is not a section amendment date.", "version_state": "Current eCFR selected provisions, displayed through 2026-10-01 and reviewed 2026-10-03; authoritative but unofficial electronic edition" }, { "id": "RULE-0200", "title": "Establish XaaS pilot eligibility, approval and measurable outcomes", "citation": "P.L.118-31 section 809(a)-(b), (g); DPCAP Revision 1 memo pp.1-2; Attachment 1 Revision 1", "issuer": "U.S. Congress / DoD DPCAP", "instrument_type": "Policy memorandum", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "The pilot concerns a technology-supported capability metered and billed by actual usage at fixed-price units. Agreements must require measurable outcomes, including cost and delivery speed compared with non-XaaS processes at customary intervals. A subscription label alone does not establish eligibility.", "applies_when": "Considering software, data or another consumption-based capability for ABAD through the XaaS pilot.", "required_action": "Define usage units, outcome measures and comparison intervals; check the attachment PSC categories and seek DPCAP/CP approval using the prescribed application. Address enterprise software sourcing where applicable and document independent funding, cyber, licensing and contracting authority.", "exceptions": "Initial categories are SaaS, DaaS and narrowly defined short-term, temporary, non-exclusive commercial coworking. Additional PSCs may be proposed for consideration. Classified coworking also needs relevant DoD/MILDEP security approval. Neither an unlisted PSC nor a routine fixed subscription automatically qualifies.", "approval_authority": "DPCAP and Contract Policy approve pilot participation; the memo says approve/disapprove within 30 days of receipt. Elapsed time is not approval.", "locator": "Section 809(a)-(b), (g), 137 Stat.320-321; memo p.1 definition/PSC paragraphs and p.2 application/approval bullets; Attachment 1 p.1", "source_ids": [ "RSRC-0164", "RSRC-0165", "RSRC-0167" ], "limitations": "Program approval is not a warrant, an OT authority, a funding exception or an authorization to operate. No actual requirement has been accepted into the pilot. Statutory currency and implementation limits remain in GAP-021.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-08-21", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0201" }, { "type": "related requirement", "target": "RULE-0202" }, { "type": "related requirement", "target": "RULE-0203" }, { "type": "related requirement", "target": "RULE-0204" } ], "date_note": "P.L.118-31 enacted December 22, 2023; signed Revision 1 memo dated August 21, 2025, with no separate effective date stated. No section 809 sunset is stated in the reviewed editions. Current statute after the January 2026 compilation remains a currency check.", "version_state": "August 21, 2025 Revision 1 memo plus enacted section 809; January 2026 compilation corroboration, later statutory currency not conclusively established" }, { "id": "RULE-0201", "title": "Plan the XaaS approval, public notice and justification sequence", "citation": "P.L.118-31 section 809(c)-(d); DPCAP Revision 1 memo p.2", "issuer": "U.S. Congress / DoD DPCAP", "instrument_type": "Policy memorandum", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "After pilot approval, the memo requires a public notice allowing at least 60 days for receipt of proposals and a justification for each pilot contract, posted 60 days before award. The statute sets a practicable target of agreement within 100 days after the participation notice.", "applies_when": "Scheduling an approved XaaS pilot acquisition and the required acquisition-file decisions.", "required_action": "Obtain approval before posting the notice; calendar the proposal period and justification posting. The memo cites FAR 6.302-5 and 6.305(d)(1)/(2); confirm current adopted equivalents, the actual basis for any limited competition and applicable approvals before award. Include presolicitation notices within the memo's 60-day window.", "exceptions": "The 100-day target is expressly to the extent practicable. The memo describes its trigger as synopsizing the action or posting the justification; preserve the statute's participation-notice trigger when planning. Do not subtract the periods to invent a mandatory 40-day award window.", "approval_authority": "DPCAP/CP approves participation; CO carries out notice and justification procedures under applicable current authority.", "locator": "Section 809(c)-(d); memo p.2 approval, notice, justification and final timing bullets", "source_ids": [ "RSRC-0164", "RSRC-0165" ], "limitations": "The statute's competition exemption in 809(e)(2) expressly addresses qualifying modifications; the memo's requirement to prepare a justification does not establish a blanket initial-award sole-source exemption. The memo predates RFO implementation. Resolve this relationship and current references with policy/counsel under GAP-021.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-08-21", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0200" }, { "type": "related requirement", "target": "RULE-0203" } ], "date_note": "P.L.118-31 enacted December 22, 2023; signed Revision 1 memo dated August 21, 2025, with no separate effective date stated. No section 809 sunset is stated in the reviewed editions. Current statute after the January 2026 compilation remains a currency check.", "version_state": "August 21, 2025 Revision 1 memo plus enacted section 809; January 2026 compilation corroboration, later statutory currency not conclusively established" }, { "id": "RULE-0202", "title": "Keep price-reasonableness analysis despite XaaS certified-data relief", "citation": "P.L.118-31 section 809(e)(1); DPCAP Revision 1 memo pp.1-2", "issuer": "U.S. Congress / DoD DPCAP", "instrument_type": "Policy memorandum", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "Section 809 exempts qualifying pilot agreements from 10 USC 3702. The memo says individual deviations from the implementing certified cost/pricing-data requirements may be needed, limits that deviation to new awards, and still requires a price-reasonableness determination.", "applies_when": "Pricing a qualifying pilot award or considering pricing treatment of a later modification.", "required_action": "Establish actual pilot acceptance and the required individual deviation under current agency procedures, include the approved deviation with the application when applicable, and retain an authorized price-reasonableness analysis. Separately analyze modification pricing and applicable current pricing policy.", "exceptions": "The memo explicitly says the deviation is not applicable to modifications under the pilot. Do not treat this new-award deviation as automatic modification relief or as permission to omit all pricing evidence.", "approval_authority": "Authorized individual-deviation official under current agency procedures; CO determines price reasonableness; DPCAP/CP approves pilot participation.", "locator": "Section 809(e)(1); memo p.1 exemption (1) and individual-deviation paragraph continued on p.2; p.2 deviation-submission bullet", "source_ids": [ "RSRC-0164", "RSRC-0165" ], "limitations": "The reviewed memo cites pre-RFO FAR 1.403/15.403/15.4 and DFARS 201.403/215.403/215.4. Their current application, the statutory versus memo modification treatment, and later pricing reform must be resolved for the action. This rule does not establish a dollar threshold, blanket certified-data waiver or a new negotiation method.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-08-21", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0200" }, { "type": "related requirement", "target": "RULE-0203" }, { "type": "related requirement", "target": "RULE-0161" } ], "date_note": "P.L.118-31 enacted December 22, 2023; signed Revision 1 memo dated August 21, 2025, with no separate effective date stated. No section 809 sunset is stated in the reviewed editions. Current statute after the January 2026 compilation remains a currency check.", "version_state": "August 21, 2025 Revision 1 memo plus enacted section 809; January 2026 compilation corroboration, later statutory currency not conclusively established" }, { "id": "RULE-0203", "title": "Limit XaaS modification competition relief to qualifying pilot changes", "citation": "P.L.118-31 section 809(e)(2); DPCAP Revision 1 memo p.1 exemption (2)", "issuer": "U.S. Congress / DoD DPCAP", "instrument_type": "Policy memorandum", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "For a contract or agreement entered into under the pilot, the reviewed statute exempts a modification adding new features or capabilities from full-and-open competition when its amount is no more than 25 percent of the total value of that contract or agreement.", "applies_when": "Proposing a new-feature or capability modification to an existing, qualifying XaaS pilot agreement.", "required_action": "Confirm the agreement was entered into under the pilot; identify the added feature/capability and document the proposed amount and the supported total-value calculation. Resolve valuation and aggregation questions with policy/counsel before relying on the exemption; satisfy remaining modification, funds, pricing and approval requirements.", "exceptions": "This is a limited competition exemption, not general authority to convert any existing sensor or C2 contract into a pilot agreement. A larger or different change needs another lawful route. Other contract requirements are not waived by this provision.", "approval_authority": "CO and applicable reviewing/approving officials under the actual instrument and current implementation; no local delegation is inferred.", "locator": "Section 809(e)(2), 137 Stat.320; memo p.1 exemption (2)", "source_ids": [ "RSRC-0164", "RSRC-0165" ], "limitations": "The reviewed text says total value, without defining an original-award baseline or cumulative-modification calculation. No repeatable 25-percent allowance is inferred. Proposed later legislative language is not incorporated. Modification pricing relief is a separate issue under RULE-0202 and GAP-021.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-08-21", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0200" }, { "type": "related requirement", "target": "RULE-0202" } ], "date_note": "P.L.118-31 enacted December 22, 2023; signed Revision 1 memo dated August 21, 2025, with no separate effective date stated. No section 809 sunset is stated in the reviewed editions. Current statute after the January 2026 compilation remains a currency check.", "version_state": "August 21, 2025 Revision 1 memo plus enacted section 809; January 2026 compilation corroboration, later statutory currency not conclusively established" }, { "id": "RULE-0204", "title": "Check DoD software inventory before selecting an enterprise agreement", "citation": "2026-O0049 DFARS 208.7400-.7403; PGI 208.7403(1)-(4)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "Commercial software and related maintenance requirements follow ESI, including applicable service, interagency, schedule and system-upgrade acquisitions. After determining requirements, use available DoD inventory first. If an ESA is available, assess its terms, conditions and prices under applicable source-selection requirements and use it when it provides best value.", "applies_when": "Acquiring commercial software or related services for C2, sensor integration or support, including an applicable new order, renewal or upgrade.", "required_action": "Have the requiring official check available DoD inventory, including bulk licenses and DoD-wide maintenance. If neither inventory nor an ESA contains the requirement, other means may be used. Otherwise document the ESA comparison and use the prescribed SPM process before pursuing an alternate source when the ESA is not best value.", "exceptions": "System/system-upgrade coverage is qualified by where practicable. ESI does not dictate which product or service to acquire. The XaaS attachment expressly retains ESI procedures for commercial software; pilot participation is not an ESI waiver.", "approval_authority": "Requiring official checks inventory; CO or requiring official evaluates the ESA under otherwise applicable selection requirements.", "locator": "PDF pp.11-12: DFARS 208.7400-.7403; pp.32-33: PGI 208.7401/.7403(1)-(4); XaaS Attachment 1 p.1", "source_ids": [ "RSRC-0166", "RSRC-0167" ], "limitations": "No actual ESI inventory, agreement terms or product availability is established here. An inaccessible website does not prove no inventory/ESA exists. An existing contract requires action-specific scope/terms analysis; this policy does not cancel an existing obligation or itself authorize a renewal. Supply-chain and licensing requirements remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-03-06", "effective_date": "2026-03-16", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0013" }, { "type": "related requirement", "target": "RULE-0147" }, { "type": "related requirement", "target": "RULE-0200" }, { "type": "related requirement", "target": "RULE-0205" } ], "date_note": "March 6, 2026 deviation effective March 16, 2026, until rescinded or incorporated.", "version_state": "2026-O0049 adopted DFARS/PGI text, selected provisions reviewed 2026-10-03" }, { "id": "RULE-0205", "title": "Give the ESI software product manager the prescribed opportunity", "citation": "2026-O0049 PGI 208.7403(5)(i)-(iii)", "issuer": "DoD DPCAP", "instrument_type": "Class deviation", "topic": "Software and services", "equipment": [ "C2", "Software", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisitions within the cited program or commercial software coverage, including overseas requirements", "summary": "If an ESA does not provide best value, the CO or requiring official must give the software product manager an opportunity to provide the same or a better value before using another source. Within three working days the SPM must update the ESA, provide an estimated update date, or state that no change will be made.", "applies_when": "An available ESA does not provide best value for a defined software or related-services requirement.", "required_action": "Notify the SPM of specific concerns through ESI and retain the response and timing. The SPM considers adjustments within ESA scope. Other means may be used if the SPM will not change the agreement, fails to respond within three working days, or does not plan to adjust it within 90 days. Follow the separate designated-official waiver route when applicable.", "exceptions": "A department/agency-designated management official may waive ESA use after the specified notice and response steps in (5)(i) and (5)(ii)(A). Include alternate-source rationale in the request and provide it to the SPM. Do not invent a mandatory 90-day wait when another express trigger has occurred.", "approval_authority": "SPM manages the ESA; department/agency-designated management official grants the cited waiver. The user's command chain does not establish that designation.", "locator": "PDF p.33, PGI 208.7403(5)(i), (ii)(A)-(C), (iii)", "source_ids": [ "RSRC-0166" ], "limitations": "A lower price alone does not substitute for the required best-value comparison. Unavailable ESI web access is not an SPM nonresponse to a documented requirement. The current DAF management-official designation and individual agreement terms remain unverified in GAP-021.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-03-06", "effective_date": "2026-03-16", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0204" }, { "type": "related requirement", "target": "RULE-0147" } ], "date_note": "March 6, 2026 deviation effective March 16, 2026, until rescinded or incorporated.", "version_state": "2026-O0049 adopted DFARS/PGI text, selected provisions reviewed 2026-10-03" }, { "id": "RULE-0206", "title": "Determine the engineering-plan requirement and approval gate", "citation": "DoDI 5000.88 paragraphs 1.2(b), 3.4(a)(1)-(2)", "issuer": "USD(R&E)", "instrument_type": "DoD instruction", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "A Systems Engineering Plan is required for MDAP and ACAT II/III programs unless waived by the applicable authority. The plan must be approved before release of the RFP for major program phases and included in that RFP.", "applies_when": "An ABAD system acquisition is part of a covered program or is preparing a major program-phase solicitation.", "required_action": "Establish program category, pathway and the proper SEP approval authority before setting the solicitation schedule. Have the lead systems engineer under the PM prepare the plan using the prescribed outline and obtain approval or an authorized waiver. Address substantive postaward changes with the approving authority.", "exceptions": "MDAP waivers are by SEP approval authority; ACAT II/III waivers are by the DoD Component. Content may be tailored with approval. Other programs are recommended to develop an SEP as a best practice; a standalone equipment purchase is not automatically an MDAP.", "approval_authority": "ACAT ID: USD(R&E) or designee. ACAT IB/IC: MDA or designee. Component Acquisition Executive designates approval authorities for other acquisition programs. No local designation is inferred.", "locator": "Paragraph 1.2(b), p.4; 3.4(a)(1), pp.11-12; 3.4(a)(2)(a)-(b), p.12", "source_ids": [ "RSRC-0169" ], "limitations": "Paragraph 3.4(a)(2)(b) uses ambiguous postaward wording: at least 120 days after award or 30 days before the next technical review, whichever comes first. Do not convert it into a within-120-day deadline; resolve with policy/SEP authority under GAP-022. No current pathway exception or DAF waiver delegation is established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-11-18", "effective_date": "2020-11-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0012" }, { "type": "related requirement", "target": "RULE-0101" } ], "date_note": "November 18, 2020 instruction, effective the same day. Apply current amendments, pathway implementation and authorized waivers to the specific action.", "version_state": "November 18, 2020 edition, selected provisions; current implementation and edition limits remain applicable" }, { "id": "RULE-0207", "title": "Plan engineering deliverables, interfaces and technical review criteria", "citation": "DoDI 5000.88 paragraph 3.4(a)(3)(b),(h),(j)-(m),(r)-(s)", "issuer": "USD(R&E)", "instrument_type": "DoD instruction", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "For covered programs, the SEP documents technical baselines and traceability, required digital technical data and formats, contract deliverables and reporting periods, technical-review timing and entry/exit criteria, and an IP/data-rights plan. It also addresses interface dependencies and MOSA considerations.", "applies_when": "Planning an integrated sensor, effector or C2 program, solicitation, order or substantive engineering change.", "required_action": "Translate approved engineering needs into defined deliverables, interfaces, formats, reporting intervals and measurable review criteria in the acquisition package. Reconcile delivery requirements with the actual license/data-rights strategy, contract scope and authorized contractual terms.", "exceptions": "The cited SEP-content requirements address MDAP and ACAT II/III programs unless waived by the SEP approval authority. Digital modeling and data access do not establish an unlimited government license or automatically add contractor obligations.", "approval_authority": "Lead systems engineer under the PM prepares the SEP; applicable SEP approval authority approves or waives covered content. CO uses lawful contract terms to establish contractor obligations.", "locator": "Paragraph 3.4(a)(3), printed/PDF pp.12-14: subparagraphs (b),(h),(j)-(m),(r)-(s)", "source_ids": [ "RSRC-0169" ], "limitations": "Engineering policy and an approved plan alone do not amend an existing contract. Data delivery and license rights require separate analysis. The 2024 MOSA direction adds relevant policy context; current statute and Service implementation remain GAP-022 questions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-11-18", "effective_date": "2020-11-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0206" }, { "type": "related requirement", "target": "RULE-0208" }, { "type": "related requirement", "target": "RULE-0210" }, { "type": "related requirement", "target": "RULE-0211" } ], "date_note": "November 18, 2020 instruction, effective the same day. Apply current amendments, pathway implementation and authorized waivers to the specific action.", "version_state": "November 18, 2020 edition, selected provisions; current implementation and edition limits remain applicable" }, { "id": "RULE-0208", "title": "Preserve technical baselines and engineering-change traceability", "citation": "DoDI 5000.88 paragraphs 3.4(b)-(c)", "issuer": "USD(R&E)", "instrument_type": "DoD instruction", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "The PM describes baseline management in the SEP, and the engineering team maintains the functional, allocated and product baselines through technical reviews. Configuration management records controlled changes and preserves an audit trail and requirements traceability throughout the system life cycle.", "applies_when": "Integrating, upgrading or sustaining an ABAD system under a covered acquisition program, including proposed hardware, firmware, software or interface changes.", "required_action": "Identify the approved baseline and change-control responsibilities; record effects on schedule, cost, function, physical characteristics and performance, including changes within or outside formal engineering change proposals. Coordinate technical approval with separate CO scope, pricing, funding and modification decisions.", "exceptions": "The instruction places initial product-baseline Class I change control with the PM at completion of system-level CDR; Class I is defined by the program configuration-management plan. A digital authoritative source of truth is qualified by if practicable.", "approval_authority": "PM and lead systems engineer have the cited engineering responsibilities. Technical change approval does not confer contracting-officer authority or authorize funds.", "locator": "Paragraph 3.4(b), p.14; 3.4(c), pp.14-15", "source_ids": [ "RSRC-0169" ], "limitations": "No blanket permission to direct a contractor, expand an order or issue a unilateral modification follows from engineering change control. Apply the existing instrument, governing change clause, contract-scope rules and delegated CO authority independently.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-11-18", "effective_date": "2020-11-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0188" }, { "type": "related requirement", "target": "RULE-0212" } ], "date_note": "November 18, 2020 instruction, effective the same day. Apply current amendments, pathway implementation and authorized waivers to the specific action.", "version_state": "November 18, 2020 edition, selected provisions; current implementation and edition limits remain applicable" }, { "id": "RULE-0209", "title": "Maintain an integrated engineering plan and schedule", "citation": "DoDI 5000.88 paragraph 3.4(d)", "issuer": "USD(R&E)", "instrument_type": "DoD instruction", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "The PM ensures an Integrated Master Plan and Integrated Master Schedule are developed and maintained through the program life cycle. They address activities, reviews, dependencies and contracted technical tasks; a government program office acting as systems integrator has the system-level plan and schedule responsibility.", "applies_when": "Managing integration among radar, cameras, C2 and other system elements under a covered acquisition program.", "required_action": "Assign plan/schedule responsibility, account for interprogram dependencies and technical tasks, and keep the schedule current for technical reviews, risk assessments, milestones and significant unplanned changes. Align any contractor deliverables with the actual contract.", "exceptions": "Where the government program office is the systems integrator, the PM develops and maintains the system-level IMP/IMS. Other programs may contract for that task, with government responsibility governed by the instruction.", "approval_authority": "Program manager; engineering team and contracted support within assigned and contractual responsibilities.", "locator": "Paragraph 3.4(d)(1)-(2), printed/PDF p.15", "source_ids": [ "RSRC-0169" ], "limitations": "This does not establish an EVM/EVMS contract-clause threshold, mandate a particular commercial scheduling tool, or authorize a lead-system-integrator arrangement. Referenced EVM/DCMA guides were not independently reviewed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2020-11-18", "effective_date": "2020-11-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0044" }, { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0208" } ], "date_note": "November 18, 2020 instruction, effective the same day. Apply current amendments, pathway implementation and authorized waivers to the specific action.", "version_state": "November 18, 2020 edition, selected provisions; current implementation and edition limits remain applicable" }, { "id": "RULE-0210", "title": "Plan and verify the five MOSA pillars", "citation": "Tri-Service MOSA memorandum, December 17, 2024, pp.1-2", "issuer": "Secretaries of the Navy, Army and Air Force", "instrument_type": "Policy memorandum", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "The Service Secretaries direct MOSA implementation and commitment to five pillars: modular design, designated modular interfaces, consensus open standards, an enabling environment and conformance certification. MOSA guidance must address an appropriate verification method and timing during program development.", "applies_when": "Planning or changing a DoD weapon-system acquisition with modular interfaces and integration, including applicable ABAD programs.", "required_action": "Identify the program-specific approach to each pillar and the evidence, method and timing for verifying it. Bring that approach into engineering and acquisition planning, including needed interface data and rights. Obtain current Service implementation and the actual responsible approval/review authorities.", "exceptions": "The memo lists standards as examples, not a requirement to apply all of them to every purchase. The SAE must ensure MOSA is implemented to the extent practical and must review MOSA compliance with MDAPs at systems-engineering technical, gate and program reviews.", "approval_authority": "Service Acquisition Executives and program acquisition officials within the memorandum. No specific conformance certifier, local waiver authority or contracting delegation is established here.", "locator": "PDF p.1 implementation/standards paragraphs; p.2 five pillars, verification, SAE review and 60-/120-day implementation tasks", "source_ids": [ "RSRC-0170" ], "limitations": "The memo’s 60-/120-day tasks concern historical SAE reporting and issuance of Service guidance; they are not newly running CO deadlines or evidence that guidance was issued. The referenced January 2019 memo and current 10 USC 4401-4403 were not independently reviewed. MOSA does not automatically provide data rights or interoperability certification.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2024-12-17", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0208" } ], "date_note": "Signed December 17, 2024; no separate effective date stated. Historical SAE tasks are not new contracting-office deadlines.", "version_state": "Signed December 17, 2024 memorandum reviewed in full; subsequent Service implementation unresolved" }, { "id": "RULE-0211", "title": "Use engineering expertise to shape contract requirements and incentives", "citation": "Systems Engineering Guidebook, September 2026, preface and section 4.6", "issuer": "Office of the Under Secretary for Research and Engineering", "instrument_type": "Guidance", "topic": "Systems engineering and interoperability", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD acquisition programs within the cited instruction or policy scope; overseas location does not establish an exception", "summary": "The guide recommends systems-engineer participation in statements of work/objectives, performance work statements, deliverables and acquisition planning so technical activities, resources, milestones and integration needs are clear. Technical-review incentives warrant objective engineering judgment to avoid premature closure.", "applies_when": "Developing an ABAD solicitation or change package and considering engineering deliverables, technical review criteria or performance incentives.", "required_action": "As a planning practice, have the engineering team review technical tasks, CDRLs, data-rights needs, milestones and objective completion criteria with the CO and PM. Tailor the recommendations to the program and establish obligations through authorized contract terms.", "exceptions": "The preface expressly presents a flexible reference guide, not a mandatory checklist. Section 4.6 recommendations do not independently prescribe clauses or contractor duties.", "approval_authority": "PM, lead systems engineer and contracting team under existing roles and delegations; the guide grants no new authority.", "locator": "Preface printed p.viii/PDF p.8; section 4.6 Systems Engineering Role in Contracting, printed p.49/PDF p.59", "source_ids": [ "RSRC-0171" ], "limitations": "The recommendation to enable delegated subcontract authority does not itself waive consent requirements or grant a delegation. The guide cannot override binding law, regulation, instruction or existing contract terms. Only selected portions of the September 2026 edition were reviewed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0208" }, { "type": "related requirement", "target": "RULE-0210" } ], "date_note": "September 2026 guidebook; exact day and a separate effective date are not stated. Recommendations are guidance.", "version_state": "September 2026 guidebook, selected front matter and sections 1.5/4.6 reviewed" }, { "id": "RULE-0212", "title": "Assess cyber testing needs when a fielded system changes", "citation": "DoWM 5000.103 paragraphs 3.1(a), 3.2(a)(13)-(14)", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "Cyber developmental testing applies across acquisition pathways and to sustainment or postproduction systems when the listed changes occur. Those changes include recurring software releases, architecture or baseline upgrades, new components, technology replacement, evolving threats and changes to interfacing systems or supply chains.", "applies_when": "Planning an ABAD acquisition, integration increment, software release, hardware replacement or sustainment change covered by the manual.", "required_action": "Have the program and cyber test team assess the change and define applicable test and remediation evidence, resources and schedule. Coordinate any new contractor work through the CO and the governing instrument; connect the cyber review to technical-baseline and contract-scope decisions.", "exceptions": "The sustainment/postproduction application is tied to the changes in 3.2(a)(13). No fixed recurring interval or automatic every-option test requirement is established by these selected provisions. Required scope remains system- and change-specific.", "approval_authority": "Program manager/project lead or equivalent and responsible cyber T&E officials; Component implementation determines applicable approvals.", "locator": "Paragraph 3.1(a)(1)-(4), p.8; 3.2(a)(13)-(14), p.11", "source_ids": [ "RSRC-0129" ], "limitations": "This is a departmental lifecycle requirement, not a unilateral addition to an existing contract. CMMC, contract safeguarding, system RMF and source prohibitions retain their distinct requirements. No actual system test scope, operational authority or local exception is determined.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0065" }, { "type": "related requirement", "target": "RULE-0208" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0097" }, { "type": "related requirement", "target": "RULE-0213" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0213", "title": "Put cyber test access, support and data requirements in the acquisition package", "citation": "DoWM 5000.103 paragraphs 3.5(a)(2),(6),(8)-(10), 3.5(b)(10), 4.2(b)", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "The program lead identifies a cybersecurity lead and charters a cyber working group at initiation of S&T research, pre-acquisition projects or acquisition programs, or before any contractual commitment or release of the first RFP. The group works with the CO to specify cyber DT&E requirements through CDRLs, data item descriptions and terms aligned with the FAR, DFARS or other applicable agreements.", "applies_when": "Preparing a covered solicitation, contract, other transaction or a proposed change requiring cyber testing support and deliverables.", "required_action": "Define contractor test obligations, qualified personnel, government observation and facility/test-environment access, support, remediation responsibilities and data delivery. Include applicable supply-chain data, design information, traceability, test plans/reports and corrective-action evidence; plan government resources and schedules alongside contractor work.", "exceptions": "Software reverse-engineering data rights or source-code delivery are expressly if applicable. Rights and access must be established through the actual instrument; the manual does not itself grant unlimited rights or authorize entry into supplier facilities.", "approval_authority": "Program lead charters the CyWG and ensures requirements/resources; CyWG works with the contracting officer. Other-transaction coverage does not establish authority to use an OT.", "locator": "Paragraph 3.5(a)(2), p.15; 3.5(a)(6),(8)-(10), p.16; 3.5(b)(10), p.17; 4.2(b)(1)(a)-(l), (2)(a)-(i), pp.25-26", "source_ids": [ "RSRC-0129" ], "limitations": "The paragraph is not a ready-made contract clause and does not waive scope, funding, competition, privacy or license requirements. Existing orders/modifications need independent terms and authority analysis. Tables 3 and 4 are referenced for plan/report alignment but their complete field requirements are not reproduced here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0212" }, { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0207" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0217" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0214", "title": "Use government cyber acceptance evidence in the product-acceptance decision", "citation": "DoWM 5000.103 paragraphs 3.2(b), 3.5(a)(7)", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "Government acceptance cyber T&E validates specified cyber performance and in-scope technical security controls for a delivered system or intermediate release before proceeding into government DT&E. It includes the appropriate contractor/government participants and supply-chain risk office and informs the decision to accept the product.", "applies_when": "Planning receipt and acceptance of a covered system, minimum viable capability, later software release, increment or other intermediate deliverable.", "required_action": "Align specified requirements, required test evidence, participating offices and remediation responsibilities with the acceptance terms. Have the program lead decide actions on cyber acceptance recommendations and coordinate contract remedies or acceptance decisions with the authorized contracting/acceptance officials.", "exceptions": "The manual says the testing may include government DT&E and OT&E and permits a digital twin, integration lab, hardware-in-the-loop facility or other test asset. It does not require purchasing every listed type of test asset.", "approval_authority": "Program lead decides actions on cyber acceptance recommendations; authorized contract officials retain their separate acceptance and remedy responsibilities.", "locator": "Paragraph 3.2(b)(1)-(5), p.12; 3.5(a)(7), p.16; contractor-remediation terms at 4.2(b)(1)(k), p.26", "source_ids": [ "RSRC-0129" ], "limitations": "Cyber acceptance testing informs a decision; it is not itself contractual acceptance, payment approval or an ATO. Rejection, correction, retest and payment consequences must be supported by the actual contract and applicable law. No blanket postacceptance warranty or new remedy is created.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0193" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0213" }, { "type": "related requirement", "target": "RULE-0215" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0215", "title": "Keep cyber developmental testing and RMF authorization coordinated", "citation": "DoWM 5000.103 paragraphs 2.7(f), 3.3(a)-(f)", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "RMF does not replace or supersede the manual’s cyber DT&E procedures. Testing data and RMF artifacts complement each other; Component heads require cyber DT&E before RMF authorization decisions, and program leads provide current cyber test results to the authorizing official for every ATO decision.", "applies_when": "Planning system testing, connection, authorization or a later authorization decision for an ABAD system.", "required_action": "Coordinate the cyber test plan and RMF assessment path and deliver all current results to the authorizing official. Complete the applicable assessment procedures for Assess Only, IATT, authorization to connect, ATO with conditions or ATO, as required to connect and operate before the final operational test readiness review under 3.3(e). Record the environment and basis for any narrowly applicable test-environment provision.", "exceptions": "Paragraph 3.3(d) says cyber DT&E on closed loop test ranges does not require IATT, ATO, another cybersecurity certification attestation, or a certified/accredited department cyber red team, in accordance with DoDI 8585.01. This scoped provision does not establish a general exemption for connected or fielded systems.", "approval_authority": "Component heads, program lead and the system authorizing official under their actual responsibilities; the closed-loop provision does not create a CO authorization delegation.", "locator": "Paragraph 2.7(f), p.7; 3.3(a)-(f), p.14; 3.5(a)(14)-(15), p.16", "source_ids": [ "RSRC-0129" ], "limitations": "Full DoDI 8510.01 and 8585.01 implementation is not established here. Determine actual boundary/environment eligibility and applicable authorities; contractor CMMC status, contract award or a successful test does not alone establish a system ATO.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0064" }, { "type": "related requirement", "target": "RULE-0097" }, { "type": "related requirement", "target": "RULE-0214" }, { "type": "related requirement", "target": "RULE-0217" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0216", "title": "Include cyber test requirements in commercial IT services planning and performance", "citation": "DoWM 5000.103 section 5.7(a) and Table 10", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "For commercial information-technology services within the acquisition-of-services pathway, the program conducts cyber DT&E to inform project decisions and assess mission risks. Table 10 assigns activities across Plan, Develop and Execute, including contract requirements, testing, reporting and sustainment updates.", "applies_when": "Acquiring or administering applicable commercial IT services supporting C2, hosted sensor processing or system integration.", "required_action": "Establish the CyWG in Plan; include cyber DT&E requirements in each RFP and contract in Develop and update them in Execute. Plan resources, infrastructure and sustainment testing and retain reporting/access to authorized users across the three stages. Use the table’s actual required, recommended/program-specific and required-update symbols.", "exceptions": "Table 10 marks an MBCRA in Develop as required but its Execute-stage entry as recommended or program-specific. Do not turn every listed activity into an identical mandatory task at every stage. The cited paragraph concerns commercial IT services, not all service purchases.", "approval_authority": "Program lead and CyWG, with the CO for contract terms; Component officials establish applicable plan approvals and reporting destinations.", "locator": "Section 5.7(a), p.50; Table 10 and its legend/three stage columns, p.51", "source_ids": [ "RSRC-0129" ], "limitations": "Existing service agreements require terms/scope/funding analysis before new contractor duties are added. Section 5.7(b) references Figure 9 while the services example is captioned Figure 10; this rule relies on section 5.7(a) and Table 10 and does not resolve that source cross-reference.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0033" }, { "type": "related requirement", "target": "RULE-0213" }, { "type": "related requirement", "target": "RULE-0217" }, { "type": "related requirement", "target": "RULE-0200" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0217", "title": "Track cyber deficiencies and preserve test evidence for authorized decisions", "citation": "DoWM 5000.103 paragraphs 3.5(a)(15)-(19), 4.6(a)-(e)", "issuer": "Under Secretary of War for Research and Engineering", "instrument_type": "Department manual", "topic": "Cybersecurity", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Software", "Integration", "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Department systems and applicable acquisition pathways, including overseas requirements", "summary": "Program leads provide cyber test results to decision authorities and authorizing officials, track deficiencies in the designated department/component system, and preserve documentation and contractor-delivered data for authorized users. Responsible test teams report results, mark/handle them appropriately and store copies under records-management requirements.", "applies_when": "Managing cyber test deliverables, corrective-action evidence, acceptance decisions, sustainment transition or contract closeout for a covered system.", "required_action": "Specify deliverables and recipients in the instrument, track deficiencies and remediation evidence, and ensure authorized officials can obtain the current reports. At transition or closeout, reconcile contract data delivery with the government’s custody and applicable records-management requirements.", "exceptions": "Findings not adjudicated as deficiencies are also tracked in eMASS or equivalent systems for RMF support. Report handling must comply with applicable classification guidance. Availability to authorized users is not public release.", "approval_authority": "Program lead and responsible cyber DT&E teams; Component heads specify when and to whom plans and reports are delivered under 2.7(e)(3).", "locator": "Paragraph 2.7(e)(3), p.7; 3.5(a)(15)-(18), p.16 and (19), p.17; 4.6(a)-(e), p.31", "source_ids": [ "RSRC-0129" ], "limitations": "No fixed retention period, contractor report deadline, data license or automatic closeout condition is inferred. Current records-management implementation and contract-specific delivery schedules must be established separately; the manual’s cited records instruction is not independently revalidated here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-25", "effective_date": "2026-02-25", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0213" }, { "type": "related requirement", "target": "RULE-0214" }, { "type": "related requirement", "target": "RULE-0215" }, { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0148" } ], "date_note": "Manual approved February 19, 2026; issuance dated and effective February 25, 2026. No sunset is stated.", "version_state": "February 25, 2026 manual, selected provisions; apply current Component implementation and action-specific conditions" }, { "id": "RULE-0218", "title": "Identify the frequency-authorization clause variant and resolve its prescription", "citation": "2026-O0014: DFARS 235.176(c)(1)-(2); 252.235-7003 Basic/Alternate I", "issuer": "DPCAP", "instrument_type": "Class deviation / contract clause", "topic": "Spectrum", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD contracting, including applicable overseas performance", "summary": "Adopted paragraph 235.176(c) specifies the frequency-authorization clause for solicitations and contracts to develop, produce, construct, test or operate a device requiring frequency authorization. It selects Basic when agency procedures do not authorize DD Form 1494, and Alternate I when they do. The section’s indemnification introduction creates a drafting issue requiring clarification.", "applies_when": "Selecting terms for work involving a device requiring frequency authorization, including an order or proposed modification; existing terms and the unresolved section introduction must be assessed.", "required_action": "Identify the actual device/activity, governing clause edition and current agency procedure for DD Form 1494. Resolve the introductory indemnification wording with policy/counsel before relying on this paragraph for a disputed inclusion or omission. For an existing instrument, review its clauses and scope before adding duties.", "exceptions": "The adopted paragraph lists production, construction, testing and operation as well as development. Neither an R&D-only limitation nor an indemnification-based spectrum exemption is established here. The Basic/Alternate choice depends on agency procedures, not contractor preference.", "approval_authority": "CO selects the applicable contract terms under current policy; spectrum officials administer frequency permissions. No 764th ESS, AFICC or theater-specific delegation is established.", "locator": "Memo PDF pp.1-2; Attachment A1 235.176 introduction and (c)(1)-(2), printed p.3/PDF p.5; clause headings and paragraph(c), printed pp.10-11/PDF pp.12-13", "source_ids": [ "RSRC-0174" ], "limitations": "235.176 opens with an indemnification condition while (c) contains the separate frequency prescription. GAP-024 preserves this conflict; no silent correction or blanket clause-insertion conclusion is made. The codified page still uses 235.072(b), whereas the adopted attachment and clause use 235.176(c). Current agency/host-nation procedures remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0063" }, { "type": "related requirement", "target": "RULE-0102" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0219" }, { "type": "related requirement", "target": "RULE-0220" } ], "date_note": "Deviation signed December 18, 2025; effective February 1, 2026 until rescinded or incorporated. Basic and Alternate I clause texts retain MAR2014 dates.", "version_state": "2026-O0014 adopted Part235; selected frequency provisions and unresolved introductory drafting issue" }, { "id": "RULE-0219", "title": "Track contractor frequency authorization and early technical-characteristic delivery", "citation": "2026-O0014: DFARS 252.235-7003 Basic/Alternate I (a)-(c)", "issuer": "DPCAP", "instrument_type": "Class deviation / contract clause", "topic": "Spectrum", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD contracting, including applicable overseas performance", "summary": "Both variants require the contractor to obtain radio-frequency authorizations needed to support the contract. If appropriate allocation has not been made for experimental, developmental or operational equipment, the contractor provides the proposed radiating device’s technical operating characteristics to the CO during the initial planning, experimental or developmental phase of performance.", "applies_when": "Administering a contract containing the applicable frequency-authorization clause, including qualifying development, production, integration, testing or operation work.", "required_action": "Track the required authorization and timely delivery of technical operating characteristics when allocation is missing. Under Basic, the CO furnishes the authorization procedures; under Alternate I, the contractor uses DD Form 1494. Coordinate the current submission route and responsible spectrum office, and document any change under the governing instrument.", "exceptions": "Paragraph(b) is conditional on missing appropriate frequency allocation. Its timing refers to early phases of contract performance; it does not establish a universal preaward submission deadline. Submission of an application or data is not itself authorization.", "approval_authority": "Contractor obtains required authorization; CO receives characteristics and furnishes procedures under Basic. The clause does not make the CO the spectrum approving authority.", "locator": "Attachment A1 252.235-7003 Basic (a)-(c), printed p.10/PDF p.12; Alternate I(a)-(c), printed p.11/PDF p.13", "source_ids": [ "RSRC-0174" ], "limitations": "A purchase, contract acceptance, option or modification does not itself grant permission to transmit. Full equipment-certification, host-nation and E3 requirements remain unresolved; distinguish frequency authorization from a cyber authority to operate. No new withholding, suspension or acceptance remedy is inferred from these paragraphs.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0218" }, { "type": "related requirement", "target": "RULE-0121" }, { "type": "related requirement", "target": "RULE-0122" }, { "type": "related requirement", "target": "RULE-0215" }, { "type": "related requirement", "target": "RULE-0220" } ], "date_note": "Deviation signed December 18, 2025; effective February 1, 2026 until rescinded or incorporated. Basic and Alternate I clause texts retain MAR2014 dates.", "version_state": "2026-O0014 adopted Part235; selected frequency provisions and unresolved introductory drafting issue" }, { "id": "RULE-0220", "title": "Preserve the frequency-authorization clause in qualifying subcontracts", "citation": "2026-O0014: DFARS 252.235-7003 Basic/Alternate I (d)", "issuer": "DPCAP", "instrument_type": "Class deviation / contract clause", "topic": "Spectrum", "equipment": [ "Radar", "Camera", "Drone", "Counter-UAS", "Effector", "C2", "Integration" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "DoD contracting, including applicable overseas performance", "summary": "Both variants require the contractor to include the clause, including paragraph(d), in all subcontracts requiring development, production, construction, testing or operation of a device for which radio-frequency authorization is required.", "applies_when": "A prime contract contains the frequency-authorization clause and subcontract work meets paragraph(d)’s device/activity condition, including affected work added during performance.", "required_action": "Address the full clause flow-down in subcontract planning and verify compliance through the prime and the actual contract-administration arrangements. Reassess the condition when changed subcontract work adds a qualifying device or activity.", "exceptions": "The express condition concerns the subcontracted work and the need for authorization. Paragraph(d) provides no blanket exception for a lower tier or a commercial label; determine the applicable instrument and facts without inventing a separate universal consent requirement.", "approval_authority": "Prime/subcontractors carry their clause obligations; CO and authorized administrators act within the prime contract and their delegations.", "locator": "Attachment A1 252.235-7003 Basic (d), printed p.10/PDF p.12; Alternate I(d), printed p.11/PDF p.13", "source_ids": [ "RSRC-0174" ], "limitations": "The flow-down does not authorize government direction of a subcontractor, grant frequencies, create direct contractual privity or supply a new payment/closeout condition. Existing contract changes still require their own authority, scope and funding analysis.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0218" }, { "type": "related requirement", "target": "RULE-0219" }, { "type": "related requirement", "target": "RULE-0037" }, { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0036" } ], "date_note": "Deviation signed December 18, 2025; effective February 1, 2026 until rescinded or incorporated. Basic and Alternate I clause texts retain MAR2014 dates.", "version_state": "2026-O0014 adopted Part235; selected frequency provisions and unresolved introductory drafting issue" }, { "id": "RULE-0221", "title": "Identify covered systems of records and specify the privacy work", "citation": "2026-O0009; RFO FAR 24.101-.104; DFARS 224.103(b)(2)", "issuer": "FAR Council / DPCAP", "instrument_type": "Adopted regulation / contract clause", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. agency contracting, including DoD overseas performance; host-nation law assessed separately", "summary": "The CO reviews whether the requirement includes design, development or operation of a system of records on individuals for an agency function. For covered work, identify both the specific system and required work in the contract work statement, provide agency implementing rules, and include 52.224-1 and 52.224-2 in the solicitation and contract.", "applies_when": "Planning an acquisition or reviewing an order/change that may add covered system-of-records work. A system of records requires agency-controlled records retrieved by a person’s name or assigned identifying particular; the mere purchase of a camera does not decide that question.", "required_action": "Map the intended data, retrieval method, agency function and contractor role with privacy officials. Identify the covered system and work; provide applicable DoD privacy implementing rules identified in 224.103(b)(2). For an existing vehicle or proposed change, assess the governing terms and modification authority before adding obligations.", "exceptions": "RFO 24.101 defines individual as a U.S. citizen or lawful permanent resident and separately defines PII. The narrower system-of-records coverage test is not a blanket exemption from PII training, other privacy rules or host-nation law. Full Privacy Act exceptions and current implementing texts require separate review.", "approval_authority": "The CO reviews requirements and selects contract terms; responsible privacy officials establish the applicable privacy framework. No local privacy approval delegation is established.", "locator": "RFO 24.101 definitions, 24.102(a)-(d), 24.103(a)-(b), 24.104; deviation memo PDF pp.1-2 and Attachment A1 224.103(b)(2), PDF p.3; 52.224-1 complete clause; 52.224-2(a)(1),(c)", "source_ids": [ "RSRC-0176", "RSRC-0177", "RSRC-0178", "RSRC-0180" ], "limitations": "The definitions include photographs, fingerprints and voiceprints, but do not make every image archive a system of records. This rule neither approves collection/use nor establishes a SORN or PIA. Current instruction, notice, retention and overseas implementation questions remain in GAP-025.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0080" }, { "type": "related requirement", "target": "RULE-0098" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0222" }, { "type": "related requirement", "target": "RULE-0223" } ], "date_note": "Dates identify DoD adoption by 2026-O0009, which remains until rescinded or incorporated. Clauses 52.224-1/-2 retain APR 1984 dates; 52.224-3 and Alternate I retain JAN 2017 dates. Page update/FAC dates are not substituted for those clause dates.", "version_state": "DoD-adopted RFO Part 24 with current displayed FAR 52.224 clauses; actual instrument terms control existing-contract duties" }, { "id": "RULE-0222", "title": "Preserve Privacy Act notification and clause duties in qualifying subcontracts", "citation": "FAR 52.224-2(a)(1)-(3), (b)-(c); 52.224-1", "issuer": "FAR Council / DPCAP", "instrument_type": "Adopted regulation / contract clause", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. agency contracting, including DoD overseas performance; host-nation law assessed separately", "summary": "When the contract identifies the covered system and work, 52.224-2 requires compliance with the Act and agency rules. It separately requires the Privacy Act notification in qualifying subcontract solicitations, resulting subcontracts and subcontracts without solicitation, and the full Privacy Act clause in qualifying subcontracts.", "applies_when": "An applicable prime contract contains 52.224-2 and subcontract work falls within its system-of-records condition, including affected work added during performance.", "required_action": "Address both the notification and clause flow-downs through the prime. Preserve (a)(2)’s wording for redesign, development or operation of a system subject to the Act and (a)(3)’s design, development or operation condition. Reassess changed analytics, hosting or support work against the actual terms.", "exceptions": "The two flow-down paragraphs use different wording; do not silently make them identical or apply them to every purchase solely because it includes a sensor. Operation includes collection, use and dissemination associated with maintaining the system.", "approval_authority": "Contractors carry their applicable clause duties; the CO and authorized administrators act through the governing prime contract and delegations.", "locator": "52.224-2(a)(1)(i)-(ii),(a)(2)-(3),(b),(c)(1)-(3); 52.224-1 complete notification", "source_ids": [ "RSRC-0176", "RSRC-0177", "RSRC-0178", "RSRC-0180" ], "limitations": "This clause does not establish direct government privity with subcontractors or authorize collection, disclosure or changes. Liability language does not make contractor personnel government employees for every purpose. Current Privacy Act implementation and exceptions remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0221" }, { "type": "related requirement", "target": "RULE-0037" }, { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0224" } ], "date_note": "Dates identify DoD adoption by 2026-O0009, which remains until rescinded or incorporated. Clauses 52.224-1/-2 retain APR 1984 dates; 52.224-3 and Alternate I retain JAN 2017 dates. Page update/FAC dates are not substituted for those clause dates.", "version_state": "DoD-adopted RFO Part 24 with current displayed FAR 52.224 clauses; actual instrument terms control existing-contract duties" }, { "id": "RULE-0223", "title": "Apply the separate PII privacy-training trigger and select the training route", "citation": "RFO FAR 24.302; FAR 52.224-3(a)-(c), Alternate I (c)", "issuer": "FAR Council / DPCAP", "instrument_type": "Adopted regulation / contract clause", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. agency contracting, including DoD overseas performance; host-nation law assessed separately", "summary": "RFO 24.302 prescribes 52.224-3 when contractor employees, on the agency’s behalf, access a system of records, handle PII, or design, develop, maintain or operate a system of records. The clause requires initial training and annual training thereafter for covered employees.", "applies_when": "Contractor personnel will perform any listed activity, including handling identifiable camera/C2 information, hosted data, maintenance exports or disposal of PII on the agency’s behalf. A system-of-records finding is not required for the separate PII-handling trigger.", "required_action": "Assess employee roles and actual data flows. Select Alternate I when the agency specifies only agency-provided training is acceptable. Under Basic, verify role-based foundational/advanced training, knowledge testing and all six minimum subjects: Privacy Act provisions/penalties, handling/safeguarding, authorized use, unauthorized equipment restrictions, unauthorized access/use/disclosure prohibitions, and breach procedures; an agency-developed or agency-conducted course satisfies those content elements.", "exceptions": "Alternate I replaces only (c): the agency provides initial and annual training for the contract duration. It does not remove the contractor’s other obligations. PII includes identity information that becomes identifiable in combination with other linked or linkable information.", "approval_authority": "CO selects the prescribed variant under agency requirements; contractor ensures completion, while the contracting agency provides training under Alternate I.", "locator": "RFO 24.302(a)(1)-(3),(b); 52.224-3(a),(b)(1)-(3),(c)(1)(i)-(vi),(c)(2); Alternate I (c)", "source_ids": [ "RSRC-0176", "RSRC-0177", "RSRC-0179" ], "limitations": "Review of these provisions does not establish a particular agency-approved course, automatic training equivalency beyond (c)(2), breach-reporting deadline or a permission to collect data. Buying equipment alone does not establish contractor PII access or satisfy training requirements.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0221" }, { "type": "related requirement", "target": "RULE-0098" }, { "type": "related requirement", "target": "RULE-0159" }, { "type": "related requirement", "target": "RULE-0224" } ], "date_note": "Dates identify DoD adoption by 2026-O0009, which remains until rescinded or incorporated. Clauses 52.224-1/-2 retain APR 1984 dates; 52.224-3 and Alternate I retain JAN 2017 dates. Page update/FAC dates are not substituted for those clause dates.", "version_state": "DoD-adopted RFO Part 24 with current displayed FAR 52.224 clauses; actual instrument terms control existing-contract duties" }, { "id": "RULE-0224", "title": "Verify privacy training before access and throughout subcontract performance", "citation": "FAR 52.224-3(b), (d)-(f), Alternate I", "issuer": "FAR Council / DPCAP", "instrument_type": "Adopted regulation / contract clause", "topic": "Privacy", "equipment": [ "Camera", "C2", "Software", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. agency contracting, including DoD overseas performance; host-nation law assessed separately", "summary": "Under the clause, the contractor must not permit covered access, PII handling or system work before required privacy training is completed. It keeps completion documentation and provides it to the CO on request. The substance of the clause, including (f), flows into subcontracts meeting the listed employee-activity conditions.", "applies_when": "Administering a contract containing52.224-3, including changes in staff, data-handling roles, subcontracts or the work performed during an order or option period.", "required_action": "Coordinate the access gate with the responsible officials; request completion evidence when needed and track initial/annual coverage for affected roles. Check conditional subcontract flow-downs and preserve appropriate administration records under the governing retention rules. Address deficiencies using the actual contract and delegated authority.", "exceptions": "The flow-down is the substance of this clause including (f), conditioned on system access, PII handling or specified system work. Both Basic and Alternate I retain (d)-(f). The clause provides no fixed records-retention period and does not require automatic routine submission of every training record to the CO.", "approval_authority": "Contractor controls its employees’ compliance and supplies records on request; CO and authorized administrators verify within their contract authority. System-access approvals remain with responsible officials.", "locator": "52.224-3(b),(d),(e),(f)(1)-(3); Alternate I substitutes only paragraph (c)", "source_ids": [ "RSRC-0176", "RSRC-0177", "RSRC-0179" ], "limitations": "The clause supplies a training gate, not permission for collection or public release. It does not create a new payment-withholding or closeout condition, a fixed annual calendar date, direct government control of subcontractors, or an exception based on command/funding source.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0223" }, { "type": "related requirement", "target": "RULE-0222" }, { "type": "related requirement", "target": "RULE-0035" }, { "type": "related requirement", "target": "RULE-0037" } ], "date_note": "Dates identify DoD adoption by 2026-O0009, which remains until rescinded or incorporated. Clauses 52.224-1/-2 retain APR 1984 dates; 52.224-3 and Alternate I retain JAN 2017 dates. Page update/FAC dates are not substituted for those clause dates.", "version_state": "DoD-adopted RFO Part 24 with current displayed FAR 52.224 clauses; actual instrument terms control existing-contract duties" }, { "id": "RULE-0225", "title": "Assess first-article need when products, production or specifications change", "citation": "2026-O0042; RFO FAR 9.301-.304", "issuer": "FAR Council / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. defense acquisitions, including overseas performance; contract and agency conditions assessed separately", "summary": "Before requiring first-article testing, consider cost and delivery effects, the risk of foregoing testing and less costly quality methods. Testing may be appropriate for a new government supplier, changed processes or specifications, a long production lapse, prior lifecycle problems, performance specifications or a needed manufacturing standard.", "applies_when": "Planning supplies for a new award, follow-on order or proposed production/specification change. These are considerations for the requirement decision, not automatic testing mandates for every sensor, effector or C2 purchase.", "required_action": "Coordinate the documented requirement decision with technical and quality personnel. Compare the actual product and process baseline, prior government acceptance evidence and alternatives. For existing contracts, establish the applicable terms and modification authority before adding testing work.", "exceptions": "Normally do not require first-article testing for R&D, products requiring preaward qualification, products normally sold commercially, or products covered by complete detailed specifications. The last category has an express novel-or-exacting-requirements qualification. Normally is not an absolute prohibition; these exceptions do not waive other testing, safety or acceptance requirements.", "approval_authority": "CO applies the adopted provisions with responsible technical and quality activities; current Service/command implementation and written delegations remain separate.", "locator": "Signed deviation pp.1-2; RFO 9.301; 9.302(a)-(c); 9.303(a)-(d); 9.304(a)-(d)", "source_ids": [ "RSRC-0181", "RSRC-0182", "RSRC-0183" ], "limitations": "A prior delivery, commercial label, funding source or organizational chain alone establishes neither a waiver nor an exception. AFMCI 23-110 and command approval requirements remain unresolved in GAP-004. Program OT&E, cyber testing and operational authorization are distinct.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0014" }, { "type": "related requirement", "target": "RULE-0188" }, { "type": "related requirement", "target": "RULE-0120" }, { "type": "related requirement", "target": "RULE-0212" }, { "type": "related requirement", "target": "RULE-0226" } ], "date_note": "Dates identify DoD adoption by 2026-O0042. The RFO Basic clause headers display Deviation Date; no separate clause date is invented. Alternate I: January 1997; Alternate II: September 1989. The deviation remains until rescinded or incorporated.", "version_state": "DoD-adopted RFO 9.3 and current referenced RFO first-article clause forms; actual incorporated terms control existing-contract duties" }, { "id": "RULE-0226", "title": "Specify first-article evidence and preserve the conditional waiver route", "citation": "RFO FAR 9.306; 52.209-3(h); 52.209-4(i)", "issuer": "FAR Council / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. defense acquisitions, including overseas performance; contract and agency conditions assessed separately", "summary": "A solicitation requiring first-article approval must identify approval characteristics and the testing requirements; contractor testing also requires specified report data. It must address quantities, schedules, manufacturing-standard status, waiver eligibility, eligible alternative offers and applicable evaluation information.", "applies_when": "Preparing a solicitation or evaluating whether a follow-on requirement can waive first-article testing based on identical or similar supplies previously furnished by that offeror and accepted by the Government.", "required_action": "Describe the required test evidence and its relation to production quantity. Invite the supporting contract numbers, if any, and eligible offers with and without testing. Include appropriate estimated government testing costs in evaluation, and identify the restriction on materially unbalanced first-article/test prices if separately priced.", "exceptions": "The Government may waive testing; an offeror/contractor may request a waiver. Prior acceptance is an eligibility condition, not an automatic waiver. If the solicitation permits earlier delivery when testing is waived and the Government requires it, that resulting schedule difference must not become an award evaluation factor.", "approval_authority": "CO applies the solicitation and waiver provisions with technical advice and applicable agency procedures; no local waiver delegation is established.", "locator": "RFO 9.306(a)-(j), especially(c)-(d),(f)-(j); 52.209-3(h); 52.209-4(i)", "source_ids": [ "RSRC-0181", "RSRC-0182", "RSRC-0183" ], "limitations": "This is a first-article waiver route, not a waiver of production acceptance, source qualification, OT&E, cyber, spectrum or safety duties. The displayed 9.306(j) cross-reference to 15.404-1(g) requires reconciliation with current adopted Part 15 for a pricing action; this review does not settle that numbering.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0225" }, { "type": "related requirement", "target": "RULE-0227" }, { "type": "related requirement", "target": "RULE-0039" } ], "date_note": "Dates identify DoD adoption by 2026-O0042. The RFO Basic clause headers display Deviation Date; no separate clause date is invented. Alternate I: January 1997; Alternate II: September 1989. The deviation remains until rescinded or incorporated.", "version_state": "DoD-adopted RFO 9.3 and current referenced RFO first-article clause forms; actual incorporated terms control existing-contract duties" }, { "id": "RULE-0227", "title": "Choose the testing clause and obtain a written first-article decision", "citation": "RFO FAR 9.301, 9.307-.308; 52.209-3(a)-(b),(e); 52.209-4(a)-(b),(e)", "issuer": "FAR Council / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. defense acquisitions, including overseas performance; contract and agency conditions assessed separately", "summary": "Use 52.209-3 when the contractor conducts first-article testing and 52.209-4 when the Government conducts it, under their prescriptions. The CO gives written approval, conditional approval or disapproval. Approval accepts test results; all specifications and other contract terms remain in force.", "applies_when": "Selecting first-article terms or administering test-report submission, sample delivery and the government decision for a covered supply contract.", "required_action": "Complete item/quantity, facility, notice, delivery/report and government-response blanks. Contractor testing requires advance written notice so the Government may witness it. Coordinate advance shipment/report notice through the administration office to the testing activity; obtain its recommendation, issue the CO notice and copy administration. Include the applicable line item and shipment number when available.", "exceptions": "Fixed-price prescriptions call for the clause; cost-reimbursement prescriptions call for a substantially similar clause. If not consumed/destroyed, an approved article may count toward quantity only if it meets all acceptance requirements and the contract does not provide otherwise. Conditional approval states further action; disapproval states reasons.", "approval_authority": "Testing activity advises the contracting office; CO issues the decision. The administration office coordinates the notice. First-article approval does not substitute for an authorized contractual acceptance decision.", "locator": "RFO 9.301; 9.307(a)-(b); 9.308-1(a)-(b), 9.308-2(a)-(b); 52.209-3(a)-(b),(e); 52.209-4(a)-(b),(e)(1)", "source_ids": [ "RSRC-0181", "RSRC-0182", "RSRC-0183" ], "limitations": "No default number of approval days is established: the contract blanks matter. Drawing, design or specification changes use the Changes clause under 9.307(b). Technical approval cannot itself change the contract or authorize operational use.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0193" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0226" }, { "type": "related requirement", "target": "RULE-0228" }, { "type": "related requirement", "target": "RULE-0229" } ], "date_note": "Dates identify DoD adoption by 2026-O0042. The RFO Basic clause headers display Deviation Date; no separate clause date is invented. Alternate I: January 1997; Alternate II: September 1989. The deviation remains until rescinded or incorporated.", "version_state": "DoD-adopted RFO 9.3 and current referenced RFO first-article clause forms; actual incorporated terms control existing-contract duties" }, { "id": "RULE-0228", "title": "Control production before first-article approval and select the alternates", "citation": "RFO FAR 9.305, 9.308; 52.209-3(g), Alternates I/II; 52.209-4(h), Alternates I/II", "issuer": "FAR Council / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. defense acquisitions, including overseas performance; contract and agency conditions assessed separately", "summary": "Under the Basic clauses, buying materials/components for or starting the remaining production quantity before approval is at the contractor’s sole risk; those costs are not allocable for progress payments or convenience-termination settlements. Alternate II provides a limited written CO authorization route.", "applies_when": "Delivery planning or a request to buy materials or begin production before the first article is approved, including an existing contract where the applicable clause and alternate must first be identified.", "required_action": "Allow enough delivery time after approval for material acquisition and production. When the prescribed Alternate II is used, identify the specific materials/components or production necessary for the delivery schedule in written CO authorization. Track authorized costs distinctly. Select Alternate I when the contract requires first article and production at the same facility.", "exceptions": "Alternate II replaces only the Basic risk paragraph: until approval, first-article costs and authorized costs are allocable for the two listed purposes. If testing reveals deviations, the contractor must correct or replace produced items at the government-designated location without changing contract price. Authorization is limited to the necessary production/materials scope.", "approval_authority": "CO provides the written authorization under the applicable Alternate II; agency implementation and actual contract terms must support its use.", "locator": "RFO 9.305(a)-(b); 9.308-1/-2(a)(2)-(3),(b)(2)-(3); 52.209-3 Basic(g), Alternate I(i), Alternate II(g); 52.209-4 Basic(h), Alternate I(j), Alternate II(h)", "source_ids": [ "RSRC-0181", "RSRC-0182", "RSRC-0183" ], "limitations": "This is not automatic payment entitlement, a blanket cost-allowability determination, first-article approval or a waiver of other funding/payment conditions. An informal technical assurance does not satisfy the written authorization provision.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0227" }, { "type": "related requirement", "target": "RULE-0030" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0229" } ], "date_note": "Dates identify DoD adoption by 2026-O0042. The RFO Basic clause headers display Deviation Date; no separate clause date is invented. Alternate I: January 1997; Alternate II: September 1989. The deviation remains until rescinded or incorporated.", "version_state": "DoD-adopted RFO 9.3 and current referenced RFO first-article clause forms; actual incorporated terms control existing-contract duties" }, { "id": "RULE-0229", "title": "Track first-article retests, government delays and test-support duties", "citation": "RFO FAR 9.307(b); 52.209-3(c)-(f); 52.209-4(c)-(g)", "issuer": "FAR Council / DPCAP", "instrument_type": "Class deviation", "topic": "Acceptance", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Applicable U.S. defense acquisitions, including overseas performance; contract and agency conditions assessed separately", "summary": "After disapproval, the Government may request another test or article under the clauses; the contractor bears the stated additional testing costs. Late article/report delivery or disapproval engages the contract’s Default-clause delivery language. Government decision delay has a separate equitable-adjustment provision conditioned on a timely written contractor request.", "applies_when": "Administering first-article failures, corrections, repeat testing, government-response dates, test-site support or disposition under an incorporated first-article clause.", "required_action": "Track receipt and response dates against filled contract terms, record reasons and required corrective action, and use authorized contract changes for drawing/design/specification changes. On a government delay, assess the timely written request under the Changes clause. For government testing, enforce the stated operating/maintenance instructions, spare-parts support and repair duties and applicable article removal/disposal terms.", "exceptions": "Government testing clause(e)(2) places removal/disposal expense on the contractor unless the contract provides otherwise. The clauses reserve government rights to seek an equitable price adjustment for an extended delivery schedule or added government test costs. Their government-delay adjustment addresses affected dates, price and other terms; it is not automatic approval.", "approval_authority": "CO administers contractual decisions, adjustments and remedies with the test/administration activities and counsel as appropriate; the testing laboratory does not acquire independent modification authority.", "locator": "52.209-3(c),(d),(e),(f); 52.209-4(c),(d),(e)(1)-(2),(f),(g); RFO 9.307(b)", "source_ids": [ "RSRC-0181", "RSRC-0182", "RSRC-0183" ], "limitations": "The Default-clause reference does not itself terminate a contract; apply the actual clause and procedures. Retest costs and remedies are bounded by the incorporated terms, including cost-reimbursement adaptations. No fixed payment hold, acceptance shortcut or additional closeout condition is created.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0227" }, { "type": "related requirement", "target": "RULE-0228" }, { "type": "related requirement", "target": "RULE-0192" }, { "type": "related requirement", "target": "RULE-0036" } ], "date_note": "Dates identify DoD adoption by 2026-O0042. The RFO Basic clause headers display Deviation Date; no separate clause date is invented. Alternate I: January 1997; Alternate II: September 1989. The deviation remains until rescinded or incorporated.", "version_state": "DoD-adopted RFO 9.3 and current referenced RFO first-article clause forms; actual incorporated terms control existing-contract duties" }, { "id": "RULE-0230", "title": "Establish the FDA exemption route before specifying a nonconforming laser", "citation": "21 CFR 1010.5(a)-(c), (e)(1)", "issuer": "FDA / CDRH", "instrument_type": "Regulation", "topic": "Safety", "equipment": [ "Laser", "Effector", "Counter-UAS", "Camera", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. electronic-product radiation rules and the stated DoD exemption; overseas and host-nation scope require separate determination", "summary": "Government use alone does not grant a performance-standard exemption. FDA’s CDRH Director may grant one on application where the specified criteria are met. The regulation recommends early agency consultation when specifications must depart from applicable radiation standards, and retention of compatible standard requirements.", "applies_when": "A proposed product or product class is otherwise subject to a Subchapter J performance standard and the agency or manufacturer seeks an exemption. Assess the applicable standard and transaction scope first.", "required_action": "Identify whether an existing exemption covers the precise product/use or a new FDA application is needed. For an application, address the applicable 1010.5(c) contents: product/use, required deviations, justification, radiation protection, duration/units and responsible parties, plus any required study information. Coordinate requirements and evidence with safety officials and counsel.", "exceptions": "The two criteria routes differ: (a)(1) requires agency radiation procurement specifications and a type used solely/predominantly by government; (a)(2) covers the stated research, investigation, study, demonstration, training or national-security purposes. These are bases for application, not self-executing exemptions. Paragraph(b) uses should, not shall.", "approval_authority": "FDA CDRH Director grants the regulatory exemption by written notice and may impose conditions. The CO does not acquire that FDA authority from a warrant, command affiliation or funding source.", "locator": "21 CFR 1010.5(a)(1)-(2), (b), (c) opening and(c)(1)-(13), (e)(1)", "source_ids": [ "RSRC-0188" ], "limitations": "For a confidential petition the regulation specifies original/redacted copies; classified national-security information must not be included. This reference is not an application. It does not establish that all overseas purchases are subject to identical U.S. market requirements or that exemption from one standard waives other law.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0231" }, { "type": "related requirement", "target": "RULE-0232" }, { "type": "related requirement", "target": "RULE-0036" } ], "date_note": "Dates identify the cited instrument only. eCFR title-wide update dates are not section effective dates; the individual exemption controls its duration. The 1976 letter transcription has a July29 letter date and July26 exemption-issuance reference.", "version_state": "Current displayed 1010.5 and/or the cited historical exemption instruments as amended, with FDA Notice 52 expressly classified as nonbinding guidance" }, { "id": "RULE-0231", "title": "Verify the product-specific military laser exemption letter", "citation": "FDA Laser Notice 52, Background and Guidance; exemption 76EL-01DOD", "issuer": "FDA / CDRH", "instrument_type": "Agency guidance and exemption conditions", "topic": "Safety", "equipment": [ "Laser", "Effector", "Counter-UAS", "Camera", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. electronic-product radiation rules and the stated DoD exemption; overseas and host-nation scope require separate determination", "summary": "FDA’s nonbinding Notice 52 explains that a manufacturer needs a written letter from an authorized DoD procuring agency before selling a specific product under the standing military laser exemption. A military-exempt label or sales assertion does not establish that documentation.", "applies_when": "Considering a laser represented as military exempt for a new award, order, replacement, modification or additional quantity.", "required_action": "Identify the product and configuration, review the written letter and any unit, Service or time limits, and obtain the appropriate DoD laser safety evaluation. Match the proposed acquisition to the letter and applicable exemption conditions; establish the current authorized DoD issuing office through current implementation.", "exceptions": "The standing exemption addresses lasers used exclusively by DoD components for the stated combat, combat-training or classified purposes. Notice 52’s account of that exemption is distinct from 1010.5’s general application categories; ordinary government ownership or a training label does not automatically extend the military exemption.", "approval_authority": "Authorized DoD procuring agency under the standing exemption, with appropriate DoD laser safety representatives. Current DAF delegation is not established by the guidance’s historical contact list or by this library.", "locator": "Notice 52: disclaimer, Background and Guidance paragraphs1-3 (PDF pp.3-4);1976 letter: grant and procurement-monitoring paragraphs", "source_ids": [ "RSRC-0185", "RSRC-0186", "RSRC-0188" ], "limitations": "Notice 52 expressly disclaims independent binding force; the statute, regulations and written exemption conditions control. The complete current DoDI 6055.15/DAF implementation remains unresolved in GAP-012. An FDA product exemption is not permission to operate, engage targets, export, import or disregard host-nation requirements.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2002-07-12", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0230" }, { "type": "related requirement", "target": "RULE-0232" }, { "type": "related requirement", "target": "RULE-0059" } ], "date_note": "Dates identify the cited instrument only. eCFR title-wide update dates are not section effective dates; the individual exemption controls its duration. The 1976 letter transcription has a July29 letter date and July26 exemption-issuance reference.", "version_state": "Current displayed 1010.5 and/or the cited historical exemption instruments as amended, with FDA Notice 52 expressly classified as nonbinding guidance" }, { "id": "RULE-0232", "title": "Recheck exemptions before laser modifications, changed use or expiry", "citation": "21 CFR 1010.5(d), (e)(2); FDA Laser Notice 52 Guidance paragraph1", "issuer": "FDA / CDRH", "instrument_type": "Regulation and agency guidance", "topic": "Safety", "equipment": [ "Laser", "Effector", "Counter-UAS", "Camera", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. electronic-product radiation rules and the stated DoD exemption; overseas and host-nation scope require separate determination", "summary": "Under 1010.5, changes that make the application’s radiation-safety information incorrect require an amendment request in advance. An extension request, if needed, is due at least 60 days before the exemption expires. Notice 52 separately explains that a manufacturer’s subsequent modification of a military-exempt product requires a new DoD letter.", "applies_when": "Proposing a product modification, changed use/control procedure, replacement configuration, additional order or continuation beyond an exemption’s terms.", "required_action": "Compare the planned configuration/use with the underlying FDA exemption and product-specific DoD letter. Route the required amendment or new letter before relying on coverage; track applicable duration and quantity limits alongside contract milestones. Record the exemption number, expiration, requested change and its basis as required by(d).", "exceptions": "The 60-day period belongs to an FDA exemption extension request, not every contract option or every DoD letter. A contract option does not itself extend regulatory coverage. FDA may amend or withdraw an exemption on the notice’s date, or immediately for an imminent health hazard.", "approval_authority": "The applicant requests amendment/extension; FDA controls its regulatory grant. The authorized DoD procuring agency controls the product letter within the standing exemption. The CO separately controls authorized contract changes.", "locator": "21 CFR 1010.5(d)(1)-(3), (e)(2); Notice 52 Guidance paragraph1 (PDF p.4)", "source_ids": [ "RSRC-0188", "RSRC-0185" ], "limitations": "Do not treat an FDA amendment, DoD product letter and contract modification as interchangeable documents. No actual product change, software alteration, exemption extension or acceptance determination is made here; technical safety officials must assess the facts.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0231" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0233" } ], "date_note": "Dates identify the cited instrument only. eCFR title-wide update dates are not section effective dates; the individual exemption controls its duration. The 1976 letter transcription has a July29 letter date and July26 exemption-issuance reference.", "version_state": "Current displayed 1010.5 and/or the cited historical exemption instruments as amended, with FDA Notice 52 expressly classified as nonbinding guidance" }, { "id": "RULE-0233", "title": "Carry laser safety conditions and exemption identification into delivery requirements", "citation": "21 CFR 1010.5(b), (e)(1), (f); exemption 76EL-01DOD; FDA Laser Notice 52 Background", "issuer": "FDA / CDRH", "instrument_type": "Regulation and exemption conditions", "topic": "Safety", "equipment": [ "Laser", "Effector", "Counter-UAS", "Camera", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. electronic-product radiation rules and the stated DoD exemption; overseas and host-nation scope require separate determination", "summary": "An exemption may impose manufacture, use, control and disposal conditions. Section 1010.5(f) requires permanent, legible, accessible identification unless the exemption prescribes another manner. The DoD exemption retains practicable radiation-safety specifications and adequate alternative controls rather than eliminating safety obligations.", "applies_when": "Preparing specifications, negotiating a covered change or planning delivery verification for a laser supplied under an exemption.", "required_action": "Translate the applicable written exemption’s identification, configuration and documentation conditions into the acquisition package with safety/quality officials. Specify evidence needed to verify those contract requirements on delivery. Preserve applicable safety provisions and DoD controls instead of accepting a generic military-exempt claim.", "exceptions": "The exemption can prescribe alternative identification;1010.5(f) is not authority to remove identification at the contractor’s discretion. The 1976 exemption has its own identification wording and conditions; use the controlling grant rather than combining labels by inference.", "approval_authority": "FDA sets regulatory/exemption terms; DoD safety officials assess applicable controls; authorized contracting and acceptance officials administer incorporated requirements.", "locator": "21 CFR 1010.5(b), (e)(1), (f);1976 letter procurement-specification and identification paragraphs; Notice 52 Background conditions (PDF pp.3-4)", "source_ids": [ "RSRC-0188", "RSRC-0186", "RSRC-0185" ], "limitations": "This is an acquisition documentation and compliance requirement, not a laser design specification or operational safety assessment. No particular warning device is waived by this record. Changes to existing contracts require an authorized contractual route, and product documentation alone is not operational authorization.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0231" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0234" } ], "date_note": "Dates identify the cited instrument only. eCFR title-wide update dates are not section effective dates; the individual exemption controls its duration. The 1976 letter transcription has a July29 letter date and July26 exemption-issuance reference.", "version_state": "Current displayed 1010.5 and/or the cited historical exemption instruments as amended, with FDA Notice 52 expressly classified as nonbinding guidance" }, { "id": "RULE-0234", "title": "Preserve exempt-laser records and check restrictions before disposition", "citation": "FDA exemption 76EL-01DOD; March 18, 1986 amendment; Laser Notice 52 Guidance final paragraph", "issuer": "FDA / CDRH", "instrument_type": "Agency exemption and amendment", "topic": "Safety", "equipment": [ "Laser", "Effector", "Counter-UAS", "Camera", "Drone", "Integration", "Sustainment" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. electronic-product radiation rules and the stated DoD exemption; overseas and host-nation scope require separate determination", "summary": "The 1986 FDA amendment removed the standing DoD exemption’s annual-report requirement effective September 1, 1985, while retaining underlying records for verification. The original exemption calls for permanent status records including ultimate disposition and advance FDA authorization for excess/surplus disposal; Notice 52 also addresses transfers outside DoD.", "applies_when": "Planning lifecycle records, maintenance returns, contract closeout support, excess/surplus disposition or a proposed transfer of an exempt laser.", "required_action": "Identify the responsible DoD custodian and preserve product, manufacturer, exemption and disposition status records. Check applicable grant conditions before releasing equipment through excess/surplus channels. For an outside-DoD transfer, Notice 52 explains the need for full FDA-standard compliance, certification and reporting; route the actual disposition with property, safety and legal officials.", "exceptions": "Annual-report relief is specific to this DoD exemption; it is not relief from every reporting or records duty. The original grant expressly retains 1002.20 accidental-radiation reporting. No deadline or procedure from that unreviewed provision is supplied here.", "approval_authority": "DoD maintains the exemption records; FDA may request information and controls applicable disposal authorization. Actual property-disposal officials and contractor deliverables must be established separately.", "locator": "1976 letter monitoring/status/disposition paragraphs and 1002.20 reservation; March 18, 1986 letter operative amendment and records paragraphs; Notice 52 Guidance final paragraph (PDF pp.4-5);1010.5(e)(1)", "source_ids": [ "RSRC-0186", "RSRC-0187", "RSRC-0185", "RSRC-0188" ], "limitations": "Permanent exempt-product status records are not a new retention period for every contract file. Notice 52 is guidance; apply the actual grant and current disposal rules together. FDA compliance does not itself authorize export, transfer to an ally, payment or contract closeout. The historical letter’s original annual-report terms must be read with the later amendment.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "1986-03-18", "effective_date": "1985-09-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0232" }, { "type": "related requirement", "target": "RULE-0233" }, { "type": "related requirement", "target": "RULE-0074" }, { "type": "related requirement", "target": "RULE-0075" } ], "date_note": "Dates identify the cited instrument only. eCFR title-wide update dates are not section effective dates; the individual exemption controls its duration. The 1976 letter transcription has a July29 letter date and July26 exemption-issuance reference.", "version_state": "Current displayed 1010.5 and/or the cited historical exemption instruments as amended, with FDA Notice 52 expressly classified as nonbinding guidance" }, { "id": "RULE-0235", "title": "Document why Government property should be furnished", "citation": "RFO FAR 45.000-.103; 2026-O0046 Rev1,PGI 245.103-70", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "Contractors ordinarily supply their own property. Furnishing Government property requires the stated benefit, cost, risk and necessity findings; a contractor’s inability or unwillingness to supply resources is insufficient. The Part 45 property framework excludes software and intellectual property.", "applies_when": "Planning Government-furnished radar, camera, drone, effector, C2 hardware, spares or support equipment for a new award, order or change.", "required_action": "Identify tangible property, ownership and the relevant contract. Obtain the requiring activity’s documented furnishing decision and address the four FAR 45.102(b) elements in the contract file, including administration, removal and disposal costs and Government risk. Coordinate separate software/license rights.", "exceptions": "FAR 45.102(d) exempts property provided under repair, maintenance, overhaul or modification contracts from paragraph(b). PGI 245.103-70(1) separately lists repair, modification and overhaul for its requiring-activity documentation exception; do not broaden that list silently. Other Part 45 scope exclusions and clause duties require separate assessment.", "approval_authority": "Requiring activity makes the furnishing decision; contracting officer ensures applicable findings and documentation. No local delegation is established.", "locator": "RFO45.000(b), 45.101 property/GFP/CAP definitions, 45.102(a)-(e); Rev1 PDF pp.19-20,Attachment2 pp.1-2,PGI 245.103-70(1)-(2)", "source_ids": [ "RSRC-0190", "RSRC-0191" ], "limitations": "This is the contractor-property framework. Current DoDI 5000.64/DAF accountable-property implementation remains unresolved. A furnishing decision is not appropriation, export, operational or system-use authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0066" }, { "type": "related requirement", "target": "RULE-0141" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0236", "title": "Keep the GFP attachment aligned with contract changes", "citation": "2026-O0046 Rev1,DFARS 245.103-72; PGI 245.103-72/-74; RFO45.201", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "Anticipated GFP requires an attachment for the solicitation and award. Listed changes require both a contract modification and an updated, consolidated GFP attachment; updating a logistics record alone does not perform those contract actions.", "applies_when": "Offering Government equipment or changing its identity, quantity, status, use authority or contractual accountability.", "required_action": "Create the attachment in the PIEE GFP module, with required item data and serial-management/requisition information. Modify the contract and update the attachment for mandatory-field changes, additions/deletions, transfers, accepted CAP retained for contractor use, substitutions and withdrawal of use authority.", "exceptions": "If the GFP attachment itself is classified, use a separate attachment with similar data instead of the PIEE GFP module. A classified contract is not exempt merely because it is classified. No controlled attachment is needed for this public reference.", "approval_authority": "Contracting officer, coordinating accurate property data with the requiring activity and property officials.", "locator": "Rev1 PDF p.5,Attachment1 p.3, 245.103-72; PDF pp.21-22,Attachment2 pp.3-4,PGI 245.103-72(a)-(c), 245.103-74(1)-(3); RFO45.201(a)", "source_ids": [ "RSRC-0190", "RSRC-0191" ], "limitations": "No actual attachment or contract is evaluated. Property changes do not independently establish scope, competition, funding or modification authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0237" }, { "type": "related requirement", "target": "RULE-0238" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0237", "title": "Transfer property accountability through both contracts", "citation": "RFO45.106; 2026-O0046 Rev1,PGI 245.102(2), 245.103-71", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "Government property is accountable to one contract at a time. A transfer requires a firm need on the gaining contract and modifications to both contracts. DoD uses SF30 for accountability transfers; a DD1149 shipping document does not transfer contractual accountability.", "applies_when": "Moving GFP to a follow-on contract, replacement support contract or another existing contract.", "required_action": "Confirm the gaining contract’s firm requirement, coordinate SF30 modifications to gaining and losing contracts, use the GFP attachment and add required property clauses if absent from the gaining contract. Separately complete transaction reporting and any physical shipment.", "exceptions": "Accountability to one contract does not prohibit separately authorized use on other contracts under applicable terms. For former CAP transferred to another contract with the same contractor, FAR 45.106 excludes the stated suitability/timely-delivery warranties. CAP must first follow its delivery route.", "approval_authority": "Contracting officers responsible for the gaining and losing contracts, with property-administration coordination.", "locator": "RFO45.106; Rev1 PDF p.19,Attachment2 p.1,PGI 245.102(2); PDF pp.20-21,Attachment2 pp.2-3,PGI 245.103-71(1)-(2)", "source_ids": [ "RSRC-0190", "RSRC-0191" ], "limitations": "An option exercise, shipping form, GFP-system entry or operational handover alone does not establish the two-contract transfer. Applicable scope, consent and funding questions remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0238" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0238", "title": "Deliver contractor-acquired property before transferring it as GFP", "citation": "2026-O0046 Rev1,PGI 245.402-71", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "CAP requires a delivery line item. Direct contractual transfer of CAP between contracts is prohibited; delivery under a line item precedes transfer as GFP. Delivered and accepted CAP retained by the contractor becomes GFP and must be added to the attachment.", "applies_when": "Retaining contractor-acquired equipment for continuing support or moving it to another contract, including performance-based sustainment.", "required_action": "Provide a delivery line item and acceptance path. For unanticipated CAP or items lacking a delivery line item, direct delivery on an NSP line item with the six required identifiers. Apply the prompt-delivery conditions for qualifying capitalization values or designated special tooling/test equipment/equipment; then update the GFP attachment and contract as required.", "exceptions": "PGI 245.402-71(4)(ii) sets conditions for delivery as soon as practicable after identification. It does not remove the general line-item requirement for other CAP. Its capitalization reference is an accounting/delivery trigger, not authority to choose an appropriation.", "approval_authority": "Contracting officer directs delivery; authorized Government personnel perform acceptance and property officials reconcile records.", "locator": "Rev1 PDF pp.24-25,Attachment2 pp.6-7,PGI 245.402-71(1)-(4),including(4)(iii)(A)-(F); PGI 245.103-74(2)(iv)", "source_ids": [ "RSRC-0190" ], "limitations": "Government title may already exist before delivery. Title, formal delivery, acceptance, contractor custody and accountable-contract transfer are distinct. Full FAR 52.245-1 title rules and DoD/DAF accountable-system requirements remain beyond this review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0141" }, { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0237" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0239", "title": "Track GFP transactions and the reporting deadline that applies", "citation": "DFARS 252.245-7005(a)-(c),January 2024; 2026-O0046 Rev1 attachment", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "The reporting clause directs use of the PIEE GFP module for specified receipts, transfers, shipments, incorporation, loss, plant clearance and CAP requests. Its seven-business-day default applies specifically to receipt, transfer, shipment and incorporation status changes, unless the contract specifies otherwise.", "applies_when": "Administering a contract containing the applicable reporting clause, including property held by subcontractors.", "required_action": "Assign responsibility for each required event and data element. Keep NSN or the permitted identifier alternative, accountable-contract CAGE and number, shipment/receipt dates, qualifying serial numbers and reparable-item condition codes. Use WAWF for shipment of reparables after completed repair, maintenance, modification or overhaul, as specified by the clause and Appendix F.", "exceptions": "The seven-business-day rule covers(b)(1)(i)-(iv), not every event in(b)(1). Loss, plant clearance and buyback/conversion requests retain their own referenced requirements. A submission requesting conversion or buyback is not approval.", "approval_authority": "Contractor performs contract reporting, including ensuring the specified subcontractor-property reporting; contracting and property officials administer the incorporated terms.", "locator": "Rev1 PDF pp.11-14,Attachment1 pp.9-12, 252.245-7005(a)-(c); Acquisition.gov and current eCFR clause(b)(1)-(5),(c)(1)-(6)", "source_ids": [ "RSRC-0190", "RSRC-0192" ], "limitations": "Reporting a transfer does not replace SF30 modifications or delivery/acceptance. Complete loss, disposal, demilitarization, Appendix F and FAR 52.245-1 duties are not reproduced here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0237" }, { "type": "related requirement", "target": "RULE-0238" }, { "type": "related requirement", "target": "RULE-0035" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0240", "title": "Specify sustainment inventory reports and hardware delivery lines", "citation": "2026-O0046 Rev1,PGI 245.103-73 and245.103-74(3)", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "Sustainment arrangements holding Government inventory require scheduled inventory reporting. The requiring activity supplies reporting requirements; semiannual reporting is described as typical, not a universal fixed interval. Performance goals alone may leave hardware delivery and title undocumented.", "applies_when": "Acquiring contractor logistics support, performance-based logistics or other sustainment with Government inventory and replacement hardware.", "required_action": "Include the requiring activity’s applicable inventory CDRL. Use its assessment during planning, pricing, option and past-performance reviews as the PGI recommends. Where a fixed-price performance arrangement requires property without delivery lines, include NSP delivery lines; unit-acquisition-price tables may support receiving reports.", "exceptions": "Choose the actual reporting schedule and deliverables for the arrangement. The PGI says contracting officers should review the assessment at the listed decisions; do not recast that language as an automatic option prohibition.", "approval_authority": "Requiring activity defines reporting needs; contracting officer incorporates applicable CDRLs and delivery terms; acceptance/property officials reconcile resulting deliveries.", "locator": "Rev1 PDF pp.21-22,Attachment2 pp.3-4,PGI 245.103-73(1)-(3), 245.103-74(3)", "source_ids": [ "RSRC-0190" ], "limitations": "Inventory reporting does not itself create a delivery line, establish title or authorize an option. Current data-item instructions, all sustainment policy and actual contract requirements remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0238" }, { "type": "related requirement", "target": "RULE-0239" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0241", "title": "Apply the current property-clause prescriptions and narrow exception", "citation": "2026-O0046 Rev1 memo and DFARS245.107; RFO45.107", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; property-specific overseas requirements remain separate", "summary": "DoD requires FAR 52.245-1 in property repair, maintenance, overhaul and modification purchase orders regardless of unit acquisition cost. Revision 1 excludes nontraditional defense contractors from the 252.245-7003 system clause unless the exemption is waived; it separately retains the 252.245-7005 prescription.", "applies_when": "Selecting property clauses for a new solicitation, order or authorized change, including commercial acquisitions and proposed nontraditional-contractor treatment.", "required_action": "Apply current FAR/DoD prescriptions together. Establish eligibility and any lawful waiver before applying the 252.245-7003 exception. Include 252.245-7005 where 52.245-1 is required under the stated prescription, including covered Part 12 actions. Check gaining-contract clauses during a property transfer.", "exceptions": "The system-clause exception does not state a blanket exception from property reporting, attachments, FAR 52.245-1 or other duties. The DoD repair-purchase-order rule replaces FAR 45.107(d). For the negotiated fixed-price case described in245.107(1)(ii), use 52.245-1 without Alternate I.", "approval_authority": "Contracting officer applies the prescriptions. The reviewed245.107 text does not establish the current nontraditional-eligibility determination or waiver approval process; obtain applicable implementation and authority.", "locator": "Rev1 PDF pp.1-2 supersession/partial section 1826 implementation; PDF p.7,Attachment1 p.5, 245.107(1)-(4); RFO45.107(a)-(d)", "source_ids": [ "RSRC-0190", "RSRC-0191" ], "limitations": "The September 9 revision supersedes the February20 original. No eligibility, waiver, automatic deletion from an existing contract or payment-withholding authority is inferred. Full section 1826/business-system implementation remains in GAP-026.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-09", "effective_date": "2026-09-09", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0038" }, { "type": "related requirement", "target": "RULE-0236" }, { "type": "related requirement", "target": "RULE-0237" }, { "type": "related requirement", "target": "RULE-0239" } ], "date_note": "Dates identify the signed Revision 1 adoption, effective immediately; it remains in effect until rescinded or incorporated. A clause month or a site-wide update is not assigned an invented day. Existing contract terms and authorized modifications require separate assessment.", "version_state": "2026-O0046 Revision 1 dated September 9, 2026; selected adopted provisions and January 2024 reporting-clause text" }, { "id": "RULE-0242", "title": "Select the data-warranty form and justify added protection", "citation": "2026-O0035: DFARS 246.708, 246.710(1); RFO FAR 46.703, 46.705, 46.708", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "Obtain technical-data warranties when practicable and cost effective. The adopted prescription calls for a clause substantially the same as 252.246-7998 when 252.227-7989 is included and greater protection or duration than the ordinary inspection/warranty clauses is needed. Basic applies to contracts other than firm-fixed-price or fixed-price-incentive; Alternate I to fixed-price-incentive; Alternate II to firm-fixed-price.", "applies_when": "Selecting warranty coverage for manuals, drawings or other qualifying support data in a new solicitation, order or authorized contract change.", "required_action": "Evaluate use, harm, detectability, costs and enforceability; document why ordinary correction, replacement or price adjustment is inadequate if considering extended liability, and whether added liability deters nonconforming data. Check the required chief-of-contracting-office approval when extended liability applies. Record the actual clause number, edition, alternate and incorporated text.", "exceptions": "A data warranty is conditional, not mandatory for every deliverable. RFO 46.705(a) generally prohibits cost-reimbursement warranties absent stated exceptions/agency authorization. The signed 246.705(a) data exception contains 252.246-7XXX rather than the prescribed 252.246-7998; resolve GAP-027 before relying on that cross-reference.", "approval_authority": "CO selects the applicable form and documents the basis; chief of the contracting office approval under 246.703-1 applies unless an enumerated exception covers the action.", "locator": "2026-O0035 Attachment A1 pp. 10-11 (PDF pp. 12-13), 246.705(a), 246.708 and 246.710(1)(i)-(iii); RFO 46.703/.705/.708", "source_ids": [ "RSRC-0159", "RSRC-0160", "RSRC-0193" ], "limitations": "The standard 252.246-7001 March 2014 page is a separate edition reference for existing terms; it does not replace the adopted 252.246-7998 February 2026. No automatic modification, authority or commercial-software coverage is inferred.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0194" }, { "type": "related requirement", "target": "RULE-0039" }, { "type": "related requirement", "target": "RULE-0243" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0243", "title": "Separate technical-data coverage from software warranty approval", "citation": "2026-O0036: DFARS 227.7103-14(c); 252.227-7989(a), Technical data definition", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "Technical data includes software documentation but excludes computer software. Consider repair/maintenance use and warranty cost before obtaining a data warranty. Software that is part of a weapon system or major subsystem should be warranted within its system warranty; a non-weapon-system software warranty requires CO approval and tailored terms.", "applies_when": "Buying or changing support manuals, software documentation or noncommercial C2 software where the selected Part 227 provisions apply.", "required_action": "Identify the deliverable category and intended maintenance use. For non-weapon-system software, obtain CO approval, consider FAR 46.703 factors and tailor the data-warranty form as needed. Reconcile the Part 227 reference to 252.246-7001 with the Part 246 adopted 252.246-7998 prescription before drafting or changing terms.", "exceptions": "The weapon-system statement uses should; the non-weapon software approval uses must. These selected noncommercial provisions do not establish a blanket commercial software or cloud warranty. Technical-data definitions also exclude financial, administrative, cost/pricing, management and incidental contract-administration information.", "approval_authority": "CO approves the stated non-weapon-system software warranty. Applicable Part 246 approval requirements remain separate; no local delegation is established.", "locator": "Attachment A1 p. 28 (PDF p. 30), 227.7103-14(c)(1)-(3); p. 44 (PDF p. 46), 252.227-7989(a) Technical data definition", "source_ids": [ "RSRC-0133", "RSRC-0159" ], "limitations": "GAP-027 preserves the signed instruments’ inconsistent clause-number references. Warranty protection alone does not grant data or software license rights, access or operational authorization; full Part 227 rights and commercial-license terms need separate review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0147" }, { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0242" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0244", "title": "Track the data-line warranty period and written breach notices", "citation": "2026-O0035: 252.246-7998 Basic/Alternates I/II(b)-(d); standard 252.246-7001(b)-(d)", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "The data warranty covers conformity at delivery despite Government inspection or acceptance. The period extends three years after completion of delivery of the data line item identified in DD Form 1423, or longer if specified in the contract. A contractor discovering a breach within that period must notify the CO immediately in writing.", "applies_when": "Administering an incorporated data-warranty clause for delivered manuals, drawings or qualifying documentation, including after hardware acceptance.", "required_action": "Maintain the actual data-line delivery-completion date, contract-specific longer period and written-notice evidence. For Government-discovered breaches, notify the contractor in writing within the warranty period. Calendar from completion of the relevant data line, not an assumed equipment-acceptance or contract-closeout date.", "exceptions": "The clause warrants conformity at delivery, not all future obsolescence or every later Government requirement. Duration and notice analysis must use the actual incorporated edition and any authorized tailoring.", "approval_authority": "Contractor provides immediate written discovery notice; CO manages Government written notice and contract remedies.", "locator": "2026-O0035 PDF pp. 17-19, 21, paragraphs (b), (c), (d) introductory text for each variant; standard March 2014 form corresponding paragraphs", "source_ids": [ "RSRC-0159", "RSRC-0193" ], "limitations": "No warranty is created by this reference alone. Existing orders, modifications, final payment and closeout require review of their own terms; no universal closeout hold or statutory claim deadline is established here.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0242" }, { "type": "related requirement", "target": "RULE-0245" }, { "type": "related requirement", "target": "RULE-0191" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0245", "title": "Use the data-warranty remedy sequence and renewed coverage", "citation": "2026-O0035: 252.246-7998 Basic/Alternates I/II (d)-(e); standard 252.246-7001(d)-(e)", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "After qualifying breach notice, the CO may within a reasonable time direct prompt correction or replacement at contractor expense, or elect a price/fee adjustment when correction is no longer required or Government correction is more reasonable. If the contractor refuses or fails the direction, the CO may arrange correction and charge its cost, or elect an adjustment.", "applies_when": "A breach of an incorporated data warranty has been notified as required and the Government is selecting or enforcing a remedy.", "required_action": "Issue the written direction or election, document the adjustment basis and preserve the refusal/failure evidence before using the follow-on remedy. Track corrected or replaced data separately: the clause applies anew to the portion furnished under (d)(1)(i). Evaluate added liability only under the actual alternate.", "exceptions": "Basic (d)(3) limits enforcement of rights under this clause to its stated remedies. That wording is not a universal elimination of every other contract remedy. The renewed application covers the corrected/replaced portion, not automatically every original data deliverable.", "approval_authority": "CO exercises the specified written direction/election and reasonable-time determinations.", "locator": "2026-O0035 PDF pp. 18-22, complete (d)-(e) in Basic/Alternates; standard March 2014 form corresponding paragraphs; RFO 46.705(b)", "source_ids": [ "RSRC-0159", "RSRC-0193", "RSRC-0160" ], "limitations": "Inspection-clause rights concerning latent defects, fraud or gross mistakes amounting to fraud may not be limited by warranty clauses under RFO 46.705(b). Actual contract terms, evidence and counsel review govern disputed liability.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0244" }, { "type": "related requirement", "target": "RULE-0246" }, { "type": "related requirement", "target": "RULE-0191" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0246", "title": "Apply additional-liability caps and exclusions to the correct warranty alternate", "citation": "2026-O0035: 252.246-7998 Alternate I/II (d)(3); standard 252.246-7001 Alternate I/II (d)(3)", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "Alternate I adds breach damages subject to a cap of 75 percent of target profit; Alternate II uses 10 percent of total contract price. Both specify separate equipment-subcontractor data limits and exclusions. These are limits on the additional-liability provision, not a general 10-percent cap on all warranty correction costs.", "applies_when": "Assessing extended liability under an incorporated fixed-price-incentive or firm-fixed-price data-warranty alternate.", "required_action": "Identify the variant, target profit/contract price and whether the defective data came from an equipment subcontractor. Under the subcontract provision, use 10 percent of total FFP subcontract price, 75 percent of total CPFF/CPAF subcontract fee, or 75 percent of FPI/CPIF subcontract target profit/fee as specified. Assess every exclusion before asserting damages.", "exceptions": "Additional liability does not apply to the enumerated drawing/SIE data and named specification editions if current, accurate at submission and free of significant required-data omissions, or to defects the contractor discovers and reports in writing before Government discovery. These exceptions do not themselves erase (d)(1)-(2) correction/adjustment remedies. Alternate I expressly says damages due under the warranty are not allowable cost; do not attribute that sentence to Alternate II.", "approval_authority": "CO administers the incorporated alternate and coordinates disputed damages, calculations and exclusions with counsel.", "locator": "2026-O0035 PDF pp. 19-20, Alternate I (d)(3)(i)-(iv); pp. 21-22, Alternate II (d)(3)(i)-(iii); standard March 2014 corresponding paragraphs", "source_ids": [ "RSRC-0159", "RSRC-0193" ], "limitations": "The exact older specification names, categories and editions in the exclusion must be checked against actual deliverables; no new-design use or current status of those specifications is established. No unsupported universal choice between potentially interacting caps is supplied.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0242" }, { "type": "related requirement", "target": "RULE-0245" }, { "type": "related requirement", "target": "RULE-0194" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0247", "title": "Plan enforceable overseas repair and warranty costs", "citation": "RFO FAR 46.702-.703, 46.706(a), (b)(2)-(4), (6), 46.707, adopted by 2026-O0035", "issuer": "DoD / DPCAP; FAR Council", "instrument_type": "Adopted regulation and contract clause", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas implementation depends on the contract and applicable agreements", "summary": "Warranty value depends on enforceability and administration as well as the contractor’s price. Terms must specify coverage, obligations, remedies and duration. Repair in place should be provided when return, alternate-source repair or replacement is foreseeably impractical; transportation liability has a specified contractual-place-of-delivery limit.", "applies_when": "Drafting or changing warranties for deployed sensors, effectors, C2 hardware, spares or related services, and administering incorporated repair terms.", "required_action": "Assess location, distance, storage, defect reporting and traceability before award. If Government repair in place is contemplated, provide for contractor-furnished parts/material and installation instructions at the place of delivery. State reasonable duration and notice periods, consistent remedies and responsibility for repair, retest and transport. For FPI warranties, consider estimated warranty cost in target/ceiling prices and warranty costs in the final price; compliance after final-price establishment adds no cost to Government.", "exceptions": "The FAR says contractor transportation expense generally covers return from the contract delivery location and subsequent return, irrespective of FOB or acceptance point. Returns from other locations or alternate remedies do not create unlimited transport liability: charges may not exceed usual-commercial-method transport between that delivery location and the contractor plant and return. Specific incorporated terms remain controlling.", "approval_authority": "CO drafts consistent enforceable warranty terms with the requiring, technical and contract-administration activities.", "locator": "Official RFO Part 46: 46.702(c), 46.703(a)-(e), 46.706(a), complete (b)(2)(i)-(v), (b)(3)-(4), (6), 46.707; adoption memo PDF p. 1", "source_ids": [ "RSRC-0160", "RSRC-0159" ], "limitations": "These drafting provisions are not an automatic overseas repair entitlement, customs exemption or authority to alter an existing warranty unilaterally. Commercial warranty rules under Part 12 and complete Service sustainment policy remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-20", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0195" }, { "type": "related requirement", "target": "RULE-0192" }, { "type": "related requirement", "target": "RULE-0242" } ], "date_note": "Dates identify the signed adopting deviation and its February 1, 2026 effect; it continues until rescinded or incorporated. Contract incorporation, edition, approved tailoring and later modifications require action-specific assessment. A March 2014 clause-month label is not a new 2026 effective date.", "version_state": "Selected adopted 2026-O0035/2026-O0036 provisions; February 2026 clause compared with the standard March 2014 data-warranty form" }, { "id": "RULE-0248", "title": "Order generated data and software within the applicable deferred-ordering window", "citation": "2026-O0036: 227.7103-6(h), 227.7103-8; 252.227-7995; standard 252.227-7027", "issuer": "DoD / DPCAP", "instrument_type": "Adopted regulation and contract clause", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "Use the adopted deferred-ordering clause when a potential need exists but no firm requirement for the particular data item is established before award. It permits ordering data/software generated in contract or subcontract performance during performance or within the stated three-year period; ordering does not itself grant unlimited license rights.", "applies_when": "Planning potential later needs for sensor interfaces, repair data or C2 software, or administering an incorporated deferred-ordering term.", "required_action": "Identify the actual clause and generated deliverable. Under 227.7103-8, calendar three years after acceptance of all items other than data/software or contract termination, whichever is later. Separately track the clause’s technical-data obligation for a subcontractor item: three years after the contractor accepts final delivery of that item. Compensate conversion into the prescribed form, reproduction and delivery; determine use rights under the incorporated rights clause.", "exceptions": "The adopted 7995 clause references 7989 for use rights; the standard April 1988 7027 references the contract’s Rights in Technical Data and Computer Software clause. The provision reaches generated material, not every preexisting vendor asset, and does not itself direct new development. The subcontract-item clock can differ from the prime-contract clock.", "approval_authority": "CO determines applicable incorporation, timing, order scope and compensation; rights determinations and disputes require the contract and appropriate counsel.", "locator": "2026-O0036 Attachment A1 pp.18,21,84-85 (PDF pp.20,23,86-87): 227.7103-6(h), -8 and full 252.227-7995; standard 252.227-7027 April 1988 complete body", "source_ids": [ "RSRC-0133", "RSRC-0195" ], "limitations": "This is not authority to add an out-of-scope requirement, replace an existing clause automatically, or acquire source code and all license rights without assessing the actual contract. Full IP and challenge implementation remains unresolved.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0249" }, { "type": "related requirement", "target": "RULE-0207" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0249", "title": "Preserve the older two-year deferred-delivery term when reviewing existing contracts", "citation": "Standard 252.227-7026 (APR 1988); 2026-O0036 reserved 252.227-7026", "issuer": "DoD / DPCAP", "instrument_type": "Contract clause and adopted edition comparison", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "The April 1988 deferred-delivery clause covers data/software specifically identified in the contract as deferred. It permits delivery instructions during performance or within two years after acceptance of other items or termination, whichever is later. This differs from the three-year deferred-ordering mechanism.", "applies_when": "An existing contract or order actually incorporates 252.227-7026 April 1988, subject to any authorized modification.", "required_action": "Check the identified deferred deliverables and incorporation before sending delivery instructions. Calendar the two-year prime-contract period and the separate technical-data clock ending two years after contractor acceptance of final delivery of the relevant subcontractor item. Preserve those records through administration and closeout.", "exceptions": "The signed 2026-O0036 attachment marks 252.227-7026 reserved. Its standard web page remains useful for incorporated-term comparison but is not a basis for treating this clause as the current adopted prescription. No automatic conversion to three years is established.", "approval_authority": "CO verifies the actual contract term and any lawful change; this library establishes no local waiver or extension authority.", "locator": "Complete standard 252.227-7026 April 1988 body; 2026-O0036 Attachment A1 p.84 (PDF p.86), reserved entry", "source_ids": [ "RSRC-0194", "RSRC-0133" ], "limitations": "A clause reference in this library does not prove that any actual contract contains it. Separate the deadline to call for delivery from warranty periods, license durations, funding availability and closeout procedures.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0248" }, { "type": "related requirement", "target": "RULE-0244" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0250", "title": "Specify and assess data and software acceptance separately", "citation": "2026-O0036: DFARS 227.7103-14(b)(1)-(5)", "issuer": "DoD / DPCAP", "instrument_type": "Adopted regulation and contract clause", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "Solicitations and contracts must state what makes delivered technical data, documentation and software acceptable. COs or their authorized representatives determine conformity. Nonconforming deliverables generally require correction/replacement or an equitable price reduction under the stated conditions; marking-only defects use a separate procedure.", "applies_when": "Drafting deliverable requirements or accepting integration data, manuals, software documentation or noncommercial software during contract performance.", "required_action": "Define the required content and acceptance evidence before award or an authorized change. Apply the incorporated inspection/remedy clause; if it is absent, the cited policy refers to FAR 46.407(c)-(g). Do not accept nonconforming data/software under the ordinary route. When correction/replacement is impractical or not in the Government’s interest, assess the stated equitable-reduction alternative. For markings as the sole defect, use 227.7103-12(a) and reconcile GAP-028.", "exceptions": "Technical-data paragraph (b)(3) and software paragraph (b)(5) contain the marking-only exception. A hardware receipt, inspection stamp or shipment release does not by itself establish conformity of a separate data/software deliverable. The withholding clause has its own scope and limits.", "approval_authority": "CO or authorized representative determines conformity; CO administers remedies and markings procedures within actual authority.", "locator": "2026-O0036 Attachment A1 pp.27-28 (PDF pp.29-30), complete 227.7103-14(b)(1)-(5)", "source_ids": [ "RSRC-0133" ], "limitations": "The FAR fallback is a cross-reference, not a complete new review of FAR 46.407. The selected noncommercial implementation does not settle commercial software acceptance, RMF/operational approval or full validation/appeal procedures.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0193" }, { "type": "related requirement", "target": "RULE-0243" }, { "type": "related requirement", "target": "RULE-0251" }, { "type": "related requirement", "target": "RULE-0252" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0251", "title": "Apply technical-data withholding only within the clause’s limits", "citation": "2026-O0036: 227.7103-6(g)(3), 227.7103-14(b)(2),(4); 252.227-7996(a)-(b); standard 252.227-7030", "issuer": "DoD / DPCAP", "instrument_type": "Adopted regulation and contract clause", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "For required technical data that are late or deficient, the CO may withhold ten percent of the total contract price or amount unless the contract specifies less, until the data are accepted. Withholding is discretionary and subject to the clause’s exception; it is not an automatic penalty.", "applies_when": "An applicable incorporated technical-data withholding clause supports action on a late or deficient deliverable, including the specified restrictive-marking deficiency.", "required_action": "Verify the clause edition, delivery requirement, deficiency, amount and acceptance status. Consider data value and importance under 227.7103-14(b)(2), which allows a fixed amount or percentage up to ten percent pending correction/replacement or equitable reduction. Apply the lesser amount if specified. Preserve the basis for withholding and later payment.", "exceptions": "Paragraph (a) prohibits withholding and other action under that paragraph if the failure arises beyond the contractor’s control and without its fault or negligence. Withholding or subsequent payment does not waive Government rights. Technical data includes qualifying software documentation but excludes software itself; do not extend this clause to software code without separate authority. The 7996 introduction cites (g)(2), while the actual prescription is (g)(3); GAP-028 remains open.", "approval_authority": "CO exercises the clause’s discretionary remedy and coordinates disputed applicability, causation and amount with counsel.", "locator": "2026-O0036 PDF pp.20,29,87-88: prescription (g)(3), 227.7103-14(b)(2),(4), 7996 introduction and complete (a)-(b); standard 252.227-7030 March 2000 complete (a)-(b)", "source_ids": [ "RSRC-0133", "RSRC-0196" ], "limitations": "The standard 7030 form uses different rights-clause cross-references and must be matched to actual incorporated terms. No universal invoice hold, closeout hold, penalty or software-payment remedy is created. Warranty remedies and license rights remain separate.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0250" }, { "type": "related requirement", "target": "RULE-0252" }, { "type": "related requirement", "target": "RULE-0245" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0252", "title": "Separate defective marking format from disputed substantive rights", "citation": "2026-O0036: 227.7103-12(a)-(b); 252.227-7989(i)(1)-(2)", "issuer": "DoD / DPCAP", "instrument_type": "Adopted regulation and contract clause", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "A nonconforming marking has unauthorized form or content; an unjustified marking uses an authorized form but misstates Government rights. Different correction and validation procedures apply. A disagreement about license rights does not by itself permit removing the restriction.", "applies_when": "Reviewing restrictive legends on delivered technical data or noncommercial software before acceptance, use or disclosure.", "required_action": "Identify the defect type and applicable clause. For nonconforming format, 7989(i)(2) calls for CO notification and allows the stated ignore/correct/remove remedy if the contractor fails to correct within sixty days. For disputed justification, 7989(i)(1) requires the 7997 validation procedures and a determination before the stated remedy. Preserve the policy/clause timing difference in GAP-028 before acting.", "exceptions": "Policy 227.7103-12(a)(2) literally measures sixty days following the person’s receipt of the data or software, whereas clause 7989(i)(2) describes notice followed by failure to correct within sixty days. Do not silently replace either trigger. Policy (b)(2) separately permits agreement during performance that a restriction is unjustified, with correction/strike or instruction to correct; its failure-to-correct period runs sixty days after the instruction.", "approval_authority": "CO manages notification, correction and any challenge or agreement with the rights asserter; reconcile the timing issue and full validation requirements with authoritative policy and counsel.", "locator": "2026-O0036 Attachment A1 pp.22-23,54 (PDF pp.24-25,56), complete 227.7103-12(a)-(b) and 252.227-7989(i)(1)-(2)", "source_ids": [ "RSRC-0133" ], "limitations": "This selected review does not complete 252.227-7997 challenge periods, burdens, appeals, third-party release or commercial-license rules. No right to disclose, erase legends or infer unlimited rights merely from delivery, funding or an assertion is established.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0250" }, { "type": "related requirement", "target": "RULE-0251" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0253", "title": "Identify prior Government deliveries when restricted data are offered", "citation": "2026-O0036: 227.7103-6(f); 252.227-7028 (JUN 1995)", "issuer": "DoD / DPCAP", "instrument_type": "Adopted regulation and contract clause", "topic": "Data and software rights", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas application depends on the action and applicable agreements", "summary": "When the resulting contract requires technical-data delivery, the selected prescription calls for 252.227-7028. The provision requires identification of intended data/software deliveries with other-than-unlimited rights that are identical or substantially similar to material previously produced for, delivered to, or owed to the Government.", "applies_when": "Preparing a solicitation under the selected prescription and evaluating the required offer attachment for restricted data or software.", "required_action": "Require identification of the production contract number; the most recent or future delivery contract number and recipient organization’s name/address; and Government use/disclosure limitations, including the earliest expiration when applicable. Use the information to assess needed rights and prior-delivery history in the proper protected contract file.", "exceptions": "The disclosure concerns the provision’s stated intended restricted deliveries, not every vendor document or every prior contract. A prior Government delivery does not automatically establish unlimited rights in the current acquisition.", "approval_authority": "Offeror supplies the prescribed identification; CO evaluates it under applicable rights and acquisition procedures.", "locator": "2026-O0036 Attachment A1 pp.18,85 (PDF pp.20,87), 227.7103-6(f) and complete 252.227-7028(a)-(c)", "source_ids": [ "RSRC-0133" ], "limitations": "This public guide identifies required information but does not collect actual offers, contract numbers, data or source-selection material. Complete SBIR/STTR prescriptions and validation procedures are outside this bounded review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-01-21", "effective_date": "2026-02-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0148" }, { "type": "related requirement", "target": "RULE-0248" }, { "type": "related requirement", "target": "RULE-0252" } ], "date_note": "January 21, 2026 identifies the signed adopting deviation; February 1 is its stated effect, continuing until rescinded or incorporated. Standard clause month labels do not establish a new effective date or automatic existing-contract amendment. Identify actual incorporation and authorized modifications.", "version_state": "Selected 2026-O0036 provisions; February 2026 adopted clauses and June 1995 provision distinguished from standard April 1988/March 2000 forms" }, { "id": "RULE-0254", "title": "Revalidate committed funds against the draft award and line items", "citation": "FMR Volume 3 (SEP 2026), §§8.1–8.2", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas funding and local authority require action-specific assessment", "summary": "Drafting can change descriptions or line-item structure from the funded purchase request. Certifying officials must perform automated pre-award validation with the contract-issuing organization so committed funds remain available and suitable for the intended purpose.", "applies_when": "Preparing or administering ABAD sensor, effector or C2 awards, orders or funding changes; identify the actual appropriation, available period, legal obligation and incorporated terms.", "required_action": "Reconcile the final draft with the certified requirement before award. Preserve SLOA and accounting-to-procurement line-item traceability from commitment to obligation and payment; segregate line items requiring different accounting treatment. Resolve changed purpose, amount or structure with the certifying official and FM.", "exceptions": "The Global Exchange tool is a permitted implementation option, not a universal mandatory system. Availability and purpose checks do not authorize a new appropriation use, exception or local delegation.", "approval_authority": "Certifying official with the contract-issuing organization; accounting/funding officials maintain the required transaction alignment.", "locator": "Complete §§8.1–8.2, PDF p.15; applicability p.3", "source_ids": [ "RSRC-0124" ], "limitations": "Local systems, routing and supplemental procedures remain unresolved in GAP-016. Funding origin in USAFE/EUCOM alone does not establish purpose or approval authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0053" }, { "type": "related requirement", "target": "RULE-0056" }, { "type": "related requirement", "target": "RULE-0255" } ], "date_note": "September 2026 is the FMR edition, without an invented day. GAO dates identify decisions, not a new department policy effective date. The July 15, 2026 signed RFO adoption is effective immediately until rescinded/incorporated; no automatic change to existing terms is inferred.", "version_state": "Selected September 2026 FMR policy" }, { "id": "RULE-0255", "title": "Document and record obligations promptly within the same month", "citation": "FMR Volume 3 (SEP 2026), §§8.3–8.4", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas funding and local authority require action-specific assessment", "summary": "The incurring office supplies the obligating document within five calendar days; the recording office records it within five calendar days of receipt. All obligations must be recorded within ten calendar days following incurrence and in the same calendar month.", "applies_when": "Preparing or administering ABAD sensor, effector or C2 awards, orders or funding changes; identify the actual appropriation, available period, legal obligation and incorporated terms.", "required_action": "Record the legal obligation when incurred, supported by documentary evidence and the required accounting classification. Reduce an authorized verbal agreement to writing before recording. When the amount cannot feasibly be ascertained, use the best estimate and retain its inputs, assumptions and calculations. Track both office deadlines and the stricter month-end boundary; refer late items for the applicable missed-obligation procedures.", "exceptions": "The five/ten-day administrative limits do not extend fund availability or authorize backdating, an unauthorized commitment or delaying month-end recording. This selected review does not establish all §8.16 correction procedures.", "approval_authority": "Office incurring the obligation transmits support; recording office posts it; responsible FM officials address corrections and possible funding violations.", "locator": "Complete §§8.3, 8.4.1 and 8.4.2.1–8.4.2.2, PDF pp.15–16", "source_ids": [ "RSRC-0124" ], "limitations": "The existing statutory record retains its annual-edition currency limit. System-specific evidence, adjustments and supplementary procedures require separate verification.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0056" }, { "type": "related requirement", "target": "RULE-0135" }, { "type": "related requirement", "target": "RULE-0254" }, { "type": "related requirement", "target": "RULE-0256" } ], "date_note": "September 2026 is the FMR edition, without an invented day. GAO dates identify decisions, not a new department policy effective date. The July 15, 2026 signed RFO adoption is effective immediately until rescinded/incorporated; no automatic change to existing terms is inferred.", "version_state": "Selected September 2026 FMR policy" }, { "id": "RULE-0256", "title": "Reconcile obligations quarterly and separate recording from acceptance and payment", "citation": "FMR Volume 3 (SEP 2026), §8.17", "issuer": "DoW Comptroller", "instrument_type": "Department policy", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas funding and local authority require action-specific assessment", "summary": "Funds holders validate commitments and obligations as transactions occur and quarterly reconcile obligations incurred during the period to general-ledger and contracting records or obligating documents. Differences must be documented, investigated and brought to financial managers.", "applies_when": "Preparing or administering ABAD sensor, effector or C2 awards, orders or funding changes; identify the actual appropriation, available period, legal obligation and incorporated terms.", "required_action": "Use documented departmental SOPs; have FM assess necessary ledger adjustments and retain support before recording. Limit and reconcile estimated bulk obligations; do not use them for DLMS/MILSTRIP materiel requisitions requiring individual line-item obligations. Provide automated line-item recording for the specified external internet ordering processes. Within the responsible FM office, separate obligation/order-acceptance duties from receiving reports and acceptance/payment certification.", "exceptions": "If management determines segregation is impractical, it must identify and implement additional mitigating controls under Volume 5. This is not a general staffing waiver. An apparent Antideficiency Act violation on recording requires immediate research including consultation with the funds holder.", "approval_authority": "Assistant Secretaries/Comptrollers establish SOPs; funds holder performs reconciliation; FM reviews adjustments; management addresses segregation and mitigating controls.", "locator": "Complete §8.17.1–8.17.5, PDF pp.23–24", "source_ids": [ "RSRC-0124" ], "limitations": "Volume 5 controls, Volume 3 supplemental procedures and local implementation remain separately required; the quarterly obligation reconciliation is distinct from an unreviewed full dormant-account process.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0056" }, { "type": "related requirement", "target": "RULE-0255" }, { "type": "related requirement", "target": "RULE-0054" } ], "date_note": "September 2026 is the FMR edition, without an invented day. GAO dates identify decisions, not a new department policy effective date. The July 15, 2026 signed RFO adoption is effective immediately until rescinded/incorporated; no automatic change to existing terms is inferred.", "version_state": "Selected September 2026 FMR policy" }, { "id": "RULE-0257", "title": "Support and record an IDIQ minimum as a real commitment", "citation": "GAO B-318046 (JUL 7, 2009); B-321640 (SEP 19, 2011); adopted RFO 16.504-1/-2/-5", "issuer": "GAO; FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and GAO legal interpretation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas funding and local authority require action-specific assessment", "summary": "The adopted RFO text requires a minimum above nominal value that should not exceed what the Government is fairly certain to order. GAO explains that the guaranteed minimum creates a liability recorded on execution and must reflect a bona fide need then.", "applies_when": "Preparing or administering ABAD sensor, effector or C2 awards, orders or funding changes; identify the actual appropriation, available period, legal obligation and incorporated terms.", "required_action": "Document the expected minimum using relevant demand evidence and the need supported by the available appropriation. State the contract minimum, maximum, ordering period and last delivery date; distinguish the total contract guarantee from per-order limits. Identify when a binding liability arises and record it with FM. Check actual existing terms before any minimum change.", "exceptions": "B-318046’s $500 FEDLINK conclusion was fact-specific, not a Government-wide minimum or percentage of the ceiling. Historical competition thresholds and FAR numbering in the decision are not current thresholds. Current 16.504-2 addresses known kinds/minimum needs and ongoing repeated requirements.", "approval_authority": "CO sets supported contract terms under the adopted rules; funds certifier/FM and counsel assess the actual need, liability and appropriation. GAO opinions supply legal interpretation, not a local delegation.", "locator": "B-318046, IDIQ Contract Minimum Quantity Guarantee and Contracting Vehicles sections; B-321640 pp.3–4; current model 16.504-1/-2/-5; signed 2026-O0045 Rev1 pp.1–2", "source_ids": [ "RSRC-0197", "RSRC-0198", "RSRC-0199", "RSRC-0108" ], "limitations": "Full ordering, competition, option and funding-exception implementation is not established by these selected provisions. No specific ABAD vehicle or appropriation has been assessed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0020" }, { "type": "related requirement", "target": "RULE-0055" }, { "type": "related requirement", "target": "RULE-0056" }, { "type": "related requirement", "target": "RULE-0258" } ], "date_note": "September 2026 is the FMR edition, without an invented day. GAO dates identify decisions, not a new department policy effective date. The July 15, 2026 signed RFO adoption is effective immediately until rescinded/incorporated; no automatic change to existing terms is inferred.", "version_state": "GAO decision interpretation; selected current adopted RFO provisions separately identified" }, { "id": "RULE-0258", "title": "Establish the need before increasing an IDIQ minimum near year-end", "citation": "GAO B-321640 (SEP 19, 2011)", "issuer": "GAO", "instrument_type": "GAO legal interpretation", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; overseas funding and local authority require action-specific assessment", "summary": "In the SBA annual-fund case, a general replacement-cycle claim did not support the guaranteed amounts obligated at year-end. Moving funds to an IDIQ does not make them available for every later need throughout the contract’s life.", "applies_when": "Preparing or administering ABAD sensor, effector or C2 awards, orders or funding changes; identify the actual appropriation, available period, legal obligation and incorporated terms.", "required_action": "Before awarding or increasing a guarantee, including an option-period funding action, document the specific need, amount and appropriation period. Assess later orders separately and retain evidence for both the initial minimum and subsequent obligations. Correcting order funding does not by itself establish that the original guarantee was a bona fide need.", "exceptions": "The decision assessed annual FY2009/2010 funds and the total circumstances. It did not impose a categorical ban on year-end awards, later delivery or all inventory purchases; inventory replenishment was not asserted as the justification there. Identify any applicable lead-time or statutory exception separately.", "approval_authority": "CO, requirement owner, funds certifier/FM and counsel evaluate the actual facts and legal authority; the decision does not create a funding exception or determine every option’s obligation treatment.", "locator": "B-321640, facts pp.1–3, discussion pp.3–5 (including footnote5) and conclusion p.6", "source_ids": [ "RSRC-0198" ], "limitations": "No-year/multiyear appropriations and action-specific exceptions require their own analysis. GAO interpretation is distinguished from departmental implementation; targeted searches are not a comprehensive case citator.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2011-09-19", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0055" }, { "type": "related requirement", "target": "RULE-0133" }, { "type": "related requirement", "target": "RULE-0257" } ], "date_note": "September 2026 is the FMR edition, without an invented day. GAO dates identify decisions, not a new department policy effective date. The July 15, 2026 signed RFO adoption is effective immediately until rescinded/incorporated; no automatic change to existing terms is inferred.", "version_state": "GAO decision interpretation; selected current adopted RFO provisions separately identified" }, { "id": "RULE-0259", "title": "Allocate assisted-acquisition responsibilities before solicitation", "citation": "Adopted RFO17.502-1(a),17.503; DFARS217.500; PGI217.502-1/217.503", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and departmental procedures", "topic": "Contract vehicle", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "For covered assisted acquisitions, both agencies sign a written agreement before solicitation, allocating acquisition planning, execution, administration and management. The requesting agency supplies applicable unique requirements, or confirms in writing when none apply, and both agencies retain the agreement for audit.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Assign the CO, requirement owner, inspection/acceptance, funding, invoice, records and dispute responsibilities for the action. Include the required order description, delivery, funds, payment and statutory authority. The servicing agency prepares required acquisition J&As/D&Fs except the requesting agency’s Economy Act D&F; attach that D&F to the Economy Act order and retain the required servicing contract-file copy. Check that a non-FAR servicing agency can protect the customer’s requirements and funds.", "exceptions": "Model17.502-1(a)(2) does not require that paragraph’s agreement for a direct acquisition administered by the requesting agency; it does not waive all financial agreements or FPM25-05. Model17.500 contains an FSS-order exception at or below $750,000, while DFARS217.500 states the broader DoD rule for purchases by another agency, except micropurchases, unless more specific statutory authority exists. Evaluate both scopes. Deployed-unit cross-Component PGI provisions are not triggered merely by an overseas assignment.", "approval_authority": "Authorized requesting/servicing officials and their COs; specific approvals and written delegations remain action dependent.", "locator": "Model17.500,17.502-1(a),17.503(a)–(d); signedO0027 PDF pp.1–2,11,48", "source_ids": [ "RSRC-0200", "RSRC-0109", "RSRC-0127" ], "limitations": "GAP-029 preserves model cross-reference and PGI DD448/FPM25-05 implementation issues. No actual agreement or local authority has been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0021" }, { "type": "related requirement", "target": "RULE-0138" }, { "type": "related requirement", "target": "RULE-0139" }, { "type": "related requirement", "target": "RULE-0260" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected adopted RFO provisions with separately identified FY2027 certification where applicable" }, { "id": "RULE-0260", "title": "Review non-DoD vehicle scope, funding, fees and oversight", "citation": "DFARS217.600/217.601/217.670; PGI217.670(a)(3)", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and departmental procedures", "topic": "Contract vehicle", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "DoD direct and assisted acquisitions using non-DoD contracts above the applicable simplified acquisition threshold require review and approval. The review considers customer requirements, schedule, cost effectiveness including fees and discounts, and contract administration and oversight.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Document why the route serves DoD’s best interest, confirm vehicle scope and appropriation limitations, and address reporting. Require the provider to disclose use of another agency’s vehicle and all direct and indirect fees. If the route continues with layered fees, retain the rationale using the total costs and assigned oversight responsibilities. Reassess relevant facts when a later order or change alters the requirement.", "exceptions": "Use the applicable threshold and instrument-specific scope, not the historical SAT in an old delegation letter. An existing vehicle, another agency’s award or a favorable fee comparison does not establish order scope, funds availability or approval authority.", "approval_authority": "Department/agency review and approval under217.670 and applicable written procedures; no particular USAFE, EUCOM, AFICC or HCA delegation is established.", "locator": "SignedO0027 complete DFARS217.600/.601/.670, PDF pp.12–13; PGI217.670(a)(3), p.48", "source_ids": [ "RSRC-0109" ], "limitations": "Specific vehicle eligibility, ordering permissions, contracting delegation and local approval chain require separate assessment.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0021" }, { "type": "related requirement", "target": "RULE-0259" }, { "type": "related requirement", "target": "RULE-0261" }, { "type": "related requirement", "target": "RULE-0138" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected adopted RFO provisions with separately identified FY2027 certification where applicable" }, { "id": "RULE-0261", "title": "Check the current fiscal-year certification for nondefense assisted acquisitions", "citation": "Adopted RFO17.600–17.603; GSA FY2027 certification", "issuer": "FAR Council / DoD DPCAP; GSA", "instrument_type": "Adopted regulation and signed fiscal-year certification", "topic": "Contract vehicle", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "Covered DoD acquisitions through a nondefense agency above the applicable SAT require that agency’s current fiscal-year certification or the applicable written waiver. GSA’s signed FY2027 letter certifies its assisted-acquisition compliance with FAR and DoD requirements.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Retain the relevant agency and fiscal-year certification, check the assisted/direct route and any exclusions, and document the order’s separate scope, funding and approval analysis. Communicate DoD-unique requirements and verify the provider’s procedures/internal controls cover DoD FMR, DFARS, class deviations and PGI. Confirm the certification for a later fiscal year before relying on the route then.", "exceptions": "The requirement excludes the specified nondefense intelligence-community joint program meeting both agencies’ needs. The thirty-day submission requirement is not an automatic uncertified grace period. The GSA letter is expressly for assisted acquisitions in FY2027; it does not certify all agencies, independently approve an ABAD order or supply a waiver.", "approval_authority": "Nondefense agency head certification; separately applicable written waiver authority under17.603(e) and verified delegations. GSA’s letter is signed by its Senior Procurement Executive.", "locator": "Model17.600–17.603; GSA letter p.1, visible September8,2026 signature; signedO0027 pp.1–2", "source_ids": [ "RSRC-0200", "RSRC-0201", "RSRC-0109" ], "limitations": "Other agencies’ FY2027 letters were listed but not reviewed. Older17.703 numbering in the letter/directory is preserved in GAP-029.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-08", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0260" }, { "type": "related requirement", "target": "RULE-0262" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected adopted RFO provisions with separately identified FY2027 certification where applicable" }, { "id": "RULE-0262", "title": "Verify the written waiver delegation before bypassing nondefense certification", "citation": "RFO17.603(e); Section801 delegation memoranda dated2011-08-29,2018-08-27,2019-06-17", "issuer": "DoD DPCAP / predecessor offices", "instrument_type": "Signed delegation policy; current applicability requires confirmation", "topic": "Contract vehicle", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "The published delegation chain reaches Component Senior Procurement Executives and permits redelegation no lower than the Head of the Contracting Activity. That chain is distinct from a written determination waiving a certification requirement for specified acquisitions and a fiscal year.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Identify the applicable current statutory provision and written delegation, any redelegation, the authorized signer, covered acquisition categories and fiscal year before relying on a waiver. Preserve the actual determination and its limits. Resolve the historical chain’s continued applicability and DAF implementation through the authorized policy/legal route.", "exceptions": "The2011 memorandum’s $100,000 SAT is historical and must not be used as the current threshold. Its continuation clause depends on absence of rescission and Section801 repeal/modification. The current directory still links the chain, but that does not establish a current local redelegation or a blanket FY2027 waiver.", "approval_authority": "Model17.603(e) identifies USD(A&S); published2019 chain delegates to Component SPE with an HCA redelegation floor, subject to verification of current written authority. Organizational placement alone establishes none of these powers.", "locator": "Model17.603(e); delegation bundle p.1 June17,2019, p.2 August27,2018, pp.3–4 August29,2011", "source_ids": [ "RSRC-0200", "RSRC-0202" ], "limitations": "GAP-029 remains open for statutory/organizational succession and applicable current DAF redelegation. No actual waiver has been assessed.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2019-06-17", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0261" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Published historical delegation chain; current action-specific authority unresolved" }, { "id": "RULE-0263", "title": "Document the specific authority and funding package for a non-Economy Act order", "citation": "FMR Volume11 §§18.1–18.8; Supplemental §§18.1–18.5 and Figure18-1 (SEP2026)", "issuer": "DoW Comptroller", "instrument_type": "Department policy and supplemental procedures", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "A non-Economy Act order needs a specific alternative statutory authority and a supported bona fide need. The supplemental procedures require DoW-warranted CO review of orders greater than $500,000 before the funds-certifier or FS7600A/B issuance step; other policy duties separately use the applicable SAT.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Identify the enabling statute, definite goods/services, delivery/performance, proper fund cite, payment method, any advance-payment authority, DODAAC, competition/DoD-unique terms and fees. Use the exact applicable severable-service statement or goods/nonseverable certification at Supplemental18.1.2.6–.7. Have the requesting official certify availability, time and purpose. Establish all written binding-obligation criteria before recording; coordinate the current agreement/order and system route with FM.", "exceptions": "Do not replace the printed $500,000 review trigger with the SAT or use it to remove other review duties. An agreement cannot park expiring funds. The limited22USC2695 overseas-support MOU provision is not a general ABAD exception. System/form transition language does not establish a blanket exception to G-Invoicing or direct-cite PRDS deadlines.", "approval_authority": "Requesting official, DoW-warranted reviewing CO and funds certifier, with servicing agency and FM; the actual statute and written delegations govern authority.", "locator": "Policy18.1–18.8, PDF pp.83–86; Supplemental18.1–18.5, pp.72–74, and Fig18-1 p.77", "source_ids": [ "RSRC-0125", "RSRC-0203", "RSRC-0127" ], "limitations": "Supplemental18.5.2.2 names FS7600A. Do not infer that general terms alone create a valid obligation; reconcile current Treasury form instructions and the binding funding document. GAP-029 preserves cross-reference/form/system discrepancies.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0138" }, { "type": "related requirement", "target": "RULE-0139" }, { "type": "related requirement", "target": "RULE-0255" }, { "type": "related requirement", "target": "RULE-0264" }, { "type": "related requirement", "target": "RULE-0265" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected September2026 non-Economy Act departmental policy and supplemental procedures" }, { "id": "RULE-0264", "title": "Apply non-Economy Act return-of-funds rules by goods and service type", "citation": "FMR Volume11 Supplemental §18.6 (SEP2026)", "issuer": "DoW Comptroller", "instrument_type": "Department policy and supplemental procedures", "topic": "Funding", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "Departmental non-Economy Act deobligation controls distinguish goods, severable services, nonseverable services and excess/expired funds. Moving funds to another agency does not extend their period for new obligations.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "For goods, assess the original timely request, bona fide need and any justified delivery/production/manufacturing lead time or unforeseen delay. For severable services under the stated10USC3133 route, ensure performance begins while the customer funds are available and lasts no more than one year. Fund nonseverable contracts fully with appropriations available for new obligations at award; return identified excess. Reconcile balances, have the performer return the required excess/expired funds and have the requester deobligate them.", "exceptions": "Later delivery of goods is not categorically forbidden: the stated exception requires a genuine timely need and nonexcessive delay, and does not cover standard COTS readily available elsewhere. Prior-year annual funds cannot support severable performance entirely in the following year; the stated route cannot extend annual-fund performance beyond September30 of the following year. Analyze other specific statutory authorities separately. Section18.6.4 measures unperformed/uncontracted funds against the customer appropriation’s availability.", "approval_authority": "Requesting and performing agencies with FM/accounting officials; counsel and the CO assess the specific need, severability, timing and statutory route.", "locator": "Complete Supplemental18.6.1–18.6.4, PDF pp.74–75 (printed11-92–11-93)", "source_ids": [ "RSRC-0203", "RSRC-0125" ], "limitations": "These are the selected departmental non-Economy Act controls, not a conclusion that every non-Economy statute has the Economy Act’s statutory deobligation rule. Actual contracts, obligations and exceptions have not been evaluated.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0139" }, { "type": "related requirement", "target": "RULE-0140" }, { "type": "related requirement", "target": "RULE-0263" }, { "type": "related requirement", "target": "RULE-0265" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected September2026 non-Economy Act departmental policy and supplemental procedures" }, { "id": "RULE-0265", "title": "Retain customer oversight and fiscally close non-Economy Act orders", "citation": "FMR Volume11 Supplemental §18.7 and repeated §18.3 “Non-Economy Act Order Close-Out” (SEP2026)", "issuer": "DoW Comptroller", "instrument_type": "Department policy and supplemental procedures", "topic": "Contract administration", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD interagency acquisition; overseas and appropriation-specific limits require separate assessment", "summary": "For non-Economy Act orders above the applicable SAT, the requesting official must establish and execute quality surveillance plans covering administration, receiving reports, invoice review/reconciliation and documented acceptance. Completed orders require fiscal closeout.", "applies_when": "Considering or administering ABAD sensors, effectors or C2 through another agency or Component; determine the actual authority, acquisition route, amount, fiscal year, scope and incorporated terms.", "required_action": "Assign and execute the customer’s surveillance and receipt/invoice responsibilities. Monitor fund status, confirm open balances, perform the referenced dormant-account review and AFR attestation, and coordinate returns and accounting deobligations. For every order, determine completion, reconcile funds, identify outstanding invoices and excess/expired balances, and fiscally close completed orders.", "exceptions": "The above-SAT surveillance-plan trigger does not limit the separate all-orders completion and closeout review. Closing the interagency fiscal order does not by itself satisfy the underlying procurement contract’s separate closeout duties or authorize final payment without required acceptance.", "approval_authority": "Requesting official retains the specified oversight and fiscal-closeout duties; performing agency and accounting office coordinate reports, funds returns and deobligations.", "locator": "Supplemental18.7.1–18.7.4, PDF pp.75–76; repeated18.3 heading “Non-Economy Act Order Close-Out,” p.76 (printed11-94)", "source_ids": [ "RSRC-0203" ], "limitations": "Duplicate numbering is preserved with heading/page locators in GAP-029. Full Volume3 dormant-account and Volume6 reconciliation procedures are not established by this selected review.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0263" }, { "type": "related requirement", "target": "RULE-0264" }, { "type": "related requirement", "target": "RULE-0256" } ], "date_note": "September2026 identifies the FMR edition without an invented day. Signed2026-O0027 is dated December18,2025 and effective February1,2026 until rescinded/incorporated. GSA certification is expressly FY2027; historical delegation dates are not a new waiver effective date. Existing contract changes require their own authority and terms.", "version_state": "Selected September2026 non-Economy Act departmental policy and supplemental procedures" }, { "id": "RULE-0266", "title": "Compare added work with the original competition and whole contract", "citation": "Rice Services, B-424208 et al. (APR9,2026), pp.6–9; Red Cat, B-424397/.2 (JUL10,2026), pp.4–9", "issuer": "GAO", "instrument_type": "GAO legal interpretation", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; actual vehicle, agency and overseas requirements remain action dependent", "summary": "GAO examines whether an order or modification is materially different from the underlying contract: original procurement circumstances, changes in work, performance period and cost, solicitation notice, and what offerors reasonably could have anticipated.", "applies_when": "Considering ABAD sensor, effector or C2 orders, scope changes or option extensions; identify the original competition, actual contract/order terms and governing current rules.", "required_action": "Prepare a provision-based comparison of the proposed work and original solicitation/contract. Read the instrument as a whole, including customer, mission, service/product, duration and value limits. Address each material change and the competitive field, then identify the applicable competition route. Keep funding-scope analysis separately documented.", "exceptions": "A broad contract title, available ceiling or small percentage change alone does not resolve scope. Specific LOGCAP/SOETLSP outcomes do not authorize orders on another vehicle; the XaaS pilot has its own distinct statutory conditions.", "approval_authority": "CO and responsible policy/counsel officials assess the actual action. GAO interpretations do not grant local authority, approve a vehicle or authorize drone/counter-drone operation.", "locator": "Rice pp.6–9; Red Cat Scope Challenge pp.4–9", "source_ids": [ "RSRC-0204", "RSRC-0208" ], "limitations": "No actual ABAD contract or ordering delegation assessed. GAO conclusions are fact-specific; targeted searches are not an exhaustive citator. Fiscal, security, source restrictions and operating permissions remain separate. GAP-013 retains wider case-law coverage; RULE-0114/GAP-015 retain option-security implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-04-09", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0036" }, { "type": "related requirement", "target": "RULE-0086" }, { "type": "related requirement", "target": "RULE-0134" }, { "type": "related requirement", "target": "RULE-0203" }, { "type": "related requirement", "target": "RULE-0267" }, { "type": "related requirement", "target": "RULE-0268" } ], "date_note": "GAO dates identify opinions, not new department-wide policy effective dates. The December18,2025 signed2026-O0027 adopts the linked model text effectiveFebruary1,2026 until rescinded/incorporated. The dynamic model page supplies no separate provision-level date. Existing contract terms are not automatically amended.", "version_state": "Case-specific released GAO interpretation with selected current adopted option provisions separately identified" }, { "id": "RULE-0267", "title": "Apply the drone-order precedent to actual vehicle terms", "citation": "Red Cat Holdings, B-424397/B-424397.2 (JUL10,2026)", "issuer": "GAO", "instrument_type": "GAO legal interpretation", "topic": "Modifications", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; actual vehicle, agency and overseas requirements remain action dependent", "summary": "GAO found the challenged drone order within SOETLSP scope after examining the contract’s broad customer/mission coverage, expressly flexible delivery terms and order-value structure. The protester did not dispute that drone products could fit its categories.", "applies_when": "Considering ABAD sensor, effector or C2 orders, scope changes or option extensions; identify the original competition, actual contract/order terms and governing current rules.", "required_action": "For a contemplated drone or sensor order, identify the actual product/service coverage, authorized ordering customer, delivery flexibility and value limits. Explain the original competition’s notice of those possibilities. Assess required sourcing, funds and operating permissions independently.", "exceptions": "The opinion creates no percentage safe harbor and does not establish that every logistics or IT vehicle covers drones. Its dismissed brand-name and vehicle-selection allegations do not supply blanket approval of a restriction or permission to disregard a mandatory source/program.", "approval_authority": "CO and responsible policy/counsel officials assess the actual action. GAO interpretations do not grant local authority, approve a vehicle or authorize drone/counter-drone operation.", "locator": "Scope Challenge pp.4–9; Interested Party Status pp.9–12 and footnotes9–10", "source_ids": [ "RSRC-0208" ], "limitations": "No actual ABAD contract or ordering delegation assessed. GAO conclusions are fact-specific; targeted searches are not an exhaustive citator. Fiscal, security, source restrictions and operating permissions remain separate. GAP-013 retains wider case-law coverage; RULE-0114/GAP-015 retain option-security implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-10", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0266" }, { "type": "related requirement", "target": "RULE-0268" }, { "type": "related requirement", "target": "RULE-0260" } ], "date_note": "GAO dates identify opinions, not new department-wide policy effective dates. The December18,2025 signed2026-O0027 adopts the linked model text effectiveFebruary1,2026 until rescinded/incorporated. The dynamic model page supplies no separate provision-level date. Existing contract terms are not automatically amended.", "version_state": "Case-specific released GAO interpretation with selected current adopted option provisions separately identified" }, { "id": "RULE-0268", "title": "Distinguish IDIQ scope from order scope and protest standing", "citation": "Network Designs, B-423525/.2 (AUG8,2025); Rice Services, B-424208 et al.; Red Cat, B-424397/.2", "issuer": "GAO", "instrument_type": "GAO legal interpretation", "topic": "Contract vehicle", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; actual vehicle, agency and overseas requirements remain action dependent", "summary": "Underlying IDIQ scope and an individual order’s scope raise different competition questions. Network Designs dismissed a nonholder’s order-modification challenge; Rice distinguishes an underlying-contract scope challenge; Red Cat dismissed a nonholder supplier’s brand-name challenge.", "applies_when": "Considering ABAD sensor, effector or C2 orders, scope changes or option extensions; identify the original competition, actual contract/order terms and governing current rules.", "required_action": "Identify whether added work exceeds the underlying competed contract, changes an existing order within that vehicle, or restricts competition for a new order. Check the applicable ordering and fair-opportunity duties independently of whether a particular protester has standing. Record whether a cited decision reached the merits or only a procedural threshold.", "exceptions": "Dismissal does not approve the action on its merits. Supplier/incumbent status on a different vehicle is not equivalent to holding the relevant IDIQ. Network footnote4 did not decide whether the modification increment or total order value controls jurisdiction; no threshold rule is supplied here.", "approval_authority": "CO and responsible policy/counsel officials assess the actual action. GAO interpretations do not grant local authority, approve a vehicle or authorize drone/counter-drone operation.", "locator": "Network pp.3–5 and fn4; Rice pp.4–6 and fn4; Red Cat pp.9–12", "source_ids": [ "RSRC-0205", "RSRC-0204", "RSRC-0208" ], "limitations": "No actual ABAD contract or ordering delegation assessed. GAO conclusions are fact-specific; targeted searches are not an exhaustive citator. Fiscal, security, source restrictions and operating permissions remain separate. GAP-013 retains wider case-law coverage; RULE-0114/GAP-015 retain option-security implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-08-08", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0266" }, { "type": "related requirement", "target": "RULE-0267" }, { "type": "related requirement", "target": "RULE-0020" } ], "date_note": "GAO dates identify opinions, not new department-wide policy effective dates. The December18,2025 signed2026-O0027 adopts the linked model text effectiveFebruary1,2026 until rescinded/incorporated. The dynamic model page supplies no separate provision-level date. Existing contract terms are not automatically amended.", "version_state": "Case-specific released GAO interpretation with selected current adopted option provisions separately identified" }, { "id": "RULE-0269", "title": "Evaluate extension options before relying on them for continuity", "citation": "Major Contracting Services, B-401472 (SEP14,2009); Army—Reconsideration, B-401472.2 (DEC7,2009); adopted RFO17.202/17.204-1(b)(3)(vi)", "issuer": "GAO; FAR Council / DoD DPCAP", "instrument_type": "GAO legal interpretation and adopted regulation", "topic": "Options and interagency", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; actual vehicle, agency and overseas requirements remain action dependent", "summary": "Initial option evaluation and a specified or determinable exercise price are separate requirements. GAO sustained an unevaluated service extension and denied reconsideration; including52.217-8 and evaluating base/option-year rates did not itself satisfy evaluation of the extension.", "applies_when": "Considering ABAD sensor, effector or C2 orders, scope changes or option extensions; identify the original competition, actual contract/order terms and governing current rules.", "required_action": "Define and evaluate the intended option quantities/periods at competition, then verify the evaluation record before exercise. If an extension was unevaluated, establish a lawful competition/justification route under the applicable rules with counsel. Plan the follow-on early; the cases rejected the sole-source justification where inadequate planning and alternative capable firms undermined it.", "exceptions": "Current17.202(b) permits a rare exception for evaluation of option quantities with written approval at least one level above the CO and filing; it does not itself waive competition at exercise. Historical17.207(f), thresholds and the case’s notice period are not current universal requirements. Urgency does not automatically justify an incumbent-only extension.", "approval_authority": "CO and responsible policy/counsel officials assess the actual action. GAO interpretations do not grant local authority, approve a vehicle or authorize drone/counter-drone operation.", "locator": "Major, Discussion and fn3; Army reconsideration pp.3–6, fn3–6; current17.202 and17.204-1(b)(3)(vi); signedO0027 pp.1–2", "source_ids": [ "RSRC-0206", "RSRC-0207", "RSRC-0200", "RSRC-0109" ], "limitations": "No actual ABAD contract or ordering delegation assessed. GAO conclusions are fact-specific; targeted searches are not an exhaustive citator. Fiscal, security, source restrictions and operating permissions remain separate. GAP-013 retains wider case-law coverage; RULE-0114/GAP-015 retain option-security implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2009-09-14", "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0114" }, { "type": "related requirement", "target": "RULE-0270" }, { "type": "related requirement", "target": "RULE-0258" } ], "date_note": "GAO dates identify opinions, not new department-wide policy effective dates. The December18,2025 signed2026-O0027 adopts the linked model text effectiveFebruary1,2026 until rescinded/incorporated. The dynamic model page supplies no separate provision-level date. Existing contract terms are not automatically amended.", "version_state": "Case-specific released GAO interpretation with selected current adopted option provisions separately identified" }, { "id": "RULE-0270", "title": "Check option limits, notice, funds and current market conditions", "citation": "Adopted RFO17.200,17.201-2 and17.204-1;2026-O0027", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation", "topic": "Options and interagency", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; actual vehicle, agency and overseas requirements remain action dependent", "summary": "Option exercise requires the prescribed notice and available funds, an existing need, required synopsis, no active SAM exclusion, acceptable performance, fair/reasonable pricing under current market conditions, Government interest and the competition prerequisites.", "applies_when": "Considering ABAD sensor, effector or C2 orders, scope changes or option extensions; identify the original competition, actual contract/order terms and governing current rules.", "required_action": "Use the actual contract’s quantity/service/duration and exercise-period limits. Provide the required written intention notice on time and separately comply with the option’s exercise mechanism; intention notice alone is not treated as binding exercise. Assess any requested economic price adjustment first. Document need, funds, synopsis/exemption, exclusion/performance checks and current price/value analysis; add the applicable defense option-security checks.", "exceptions": "Subpart17.2 excludes the listed real-property construction/repair, architect-engineer and R&D service contracts except as agency regulations provide; agencies may use their own options rules. Statutory duration limits still apply. An established contract price alone does not replace the current-market review.", "approval_authority": "CO and responsible policy/counsel officials assess the actual action. GAO interpretations do not grant local authority, approve a vehicle or authorize drone/counter-drone operation.", "locator": "Complete17.200,17.201-2 and17.204-1(a)–(b);17.203(f)–(g) context; signedO0027 pp.1–2", "source_ids": [ "RSRC-0200", "RSRC-0109" ], "limitations": "No actual ABAD contract or ordering delegation assessed. GAO conclusions are fact-specific; targeted searches are not an exhaustive citator. Fiscal, security, source restrictions and operating permissions remain separate. GAP-013 retains wider case-law coverage; RULE-0114/GAP-015 retain option-security implementation limits.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0114" }, { "type": "related requirement", "target": "RULE-0269" }, { "type": "related requirement", "target": "RULE-0254" } ], "date_note": "GAO dates identify opinions, not new department-wide policy effective dates. The December18,2025 signed2026-O0027 adopts the linked model text effectiveFebruary1,2026 until rescinded/incorporated. The dynamic model page supplies no separate provision-level date. Existing contract terms are not automatically amended.", "version_state": "Selected adopted RFO17.2 as displayed October4,2026" }, { "id": "RULE-0271", "title": "Start contract closeout from physical-completion evidence and observe holds", "citation": "Adopted RFO 4.308-2 and Table 4-2; 2026-O0043", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "Initiate closeout after evidence of physical completion, with an initial funds-status review. The table sets target timing; it does not permit closing a file in litigation or appeal, or before all termination actions finish.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Record receipt of physical-completion evidence and the applicable agency criteria. For simplified acquisitions, close when receipt of property and final payment are evidenced unless agency regulations prescribe otherwise. For other firm-fixed-price contracts, the target is six months after the date the CO receives physical-completion evidence; contracts needing indirect-cost settlement use 36 months of that month, and other contracts use 20 months of that month. Apply 4.308-1 to the non-simplified categories and track unresolved actions.", "exceptions": "Table 4-2 uses should for these time standards. Litigation/appeal and incomplete termination actions are explicit prohibitions. An elapsed target or delivery alone does not prove all closeout conditions. The current physical-completion definition and local implementation require confirmation; old numbering is not silently substituted.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "4.308-2(a)–(d), Table 4-2; signed cover pp.1–2", "source_ids": [ "RSRC-0209", "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0273" }, { "type": "related requirement", "target": "RULE-0275" }, { "type": "related requirement", "target": "RULE-0277" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0272", "title": "Complete the administrative checklist before signing the completion statement", "citation": "Adopted RFO 4.308-1; 2026-O0043", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "Closeout verifies classified-material disposition, patent/royalty reports, value-engineering proposals, plant/property clearance, cost and price actions, subcontracts, indirect rates, termination, audit, closing statement, final invoice submission and excess-funds review.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Assign owners for all fifteen 4.308-1(a) items and document their disposition. Reconcile property, data, patent and payment obligations against the actual contract. Once verified, prepare the completion statement with the required office/contract/order identifiers, excess funds, applicable voucher or invoice information, completion assertion and CO signature/date; retain the signed original and furnish the separate administration office its copy.", "exceptions": "A missing final patent report has a specific notice, Government-rights and patent-counsel/agency-procedure route; it is not an IP waiver. The stated 60-day patent clearance goal does not eliminate those steps. Final invoice submission is not itself proof of final payment. Apply the specific GPC documentation rule where appropriate.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "4.308-1(a)(1)–(15), including (a)(2); (b)(1)–(12) and (c)", "source_ids": [ "RSRC-0209", "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0273" }, { "type": "related requirement", "target": "RULE-0274" }, { "type": "related requirement", "target": "RULE-0276" }, { "type": "related requirement", "target": "RULE-0227" }, { "type": "related requirement", "target": "RULE-0244" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0273", "title": "Coordinate DoD completion records, late-closeout notices and GPC evidence", "citation": "2026-O0043; DFARS/PGI 204.308-170, 204.308-171, 204.308-2 and 204.308-270", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "DoD assigns closeout-date and completion-record responsibilities between procuring and administering offices. An ACO missing the applicable closeout period must notify the PCO within 45 days, with reasons and a new target; a missed revised target requires another notice.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Use DD 1594/1597 or authorized equivalents and the prescribed EDA/financial-system distribution. Record the PCO closeout date and major later action as directed. The PGI completion-statement route permits block-5 deobligation on distribution without a modification; provide the comptroller copy for ledger reconciliation. If GPC is the sole payment method, a final invoice is not required for closeout, but the completion statement must include the final acceptance date.", "exceptions": "The specific statement/deobligation procedure is not general permission to omit funding controls. A checklist applies above the applicable SAT; current data formats and local procedures require confirmation. The GPC exception omits voucher/final-invoice information, not acceptance evidence or other applicable closeout duties. Final-payment documentation and ordinary separated-office completion rules remain distinct.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "DFARS 204.308-170(a), 204.308-171 and 204.308-2/-270; PGI same sections, PDF pp.97–100; particularly PGI 204.308-270(b)–(c)", "source_ids": [ "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0160" }, { "type": "related requirement", "target": "RULE-0255" }, { "type": "related requirement", "target": "RULE-0265" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0274", "title": "Screen every condition before using automated closeout", "citation": "PGI 204.308-170(a)(6), adopted by 2026-O0043", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "The selected DoD automated route is limited to contracts with only firm-fixed-price line items, a value of $500,000 or less, and none of eleven listed clauses. Components may impose further limits.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Check line types, contract value and absence of 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. Check Component configuration and applicable completion conditions. BOAs, BPAs and IDIQ contracts can automatically close after all orders are closed and the ordering period has expired.", "exceptions": "The stated $500,000 limit is not the simplified acquisition threshold and is unrelated to the $2 million quick-closeout test or $1,000 residual waiver. The agreement/IDIQ provision does not allow closure while orders remain open. Presence of a listed clause defeats this stated automated route, not necessarily ordinary closeout.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "PGI 204.308-170(a)(6)(i)–(v), PDF pp.97–98", "source_ids": [ "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0275" }, { "type": "related requirement", "target": "RULE-0276" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0275", "title": "Use the DoD quick-closeout threshold and preserve the DCMA authority limit", "citation": "Adopted RFO 42.507; DFARS 242.507; 2026-O0050", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "Quick closeout can settle allocable costs before final indirect rates when the stated conditions are met. DoD replaces the model cost-size test with total unsettled direct and indirect costs of $2 million or less, regardless of contract or order value. A separate no-dollar-or-percentage-limit provision applies expressly to DCMA ACOs.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Confirm physical completion, assess systems and audit concerns plus other relevant risk factors, and agree a reasonable estimate of allocable costs for the specific contract/task/delivery order. Use the DoD replacement for 42.507(a)(2). For any reliance on the broader route, verify the official is a DCMA ACO and the actual administration assignment. Record that the settlement is final for that contract and does not establish rates for other contracts.", "exceptions": "The model lesser-of-$1-million/10-percent threshold is displaced by the selected DoD text. The DCMA-specific authorization cannot be assumed from USAFE/AFICC assignment or funding. Unrecovered or over-recovered costs cannot be shifted to other contracts through this settlement, and its rates are not binding precedent elsewhere. Read the actual incorporated payment clause and remaining conditions.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "Complete model 42.507(a)–(c); signed cover pp.1–2; complete DFARS 242.507, PDF p.7 (printed p.5 of 32)", "source_ids": [ "RSRC-0211", "RSRC-0107" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-03-06", "effective_date": "2026-03-16", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0274" }, { "type": "related requirement", "target": "RULE-0276" }, { "type": "related requirement", "target": "RULE-0116" } ], "date_note": "Signed 2026-O0050 dated March 6, 2026 adopts the linked model and attached defense provisions effective March 16, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0276", "title": "Apply the residual-balance clause only after closeout actions and mutual agreement", "citation": "DFARS 204.308-170(d), 204.308-70 and 252.204-7022; 2026-O0043", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "The prescribed clause allows both parties to waive payment of an agreed residual amount of $1,000 or less after all applicable FAR 4.308 closeout requirements are satisfied. It includes a defined limit on what counts as residual money.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Confirm 252.204-7022 is applicable in the actual contract, finish the required closeout actions, determine and mutually agree the residual amount, and apply only lawful offsets. Preserve the agreement and closeout record. The prescription includes Part 12 acquisitions when the CO intends to use this expedited residual-balance route.", "exceptions": "Residual amounts exclude taxation and amounts involving a violation of law or regulation. This is not unilateral authority to forgive any small debt, an unsettled-cost quick-closeout threshold, or permission to add the clause retroactively without an authorized contract action. The aged/unreconcilable statutory route is separately unresolved in GAP-030.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "DFARS 204.308-170(d) and 204.308-70, PDF p.11; complete 252.204-7022(a)–(c), PDF p.25", "source_ids": [ "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0274" }, { "type": "related requirement", "target": "RULE-0275" }, { "type": "related requirement", "target": "RULE-0277" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0277", "title": "Retain Government contract records beyond closeout when required", "citation": "Adopted RFO 4.309 and Table 4-3; DFARS 204.309-70 and 204.705-70; 2026-O0043", "issuer": "FAR Council / DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Administration", "equipment": [ "All" ], "stages": [ "Contract administration" ], "jurisdiction": "U.S. federal and DoD contracting; applicable agency procedures and actual contract terms remain controlling", "summary": "Ordinary Government contract and related records are retained six years after final payment. Investigation, litigation, protest or enforcement records may require longer retention, and mixed program files and other listed record classes have their own rules.", "applies_when": "Closing an ABAD sensor, effector, C2, software or support contract/order, settling costs or retaining its final records. Identify the governing edition and actual contractual conditions.", "required_action": "Identify the applicable Table 4-3 class and agency/NARA schedule before disposal. Retain held material until final clearance or settlement, or the related retention period, whichever is later. Preserve inseparable program records under the approved program schedule. Apply EDA restrictions: do not place classified material, sensitive PII/Privacy Act/HIPAA information or impractical attachments there; documents beyond contracts, modifications and orders are optional in EDA under the selected provision.", "exceptions": "Six years after final payment is not six years after delivery or administrative closeout and is not blanket authority for deletion. Contractor record-retention duties are a separate subject. Current DAF schedules, holds, access controls and authorized repositories require action-specific confirmation; EDA availability does not make the contract file public. Selected 204.705-70 also specifies initial 12-month office retention and subsequent staging, with a six-year pricing-review period or nine years if final payment cannot be determined. Resolve its old GRS/numbering references against current schedules before disposal.", "approval_authority": "CO, assigned ACO and responsible finance/records officials within their actual written authority. DCMA-specific authority is not inferred for an AFICC CO; policy/counsel must resolve any exceptional route.", "locator": "Complete 4.309(a)–(c), Table 4-3; DFARS 204.309-70 and 204.705-70, PDF pp.11–12", "source_ids": [ "RSRC-0209", "RSRC-0210" ], "limitations": "No actual contract, payment, delegation or local automated-closeout configuration assessed. GAP-030 preserves current physical-completion criteria, exceptional statutory closeout, inconsistent references, local procedures and records-schedule questions. Acquisition closeout does not supply drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-02-03", "effective_date": "2026-02-17", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0271" }, { "type": "related requirement", "target": "RULE-0272" }, { "type": "related requirement", "target": "RULE-0273" } ], "date_note": "Signed 2026-O0043 dated February 3, 2026 adopts the linked model and attached defense provisions effective February 17, 2026 until rescinded/incorporated. Dates identify the adopting deviation, not an independent publication date for the dynamic model text. No automatic amendment of existing contract terms is inferred.", "version_state": "Selected adopted RFO provisions and signed defense implementation as reviewed October 4, 2026" }, { "id": "RULE-0278", "title": "Preserve contractor export duties and subcontract flowdown", "citation": "DFARS 225.7901-1 through -4; complete 252.225-7048; 2026-O0041 Revision 1", "issuer": "DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "The export-control clause is prescribed for all solicitations and contracts. It preserves contractor responsibility for applicable export controls independently of the contract and requires its substance, including the flowdown paragraph, in all subcontracts.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "Include the prescribed 252.225-7048 clause for the applicable new action and check the governing terms of existing contracts/orders and modifications. Plan for export-controlled hardware, software, technology, technical data and services. Direct contractor compliance questions to State or Commerce as appropriate, including applicable ITAR registration. Verify the all-subcontract flowdown and maintain action-specific export documentation before performance.", "exceptions": "The clause does not add, alter, supersede or waive applicable export law. Registration applicability and exceptions require separate analysis; not every contractor is automatically required to register. No overseas order or option creates an export exception, and the current prescription does not itself retrofit an older contract.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "DFARS 225.7901-1 through -4, PDF pp.79–80; 252.225-7048(a)–(e), pp.212–213", "source_ids": [ "RSRC-0106" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-01", "effective_date": "2026-07-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0279" }, { "type": "related requirement", "target": "RULE-0280" }, { "type": "related requirement", "target": "RULE-0281" }, { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0074" }, { "type": "related requirement", "target": "RULE-0075" } ], "date_note": "Signed 2026-O0041 Revision 1 is dated July 1, 2026 and effective immediately until rescinded/incorporated. Clause 7048 retains its June 2013 date. New adopted prescriptions do not silently amend existing contract terms.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0279", "title": "Keep export-compliance interpretation with State and Commerce", "citation": "PGI 225.7901-2(1)–(5); 2026-O0041 Revision 1", "issuer": "DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "DoD identifies DTSA as the focal point for Government export-control issues in acquisition. COs should refer contractor questions about ITAR registration or EAR/ITAR compliance to the relevant agency and clause, rather than answer how to comply.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "Identify the export issue in acquisition planning, distinguish a Government policy question from a contractor compliance question, and use DTSA or the relevant State/Commerce channel. For research contracts, check whether controlled items or data will be used or generated; a fundamental-research description alone does not remove export controls.", "exceptions": "The PGI describes fundamental research as generally not involving controlled items but expressly preserves statutory controls when controlled items are used or generated. Its older statute and policy references are not independently certified current. This referral instruction is not permission to omit compliance requirements or make an unsupported exemption determination.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "PGI 225.7901-2(1), (2)(i)(D)–(E), (2)(ii)(C)–(D), (3)–(5), PDF pp.260–263", "source_ids": [ "RSRC-0106" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-01", "effective_date": "2026-07-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0278" }, { "type": "related requirement", "target": "RULE-0074" }, { "type": "related requirement", "target": "RULE-0075" } ], "date_note": "Signed 2026-O0041 Revision 1 is dated July 1, 2026 and effective immediately until rescinded/incorporated. Clause 7048 retains its June 2013 date. New adopted prescriptions do not silently amend existing contract terms.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0280", "title": "Document treaty eligibility before using an Australia or UK route", "citation": "DFARS 225.7902-1 through -5; PGI 225.7902, 225.7902-2 and -4; 2026-O0041 Revision 1", "issuer": "DoD DPCAP", "instrument_type": "Adopted regulation and implementing procedures", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "The selected defense procedures require the PM to identify in writing which articles and treaty activities qualify before solicitation and before award. The CO uses that information for the treaty provision/clause and qualifying line items; nationality or procurement-source eligibility alone is insufficient.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "Obtain the PM determination identifying the applicable treaty paragraph, qualifying defense articles and excluded-technology conditions. Check approved-community participation/facilities, authorized end use and technology exclusions through current authoritative routes. Apply the 252.225-7046/-7047 prescriptions and identify qualifying CLINs in the clause. Preserve applicable marking and recordkeeping requirements and any existing license until transition is approved.", "exceptions": "This record establishes PM/CO documentation gates, not eligibility of a supplier, article or transfer. Full current 126.16/126.17/126.7, approved-community and excluded-technology lists, and complete 7046/7047 terms remain to be reviewed. An existing license continues to govern until its transition is approved. Other domestic/import obligations remain; no automatic treaty or AUKUS exemption is asserted.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "DFARS 225.7902-1 through -5, PDF pp.80–82, especially -4(a)–(b) and -5; PGI 225.7902 and 225.7902-2/-4, pp.263–265", "source_ids": [ "RSRC-0106" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-07-01", "effective_date": "2026-07-01", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0278" }, { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0284" }, { "type": "related requirement", "target": "RULE-0025" } ], "date_note": "Signed 2026-O0041 Revision 1 is dated July 1, 2026 and effective immediately until rescinded/incorporated. Clause 7048 retains its June 2013 date. New adopted prescriptions do not silently amend existing contract terms.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0281", "title": "Establish the conditions for a transfer made by the Government", "citation": "22 CFR 126.4(a)(1)–(7)", "issuer": "U.S. Department of State", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "The Government-transfer provision contains distinct official-use, international-agreement, assistance/sales and security-cooperation grounds. For contracted official-use activities, the contract relationship and scope must be accompanied by one of the specified control or approval conditions.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "For agency-made transfers relying on (a)(1)(ii), identify the contracted activity and its scope, then document a Government-controlled facility, an empowered and responsible Government employee preventing diversion and limiting use to that scope, or the specified DDTC Deputy Assistant Secretary authorization requested by an agency. Apply the technical-data restriction for persons/entities of 126.1 countries. For another (a) ground, establish its specific legal/program and assurance requirements.", "exceptions": "Paragraph (a) is not available when the agency is merely a transmittal agent for a private firm for convenience or security. It addresses ITAR compliance only and leaves other approval, statutory, Government-process and embargo requirements in force. Contractor-made transfers must be examined under (b), rather than inferred from the existence of a contract. Paragraph (a)(7) separately qualifies the end-use/user approval rule.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "Complete 126.4(a), especially (a)(1)(ii)(A)–(D), (a)(4)(ii), (a)(5)–(7); 84 FR 16401", "source_ids": [ "RSRC-0212" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2019-04-19", "effective_date": "2019-04-19", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0283" }, { "type": "related requirement", "target": "RULE-0284" }, { "type": "related requirement", "target": "RULE-0075" } ], "date_note": "Section 126.4 final rule published and effective April 19, 2019; corroborated by 84 FR 16398–16402. eCFR title-wide October 1, 2026 currency is not a new section effective date.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0282", "title": "Distinguish an agency request from written direction to another recipient", "citation": "22 CFR 126.4(b)(1)–(2), read with (a)(1)–(4) and (d)", "issuer": "U.S. Department of State", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "A person acting for an agency has two stated routes: transfer to a Government department or agency at its request; or transfer to another entity at an agency’s written direction or under an international agreement/arrangement for an activity authorized in (a)(1)–(4).", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "Identify who transfers, who receives and which paragraph applies. Retain evidence of the agency request for (b)(1). For a non-Government recipient under (b)(2), establish the written agency direction or qualifying international agreement/arrangement and the authorized underlying activity. Confirm the responsible official’s authority and other applicable restrictions before overseas delivery, support or technical-data access.", "exceptions": "The text expressly requires written direction for that (b)(2) route; (b)(1) says at the agency’s request and is not silently rewritten to add the same express form requirement. A purchase order, USAFE/EUCOM funding, contracting warrant or shipment for a defense purpose alone does not establish all conditions. No local delegation or particular document is approved by this library.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "126.4(b)(1)–(2), (a)(1)–(4) and (d); 84 FR 16401–16402", "source_ids": [ "RSRC-0212" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2019-04-19", "effective_date": "2019-04-19", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0278" }, { "type": "related requirement", "target": "RULE-0281" }, { "type": "related requirement", "target": "RULE-0283" }, { "type": "related requirement", "target": "RULE-0284" } ], "date_note": "Section 126.4 final rule published and effective April 19, 2019; corroborated by 84 FR 16398–16402. eCFR title-wide October 1, 2026 currency is not a new section effective date.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0283", "title": "Track export clearance, returns and changes of end use or user", "citation": "22 CFR 126.4(c), (e), (f) and (a)(7)", "issuer": "U.S. Department of State", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "Use of the Government-transfer exemption leaves continuing controls. The return provision requires an eligible export and transfer history, export clearance has an EEI requirement with specified transport exceptions, and changes outside authorized end uses/users require DDTC approval.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "For a return to the United States under (c), confirm export under this section and no subsequent reexport/retransfer except under this section, with return to the agency or original exporter. Under (e), arrange EEI at the time of export unless shipment is by U.S. diplomatic pouch or U.S. Government aircraft, vehicle or vessel; follow CBP/DoD instructions if electronic submission is unavailable. Before reassignment, loan, repair support or disposition, evaluate whether a changed end use/user falls outside the section.", "exceptions": "Paragraph (a)(7) removes the (f) authorization requirement for articles/services exported under (a)(1) or (3) while they remain subject to those terms. The return route is not a blanket repair-import exemption for every defense item, and property transfer or contract modification does not itself approve a changed recipient. Other customs/import and foreign-country requirements remain separate.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "Complete 126.4(c), (e), (f) and (a)(7); 84 FR 16401–16402", "source_ids": [ "RSRC-0212" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2019-04-19", "effective_date": "2019-04-19", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0281" }, { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0284" }, { "type": "related requirement", "target": "RULE-0179" }, { "type": "related requirement", "target": "RULE-0239" } ], "date_note": "Section 126.4 final rule published and effective April 19, 2019; corroborated by 84 FR 16398–16402. eCFR title-wide October 1, 2026 currency is not a new section effective date.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0284", "title": "Screen restricted recipients, proposals and conveyances with current exceptions", "citation": "22 CFR 126.1(a)–(e); September 23, 2026 correction, 91 FR 60299", "issuer": "U.S. Department of State", "instrument_type": "Regulation", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "U.S. export controls; foreign-country import, customs, operating and other approvals remain separate", "summary": "ITAR restrictions reach specified destinations/persons, certain conveyances and qualifying proposals as well as completed transfers. Current paragraph (a) preserves specific exceptions, including identified Government-transfer grounds restored by the September 23 correction; it is neither a blanket prohibition on all Government transfers nor blanket permission.", "applies_when": "Planning or administering ABAD hardware, software, technical data or support involving a potential export, reexport, retransfer, foreign recipient or return. First establish applicable jurisdiction and classification.", "required_action": "Screen the parties, destination, conveyance, proposed communication and transaction against the current applicable restrictions and country provisions. Identify the exact paragraph (a) exception if relevant, including its limited 126.4 cross-references, and reconcile 126.4(d) and other laws. Paragraph (e) requires prior DDTC license/written approval for the stated transactions or proposals and immediate notification by a person knowing or having reason to know of a proposed, final or actual transaction described there.", "exceptions": "Paragraph (a)(2) identifies 126.4(a)(1)/(3), (b)(1), and the specially limited Russia Government-space-cooperation (a)(2)/(b)(2) case; (a)(3) addresses a Government recipient. These are not a general clearance for restricted parties or a waiver of other sanctions. Paragraph (b) restricts specified ownership/operation/lease relationships of conveyances even for otherwise authorized articles. Full country-specific paragraphs, other exception bodies and sanctions regimes need separate review.", "approval_authority": "State DDTC for ITAR licensing/approval and Commerce BIS for EAR; responsible agency officials must establish the particular Government request/direction or other authority. A contracting warrant, USAFE/EUCOM funding or AFICC assignment is not evidence of an export delegation.", "locator": "126.1(a)–(e), including note to (e); operative amendment 4 of 91 FR 60299 (one page), effective September 23, 2026", "source_ids": [ "RSRC-0213", "RSRC-0214", "RSRC-0212" ], "limitations": "No actual transaction, classification, registration status or written delegation assessed. GAP-031 retains current treaty/registration implementation, EAR exceptions, cited DoD/DAF policy and statutory-reference questions. Export authorization does not establish customs relief, foreign-country permissions or drone/counter-drone operating authority.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0281" }, { "type": "related requirement", "target": "RULE-0282" }, { "type": "related requirement", "target": "RULE-0283" }, { "type": "related requirement", "target": "RULE-0075" } ], "date_note": "Paragraph 126.1(a) correction published and effective September 23, 2026; other paragraph dates are not established here. Compilation displays title 22 current through October 1, 2026; that is not a section-wide effective date.", "version_state": "Selected current adopted defense text, or current eCFR text reconciled with the identified operative Federal Register rule, as reviewed October 4, 2026" }, { "id": "RULE-0285", "title": "Separate SOFA subsistence purchasing, payment and tax questions", "citation": "NATO SOFA Article IX(2), (3), (7) and (8)", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "NATO SOFA parties and applicable territory; supplements and implementing arrangements may qualify the rule", "summary": "Article IX normally routes locally sourced subsistence goods through receiving-state military purchasing authorities. It separately addresses accommodation/services arrangements and prompt local-currency payment. Article IX itself supplies no tax or duty exemption.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Identify whether the requirement is subsistence, accommodation/services, or equipment governed by a supplementary route. Check receiving-state restrictions intended to protect its economy and applicable financial arrangements. Arrange prompt payment for the paragraph (2)–(6) goods, accommodation and services, and establish tax/customs relief under its separate legal basis.", "exceptions": "Do not extend the subsistence rule to every radar, camera, C2 or effector purchase. Paragraph (3) is subject to existing/future agreements and preserves receiving-state occupation/use law absent a contrary specific contract. Paragraph (7) is subject to financial arrangements; paragraph (8) does not cancel relief granted elsewhere.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Complete Article IX reviewed; operative IX(2), (3), (7)–(8)", "source_ids": [ "RSRC-0077" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0077" }, { "type": "related requirement", "target": "RULE-0286" }, { "type": "related requirement", "target": "RULE-0288" }, { "type": "related requirement", "target": "RULE-0149" }, { "type": "related requirement", "target": "RULE-0150" } ], "date_note": "Agreement signed June 19, 1951; Article XVIII and party-specific instruments govern entry into force. No action-specific entry date is inferred.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0286", "title": "Choose the German procurement route and its notification requirements", "citation": "Germany Supplementary Agreement Article 47(1)–(4)", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany; establish applicable sending-state and territorial arrangements", "summary": "Article 47 permits needed goods/services to be procured directly or, after prior agreement, through German authorities. Direct procurement may use normal procedures while respecting the specified German public-procurement principles and notification duty.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Record the applicable route before award or an order. For direct procurement, resolve how German principles reflected in competition, preferred-tenderer and public-contract price rules apply; notify German authorities of the subject, size, supplier and agreed price except for minor orders. Provide defined supply requirements on request under paragraph (2).", "exceptions": "The agreement does not define a U.S. dollar minor-order threshold here; do not substitute the micro-purchase or simplified-acquisition threshold. The notification exception is not a blanket waiver of procurement principles. Prior agreement is required for the German-authority route. Transport execution is separately governed by Article 57, not newly reviewed here.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Article 47(1)–(4), PDF pp.53–54", "source_ids": [ "RSRC-0215" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0285" }, { "type": "related requirement", "target": "RULE-0287" }, { "type": "related requirement", "target": "RULE-0288" }, { "type": "related requirement", "target": "RULE-0289" }, { "type": "related requirement", "target": "RULE-0111" }, { "type": "related requirement", "target": "RULE-0149" } ], "date_note": "Germany compilation covers the 1959 agreement as amended through March 18, 1993 and labels that revision effective March 29, 1998; that is not a newly established effective date for each selected article. Compilation upload/retrieval dates are not treaty dates.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0287", "title": "Preserve written consent and joint acceptance in German-authority purchases", "citation": "Germany Supplementary Agreement Article 47(5)(a)–(c), (g)", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany; establish applicable sending-state and territorial arrangements", "summary": "When procurement runs through German authorities, those authorities contract with the supplier under German public-contract rules. The force participates to protect its interests; award and modification require its written consent, and acceptance is joint unless otherwise agreed.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Supply detailed requirements, technical specifications and special delivery/payment conditions in time. Obtain the appropriate written consent before placing or modifying the German contract and identify the agreed acceptance participants. Carry these controls through changes, delivery, acceptance and administration using the applicable administrative agreement.", "exceptions": "German authorities retain exclusive competence in relation to the supplier. Sending-state consent does not authorize a U.S. official to direct that supplier outside the agreed route. Joint acceptance is qualified by contrary agreement; these paragraph (5) procedures are not automatically imposed on a direct U.S. contract.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Article 47(5)(a)–(c), (g), PDF pp.54–55", "source_ids": [ "RSRC-0215" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0286" }, { "type": "related requirement", "target": "RULE-0288" }, { "type": "related requirement", "target": "RULE-0289" }, { "type": "related requirement", "target": "RULE-0039" } ], "date_note": "Germany compilation covers the 1959 agreement as amended through March 18, 1993 and labels that revision effective March 29, 1998; that is not a newly established effective date for each selected article. Compilation upload/retrieval dates are not treaty dates.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0288", "title": "Fund and reconcile payments made through German authorities", "citation": "Germany Supplementary Agreement Article 47(5)(d)–(g) and Re Article 47", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany; establish applicable sending-state and territorial arrangements", "summary": "The sending state reimburses specified German procurement expenditures and must supply funds in time for due dates. The agreed procedure permits audit of German payment documents. Re Article 47 requires implementing agreements to include certification of available budgetary funds in the written consent.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Use the applicable administrative agreement to certify funds availability with consent, provide funds before payment falls due, and reconcile reimbursable expenditure and payment records. Preserve consent for out-of-court settlements and ex gratia payments, and identify emergency protective expenditure that cannot be charged to the contractor. Agree the audit procedure and retain records for financial reconciliation and closeout.", "exceptions": "These are treaty allocation and process rules, not a U.S. appropriation, obligation or payment delegation. Out-of-court settlement reimbursement and ex gratia payments carry consent conditions. The emergency-cost provision does not create a general emergency procurement exception. Do not infer a particular form or responsible officer from the treaty alone.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Article 47(5)(d)–(g) and complete Re Article 47, PDF pp.54–55", "source_ids": [ "RSRC-0215" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0285" }, { "type": "related requirement", "target": "RULE-0287" }, { "type": "related requirement", "target": "RULE-0289" }, { "type": "related requirement", "target": "RULE-0255" }, { "type": "related requirement", "target": "RULE-0264" } ], "date_note": "Germany compilation covers the 1959 agreement as amended through March 18, 1993 and labels that revision effective March 29, 1998; that is not a newly established effective date for each selected article. Compilation upload/retrieval dates are not treaty dates.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0289", "title": "Check bilateral dispute arrangements before selecting a German procurement forum", "citation": "Germany Supplementary Agreement Article 44(1)–(6)", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "Germany; establish applicable sending-state and territorial arrangements", "summary": "Article 44 establishes cooperation, consultation and specified cost responsibilities for procurement disputes. Its default for direct procurement is German courts or independent arbitration, but agreements between Germany and the sending state expressly take precedence over that default.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Obtain the applicable U.S.–German agreement and governing contract terms before identifying the forum or issuing dispute instructions. For the German-authority route, preserve timely notice, consultation at material stages, the stated agreement requirements for ending disputes and the applicable appeal/essential-interest process. Coordinate judgments, settlements and agreed costs with counsel and the responsible funding officials.", "exceptions": "Do not replace a U.S. contract disputes clause with the default in Article 44(6)(a) without resolving (6)(b). Paragraph (5) distinguishes judgment/settlement obligations, certain extra appeal costs allocated case by case, and non-awarded litigation costs requiring advance agreement. This review establishes no U.S.–German forum exception, settlement authority or litigation delegation.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Complete Article 44, PDF pp.49–51; especially (2), (4), (5) and (6)(a)–(b)", "source_ids": [ "RSRC-0215" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0286" }, { "type": "related requirement", "target": "RULE-0287" }, { "type": "related requirement", "target": "RULE-0288" }, { "type": "related requirement", "target": "RULE-0035" } ], "date_note": "Germany compilation covers the 1959 agreement as amended through March 18, 1993 and labels that revision effective March 29, 1998; that is not a newly established effective date for each selected article. Compilation upload/retrieval dates are not treaty dates.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0290", "title": "Keep locally hired civilian labor separate from SOFA civilian-component status", "citation": "NATO SOFA Articles I(1)(b) and IX(4)", "issuer": "Treaty parties", "instrument_type": "Treaty", "topic": "Overseas execution", "equipment": [ "All" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option", "Contract administration" ], "jurisdiction": "NATO SOFA parties and applicable territory; supplements and implementing arrangements may qualify the rule", "summary": "Article IX(4) addresses local civilian labor requirements and receiving-state employment conditions. Such local workers are not members of the force or civilian component for SOFA purposes. Article I separately defines the civilian component by employment and excluded categories.", "applies_when": "Planning or administering purchases, orders, changes, support or related disputes within the applicable treaty and implementing arrangements. Establish the parties, procurement route and personnel category first.", "required_action": "Identify whether support uses locally hired civilian labor, sending-state civilian personnel or contractor personnel. For the Article IX(4) category, account for receiving-state wages, supplementary payments and worker-protection conditions, including the stated employment-exchange assistance. Establish any contractor status under the actual applicable supplementary agreement and procedures.", "exceptions": "Do not treat every contracted technician as a civilian-component member or assume that all contractor employees are the local-labor category. Article I(1)(b) excludes specified nationality/residence categories. Full German Article 56 labor implementation and Article 73 contractor provisions are not reviewed by this record.", "approval_authority": "Competent sending-state and receiving-state authorities under the applicable agreement and actual written delegations; consult responsible contracting, legal and host-nation liaison officials. No local authority follows solely from organizational assignment or funding.", "locator": "Article I(1)(b); complete Article IX(4)", "source_ids": [ "RSRC-0077" ], "limitations": "Selected treaty provisions are a navigation aid. Current U.S.–German administrative/bilateral agreements, procurement-principle implementation, minor-order meaning, notification procedures, dispute forum and delegations remain GAP-032. No actual contract or personnel status is decided. Procurement authority is separate from tax relief, export/import, spectrum, flight, privacy and effector permissions.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0077" }, { "type": "related requirement", "target": "RULE-0079" }, { "type": "related requirement", "target": "RULE-0287" } ], "date_note": "Agreement signed June 19, 1951; Article XVIII and party-specific instruments govern entry into force. No action-specific entry date is inferred.", "version_state": "Selected official-hosted text reviewed October 4, 2026; current bilateral/administrative implementation and complete amendment assurance remain unresolved" }, { "id": "RULE-0291", "title": "Obtain written SMCA concurrence before conventional-ammunition procurement", "citation": "2026-O0020 Revision 1, DFARS 207.103-70(d)(1)-(2); PGI 207.103-70(d)", "issuer": "DoD", "instrument_type": "Class deviation", "topic": "Acquisition planning", "equipment": [ "Effector", "Drone" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option" ], "jurisdiction": "DoD acquisitions; applicability and item identity must be established", "summary": "For covered conventional-ammunition procurement, submit the acquisition plan to SMCA and do not proceed until SMCA provides written concurrence. The review addresses retention of national technology and industrial-base capabilities. This requirement does not itself assign contract execution to a particular Service.", "applies_when": "The contemplated procurement is conventional ammunition under the governing definition. This is a procurement-planning gate, not a blanket approval or operating authorization for all effectors.", "required_action": "Use the current plan and obtain written SMCA concurrence through the PGI route: Joint Program Executive Office Armaments and Ammunition, ATTN SFAE-AA, Picatinny Arsenal; published mailbox usarmy.pica.peo-ammo.list.zjs-section-806@army.mil. Preserve concurrence and its scope in the appropriate official file. For an order, option or modification acquiring ammunition, confirm that the contemplated items and scope are covered by the plan/concurrence; this review does not establish that every administrative modification needs a new concurrence. Non-concurrence is resolved by SMCA with the Army Office of the Executive Director for Conventional Ammunition.", "exceptions": "Paragraph (d) states no dollar threshold or Service-managed exception. Do not infer an exemption from USAFE/EUCOM funding, a contracting warrant, an existing vehicle, commerciality or the general planning thresholds in paragraph (a). Full instruction-defined applicability and implementing procedures remain to be established; no blanket re-concurrence interval is inferred.", "approval_authority": "SMCA for written concurrence; SMCA and Army Office of the Executive Director for Conventional Ammunition for non-concurrence resolution. Contract execution authority is a separate determination.", "locator": "Memorandum PDF pp.1-2; attachment 1 p.1 / PDF p.3; attachment 2 p.1 / PDF p.10", "source_ids": [ "RSRC-0218" ], "limitations": "The adopted text still references DoDD 5160.65. The current DoDI 5160.68 full text, succession, item-management assignment, execution exception and section 817 implementation remain GAP-033. This record makes no Blaze or other product-specific classification and does not determine whether an existing concurrence covers a particular later action.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2026-09-02", "effective_date": "2026-09-02", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0292" }, { "type": "related requirement", "target": "RULE-0293" } ], "date_note": "September 2, 2026 deviation is immediately effective and remains in effect until rescinded or incorporated.", "version_state": "Selected current adopted provision reviewed October 4, 2026" }, { "id": "RULE-0292", "title": "Check the FY2026 NDAA review of one-way armed/attack UAS before settling ammunition classification", "citation": "P.L. 119-60, section 817(a)-(c); amendment to P.L. 105-261 section 806(c)", "issuer": "U.S. Congress", "instrument_type": "Statute", "topic": "Acquisition planning", "equipment": [ "Effector", "Drone" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option" ], "jurisdiction": "DoD acquisitions; applicability and item identity must be established", "summary": "Section 817(a) changes the section 806(c) definition reference to include a successor directive or instruction. Section 817(b) directs review of DoDI 5160.68 and assessment of whether conventional ammunition should include one-way lethal or non-lethal armed/attack unmanned aerial vehicles and systems, with an instruction update if the Secretary determines it appropriate. It is not an automatic classification of every such system.", "applies_when": "An acquisition involves a potentially affected one-way armed/attack UAS or uncertainty about which ammunition-definition edition controls. The statutory review obligation is directed to the Secretary, not a delegated local classification decision.", "required_action": "Resolve the current instruction, any implementing determination and item classification through responsible acquisition, munitions and legal channels before relying on an exclusion. Keep system classification, component classification, SMCA concurrence and procurement execution as separate decisions. Treat passage of the review deadline as a reason to check implementation, not proof of its outcome.", "exceptions": "The amendment is conditional: section 817(b)(3) requires an instruction update only if the Secretary finds the modification appropriate. No conclusion about the nature or classification of a particular interceptor, guided effector or product follows from this section alone.", "approval_authority": "Secretary of Defense for the review, assessment and conditional instruction update; report to congressional defense committees.", "locator": "Complete section 817(a)-(c), 139 Stat. 953-954", "source_ids": [ "RSRC-0110" ], "limitations": "No completed assessment, amended instruction or resulting item-specific determination was established. The instruction and management/execution details remain GAP-033. This is not a determination that any named product is a one-way armed/attack UAS.", "status": "sourced", "evidence_grade": "G-Program", "applicability": "Requires action-specific assessment", "publication_date": "2025-12-18", "effective_date": "2025-12-18", "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0291" }, { "type": "related requirement", "target": "RULE-0293" } ], "date_note": "Enacted December 18, 2025; section 817(b) sets a 180-day review deadline and (c) a December 31, 2026 report deadline.", "version_state": "Enacted section reviewed; resulting DoDI implementation not established" }, { "id": "RULE-0293", "title": "Resolve whole-effector and warhead management and execution under the current SMCA instruction", "citation": "DoDI 5160.68: concurrence, procurement execution and conventional-ammunition management provisions — review pending", "issuer": "DoD", "instrument_type": "DoD instruction", "topic": "Acquisition planning", "equipment": [ "Effector", "Drone" ], "stages": [ "New acquisition", "Existing vehicle/order", "Modification or option" ], "jurisdiction": "DoD acquisitions; applicability and item identity must be established", "summary": "Open classification and execution question: distinguish the complete guided effector from a separately procured conventional warhead, then establish both the management assignment and the authorized procuring organization. The library has not verified the detailed instruction provisions and exceptions needed for an item-specific conclusion.", "applies_when": "A proposed purchase, order, option or modification includes conventional warheads, ammunition, guided effectors or potentially affected UAS, and the management/SMCA concurrence or executing-Service route is uncertain.", "required_action": "Obtain the current complete DoDI and its amendments through authorized public or agency policy channels. Review the concurrence requirement for SMCA-assigned and non-assigned ammunition, any transition-to-SMCA procurement rule and EDCA-notification exception, the precise glossary component and retained-item language, and any later section 817 determination. Request an item-specific written classification/routing determination for the actual configuration and separately ordered components. Keep official transaction records in the agency system; this library holds only rules and public policy.", "exceptions": "A separate analytical treatment is not authority to split a procurement or avoid concurrence. A product name, guided capability, funding source or local warrant does not settle category or delegation. No Service-retained exception to the reviewed DFARS concurrence gate is established here.", "approval_authority": "Responsible SMCA/EDCA and Service munitions/acquisition officials under the governing instruction; exact execution conditions require verification.", "locator": "Candidate March 15, 2022 instruction; concurrence/procurement provisions and glossary pp.24-26 require full-text review", "source_ids": [ "RSRC-0216", "RSRC-0218", "RSRC-0110" ], "limitations": "Source RSRC-0216 remains pending. Complete current instruction review is needed before item management and procurement execution can be determined. No conclusion is made that a complete guided effector is excluded from concurrence or that every integrated warhead is independently SMCA-managed.", "status": "open", "evidence_grade": "Unknown", "applicability": "Requires action-specific assessment", "publication_date": null, "effective_date": null, "expiration_date": null, "verified_on": null, "relationships": [ { "type": "related requirement", "target": "RULE-0291" }, { "type": "related requirement", "target": "RULE-0292" } ], "date_note": "Indexed March 15, 2022 edition is a discovery lead; current full text and amendments are not established by this record.", "version_state": "Full-text and current-implementation review pending" } ]