to design and contract award. Tis time- line was long because the range required nonstandard equipment and a develop- ment effort. Other equipment, such as optical tables and temperature chambers, took six months to acquire and install at the depot.
Te next step entails identifying the probable repairs, as well as the parts and suppliers needed to complete them. PdM GS, along with TYAD and the CECOM LRC, conducted an analysis to identify items that could be repaired at the lowest possible level, such as lower-level assem- blies and components of those assemblies. A National Stock Number was assigned to each of the replacement components to enable easier procurement from sup- pliers. PdM GS and TYAD, with help from CECOM LRC, identified sources of supply at the lowest
level to ensure
the best value to the government, as there is usually little or no added value in going through the original equipment manufacturer (OEM) for an off-the-shelf component from a subtier vendor.
When beneficial, based on engineering value judgments, the team also contracted with vendors to train depot personnel on specific tools and techniques for handling critical components. For example, the team contracted an optics manufactur- ing company to teach a class on cleaning and handling the sensitive optical com- ponents found within the LRAS3.
As PdM GS conducted repairs and devel- oped technical instructions for specific repairs and tests, it also decided to aggre- gate all tests, known repairs and parts listings into a depot maintenance work requirement (DMWR). Te DMWR is designed to serve as the primary source of repair processes and knowledge. Using the DMWR enables a depot technician to perform repairs on systems and their
components without the need for institu- tional knowledge.
DATA AND SOURCE CODE Depending on the type of data a pro- gram possesses, the development of test programs and test facilities can be chal- lenging. For example, both the LRAS3 and the 2GF programs started during the acquisition reform period, when the Army bought systems based on a specifi- cation and required the vendor to deliver little technical data over the life of the program. With the establishment of an organic depot, however, there is a need for such data. Some suppliers will not engage in conversations with the depot or sell replacement parts to the depot unless the government has secured its technical data for a nonstandard, vendor-supplied item. For example, one optics manufacturer would not supply components to TYAD unless the government secured the “build to” drawings relating to their parts.
To acquire the data needed for facil- itization, programs are invoking several Defense Federal Acquisition Regulation Supplement (DFARS) clauses contained within the contracts used to procure the systems. Specifically, DFARS
252.227-7027, “Deferred Ordering of Technical Data or Computer Software,” states that “the Government may … order any technical data or computer software generated in the performance of this con- tract or any subcontract hereunder.” It is of particular relevance to depot facilitiza- tion efforts that the clause uses the term “generated,” not “delivered.”
Tus, deferred ordering is not limited to contract deliverables. Rather, the clause covers anything created using govern- ment funds pursuant to the contract. Te clause also applies for three years after contract closure or the delivery of all con- tract items. So, by exercising this DFARS clause, a program may compel a contrac- tor to deliver the data, software source code and other technical items that depot facilitization requires. In return, the contractor is entitled to payment for the cost of gathering and reproducing the data, provided that the data is delivered
“as is” (i.e., without any modification by the contractor).
FACILITIZATION IS NOT AN EASY TASK; IT TAKES RESOURCES AND DEDICATED PEOPLE TO SUCCEED.
Typically this “gathering and reproduc- ing” charge is an order of magnitude less than the cost of building a full technical data package for the government. Tese data should be delivered with govern- ment unlimited rights or government purpose rights. While the government does not own the data, both levels of rights convey a license from the contrac- tor to the government that is adequate for any and all required maintenance tasks, including facilitization.
PdM GS has spent considerable time and energy on technical data, obtaining source code and document markings. In light of this, programs should obtain the required data as a contract deliverable in an initial contract or request it at key points throughout the program, such as in engineering change proposals, software
ASC.ARMY.MIL 49
ACQUISITION
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 |
Page 197 |
Page 198 |
Page 199 |
Page 200
