LOGISTICS
SPOTLIGHT MAJ JAMES A. “TONY” LINDH II
Combining different viewpoints for better analytics MAJ JAMES A. “TONY” LINDH II
COMMAND/ORGANIZATION: Project Manager for Army Enterprise Systems Integration Program, Program Executive Office Enterprise Information Systems (PEO EIS)
POSITION AND OFFICIAL TITLE: Assistant project manager, Army centralized business analytics
YEARS OF SERVICE:
4 years in the workforce, 14 years of military service
AWARDS:
Bronze Star Medal, Meritorious Service Medal, Army Commendation Medal, Army Achievement Medal, Meritorious Unit Commendation, National Defense Service Medal, Iraq Campaign Medal Campaign Stars, Global War on Terror Expeditionary Medal, Global War on Terror Service Medal, Army Service Rib- bon, Overseas Service Ribbon, Combat Action Badge, Parachutist Badge, Para- chute Rigger Badge
EDUCATION:
M.S. in project management, University of Alaska Anchorage; B.S. in biomedi- cal sciences, Montana State University – Bozeman
M
AJ James “Tony” Lindh II might be part of the acquisition workforce, but “technically, I am
and will always be an Army logistician,” he said.
Lindh started his logistics career as a quar- termaster officer at Fort Hood, TX, and has since served as a supply platoon leader, a supply and services officer, a security and plans officer, and the deputy in a support operations shop. He served in Iraq as a bat- talion S4 (essentially a battalion’s logistics officer), a material readiness officer and a field maintenance company commander, and was most recently a rear detachment commander before moving to acquisition four years ago.
He’s now the assistant project manager under the product director (PD) for the Army Enterprise Systems Integration Program (AESIP) Hub and is
leading
the Army Centralized Business Analyt- ics (ACBA) project. “PD AESIP Hub is building out the ACBA to aggregate data from multiple enterprise resource planning [ERP] and non-ERP systems, as well as business warehouse systems,
into a single environment for enterprise reporting and dashboards,” he explained,
“allowing users a streamlined, cross- program view of data from a single access portal.”
His biggest challenge? “Communicat-
ing with our numerous stakeholders in order to refine requirements to the point where my developers can build the best product to exceed expectations,” he said.
“We have to bridge the gap between the technical—software and reporting tech- nology tools—and functional. Tis is similar to many other projects, but our gap is unique in that functional folks can’t rely on their years and years of leg- acy knowledge to give us requirements. Tey are developing and learning a new way of doing business at the same time they learn new software.”
Tat work has its payoffs, Lindh said.
“Te biggest reward is working with the large breadth of stakeholders from mul- tiple domains and agencies, from AMC [U.S. Army Materiel Command] to DA G-3, in order to build their under- standing of the ERPs and the reporting technology in SAP Business Objects
32
Army AL&T Magazine
October–December 2014
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
