Results for “interoperability and control” — Page 8

NASA NTRS1997

Research in Satellite-Fiber Network Interoperability

This four part report evaluated the performance of high data rate transmission links using the ACTS satellite, and to provide a preparatory test framework for two of the space science applications that have been approved for tests and demonstrations as part of the overall ACTS program. The test plan will provide guidance and information necessary to find the optimal values of the transmission parameters and then apply these parameters to specific applications. The first part will focus on the satellite-to-earth link. The second part is a set of tests to study the performance of ATM on the ACTS channel. The third and fourth parts of the test plan will cover the space science applications, Global Climate Modeling and Keck Telescope Acquisition Modeling and Control.

Edelson, Burt↗

NASA NTRS2006

An Executable Choreography Framework for Dynamic Service-Oriented Architectures

Interoperability and loose coupling requirements are pushing the next generation of distributed applications towards more decentralized and more dynamic interaction schemes, which the classic requestJresponse communication paradigm can hardly accommodate. Hence, sound foundations and mechanisms for the establishment of unmticiptitteb peer-to-peer interactions across organizational boundaries are of significant importance to upcoming middleware platforms. The Executable Choreography Framework (ECF) is a middleware-level framework that targets dynamic and decentralized service compositions. The ECF combines transparent context propagation with aspect-oriented software composition techniques to dynamically refine the default control and data flow of service invocations. The framework provides a ground for experimentation with dynamic and distributed workflows, and a base to assess their safety and applicability when depioyed across organizational boundaries.

Akkawi, Faisal↗

NASA NTRS2012

A System to Provide Real-Time Collaborative Situational Awareness by Web Enabling a Distributed Sensor Network

In this paper, we describe the architecture of both the PATS and SAP systems and how these two systems interoperate with each other forming a unified capability for deploying intelligence in hostile environments with the objective of providing actionable situational awareness of individuals. The SAP system works in concert with the UICDS information sharing middleware to provide data fusion from multiple sources. UICDS can then publish the sensor data using the OGC's Web Mapping Service, Web Feature Service, and Sensor Observation Service standards. The system described in the paper is able to integrate a spatially distributed sensor system, operating without the benefit of the Web infrastructure, with a remote monitoring and control system that is equipped to take advantage of SWE.

Visualization↗

NASA NTRS2002

Secure Remote Access Issues in a Control Center Environment

The ISS finally reached an operational state and exists for local and remote users. Onboard payload systems are managed by the Huntsville Operations Support Center (HOSC). Users access HOSC systems by internet protocols in support of daily operations, preflight simulation, and test. In support of this diverse user community, a modem security architecture has been implemented. The architecture has evolved over time from an isolated but open system to a system which supports local and remote access to the ISS over broad geographic regions. This has been accomplished through the use of an evolved security strategy, PKI, and custom design. Through this paper, descriptions of the migration process and the lessons learned are presented. This will include product decision criteria, rationale, and the use of commodity products in the end architecture. This paper will also stress the need for interoperability of various products and the effects of seemingly insignificant details.

Pitts, Lee↗

NASA NTRS2001

Runway Incursion Prevention System ADS-B and DGPS Data Link Analysis Dallas-Fort Worth International Airport

A Runway Incursion Prevention System (RIPS) was tested at the Dallas - Ft. Worth International Airport in October 2000. The system integrated airborne and ground components to provide both pilots and controllers with enhanced situational awareness, supplemental guidance cues, a real-time display of traffic information, and warning of runway incursions in order to prevent runway incidents while also improving operational capability. Rockwell Collins provided and supported a prototype Automatic Dependent Surveillance - Broadcast (ADS-B) system using 1090 MHz and a prototype Differential GPS (DGPS) system onboard the NASA Boeing 757 research aircraft. This report describes the Rockwell Collins contributions to the RIPS flight test, summarizes the development process, and analyzes both ADS-B and DGPS data collected during the flight test. In addition, results are report on interoperability tests conducted between the NASA Advanced General Aviation Transport Experiments (AGATE) ADS-B flight test system and the NASA Boeing 757 ADS-B system.

Timmerman, J.↗

NASA NTRS1986

Transportability, distributability and rehosting experience with a kernel operating system interface set

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Blumberg, F. C.↗

NASA NTRS1996

Towards the Interoperability of Web, Database, and Mass Storage Technologies for Petabyte Archives

At the San Diego Supercomputer Center, a massive data analysis system (MDAS) is being developed to support data-intensive applications that manipulate terabyte sized data sets. The objective is to support scientific application access to data whether it is located at a Web site, stored as an object in a database, and/or storage in an archival storage system. We are developing a suite of demonstration programs which illustrate how Web, database (DBMS), and archival storage (mass storage) technologies can be integrated. An application presentation interface is being designed that integrates data access to all of these sources. We have developed a data movement interface between the Illustra object-relational database and the NSL UniTree archival storage system running in a production mode at the San Diego Supercomputer Center. With this interface, an Illustra client can transparently access data on UniTree under the control of the Illustr DBMS server. The current implementation is based on the creation of a new DBMS storage manager class, and a set of library functions that allow the manipulation and migration of data stored as Illustra 'large objects'. We have extended this interface to allow a Web client application to control data movement between its local disk, the Web server, the DBMS Illustra server, and the UniTree mass storage environment. This paper describes some of the current approaches successfully integrating these technologies. This framework is measured against a representative sample of environmental data extracted from the San Diego Ba Environmental Data Repository. Practical lessons are drawn and critical research areas are highlighted.

Moore, Reagan↗

NASA NTRSDate not supplied

Microbial Vessel for Impedance Spectroscopy and Electrochemistry (Mvise): an Extensible, Interoperable Data Acquisition Platform for Liquid Culture Studies in Space Biology Research

The White House Office of Science and Technology Policy (OSTP) has declared 2023 to be the Year of Open Science following an initiative to democratize scientific knowledge. Simultaneously, new sensor technologies have broadened the experimental space available to bioastronautics research. With these open-science goals and technological advances in mind, we have designed and constructed a data acquisition platform for high-precision, real-time monitoring of liquid culture systems. The vessel rig is fitted with six Atlas Scientific probes (micro pH, electrical conductivity, dissolved oxygen, oxidation-reduction potential, liquid temperature, air CO2) and a custom optical density probe similar to the one on BioSentinel’s BioSensor payload. A custom dielectric spectroscopy probe is also planned. The structure of the vessel is resin 3-D printed on a hobbyist-level machine, reducing the production cost and iteration time by over 60% each while increasing extensibility. Data acquisition and storage is controlled with a standalone C state machine-based program running on a Raspberry Pi 3 Model B. When not running headless, an additional program automatically generates and updates plots for live data visualization. Validation of the rig as a data collection system was performed with a yeast liquid culture experiment. While the vessel rig is currently used for standalone experiments, it can also be used as the base perception unit in a self-driving laboratory (SDL). SDLs are high-throughput data collection systems that employ automation and artificial intelligence to conduct and manage routine experiments. Here, we envision an SDL driven by several vessel rigs in which an automated script compares key results, informing the design of future experiments. A vessel rig SDL would streamline many operations, including 1) strain selection for the Lunar Explorer Instrument for space biology Applications (LEIA) investigation and 2) the study of bioregenerative life support systems (BLSS). Ultimately, the datasets that can now be acquired will provide crucial information for accelerating bioastronautics application development in the era of commercial space.

Stephen Lantin↗

NASA NTRS2001

Space Shuttle RTOS Bayesian Network

With shrinking budgets and the requirements to increase reliability and operational life of the existing orbiter fleet, NASA has proposed various upgrades for the Space Shuttle that are consistent with national space policy. The cockpit avionics upgrade (CAU), a high priority item, has been selected as the next major upgrade. The primary functions of cockpit avionics include flight control, guidance and navigation, communication, and orbiter landing support. Secondary functions include the provision of operational services for non-avionics systems such as data handling for the payloads and caution and warning alerts to the crew. Recently, a process to selection the optimal commercial-off-the-shelf (COTS) real-time operating system (RTOS) for the CAU was conducted by United Space Alliance (USA) Corporation, which is a joint venture between Boeing and Lockheed Martin, the prime contractor for space shuttle operations. In order to independently assess the RTOS selection, NASA has used the Bayesian network-based scoring methodology described in this paper. Our two-stage methodology addresses the issue of RTOS acceptability by incorporating functional, performance and non-functional software measures related to reliability, interoperability, certifiability, efficiency, correctness, business, legal, product history, cost and life cycle. The first stage of the methodology involves obtaining scores for the various measures using a Bayesian network. The Bayesian network incorporates the causal relationships between the various and often competing measures of interest while also assisting the inherently complex decision analysis process with its ability to reason under uncertainty. The structure and selection of prior probabilities for the network is extracted from experts in the field of real-time operating systems. Scores for the various measures are computed using Bayesian probability. In the second stage, multi-criteria trade-off analyses are performed between the scores. Using a prioritization of measures from the decision-maker, trade-offs between the scores are used to rank order the available set of RTOS candidates.

Morris, A. Terry↗

NASA NTRS2013

Navigation Performance of Global Navigation Satellite Systems in the Space Service Volume

This paper extends the results I reported at this year's ION International Technical Meeting on multi-constellation GNSS coverage by showing how the use of multi-constellation GNSS improves Geometric Dilution of Precision (GDOP). Originally developed to provide position, navigation, and timing for terrestrial users, GPS has found increasing use for in space for precision orbit determination, precise time synchronization, real-time spacecraft navigation, and three-axis attitude control of Earth orbiting satellites. With additional Global Navigation Satellite Systems (GNSS) coming into service (GLONASS, Galileo, and Beidou) and the development of Satellite Based Augmentation Services, it is possible to obtain improved precision by using evolving multi-constellation receiver. The Space Service Volume formally defined as the volume of space between three thousand kilometers altitude and geosynchronous altitude ((is) approximately 36,500 km), with the volume below three thousand kilometers defined as the Terrestrial Service Volume (TSV). The USA has established signal requirements for the Space Service Volume (SSV) as part of the GPS Capability Development Documentation (CDD). Diplomatic efforts are underway to extend Space service Volume commitments to the other Position, Navigation, and Timing (PNT) service providers in an effort to assure that all space users will benefit from the enhanced capabilities of interoperating GNSS services in the space domain.

Force, Dale A.↗

NASA NTRS2010

CCSDS - Advancing Spaceflight Technology for International Collaboration

The Consultative Committee for Space Data Systems (CCSDS) has been developing data and communications standards since 1982, with the objective of providing interoperability for enabling international collaboration for spaceflight missions. As data and communications technology has advanced, CCSDS has progressed to capitalize on existing products when available and suitable for spaceflight, and to develop innovative new approaches when available products fail. The current scope of the CCSDS architecture spans the end-to-end data architecture of a spaceflight mission, with ongoing efforts to develop and standardize cutting-edge technology. This manuscript describes the overall architecture, the position of CCSDS in the standards and international mission community, and some CCSDS processes. It then highlights in detail several of the most interesting and critical technical areas in work right now, and how they support collaborative missions. Special topics include: Delay/Disruption Tolerant Networking (DTN), Asynchronous Message Service (AMS), Multispectral/Hyperspectral Data Compression (MHDC), Coding and Synchronization, Onboard Wireless, Spacecraft Monitor and Control, Navigation, Security, and Time Synchronization/Correlation. Broad international participation in development of CCSDS standards is encouraged.

Kearney, Mike↗

NASA NTRS2016

High Data Rate Architecture (HiDRA)

One of the greatest challenges in developing new space technology is in navigating the transition from ground based laboratory demonstration at Technology Readiness Level 6 (TRL-6) to conducting a prototype demonstration in space (TRL-7). This challenge is com- pounded by the relatively low availability of new spacecraft missions when compared with aeronautical craft to bridge this gap, leading to the general adoption of a low-risk stance by mission management to accept new, unproven technologies into the system. Also in consideration of risk, the limited selection and availability of proven space-grade components imparts a severe limitation on achieving high performance systems by current terrestrial technology standards. Finally from a space communications point of view the long duration characteristic of most missions imparts a major constraint on the entire space and ground network architecture, since any new technologies introduced into the system would have to be compliant with the duration of the currently deployed operational technologies, and in some cases may be limited by surrounding legacy capabilities. Beyond ensuring that the new technology is verified to function correctly and validated to meet the needs of the end users the formidable challenge then grows to additionally include: carefully timing the maturity path of the new technology to coincide with a feasible and accepting future mission so it flies before its relevancy has passed, utilizing a limited catalog of available components to their maximum potential to create meaningful and unprecedented new capabilities, designing and ensuring interoperability with aging space and ground infrastructures while simultaneously providing a growth path to the future. The International Space Station (ISS) is approaching 20 years of age. To keep the ISS relevant, technology upgrades are continuously taking place. Regarding communications, the state-of-the-art communication system upgrades underway include high-rate laser terminals. These must interface with the existing, aging data infrastructure. The High Data Rate Architecture (HiDRA) project is designed to provide networked store, carry, and forward capability to optimize data flow through both the existing radio frequency (RF) and new laser communications terminal. The networking capability is realized through the Delay Tolerant Networking (DTN) protocol, and is used for scheduling data movement as well as optimizing the performance of existing RF channels. HiDRA is realized as a distributed FPGA memory and interface controller that is itself controlled by a local computer running DTN software. Thus HiDRA is applicable to other arenas seeking to employ next-generation communications technologies, e.g. deep space. In this paper, we describe HiDRA and its far-reaching research implications.

DTN↗

NASA NTRS1997

Study and Simulation of Enhancements for TCP (Transmission Control Protocol) Performance Over Noisy, High-Latency Links

The designers of the TCP/IP protocol suite explicitly included support of satellites in their design goals. The goal of the Internet Project was to design a protocol which could be layered over different networking technologies to allow them to be concatenated into an internet. The results of this project included two protocols, IP and TCP. IP is the protocol used by all elements in the network and it defines the standard packet format for IP datagrams. TCP is the end-to-end transport protocol commonly used between end systems on the Internet to derive a reliable bi-directional byte-pipe service from the underlying unreliable IP datagram service. Satellite links are explicitly mentioned in Vint Cerf's 2-page article which appeared in 1980 in CCR [2] to introduce the specifications for IP and TCP. In the past fifteen years, TCP has been demonstrated to work over many differing networking technologies, including over paths including satellites links. So if satellite links were in the minds of the designers from the beginning, what is the problem? The problem is that the performance of TCP has in some cases been disappointing. A goal of the authors of the original specification of TCP was to specify only enough behavior to ensure interoperability. The specification left a number of important decisions, in particular how much data is to be sent when, to the implementor. This was deliberately' done. By leaving performance-related decisions to the implementor, this would allow the protocol TCP to be tuned and adapted to different networks and situations in the future without the need to revise the specification of the protocol, or break interoperability. Interoperability would continue while future implementations would be allowed flexibility to adapt to needs which could not be anticipated at the time of the original protocol design.

Shepard, Timothy J.↗

NASA NTRSDate not supplied

Earth-Independent Medical Operations (EIMO) Concept of Operations

Compared to the current paradigm for crew health in low-Earth orbit and Lunar missions that rely on constant communication with Mission Control, there is an anticipated shift in medical operations for deep-space exploration missions. This shift stems from mission constraints imposed by the considerable distance from Earth, which include resource limitations due to a lack of resupply, mass, power, volume, and data limitations, challenges imposed by communication latency and the inability to evacuate in case of emergencies. To transition towards a more self-reliant medical approach, a comprehensive strategy is essential to progressively enable crew autonomy and mitigate mission success risks in the challenging environment of space. This transformative shift is collectively referred to as "Earth-Independent Medical Operations" (EIMO), signifying the gradual transfer of medical care and decision-making from terrestrial resources to space-based assets. This transition is aimed at bolstering astronaut health and performance while simultaneously reducing the overall risks associated with space missions. The constraints related to EIMO necessitate an integrated development of medical systems, featuring interoperability with mission planning, vehicle design, spacesuit design, and data architecture. This integration is vital in establishing a robust medical infrastructure that not only supports the well-being of astronauts but also ensures the success of the mission as a whole. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a model-based Concept of Operations (ConOps) outlining an initial vision for EIMO. Within this ConOps, a comprehensive view is presented, encompassing stakeholder needs, system objectives, and system goals associated with EIMO. Additionally, it provides illustrative examples of the various activities (scenarios) for which the system will be employed during missions. The selection of these activities has been meticulous, aiming to encompass a wide spectrum of medical conditions, including those falling under different risk categories, such as low-likelihood-low-consequence, low-likelihood-high-consequence, and high-likelihood-low-consequence. The selection of these activities (scenarios) effectively encompasses the wide range of medical events situated within an assumed probability-consequence bell curve. In each scenario, at least one of the five main EIMO components identified is captured. Those EIMO components are: Pre-mission Planning, Acute and Emergent Management Decision Making, Prolonged Medical Management Decision Making, Supplies and Resource Management, and Task Load Management. The ConOps was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA and aims to serve as an initial recommendation to gradually and safely enabling crew autonomy for Mars missions and beyond.

Earth Independent Medical Operations↗

NASA NTRS2024

Earth-Independent Medical Operations (EIMO) Concept of Operations (ConOps)

Compared to the current paradigm for crew health in low-Earth orbit and Lunar missions that rely on constant communication with Mission Control, there is an anticipated shift in medical operations for deep-space exploration missions. This shift stems from mission constraints imposed by the considerable distance from Earth, which include resource limitations due to a lack of resupply, mass, power, volume, and data limitations, challenges imposed by communication latency and the inability to evacuate in case of emergencies. To transition towards a more self-reliant medical approach, a comprehensive strategy is essential to progressively enable crew autonomy and mitigate mission success risks in the challenging environment of space. This transformative shift is collectively referred to as "Earth-Independent Medical Operations" (EIMO), signifying the gradual transfer of medical care and decision-making from terrestrial resources to space-based assets. This transition is aimed at bolstering astronaut health and performance while simultaneously reducing the overall risks associated with space missions. The constraints related to EIMO necessitate an integrated development of medical systems, featuring interoperability with mission planning, vehicle design, spacesuit design, and data architecture. This integration is vital in establishing a robust medical infrastructure that not only supports the well-being of astronauts but also ensures the success of the mission as a whole. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a model-based Concept of Operations (ConOps) outlining an initial vision for EIMO. Within this ConOps, a comprehensive view is presented, encompassing stakeholder needs, system objectives, and system goals associated with EIMO. Additionally, it provides illustrative examples of the various activities (scenarios) for which the system will be employed during missions. The selection of these activities has been meticulous, aiming to encompass a wide spectrum of medical conditions, including those falling under different risk categories, such as low-likelihood-low-consequence, low-likelihood-high-consequence, and high-likelihood-low-consequence. The selection of these activities (scenarios) effectively encompasses the wide range of medical events situated within an assumed probability-consequence bell curve. In each scenario, at least one of the five main EIMO components identified is captured. Those EIMO components are: Pre-mission Planning, Acute and Emergent Management Decision Making, Prolonged Medical Management Decision Making, Supplies and Resource Management, and Task Load Management. The ConOps was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA and aims to serve as an initial recommendation to gradually and safely enabling crew autonomy for Mars missions and beyond.

Earth Independent Medical Operations↗

NASA NTRSDate not supplied

Gateway at the Crossroads of Sustainable Lunar Exploration

The Gateway Program has made substantial design and development progress toward delivering a small, human-tended lunar space station purposefully designed to enable sustainable human exploration. The Program integrates partners and providers organizationally and physically as part of the spacecraft. The Power and Propulsion Element (PPE) and the Habitation and Logistics Outpost (HALO) with the European System Providing Refueling, Infrastructure and Telecommunications (ESPRIT) HALO Lunar Communications System (HLCS) have begun manufacturing the long lead components and will be launched first as a Co-Manifested Vehicle (CMV). The International Habitat (I-Hab) and ESPRIT Refueling Module (ERM) are passing life cycle milestones and include capabilities key for human crewmembers, such as windows, private sleeping quarters, and galley functions. The Logistics Module (LM) may provide a variety of services to Gateway depending on each mission. Requirements for the airlock have been developed, including requests that it support the integrated spacecraft with functions like augmenting heat rejection capabilities, and interfaces with new spacesuits will soon be developed in more detail. As a critical element of the architecture for solar system exploration, Gateway implements key tenets and features of international interoperability standards necessary to operate with multiple visiting vehicles and lunar assets, especially avionics, communications, and docking. Specific choices such as software architecture and standards, power standards, and robotics standards make it possible to utilize heritage or proprietary technology, yet still operate as one spacecraft. Engineering teams are evaluating many possible future missions to be executed at or utilizing the Gateway. The system architecture protects for an evolvable, extensible, and flexible capability. Designing systems robust enough to serve as a cornerstone of exploration activities for decades while remaining adaptable is not without its challenges. The detailed integration activities have revealed challenges and the need to mature key technologies. Refueling is a key component of achieving long life for Gateway, with unique operations to plan, safety concerns to mitigate, and risk reduction activities to conduct to better understand the system. The constraints and impacts of the design of visiting vehicles is also an important concern, with orientation constraints, control of attitude and orbit of the Gateway with docked visiting vehicles. Tradeoffs between robust maintainable systems and lightweight, compact systems must be balanced. Opportunities still exist for adding additional advanced capabilities to increase and extend Gateway’s benefits, such as intravehicular robotics, autonomous Guidance Navigation and Control (GN&C), and augmented control propulsion, heat rejection, or other services.

Molly S Anderson↗

NASA NTRSDate not supplied

Gateway at the Crossroads of Sustainable Lunar Exploration

The Gateway Program has made substantial design and development progress toward delivering a small, human-tended lunar space station purposefully designed to enable sustainable human exploration. The Program integrates partners and providers organizationally and physically as part of the spacecraft. The Power and Propulsion Element (PPE) and the Habitation and Logistics Outpost (HALO) with the European System Providing Refueling, Infrastructure and Telecommunications (ESPRIT) HALO Lunar Communications System (HLCS) have begun manufacturing the long lead components and will be launched first as a Co-Manifested Vehicle (CMV). The International Habitat (I-Hab) and ESPRIT Refueling Module (ERM) are passing life cycle milestones and include capabilities key for human crewmembers, such as windows, private sleeping quarters, and galley functions. The Logistics Module (LM) may provide a variety of services to Gateway depending on each mission. Requirements for the airlock have been developed, including requests that it support the integrated spacecraft with functions like augmenting heat rejection capabilities, and interfaces with new spacesuits will soon be developed in more detail. As a critical element of the architecture for solar system exploration, Gateway implements key tenets and features of international interoperability standards necessary to operate with multiple visiting vehicles and lunar assets, especially avionics, communications, and docking. Specific choices such as software architecture and standards, power standards, and robotics standards make it possible to utilize heritage or proprietary technology, yet still operate as one spacecraft. Engineering teams are evaluating many possible future missions to be executed at or utilizing the Gateway. The system architecture protects for an evolvable, extensible, and flexible capability. Designing systems robust enough to serve as a cornerstone of exploration activities for decades while remaining adaptable is not without its challenges. The detailed integration activities have revealed challenges and the need to mature key technologies. Refueling is a key component of achieving long life for Gateway, with unique operations to plan, safety concerns to mitigate, and risk reduction activities to conduct to better understand the system. The constraints and impacts of the design of visiting vehicles is also an important concern, with orientation constraints, control of attitude and orbit of the Gateway with docked visiting vehicles. Tradeoffs between robust maintainable systems and lightweight, compact systems must be balanced. Opportunities still exist for adding additional advanced capabilities to increase and extend Gateway’s benefits, such as intravehicular robotics, autonomous Guidance Navigation and Control (GN&C), and augmented control propulsion, heat rejection, or other services.

Molly S Anderson↗

NASA NTRS2010

Joint Composable Object Model and LVC Methodology

Within the Department of Defense, multiple architectures are created to serve and fulfill one or several specific service or mission related LVC training goals. Multiple Object Models exist across and within those architectures and it is there that those disparate object models are a major source of interoperability problems when developing and constructing the training scenarios. The two most commonly used architectures are; HLA and TENA, with DIS and CTIA following close behind in terms of the number of users. Although these multiple architectures can share and exchange data the underlying meta-models for runtime data exchange are quite different, requiring gateways/translators to bridge between the different object model representations; while the Department of Defense's use of gateways are generally effective in performing these functions, as the LVC environment increases so too does the cost and complexity of these gateways. Coupled with the wide range of different object models across the various user communities we increase the propensity for run time errors, increased programmer stop gap measures during coordinated exercises, or failure of the system as a whole due to unknown or unforeseen incompatibilities. The Joint Composable Object Model (JCOM) project was established under an M&S Steering Committee (MSSC)-sponsored effort with oversight and control placed under the Joint Forces Command J7 Advanced Concepts Program Directorate. The purpose of this paper is to address the initial and the current progress that has been made in the following areas; the Conceptual Model Development Format, the Common Object Model, the Architecture Neutral Data Exchange Model (ANDEM), and the association methodology to allow the re-use of multiple architecture object models and the development of the prototype persistent reusable library.

Rheinsmith, Richard↗