search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
RESPONSIBLE SPEED


through a family of long-, medium- and short-range unmanned systems designed to be deployed from the ground and air.


Te LRPM MTA-RP commenced with responsible speed in July 2024, follow- ing a series of acquisition shaping panels and a program initiation brief to the Hon. Douglas R. Bush, then assistant secretary of the Army for acquisition, logistics and technology (ASA(ALT)) and the Army Acquisition Executive (AAE). Bush desig- nated LRPM as an MTA-RP program and charged the Program Executive Office for Missiles and Space (PEO MS) with deci- sion authority and developing, procuring and testing this new lethal munition concept.


Te MTA pathway provides a unique opportunity to fast-track LRPM prototyp- ing and integrating emerging technologies. The MTA-RP framework minimizes bureaucratic hurdles, enables agile deci- sion-making and supports operational employment quickly. By rapidly prototyp- ing and demonstrating the capability in an operational environment, the Army can make an informed decision on the suitabil- ity of the materiel solution. A prescribed five-year MTA authority ensures accel- erated timelines to assess solutions to immediate capability gaps, while simul- taneously providing insights for further refinement on subsequent variants and iterations.


EXECUTING RESPONSIBLE SPEED In December 2024, the LRPM MTA-RP Decision Authority, Maj. Gen. Frank J. Lozano, PEO MS, established the baseline LRPM hardware configuration comprised of an Anduril Altius A700M air-vehicle and multiple science and technology (S&T) initiatives from the Army Combat Capabilities Development Command’s (DEVCOM) Aviation and Missile Center


64 Army AL&T Magazine Spring 2025


(AvMC). Te DEVCOM AvMC S&T initiatives included in the LRPM are the Multiple Simultaneous Engagement Technologies and Precision Target Acquisition Seeker software capabilities, a seeker and guidance section collectively developed


by Hood Technology


Corporation and DEVCOM AvMC and a DEVCOM AvMC-developed combined effects warhead. Tis configuration of the LRPM will undergo safety and suitability testing and be employed in follow-on ground and air-based operational demonstrations to inform production and deployment decisions.


In keeping with the themes of “responsible speed” and accountability, agile develop- ment and foundations for transition, there are various examples of functional appli- cation in the LRPM MTA-R.


ADAPTING TO RESPONSIVE REQUIREMENTS An Abbreviated Capability Development Document (A-CDD) is a streamlined version of the traditional Capabilities Development Document that outlines essential performance requirements, operational needs and intended use of a system or capability in a concise manner. Tis abbreviated structure allows flexibility among the requirements, user and materiel developer communities to achieve a desired capability quickly, while informing the requirements community of what is possible. The A-CDD supporting the LRPM program is in evolution as lessons learned from ongoing conflicts improve understanding of what is necessary to develop a combat-effective system on a modern battlefield.


Tere is a natural conflict between an evolving A-CDD responding to battlefield realities and the stringent requirements necessary to place explosive munitions in the hands of Soldiers. Qualifying and


testing a munition requires extensive and often sequential tests to ensure safety and reliability. In addition to ensuring safety validation requirements, LRPM is responsible for integrating emerging tech- nologies to address the demands of the evolving battlespace. However, adoption of these technologies introduces risks to cost, schedule and performance. A criti- cal aspect of this process is determining when to execute a branch plan to mitigate risk associated with long-lead requirements and ensure timely delivery of the LRPM to operational units.


“GOOD IDEA CUT-OFF” POINTS Te LRPM program must have a plan to integrate (or defer to a future LRPM version) the capabilities being developed for the LE enterprise (e.g., a multi-use air and ground launcher solution and a universal command and control system). Lozano directed the program to identify “good idea cut-off” (GICO) points. Essen- tially, to meet the constraints of the MTA timeline, the LRPM program must have off-ramps and alternatives if any of the LE-enabling capabilities are not mature enough to support the LRPM timeline. Te LRPM program backward planned from mandated operational demonstra- tion dates to identify the “no later than” points, which the LRPM must have access to properly incorporate and test.


Te resultant product is a programmatic plan that incorporates GICO decision points with alternate paths to successfully execute. Te program maintains active stakeholder engagement to understand the planned inclusion of emerging technolo- gies and LRPM’s plan to incorporate the technologies in a future version. Active, transparent communication with stake- holders on current program status falls in the box of “must do” to achieve and main- tain responsible speed.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112