A Case Study in NASA-DoD - The Black Vault
A Case Study in NASA-DoD - The Black Vault
A Case Study in NASA-DoD - The Black Vault
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
-69-<br />
to <strong>in</strong>crease to 13. That was found to be true across a wide number of<br />
excursions.<br />
It should be noted here that assum<strong>in</strong>g a maximum number of payloads<br />
per spacecraft of 13 results <strong>in</strong> an average number of payloads per spacecraft<br />
of only 5 to 8, depend<strong>in</strong>g on the procurement option. <strong>The</strong> largest<br />
benefit is from orbits 1 and 2 where the majority of Space Test Program<br />
payloads are scheduled to be flown. To illustrate that, Fig. 8 presents<br />
a detailed breakdown of the distribution of the actual maximum number of<br />
payloads per spacecraft by orbit for the all-STPSS procurement option.<br />
For orbit l-S, for example, if the assumed maximum number of payloads<br />
per spacecraft is allowed to <strong>in</strong>crease from 6 to 13, the actual maximum<br />
number of payloads assigned to a spacecraft <strong>in</strong>creases from 5 to 10.<br />
<strong>The</strong> difference between the actual number of payloads assigned to a<br />
spacecraft and the upper limit occurs <strong>in</strong> all orbits because of the<br />
limited number of payloads <strong>in</strong> each orbit.<br />
In orbit 1-S, for example,<br />
the mission model <strong>in</strong>cludes only 20 payloads, which were distributed<br />
evenly between two spacecraft when the assumed maximum number of payloads<br />
per spacecraft was <strong>in</strong>creased to 10.<br />
Consequently, the average<br />
number of payloads per spacecraft for a given procurement option does<br />
not <strong>in</strong>crease substantially as a result of allow<strong>in</strong>g the assumed maximum<br />
number of payloads per spacecraft to <strong>in</strong>crease from 6 to 13.<br />
<strong>The</strong> ma<strong>in</strong> difficulty associated with <strong>in</strong>creas<strong>in</strong>g the number of payloads<br />
per spacecraft lies <strong>in</strong> the payload-<strong>in</strong>tegration area. Although<br />
the specific performance limits of each spacecraft were imposed while<br />
allocat<strong>in</strong>g payloads, payload-<strong>in</strong>tegration problems and costs were not<br />
explicitly exam<strong>in</strong>ed. Based on the sav<strong>in</strong>g <strong>in</strong> program costs identified<br />
as a result of <strong>in</strong>creas<strong>in</strong>g the maximum number of payloads per spacecraft,<br />
it appears that a systematic study of the payload <strong>in</strong>tegration problems<br />
and costs would be useful.<br />
Figure 9 illustrates the variation <strong>in</strong> program cost as a function<br />
of Space Test Program size.<br />
Here program size was doubled to a total<br />
of 228 payloads to see if economies of scale might preferentially benefit<br />
the MKS and thereby alter the order<strong>in</strong>g of the procurement options.<br />
*<br />
While 13 payloads are never allocated to a spacecraft <strong>in</strong> the<br />
example shown <strong>in</strong> Fig. 8, this is not the case for other procurement<br />
options, especially those <strong>in</strong>clud<strong>in</strong>g the MMS.