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
paying the upfront cost for the technical data rights did not seem justified; there was simply no intention to sustain the sys- tem long term. However, other programs in planning stages should err on the side of caution when making this decision, and favor paying the cost of procuring the data rights from the outset if a reasonable likelihood exists that


the program will ever be extended into sustainment.


Because it does not have the data rights for CSS VSAT, the Army is limited to purchasing replacement parts through the original


equipment manufacturer.


No competition exists among vendors, and the government cannot reverse- engineer comparable parts.


Te Better Buying Power (BBP) tenet of promoting effective competition, first outlined in BBP 1.0 and continued in BBP 2.0 and now 3.0, underscores the importance


BETTER LATE THAN NEVER SPC Matthew J. Cavey, left, of the 4th Battalion, 3rd U.S. Infantry Regiment (The Old Guard) and SGT Benford J. Holland of the Alabama Army National Guard simulate troubleshooting a CSS VSAT system error during the logistics demonstration. The demonstration was completed in July 2015—unusual timing for a product that was fielded a decade ago and has since supported military and humanitarian efforts around the world. (Photo by Jeff Wright, PM DCATS)


of planning the procure-


ment of data rights early in the product life cycle to leverage competition. Expe- rience confirms the importance of this initiative. For rapid fielding programs, an intellectual property plan that includes procuring data rights must consider— and weigh heavily—the likelihood of extended contingency operations.


GET THE TECHNICAL MANUAL With the data rights now too expensive to procure for CSS VSAT, the government has spent substantial time and money to produce a technical manual for the system from scratch. Tis leads to the sec- ond lesson learned: If the program might transition to organic sustainment at any point in the future, build the technical manual into the original contract.


While the system was in development, the CSS VSAT contractor


did not


produce a technical manual for the gov- ernment. Only now are the contractors


who support the system developing a technical manual based on their years of experience in the field. System developers generally possess a more intimate knowl- edge of the system as a whole and should be able to produce a detailed technical manual more readily than the field engi- neers who have been involved only with maintaining it.


Relying on field engineers’ expertise will produce a high-quality manual but will greatly lengthen the process because it requires translating hands-on, trial-and- error approaches to diagnose and repair failures and convert that information into reliable, step-by-step instructions that Soldiers can use in the field. Tis delays the entire transition of the system to CECOM sustainment.


Validation and verification of the CSS VSAT


technical manual will take


more than a year and stretch into FY17, representing the longest piece of the tran- sition process. Validation and verification events require page-by-page scrutiny of


the manual by the system’s proponent, CASCOM, working with the program office to confirm the accuracy and clar- ity of every step, every word and every National Stock Number. Te time and costs associated with this roundabout way of developing a technical manual should provide a cautionary tale for other rapid fielding initiatives. Upfront procurement of the technical manual, as with data rights, enables industry competition and ultimately provides the government with a better price.


CONCLUSION As CSS VSAT approaches readiness for organic sustainment, the lessons brought to light in that transition are already a consideration in planning for the next iteration of


CASCOM, HQDA G-4’s U.S. Army Logistics Innovation Agency and end users are capturing requirements that will expand the role of CSS VSAT to carry more enterprise resource planning systems and more maintenance data in the program’s next generation.


ASC.ARMY.MIL 29


the capability. PL DWTS,


LOGISTICS


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  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203