TPF-C Technology Plan - Exoplanet Exploration Program - NASA
TPF-C Technology Plan - Exoplanet Exploration Program - NASA
TPF-C Technology Plan - Exoplanet Exploration Program - NASA
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Integrated Modeling and Model Validation<br />
analysis, the flight system requirements to the system testbed performance. This process is in<br />
progress. Some requirements are understood for the near-term model validation activities, e.g.,<br />
limits on the variability of optical material CTE, and some are clearly less defined, e.g., larger<br />
testbeds planned for Phase A-B. The requirements for all the testbeds will be firmed up as soon<br />
as the flight design and flight performance requirements are formally established.<br />
By the end of the project, the primary questions asked to the analysts will be, “Why do you<br />
believe the prediction” To help achieve this challenge, a novel modeling strategy will be<br />
implemented on <strong>TPF</strong>-C. It is standard practice to include hardware fabrication tolerances as<br />
margins within the error budget. For <strong>TPF</strong>-C it is proposed to treat models as “software<br />
fabrication” by including additional margin in the error budget to account for modeling<br />
tolerances, a.k.a. modeling uncertainties. This implies that the accuracy of the prediction will be<br />
quantified by tracking contributions to the modeling errors during the project lifecycle.<br />
Because the system performance objective now takes into account the predictability variances of<br />
the analysis, the design goal is no longer to select the design which meets the best nominal<br />
performance, but one that meets the best bounded performance including the modeling<br />
uncertainty. This means, for instance, that from the view point of predicting performance and<br />
meeting the error budget, a low CTE material having high variability and high uncertainty may<br />
not be as good a design choice as a higher CTE material with low variability and low<br />
uncertainty. Additional examples of modeling uncertainties include the nonlinear mechanics of<br />
hinges/latches, damping, etc.<br />
The concern that arises from this new modeling paradigm is the issue of “over-designing” the<br />
system by imposing tighter nominal performance requirements to make up for larger margin<br />
allocations in modeling uncertainties. This unfortunately is inevitable when analysis is the only<br />
means to validate on-orbit system performance, as it will be for an increasing number of flight<br />
systems in the future. The best that can be done to alleviate this concern is to address the<br />
problem up front, and to devise means by which modeling uncertainties can be evaluated,<br />
tracked, and, especially, reduced to minimize its overall contribution to the margin. It is<br />
recognized that modeling uncertainties will be naturally reduced through the course of the<br />
Project as testbeds and design mature. Nonetheless, there will still be residual uncertainties in the<br />
prediction of those flight performances that can only be validated through analysis, and those<br />
need to be accounted for in the V&V process.<br />
The overall margin allocation strategy is the responsibility of the Design Team and will not be<br />
discussed herein. At this time the design of the Baseline Mission concept is not mature and the<br />
margin philosophy has not yet been agreed upon. Nonetheless, eventually the Design Team will<br />
identify the required margin and levels of Modeling Uncertainty Factors (MUF) to achieve the<br />
mission. A future version of the <strong>Technology</strong> <strong>Plan</strong> will then be able to expand on how the<br />
required MUF levels will be validated. For now, the plan will focus on the approach and the<br />
testbeds planned for model validation. The current version of the error budget requirements will<br />
be used to illustrate the levels of magnitude expected from the model validation activity, but<br />
should not be considered as the definitive model validation technology requirements.<br />
This paradigm is fairly new to <strong>NASA</strong> missions, with JWST and SIM using engineering judgment<br />
to define empirical uncertainty bounds through the mission lifecycle. Because the <strong>TPF</strong>-C<br />
requirements are in a realm where there exists no past experience from which to develop<br />
83