When you write something, read it first to ensure that you don’t burst out laughing after reading it.
If you read SAM.gov for fun, you may have seen Notice ID DCSA_2026_HS002126QE023 for Michigan Fingerprint Channeling. Offers are due on April 23, so if you can satisfy the requirements, get working.
As the acronym-aware probably already know, this was issued by the Defense Counterintelligence and Security Agency (DCSA), part of the U.S. Department of Defense (with the secondary title the Department of War).
Why?
“DCSA has a recurring need for a simplified method of filling the anticipated repetitive needs for fingerprint channeling for the purpose of obtaining Criminal History Records Information (CHRI) from the state of Michigan.”
Because it’s a bad thing to make things hard, so DCSA needs a simplified method.
This is explained in the Performance Work Statement that is attached to the Solicitation Form. Another attachment is the Pricing Workbook.
So to make things simple for DCSA, you need to review all three of these documents and provide the approprirate responses.
And don’t forget to review ALL of the incorporated contract clauses, such as this one:
252.232-7006 Wide Area WorkFlow Payment Instructions. (Jan 2023)
WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)
(a) Definitions. As used in this clause-
“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.
“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).
“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.
“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by
Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.
(c) WAWF access. To access WAWF, the Contractor shall-
(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and
(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.
(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before
submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/
(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.
(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this
contract or task or delivery order:
(1) Document type. The Contractor shall submit payment requests using the following document type(s):
(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.
(ii) For fixed price line items-
(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.
Invoice 2-in-1
(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and
receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.
Invoice 2-in-1
(iii) For customary progress payments based on costs incurred, submit a progress payment request.
(iv) For performance based payments, submit a performance based payment request.
(v) For commercial financing, submit a commercial financing request.
(2) ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.
(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.
OK, that’s not the whole thing. I stopped copying it at the actual Routing Data Table itself.
This is of course a cost of doing business with any large entity, whether it’s the federal government or a multi-billion dollar firm. This who want money from these large organizations put up with it.
And laugh to themselves about the desire for things “simplified.”
Bredemarket 