Showing posts with label OMFV. Show all posts
Showing posts with label OMFV. Show all posts

Tuesday, July 27, 2021

Here is the Point Blank Enterprises, Inc. OMFV concept

 United States Army Contracting Command, Detroit Arsenal has awarded Point Blank Enterprises, Inc. Contract for Concept Design for the U.S. Army’s Optionally Manned Fighting Vehicle (OMFV) Program.



MIAMI LAKES, Fla., July 27, 2021 (GLOBE NEWSWIRE) -- Army Contracting Command, Detroit Arsenal has awarded Point Blank Enterprises, Inc. (PBE) business unit, The Protective Group (TPG) a $60.6M Firm Fixed Price Contract for Phase 2, Concept Design for the U.S. Army’s Optionally Manned Fighting Vehicle (OMFV) Program. The OMFV is planned to be an important weapon system platform in the Army’s Armored Brigade Combat Teams (ABCTs) and is part of the larger Next Generation Combat Vehicle Family of Combat Vehicles. The OMFV concept is envisioned to encompass future capabilities and basic operational requirements including: scalable survivability and protection, remotely controllable, preplanned growth to easily integrate future capabilities, embedded platform training, and decisive battlefield lethality. The Army plans for the first OMFV delivery in the fourth quarter of FY2028 for final testing with a final Full Rate Production (FRP) decision in the third quarter of FY2029.


Mark Edwards, Executive Vice President for Point Blank Enterprises said, “We are honored to be selected to participate in this essential Army combat vehicle program. We have assembled a diverse industry team that, like Point Blank, is fully committed to providing the most advanced and reliable products to our men and women in uniform. This award reaffirms our ability to assemble and manage diverse technical teams performing complex and innovative collaborative design engineering programs. Our OMFV design concept will not be constrained or limited by previous design engineering approaches or technologies that produced the last generation of combat vehicles. Innovative engineering solutions and continuously integrating improvements into our product designs are in our DNA, both of which are key to this phase of the OMFV program.”


For nearly 50 years, Point Blank Enterprises, Inc. has been a leading provider of threat protection products engineered to maximize user survivability.

Saturday, March 20, 2021

Soggy Boots on Everest and Robotic Warfare: Why We Should Not Wait for the Arrival of Full Autonomy to Field Unmanned Ground Vehicles


Ripsaw M5 RCV-M


Before beginning any endeavor, one must ask themselves a question: Do I do this now or wait for better conditions?


The night prior to his historic summit of Mount Everest in 1953, Sir Edmund Hillary left his boots outside his tent. Naturally, the subzero temperatures froze them solid. Hillary and Tenzing, his Sherpa guide, did their best to thaw the boots using a camp stove and made the decision to push to the summit in less than ideal conditions. On 29 May 1953, Hillary and Tenzing became the first known humans to stand upon the highest point on Earth. The duo had the option of waiting for a better hand, but they elected to play the cards that the mountain dealt. Accordingly, history now binds their names to a monumental achievement as opposed to a footnote describing a failed attempt.


Now, we find ourselves facing a similar choice with regard to Robotic Combat Vehicles (RCV). We must decide if we should wait until unmanned ground vehicles (UGVs), such as the RCV, are able to autonomously maneuver through dense terrain, negotiate obstacles, and acquire targets for their human operators before we begin to integrate them into combat formations. Given what we have learned during the past four years of experimentation, we categorically believe that moving forward, while working with a still maturing level of technology, is the best path towards long-term success with bringing robotic warfare into fruition. Current technology will enable UGVs to provide significant value to both contemporary and future combat formations.


Robotic Combat Vehicle information sheet, March 2021


In 2020, the RAND Corporation conducted a company-level table top exercise (TTX) set in the Baltic States in the 2030s. Friendly forces (BLUFOR), consisting of a Manned Unmanned-Teamed (MUM-T) rifle company, augmented with both Light and Medium RCV variants and Unmanned Aerial Systems (UAS), attacked an enemy (OPFOR) rifle company defending a covered and concealed position. RAND conducted two iterations of the TTX. The first scenario, or the baseline, featured autonomy with a contemporary capability suite, to which we refer as “augmented teleoperation.” Further, the BLUFOR was only able to control RCVs if the control vehicles had a direct line of sight and in the absence of enemy electronic warfare attacks. Additionally, each control vehicle was limited to controlling two RCVs, thus “preventing [BLUEFOR] from massing RCVs against an [enemy] position” (RAND, 2020). Following the initial iteration, the BLUEFOR attacked with a very robust autonomy capability suite. During this second round, BLUEFOR RCVs could autonomously maneuver to positions of dominance without human intervention and converge lethal effects upon the enemy. These unmanned vehicles had “the ability to detect, identify, and engage targets without human intervention—which the Army does not yet envision—as an exemplar of the capabilities that might be technically feasible in the farther term” (RAND, 2020). In short, the autonomous vehicles “never failed to do what the players wanted” (RAND, 2020). Given the disparity between these capability sets, the results were little more than a forgone conclusion. In a Jan. 6, 2021, Forbes article, David Axe surmised the experiment’s results concluded that “remote-controlled vehicles are actually inferior to both manned vehicles and A.I. vehicles in certain key regards. Go with human beings or self-steering ‘bots, but maybe don’t try to comprise between the two” (Axe, 2021). Taking this single data point at face-value, one would logically have little, if any, desire to integrate UGVs into a combat formation prior to the arrival of full autonomy characteristics. We disagree with Axe’s conclusions.


Both virtual and live experiments have generated the Army’s initial robotic warfare concept. This vision includes UGVs and UASs operating forward of the human element and employing their sensors to rapidly develop a common operating picture that commanders will use to dictate the terms of the first human engagement. Unmanned vehicles will significantly extend the battlefield’s geometry and make first contact with an enemy well beyond the direct fire range of manned platforms. This form of ground maneuver warfare is a revolutionary change from our current doctrine and will require a substantial amount of time to learn how best to employ MUM-T on a hyperactive battlefield. The Army will build competence in this regard incrementally through ample “sets and reps.” Whether we begin this journey now or wait until 2040, the fact remains that robotic warfare is not something that will materialize overnight, regardless of autonomy’s maturity.


Integrating UGVs into combat formations prior to the arrival of full autonomy will allow Soldiers and leaders to develop and refine the necessary doctrine and tactics, techniques, and procedures (TTPs) required to effectively employ UGVs on future battlefields. Failing to couple the integration of new technology with validated doctrine and TTPs negates much of a new technology’s potential utility to the warfighter. For example, the US Army began using Night Vision Devices (NVDs) in the early years of Vietnam and continued to do so until the Army of the ‘80s and ‘90s boasted that it categorically “owned the night.” This capability gave the Army a substantial advantage over its adversaries up to the present day.


The Army built upon the lessons learned in Vietnam and continued to refine its doctrine and TTPs until it arrived at its current state of night-fighting proficiency. Speaking plainly, arriving at this point has taken a substantial amount of time and repetitions. Today’s Soldiers might scoff at the sight of a Starlight Scope or PVS-5s, but that archaic technology allowed their predecessors to own the night and led to today’s thermal night vision goggles and tomorrow’s Integrated Visual Augmentation System.


The same logic applies to the future revolutionary integration of UGVs into combat formations. Waiting for the perfect conditions that we presume will arrive upon the advent of full autonomy will deny years, if not decades, worth of training and doctrine development, thus offsetting a significant portion of UGV utility and effectiveness.


Our adversaries are certainly not waiting for perfect autonomy to move forward with integrating UGVs into their formations. Open source reporting provides one with a deluge of information about China and Russia’s efforts in this regard. In June 2020, The Daily Mail published both an article and footage of China’s “Sharp Claw 1” (Thomson, 2020). In a statement reminiscent to those made by our own Army leaders, Bai Mengchen explained that the PLA will have a “human-in-the-loop” to authorize lethal engagements and help the robot improvise and “halt [a] task when necessary” (Thomson, 2020). Meanwhile, Russia went as far as to test the Uran-9 platform in combat while conducting operations in Syria (Roblin, 2019). While the platform performed poorly during these operations, Russia took note of its shortcomings and is working to improve the system’s future performance to support Russia’s strategic objective of “deploying 30 percent of Russia’s kinetic weapons on remote-control platforms by 2025” (Roblin, 2019). Recall the example of the Army’s embrasure of NVDs during Vietnam which culminated with the dominance of operating in limited visibility conditions. Our adversaries are taking the same approach with UGVs. They are not waiting for the arrival of full autonomy for they see the value of an aggressive integration to optimize platform performance with mature doctrine and force structures. We cannot wait for perfect technological conditions while our adversaries enjoy a significant head start in the development and implementation of robotic warfare.


While maintaining pace with our adversaries is important, we must also develop a bond of trust between UGVs and their operators, Army leaders, and our civilian legislature. Humans are naturally apprehensive about embracing new technology that poses a potential of physical harm. For example, people refused to ride in elevators during the 19th century due to a fear that the system would fail, crash, and kill everyone foolish enough to ride in the deathtraps. This attitude changed with the inclusion of an elevator attendant who directed the elevator to the floor desired by its passengers. The human attendant helped establish a degree of trust that enabled the idea of an elevator transcend from a deathtrap to the common convenience that we know today (Hill, 2019). We must cultivate a similar degree of trust with UGVs if we hope to successfully integrate them into future combat formations.


In addition to building trust, integrating UGVs into combat formations will enable the Army to collect the data necessary to improve autonomy with relevant and reliable behaviors. Data collected from small-scale experiments and limited engineering evaluation tests will enable UGVs to perform well in those environments. But Soldiers and engineers employ combat vehicles in much different ways. Integrating UGVs into combat formations, maneuvering them in conjunction with a human element, and training them to perform tactical tasks in a relevant mission environment will provide future autonomy relevant to the warfighter. The Ground Vehicle System Center (GVSC) understands this approach and is placing it into practice with their Leader-Follower program. This effort consists of Palletized Load Systems (PLSs) autonomously following a human-operated PLS. Currently, Soldiers are operating a fleet of Leader-Follower vehicles at Fort Polk, Louisiana. Leader-Follower is not only influencing future autonomy, but this experiment is enabling developers to learn how to do the actual integration of unmanned systems into a human formation. Developers are also using the Soldier feedback to develop new TTPs and accurately define the value proposition of Leader Follower. To be specific, GVSC has learned that Leader-Follower has the potential to decrease the number of Soldiers required to provide logistic support and thus gives commanders options to re-task those Soldiers to other missions such as security augmentation or additional logistic resupply missions. The Army must take the same approach with UGVs and integrate them into combat formations to deliver the same results provided by the Leader-Follower program.


Let us further pull the thread of the actual definition of “full autonomy.” Both civilian and government efforts struggle to define what automated behaviors constitute this term. Everyone agrees that we must continue to work towards full autonomy; however, the moment at which we will reach our goal is still up for debate. Some viewpoints believe that full autonomy consists of behaviors that are almost as good as human behaviors while others demand that machines must bypass our capabilities before we can deem them fully autonomous. Anchoring the decision to move forward with integrating UGVs upon the arrival of full autonomy therefore hinges the entire effort upon a subjective opinion. If we believe full autonomy is ten years away, how can we be certain that we will be satisfied with what we find in 2031 or another arbitrary starting point? Goal posts tend to move when they are anchored on subjective opinions as opposed to tying decisions to objective performance measures such as a formation’s performance at a combat training center or the outputs of a Mission Essential Task List evaluation in a training environment. Both our live and virtual experiments have proven that UGVs enhance a formation’s lethality and survivability. We are where we need to be now. Let us move forward with the autonomy we have instead of waiting for better conditions that will always await on the far side of the next decade.


Moving forward with integrating UGVs into combat formations now will allow the Army to iterate upon the platform’s software and hardware requirements vis-à-vis Soldier and leader feedback. While there is a hardware technology element to combat UGVs, the driver for future capability, the elusive “full autonomy”, is a software defined future. Exquisite requirements defined in a “waterfall development process” are the antithesis of modern software development best practices. Software-defined UGVs offer the Army the ability to quickly iterate small, incremental capability improvements based on agile software sprints allowing tactics and technology to evolve together. Compare this approach vice moonshot requirements effort that could very well be focused on the wrong target. The specter of Future Combat Systems still haunts contemporary modernization efforts and serves as salient reminder of what happens when the Army develops requirements in a vacuum as opposed to embracing an iterative and dynamic process. Therefore, waiting for ideal conditions and hoping that we get the requirements right on the first attempt is yet another permutation of past failed endeavors.


A modern software developmental approach is not something the Army can simply “will” into existence; rather, the Army must take several critical steps to realizing this desire. The Army has dedicated significant investment into taking a modular open system approach (MOSA) for unmanned maneuver capabilities for UGVs. Leveraging the ubiquitous Robotic Operating System (ROS) middleware for autonomy, purposeful intellectual property management – combined with the new Software Acquisition authorities granted by Congress -- the Army has the ability to quickly and affordability improve baseline system capabilities driven by direct feedback from Soldiers using the systems. We acknowledge that implementing this vision will challenge every element of the Army Acquisition Enterprise, from how we write requirements to how systems are developed, acquired, tested, safety certified, and ultimately upgraded over their life cycle. That said, we categorically believe a modular and iterative approach is the path the gives the Army the best chance to get this critical bet right. This approach enables the Army to take advantage of innovation to get UGVs into the fight as quickly, efficiently and affordably as possible.


Let us now pose the counterargument and take the position that there is little point of moving forward with UGVs until unmanned vehicles are capable of autonomously flowing across battlefields in formations of RCVs paired with UASs that rapidly detect targets and strike our enemies miles behind their front lines. Anything short of that standard would waste both the Army’s time and taxpayer dollars. Let us also disregard this paper’s previously stated arguments. All things being equal, we still have one unmitigated challenge: Soldiers will continue to perform the most dangerous tasks on hyperactive and lethal future battlefields while we wait for full autonomy to arrive. Prior to that moment, Soldiers, not robots, will investigate potential chemical strikes, breach obstacles while under coordinated combined arms fire, and conduct reconnaissance on isolated and dangerous observation positions. These are all tasks that UGVs can perform, but our Soldiers will not be able to offload the extreme risk associated with these missions until the Army decides to integrate UGVs into combat formations. Integrating UGVs into combat formations is risky, but the potential consequences pale when compared to making a parlay bet to deliver both perfect doctrine, MUM-T force structures, and platforms on the first attempt after our adversaries have been experimenting with robotic formations for an entire decade.


In closing, let’s revisit our friend Sir Edmund Hillary shivering in a tent on Mount Everest in 1953. His boots were soggy and the aggregate conditions for summiting the highest point on Earth were far from ideal, but he and Tenzing took the risk and achieved their goal. Applying this metaphor to our argument, we and our adversaries are climbing towards employing MUM-T formations on future battlefields for we know the extreme lethality of the next conflict is something we have yet to fully appreciate. Successfully integrating UGVs into combat formations will take time, resources, and repetitions. Contemporary technology is adequate to enhance a ground maneuver formation’s effectiveness and will enable that formation’s capability to evolve as technology matures based on direct Soldier feedback. Our adversaries know this and have begun their own respective MUM-T journeys. And just as Hillary and Tenzing clawed their way to the top of Everest with soggy boots, we too must drive forward with our UGV effort while we enjoy relatively stable conditions in the world. Let us not wait for war to solve the problem. And should the veil of tranquility depart and we find ourselves at the precipice of a violent, engulfing global contact, the one question we do not want to ask ourselves is, “Why did we wait?” 


Via DVIDS

Friday, December 18, 2020

US Army Manned Unmanned Teaming (MUM-T) concept

This past summer at Fort Carson, Col., modified Bradley Fighting Vehicles, known as Mission Enabling Technologies Demonstrators, and modified M113 tracked armored personnel carriers, or Robotic Combat Vehicles, were used for the Soldier Operational Experimentation (SOE) Phase 1 to further develop learning objectives for the Manned Unmanned Teaming (MUM-T) concept.


Photo by Jerome Aliotta

Saturday, July 18, 2020

U.S. Army Releases Draft RFP for OMFV Preliminary Digital Design Phase

The U.S. Army issued a draft Request for Proposal (RFP) for the Optionally Manned Fighting Vehicle (OMFV) Preliminary Digital Design phase on July 17.

Raytheon/Rheinmetall Lynx Prototype


The draft RFP describes the transformational vision for OMFV, outlines broad performance specifications and characteristics, and places a great deal of emphasis on a squad-focused platform. It will gather additional industry feedback prior to the final RFP release for this phase later this year.

“As we continue to progress through the first phase of our five-phased approach for the OMFV program, communication, inclusive feedback and innovative thinking from industry remains key,” said Maj. Gen. Brian Cummings, the Army’s program executive officer for Ground Combat Systems. “We are looking forward to receiving feedback and learning from industry what’s in the realm of the possible as we continue to develop this truly transformational vehicle for our Soldiers.”

“Accurately defining the desired set of capabilities without over-constraining the design is critically important,” said Brig. Gen. Ross Coffman, director of the Next Generation Combat Vehicles Cross Functional Team (NGCV CFT). “The Army is committed to open communication with industry to ensure the characteristics and eventual requirements of the OMFV are informed by technological advances.”

The draft RFP will be open for feedback for 40 days, and the feedback received from industry will help shape additional industry engagements and ultimately the final RFP for this phase of the program. The final RFP for the Preliminary Digital Design phase is planned to result in the award of up to five contracts in June of 2021 under a full and open competition.

“We do not want to box industry into a solution,” said Cummings. “We want to incentivize industry as they lean forward and think creatively to bring the Army innovative technologies and solutions necessary to achieve our vision – both in terms of the ability to integrate newer technology we are seeing today and leaving space for future growth on the OMFV platform.”

As stated earlier this year, the Army is planning a five-phased approach to design, prototype, test and produce the OMFV. This approach focuses on encouraging innovation, maximizing competition throughout the entire program, and producing a transformational infantry fighting vehicle (IFV) that will dominate maneuver in Multi-Domain Operations (MDO).

U.S. Army OMFV Program

The Optionally Manned Fighting Vehicle (OMFV) program is seeking to replace the U.S. Army’s Bradley Fighting Vehicles (BFV).

The OMFV program is part of the larger Next Generation Combat Vehicles (NGCV) program. Other programs under NGCV are Armored Multi-Purpose Vehicle, or AMPV; Mobile Protected Firepower, or MPF; future robotic combat vehicles, or RCV; and the next-generation main battle tank.

The NGCV-OMFV will be designed to maneuver Soldiers in the future operating environment to a position of advantage to engage in close combat and deliver decisive lethality during the execution of combined arms maneuver. NGCV must exceed current capabilities while overmatching similar threat class systems.

The vehicle must have the following capabilities:

  • Optionally manned. It must have the ability to conduct remotely controlled operations while the crew is off platform.
  • Capacity. It should eventually operate with no more than two crewmen and possess sufficient volume under armor to carry at least six Soldiers.
  • Transportability. Two OMFVs should be transportable by one C-17 aircraft and be ready for combat within 15 minutes.
  • Dense urban terrain operations and mobility. Platforms should include the ability to super elevate weapons and simultaneously engage threats using main gun and an independent weapons system.
  • Protection. It must possess requisite protection to survive on the contemporary and future battlefield.
  • Growth. It will possess sufficient size, weight, architecture, power, and cooling for automotive and electrical purposes to meet all platform needs and allow for pre-planned product improvements.
  • Lethality. It should apply immediate, precise and decisively lethal extended range medium caliber, directed energy, and missile fires in day/night all-weather conditions, while moving and/or stationary against moving and/or stationary targets. The platform should allow for mounted, dismount, and unmanned system target handover.
  • Embedded Platform Training. It should have embedded training systems that have interoperability with the Synthetic Training Environment.
  • Sustainability. Industry should demonstrate innovations that achieve breakthroughs in power generation and management to achieve increased operational range and fuel efficiency; increased silent watch, part and component reliability, and significantly reduced sustainment burden.

Friday, April 24, 2020

Secretary of the Army, Hon. Ryan D. McCarthy in the General Dynamics factory

Secretary of the Army, Hon. Ryan D. McCarthy, and Vice Chief of Staff of the Army General Joseph M. Martin, visit General Dynamics in Detriot, Mi., April. 23, 2020. (U.S. Army photo by Sgt. James Harvey).

Here is the some interesting photos from visit:

Mobile Protected Firepower (MPF) 







Optionally Manned Fighting Vehicle (OMFV)



Optionally Manned Fighting Vehicle (OMFV) on background and an unknown UGV on front


Multi-Utility Tactical transport (MUTT)


Sunday, April 12, 2020

OMFV: US Army Revamps Bradley Replacement For Russian Front

Survivability in battle is priority No. 1. Transportability by aircraft? It’s been demoted to a subitem under priority No. 7. designs are due in 2023, physical prototypes in 2025, and operational vehicles by 2028.


  • The Ex-OMFV:
The Mission Enabling Technologies Demonstrator manned vehicle can operate two unmanned platforms to make contact with the enemy before soldiers do, while achieving overmatch against future operating environment threats. The Army’s vision includes three robotic vehicle variants—light, medium and large, but service officials have decided for now to cancel the acquisition of a medium variant. U.S. Army photo by Jerome Aliotta/Released 

WASHINGTON: Last night, with face-to-face meetings shut down by the COVID-19 coronavirus, the Army posted 14 pages of in-depth answers to industry’s questions about the rebooted Optionally Manned Fighting Vehicle program.

Just in case anyone didn’t understand just how thoroughly the Army has changed course, the document released yesterday spells it out: “No requirements from the first RFP [Request For Proposals] remain valid. This is a new RFP.”

The Army cancelled that first attempt at OMFV back in January when no bidder could meet its ambitious schedule and technical requirements. OMFV is meant to replace the Reagan-era M2 Bradley troop carrier with a “transformational” war machine boasting extensive automation, tactical networking, and other cutting-edge technologies.

A US Army M2 Bradley and Hungarian BTR-80s exercise in Lithuania. The BTR-80, like most European troop carriers, is much more lightly armed and armored than the Bradley.

Two critical details of the “programmatic narrative” stand out: the emphasis on survivability over transportability, and the more realistic demands on industry for both timeline and technology. The revised vehicle is now even more clearly focused on combatting the Russian threat in Eastern Europe.

For the first time, the Army put its nine desired “characteristics” for the OMFV in rank order.

Survivability beats transportability


For the first time, the Army unequivocally makes survivability the top priority, ahead of air transportability.

Now, that’s survivability against enemy Infantry Fighting Vehicles like the Russian BMP,-3 armed with anti-tank missiles and mid-calibre weapons, not against main battle tanks with 125 mm high-velocity cannon: “The OMFV must protect its crew and infantry from enemy IFVs,” the narrative states. But survivability is nevertheless central to the Bradley replacement’s mission statement (emphasis ours): “The OMFV will serve as the Army’s Infantry Fighting Vehicle (IFV) tasked to maneuver through the enemy’s disruption zone and deliver Soldiers to their dismount point unharmed.”

The new document even puts survivability (priority No. 1) slightly ahead of ground mobility (priority No. 2). While weight isn’t as big a factor on the ground as in the air, heavily armored vehicles over 50 tons – like the M1 Abrams main battle tank – can’t safely cross most bridges in Eastern Europe.

By contrast, the Army’s original Request For Proposals required two OMFVs to fit on a single Air Force C-17 jet transport. That meant they could be no heavier than a late-model Bradley, even though they were supposed to be much better armored.

The new document makes clear that, in the vast majority of both historical and projected conflicts, heavy armored units rarely move by plane. “The Army anticipates that Armored Brigade Combat Teams (ABCT) will continue to deploy primarily via water and rail, but must maintain the ability to transport via air as an option for commanders,” the programmatic narrative says. “The C-5 and C-17 will be the primary aircraft used to transport the OMFV.”

Two crucial pieces of context here. First, the C-5 is a much larger Air Force transport than the C-17, able to carry twice the load. Second, even though the C-17 is still an option, there’s nothing about fitting more than one OMFV aboard.

A single C-17 (right column) can carry 1 M1 Abrams main battle tank, two M2 Bradley infantry fighting vehicles, or three partially disassembled AH-64 Apache helicopters. A C-5 (left column) can carry twice as much. SOURCE: Lockheed Martin

Yes, the Army is giving up some strategic flexibility here. The service has struggled for eight decades to square the circle of an armored vehicle heavy enough to survive and light enough to transport by air. The resulting compromises ranged from partial successes to total failures: the little-used M22 Locust of World War II, the problematic M41 Walker Bulldog of the 1950s, the breakdown-prone M551 Sheridan used in Vietnam and Panama, the cancelled Future Combat System of the 2000s, and the ongoing Mobile Protected Firepower program.

But while the Air Force can fly a few tanks almost anywhere on short notice — which could be decisive against a lightly armed adversary — there just aren’t enough planes to deploy and supply multiple armored brigades, which is what you’d need against a foe like Russia.

Fortunately, while lightly armed adversaries could and do pop up unexpectedly around the world, we know exactly where Russia is and what countries its armored legions can reach. That’s why the US is prepositioning warehouses full of armored vehicles and other equipment in Europe.

We also know where China could strike, but the Western Pacific, with its scattered, rugged islands, is poor terrain for tanks. While the Army and Marines plan to deploy missile launchers on Pacific Islands, any Chinese landing force sent to dig them out would have to come by ship or plane, limiting the weapons it could bring.

If you know where the war you’re worried about will be, the best time to get there is before the shooting starts. By choosing to optimize the OMFV for Eastern Europe, rather than make it a jack-of-all trades for crises worldwide, the Army makes the program’s problems much more solvable.

More time, more money, more leeway for bidders


The tentative schedule released yesterday (above) starts with an extensive period of back-and-forth between industry and the Army, already underway, about what the new vehicle should look like.

  • A formal Request For Proposals based on these discussions won’t come out until April 2021.
  • In October 2021, the Army will kick off the first round of competition, picking up to five of those proposals it will pay industry to develop into “initial digital designs.” The Army will then evaluate those virtual vehicles in computer models and simulations.
  • In April 2023, the Army will narrow the field further, to at most three competitors, which will get government funding to refine their designs and build actual working prototypes by July 2025.
  • The Army will test those prototypes through 2026 and pick one winner in January 2027. The winning vehicle will Low-Rate Initial Production (LRIP) later that year, and a full battalion of OMFVs should be operational by September 2028.
By contrast, the original Request For Proposals, released in March 2019, demanded each bidder build a working vehicle at its own expense as and deliver this “bid sample” by Oct. 1st last year. Most potential manufacturers didn’t even try, and only one competitor, General Dynamics, managed to meet the deadline. Then the Army disqualified GD’s vehicle anyway for not meeting the (arguably impossible) requirement to combine heavy armor with air transportability.

This time around, “the Army is not requiring any bid samples prior to contract award,” yesterday’s release makes clear. “The Army is still drafting the M&S [Modeling & Simulation] test plan which may require vendors to build early surrogate platforms” (emphasis ours), but any “surrogate” will be only “a low-level mockup (e.g., digital, wood, etc.),” not anything nearly as expensive as an actual drivable vehicle.

By contrast, the original Request For Proposals, released in March 2019, demanded each bidder build a working vehicle at its own expense as and deliver this “bid sample” by Oct. 1st last year. Most potential manufacturers didn’t even try, and only one competitor, General Dynamics, managed to meet the deadline. Then the Army disqualified GD’s vehicle anyway for not meeting the (arguably impossible) requirement to combine heavy armor with air transportability.

This time around, “the Army is not requiring any bid samples prior to contract award,” yesterday’s release makes clear. “The Army is still drafting the M&S [Modeling & Simulation] test plan which may require vendors to build early surrogate platforms” (emphasis ours), but any “surrogate” will be only “a low-level mockup (e.g., digital, wood, etc.),” not anything nearly as expensive as an actual drivable vehicle.

As with air transportability, the Army is giving up something it wanted: time. While the original plan would have put operational OMFVs in a combat unit by 2026, the new schedule adds two more years. Fielding enough to fight the Russians in Eastern Europe will take even longer.

There is a strategic risk to not having the new vehicles in time. But there is an equal danger of taking on too much too fast — and failing. Then you might not get any new vehicles at all – which is what happened with the Army’s last two attempts to replace the Bradley, the Future Combat System and the Ground Combat Vehicle. The service can’t afford another failure, which means realism has to trump ambition.

That’s why yesterday’s release also doubles down on a key feature of the rebooted OMFV approach first outlined in February: Instead of requiring bidders to meet rigid technical requirements, which may or may not be feasible, the Army is laying out broad “characteristics” and asking industry how best to achieve them. (Those characteristics were first spelled out in February, but they weren’t explicitly put in order by priority until now). Only after years of dialogue, digital design work, and simulations show what’s really feasible does the Army plan to lock down technical requirements.

“The magic here is keeping broad characteristics and slowly refining them over time,” Army Futures Command’s director for armor modernization, Brig. Gen. Richard Ross Coffman, told me back in February. “We won’t lock requirements until we absolutely have to.”

Thursday, July 4, 2019

აშშ-ს არმიის რობოტიზირებული საბრძოლო მანქანების პროგრამა


აშშ-ს არმიის "სახმელეთო სისტემების საბრძოლო შესაძლებლობების განვითარების სამმართველოს ცენტრმა" (Combat Capabilities Development Command Ground Vehicle Systems Center -  CCDC GVSC) სატრანსპორტო საშუალებების ტექნოლოგიის დემონსტრატორის ამბიციური პროექტ (Mission Enabler Technologies-Demonstrator-ის (MET-D) პრეზენტაცია განახორციელა. ტექნოლოგიების დემონსტრატორი M113-ისა ქსმ Bradley-ს ბაზაზე შექმნილ რობოტიზირებული საბრძოლო მანქანების სახით იქნა წარმოდგენილი.



დემონსტრატორში გამოყენებულია კამერების, გამოსახულების ასახვის, სამომხმარებლო გრაფიკული ინტერფეისი და ინფორმაციის კაბელით გადაცემის უახლესი ტექნოლოგიები, რომლის საშუალებითაც შესაძლებელია გამოსახულების უპილოტო საფრენი აპარატებიდან მიღება და მეწინავე საკომუნიკაციო საშუალებებში ინტეგრირება. ეს ყველაფერი ქვეითებისთვის ბრძოლის ველის უკეთესი გათვითცნობიერებისა და საკომუნიკაციო შესაძლებლობების გასაუმჯობესებლად იქნება გამოყენებული.


პროგრამა, სახელწოდებით NGCV (Next Generation Combat Vehicle - ახალი თაობის საბრძოლო მანქანა) ოფიციალურად 2018 წლის ივნისში დაიწყო. 2018 წლის ოქტომბერში პროგრამას სახელი შეუცვალეს და მას OMFV (Optionally Manned Fighting Vehicle - ოფციონალურად მართვადი საბრძოლო მანქანა) ეწოდა, დაემატა სხვა პროგრამებიც და მთლიანობაშუ NGCV-ს პროგრამის სახელის ქვეშ გაერთიანდა. ახალი NGCV პროგრამის ფარგლებში დაგეგმილია შემდეგი სახის მანქანების შექმნა:


  • ოფციონალურად მართვადი საბრძოლო მანქანა (Optionally Manned Fighting Vehicle - OMFV) - ქსმ M-2 Bradley-ს შემცვლელი.
  • მრავალფუნქციური ჯავშანმანქანა (Armored Multi-Purpose Vehicle - AMPV) - ჯტრ M-113-ის შემცვლელი.
  • მობილური დაცული საცეცხლე მანქანა (Mobile Protected Firepower - MPF).
  • ქვეითთა საბრიგადო საბრძოლო ჯგუფებისთვის (IBCT) განკუთვნილი მსუბუქი ტანკები.
  • რობოტული საბრძოლო მანქანები (Robotic Combat Vehicles - RCV) სამ ვარიანტად: პირველი ვარიანტი, ეგრეთ წოდებული RCV-Light, იქნება შვიდი ტონის ფარგლებში და აღჭურვილი იქნება სენსორების კომპლექტით, რომელიც მანქანას ცეცხლის წარმოების საშუალებას მისცემს. მეორე ვარიანტი, RCV-Medium, ათი ტონის ფარგლებში იქნება და აღჭურვილი იქნება საშუალო კალიბრის ქვემეხითა და ტსმრ-ით, ხოლო მესამე და ყველაზე მძიმე მანქანა, RCV-Heavy, ოც ტონას აიწონის და საშუალება ექნება განახორციელოს პირდაპირი საცეცხლე დარტყმები (სავარაუდოდ საუბარია თანამდეროვე სატანკო ქვემეხის ანალოგზე).
  • გადამწყვეტი გამანადგურებელი დარტყმის პლატოფრმა (Decisive Lethality Platform - DLP) - ტანკ M-1 Abrams-ის შემცვლელი.
რობოტიზირებული საბრძოლო მანქანების სამი ვარიანტი (მსუბუქი, საშუალო და მძიმე)


RCV დანიშნულებას მოდულური მისიების მხარდაჭერა წარმოადგენს და ის მეთაურს საშუალებას აძლევს მოახდინოს მანქანის შესაძლებლობების ადაპტირება ყველა კონკრეტული მისიისთვის. ტექნოლოგიების განვითარება საბრძოლო მანქანის დისტანციურად მართვის და მისი სხვა უპილოტო საბრძოლო მანქანებთან მიერთების საშუალებას იძლევა. ერთ პილოტირებად მანქანას შესაძლებლობა ექნება მართოს ერთიდან ოთხამდე უპილოტო საბრძოლო მანქანა RCV. მანქანების ჯგუფის მართვა რადიოკავშირით განხორციელდება. პროექტის განვითარების მაღალ დონეზე მანქანები სრულიად ავტონომიურად იმოქმედებენ, ამისათვის მათ ხელოვნური ინტელექტი და ნეირონული ქსელები დასჭირდებათ - რაც ჯერ-ჯერობით მიუღწევადია, მაგრამ უკვე განვითარების ჰორიზნტზეა.


წყარო: