Introduction | Control System Migrations | Part 7 | Cutover, Commissioning, and the Final Push August 2025 — by Tom McGreevy, PE, PMP, CFSE — Welcome to part 7 of our Control Systems Migration blog series . In this installment, we’ll be covering the cutover phase, which is where it all comes together. This is the point where months or even years of preparation culminate in the actual replacement of the old control system with the new. It’s a high-stakes, high-pressure moment, and one where success is determined by how well you’ve planned, documented, and executed. The term “ cutover ” covers everything from physical equipment replacement to software commissioning and testing. It’s not just about wiring panels; it’s about making sure every step, from demo drawings to site acceptance testing, is aligned and accounted for. Do I Need to Begin with a Full System Backup? The short answer: Absolutely . Before any equipment is touched, every element of the current system must be backed up. That includes program logic, Human Machine Interface  (HMI) configurations, and current “ as-found ” drawings. Photos of panel internals and field installations can also be valuable, not just as references in case you need to troubleshoot, but as a last-resort rollback option if something unexpected forces you to pause or reset the transition. In a rip-and-replace scenario, rolling back may not be feasible, but having a complete picture of the system you’re decommissioning can still help solve problems when they arise during construction or testing. What Should I Include in a Cutover Execution Plan? Your cutover execution plan should be specific and clearly documented. It must describe step by step how the cutover will proceed and clarify who’s responsible for each task. It should also detail what tools, drawings, resources, and timing are required for each stage. This plan should leave no room for ambiguity. What’s happening to each wire? Which devices stay, which go? Are there mystery components, the purpose and disposition of which is not 100% understood? Those need to be resolved before the first wire is lifted, or if not, at least addressed as part of your early cutover activities. Most importantly, there is significant value in making sure this plan is in the hands of the right people. Having a perfectly crafted set of work packages and drawings means nothing if the team in the field doesn’t have them. This kind of breakdown in communication is surprisingly common, but fortunately, it is also completely avoidable. What Pre-Shutdown Work Should Be Done Before a Control System Migration? Any construction or staging work that can be done before the shutdown should already be complete. This includes routing and tagging cables, installing panels where possible, staging materials, and setting up temporary facilities like backup power in accordance with OSHA safety guidelines . If it can be done early, do it early. This will reduce the pressure during actual outage windows and create space to address the unexpected. The Details Matter — Down to the Wire One of the most critical aspects of a successful cutover is understanding where every single  wire goes and what it does. If wires aren’t clearly labeled, properly documented, or tied to an understood function, you risk losing control over the tactical situation very quickly. Similarly, you must know the purpose and disposition of every field device. Is it being reused, replaced, or removed? Has it been tagged and labeled correctly? These details feed directly into the accuracy of your demo drawings and revised documentation, which in turn drives construction confidence and efficiency. Even the basics, like wire sizes, must be documented. Tasks like these may seem like a small detail, but mismatched or unlabeled wire sizes can lead to serious setbacks during installation. Construction Documents vs. Loop Sheets It’s also worth noting that loop sheets, while useful for function testing and configuration, are not  construction documents. Teams need full demo drawings, updated termination diagrams, and accurate cable schedules to perform field work efficiently. Relying on loop sheets for installation will almost certainly slow the progress and may invite error and confusion. Mechanical Completion: Knowing When You’re Ready Before applying power to the new system, everyone involved must agree on what defines mechanical completion. At this point, all installation work should be finished, verified, and supported by construction assurance documentation. It’s a formal milestone that marks the transition from building the system to bringing it to life. Assurance activities in support of demonstration of Mechanical Completion include visual inspections, comparison to approved drawings, wiring continuity checks, and proper ground measurements (of both safety and signal ground). Site Acceptance Testing, Commissioning, and Function Checks Once mechanically complete, the system undergoes site acceptance testing  (SAT) the first time it’s powered on in its new environment. This phase confirms that nothing was damaged during shipping or installation, and that devices are behaving as expected at a basic level. From there, teams move into loop checks, verifying that inputs and outputs are correctly wired and responsive. These checks ensure that transmitters, control valves , and I/O points communicate properly with the system and that grounding is correct. This may also include bumping of motors for those motors controlled by the system, and verification of good communications to any and all third-party devices. It is critical that EVERY I/O device that had its wiring touched during the cutover be checked, to give high confidence in wiring integrity and to enable efficient functional testing. Finally, functional testing begins. Depending on the system, this could include “ water runs ,” simulation of Safety Instrumented Functions  (SIFs), and validation of interlocks . Every step should follow a documented test plan, not just for consistency, but to ensure accountability and traceability. The temptation to rush through these tests can be strong, especially during time-constrained shutdowns. But skipping steps here can have serious consequences, ranging from costly mistakes to safety hazards and legal liabilities. The Takeaway The cutover process is considered the most visible and intense phase of a control system migration. It’s where all the planning, documentation, and collaboration either pay off or fall short. When executed well, the cutover is a moment of accomplishment, the grand finale of your migration efforts. But without discipline, rigor, and proper preparation, it can quickly become chaotic, stressful, and, worst of all, dangerous to equipment and people This phase rewards diligence, not improvisation. Success lies in backing up thoroughly, planning clearly, assessing and addressing risk, labeling accurately, executing deliberately, and testing without compromise. If all of that is in place, your team can move forward with confidence, and your process can start up on a solid, resilient foundation .

Introduction | When “Just Fix It” Isn’t That Simple July 2025 — by Emily Henry, PE (SC) , CFSE, Functional Safety Group Manager — This blog is the second installment in our PHA Recommendation Playbook series , which is intended to help Process Safety, EHS, and facility managers overcome the common challenges they face when trying to close Process Hazard Analysis recommendations. If you missed Part 1, we explored how staffing and budget limitations create obstacles  that can stall even the most straightforward resolutions. In this article, we’re focusing on a challenge that doesn’t always get the attention it deserves: technical complexity . While some recommendations from a PHA might seem routine at first glance, others involve engineering considerations, system interdependencies, or implementation feasibility that turn them into long-haul capital project efforts. These complications can extend gap closure timelines, inflate costs, and even introduce new risks if not addressed with requisite knowledge and intentionality. Technical Challenges in PHA Recommendations | What Makes Them So Complex? Technical complexity refers to the engineering depth, system interdependencies, or feasibility issues that complicate the implementation of PHA recommendations . In industrial environments, this might include design changes that require coordination between multiple engineering disciplines, recommendations that call for feasibility studies, or changes to safety instrumented systems that necessitate revalidation. Sometimes, the complexity lies in hidden system dependencies, meaning that fixing one issue inadvertently introduces another. Compatibility concerns also surface, particularly when legacy systems aren’t designed to accommodate newer technology. Complicating matters further, many of these challenges aren’t fully apparent during the PHA session itself. A recommendation may seem simple on the surface — “install a relief valve”  or “update control logic” — but as the team attempts to move forward with recommendation implementation, the depth of technical complexity becomes clear. The Compliance Cost of Complexity | What Are the Risks of Unresolved PHA Recommendations? Delays caused by technical complexity come with consequences. Regulatory expectations require timely closure of PHA recommendations or, at the very least, well-documented justifications for delays. Facilities that fail to address these recommendations in a structured way may face unexpected audit findings, regulatory scrutiny, or even fines. Beyond compliance, unresolved technical items can increase safety risks. A partially implemented fix or an unaddressed hazard can lead to new vulnerabilities or process weaknesses. From an operational standpoint, unresolved recommendations may lead to unplanned downtime, deferred maintenance, or extended outage windows. Over time, these delays can cause friction between departments and erode trust in the process. How Should You Navigate Complex Technical PHA Recommendations Internally? Handling complex recommendations starts with engaging the right people early. Engineering, operations, maintenance, and safety teams must be aligned on what’s practical, what’s required, and what constraints exist. Cross-functional collaboration is essential for identifying implementation barriers before a plan is set in motion. Conducting feasibility reviews internally can reveal potential problems with space, access, process compatibility, or cost. These reviews don’t have to be overly formal, but they should be consistent and thorough enough to inform the feasibility of implementation of the recommendation at a high level. Documenting known interdependencies also helps ensure one recommendation doesn’t inadvertently conflict with another. Instead of treating each recommendation as a siloed task, consider how they fit into the broader operational strategy. Iterative planning, where adjustments are made as new information surfaces, can help prevent bottlenecks and avoid over-committing resources. When Does Technical Complexity Require External Expertise? There are times when a PHA recommendation goes beyond internal capacity, whether due to staffing limitations or the depth of technical expertise required. Yet not all third-party support is created equal. Some firms deliver a report and walk away, leaving your team with a list of action items and little else in the form of background education. Working with an experienced third-party can change the dynamic. The right partner doesn’t just identify risks; they help you engineer prioritized solutions that are feasible, effective, and aligned with your facility’s operations. A third-party familiar with system interdependencies can offer practical mitigation strategies that don’t introduce new problems elsewhere. Execution also matters. A partner that provides project management oversight can track progress, maintain accountability, and deliver documentation that supports audit defensibility. By helping prioritize what matters most and sequencing efforts strategically, an experienced partner can support smarter capital planning and more efficient implementation. Collaboration with a third-party should never feel like you’re relinquishing control. Instead, it should feel like gaining clarity with a clear line of sight from risk to resolution, with results your team can stand behind. What Are Proactive Strategies to Minimize Technical Implementation Risks? Managing technical complexity isn’t only about reacting once a challenge appears. Many of the difficulties associated with implementation can be mitigated through proactive planning. Three core proactive strategies include: Integrating front-end engineering and risk assessment into your safety processes. This helps identify potentially complex recommendations earlier in the lifecycle. Flagging technically intensive items during the PHA itself or revalidation workshops, so that additional analysis can be scoped and scheduled. Allocating budget and time for follow-up studies, such as feasibility analyses, LOPA updates, or HAZOP reviews, when recommendations involve significant system changes. Maintaining clear documentation is also essential. It not only aids internal decision-making but strengthens your position during audits or external reviews. Finally, it helps to reframe these efforts not just as compliance tasks but as opportunities to improve long-term reliability and operational resilience of your facility. From Risk to Resilience | Technical PHA Resolution Isn’t Just a Fix—It’s a Foundation Facilities that manage technical complexity well don’t just avoid problems, they build stronger, safer operations. When engineering, safety, and operations teams work together to resolve complex PHA recommendations, the resulting improvements often go beyond the immediate fix. Systems become more reliable. Cross-team collaboration improves. Equipment failures and unplanned outages decrease. Moreover, facilities gain stronger footing in the face of audits or regulatory reviews. Well-documented resolutions with traceability to risk assessments show diligence and intent, both of which matter when follow-up questions are asked. When resolutions are handled with care, the outcome shouldn’t feel like a temporary workaround. It should feel like progress. The Takeaway | Moving from Technical Complexity to Technical Confidence Technical complexity is one of the more nuanced challenges in PHA recommendation resolution. It’s also one of the easiest to underestimate. The surface-level simplicity of a recommendation often belies the engineering coordination, feasibility analysis, and systems thinking required to see it through. By planning ahead, involving the right teams, and knowing when to seek experienced, third-party expertise , your facility can navigate even the most intricate recommendations without losing momentum. And when you do choose to bring in third-party support, working with a team that understands engineering, project delivery, and compliance can be the difference between checking a box and building something truly defensible. At its best, technical resolution doesn’t just close a gap, it builds a stronger foundation. From risk to resilience, the path is clearer when the process is collaborative, strategic, and informed.

Introduction | Compliance in the Face of Limited Teams and Tight Funds May 2025 — by Emily Henry, PE(SC), CFSE, Functional Safety Group Manager — Welcome to the first entry in our multipart blog series, designed as a guide for process safety, EHS, and facility managers who are in the process of resolving PHA recommendations. Each installment will address one of the most common practical, technical, or organizational challenges faced when closing the recommendation gaps of a PHA study. In part one, we will discuss one of the most frequent hurdles: resource constraints, particularly staff and budget limitations . PHA Primer A Process Hazard Analysis (PHA) serves as a mechanism for identifying and mitigating risks in industrial environments. OSHA mandates both initial PHAs and regular revalidations  for facilities that handle hazardous chemicals or operate under process safety management (PSM) regulations. The recommendations that stem from these analyses are not optional — they are necessary actions required to close safety gaps and prevent incidents. Yet, the journey from recommendation to resolution is rarely straightforward. Among the most common early challenges are staff shortages and budget limitations, both of which can stall progress and jeopardize compliance. Staff and Budget Limitations: A Common Roadblock in Resolving PHA Recommendations Resource constraints, particularly in the form of personnel and budgetary limitations, present persistent barriers to the stewardship and closure of PHA recommendations. These constraints are rarely isolated issues. Instead, they tend to surface across departments and project phases, especially when expertise is scarce, or budgets are tight. In the industrial and manufacturing sectors, managers are often asked to do more with less, juggling compliance deadlines with daily operations. Delays in addressing PHA recommendations can result in increased exposure to safety or operational risks, missed regulatory deadlines, and a higher likelihood of enforcement actions. The cost is more than administrative; it can reverberate throughout the organization, increasing the potential for incidents and ultimately impacting the bottom line. Resolving PHA Recommendations with Limited Staff and Technical Expertise Staffing limitations can significantly hamper the PHA resolution process, especially when specialized technical skills are required. For facilities with high-severity hazards, recommendations often involve complex engineering assessments, equipment modifications, or the implementation of advanced safety protocols. These activities call for experienced professionals, typically engineers, safety specialists, or technicians with niche expertise. When internal teams lack the required personnel or technical depth, recommendation resolution will certainly lag. The risks are not hypothetical; delayed action can mean extended periods where known hazards lack the necessary layers of protection, increasing the possibility of an unmitigated hazard consequence occurring. Over time, this not only erodes safety culture , but can put the entire operation under scrutiny from regulators, insurers, or even the public. Dealing with Budgetary Restriction Headaches for PHA Recommendations Budget limitations can be equally as challenging as personnel constraints. Many PHA recommendations require upgrades or modifications to equipment or investments in new safety systems. When budgets are stretched, it’s tempting to defer or downsize these actions. However, the potential consequences of postponement are rarely minimal. Financially, the long-term risks can outweigh any short-term savings. Delaying investments in safety may lead to regulatory fines, incident-related expenses , or increased insurance premiums. Facilities that consistently operate with unresolved risks may also face reputational harm if non-compliance becomes public or results in an adverse event. Additionally, legal risks escalate if known issues are a contributing factor in an incident. Navigating Resource Constraints Internally Effective management of resource constraints begins with prioritization. Not all PHA recommendations carry the same weight or urgency. By ranking actions based on risk severity and regulatory impact, managers can ensure that the most critical items receive attention first. Tying implementation timelines to budget cycles also helps align resources with compliance needs. Another best practice involves communicating risk in clear, compelling terms to decision-makers. Presenting the business case for timely resolution — not only as a regulatory obligation but as a risk mitigation strategy  — can help secure funding and staffing. In short, thorough planning and a clear understanding of the resources required can empower managers to justify funding requests and advocate for staff allocation in a focused, strategic way. The Support Advantage: Leveraging Third-Party Partners for PHA Resolution While many facilities strive to resolve recommendations internally, there are times when third-party expertise can be invaluable. Not all PHA providers offer the same level of post-study support; many simply deliver a report and move on, leaving your team with a daunting list to decipher and prioritize. Partnering with an experienced provider can offer several benefits . External experts often bring specialized credentials and the ability to mobilize skilled personnel quickly, ensuring that urgent PHA recommendations do not drag on unresolved. A knowledgeable partner can also help optimize budgets by identifying targeted, cost-effective options — often with strategic solutions that can resolve multiple recommendations with one move .   Furthermore, partnering with an experienced company can support your team in developing practical resolution plans and provide tools , resources, and expert guidance tailored to your facility’s needs. This approach not only reduces the internal burden but positions you as a champion of compliance and safety within your organization — saving time, money, and stress. Planning Ahead: Proactive Strategies to Mitigate Staff and Budget Limitations Proactive resource planning can make a significant difference. Integrating anticipated PHA recommendations into annual budgets and resource allocation processes can help ensure that funds and personnel are available when needed. Establishing clear internal procedures for escalating and addressing urgent recommendations helps prevent bottlenecks. Investing in skill development and cross-training internal staff broadens your facility’s capabilities. These measures collectively strengthen the ability to resolve recommendations in a timely, efficient manner. Lean Teams, Big Gains: The Benefits of Overcoming Staff and Budget Barriers Successfully managing staff and budget limitations pays dividends beyond OSHA compliance. Facilities that close PHA recommendations efficiently will see a reduced regulatory risk, enhanced operational resilience, and ultimately, fewer incidents. Cost savings accrue through avoided penalties and proactive safety management, while the organization’s reputation is bolstered by a demonstrated commitment to safety and continuous improvement. The Takeaway | Limited Resources, Unlimited Potential Staff and budget limitations do not have to be the challenge that prevents your facility’s PHA recommendations from being resolved. With strategic planning, clear prioritization, and — when needed  — the support of a capable external partner, facilities can bridge the gap between recommendations and resolution. For those facing persistent resource challenges, now is the time to review your internal capacity and consider the value of experienced collaboration. By doing so, you not only safeguard compliance and safety but also lead your organization with resilience and integrity, turning every challenge into an opportunity for growth. Be sure to keep an eye out for the next article in this series, where we will discuss strategies to prevent technical complexities from slowing your PHA recommendation resolution progress. In the meantime, check out this article on the five facets of an efficient process hazard analysis .

Join some of the aeSolutions team as we hold a panel discussion on the New Engineering Business, held as part of Engineers Week 2021. Engineers Week is “dedicated to ensuring a diverse and well-educated future engineering workforce by increasing understanding of and interest in engineering and technology careers.” Moderated by Ben Burris & Emily Henry. Founded by National Society of Professional Engineers in 1951, Engineers Week is dedicated to ensuring a diverse and well-educated future engineering workforce by increasing understanding of and interest in engineering and technology careers. Learn more from the NSPE At aeSolutions, we know that our success is a result of having talented, dedicated and passionate team members driving our projects. If working for a company that takes on complex challenges in nearly every capacity interests you, we would love to talk to you. We are proud to have over 50 certified engineers on staff.

May 2025 - Check out our contributed content in Processing Magazine . This article, written by Tom McGreevy, explains five tips to include in your conversation with leadership to secure their support for control system migration projects. Click here to read the full article in Processing Magazine Written by Tom McGreevy, PE, PMP, CFSE Senior Project Manager at aeSolutions . Read the full article on Processing Magazine here: The Need for a Control System Migration: Building the Case to Upper Management

May 2025 - Check out our coverage in Chemical Processing's "How They Made It Work" series that features our FGS 1300 Fire and Gas alarm controller . This article dives into how the FGS 1300 was implemented in a pharmaceutical manufacturing facility's boiler house as a natural gas leak-detection and isolation system, based on a PHA recommendation. Click here to read the full article in Chemical Processing Written by Warren Johnson, PE, PMP, Senior Project Manager at aeSolutions . Read the full article here: How They Made It Work: aeSolutions' FGS 1300 Fire and Gas Alarm Controller

Introduction | Process Hazard Analysis Revalidation April 2025 — by Carolyn Bott, Process Safety Group Manager — In the world of industrial operations, hazards are a given — but unmanaged hazards are a risk no facility can afford. A well-executed Process Hazard Analysis (PHA) is a vital safeguard, helping teams identify potential risks and define the controls needed to mitigate them. But a PHA isn’t a one-time event. As facilities and operations evolve, so must the analysis. That’s where a PHA Revalidation comes in. What is a PHA Revalidation? A PHA revalidation is a systematic update of an existing PHA study to ensure that it accurately reflects current operations, risks, and safeguards. Mandated under OSHA’s Process Safety Management (PSM) standard  (29 CFR 1910.119), PHA revalidations are required at least once every five years. This ensures that facilities consistently assess whether existing safeguards and Independent Protection Layers  (IPLs) are still appropriate and effective. Unlike a first-time PHA, a revalidation starts with reviewing the previous study. The team evaluates modifications — be it process design, control systems, staffing, procedures, or incident history — and determines whether those changes introduce new risks or warrant updates to the previous Process Hazard Analysis study. It should be noted that in some cases, a facility may determine that the existing PHA is no longer a reliable baseline — perhaps because of major modifications, process redesign, or poor quality in the original study. In these situations, a full PHA redo may be the better option. Methodologies Commonly Used in PHA Revalidations Several risk assessment methodologies are used during PHA revalidations, depending on process complexity and organizational preference. These include: HAZOP (Hazard and Operability Study) : A systematic, guideword-based approach for continuous and batch processes LOPA (Layers of Protection Analysis) : A method for evaluating the effectiveness of protection layers in reducing the frequency or consequence severity of hazardous events What-If and Checklist Analyses : Useful for simpler systems or as supplementary tools HAZID (Hazard Identification Study) : Often applied in the early design phase or as a high-level review FMEA (Failure Modes and Effects Analysis) : Focuses on component-level failure scenarios Bowtie Analysis : Visual mapping of causal pathways and safeguards for major hazards These methodologies are not mutually exclusive — they are often used in combination. The chosen methodology(s) should match the process and risk profile. Regulatory Requirements and OSHA Expectations for PHA Revalidations According to OSHA, a PHA must be revalidated at least every five years to ensure it remains consistent with the current process. The revalidation must be conducted by a team with expertise in engineering, operations, and hazard analysis methodology. The team should evaluate changes in equipment, procedures, and materials; verify that recommendations from previous PHAs have been resolved; and confirm that documentation and drawings (such as P&IDs) are current. OSHA further clarifies that a PHA revalidation doesn’t need to start from scratch. It can build upon the previous PHA, provided the review is thorough and documented. Failing to properly revalidate — whether by missing the five-year deadline or conducting an insufficient review — can lead to citations and increased risk exposure. Should I Revalidate Sooner Than Five Years? While the five-year cycle is the regulatory minimum, some facilities choose or need to revalidate more frequently. Situations that may warrant earlier review include: -          Significant process changes such as new equipment, revised control strategies, or major throughput adjustments -          Facility expansions or new unit operations -          Introduction of new chemicals or process conditions -          Recurring incidents or near misses suggesting underlying hazards were missed -          Internal audits that identify PHA gaps or non-compliance -          Evolving industry standards or new safety guidance that impact existing risk assessments In such cases, updating the PHA before the five-year mark can strengthen safety performance and demonstrate due diligence to regulators and insurers. Five Common Challenges in PHA Revalidations Executing a quality PHA revalidation takes planning, expertise, and cross-functional engagement. Below, we describe five common challenges that facilities face when conducting a Process Hazard Analysis Revalidation. 1.      Inadequate Documentation and Information Management  A revalidation is only as good as the information available. If the previous PHA scenarios were poorly documented or if process safety information (P&IDs, chemistries, etc.) hasn’t been kept current, the team will struggle. Without complete, up-to-date data on what has changed since the last PHA, important scenarios might be overlooked, or the team may waste time reconfirming basic facts. 2.     Loss of Key Knowledge and Stakeholder Engagement It isn’t uncommon to find that the team who performed the initial PHA has transferred, retired, or simply moved into new roles by the time of revalidation. If a PHA Reval is not documented effectively, nor involves the appropriate process experts, understanding of the process risks can be lost. This type of insufficient stakeholder engagement can result in missing insights into how the process truly operates or deviates. Every PHA relies on the collective knowledge of its team and if that’s weakened, the revalidation may miss hazards or misunderstand the adequacy of IPLs. 3.     Poor or Inconsistent Methodology Application If your PHA revalidation isn’t executed with consistent and up-to-date methods, gaps can occur. In some cases, the prior PHA might have used a different method or risk criteria than what the company uses now, causing confusion. For example, if the initial PHA methodology was misapplied or too simplistic for the process, it can result in the need for substantial correction down the road. Ensuring a comprehensive and systematic approach is applied during revalidation is vital to avoid leaving gaps. 4.     Underestimating Time and Resources Required PHA revalidations can be resource intensive. A common mistake is assuming a revalidation will be quick since “ we’ve done this before ”, and then not allocating enough time or personnel knowledgeable in the process. The result can be rushed sessions, incomplete reviews, or missing documentation. If an organization doesn’t budget adequate time (including for pre-work and team meetings), the five-year deadline can sneak up. 5.     Failure to Close Gaps from Previous PHA Recommendations A situation that many face during a PHA revalidation is discovering that some recommendations or gaps  from the last PHA were never implemented or fully resolved. Not only does this pose an ongoing risk, but it also complicates the analysis — the team might find themselves re-discussing hazards that should have been mitigated. OSHA expects that existing PHA recommendations are tracked and completed before revalidation ​. If that hasn’t happened, your facility faces both compliance issues and potentially repetitive findings. This issue often stems from lack of a robust management system for PHA action items. Anticipating and addressing these challenges early can significantly improve the quality of your PHA revalidation process. Best Practices for an Effective PHA Revalidation To mitigate the challenges described above, facilities should adopt several best practices for PHA revalidations: Prepare thoroughly : Update your process safety information, drawings, procedures, and incident history before the first team meeting. Performing this type of “ mini   audit ” of changes and process safety performance since the last PHA will help drive the revalidation scope. Engage experienced facilitators : Facilitators with expertise in the methodology selected for the reval can guide the process and ensure consistency across nodes and scenarios. Ultimately, your PHA Reval team should consist of experienced operations personnel, engineers familiar with the process, and a competent facilitator. Additionally, involving members from the original PHA team and/or certified PHA leaders can benefit the effort. Involve stakeholders:  Cross-functional support from those in operations, engineering, maintenance, and even management stakeholders who understand the process will increase your ability to maintain consistency and accuracy throughout the revalidation process. Verify implementation of past recommendations:  A revalidation is an opportunity to check the status of all previously identified hazards. Best practice is to explicitly review how each risk scenario identified last time has been addressed. The team should verify that no known hazard has been forgotten. If some recommendations were deferred or not resolved, this is the time to reassess those risks and decide on an action. Additionally, incorporate any relevant incident learnings (from your site or industry) to enhance the prior analysis​. By looping back on past findings and new learnings, the revalidation closes gaps and solidifies your facility’s risk baseline. Document and track everything : Just as you review old recommendations, establish a strong process for following through on new PHA recommendations coming out of the revalidation. This includes clearly prioritizing them (e.g. using a risk matrix or LOPA results to rank urgency), assigning responsibility, and setting deadlines. Remember, OSHA requires documented resolution of PHA recommendations​ — having a tracking system not only aids safety but keeps your facility compliant. Consider partnering with a qualified PHA facilitator : One of the best investments for a successful PHA revalidation can be partnering with a skilled facilitator. An experienced, third-party PHA facilitator can provide a litany of benefits — including chemical and process knowledge across industries. Beyond providing expert guidance, facilitators can also serve as an objective, unbiased perspective. When considering an external PHA facilitator, look for a provider who goes beyond “ checking the boxes. ” Facilitators should also offer effective prioritization of risks and recommendations. Additionally, a facilitator should be able to present an actionable gap closure game plan that includes recommendations for trusted engineering solutions providers  who can support resolving identified issues.     You’ve Completed Your PHA Reval — What Next? A successful PHA revalidation doesn’t end when the last worksheet is signed. The real value comes from implementing recommendations and closing identified gaps. At this stage, facilities should: -          Prioritize recommendations  using risk matrices or LOPA to focus efforts on high-consequence scenarios -          Develop actionable plans  for implementation, assigning ownership, and tracking progress -          Work with a facilitator or engineering partner  who can help close common recommendations such as SIS upgrades, BPCS changes, Alarm Management improvements, BMS modifications, Facility Siting enhancements, and Fire & Gas system updates. -          Document closure , including verification of effectiveness and updates to procedures or training as needed Without follow-through, a PHA revalidation becomes a compliance checkbox rather than a meaningful tool for reducing risk. The Takeaway | Turn Your PHA Reval Findings into Forward Motion Process safety isn’t static — and your PHA shouldn’t be either. Regular, well-executed PHA revalidations are essential to staying compliant with OSHA, maintaining operational continuity, and safeguarding personnel and assets. For facilities navigating complex changes, aging infrastructure, or resource constraints, engaging with experienced PHA facilitators  can bring structure, insight, and measurable outcomes to the revalidation process. When done right, PHA revalidations don’t just ensure compliance — they create a roadmap for safer, smarter operations.

Greenville, SC – April 2025 – aeSolutions, a provider of integrated, end-to-end critical system solutions that empower resilient operations and safer communities, is proud to announce three strategic internal promotions, reflecting the company’s continued commitment to realizing employee potential through the achievement of client success. Roland Stock, PMP, a current member of our Senior Leadership Team, has been named Vice President of Projects , where he will lead our Project Management Office and cross-functional project teams in the development and execution of projects to achieve our clients’ goals. Roland brings deep experience in project leadership and a strong track record of delivering complex solutions across industries.  Chris Powell, PE, CFSE, joins our Senior Leadership as the Director of Engineering where he will focus our Engineering Team’s development, collaboration and performance to drive our mission of improving industry by guiding our clients to increasingly resilient operations and safer communities. Chris will apply his leadership and expertise developed through the application of the Safety Lifecycle in his previous roles, including his most recent position as the Functional Safety Group Manager. Emily Henry, PE, CFSE, has been appointed Functional Safety Group Manager , where she will lead the team of safety professionals responsible for delivering lifecycle safety services. Her depth of expertise in functional safety as well as her relentless drive for our client’s desired outcomes position her to lead this group. “ These promotions reflect the depth and breadth of talent and the strategic importance of developing our leaders’ potential, ” said Chris Neff, COO at aeSolutions. “ Roland, Chris, and Emily have each demonstrated dedication to our clients’ success through exceptional leadership, technical acumen, and progressive experience. We are thrilled to see them step into these new roles. ” Visit aeSolutions for more information.

Introduction | Control System Migrations | Part 6 April 2025 — by Tom McGreevy, PE, PMP, CFSE — By now, you've successfully navigated the Front-End Loading (FEL) phases , clearly defined your scope, budget, and schedule , and received approval for funding. However, the real challenge arises when plans meet the unpredictability of real-world execution. Monitoring, managing changes, and reporting effectively during this execution phase are critical to a project’s success. Contractor Reporting Requirements Detailed reporting expectations must be clearly defined early — ideally during the solicitation phase  — to ensure effective project control. Three key elements to consider with contractor reporting requirements are: Required Information Must be Specified Explicitly state the type of information needed, including task progress, upcoming activities, recent accomplishments, roadblocks, and actionable items. Specify the report format ( e.g., Excel, Microsoft Project, Primavera ) to ensure data usability. Reporting Frequency Reporting intervals — which are typically established based on the project’s size — enable timely identification of issues and corrective action. Frequent communication helps maintain project momentum and clarity. Report Detail Reports should provide enough detail to enable actionable decisions without overwhelming the management team. They should also include specific metrics on schedule performance, budget status, and risk assessment outcomes. Managing Change Orders Changes will happen. Whether driven by unexpected conditions, improved technical ideas, or shifting requirements, a structured change management process with proper documentation is essential. Change orders fall into two types of categories, which is determined by the reasoning behind the change: Design Change Orders Design changes can be positively received as they often involve beneficial, innovative ways to achieve the same project goals more efficiently. Design changes usually involve adjustments in how requirements are implemented rather than what is implemented. They typically deliver cost, schedule, or reliability benefits. Scope Change Orders Usually driven by unforeseen events or missed requirements, scope changes can be particularly challenging to justify. They require a thorough evaluation and management buy-in of documented impact on costs, schedule, and potential new risks. Even legitimate scope changes can face high scrutiny, as they must demonstrate independent financial justification and alignment with organizational priorities. Both types of change orders should follow a structured approach: Document the proposed change via a Request for Information (RFI) Group review to determine if there is a compelling reason supporting the change Estimate the impact on scope, schedule, cost, & new risks Approval or rejection by the designated management team This ensures transparency and control, preventing unauthorized or detrimental changes.   Earned Value Management  Earned Value Management (EVM) is a powerful tool that integrates project scope, schedule, and budget. To leverage EVM effectively, projects must be set up correctly during FEL phases with: 1.      A well-defined Work Breakdown Structure (WBS) 2.      Resource-loaded schedules 3.      Documented cost allocations Image Source EVM allows project managers to detect early deviations in schedule or budget, enabling timely corrective actions. The primary metrics used in EVM include: Planned Value (PV):   What you planned to spend. This can also be referred to as Budgeted Cost of Work Scheduled (BCWS). Earned Value (EV):   The amount of work that’s been performed and the budgeted cost of that work. Actual Cost (AC):   The actual  expenditure for the work completed, sometimes referred to as Actual Cost of Work Performed (ACWP). Regularly tracking these metrics helps maintain control and transparency, providing valuable insight into how well a team is managing budget and schedule, in addition to indicating early warnings that can help prevent minor deviations from escalating. The Takeaway Effective project monitoring, proactive change management, and thorough reporting are keys to successful control system migrations. When executed properly, these processes provide significant stress relief, enabling project teams to maintain control amidst inevitable uncertainties. Organizations benefit immensely from clearly defined reporting standards, structured change processes, and earned value management practices. By incorporating these practices early and consistently, teams enhance project outcomes and organizational confidence in project delivery. In the meantime, check out parts 1-5 of our control systems migration blog series .

When TGES America, Ltd. (hereinafter TGES America) needed a critical overhaul of the complex control system and instrumentation for the central utilities plant (CUP) of a specialty materials manufacturing plant, they turned to aeSolutions, a Siemens Solution Partner. Subsequently, due to the need to complete the project four months early, the planned cold cutover to the new systems had to be done as a hot cutover without disrupting production. TGES America, aeSolutions, and Siemens made it happen, much to the delight of the customer. February 2025 — Based in Duncan, South Carolina, TGES America opened its doors in 2015 as a subsidiary of Tokyo Gas Engineering Solutions Corporation, a global engineering and energy solution provider with more than 50 years in the energy industry. In addition to EPC services, TGES America offers U.S. industrial customers onsite energy services, for which TGES America owns the plant facilities that provide electricity, steam and other utilities needed for production. Known in aggregate as a central utilities plant (CUP), TGES America operates these facilities for customers on leases running 20 years or more. TGES America can also negotiate long-term power agreements with external utilities, including solar and other renewables so plants and the firms owning them can meet their net-zero decarbonization goals. The TGES America model eliminates the capital expenditure and helps to level operating expenses that its customers would otherwise incur in owning and maintaining those facilities themselves while simplifying plant budgeting and planning. It also allows plant management to focus more on meeting production goals and delivery commitments. The Challenge | Introducing a state-of-the-art and reliable control system early to enhance customer satisfaction One TGES America customer is a specialty materials manufacturer. The plant’s CUP provides steam, compressed air, chilled water, deionized water and cooling water, all of which are required by several production lines for their many sophisticated and carefully calibrated processes that ensure maximum efficiency and yield. When TGES America took on responsibility for the plant’s CUP several years ago via a long-term lease, it became apparent that the existing control system needed to be upgraded to ensure greater stability. “ We quickly realized upgrading the system was necessary to consistently meet our customer's requirements, ” says TGES America CEO Konosuke Usui.” TGES America decided to develop and deploy a more advanced and highly reliable industrial control system (ICS). Moreover, given that CUP energy service agreements typically span 20 to 30 years, the ICS needed to be future-proofed for such a long lifecycle and be upgradeable with the latest technologies over that time. The Solution | Engage an expert partner to design, engineer, and install fully modern and ultra-reliable systems for CUP controls and monitoring In 2019, TGES America began searching for solution providers. Familiar with Siemens' reputation for high-quality and reliable automation and controls, TGES America's project team used the Siemens Partner Finder to shortlist potential system integrators. After carefully evaluating five candidates, TGES America's project team chose aeSolutions, a 120-employee systems integrator based in Greenville, South Carolina, with offices in Houston and Anchorage. As a certified Siemens Solution Partner, the company specializes in solving extreme industrial engineering challenges in process safety, combustion control and safeguarding, safety instrumented systems, control system design and integration, alarm management, and related operations and integrity management systems. “ aeSolutions stood out from the others with their excellent response and superior technical proposal, which made them the clear choice for assisting us in the critical overhaul of our customer’s CUP facilities, ” Usui says. “ We also knew we could trust the highly integrated Siemens technologies included in aeSolutions’ proposal. ” Solution Designed - Cold Cutover Planned In December 2020, TGES America‘s Project team awarded aeSolutions an initial contract to allow for preliminary engineering and for the early purchase of equipment due to the global pandemic extending supply chain deliveries. “ At that time, the project had a completion target of March 2022, ” aeSolutions CEO Ken O’Malley recalls. “ The production facility was idle due to the pandemic, so the project’s execution plan would allow for an extended cold cutover to the new control system. ” His engineering team worked closely with TGES America’s Project team to develop a comprehensive ICS solution consisting of these Siemens components drawn from the Totally Integrated Automation (TIA) portfolio: SIMATIC S7-1500H Programmable Logic Controllers (PLCs) , which provides the CUP with high availability and built-in redundancy via a backup CPU synchronized with the primary CPU to ensure continued operation with no data loss. It also features built-in diagnostics with highly secure remote accessibility from anywhere at anytime by any web-enabled device. SIMATIC ET 200SP Distributed IO , a scalable and highly flexible system for connecting process signals to the S7-1500H PLC over high-speed PROFINET. SCALANCE Layer 2 Managed Switches , for securely segmenting the plant network that supports the CUP’s many physical utilities and their production process- enabling functions. WinCC Runtime Professional V17 , a PC-based operator control and monitoring system for visualization and operation of all the CUP’s processes, production sequences, and connected machines across the plant. SCALANCE Industrial Ethernet Security Appliance , for secure remote access to the control LAN. The Siemens TIA Portal was used to program the CUP’s control system as well as its WinCC Professional HMI. The TIA Portal’s intuitive, all-in-one software engineering platform with a drag-and-drop interface unifies control programming, HMI visualization development, and parameter settings. “ With TIA Portal, our engineers saved time and delivered higher quality with less effort versus other ICS platforms because of the totally integrated architecture, ” O’Malley says. Schedule Accelerated by Four Months - Hot Cutover Required In March 2021, Usui recalls, the customer told TGES America that the global pandemic was easing and that there was a change in the customer's production schedule, meaning the plant would be ramping up to full production four months earlier than originally planned. “ So, after considering how much our project team could pull in the various engineering, procurement, testing, and commissioning tasks involved, we agreed to a new target completion date, ” he says. But this accelerated timeline didn’t come without execution risks, according to O’Malley. “ Because the production facility’s ramp-up would be well underway when the new date for the new control system cutover would happen, we’d have to perform it hot without interrupting the plant’s utilities supply to production, ” he says. “ Clearly, doing this would be no small feat. ” In such challenging circumstances, TGES America project manager Atsushi Iwamoto and aeSolutions project manager Shane Kjergaard worked closely together, repeatedly revising the project plan and tirelessly coordinating with stakeholders to ensure the project stayed on schedule. As a result of the TGES America and aeSolutions teams coming together as one team, they were able to achieve completion on the revised schedule. In addition, aeSolutions’ engineering team is very experienced completing complex hot cutovers, for example, the hot relocation of a large control room in the Artic for one of the world’s largest natural gas processing plants. “ In the end, we managed a complex, step-by-step hot cutover plan of the control system without interrupting the plant’s utilities supply, ” O’Malley says. “ The easy Siemens component integration and TIA Portal programming took systems integration off the critical path so we could focus on executing the hot cutover. ” For that, aeSolutions developed an interim hybrid control architecture using the site’s existing Modbus TCP/IP network to share signals between the old system and the new Siemens ICS. “ Think back to hard-wired signal switches, ” he explains. “ As we moved the signal wires from the old system to the new Siemens ICS, the old system still had access to those signals via Modbus. Once most of the signals for a given system had been moved over to the Siemens system, we switched master control for that system over to the Siemens ICS. It was a tightly coordinated, high-stakes dance with operations, construction, and engineering all working together. ” Results | Improved Margins and a Repeatable Reference Model for TGES America — With Reliable Plant Utilities and Customer Trust Restored Now, Usui reports the Siemens ICS is working reliably and to specification. TGES America has improved efficiency and successfully enhanced the operational stability of the plant. “ Our customer is satisfied, so we are quite satisfied. ” he says. “ Our successful ICS solution provides us with a repeatable reference model for other customers. And it’s one we can quickly configure to their specifications while saving custom engineering time and costs. ” Usui adds ,“ The Siemens PLC’s built-in diagnostics enable onsite operators to quickly troubleshoot and remedy issues before they impact production. And if an escalation is required, aeSolutions or Siemens experts can remotely access the system using the Siemens SCALANCE security appliance with TIA Portal to do the troubleshooting and remediation themselves, minimizing downtime. ” Future-Proofed for Decades to Come What’s more, the advanced Siemens technologies inside the ICS provide much greater operational visibility, so TGES America can conduct condition monitoring for preventive and even predictive maintenance of plant facilities. “ As we expand our TGES America customer base, we can extend this visibility and monitoring across all of our deployments to manage them as a fleet and keep watch on each site’s performance, ” Usui says. TGES America and aeSolutions are also discussing whether they can pursue even greater stability by introducing new technologies. “ For example, the new AI tools coming available for our customers today are exciting, such as Siemens S7-1500 TM NPU module that operates using a trained neural system, ” says O’Malley. “ It’s literally a plug-and-play upgrade and, with it, the CUP’s different utility provisioning systems can read their own sensor data, intelligently interpret performance variations and anomalies, then respond flexibly and automatically to situations that used to require manual intervention, reducing downtime and increasing availability. ” This kind of Siemens technology advancement gives Usui the confidence to know that when TGES America deploys a control system, its lifecycle will span the long-term leases that are the basis of the TGES America business model. “ At the same time, we expect our strategic partnership with aeSolutions and their expertise, experience, and tight relationship with Siemens will help us continue to prosper and help our customers be successful for many decades to come, ” he says.

aeSolutions’ next generation of fire and gas alarm and control solutions for the industrial market has arrived. The FGS 5000 combines the required functionality into a Rockwell control logix control platform. The FGS 5000 was designed to give customers a reliable, easy-to-maintain fire and gas platform that instrument techs familiar with the Rockwell control system platform can maintain and troubleshoot. The system is designed to be highly scalable, from small 50 I/O systems up to systems with 500+ I/O. A critical component of the FGS 5000 is an FM Approved secondary power supply system consisting of a charger panel and an associated self-contained battery system. To support system design, aeSolutions has developed an FM Approved battery sizing tool which confirms the battery system design based on the specific requirements of each application. By using the same hardware/software platform as end users using Rockwell BPCS systems and infrastructure, the FGS 5000 can be integrated into the entire plant system solution. It offers the advantages of common HMIs, spare parts, training, engineering/configuration tools, maintenance, and procedures to save installed and lifecycle costs dramatically. The aeSolutions FM Approved family of Fire & Gas systems are designed to the latest standards using our first-hand industry experience. Gas Monitoring & Control The FGS 5000 has also been FM Approved to be in conformance with FM Approval’s Combustible Gas Standard 6320, Toxic Gas Detection Standard 6340 and ANSI/ISA 12.13.01 Performance Requirements for Combustible Gas Detectors standard. Fire System Monitoring & Control The FGS 5000 has been FM Approved to be in conformance with the requirements of NFPA 72 and FM 3010 standard for fire alarming and mitigation control. The system has approval for either simplex or redundant processors, a variety of I/O configurations, including remote I/O, and a battery back-up/charger subsystem. Features The FGS 5000 Fire & Gas System is a pre-engineered, pre-configured, and pre-packaged system that is suitable for a wide variety of applications and is available as a turnkey solution. A complete turnkey Fire & Gas System that is FM Approved to be compliant with NFPA 72 (2022 Edition) and FM 3010 standard for both fire and gas monitoring in the same PLC Approved for combination system I/O – Can be used to control HVAC Developed around the Rockwell ControlLogix® Series PLC platform Supports simplex I/O and either simplex or redundant processors: offers a remote I/O option Uses Rockwell Flex5000 I/O cards The system includes interface capability to a wide variety of sensors and final control elements with fully supervised circuits (IDC, NAC, FSF, and SDC) Communication to control systems via Industrial Ethernet, hardwired I/O, or Modbus FGS 5000 includes a complete battery backup system with charger No on-site programming required The FGS 5000 has 2 operator interface options: 12” Panelview Plus, or Industrial PC’s running RS-View Field Device Options Manual pull stations Heat & smoke detectors Temperature rate-of-rise sensors Toxic gas detectors Combustible gas detectors Suppression subsystems Local alarm horn / beacon Environmental protection Host communication capability IR fire detectors Multi-spectrum fire detectors Addressable detectors from Apollo System Integration Options Our qualified engineers apply years of expertise to provide: A complete single-source turnkey solution for the optimum FGS 5000 solution Detector placement and modeling services Complete field construction package Implementation of all phases of design, fabrication, configuration, and documentation System verification and validation including factory acceptance, integration, and client acceptance testing Training at both the engineering and technician levels Commissioning and startup support System Specifications Processor Rockwell ControlLogix® 5580 Series with redundant processor option I/O Both analog and discrete supervised circuits and remote I/O option Inputs/Outputs Application-dependent Power Supply Options PS1400-20-252: 20 Amp 24VDC Output Nominal; 115/230 VAC Input/252 amp Hour Battery Backup. PS1400-50-600: 50 Amp 24VDC Output Nominal; 115/230 VAC Input/600 Amp Hour Battery Backup. PS1400-100-1200: 100 Amp 24VDC Output Nominal; 115/230 VAC Input/1200 Amp Hour Battery Backup. PS1400- 150-1800: 150 Amp 24VDC Output Nominal; 208/240/480 VAC Input/1800 amp hour battery set. Optional Rack assembly to stack charger and battery set. Temperature Operating: 0 to 50 Deg C. Storage: -40 to 60 Deg C Humidity Operating: 0 to 95% non-condensing Cabinet Nema 4, 4X, 12, powder coated or stainless steel; size is application-dependent Area Class General purpose or Class I Div 2 Weight Application-dependent Certifications FM Approved for compliance with NFPA 72 and FM 3010 for both Fire & Gas; FM Approval’s Combustible Gas Standard 6320, Toxic Gas Detection Standard 6340 and ANSI/ISA 12.13.01 Performance Requirements for Combustible Gas Detectors standard. Initiating Device Circuits Class A & B for discrete dry contact IDCs; Class B for Analog IDCs Notification Appliance Circuits Class B

Introduction | Control System Migration | Part 4 November 2024 — by Tom McGreevy, PE, PMP, CFSE — Give yourself a pat on the back, you’ve successfully navigated the tasks of providing procurement specification and selecting a vendor for your control system migration project . In part four of this series , we will be exploring scope, schedule, and budget. These elements form the “triple constraint” or what is sometimes referred to as the “three-headed monster” of control system migration project management — or any project, for that matter . The success of a migration project depends on balancing these constraints, with trade-offs required to meet objectives while addressing stakeholder needs, industry mandates, and operational realities. Phased Project Execution and Trade-offs Ideally, control system migrations follow a phased approach — starting with conceptual and preliminary design, moving through detailed design, and ending in execution. However, phases do not always flow sequentially, and overlapping activities are common, a phenomenon that makes a project more challenging. At the heart of control system projects lies the negotiation between scope, schedule, and budget. These three variables shape the project from inception to completion. Stakeholders, including project sponsors, operations teams, and users, bring different priorities to the table — requiring alignment to strike the right balance. For example, a project's scope must align with user requirements while staying within budget and schedule constraints. While many projects have some flexibility for scope, budget and schedule trade-offs, few projects are entirely unconstrained. Rare exceptions exist — such as the rapid construction of the Pentagon during World War II or the development of the atomic bomb — where scope and schedule were paramount, and budget was comparatively unlimited. However, most control system migrations are not afforded a constraint waiver, making the balancing act of scope, schedule, and budget a constant challenge. The Importance of Schedule and Outage Management In many control system migration initiatives, the project schedule is non-negotiable. Certain projects — such as those in the energy sector — are driven by government regulations (like Title V permitting ) or market demands, forcing strict adherence to timelines. Refinery turnarounds are a prime example: These large-scale maintenance events may only occur every 10 years, and once scheduled, the dates cannot shift. The high cost of shutting down operations for a refinery or chemical plant places immense pressure on teams to execute migrations efficiently within the set outage window. Outage durations and deadlines are major factors influencing both project scope and budget. Teams must prepare thoroughly to avoid overruns, as missing an outage window could result in costly delays. Planning and execution are equally critical during cutover phases when legacy systems are replaced with new ones, requiring seamless transitions within tight timeframes. Stakeholder Engagement and Balancing Constraints Engaging stakeholders early in the migration process is essential to align expectations around scope, schedule, and budget. By understanding their priorities — whether cost control, quality, or speed — project teams can manage trade-offs effectively. For example, a project may prioritize scope and quality, leaving budget as a secondary concern. However, as the old project management adage goes: “ You can have two of the three—scope, schedule, or budget—but the third must remain flexible .” A common question when setting priorities is whether quality fits within scope. In control system migrations, quality is considered a given. If the migration is poorly executed, operational issues will surface immediately, posing significant risks to production. Based on this, ensuring quality throughout the process is non-negotiable, even if it means adjusting schedule or budget constraints. Whether the new control system is ultimately a “Chevrolet”, or a “Cadillac” is a scope question, the answer to which depends on user requirements. However, whether a Chevy or a Caddy, the solution must be of high quality.    Scope — V-Model Systems Engineering The V-Model Systems Engineering approach is a widely recognized and robust framework, that is particularly valuable in managing project scope within control system migrations. Originating from the systems engineering discipline, the V-Model has been used extensively by industries such as process control and process safety and is a standard practice in high-stakes environments like the Department of Defense (DoD). The DoD has adopted the V-Model as a foundational approach for all acquisition systems, owing to its reliability and flexibility across various complex systems. The V-Model’s structured yet adaptable framework makes it an ideal tool for managing the many layers of control system migrations, where scope must be clearly defined and rigorously adhered to. The model is not only a theoretical construct but also integrated into practical standards like the IEC 61511 standard for Safety Instrumented Systems, demonstrating its alignment with the development and delivery of safety-critical industrial automation systems. Understanding the V-Model Structure   Image Source   The V-Model is visually represented as a “V” shape, with each side denoting specific phases of a project lifecycle. Starting from the upper left, the model begins with conceptualization and planning stages, where project requirements are established. These initial steps serve as the foundation for the entire project, ensuring clarity in objectives and design specifications. As the project progresses down the left side of the “V,” each phase deepens the project’s detail, moving through stages such as system architecture, preliminary design, and detailed design. At the bottom of the “V,” the project reaches the development and integration phase, where the designed systems are constructed and configured. The right side of the “V” begins with the validation and verification stages, where each element developed is thoroughly tested and validated against the original requirements set out in the project’s conceptual phase. This structured approach provides a clear pathway from inception to completion, ensuring that each component of the control system migration aligns with the initial scope and quality expectations. An important element of the “V” is that systems engineering does not end after system commissioning but should continue throughout the life of the asset to ensure upgrades and changes are also managed in a systematic manner. Benefits of the V-Model in Control System Migrations The V-Model’s stepwise progression is highly beneficial in control system migrations, where maintaining scope integrity is crucial. Each phase builds upon the last, allowing for consistent alignment with project objectives. The systematic approach helps minimize scope creep —  a common risk in complex migrations — and ensures that each requirement is tracked through development to final validation. One of the unique strengths of the V-Model is its emphasis on early-stage requirements. By investing time in clearly defining the project’s scope and requirements at the outset, teams can better manage expectations, budgets, and timelines. This is particularly valuable in environments where safety and reliability are critical, as any deviation from the intended design could result in costly or even hazardous outcomes. Scope — Requirements Document The Requirements Document is a foundational component in any control system migration, defining what the project must achieve and setting the framework for success. At the outset, the project team collaborates with stakeholders to clearly define the project’s objectives, specifications, and performance standards. This process ensures alignment around the key questions: What are we trying to accomplish?  and What are the essential requirements? In a control system migration, whether a Basic Process Control System (BPCS) or Safety Instrumented System  (SIS), a requirements document addresses the unique demands of replacing outdated and unsupported systems. As technology evolves, older systems eventually become unsupported, are difficult to maintain, lack operational reliability and flexibility, and no longer meet the organization’s needs. Establishing clear, detailed requirements is imperative in ensuring the new control system addresses these challenges effectively. Key Elements in Requirements Documentation The requirements document must integrate inputs from multiple entities involved in the control system’s operation and maintenance: Physical Environment Requirements :  This includes details about the physical assets the control system connects to, such as motors, pumps, compressors, tanks, and valves. Understanding the full scope of the machinery and processes the control system controls is crucial for designing a system that operates safely and effectively. User Requirements : Operators are on the front lines of system interaction, making user-friendly interfaces critical. The requirements document specifies Human-Machine Interface  (HMI) design, alarm management, and process visualization needs, ensuring that operators can navigate the system efficiently and without undue stress. Maintenance and Troubleshooting Requirements :  Maintenance teams need access to troubleshooting tools and systems capable of proactive fault detection. Requirements for system diagnostics, error reporting, and asset management tools (such as those using HART communication protocols ) are outlined to streamline ongoing maintenance. Advanced Control and Optimization :  For organizations aiming to optimize quality and profitability, the requirements document includes specifications for advanced applications and optimization tools. These capabilities allow for efficient control of complex processes and help meet business objectives. Cybersecurity and IT Requirements :  IT teams and cybersecurity stakeholders provide input on access control, remote troubleshooting capabilities, and integration with broader IT systems. This is especially important in cases where engineers or maintenance personnel may need secure, remote access to the control system. Business and Management Requirements :  Business leaders often have specific visibility requirements, allowing them to monitor production and other metrics from a management perspective. The requirements document captures these needs, balancing operational transparency with security concerns. The Systems Engineering V-Model for Requirements Documentation The Systems Engineering V-Model discussed earlier is also frequently applied to structuring the process of defining, refining, and verifying requirements documentation. During the initial FEL ( Front-End Loading ) phases, the project team identifies high-level requirements, involving potential vendors, systems integrators, and Original Equipment Manufacturers (OEMs) to validate early concepts. As the project progresses, requirements are broken down into more specific design elements, such as Piping and Instrumentation Diagrams (P&IDs), system architecture diagrams, and detailed hardware and software specifications. This phase culminates in a comprehensive set of design deliverables, including finalized drawings and specifications. As the project moves from design into implementation, the V-Model allows teams to check each aspect of the implementation against the original requirements, ensuring that the system meets expectations through validation and verification steps. Ongoing Maintenance and Adaptation Control system migrations do not end with commissioning. Modern control systems are increasingly software-dependent, relying on regular updates and security patches for sustained performance. As part of the requirements documentation, teams establish processes for managing updates and maintaining alignment with evolving cybersecurity standards. These “ living ” documents serve as references for future maintenance, ensuring the control system remains functional, secure, and aligned with operational needs well into the future.   Scope — Work Breakdown Schedule (WBS) A Work Breakdown Structure (WBS) is fundamental to the scope definition process in control system migrations, as they establish a clear framework for planning, estimating, and executing the project. The WBS divides a project into smaller, manageable parts, facilitating clearer communication, better cost control, and improved resource allocation. At its core, a Work Breakdown Schedule helps the team “ eat the elephant one bite at a time ,” breaking down complex tasks into structured and measurable components. Developing the Work Breakdown Structure In a WBS, the project is defined at the highest level and progressively divided into subprojects, sub-phases, and tasks. The process typically starts with defining the overarching goal — whether that’s replacing outdated control systems, implementing new safety standards, or optimizing performance. From there, the WBS is broken down into manageable sections, with each phase building on the previous ones. The ultimate goal is to create small enough tasks that allow for accurate estimation and efficient management. A comprehensive WBS should be developed early in the control system migration project, ideally before the schedule is finalized. Breaking down the project into smaller components enables teams to estimate durations and resources for each element more accurately. This is especially valuable in complex control system migrations, where precise scheduling is a must-have to minimize operational disruptions. Owner-Level and Vendor/Contractor-Level WBS In many projects, including government and large-scale industrial migrations, the WBS is divided into two levels: Owner-Level WBS : The project owner (often the client or the entity funding the project) typically defines the first few levels of the WBS. This includes outlining the major phases, primary objectives, and key deliverables. For instance, in government contracts, the owner might specify the first two levels of the WBS, setting the foundational structure of the project without delving into granular details. Vendor/Contractor-Level WBS : Contractors or vendors are then responsible for developing the WBS beyond the initial levels specified by the owner. They add the finer details needed for execution, filling in tasks, subtasks, and resource assignments to meet the owner’s requirements. This approach empowers contractors to bring their expertise to the project, structuring their work to align with the project goals and optimizing resource allocation. This dual-level WBS structure allows owners to set clear expectations while giving vendors the flexibility to plan and execute in a way that leverages their strengths. It’s a common practice to help ensure a balanced approach where high-level objectives are set by the owner, and detailed planning is conducted by those executing the work. Benefits of a Well-Defined WBS A well-defined WBS simplifies schedule and budget development by enabling a “ bottom-up ” approach to project planning and execution. It provides a structured method for estimating time and resources, making it easier to assign costs accurately and avoid budget overruns. By breaking the project down into smaller parts, the WBS helps identify risks early, setting the stage for more effective project management. In the context of control system migrations, where tasks may vary in complexity and dependencies, a robust WBS can help mitigate scheduling challenges. Estimating timeframes for smaller tasks is inherently easier than for large, undefined tasks, leading to a more realistic and achievable schedule. Additionally, as the project progresses, the WBS serves as a roadmap, enabling the project team to track progress, adjust resources as needed, and ensure each phase aligns with the defined scope. For owners and contractors alike, a well-defined WBS not only clarifies project expectations but also enhances the likelihood of completing the migration on time and within budget.   Schedule — Resource-Loaded with Logic Creating a resource-loaded schedule with logic is a vital step in control system migrations, allowing project teams to allocate resources efficiently while ensuring all tasks follow a logical sequence. Once the scope is established, and the Work Breakdown Structure (WBS) is outlined, these elements provide the foundation for developing a detailed, executable schedule. By defining what needs to be done at a granular level, teams can move forward with estimating timelines and applying resources in a structured manner. Building the Schedule with Logical Sequencing A well-crafted schedule isn’t just a list of tasks — it is a sequence of events governed by logic. In this context, logic refers to the relationships and dependencies between tasks, dictating what must happen in a specific order and what can happen concurrently. This logical structure ensures that each activity aligns with the project's overall timeline, minimizing delays and optimizing efficiency. For example, certain tasks may need to finish before others can start, while some can proceed simultaneously, depending on resource availability and task dependencies. Using the WBS, each task in the schedule can be broken down into smaller sections, often organized in a Gantt chart format. The WBS sections align directly with the schedule, allowing for a smooth transition from scope definition to scheduling. As the project progresses from conceptual design (FEL 1) through preliminary (FEL 2) and detailed design stages (FEL 3), the schedule becomes increasingly specific. By the time the project reaches the execute stage, the schedule should be thoroughly developed, reflecting both the scope and WBS in a detailed, logical format. Resource Loading and Effort Estimation Resource loading is the process of assigning human resources, materials, and equipment to each task based on effort estimates. This step involves calculating the actual effort hours needed for each task, allowing the project manager to allocate the appropriate resources at the right times. Effort estimates are based on the complexity of the work, skill requirements, and task duration. A resource-loaded schedule helps ensure that project teams are neither overburdened nor underutilized, helping to keep the project on track and within budget. The resource-loaded schedule allows project managers to see where resources may be constrained or where adjustments might be needed. By integrating resource availability with task dependencies, the team can make informed decisions on scheduling adjustments, such as reallocating personnel or shifting task start dates. This level of planning is imperative in large-scale control system migrations, where resource constraints could lead to significant delays. The Value of Progressive Detailing The level of detail in the schedule should grow as the project advances. Early in the project, schedules are often high-level, with broader phases outlined in sequence. As the project reaches subsequent stages, each phase becomes more defined. By the time the project is ready for funding approval at the execute stage, the schedule should be highly detailed, providing a clear roadmap for completion. A well-detailed, resource-loaded schedule with logical sequencing is essential for obtaining project funding. Investors and stakeholders need confidence in the project’s timeline and feasibility, and a thoroughly prepared schedule demonstrates both preparedness and reliability. The more specific the schedule at this stage, the better equipped the team will be to manage the project’s complexities during execution.   Schedule — Critical Path The Critical Path is a fundamental concept in control system migration project scheduling. It represents the longest sequence of dependent tasks that must be completed for the project to reach its end date. In essence, the critical path is “ the longest pole in the tent ” — the chain of tasks that dictates the overall project duration. Identifying the Critical Path Identifying the critical path involves mapping out the sequence of tasks and understanding their dependencies. Each task on the critical path has no leeway for delay, as any delay in these tasks will directly impact the project’s completion date. Thus, accurately identifying this sequence early in the planning phase is essential, and a resource-loaded schedule can help visualize these dependencies and constraints. A resource-loaded schedule aligns resources with each task, allowing teams to see how resource availability impacts the critical path. By continuously managing to this path, project managers can ensure that resources are allocated to high-priority tasks, keeping the project on track. Managing the Critical Path Once identified, the critical path must be actively managed throughout the project. It’s common for the critical path to evolve as the project progresses — some tasks may be optimized, resources may be reallocated, or unforeseen issues may necessitate changes in task sequencing. For example, a task initially identified as critical “ subtask A ” might later be optimized, shifting the critical path to another task “ subtask D ”. This shifting nature requires a proactive approach to critical path management, with regular reviews to ensure the path remains accurate. Adjustments should be made as necessary to reflect any changes in the sequence or duration of tasks. By monitoring the critical path, teams can quickly adapt to changes and avoid potential delays. Ultimately, the critical path is the backbone of a control system migration project’s schedule. When managed well, the critical path provides a clear roadmap for prioritizing resources and activities to keep the project on track.   Schedule — Slip In any control system migration project, project managers should plan for schedule slip. Slip refers to the allowance for unexpected delays or setbacks that may impact the project timeline. Recognizing that projects are executed by human beings and subject to real-world unpredictability, building in a buffer for slip is a practical and necessary component of scheduling. Why Allow for Schedule Slip? Projects are seldom immune to delays. Factors such as natural disasters, world events, and unforeseen technical challenges can disrupt even the most meticulously planned schedules. By planning for possible delays, teams can set realistic expectations with stakeholders and avoid the need for crisis management when things don’t go as planned. A well-designed schedule with built-in slip is a reflection of common sense and practical risk management. This buffer provides the flexibility needed to adapt to changes without jeopardizing the overall project timeline. It allows project managers to respond to issues effectively, keeping the project on track while managing unforeseen obstacles. Managing Slip in Schedule Development Managing slip requires a careful balance between optimism and realism. Too little allowance for slip may result in unnecessary pressure on resources, increasing the risk of errors and burnout. Conversely, too much allowance may inflate the schedule, impacting cost and resource allocation. The goal is to include just enough flexibility to accommodate probable delays without compromising efficiency. In the context of control system migrations, schedule slip is especially important. These projects often involve complex integrations, interdependent systems, and critical operations. Allowing for slip in the schedule ensures that these complexities are managed without excessive risk of delay, helping the project team deliver a successful migration within a reasonable timeframe. A realistic approach to slip allows for smoother project execution, reducing the impact of setbacks and fostering a more resilient project plan.   Budget — Parametric, Analogous, & Bottom-Up Estimating As you might imagine, budget is an important component when planning a control system migration. Determining the funds required to complete the project is essential to ensure that resources are allocated effectively and that project stakeholders have realistic cost expectations. However, establishing an accurate budget can be challenging, particularly if cost estimates are provided too early in the process without sufficient data or analysis. The following budgeting techniques — Parametric Estimating, Analogous Estimating, and Bottom-Up Estimating — offer different methods to approach budgeting based on the project’s phase and the level of detail available.   Parametric Estimating Parametric estimating is commonly used in the early phases of project development when only high-level information is available. This technique relies on statistical relationships between historical data and other variables, allowing teams to estimate costs based on a unit of measure. For example, building a control system for a manufacturing plant might be estimated based on a cost per Input/Output (I/O) point or cost per square foot. Parametric estimates can vary significantly depending on the type of facility and the complexity of the control logic. For instance, while a widget manufacturing plant may have relatively simple I/O points, a chemical processing plant with advanced controls would require a more sophisticated (and thus more costly) system. Although parametric estimates are useful, they should be used cautiously, as variations in project scope or industry standards can impact the accuracy of these estimates. Unit cost estimating is a similar approach to parametric estimating, where costs are determined based on the cost per unit (e.g., per foot, per ton) of a particular item. This technique is often applied when more specific information about project components is available. In control system migrations, unit cost estimating might apply to components like stainless steel piping or wiring, providing a straightforward calculation for materials or parts with standard unit costs. Unit cost estimating is particularly useful for elements that have consistent pricing structures, allowing project teams to forecast material costs with a fair degree of accuracy. Like parametric estimating, this approach is more reliable when sufficient historical data exists, enabling comparisons across similar projects or components. Analogous Estimating Analogous estimating is another common technique used in the early stages of control system project budgeting. This method relies on historical data from similar past projects to estimate the costs of a new project. For instance, if a similar control system migration was completed five years ago, or if a nearly identical project was executed at another facility a year prior, those projects can serve as benchmarks for the current estimate. Analogous estimating allows teams to leverage known data, adjusting for differences in scope, inflation, or other variables, to create a rough cost estimate without extensive upfront details. While it may not provide the level of accuracy achieved through bottom-up estimating, analogous estimating is a practical tool for generating early budget figures and can be refined as more specific project information becomes available. Bottom-Up Estimating Bottom-up estimating is the most detailed and precise budgeting method, typically applied in the final design phases, such as the FEL 3. By this point, the project team has completed a detailed Work Breakdown Structure and can estimate costs for each subtask with higher accuracy. Bottom-up estimating involves calculating the cost of each component or task individually and then summing them to derive the total project cost. This technique requires a comprehensive understanding of the project’s scope, schedule, and resource requirements, making it best suited for later stages when detailed design and planning are complete. Although time-consuming, bottom-up estimating is highly accurate, as it accounts for specific project needs and is based on actual data from the project’s planning stages. Each of these budgeting techniques serves a unique purpose at different stages of project development. Parametric and Analogous estimating are effective tools in the early stages when only high-level information is available, while bottom-up estimating provides a more precise calculation as the project reaches maturity. By employing the appropriate technique at each stage, project teams can ensure that budget estimates evolve alongside the project, aligning with the increasing specificity of scope and design.   Budget — Analyzing the Quality of Your Budget Once a budget has been established for your control system migration, you’ll want to evaluate its quality. Analyzing the quality of a budget involves assessing whether the cost estimate is optimistic, pessimistic, or realistically positioned within the range of expected expenses. This process allows project managers to ensure that the budget is grounded in reality and aligned with project risks. Contingency and Reserve Planning One element of budget analysis is establishing a contingency amount. Contingency planning accounts for known risks that might affect costs, such as potential delays or changes in scope. Project teams can use various methods to determine contingency amounts, including expert opinion or quantitative approaches like Monte Carlo analysis . By calculating an appropriate contingency, the project team provides a buffer for foreseeable risks, adding a layer of resilience to the budget. In addition to contingency planning, projects should include a management reserve — a fund set aside at the discretion of the project manager to cover unforeseen issues. Unlike contingency, which addresses specific identified risks, the management reserve handles unexpected, “ unknown unknowns ” that may arise. This reserve allows project managers to navigate unanticipated challenges without immediately compromising the budget. Assessing Budget Confidence Analyzing budget quality also involves reflecting on the methodology used to develop cost estimates. Project teams should consider whether their cost elements are based on realistic assumptions and whether they have allocated resources prudently. By evaluating each component of the budget and ensuring it aligns with project goals and constraints, teams can increase their confidence in the budget’s accuracy. Before submitting the budget for final funding, it’s important to undergo this self-assessment. This evaluation helps in identifying any potential gaps and ensures that the budget reflects all known variables and has adequate provisions for managing uncertainty. Moving Forward with an Approved Budget Once the budget has been thoroughly analyzed and approved, the project is equipped with a solid financial plan. At this point, the project should also have a resource-loaded schedule, a clear critical path, built-in allowances for schedule slip, and structured reserve management. These elements together form a comprehensive project plan, ready for execution. As the project progresses, maintaining control over scope, schedule, and budget is crucial. Any project that begins with delays or budget overruns is challenging to recover, making it essential to start on solid ground. Proactively addressing risks early increases the chances of successful project completion and mitigates the impact of any adverse events that might arise.   Project Controls — In-House or Third-Party? Project controls are extremely important for the success of any control system migration. They provide the structure and oversight necessary to manage risks, monitor progress, and ensure that the project remains on schedule and within budget. The decision to handle project controls in-house or to engage a third-party firm depends on factors like organizational culture, project complexity, and available resources. In-House Project Controls Organizations with the necessary skills and resources may choose to manage project controls internally. This approach allows the project manager or other team members to oversee scheduling, estimation, and physical progress. An in-house team can solicit feedback directly from the design, procurement, and construction teams, collating data to update progress against the baseline. In-house project controls require a dedicated team with the ability to monitor percent completions, maintain schedules, and adjust resources as needed. However, many organizations today operate with lean staffing, focusing primarily on operational roles rather than project-specific capabilities. This limitation can impact their ability to execute comprehensive project controls effectively. Third-Party Project Controls When internal resources are insufficient, engaging a third-party project controls firm can be a strategic choice. Specialized firms focus solely on project controls, often bringing a high level of expertise and efficiency. Some third-party firms specialize in control systems, offering insights tailored to the needs of complex control system migrations. Larger engineering firms may also provide project controls services, supported by dedicated departments with robust processes and systems. Outsourcing project controls can offer a level of sophistication and objectivity that may be challenging to maintain in-house, especially for smaller organizations. These smaller facilities may lack the resources or expertise required for project controls and can benefit significantly from external support. Risk Management and Decision-Making Whether in-house or outsourced, project controls are fundamentally about risk management. They provide a framework to assess if the project is on track, identify potential delays, and highlight budget overruns. Having accurate and timely project controls data allows organizations to address issues proactively, minimizing disruptions and maintaining project momentum. Project controls serve as an early warning system, enabling project managers to intervene before small issues become major setbacks. They answer the key questions: Are we ahead or behind schedule? Are we within budget? Are we meeting quality standards?  This transparency is invaluable in ensuring that the project stays aligned with organizational goals. Project Controls in Procurement and Vendor Management When selecting vendors, systems integrators, or OEMs for a control system migration, it’s important to consider their project controls capabilities. Any vendor contributing to the project’s scope should be able to demonstrate project controls skills, providing regular reports on progress, costs, and quality metrics. This requirement applies even to subcontractors like electrical contractors, who may manage specific project segments but still impact overall timelines and budget. In larger companies, project controls are often standardized across departments, ensuring consistency in execution. Smaller organizations, however, may need to assess whether outsourcing these skills can provide the necessary structure to keep projects on track. Regardless of the approach, project controls are indispensable for managing scope, schedule, and budget in control system migrations, providing the transparency needed to ensure a successful outcome.   The Takeaway Control system migrations are complex projects that require a careful balancing of scope, schedule, and budget — the three primary constraints that govern project success. This fourth installment in our series has explored the essential frameworks, methodologies, and tools that can help manage these constraints effectively, from defining scope using the V-Model Systems Engineering approach to managing project controls in-house or through a third-party provider. Moving Forward with Confidence Control system migrations demand precision, foresight, and flexibility. By embracing the methods discussed in this series — from structured planning to diligent budgeting and project controls — organizations can enhance their capacity to deliver successful migrations that meet performance, safety, and financial objectives. Be sure to keep an eye out for the fifth installment in our control system migrations series, where we will explore best practices when planning and implementing training after a system migration. More information about aeSolutions' comprehensive DCS/PLC migrations and upgrades capabilities and services.