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
TWENTY-FIRST CENTURY APPROACH TO ACQUISITION


upon perfect predictions many years in advance of application by Soldiers. Vehicle requirements became fluid as operating environ- ment conditions changed or new requirements were added late in lengthy development cycles, causing cost projections to skyrocket.


Past efforts to develop a new infantry fighting vehicle to replace the Bradley in our armored brigade combat teams did not come to fruition. Tose efforts are well-documented elsewhere and do not need to be re-hashed here. What is important to note is that the Army is a learning organization. We learned from our past efforts and modified our approach to developing combat vehicles. With OMFV, the opportunity to change the historical dynamic is available thanks to more flexible and modern program manage- ment tools such as the middle tier of acquisition pathway and digital engineering.


THE RIGHT BALANCE Using these tools, the Next-Generation Combat Vehicle Cross- Functional Team, the Project Manager for Mounted Combat Systems and the Ground Vehicle Systems Center crafted an approach to OMFV requirements development and refinement incorporating several key themes:


Communicating broad design characteristics for industry to focus their design capabilities and innovation on addressing our capability gaps, rather than requiring compliance with overly technical requirements, based on imperfect assumptions or legacy approaches. Te Army awarded contracts to five prime vendors to develop digital designs for the specific purpose of informing and maturing initial characteristics into more detailed require- ments. Te nine “characteristics of need,” in priority order, are: survivability, mobility, growth, lethality, weight, logistics, transportability, manning and training. In each of those nine areas, the Army challenged vendors to provide their best over- all solution.


Collaborative, rather than transactional engagements between government and industry. Tis approach allows government and industry to come together to a common under- standing of what technology is ready and affordable today vs. what is not yet ready for integration at scale and operational


implementation. Initially, some vendors were skeptical that the Army was serious about change, but close collaboration and open dialogue produced productive refinement of requirements. Model-based systems engineering and modular open system architecture standards enabled use of competing vendor concepts and digital designs to explore different approaches to the right balance between the needs for mobility, survivability, lethality, and, since this is an infantry fighting vehicle, how many Soldiers can feasibly be delivered safely onto an objective.


Requirements analysis and definition. Over a period of 12 months with five vendor digital designs, the Army completed 11 distinct analytical efforts—ranging from fuel consumption expectations to survivability against known threats. Trough these efforts, the Army provided vendors four revisions of draft performance specifications, received over 2,000 comments from government and industry technical experts, conducted three digi- tal design reviews with each vendor, and had four total months of Soldier touch points providing user feedback on vendor designs.


Modeling and simulation. Vendor digital designs assessed through government modeling and simulation tools refined the nine broad characteristics of need into 28 detailed and prioritized attributes. We were able to see, question and understand rela- tionships between performance and cost across engineering and operational expectations well before committing to expensive, long lead physical prototypes. By placing Soldiers into virtual OMFVs, the Army was able to determine if the vehicle designs were realistic and feasible. We were able to run extensive simula- tions to explore the impacts of different decisions and proposals to determine if our requirement prioritization is correct.


Soldier centered design. Soldiers from Armored brigade combat teams engaged directly with virtual designs, and later with virtual prototypes and physical models. Te Ground Vehi- cle Systems Center created virtual environments for Soldiers to experience each vendor’s approach. Soldiers directly helped engi- neers and designers understand how human performance with new capabilities and design requirements influence desired system effectiveness objectives. Te value of gaining these Soldier inputs early in the process cannot be overemphasized.


“This approach brings a stability of requirements to the process—nobody has to guess what the requirements will be.”


34 Army AL&T Magazine Fall 2022


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  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148