Display:

Results

Viewing 181 to 210 of 13118
2014-10-01
Standard
GEIAHB748_1
This guide clearly defines the purpose, goals, and objectives of an IBR. It also describes the attributes of an effective IBR and discusses a baseline review process that will lead to a better understanding of program risks. It provides a common definition and framework for the IBR Process. This process harmonizes, and to the extent possible, unifies the management objectives for all PMs. The IBR Process enables managers to effectively utilize the project Performance Measurement Baseline (PMB) to assess performance, and to better understand inherent risks. The IBR Process should continue throughout the life of a project.
2014-10-01
Standard
CMB6_8
Data Management in house training course.
2014-10-01
Standard
CMB6_6
The objective of this course is to provide an in-depth understanding of the concepts and principles involved in the Review and Configuration Audit process. It is intended for an individual who has completed a basic introductory course in CM and who requires the deeper knowledge of a CM practitioner rather than a superficial overview. Technical review and product audit practices described in this text are based on Government requirements. This emphasis is made because the Department of Defense DOD) represents a major customer of goods and services and because the referenced specifications and standards reflect good business practices refined over many years of usage. For commercial companies producing items for other companies or the public, many of these reviews and audits may not be formally implemented. They are, however, an integral and essential part of the systems engineering process.
2014-10-01
Standard
CMB6_10
In today's high technology environment, a variety of management tools have been developed within government and industry to govern the fast changing technical environment. There is a particular demand in industry for formal education in the disciplines of Configuration Management and Data Management (CM/DM). Briefly, Configuration Management is the disciplined continuous identification of design and control of changes. Data Management ensures that the data (technical, financial, administrative) delivered as part of a contract comply with contractual requirements and are adequate to satisfy the intended use or functions (e.g. logistics, maintenance, reprocurement).
2014-10-01
Standard
CMB6_3
Overview of Configuration Management. To manage the development and procurement of modern-day hardware and software systems, the project management concept and many engineering, logistic, and management disciplines have developed over the years. Configuration Management (CM) is the special name that has been coined to describe those specialized engineering management practices used by industry and the Government to define and control items (sometimes referred to as configuration items (CIS)) in their inventories. CM supports the establishment of a product service network for all hardware, software, and supporting data in the form of drawings, design documents, operating manuals, repair instructions, etc., being developed, and ensures the continued serviceability of these items as changes are made throughout their service lives.
2014-10-01
Standard
CMB4_1A
This Bulletin is intended for use as a guide and defines the terms and definitions to be used during the development, documentation, verification, and delivery cycles of new and modified computer software. It lists and defines the most common terms currently used int he world of computer software configuration management. There has been no attempt to compete with some of the more formal documents in use within the software programming community.
2014-10-01
Standard
CMB4_3
Computer software libraries are an essential element of a software configuration management (CM) system. However, the term, "library" while commonly used in the world of software, has had no significance in the field of CM until recently. Further, even in the software, world, the term has several different meanings. The purpose of this bulletin is to relate the term to the software CM system, e.g., the role of a library in the release of software. It describes the three types of libraries which are involved in the system, it discusses the principles and factors which affect their design and it presents a model, including samples o records and forms. Also included is a "univerals" position description for a librarian.
2014-10-01
Standard
CMB5A
The purpose of this Bulleting is to provide a guide for the Buyer in levying tailored CM requirements on his Suppliers; and as a guide for the Suppliers to assist in establishing a management system necessary to satisfy those requirements. through general use of this Bulletin, it is anticipated that: a. Alll buyers, at any level, can impose more consistent CM requirements on the Suppliers. b. Suppliers, because of consistent requirements imposed upon them by the Buyers, will be able to use the same internal systems for all supply activity. c. Because of consistency of requirements and systems, the overall system costs should be reduced.
2014-10-01
Standard
GEIASE0001
The purpose of this panel was to present a set of visions about how Systems Engineering (SE) will transform the engineering of systems in the next decade through development and application of concepts under current Research and Development (R&D). A survey was done of the most significant and innovative systems engineering Initiatives and Technologies covering: Processes Methods, techniques and standards Engineering environments and tools Modeling and simulation Representatives of the most influential Initiatives and Technologies identified were invited to become panelists. Panelists presented an overview of their Initiatives or Technologies and engaged in question and answer periods to elicit further understanding. A final capstone session assessed the effectiveness of the approaches being taken by academia, government and industry.
2014-10-01
Standard
CMB6_9
The functional and/or physical characteristics or hardware/software as set forth in technical documentation and achieved in a product. What is Configuration Management? A discipline applying technical and administrative direction and surveillance to (a) identify and document the functional and physical characteristics of a configuration item, (b) control changes to those characteristics, and (c) record and report change processing and implementation status.
2014-10-01
Standard
CMB7_2
This guideline is not intended to provide detailed instructions for implementing an automated CM system. It is intended to provide a framework for planning the automation of CM functions by identifying the issues and potential problems to be considered. We begin with a look at the current problems encountered with the use of manual and semiautomated CM approaches. In order to aid in the cultural acceptance of a fully automated CM system, the benefits of automation are reviewed and the issues of the psychology or change are discussed. Finally, this guideline focuses on automating the CM functions: identification, configuration control, status accounting, and audit. Given current technology and the constraints of available resources, this seciton discusses some of the concerns which must be addressed in order to achieve a successful implementation.
2014-10-01
Standard
CMB7_1
The scope of this bulletin is to provide guidance on the use of current and future technologies for the electronic interchange of CMS data. the purpose of this guide is to ensure requirements of CM (identificaiton, control, status accounting and audit) are used as the basis for transitioning to an automated environment.
2014-10-01
Standard
CMB7_3
the purpose of the Statement of Work is to define the Configuration Management requirements necessary to maintain and control CALS databases and provide transmission, access and receipt of digital data between contractors, subcontractors, vendors and the government. Digital data includes not only traditional configuration management documents such as specifications, drawings, and ECP's but includes all technical data listed in the CDRL. This Model SOW document will provide the government suggested SOW wording that should be included in RFP's and guidance in applying those SOW paragraphs.
2014-10-01
Standard
DMG1
To the reader, this publication may appear to have been prepared soley to provide guidance for companies doing business with the Department of Defense (DoD). Such is not the case. The DoD, as the largest procurer of data, has the greatest number of regulations governing the acquisition of data, and, therefore, presents the most problems to the data provider. However, principles which apply to all data acquisitions and their implementation can be tailored to satisfy various customers. The present day world of technical advancement sees increasing demands for recorded information. This documentation provides a means for communicating technical ideas, presents plans for developing them, gives instructions to those who will build, operate and service hardware, records the results of technical performance tests and evaluation, and provides visibility for managing technical and business aspects that are necessary to assure program success.
2014-10-01
Standard
CMB7_4A
This Bulletin provides a comprehensive list of Terms and Definitions used in or related to TechAmerica prepared standards/documents. The information in these listings was extracted from standards and documents prepared by the Systems Engineering (G47), Configuration Management (G33), Life Cycle Logistics Supportability and Enterprise Information Management Interoperability Committees along with other pertinent international, industry and government standards. It is intended that this bulletin be used as a resource to help with harmonization of terms and definitions across standards. One should be cognizant of the release date of this Bulletin and understand that updates to the included standards and handbooks after this Bulletin was released may affect its accuracy.
2014-10-01
Journal Article
2014-01-9027
Berna Balta, Onur Erk, H. Ali Solak, Numan Durakbasa
Rear underrun protection device is crucial for rear impact and rear under-running of the passenger vehicles to the heavy duty trucks. Rear underrun protection device design should obey the safety regulative rules and successfully pass several test conditions. The objective and scope of this paper is the constrained optimization of the design of a rear underrun protection device (RUPD) beam of heavy duty trucks for impact loading using correlated CAE and test methodologies. In order to minimize the design iteration phase of the heavy duty truck RUPD, an effective, real-life testing correlated, finite element model have been constructed via RADIOSS software. Later on, Pareto Optimization has been applied to the finite element model, by constructing designed experiments. The best solution has been selected in terms of cost, manufacturing and performance. Finally, real-life verification testing has been applied for the correlation of the optimum solution.
2014-10-01
Book
Honda's October 2014 R&D Technical Review features cutting-edge developments from Honda's worldwide R&D teams. This edition brings 32 original papers. They cover advancements in the following areas: • Development of HF120 turbofan engine • Development of High-access survey robot for TEPCO's Fukushima Daiichi Nuclear Power Station • Advanced ignition control technology for HCCI Combustion • Identification of brake-drag mechanism in coasting-down mode and proposal of brake-drag stabilization and reduction methods
2014-09-30
Article
The industry outlook for 2021 underscores engineering efficiency and flexible, modular architectures, according to industry forecasters IHS Automotive.
2014-09-30
Technical Paper
2014-01-2350
Zhiguo Zhao, Guanyu Zheng, Fengshuang Wang, Suying Zhang, Jianhua Zhang
In order to satisfy China IV emissions regulations, a unique design concept was proposed with injector closely coupled with Selective Catalytic Reduction (SCR) system outer body. The benefit of this design is significant in cost reduction and installation convenience. One paper was published to describe the vertical inlet layout [1]; this work is the second part describing applications of this concept to horizontal inlet configurations. For horizontal inlet pipe, two mixing pipe designs were proposed to avoid urea deposit and meet EU IV emission regulations. Computational Fluid Dynamics (CFD) technique was used to evaluate two design concepts; experiments were performed to validate both designs. CFD computations and experiments give the same direction on ranking of the two decomposition tubes. With the straight decomposition pipe design and unique perforated baffle design, no urea deposits were found; in addition, the emission level satisfied EU IV regulations.
2014-09-30
Technical Paper
2014-01-2395
Gurunathan Varun Kumar, Meer Reshma Sheerin, Vedachalam Saravana Prabu, Kallikadan Jean, Chaitanya Rajguru, Murugesan Dinesh, Andrew Croft
Abstract Automotive climate control systems are evolving at a rapid pace to meet the overall vehicle requirements and the user expectations for comfort and convenience. This poses a challenge in the product development life cycle of multi-platform vehicle systems with respect to development time and optimal performance in the Heating, Ventilation and Air Conditioning (HVAC) system. This paper proposes rapid HVAC plant model design and development using simplified one-dimensional (1D) simulation models for fast simulations. The specific accuracy limitations of such a simplified model are overcome using limited three-dimensional computational fluid dynamics (3D CFD) modelling. User-level control strategy is developed in an integrated simulation environment that includes a reference 1D model and a control algorithm simulator. The simulation data is used to study and analyse the temperature and airflow distribution in the system.
2014-09-30
Technical Paper
2014-01-2394
Demetrio Cortese
Abstract Using a Model-based approach to the embedded software development process contributed significantly in reducing the development time while also supporting a high quality level of the software code implementation. However, based on our experience with CNH Industrial application scenarios, involving multiple suppliers from vehicle ECU to the engine ECU, it only addressed the need of the implementation phase without any consistent influence in other software development life-cycle phases such as requirements and specification. Mandatory functional safety requirements, new complex functionalities, and reducing time to delivery while maintaining high quality level of software are driving factors in our new software development projects. Ideally the adoption of international standards, as for example the ISO 12007, and the safety standards, as the ISO 26262, ISO 25119 and ISO 13849, should represent a consistent guide to develop software.
2014-09-30
Journal Article
2014-01-2410
Xinyu Ge, Jonathan Jackson
Cost reduction in the automotive industry becomes a widely-adopted operational strategy not only for Original Equipment Manufacturers (OEMs) that take cost leader generic corporation strategy, but also for many OEMs that take differentiation generic corporation strategy. Since differentiation generic strategy requires an organization to provide a product or service above the industry average level, a premium is typically included in the tag price for those products or services. Cost reduction measures could increase risks for the organizations that pursue differentiation strategy. Although manufacturers in the automotive industry dramatically improved production efficiency in past ten years, they are still facing the pressure of cost control. The big challenge in cost control for automakers and suppliers is increasing prices of raw materials, energy and labor costs. These costs create constraints for the traditional economic expansion model.
2014-09-28
Journal Article
2014-01-2487
Mohamed Samy Barakat
The Braking System is the most crucial part of the racing vehicle. There is no doubt, that if only one minority failure in the braking system took place, this would be more than enough reason to cause the racing team disqualification from the competition. Time is the main and the most important criteria for any racing competition; on the other hand the formula student “FS UK SAE” competition care the most about developing the automotive engineering sense in the students by putting them under strict rules normally taken from the original version “formula 1” to encourage their creativity to reach the optimum performance under these strict rules. One of the most important rules is “No Braking by wire”, and the obvious consequences are more stopping distance and time. Braking distance is a critical facture in achieving racing success in a competitive domain.
2014-09-23
WIP Standard
GEIA859B
Data is information (e.g., concepts, thoughts, and opinions) that have been recorded in a form that is convenient to move or process. Data may represent tables of values of various types (numbers, characters, and so on). Data can also take more complex forms such as engineering drawings and other documents, software, pictures, maps, sound, and animation.

Data management, from the perspective of this standard, consists of the disciplined processes and systems that plan for, acquire, and provide stewardship for product and product-related business data, consistent with requirements, throughout the product and data life cycles. Thus, this standard primarily addresses product data and the business data required for collaboration from the team level or extended through the trading partner level during product acquisition and sustainment. It is recognized, however, that the principles described in this standard also have broader application to business data and operational data generally.

2014-09-16
Technical Paper
2014-01-2125
Janice Meraglia, Mitchell Miller
Abstract Counterfeit items can be viewed as the by-product of a supply chain which has been compromised. While many industries are impacted, certain types of products can mean the difference between life and death. Electronics are of special interest, however, mechanical parts can also have dire consequences. The point is that the counterfeiting community is very diverse. The business model is fluid and unrestricted. Electronics today…hardware tomorrow. All of this leads to the need for an authentication platform that is agnostic to product. Most supply chains would benefit from a technical way to have assurance of authenticity - a benefit that could be shared by all.
2014-09-16
Technical Paper
2014-01-2173
Aurelie Beaugency, Marc Gatti, Didier Regis
Abstract Since 2000, avionics is facing several changes, mostly driven by technological improvements in the electronics industry and innovation requirements from aircraft manufacturers. First, it has progressively lost its technological leadership over innovation processes. Second, the explosion of the electronics consumer industry has contributed to shorten even more its technology life cycles, and promoted the use of COTS. Third, the increasing complexity of avionics systems, which integrate more and more functions, have encouraged new players to enter the market. The aim of this article is to analyze how technological changes can affect the competitiveness of avionics firms. We refer to criticality levels as a determinant of the market competitiveness. Certification processes and costs could stop new comers to bring innovations from the consumer electronics industry and protects traditional players.
2014-09-16
Technical Paper
2014-01-2165
Andreas Himmler
Abstract To make the development of complex aircraft systems manageable and economical, tests must be performed as early as possible in the development process. The test goals are already set in advance before the first hardware for the ECUs exists, to be able to make statements about the system functions or possible malfunctions. This paper describes the requirements on and solutions for test systems for ECUs that arise from these goals. It especially focuses on how a seamless workflow and consistent use of test systems and necessary software tools can be achieved, from the virtual test of ECUs, which exist only as models, up to the test of real hardware. This will be shown in connection with a scalable, fully software-configurable hardware-in-the-loop (HIL) technology. The paper also covers the seamless use of software tools that are required for HIL testing throughout the different test phases, enabling the reuse of work products throughout the test phases.
2014-09-16
Technical Paper
2014-01-2149
Jace Allen
Abstract In the last few years, we have seen a tremendous increase in the rise in product complexity due to advances in technology and aircraft system functionality enhancement. The Model-based Design (MBD) process has helped manage the complexity of these systems while making product development faster by bringing more effective tools and methods to the entire process. Developing software using MBD has required extensive, sophisticated tool-chains that allow for efficient rapid controls prototyping, automatic code generation, and advanced validation and verification techniques using model-in-the-loop (MIL), software-in-the-loop (SIL), and hardware-in-the-loop (HIL) for both component testing and integration testing. However, the MBD process leads to generation of large volumes of data artifacts and work-products throughout the V-Cycle.
2014-09-16
Technical Paper
2014-01-2262
Rostislav Sirotkin, Galina Susova, Gennadii Shcherbakov
Abstract Within the Russian aviation industry the necessary level of reliability risks related to the failures of aircraft mechanical parts and systems vital to the safety of flight is assured via the system of activities aimed at influencing the parameters of critical parts (CP). The goal of the system is to provide a relationship between activities aimed at prevention of dangerous failures at all phases of airplane life cycle. The system operation is regulated by the normative documents and by controlling their observance. Normative documents containing requirements and recommendations were developed about 15 years ago based on the industry experience and traditions and taking into account the requirements of AS9100 series of international standards [2] wherever possible. The documents were developed taking into account typical safety management errors outlined in [1].
2014-09-16
Technical Paper
2014-01-2214
Manxue Lu
Abstract This article attempts to provide a big picture of systems engineering in both philosophy and engineering perspectives, discusses current status and issues, trends of systems engineering development, future directions and challenges, followed by certain examples.
Viewing 181 to 210 of 13118

Filter