Abstract
For a chemical plant, changes caused by load fluctuation, transition of product markets, revamping of the plant's facilities, et al. are inevitable. Uncontrolled changes caused many accidents or disasters. Thus, management of change (MOC) has been a very important issue in process safety management. In this paper, it is considered that the MOC is divided to two parts: one is an individual change management and the other is a management of them. An individual change management is an instance of engineering over the plant lifecycle (Plant-LCE). A business flow of MOC is expected to be based on a business process model (BPM) of Plant-LCE. An overview for the BPM of Plant-LCE has been proposed. Using an individual change management example, this paper demonstrates that a business flow of the MOC can be described in the overview of the BPM of Plant-LCE. According to the results, importance of sharing information among design, operation and maintenance activities and requirement of supporting system for MOC and Plant-LCE were indicated.
Introduction
Chemical plants are dynamic environments that must constantly adapt to market shifts, raw material variations, and regulatory updates. While adaptation is necessary for survival, uncontrolled changes are a primary driver of industrial accidents. To mitigate these risks, the industry employs Management of Change (MOC) frameworks. However, MOC is frequently treated as an isolated administrative hurdle rather than a core engineering process.
This paper addresses the lack of a unified business process model that integrates technical changes into the broader plant lifecycle. By mapping MOC onto a comprehensive Plant Lifecycle Engineering (Plant-LCE) model, the authors demonstrate how to bridge the information gap between design, operations, and maintenance.
The Plant-LCE Business Process Model
The researchers utilize a pre-existing Business Process Model (BPM) for Plant-LCE, which categorizes approximately 160 distinct business activities. The model distinguishes between "Risk Management of Change" (the technical execution of a specific change) and "Integrated Management of Change" (the high-level oversight of all site changes).
As shown in the model overview, the lifecycle is not a simple linear progression but a complex web of feedback loops. For instance, activity A1 (Manage LCE) coordinates with A3 (Design) and A5 (Produce/Operate), ensuring that operational realities inform design standards and vice versa.
Case Study: Tracing a Feed-Rate Change
To validate the model, the authors performed a "trace" of a real-world event: adjusting the minimum feed rate in a gasoline desulfurization unit within a Fluid Catalytic Cracking (FCC) facility. This process involves multiple stages, from the initial request to design review, test runs, and updating operational standards.
The trace (illustrated above) demonstrates that the complex MOC flow can be entirely mapped within the Plant-LCE BPM. Key steps include:
- A1/A2: Management and planning of the change scope.
- A3: Engineering design review to determine if the hardware can handle the new load.
- A5: Conducting test runs and gathering real-time operational data.
- A7: Updating the "standards" for stable operation based on the test results.
Key Insights and Conclusion
The tracing exercise revealed that design documentation alone is often insufficient for safe change management. Engineers required real-time maintenance history and operational data to conduct successful safety reviews, highlighting a critical need for integrated information systems.
Furthermore, the study identified "implicit" management activities—steps that occur in practice but are not supported by current software. This lack of formal documentation in the Plan-Do-Check-Act (PDCA) cycle can lead to significant knowledge loss. The paper concludes that for MOC to be truly effective, supporting IT systems must be built upon a lifecycle-wide model that facilitates seamless data flow across all plant phases.
Summary updated