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
COMMENTARY


of fifth-generation fighter aircraft. While Boeing is still build- ing older, fourth-generation F-15 and F-18 aircraft, Lockheed, with a trained workforce and already-developed intellectual property and software, is uniquely positioned to be ready for a sixth-generation program should one develop. RFPs for these generational-type systems are often designated as must-wins for a company because a loss has such far-reaching potential busi- ness effects. Must-win proposals have virtually unlimited budgets and are carefully managed. (Whether this is a good thing for the government is another column.)


Te proposal manager backward-plans a proposed delivery sched- ule based on the submission due date. Planning estimates are measured by the individual writer in pages, by section, by day. Proposal sections are combined to construct volumes (or books) with the overall number of pages set by Section L of the RFP. (Section L is the part of the RFP that contains instructions, condi- tions and notices to offerors or respondents.) Given the relatively short turnaround time between RFP release and submission of proposals, actual solution development must start early in the pre-RFP process. RFP turnaround times are measured in weeks, or maybe a month or two.


Solution development is executed like an actual project, only accelerated. Costs and schedules must be estimated. Risk assess- ments are ongoing. Proposal team members are gearing up for 12- to 16-hour days to stay on schedule. Te crunch can be even worse when the government releases an RFP shortly before a major holiday.


WRITING THE FIRST (AND THE SECOND AND THIRD ... ) DRAFTS Writing the proposal is the nuts and bolts of developing it. Experts across the proposal sections are sequestered in the proposal devel- opment center or another dedicated space so they can focus on the writing as well as collaborate with other team members. Speed is of the essence. Bigger, more complex proposals often require people from outside the central organization to join the team, which complicates this process.


Four key metrics drive industry: orders, sales, EBIT and cash.


Key initial activities include developing and approving story- boards and identifying graphics, while always checking the rules in Section L of the RFP. Te prime directive for the team at this point is to get something on paper for editing and revisions, and the pressure is significant. Everyone knows that the best propos- als, much like academic work, come from constant revision.


Short timelines, tension and the complexity of answering RFPs often cause real problems on a team. I have worked on proposal teams where we had to physically separate engineers after disagreements on the finer points of the technology. An oft- repeated phrase around the proposal center goes, “Tell them what they (the government) want to hear—not what you want to tell them.” Tat is harder to do than it sounds. Hours turn into days into weeks and so on. For the many people writing a proposal, their world becomes focused on two things: writing deliverables and making sure these products conform precisely to require- ments stated in the RFP.


QUALITY CONTROL AND A METRIC FOR PROGRESS Whatever the differences among different companies’ proposal processes, most use a series of reviews, generically referred to as color teams, because of their designation. Part of the planning process is establishing and scheduling the color teams. While varying from company to company, teams execute a series of events shown in Table 1, Page 142.


A Red Team review is the big event for proposal developers. It is a complete review of the technical and management volumes from the government evaluator’s perspective. Te Red Team simulates the government evaluation board process as best it can, and its end state is the identification of issues the team believes require improvement. Once the proposal has gotten past the Red Team, the pressure to get it fixed, completed and out the door drives everything the proposal manager does.


DELIVERED, AT LAST Te last step (which is actually a series of steps) before a proposal can be delivered is to gain the necessary internal approvals. Te approvals range from the technical solution to the cost. Most proposal managers engage the company leadership throughout the process because no one wants to be surprised.


While the proposal manager is finalizing the proposal, functional managers are meeting with the company president or their busi- ness unit brass for final approvals. If the proposal manager is lucky, this last approval meeting occurs well before the required


https://asc.ar my.mil 145


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