SEARCH · Engineering Papers

Results for “Organizational”

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 199 records · Page 11

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Modeling Personnel Turnover in the Parametric Organization

A primary issue in organizing a new parametric cost analysis function is to determine the skill mix and number of personnel required. The skill mix can be obtained by a functional decomposition of the tasks required within the organization and a matrixed correlation with educational or experience backgrounds. The number of personnel is a function of the skills required to cover all tasks, personnel skill background and cross training, the intensity of the workload for each task, migration through various tasks by personnel along a career path, personnel hiring limitations imposed by management and the applicant marketplace, personnel training limitations imposed by management and personnel capability, and the rate at which personnel leave the organization for whatever reason. Faced with the task of relating all of these organizational facets in order to grow a parametric cost analysis (PCA) organization from scratch, it was decided that a dynamic model was required in order to account for the obvious dynamics of the forming organization. The challenge was to create such a simple model which would be credible during all phases of organizational development. The model development process was broken down into the activities of determining the tasks required for PCA, determining the skills required for each PCA task, determining the skills available in the applicant marketplace, determining the structure of the dynamic model, implementing the dynamic model, and testing the dynamic model.

Dean, Edwin B.↗

NASA NTRS2004

Low Gravity Materials Science Research for Space Exploration

On January 14, 2004, the President of the United States announced a new vision for the United States civil space program. The Administrator of the National Aeronautics and Space Administration (NASA) has the responsibility to implement this new vision. The President also created a Presidential Commission 'to obtain recommendations concerning implementation of the new vision for space exploration.' The President's Commission recognized that achieving the exploration objectives would require significant technical innovation, research, and development in focal areas defined as 'enabling technologies.' Among the 17 enabling technologies identified for initial focus were advanced structures; advanced power and propulsion; closed-loop life support and habitability; extravehicular activity system; autonomous systems and robotics; scientific data collection and analysis; biomedical risk mitigation; and planetary in situ resource utilization. The Commission also recommended realignment of NASA Headquarters organizations to support the vision for space exploration. NASA has aggressively responded in its planning to support the vision for space exploration and with the current considerations of the findings and recommendations from the Presidential Commission. This presentation will examine the transformation and realignment activities to support the vision for space exploration that are underway in the microgravity materials science program. The heritage of the microgravity materials science program, in the context of residence within the organizational structure of the Office of Biological and Physical Research, and thematic and sub-discipline based research content areas, will be briefly examined as the starting point for the ongoing transformation. Overviews of future research directions will be presented and the status of organizational restructuring at NASA Headquarters, with respect to influences on the microgravity materials science program, will be discussed. Additional information is included in the original extended abstract.

Clinton, R. G., Jr.↗

NASA NTRS2004

Facilitating the Specification Capture and Transformation Process in the Development of Multi-Agent Systems

To support the development of flexible and reusable MAS, we have built a framework designated MAS-CF. MAS-CF is a component framework that implements a layered architecture based on contextual composition. Interaction rules, controlled by architecture mechanisms, ensure very low coupling, making possible the sharing of distributed services in a transparent, dynamic and independent way. These properties propitiate large-scale reuse, since organizational abstractions can be reused and propagated to all instances created from a framework. The objective is to reduce complexity and development time of multi-agent systems through the reuse of generic organizational abstractions.

Filho, Aluzio Haendehen↗

NASA NTRS2006

An Executable Choreography Framework for Dynamic Service-Oriented Architectures

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

Akkawi, Faisal↗

NASA NTRS1994

Experience with a Technology Transfer Lifecycle and Implementation of Formal Inspections

In an organization with diverse project support and focus, a technology transfer program will be most successful with support from an advocate who can work to implement new technologies on multiple projects across organizational boundaries. In addition, a strong, ongoing technology transfer program needs to be in place to support training, implementation, metrics analysis, and project and organizational feedback of the new technology.

software technology transfer adoption support orga↗

NASA NTRS2006

Advancing the practice of systems engineering at JPL

In FY 2004, JPL launched an initiative to improve the way it practices systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to "significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks." The scope of the SEA Project includes the systems engineering work performed in all three dimensions of a program, project, or task: 1. the full life-cycle, i.e., concept through end of operations 2. the full depth, i.e., Program, Project, System, Subsystem, Element (SE Levels 1 to 5) 3. the full technical scope, e.g., the flight, ground and launch systems, avionics, power, propulsion, telecommunications, thermal, etc. The initial focus of their efforts defined the following basic systems engineering functions at JPL: systems architecture, requirements management, interface definition, technical resource management, system design and analysis, system verification and validation, risk management, technical peer reviews, design process management and systems engineering task management, They also developed a list of highly valued personal behaviors of systems engineers, and are working to inculcate those behaviors into members of their systems engineering community. The SEA Project is developing products, services, and training to support managers and practitioners throughout the entire system lifecycle. As these are developed, each one needs to be systematically deployed. Hence, the SEA Project developed a deployment process that includes four aspects: infrastructure and operations, communication and outreach, education and training, and consulting support. In addition, the SEA Project has taken a proactive approach to organizational change management and customer relationship management - both concepts and approaches not usually invoked in an engineering environment. This paper'3 describes JPL's approach to advancing the practice of systems engineering at the Lab. It describes the general approach used and how they addressed the three key aspects of change: people, process and technology. It highlights a list of highly valued personal behaviors of systems engineers, discusses the various products, services and training that were developed, describes the deployment approach used, and concludes with several lessons learned.

process improvement↗

NASA NTRS2007

2004 Space Report: Environment and Strategy for Space Research at NATO's Research and Technology Organisation (RTO)

This report describes the motivation for and a strategy to enhance the NATO Research and Technology Organisation's (RTO) current space research effort to reflect NATO's growing military dependence on space systems. Such systems and services provided by these systems are critical elements of military operations. NATO uses space systems for operational planning and support, communication, radio navigation, multi-sensor and multi-domain demonstrations. Such systems are also used to promote regional stability. A quantitative analysis of work related to space in the NATO RTO showed that during the period of 1998 - 2004, 5% of the research pursued in the NATO RTO has been clearly focused on space applications. Challenging environmental and organizational barriers for increasing RTO space research were identified. In part, these include lack of sufficient space expertise representation on panels, the military sensitivity of space, current panel work loads and the need for specific technical recommendations from peers. A strategy for enhancing space research in the RTO is to create a limited-life Space Advisory Group (SAG) composed of Space Expert Consultants who are panel members with appropriate expertise and additional expertise from the nations. The SAG will recommend and find support in the nations for specific technical activities related to space in the areas of Space Science, Remote Sensing Data Analysis, Spacecraft Systems, Surveillance and Early Warning, Training and Simulation and Policy. An RTO Space Advisory Group will provide an organizational mechanism to gain recognition of RTO as a forum for trans-Atlantic defence space research and to enhance space research activities.

Woods-Vedeler, Jessica A.↗

NASA NTRS2009

Columbia Crew Survival Investigation Report

NASA commissioned the Columbia Accident Investigation Board (CAIB) to conduct a thorough review of both the technical and the organizational causes of the loss of the Space Shuttle Columbia and her crew on February 1, 2003. The accident investigation that followed determined that a large piece of insulating foam from Columbia s external tank (ET) had come off during ascent and struck the leading edge of the left wing, causing critical damage. The damage was undetected during the mission. The CAIB's findings and recommendations were published in 2003 and are available on the web at http://caib.nasa.gov/. NASA responded to the CAIB findings and recommendations with the Space Shuttle Return to Flight Implementation Plan. Significant enhancements were made to NASA's organizational structure, technical rigor, and understanding of the flight environment. The ET was redesigned to reduce foam shedding and eliminate critical debris. In 2005, NASA succeeded in returning the space shuttle to flight. In 2010, the space shuttle will complete its mission of assembling the International Space Station and will be retired to make way for the next generation of human space flight vehicles: the Constellation Program. The Space Shuttle Program recognized the importance of capturing the lessons learned from the loss of Columbia and her crew to benefit future human exploration, particularly future vehicle design. The program commissioned the Spacecraft Crew Survival Integrated Investigation Team (SCSIIT). The SCSIIT was asked to perform a comprehensive analysis of the accident, focusing on factors and events affecting crew survival, and to develop recommendations for improving crew survival for all future human space flight vehicles. To do this, the SCSIIT investigated all elements of crew survival, including the design features, equipment, training, and procedures intended to protect the crew. This report documents the SCSIIT findings, conclusions, and recommendations.

Source record↗

NASA NTRS2008

Managing Large Scale Project Analysis Teams through a Web Accessible Database

Large scale space programs analyze thousands of requirements while mitigating safety, performance, schedule, and cost risks. These efforts involve a variety of roles with interdependent use cases and goals. For example, study managers and facilitators identify ground-rules and assumptions for a collection of studies required for a program or project milestone. Task leaders derive product requirements from the ground rules and assumptions and describe activities to produce needed analytical products. Disciplined specialists produce the specified products and load results into a file management system. Organizational and project managers provide the personnel and funds to conduct the tasks. Each role has responsibilities to establish information linkages and provide status reports to management. Projects conduct design and analysis cycles to refine designs to meet the requirements and implement risk mitigation plans. At the program level, integrated design and analysis cycles studies are conducted to eliminate every 'to-be-determined' and develop plans to mitigate every risk. At the agency level, strategic studies analyze different approaches to exploration architectures and campaigns. This paper describes a web-accessible database developed by NASA to coordinate and manage tasks at three organizational levels. Other topics in this paper cover integration technologies and techniques for process modeling and enterprise architectures.

O'Neil, Daniel A.↗

NASA NTRS2009

Development and Deployment of NASA's Budget Execution Dashboard

This paper discusses the successful implementation of a highly visible company-wide management system and its potential to change managerial and accounting policies, processes and practices in support of organizational goals. Applying the conceptual framework of innovation in organizations, this paper describes the development and deployment process of the NASA Budget Execution Dashboard and the first two fiscal years of its use. It discusses the positive organizational changes triggered by the dashboard, like higher visibility of financial goals and variances between plans and actuals, increased involvement of all management levels in tracking and correcting of plan deviations, establishing comparable data standards across a strongly diversified organization, and enhanced communication between line organizations (NASA Centers) and product organizations (Mission Directorates). The paper also discusses the critical success factors experienced in this project: Strong leadership and division of management roles, rapid and responsive technology development, and frequent communication among stakeholders.

Putz, Peter↗

NASA NTRS2010

Handling Emergency Management in [an] Object Oriented Modeling Environment

It has been understood that protection of a nation from extreme disasters is a challenging task. Impacts of extreme disasters on a nation's critical infrastructures, economy and society could be devastating. A protection plan itself would not be sufficient when a disaster strikes. Hence, there is a need for a holistic approach to establish more resilient infrastructures to withstand extreme disasters. A resilient infrastructure can be defined as a system or facility that is able to withstand damage, but if affected, can be readily and cost-effectively restored. The key issue to establish resilient infrastructures is to incorporate existing protection plans with comprehensive preparedness actions to respond, recover and restore as quickly as possible, and to minimize extreme disaster impacts. Although national organizations will respond to a disaster, extreme disasters need to be handled mostly by local emergency management departments. Since emergency management departments have to deal with complex systems, they have to have a manageable plan and efficient organizational structures to coordinate all these systems. A strong organizational structure is the key in responding fast before and during disasters, and recovering quickly after disasters. In this study, the entire emergency management is viewed as an enterprise and modelled through enterprise management approach. Managing an enterprise or a large complex system is a very challenging task. It is critical for an enterprise to respond to challenges in a timely manner with quick decision making. This study addresses the problem of handling emergency management at regional level in an object oriented modelling environment developed by use of TopEase software. Emergency Operation Plan of the City of Hampton, Virginia, has been incorporated into TopEase for analysis. The methodology used in this study has been supported by a case study on critical infrastructure resiliency in Hampton Roads.

Tokgoz, Berna Eren↗

NASA NTRS2010

Integrated Budget Office Toolbox

The Integrated Budget Office Toolbox (IBOT) combines budgeting, resource allocation, organizational funding, and reporting features in an automated, integrated tool that provides data from a single source for Johnson Space Center (JSC) personnel. Using a common interface, concurrent users can utilize the data without compromising its integrity. IBOT tracks planning changes and updates throughout the year using both phasing and POP-related (program-operating-plan-related) budget information for the current year, and up to six years out. Separating lump-sum funds received from HQ (Headquarters) into separate labor, travel, procurement, Center G&A (general & administrative), and servicepool categories, IBOT creates a script that significantly reduces manual input time. IBOT also manages the movement of travel and procurement funds down to the organizational level and, using its integrated funds management feature, helps better track funding at lower levels. Third-party software is used to create integrated reports in IBOT that can be generated for plans, actuals, funds received, and other combinations of data that are currently maintained in the centralized format. Based on Microsoft SQL, IBOT incorporates generic budget processes, is transportable, and is economical to deploy and support.

Rushing, Douglas A.↗

NASA NTRS2010

Forum on Workforce Development

APPEL Mission: To support NASA's mission by promoting individual, team, and organizational excellence in program/project management and engineering through the application of learning strategies, methods, models, and tools. Goals: a) Provide a common frame of reference for NASA s technical workforce. b) Provide and enhance critical job skills. c) Support engineering, program and project teams. d) Promote organizational learning across the agency. e) Supplement formal educational programs.

Hoffman, Edward↗

NASA NTRS2010

Collective Intelligence and Three Aspects of Planning in Organizations: A NASA Example

For many complex sociotechnical systems, planning seems to require explicit coordination; certainly, in executing a plan the activities of different actors must be tightly coupled. However, distributing the needed planning information can be very burdensome and error prone, because different groups need different collections of information, updated or kept current on different time cycles. Further, the information needed to form successful plans is often highly distributed, and while feedback about the success of prior plans may exist, it may not be available to those in a position of using this to improve plans or to detect and resolve other problems in the system (Weick, 1995). Tools to support various aspects of planning have been developed, and can provide a huge benefit to the individuals working on that aspect. To be tractable, most solutions address a quite bounded slice of work, isolating it from the larger context. Prospective planning takes place over multiple, nested cycles of decision making. This builds a plan that specifies activities of different granularity. "Subplans" may specify multiple parallel activities by different groups and individuals, as well as sequential, nested actions by a single actor. Planning produces valuable, sharable, external, representations: in addition to prospective use, plans support retrospective assessment and also action in the present. Viewing planning in a larger context - both temporal and organizational -- enables noticing what one does not know and generating more systemic and effective solutions. Viewing a problem as one of collective intelligence invites thinking about the larger organizational context. Many approaches to supporting collective intelligence do not support execution of highly contingent actions, distributed across many players, and hence provide incomplete support for planning. However, CI technology maybe helpful in managing the processes of gathering information for decision making in planning and of distributing plan information to various actors, needed on various time cycles.

Billman, Dorrit↗

NASA NTRS2003

Expert Seeker

Expert Seeker is a computer program of the knowledge-management-system (KMS) type that falls within the category of expertise-locator systems. The main goal of the KMS system implemented by Expert Seeker is to organize and distribute knowledge of who are the domain experts within and without a given institution, company, or other organization. The intent in developing this KMS was to enable the re-use of organizational knowledge and provide a methodology for querying existing information (including structured, semistructured, and unstructured information) in a way that could help identify organizational experts. More specifically, Expert Seeker was developed to make it possible, by use of an intranet, to do any or all of the following: Assist an employee in identifying who has the skills needed for specific projects and to determine whether the experts so identified are available. Assist managers in identifying employees who may need training opportunities. Assist managers in determining what expertise is lost when employees retire or otherwise leave. Facilitate the development of new ways of identifying opportunities for innovation and minimization of duplicated efforts. Assist employees in achieving competitive advantages through the application of knowledge-management concepts and related systems. Assist external organizations in requesting speakers for specific engagements or determining from whom they might be able to request help via electronic mail. Help foster an environment of collaboration for rapid development in today's environment, in which it is increasingly necessary to assemble teams of experts from government, universities, research laboratories, and industries, to quickly solve problems anytime, anywhere. Make experts more visible. Provide a central repository of information about employees, including information that, heretofore, has typically not been captured by the human-resources systems (e.g., information about past projects, patents, or hobbies). Unify myriad collections of data into Web-enabled repository that could easily be searched for relevant data.

Fernandez, Becerra↗

NASA NTRS2011

NASA Risk Management Handbook

The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.

Dezfuli, Homayoon↗

NASA NTRS2012

Integrated Data Modeling and Simulation on the Joint Polar Satellite System Program

The Joint Polar Satellite System is a modern, large-scale, complex, multi-mission aerospace program, and presents a variety of design, testing and operational challenges due to: (1) System Scope: multi-mission coordination, role, responsibility and accountability challenges stemming from porous/ill-defined system and organizational boundaries (including foreign policy interactions) (2) Degree of Concurrency: design, implementation, integration, verification and operation occurring simultaneously, at multiple scales in the system hierarchy (3) Multi-Decadal Lifecycle: technical obsolesce, reliability and sustainment concerns, including those related to organizational and industrial base. Additionally, these systems tend to become embedded in the broader societal infrastructure, resulting in new system stakeholders with perhaps different preferences (4) Barriers to Effective Communications: process and cultural issues that emerge due to geographic dispersion and as one spans boundaries including gov./contractor, NASA/Other USG, and international relationships.

Roberts, Christopher J.↗

NASA NTRS2012

NASA Integrated Model Centric Architecture (NIMA) Model Use and Re-Use

This whitepaper accepts the goals, needs and objectives of NASA's Integrated Model-centric Architecture (NIMA); adds experience and expertise from the Constellation program as well as NASA's architecture development efforts; and provides suggested concepts, practices and norms that nurture and enable model use and re-use across programs, projects and other complex endeavors. Key components include the ability to effectively move relevant information through a large community, process patterns that support model reuse and the identification of the necessary meta-information (ex. history, credibility, and provenance) to safely use and re-use that information. In order to successfully Use and Re-Use Models and Simulations we must define and meet key organizational and structural needs: 1. We must understand and acknowledge all the roles and players involved from the initial need identification through to the final product, as well as how they change across the lifecycle. 2. We must create the necessary structural elements to store and share NIMA-enabled information throughout the Program or Project lifecycle. 3. We must create the necessary organizational processes to stand up and execute a NIMA-enabled Program or Project throughout its lifecycle. NASA must meet all three of these needs to successfully use and re-use models. The ability to Reuse Models a key component of NIMA and the capabilities inherent in NIMA are key to accomplishing NASA's space exploration goals. 11

Conroy, Mike↗