C4S SRR Platoon Level Questions (2).xlsx
XLSX spreadsheet 29 KB Posted
- Solicitation number
- W58RGZ-26-S-C001-0002
About this file
This file is a Questions and Answers document from a federal contract opportunity for the Platoon Level Small Uncrewed Aircraft System (SUAS) Call for Solutions (C4S), solicitation number W58RGZ-26-S-C001. The document records inquiries and responses from multiple companies including Lockheed Martin, Skycutter, COLSA, SafeSky Systems USA, WISPR, and Red Cat regarding submission requirements and evaluation procedures.
Key submission requirements clarified include: the Independent Assessment Process (IAP) and Whitepaper submission are separate actions with different submission points of contact; the IAP should be submitted to uasmarketplace@army.mil while the Whitepaper should be sent to the ACC POCs (Michelle Hurt and Benjamin May); the initial Whitepaper cut-off date is 15 May 2026 with submissions after that date considered for future marketplace efforts; the 10-page Whitepaper limit does not include the cover page, OCI analysis (submitted as a separate document), NDAA compliance reports, or cyber assessment documentation. Respondents must address Core Operational Capabilities as minimum acceptable capabilities and include specific spectrum-related information (operating frequencies, bandwidth, radio supplier, and RF equipment details) rather than DD Form 1494 in the Whitepaper, though the form must be presented at the flight demonstration phase. Vendors selected for demonstration will receive 10 or more calendar days' notice before the event. The Government anticipates earliest system delivery in August 2026 and will not publicly disclose anticipated pricing or budgetary information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| C4S SRR Platoon Level Questions (1).xlsx | XLSX spreadsheet | |
| Platoon lvl System(Attachment2) rev1.xlsx | XLSX spreadsheet | |
| CLIK (Attachment 3).pdf | ||
| Platoon lvl System Characts (Attachment 2).xlsx | XLSX spreadsheet | |
| C4S Platoon lvl 23APR26 Final.pdf | ||
| Platoon Lvl SOO (Attachment 1).pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Company Name | POC | Phone | Question | USG Answer | Additional Notes | ||
| 28-Apr | Lockheed Martin | Juan R Gomez | 801.368.7492 | Lockheed has submitted our IAP and received provisional status for our Indago 4 sUAS quadrotor. Considering this fact, what do we need to do to bid on the CSO? | The IAP and Whitepaper submission are two separate actions. Please follow all instructions associated with the Platoon Level UAS C4S. The Platoon level CSO should be sent to ACC POCs listed on theSAM.Gov posting page. |
Primary Point of Contact Michelle Hurt michelle.s.hurt2.civ@army.mil Secondary Point of Contact Benjamin May benjamin.r.may4.civ@army.mil
The IAP should be submitted to uasmarketplace@army.mil
| 28-Apr | Lockheed Martin | Additionally, should we understand the Core Operational Capabilities to be objective requirements? | Core Operational Capabilies are the minimum acceptable capabilites that are defined in the excel sheet (Platoon lvl system characteristics) | |||
| 29-Apr | Skycutter | Jonathan Douglas-Smith | 44 7400338010 | jon@skycutteruas.co.uk | I was wondering if you have an idea on timescales for delivery of the UAS under this solicitation? | Earliest delivery of any amount of system will likely be AUG 2026 timeframe |
| Skycutter | And will there be any budgetary information made public on expected price per aircraft? | Anticipated cost of a system/aircraft will not be made public. Pricing in submissions will be evaluated | ||||
| 5/12/26 | COLSA | Mary Peterman | mpeterman@colsa.com | Section 6.1 states “Please include a separate cover page listing.” It appears the sentence was cut off after “listing.” Is there specific information required to be listed on the Cover Page? | General Cover page requirements. The cover page addressing this listing/call for solutions is not counted against 10 page total. The cover page should include: |
Submission Identification (Solicitation/C4S Number, CAGE, and UEI, Title of Submission, clear, descriptive title of your proposed solution, Submission Date, Offeror/Company Information, Points of Contact, Procurement/Program Information, Signature Block
5/12/26 COLSA Mary Peterman mpeterman@colsa.com Call for Solutions, Section 10 Organizational Conflict of Interest (OCI) states “however, a description of the analysis methodology, and an affirming statement that no conflicts are identified shall be included.” Are the results of the OCI analysis required to be included in the Whitepaper submission? If the OCI analysis is to be delivered with the Whitepaper, to “describe in detail the methodology used to identify actual or potential OCI issues”, will the Government allow the OCI statement to be a separate, non-counted attachment to the Whitepaper? The OCI is a separate document, that only applies if:
A company sets the ground rules for a competition in which it later competes.
Work under one contract requires it to assess itself or an affiliated entity.
Has access to non-public, competitively useful information not available to competitors.
When no conflicts are identified, a typical affirming statement reads:
"[Company Name] has conducted a thorough review of all current, past, and anticipated contracts, subcontracts, teaming arrangements, and business relationships. Based on our analysis methodology, we affirm that no actual or potential Organizational Conflicts of Interest exist with respect to this procurement."
| 5/12/26 | COLSA | Mary Peterman | mpeterman@colsa.com | Call for Solutions Section 4, Item 1, can Offerors include the “compliance report or certification from a 3rd party independent assessor and status of 2020 NDAA Sec 848, 2023 NDAA Sec 817, and cyber assessments” as a separate, non-counted attachment to the Whitepaper? | Yes. NDAA compliance reports and cyber docs are considered separate from the Whitepaper and not counted as part of the Whitepaper. |
| 5/12/26 | COLSA | Mary Peterman | mpeterman@colsa.com | Page 1 of the Call for Solutions states the IAP is to be submitted in accordance with UAS Marketplace Commercial Solution Opening (CSO) instructions. However, the W58RGZ-26-S-C001 CSO posted on SAM.gov does not include IAP submission instructions. Can the IAP be submitted by email to uasmarketplace@army.mil? | The Platoon level CSO should be sent to ACC POCs listed on theSAM.Gov posting page. Primary Point of Contact |
Michelle Hurt michelle.s.hurt2.civ@army.mil Secondary Point of Contact Benjamin May benjamin.r.may4.civ@army.mil
The IAP and questions should be submitted to uasmarketplace@army.mil
| 5/12/26 | COLSA | Mary Peterman | mpeterman@colsa.com | Is the IAP submission due on the same date as the Whitepaper and Attachment 2 System Characteristics? | The IAP is a seperate submission and does NOT have to be submitted on the same date. The Marketplace is on a continuous submission process, while the Platoon Level SUAS Call for Solutions closes on 15 May. | |
| 5/12/26 | SafeSky Systems USA | Jamie Shepler | 1 731-727-6789 | jjones@safeskysystemsusa.com | In revieing the Platoon level requirement, the opening of the C4S+Platton+lvl document as it pertains to “Whitepaper Submission Due Date/Time - Initial cut-off: 15 May 2026 |
Subsequent submissions will be evaluated on a continuous rolling basis.
Can you provide any further information on what this means? Can we submit our whitepaper anytime after the 15th of May and it will still be evaluated or will there be specific openings such as this one to submit and we would need to respond to those specific openings with due dates? The Platoon Level SRR Call for Solutions cut off date is 15 MAY 2026. Thus all Platoon Level whitepapers to be considered for this upcoming flight demonstratin and acceptance window must be received by COB, MAY 15 for the Platoon Level SUAS Call for Solutions.
Submissions received after 15 May, will be considered for future UAS Marketplace efforts. IAPs must be submitted for UAS Marketplace consideration.
5/12/26 WISPR Conor Ferguson conor@wisprsystems.com IAP and DD Form 1494 (Reference: Section 5.4 / SOO Section 2.2): Should a copy of the DD Form 1494 for our RF equipment also be included in our whitepaper submission to the PCO and CS, or is it only required to be presented at the flight demonstration phase? Submission of DD Form 1494 is not required as part of the Whitepaper response to this Call for Solutions. However, respondents must include the following spectrum-related information within their Whitepaper submission:
Operating Frequencies – Specify all frequencies or frequency ranges utilized by the proposed solution.
Bandwidth – Identify the bandwidth requirements for each frequency or frequency range.
Radio Supplier/Manufacturer – Provide the name of the radio equipment manufacturer or supplier.
RF Equipment Details – Include detailed technical specifications of the RF equipment, including model numbers, transmit power, modulation types, and any other pertinent characteristics.
This information will be used to assess spectrum compatibility and inform any subsequent spectrum certification requirements should the solution advance beyond the Whitepaper phase. Additionally the DD From1494 document must be presented at the flight demonstation.
5/13/26 WISPR Conor Ferguson conor@wisprsystems.com OCI Analysis (Reference: Section 10): Section 10 directs offerors to submit the OCI analysis "in addition to the IAP submission." Please clarify whether the Government's expectation is that the OCI analysis be included within the whitepaper document itself, or submitted as a separate standalone document accompanying the whitepaper submission. The OCI is a separate document, and only applies if:
A company sets the ground rules for a competition in which it later competes.
Work under one contract requires it to assess itself or an affiliated entity.
Has access to non-public, competitively useful information not available to competitors.
When no conflicts are identified, a typical affirming statement reads:
"[Company Name] has conducted a thorough review of all current, past, and anticipated contracts, subcontracts, teaming arrangements, and business relationships. Based on our analysis methodology, we affirm that no actual or potential Organizational Conflicts of Interest exist with respect to this procurement."
5/13/26 Red Cat JIm Miller jim.miller@redcat.red Would you please confirm the significance of the initial cut-off date, 15 May 2026 regarding the Call for Solution listed below. Specifically, we would like to confirm if 15 May 2026 is the final date for any submissions for the CSO listed below? The Platoon Level SRR Call for Solutions cut off date is 15 MAY 2026. Thus all Platoon Level whitepapers to be considered for this upcoming flight demonstratin and acceptance window must be received by COB, MAY 15 for the Platoon Level SUAS Call for Solutions.
Submissions received after 15 May, will be considered for future UAS Marketplace efforts. IAPs must be submitted for UAS Marketplace consideration.
| 5/13/26 | Red Cat | JIm Miller | jim.miller@redcat.red | Will solution submissions be accepted immediately following 15 May 2026 under different or the same conditions? | Submissions received after 15 May, will be considered for future UAS Marketplace efforts. IAPs must be submitted for UAS Marketplace consideration. |
| 5/13/26 | Red Cat | JIm Miller | jim.miller@redcat.red | Will another window to submit relevant submission open at a later date following 15 May 2026 in four, six or 12 months from now? | The Army will reassess the frequency of expanding OEMs into Platoon Level UAS fieldings based on evolving requirements and the pace of technological advancement. |
| 5/13/26 | Red Cat | JIm Miller | jim.miller@redcat.red | How long following a submission for the CSO below (Platoon Level Small Uncrewed Aircraft System (SUAS)) should a vendor be expected to be available to demonstrate a system to SUAS? | Each vendor will have 10 or more calendar days after notification of selection to prepare for the demonstration |
mailto:Jon@skycutteruas.co.ukmailto:jim.miller@redcat.redmailto:jim.miller@redcat.redmailto:jim.miller@redcat.redmailto:jim.miller@redcat.redmailto:mpeterman@colsa.commailto:mpeterman@colsa.commailto:mpeterman@colsa.commailto:mpeterman@colsa.commailto:mpeterman@colsa.commailto:jjones@safeskysystemsusa.commailto:conor@wisprsystems.commailto:conor@wisprsystems.com
File details come from the government source that posted it. Updated .