Advanced Process Control Is Designed for the Wrong End User
By V. KNOTT, J. HUM, CruxOCM, Calgary, Alberta
(P&GJ) — In modern software development, a fundamental approach known as user-centered design (UCD) places the needs, goals and preferences of users at the center of the entire process. This principle dictates that truly great software is designed for its users.
The UCD process: A three-pillar approach. Implementing UCD involves a structured approach encompassing three key elements:
1. Deep user understanding: This begins with thorough research and consistent engagement to truly grasp user needs
2. Intuitive interface design: The focus here is on creating interfaces that prioritize a seamless and effective user experience
3. Continuous user feedback integration: Throughout the product lifecycle, gathering and incorporating user feedback is essential for ongoing improvement.
The high stakes of ignoring the end user in large enterprises. When large enterprise organizations fail to design software with their end users in mind intentionally, they expose themselves to a range of significant risks. These issues can severely impact various aspects of the business, including:
· Low user adoption: Resulting in poor return on investment and the continued reliance on outdated tools
· Employee frustration: Leading to low morale and higher employee turnover
· Decreased productivity: Slower work processes and an increased likelihood of errors
· Increased costs and complexity: Contributing to higher maintenance demands and accumulating technical debt
· Missed business goals: Failed projects and wasted financial investment
· Lost competitive edge: Hindering innovation and causing the organization to fall behind
· Reputational damage: Resulting in lost customers and a negative brand image.
The case of advanced process control (APC) in heavy industry. The authors’ experience suggests that legacy APC packages often present a unique challenge due to multiple end users, creating friction in value creation and validating the risks outlined above. For large enterprises, neglecting the end user in such critical systems translates directly into tangible business risks, spanning operational inefficiencies and increased costs to significant reputational harm and strategic failures. Therefore, proactively involving all relevant users, with the correct prioritization, throughout the design and implementation of these systems is critical for achieving successful and sustainable outcomes.
Consider those working in refineries or chemical facilities utilizing APC. When was the last time your APC vendor directly engaged with your control room operators? In the authors’ experience, this is a rare occurrence. It is important to distinguish this from the invaluable work of system integrators or in-house teams who diligently implement these packages. This specifically refers to the APC software vendor's product managers. Imagine the insight gained from them observing and interacting with control room operators in their actual work environment, rather than solely engaging with APC engineers.
McKinsey notes that a “low utilization rate (less than 80%) of existing APCs that control key processes” is a common indicator of suboptimal performance in energy and materials industries. Furthermore, another industry case study reports that, after initial commissioning, average APC utilization was above 50%—excluding periods of plant shutdown or exceptional events—indicating that rates above 50% are considered good adoption, with best-in-class sites aiming for 80% or higher. This raises a crucial question: why is such a level of partial utilization deemed acceptable for critical industrial processes that underpin our economy?
Contrast this with our expectations for consumer applications such as Netflix or Amazon. We expect and achieve near-perfect usability and enjoyment, despite paying a relatively small monthly fee (e.g., $10.99). Our standards for these everyday tools seem significantly higher than for the complex industrial systems that are far more vital.
The historical roots of the design disconnect in heavy industry. This is not necessarily a fault of the APC vendors themselves. Instead, it appears to be an unintended consequence of historical design practices within a traditionally slow-evolving industry like oil and gas. The prevalence of the waterfall development method in the 1990s─when much of our operational technology (OT) software was conceived─made it challenging to adapt initial design decisions. Given the intricate nature of configuring APCs for specific industrial assets, it naturally followed that these packages were primarily designed with the APC engineer in mind.
However, this focus is misdirected. While the APC engineer is undoubtedly crucial for the successful deployment of these systems in critical industrial environments, they are not the primary daily users of the software. The control room operator is the one who interacts with the system day in and day out. While the understanding exists that the control room operator is the true end user, the legacy of these systems has prevented a swift redesign to effectively empower them.
Shifting the focus: Empowering the control room operator. The authors’ firmly believe that the control room operator is the correct primary end user for APC applications. Currently, the APC packages the authors’ have encountered are predominantly designed around the APC engineer. While the engineer's role is vital during deployment, recognizing the control room operator as the primary user presents a significant opportunity. There is potential to capture an additional 3%–5% increase in production on top of the 3%–5% gains already being realized by optimizing the user experience for the operator.
Key principles reinforcing the importance of user-centered design. The significance of UCD is underscored by several fundamental principles:
· User involvement: Actively engaging users throughout the entire software development lifecycle, from initial research to final implementation, is paramount. This ensures the software directly addresses real user needs and aligns with their expectations.
· Iterative process: UCD is inherently iterative. A key tenet in the field emphasizes that iteration is critical and customers do not know what they want until they see it. This approach allows for continuous refinement and improvement based on ongoing user feedback.
· Enhanced user experience: By prioritizing the creation of exceptional user experiences, developers can build software that truly resonates with its intended audience, leading to increased user satisfaction, engagement and loyalty.
· Risk reduction: Designing with and for users proactively mitigates project risks by ensuring the software solves genuine problems rather than perceived ones. It also facilitates the early identification and resolution of potential usability issues.
· Quality assurance: UCD places a strong emphasis on rigorous testing. Another established principle highlights that a great developer spends significant time testing for every hour coding. This commitment to quality from the outset is crucial, a concept further reinforced by the idea that the quality of work established early in a project tends to persist throughout.
By consistently adhering to these user-centered principles, software developers can create products that not only meet technical specifications but also deliver genuine value and satisfaction to their end users.
Alignment with broader business objectives. Finally, ensuring that product development aligns with overarching business goals is essential. This involves:
· Translating high-level business strategies into specific and actionable technical requirements
· Making informed trade-offs between competing priorities, such as feature implementation vs. time and cost constraints
· Continuously tracking progress against key business metrics to ensure alignment and measure success.
UCD business case. This case study examines the impact of advanced automation technology on liquid pipeline control room operations. By comparing historical operations with and without the technology, we highlight the benefits of advanced automation in maintaining optimal pressure levels, maximizing profitability, improving efficiency and reducing manual intervention.
In legacy APC applications, the APC engineer designs the plant-wide control system setup, resulting in a unique configuration at each plant or refinery site. Before handover to the control room operators, the advanced control engineer is the end user. While there is tremendous value in bespoke APC roll-outs, combining UCD for the daily user and the control room operator will maximize the experience significantly. The APC engineer can then act as an administrator of the application [or supervisory control and data acquisition (SCADA)/automation engineer].
In the pursuit of maximizing the number of end users (control room operators) who could benefit from individual products, there was a natural delineation of industry verticals for standardized APC installations. Starting in the pipeline sector, APCs are being applied to pipeline systems and facilities and are working to enhance the experience for administrators/deployment folks through self-service tools.
In traditional liquid pipeline control rooms, operators set a static discharge or suction pressure set point for pump stations. This set point remains unchanged until manually adjusted, often resulting in a stair-step pattern of pressure changes (FIG. 1).
Operators monitor pressure transmitters downstream to manage high-pressure points, using the upstream discharge or suction pressure set point to maintain desired pressure levels. However, this manual approach can lead to inefficiencies and suboptimal pressure management, resulting in underutilization of the asset, not maximizing profitability.
· Manual adjustments: Operators must manually adjust the discharge/suction pressure set point, which can vary by 10 psi, 20 psi or more, based on operational needs
· Limited focus: Operators handle multiple tasks and responsibilities, making it difficult to consistently monitor and adjust pressure levels to maintain consistent maximum flow rates
· Human error: The need for continuous monitoring and adjustments increases the risk of human error, especially in hydraulically challenging pipeline operations (FIGS. 2a and 2b).
Over time, the difference between the pressure limit at the ever-moving bottleneck location and the minimum pressure that the control room operator can maintain on the system is the volume, or profit, left on the table for liquid pipeline operators.
The difference between the limit that the technology a,b can maintain and what the control room operator can maintain is the additional utilization or volumetric throughput that can be captured and sold by liquid pipeline organizations (FIGS. 4a−4d). TABLE 1 shows the benefit summary realized in production by the authors’ company’s customers.
LESSONS LEARNED
With the rollout and adoption of any new technology, there are lessons learned to help others succeed in their journey to human-centric industrial autonomy for pipeline control rooms:
· Enhanced operational efficiency: Automation significantly improves operational efficiency by minimizing manual tasks and allowing operators to focus on critical responsibilities
· Improved safety and reduced human error: Automation reduces the risk of human error and enhances safety by ensuring consistent and accurate pressure management
· Better visibility and decision-making: Automation improves visibility and decision-making for managers and executives through real-time data gathering and analysis
· Increased profitability: Automation leads to cost savings and increased profitability by ensuring that software solutions consistently deliver value
· Future-proofing operations: Automation ensures that control room operations remain adaptable and resilient, maintaining a competitive edge
· Reduction in manual adjustments: Automation maintains pressure levels close to the maximum limit, reducing the need for frequent manual adjustments
· Enhanced operator focus: Automation reduces the burden on operators, allowing them to manage the entire pipeline more effectively and focus on other critical tasks.
These lessons have been incorporated into the rollout and adoption process with pipeline control room customers.
Regulatory considerations. The Pipeline and Hazardous Materials Safety Administration (PHMSA) in North America regulates the safe and secure movement of hazardous materials, including pipelines. Key regulatory guidelines include, but are not limited to, control room management, management of change and point-to-point check.
Takeaway. This article argues for the critical importance of UCD in heavy industrial software development, particularly within large enterprises and specifically concerning APC systems. By prioritizing user needs throughout the design process, providers of OT software can mitigate significant risks such as low adoption, decreased productivity and reputational damage, ultimately leading to software that drives tangible value and achieves sustainable success for their oil and gas clients.
The article highlights a disconnect in the design of current APC packages, which are often centered around the APC engineer rather than the control room operator, the true end-user. This misalignment results in suboptimal utilization rates, as noted by McKinsey, and contrasts sharply with the usability expectations of consumer-grade software. This design flaw, rooted in historical development practices, prevents APC systems from reaching their full potential─advancing human-centered industrial autonomy.
By embracing the key principles of UCD, including user involvement, iterative processes, enhanced user experience, risk reduction and quality assurance, and realigning the focus of APC design towards the control room operator, there is a significant opportunity to unlock further production gains and realize the full promise of these critical industrial automation tools.
NOTES
a CruxOCM’s pipeBOT
b CruxOCM’s maxOPT
About the authors
VICKI KNOTT is the CEO and Co-Founder of CruxOCM, a company pioneering human-centered industrial autonomy that transforms how critical energy infrastructure operates. As a chemical engineer who trained as a control room operator, Knott brings rare frontline operational experience to enterprise technology leadership, understanding both the strategic imperatives and day-to-day realities driving industrial transformation. Under her leadership, CruxOCM has developed AI-driven automation solutions that deliver measurable impact: dramatically increasing revenue, reducing operator workload and enhancing safety across pipeline operations. This combination of operational excellence and business results has attracted backing from M12, Microsoft's Venture Fund.
JAY HUM is a product leader, founder and investor who has spent more than two decades driving innovation and turning big ideas into products people love to use. Currently, he serves as the Chief Product Officer at CruxOCM, where he’s simplifying operations and driving profitability with human-centered industrial autonomy. Hun has shipped breakthrough products that delight users, scaled a platform to support billions of data points, and led cross-functional teams that transform industries. He’s worked with pre-revenue startups and Fortune 100 enterprises, including CoreLogic, Facebook/Meta, Ford, NFL, Phillips 66 and Samsung.