Tag Archives: distributed lethality

Leading the Digital Fight: How the Navy’s IW Community Must Innovate to Win

By Shane Halton and Adam Reiffen

“When companies spend millions of dollars on new information technologies but don’t change anything else, there are usually barely detectable productivity improvements. In contrast, when they also invest similar amounts in business process changes and in worker training, productivity can double or more.-The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies by Andrew McAfee and Erik Brynjolfsson

In the last year, Israel disabled all of Iran and Hezbollah’s senior military leadership at a stroke with a series of audacious precision strikes. Ukraine launched hundreds of small drones against Russia’s strategic air assets from clandestine launch locations deep inside Russian territory. Though the weaponry and tactics employed in these strikes varied wildly from explosive pagers to first person view (FPV) drones, one common thread tied these operations together – innovation in the realm of Information Warfare (IW). From the Levant to the Black Sea, the crucial role played by IW (hereafter used collectively to refer to the intelligence, cryptology, information technology, meteorology/oceanography, cyber, and space communities) has never been more impactful to warfighting than it is today.

The US Navy has adjusted accordingly to this changing character of war. In 2024, the Navy moved Information Warfare (IW) out of the Restricted Line officer category and into a newly minted Information Warfare Line (IWL) category, which serves to both acknowledge IW’s growing impact on operations and to open additional opportunities for leadership across the Fleet. This elevation offers the IW community an excellent chance to step back, assess its tactical strengths and weaknesses, and innovate where needed. 

If called upon today, could the Navy’s IW community deliver the same level of support to operations that the IDF and Ukrainian military receive from their respective military intelligence communities today? Surely it has the resources. The IW community has a workforce in the tens of thousands and close working ties with the national intelligence community. The DoW is making huge capital investments in AI solutions that should positively impact IW workflows. With all these resources available, is innovation even necessary? 

The answer is yes. Despite being well-stocked with talented personnel and appropriated funds, the Navy IW community aboard Carrier Strike Groups (CSGs), Amphibious Readiness Groups (ARGs), and at fleet-level Maritime Operations Centers (MOCs) still operate according to increasingly antiquated and inefficient business practices. Dozens of human analysts spend countless man-hours every day creating and editing PowerPoints. Others spend time using outdated search tools to answer requests for information (RFIs) from senior leadership, watchstanders, and other operators throughout the organization. Compounding these challenges is the structure of the information systems themselves, as critical information remains siloed in disparate databases, thwarting rapid retrieval, analysis, and automated fusion. The net effect of these overlapping issues is that the most data-centric part of the Navy, the Information Warfare Community, is today poorly postured to lead the Navy’s digital transformation and risks failing to effectively adapt to the modern maritime battlespace. 

Luckily for the Navy and the country at-large, there are several innovative initiatives underway across the naval IW enterprise that are showing us the way forward. These efforts, coupled with the thoughtful integration of commercially available AI solutions, offer Navy IW a once in a generation opportunity to increase productivity and output for relatively little cost. The solutions can be grouped into three categories: workforce, organizational reform, and technological solutions.

Workforce: Identifying and Cultivating Digital Talent

Walk into any MOC in the Navy and you may find an intelligent, bright-eyed young individual who identifies themselves as the command’s Chief Data Officer, or maybe Chief Technology Officer, or perhaps lead for Artificial Intelligence or Data Science. Press them a little further and they will happily explain to you that they started off at the MOC doing something entirely different but at some point they shared with their leadership that they had a technical background and could do some coding and voila they received a new job, a new set of responsibilities, and a direct line of communication to senior leadership. 

The positions of Chief Data Officer, Chief Technology Officer, AI Lead, etc. do not exist on any MOC manning documents. Still, those individuals are today found at every MOC in the Fleet. What is happening? The simplest answer is that the operational leadership at the MOCs realized they needed something that Big Navy was unable or unwilling to provide, then created new positions of their own accord by drawing from their own staffs. Every MOC did this independently, seemingly without coordinating across the Service. This is both an admirable example of deckplate innovation at the MOC-level and a fairly serious indictment of the Navy’s manpower challenges when it comes to manning a modern, digital workforce.

But the need for an innovative solution only highlights a Fleet-wide problem. The Navy lacks the ability to identify, employ, and retain digital talent (hereafter “digital” will refer to data science, data engineering, and artificial intelligence, broadly defined). There is one Navy Additional Qualifying Designator (AQD) for Data Science and it is only granted upon graduation from the Naval Postgraduate School’s (NPS) Data Science Program. There are no equivalent AQDs for artificial intelligence or other information- and data- related fields of study. The Navy currently has a much better understanding of which Sailors speak Hausa than which can code in Python, C++, or Java.

The easiest way for the Navy to address this issue is to leverage work already done by the DoW. The DoW’s Digital Workforce initiative, started by the DoW Chief Data and Analytics Office (CDAO) in 2022, generated multiple highly readable reports and useful insights for how to develop “digital talent” across the DoW. CDAO already did the hard work by creating language that could easily convert to Navy AQDs and Sub Specialty Codes (SSPs) related to data science, data engineering, software engineering, AI, etc. Once established, these AQDs and SSPs should be called out explicitly in board convening orders and other promotion criteria, making plain to both promoters and promotees that such skills are as much Navy priorities as Operations Research and Financial Management. The IW community can further lead in workforce development by serving as the community sponsor for innovative graduate certificate programs and “stackable” degrees delivered asymmetrically, including the recently-launched Master of Applied Computing program at NPS.

The AQD/SSP approach has the advantage of increasing the Navy’s oversight of who has which digital skills without unduly disturbing existing career paths, and allows detailers, commanders, and other senior leaders to quickly find and fit talent to key roles in the Fleet. Formally recognizing digital qualifications would have positive impacts on URL communities as well. For instance, an E-2D pilot with coding expertise can still be a pilot, but the Navy will also be aware that he or she has coding expertise, allowing that person to fill relevant billets, liaison roles, or collateral duties. Over time, this AQD/SSP approach will allow the formal creation of billets like the MOC Chief Data Officer and ensure that those billets are manned by qualified personnel. We believe the above recommendations are in alignment with the “Talent” section of the DoW’s January 9, 2026 AI guidance.

Organizational Reform Afloat and at the Fleets

In November 2022, Carrier Strike Group One (CSG-1), in collaboration with Project Overmatch, established the Navy’s first Data Science at Sea (DS@S) team empowered to use all available intelligence, battlespace, and operational data to address emerging warfare requirements. The DS@S team, cobbled together from volunteers around CSG-1 and its subordinate units, automated routine tasks and found novel ways to analyze, fuse, and visualize battlespace data over two deployments to the Western Pacific and the 2024 Rim of the Pacific (RIMPAC) exercise in Hawaii. This grassroots effort went on to inspire similar efforts through PACFLT and resulted in the generation of a classified TACMEMO from the Navy Information Warfare Development Center (NIWDC) detailing the initiative.1 

Over the teams’ nearly three years of operations on CSG-1, it partially or fully automated many IW processes across the Strike Group. The major lesson learned was not that you can do more IW work with fewer people – although this is true – but rather that the DS@S approach creates more bandwidth and time for meaningful human analysis. The DS@S team also developed several novel battlespace awareness and planning tools that are now commonly used by units across the Pacific.2

These teams cannot continue to operate on an ad hoc basis, however, and must be codified, trained, and employed with the same eye towards standardization as at any ESG or MOC across the Fleet. Activating reservists and peeling civilian shipriders away from other tasks has worked well enough to date but is not sustainable over time due to an ever expanding list of operational requirements with ever limited material and personnel resources. To generate consistent decision advantage, build skills over time, and be maximally responsive to the needs of the CSG, ESG, or MOC Commander, data science teams must have a permanent home, dedicated billets, and funding for both training and equipment. In May 2025, the Naval Postgraduate School hosted a summit with a variety of stakeholders to tackle these issues and explore how best to scale the DS@S initiative across the Fleet and “productionalize” the tools that the deployed teams develop.

Until now, the CSG-1 DS@S team has been housed within the Admiral’s staff, but the most natural fit for such a group is within the Information Warfare Commander (IWC) afloat construct. At present, the IWC is the senior member of the IW community embarked with the CSG, but as a member of the Admiral’s staff is without ADCON of any personnel and OPCON of only a select few. The exact nature of the IWC’s roles and responsibilities varies between CSGs based on commander’s discretion. The lack of job standardization and formal authorities (i.e., budget, NJP) for IWCs across the Fleet has hamstrung the role. 

There is an effort underway to address the structural weakness of the current IWC construct. In December 2025, Naval Information Forces (NAVIFOR), the TYCOM for IW across the fleet, established two Information Warfare Squadrons or IWRONs. These IWRONs are designed to “addresses the increasing complexity and sophistication of global threats, which actively seek to exploit vulnerabilities from seabed to space.”3 It is critical that these new IWRONs establish DS@S teams as a Department within the command. Should these pilot IWRON initiatives succeed, they should be replicated both ashore at the MOC (as previously discussed) and afloat at the Navy’s Amphibious Readiness Groups (ARGs). In this construct, the DS@S team would have the personnel, budget, hardware, and authorities to operate continuously as a digital innovation hub for the entire CSG. The IWC could even dispatch the team to work with allies and partners, as the CSG-1 DS@S team did with its French counterparts aboard ships within the CHARLES DE GAULLE Strike Group during the PACIFIC STELLER series of exercises in early 2025.4

Technological Transformation: Leveraging AI and Data

First airing in 1966, Gene Rodenberry’s Star Trek imagined a future where technology had completely redefined the human experience, allowing us to explore the universe with a fleet of massive spacecraft. One thing that the starship Enterprise did not have was an Intelligence Officer. If someone wanted to know a specific scientific fact, the capabilities of Klingon ships or the location of the nearest spaceport, they asked “Computer.” The US Navy is not quite there yet, but we’re much closer now than ever. In July 2025, the DoW announced it was granting contract awards of up to $200 million for artificial intelligence development at Anthropic, Google, OpenAI and xAI.5 Not all of that money will directly impact Navy priorities, nor will it be immediately available to afloat units, but we are getting very close to the day when almost all classified RFIs can be answered by a Large Language Model (LLM) connected to every SIPR and JWICS on a ship. Secretary Hegseth’s December announcement of GenAi.mil is a welcome step towards realizing this vision.6

The deployment of LLMs on classified datasets across the Fleet is unlikely to lead to the wholesale replacement of IW personnel but will likely change the nature of their work. LLMs on warships will need to be optimized to operate in denied or degraded communications environments, meaning they likely need to be installed and run locally onboard ships. This will improve daily performance by removing the need for an internet connection, but it also means that over the course of a deployment the datasets feeding the LLM will become out of date and questions like “when is the last time Country X’s ship operated here” will go from being accurate and useful to inaccurate and misleading after a few weeks. 

This means that the role of deployed IW personnel will be ensuring that the datasets feeding LLMs are accurate and up to date. This includes the tactical data that is collected by the ship during the course of a deployment, whether that is intelligence, METOC, or SIGINT data. As this data management and LLM curation will be a cross-IW enterprise it should become a core function of the nascent IWRON structure discussed above. Some learning and experimentation will be required as the knowledge management practices onboard most ships today do not extend beyond maintaining Sharepoint sites, Collaboration at Sea (CaS) pages, or share drive folders.

Of course ships themselves must also be considered in the execution of this concept, particularly regarding space available for hardware and power output to run LLMs as described. Operating the aforementioned equipment requires specialized–or at least dedicated–compute, which will have to be installed likely in classified spaces already at a premium on smaller classes of warship. Furthermore, both the ship’s Engineering and Information Warfare teams must be engaged to determine what capabilities could be lost or degraded if LLMs are integrated into the ship’s technology stack, including hardware, software, power supply, maintainers, and operators. These conversations and their solutions fall squarely in the wheelhouse of NAVIFOR’s IWRON program, currently being piloted on both the east and west coasts. IW Commodores and their staffs should work directly with both operational and training DESRONs, along with AIRLANT/PAC and CSG staffs, to ensure hardware, software, and manpower training and operational needs are met going into workup and deployment cycles. Integrating these solutions into routine operations as quickly as possible will be key to fully implementing an AI strategy that is set up for success.

Innovation is Necessary to Retain IW’s Warfighting Edge

As McAfee and Brynjolfsson note, investments in both workforce training and improved business practices are more impactful than technological investment alone. The Navy IW community must therefore be proactive in addressing its productivity challenges by taking a round turn on training and innovation. We must organize our forces both afloat and ashore to identify current talent, train new innovators, and ensure they are accounted for throughout their time in uniform. We must prioritize our operational forces both afloat and ashore. This means the IWC must be resourced, staffed, and authorized appropriately to operate afloat, while their MOC counterparts must be similarly taken care of ashore. And we must incentivize our most innovative personnel–the Navy’s greatest strength–to learn, train, fight, and stay Navy.

Taken together, these improvements are critical to the Navy’s future and certainly greater than the sum of their parts. The journey of a thousand miles begins with a single step, after all. The Navy has reorganized itself to adapt to technological change time and again – steel over wood, steam over wind. Now the Navy must absorb, understand, and harness the power of the digital technologies to maintain its warfighting edge. 

Lieutenant Commander Shane Halton is an Intelligence Officer currently serving in Washington DC. He previously served as a Requirements Officer at the Navy’s Digital Warfare Office and helped create the Navy’s first Data Science at Sea team aboard CSG-1.

Lieutenant Commander Adam Reiffen is an Intelligence Officer currently serving as a Federal Executive Fellow at Brown University’s Watson School of International and Public Affairs. He previously served as a Requirements Officer at OPNAV N2N6 and was Officer-in-Charge of the Navy’s Data Science at Sea team aboard CSG-1 from 2024-25.

The opinions expressed are those of the authors and do not reflect the views or policy of the U.S. Department of War, the Department of the Navy, or the U.S. government. No federal endorsement is implied or intended.

References

1. Rear Admiral Carlos Sardiello and Lieutenant Commander Shane Halton, U.S. Navy, and Annie Voigt, CNA, “The Case for Data Science at Sea,” CNA In-Depth, June 2024, https://www.cna.org/our-media/indepth/2024/06/the-case-for-data-science-at-sea.

2. Lieutenant Commanders Adam Reiffen and Shane Halton, U.S. Navy, “Lessons Learned in Year One of Data Science at Sea,” Proceedings, May 2024, https://www.usni.org/magazines/proceedings/2024/may/lessons-learned-year-one-data-science-sea.

3. Joshua Rodriguez, U.S. Navy, “A Paradigm Shift: Navy Establishes First Information Warfare Squadron, ” navy.mil, Dec 2025, https://www.navy.mil/Press-Office/News-Stories/display-news/Article/4353901/a-paradigm-shift-navy-establishes-first-information-warfare-squadron/  

4. Ensign Rachael Jones, U.S. Navy, “U.S. and French Host First-Ever Military Hackathon at Sea,” DVIDS, May 2024, https://www.dvidshub.net/news/492989/us-french-host-first-ever-military-hackathon-sea.

5. Sydney J. Freedberg, Jr., “Anthropic, Google and xAI win $200M each from Pentagon AI chief for ‘agentic AI’,” Breaking Defense, July 14, 2025, https://breakingdefense.com/2025/07/anthropic-google-and-xai-win-200m-each-from-pentagon-ai-chief-for-agentic-ai/ 

6. C. Todd Lopez, ”Hegseth Introduces Department to New AI Tool,” war.gov, Dec 2025, https://www.war.gov/News/News-Stories/Article/Article/4355797/hegseth-introduces-department-to-new-ai-tool/.

Featured Image: GULF OF ALASKA (Aug. 23, 2025) Lt. Michael Zittrauer works on a terminal in the combat information center (CIC) aboard the Arleigh Burke-class guided-missile destroyer USS Frank E. Petersen Jr. (DDG 121) during exercise Northern Edge 2025 (NE25). (U.S. Navy photo by Mass Communication Specialist 3rd Class Christian Kibler)

A New DESRON Staff – Beyond the Composite Warfare Commander Concept

By Bill Shafley

A destroyer squadron (DESRON) staff’s employment as a Sea Combat Commander in the Composite Warfare Commander (CWC) construct is unnecessarily narrow and prevents a more lethal and agile strike group. Tomorrow’s fight requires multiple manned, trained, and certified command elements. These elements should be capable of maneuvering and employing combat power. This combat power is required to support area-denial operations, assure the defense of a high-value unit, or conduct domain-coordinated advance force operations to sanitize an operating area in advance of the main body. This ability to diffuse command and control, disperse combat power, and contribute to sea control operations is imperative to fully realize the Distributed Maritime Operations (DMO) concept.

The Fight

The carrier battle groups (CVBGs) of the Cold War evolved into the carrier strike groups (CSG) of today. The components of the CWC organization did as well. The CWC organization evolved into managed defense of a high-value unit to preserve the capability of the carrier air wing (CVW). A destroyer squadron staff embarked on a Spruance-class destroyer managed multiple surface action groups (SAGs) and search and attack units (SAUs). They managed a kill chain designed to prevent submarines and surface ships equipped with anti-ship cruise missiles from ever entering their weapons release lines. As the anti-submarine warfare commander, they also managed the up-close defense of the carrier through assigning screening units and maneuvering the force as necessary to defend the ship and the air wing.

As the CVBG evolved into the CSG of today, the offensive and defensive missions were merged into one. The DESRON Staff was employed as the sea combat commander. The staff left the ships and embarked on the carrier. As maritime forces operated in support of land campaigns with precision fires far afield in mostly benign waters, defense of the CVN as a sortie generation machine became a primary mission. The carrier defense problem could be managed with one or two multi-mission cruisers or destroyers because the mission was generally limited to confined strait transits, managing a layered defense against fast attack craft, and establishing airspace control. The remainder of cruiser and destroyer offensive capability was chopped about between in-theater task force commanders to meet additional missions of interest, namely maritime interdiction and critical maritime infrastructure defense, and support to security cooperation plans. Near the conclusion of deployment, the strike group elements rejoined and went home together. This evolution has been fit for purpose over the last 25 years, but no longer.

The fight of tomorrow looks more like the fight planned for during the Cold War, with one major difference. China’s blue water fleet is quickly becoming more capable than the Soviet fleet ever was. Consequently, the wartime employment of tomorrow’s CSG must focus more on offensive employment in sea control operations while also facing greater threats. These operations are uniquely maritime as they are focused on the destruction of an enemy fleet and its components that may impact the United States Navy’s ability to operate with superiority. Commanders in this environment manage scarce resources (see fig 1) to establish and maintain a kill chain while assuring adequate defense. A CSG must fight into an environment, survive, exploit sea control, and be prepared to move and establish it again; perhaps multiple times. Each CSG, with the CVN, its air wing, the fires resident in the VLS tubes of the DDGs, needs to be preserved as a fighting unit in order to generate the combat power necessary to achieve sea control while assuring its survivability through subsequent engagements.

The defense of the carrier must now be balanced with the work necessary to survive as a complete task-organized force. The greater the demand for sea control in time and space, and the greater the enemy force contesting sea control, the more offensive firepower will be required to neutralize the enemy and establish sea control. At the same time, this enemy force may also out-range many of the CSG’s weapons, might shoot first, and will shoot back. This threat environment increases the requirement for defensive firepower. This is a conundrum for the traditional approach. As the DMO concept suggests, disaggregation of the CSG is driven now by lethality and survivability.

Fig. 1: Establishing and maintaining sea control is a balance between resources and time. Planning for and employing forces in this environment requires new thinking. See the author’s piece at: https://cimsec.org/new-forms-of-naval-operational-planning-for-earning-command-of-the-seas/

 As the above graphic notes, this tactical problem is far more complex than one of classic CVBG defense. Establishing sea control requires an optimized balance between offense and defense. This dilemma poses interesting questions. How much of the combat power of a CSG is left behind in defense? How much of it is committed to strike hard and win the war at sea? How is the offense commanded and controlled? Is there adequate command element (CE) depth to manage the CWC defense in one area and hunt/kill in another? What is the nature of the CE for these missions? Where should the CE be embarked for greatest effectiveness? How robust is it? What is the duration of the mission? The DMO concept requires command elements that, through the use of mission command can control all facets of sea control operations (to include logistics), in communications denied environments and at scale.

Today’s CSG commander lacks command and control options to address these questions. A differently manned, trained, and employed DESRON staff could provide this flexibility. This staff is at its core a command element. It could be ashore working for the numbered fleet commander as a combined task force (CTF) commander one week, embarked on a command platform the next week, and on the carrier the week after that. It might even be dispersed to all of those at once and with multiple units under tactical control (TACON). This flexibility gives higher echelon commanders multiple employment options as they consider how to delegate their command and control to meet mission needs. However, the DESRON of today is not manned, trained, or certified to be employed in this manner.

Manning Concept

The proposed command element would require watch standers and planners, including enough subject matter experts to plug into multiple battle rhythm events. The command element would have cells for current operations (COPS), future operations and plans (FOPS), information warfare (IW), and readiness. It would be manned to provide a six-section watchbill, a distinct and separate planning team, an IW cell and readiness monitoring team that would coordinate with fleet logistics and maintenance support for assigned ships. The six-section watchbill requirement would afford the staff enough personnel to split and establish command and control in two different locations for missions as assigned. This staff size is roughly equivalent to current DESRON manpower levels (40-45 personnel). Its makeup in terms of subject matter expertise is more tailored to the Sea Control mission set.

This new DESRON staff would be manned as follows:

Fig. 2: Staff Manning Construct reflects subject matter expertise for planning and watchstanding functions

Training Concept

This command element should be educated and trained to apply joint warfighting functions with multi-domain maritime resources to establish, execute, and maintain a kill chain in an assigned geographic area. This is a robust capability that can be brought to bear in defense of high value units, in intelligence preparation of the battlefield, in surveillance and counter surveillance, or in direct action against enemy surface and subsurface units.

This organization is led by a major command selected captain (O6) surface warfare officer. This officer should have significant tactical experience in command as a commander (O5), have received a Warfare Tactics Instructor certification, and/or graduated from an advanced in-residence planner course (Maritime Advanced Warfighting School, School of Advanced Air and Space Studies, School of Advanced Warfighting, School of Advanced Military Studies). Experience on squadron, strike group, or fleet staffs would also be beneficial. The chief staff officer would be an O5, post-command officer of similar qualification. Service as the chief staff officer should be viewed as a career enhancing opportunity in the 5 years between O5 command and O6 major command. The leadership of this team would be rounded out by a billeted and selected command master chief.

Officers assigned to the staff should be proven shipboard operators in the all the major warfare areas. They should be qualified as ASW Evaluators and Shipboard Tactical Action Officers. Four post-department surface warfare officers would be assigned to the staff. They would serve as lead officers for current operation (COPs), future operations and plans (FOPs), training, and readiness, and serve staggered 24 month tours. Officers would follow an assignment track within these billets to afford experience in all four jobs, culminating as COPs or FOPs. These leaders should be post-department head officers eligible and competitive for command at sea.

There would be four post-division officer tour officers assigned to this staff structure. These would be qualified as surface warfare officers and served as an Anti-Submarine Warfare Officers/Evaluators, Tomahawk Engagement Control Officers, and/or hold Warfare Coordinator Qualification. These officers would be selected for department head and due course, that is, competitive for further advancement. All of these officers would attend the Staff Watch Officer, Joint Maritime Tactics Course, Maritime Staff Officer’s Course, and specialty schools as necessary. Officer who trained with foreign navies at their principal warfare officer courses and planning courses would also be sought after to bring Coalition Integration to bear.

There would be 3 senior chiefs and 8 chief petty officers permanently assigned to this staff. The senior chief petty officers (SCPOs) would be from the ratings of Sonar Technicians, Operations Specialists, and Information Systems Technicians each would have successfully completed shipboard leading chief petty officer (LCPO) tours. They should respectively hold advanced Navy Enlisted Classifications in the ASW field, achieved senior-level air controller qualifications, and hold Communication Watch Officer and associated computer network management credentials. Assigned LCPOs in rates depicted would provide technical and watchstanding expertise in their rate. All SCPO and CPOs would complete the STWO/JMTC course work and additional rate specific training. The remaining enlisted sailors would be first or second class petty officers (E6/E5), and trained as watchstanders to support the 6 section watchbill and planning cell.

This staff would include support from additional warfare communities. The IW cell would be comprised of a lieutenant commander (O4) maritime space officer and a lieutenant (O3) intelligence officer. The IW community would provide a lieutenant commander (O4) Information Professional officer to manage communications requirements for this rapidly-deployable team. The team would be rounded out with the addition of two aviators: an MH-60R pilot and a P-8A naval flight officer. Their experience would be crucial in planning and for watchstander assistance during training and operations.

Certification Process

The proposed DESRON staff would be assigned to the Carrier Strike Group commander for administrative purposes. The DESRON staff would follow the Carrier Strike Group’s optimized fleet response plan (OFRP) progression (i.e., maintenance phase, basic phase, advanced phase, integrated phase, deployment, and sustainment phase). The staff would be deployable from deployment through the end of sustainment phase, and its qualifications would lapse as the CSG entered the maintenance phase.

Over the course of the OFRP maintenance phase, the staff would go through a personnel turnover period, to include key leadership. The primary purpose of this phase would be to establish the staff’s training plan. The WTIs would tailor the staff training plan based upon lessons learned from previous employment and potential future assignments. This training plan would incorporate the latest in tactical developments and experimentation. Furthermore, participation in table top exercises, Naval Warfare Development Command wargames, and Fleet 360 programs would be included. This training plan would be approved by the Surface and Mine Warfighting Development Center (SMWDC) and enacted by the appropriate tactical training group (Atlantic or Pacific), the Naval War College, and various warfare development commands.

The staff’s basic phase would mirror a ship’s in length and complexity by field. Staff WTIs, along with the appropriate tactical training group, would craft scenarios that build in complexity and the amount of integration with the individual cells. The staff would benefit from staff rides to all of the warfare development centers, and significant time at the tactical training group to learn cutting edge tactics, techniques, and procedures and capabilities and limitations. Through the use of live, virtual, and constructive training tools, the staff would train to the Plan, Brief, Execute, De-brief (PBED) standard in stand-alone work before gradually integrating the staff. The DESRON commander would focus on crafting intent, planning guidance, and risk assessment. The IW Cell would conduct Intelligence Preparation of the Operating Environment, the planners learn the effective use of base plans, branches, and sequels, and the watch standers would execute these in scenario work. The basic phase would culminate with the entire staff certifying over a week long exercise where the team operates in a higher headquarters battle-rhythm driven environment and is certified to a basic standard by Tactical Training Group Atlantic or Pacific (TTGL/P).

The advanced phase would begin with the DESRON staff executing Surface Warfare Advanced Tactics and Training (SWATT) at-sea with SMWDC mentors with live ships, submarines, and aircraft. This exercise mimics the training conducted during the basic phase. In this program, the staff embarks a platform and integrates with the assigned ships and operates at-sea introducing frictions not seen in the live, virtual, or constructive environment. Watch sections and planning teams would be assessed again in-situ and performance assessed to assure continued development. The SMWDC senior mentor would then recommend advanced certification to the certifying authority. If practical, the staff should embark aboard the CVN with the CSG for Group Sail (GRUSL) for additional training opportunity prior to the pre-deployment Composite Training Unit Exercise (COMPTUEX, or C2X).

The COMPTUEX would remain the final hurdle in integrated training leading to deployment certification. Over the course of the 6 weeks at-sea, the staff would have to demonstrate its capability in integrating into the CSG battle rhythm and demonstrate watch stander acumen in increasingly complex live exercise (LIVEX) evolutions.

During the COMPTUEX, the DESRON Staff would have to demonstrate its capability to act as a CTF commander afloat, both on the CVN and embarked in a smaller unit with assigned units. It must demonstrate the capability to conduct “split-staff” operations at a remote site ashore. In each of these instances, the staff must demonstrate its capability to establish C2 of assigned units for mission effect, control operations effectively, and integrate into a higher headquarters battle-rhythm.

Satisfactorily assessed in these areas, the staff would be certified to deploy. During deployment, it would be employed flexibly and with optionality based upon the tactical situation and the desired effects from commanders at-echelon. As the CSG heads over the horizon, the DESRON staff could participate in fleet battle problems (FBP) and coalition-led exercises to test and validate a whole range of new tactics, techniques, procedures, doctrine, and interoperability. As FBPs continue to develop and live, virtual and constructive training tools come on line, the chance to “fail fast” in this space only increases.

Employment Concept

The proposed tactical DESRON could be employed across a wide range of operations supporting Carrier Strike Groups, Amphibious Ready Groups, and fleet commanders. Mission and associated tasks drive span of control in terms of assigned ships, aircraft, and additional resources. As a task organized, employed, and expeditionary staff, its main value prospect would be its flexibility.

Manned, trained, and certified during the intermediate and advance training phases, the command element’s normal mode of operation would be embarked aboard a command ship. Employed to protect a command ship, it would be capable of exercising warfare commander duties in a strike group/CWC environment with up to five assigned ships. While its primary missions would remain anti-surface and anti-submarine warfare, it could augment or establish additional warfare area support (Integrated Air and Missile Defense or Information Warfare) in any surface combatant. Employed as a scouting force further afield in the assigned operating areas, a portion of the staff may embark detached assets to afford command control and transition scouting missions into local maritime superiority missions. Employed as a task force commander, it may disperse further and move ashore with a local fleet commander to oversee operations over a broader area. Though this employment method would be more taxing on the staff, it might be required for short durations of high operational tempo. With basic manning and training levels achieved, the command element could be employed to C2 joint exercises or lead TSC missions ashore with partner nations as part of its further development.

The sustainment phase would be the most important of all for this staff because it would be key to force-wide improvement. Over the course of a deployment, the DESRON staff would have participated in various operations and exercises. Based on these experiences, the staff training officer would lead a robust program of lessons learned. The assigned WTIs would also compile and prepare various tactical notes and after action reports to share amongst other DESRON staffs and units alike. As the staff transitioned into its maintenance phase, it would go “on the road” to debrief its lessons learned, new tactical and doctrinal proposals with the goal of driving organizational learning for future operations. The habitual relationships with War College and its various research groups, the warfare development commands, and SMWDC WTI community makes for an amazing opportunity to share experiences, connect subject matter experts and further development efforts across the fleet.

Conclusion

This concept is aspirational and developed without respect to resources. There are numerous additional details necessary to bring a capability like this to fruition, but none of these details require new thinking to manage. Commitment, purposeful planning, and some smart staff work would be adequate to address each on in turn. A capability like this could be developed within the 5-year Future Year Defense Program/Program Objective Memorandum cycle. The staff’s full capability will be realized over time as new business rules for assignment are enacted. The certification criteria would be amended and in some cases completely developed. But much of this infrastructure, the school houses, the courseware, and training systems already exists.

This model makes no mention of permanently assigned surface ships to the DESRON. This work presupposes that ships assigned to the squadron arrive manned, trained, equipped and certified at the basic level. Ships change operational control to the DESRON for employment via formal tasking order. Readiness oversight functions of this staff are limited across the board. This staff retains a strong working relationship with the various type commands and local maintenance centers to assure in-situ readiness issues can be resolved.

The deployment and sustainment phases of the OFRP are vital to successful maintenance and basic phases for the next set of employment. The DESRON staff responsibility in this work is to assure that the events prescribed by the Surface Force Readiness Manual are scheduled, are thoroughly completed by assigned units, and that long-term readiness risks are endorsed. Once sustainment phase is complete, the assigned ships are returned via “chop” in the same official manner. Readiness oversight success in this environment means that ships have true and complete self-assessments with ample transparency of emergent and voyage work necessary to maintain assigned readiness conditions.

The proposal for a tactical DESRON represents an opportunity to leap ahead of the competition and bring the elements of speed, synchronization, and surprise to the employment of naval forces. The CSG and ARG as units of employment have been disaggregated for most of the last 20 years in an effort to get the most out of assigned theater maritime resources. Forces have been chopped up and moved about amongst standing fleet task forces, leaving the strike group staff in most instances over-billeted in terms of staff capability. This has left DESRON staffs as the under-employed adjuncts of CSG staffs and merely augmenting the battle-rhythm. This proposal to invest in the DESRON staff and reorient it towards looming challenges would correct these trends and yield a more lethal force for employment within the Distributed Maritime Operations concept.

Captain Bill Shafley is a career Surface Warfare Officer who has written extensively on strike group operations, mission command, and sea control in this forum and others. He has served on both coasts and overseas in Asia and Europe. He is a graduate of the Naval War College’s Advanced Strategy Program and a designated Naval Strategist. These views are presented in a personal capacity.

Featured Image: PHILIPPINE SEA (June 18, 2022) Sailors aboard Arleigh Burke-class guided-missile destroyer USS Spruance (DDG 111) handle lines during a replenishment-at-sea with Nimitz-class aircraft carrier USS Abraham Lincoln (CVN 72). Abraham Lincoln Strike Group is on a scheduled deployment in U.S. 7th Fleet to enhance interoperability through alliances and partnerships while serving as a ready-response force in support of a free and open Indo-Pacific region. (U.S. Navy photo by Mass Communication Specialist 3rd Class Taylor Crenshaw)

Distributed Maritime Operations Week Concludes on CIMSEC

By Dmitry Filipoff

Last week CIMSEC published articles on the U.S. Navy’s nascent Distributed Maritime Operations (DMO) concept. Authors looked at institutional challenges, capability gaps, and other facets that could inform the development of the DMO concept. We thank the below authors for their contributions.

Look Beyond the Fleet: Finding the Capability for Distributed Maritime Operations” by Walker D. Mills

“The 2016 SFS labels the ‘right mix of resources to persist in a fight’ as one of the three tenets of Distributed Lethality. At a minimum that mix must include Marine and Army surface fires, fast attack craft, Air Force anti-surface warfare, and whatever else is needed to distribute firepower and sustain command of the seas.”

Operationalizing Distributed Maritime Operations” by Kevin Eyer and Steve McJessy

“In the course of operationalizing a viable DMO system and concept, a voyage of discovery will be necessary, and in this, both blind alleys and new approaches will be discovered. What is essential is a clear understanding of what DMO might look like so that a path to a solution can then begin to be envisioned.”

Dmitry Filipoff is CIMSEC’s Director of Online Content. Contact him at Nextwar@cimsec.org.

Featured Image: PACIFIC OCEAN (Feb. 19, 2019) The guided-missile destroyer USS Preble (DDG 88) changes course after steaming beside the aircraft carrier USS John C. Stennis (CVN 74) during flight operations. (U.S. Navy photo by Mass Communication Specialist 1st Class Bryan Niegel)

Call for Articles: The Distributed Maritime Operations (DMO) Concept

By Dmitry Filipoff

Articles Due: February 25, 2019
Week Dates: March 4-8, 2019

Article Length: 1000-3500 words 
Submit to: Nextwar@cimsec.org

The U.S. Navy is pursuing a new Distributed Maritime Operations (DMO) concept that will help redefine how the Navy fights and operates. This major operating concept will soon play a significant role in how the Navy organizes its future force development. This important line of effort was highlighted in the Chief of Naval Operations’ recently released Design For Maintaining Maritime Superiority 2.0

“Continue to mature the Distributed Maritime Operations (DMO) concept and key supporting concepts. Design the Large Scale Exercise (LSE) 2020 to test the effectiveness of DMO. LSE 2020 must include a plan to incorporate feedback and advance concepts in follow-on wargames, experiments, and exercises, and demonstrate significant advances in subsequent LSE events.”

CIMSEC invites authors to discuss the Distributed Maritime Operations concept and what it means for the future of naval power. What will it take to make this vision come alive? What new strategies and operational approaches could this concept enable? Authors are invited to discuss these questions and more as the U.S. Navy seeks to orient itself around this new concept. 

For related reading on distributed naval power, check out below the two topics weeks CIMSEC previously launched in partnership with the Navy’s Distributed Lethality Task Force.

Distributed Lethality Topic Week February 2016

Distributed Lethality Topic Week September 2016

Dmitry Filipoff is CIMSEC’s Director of Online Content. Contact him at Nextwar@cimsec.org

Featured Image: Atlantic Ocean (Nov. 30, 2003) — USS George Washington (CVN 73) Carrier Strike Group breaks formation in the Atlantic. Washington is conducting Composite Training Unit Exercise (COMPTUEX) in the Atlantic Ocean in preparation for their upcoming deployment. (U.S. Navy photo by Photographer’s Mate 2nd Class Summer M. Anderson.)