search.noResults

search.searching

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
The art of acquisition lies partially in


avoiding the elevation of new products or systems to major defense acquisition program status whenever possible.


ACAT III radio product from a milestone C decision out to testing in two weeks. Te entire process from milestone C to successful, full-rate production decision took just seven months.


Remember: Be creative in how you tailor a program. For example, to deliver capa- bility more rapidly,


if possible leverage


DOD 5000.02 Enclosure 13, a provision that allows for reduced acquisition time- lines based on urgent operational need. Te EMC program office leveraged this approach and was able to deliver capabil- ity in two years.


Challenge convention and use nonstan- dard programs of record to accelerate the process where applicable. Tis approach gets capability into the hands of Soldiers rapidly while creatively meeting acqui- sition requirements and staying ahead of obsolescence. Get away from unique capabilities or designs where possible. In a previous assignment as an assistant


product manager in the PEO for Enter- prise Information Systems, I led a team that standardized strategic network architecture for long-haul communica- tions by putting the engineering up front and standardizing the product selections on the back end, the reverse of traditional approaches.


Car manufacturers know there is no sense in doing a custom design for each new vehicle. Similarly,


this concept worked


well for the Army in the delivery of modular network capabilities that con- nected countries across Southwest Asia. Te concept is repeatable and can apply to any network by figuring out capability based on mission and scale and address- ing it with basic configurations such as mini, small, medium or large, then work- ing out the engineering in advance with room for à la carte, Lego-like additions. At that point, a commander simply needs to select a scalable package that best fits his or her situation.


TESTING Tough it sounds simple, think through the test strategy early in the process, well before testing begins. Ensure that testing is done in accordance with the require- ments and does not extend into other factors outside of what is actually needed, adding little additional value. Make Sol- diers, the end users, part of the process early and grow capability through user feedback in both laboratory and opera- tional environments, to improve products using a test, fix, test approach. Don’t be afraid to find problems.


Also, do not be afraid to use capabilities and limitations reports or operational assessments in lieu of formal testing where applicable. When a formal test is required, partner with the test com- munity early and leverage development tests or operational assessments with


Soldiers in conjunction with the testers to eliminate surprise and reduce overall test risk. Remember to leverage teams and relationships by working closely with the requirements generators as well as the test community. Testers want to see the best capabilities get into Soldiers’ hands, and are typically willing to work with a product office to help move the ball down the field.


CONCLUSION A little creativity and innovation can speed acquisition timelines, and despite recent news headlines, we as a community have been doing just that. DOD 5000.02 provides the authority to tailor the pro- cess, cut through bureaucracy, think holistically while leveraging relationships and apply creativity to get to “yes.” Rapid acquisition is real and can flourish with a little bit of innovative thinking.


For more information, go to the PEO C3T website at http://peoc3t.army.mil/c3t/ or contact the PEO C3T Public Affairs Office at 443-395-6489 or usarmy.APG.peo- c3t.mbx.pao-peoc3t@mail.mil.


LT. COL. MARK P. HENDERSON is the product manager for Network Modernization, assigned to PEO C3T’s Project Manager for Tactical Network. He holds an executive MBA with emphasis in information systems management and a master of education with emphasis in counseling and psychology from Troy University, and a B.S. in political science and government from Kennesaw State University. He is Level III certified in program management and holds master’s certificates in Lean Six Sigma, negotiations, expert selling, applied program management and advanced program management. He is a member of the Army Acquisition Corps.


HTTPS: / /ASC.ARMY.MIL


147


COMMENTARY


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  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168