Engineering Papers⌕ Search

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.

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

At least 181 records · Page 10

The business case for connectivity

Information systems that provide competitive advantages to organizations can be broadly classified into those that improve the effectiveness of a business function and those that improve the reach of information in the organization. The latter, organizational connectivity systems, can be categorized as intraorganizational and interorganizational systems. Intraorganization systems provide connectivity to function areas within the business, while interorganizational systems support the exchange of business data between independent business units. These system are not confined to a single entity but span organizational boundaries which can be national or international in scope. A series of case studies was undertaken in an effort to better understand the issues and problems associated with providing an increased flow of information within and outside of an organization. Ten issues emerged from this study. In summary, it is necessary for firms to first consider how effective their internal communications systems are before launching projects that tie the organization to external systems.

Adams, Dennis↗

Total Quality Management in Space Shuttle Main Engine manufacturing

The Total Quality Management (TQM) philosophy developed in the Marshall Space Flight Center (MSFC) is briefly reviewed and the ongoing TQM implementation effort which is being pursued through the continuous improvement (CI) process is discussed. TQM is based on organizational excellence which integrates the new supportive culture with the technical tools necessary to identify, assess, and correct manufacturing processes. Particular attention is given to the prime contractor's change to the organizational excellence management philosophy in SSME manufacturing facilities.

Ding, J.↗

Commercial non-aerospace technology transfer program for the 2000s: Strategic analysis and implementation

This report presents a strategic analysis and implementation plan for NASA's Office of Commercial Programs (OCP), Technology Transfer Division's (TTD), Technology Transfer Program. The main objectives of this study are to: (1) characterize the NASA TTD's environment and past organizational structure; (2) clearly identify current and prospective programmatic efforts; (3) determine an evolutionary view of an organizational structure which could lead to the accomplishment of NASA's future technology transfer aims; and (4) formulate a strategy and plan to improve NASA's (and other federal agencies) ability to transfer technology to the non-aerospace sectors of the U.S. economy. The planning horizon for this study extends through the remainder of the 1990s to the year 2000.

Horsham, Gary A. P.↗

Organization and management of space grant programs

The 21 Space Grant Programs represent a broad range of organizational structures which operate programs ranging in size from single university organizations to organizations including up to 41 members involving a composite of industrial organizations such as state agencies, and universities. Some of the space grant awards were made to organizations already in existence with on-going programs while other awards were made to consortia newly formed for the purpose of applying to the Space Grant Program. The workshop on organization and management of Space Grant Programs provided an opportunity for directors and program representatives to discuss and compare the relative advantages and disadvantages of the various models being used. This paper offers examples of the diversity of organizations, summarizes the common concerns to be met by each organizational model, and provides a case study of the Texas Space Grant Consortium organization.

Sheppard, Sallie↗

Systems engineering and integration and management for manned space flight programs

This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.

Morris, Owen↗

Requirements for significant problem reporting and trend analysis

This handbook supplements policies, requirements, and procedures of NMI 8070.3 to ensure that NASA management at each organizational level is: fully aware of trends affecting both the level of safety and the potential for mission success established for both NASA manned space programs and its supporting institutions; fully and independently informed of problems that represent significant risk to the safety of all personnel (including the general populace) and to the success of a mission or operation through a program mechanism herein defined as Significant Problem Reporting; and in full agreement with the level of elimination of these problems through the closed-loop accounting of corrective actions. The requirements of this handbook are supportive of the agency's safety, reliability, maintainability, and quality assurance (SRM&QA) program objectives and are applicable to all organizational elements of NASA connected with or supporting developmental or operational manned space program/projects (including associated payloads) and the related institutional facilities.

George A Rodney↗

Facilities maintenance handbook

This handbook is a guide for facilities maintenance managers. Its objective is to set minimum facilities maintenance standards. It also provides recommendations on how to meet the standards to ensure that NASA maintains its facilities in a manner that protects and preserves its investment in the facilities in a cost-effective manner while safely and efficiently performing its mission. This handbook implements NMI 8831.1, which states NASA facilities maintenance policy and assigns organizational responsibilities for the management of facilities maintenance activities on all properties under NASA jurisdiction. It is a reference for facilities maintenance managers, not a step-by-step procedural manual. Because of the differences in NASA Field Installation organizations, this handbook does not assume or recommend a typical facilities maintenance organization. Instead, it uses a systems approach to describe the functions that should be included in any facilities maintenance management system, regardless of its organizational structure. For documents referenced in the handbook, the most recent version of the documents is applicable. This handbook is divided into three parts: Part 1 specifies common definitions and facilities maintenance requirements and amplifies the policy requirements contained in NMI 8831. 1; Part 2 provides guidance on how to meet the requirements of Part 1, containing recommendations only; Part 3 contains general facilities maintenance information. One objective of this handbook is to fix commonality of facilities maintenance definitions among the Centers. This will permit the application of uniform measures of facilities conditions, of the relationship between current replacement value and maintenance resources required, and of the backlog of deferred facilities maintenance. The utilization of facilities maintenance system functions will allow the Centers to quantitatively define maintenance objectives in common terms, prepare work plans, and develop management information in order to statistically identify and analyze variances from those plans. It will also add credibility to the NASA facilities maintenance budgeting process. The key to a successful maintenance program is the understanding and support of the senior Center managers.

Source record↗

Interoperability through standardization: Electronic mail, and X Window systems

Since the introduction of computing machines, there has been continual advances in computer and communication technologies and approaching limits. The user interface has evolved from a row of switches, character based interface using teletype terminals and then video terminals, to present day graphical user interface. It is expected that next significant advances will come in the availability of services, such as electronic mail and directory services, as the standards for applications are developed and in the 'easy to use' interfaces, such as Graphical User Interface for example Window and X Window, which are being standardized. Various proprietary electronic mail (email) systems are in use within organizations at each center of NASA. Each system provides email services to users within an organization, however the support for email services across organizations and across centers exists at centers to a varying degree and is often easy to use. A recent NASA email initiative is intended 'to provide a simple way to send email across organizational boundaries without disruption of installed base.' The initiative calls for integration of existing organizational email systems through gateways connected by a message switch, supporting X.400 and SMTP protocols, to create a NASA wide email system and for implementation of NASA wide email directory services based on OSI standard X.500. A brief overview of MSFC efforts as a part of this initiative are described. Window based graphical user interfaces make computers easy to use. X window protocol has been developed at Massachusetts Institute of Technology in 1984/1985 to provide uniform window based interface in a distributed computing environment with heterogenous computers. It has since become a standard supported by a number of major manufacturers. Z Windows systems, terminals and workstations, and X Window applications are becoming available. However impact of its use in the Local Area Network environment on the network traffic are not well understood. It is expected that the use of X Windows systems will increase at MSFC especially for Unix based systems. An overview of X Window protocol is presented and its impact on the network traffic is examined. It is proposed that an analytical model of X Window systems in the network environment be developed and validated through the use of measurements to generate application and user profiles.

Amin, Ashok T.↗

Challenging the Future - Journey to Excellence. Aeropropulsion strategic plan for the 1990's

Over the past several months, the Lewis Aeropropulsion Management Council (AMC) has conducted a critical assessment of its strategic plan. This assessment clearly indicated a need for change, both in the aeropropulsion program emphasis and in the approach to carrying out that program. Customers sent a strong message that the program must improve the timeliness of research and technology products and services and must work more closely with them to develop and transfer new technology. The strategic plan defines AMC's vision for the future and underlying organizational values. It contains a set of broad strategies and actions that point the way toward achieving the goals of customer satisfaction, organizational effectiveness, and programmatic excellence. Those strategies are expected to form the basis for the development of specific tactical plans by Lewis aeropropulsion thrust teams, divisions, and branches. To guide tactical planning of the aeropropulsion program, this strategic plan outlines the agency's strategic directions and long-range aeronautics goals, the aeropropulsion goals and key objectives for achieving them, projections of Lewis aeropropulsion budgets, planned allocations of resources, and the processes that will be used to measure success in carrying out the strategic plan.

Source record↗

Efficient mission control for the 48-satellite Globalstar Constellation

The Globalstar system is being developed by Globalstar, Limited Partnership and will utilize 48 satellites in low earth orbit (See Figure 1) to create a world-wide mobile communications system consistent with Vice President Gore's vision of a Global Information Infrastructure. As a large long term commercial system developed by a newly formed organization, Globalstar provides an excellent opportunity to explore innovative solutions for highly efficient satellite command and control. Design and operational concepts being developed are unencumbered by existing physical and organizational infrastructures. This program really is 'starting with a clean sheet of paper'. Globalstar operations challenges can appear enormous. Clearly, assigning even a single person around the clock to monitor and control each satellite is excessive for Globalstar (it would require a staff of 200! . Even with only a single contact per orbit per satellite, data acquisitions will start or stop every 45 seconds! Although essentially identical, over time the satellites will develop their own 'personalities'and will re quire different data calibrations and levels of support. This paper discusses the Globalstar system and challenges and presents engineering concepts, system design decisions, and operations concepts which address the combined needs and concerns of satellite, ground system, and operations teams. Lessons from past missions have been applied, organizational barriers broken, partnerships formed across the mission segments, and new operations concepts developed for satellite constellation management. Control center requirements were then developed from the operations concepts.

Smith, Dan↗

Domain analysis for the reuse of software development experiences

We need to be able to learn from past experiences so we can improve our software processes and products. The Experience Factory is an organizational structure designed to support and encourage the effective reuse of software experiences. This structure consists of two organizations which separates project development concerns from organizational concerns of experience packaging and learning. The experience factory provides the processes and support for analyzing, packaging, and improving the organization's stored experience. The project organization is structured to reuse this stored experience in its development efforts. However, a number of questions arise: What past experiences are relevant? Can they all be used (reused) on our current project? How do we take advantage of what has been learned in other parts of the organization? How do we take advantage of experience in the world-at-large? Can someone else's best practices be used in our organization with confidence? This paper describes approaches to help answer these questions. We propose both quantitative and qualitative approaches for effectively reusing software development experiences.

Basili, V. R.↗

The new organization: Rethinking work in the age of virtuality

Like two enormous steam engines, throttles wide-open, bells clanging and whistles screeching, careening toward each other down the same track, two powerful forces are about to collide and the point of collision will be smack in the middle of the white-collar workplace. Moreover, once the dust has settled, it is quite likely that we will never be able to think about the white-collar workplace in quite the same way again. The forces couldn't be more different. One force, the theory of complex adaptive systems, has its roots in the radical new sciences of chaos and complexity. The other force, the notion of organizations being learning systems, more like living organisms than 'information factories,' is an outgrowth of the new management thinking of leading organizational theorists like the Claremont Graduate School's Peter Drucker, MIT's Peter Senge, and Hitotsubashi University's Ikujiro Nonaka. Nevertheless, both the new science and the new management thinking seem to point to a similar and perhaps even startling conclusion: the business organization of the 21st century will look nothing like the bureaucratic organizational model that prevails in most companies today, a model that has remained largely unchanged since the manufacturing heydays of 1950s. While the details of the new organization remain sketchy, its rough outline is already beginning to take shape. Rather than simply being flatter through the elimination of layer upon layer of 'middle management,' the new organization is likely to be made up of networks of specialists who will be, for all practical purposes, self-managing. Rather than focusing on issues like re-engineering business processes, a holdover from Taylorism, the focus will be on supporting the continuous learning of an organization's specialists, the sharing of this learning with other specialists, and the embedding of this learning in the organization's physical structure. Finally, rather than viewing themselves as going through relatively long periods of stability punctuated by shorts bursts of 'reorganization,' business enterprises will come to realize that their very survival depends upon their being in a state of continuous organization. The implications of the new organization with respect to how companies approach the planning, design, and management of the technology infrastructure that enables individual learning, self-management, and continuous orgsnization, are both numerous and far-reaching. As part of this technology infrastructure, the white-collar workplace exists in the form it does today as a direct result of management's beliefs about how time, space, and tools ought to be organized and managed in order to accomplish useful intellectual work. Obviously, if these beliefs change radically, as both the new science and the new management thinking suggest is about to happen, then it is almost inevitable that the form and function of the white-collar workplace will change radically, as well. Will there even be a white-collar workplace in the 21st century, in the sense of purpose-built facilities designed to support the co-location of large numbers of white-collar workers? Only time will tell. However, the leading indicators seem to suggest that, as the old saying goes, 'We ain't seen nothin' yet!'

Sutherland, Duncan B., Jr.↗

Communication Problems in Requirements Engineering: A Field Study

The requirements engineering phase of software development projects is characterized by the intensity and importance of communication activities. During this phase, the various stakeholders must be able to communicate their requirements to the analysts, and the analysts need to be able to communicate the specifications they generate back to the stakeholders for validation. This paper describes a field investigation into the problems of communication between disparate communities involved in the requirements specification activities. The results of this study are discussed in terms of their relation to three major communication barriers: (1) ineffectiveness of the current communication channels; (2) restrictions on expressiveness imposed by notations; and (3) social and organizational barriers. The results confirm that organizational and social issues have great influence on the effectiveness of communication. They also show that in general, end-users find the notations used by software practitioners to model their requirements difficult to understand and validate.

Al-Rawas, Amer↗

The ASSIST: Bringing Information and Software Together for Scientists

The ASSIST was developed as a step toward overcoming the problems faced by researchers when trying to utilize complex and often conflicting astronomical data analysis systems. It implements a uniform graphical interface to analysis systems, documentation, data, and organizational memory. It is layered on top of the Answer Garden Substrate (AGS), a system specially designed to facilitate the collection and dissemination of organizational memory. Under the AISRP program, we further developed the ASSIST to make it even easier for researchers to overcome the difficulties of accessing software and information in a complex computer environment.

Mandel, Eric↗

International GPS Service for Geodynamics

This 1995 annual report of the IGS International GPS (Global Positioning System) Service for Geodynamics - describes the second operational year of the service. It provides the many IGS contributing agencies and the rapidly growing user community with essential information on current organizational and technical matters promoting the IGS standards and products (including organizational framework, data processing strategies, and statistics showing the remarkable expansion of the GPS monitoring network, the improvement of IGS performance, and product quality). It also introduces important practical concepts for network densification by integration of regional stations and the combination of station coordinate solutions. There are groups of articles describing general aspects of the IGS, the Associate Analysis Centers (AACs), Data Centers, and IGS stations.

Zumberge, J. F.↗

Characterizing and Assessing a Large-Scale Software Maintenance Organization

One important component of a software process is the organizational context in which the process is enacted. This component is often missing or incomplete in current process modeling approaches. One technique for modeling this perspective is the Actor-Dependency (AD) Model. This paper reports on a case study which used this approach to analyze and assess a large software maintenance organization. Our goal was to identify the approach's strengths and weaknesses while providing practical recommendations for improvement and research directions. The AD model was found to be very useful in capturing the important properties of the organizational context of the maintenance process, and aided in the understanding of the flaws found in this process. However, a number of opportunities for extending and improving the AD model were identified. Among others, there is a need to incorporate quantitative information to complement the qualitative model.

Briand, Lionel↗

Strategic Plan

The purpose of this document is to present the strategic plan and associated organizational structure that the National Space Biomedical Research Institute (NSBRI) will utilize to achieve the defined mission and objectives provided by NASA. Much of the information regarding the background and establishment of the NSBRI by NASA has been provided in other documentation and will not be repeated in this Strategic Plan. This Strategic Plan is presented in two volumes. Volume I (this volume) begins with an Introduction (Section 2) that provides the Institute's NASA-defined mission and objectives, and the organizational structure adopted to implement these through three Strategic Programs: Countermeasure Research; Education, Training and Outreach; and Cooperative Research and Development. These programs are described in Sections 3 to 5. Each program is presented in a similar way, using four subsections: Goals and Objectives; Current Strategies; Gaps and Modifications; and Resource Requirements. Section 6 provides the administrative infrastructure and total budget required to implement the Strategic Programs and assures that they form a single cohesive plan. This plan will ensure continued success of the Institute for the next five years. Volume II of the Strategic Plan provides an in-depth analysis of the current and future strategic programs of the 12 current NSBRI teams, including their goals, objectives, mutual interactions and schedules.

Source record↗

Safe Grid

The biggest users of GRID technologies came from the science and technology communities. These consist of government, industry and academia (national and international). The NASA GRID is moving into a higher technology readiness level (TRL) today; and as a joint effort among these leaders within government, academia, and industry, the NASA GRID plans to extend availability to enable scientists and engineers across these geographical boundaries collaborate to solve important problems facing the world in the 21 st century. In order to enable NASA programs and missions to use IPG resources for program and mission design, the IPG capabilities needs to be accessible from inside the NASA center networks. However, because different NASA centers maintain different security domains, the GRID penetration across different firewalls is a concern for center security people. This is the reason why some IPG resources are been separated from the NASA center network. Also, because of the center network security and ITAR concerns, the NASA IPG resource owner may not have full control over who can access remotely from outside the NASA center. In order to obtain organizational approval for secured remote access, the IPG infrastructure needs to be adapted to work with the NASA business process. Improvements need to be made before the IPG can be used for NASA program and mission development. The Secured Advanced Federated Environment (SAFE) technology is designed to provide federated security across NASA center and NASA partner's security domains. Instead of one giant center firewall which can be difficult to modify for different GRID applications, the SAFE "micro security domain" provide large number of professionally managed "micro firewalls" that can allow NASA centers to accept remote IPG access without the worry of damaging other center resources. The SAFE policy-driven capability-based federated security mechanism can enable joint organizational and resource owner approved remote access from outside of NASA centers. A SAFE enabled IPG can enable IPG capabilities to be available to NASA mission design teams across different NASA center and partner company firewalls. This paper will first discuss some of the potential security issues for IPG to work across NASA center firewalls. We will then present the SAFE federated security model. Finally we will present the concept of the architecture of a SAFE enabled IPG and how it can benefit NASA mission development.

Chow, Edward T.↗