FOREWORD
In the future, the competitiveness of modern technical systems will depend on characteristics like reliability, maintainability, operability, safety, and affordability. In order to achieve these characteristics, it is necessary to create mechanisms for dealing with mutually competing design requirements. It is fair to say that there is no optimal design; in essence, there is no design which can incorporate all optimal solutions proposed by specialist disciplines. Thus, the best design should represent the optimal compromise between competing requirements during the system integration process.
The traditional engineering and management education process, and consequently existing literature, does not encourage systems thinking, and even less prepare project managers and system integrators the for task of managing the system integration process.
Thus, there is a real need for better literature in the area of system engineering management. Decision makers need to be equipped with knowledge based on sound technical and scientific principles rather than personal experience and belief.
DR. J. KNEZEVIC
Reader in reliability and logistics engineering, School of Engineering, and director,
Research Centre for Management of Industrial Reliability, Cost and Effectiveness University of Exeter, United Kingdom
In the future, the competitiveness of modern technical systems will depend on characteristics like reliability, maintainability, operability, safety, and affordability. In order to achieve these characteristics, it is necessary to create mechanisms for dealing with mutually competing design requirements. It is fair to say that there is no optimal design; in essence, there is no design which can incorporate all optimal solutions proposed by specialist disciplines. Thus, the best design should represent the optimal compromise between competing requirements during the system integration process.
The traditional engineering and management education process, and consequently existing literature, does not encourage systems thinking, and even less prepare project managers and system integrators the for task of managing the system integration process.
Thus, there is a real need for better literature in the area of system engineering management. Decision makers need to be equipped with knowledge based on sound technical and scientific principles rather than personal experience and belief.
DR. J. KNEZEVIC
Reader in reliability and logistics engineering, School of Engineering, and director,
Research Centre for Management of Industrial Reliability, Cost and Effectiveness University of Exeter, United Kingdom
FOREWORD
The multidisciplinary domain of systems engineering is finally being recognized for its potential to facilitate development systems fully responsive to customer requirement. This recognition is even more pronounced in the case of complex, distributed, and software-intensive systems. The development and implementation of system engineering processes and practices notwithstanding, their effective and efficient management is imperative if their full potential is to be realized. Management and organizational issues become even more pronounced for projects involving a geographically distributed design team from multiple organizations.
Only an individual such as Ben Blanchard, with a vast and balanced experience within industry (seventeen years-Boeing. General Dynamics, Bendix) and academia (twenty-five years-Virginia Tech) can harness, demystify, and then explain the issues relating to system engineering management. This is reflected in System Engineering Management. While providing the necessary focus on the core subject, the reader is also provided an insight into the vast literature supporting this field through numerous well-placed footnotes and a detailed bibliography.
System Engineering Management provides a proper context by first focusing on the need for systems engineering along with a discussion of the current development environment. Thereafter, the focus shifts to the systems engineering process itself along with a discussion of selected and pertinent system engineering tools. With this introduction, the author then discusses the organizational and management issues and concerns at length. The simple and lucid discussion of the subject matter will make this textbook an indispensable addition to the library of any professional involved in the implementation and management of the system engineering process.
DINESH VERMA, PH.D.
Lockheed Martin Federal Systems, Inc.
http://128.102.216.35/factsheets/category.php?c=21
http://home2.btconnect.com/managingstandard/semp31.htm
home.btconnect.com/managingstandard/semp1.htm
SYSTEM ENGINEERING MANAGEMENT
The successful implementation of system engineering concepts and principles is dependent not only on technological issues as well. As illustrated in Figure 1.20, there are two sides of the spectrum, each dependent on the other. The best tools/models may be to available to implement the process shown in Figure 1.12; however, there is no guarantee for success the proper organizational environment has been created and an effective management structure is in place. Top management must first believe in and then provide the necessary support to enable the application of system engineering methods on in-house projects. Specific objectives must be defined, policies and procedures must be developed, and an effective reward structure must be supportive.
Although there are variations from one program to the next, Figure 1.21 presents a baseline for discussion. The major program phases and milestones are noted, along with a few selected activities and events that are significant from a system engineering perspective.
During the early stages of conceptual design, it is essential that good communications between the producer and the consumer(s) be established from the beginning. Defining the true need, conduction feasibility analyses, developing operational requirement and the maintenance concept, and identifying specific quantitative and qualitative requirement at the system level are critical! These requirements must be properly conveyed through a well-prepared System Specification (Type "A"). This top-level system specification constitutes the most important technical document, from which all lower-level specification evolve. Without a good "foundation" from the beginning, all subsequent lower-level requirements may be questionable
During the latter stages of conceptual design, a comprehensive System Engineering Management Plant (SEMP) must be developed to ensure the implementation of a program that will lead to a will-coordinated and integrated product output. The SEMP, which evolves from the top-level Program Management Plan (PMP), provides the integration of lower-level planning documents. It includes the design related tasks necessary to enhance the day-to-day system development effort, the implementation of concurrent engineering methods, and the integration of the appropriate organizational entities into a "team" approach. The SEMP must directly support the requirements in the System Specification (Type "A") from a management perspective, and the two documents must "talk to each other!"
During the latter stages of conceptual design, a Test and Evaluation Master Plan (TEMP), or equivalent, must be developed for the purposes of assessment and ultimate validation. As requirements are initially specified in the System Specification (Type "A") and planned through the tasks described in the SEMP, the methods/techniques to be used for measuring and evaluating the system to ensure compliance with these requirements must be described. This plan must address test and evaluation on a fully integrated basis, employing the appropriate combination of simulation and other analytical tools, mockups, laboratory models, and prototype models.
As system design and development progresses, there is a need to schedule a series of formal design reviews at discrete points where the design configuration evolves from one level of definition to another; that is, conceptual, system equipment/software, and critical design reviews. The purpose of these reviews is to ensure that the specified requirements are being met prior to entering into a subsequent phase of effort, and to ensure that the necessary communications exist across organizational lines.
Toward the latter stages of detail design, throughout the construction/production phase, and during the operational use and maintenance support phase, there is a need to provide an ongoing system assessment and validation effort. The objective is to ensure that the consumer requirements are being met, and to establish a "baseline" for the purposes of benchmarking and the initiation of a continuous process improvement activity. Design changes are initiated as required to correct any note deficiencies.
The successful implementation of system engineering principles is highly dependent on properly managing the simplified process depicted in Figure 1.22. Inherent within this process is the application of the different technologies employed to facilitate the step of requirements analysis, functional analysis and allocation, synthesis, design optimization, and validation.
Benjamin S. Blanchard
Virginia Polytechnic Institute
Blacksburg, Virginia
United Kingdom
The multidisciplinary domain of systems engineering is finally being recognized for its potential to facilitate development systems fully responsive to customer requirement. This recognition is even more pronounced in the case of complex, distributed, and software-intensive systems. The development and implementation of system engineering processes and practices notwithstanding, their effective and efficient management is imperative if their full potential is to be realized. Management and organizational issues become even more pronounced for projects involving a geographically distributed design team from multiple organizations.
Only an individual such as Ben Blanchard, with a vast and balanced experience within industry (seventeen years-Boeing. General Dynamics, Bendix) and academia (twenty-five years-Virginia Tech) can harness, demystify, and then explain the issues relating to system engineering management. This is reflected in System Engineering Management. While providing the necessary focus on the core subject, the reader is also provided an insight into the vast literature supporting this field through numerous well-placed footnotes and a detailed bibliography.
System Engineering Management provides a proper context by first focusing on the need for systems engineering along with a discussion of the current development environment. Thereafter, the focus shifts to the systems engineering process itself along with a discussion of selected and pertinent system engineering tools. With this introduction, the author then discusses the organizational and management issues and concerns at length. The simple and lucid discussion of the subject matter will make this textbook an indispensable addition to the library of any professional involved in the implementation and management of the system engineering process.
DINESH VERMA, PH.D.
Lockheed Martin Federal Systems, Inc.
http://128.102.216.35/factsheets/category.php?c=21
http://home2.btconnect.com/managingstandard/semp31.htm
home.btconnect.com/managingstandard/semp1.htm
SYSTEM ENGINEERING MANAGEMENT
The successful implementation of system engineering concepts and principles is dependent not only on technological issues as well. As illustrated in Figure 1.20, there are two sides of the spectrum, each dependent on the other. The best tools/models may be to available to implement the process shown in Figure 1.12; however, there is no guarantee for success the proper organizational environment has been created and an effective management structure is in place. Top management must first believe in and then provide the necessary support to enable the application of system engineering methods on in-house projects. Specific objectives must be defined, policies and procedures must be developed, and an effective reward structure must be supportive.
Although there are variations from one program to the next, Figure 1.21 presents a baseline for discussion. The major program phases and milestones are noted, along with a few selected activities and events that are significant from a system engineering perspective.
During the early stages of conceptual design, it is essential that good communications between the producer and the consumer(s) be established from the beginning. Defining the true need, conduction feasibility analyses, developing operational requirement and the maintenance concept, and identifying specific quantitative and qualitative requirement at the system level are critical! These requirements must be properly conveyed through a well-prepared System Specification (Type "A"). This top-level system specification constitutes the most important technical document, from which all lower-level specification evolve. Without a good "foundation" from the beginning, all subsequent lower-level requirements may be questionable
During the latter stages of conceptual design, a comprehensive System Engineering Management Plant (SEMP) must be developed to ensure the implementation of a program that will lead to a will-coordinated and integrated product output. The SEMP, which evolves from the top-level Program Management Plan (PMP), provides the integration of lower-level planning documents. It includes the design related tasks necessary to enhance the day-to-day system development effort, the implementation of concurrent engineering methods, and the integration of the appropriate organizational entities into a "team" approach. The SEMP must directly support the requirements in the System Specification (Type "A") from a management perspective, and the two documents must "talk to each other!"
During the latter stages of conceptual design, a Test and Evaluation Master Plan (TEMP), or equivalent, must be developed for the purposes of assessment and ultimate validation. As requirements are initially specified in the System Specification (Type "A") and planned through the tasks described in the SEMP, the methods/techniques to be used for measuring and evaluating the system to ensure compliance with these requirements must be described. This plan must address test and evaluation on a fully integrated basis, employing the appropriate combination of simulation and other analytical tools, mockups, laboratory models, and prototype models.
As system design and development progresses, there is a need to schedule a series of formal design reviews at discrete points where the design configuration evolves from one level of definition to another; that is, conceptual, system equipment/software, and critical design reviews. The purpose of these reviews is to ensure that the specified requirements are being met prior to entering into a subsequent phase of effort, and to ensure that the necessary communications exist across organizational lines.
Toward the latter stages of detail design, throughout the construction/production phase, and during the operational use and maintenance support phase, there is a need to provide an ongoing system assessment and validation effort. The objective is to ensure that the consumer requirements are being met, and to establish a "baseline" for the purposes of benchmarking and the initiation of a continuous process improvement activity. Design changes are initiated as required to correct any note deficiencies.
The successful implementation of system engineering principles is highly dependent on properly managing the simplified process depicted in Figure 1.22. Inherent within this process is the application of the different technologies employed to facilitate the step of requirements analysis, functional analysis and allocation, synthesis, design optimization, and validation.
Benjamin S. Blanchard
Virginia Polytechnic Institute
Blacksburg, Virginia
United Kingdom
http://www.sea-engr.com/body.php
ไม่มีความคิดเห็น:
แสดงความคิดเห็น