Table of Contents
(Revised August 14, 2006)
Office of Federal Procurement Policy memorandum of April 11, 2005, Subject: Use of Brand Name Specifications, reinforces the need to maintain vendor and technology neutral contract specifications, and asks agencies to publish the supporting justification when using brand name specifications in a solicitation.
Office of Federal Procurement Policy memorandum of April 17, 2006, Subject: Publication of Brand Name Justifications, provides additional guidance regarding publication of justifications for use of brand name specifications.
(Revised February 15, 2019)
(1) Specifications, standards, and data item descriptions are indexed in the Acquisition Streamlining and Standardization Information System (ASSIST).
(2) Most unclassified specifications, standards, and data item descriptions, and DoD adoption notices on voluntary consensus standards may be downloaded from the ASSIST database (https://assist.dla.mil/ or http://quicksearch.dla.mil/). Documents contained in ASSIST that are not available for download may be identified and obtained by following the instructions at http://assist.dla.mil/online/faqs/overview.cfm.
(1) Solicitations for previously developed items shall encourage offerors to identify Single Process Initiative (SPI) processes for use instead of military or Federal specifications and standards cited in the solicitation. Use of the clause at DFARS 252.211-7005, Substitutions for Military or Federal Specifications and Standards, satisfies this requirement.
(2) Contracting officers shall ensure that
(i) Concurrence of the requiring activity is obtained for any proposed substitutions prior to contract award;
(ii) Any necessary additional information regarding the SPI process identified in the proposal is obtained from the cognizant administrative contracting officer; and
(iii) In competitive procurements, prospective offerors are provided the opportunity to obtain verification that an SPI process is an acceptable replacement for a military or Federal specification or standard for the particular procurement prior to the date specified for receipt of offers.
(3) Any determination that an SPI process is not acceptable for a specific procurement shall be made prior to contract award at the head of the contracting activity or program executive officer level. This authority may not be delegated.
(b)(2)(ii) Send the copy of the determination and findings required by DFARS 211.274-2(b)(2)(i) to DPAP/Program Development and Implementation, Deputy Director, 3060 Defense Pentagon, 3B855, Washington, DC 20301-3060; or via email to: firstname.lastname@example.org.
(Revised December 31, 2019)
PGI 211.70 -- PURCHASE REQUESTS
Requiring activities are responsible for developing and distributing purchase requests, except for the requirements for Military Interdepartmental Purchase Requests (MIPRs) (DD Form 448) addressed in 253.208-1.
(a) Agencies may use a combined numbering series for MIPRs and internal purchase requests, following the rules at 253.208-1(c)(1) for both. If using a separate numbering sequence for internal purchase requests, procedures shall be in place to ensure that the same number cannot be assigned to both a MIPR and an internal purchase request. Use of a purely internal tracking number in addition to the purchase request number is authorized and supported by the data standards. Number the purchase request by using—
(1) The requiring activity s Department of Defense Activity Address Code (DODAAC), as described in DLM 4000.25 Volume 6, Chapter 2. DODAACs may be verified at https://www.transactionservices.dla.mil/daasinq.
(2) A serial number of eight alphanumeric characters, excluding I and O ; and
(3) A revision number, with the original request being assigned zero and subsequent revisions or amendments being numbered consecutively.
(b) Prior to taking action on a purchase request, contracting officers shall ensure that the requiring activity has prepared the purchase requests in uniform contract format (see FAR 14.201-1 and 15.204), except for procurement of construction (see part 36), which should follow the current edition of the Construction Specifications Institute format. Purchase requests shall include all supporting documentation required by local contract procedures.
(c) Prior to taking action on a purchase request, contracting officers shall ensure that the purchase requests follow the line item rules and data requirements in DFARS 204.71. Purchase requests for individual supplies (i.e., not bulk commodities such as oil) shall identify whether the item to be acquired is subject to the item unique identification requirements of DFARS 211.274-2.
(d)(1) Purchase requests may be unfunded for planning purposes, partially funded,
or fully funded.
(2) Funding data in purchase requests will, at a minimum, identify the following elements of the funding source: Department Code (e.g. 21 Army), Main Account (e.g. 1804, Operation and Maintenance, Navy), Subaccount (where applicable), and Fiscal Year. Lists of these codes are published in Supplement 1 to Volume I of the Treasury Financial Manual, Federal Account Symbols and Titles, generally referred to as The FAST Book.
(3) Agencies shall have sufficient procedures in place to enable traceability of line items identified in the purchase request to those in the resulting contract. In developing such procedures, agencies shall ensure that provisions are made for circumstances in which the deliverables may be more completely defined during the process of soliciting offers and making an award.
(e) Contracting officers shall not obligate funds that have not been certified as currently available and suitable. All purchase requests shall be reviewed and certified after agreement on price and prior to award to ensure that the funds are—
(1) Suitable and available for the purpose and amount of the contract; and
(2) Traceable from the purchase request to the resultant contract.
(f) Purchase requests transmitted between requiring systems and contract writing systems shall be transmitted via the Global EXchange system (GEX) using the Purchase Request Data Standard Extensible Markup Language (XML) format (http://www.acq.osd.mil/dpap/pdi/eb/procurement_data_standard.html). Copies shall be sent via the GEX to the Electronic Data Access (EDA) (http://eda.ogden.disa.mil) system. Requiring systems and contract writing systems may use a format that can be translated to or from the purchase request Data Standard Extensible Markup Language (XML) format.