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
A LOOK BACK, AND AHEAD


Gary L. Winkler, an Army civilian for 23 years culminating in 3½ years as the leader of PEO EIS, saw dramatic changes in his career, and wished some other changes had been more dramatic than they were.


Army AL&T Magazine on April 27, in his last week as PEO, to share his perspectives on where the Army stands in today’s com- puting environment and in the ongoing efforts to do more without more while building a robust Acquisition, Logistics, and Technology Workforce.


W


PEO EIS’ mission is to design, develop, integrate, test, and field new network- based capabilities by leveraging commer- cial hardware and software solutions in finance, logistics, personnel, communica- tions infrastructure, biometrics, medical, and warfighting functions.


PEO EIS typically is the “first in” to a the- ater of operations, to set up IT systems before troops arrive. Its portfolio is broad and diverse. Most of its large-scale systems support the generating force, although some of its systems, such as DOD Bio- metrics and Medical Communications for


inkler, who stepped down at the end of April to join the private sector, sat down with


Combat Casualty Care, support the oper- ating force.


Winkler has seen DOD budgets wax and wane, and grappled with how best to make programs more efficient while ensuring top-notch service to the warfighter.


AN IT TRANSFORMATION


“It’s been amazing to be part of the Army and DOD transformation to a net-centric, knowledge-based force,” Winkler said.


“Earlier in my career, there were only mainframes and punch cards, and then we moved into the PC and workstation environment. Then it was client-server applications, which only worked for local networks. Now we have global enterprise systems that are web-based, and most sys- tems are accessible through ‘the cloud.’ Cloud computing is now in play as the next evolution of server consolidation.”


Over the next three to five years, the Army and DOD will be challenged to get applications into secure cloud


THERE ARE ALWAYS EFFICIENCIES TO BE GAINED WHEN PEOPLE ARE FORCED TO BE CREATIVE, AND I’M CONFIDENT THE PEO AND PMS WILL RISE TO


THE CHALLENGE.” 44 Army AL&T Magazine


computing environments where they can function on smartphones and tablets, Winkler said.


“Without a doubt, network and informa- tion security will be the biggest challenge as we move to integrate commercial data centers, aka cloud environments, and commercial software-as-a-service into our operations and capabilities.”


Software-as-a-service is a rapidly growing sector in private industry, taking busi- ness functions that can easily be treated as commodities—such as email, calen- dars, contacts, and tasks—and leveraging massive economies of scale to lower costs while meeting capability requirements.


“There is not much risk in buying such capabilities this way,” Winkler said, although there is risk with complex func- tions and capabilities, which are not appropriate for outsourcing to software- as-a-service vendors.


MANAGING RISK


“I had hoped to be able to move the Army forward a little faster in the mobile smart- phone area,” Winkler said in reviewing his tenure as PEO. “We have [security] solutions in place, but the processes to get those solutions approved are cumbersome and time-consuming, as always with any- thing new.”


The Army and DOD are behind the curve in addressing security concerns with commercial technology, Winkler said. “It’s not that there is necessarily a huge security risk or vulnerability with commercial technology, but rather we need to develop policies and processes to assess and manage risk.”





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