DSMS information systems architecture (DISA) overview
Explore the source record for details and available documents.
DSMS Information Systems Architecture (DISA)↗
SEARCH · Search NASA
Results for “information architectures”
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.
Deep Space Network information system architecture study
The purpose of this article is to describe an architecture for the Deep Space Network (DSN) information system in the years 2000-2010 and to provide guidelines for its evolution during the 1990s. The study scope is defined to be from the front-end areas at the antennas to the end users (spacecraft teams, principal investigators, archival storage systems, and non-NASA partners). The architectural vision provides guidance for major DSN implementation efforts during the next decade. A strong motivation for the study is an expected dramatic improvement in information-systems technologies, such as the following: computer processing, automation technology (including knowledge-based systems), networking and data transport, software and hardware engineering, and human-interface technology. The proposed Ground Information System has the following major features: unified architecture from the front-end area to the end user; open-systems standards to achieve interoperability; DSN production of level 0 data; delivery of level 0 data from the Deep Space Communications Complex, if desired; dedicated telemetry processors for each receiver; security against unauthorized access and errors; and highly automated monitor and control.
Beswick, C. A.↗
Space-Based Information Infrastructure Architecture for Broadband Services
This study addressed four tasks: (1) identify satellite-addressable information infrastructure markets; (2) perform network analysis for space-based information infrastructure; (3) develop conceptual architectures; and (4) economic assessment of architectures. The report concludes that satellites will have a major role in the national and global information infrastructure, requiring seamless integration between terrestrial and satellite networks. The proposed LEO, MEO, and GEO satellite systems have satellite characteristics that vary widely. They include delay, delay variations, poorer link quality and beam/satellite handover. The barriers against seamless interoperability between satellite and terrestrial networks are discussed. These barriers are the lack of compatible parameters, standards and protocols, which are presently being evaluated and reduced.
Price, Kent M.↗
Mnemosyne
SAND2024-08570O Mnemosyne is an interactive tool for finding, retrieving, and exploring information about U.S. nuclear tests documented in the National Nuclear Security Administration’s NV-209 report. It also acts as an information architecture and codebase for integrating additional information and computational tools related to these tests at the unclassified and classified levels. Users can search by any number of nuclear test attributes—name, yield range, altitude ranges, purpose of a test—and find all matching tests. Users can also retrieve specific test information published in NV-209. The tool displays geospatial and topological data about test location, and it provides an information architecture for storing additional contextual material, such as photographs. Mnemosyne provides a capability of interfacing with HYCHEM, Sandia's nuclear detonation optical waveform tool. The software is designed for use by government, academia, military, and research institutions. The software will likely be advanced to integrate seismic data and the nuclear detonation optical signal simulation code radCTH. Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy’s National Nuclear Security Administration under contract DE-NA0003525.
Fisher, Dustin↗
Architecture and Information Requirements to Assess and Predict Flight Safety Risks During Highly Autonomous Urban Flight Operations
As aviation adopts new and increasingly complex operational paradigms, vehicle types, and technologies to broaden airspace capability and efficiency, maintaining a safe system will require recognition and timely mitigation of new safety issues as they emerge and before significant consequences occur. A shift toward a more predictive risk mitigation capability becomes critical to meet this challenge. In-time safety assurance comprises monitoring, assessment, and mitigation functions that proactively reduce risk in complex operational environments where the interplay of hazards may not be known (and therefore not accounted for) during design. These functions can also help to understand and predict emergent effects caused by the increased use of automation or autonomous functions that may exhibit unexpected non-deterministic behaviors. The envisioned monitoring and assessment functions can look for precursors, anomalies, and trends (PATs) by applying model-based and data-driven methods. Outputs would then drive downstream mitigation(s) if needed to reduce risk. These mitigations may be accomplished using traditional design revision processes or via operational (and sometimes automated) mechanisms. The latter refers to the ‘in-time’ aspect of the system concept. This report comprises architecture and information requirements and considerations toward enabling such a capability within the domain of low altitude highly autonomous urban flight operations. This domain may span, for example, public-use surveillance missions flown by small unmanned aircraft (e.g., infrastructure inspection, facility management, emergency response, law enforcement, and/or security) to transportation missions flown by larger aircraft that may carry passengers or deliver products. Caveat: Any stated requirements in this report should be considered initial requirements that are intended to drive research and development (R&D). These initial requirements are likely to evolve based on R&D findings, refinement of operational concepts, industry advances, and new industry or regulatory policies or standards related to safety assurance.
Young, Steven↗
Constellation's Command, Control, Communications and Information (C3I) Architecture
Operations concepts are highly effective for: 1) Developing consensus; 2) Discovering stakeholder needs, goals, objectives; 3) Defining behavior of system components (especially emergent behaviors). An interoperability standard can provide an excellent lever to define the capabilities needed for system evolution. Two categories of architectures are needed in a program of this size are: 1) Generic - Needed for planning, design and construction standards; 2) Specific - Needed for detailed requirement allocations, interface specs. A wide variety of architectural views are needed to address stakeholder concerns, including: 1) Physical; 2) Information (structure, flow, evolution); 3) Processes (design, manufacturing, operations); 4) Performance; 5) Risk.
constellation↗
JPL's Enterprise Information System Architecture: Summary of Recommendations
Explore the source record for details and available documents.
EISAT enterprise information system↗
An image based information system - Architecture for correlating satellite and topological data bases
The paper describes the development of an image based information system and its use to process a Landsat thematic map showing land use or land cover in conjunction with a census tract polygon file to produce a tabulation of land use acreages per census tract. The system permits the efficient cross-tabulation of two or more geo-coded data sets, thereby setting the stage for the practical implementation of models of diffusion processes or cellular transformation. Characteristics of geographic information systems are considered, and functional requirements, such as data management, geocoding, image data management, and data analysis are discussed. The system is described, and the potentialities of its use are examined.
Bryant, N. A.↗
Spaceport Command and Control System - Support Software Development
The Information Architecture Support (IAS) Team, the component of the Spaceport Command and Control System (SCCS) that is in charge of all the pre-runtime data, was in need of some report features to be added to their internal web application, Information Architecture (IA). Development of these reports is crucial for the speed and productivity of the development team, as they are needed to quickly and efficiently make specific and complicated data requests against the massive IA database. These reports were being put on the back burner, as other development of IA was prioritized over them, but the need for them resulted in internships being created to fill this need. The creation of these reports required learning Ruby on Rails development, along with related web technologies, and they will continue to serve IAS and other support software teams and their IA data needs.
Information Architecture↗
ELISA, a demonstrator environment for information systems architecture design
This paper describes an approach of reusability of software engineering technology in the area of ground space system design. System engineers have lots of needs similar to software developers: sharing of a common data base, capitalization of knowledge, definition of a common design process, communication between different technical domains. Moreover system designers need to simulate dynamically their system as early as possible. Software development environments, methods and tools now become operational and widely used. Their architecture is based on a unique object base, a set of common management services and they host a family of tools for each life cycle activity. In late '92, CNES decided to develop a demonstrative software environment supporting some system activities. The design of ground space data processing systems was chosen as the application domain. ELISA (Integrated Software Environment for Architectures Specification) was specified as a 'demonstrator', i.e. a sufficient basis for demonstrations, evaluation and future operational enhancements. A process with three phases was implemented: system requirements definition, design of system architectures models, and selection of physical architectures. Each phase is composed of several activities that can be performed in parallel, with the provision of Commercial Off the Shelves Tools. ELISA has been delivered to CNES in January 94, currently used for demonstrations and evaluations on real projects (e.g. SPOT4 Satellite Control Center). It is on the way of new evolutions.
Panem, Chantal↗
ECLSS Does Not Exist in a Vacuum: Integrated Analysis is Necessary to Inform System Architecture Decisions
Environmental Control and Life Support System (ECLSS) architecture selection has profound implications for mission cost and mass extending far beyond the ECLSS itself. Similarly, other mission architecture decisions – particularly involving transportation systems – can influence optimal ECLSS architectures. Loop closure influences requirements for water, oxygen, and other consumables. System maintainability and reliability influences spares mass and risk. System, consumables, and spares mass interact with transportation system architectures and propellant demands and propulsion element sizing. All these interactions with other systems must be considered when evaluating ECLSS options. Analyses that focus only on maximizing ECLSS loop closure – or minimizing ECLSS mass, or minimizing ECLSS life cycle cost – may lead to sub-optimal or even counterproductive system architecture and investment decisions at the mission level. For example, an ECLSS architecture that minimizes ECLSS lifecycle cost but results in excessively high logistics mass could lead to significantly increased transportation system costs or make interplanetary transportation infeasible. Increased loop closure could result in higher development costs and higher mass if system/spares mass increases outweigh consumables reduction. In addition, systems mass and consumables mass are not directly comparable and have different impacts on propellant requirements, as consumables mass changes over the course of the mission. This paper presents an integrated analysis examining the overall impact of different ECLSS and transportation architectures on mass for a crewed Mars mission, including the habitat and transportation systems as well as consumables, spares, and propellant. Key observations are discussed, along with opportunities for further sensitivity analysis and model development. Overall, ECLSS development activities must consider their impacts at the mission level, as part of an integrated system, rather than in isolation.
Systems Analysis↗
A Reference Architecture for Space Information Management
We describe a reference architecture for space information management systems that elegantly overcomes the rigid design of common information systems in many domains. The reference architecture consists of a set of flexible, reusable, independent models and software components that function in unison, but remain separately managed entities. The main guiding principle of the reference architecture is to separate the various models of information (e.g., data, metadata, etc.) from implemented system code, allowing each to evolve independently. System modularity, systems interoperability, and dynamic evolution of information system components are the primary benefits of the design of the architecture. The architecture requires the use of information models that are substantially more advanced than those used by the vast majority of information systems. These models are more expressive and can be more easily modularized, distributed and maintained than simpler models e.g., configuration files and data dictionaries. Our current work focuses on formalizing the architecture within a CCSDS Green Book and evaluating the architecture within the context of the C3I initiative.
information systems↗
Advance Reactor Operational Technology Architecture Categorization
Seven generation III+ and generation IV nuclear reactor types, based on twelve reactor concepts surveyed, are examined using functional decomposition to extract relevant operational technology (OT) architecture information. This information is compared to existing nuclear power plants (NPPs) OT architectures to highlight novel and emergent cyber risks associated with next generation NPPs. These insights can help inform operational technology architecture requirements that will be unique to a given reactor type. Next generation NPPs have streamlined OT architectures relative to the current generation II commercial NPP fleet. Overall, without compensatory measures that provide sufficient and efficient cybersecurity controls, next generation NPPs will have increased cyber risk. Verification and validation of cyber-physical testbeds and cyber risk assessment methodologies may be an important next step to reduce cyber risk in the OT architecture design and testing phase. Coordination with safety requirements can result in OT architecture design being an iterative process.
22 GENERAL STUDIES OF NUCLEAR REACTORS↗
Mind the Gap: Building Simulation in the Architectural Design Studio
Building modelling and simulation approaches are increasingly being utilized in architectural design studios to guide and inform the design process and offer evidence-based feedback on proposed building performance. The development of intuitive and simplified simulation interfaces has greatly contributed to achieving this integration. One aspect that is often overlooked is the workflow that governs and regulates integrated design, which can have significant impacts on final design outcomes. Currently there are numerous software packages available for building performance simulations. This makes it challenging to select an appropriate tool that provides accurate results yet allows a designer to make informed architectural decisions with a designer-friendly interface. Furthermore, workflows to incorporate simulations into the design process proved to highly impact student’s project design integration. Yet, it is not clear what type of workflows are successful to achieve this goal, under what conditions, and/or for which building and site typologies. This paper addresses these issues by first reviewing three different workflows for integrating building performance simulation processes and highlighting their strengths and weaknesses. Second, a comparative case study approach was employed to test three of the most common workflows in three different integrated design architectural studios at the senior and vertical studio levels as well as in two courses that run parallel and complementary to the design studios. The workflows, processes, and the resultant student projects were further analyzed based on criteria for better integrated design and architectural excellence as outlined in the American Institute of Architects Committee on the Environment (AIA COTE) Top 10 Student’s Competition. Third, to situate the pedagogical case studies’ results within a larger context, a survey of the AIA COTE Top 10 student competition award recipients over the last five years was conducted. The results are summarized in a pedagogical framework that outlines best strategies of the type of workflows, software, design process used, methods to achieve desired interaction between design process and analytical feedback, and metrics for educators to evaluate the success of this integration and their learning outcomes in the design studio. The goal is to help bridge the gap between the building design and simulation within the design studio’s creative process for more integrated design outcomes.
Elzeyadi, Ihab↗
Data-driven modeling of dislocation mobility from atomistics using physics-informed machine learning
Dislocation mobility, which dictates the response of dislocations to an applied stress, is a fundamental property of crystalline materials that governs the evolution of plastic deformation. Traditional approaches for deriving mobility laws rely on phenomenological models of the underlying physics, whose free parameters are in turn fitted to a small number of intuition-driven atomic scale simulations under varying conditions of temperature and stress. This tedious and time-consuming approach becomes particularly cumbersome for materials with complex dependencies on stress, temperature, and local environment, such as body-centered cubic crystals (BCC) metals and alloys. In this paper, we present a novel, uncertainty quantification-driven active learning paradigm for learning dislocation mobility laws from automated high-throughput large-scale molecular dynamics simulations, using Graph Neural Networks (GNN) with a physics-informed architecture. We demonstrate that this Physics-informed Graph Neural Network (PI-GNN) framework captures the underlying physics more accurately compared to existing phenomenological mobility laws in BCC metals.
36 MATERIALS SCIENCE↗
Safely Enabling Low-Altitude UAS Operations: Unmanned Aircraft System Traffic Management
Concept of operations; Roles, responsibilities, implications on who pays; Information architecture paved way for FAA's (Federal Aviation Administration's) RFI (Request for Information); Demonstrated initial feasibility of architecture, application-protocol-interface-based approach, and overall construct; Data exchange and protocols; Demonstration of UTM (Unmanned Aerial Systems Traffic Management) TCL1 (Tuscaloosa, AL Airport Terminal 1) with all 6 test sites; Initial demonstration of UTM TCL2 for BVLOS (Beyond Visual Line-of-Sight) requirements.
Low-altitude UTM↗
Antiterrorist Software
In light of the escalation of terrorism, the Department of Defense spearheaded the development of new antiterrorist software for all Government agencies by issuing a Broad Agency Announcement to solicit proposals. This Government-wide competition resulted in a team that includes NASA Lewis Research Center's Computer Services Division, who will develop the graphical user interface (GUI) and test it in their usability lab. The team launched a program entitled Joint Sphere of Security (JSOS), crafted a design architecture (see the following figure), and is testing the interface. This software system has a state-ofthe- art, object-oriented architecture, with a main kernel composed of the Dynamic Information Architecture System (DIAS) developed by Argonne National Laboratory. DIAS will be used as the software "breadboard" for assembling the components of explosions, such as blast and collapse simulations.
Clark, David A.↗
EVA Suit Studies: Human Forward Contamination Project
Background: NASA Strategic Knowledge Gap B5: Forward Contamination for Mars. Issue: we have knowledge gaps!: Whether / how microbes are released from crewed pressure systems. Why do we care?: Informs Mars operational concepts - How to protect the science; Informs architecture decisions - How “open” Environmental Control and Life Support (ECLS) systems are; Informs landing site selection decisions - How close we can land / operate to where life may be present. Project goal: get some data to fill in these gaps: Data will help determine whether we’re ready to go to Mars, or if we need to change our systems or operational designs.
Rucker, Michelle↗