GFEBS FINDS ITS SEA LEGS
Moving Navy BUMED from legacy systems to GFEBS was not a “light switch” event. Te Army deployed roadshow teams comprising five IBM staffers; Alaimalo as the GFEBS project lead; representatives from the functional organization, the Office of the Assistant Secretary of Defense for Health Affairs; and a BUMED tran- sition team of experts familiar with both the old Navy system and the new Army platform.
A comprehensive team of stakeholders is part of every GFEBS implementation.
Scott Wardell is director for Health Affairs, the proponent organization for the BUMED deployment of GFEBS. Wardell oversaw a team of experts who assisted in the coordination of the road- show development. Health Affairs bridged the gap between “as is” and “to be.”
“Te roadshow team has their boots on the ground and visits each site,” said Alaimalo. “It’s an important part of the deployment where end users can meet with the folks who have the subject matter expertise. All stakeholders—IBM, Health Affairs, GFEBS and the BUMED transi- tion team—all have a piece of it and own the success.”
“It was like a whole new language,” said John Day, deputy comptroller for Naval Health Clinic Annapolis. “It helped having people there who spoke both languages—Navy and Army—so that we could better understand the language we were learning.” Te roadshows included training, transactional simulations and role-playing to define the various user roles. “Te training was very good,” said Day. “It wasn’t like typical military train- ing where you have to click through slides. You actually had to pay attention and do some transactions.”
GETTING TO GREEN Tere are many different user roles within GFEBS. Data entry, inventory, cost management, reconciliation and analy- sis are just a few. To bridge the language gap between Army and Navy, roadshows focused on identifying how each person at the Navy’s military treatment facili- ties would use GFEBS to perform their daily duties. “We gave out initial role
assignments and quickly realized we gave some people too much access—others not enough—and had to dial that back a bit,” said Day.
Every role assigned during the roadshow incorporates associated training that must be completed by the user before access- ing GFEBS. “We monitor the metrics of these users as they prepare for GFEBS,”
A LOOK INSIDE
The GFEBS software captures and records financial transactions on a single, worldwide platform, eliminating the need for data reentry. It is built on SAP commercial off-the-shelf software, and complies with statutory and regulatory requirements for funds control and accounting. (Image courtesy of PEO EIS)
56
Army AL&T Magazine
Fall 2020
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
