141,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Fachliteratur
- Serie: Wiley Series in Systems Engineering and Management
- Sprache: Englisch
A practical, step-by-step guide to total systems management Systems Engineering Management, Fifth Edition is a practical guide to the tools and methodologies used in the field. Using a "total systems management" approach, this book covers everything from initial establishment to system retirement, including design and development, testing, production, operations, maintenance, and support. This new edition has been fully updated to reflect the latest tools and best practices, and includes rich discussion on computer-based modeling and hardware and software systems integration. New case studies illustrate real-world application on both large- and small-scale systems in a variety of industries, and the companion website provides access to bonus case studies and helpful review checklists. The provided instructor's manual eases classroom integration, and updated end-of-chapter questions help reinforce the material. The challenges faced by system engineers are candidly addressed, with full guidance toward the tools they use daily to reduce costs and increase efficiency. System Engineering Management integrates industrial engineering, project management, and leadership skills into a unique emerging field. This book unifies these different skill sets into a single step-by-step approach that produces a well-rounded systems engineering management framework. * Learn the total systems lifecycle with real-world applications * Explore cutting edge design methods and technology * Integrate software and hardware systems for total SEM * Learn the critical IT principles that lead to robust systems Successful systems engineering managers must be capable of leading teams to produce systems that are robust, high-quality, supportable, cost effective, and responsive. Skilled, knowledgeable professionals are in demand across engineering fields, but also in industries as diverse as healthcare and communications. Systems Engineering Management, Fifth Edition provides practical, invaluable guidance for a nuanced field.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 896
Veröffentlichungsjahr: 2016
Ähnliche
Table of Contents
Title Page
Copyright
Preface
Chapter 1: Introduction to System Engineering
1.1 Definition of a System
1.2 The Current Environment: Some Challenges
1.3 The Need for System Engineering
1.4 Related Terms and Definitions
1.5 System Engineering Management
1.6 Summary
Questions and Problems
Chapter 2: The System Engineering Process
2.1 Definition of the Problem (Current Deficiency)
2.2 System Requirements (Needs Analysis)
2.3 System Feasibility Analysis
2.4 System Operational Requirements
2.5 The Logistics and Maintenance Support Concept
2.6 Identification and Prioritization of Technical Performance Measures (TPMs)
2.7 Functional Analysis
2.8 Requirements Allocation
2.9 System Synthesis, Analysis, and Design Optimization
2.10 Design Integration
2.11 System Test and Evaluation
2.12 Production and/or Construction
2.13 System Operational Use and Sustaining Support
2.14 System Retirement and Material Recycling/Disposal
2.15 Summary
Questions and Problems
Chapter 3: System Design Requirements
3.1 Development of Design Requirements and Design-To Criteria
3.2 Development of Specifications
3.3 The Integration of System Design Activities
3.4 Selected Design Engineering Disciplines
3.5 SOS Integration and Interoperability Requirements
3.6 Summary
Questions and Problems
Chapter 4: Engineering Design Methods and Tools
4.1 Conventional Design Practices
4.2 Analytical Methods
4.3 Information Technology, the Internet, and Emerging Technologies
4.4 Current Design Technologies and Tools
4.5 Computer-Aided Design (CAD)
4.6 Computer-Aided Manufacturing (CAM)
4.7 Computer-Aided Support (CAS)
4.8 Summary
Questions and Problems
Chapter 5: Design Review and Evaluation
5.1 Design Review and Evaluation Requirements
5.2 Informal Day-to-Day Review and Evaluation
5.3 Formal Design Reviews
5.4 The Design Change and System Modification Process
5.5 Supplier Review and Evaluation
5.6 Summary
Questions and Problems
Chapter 6: System Engineering Program Planning
6.1 System Engineering Program Requirements
6.2 System Engineering Management Plan (SEMP)
6.3 Determination of Outsourcing Requirements
6.4 Integration of Design Specialty Plans
6.5 Interfaces with Other Program Activities
6.6 Management Methods/Tools
6.7 Risk Management Plan
6.8 Global Applications/Relationships
6.9 Summary
Questions and Problems
Chapter 7: Organization for System Engineering
7.1 Developing the Organizational Structure
7.2 Customer, Producer, and Supplier Relationships
7.3 Customer Organization and Functions
7.4 Producer Organization and Functions (the Contractor)
7.5 Tailoring the Process
7.6 Supplier Organization and Functions
7.7 Human Resource Requirements
7.8 Summary
Questions and Problems
Chapter 8: System Engineering Program Evaluation
8.1 Evaluation Requirements
8.2 Benchmarking
8.3 Evaluation of the System Engineering Organization
8.4 Program Reporting, Feedback, and Control
8.5 Summary
Questions and Problems
Appendix A: Functional Analysis (Case-Study Examples)
Appendix B: Cost Process and Models
B.1 Life-Cycle Cost Analysis Process
B.2 Cost Models and Objective Functions
Appendix C: Selected Case Studies (Nine Examples)
C.1 Failure Mode, Effects, and Criticality Analysis (FMECA)
C.2 Fault-Tree Analysis (FTA)
C.3 Reliability-Centered Maintenance (RCM)
C.4 Maintenance Task Analysis (MTA)
C.5 Level-of-Repair Analysis (LORA)
C.6 Design Evaluation of Alternatives
C.7 Life-Cycle Cost Analysis (LCCA)
C.8 Organizational Structure's Effect on Development
C.9 Implementation in Hardware vs. Software
Appendix D: Design Review Checklist
Appendix E: Supplier Evaluation Checklist
Appendix F: Selected Bibliography
1. Systems, Systems Analysis, and Systems Engineering
2. Concurrent and Simultaneous Engineering
3. Software and Computer-Aided Systems
4. Reliability Engineering
5. Maintainability Engineering and Maintenance
6. Human Factors, Safety, and Security Engineering
7. Logistics, Supply Chain Management and Supportability
8. Production, Manufacturing, Quality Control, and Assurance
9. Operations Research and Operations Management
10. Engineering Economy and Life-Cycle Cost Analysis
11. Management and Supporting Areas
Index
End User License Agreement
Pages
xi
xii
xiii
xiv
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
Guide
Table of Contents
Begin Reading
List of Illustrations
Chapter 1: Introduction to System Engineering
Figure 1.1 The system.
Figure 1.2 Major elements of a system.
Figure 1.3 System, system elements, and enabling system elements.
Figure 1.4 Multiple systems (system of systems).
Figure 1.5 The current environment.
Figure 1.6 The cost impact due to changes.
Figure 1.7 The imbalance between system cost and effectiveness factors.
Figure 1.8 Total cost visibility.
Figure 1.9 Commitment of life-cycle cost.
Figure 1.10 The system life cycle.
Figure 1.11 Examples of a system life cycles.
Figure 1.12 Top-down/bottom-up system development process.
Figure 1.13 System engineering within the acquisition process.
Figure 1.14 The integration of the hardware, software, and human life cycles.
Figure 1.15 The top-down traceability of requirements.
Figure 1.16 Feedback in the system engineering process.
Figure 1.17 Waterfall model of the software life cycle.
Figure 1.18 The spiral model for the software life cycle.
Figure 1.19 Generic “Vee” developmental model.
Figure 1.20 The systems versus software engineering boundary.
Figure 1.21 System operational and maintenance flow.
Figure 1.22 Logistics activities in the production process.
Figure 1.23 System maintenance and support infrastructure.
Figure 1.24 Functional elements of logistics.
Figure 1.25 Total system value.
Figure 1.26 Management and technology application to the system engineering process.
Figure 1.27 The system acquisition process and major milestones.
Figure 1.28 The basic system requirements, evaluation, and review process.
Chapter 2: The System Engineering Process
Figure 2.1 The system engineering process in the life cycle.
Figure 2.2 System requirements.
Figure 2.3 System operational requirements (geographical distribution).
Figure 2.4 Sample system operational profiles.
Figure 2.5 System operational and maintenance flow.
Figure 2.6 System maintenance concept flow (repair policy).
Figure 2.7 Objectives tree (partial).
Figure 2.8 House of Quality (modified).
Figure 2.9 Family of houses (traceability of requirements).
Figure 2.10 System functional breakdown.
Figure 2.11 Evolutionary development of functional requirements.
Figure 2.12 Functional block diagram (partial).
Figure 2.13 Transition from operational functions to maintenance functions.
Figure 2.14 Maintenance functional flow diagram.
Figure 2.15 Functional flow diagram for a manufacturing system.
Figure 2.16 Identification of resource requirements (i.e., mechanisms).
Figure 2.17 Identification of COTS items from functional analysis.
Figure 2.18 Manufacturing system (critical integration points).
Figure 2.19 Document format for resource requirements.
Figure 2.20 Functional interfaces in a system-of-systems (SOS) configuration.
Figure 2.21 Hierarchy of system components.
Figure 2.22 Abbreviated functional analysis leading to system packaging.
Figure 2.23 Allocation of system requirements.
Figure 2.24 Specification tree (partial).
Figure 2.25 Order of evaluation parameters.
Figure 2.26 Evaluation of alternatives.
Figure 2.27 Example application of models.
Figure 2.28 Example of evaluation results.
Figure 2.29 The integration of design requirements.
Figure 2.30 Design communication network.
Figure 2.31 The data environment.
Figure 2.32 Stages of system evaluation during the life cycle.
Figure 2.33 System evaluation and corrective-action loop.
Figure 2.34 Component material retirement, recycling, and disposal.
Chapter 3: System Design Requirements
Figure 3.1 The major steps of system design and development.
Figure 3.2 Hierarchy of technical specifications.
Figure 3.3 Sample specification tree (partial).
Figure 3.4 System design requirements.
Figure 3.5 Software-hardware steps and interfaces.
Figure 3.6 Traditional reliability exponential function.
Figure 3.7 Typical failure-rate curve relationships.
Figure 3.8. Failure-rate curve with maintenance (software application).
Figure 3.9 Reliability component relationships.
Figure 3.10. Effects of redundancy on reliability in design.
Figure 3.11. Progressive expansion of the reliability block diagram.
Figure 3.12 Expanded reliability block diagram of system.
Figure 3.13 Reliability tasks in the system life cycle.
Figure 3.14 Application of FMECA to a package-handling system.
Figure 3.15 Time relationships.
Figure 3.16 Maintainability distributions.
Figure 3.17 System XYZ unscheduled maintenance actions.
Figure 3.18 Maintainability tasks in the system life cycle.
Figure 3.19 System/decomposition for maintainability analysis and prediction.
Figure 3.20 Example of the relationships between selected reliability and maintainability tools.
Figure 3.21 Human-factors requirements.
Figure 3.22 The processing of information and subsequent human response (simplified).
Figure 3.23 Human factors tasks in the system life cycle.
Figure 3.24 Example of Operational Sequence Diagram (OSD)
Figure 3.25 The application and relationships of selected tools/methods used for human factors in design.
Figure 3.26 Selected technical performance measures for the support infrastructure.
Figure 3.27 Supportability analysis emphasis.
Figure 3.28 Logistics and supportability requirements in the system life cycle.
Figure 3.29 The material reuse/recycling/disposal process.
Figure 3.30 Environmental influences considered in system design and development.
Figure 3.31 System evaluation factors.
Figure 3.32 Sample cost breakdown structure (CBS).
Figure 3.33 Life-cycle cost applications.
Figure 3.34 Life-cycle cost analysis process.
Figure 3.35 Examples of cost-effectiveness analysis applications.
Figure 3.36 Considerations of value/cost in the system life cycle.
Figure 3.37 SOS integration and interoperability requirements.
Figure 3.38 The design process.
Figure 3.39 Problem 8 network.
Figure 3.40 Problem 9 network.
Chapter 4: Engineering Design Methods and Tools
Figure 4.1 System engineering design models and tools.
Figure 4.2 Basic design sequence.
Figure 4.3 Example of project design communications network.
Figure 4.4 Computer-aided engineering (CAE) and related features (example).
Figure 4.5 Application of CAD/CAM/CAS.
Figure 4.6 Major CAD/CAM/CAS interfaces.
Chapter 5: Design Review and Evaluation
Figure 5.1 Design review and evaluation.
Figure 5.2 The relationship between TPMs and responsible design disciplines.
Figure 5.3 Design review and evaluation procedure.
Figure 5.4 System parameter measurement and evaluation at design review (sample).
Note
: The shaded area represents the desired goal.
Figure 5.5 System change control procedure.
Chapter 6: System Engineering Program Planning
Figure 6.1 Management and technology applied to the system engineering process.
Figure 6.2 System engineering planning.
Figure 6.3 The application of system engineering requirements.
Figure 6.4 Consumer, producer, and supplier interfaces.
Figure 6.5 System Engineering Management Plan (SEMP) Outline.
Figure 6.6 System engineering documentation.
Figure 6.7 System engineering organization and interfaces.
Figure 6.8 Partial WBS development.
Figure 6.9 Example summary work breakdown structure (SWBS).
Figure 6.10 CWBS expansion showing system engineering activities.
Figure 6.11 Organizational integration with CWBS.
Figure 6.12 Example specification/documentation tree.
Figure 6.13 Partial bar chart.
Figure 6.14 Sample milestone chart.
Figure 6.15 Major system engineering activities and milestones.
Figure 6.16 Partial program summary network.
Figure 6.17 Sample distribution curves.
Figure 6.18 Top-level network breakdown by program element.
Figure 6.19 Gantt chart for a machine used in production.
Figure 6.20 Project labor projection (man-months).
Figure 6.21 Partial cost account code breakdown structure.
Figure 6.22 Project cost projection.
Figure 6.23 Program cost-schedule reporting.
Figure 6.24 Pareto diagram identifying problem areas.
Figure 6.25 Potential suppliers for system XYZ.
Figure 6.26 Typical structure involving the layering of suppliers.
Figure 6.27 Supplier identification and procurement process.
Figure 6.28 Supplier evaluation checklist.
Figure 6.29 Schedule of proposed contractual payments.
Figure 6.30 Multiple incentive/penalty plans.
Figure 6.31 A sample of supplier project activities.
Figure 6.32 The integration of individual design discipline plans.
Figure 6.33 Interfaces with other planning activities.
Figure 6.34 A mathematical model for risk assessment.
Figure 6.35 Risk analysis and reporting procedure.
Chapter 7: Organization for System Engineering
Figure 7.1 Customer/producer/supplier interfaces.
Figure 7.2 Producer organization (traditional functionally oriented structure).
Figure 7.3 Breakout of engineering organizational activities.
Figure 7.4 Traditional project/product-line organization.
Figure 7.5 Product-line organization with project subunits.
Figure 7.6 Pure matrix organization structure.
Figure 7.7 Functional organization structure showing IPPD/IPTs.
Figure 7.8 Producer organization (combined project-functional structure).
Figure 7.9 Producer (work flow).
Figure 7.10 Functional/project organizational relationships (software-oriented).
Figure 7.11 Major system engineering communication links (producer organization).
Figure 7.12 Classical, four-step systems engineering iterative process.
Figure 7.13 Middle-out or inside-out systems engineering is a popular tailoring process.
Figure 7.14 The middle-out approach connects both the top-down and bottom-up activities in the iterative requirement-function-synthesis process.
Figure 7.15 The middle-out approach uses the inherent iterative nature of system engineering to combine a top-down requirements-based approach and bottom-up details to add new functionality to an existing system.
Figure 7.16 Large-scale supplier organization.
Figure 7.17 Basic matrix representation consisting of three subsystem elements (A, B, C) and two dependencies (between AC and AB).
Chapter 8: System Engineering Program Evaluation
Figure 8.1 System requirements, review and evaluation, and feedback and corrective-action process.
Figure 8.2 Benchmarking process.
Figure 8.3 Benchmarking.
Figure 8.4 Improvement path for system engineering process capability.
Figure 8.5 Focus area capability assessment.
List of Tables
Chapter 2: The System Engineering Process
Table 2.1 Major levels of maintenance.
Table 2.2 Prioritization of technical performance measures (TPMs)
Chapter 3: System Design Requirements
Table 3.1 Example of a system specification (Type A) format
Table 3.2 Reliability engineering program tasks
Table 3.3 Maintainability engineering program tasks
Table 3.4 Human-factors engineering program tasks
Table 3.5 Safety engineering program tasks
Table 3.6 The basic steps in a life-cycle cost analysis
Table 3.7 An abbreviated design review checklist (example)
Chapter 5: Design Review and Evaluation
Table 5.1 Sample design review checklist
Table 5.2 Partial listing of design review questions (packaging and mounting)
Table 5.3 Partial listing of design review questions (software)
Table 5.4 Supplier Evaluation Checklist (Partial)
Chapter 6: System Engineering Program Planning
Table 6.1 System engineering tasks
Table 6.2 Time-line analysis sheet
Table 6.3 Requirements allocation sheet
Table 6.4 List of activities in the program network
Table 6.5 Example of program network calculations
Table 6.6. Proposal evaluation results
Table 6.7 Sample checklist of evaluation criteria for supplier proposals
Table 6.8 Problem 7 data
Chapter 7: Organization for System Engineering
Table 7.1 A functional organization—advantages and disadvantages
Table 7.2 A project/product-line organization—advantages and disadvantages
Table 7.3 A matrix organization—advantages and disadvantages
Table 7.4 Description of major project interface requirements
Table 7.5 Comparing top-down, middle-out, and bottom-up systems engineering processes
Table 7.6 Checklist of leadership characteristics
Table 7.7 Sample position description
Chapter 8: System Engineering Program Evaluation
Table 8.1 SECM Focus areas and categories (EIA/IS-731)
Table 8.2 CMMI process areas and categories
SYSTEM ENGINEERINGMANAGEMENT
FIFTH EDITION
Benjamin S. BlanchardProfessor — EmeritusDepartment of Industrial and Systems EngineeringVirginia Polytechnic Institute and State UniversityBlacksburg, Virginia
John E. BlylerFounding Advisor and Affiliate ProfessorSystems Engineering DepartmentPortland State UniversityPortland, Oregon
This book is printed on acid-free paper.
Copyright © 2016 by John Wiley & Sons, Inc. All rights reserved.
Published by John Wiley & Sons, Inc., Hoboken, New Jersey.
Published simultaneously in Canada.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with the respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor the author shall be liable for damages arising herefrom.
For general information about our other products and services, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.
Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.com. For more information about Wiley products, visit www.wiley.com.
Library of Congress Cataloging-in-Publication Data is available:
ISBN 9781119047827 (Hardcover)
ISBN 9781119225317 (ePDF)
ISBN 9781119225324 (ePub)
Cover Design: Wiley
Cover Images: Blue arrow background © rzymuR/Shutterstock;
Abstract textural background © saicle/shutterstock
Preface
Current trends indicate that, in general, the complexity of systems is increasing, and the challenges associated with bringing new systems into being are greater than ever! Requirements are constantly changing with the introduction of new technologies on a continuing and evolutionary basis; the life cycles of many systems are being extended, while at the same time, the life cycles of individual and specific technologies are becoming shorter; and systems are being viewed more in terms of interoperability requirements and within a system of systems (SOS) context. There is a greater degree of outsourcing and the utilization of suppliers throughout the world, and international competition is increasing in a global environment. Available resources are dwindling worldwide, and many of the systems (products) in use today are not meeting the needs of the customer/user in terms of performance, reliability, supportability, quality, and overall cost-effectiveness.
Given today's environment, there is an ever-increasing need to develop and produce systems that are robust, reliable and of high-quality, supportable, cost-effective from a total-life-cycle perspective and that are responsive to the needs of the customer/user in a satisfactory manner. Further, future systems must be designed with an open-architecture approach in mind in order to facilitate the incorporation of quick configuration changes and new technology insertions, and to be able to respond to system interoperability requirements on an expedited basis.
From past experience, the majority of the problems noted have been the direct result of not applying a tailored and total systems approach, from the beginning, in meeting the desired objectives. That is, the overall top-down requirements for the system in question were not very well defined initially; a bottom-up approach was followed in the system development process; the overall perspective pertaining to meeting the customer's need was relatively short-term; and, in many instances, the philosophy has been to “design-it-now-and-fix-it-later.” In essence, the system design and development process has suffered somewhat from the lack of good early planning and the definition of requirements in a complete and methodical manner, and total-life-cycle considerations have basically been addressed after the fact! This approach has turned out to be quite costly in the long term, particularly in assessing the risks associated with the decision-making processes during the early stages of system development.
The combination of these and related factors has created a critical need—that is, the requirements for developing and producing (or constructing) well-integrated, high-quality, reliable, supportable, and cost-effective systems with complete customer (user) satisfaction in mind. In this highly competitive resource-constrained environment, it is now more important than ever to ensure that the principles and concepts of system engineering are properly implemented, both in the design and development of new systems and/or in the reengineering and modification of existing systems. System requirements must be well defined from the beginning. The system must be viewed in terms of all of its components on a totally integrated basis—to include prime equipment, software, operating personnel, facilities, associated data and information, its associated production and distribution process, and the elements of maintenance and support (and not limited to just those elements utilized to accomplish a specific mission scenario).
Computer-based models have become increasingly robust and useful in this endeavor. A top-down (and bottom-up) integrated approach must complement a middle-out mind-set, with the appropriate allocation of requirements from the system level and down to its various elements. The system must be addressed within a higher-level system of systems (SOS) context, as appropriate, and considering applicable interoperability requirements. Further, the system must be viewed in terms of its entire life cycle; that is, from conceptual through preliminary and detailed design, production and/or construction, system utilization, maintenance and support, and system retirement and material recycling and/or disposal. Decisions made in any one phase of the system life cycle will likely have a significant impact on the activities in the other phases. Thus, a total system's life-cycle approach must be assumed while being tailored to the unique context of each applicable project.
These concepts are not necessarily new or novel. System engineering, in its current context, has been a subject of interest since the late 1950s and early 1960s (and perhaps even earlier). The principles have been successfully applied in a few programs. However, in most instances, although we may believe that we utilize these methods successfully, we really do not implement them very well (if at all). The successful implementation of system engineering requires not only a technical thrust, but a management thrust as well. It is essential that one select the appropriate technologies, utilize the proper analytical tools, and apply the necessary resources to enhance the system engineering process. In addition, the proper organizational environment must be established to allow for the effective implementation of this process and mapping to the final end-product. Thus, it is necessary, first, to understand and believe in the process and, second, to establish the proper management and organizational structure that will allow it to happen! This approach, in turn, provides a cultural challenge for the future.
This text was developed with the preceding objectives in mind. The basic principles and concepts, the need for system engineering and its applications, and introduction to some key terms and definitions are covered in Chapter 1. This leads to a comprehensive presentation of the system engineering process in Chapter 2. This process commences with the identification of a consumer need and extends though the definition of system operational requirements and the maintenance and support concept; the identification and prioritization of technical performance measures (TPMs); a description of system architecture and the elements of the system in functional terms; the allocation of top system-level requirements to the various components of the system in form of input design-to criteria; system synthesis, analysis, and design optimization; test, evaluation, and validation; production and/or construction; distribution, installation, and system utilization in the user's environment; system maintenance and sustaining life-cycle support; and system retirement and material recycling and/or disposal. Key areas of emphasis for system engineering are noted throughout, including the growing influence of hardware-software embedded systems and intellectual property (IP) concerns. A thorough understanding of this process is fundamental in dealing with the overall subject area, and the material in Chapter 2 serves as a baseline for discussion in subsequent chapters.
Given the preceding overview, it is appropriate to delve further into some of the objectives of system engineering. One goal includes the integration of a wide variety of key design support disciplines into the total mainstream system design effort. Chapter 3 provides an introduction to some of these disciplines to include software engineering, reliability, and maintainability engineering, human factors and safety engineering, manufacturing and production, logistics and supportability, disposability, quality, environmental and value/cost engineering. Chapter 4 follows with a discussion pertaining to the application of design methods and tools, utilized in such a manner as to enhance the fulfillment of system engineering objectives. The appropriate application of electronic commerce (EC), information technology (IT), electronic data interchange (EDI), and computer-aided design (CAD) methods allows for “front-end” analysis, leading to a better system definition at an earlier stage in the life cycle. Chapter 5 discusses the checks and balances in the design process, provided through the accomplishment of formal design review, evaluation, feedback and control, and the initiation of changes for corrective action as necessary. An objective of system engineering is to provide a strong engineering leadership role relative to the initial definition of system requirements, the necessary integration of design activities to ensure effective and efficient results, and the follow-on measurement and evaluation functions to ensure that the initially specified requirements have been met.
The next step addresses the management issues pertaining to the application of system engineering requirements to different projects. Chapter 6 leads off with an in-depth discussion of planning and the development of the System Engineering Management Plan (SEMP). System engineering tasks, the development of a work breakdown structure (WBS), program task schedules, and the preparation of cost projections are included. Customer, producer (prime contractor), supplier activities, and interface management are covered. Of particular note is the identification, selection, and contracting with key suppliers. Chapter 7 addresses system engineering in a typical project organizational structure, highlighting the differences between functional, product-line, project, and matrix structures. Also covered are the effects of organizational structure on system and product development. The many interfaces between the customer (consumer), the producer (contractor), and suppliers are discussed, as well as the human resources requirements pertaining to the staffing and management of a system engineering department/group. Having covered the planning, organization, and implementation of a system engineering program, it is essential that one consider a formal evaluation to properly measure and assess the degree to which the organization is performing in accomplishing its overall objectives. Chapter 8 introduces organizational benchmarking and the application of several different models for the purposes of evaluation and feedback (e.g., the SECM and the CMMI models). Dealing with the issues of planning and organization only, without the benefit of evaluation and feedback, constitutes only part of the process and tends to inhibit future growth.
The six appendixes provide excellent supplemental material in support of the various topics covered throughout the eight chapters in the text. Appendix A includes case-study illustrations of the functional analysis; Appendix B describes in detail the steps involved in performing a life-cycle cost analysis (LCCA) and cost models versus objective functions; Appendix C includes nine different case-study examples of various types of design analysis, organizational structure and hardware-software trade-offs; Appendix D includes an extensive design-review checklist; Appendix E contains a supplier evaluation checklist; and Appendix F is an extensive bibliography.
In summary, the intent herein is to describe system engineering in terms of its objectives and applications and the steps in the system engineering process, and to provide a management perspective for the implementation of real-world programs with a strong system engineering thrust. It is believed that this text can be effectively utilized in the academic classroom (at both the undergraduate and graduate levels), in support of a continuing education seminar or workshop, and as an on-the-job reference guide. Questions and problem exercises are included at the end of each chapter to provide the necessary emphasis where required, and an instructor's guide is available for academic classroom support.
Finally, I wish to express my sincere thanks and appreciation to my daughter, Lisa B. McCade (McCade Design), for her continuing assistance in the development, presentation, and processing of material throughout this text. Her support was essential in helping me to complete my portion of the input as presented herein.
Benjamin S. Blanchard
Many years ago, while still working as an engineer in industry, I had the good fortune to meet Ben Blanchard as he helped in the formation of the graduate-level systems engineering program at Portland State University (PSU). Years later, I eagerly accepted his offer to help update this latest (fifth) edition of his time-tested book. While our efforts have not been without challenges, I have thoroughly enjoyed the experience.
I offer special thanks to Dr. Herman Migliore, director of the systems engineering program at PSU. His dedication and leadership skills have helped keep the program going through both good and bad times, in addition to inspiring the professors under his guidance.
I wish to give a thankful nod to Bill Chown, chief information officer of INCOSE and veteran systems engineer from industry, for his help in discerning the most significant real-world systems engineering management challenges for inclusion in this text.
Finally, I thank my family—Rosa, Juan, and Isabel—for their support and understanding when deadlines interrupted the normal workflow of our household. No man is an island and no author does it alone.
John E. Blyler
Chapter 1Introduction to System Engineering
This text deals with system engineering, or the orderly process of bringing a system into being and the subsequent effective and efficient operation and support of that system throughout its projected life cycle. It constitutes an interdisciplinary approach and means for enabling the realization and the follow-on deployment of a successful system.
A system comprises a complex combination of resources (in the form of human beings, materials, equipment, hardware, software, facilities, data, information, services, etc.), integrated in such a manner as to fulfill a specified operational requirement. A system is developed to accomplish a specific function, or a series of functions, with the objective of responding to some identified need. The various elements of a system must be directly tied to and supportive in the accomplishment of some given mission scenario or series of scenarios.
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
