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
INDUSTRY DAY OPENS DOORS


be made for that block of time where there could be an open forum for any interested party, member or not. Tis would allow ARDEC and PM CCS to announce the event to the public through FedBizOps and give DOTC and NAC an opportunity to engage prospective new members. Many prospective participants would already be on site, reducing travel costs and providing an incentive to stick around and learn about the emerging requirements when they may not oth- erwise have been interested enough to make the trip.


ARDEC and the DOTC agreed on an event format that would achieve the two primary goals and result in everyone walking away with more knowledge than they started with. Te first session, open to everyone, focused on the government conveying the emerging requirements to the full audience. Te second, a closed- door session, allowed interested parties to present how they felt they could address those requirements and what the current state of their capabilities were.


When it comes to presenting the material, it can be tempting for the government to go beyond the facts and into conjecture and theories on what exactly the solu- tion looks like. Te key is to stick with the facts as they are known and let the audience use its expertise to develop solu- tions based on the requirements. In this case, the government team focused on the capability gap, characteristics desired by the initial capabilities document and the driving external forces such as policy constraints. Te intent is not to answer all the questions participants may have, but to get all the combined experience and expertise in the room thinking about the problem.


Once they hear what the government team has to say, it is up to the representatives


120


from industry and academia to decide if they have something relevant to the problem worth sharing. Te individual sessions provided them the opportunity to demonstrate their interest and capa- bilities in an “intellectual-property safe environment.” Significantly fewer firms decided to meet with the government team in the individual sessions, which itself


is a valuable data point that sets expectations for the future.


INDUSTRY DAY FIRST OF MANY STEPS TOWARD PARTNERSHIP Successful partnerships are not built on a single engagement. Te industry day is the initial event in a long, collabora- tive development process. At this stage, requirements are evolving rapidly and the program plan is becoming clearer week by week. Armed with the knowl- edge shared during the industry day, the interested potential proposers sharpened pencils and started developing their con- cepts. Meanwhile,


the program team


continued to build the necessary detail into the competitive prototyping strategy.


Another advantage of the DOTC pro- posal process that was particularly useful during this stage was the ability for the government and contractor team to col- laborate on the development of their


CONCLUSION Looking back, the obstacles that appeared to exist really turned into opportuni- ties, which had a ripple effect through the early phases of acquisition. Engaging industry with the assistance of ARDEC, DOTC and NAC opened possibilities that otherwise may not have existed. PM


proposal. Collaboration must stop once proposals are submitted, but up to that point cooperation is encouraged to ensure that everyone is on the right path. Te beginning of the proposal develop- ment period provided a logical point for a follow-on group engagement. (See Figure 2.) Te government plan for executing the competitive prototyping phase was further defined, the contractors started pulling together their concepts and team- ing between primes and subs had taken place.


To maintain competitive fairness, it was important that information flowed consistently across the board from the government team to the proposing con- tractors, so it made sense to pull everyone together for another industry day. Hav- ing made it through the first industry day, the hurdles faced the second time were minimal, and it was smooth sailing toward awards.


The intent is for industry to help identify risks, quantify affordability and define development timelines. That is information that can feed into the AoA and ensure a well-informed path forward.


Army AL&T Magazine


July-September 2016


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