Engineering PapersSearch

Engineering topics

Ingalls, John

Publications and source records attributed to Ingalls, John.

Technical Data Interoperability (TDI) Pathfinder Via Emerging Standards

The TDI project (TDI) investigates trending technical data standards for applicability to NASA vehicles, space stations, payloads, facilities, and equipment. TDI tested COTS software compatible with a certain suite of related industry standards for capabilities of individual benefits and interoperability. These standards not only esnable Information Technology (IT) efficiencies, but also address efficient structures and standard content for business processes. We used source data from generic industry samples as well as NASA and European Space Agency (ESA) data from space systems.

Technical Data

IT Labs Proof-of-Concept Project: Technical Data Interoperability (TDI) Pathfinder Via Emerging Standards

No known system is in place to allow NASA technical data interoperability throughout the whole life cycle. Life Cycle Cost (LCC) will be higher on many developing programs if action isn't taken soon to join disparate systems efficiently. Disparate technical data also increases safety risks from poorly integrated elements. NASA requires interoperability and industry standards, but breaking legacy ways is a challenge.

Interoperability

Integrated Procedures for Flight and Ground Operations Using International Standards

Imagine astronauts using the same Interactive Electronic Technical Manuals (IETM's) as the ground personnel who assemble or maintain their flight hardware, and having all of that data interoperable with design, logistics, reliability analysis, and training. Modern international standards and their corresponding COTS tools already used in other industries provide a good foundation for streamlined technical publications in the space industry. These standards cover everything from data exchange to product breakdown structure to business rules flexibility. Full Product Lifecycle Support (PLCS) is supported. The concept is to organize, build once, reuse many ways, and integrate. This should apply to all future and some current launch vehicles, payloads, space stations/habitats, spacecraft, facilities, support equipment, and retrieval ships.

Ingalls, John

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.

Ingalls, John

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John