{"id":2963,"date":"2026-10-17T20:39:51","date_gmt":"2026-10-17T20:39:51","guid":{"rendered":"https:\/\/petrostreet.com\/main\/?p=2963"},"modified":"2026-10-17T20:39:58","modified_gmt":"2026-10-17T20:39:58","slug":"defining-safe-operating-limits-solin-petrochemical-units","status":"publish","type":"post","link":"https:\/\/petrostreet.com\/main\/defining-safe-operating-limits-solin-petrochemical-units\/","title":{"rendered":"Defining Safe Operating Limits (SOL)in Petrochemical Units"},"content":{"rendered":"\n

1. Introduction<\/strong><\/strong><\/h4>\n\n\n\n

Safe Operating Limits (SOLs) are a fundamental element of process safety management in petrochemical, refining, and oil and gas facilities. They define process-condition boundaries beyond which operators must stop routine troubleshooting and implement predetermined actions to return the process to a known safe state. Properly defined SOLs help prevent loss of primary containment (LOPC), equipment damage, runaway reactions, fires, explosions, and toxic releases.<\/p>\n\n\n\n

SOLs also provide a practical means of measuring process safety performance. Under API Recommended Practice 754 (API RP 754), qualifying excursions beyond applicable SOLs are examples of Tier 3 process safety indicators, representing challenges to safety systems before a more consequential process safety event occurs. API published the fourth edition of RP 754 in August 2026; therefore, organizations should verify exact definitions and counting rules against their controlled copy of the current edition.<\/p>\n\n\n\n

A critical distinction must be maintained between SOLs, normal operating ranges, alarm limits, equipment design limits, and operating-window limits. Treating these boundaries as interchangeable can result in under-reporting, unnecessary reporting, or misleading process safety statistics.<\/p>\n\n\n\n

2. What are Safe Operating Limits?<\/strong><\/strong><\/h4>\n\n\n\n

SOLs are defined process-parameter boundaries applicable to a particular operating phase. Crossing an SOL means that normal troubleshooting must give way to predetermined corrective action, which may range from an operator intervention to an automatic safety instrumented system (SIS) action.<\/p>\n\n\n\n

The relevant parameter may include:<\/p>\n\n\n\n

    \n
  • Pressure and temperature.<\/li>\n\n\n\n
  • Liquid level and flow rate.<\/li>\n\n\n\n
  • Chemical composition, concentration, or purity.<\/li>\n\n\n\n
  • Reaction rate, pH, or other chemistry-specific parameters.<\/li>\n\n\n\n
  • Corrosion inhibitor, neutralizing agent, or other essential chemical dosing.<\/li>\n\n\n\n
  • Other variables that can challenge containment, process stability, or critical safeguards.<\/li>\n<\/ul>\n\n\n\n

    The applicable SOL depends on the equipment, process hazards, and operating phase. A reactor may have different SOLs during startup, normal production, catalyst regeneration, shutdown, or a batch reaction. An SOL is a defined process safety boundary\u2014not simply an alarm setpoint or the equipment’s maximum design rating.<\/p>\n\n\n\n

    3. International codes, standards, and guidance<\/strong><\/strong><\/h4>\n\n\n\n

    No single international standard provides a universal numerical formula for establishing every SOL in a petrochemical plant. Limits should be developed from process design information, hazard studies, equipment capabilities, operating experience, and the consequences of deviation.<\/p>\n\n\n\n

    Reference<\/strong><\/td>Relevance to SOLs<\/strong><\/td><\/tr>
    API RP 754, 4th Edition (2026)<\/strong><\/td>Process safety performance indicators, including Tier 3 indicators. Confirm current SOL excursion criteria and counting rules in the controlled edition.<\/td><\/tr>
    OSHA 29 CFR 1910.119(d), (e), (f)<\/strong><\/td>For covered processes, requires documented safe upper\/lower limits, evaluation of deviation consequences, process hazard analysis, and operating procedures specifying limits and corrective actions.<\/td><\/tr>
    CCPS, Guidelines for Engineering Design for Process Safety<\/strong><\/td>Supports engineering-based selection of limits, design margins, process hazard evaluation, and safe operating envelopes.<\/td><\/tr>
    CCPS, Guidelines for Risk Based Process Safety<\/strong><\/td>Provides a broader framework for operating discipline, hazard control, incident learning, and performance indicators.<\/td><\/tr>
    IEC 61511<\/strong><\/td>Functional safety lifecycle requirements for safety instrumented systems in the process industry. It does not independently establish every process SOL.<\/td><\/tr>
    IEC 61508<\/strong><\/td>General functional safety framework underpinning safety-related systems.<\/td><\/tr>
    ISA-18.2 \/ IEC 62682<\/strong><\/td>Alarm management, alarm rationalization, setpoint selection, operator response, and lifecycle management. Alarm limits must be coordinated with SOLs but are not automatically equivalent.<\/td><\/tr>
    API RP 584, Integrity Operating Windows<\/strong><\/td>Addresses operating windows used to manage equipment integrity and reliability against process-related damage mechanisms.<\/td><\/tr>
    API RP 571<\/strong><\/td>Identifies damage mechanisms affecting fixed equipment in the refining industry and helps inform relevant integrity-related limits.<\/td><\/tr>
    API 520 \/ API 521 and applicable design codes<\/strong><\/td>Provide pressure-relief and equipment-specific design requirements. Design and relief limits inform SOL development but should not be substituted blindly for SOLs.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Apply each reference according to its scope and legal applicability. OSHA is a United States regulatory reference; API and IEC standards may be adopted through company engineering practices, contracts, or local requirements.<\/p>\n\n\n\n

    4. Methodology for establishing SOLs<\/strong><\/strong><\/h4>\n\n\n\n
    4.1 Identify critical process parameters<\/strong><\/strong><\/h5>\n\n\n\n

    Review process flow diagrams, P&IDs, process design basis, heat and material balances, equipment datasheets, operating procedures, control narratives, and cause-and-effect charts. Identify parameters whose deviation could cause a major accident, compromise containment, damage safety-critical equipment, or defeat a critical safeguard.<\/p>\n\n\n\n

    4.2 Establish the technical basis<\/strong><\/strong><\/h5>\n\n\n\n

    For each candidate parameter, document:<\/p>\n\n\n\n

      \n
    • Normal operating range and expected variability.<\/li>\n\n\n\n
    • Equipment allowable operating conditions and applicable design constraints.<\/li>\n\n\n\n
    • Process dynamics, including how quickly a deviation can develop.<\/li>\n\n\n\n
    • Consequences of deviation, as established through HAZOP, LOPA, and other process hazard analyses.<\/li>\n\n\n\n
    • Available preventive and mitigative safeguards, including alarms, trips, interlocks, and relief systems.<\/li>\n\n\n\n
    • Time available for effective intervention and the reliability of the required response.<\/li>\n<\/ul>\n\n\n\n

      An SOL should be conservative enough to allow the specified protective action before the process enters an unsafe state. It should not be derived simply by selecting a percentage below design pressure or temperature.<\/p>\n\n\n\n

      4.3 Distinguish the operating boundaries<\/strong><\/strong><\/h5>\n\n\n\n

      A practical conceptual hierarchy is: (1) normal operating range for stable and efficient operation; (2) alarm\/operator-response region, where an alarm prompts a defined response; (3) SOL, where predetermined actions to restore a known safe state must be initiated; and (4) further protective actions and equipment\/design boundaries, such as trips or relief devices, as conditions deteriorate. This is not a universal sequence of setpoints: actual relationships depend on process design, dynamic response, and the protection strategy. OSHA PSM guidance distinguishes routine operating limits from safe upper and lower design limits.<\/p>\n\n\n\n

      4.4 Define limits for each operating phase<\/strong><\/strong><\/h5>\n\n\n\n

      The same equipment may require different SOLs during startup, normal operation, regeneration, shutdown, and abnormal operations. For example, a reactor’s allowable temperature trajectory during startup may differ from its normal operating SOL. Differences must be technically justified and explicitly documented in phase-specific procedures.<\/p>\n\n\n\n

      4.5 Specify the response to an excursion<\/strong><\/strong><\/h5>\n\n\n\n

      For every SOL, define the actions needed to restore the process to a safe state. These may include stopping a feed, increasing cooling, isolating a source, switching to standby equipment, reducing throughput, or initiating an emergency shutdown. Specify responsibilities, response time where applicable, escalation criteria, and restart conditions. Where a protective function is credited, verify its design and performance against the hazard assessment and applicable functional safety requirements.<\/p>\n\n\n\n

      4.6 Approve, document, and maintain the limits<\/strong><\/strong><\/h5>\n\n\n\n

      Each SOL register entry should include at least:<\/p>\n\n\n\n

        \n
      • Equipment\/process tag and operating phase.<\/li>\n\n\n\n
      • Parameter, units, upper\/lower boundary, and direction of deviation.<\/li>\n\n\n\n
      • Technical justification and supporting studies.<\/li>\n\n\n\n
      • Alarm\/trip setpoints, where applicable, and their relationship to the SOL.<\/li>\n\n\n\n
      • Consequences of deviation and required actions.<\/li>\n\n\n\n
      • Process owner, approval date, revision history, monitoring method, and historian tag.<\/li>\n\n\n\n
      • Excursion-reporting requirements and evidence needed for classification.<\/li>\n<\/ul>\n\n\n\n

        Review SOLs after process changes, incidents, near misses, HAZOP\/LOPA updates, significant operating experience, and periodic verification. Changes to SOLs must be managed through the applicable Management of Change (MOC) process.<\/p>\n\n\n\n

        5. How SOL excursions should be reported as Tier 3 indicators<\/strong><\/strong><\/h4>\n\n\n\n

        API RP 754 classifies Tier 3 indicators as challenges to safety systems. SOL excursions are one example; other examples can include demands on safety systems and primary containment inspection or testing results outside acceptable limits. Tier 3 metrics are primarily intended for internal company learning and improvement. Because the fourth edition was published in August 2026, verify all detailed criteria against the current controlled copy.<\/p>\n\n\n\n

        5.1 When should an excursion be counted?<\/strong><\/strong><\/h5>\n\n\n\n

        A Tier 3 SOL excursion occurs when a process parameter exceeds the applicable SOL for the relevant operating phase, subject to the precise inclusion criteria in the applicable edition of API RP 754. The key test is whether the SOL itself was crossed\u2014not merely whether an alarm activated, the normal operating range was exceeded, or an integrity operating window was breached.<\/p>\n\n\n\n

        Examples may include:<\/p>\n\n\n\n

          \n
        • Reactor temperature exceeds its approved SOL, requiring the specified response.<\/li>\n\n\n\n
        • Column pressure exceeds its SOL following a condenser or cooling-water failure.<\/li>\n\n\n\n
        • Essential corrosion-inhibitor dosing falls below an SOL formally established because the deviation meets the relevant process safety criteria.<\/li>\n\n\n\n
        • Vessel level exceeds its approved SOL, requiring predetermined corrective action.<\/li>\n<\/ul>\n\n\n\n

          A deviation in chemical dosing is not automatically a Tier 3 event merely because it is outside the desired dosing rate. The parameter, boundary, and consequence must meet the site’s approved SOL methodology and API RP 754 criteria.<\/p>\n\n\n\n

          5.2 Event counting and documentation<\/strong><\/strong><\/h5>\n\n\n\n
            \n
          • Count each qualifying excursion according to the applicable edition. One initiating event, such as a utility failure, can cause multiple distinct SOL excursions.<\/li>\n\n\n\n
          • Avoid duplicate counting of one continuous excursion. Repeated fluctuations around an SOL during one continuous episode should not automatically be treated as separate events.<\/li>\n\n\n\n
          • Record start\/end times, maximum or minimum deviation, and duration as useful supplementary information.<\/li>\n\n\n\n
          • Document initiating cause, affected equipment, operator actions, automatic protection-system demands, and corrective measures.<\/li>\n<\/ul>\n\n\n\n

            These principles are described in the SOL-excursion section of API RP 754’s 2021 edition; confirm whether the fourth edition modifies details before finalizing a site procedure.<\/p>\n\n\n\n

            5.3 Recommended reporting workflow<\/strong><\/strong><\/h5>\n\n\n\n
              \n
            1. Detect:<\/strong> Identify deviation through the process historian, alarm\/event logs, operator rounds, or an approved monitoring system.<\/li>\n\n\n\n
            2. Verify:<\/strong> Confirm the process value, instrument validity, applicable SOL, and operating phase. Do not disregard a genuine excursion solely because an alarm was inhibited or failed to activate.<\/li>\n\n\n\n
            3. Protect:<\/strong> Follow the operating procedure and restore the process to a known safe state. Safety actions take priority over KPI classification.<\/li>\n\n\n\n
            4. Register:<\/strong> Log the event in the process safety indicator register with a unique reference and supporting evidence.<\/li>\n\n\n\n
            5. Investigate:<\/strong> Determine initiating cause and whether instrumentation, control strategy, equipment condition, operator response, or procedures contributed.<\/li>\n\n\n\n
            6. Close out:<\/strong> Assign corrective actions, owners, deadlines, and effectiveness checks. Review recurring excursions for systemic weaknesses.<\/li>\n<\/ol>\n\n\n\n
              5.4 Suggested Tier 3 reporting fields<\/strong><\/strong><\/h5>\n\n\n\n
              Field<\/strong><\/td>Information to capture<\/strong><\/td><\/tr>
              Event reference<\/strong><\/td>Unique SOL excursion ID<\/td><\/tr>
              Equipment\/process<\/strong><\/td>Unit, equipment tag, and parameter<\/td><\/tr>
              Approved limit<\/strong><\/td>SOL value, units, and applicable operating phase<\/td><\/tr>
              Actual deviation<\/strong><\/td>Peak value, direction, start\/end time, duration<\/td><\/tr>
              Initiating cause<\/strong><\/td>Utility failure, control malfunction, process upset, etc.<\/td><\/tr>
              Safeguard response<\/strong><\/td>Alarm, operator intervention, SIS trip, or other action<\/td><\/tr>
              Consequence<\/strong><\/td>Actual effect and credible potential consequence<\/td><\/tr>
              Corrective action<\/strong><\/td>Immediate response and preventive measures<\/td><\/tr>
              Classification<\/strong><\/td>Tier 3 SOL excursion, with rationale<\/td><\/tr>
              Closure<\/strong><\/td>Action owner, due date, and verification status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              A useful dashboard should show both excursion count and causes, duration, recurrence, affected units, and overdue corrective actions. A declining event count is not sufficient evidence of improved safety if limits have been altered without justification or event detection has deteriorated.<\/p>\n\n\n\n

              6. SOL, and Integrity Operating Windows: an important distinction<\/strong><\/strong><\/h4>\n\n\n\n

              An IOW is a set of limits for process variables established to maintain the integrity and reliability of equipment potentially affected by specific damage mechanisms. IOWs are concerned with equipment degradation. For example, a unit may have a maximum chloride concentration, minimum neutralizing-agent concentration, or a temperature range intended to prevent corrosion, cracking, or another damage mechanism.<\/p>\n\n\n\n

              An IOW excursion is not automatically a Tier 3 SOL excursion under API RP 754. Classification depends on whether the parameter also crosses an established SOL and satisfies the applicable reporting criteria.<\/p>\n\n\n\n

              Comparison<\/strong><\/td>Safe Operating Limit (SOL)<\/strong><\/td>Integrity Operating Window (IOW)<\/strong><\/td><\/tr>
              Primary purpose<\/strong><\/td>Prevent unsafe process conditions and challenges that may lead to a major process safety event<\/td>Manage process conditions that may cause equipment damage or loss of integrity<\/td><\/tr>
              Technical basis<\/strong><\/td>Process hazards, equipment limits, process dynamics, safeguards, and consequences<\/td>Damage mechanisms, materials, corrosion\/degradation susceptibility, and equipment reliability<\/td><\/tr>
              Typical example<\/strong><\/td>Reactor pressure exceeds its approved process safety boundary<\/td>Chloride concentration exceeds a corrosion-control limit for a susceptible exchanger<\/td><\/tr>
              Immediate response<\/strong><\/td>Predetermined action to return the process to a known safe state<\/td>Assess breach, duration, and damage potential; implement defined integrity response<\/td><\/tr>
              API RP 754 Tier 3 classification<\/strong><\/td>Count a qualifying SOL excursion according to the applicable edition<\/td>Do not automatically count an IOW breach as an SOL excursion<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              The two systems should be coordinated. A single process variable can have both an IOW and an SOL, but the values and purposes need not be the same.<\/p>\n\n\n\n

              Example: corrosion-inhibitor dosing<\/strong><\/strong><\/h5>\n\n\n\n
                \n
              • The IOW may define a minimum dose necessary to control a particular corrosion mechanism.<\/li>\n\n\n\n
              • The SOL may define a lower boundary at which continued operation is no longer acceptable because the process safety risk requires predetermined action.<\/li>\n\n\n\n
              • A breach below the IOW but above the SOL requires the defined integrity response, but it is not automatically a Tier 3 SOL excursion.<\/li>\n\n\n\n
              • A breach below the SOL must be assessed and reported under the applicable SOL excursion criteria, even if the IOW breach began earlier.<\/li>\n<\/ul>\n\n\n\n

                This distinction does not permit indefinite operation below an IOW. Integrity risk may require immediate intervention, reduced throughput, or shutdown according to the engineering assessment and operating procedures.<\/p>\n\n\n\n

                7. Practical implementation in a petrochemical plant<\/strong><\/strong><\/h4>\n\n\n\n

                Maintain two linked registers: an SOL register managed through Process Safety and Operations, and an IOW register managed through Process Engineering and Mechanical Integrity. Both should be accessible to the control room and integrated with the process historian, alarm management system, MOC workflow, and incident reporting system.<\/p>\n\n\n\n

                  \n
                • Confirm SOLs remain consistent with current HAZOP\/LOPA, equipment design, and operating procedures.<\/li>\n\n\n\n
                • Verify alarm setpoints and protective functions provide the intended response before an unsafe condition develops.<\/li>\n\n\n\n
                • Capture IOW breaches even when they do not trigger a process alarm.<\/li>\n\n\n\n
                • Classify SOL excursions consistently using clear event-counting rules.<\/li>\n\n\n\n
                • Ensure repeat excursions lead to engineering improvements rather than repeated reliance on operator intervention.<\/li>\n\n\n\n
                • Require technical justification, approval, and traceability for changes to either set of limits.<\/li>\n<\/ul>\n\n\n\n

                  8. Conclusion<\/strong><\/strong><\/h4>\n\n\n\n

                  Defining SOLs is an engineering and process safety activity, not merely a KPI-setting exercise. Each limit must have a documented technical basis, account for process hazards and equipment capabilities, and specify the actions required when the boundary is crossed.<\/p>\n\n\n\n

                  API RP 754 provides a mechanism to use qualifying SOL excursions as Tier 3 indicators, enabling companies to identify challenges to safety systems before more serious events occur. Meaningful reporting depends on consistent definitions, reliable data capture, defensible event counting, and effective corrective actions.<\/p>\n\n\n\n

                  Integrity operating windows serve related but distinct purposes. Their excursions should be recorded and managed according to the applicable integrity-management procedure, while Tier 3 SOL reporting should be reserved for events that satisfy the applicable API RP 754 criteria. The objective is not simply zero reported excursions; it is technically sound limits, prompt detection and response, and elimination of recurring causes.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  1. Introduction Safe Operating Limits (SOLs) are a fundamental element of process safety management in petrochemical, refining, and oil and […]<\/p>\n","protected":false},"author":1,"featured_media":2964,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_uag_custom_page_level_css":"","_ppp_document_settings_meta":"{\"product_ids\":[{\"label\":\"Defining Safe Operating Limits (SOL) in Petrochemical Units - [#2961]\",\"value\":\"2961\"}],\"delay_restriction_enable\":\"\",\"delay_restriction\":\"\",\"delay_restriction_frequency\":\"day\",\"page_view_restriction_enable\":\"\",\"page_view_restriction\":\"\",\"page_view_restriction_frequency\":\"day\",\"page_view_restriction_enable_time_frame\":\"\",\"page_view_restriction_time_frame\":\"\",\"expire_restriction_enable\":\"\",\"expire_restriction\":\"\",\"expire_restriction_frequency\":\"day\",\"show_warnings\":\"\"}","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[20],"tags":[],"class_list":["post-2963","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-paid-articles","locked-post"],"acf":[],"uagb_featured_image_src":{"full":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",1600,900,false],"thumbnail":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",150,84,false],"medium":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",300,169,false],"medium_large":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",768,432,false],"large":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",1024,576,false],"1536x1536":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",1536,864,false],"2048x2048":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",1600,900,false],"woocommerce_thumbnail":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units-300x300.jpg",300,300,true],"woocommerce_single":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units.jpg",600,338,false],"woocommerce_gallery_thumbnail":["https:\/\/petrostreet.com\/main\/wp-content\/uploads\/2026\/10\/Defining-Safe-Operating-Limits-SOL-in-Petrochemical-Units-100x100.jpg",100,100,true]},"uagb_author_info":{"display_name":"Hussnain Ahmad","author_link":"https:\/\/petrostreet.com\/main\/author\/hussnainahmad983gmail-com\/"},"uagb_comment_info":0,"uagb_excerpt":"1. Introduction Safe Operating Limits (SOLs) are a fundamental element of process safety management in petrochemical, refining, and oil and […]","_links":{"self":[{"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/posts\/2963","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/comments?post=2963"}],"version-history":[{"count":1,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/posts\/2963\/revisions"}],"predecessor-version":[{"id":2965,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/posts\/2963\/revisions\/2965"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/media\/2964"}],"wp:attachment":[{"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/media?parent=2963"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/categories?post=2963"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/petrostreet.com\/main\/wp-json\/wp\/v2\/tags?post=2963"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}