MIL-STD-1798C
consumption of growth capacity versus time for each applicable subsystem. The program shall then retain this as a living document, periodically updating the plot of actual growth capacity consumption against the predicted value. Two technically acceptable methods to address a subsystem growth requirement are as follow:
a. Build in excess capacity to accommodate future growth; build in provisions to increase system capacity easily in the future (e.g., insure physical size is available to accommodate increased capacity). Discipline must be maintained to prevent encroachment on the growth provisions if this approach is taken.
b. Deliver the extra capacity in the initial design to accommodate the level of growth determined appropriate in the derived growth requirement.
Historically, the two subsystems most commonly requiring growth capacity are electric power and ECS. Other subsystems may also require growth capacity.
5.1.4 Preliminary integrity analysis.
The Pre-Development Activity shall define the critical hardware design features affecting integrity, and the mitigation plans to resolve or address these features. The preliminary analysis should also attempt to predict or estimate the potential of the candidate system concepts to achieve performance and integrity goals. This requires an understanding of the physical concepts and failure modes, and requires a limited database that defines the candidate materials, processes, and technologies. These analyses are particularly important, since they typically support the early engineering trade studies. Preliminary analyses should include, but not be limited to, equipment sizing, estimates of component and system service life potential, failure modes analysis, classification of critical components, and identification of latent failure modes.
5.1.5 Technical Data Package (TDP).
The Procuring Activity shall identify what level of technical data is required to flow smoothly into the sustainment phase and place requirements to obtain the appropriate level of data into the procurement contract. Experience shows it is far less expensive to contract for necessary data as early in the program life cycle as possible. If the support concept is not yet developed, the program should pursue a TDP which supports the highest level of organic sustainment that remains possible.
5.1.6 Technical reviews.
Criteria shall be developed that describe the content and level of completion of each MECSIP task for each program milestone. These criteria shall be used in a gated technical review process to proceed from one program milestone to the next. The intent of these criteria is to show the level of knowledge attained for the mechanical system components and that this level of knowledge is sufficient to proceed toward the next milestone. Appendix A shall be used as a guide to create these criteria.
5.1.7 Identify technical needs.
MECSIP Managers shall make a listing of Technical Needs encountered on an annual basis. A compiled list, from all programs, will be discussed/finalized at the MECSIP Technical Interchange Meeting and submitted into the Service-specific Research Laboratory as candidate developmental Technical Needs.
19
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business