BAT is a Web-based application used for the assembly and inspection of critical flight and associated ground support hardware for JPL missions that are developed in-house. It is used to capture and communicate data that is unique to a part or assembly that cannot be captured in an engineering drawing or a test procedure. It includes a list of parts and tools, along with specific steps required for building and assembling a piece of hardware.
In order to leverage expertise and technology development from previous missions, it is necessary to find and reuse complete build instructions. In the effort to create a fully electronic and searchable build book, the data needed to be captured electronically. The BAT application was designed to improve efficiency, reliability, and quality of the end-to-end process and reduce communications overhead.
The BAT application has a workflow that supports and enforces the assembly and inspection processes. The application helps users collaborate on creating and editing records. BAT validates part information and links to multiple systems for better data integration and easy access to relevant material. The application captures electronic signatures of the Engineering and Quality Assurance team and keeps a change log. It has a customized user inbox for easy access to records. BAT captures fabrication, assembly, and test steps electronically. Users are able to create, edit, or bring over existing rich text, images, and tables into the Web application. Users are able to duplicate, move, or delete one or more steps, and the system will re-number the steps based on business processes and the step type of inspection.
The BAT system is built on an extensible, integrated, and flexible infrastructure that makes the data in the system more reliable and valuable. The state of hardware is more visible to all users. Audits of the build-assemble-test process are significantly less resource-intensive.
BAT is fast, easy to use, robust, and flexible. Other software applications typically require download of software and significant training vs. BAT, which provides a Web-based application.
This work was done by Mona H. Postma, John R. Narva, Steve N. Flanagan, Azeemuddin Khaja, Lori A. Williams, Patricia L. Brandon, Jeffrey A. Holt, and John Flores of Caltech for NASA’s Jet Propulsion Laboratory.
The software used in this innovation is available for commercial licensing. Please contact Dan Broderick at
This Brief includes a Technical Support Package (TSP).
Build, Assemble, Test (BAT) Planning and Execution Resources Application
(reference NPO49452) is currently available for download from the TSP library.
Don't have an account?
Overview
The Technical Design Document (TDD) for the Instructions for Build, Assemble, and Test (I-BAT) serves as a comprehensive guide for stakeholders to understand how the technical product will meet functional business requirements. Developed during the Construction Stage of the project, the TDD is a deliverable document that outlines the technical design decisions, system requirements, and the overall architecture of the I-BAT.
The document emphasizes the importance of maintaining a stable TDD after its initial acceptance, as changes to the business problem statement, solution requirements, or technical architecture can adversely affect the project's scope, schedule, and cost. Major updates to the TDD will result in a version upgrade, while minor changes may be documented as an addendum. The Project Manager is responsible for communicating any changes to stakeholders, ensuring transparency throughout the project lifecycle.
The TDD includes a section dedicated to technical design decisions, which outlines the rationale behind the chosen design elements for the I-BAT. This section is crucial for understanding the underlying principles guiding the development process. Additionally, the document references the System Requirements Document, which provides further details on the specific requirements that the I-BAT must fulfill.
An appendix within the TDD contains a glossary of acronyms and terms relevant to the project, aiding in clarity and understanding for all stakeholders involved. The I-BAT itself is developed using BI Publisher, adhering to the current templates utilized by the Jet Propulsion Laboratory (JPL) for consistency and standardization in reporting.
The TDD is part of a broader Technical Support Package provided under NASA's Commercial Technology Program, aimed at disseminating aerospace-related developments with potential wider applications. The document is prepared under the sponsorship of NASA, with contributions from various experts at JPL, ensuring a high level of technical rigor and relevance.
In summary, the TDD for I-BAT is a critical document that outlines the technical framework and design decisions necessary for the successful execution of the project. It serves as a foundational resource for project stakeholders, ensuring that all parties are aligned on the objectives, requirements, and methodologies employed throughout the development process.
