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
MOBILE MAPPER


  


Development of the MPLAF will also allow the live training domain to syn- chronize


the road map between the


current LT2 product line and the mobile devices. The MPLAF will provide the architectural framework and standards for SOA (Training as a Service) and cloud computing solutions.


The ability to implement SOA and cloud- based services will extend the functional reach of the LT2 Family of Training Sys- tems, as well as provide mechanisms to lower life-cycle operational and sustain- ment costs. By centralizing the services and abstracting the processing, less man- power will be required to operate and sustain each system, as common func- tions could be run from a remote facility for all training applications.


CONCLUSION The key to ensuring a positive ROI with respect to the MPLAF lies in the early implementation of


the construct, as


well as early implementation of lessons learned. Therefore, it is incumbent not only to develop the MPLAF based on best practices, but also to temper these with concrete lessons learned.


It is very tempting to move forward with mobile applications as if they were dispos- able. However, given tighter budgets, it is imperative that we implement a sound product-line approach for mobile applica- tions and devices, and focus resources on product-line development and advance- ment that promote the systematic reuse of common assets and capabilities.


For more information, portal.org.


go to www.lt2


with Urban Operations. Morhack holds a B.S. in computer science from the Uni- versity of Central Florida and a B.B.A. in marketing from Stetson University.


JAMES TODD is the Lead Systems Engi- neer and Architect for the Future Army System of Integrated Targets at PEO STRI, and a Senior Systems Engineer for the LT2 product line. Todd holds a B.S in mechani- cal engineering from the University of New Orleans and an M.S. in industrial engineer- ing from Texas A&M University.


ANDREA MORHACK is a Systems Engi- neer for the Target Modernization program within PM TRADE at PEO STRI. She has more than nine years’ experience working in DOD acquisition associated


DR. JEREMY T. LANMAN is the lead systems architect for PEO STRI’s Common Training Instrumentation Architecture and Consolidated Product-Line Management construct, supporting the LT2 Family of Training Systems. Lanman holds a B.S. in computer science from Butler University, an M.S. in software engineering from Embry- Riddle Aeronautical University, and a Ph.D. in modeling and simulation from the University of Central Florida.


ASC.ARMY.MIL 27


ACQUISITION


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