USSOCOM sUMS-G Rapid Capability Assessment: The Complete Guide for Ground Robotics Companies
Below is a brief summary. Please check the full solicitation before applying (link in resources section).
Quick Answer: What Is the sUMS-G Rapid Capability Assessment?
The sUMS-G Rapid Capability Assessment is an open Call on the Vulcan platform seeking commercially available small-to-medium Uncrewed Ground Systems (UGS) and Unmanned Ground Vehicles (UGV) that can contribute to the U.S. Special Operations Command small Uncrewed Multi-Domain Systems (sUMS) Ground Capability Portfolio. The Call opened 16 August 2026 and closes 01 October 2026 at 22:59 CDT. Companies respond by submitting a Scout Card through Vulcan, then completing a structured self-assessment of their system against a small tactical robotic ecosystem architecture. The engagement objective is market research, which means no funding is awarded directly from this Call. Selection can lead to a demonstration invitation and downstream consideration for prototype agreements, Other Transaction Agreements, SBIR or STTR topics, CRADAs, or FAR-based procurement.
The central question the Government is asking is direct: which small-to-medium UGS can solve the identified mission-thread Key Technical Problem and provide a viable capability for the sUMS Ground Capability Portfolio?
If your company builds throwable robots, packable or man-packable UGVs, quadrupeds, tracked or wheeled tactical UGVs, or purpose-built robotic platforms with manipulators, this is the single most important open door into the SOF ground robotics portfolio in fiscal year 2026.
At a Glance
Call name: sUMS-G Rapid Capability Assessment
Sponsor: U.S. Special Operations Command (USSOCOM), small Uncrewed Multi-Domain Systems (sUMS) Ground Capability Portfolio, aligned to the Program Executive Office for Tactical Information Systems (PEO-TIS) Remote Capabilities program office
Platform: Vulcan, at vulcan-sof.com, the SOF enterprise technology scouting platform and the front end for Engage SOF (eSOF)
Engagement objective: Market research
Open date: 16 August 2026, 23:00 CDT
Deadline: 01 October 2026, 22:59 CDT
Submission vehicle: Scout Card, plus a structured self-assessment and supporting evidence
Funding attached to this Call: None published. This is a market research and assessment engagement, not a solicitation with an award ceiling.
Classification level: Unclassified only
Who should respond: Commercial UGS and UGV manufacturers, robotics integrators, autonomy software companies with a hosted platform, payload and manipulator developers with a fielded host vehicle
What disqualifies you fastest: Submitting a concept, a roadmap, or a future configuration instead of a system you can put on the ground and demonstrate now
Why This Call Matters More Than a Typical RFI
USSOCOM validated its ground robotics requirements in March 2026. That validation is the gate that opens formal solicitation activity, and the portfolio lead told industry at SOF Week 2026 that solicitations would flow across the different categories of ground robotic products in the cycle that followed. The Remote Capabilities office also posted a Ground Robotics Element and Team Man Portable Systems capability assessment event on its fiscal year 2026 industry slide. This Call is the market research front end of that activity.
Two structural facts make the ground portfolio unusual. First, PEO-TIS does not own most of the platforms its sensors ride on, with one stated exception: the ground robotics portfolio, where the office does provide the platform. That makes the ground portfolio a direct platform buyer rather than a payload integrator working through another program office. Second, the office described itself as being in a constant state of market research and running roughly three RFIs per year per system category, moving faster when the operational environment changes. Companies that get into the assessment record now are positioned for the next several cycles, not just this one.
The buying posture briefed to industry was blunt. The office is looking to field what it selects. In the portfolio lead's framing, if development work is needed, that development work will most likely happen after fielding, usually as software modification or SOF-peculiar adaptation such as marinizing a system for maritime special operations use. The standing guidance to vendors was to bring mature items that are tested, that can be produced and scaled, and that operate in contested environments.
Translated for a startup: this is a fielding pipeline, not a research program. Maturity beats ambition here.
The sUMS Ground Capability Portfolio Structure
The portfolio is organized into categories by size, transportability, and mission role. Understanding which category your system belongs in is the first strategic decision you make, because the Government assesses systems inside a category and against a mission thread, not against the entire robotics market.
T-0.1, Training and Experimentation. Modular interface and drone docking systems. This category supports modular integration, concepts, and experimentation and does not fit the primary operational portfolio categories. If your product is an interface standard, a docking or launch module, a payload carrier, or a test article that enables integration rather than delivering an operational effect, this is your lane.
E-0.1, Throwables. Throwable, ruggedized recon and ISR robots. Small spherical or impact-tolerant platforms deployed by hand into a structure, a stairwell, a tunnel, or a vehicle. Assessment attention lands on survivability at impact, self-righting, camera and audio fidelity, and how quickly an operator gets usable video.
E-0.2, Packable. Compact tracked or wheeled UGVs that fit in a pack. The emphasis is on compactness and rapid deployment without dedicated transport.
E-0.3, Man-Packable. Crawling and articulated platforms carried by a single operator. Serpentine and segmented designs for confined space, void, tunnel, and rubble access sit here.
E-1.1, Element-Man-Packable. Quadruped and legged platforms at the element level. Stair climbing, rubble traverse, and payload carriage on legs. This is the fastest-growing commercial segment and the most crowded category in the portfolio, which raises the evidentiary bar rather than lowering it.
E-1.2, Team-Man-Packable. Team-level, team-packable wheeled or tracked UGVs, typically multi-wheeled platforms carrying mission payloads for a whole team rather than one operator.
E-2.0, Heavy. Heavy payload, high capacity tracked platforms. Logistics carriage, casualty movement, heavy sensor masts, and breaching or engineering support at scale.
E-3.0, Dedicated Purpose. Specialized mission platforms with dedicated capability, including manipulator-equipped systems for tasks that a general purpose UGV cannot perform.
The portfolio banner is scalable, modular, mission ready, and the framing question the Government keeps returning to is the right UGS or UGV for the right mission with the right effect. Your submission is stronger when it names the mission thread it serves and stays in its category, and weaker when it claims to cover four categories at once.
What the Government Is Actually Looking For
Available now, not conceptual
The Call is explicit that vendors should describe the capability actually available for demonstration, not a conceptual or future configuration. This is the single most consequential instruction in the document. A Scout Card that describes a system arriving next year is not a responsive submission, and the assessment structure is designed to surface the difference.
The complete system, not the chassis
Responses should clearly identify the system configuration, hardware, software and firmware, payloads, communications, autonomy features, support equipment, and other components included in the proposed capability. Two implications follow. First, the boundaries of what you are offering must be unambiguous, because the Government is assessing a deployable capability rather than a vehicle. Second, everything you omit is read as absent. If the operator control unit, the charging solution, the spares kit, the training materials, and the transit case are part of the capability, list them.
A structured self-assessment against a defined architecture
After submission, vendors complete a structured self-assessment based on the small tactical robotic ecosystem architecture developed by Dr. Jon M. Hackett, whose doctoral research addressed small tactical robotics applications and who serves as a program manager in the intelligent robotic autonomous systems space. The assessment characterizes the capability across a defined set of dimensions:
Intended mission
Operating environment
Human-machine interaction
Mobility
Power
Communications
Autonomy
Interfaces
Supportability
Resilience
Integration with other systems
This is not a marketing questionnaire. It is a comparative instrument, and it is the mechanism by which the Government builds an apples-to-apples picture of a fragmented commercial market. Prepare for it before you submit, because your answers become part of the assessment record attached to your Scout Card.
Practical guidance on the harder dimensions:
Human-machine interaction. Expect scrutiny on operator workload, one-to-many control, glove and night operation, latency, and whether the operator can reconfigure the system at their own level rather than sending it back to the manufacturer.
Power. Battery chemistry, standard military battery compatibility, hot swap, charge time, runtime at realistic duty cycles rather than idle, and the logistics footprint required to keep the system running for a multi-day mission.
Communications. Line of sight and non line of sight performance, mesh and MANET behavior, bandwidth demand, degraded and denied operation, spectrum and waveform details, and behavior on link loss. Contested electromagnetic environments are a stated requirement across the portfolio, not a differentiator.
Autonomy. Where the autonomy sits, what it does without a link, what degradation looks like, and how it behaves at the edge. USSOCOM has publicly named swarm technology, decentralized control and collective intelligence, and environment-agnostic traversability as capability development areas. Vendor-locked, proprietary vertical autonomy stacks are treated as a liability across the SOF autonomy enterprise.
Interfaces. This is where deals are won or lost. The command is buying sensors, payloads, radios, and autonomy as interchangeable elements of an architecture, and conformance to published standards is becoming the price of admission. The USSOCOM Modular Payload Standard, managed for the command by the Johns Hopkins University Applied Physics Laboratory, defines common interfaces and attributes for payloads and hosting platforms, and has expanded from Group 2 UAS to Groups 1 and 3, unmanned surface vessels, and dismounted applications, with a micro variant for smaller systems. The guidance from the command's chief systems engineer for Tactical Information Systems was explicit: adopt common standards, and do not arrive with a proprietary standard that locks the Government out of the interface. Document your mechanical, electrical, and data interfaces. State plainly whether they are open, licensable, or closed.
Supportability and resilience. Mean time between failure and repair data, field repairability at the operator level, spares and tooling, environmental and ingress protection ratings, temperature range, EMI and EMC test results, transportability, and safety documentation.
Integration with other systems. Data output formats, message standards, ATAK and common operating picture integration, edge processing, and whether your system can hand off to and receive tasking from other unmanned systems. The stated goal on the sensor side is edge processing with the least amount of data required to make a decision moving forward to the decision point, rather than everything returning to a centralized node.
Evidence, tiered honestly
For each material claim, vendors should be prepared to provide supporting evidence: test data, technical documentation, photographs, videos, interface information, safety documentation, or prior demonstration results. The Call requires vendors to clearly distinguish between four claim tiers:
Demonstrated capability
Vendor-tested capability
Calculated or estimated performance
Planned or future capability
Label every claim to the correct tier. Assessors are reading many submissions in the same category, and the fastest way to lose credibility is to present a calculated figure as a demonstrated one. A submission that is honest about tiers and thin in places reads as trustworthy. A submission that presents everything as demonstrated reads as unverified, and it will be tested at demonstration if you get that far.
What the Government Will Do With Your Submission
The Government may use the information and supporting evidence to inform comparative assessment, selection for demonstration, and subsequent marketplace consideration.
Equally important is what the Call says it does not do. Submission or successful completion of a demonstration does not constitute operational approval, certification, fielding authorization, or a Government commitment to procure the system. Treat a favorable assessment as qualification and visibility inside the SOF enterprise, not as a contract.
Assessments published in Vulcan become visible to Government users across the SOF and defense enterprise. That is the durable value of a strong submission: a well-evidenced Scout Card with a published Government assessment continues working for you across future Calls, RFIs, and program office searches long after this deadline passes.
Timeline and Key Dates
16 August 2026, 23:00 CDT. Call opens on Vulcan. Submissions accepted.
Now through late September 2026. Build or refresh the Scout Card, assemble the evidence package, resolve export control and data rights questions, and confirm any spectrum authorizations you would need for a live demonstration.
01 October 2026, 22:59 CDT. Submission deadline. This is a hard cutoff in the platform, and Vulcan has no private or draft state that holds a partial submission past the close.
Following submission. Vendors complete the structured self-assessment. Expect requests for supporting evidence against material claims.
After the assessment window. Government comparative assessment and downselection for demonstration. On comparable SOF assessment engagements, published assessments typically reach vendor Scout Cards on the order of twenty business days after an assessment event concludes.
Downstream. Selection for a demonstration or assessment event, then negotiation of an agreement if the evaluation is favorable.
Two planning notes. First, the deadline sits one day into fiscal year 2027, which means the assessment and any resulting negotiation activity happens under new-year funding. Second, if your system radiates on any frequency, approval to transmit is required before a demonstration, which may include compliance with FCC Title 47 Part 15 or a Special Temporary Authority. The FCC recommends submitting an STA request 30 to 60 days before an event. Start that clock now rather than after you receive an invitation.
Funding Allowance: What Money Is and Is Not Attached
Be clear-eyed here, because this is where companies misread SOF engagements most often.
This Call carries no published funding ceiling and makes no award. The engagement objective is market research. You are not writing a priced proposal, and there is no dollar figure to size a budget against. What you are buying with your effort is assessment, visibility, and eligibility for the pathways below.
Where the money actually appears. On SOF assessment engagements, favorably evaluated solutions move into negotiation under one or a combination of the following authorities. This is the standard path forward language used across USSOCOM assessment events run through SOFWERX:
Business to business research and development agreement as a sub-award through the SOFWERX Partnership Intermediary Agreement, under 15 U.S. Code Section 3715
Other Transaction Agreement for research or prototype projects, under 10 U.S. Code Sections 4021 and 4022. An award under Section 4022 may result in a follow-on production agreement without additional competition based on successful prototype completion, against prototype criteria determined for each project
Procurement for experimental purposes, under 10 U.S. Code Section 4023
Cooperative Research and Development Agreement, under 15 U.S. Code Section 3710a
Prizes for advanced technology achievements under 10 U.S. Code Section 4025, or prize competitions under 15 U.S. Code Section 3719
FAR-based procurement contract
The Section 4022 prototype-to-production path is the one worth understanding in detail. It is the mechanism by which a successful prototype effort converts into production without recompeting, and it is the reason non-traditional defense companies pursue OTAs rather than waiting for a full and open competition.
The parallel non-dilutive tracks. A strong showing in this portfolio also sets up funding you pursue on your own initiative rather than waiting to be selected:
USSOCOM SBIR and STTR, including Direct to Phase II, which allows a Phase II award without a prior Phase I when you can document that the feasibility objectives have already been met. For a company with a fielded UGV, Direct to Phase II is frequently the right entry point rather than Phase I
Department of War SBIR and STTR release cycles, where SBIR Phase I awards commonly land in the low hundreds of thousands and Phase II awards run into the low millions against the current statutory ceiling, with topic-specific variation
The USSOCOM Broad Agency Announcement, a standing mechanism for unsolicited proposals against command interests
SOFWERX technical experimentation and assessment events, which run on a white paper submission and review cycle culminating in live assessment with operators in the loop
Cross-service and cross-agency opportunities in ground autonomy, including Army and Marine Corps robotics programs and DIU solicitations, where the same evidence package you build for this Call is directly reusable
Budget the real cost of participation. Submission itself is free. What costs money is being demonstration-ready: shipping and travel to an assessment event, an operator and a maintainer to run the system, spares, a demonstration article you can afford to break, spectrum authorization, and the engineering time to produce interface documentation and test data you may not currently have written down. Companies that win these engagements have that package on the shelf before the Call opens.
Eligibility and Access Requirements
Vulcan registration. You need a Vulcan account at vulcan-sof.com, registered with your official organizational email address rather than a personal address. Registration establishes access type as commercial, academic, non-profit, or government, and your organizational affiliation is verified. Set this up first if you do not already have an account, because verification takes time you will not have on 30 September.
Unclassified only. All submissions must be at the unclassified level. Do not put classified or export-restricted technical detail into a Scout Card. If your differentiator cannot be described unclassified, describe the capability and offer the detail through an appropriate channel.
U.S. persons and U.S. industry. SOF assessment engagements are routinely restricted to U.S. persons or U.S. industry. Confirm the specific restriction in the Call document before investing.
Export control. ITAR and export licensing exposure is real for ground robotics with military applications, particularly where foreign nationals are employed on the effort. USSOCOM SBIR practice, for example, requires a firm employing foreign nationals on an ITAR topic to possess an export license to receive an award. Resolve your position before you are asked.
Cybersecurity. Awardees may need to comply with NIST SP 800-171 for protecting Controlled Unclassified Information in non-federal systems. If you are pre-revenue on defense work, understand this as a cost of doing business downstream rather than a surprise during negotiation.
Business size. There is no small business set-aside on a market research Call of this type. Startups and large primes are assessed on technical merit inside the same category, which is favorable for a mature small company with a real product and unfavorable for a company selling a roadmap.
How to Submit
Register or log in at vulcan-sof.com using your organizational email address
Navigate to Calls in the top menu and open the Call titled sUMS-G Rapid Capability Assessment
Decide whether to submit an existing Scout Card or create a new one. Vulcan lets you tailor elements of a submission to the specific context of each Call without maintaining multiple Scout Cards for the same solution
Do not create a duplicate Scout Card for a solution you have already carded. Duplicates will be removed. Tailor the existing card to this Call instead
Complete the card with a precise capability description, system boundaries, photographs, video, interface information, applicable tags, technology readiness level, and any Government references
Complete the structured self-assessment when prompted
Assemble and be ready to provide the supporting evidence package against every material claim
Submit before 01 October 2026 at 22:59 CDT. Cards remain editable up to the close, and there is no draft state that survives the deadline
Questions on the platform itself go to the Vulcan support team at support@vulcan-sof.com.
The Five Mistakes That Sink Ground Robotics Submissions
Selling the roadmap. The Call asks for what is available for demonstration. A future configuration described as though it exists fails the assessment and damages credibility for the next Call.
Category sprawl. Claiming that one platform serves throwable, man-packable, team-packable, and heavy roles at once reads as a company that has not chosen a mission thread. Pick the category where you are strongest and win it.
Undocumented interfaces. A proprietary interface with no published specification, or an unwillingness to discuss licensing, is now a first-order disqualifier in a portfolio built on modular payload standards.
Unlabeled claim tiers. Presenting calculated endurance, estimated range, or simulated autonomy performance without labeling it as such is the most common failure mode in structured self-assessments.
Ignoring supportability. Companies over-invest in mobility demonstration video and under-invest in the mean time between failure data, spares posture, field repair procedures, and safety documentation that determine whether a system can actually be fielded. The office intends to field what it selects, and supportability is what fielding turns on.
Who Should Respond
You are a strong fit if you have a fielded or demonstration-ready UGS or UGV in one of the portfolio categories, you can document performance with test data, and you can put an operator and a system in a room in front of an evaluation panel within a few months.
You are a plausible fit if you build payloads, manipulators, autonomy software, power systems, or comms modules and you can present them integrated on a host platform. Partnering matters here. The command has repeatedly urged vendors to team with one another, because a modular, standards-based architecture rewards integrated, compliant solutions over isolated components.
You are a poor fit if your system exists as a CAD model, a simulation, or a single hand-built prototype that has never left a controlled environment. Use the time to pursue SBIR, STTR, or BAA funding to reach demonstration maturity, then enter the portfolio at the next assessment cycle.
Frequently Asked Questions
What is the deadline for the sUMS-G Rapid Capability Assessment? Submissions close 01 October 2026 at 22:59 CDT. The Call opened 16 August 2026 at 23:00 CDT.
Is there funding attached to this Call? No. The engagement objective is market research, and no funding ceiling is published. Favorably assessed companies may be selected for demonstration and then move into negotiation under a range of authorities including Other Transaction Agreements for prototypes, sub-awards through the SOFWERX Partnership Intermediary Agreement, procurement for experimental purposes, CRADAs, prize authorities, or FAR-based contracts.
How much funding could this eventually lead to? There is no published figure for this Call. Downstream award size depends entirely on the vehicle. Prototype OTAs under 10 U.S. Code Section 4022 can carry follow-on production without recompetition. USSOCOM SBIR Phase II and Direct to Phase II awards typically run into the low millions against the current statutory ceiling. Treat this Call as qualification, and pursue priced funding vehicles in parallel.
What is a Scout Card? A Scout Card is the standard capability submission format on Vulcan. It summarizes and depicts your capability, including a description of what differentiates it, technology readiness level, media, tags, and supporting documentation. Government users across the SOF and defense enterprise can search Scout Cards, and published Government assessments attach to the card.
Can I reuse an existing Scout Card? Yes, and you should. Vulcan allows you to tailor elements of a submission to the specific context of each Call without maintaining multiple cards for the same solution. Do not create a duplicate card for a solution you have already carded, because duplicates will be removed.
What does sUMS stand for? Small Uncrewed Multi-Domain Systems. It is a USSOCOM line of effort covering Group 1 and Group 2 unmanned aerial systems and unmanned ground systems, delivering tactical organic robotic and modular payload solutions to the SOF operator. sUMS-G refers to the ground portion of that portfolio.
Which office runs this? The sUMS portfolio sits under the Remote Capabilities program office within the USSOCOM Program Executive Office for Tactical Information Systems, part of SOF Acquisition, Technology and Logistics. Remote Capabilities holds the mandate for unmanned systems across space, air, ground, and maritime domains.
Do I need to be a small business? No. There is no small business set-aside on this Call. Submissions are assessed on technical merit within a capability category.
Can a non-U.S. company respond? SOF assessment engagements are routinely limited to U.S. persons or U.S. industry, and export control rules apply to systems with military application. Confirm the specific restriction in the Call document before investing effort.
Does my system have to be a complete robot, or can I submit a payload? The Call asks for a capability available for demonstration, described as a complete configuration including hardware, software, payloads, communications, autonomy, and support equipment. A payload or software component is best submitted integrated on a host platform, ideally through a teaming arrangement. The command has actively encouraged vendors to partner rather than pitching isolated components.
What is the structured self-assessment based on? It is based on the small tactical robotic ecosystem architecture developed by Dr. Jon M. Hackett. It characterizes your capability across intended mission, operating environment, human-machine interaction, mobility, power, communications, autonomy, interfaces, supportability, resilience, and integration with other systems.
What evidence do I need? Be prepared to substantiate every material claim with test data, technical documentation, photographs, video, interface information, safety documentation, or prior demonstration results. Each claim must be labeled as demonstrated capability, vendor-tested capability, calculated or estimated performance, or planned or future capability.
Does a successful demonstration mean I have been selected or approved? No. Submission or successful completion of a demonstration does not constitute operational approval, certification, fielding authorization, or a commitment to procure. It qualifies you for comparative assessment, demonstration selection, and marketplace consideration.
How mature does my system need to be? Mature enough to demonstrate now. USSOCOM's stated posture is to field what it selects, with SOF-peculiar development, usually software modification or platform adaptation, occurring after fielding rather than before. Systems that are finicky at the tactical edge are not competitive.
Do standards compliance and open interfaces matter? Substantially. The command is building a modular architecture around the USSOCOM Modular Payload Standard, managed for the command by Johns Hopkins University Applied Physics Laboratory, and it has told industry directly not to arrive with proprietary standards that lock the Government out of the interface. Document your interfaces and be prepared to discuss access.
What if my system transmits on a radio frequency? Any developmental device radiating on a given frequency or band needs prior approval to transmit, which may include FCC Title 47 Part 15 compliance or a Special Temporary Authority. The FCC recommends submitting an STA request 30 to 60 days before an event, so begin that process before you receive a demonstration invitation.
Where do I submit? On the Vulcan platform at vulcan-sof.com, under the Call titled sUMS-G Rapid Capability Assessment. Register with your official organizational email address if you do not have an account.
What happens if I miss the deadline? The Remote Capabilities office described itself as being in a constant state of market research and typically running about three RFIs per year per system category, with additional activity when operational needs shift. A ground robotics assessment event and a small UAS assessment event were both on the fiscal year 2026 and 2027 industry slides. Missing this Call is not fatal, but it delays you by a cycle and cedes the assessment record to competitors in your category.
Get Your Submission Assessed Before the Government Does
The companies that convert SOF assessment engagements into agreements are the ones that walk in with the evidence package already built: labeled claim tiers, documented interfaces, test data behind every number, a clear category, and a named mission thread.
BW&CO helps deep-tech, robotics, autonomy, and dual-use founders position for non-dilutive federal funding and build the technical and strategic packages that agencies act on. Innovation Funding Simplified. More than $350M in funding secured for our clients.
If you are weighing whether your UGS or UGV is ready for the sUMS-G Call, or you want to run a parallel SBIR, STTR, Direct to Phase II, or BAA strategy alongside it, let's talk before the 01 October deadline.
