Search NASA⌕ Search

SEARCH · Search NASA

Results for “Task scheduling”

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 667 records · Page 37

Space-based multifunctional end effector systems functional requirements and proposed designs

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested manipulator systems in time for space stations operations in the early 1990s.

Mishkin, A. H.↗

A software tool for dataflow graph scheduling

A graph-theoretic design process and software tool is presented for selecting a multiprocessing scheduling solution for a class of computational problems. The problems of interest are those that can be described using a dataflow graph and are intended to be executed repetitively on multiple processors. The dataflow paradigm is very useful in exposing the parallelism inherent in algorithms. It provides a graphical and mathematical model which describes a partial ordering of algorithm tasks based on data precedence.

Jones, Robert L., III↗

Affordable Development and Demonstration of a Small Nuclear Thermal Rocket (NTR) Engine and Stage: How Small Is Big Enough?

The Nuclear Thermal Rocket (NTR) derives its energy from fission of uranium-235 atoms contained within fuel elements that comprise the engine's reactor core. It generates high thrust and has a specific impulse potential of approximately 900 specific impulse - a 100 percent increase over today's best chemical rockets. The Nuclear Thermal Propulsion (NTP) project, funded by NASA's Advanced Exploration Systems (AES) program, includes five key task activities: (1) Recapture, demonstration, and validation of heritage graphite composite (GC) fuel (selected as the Lead Fuel option); (2) Engine Conceptual Design; (3) Operating Requirements Definition; (4) Identification of Affordable Options for Ground Testing; and (5) Formulation of an Affordable Development Strategy. During fiscal year (FY) 2014, a preliminary Design Development Test and Evaluation (DDT&E) plan and schedule for NTP development was outlined by the NASA Glenn Research Center (GRC), Department of Energy (DOE) and industry that involved significant system-level demonstration projects that included Ground Technology Demonstration (GTD) tests at the Nevada National Security Site (NNSS), followed by a Flight Technology Demonstration (FTD) mission. To reduce cost for the GTD tests and FTD mission, small NTR engines, in either the 7.5 or 16.5 kilopound-force thrust class, were considered. Both engine options used GC fuel and a common fuel element (FE) design. The small approximately 7.5 kilopound-force criticality-limited engine produces approximately157 thermal megawatts and its core is configured with parallel rows of hexagonal-shaped FEs and tie tubes (TTs) with a FE to TT ratio of approximately 1:1. The larger approximately 16.5 kilopound-force Small Nuclear Rocket Engine (SNRE), developed by Los Alamos National Laboratory (LANL) at the end of the Rover program, produces approximately 367 thermal megawatts and has a FE to TT ratio of approximately 2:1. Although both engines use a common 35-inch (approximately 89-centimeters) -long FE, the SNRE's larger diameter core contains approximately 300 more FEs needed to produce an additional 210 thermal megawatts of power. To reduce the cost of the FTD mission, a simple one-burn lunar flyby mission was considered to reduce the liquid hydrogen (LH2) propellant loading, the stage size and complexity. Use of existing and flight proven liquid rocket and stage hardware (e.g., from the RL10B-2 engine and Delta Cryogenic Second Stage) was also maximized to further aid affordability. This paper examines the pros and cons of using these two small engine options, including their potential to support future human exploration missions to the Moon, near Earth asteroids (NEA), and Mars, and recommends a preferred size. It also provides a preliminary assessment of the key activities, development options, and schedule required to affordably build, ground test and fly a small NTR engine and stage within a 10-year timeframe.

Spacecraft design↗

Assessment of Scheduling and Plan Execution of Apollo 14 Lunar Surface Operations

Although over forty years have passed since first landing on the Moon, there is not yet a comprehensive, quantitative assessment of Apollo extravehicular activities (EVAs). Quantitatively evaluating lunar EVAs will provide a better understanding of the challenges involved with surface operations. This first evaluation of a surface EVA centers on comparing the planned and the as-ran timeline, specifically collecting data on discrepancies between durations that were estimated versus executed. Differences were summarized by task categories in order to gain insight as to the type of surface operation activities that were most challenging. One Apollo 14 EVA was assessed utilizing the described methodology. Selected metrics and task categorizations were effective, and limitations to this process were identified.

Marquez, Jessica J.↗

Real-Time MENTAT programming language and architecture

Real-time MENTAT, a programming environment designed to simplify the task of programming real-time applications in distributed and parallel environments, is described. It is based on the same data-driven computation model and object-oriented programming paradigm as MENTAT. It provides an easy-to-use mechanism to exploit parallelism, language constructs for the expression and enforcement of timing constraints, and run-time support for scheduling and exciting real-time programs. The real-time MENTAT programming language is an extended C++. The extensions are added to facilitate automatic detection of data flow and generation of data flow graphs, to express the timing constraints of individual granules of computation, and to provide scheduling directives for the runtime system. A high-level view of the real-time MENTAT system architecture and programming language constructs is provided.

Grimshaw, Andrew S.↗

A rule-based shell to hierarchically organize HST observations

An observing program on the Hubble Space Telescope (HST) is described in terms of exposures that are obtained by one or more of the instruments onboard the HST. These exposures are organized into a hierarchy of structures for purposes of efficient scheduling of observations. The process by which exposures get organized into the higher-level structures is called merging. This process relies on rules to determine which observations can be 'merged' into the same higher level structure, and which cannot. The TRANSformation expert system converts proposals for astronomical observations with HST into detailed observing plans. The conversion process includes the task of merging. Within TRANS, we have implemented a declarative shell to facilitate merging. This shell offers the following features: (1) an easy way of specifying rules on when to merge and when not to merge, (2) a straightforward priority mechanism for resolving conflicts among rules, (3) an explanation facility for recording the merging history, (4) a report generating mechanism to help users understand the reasons for merging, and (5) a self-documenting mechanism that documents all the merging rules that have been defined in the shell, ordered by priority. The merging shell is implemented using an object-oriented paradigm in CLOS. It has been a part of operational TRANS (after extensive testing) since July 1993. It has fulfilled all performance expectations, and has considerably simplified the process of implementing new or changed requirements for merging. The users are pleased with its report-generating and self-documenting features.

Bose, Ashim↗

The Joint Confidence Level Paradox: A History of Denial

This paper is intended to provide a reliable methodology for those tasked with generating price tags on construction (C0F) and research and development (R&D) activities in the NASA performance world. This document consists of a collection of cost-related engineering detail and project fulfillment information from early agency days to the present. Accurate historical detail is the first place to start when determining improved methodologies for future cost and schedule estimating. This paper contains a beneficial proposed cost estimating method for arriving at more reliable numbers for future submits. When comparing current cost and schedule methods with earlier cost and schedule approaches, it became apparent that NASA's organizational performance paradigm has morphed. Mission fulfillment speed has slowed and cost calculating factors have increased in 21st Century space exploration.

Butts, Glenn↗

Effectiveness of Redundant Communications Systems in Maintaining Operational Control of Small Unmanned Aircraft

NASA has been researching prototype technologies for an Unmanned Aircraft System (UAS) Traffic Management (UTM) system to facilitate enabling of safe and efficient civilian low-altitude airspace and UAS operations, in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for beyond visual line-of-sight (BVLOS) operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 will build on the earlier TCLs and focus on technologies and requirements for operations in higher-density urban areas for tasks such as news gathering, package delivery and for managing large-scale contingencies. This paper describes a communications test conducted in TCL3 and discusses insights gained from the test. In the test, operators were directed to equip UAS with redundant Command and Control (C2) communications systems, send a maneuver command to Unmanned Aircraft (UA) via the primary system, then verify execution of the sent command. This exercise was repeated with each redundant system. The test was designed to assess effectiveness of redundant C2 systems in maintaining operational control of UA. Several UAS were configured with varying arrangements to achieve redundancy, including two identical radio modems using the same frequency band, WiFi and Long-Term Evolution (LTE) cellular modems, etc. From the test, digital data such as time maneuver command sent, time maneuver verified, etc., were collected. Descriptions of methods to detect loss of C2 communications and contingency steps for such event were collected and assessed. The final paper will include a detailed analysis of the collected data leading to the following insights. First, effectiveness of redundant C2 systems depends on several factors, such as operational environment and communications service availability. For example, use of two identical point-to-point radio to connect operator and UA on the same frequency band can be effective in mitigating radio malfunction when operating in an environment where possibility of Radio Frequency (RF) interference is low, such as over open plains. However, the same arrangement may not be effective where high level of RF transmissions in broad spectrum ranges can be expected, such as over or near urban areas. For redundant systems that consist of external communications services, such as cellular and satellite communications network, redundancy is maintained only in the areas where more than one services are available. Therefore, UAS operators should have the means to plan for and monitor the performance of external communications services they are relying on to control UA. Second, communications performance needs, such as the minimum data transfer rate and the maximum tolerable latency, should be assessed to reflect the potential hazard that can come from loss of UA control. For example, UA operations over desolate area pose less hazard to people than operations over densely populated area and performance need for the former would be less than the latter.

Jung, Jaewoo↗

Surface Systems Capability Gaps for Enabling NASA’s Sustainable Lunar Operations

This paper discusses the NASA Ground, Test, and Surface Systems Taxonomy (TX-13) related capability gaps, including details of architecture, technology, engineering, and policy gaps for enabling sustainable lunar surface operations and subsequent Mars missions. Architecture gaps include standardized architectures and interfaces, multi-element systems engineering and integration, design for supportability, and nuclear payload processing and launch approach. Technology gaps, primarily focused on uncrewed surface operations, include automated/autonomous cryogenic loading, transfer, servicing, and storage of commodities; health determination and fault management; automated/autonomous planning and scheduling; automated/autonomous inspection, maintenance and repair; logistics management and reliability; launch and landing site preparation; commodity management; and advanced umbilicals and dust tolerant interfaces. Engineering gaps include high-purity propellant production for ground and surface applications and large-scale xenon servicing capabilities. The policy gap includes nuclear propulsion acceptance testing and qualification approach. Strategically identifying human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle is essential for achieving the mission objectives for a sustainable human lunar presence, improving performance and mission effectiveness, reducing operations costs and reliance on humans to perform tasks, and accommodating ground communication delays.

Surface Systems↗

Creative Analytics of Mission Ops Event Messages

Historically, tremendous effort has been put into processing and displaying mission health and safety telemetry data; and relatively little attention has been paid to extracting information from missions time-tagged event log messages. Todays missions may log tens of thousands of messages per day and the numbers are expected to dramatically increase as satellite fleets and constellations are launched, as security monitoring continues to evolve, and as the overall complexity of ground system operations increases. The logs may contain information about orbital events, scheduled and actual observations, device status and anomalies, when operators were logged on, when commands were resent, when there were data drop outs or system failures, and much much more. When dealing with distributed space missions or operational fleets, it becomes even more important to systematically analyze this data. Several advanced information systems technologies make it appropriate to now develop analytic capabilities which can increase mission situational awareness, reduce mission risk, enable better event-driven automation and cross-mission collaborations, and lead to improved operations strategies: Industry Standard for Log Messages. The Object Management Group (OMG) Space Domain Task Force (SDTF) standards organization is in the process of creating a formal standard for industry for event log messages. The format is based on work at NASA GSFC. Open System Architectures. The DoD, NASA, and others are moving towards common open system architectures for mission ground data systems based on work at NASA GSFC with the full support of the commercial product industry and major integration contractors. Text Analytics. A specific area of data analytics which applies statistical, linguistic, and structural techniques to extract and classify information from textual sources. This presentation describes work now underway at NASA to increase situational awareness through the collection of non-telemetry mission operations information into a common log format and then providing display and analytics tools to provide in-depth assessment of the log contents. The work includes: Common interface formats for acquiring time-tagged text messages Conversion of common files for schedules, orbital events, and stored commands to the common log format Innovative displays to depict thousands of messages on a single display Structured English text queries against the log message data store, extensible to a more mature natural language query capability Goal of speech-to-text and text-to-speech additions to create a personal mission operations assistant to aid on-console operations. A wide variety of planned uses identified by the mission operations teams will be discussed.

events↗

Space Station power system

A Space Station Task Force was established by the NASA Administrator in May 1982 to provide focus and direction for Space Station planning activities. The Task Force also provides Congress and the Administration with sufficient information to allow them to make an informed decision on whether the United States should proceed with a Space Station as the next major national initiative in space. This paper will present the status of planning activities to date, with major emphasis on the power system. Technology options, power requirements, and schedule will be discussed.

Forestieri, A. F.↗

Space transportation nodes assumptions and requirements: Lunar base systems study task 2.1

The Space Transportation Nodes Assumptions and Requirements task was performed as part of the Advanced Space Transportation Support Contract, a NASA Johnson Space Center (JSC) study intended to provide planning for a Lunar Base near the year 2000. The original task statement has been revised to satisfy the following queries: (1) What vehicles are to be processed at the transportation node; (2) What is the flow of activities involved in a vehicle passing through the node; and (3) What node support resources are necessary to support a lunar scenario traffic model composed of a mix of vehicles in an active flight schedule. The Lunar Base Systems Study is concentrating on the initial years of the Phase 2 Lunar Base Scenario. The study will develop the first five years of that phase in order to define the transportation and surface systems (including mass, volumes, power requirements, and designs).

Kahn, Taher Ali↗

Human factors issues in performing life science experiments in a 0-G environment

An overview of the environmental conditions within the Spacelab and the planned Space Station Freedom is presented. How this environment causes specific Human Factors problems and the nature of design solutions are described. The impact of these problems and solutions on the performance of life science activities onboard Spacelab (SL) and Space Station Freedom (SSF) is discussed. The first area highlighted is contamination. The permanence of SSF in contrast to the two-week mission of SL has significant impacts on crew and specimen protection requirements and, thus, resource utilization. These requirements, in turn impose restrictions on working volumes, scheduling, training, and scope of experimental procedures. A second area is microgravity. This means that all specimens, materials, and apparatus must be restrained and carefully controlled. Because so much of the scientific activity must occur within restricted enclosures (gloveboxes), the provisions for restraint and control are made more complex. The third topic is crewmember biomechanics and the problems of movement and task performance in microgravity. In addition to the need to stabilize the body for the performance of tasks, performance of very sensitive tasks such as dissection is difficult. The issue of space sickness and adaption is considered in this context.

Gonzalez, Wayne↗

An intelligent planning and scheduling system for the HST servicing missions

A new, intelligent planning and scheduling system has been delivered to NASA-Goddard Space Flight Center (GSFC) to provide support for the up-coming Hubble Space Telescope (HST) Servicing Missions. This new system is the Servicing Mission Planning and Replanning Tool (SM/PART). SM/PART is written in C and runs on a UNlX-based workstation (IBM RS/6000) under Motif. SM/PART effectively automates the complex task of building or rebuilding integrated timelines and command plans which are required by HST Servicing Mission personnel at their consoles during the missions. SM/PART is able to quickly build or rebuild timelines based on information stored in a Knowledge Base (KB) by using an Artificial Intelligence (AI) tool called the Planning And Resource Reasoning (PARR) shell. After a timeline has been built in the batch mode, it can be displayed and edited in an interactive mode with help from the PARR shell. Finally a detailed command plan is generated. The capability to quickly build or rebuild timelines and command plans provides an additional safety factor for the HST, Shuttle and Crew.

Johnson, Jay↗

Development of the command data system and ground software for the SEDSAT-1 microsatellite

SEDSAT-1 is designed to be a low cost scientific satellite which is to be used to perform a minimum of five tasks which include: (1) the acquisition of a number of important parameters associated with the tethering processes from the payloads perspective (such as accelerations incurred and imaging data of the tether during deployment), (2) to act as a remote sensing platform for making measurements of the Earth's Atmosphere (allowing research to be performed in such areas as vertical lightning observation, visible light spectrography, and cloud cover studies, (3) to act as a general purpose amateur radio communication satellite relaying information back to earth, (4) to demonstrate the feasibility of the deployment in low earth orbit of advanced technology such as the Gallium Arsenide Solar Cells, Nickel Metal Hydride batteries, and multi-chip module technology and, (5) to support student's active participation in applying the disciplines of engineering and science to space-based hardware platforms. The project includes the Three-axis Accelerometer System, TAS, Experiment which is designed to report the accelerations that the satellite undergoes during the tethering operations and during the second phase of the mission when the free floating satellite comes in contact with orbit debris. The SEASIS (SEDS Earth, Atmosphere, and Space Imaging System) is another SEDSAT experiment designed to provide images of the tether during its deployment and the earth during the second phase of the mission. To control these experiments and virtually all other satellite operations the Command Data System, CDS is employed. This system utilizes a moderate complexity micro-controller controlled by tasks operating under a real-time operating system to dynamically monitor and control the satellite. The scope of this researchers efforts has been in the general area of coordinating and assisting the student researchers with the development of the CDS and ground station interfaces. This included the low level CDS hardware design and the formulization of a general software plan and schedule for both the CDS and ground station portions of the project.

Wells, B. Earl↗

MaROS: Information Management Service

This software is provided by the Mars Relay Operations Service (MaROS) task to a variety of Mars projects for the purpose of coordinating communications sessions between landed spacecraft assets and orbiting spacecraft assets at Mars. The Information Management Service centralizes a set of functions previously distributed across multiple spacecraft operations teams, and as such, greatly improves visibility into the end-to-end strategic coordination process. Most of the process revolves around the scheduling of communications sessions between the spacecraft during periods of time when a landed asset on Mars is geometrically visible by an orbiting spacecraft. These relay sessions are used to transfer data both to and from the landed asset via the orbiting asset on behalf of Earth-based spacecraft operators. This software component is an application process running as a Java virtual machine. The component provides all service interfaces via a Representational State Transfer (REST) protocol over https to external clients. There are two general interaction modes with the service: upload and download of data. For data upload, the service must execute logic specific to the upload data type and trigger any applicable calculations including pass delivery latencies and overflight conflicts. For data download, the software must retrieve and correlate requested information and deliver to the requesting client. The provision of this service enables several key advancements over legacy processes and systems. For one, this service represents the first time that end-to-end relay information is correlated into a single shared repository. The software also provides the first multimission latency calculator; previous latency calculations had been performed on a mission-by-mission basis.

Allard, Daniel A.↗

Thermal Protection Systems Technology Transfer from Apollo and Space Shuttle to the Orion Program

This paper describes how the Orion program is utilizing the Thermal Protection System (TPS) experience from the Apollo and Space Shuttle programs to reduce program risk and improve affordability to meet NASA's future manned exploration missions. The Orion program successfully completed the Exploration Flight Test (EFT-1) mission in 2014 and is currently assembling, integrating, and testing the next spacecraft for the Exploration Mission (EM-1) to meet the flight test objectives of an unmanned orbital mission to the moon and return to earth in 2019. The Orion spacecraft production operations are located in the Neil Armstrong Operations and Checkout (O&C) facility at the Kennedy Space Center (KSC) providing an affordable and seamless delivery approach of vehicles directly to the launch site eliminating spacecraft transportation and additional checkout testing. Innovative vehicle design, manufacturing and test operations approaches are maturing and evolving with each Orion vehicle build to support the challenging NASA exploration mission requirements beyond Low Earth Orbit (LEO) while reducing program cost and schedule impacts. An example of Orion's evolution is the incorporation of an improved heat shield design, assembly and testing approach to meet the higher re-entry velocities for a lunar return for the EM-1 mission. The EFT- 1 heat shield was based on the Apollo heat shield manufacturing processes and was assembled at a supplier location and then transported to KSC for final integration. The EM-1 heat shield is now manufactured, assembled, tested, and installed into the spacecraft at the O&C facility reducing program cost and production schedules. The transition of the Space Shuttle TPS capabilities has enabled Orion to provide a human rated capsule design using proven materials and processes established over years of orbiter re-entry missions. The Orion Crew Module (CM) TPS configuration is derived from the Apollo CM approach utilizing improved materials and processes developed from the Space Shuttle program. The Orion EFT-1 heat shield utilized the Avcoat ablative material from Apollo which was injected into a honeycomb substrate and has been updated for EM-1 incorporating a block configuration bonded to a composite shell structure. This approach utilizes the proven Avcoat material for the heat shield ablator and is utilizing derived bonding and inspection methods and techniques from the Space Shuttle tile experience. The Orion back shell TPS configuration is based on Space Shuttle tile designs using proven tile materials and coatings. The Orion forward bay cover utilizes the high temperature tiles similar to the back shell tiles and low temperature blankets derived from the Space Shuttle program reducing weight impacts. Space Shuttle Multi-Layer Insulation (MLI) is installed in the Orion capsule to control the interior temperature environment providing a light weight design. These TPS design approaches have performed successfully on the Orion first flight test on EFT-1 and are incorporated in the configuration for the next flight test for EM-1. Completion of these two flight tests will certify the TPS for the Orion program for human rated exploration missions and has reduced the development cost to the Orion program. In addition to transitioning the Space Shuttle TPS design configurations to Orion, the supporting manufacturing infrastructure, manufacturing processes, and inspection methods are also incorporated into the Orion assembly operations at KSC. This has avoided significant startup schedule and costs impacts of new capabilities and development of support operations necessary to fabricate, install, inspect, and validate the TPS installations for the Orion spacecraft. The Thermal Protection System Facility (TPSF) which supported the Space Shuttle program provides the heat shield Avcoat blocks and the back shell AETB-8 tiles for Orion program. Extending the existing Space Shuttle TPS operations at KSC provides onsite support to the Orion spacecraft assembly operations. A significant benefit to the Orion program is the transition of the Space Shuttle technician work force at KSC. This highly skilled workforce was able to transition to the Orion program and immediately support the TPS installation operations. They brought with them the human rated manufacturing and assembly operations culture that was critical to the Space Shuttle success avoiding the retraining cost and schedule impacts of a new workforce to Orion. The technician skills certification program from the Space Shuttle was found to be compatible with the Lockheed Martin technician certification programs enabling a seamless training process utilizing process similarity avoiding the cost of retraining the work force to Orion standards. The existing workforce is certificated for multiple processes enabling reassignment of technicians to other tasks in the Orion AI&P operations reducing the overall touch labor manpower requirements. Additional benefits of using the Space Shuttle workforce is the incorporation of the lessons learned from Space Shuttle processes to improve the Orion TPS processes. This has resulted in a continuous evolution of TPS processes to improve the producibility and reduce the program cost for the TPS for the Orion program. Transitioning the Apollo and Space Shuttle TPS designs, processes, and technician workforce has been instrumental in enabling Orion to successfully meet the program challenges for NASA's exploration missions of the future.

Stewart, Michael↗

An “EPIIC” Vision to Evolve Project Integration, Innovation, and Collaboration with Broad Impact for How NASA Executes Complex Projects

Evolving Project Integration, Innovation, and Collaboration (EPIIC) is a vision defined to transform the way projects manage information to support real-time decisions, capture best practices and lessons learned, perform assessments, and manage risk across a portfolio of projects. The foundational project management needs for data and information will be revolutionized through innovations on how we manage and access that data, implement configuration control, and certify compliance. The embedded intelligence of new interactive data interfaces integrate technical and programmatic data such that near real time analytics can be accomplished to more efficiently and accurately complete systems engineering and project management tasks. The system-wide data analytics that are integrated into customized data interfaces allows the growing team of engineers and managers required to develop and implement major NASA missions the ability to access authoritative source(s) of system information while greatly reducing the labor required to complete system assessments. This would allow, for example, much of what is accomplished in a scheduled design review to take place as needed, between any team members, at any time. An intelligent data interface that rigorously integrates systems engineering and project management information in near real time can provide substantially greater insight for systems engineers, project managers, and the large diverse teams required to complete a complex project. System engineers, programmatic personnel (those who focus on cost, schedule, and risk), the technical engineering disciplines, and project management can realize immediate benefit from the shared vision described herein. Implementation of the vision also enables significant improvements in the performance of the engineered system being developed.

Moreland, Robert J.↗