Search NASA⌕ Search

SEARCH · Search NASA

Results for “Enterprise Architecture”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission type, domain component, causal fault, and other key characteristics. The repository has a firm structure, initial collection of data, and an interface established for informational queries, with plans for integration within the Enterprise Architecture at NASA IVV, enabling support and accessibility across the Agency. The development of an improved workflow process for adaptive, risk-informed FM assurance is currently underway.

Software Verification & Validation↗
NASA NTRS2007

NASA's Core Trajectory Sub-System Project: Using JBoss Enterprise Middleware for Building Software Systems Used to Support Spacecraft Trajectory Operations

NASA's Johnson Space Center (JSC) / Flight Design and Dynamics Division (DM) has prototyped the use of Open Source middleware technology for building its next generation spacecraft mission support system. This is part of a larger initiative to use open standards and open source software as building blocks for future mission and safety critical systems. JSC is hoping to leverage standardized enterprise architectures, such as Java EE, so that its internal software development efforts can be focused on the core aspects of their problem domain. This presentation will outline the design and implementation of the Trajectory system and the lessons learned during the exercise.

Stensrud, Kjell C.↗
NASA NTRS2010

Cyberinfrastructure for Aircraft Mission Support

Forth last several years NASA's Airborne Science Program has been developing and using infrastructure and applications that enable researchers to interact with each other and with airborne instruments via network communications. Use of these tools has increased near realtime situational awareness during field operations, resulting it productivity improvements, improved decision making, and the collection of better data. Advances in pre-mission planning and post-mission access have also emerged. Integrating these capabilities with other tools to evolve coherent service-oriented enterprise architecture for aircraft flight and test operations is the subject of ongoing efforts.

Freudinger, Lawrence C.↗
NASA NTRS2019

Application of AI in the NAS - the Rationale for AI-Enhanced Airspace Management

This paper extends on the initial findings of "Application of Artificial Intelligence in the National Airspace System: A Primer" (Stroup & Niewoehner: Herndon, VA; ICNS-2019), and looks at why the current technologies, enterprise architecture, and future program plans may not be enough to address persistent operational challenges. This paper further explores why emergent operational concepts, business models, and demand profiles may necessitate AI-enhanced Communications, Navigation and Communications (CNS) infrastructure to disrupt current operational impediments. European airspace, as well as the NAS, has similar challenges. Key challenges explored in this study include: quantifiable improvements to NAS capacity, efficiency, and resiliency; traffic flow management of diverse users; UTM-ATM airspace integration; equitable access to airspace; and airborne-ground interoperability of AI applications. Finally, we examine why trustworthiness and resiliency will be key mileposts on the regulatory pathway to AI certification.

Aviation↗
NASA NTRS2014

A Systems Engineering Approach to Architecture Development

Architecture development is conducted prior to system concept design when there is a need to determine the best-value mix of systems that works collectively in specific scenarios and time frames to accomplish a set of mission area objectives. While multiple architecture frameworks exist, they often require use of unique taxonomies and data structures. In contrast, this presentation characterizes architecture development using terminology widely understood within the systems engineering community. Using a notional civil space architecture example, it employs a multi-tier framework to describe the enterprise level architecture and illustrates how results of lower tier, mission area architectures integrate into the enterprise architecture. It also presents practices for conducting effective mission area architecture studies, including establishing the trade space, developing functions and metrics, evaluating the ability of potential design solutions to meet the required functions, and expediting study execution through the use of iterative design cycles.

Architecture Development↗
NASA NTRS2015

A Systems Engineering Approach to Architecture Development

Architecture development is often conducted prior to system concept design when there is a need to determine the best-value mix of systems that works collectively in specific scenarios and time frames to accomplish a set of mission area objectives. While multiple architecture frameworks exist, they often require use of unique taxonomies and data structures. In contrast, this paper characterizes architecture development using terminology widely understood within the systems engineering community. Using a notional civil space architecture example, it employs a multi-tier framework to describe the enterprise level architecture and illustrates how results of lower tier, mission area architectures integrate into the enterprise architecture. It also presents practices for conducting effective mission area architecture studies, including establishing the trade space, developing functions and metrics, evaluating the ability of potential design solutions to meet the required functions, and expediting study execution through the use of iterative design cycles.

Multi-tier Framework↗
NASA NTRS2015

A Systems Engineering Approach to Architecture Development

Architecture development is often conducted prior to system concept design when there is a need to determine the best-value mix of systems that works collectively in specific scenarios and time frames to accomplish a set of mission area objectives. While multiple architecture frameworks exist, they often require use of unique taxonomies and data structures. In contrast, this paper characterizes architecture development using terminology widely understood within the systems engineering community. Using a notional civil space architecture example, it employs a multi-tier framework to describe the enterprise level architecture and illustrates how results of lower tier, mission area architectures integrate into the enterprise architecture. It also presents practices for conducting effective mission area architecture studies, including establishing the trade space, developing functions and metrics, evaluating the ability of potential design solutions to meet the required functions, and expediting study execution through the use of iterative design cycles

Architecture Development↗
NASA NTRSDate not supplied

Long -Term Architecture Development For The Moon And M

Developing an enterprise-level architecture encompassing future human-robotic science and exploration at the Moon and Mars requires a visionary approach that ensures NASA is responsive to national priorities and global science and technology advancement objectives. While the initial capabilities needed to return humans to the Moon may be well understood, NASA is still formulating a long-term infrastructure at the Moon and working to narrow the trade space for the first human missions to Mars. This paper will focus on the formulation and current status of engineering and design applications for a long-term and robust lunar architecture that will implement the Artemis Base Camp concept, including pre-formulation activities and elements currently in formulation. Authors will demonstrate how the Moon-to-Mars campaign approach fosters commonality of requirements and standards across individual mission elements, as well as multi-destination systems and operations, to reduce risk and encourage healthy competition in the growing space market. Among the Artemis Base Camp elements discussed will be multiple surface mobility elements, a fixed, anchoring surface habitat, fission surface power, and an in-situ resource development pilot plant. The narrative will clearly illustrate the direct evolution of the base camp elements to a minimal Mars architecture concept, and also outline unique development efforts that will be required in the next decade to make it possible to send humans to the Red Planet as early as the 2030s.

Greg Chavers↗
NASA NTRS2001

Space Internet Architectures and Technologies for NASA Enterprises

NASA's future communications services will be supplied through a space communications network that mirrors the terrestrial Internet in its capabilities and flexibility. The notional requirements for future data gathering and distribution by this Space Internet have been gathered from NASA's Earth Science Enterprise (ESE), the Human Exploration and Development in Space (HEDS), and the Space Science Enterprise (SSE). This paper describes a communications infrastructure for the Space Internet, the architectures within the infrastructure, and the elements that make up the architectures. The architectures meet the requirements of the enterprises beyond 2010 with Internet 'compatible technologies and functionality. The elements of an architecture include the backbone, access, inter-spacecraft and proximity communication parts. From the architectures, technologies have been identified which have the most impact and are critical for the implementation of the architectures.

Bhasin, Kul↗
NASA NTRS2011

Human Exploration Framework Team: Strategy and Status

Human Exploration Framework Team (HEFT) was formulated to create a decision framework for human space exploration that drives out the knowledge, capabilities and infrastructure NASA needs to send people to explore multiple destinations in the Solar System in an efficient, sustainable way. The specific goal is to generate an initial architecture that can evolve into a long term, enterprise-wide architecture that is the basis for a robust human space flight enterprise. This paper will discuss the initial HEFT activity which focused on starting up the cross-agency team, getting it functioning, developing a comprehensive development and analysis process and conducting multiple iterations of the process. The outcome of this process will be discussed including initial analysis of capabilities and missions for at least two decades, keeping Mars as the ultimate destination. Details are provided on strategies that span a broad technical and programmatic trade space, are analyzed against design reference missions and evaluated against a broad set of figures of merit including affordability, operational complexity, and technical and programmatic risk.

High Earth Orbit (HEO),↗
NASA NTRS1990

IDEF5 Ontology Description Capture Method: Concept Paper

The results of research towards an ontology capture method referred to as IDEF5 are presented. Viewed simply as the study of what exists in a domain, ontology is an activity that can be understood to be at work across the full range of human inquiry prompted by the persistent effort to understand the world in which it has found itself - and which it has helped to shape. In the contest of information management, ontology is the task of extracting the structure of a given engineering, manufacturing, business, or logistical domain and storing it in an usable representational medium. A key to effective integration is a system ontology that can be accessed and modified across domains and which captures common features of the overall system relevant to the goals of the disparate domains. If the focus is on information integration, then the strongest motivation for ontology comes from the need to support data sharing and function interoperability. In the correct architecture, an enterprise ontology base would allow th e construction of an integrated environment in which legacy systems appear to be open architecture integrated resources. If the focus is on system/software development, then support for the rapid acquisition of reliable systems is perhaps the strongest motivation for ontology. Finally, ontological analysis was demonstrated to be an effective first step in the construction of robust knowledge based systems.

Menzel, Christopher P.↗
NASA NTRS2002

Architecting an approach to knowledge management

This paper sets forth a method to develop an architectural approach to the design, development, creation, and implementation of knowledge management at a specific organization.

knowledge management information technology organi↗
NASA NTRS1997

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↗
NASA NTRSDate not supplied

Role of Low Cost Missions in Preparing for Human Mars Exploration

Developing an enterprise-level architecture encompassing future human-robotic science and exploration at the Moon and Mars requires a visionary approach to ensure NASA is responsive to national priorities and global science and technology advancement objectives. While the initial capabilities needed to return humans to the Moon may be well understood, NASA is still formulating a long-term infrastructure at the Moon and working to narrow the trade space for the first human missions to Mars. This talk will focus on the formulation and current status of engineering and design applications for a long-term and robust exploration architecture.

Mars↗
NASA NTRSDate not supplied

UAM Airspace Research Roadmap Orientation

Introduce the UAM Airspace Research Roadmap - What it is, how it is being used, and how you can help - A living document that describes how research informs the progression of UAM airspace capabilities.

roadmap↗
NASA NTRS2022

NASA Enterprise Digital Transformation Initiative Strategic Framework & Implementation Approach

Since 1958, NASA has delivered its enduring bold purpose, characterized in the 2022 NASA Strategic Plan as a mission to discover, explore, innovate, and advance solutions to the problems of flight, within and outside the Earth’s atmosphere, for the benefit of humankind. The NASA Strategic Plan also recognizes that this mission will be delivered differently as it looks to a future marked by radical global change, which is in part being driven by digital advances. For this reason, in late 2020 NASA established an Enterprise Digital Transformation (DT) agency-level strategic initiative to accelerate and coordinate leveraging digital advances to transform the way the Agency works, the experience of its workforce and the agility of its workplace. This paper documents NASA’s DT strategic framework and associated implementation approach, with the DT strategic initiative serving to ignite, connect, integrate, and facilitate DT progress across a federated organizational operating model.

digital transformation↗
DOE OSTI2022

Simulating Energy and Security Interactions in Semiconductor Manufacturing: Insights from the Intel Minifab Model

Semiconductor manufacturing is a highly complex. Fabrication plants must deal with re-entrant flows to support multiple types of wafers being produced simultaneously, each with their own deadlines and specifications. The manufacturing process itself depends upon the ability to control and programmatically adjust a variety of environmental conditions including temperature, humidity, and air quality. In addition, wafer fabrication consumes large amounts of electricity. Emerging technologies may help reduce the energy footprint of such facilities but can introduce cybersecurity risks. Therefore, this paper presents a modeling and simulation framework to quantify tradeoffs between operational measures of performance, energy consumption, and cybersecurity controls. We augment the Intel Minifab model, with the Purdue Enterprise Reference Architecture (PERA) for cybersecurity as well as tool-level energy consumption data from a real-world semiconductor manufacturing testbed. In this manner, we intend to provide stakeholders with a systematic, data-driven approach to evaluate emerging risks within the manufacturing process.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗