Comment Resolution Matrix (CRM).xlsx

27 KB Posted

Attached to
Air Force Research Laboratory (AFRL) Enterprise Commercial Solutions Opening (CSO)
Solicitation number
FA865226SC003
Issued by

About this file

Written by GovTribe AI ·

This is a Comment Resolution Matrix (CRM) documenting government review comments and required corrections for the AFRL Enterprise Commercial Solutions Opening (CSO) contract file (FA8652-26-S-C003). The matrix tracks feedback across the Requirements, Pre-Solicitation, Solicitation, Pre-Award, and Award phases, identifying deficiencies in documentation, file organization, and contract language that must be resolved before final solicitation release.

Key issues requiring resolution include: correcting the Statement of Work (SOW) to final version with government and contractor approval and OPSEC review; resolving discrepancies in Period of Performance (POP) dates across multiple documents (currently showing conflicts between April 3-5, 2023 start dates and April 16-27, 2027 end dates); obtaining missing or outdated documents such as the DCAA letter, JCP search, FAPIIS reports, and EEO checks; clarifying base support availability details from the final memo; correcting funding documentation and ensuring finance is aware of contract number changes; resolving SAM responsibility checks and replacing confusing Memoranda for Record with the proper SAM/FAPIIS Checklist; updating the Proposal Pricing Rationale (PPNM) to reflect adjudicated comments and correcting references to file locations; and finalizing contract language in Sections B, F, G, I, and J including delivery schedules, CLIN descriptions, clause additions (such as 5352.242-9000), and attachment numbering. The matrix also recommends moving misplaced documents to correct file elements, deleting duplicate versions, and ensuring consistency between all contract sections prior to award.

View the file

Other files

File Type Posted
AFRL Enterprise CSO_FA865226SC003_Amend 02_8Sep2026.pdf PDF
Att 1 - Areas of Interest and Mission Organization Alignment_Amend 01_8Sep2026.pdf PDF
Att 1 - Areas of Interest and Mission Organization Alignment_Amend 01_8JUL2026.pdf PDF
AFRL Enterprise CSO_FA865226SC003_Amend 01_8JUL2026.pdf PDF
AFRL Enterprise CSO Spiral Tracker_4 June 2026.xlsx XLSX spreadsheet
AFRL Enterprise CSO_FA865226SC003_30 Apr 2026.pdf PDF
Appendix 4 - AFRL Privacy Act for Covered Individuals.pdf PDF
Att 3 - CSP Template_30 Apr 2026.pdf PDF
Appendix 3 - Research and Related Senior and Key Person Profile Worksheet.pdf PDF
AFRL Enterprise CSO Spiral Tracker_30 Apr 2026.xlsx XLSX spreadsheet
Att 1 - Areas of Interest_30 Apr 2026.pdf PDF
Att 2 - CSB Template_30 Apr 2026.pdf PDF
Att 4 - AFRL Solicitation Language for Security Risk Review.pdf PDF
Att 5 - Representative List of Provisions and Clauses.pdf PDF
Appendix 2 - Security Program Questionnaire.docx DOCX document
Q and A_27 Apr 2026.pdf PDF
Att 1 - Areas of Interest_DRAFT.pdf PDF
Att 3 - CSP Template_DRAFT.pdf PDF
Att 4 - AFRL Solicitation Language for Security Risk Review.pdf PDF
AFRL Enterprise CSO - Open Centralized Spiral_DRAFT.pdf PDF
AFRL Enterprise CSO_FA865226SC003_DRAFT.pdf PDF
Att 2 - CSB Template_DRAFT.pdf PDF
Appendix 3 - Research and Related Senior and Key Person Profile Worksheet.pdf PDF
Appendix 4 - AFRL Privacy Act for Covered Individuals.pdf PDF
Appendix 2 - Security Program Questionnaire.docx DOCX document
Show all 25

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

COMPANY PROFILE

Company Name

Company Address

Point of Contact

E-mail

Telephone

Business Category
(e.g., traditional defense contractor, non-traditional defense contractor, non-profit research institution, educational institution, etc.)
Socio-economic status
(as it relates to NAICS 541715 (size standard 1000 employees))

Commercial and Government Entity (CAGE) or Unique Entity ID (UEI)

FA8652-26-S-C003 AFRL Enterprise CSO Draft Notice CRM

FEEDBACK

Document Title Pg. Line No. Comment / Question

FA8652-26-S-C003 AFRL Enterprise CSO Draft Notice CRM

Contract Clearance

ReviewerDocumentPage/Para.CommentResolution
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

CRA_21Mar

FILE - IDIQ

1. Requirements Phase
a. (S) FE#47 – FDO Review
i. Recommend filing original FDO review (AFMC Form 191) that was performed prior to BAA Release
ii. For the AFMC Form 191 that was performed after proposal receipts:
1. Recommend PM add justification for Release Recommendation. Also, if this form is being used, PM does not sign this form. This form should contain FDO determination and signature.
2. Note: Keep in mind that the ASP stated that an FDO review may be performed on topics under Open BAA, as needed. Verify the need for this review with FDO– if determined not needed – then remove this form.
b. (S) FE#1 – Funding Documents
i. Two PRs are listed – ensure Finance is aware of Contract number change and verify whether PRs will need corrected, or simply a memo stating finance is aware.
c. (S) FE#163 –GFP: Base Support Availability Memo: This copy is not final version, awaiting information from engineer – once receive final Memo, ensure the following changes/comments are answered:
i. States the Base support is for “UES, Inc.” – correct contractor name
ii. Ensure this is coordinated and approved from the TD office that has the authority to approve Base Support availability.
iii. Buildings – verify buildings listed are contained correctly in PPNM and Contract.
iv. Availability dates – ensure those listed are contained correctly in PPNM and contract. Currently does not match up with POP on contract.
d. (A) FE#141 – IGE/IGCE – Funding Profile – recommend filing this under FE#1 with other funding documents.
e. (S) FE#135 - NTB –
i. #5 – Deliverables – only mentions reports. Correct to check Software and add details as necessary. In addition, ensure hardware is not needed. If so, check and add information as necessary.
ii. #15 – SOW –Correct date once SOW is revised.
iii. #21 – Base Support – this is not checked. Check and add appropriate information as necessary.
f. (S) FE#135 - TD Direction: There is typically some form of TD direction to proceed with an effort – recommend filing said direction.
g. (S) FE#135 – OPSEC Review – dated 19 Sep 22 – ensure OPSEC review is performed on Revised SOW and filed.
h. (S) FE#6 – SOW/SOO:
i. SOW: Delete old version of SOW. Remember this will be part of original proposal package filed under another FE, so no need to be filed here.
ii. SOW – Attachment 1 – Draft Revised: This SOW is in draft version, need mark-ups finalized, and final copy approved by Government and contractor personnel. See comments below Document Review. Ensure changes are made and finalized and OPSEC performed on final version.
i. (S) FE#6 - SOW Supplemental document: File final version and see comments below.
1. Pre-Solicitation Phase:
a. (S) FE#3 – Acquisition Plan: ASP – File signed copy
b. (S) FE#4 – Clearance Request and Approvals:
i. Move files - CRM_Business Clearance and Request for Business Clearance to FE#1193. This FE#4 is for Clearance for Pre-solicitation – which is not what these documents represent.
ii. Request for Business Clearance:
1. Par. 10 –POP – ensure dates are correct prior to submitting to clearance approval authority.
2. PCO Signature Date – recommend removing 5 Nov 2029 date – date of signature is included in digitally signed block.
3. Obtain Legal review prior to submitting to Clearance Authority.
iii. CRM – Business Clearance – With regards to Branch Chief Review comments – PCO states corrections were made. However, none of the documents in KTFS reflected the changes – resolve. NOTE: In future ensure file is signature ready before requesting policy clearance review.
iv. Request for Business Clearance Form:
1. #7. – Obj + Negotiation Range – reflects $24,999,470. This does not match PPNM. PPNM does not mention Negotiation Range. Ensure this number matches PPNM.
2. #10 – POP – states starts 17 Apr 2023 and ends 16 Apr 2027. Does not match contract which states 3 Apr 2023 – 5 Apr 2027. Resolve.
3. Need signatures of PCO and legal
c. (C) FE#193 – Legal Review:
i. BC – Legal Review and Adjudication to BC Legal Review: Move to FE #1193.
ii. BC – Legal Review: Legal mentions the SAM MFR and removing the 3 checks that are required. However, 3 checks are necessary for this particular action. Review SAM Checklist and FAR 9.405(a) and 9.405(e). Recommend removing this MFR and replacing with SAM Checklist located in PZL Library. Also recommend discussing with Legal.
iii. Adjudication of BC Legal Review:
1. Limitation of Funding Language - PCO states this has been added to contract – but not shown on document in KTFS – resolve.
2. MFR and FE 134 Revised – While the DFARS PGI language can be added, 3 checks are still needed. Recommend using SAM Checklist as mentioned above and provide applicable response.
3. Software Language – this had not been adjudicated yet – once it has, then update this statement as necessary.
4. Dr. Ali – ensure this is acceptable to legal.
2. Solicitation Phase:
a. (S) FE#79 – Combined Synopsis/Solicitation:
i. ARMR BAA Ceiling Tracker – Ensure Contract numbers get changed.
ii. FA8650-20-S-6008 ARMR - Appears to be the same document as ARMR BAA Ceiling Tracker with different names. If same, delete duplication.
b. (S) FE#324 – Solicitation: File attachment 1in KTFS, with rest of these documents.
3. Pre-Award Phase
a. (S) FE#203 – ACO Pricing Comments/Recommendations: CFD – Final Determination Letter – recommend deleting this because already filed under FE#202.
b. (S) FE#134 – Contractor Responsibility/Qualifications:
i. 03122023 – SAM Check MFR: Recommend either replacing this MFR with the SAM/FAPIIS Checklist (on PZL Library), or add the SAM/FAPIIS Checklist and amend the MFR to supplement it. As written the MFR is confusing in that it references 2 checks and then states 3 checks. See comments from above under Legal Review.
ii. DLA/JCP Search: obtain and file JCP search for this Export Controlled effort.
iii. FAPIIS Report: From SAM Exclusions – see PZL Library > Contract File Documentation > Contractor Responsibility – Obtaining FAPIIS Report.
c. (S) FE#100 – EEO Check: Perform and File EEO Check
d. (S) FE#1193 – Legal Review – Same comments as shown in FE#193. Recommend this FE only include Business Clearance Legal Review and Adjudication.
e. (S) FE#340 – Non-Competitive Proposal:
i. Move these file items under FE#10 – Successful Proposal. FE#340 signifies sole source actions. This proposal is considered competitive (although APC is not applicable).
ii. The naming convention used for the documents filed under this FE are somewhat confusing because they begin with “RFP…” – so sounds like an RFP document in lieu of proposals. Keep in mind for future awards.
f. (S) FE#7 – SAM Verification
i. SAM Registration/Exclusion Checks – file here under FE#7.
g. (S) FE#198 - Proposal Evaluation
i. 09082022 – PSR – dated 17 Aug 22 – delete this document – it is an old version.
ii. 03062023 – Updated PSR – States this is an Updated PSR – what was updated? Ensure the date gets changed and ensure a signature is obtained. In future, depending on the updates needed, could have filed an email from PM with changes to original PSR.
iii. Note: For future – Review PSR Training – under Meets Criteria – should list 3-4 sentences of justification – use paragraph number citations when referencing examples from proposals. Also, under Cost/Price Criterion – PM should only comments on “Realism” issues (blue italicized items on PSR Template). For example, direct labor – PM should only review types, quantities, and mix of labor – not cost or rates. This is performed by PCO when determining price to be fair and reasonable and documented in PPNM.
iv. CFD Research Corp – WP: Move to FE#10 under Proposal.
h. (S) FE#1004 – Clearance Requests and Approvals – Same comment as above –File BC Requests and approvals here.
i. (S) FE#1004 - Request for Clearance Form – Move files under FE#4 to this FE.
j. (C) FE#1225 - Certificate of Current Cost or Pricing Data – Obtain and file prior to award.
k. (S) FE#92 - PPNM -
i. Note: Branch Chief comments under FE#4 (should be moved to FE#1193) states these comments were adjudicated and changes were made but PPNM does not reflect these changes. Resolve.
ii. Para. 1.a. – correct RFP Date.
iii. Para. 2.b. – Change “(FE340)” to “(FE10)”
iv. Para. 2.b. – Change “technical evaluation,” to “White Paper Review”
v. Para. 2.b. – Reference location in file where RFP is located, i.e. FE#324.
vi. Para. 3.d. – Deliverables – recommend clarifying that the CDRL Section J reference is part of the contract. Also, add description of software deliverables.
vii. Para. 3.j Base Support – List information similar to PPNM Template in PZL Library.
viii. Para. 4.b. – After first sentence add: Cost analysis was used to evaluate the reasonableness of the certified cost and pricing data. (see PPNM Template).
ix. Para. 4.b – Verify the date of PSR – see comments above.
x. Para. 4.2) Labor OHD – Para. 4.2)i. – insert date of DCAA letter (25 Jan 2022) for tracking purposes.
xi. Para. 4.3) – Consultant
1. Para. 4.3)i. – Mentions 2 SMEs – add the basis used for the proposed amount, for example, was the proposed amount based on historical data, quotes, engineering estimates, etc.
2. Para. 4.3)i. - Mentions 2 SMEs – but only talks to one. Resolve.
3. Para. 4.3.ii. – Still need supporting data to make determination of reasonableness – obtain this before proceeding with negotiations.
xii. Para. 4.4) ODC – Para. 4.4)ii. – Reference PSR (FE#XX and date).
xiii. Para. 4.6) Fee
1. Para. 4.6)i. – States contractor proposed a fee percentage of 10% of labor, no fee is applied to travel – what about labor Overhead, consultants, G&A – clarify.
2. Para. 4.6)ii. – See PPNM Template for additional language to be added to justification of fee objective. For example, performance risk, weightings, contract type risk, etc. See DFARS 215.404-71.
xiv. Negotiation Range – Add discussion on negotiation range. See PPNM Template for Negotiation Range Discussion.
xvi. Pare. 5.b. Government Advisory Reports –
1. Para. (1) – (6) – Add location in KTFS, FE#
2. Para. (2) PSR – check date and correct as necessary
3. Para. (6) Travel websites – is this filed in KTFS? If going to reference, ensure it is filed (probably under TE Folder)
4. Add DCAA Memo – regarding Adequate Accounting System.
5. Para. 5.e. – Add it was checked prior to RFP Release – see paragraph in PPNM Template and use it.
xvii. Para. 6 – Conclusion – Correct this paragraph. Paragraph currently states a proposed amount with an up to range of the objective amount. This is confusing because “up to” sounds like the negotiation range, but it is not. This should state objective cost plus fixed fee. See PPNM Template.
4. Award Phase
a. (S) FE#118 – 1279 Report – Complete and ensure format is IAW format identified in AFFARS MP 5305.303, and submit as necessary.
b. (S) FE#346 – BuyPlan – File
c. (S) FE#12 - CAR – Complete and submit.
d. (S) FE#13 - Contract Action – see below “DOCUMENT”

DOCUMENT

1. (S) Section B – CLIN 0001:
a. Supplies/Services Column - First para. - Add reference to date of SOW
b. Supplies/Services Column - First para. – states see Section F for shipment address. But Section F only states email addresses. Verify they will all be submitted via email, in lieu of street addresses (hardcopies).
c. Supplies/Services Column - Add FAR 52.232-22 language (See CPFF & CS CLIN Description Data Template” in PZL Library)
d. Supplies/Services Column - Ensure all PRs are listed – original and AMD.
e. Amount Column - Ensure amounts are correct after negotiations.
2. (S) Section B – CLIN 0002 – Software:
a. Supplies/Services Column - First para. Add date of SOW.
b. Supplies/Services Column - See CPFF & CS CLIN Description Data Template” in PZL Library for additional language, i.e. identify Software items..
3. (S) Section F – Guaranteed Final Report Language –
a. First para. - States scheduled delivery date is reflected in Section B. I don’t see it in Section B, appears to be in Section F. Correct.
4. (s) Section F – CDRL addresses –
a. this appears to be part of the Guaranteed Final Report Clause – however, this should be its separate clause because referring to all CDRLs, not just the Final Report. Resolve.
b. Ensure all CDRLs will be submitted only via email. If want some delivered via hardcopies – ensure street addresses are included here.
c. Verify ACO email address is correct – many times we simply refer to the generic address on the cover page of contract – however, there is no email address in Block 6 of the cover page.
d. AFRL/DO email address is stated here – however, none of the CDRLS have a report going to AFRL/DO – resolve.
5. (S) Section F – CLIN 0001 – Delivery Schedule –
a. Delivery Date and POP dates – verify these are correct prior to award. Note - Delivery date 5 Apr 2027 does not match RFC Form – resolve.
b. Only one delivery date is shown, however, this CLIN 0001 is applicable to all CDRLS and CDRLs have varying delivery dates, ie. Monthly, quarterly, ASREQ, one time delivery, etc. Recommend clarifying the varying delivery dates by using language similar to the language in the “CPFF + CS CLIN Descriptive Data Template” (Slide 7) – which states hard date for FR, but also states contractor should also deliver IAW CDRLS.
6. (S) Section F – CLIN 0001 – Address and POC – Only shows PM address but CDRLS have several POCS lists - clarify where CDRLS should be shipped and to whom. This could simply be referring to the language above regarding the delivery addresses.
7. (S) Section F – CLIN 0002 – Delivery Schedule: Delivery Date and POP dates: Verify dates are correct prior to award.
8. (S) Section F – CLIN 0002 – Address and POC – Recommend adding Mark For, Contract #, and include AF PM name, office symbol, phone (See “CPFF + CS CLIN Descriptive Data Template” (Slide 9).
9. (S) Section G – PR and CIN numbers are incorrect – resolve. Verify whether both original and AMD should be listed.
10. (S) Section I – Carefully Review all clauses prior to award. PZLC does not review clauses. However, while reviewing other parts of the file, the following comment was caught:
a. Add Clause 5352.242-9000 – add and tailor this clause (used tailored language in the PZL Library > Contract File Documentation > Clauses, “5352.242-9000 Clause Verbiage” and “Security Procedures Supplement”. Then attach the Security Procedures to the Contract.
11. (S) Section J – List of Attachments –
a. Where is number 03 on List of Attachments – why was this number skipped?
b. Add Security Procedures Supplement to Contract – as an attachment.
c. SOW – Ensure date is correct once all changes are made.
d. Ensure all of Attachments contain Attachment number of the document.
e. See comments for SOW and SOW Supplemental Requirements Document below.
12. Attachments:
a. (S) Attachment 1 – SOW –
i. Need revised/updated SOW, agreed to by Government and Contractor and reviewed by OPSEC.
ii. Insert CDRL references after applicable Paragraphs.
iii. Para. 5.1 –Deliverables – Is this only software deliverables? Or software and hardware? Difficult to tell from the title. Ensure this is titled to be more clear of the actual deliverables you are referring to. Also, ensure this is consistent with the contract.
iv. Para 5.2 – CDRLS – only lists 10, not the 11 attached to the contract - resolve.
v. Para. 7.0 and 8.0 – Delete if not applicable.
vi. Ensure OPSEC review is obtained on Revised SOW.
b. (S) Attachment 4 – SOW Supplemental Requirements –Ensure you are using the latest SOW Supplemental Requirements document located in the PZL Library. Per below, it appears this document you are using may not be the latest version (for example, implementation of patent rights email is incorrect in your copy).
i. Para. 4 – Implementation of Patent Rights – Change email address to: afmclo.jaz@us.af.mil in both paragraphs (a) and (c) – ensure you are using the most recent language.
ii. Para. 6. Base Support – Insert information in Para. 6.d. and 6.e. – ensure it matches the base support availability memo once a finalized one is received.
iii. Implementation of Pollution Prevention: Add Clause and fill-ins. See Contract Information Tool located in PZL Library for additional language.

mailto:afmclo.jaz@us.af.mil

File details come from the government source that posted it. Updated .