Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Organizational Policy”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

A Human Factors Approach to Bridging Systems and Introducing New Technologies

The application of human factors in aviation has grown to cover a wide range of disciplines and methods capable of assessing human-systems integration at many levels. For example, at the individual level, pilot workload may be studied while at the team level, coordinated workload distribution may be the focal point. At the organizational level, the way in which individuals and teams are supported by training and standards, policies and procedures may introduce additional, relevant topics. A consideration of human factors at each level contributes to our understanding of successes and failures in pilot performance, but this system focused on the flight deck alone -- is only one part of the airspace system. In the FAA's NextGen plan to overhaul the National Airspace System (NAS), new capabilities will enhance flightdeck systems (pilots), flight operations centers (dispatchers) and air traffic control systems (controllers and air traffic managers). At a minimum, the current roles and responsibilities of these three systems are likely to change. Since increased automation will be central to many of the enhancements, the role of automation is also likely to change. Using NextGen examples, a human factors approach for bridging complex airspace systems will be the main focus of this presentation. It is still crucial to consider the human factors within each system, but the successful implementation of new technologies in the NAS requires an understanding of the collaborations that occur when these systems intersect. This human factors approach to studying collaborative systems begins with detailed task descriptions within each system to establish a baseline of the current operations. The collaborative content and context are delineated through the review of regulatory and advisory materials, letters of agreement, policies, procedures and documented practices. Field observations and interviews also help to fill out the picture. Key collaborative functions across systems are identified and placed on a phase-of-flight timeline including information requirements, decision authority and use of automation, as well as level of frequency and criticality.

Kanki, Barbara G.↗
NASA NTRSDate not supplied

Risk-Based SMA and Modernizing Risk Classification at GSFC

In 2014, in response to a large volume of feedback from industry, the science community, and internal to Goddard Space Flight Center (GSFC), GSFC’s Safety and Mission Assurance (SMA) Directorate began a transition to a risk-based implementation of SMA, departing from its longstanding practice of being primarily driven by a mostly static set of Mission Assurance Requirements. The transition started out with a pilot project involving risk-based acceptance of bare-printed circuit boards that was enormously successful, continued through a complete organizational transformation in 2015, and culminated with the baselining of formal Risk-Based SMA policy in 2016. In this presentation we will describe the risk-based SMA concept, segue into how it shapes a modernization of risk classification that GSFC has rolled out, and provide results from the original pilot project for risk-based SMA, involving the printed circuit board assurance process.

Jesse Leitner↗
NASA NTRS1972

Employee Communication at the NASA Langley Research Center

The means of employee communication at the NASA Langley Research Center are reported, and their effectiveness evaluated. The history, purpose, and structure of the organization as well as the employee educational background and salary status are discussed. Some of the approaches used by Langley Research Center management in communicating with their men are addressed and compared with recommendations of experts in employee communication. The results of personal interviews involving both employee and management assessment of management-employee communication are presented and evaluated. Employees need a great deal more recommunication from management providing rationale behind the cancellation of existing projects or the disapproval of proposed research projects. Also NASA management needs to establish a policy and guidelines for the rapid and simultaneous dissemination of all non-restricted information to employees during organizational activities having potential adverse effects on large numbers of personnel. Finally some improvements should be made in employee orientation procedures.

Bendura, R. J.↗
NASA NTRS1985

Space Station engineering and technology development

Historical background, costs, organizational assignments, technology development, user requirements, mission evolution, systems analyses and design, systems engineering and integration, contracting, and policies of the space station are discussed.

Source record↗
NASA NTRSDate not supplied

A Holistic Approach to Procedures

Aviation is a dynamic industry which is constantly changing. These changes require the continuous update of people’s knowledge and skills. A fundamental part of that knowledge and skill is procedures, because procedures form the backbone of aviation operations. On the flightdeck, on the ramp, and in the maintenance shop, procedures and checklists help support pilots, line crews, and mechanics in performing their work effectively, efficiently, and thus -- safely. To design effective and efficient procedures and checklists, one must take into account the full operational context within which these procedures are embedded. This context is defined by the requirements of the technology, the capabilities and limitations of the human operators, and the constraints and affordances of the operational environment. The complexity of this context arises from the interactions of the human, machine, and environment. Procedures are in place to govern those interactions. We present a model of that operational context, namely THE Model (Technology, Human, Environment in the context of a Mission), that lays a foundation for the analysis of each of these elements and their interactions. But procedures have their limitations, and there are risks involved in over-proceduralizing. To understand these limitations and risks, and to determine when to proceduralize and when not, we present the 4P Framework (Practice, Procedures, Policies, Philosophy) as a holistic approach to procedures. This approach brings together the understanding of human behavior, of organizational and operational factors, and of the technologies involved.

procedures↗
NASA NTRS1996

Planetary protection, legal ambiguity and the decision making process for Mars sample return

As scientists and mission planners develop planetary protection requirements for future Mars sample return missions, they must recognize the socio-political context in which decisions about the mission will be made and pay careful attention to public concerns about potential back contamination of Earth. To the extent that planetary protection questions are unresolved or unaddressed at the time of an actual mission, they offer convenient footholds for public challenges in both legal and decision making realms, over which NASA will have little direct control. In this paper, two particular non-scientific areas of special concern are discussed in detail: 1) legal issues and 2) the decision making process. Understanding these areas is critical for addressing legitimate public concerns as well as for fulfilling procedural requirements regardless whether sample return evokes public controversy. Legal issues with the potential to complicate future missions include: procedural review under National Environmental Policy Act (NEPA); uncertainty about institutional control and authority; conflicting regulations and overlapping jurisdictions; questions about international treaty obligations and large scale impacts; uncertanities about the nature of the organism; and constitutional and regulatory concerns about quarantine, public health and safety. In light of these important legal issues, it is critical that NASA consider the role and timing of public involvement in the decision making process as a way of anticipating problem areas and preparing for legitimate public questions and challenges to sample return missions.

NASA Discipline Number 59-10↗
NASA NTRS1971

Program audit, A management tool

Program gives in-depth view of organizational performance at all levels of the management structure, and provides means by which managers can effectively and efficiently evaluate adequacy of management direction, policies, and procedures.

Miller, T. J.↗
NASA NTRS1991

Advanced CRM training for instructors and evaluators

It is seen that if the maximum operational benefit of crew resource management (CRM) is to be achieved, the evaluator group is the principal key and specialized training that is ongoing is necessary for this group. The training must be customized to fit the needs of a particular organization, and the training must address key topical issues that influence organizational dynamics. Attention is given to the use of video and full length scripted NASA research LOFTS, behavioral markers and debriefing skills, the importance of policy and written CRM standards, and line oriented simulations debriefing performance indicators.

Taggart, William R.↗
NASA NTRS1976

Public policy for solar heating and cooling

Recent analyses indicated that solar heating and cooling systems for residential buildings are nearly economically competitive with conventional fossil fuel or electric systems, the former having higher initial cost but a lower operating cost than the latter. The paper examines obstacles to the widespread acceptance and use of solar space conditioning systems and explores some general policies which could help to overcome them. The discussion covers such institutional barriers limiting the adoption of solar technologies as existing building codes, financing constraints, and organizational structure of the building industry. The potential impact of financial incentives is analyzed. It is noted that a tax incentive of 25% could speed the use of solar energy by 7 to 8 years and produce an 8% reduction in fossil fuel use by 1990. A preliminary incentive package which could be helpful in promoting solar energy both at federal and state levels is proposed, and the necessary incentive level is analysed.

Hirshberg, A. S.↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
DOE OSTI2026

Coordinated Natural Gas and Electric Planning: Case Studies of Current Approaches and Practices

This paper examines how natural gas and electric utilities across eight U.S. states and two Canadian provinces are beginning to coordinate historically separate planning processes in response to growing system interdependencies, policy mandates, aging infrastructure, and changing customer energy choices. Electricity planning has long relied on robust integrated resource planning frameworks that weigh numerous objectives, risks, and costs. Natural gas planning, on the other hand, is typically less transparent and more narrowly focused on safety and system integrity. As economic, reliability, and policy drivers place new and shared demands on both systems, jurisdictions and utilities are experimenting with approaches such as coordinated forecasting, non pipeline alternatives, and combined planning pilots. A few have issued regulatory or statutory directives for greater data sharing and methodological alignment. Case studies from British Columbia, California, Colorado, Illinois, Massachusetts, Minnesota, New York, Québec, Rhode Island, and Washington illustrate a wide range of approaches to rethinking siloed planning. The paper identifies several common themes across the jurisdictions examined. It provides observations on the methods, processes, and organizational steps that may be needed in the future to address the challenges being faced by states and utilities. Lastly, it identifies some initial steps that states and utilities can consider if they would like to pursue more integrated, cost-effective, policy-aligned energy system planning.

03 NATURAL GAS↗
NASA NTRS1972

Definition of Earth Resources Policy and Management Problems in California

The activities of the Social Sciences Group in solving earth resources management problems as related to social factors, are reported. Major efforts of the Group revolved around identifying potential users of ERTS data, ascertain the user's needs, and assay the organizational impacts of new and technologically advanced sources of information. Attempts were also made to develop a linear programming model to be used in decision making with respect to resources being observed by ERTS and other remote sensing vehicles. The cost effectiveness of solving these management problems is discussed.

Churchman, C. W.↗
NASA NTRS1998

New Space Industries for the Next Millennium

New Space Industries For the Next Millennium is a final report of the findings from the New Space Industries Workshop held in Washington, DC, in February 1998. The primary purpose of this workshop was to identify what must be done to develop new markets, and to generate plans, milestones and new organizational relationships designed to facilitate the goal of space development. This document provides a summary report on the results of that workshop and is not intended as a statement of NASA or government policy. Previous studies had shown great potential for the development of new markets in space (e.g., travel and entertainment, space solar power, satellite and space transfer services, research and development in space, space manufacturing, and space resources), and a great need for coordination and formation of infrastructures (e.g., space transportation, space business parks, and space utilities), to facilitate the growth of new space businesses. The New Space Industries Workshop brought together government, academia, and industry participants from several previous studies and other professionals interested in the development of space for commercial purposes. Their participation provided input into the role of government and industry in space development as well as the technology needs that will enable space development. The opening of the frontier of space, not just to government missions but to private individuals and commercial business, is a challenge of overarching importance. It is our hope that the workshop and this final report continue in earnest the process of identifying and overcoming the barriers to large-scale public access and development of space in the early years of the next century.

Smitherman, D. V., Jr.↗
NASA NTRS2008

The New NASA Orbital Debris Mitigation Procedural Requirements and Standards

NASA has issued major updates to its principal orbital debris mitigation policy directive and standards. The new NASA Procedural Requirements for Limiting Orbital Debris (NPR 8715.6), with its supporting NASA Standard 8719.14, both refine earlier orbital debris mitigation documents and in some areas expand their applicability. Organizational and individual responsibilities along with general directives are set forth in NPR 8715.6. New requirements include routine conjunction assessments for all maneuverable NASA spacecraft in LEO and GEO, prompt notifications of intended or unintended debris generation, preparation and maintenance of formal end-of-mission plans, and disposal of vehicles in operation around the Moon and Mars and at the Earth-Sun Lagrangian points. NASA Standard 8719.14 replaces the 1995 NASA Safety Standard 1740.14 with no major new requirements but with several refinements and additions, some of which had already been adopted. Compliance with human casualty risk limitations from reentering debris will be calculated explicitly and not be expressed in terms of average debris casualty area. Moreover, the minimum kinetic energy threshold for potentially injurious reentering debris is set at 15 Joules. The overarching requirement for the disposal of GEO spacecraft and launch vehicle orbital stages is to ensure that the vehicles do not come within GEO + 200 km for at least 100 km after end of mission, rather than setting specific requirements for the disposal orbit. Spacecraft operating in or routinely transiting LEO must remain in the region for no more than 25 years after end of mission or 30 years after launch, whichever occurs sooner. A comprehensive new NASA handbook on orbital debris has also been prepared to provide background on the orbital debris environment and the related NASA mitigation requirements and standards.

Johnson, Nicholas L.↗
NASA NTRS1995

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 35: The use of computer networks in aerospace engineering

This research used survey research to explore and describe the use of computer networks by aerospace engineers. The study population included 2000 randomly selected U.S. aerospace engineers and scientists who subscribed to Aerospace Engineering. A total of 950 usable questionnaires were received by the cutoff date of July 1994. Study results contribute to existing knowledge about both computer network use and the nature of engineering work and communication. We found that 74 percent of mail survey respondents personally used computer networks. Electronic mail, file transfer, and remote login were the most widely used applications. Networks were used less often than face-to-face interactions in performing work tasks, but about equally with reading and telephone conversations, and more often than mail or fax. Network use was associated with a range of technical, organizational, and personal factors: lack of compatibility across systems, cost, inadequate access and training, and unwillingness to embrace new technologies and modes of work appear to discourage network use. The greatest positive impacts from networking appear to be increases in the amount of accurate and timely information available, better exchange of ideas across organizational boundaries, and enhanced work flexibility, efficiency, and quality. Involvement with classified or proprietary data and type of organizational structure did not distinguish network users from nonusers. The findings can be used by people involved in the design and implementation of networks in engineering communities to inform the development of more effective networking systems, services, and policies.

Bishop, Ann P.↗
NASA NTRS2016

NASA Systems Engineering Research Consortium: Defining the Path to Elegance in Systems

The NASA Systems Engineering Research Consortium was formed at the end of 2010 to study the approaches to producing elegant systems on a consistent basis. This has been a transformative study looking at the engineering and organizational basis of systems engineering. The consortium has engaged in a variety of research topics to determine the path to elegant systems. In the second year of the consortium, a systems engineering framework emerged which structured the approach to systems engineering and guided our research. This led in the third year to set of systems engineering postulates that the consortium is continuing to refine. The consortium has conducted several research projects that have contributed significantly to the understanding of systems engineering. The consortium has surveyed the application of the NASA 17 systems engineering processes, explored the physics and statistics of systems integration, and considered organizational aspects of systems engineering discipline integration. The systems integration methods have included system exergy analysis, Akaike Information Criteria (AIC), State Variable Analysis, Multidisciplinary Coupling Analysis (MCA), Multidisciplinary Design Optimization (MDO), System Cost Modelling, System Robustness, and Value Modelling. Organizational studies have included the variability of processes in change evaluations, margin management within the organization, information theory of board structures, social categorization of unintended consequences, and initial looks at applying cognitive science to systems engineering. Consortium members have also studied the bidirectional influence of policy and law with systems engineering.

Watson, Michael D.↗
NASA NTRS2016

NASA Systems Engineering Research Consortium: Defining the Path to Elegance in Systems

The NASA Systems Engineering Research Consortium was formed at the end of 2010 to study the approaches to producing elegant systems on a consistent basis. This has been a transformative study looking at the engineering and organizational basis of systems engineering. The consortium has engaged in a variety of research topics to determine the path to elegant systems. In the second year of the consortium, a systems engineering framework emerged which structured the approach to systems engineering and guided our research. This led in the third year to set of systems engineering postulates that the consortium is continuing to refine. The consortium has conducted several research projects that have contributed significantly to the understanding of systems engineering. The consortium has surveyed the application of the NASA 17 systems engineering processes, explored the physics and statistics of systems integration, and considered organizational aspects of systems engineering discipline integration. The systems integration methods have included system energy analysis, Akaike Information Criteria (AIC), State Variable Analysis, Multidisciplinary Coupling Analysis (MCA), Multidisciplinary Design Optimization (MDO), System Cost Modeling, System Robustness, and Value Modeling. Organizational studies have included the variability of processes in change evaluations, margin management within the organization, information theory of board structures, social categorization of unintended consequences, and initial looks at applying cognitive science to systems engineering. Consortium members have also studied the bidirectional influence of policy and law with systems engineering.

Watson, Michael D.↗
NASA NTRS2005

An Assessment of the Effectiveness of the AGATE Program Management Model

This report describes the collaborative program model chosen to implement an aeronautics research and technology program from 1994 through 2001: the Advanced General Aviation Transport Experiments (AGATE) Program. The Program had one primary objective: to improve the ability of the General Aviation industry to adopt technology as a solution to fulfill public benefit objectives. The primary objective of this report is to assess the program s ability to meet a combination of "effectiveness measures" from multiple stakeholders. The "effectiveness" of any model forms the foundation of legitimate questions for policy makers and professional federal managers. The participants rated AGATE as achieving its primary objectives and rating well on effectiveness in most areas, with high measures for relevance, cost, speed and public benefit, but lower measures for institutional fit and flexibility at dealing with the larger NASA organizational structure. This pattern mirrors private sector surveys and represents a tradeoff between the benefits of tailoring a program using partnering, versus the changes necessary within the institutional structure to support such tailoring.

Warner, Timothy P.↗