TWI “is good for breaking down com- munication barriers between government and industry.”
What will never break down, however, is the reality that industry must make a profit to continue operating and providing services to the government, whereas Army policy- and decision-making are driven by available public funding, matched against mission requirements.
REQUIREMENTS EYE-OPENER It was at the nitty-gritty level that Ramsey found the most fertile ground for learning at Lockheed Martin. “I’d worked with requirements before in the military, but I didn’t really understand them,” Ramsey said. “Everything pretty much stems from requirements, and you kind of know that when you’re on the Army side, but I got to see it from a different perspective … how if you’re not careful, those requirements can get out of control. … I didn’t look at it like this before.”
Each requirements change translates to a specific course of action. Specifically, Ramsey saw how many hours and how much money a seemingly minor design change could cost when a key player in an Army program management office requested the change after the require- ments had been thoroughly discussed and the issues resolved. “I couldn’t believe the Army was making a real small change to what was already agreed upon [and] that really wouldn’t affect the design but was going to change the cost.
“Requirements can change, and will change, over
time,” and the program
managers for the Army and Lockheed Martin worked through the design change, Ramsey said. “But if you’ve got requirements that you and the customer agreed to … you don’t go back and waste man-hours and people.”
WALKING HIM THROUGH Ramsey, left, and Behling discuss live, virtual and constructive training between meetings at Lock- heed Martin’s Orlando facility. (Photo by Gary Wilcox, Lockheed Martin Corp.)
BUILDING BLOCKS Ramsey and Behling developed a give- and-take that both said made the TWI experience more fruitful. For Behling, who joined Lockheed Martin in 2009 just after retiring from the Air Force, the TWI program was a new assignment, and Ramsey his first TWI officer.
“When you have somebody here, in house, you’re seeing the face, you’re seeing some- body daily. You build a different kind of relationship. Jeff and I, we have very open discussions. We’ll have teleconferences with government, and I’ll just look over at Jeff: ‘You understand, you see what’s going on here. We’ve got to do this better.’
Ramsey “shadowed” Behling for much of his TWI assignment, but did not remain in the shadows, which underscores a key point of advice from Ramsey and Beh- ling for acquisition officers entering the TWI program: Don’t sit on the sidelines.
“It’s not a classroom environment,” Beh- ling said. “You’re not coming in here to sit and watch. You’re coming in here to work. Te first thing I would tell them is, do a little homework. Come to the
assignment with a list of things you want to work on, a list of government-industry issues to resolve.”
Ramsey agreed. “Do what you can do, what they’ll allow you to do, and just absorb all that information, and go out there and do it!” he said.
Ramsey, who marked 20 years of Army service in February, plans to stay in as long as he can, beyond just the addi- tional three-year service obligation that comes with a TWI assignment. He is confident that his TWI experience will help, starting with his follow-on assign- ment in contracting.
“I think it gives me a new perspective on how the defense contractor thinks. … It will help just because I can see how they put together their proposals … how they answer those questions that the Depart- ment of the Army is looking for. So when I write the statement of work as the contracting officer, I can better put it in plain English for them to understand as well as me.”
—MS. MARGARET C. ROTH
ASC.ARMY.MIL 137
WORKFORCE
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