Cost-Effectiveness Analysis
A Systems Engineering Perspective
Howard Eisner
- 102 pages
- English
- ePUB (mobile friendly)
- Available on iOS & Android
Cost-Effectiveness Analysis
A Systems Engineering Perspective
Howard Eisner
About This Book
This book provides an overview of cost-effectiveness analysis, which is a well-known and intuitive method for defining and choosing among a set of alternatives. This book relates cost-effectiveness analysis to systems engineering to solve everyday problems at home and the office. It can also be used in technical processes, system design, and project management.
Cost-Effectiveness Analysis: A Systems Engineering Perspective starts with providing an overview and background of cost-effectiveness analysis and how it's used. It then goes on to discuss cost-effectiveness concerning systems engineering and links its use to resolving military issues and problems. The book comes to an end with exploring the usage related to systems architecting, re-engineering office systems, and comparing its use to everyday life decision-making scenarios.
Targeted market includes general engineers, systems engineers, process engineers, project management, scientists, technologists, mathematicians, and lawyers.
Frequently asked questions
Information
1 WSEIAC, the Whiz Kids, and RAND
- Hitch became the president of the University of California, Berkeley.
- Enthoven was appointed Assistant Secretary of Defense for Systems Analysis (SA).
- The DoD published their WSEIAC report [2], a definitive treatise on how the DoD would deal with weapon systems and their effectiveness. The key summary report defined weapon system effectiveness as the product of A, D, and C, where:
- A = Availability
- D = Dependability
- C = Capability
The WSEIAC Analysis and Report
- The principal findings, conclusions, and recommendations of the five WSEIAC Task Groups
- A 15-step procedure for cost-effectiveness assurance
- A section of the integrated summary that contains abstracts and summaries of each of the ten reports submitted by the five Task Groups
- Appendix I, which has a more detailed treatment of each of the ten report tasks
- Appendix II, which contains an application of the methodology, and
- Appendix III, which is a glossary of cost and effectiveness terms
Effectiveness is defined as the product of Availability, Dependability and Capability, whereâAvailability is a measure of the condition of the system, at the start of a mission, when the mission is called for at an unknown (random) point in time,ââDependability is a measure of the system condition during the performance a the mission, given that it is available at the start of the mission, andââCapability is a measure of the results of the mission, given the condition of the system during the mission (dependability)ââCost-effectiveness is the value received (effectiveness) for the resources expended (cost)â
a minimum acceptable requirement of a recent SOR is given piecemeal in terms of separate probabilities and performance limits without obvious relation to one another. When combined into an overall effectiveness number (using WSEIAC notions) these requirements suggest that if this system works less than 4 times out of 100, it is still acceptable. [2, page 5]
- Review present procedures for effectiveness requirements.
- Recommend a method for determining system effectiveness requirements that are mission responsive.
- Review existing documentation of system effectiveness.
- Recommend methods and procedures for measurement and prediction of system effectiveness in all phases of a systemâs life.
- Review current Air Force data collection and reporting systems.
- Recommend uniform procedures for periodic status reporting to assist all management levels.
- Develop a set of basic instructions and procedures for conducting analysis for system optimization, considering:
- Effectiveness
- Cost
- Program time scale
- Refine current cost-effectiveness analysis techniques
- Develop a management system designed to absorb and apply systems effectiveness experience retention.
Technical Reports
- AFSC â TR â 65 â 1: Final Report of Task Group 1 âRequirements â Methodologyâ
- AFSC â TR â 65 â 2: Final Report of Task Group II: âPrediction â Measurementâ
- AFSC â TR â 65 â 3: Final Report of Task Group III: âData Collection and Management Reportsâ
- AfSC â TR â 65 - 4: Final Report of Task Group IV: âCost-Effectiveness Optimizationâ
- AFSC â TR â 65 â 5: Final Report of Task Group V: âManagement Systemsâ
Volume I â General SummaryVolume II â Integrated Summary
WSEIAC Recommendations
- The basic analytical framework and effectiveness concepts should be accepted as an initial starting base.
- The proposed effectiveness notions and evaluation techniques need to be validated on one or more Air Force systems. Changes in the techniques should be based upon the results of that validation. Contractual commitment needs to be, likewise, the validation results.
- Procedures for test and demonstration of effectiveness, similar to those for reliability, should be initiated. (Another good starting point.)
- The matter of âconfidenceâ in the effectiveness results need to be further studied.
- Specific impacts on incentive fee contracts need to be explored as soon as possible.
- The preparation and adoption of standard terminology for systems effectiveness needs to be accomplished as soon as possible.
- More attention needs to be paid to data acquisition (e.g., maintenance data).
- The fine art of parameter estimation needs further definition and standardization.
More about the Whiz Kids
he was a prize specimen of a remarkable breed in U.S. Industry â the trained specialist in the science of business management who is also a generalist moving easily from one technical area to another.