SEARCH · Search NASA

Results for “Enterprise”

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.

SourceResearch connectionFrom yearThrough year

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

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS2016

Tailoring NIST Security Controls for the Ground System: Selection and Implementation -- Recommendations for Information System Owners

The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).

GOVERNANCE↗

NASA NTRS2018

What is EA?

An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives. A single slide PowerPoint, size 36" x 48" has been produced for printing onto a poster board for display in the Pathways Internship showcase November 2018. This poster board presentation is a display of my internship from 2014 to present, to include my NIFS (NASA Interns, Fellowships, Scholarships) internship, ITSS (Information Technology Support Services) contract, and current Pathways internship. The presentation discusses my years producing deliverables for: the ISS (International Space Station) Anomaly Project in 2014, the FJET (Frangible Joint Empirical Test) database project in 2015, the CUI (Compact Unique Identifier) project in early 2016, and various Enterprise Architecture deliverables and contributions such as the Roadmap SQL (Structured Query Language) stored procedure and architectural views of Program data elements.

MySQL↗

NASA NTRS1995

NASA strategic plan

NASA's Plan summarizes the Agency's vision, mission, and values. Specific goals are listed for each externally focused Enterprise: Mission to Planet Earth, Aeronautics, Human Exploration and Development of Space, Space Science, and Space Technology. These Enterprises satisfy the needs of customers external to NASA. The Strategic Functions (Space Communications, Human Resources, and Physical Resources) are necessary in order to meet the goals of the Enterprises. The goals of these Functions are also presented. All goals must be met while adhering to the discussed values and operating principles of NASA. A final section outlines the implementing strategy.

Source record↗

NASA NTRS1993

Role of strategic planning in engineering management

Today, more than ever before, engineers are faced with uncertain and sometimes chaotic environments in which to function. The traditional roles of an engineer to design, develop, and streamline a manufacturing process for a product are still valued and relevant. However, the need for an engineer to participate in the process of identifying the product to be developed, the schedule and resources required, and the goal of satisfying the customer, has become paramount to achieving the success of the enterprise. When we include these endeavors in the functions of an engineer, management of 'engineering' takes on a new dimension. In this paper, the ramifications of the changing and increased functions of an engineer and consequent impacts on engineering management are explored. The basic principles which should be invoked in order to embrace the new environment for engineering management are outlined. The ultimate finding of this study is that the enterprise strategic plan should be developed in such a way as to allow engineering management to encompass the full spectrum of the responsibilities of engineers. A consequence of this is that the fundamental elements of the strategic process can best be implemented through a project team or group approach. The paper thus concentrates on three areas: evolving environment, strategic plan, and ways to achieve enterprise success.

Krishen, Kumar↗

NASA NTRS1997

NASA Accountability Report

NASA is piloting fiscal year (FY) 1997 Accountability Reports, which streamline and upgrade reporting to Congress and the public. The document presents statements by the NASA administrator, and the Chief Financial Officer, followed by an overview of NASA's organizational structure and the planning and budgeting process. The performance of NASA in four strategic enterprises is reviewed: (1) Space Science, (2) Mission to Planet Earth, (3) Human Exploration and Development of Space, and (4) Aeronautics and Space Transportation Technology. Those areas which support the strategic enterprises are also reviewed in a section called Crosscutting Processes. For each of the four enterprises, there is discussion about the long term goals, the short term objectives and the accomplishments during FY 1997. The Crosscutting Processes section reviews issues and accomplishments relating to human resources, procurement, information technology, physical resources, financial management, small and disadvantaged businesses, and policy and plans. Following the discussion about the individual areas is Management's Discussion and Analysis, about NASA's financial statements. This is followed by a report by an independent commercial auditor and the financial statements.

Source record↗

NASA NTRS1998

Preparing for Human Exploration

NASA's Human Exploration and Development of Space (HEDS) Enterprise is defining architectures and requirements for human exploration that radically reduce the costs of such missions through the use of advanced technologies, commercial partnerships and innovative systems strategies. In addition, the HEDS Enterprise is collaborating with the Space Science Enterprise to acquire needed early knowledge about Mars and to demonstrate critical technologies via robotic missions. This paper provides an overview of the technological challenges facing NASA as it prepares for human exploration. Emphasis is placed on identifying the key technologies including those which will provide the most return in terms of reducing total mission cost and/or reducing potential risk to the mission crew. Top-level requirements are provided for those critical enabling technology options currently under consideration.

Drake, Bret G.↗

NASA NTRS1999

Virtual Manufacturing Techniques Designed and Applied to Manufacturing Activities in the Manufacturing Integration and Technology Branch

One of the identified goals of EM3 is to implement virtual manufacturing by the time the year 2000 has ended. To realize this goal of a true virtual manufacturing enterprise the initial development of a machinability database and the infrastructure must be completed. This will consist of the containment of the existing EM-NET problems and developing machine, tooling, and common materials databases. To integrate the virtual manufacturing enterprise with normal day to day operations the development of a parallel virtual manufacturing machinability database, virtual manufacturing database, virtual manufacturing paradigm, implementation/integration procedure, and testable verification models must be constructed. Common and virtual machinability databases will include the four distinct areas of machine tools, available tooling, common machine tool loads, and a materials database. The machine tools database will include the machine envelope, special machine attachments, tooling capacity, location within NASA-JSC or with a contractor, and availability/scheduling. The tooling database will include available standard tooling, custom in-house tooling, tool properties, and availability. The common materials database will include materials thickness ranges, strengths, types, and their availability. The virtual manufacturing databases will consist of virtual machines and virtual tooling directly related to the common and machinability databases. The items to be completed are the design and construction of the machinability databases, virtual manufacturing paradigm for NASA-JSC, implementation timeline, VNC model of one bridge mill and troubleshoot existing software and hardware problems with EN4NET. The final step of this virtual manufacturing project will be to integrate other production sites into the databases bringing JSC's EM3 into a position of becoming a clearing house for NASA's digital manufacturing needs creating a true virtual manufacturing enterprise.

Shearrow, Charles A.↗

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 NTRS2000

NASA/University JOint VEnture (JOVE) Program. VIXEN(tm): Object-Oriented, Technology-Adaptive, Virtual Information Exchange Environment

Vixen is a collection of enabling technologies for uninhibited distributed object computing. In the Spring of 1995 when Vixen was proposed, it was an innovative idea very much ahead of its time. But today the technologies proposed in Vixen have become standard technologies for Enterprise Computing. Sun Microsystems J2EE/EJB specifications, among others, are independently proposed technologies of the Vixen type. I have brought Vixen completely under the J2EE standard in order to maximize interoperability and compatibility with other computing industry efforts. Vixen and the Enterprise JavaBean (EJB) Server technologies are now practically identical; OIL, another Vixen technology, and the Java Messaging System (JMS) are practically identical; and so on. There is no longer anything novel or patentable in the Vixen work performed under this grant. The above discussion, notwithstanding, my independent development of Vixen has significantly helped me, my university, my students and the local community. The undergraduate students who worked with me in developing Vixen have enhanced their expertise in what has become the cutting edge technology of their industry and are therefore well positioned for lucrative employment opportunities in the industry. My academic department has gained a new course: "Multi-media System Development", which provides a highly desirable expertise to our students for employment in any enterprise today. The many Outreach Programs that I conducted during this grant period have exposed local Middle School students to the contributions that NASA is making in our society as well as awakened desires in many such students for careers in Science and Technology. I have applied Vixen to the development of two software packages: (a) JAS: Joshua Application Server - which allows a user to configure an EJB Server to serve a J2EE compliant application over the world wide web; (b) PCM: Professor Course Manager: a J2EE compliant application for configuring a course for distance learning. These types of applications are, however, generally available in the industry today.

Anyiwo, Joshua C.↗

NASA NTRS2000

Wind Tunnel Management and Resource Optimization: A Systems Modeling Approach

Time, money, and, personnel are becoming increasingly scarce resources within government agencies due to a reduction in funding and the desire to demonstrate responsible economic efficiency. The ability of an organization to plan and schedule resources effectively can provide the necessary leverage to improve productivity, provide continuous support to all projects, and insure flexibility in a rapidly changing environment. Without adequate internal controls the organization is forced to rely on external support, waste precious resources, and risk an inefficient response to change. Management systems must be developed and applied that strive to maximize the utility of existing resources in order to achieve the goal of "faster, cheaper, better". An area of concern within NASA Langley Research Center was the scheduling, planning, and resource management of the Wind Tunnel Enterprise operations. Nine wind tunnels make up the Enterprise. Prior to this research, these wind tunnel groups did not employ a rigorous or standardized management planning system. In addition, each wind tunnel unit operated from a position of autonomy, with little coordination of clients, resources, or project control. For operating and planning purposes, each wind tunnel operating unit must balance inputs from a variety of sources. Although each unit is managed by individual Facility Operations groups, other stakeholders influence wind tunnel operations. These groups include, for example, the various researchers and clients who use the facility, the Facility System Engineering Division (FSED) tasked with wind tunnel repair and upgrade, the Langley Research Center (LaRC) Fabrication (FAB) group which fabricates repair parts and provides test model upkeep, the NASA and LARC Strategic Plans, and unscheduled use of the facilities by important clients. Expanding these influences horizontally through nine wind tunnel operations and vertically along the NASA management structure greatly increases the complexity of developing a model that can be used for successfully implementing a standardized management planning tool. The objective of this study was to implement an Integrated Wind Tunnel Planning System to improve the operations within the aeronautics testing and research group, in particular Wind Tunnel Enterprise. The study included following steps: Conducted literature search and expert discussions (NASA and Old Dominion University faculty), Performed environmental scan of NASA Langley wind tunnel operations as foundation for problem definition. Established operation requirements and evaluation methodologies. Examined windtunnel operations to map out the common characteristics, critical components, and system structure. Reviewed and evaluated various project scheduling and management systems for implementation, Evaluated and implemented "Theory of Constraints (TOC)" project scheduling methodology at NASA Langley wind tunnel operations together with NASA staff.

Jacobs, Derya, A.↗

NASA NTRS2000

Partnering to Change the Way NASA and the Nation Communicate Through Space

For at least 20 years, the Space Communications Program at NASA Glenn Research Center (GRC) has focused on enhancing the capability and competitiveness of the U.S. commercial communications satellite industry. GRC has partnered with the industry on the development of enabling technologies to help maintain U.S. preeminence in the worldwide communications satellite marketplace. The Advanced Communications Technology Satellite (ACTS) has been the most significant space communications technology endeavor ever performed at GRC, and the centerpiece of GRC's communication technology program for the last decade. Under new sponsorship from NASA's Human Exploration and Development of Space Enterprise, GRC has transitioned the focus and direction of its program, from commercial relevance to NASA mission relevance. Instead of one major experimental spacecraft and one headquarters sponsor, GRC is now exploring opportunities for all of NASA's Enterprises to benefit from advances in space communications technologies, and accomplish their missions through the use of existing and emerging commercially provided services. A growing vision within NASA is to leverage the best commercial standards, technologies, and services as a starting point to satisfy NASA's unique needs. GRC's heritage of industry partnerships is closely aligned with this vision. NASA intends to leverage the explosive growth of the telecommunications industry through its impressive technology advancements and potential new commercial satellite systems. GRC's partnerships with the industry, academia, and other government agencies will directly support all four NASA's future mission needs, while advancing the state of the art of commercial practice. GRC now conducts applied research and develops and demonstrates advanced communications and network technologies in support of all four NASA Enterprises (Human Exploration and Development of Space, Space Science, Earth Science, and Aero-Space Technologies).

Vrotsos, Pete A.↗

NASA NTRS2001

A New Direction for NASA Materials Science Research Using the International Space Station

NASA recently created a fifth Strategic Enterprise, the Office of Biological and Physical Research (OBPR), to bring together physics, chemistry, biology, and engineering to foster interdisciplinary research. The Materials Science Program is one of five Microgravity Research disciplines within this new enterprise's Division of Physical Sciences Research. The Materials Science Program will participate within this new enterprise structure in order to facilitate effective use of ISS facilities, target scientific and technology questions and transfer scientific and technology results for Earth benefits. The Materials Science research will use a low gravity environment for flight and ground-based research in crystallization, fundamental processing, properties characterization, and biomaterials in order to obtain fundamental understanding of various phenomena effects and relationships to the structures, processing, and properties of materials. Completion of the International Space Station's (ISS) first major assembly, during the past year, provides new opportunities for on-orbit research and scientific utilization. Accommodations will support a variety of Materials Science payload hardware both in the US and international partner modules with emphasis on early use of Express Rack and Glovebox facilities. This paper addresses the current scope of the flight investigator program. These investigators will use the various capabilities of the ISS to achieve their research objectives. The type of research and classification of materials being studied will be addressed. This includes the recent emphasis being placed on nanomaterials and biomaterials type research. Materials Science Program will pursue a new, interdisciplinary approach, which contributes, to Human Space Flight Exploration research. The Materials Science Research Facility (MSRF) and other related American and International experiment modules will serve as the foundation for this research. Discussion will be included to explain the changing concept for materials science research processing capabilities aboard the ISS along with the various ground facilities necessary to support the program. Finally, the paper will address the initial utilization schedule and strategy for the various materials science payloads including their corresponding hardware.

Schlagheck, Ronald↗

NASA NTRS2000

Challenges of Information Technology Security in the NASA Environment

A brief description of the NASA organization and how the CIO responsibilities are integrated into that organization followed by an introduction of the NASA ITS Program goals and objectives. An overview of the four major enterprises' cultures and how those cultures tie back to the Enterprises' missions. A description of the ITS challenges that exist stemming from the competing NASA Enterprises' requirements and how they have formed the basis of the NASA ITS Program. A talk will focus on policies and procedures and the technology being incorporated into the NASA infrastructure and how that technology ties back to the policies and procedures.

Santiago, S. S.↗

NASA NTRS2004

Overview of NASA's Earth Science Data Systems

For over the last 15 years, NASA's Earth Science Enterprise (ESE) has devoted a tremendous effort to design and build the Earth Observing System (EOS) Data and Information System (EOSDIS) to acquire, process, archive and distribute the data of the EOS series of satellites and other ESE missions and field programs. The development of EOSDIS began with an early prototype to support NASA data from heritage missions and progressed through a formal development process to today's system that supports the data from multiple missions including Landsat 7, Terra, Aqua, SORCE and ICESat. The system is deployed at multiple Distributed Active Archive Centers (DAACs) and its current holdings are approximately 4.5 petabytes. The current set of unique users requesting EOS data and information products exceeds 2 million. While EOSDIS has been the centerpiece of NASA's Earth Science Data Systems, other initiatives have augmented the services of EOSDIS and have impacted its evolution and the future directions of data systems within the ESE. ESDIS had an active prototyping effort and has continued to be involved in the activities of the Earth Science Technology Office (ESTO). In response to concerns from the science community that EOSDIS was too large and monolithic, the ESE initiated the Earth Science Information Partners (ESP) Federation Experiment that funded a series of projects to develop specialized products and services to support Earth science research and applications. Last year, the enterprise made 41 awards to successful proposals to the Research, Education and Applications Solutions Network (REASON) Cooperative Agreement Notice to continue and extend the ESP activity. The ESE has also sponsored a formulation activity called the Strategy for the Evolution of ESE Data Systems (SEEDS) to develop approaches and decision support processes for the management of the collection of data system and service providers of the enterprise. Throughout the development of its earth science data systems, NASA has had an active collaboration with a number of interagency and international partners. One of the mechanisms that has been extremely helpful in initiating and promoting this collaboration has been NASA's participation in the Committee on Earth Observation Satellites (CEOS) and its Working Group on Information Systems and Services (WGISS). The CEOS members, working together, have implemented an International Directory Network that enables users to locate collections of earth science data held by the international community and an International Catalog System to search and order specific data products. CEOS WGISS has also promoted the international interest in the Open GIS Consortium s specifications that further advance the access and use of geospatial data and the interoperation of GTS components. These are just a few highlights of the benefits that member agencies gain from CEOS participation.

McDonald, Kenneth↗

NASA NTRS2004

Earth Science Education Plan: Inspire the Next Generation of Earth Explorers

The Education Enterprise Strategy, the expanding knowledge of how people learn, and the community-wide interest in revolutionizing Earth and space science education have guided us in developing this plan for Earth science education. This document builds on the success of the first plan for Earth science education published in 1996; it aligns with the new framework set forth in the NASA Education Enterprise Strategy; it recognizes the new educational opportunities resulting from research programs and flight missions; and it builds on the accomplishments th'at the Earth Science Enterprise has made over the last decade in studying Earth as a system. This document embodies comprehensive, practicable plans for inspiring our children; providing educators with the tools they need to teach science, technology, engineering, and mathematics (STEM); and improving our citizens' scientific literacy. This plan describes an approach to systematically sharing knowledge; developing the most effective mechanisms to achieve tangible, lasting results; and working collaboratively to catalyze action at a scale great enough to ensure impact nationally and internationally. This document will evolve and be periodically reviewed in partnership with the Earth science education community.

Source record↗

NASA NTRS2009

Software Tools Streamline Project Management

Three innovative software inventions from Ames Research Center (NETMARK, Program Management Tool, and Query-Based Document Management) are finding their way into NASA missions as well as industry applications. The first, NETMARK, is a program that enables integrated searching of data stored in a variety of databases and documents, meaning that users no longer have to look in several places for related information. NETMARK allows users to search and query information across all of these sources in one step. This cross-cutting capability in information analysis has exponentially reduced the amount of time needed to mine data from days or weeks to mere seconds. NETMARK has been used widely throughout NASA, enabling this automatic integration of information across many documents and databases. NASA projects that use NETMARK include the internal reporting system and project performance dashboard, Erasmus, NASA s enterprise management tool, which enhances organizational collaboration and information sharing through document routing and review; the Integrated Financial Management Program; International Space Station Knowledge Management; Mishap and Anomaly Information Reporting System; and management of the Mars Exploration Rovers. Approximately $1 billion worth of NASA s projects are currently managed using Program Management Tool (PMT), which is based on NETMARK. PMT is a comprehensive, Web-enabled application tool used to assist program and project managers within NASA enterprises in monitoring, disseminating, and tracking the progress of program and project milestones and other relevant resources. The PMT consists of an integrated knowledge repository built upon advanced enterprise-wide database integration techniques and the latest Web-enabled technologies. The current system is in a pilot operational mode allowing users to automatically manage, track, define, update, and view customizable milestone objectives and goals. The third software invention, Query-Based Document Management (QBDM) is a tool that enables content or context searches, either simple or hierarchical, across a variety of databases. The system enables users to specify notification subscriptions where they associate "contexts of interest" and "events of interest" to one or more documents or collection(s) of documents. Based on these subscriptions, users receive notification when the events of interest occur within the contexts of interest for associated document or collection(s) of documents. Users can also associate at least one notification time as part of the notification subscription, with at least one option for the time period of notifications.

Source record↗

NASA NTRS2010

Space Toxicology Challenges and Ethical Considerations

Before delineating specific ways that nanotechnology enterprises might contribute to better management of toxicological risks during spaceflight, I will show how ethical considerations and several theories of justice can be applied to nanotechnology strategic plans. The principles that guide an ethical technical enterprise include autonomy, beneficence, non-maleficence, veracity and justice. Veracity (truth) is the underpinning principle; however, beyond this, proponents of nanotechnology must think carefully about balancing conflicting principles. For example, autonomy must yield to beneficence when fearful individuals simply lack knowledge to appreciate nanotechnology's beneficial advances. Justice is a complex topic upon which I will place six models: utilitarian, distributive, free-exchange/choice, individual dignity (social participation), equity vs. greed, and liberation of the poor. After briefly summarizing each model, I will present what I call an iterative-hybrid model of justice to show specifically how our thinking can be applied to nanotechnology enterprises. Within that broad landscape, I will discuss a single feature: how our early effort to understand health risks of carbon nanotubes fits into the iterative model. Finally, I will suggest ways that nanotechnology might advance our management of toxicological risks during spaceflight, but always with an eye toward how such advances might result in a more just world.

James, John T.↗

NASA NTRS2010

Marshall Application Realignment System (MARS) Architecture

The Marshall Application Realignment System (MARS) Architecture project was established to meet the certification requirements of the Department of Defense Architecture Framework (DoDAF) V2.0 Federal Enterprise Architecture Certification (FEAC) Institute program and to provide added value to the Marshall Space Flight Center (MSFC) Application Portfolio Management process. The MARS Architecture aims to: (1) address the NASA MSFC Chief Information Officer (CIO) strategic initiative to improve Application Portfolio Management (APM) by optimizing investments and improving portfolio performance, and (2) develop a decision-aiding capability by which applications registered within the MSFC application portfolio can be analyzed and considered for retirement or decommission. The MARS Architecture describes a to-be target capability that supports application portfolio analysis against scoring measures (based on value) and overall portfolio performance objectives (based on enterprise needs and policies). This scoring and decision-aiding capability supports the process by which MSFC application investments are realigned or retired from the application portfolio. The MARS Architecture is a multi-phase effort to: (1) conduct strategic architecture planning and knowledge development based on the DoDAF V2.0 six-step methodology, (2) describe one architecture through multiple viewpoints, (3) conduct portfolio analyses based on a defined operational concept, and (4) enable a new capability to support the MSFC enterprise IT management mission, vision, and goals. This report documents Phase 1 (Strategy and Design), which includes discovery, planning, and development of initial architecture viewpoints. Phase 2 will move forward the process of building the architecture, widening the scope to include application realignment (in addition to application retirement), and validating the underlying architecture logic before moving into Phase 3. The MARS Architecture key stakeholders are most interested in Phase 3 because this is where the data analysis, scoring, and recommendation capability is realized. Stakeholders want to see the benefits derived from reducing the steady-state application base and identify opportunities for portfolio performance improvement and application realignment.

Belshe, Andrea↗