Questions and Answers.docx

1. Scope Clarification: Could the Government clarify whether the primary requirement is for a compliance documentation service, a transactional marketplace, or a full supply chain fulfillment solution? These models involve distinct pricing, staffing, and risk profiles.

Answer: The requirement is for a full supply chain fulfillment solution. The quoter is responsible for NDAA compliance validation and a supply chain fulfillment solution including sourcing, counterfeit prevention, and final delivery of the parts.

2. Alternative Approaches: The requirement mandates a COTS web-based marketplace. Is the Government open to alternative approaches, such as managed supply chain or 3PL solutions, that achieve performance outcomes without using a "marketplace" construct?

Answer: The Government's requirement is for a Commercial-Off-the-Shelf (COTS) web-based marketplace as the primary interface for ordering, status tracking, and NDAA verification labels. While the solution itself is a managed supply chain, the use of an online marketplace as the transactional platform is a firm requirement. The 3PL system used in the process of final delivery to the Government is at the discretion of the Contractor. As described in PWS Section 3.0, the required functional outcomes are: (1) a user interface that allows for consolidated ordering and invoicing of parts; (2) a mechanism for the Government to request and receive NDAA compliance services for nominated parts; and (3) a fulfillment solution to ship parts to the Government.

3. Performance Metrics: How will metrics account for delays or rejections caused by PMA-263 validation, which is outside the contractor's control?

Answer: The Performance Metrics are directly tied to the contractor’s primary responsibility under the FFP CLIN which is preparation and submission of a complete and accurate NDAA compliance evidence package in accordance with PWS Section 3.3. The 30-calendar day performance standard in Section 5 of the PWS captures the time between the Government’s part nomination and the Contractor’s submission of the completed package to PMA-263 in accordance with applicable guidance. The Government recognizes that PMA-263 validation timelines are outside the contractor's direct control, however, delays and rejections will be adjudicated on a case-by-case basis to ensure the contractor submitted a complete and accurate package.

4. Liability: What is the contractor’s liability exposure for parts later deemed non-compliant despite having received Government approval?

Answer: As a result of this question, section 3.4.1 has been added to the PWS via amendment to further clarify this responsibility.

5. Traceability: Could the Government clarify the required depth of traceability (OEM to distributor to reseller) and the expected documentation formats?

Answer: The contractor must be able to provide traceability as required by DFARS 252.246-7008 Sources of Electronic Parts. The traceability and documentation requirements specified in the PMA-263 guidance document is attached to the updated SAM.gov posting.

6. Scope of Service (Per Part vs. Per Order): Can the Government confirm that the billable Firm-Fixed-Price (FFP) event under CLIN 0001 is triggered once per unique part type (SKU) nominated for the marketplace, rather than for each individual purchase of that part?

Answer: The Government confirms this interpretation. The Government nominates parts for compliance certification, not for inclusion in the marketplace. The Firm-Fixed-Price for CLIN 0001, "NDAA Compliance Evidence Package Preparation Service," is a one-time charge per unique part number (SKU). This FFP event is triggered when the contractor formally submits a complete compliance package to PMA-263 for a new Government-nominated part. Additionally, the Government reserves the right to purchase parts from the marketplace that are not NDAA compliant or do not require compliance checks via other contractual mechanisms. See highlighted change in Section 1 of the PWS.

7. Leveraging Existing Blue UAS/NDAA Data: If the Government nominates a part for which already possesses a complete evidence package that meets PMA-263 required guidance, will the Government require a new nomination and a separate billable submission... or can existing validated data be leveraged?

Answer: The Government is responsible for validating that parts have PMA-263 approval for NDAA compliance. See Section 2.3.2 of the PWS.

8. Recertification Requirements: Does the Government anticipate a requirement for periodic (e.g., annual or semi-annual) evidence updates to maintain a part's approved status? If so, should these updates be treated as new nominations under the current CLIN structure?

Answer: As a result of this question the PWS has been amended. See Section 3.4.2 of the PWS.

9. Submission Content: In the interest of 100% submission accuracy, could the Government provide the specific PMA-263 checklist or guidance document referenced to ensure the "Required" evidence categories are fully addressed in our proposed methodology?

Answer: As a result of this question the RFQ has been amended, see Section 3.2 and 3.3 of the PWS.

Question 10: Section 3.5 (Electronic Invoicing) specifies that the Contractor shall submit a single consolidated monthly invoice under the T&M CLIN for parts delivered. However, the PWS also establishes Firm-Fixed-Price (FFP) CLINs for NDAA Compliance Evidence Package Preparation services, where submission of a complete package appears to constitute the billable event.

Please clarify the invoicing procedures applicable to the FFP CLINs, including whether FFP services:

(a) should be invoiced upon completion of each individual compliance package,

(b) should be included within the same monthly consolidated invoice as the T&M CLIN, or

(c) require separate invoice submissions (e.g., separate WAWF invoices).

Additionally, please confirm the appropriate timing and any required supporting documentation for FFP invoice submission.

Answer:

(a) For the FFP CLINs 0001, 1001, and 2001 (NDAA Compliance Evidence Package Preparation), the contractor is authorized to submit an invoice upon submission of each individual compliance package to PMA-263.

(b) FFP services shall not be included on the same consolidated monthly invoices as the T&M CLIN.

(c) Separate invoices shall be submitted through Wide Area Workflow (WAWF) for FFP services.

(d) The required supporting documentation for the FFP invoice is evidence of PMA-263’s receipt of the submitted NDAA compliance package. This constitutes proof of performance for the FFP event.

Question 11: CLIN Quantities: The RFQ pricing schedule lists 100 units for CLINs 0001, 1001, and 2001. The PWS Section 2.3.2 estimates 100 (Base), 50 (Option Year 1), and 50 (Option Year 2). Which quantities should quoters use for pricing purposes?

Answer: As a result of this question, the PWS has been amended. See Section 2.3.2 of the PWS.

Question 12. Market Basket and NDAA Compliance Scope: Are the items identified as "NDAA" in the Compliance Example column of the Sample Market Basket the items the Government intends to nominate for the NDAA Compliance Evidence Package Preparation service under CLINs 0001/1001/2001? Or is the market basket strictly for T&M parts pricing evaluation purposes?

Answer: No, the primary purpose of the Sample Market Basket is for price evaluation of the Time & Materials (T&M) CLINs.

Question 13. Billable Status of Incomplete Packages: If a nominated part proceeds past preliminary screening and the Contractor initiates full evidence collection under PWS Section 3.2, but the OEM is unable or unwilling to provide documentation required by PMA-263 guidance, does that outcome constitute a completed billable service under the FFP CLIN? Or is it treated as a non-billable event under the preliminary screening provision of PWS Section 2.3.2?

Answer: No, see “Preliminary Assessment (Non-Billable)” in Section 2.3.2 of the PWS.

Question 14. Seeking clarification regarding PWS Section 3.2.3, which states that the Contractor is solely responsible for uploading the compliance documentation package to the SRA portal. My understanding is that Original Equipment Manufacturers (OEMs) typically upload their documentation directly, including hardware and software scans, development documentation, cybersecurity practices, and other RMF materials. Furthermore, I believe the SRA portal handles updates directly from the OEMs.

Could you please confirm if my understanding of the SRA portal is correct? It seems unlikely that a third party would be able to upload and maintain this documentation for external OEMs.

Answer: According to PMA-263 guidance, the SRA portal is designed to support self-execution from vendors and component manufacturers. As a result of this question, the PWS has been amended, see Section 3.3.3.1. Vendor Self-Execution and Attestation of the PWS.

DISTRIBUTION: DoW COMMUNITY ONLY

DISTRIBUTION: DoW COMMUNITY ONLY

DISTRIBUTION: DoW COMMUNITY ONLY