Search NASA⌕ Search

SEARCH · Search NASA

Results for “Project Implementation Plan”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 505 records · Page 28

The Plankton, Aerosol, Cloud, Ocean Ecosystem (Pace) Mission Overview: From Concept to Launch

Abstract for Technical Review: The Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission is a strategic climate continuity mission that was defined in the 2010 document Responding to the Challenge of Climate and Environmental Change: NASA’s Plan for Climate-Centric Architecture for Earth Observations and Applications from Space (referred to as the “Climate Initiative”). Launched in February 2024, the PACE mission represents NASA’s next investment in ocean biology, clouds, and aerosol data records. PACE will extend the high quality ocean ecological, ocean biogeochemical, cloud, and aerosol particle data records begun by NASA in the 1990s, building on the exceptional heritages of the Sea-Viewing Wide Field-of-View Sensor (SeaWiFS), the Moderate Resolution Imaging Spectroradiometer (MODIS), the Multi-angle Imaging SpectroRadiometer (MISR), and the Visible Infrared Imaging Radiometer Suite (VIIRS). NASA Headquarters directed the mission development and implementation to the NASA Goddard Space Flight Center (GSFC) with guidance to utilize a Design-to-Cost (DTC) process. Mission studies were conducted to define appropriate approaches within and across elements while maximizing science capabilities at a high cost confidence. Mission baseline requirements development is also embedded within the DTC process, as these requirements were not established at the onset of the mission concept development. The PACE project office at NASA’s GSFC was responsible for the satellite development, launch and commissioning. The NASA Headquarters PACE Program Science office is responsible for supporting the science data processing system and assembling competed community science teams, which includes field-based vicarious calibration and data product validation efforts to support the PACE Project Science team. The PACE observatory is comprised of three instruments, the Ocean Color Instrument (OCI) and two polarimeters, the Hyper-Angular Rainbow Polarimeter 2 (HARP2) and the Spectro-Polarimeter for Exploration (SPEXone) and the PACE spacecraft. The observatory has been commissioned and is performing on-orbit science data collection operations. Summary for Program: The Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission is a strategic climate continuity mission that was defined in the 2010 document Responding to the Challenge of Climate and Environmental Change: NASA’s Plan for Climate-Centric Architecture for Earth Observations and Applications from Space (referred to as the “Climate Initiative”). Launched in February 2024 under the leadership of the NASA Goddard Space Flight Center (GSFC), the PACE mission represents NASA’s next investment in ocean biology, clouds, and aerosol data records. PACE will extend the high quality ocean ecological, ocean biogeochemical, cloud, and aerosol particle data records begun by NASA in the 1990s. The PACE observatory is comprised of the Ocean Color Instrument (OCI), the Hyper-Angular Rainbow Polarimeter 2 (HARP2) and the Spectro-Polarimeter for Exploration (SPEXone), along with the PACE spacecraft.

Robert H Estep, Jr↗

Mission Overview and Status from Concept to Launch

The Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission is a strategic climate continuity mission that was defined in the 2010 document Responding to the Challenge of Climate and Environmental Change: NASA’s Plan for Climate-Centric Architecture for Earth Observations and Applications from Space (referred to as the “Climate Initiative”). Launched in February 2024, the PACE mission represents NASA’s next investment in ocean biology, clouds, and aerosol data records. PACE will extend the high quality ocean ecological, ocean biogeochemical, cloud, and aerosol particle data records begun by NASA in the 1990s, building on the exceptional heritages of the Sea-Viewing Wide Field-of-View Sensor (SeaWiFS), the Moderate Resolution Imaging Spectroradiometer (MODIS), the Multi-angle Imaging SpectroRadiometer (MISR), and the Visible Infrared Imaging Radiometer Suite (VIIRS). NASA Headquarters directed the mission development and implementation to the NASA Goddard Space Flight Center (GSFC) with guidance to utilize a Design-to-Cost (DTC) process. Mission studies were conducted to define appropriate approaches within and across elements while maximizing science capabilities at a high cost confidence. Mission baseline requirements development is also embedded within the DTC process, as these requirements were not established at the onset of the mission concept development. The PACE project office at NASA’s GSFC was responsible for the satellite development, launch and commissioning. The NASA Headquarters PACE Program Science office is responsible for supporting the science data processing system and assembling competed community science teams, which includes field-based vicarious calibration and data product validation efforts to support the PACE Project Science team. The PACE observatory is comprised of three instruments, the Ocean Color Instrument (OCI) and two polarimeters, the Hyper-Angular Rainbow Polarimeter 2 (HARP2) and the Spectro-Polarimeter for Exploration (SPEXone) and the PACE spacecraft. The observatory has been commissioned and is performing on-orbit science data collection operations. Summary for Program: The Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission is a strategic climate continuity mission that was defined in the 2010 document Responding to the Challenge of Climate and Environmental Change: NASA’s Plan for Climate-Centric Architecture for Earth Observations and Applications from Space (referred to as the “Climate Initiative”). Launched in February 2024 under the leadership of the NASA Goddard Space Flight Center (GSFC), the PACE mission represents NASA’s next investment in ocean biology, clouds, and aerosol data records. PACE will extend the high quality ocean ecological, ocean biogeochemical, cloud, and aerosol particle data records begun by NASA in the 1990s. The PACE observatory is comprised of the Ocean Color Instrument (OCI), the Hyper-Angular Rainbow Polarimeter 2 (HARP2) and the Spectro-Polarimeter for Exploration (SPEXone), along with the PACE spacecraft.

Robby Estep↗

Contamination Control and Hardware Processing Solutions at Marshall Space Flight Center

The Contamination Control Team of Marshall Space Flight Center's Materials and Processes Laboratory supports many Programs/ Projects that design, manufacture, and test a wide range of hardware types that are sensitive to contamination and foreign object damage (FOD). Examples where contamination/FOD concerns arise include sensitive structural bondline failure, critical orifice blockage, seal leakage, and reactive fluid compatibility (liquid oxygen, hydrazine) as well as performance degradation of sensitive instruments or spacecraft surfaces such as optical elements and thermal control systems. During the design phase, determination of the sensitivity of a hardware system to different types or levels of contamination/FOD is essential. A contamination control and FOD control plan must then be developed and implemented through all phases of ground processing, and, sometimes, on-orbit use, recovery, and refurbishment. Implementation of proper controls prevents cost and schedule impacts due to hardware damage or rework and helps assure mission success. Current capabilities are being used to support recent and on-going activities for multiple Mission Directorates / Programs such as International Space Station (ISS), James Webb Space Telescope (JWST), Space Launch System (SLS) elements (tanks, engines, booster), etc. The team also advances Green Technology initiatives and addresses materials obsolescence issues for NASA and external customers, most notably in the area of solvent replacement (e.g. aqueous cleaners containing hexavalent chrome, ozone depleting chemicals (CFC s and HCFC's), suspect carcinogens). The team evaluates new surface cleanliness inspection and cleaning technologies (e.g. plasma cleaning), and maintains databases for processing support materials as well as outgassing and optical compatibility test results for spaceflight environments.

Burns, DeWitt H.↗

Design and implementation of a ground control console prototype for OMV

One of the primary uses of the Flat Floor facility of The Marshall Flight Center is to perform autonomous and teleoperated docking of vehicles similar to NASA's Orbital Maneuvering Vehicle (OMV). Using both the air-bearing vehicle and the 8 DOF Dynamic Overhead Target Simulator (DOTS) in tandem, even the most difficult OMV docking problems can be simulated. The OMV was planned to be flown from the ground by a pilot via teleoperation. Specifications were developed for a prototype Ground Control Console (GCC) from where the vehicle will be flown. In order for testing of the OMV to occur at Flat Floor facility, this GCC must be replicated. The project was divided into three primary tasks: (1) the design and development of the video display; (2) the design and development of the switch panel using the micro switch programmable display pushbutton switches; and (3) the design and development of the hand controllers. A final task is to perform system integration on the results of these three primary tasks.

Walcott, Bruce L.↗

Start Up Research Effort in Fluid Mechanics. Advanced Methods for Acoustic and Thrust Benefits for Aircraft Engine Nozzle

In accordance with the project plan for the report period in the proposal titled above, HU and FML teams investigated two sets of concepts for reduction of noise and improvement in efficiency for jet exhaust nozzles of aircraft engines and screws for mixers, fans, propellers and boats. The main achievements in the report period are: (a) Publication of the paper in the AIAA Journal, which described our concepts and some results. (b) The Award in the Civil Research and Development Foundation (CRDF) competition. This 2 year grant for Hampton University (HU) and Central AeroHydrodynamic Institute (TSAGI, Moscow, Russia) supports the research implementation under the current NASA FAR grant. (c) Selection for funding by NASA HQ review panel of the Partnership Awards Concept Paper. This two year grant also will support our current FAR grant. (d) Publication of a Mobius Strip concept in NASA Technical Briefs, June, 1996, and a great interest of many industrial companies in this invention. Successful experimental results with the Mobius shaped screw for mixers, which save more than 30% of the electric power by comparison with the standard screws. Creation of the scientific-popular video-film which can be used for commercial and educational purposes. (e) Organization work, joint meetings and discussions of the NASA LARC JNL Team and HU professors and administration for the solution of actual problems and effective work of the Fluid Mechanics Laboratory at Hampton University. In this report the main designs are enumerated. It also contains for both concept sets: (1) the statement of the problem for each design, some results, publications, inventions, patents, our vision for continuation of this research, and (2) present and expected problems in the future.

White, Samuel G.↗

The NASA Integrated Information Technology Architecture

This document defines an Information Technology Architecture for the National Aeronautics and Space Administration (NASA), where Information Technology (IT) refers to the hardware, software, standards, protocols and processes that enable the creation, manipulation, storage, organization and sharing of information. An architecture provides an itemization and definition of these IT structures, a view of the relationship of the structures to each other and, most importantly, an accessible view of the whole. It is a fundamental assumption of this document that a useful, interoperable and affordable IT environment is key to the execution of the core NASA scientific and project competencies and business practices. This Architecture represents the highest level system design and guideline for NASA IT related activities and has been created on the authority of the NASA Chief Information Officer (CIO) and will be maintained under the auspices of that office. It addresses all aspects of general purpose, research, administrative and scientific computing and networking throughout the NASA Agency and is applicable to all NASA administrative offices, projects, field centers and remote sites. Through the establishment of five Objectives and six Principles this Architecture provides a blueprint for all NASA IT service providers: civil service, contractor and outsourcer. The most significant of the Objectives and Principles are the commitment to customer-driven IT implementations and the commitment to a simpler, cost-efficient, standards-based, modular IT infrastructure. In order to ensure that the Architecture is presented and defined in the context of the mission, project and business goals of NASA, this Architecture consists of four layers in which each subsequent layer builds on the previous layer. They are: 1) the Business Architecture: the operational functions of the business, or Enterprise, 2) the Systems Architecture: the specific Enterprise activities within the context of IT systems, 3) the Technical Architecture: a common, vendor-independent framework for design, integration and implementation of IT systems and 4) the Product Architecture: vendor=specific IT solutions. The Systems Architecture is effectively a description of the end-user "requirements". Generalized end-user requirements are discussed and subsequently organized into specific mission and project functions. The Technical Architecture depicts the framework, and relationship, of the specific IT components that enable the end-user functionality as described in the Systems Architecture. The primary components as described in the Technical Architecture are: 1) Applications: Basic Client Component, Object Creation Applications, Collaborative Applications, Object Analysis Applications, 2) Services: Messaging, Information Broker, Collaboration, Distributed Processing, and 3) Infrastructure: Network, Security, Directory, Certificate Management, Enterprise Management and File System. This Architecture also provides specific Implementation Recommendations, the most significant of which is the recognition of IT as core to NASA activities and defines a plan, which is aligned with the NASA strategic planning processes, for keeping the Architecture alive and useful.

Baldridge, Tim↗

Europa Clipper Mission: Onward to Implementation!

Europa, the fourth largest moon of Jupiter, is believed to be one of the best places in the solar system to look for extant life beyond Earth, and the Europa Clipper Mission is preparing to investigate. Now entering the fifth year of life as a formal project, the Europa Clipper Mission has completed its major design phase and is preparing for implementation. The mission envisions sending a flight system, consisting of a spacecraft equipped with a payload of NASA-selected scientific instruments, to execute numerous flybys of Europa while in Jupiter orbit. The mission is being formulated and implemented by a joint Jet Propulsion Laboratory (JPL) and Applied Physics Laboratory (APL) Project team. At the Project Preliminary Design Review (PDR) in August 2018, it was determined that the unique integration of the REASON instrument’s antennas with the spacecraft’s solar arrays required additional time for maturity and review. The required maturity was demonstrated, and in June 2019 the Clipper Mission passed its Delta Preliminary Design Review, and formal confirmation for entry into Phase C was announced by NASA in August 2019. The earliest launch opportunity is now in July 2023, one year later than originally planned. The Project is now working toward its Critical Design Review in May 2020. This paper will describe the progress of the Europa Clipper Mission since January 2019, including maturation of the spacecraft, subsystem and instrument designs, the beginning of fabrication of engineering models and the first flight models, planning for the verification & validation phase, and planning for operations.

Jackson, Maddalena↗

Mentat/A: Medium grain parallel processing

The objective of this project is to support the Algorithm to Architecture Mapping Model (ATAMM) firing rules using the Mentat run-time system and the Mentat Programming Language (MPL). Specifically, this required changes to (1) modify the run-time system to control queue length and inhibit actor firing until required data tokens are available and space is available in the input queues of all of the direct descendent actors, (2) disallow the specification of persistent object classes in the MPL, and (3) permit only decision free graphs in the MPL. We have been successful in implementing the spirit of the plan, although some goals changed as we came to better understand the problem. Here, we report on what we accomplished and the lessons we learned. The Mentat/A runtime system, the compiler, results for three applications, and a summary and some observations are given. Appendix A contains a list of technical reports and published papers partially supported by the grant. Appendix B contains listings for the three applications.

Grimshaw, Andrew S.↗

Mission Data System Java Edition Version 7

The Mission Data System framework defines closed-loop control system abstractions from State Analysis including interfaces for state variables, goals, estimators, and controllers that can be adapted to implement a goal-oriented control system. The framework further provides an execution environment that includes a goal scheduler, execution engine, and fault monitor that support the expression of goal network activity plans. Using these frameworks, adapters can build a goal-oriented control system where activity coordination is verified before execution begins (plan time), and continually during execution. Plan failures including violations of safety constraints expressed in the plan can be handled through automatic re-planning. This version optimizes a number of key interfaces and features to minimize dependencies, performance overhead, and improve reliability. Fault diagnosis and real-time projection capabilities are incorporated. This version enhances earlier versions primarily through optimizations and quality improvements that raise the technology readiness level. Goals explicitly constrain system states over explicit time intervals to eliminate ambiguity about intent, as compared to command-oriented control that only implies persistent intent until another command is sent. A goal network scheduling and verification process ensures that all goals in the plan are achievable before starting execution. Goal failures at runtime can be detected (including predicted failures) and handled by adapted response logic. Responses can include plan repairs (try an alternate tactic to achieve the same goal), goal shedding, ignoring the fault, cancelling the plan, or safing the system.

Reinholtz, William K.↗

Exploration Portable Life Support System Hatch Component Design

The design for the Exploration Extravehicular Mobility Unit (xEMU) is continuously being developed and many previous gaps in technologies have begun initial development. Various Exploration Portable Life Support System (xPLSS) Hatch components had been at a stall in technology development for many years including the Feedwater Supply Assembly, Trace Contaminant Control System, and the thermal loop filters. The challenging requirements and initial design of these components were previously discussed in “Exploration Portable Life Support System Hatch Component Design Challenges and Progress”. NASA has plans to go back to the Moon. The development of each of these components is relevant not only to the xEMU, but also to the International Space Station, Gateway, and commercial space businesses. As the xPLSS is being designed, built, integrated, and tested at the NASA Johnson Space Center, technology solutions will have a direct incorporation path as the xPLSS is matured to meet design and performance goals. This is a follow on paper to discuss the initial implementation of the hatch component designs, changes due to existing challenges, and performance results of these components as the xEMU project completes the first phase of towards flight, known as Design Verification Test (DVT).

Kristina Todd↗

Algorithmic Classification of Raman Spectra Biosignatures: Improving Life Detection Confidence

“Agnostic” biosignatures – indicators of life (or the absence of life), independent of a particular biochemistry – are increasingly considered a high standard for life detection. The Ladder of Life Detection (2018) called for investigating how combinations of independent and different potential biosignatures affect confidence. To address this gap, statistical classification of elemental abundances, isotopic fractionation, and reflectance spectroscopy (VNIR) has been implemented. Raman spectroscopy, highly desirable due to its wide availability, has the potential to improve this predictive power. This work implemented biosignature classification algorithms on Raman data alone, in preparation for combination with the other data types. Raman spectroscopy data was collected from published databases and papers as part of a manually curated dataset of “indicative” and “non-indicative of life” samples. These currently include 61 non-indicative samples (meteorites, magnetite); 3 indicative living samples (bacteria); 20 indicative non-living samples (chalk, bone); and 12 indicative mixed (with non-indicative material) samples (soil, microbial mats). Laboratory work is ongoing to characterize additional samples, particularly a greater breadth of mixed systems. Spectra were interpolated, filtered with the Savitzsky-Golay filter, and de-noised. For a preliminary examination, agnostic features were manually extracted including mean intensity, number of peaks, and mean peak width. Different peak prominences and filtering polynomials were used to refine features. Classification algorithms were implemented: k-nearest neighbors (KNN), logistic regression (LR), linear support vector machines (SVM), random forest (RF), Gaussian naïve bayes (GNB). Lastly, Monte Carlo simulations on 1,000 50%-train-test-splits were used to validate classification performance and feature significance. The preliminary feature set achieved its highest AUC of 0.52 with LR, with no strongly discriminatory features. Work to improve feature extraction, such as through deep learning with back propagation, is planned. In future work, the Raman data will be combined with the other data types, and potentially new data types such as enantiomeric excess. This project was partially supported through the NASA Ames Project EXcellence (APEX) incubator program.

Astrobiology↗

Measuring Tropospheric Winds from Space Using a Coherent Doppler Lidar Technique

The global measurement of tropospheric wind profiles has been cited by the operational meteorological community as the most important missing element in the present and planned observing system. The most practical and economical method for obtaining this measurement is from low earth orbit, utilizing a Doppler lidar (laser radar) technique. Specifically, this paper will describe the coherent Doppler wind lidar (CDWL) technique, the design and progress of a current space flight project to fly such a system on the Space Shuttle, and plans for future flights of similar instruments. The SPARCLE (SPAce Readiness Coherent Lidar Experiment) is a Shuttle-based instrument whose flight is targeted for March, 2001. The objectives of SPARCLE are three-fold: Confirm that the coherent Doppler lidar technique can measure line-of-sight winds to within 1-2 m/s accuracy; Collect data to permit validation and improvement of instrument performance models to enable better design of future missions; and Collect wind and backscatter data for future mission optimization and for atmospheric studies. These objectives reflect the nature of the experiment and its program sponsor, NASA's New Millennium Program. The experiment is a technology validation mission whose primary purpose is to provide a space flight validation of this particular technology. (It should be noted that the CDWL technique has successfully been implemented from ground-based and aircraft-based platforms for a number of years.) Since the conduct of the SPARCLE mission is tied to future decisions on the choice of technology for free-flying, operational missions, the collection of data is intrinsically tied to the validation and improvement of instrument performance models that predict the sensitivity and accuracy of any particular present or future instrument system. The challenges unique to space flight for an instrument such as SPARCLE and follow-ons include: Obtaining the required lidar sensitivity from the long distance of orbit height to the lower atmosphere; Maintaining optical alignments after launch to orbit, and during operations in "microgravity"; Obtaining pointing knowledge of sufficient accuracy to remove the speed of the spacecraft (and the rotating Earth) from the measurements; Providing sufficient power (not a problem on the Shuttle) and cooling to the instrument. The paper will describe the status and challenges of the SPARCLE project, the value of obtaining wind data from orbit, and will present a roadmap to future instruments for scientific research and operational meteorology.

Miller, Timothy L.↗

Review of NASA activities in materials sciences in space

In the year since the 18th Plenary Meeting of COSPAR, NASA has conducted eight materials processing experiments on the Apollo-Soyuz mission and 17 on two rocket flights. In addition, these three missions have implemented one Soviet and three German experiments. The Apollo-Soyuz results have confirmed and extended the findings of the Skylab experiments on solidification and crystal growth effects and have also established capabilities for separating living cells by electrophoresis and returning them still living to earth. The rocket missions provide repetitive flight opportunities much as the Space Shuttle will do, and they are being used to develop research approaches in which investigators will undertake projects calling for multiple space experiments rather than proposing experiments individually. During the year, NASA has also completed definition work on the major payload facilities planned for its initial materials processing experiment program on the Space Shuttle and Spacelab missions of 1980-81.

Bredt, J. H.↗

Weather Information Communication (WINCOMM) VDL-3 and 1090ES Final Test Requirements, Test Plans, and Test Results

NASA s Aviation Safety Program was created for the purpose of making a significant reduction in the incidents of weather related aviation accidents by improving situational awareness. The objectives of that program are being met in part through advances in weather sensor technology, and in part through advances in the communications technology that are developed for use in the National Airspace System. It is this latter element, i.e., the improvements in aviation communication technologies, that is the focus of the Weather Information Communications project. This report describes the final flight test results completed under the WINCOMM project at the NASA Glenn Research Center of the 1090 Extended Squitter (1090ES) and VDL Mode 3 (VDL-3) data links as a medium for weather data exchange. It presents the use of 1090ES to meet the program objectives of sending broadcast turbulence information and the use of VDL-3 to send graphical weather images. This report provides the test requirements and test plans, which led to flight tests, as well as final results from flight testing. The reports define the changes made to both avionics and ground-based receivers as well as the ground infrastructure to support implementation of the recommended architecture, with a focus on the issues associated with these changes.

Griner, James H.↗

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA’s Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA’s Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V’s desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V’s assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Gerek Whitman↗

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA's Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA's Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V's desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V's assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Whitman, Gerek↗

Europa Clipper Payload Verification and Validation: Avionics-Instrument Interface Test Campaign

NASA's Europa Clipper mission will investigate Jupiter's icy moon Europa using a payload suite consisting of nine instruments to address a range of scientific objectives concerning Europa's habitability. As the project proceeds past its Critical Design Review, confidence is being built in the system's ability to achieve mission objectives through the implementation of a rigorous payload verification and validation (V&V) program. As part of this payload V&V program, instrument box-level testing was performed by the payload team to verify select instrument-avionics interface requirements. This testing was performed at JPL using the avionics testbed's Bulk Data Storage Emulator (BDSEM) with visiting instrument Test Models. This paper summarizes the Data Link test campaign involving roughly four days of functional testing per instrument, including planning, testing methods, types of issues found, and the requirement closure process. Detail is also provided on the development, deployment, and validation of a standardized analysis tool used in data reviews. This testing verified requirements related to commanding rates, loss of link, packet format, clock counters, loopback test capability, and SpaceWire jitter and skew margins. Additional risk reduction testing of basic commanding, counter behavior, science data collection and transfer, and interface swapping was also performed. Because the BDSEM venue was not originally designed to be a run for record venue, the process of characterizing venue fidelity and establishing suitability for requirement closure using data collected in this venue will also be addressed.In order to close requirements, an extensible tool was developed to post-process instrument command and telemetry data from their original binary to a human-readable format and give visibility to errors detected within the data, such as packets with Cyclic Redundancy Check errors. This tool, called payload-packet-parser, is a Python 3.9 command line tool built using a variety of open-source Python libraries. Payload-packet-parser was designed to support parsing command and telemetry packets for all Europa Clipper instruments and additional analysis tools were developed for verification of specific information interface requirements. This test campaign, including post-processing using a single parsing and verification toolset, allowed for early interface testing, alleviating testing burdens on instrument teams and buying down risk on the instrument-avionics interface by finding hardware and software issues and idiosyncrasies prior to integration with system test venues. Over twenty issues were discovered across the payload, resulting in software updates and instrument rework well in advance of any system impacts. This paper concludes with an assessment of benefits and costs of this type of testing and lessons learned.

Montanez, Leticia↗

Runway Operations Planning: A Two-Stage Solution Methodology

The airport runway is a scarce resource that must be shared by different runway operations (arrivals, departures and runway crossings). Given the possible sequences of runway events, careful Runway Operations Planning (ROP) is required if runway utilization is to be maximized. Thus, Runway Operations Planning (ROP) is a critical component of airport operations planning in general and surface operations planning in particular. From the perspective of departures, ROP solutions are aircraft departure schedules developed by optimally allocating runway time for departures given the time required for arrivals and crossings. In addition to the obvious objective of maximizing throughput, other objectives, such as guaranteeing fairness and minimizing environmental impact, may be incorporated into the ROP solution subject to constraints introduced by Air Traffic Control (ATC) procedures. Generating optimal runway operations plans was approached in with a 'one-stage' optimization routine that considered all the desired objectives and constraints, and the characteristics of each aircraft (weight class, destination, Air Traffic Control (ATC) constraints) at the same time. Since, however, at any given point in time, there is less uncertainty in the predicted demand for departure resources in terms of weight class than in terms of specific aircraft, the ROP problem can be parsed into two stages. In the context of the Departure Planner (OP) research project, this paper introduces Runway Operations Planning (ROP) as part of the wider Surface Operations Optimization (SOO) and describes a proposed 'two stage' heuristic algorithm for solving the Runway Operations Planning (ROP) problem. Focus is specifically given on including runway crossings in the planning process of runway operations. In the first stage, sequences of departure class slots and runwy crossings slots are generated and ranked based on departure runway throughput under stochastic conditions. In the second stage, the departure class slots are populated with specific flights from the pool of available aircraft, by solving an integer program. Preliminary results from the algorithm implementation on real-world traffic data are included.

Anagnostakis, Ioannis↗