Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “interoperability and control”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

Interoperability Trends in Extravehicular Activity (EVA) Space Operations for the 21st Century

No other space operations in the 21 st century more comprehensively embody the challenges and dependencies of interoperability than EVA. This discipline is already functioning at an W1paralleled level of interagency, inter-organizational and international cooperation. This trend will only increase as space programs endeavor to expand in the face of shrinking budgets. Among the topics examined in this paper are hardware-oriented issues. Differences in design standards among various space participants dictate differences in the EVA tools that must be manufactured, flown and maintained on-orbit. Presently only two types of functional space suits exist in the world. However, three versions of functional airlocks are in operation. Of the three airlocks, only the International Space Station (ISS) Joint Airlock can accommodate both types of suits. Due to functional differences in the suits, completely different operating protocols are required for each. Should additional space suit or airlock designs become available, the complexity will increase. The lessons learned as a result of designing and operating within such a system are explored. This paper also examines the non-hardware challenges presented by interoperability for a discipline that is as uniquely dependent upon the individual as EVA. Operation of space suits (essentially single-person spacecrafts) by persons whose native language is not that of the suits' designers is explored. The intricacies of shared mission planning, shared control and shared execution of joint EVA's are explained. For example, once ISS is fully functional, the potential exists for two crewmembers of different nationality to be wearing suits manufactured and controlled by a third nation, while operating within an airlock manufactured and controlled by a fourth nation, in an effort to perform tasks upon hardware belonging to a fifth nation. Everything from training issues, to procedures development and writing, to real-time operations is addressed. Finally, this paper looks to the management challenges presented by interoperability in general. With budgets being reduced among all space-faring nations, the need to expand cooperation in the highly expensive field of human space operations is only going to intensify. The question facing management is not if the trend toward interoperation will continue, but how to best facilitate its doing so. Real-world EVA interoperability experience throughout the ShuttlelMir and ISS Programs is discussed to illustrate the challenges and

Miller, Gerald E.↗
DOE OSTI2022

Electric Vehicles at Scale (EVs@Scale) Laboratory Consortium Deep-Dive Technical Meetings: High Power Charging (HPC) Summary Report

Electric vehicle (EV) adoption will change the composition of EV charging load to higher-power charging as more medium- (MD) and heavy-duty (HD) applications are electrified, and as all vocations, including light-duty (LD) vehicles, are capable of faster charging. These shifts provide the opportunity for high-power charging (HPC) and facility equipment to evolve and improve efficiency, cost, and space. High-Power Electric Vehicle Charging Hub Integration Platform (eCHIP) project designs and develops a high-power, interoperable charging experimental platform to research, develop, and demonstrate the integration approaches and technology solutions. The project addresses (1) interconnection and management of a grid-tied inverter; (2) development of a DC distribution system that is responsible for system energy management, interoperability, and DC protection; (3) modular DC/DC conversion for vehicle charging; (4) EV charging interface and DC/DC integration; and (5) smart charge control and vehicle-to-edge (vehicle-to-building [V2B], vehicle-to-everything [V2X]) capability. This summary presentation is the first technical progress output of the project. It provides insight for the first deep-dive technical meeting outputs in terms of research presentations and also includes summary of the discussions occurred in the follow-up breakout sessions. The summary presentation covers three technical areas: (1) HPC: State of the art power architectures and the design of the power electronics, (2) Modeling, energy management, and power control in the HPC station, and (3) Codes and standards work that are in line with the previous two topic areas.

ADVANCED PROPULSION SYSTEMS,POWER TRANSMISSION AND↗
DOE OSTI2023

Electric Vehicles at Scale (EVs@Scale) Laboratory Consortium Deep-Dive Technical Meetings: High Power Charging (HPC) Summary Report

Electric vehicle (EV) adoption will change the composition of EV charging load to higher-power charging as more medium- (MD) and heavy-duty (HD) applications are electrified, and as all vocations, including light-duty (LD) vehicles, are capable of faster charging. These shifts provide the opportunity for high-power charging (HPC) and facility equipment to evolve and improve efficiency, cost, and space. High-Power Electric Vehicle Charging Hub Integration Platform (eCHIP) project designs and develops a high-power, interoperable charging experimental platform to research, develop, and demonstrate the integration approaches and technology solutions. The project addresses (1) interconnection and management of a grid-tied inverter; (2) development of a DC distribution system that is responsible for system energy management, interoperability, and DC protection; (3) modular DC/DC conversion for vehicle charging; (4) EV charging interface and DC/DC integration; and (5) smart charge control and vehicle-to-edge (vehicle-to-building [V2B], vehicle-to-everything [V2X]) capability. This summary presentation is the first technical progress output of the project. It provides insight for the first deep-dive technical meeting outputs in terms of research presentations and also includes summary of the discussions occurred in the follow-up breakout sessions. The summary presentation covers three technical areas: (1) HPC: State of the art power architectures and the design of the power electronics, (2) Modeling, energy management, and power control in the HPC station, and (3) Next Generation Profiles for high power charging characterization.

ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2026

Digitizing Today’s Buildings in the Real World: Lessons from Field Demonstrations

Digital twins, created by generating a virtual replica of a building, enable safe evaluation of operational scenarios and applications like fault detection and diagnosis and advanced controls. However, a prerequisite is the creation of a machine-readable digital representation of a building, currently hindered by fragmented information scattered across mechanical drawings, point lists, and natural language sequences. As a result, digital twin development remains labor-intensive, error-prone, and difficult to validate. To address these challenges, two efforts from ASHRAE aim to support the digitalization of buildings. ASHRAE s223 establishes a semantic model of buildings, representing system components, configuration, and data sources. ASHRAE s231 defines a vendor-neutral programming language for expressing their control logic. As the industry evaluates implementing them in their products, understanding the challenges that vendors and implementers may face is crucial. In this paper, we present findings and lessons learned from field demonstrations in five buildings that implemented control applications using ASHRAE s223 and s231. The demonstrations highlight how semantic modeling and formalized control descriptions can significantly reduce software development time, manual point mapping, and hard-coding. Beyond time efficiency, they enable reliable automation by minimizing human interpretation and providing a means for consistency across projects. We describe the processes and best practices for model creation and model usage, from translating heterogeneous building documentation into semantic representations to implementing control logic in real-world systems. Finally, we discuss the challenges that persist, including integration with legacy software environments, gaps in interoperability, and the level of expertise still required to effectively leverage semantic models.

Prakash, Anand Krishnan↗
NASA NTRS2022

SpaceVPX Interoperability Assessment

The existing VMEbus (VersaModular Eurocard bus) International Trade Association (VITA)-78 industry standard, also known as SpaceVPX, is an avionics board- and chassis-level standard derived from the OpenVPX standard as defined in VITA-65. While VITA-65 defines backplane and board-level profiles from COTS vendors to ensure interoperability of products used in developing systems and subsystems, the VITA-78 standard defines SpaceVPX to incorporate fault tolerance features that are required by many spaceflight systems. However, VITA-78 allows so much flexibility that interoperability between modules cannot be assured. This assessment provides guidelines on the use of, and extensions to, the VITA-78 standard to enable avionics interoperability for future NASA missions. The assessment team was comprised of subject matter experts (SMEs) from Goddard Space Flight Center (GSFC), the Jet Propulsion Laboratory (JPL), Johnson Space Center (JSC), and Langley Research Center (LaRC). The team included valuable external consulting support from a SME who was a key participant in the development of the VITA-78 standard. The team had extensive collaboration with the NASA Space Technology Mission Directorate (STMD) High Performance Spaceflight Computing (HPSC) project, specifically in the development of SpaceVPX interconnect findings, observations, and NESC recommendations. To provide an understanding of the breadth of implementations that SpaceVPX must accommodate, multiple NASA use cases were analyzed to assess the requirements for SpaceVPX implementations across a wide range of NASA missions (Appendix C). Applications included crewed missions, science missions, and orbital and surface robotic systems. Product surveys were conducted to assess the level of industry support for SpaceVPX, applications, and the variations in their implementations (Appendix D). In-depth analysis was conducted in the areas of: (a) power management and distribution, (b) form factors and daughtercards, (c) interconnect, and (d) fault tolerance. Leveraging the use cases, product surveys, and SMEs from multiple NASA Centers, these areas were analyzed to determine the range of implementations permitted by the VITA-78 standard and potential interoperability issues. Applicable findings and NESC recommendations were provided for each area. During this assessment, there were multiple opportunities to engage with other agencies to learn about their interest in SpaceVPX, their strategies for implementing SpaceVPX-based systems, and their internal development efforts. These engagements also generated findings and NESC recommendations. Based on this assessment analysis, NESC recommendations were made regarding the feature set and module profiles to support NASA SpaceVPX implementations. This feature set includes restrictions on features in VITA-78, and extensions to the standard. Key recommendations in this area include the use of 10 Gigabit Ethernet and Peripheral Component Interconnect Express (PCIe) as high bandwidth interconnect on the backplane, the retention of SpaceWire interconnect for control functions, and support for 3U (unit) and 6U, form factors for NASA systems. Restrictions were proposed on the usage of user-defined signals to promote interoperability, and specific power managements and distribution schemes for 3U systems. Beyond the technical implementation of SpaceVPX, recommendations were made on areas that warrant further investigation. Primary among these is the recommendation for NASA to collaborate with other space-going agencies and industry to incorporate recommendations into a future ‘dot spec’ of VITA-78. This would ensure wide adoption and availability of the modules that comply with the specification. The assessment includes appendices with candidate module profiles that can be considered as a starting point for this activity, and example systems based on the recommendations. Follow-on studies are recommended for architectures beyond SpaceVPX to address potential enhancements including condensed set of interconnect, software required to implement protocol layers on the interconnect (and other features), alternative power architectures, and system-level testability.

SpaceVPX↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources

This study addresses the compliance of Inverter-based Resources (IBRs) with IEEE Standard 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a controller development framework for abnormal grid conditions. This framework caters to maintaining ride-through operation in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller frame-work is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

IEEE Std 2800↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources

This study addresses the compliance of Inverter-based Resources (IBRs) with IEEE Standard 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a controller development framework for abnormal grid conditions. This framework caters to maintaining ride-through operation in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller framework is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

grid↗
NASA NTRS1999

ACTS 118x Final Report High-Speed TCP Interoperability Testing

With the recent explosion of the Internet and the enormous business opportunities available to communication system providers, great interest has developed in improving the efficiency of data transfer using the Transmission Control Protocol (TCP) of the Internet Protocol (IP) suite. The satellite system providers are interested in solving TCP efficiency problems associated with long delays and error-prone links. Similarly, the terrestrial community is interested in solving TCP problems over high-bandwidth links. Whereas the wireless community is interested in improving TCP performance over bandwidth constrained, error-prone links. NASA realized that solutions had already been proposed for most of the problems associated with efficient data transfer over large bandwidth-delay links (which include satellite links). The solutions are detailed in various Internet Engineering Task Force (IETF) Request for Comments (RFCs). Unfortunately, most of these solutions had not been tested at high-speed (155+ Mbps). Therefore, the NASA's ACTS experiments program initiated a series of TCP experiments to demonstrate scalability of TCP/IP and determine how far the protocol can be optimized over a 622 Mbps satellite link. These experiments were known as the 118i and 118j experiments. During the 118i and 118j experiments, NASA worked closely with SUN Microsystems and FORE Systems to improve the operating system, TCP stacks. and network interface cards and drivers. We were able to obtain instantaneous data throughput rates of greater than 520 Mbps and average throughput rates of 470 Mbps using TCP over Asynchronous Transfer Mode (ATM) over a 622 Mbps Synchronous Optical Network (SONET) OC12 link. Following the success of these experiments and the successful government/industry collaboration, a new series of experiments. the 118x experiments. were developed.

Ivancic, William D.↗
DOE OSTI2023

Interconnection and Interoperability Requirements of Hydrogen Assets to Enable Grid Integration

Traditionally, the inverters used for distributed energy resources (DERs) including solar, energy storage and hydrogen fuel cells are grid following assets. Grid following assets track real power and reactive power setpoints decided by either a local autonomous controller or a remote controller like a microgrid controller. In the past five years, multiple challenges have increased the need for grid forming inverters that can interface to a wide variety of energy resources. These grid forming inverters are becoming critical assets for power systems to enable the replacement of existing rotational machines and provide grid services such as grid resiliency services and black-start. Hydrogen assets (fuel cells) have the potential to successfully replace rotating machines and act as voltage and frequency master by leveraging the long-duration and seasonal energy storage capabilities of hydrogen technologies. This poster presents the progress made in budget period 1 of the proposed work. We will leverage an existing ARIES platform experimental setup to run power-hardware-in-the-loop and controller-hardware-in-the-loop experiments with grid forming fuel cell inverters to develop and document the standardization requirements.

electrolyzer↗
DOE OSTI2020

Future Vision for Autonomous Ocean Observations

Autonomous platforms already make observations over a wide range of temporal and spatial scales, measuring salinity, temperature, nitrate, pressure, oxygen, biomass; and many other parameters. However, the observations are not comprehensive. Future autonomous systems need to be more affordable, more modular, more capable and easier to operate. Creative new types of platforms and new compact, low power, calibrated and stable sensors are under development to expand autonomous observations. Communications and recharging need bandwidth and power which can be supplied by standardized docking stations. In situ power generation will also extend endurance for many types of autonomous platforms, particularly autonomous surface vehicles. Standardized communications will improve ease of use, interoperability, and enable coordinated behaviors. Improved autonomy and communications will enable adaptive networks of autonomous platforms. Improvements in autonomy will have three aspects: hardware, control, and operations. As sensors and platforms have more onboard processing capability and energy capacity, more measurements become possible. Control systems and software will have the capability to address more complex states and sophisticated reactions to sensor inputs, which allows the platform to handle a wider variety of circumstances without direct operator control. Operational autonomy is increased by reducing operating costs. To maximize the potential of autonomous observations new standards and best practices are needed. In some applications, focus on common platforms and volume purchases could lead to significant cost reductions. Cost reductions could enable order-of-magnitude increases in platform operations and increase sampling resolution for a given level of investment. Energy harvesting technologies should be integral to the system design, for sensors, platforms, vehicles, and docking stations. Connections are needed between the marine energy and ocean observing communities to coordinate among funding sources, researchers, and end users. Regional teams should work with global organizations such as IOC/GOOS in governance development. International networks such as EGO for the emerging glider operations should also provide a forum for addressing governance. Networks of multiple vehicles can improve operational efficiencies and transform operational patterns. There is a need to develop operational architectures at regional and global scales to provide a backbone for active networking of autonomous platforms.

47 OTHER INSTRUMENTATION↗
NASA NTRS2006

Moving Towards a Common Ground and Flight Data Systems Architecture for NASA's Exploration Missions

The National Aeronautics and Space Administration has embarked on an ambitious effort to return man to the moon and then on to Mars. The Exploration Vision requires development of major new space and ground assets and poses challenges well beyond those faced by many of NASA's recent programs. New crewed vehicles must be developed. Compatible supply vehicles, surface mobility modules and robotic exploration capabilities will supplement the manned exploration vehicle. New launch systems will be developed as well as a new ground communications and control infrastructure. The development must take place in a cost-constrained environment and must advance along an aggressive schedule. Common solutions and system interoperability and will be critical to the successful development of the Exploration data systems for this wide variety of flight and ground elements. To this end, NASA has assembled a team of engineers from across the agency to identify the key challenges for Exploration data systems and to establish the most beneficial strategic approach to be followed. Key challenges and the planned NASA approach for flight and ground systems will be discussed in the paper. The described approaches will capitalize on new technologies, and will result in cross-program interoperability between spacecraft and ground systems, from multiple suppliers and agencies.

Rader. Steve↗
DOE OSTI2024

Developing IEEE Std 2800-Compliant Algorithms for Transmission-Connected Inverter-Based Resources: Preprint

This study addresses the compliance of Inverter-based Resources (IBRs) with the IEEE Std 2800, a leading standard that defines interconnection and interoperability requirements for IBRs integrated into transmission systems. Focusing on abnormal grid scenarios, the research evaluates the specific demands on IBRs, proposing a comprehensive controller development framework. This framework caters to maintaining ride-trhough operation or implementing strategic disconnections in line with IEEE Std 2800, alongside managing currents during voltage ride-through scenarios. The effectiveness of this proposed controller framework is rigorously validated through case studies, employing a MATLAB/Simulink model of an IBR to test its performance under diverse grid fault conditions, ensuring the IBRs' alignment with standard requirements and their robust performance in enhancing grid reliability.

IEEE Std 2800↗
NASA NTRS2006

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.

Madden, Maureen↗
NASA NTRS2006

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Madden, Maureen↗
NASA NTRS2020

Integration Test and Evaluation (IT&E) Flight Test Series 6 Live Virtual Constructive - Distributed Environment (LVC-DE) Test Report

The goals of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) (also UAS-NAS) Project are to reduce the barriers for UAS access and its integration into the NAS. The UAS-NAS project and industry stakeholders conducted a series of flight tests integrating technologies from the Modeling & Simulation (M&S), Human Systems Integration (HSI), and Communication and Control (C2), and Integration, Test & Evaluation (IT&E) research areas. The last of the flight test series, Flight Test Series 6 (FT6) was conducted in late 2019 and focused on evaluating the interaction of the airborne non-cooperative surveillance system and the Detect and Avoid (DAA) technology. The DAA system generated conflict alert and guidance for pilots using a Research Ground Control System (RGCS) to avoid intruder aircraft. The conflict alerting and guidance information was presented on the RGCS’s display using symbology developed by the human factors team. The objective of FT6 was to investigate the interoperability of Low Size, Weight, and Power (Low SWaP) sensors with the DAA alerting, guidance, and display requirements. To support this goal, the distributed test environments (DTE) were developed at Ames Research Center (ARC) and Armstrong Flight Research Center (AFRC) and securely linked over a Virtual Private Network (VPN). These environments took advantage of existing Live Virtual Constructive (LVC) technologies to support research observation at both Centers with the insertion of live UAS and manned intruder aircraft into a simulated NAS environment with Air Traffic Control (ATC) and constructive manned aircraft. The experiment was distributed between AFRC flight operations and research facilities and the Distributed Simulation Research Laboratory (DSRL) and Software Development Laboratory (SDL) in building N243 at ARC. The Air Traffic Controller and pseudo pilots operated from the DSRL and SDL, respectively, using the Multi-Aircraft Control System (MACS). The test subject and researchers operated from the Research Ground Control Station (RGCS) at AFRC using the Vigilant Spirit Control Station (VSCS) and associated DAA software and displays. Flight Operation for the unmanned aircraft (UA) and manned intruder traffic was conducted at AFRC. Virtual traffic was managed by ARC. Voice distribution was accomplished using a combination of disparate communication systems at ARC and AFRC. The purpose of this document is to record the development, design, and execution of activities in support of the FT6 efforts from the perspective of the ARC IT&E team. Furthermore, the Armstrong IT&E team has published a thorough FT6 Test Report, with emphasis on flight test support, facilities and vehicle development; this report complements the Armstrong report. Analysis of collected FT6 data will be conducted and reported by the M&S and HSI teams and will be published in separate reports.

UAS-NAS↗
DOE OSTI2024

Guide to Developing Energy Services Interfaces

This document provides guidance to develop communications interfaces that are highly interoperable and adhere to a set of energy services interface (ESI) principles. It can be applied in the context of information and communications technology interface standards and implementation profiles that enable the integration of a facility with responsive distributed energy resources (DER) into an electric power system consistent with the fundamental ESI principles. In this context, a DER facility may consist of a single DER with a communicating controller or may be as complex as a microgrid campus with several buildings and many DERs. This document is not a technical interface standard, but the requirements described can be used to check that existing, augmented, or new interface standards meet the interoperability requirements of the ESI concept. In this way, this guide for the ESI specification can support future advancements in developing interoperability standards and implementation profiles. The intended audience for this document is DER integration practitioners and ecosystem groups that are in the business of developing and implementing communications interfaces for DER integration. It is intended that these groups apply the information and processes in this document to develop communications standards and implementation profiles that are consistent with fundamental ESI principles.

2030.5↗
NASA NTRS2010

Use of Dynamic Models and Operational Architecture to Solve Complex Navy Challenges

The United States Navy established 8 Maritime Operations Centers (MOC) to enhance the command and control of forces at the operational level of warfare. Each MOC is a headquarters manned by qualified joint operational-level staffs, and enabled by globally interoperable C41 systems. To assess and refine MOC staffing, equipment, and schedules, a dynamic software model was developed. The model leverages pre-existing operational process architecture, joint military task lists that define activities and their precedence relations, as well as Navy documents that specify manning and roles per activity. The software model serves as a "computational wind-tunnel" in which to test a MOC on a mission, and to refine its structure, staffing, processes, and schedules. More generally, the model supports resource allocation decisions concerning Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) at MOCs around the world. A rapid prototype effort efficiently produced this software in less than five months, using an integrated process team consisting of MOC military and civilian staff, modeling experts, and software developers. The work reported here was conducted for Commander, United States Fleet Forces Command in Norfolk, Virginia, code N5-0LW (Operational Level of War) that facilitates the identification, consolidation, and prioritization of MOC capabilities requirements, and implementation and delivery of MOC solutions.

Grande, Darby↗
NASA NTRSDate not supplied

Gateway - A Communications Platform for Lunar Exploration

As stated by a NASA administrator, “NASA, International Partners, and commercial partner are going forward to the moon. With Artemis, we will be exploring more of the Moon than ever before, and this time we are planning to stay. We will be demonstrating new technologies, capabilities, and business approaches needed for future exploration of Mars.” To support the complex, Artemis exploration campaign envisioned, the Gateway program is developing a communication network orbiting the Moon. Gateway will provide relay communication paths and radiometric tracking between crewed and robotic systems on the lunar surface or in cis-lunar space to mission control on the Earth. This paper is a high-level description of Gateway’s communication and ranging capabilities, the motivation and use of internationally developed interoperability standards, potential upgrade opportunities, and challenges as Gateway enables technology to support future Mars exploration.

Artemis↗