Event Brief
The Secretary of the Navy and the Chief of Naval Operations officially established the Robotic and Autonomous Systems Warfighting Development Center (RASWDC) this week, headquartered at Joint Expeditionary Base Little Creek-Fort Story, Virginia, seven miles east of Norfolk Naval Station. The command is designated an Echelon 3 warfighting development center operating under U.S. Fleet Forces Command, and Rear Adm. Melvin Smith has been named its inaugural commander. The Chief of Naval Operations framed the stand-up in stark terms, stating in a C-NOte message that "A prototype is not combat power," and separately that the center "ensures our Sailors are equipped with the tactical edge, advanced training, and specialized doctrine required to win the high-end fight."
RASWDC's stated mission spans three lines of effort: "the foundry" ties field experience to future capability development, "the fleet" runs operational tests in realistic settings and coordinates among warfare communities, and "the fight" develops doctrine and tactics, techniques and procedures, including a tactical instruction framework to certify and deploy new platforms. Smith described the center's purpose as consolidating the Navy's autonomous efforts across air, surface, and undersea domains into a single home at Little Creek, tying warfighter education, fleet equipping, and combined tactics development into one organization. Notably, RASWDC absorbs operational-employment responsibility while a separate, roughly one-month-old Direct Reporting Portfolio Manager for Robotic and Autonomous Systems (DRPM RAS) retains acquisition, budgeting, and technical-standards authority — a bifurcation that maritime-executive.com's reporting frames as the latest in a long succession of administrative homes for unmanned programs, following Surface Development Squadron One, NAVSEA's PEO Unmanned and Small Combatants, and the short-lived Portfolio Acquisition Executive for Robotic and Autonomous Systems.
The stand-up lands alongside a concrete acquisition milestone: the Navy posted a Phase II solicitation on September 23, 2026 for Medium Unmanned Surface Vessels (MUSV), seeking hulls capable of at least 10 days of unmanned operation, carrying at least two 20-foot shipping containers, and no longer than 90 meters. This followed the Navy's selection of seven companies (Sea Machines, Leidos, Saronic Technologies, Galliano Marine Services, PacMar Technologies, Birdon, and Huntington Ingalls Industries) to compete in at-sea MUSV prototype testing that ran through October 2026, each receiving a reported $15 million on successful completion. The MUSV effort itself is the successor to the cancelled Modular Attack Surface Craft (MASC) program, and program officials have said funding derives from the reconciliation bill that allocated close to $5 billion for Navy unmanned programs, including roughly $2.1 billion earmarked for MUSVs — figures attributed to a Navy official's statement to USNI News and not independently re-verified here.
Strategically, this represents an institutional bet that unmanned platforms move from experimental status to programs of record integrated into fleet warfighting doctrine, rather than isolated demonstrator projects. The CNO's framing that a prototype is not combat power signals Navy leadership's assessment that years of unmanned experimentation (Sea Hunter, Overlord USVs, Integrated Battle Problems) have not yet produced doctrine, training pipelines, or sustainment concepts adequate for contested combat employment. The center's location at Little Creek-Fort Story, an amphibious and special-warfare hub rather than a traditional surface-warfare center, suggests an intent to draw on expertise beyond conventional surface-fleet communities — a point RASWDC's commander made explicitly in prepared remarks at the command's ribbon-cutting.
Intersection Groups (5)
Proximity: DirectNear-TermFLOW C
U.S. Fleet Forces Command
Fleet Forces Command now owns operational-employment doctrine for all unmanned air, surface, and undersea systems through RASWDC, a new Echelon 3 subordinate command it must resource, staff, and integrate into existing type-commander relationships without disrupting current surface, aviation, and submarine warfighting development centers.
Strategic Options
01Direct RASWDC to publish an initial near-term implementation milestone schedule within its first quarter to establish accountability benchmarks for command structure and mission-relationship decisions
02Convene a coordination framework between RASWDC and DRPM RAS leadership to formally delineate operational-employment versus acquisition-authority boundaries before the first major TTP certification cycle
03Task RASWDC to prioritize doctrine development for the MUSV Phase II platforms entering fleet testing, given the compressed FY2027 production timeline cited in Navy shipbuilding guidance
↳ By reporting to Fleet Forces Command rather than a systems command, RASWDC is structured as a warfighting doctrine authority rather than an acquisition body, mirroring how the Navy stood up prior warfighting development centers for surface and aviation communities — suggesting unmanned systems are now being treated as a warfare community rather than a technology program.
FLOW Rationale: Moderate scale reflects a new command creation rather than a theater-level force shift, while high complexity stems from the unresolved acquisition/operations split and the command's still-forming implementation plan.
Scale (Moderate): A new Echelon 3 command reporting directly to Fleet Forces Command materially expands its doctrinal and training portfolio but does not itself redirect major force structure or theater posture.
Complexity (High): RASWDC's near-, mid-, and long-term implementation plan is still being defined by its commander, and the split between RASWDC's operational-employment role and DRPM RAS's acquisition authority creates an unresolved coordination challenge Fleet Forces Command must manage.
Key Question
What specific command-and-control relationships will RASWDC establish with existing numbered-fleet staffs and type commanders during its phased implementation, and will DRPM RAS retain full acquisition authority once RASWDC reaches full operational capability?
Watch Signals:- [Likely] Navy administrative messages or NAVADMINs detailing RASWDC's command structure and manning within the next implementation-plan phase, since Rear Adm. Smith has publicly stated a phased near-, mid-, and long-term plan is already underway per navalnews.com (Sept. 25, 2026)
- [Possible] Public friction or restructuring announcements between RASWDC and DRPM RAS over operational-versus-acquisition authority boundaries, given maritime-executive.com's characterization of unmanned-systems administration as historically unstable across multiple prior reorganizations
- [Possible] Announcement of RASWDC's first certified tactics, techniques and procedures (TTP) package tied to a specific unmanned platform, which executivegov.com reporting indicates is a stated line of effort ('the fight') for the new center
Proximity: DirectNear-TermFLOW C
Direct Reporting Portfolio Manager for Robotic and Autonomous Systems (DRPM RAS)
DRPM RAS, established only about a month before RASWDC according to maritime-executive.com reporting, must now define a durable division of labor with a second new unmanned-systems organization, with DRPM RAS retaining acquisition, budgeting, and technical-standards authority while RASWDC takes operational employment.
Strategic Options
01Establish a formal memorandum of agreement between DRPM RAS and RASWDC clarifying decision rights over platform certification, TTP sign-off, and requirements feedback loops
02Task DRPM RAS's acquisition executive to brief RASWDC's commander on the MUSV Phase II solicitation timeline to synchronize acquisition milestones with doctrine-development schedules
03Request an internal Navy review of the succession of unmanned-systems program offices (SURFDEVRON One, PEO USC, the short-lived PAE RAS, DRPM RAS, now RASWDC) to assess whether further consolidation is warranted
↳ The near-simultaneous creation of DRPM RAS and RASWDC within roughly a month of each other suggests the Navy views unmanned-systems governance as unresolved, splitting acquisition and operational-employment authority in a way that maritime-executive.com's reporting frames as the latest in a recurring pattern of administrative churn.
FLOW Rationale: Moderate scale because this reorganizes program authority rather than force posture; high complexity because the operations/acquisition split between two new organizations lacks established precedent and could generate friction during platform fielding decisions.
Scale (Moderate): The bifurcation affects program-management authority for the Navy's full unmanned portfolio but does not itself change platform numbers or theater deployments.
Complexity (High): Two newly created organizations with overlapping subject matter (one about a month old, one just stood up) must negotiate boundaries in real time, with no established precedent for how operational-employment and acquisition authorities divide in this specific unmanned-systems context.
Key Question
Will DRPM RAS and RASWDC formalize their authority boundaries before the first MUSV production decision in the 2027 fiscal year, or will overlapping mandates delay platform certification and fielding?
Watch Signals:- [Possible] A published memorandum of understanding or Navy instruction formally delineating DRPM RAS and RASWDC authorities, given the pattern of administrative restructuring documented across SURFDEVRON One, PEO USC, and PAE RAS per maritime-executive.com reporting
- [Possible] Public statements from DRPM RAS leadership (currently under Performing the Duties of Under Secretary of the Navy William Toti per maritime-executive.com, Sept. 2026) addressing coordination with RASWDC ahead of the MUSV Phase II response deadline
Proximity: CloseMonitorFLOW B
Huntington Ingalls Industries
As one of seven companies selected for MUSV at-sea prototype testing that ran through October 2026, Huntington Ingalls now faces a Phase II solicitation requiring vessels with at least 10 days of unmanned endurance and two 20-foot container payload capacity, feeding directly into the fleet-integration pathway RASWDC now owns operationally.
Strategic Options
01Submit updated MUSV design configurations meeting the revised Phase II container-payload and endurance specifications ahead of the solicitation response deadline
02Engage RASWDC's 'the foundry' line of effort to align future Romulus-family USV development with emerging fleet doctrine requirements
03Monitor DRPM RAS acquisition guidance for signals on FY2027 production-quantity decisions tied to the reconciliation-bill funding line
↳ RASWDC's doctrine-development mandate creates a feedback channel that could shape which MUSV design features contractors prioritize in Phase II submissions, shifting competitive emphasis from raw prototype demonstration toward fleet-employability characteristics.
FLOW Rationale: Moderate scale reflects a defined contract opportunity rather than a strategic shift; low complexity because the solicitation process and criteria are already published and the company has prior experience with the program's structure.
Scale (Moderate): MUSV Phase II participation affects a specific program line within a broader shipbuilding portfolio rather than the company's overall order book.
Complexity (Low): The Phase II solicitation process, response deadline, and testing criteria are clearly published and follow an established competitive framework the company has already navigated once in Phase I selection.
Key Question
Will Huntington Ingalls' Romulus-family USV design meet the Phase II requirement for at least two 20-foot container payloads and 90-meter length limits published in the September 23, 2026 solicitation?
Watch Signals:- [Possible] Huntington Ingalls Industries public statements or investor disclosures referencing MUSV Phase II submission plans ahead of the solicitation response window
- [Likely] Additional Navy contract announcements naming Phase II awardees, following the established pattern from Phase I where selected companies received $15 million each for testing per navytimes.com (June 2, 2026)
Proximity: CloseMonitorFLOW B
Saronic Technologies
As a newer entrant among the seven companies selected for MUSV prototype testing, Saronic Technologies faces a Phase II solicitation that could determine whether it transitions from a testing participant to a fielded-production vendor within the Navy's unmanned marketplace hosted on drones.mil.
Strategic Options
01Prepare a Phase II proposal addressing the revised 20-foot (down from 40-foot) container payload specification and 90-meter length ceiling
02Leverage Phase I at-sea testing performance data to strengthen Phase II positioning ahead of the November response deadline
03Track RASWDC doctrine outputs for signals on which USV mission sets (ISR, strike, logistics) the fleet will prioritize for certification
↳ The Phase II requirement reduction from two 40-foot containers to two 20-foot containers signals the Navy may be favoring smaller, more numerous unmanned hulls over larger displacement designs, a shift that could favor newer, lower-cost entrants like Saronic over traditional shipbuilders optimized for larger platforms.
FLOW Rationale: Moderate scale because Phase II selection affects a defined contract opportunity for one company; low complexity because the competitive process and criteria are already established and public.
Scale (Moderate): Phase II selection outcomes directly affect a single company's production contract prospects within a defined program rather than broader industrial-base dynamics.
Complexity (Low): The solicitation criteria, response deadline, and evaluation process are published and follow the same competitive structure Saronic already completed once in Phase I.
Key Question
Does the Phase II payload-size reduction from two 40-foot to two 20-foot containers reflect a Navy doctrinal shift toward smaller unmanned hulls that could be detected in RASWDC's fleet-employment guidance?
Watch Signals:- [Possible] Saronic Technologies public statements on Phase II submission plans or design modifications addressing the smaller container-payload requirement ahead of the November 16, 2026 response deadline noted in the solicitation record
Proximity: CloseMonitorFLOW A
Naval Information Warfare Systems Command
As the issuing office for the MUSV Phase II solicitation posted September 23, 2026, Naval Information Warfare Systems Command must manage vendor responses through the November 2026 deadline while RASWDC's parallel stand-up creates a new downstream doctrine-and-employment stakeholder for whatever platforms result.
Strategic Options
01Process Phase II vendor submissions against published criteria ahead of the November 16, 2026 response deadline
02Coordinate with RASWDC on emerging doctrine requirements that may inform future solicitation revisions
03Maintain the drones.mil marketplace listing process for approved platforms entering fleet consideration
↳ The solicitation's administrative details, including a named contracting point of contact and fixed response window, indicate this is a routine acquisition-cycle action layered under the more consequential doctrinal reorganization represented by RASWDC's creation.
FLOW Rationale: Low scale and low complexity reflect a standard solicitation-management function operating within established federal acquisition procedures, not a strategic-level decision.
Scale (Low): This is a contracting-office administrative function tied to a single solicitation cycle rather than a broader force-structure or theater change.
Complexity (Low): The solicitation process follows established federal acquisition procedures with published criteria, contact information, and response deadlines.
Key Question
Will vendor responses to the Phase II solicitation reflect the doctrine priorities RASWDC begins to articulate during its first implementation phase?
Watch Signals:- [Likely] Publication of Phase II vendor selections following the November 16, 2026 response deadline, consistent with the Navy's established pattern of timely selection announcements after prior MUSV solicitation cycles