Problem management is not recognized as a system engineering process. Unlike risk management where risks could impact a project at some future date, problems impact the project now. Therefore, a robust problem management process should be established (similar to the risk management process described in chapter five of the INCOSE handbook) , early in a project's formulation. The process should be continuous throughout all phases of the project life cycle and should be included as a part of the project System Engineering Management Plan. The process should at a minimum address: problem identification, problem assessment, problem root cause investigation, and problem corrective action planning and reporting. It should also include a roll-up of all current problems, problem closure, and the development of a strong interface with the project's knowledge management system.
This paper proposes a problem management systems engineering framework, based on the foundations of risk, opportunity management and knowledge management, which could be used by corporations, government agencies, and programs to establish a robust problem management process for use on their projects.
|Advisor:||Sarkani, Shahram, Mazzuchi, Thomas Andrew|
|Commitee:||Eveleigh, Timothy, Mazzuchi, Thomas A., Murphree, Lile, Sarkani, Shahram, Stankosky, Michael|
|School:||The George Washington University|
|Department:||Engineering Mgt and Systems Engineering|
|School Location:||United States -- District of Columbia|
|Source:||DAI-B 73/07(E), Dissertation Abstracts International|
|Subjects:||Management, Systems science, Operations research|
|Keywords:||Knowledge, Problem corrective actions, Problem management, Project life cycle, Risk|
Copyright in each Dissertation and Thesis is retained by the author. All Rights Reserved
The supplemental file or files you are about to download were provided to ProQuest by the author as part of a
dissertation or thesis. The supplemental files are provided "AS IS" without warranty. ProQuest is not responsible for the
content, format or impact on the supplemental file(s) on our system. in some cases, the file type may be unknown or
may be a .exe file. We recommend caution as you open such files.
Copyright of the original materials contained in the supplemental file is retained by the author and your access to the
supplemental files is subject to the ProQuest Terms and Conditions of use.
Depending on the size of the file(s) you are downloading, the system may take some time to download them. Please be