How iFluids Engineering Built a Behaviour Based Safety Program for a Petrochemical Complex in Assam

A leading petrochemical and polymer complex in Assam, India, engaged iFluids Engineering to design a site-wide Behaviour Based Safety (BBS) observation program. The complex runs an integrated cracker and downstream polymer operation, an environment where unsafe acts, not equipment failure alone, drive most recordable incidents. iFluids delivered a formally approved BBS Observation Procedure built around a six-step field observation cycle, an Activator-Behavior-Consequence (ABC) root-cause framework, and a site-specific observation card. The program was aligned with OSHA 29 CFR 1910.119 and the CCPS/AIChE Risk Based Process Safety guidelines, and structured for rollout across every plant and non-plant area, from process units to stores, warehousing, and material handling zones.

Field	Detail
Sector	Petrochemical (Olefins Cracker and Polymer Manufacturing)
Location	Assam, India
Facility Type	Integrated cracker and polymer complex
Client	A leading petrochemical and polymer complex in Assam, India
Scope of Work	Design and documentation of a site-wide Behaviour Based Safety (BBS) Observation Procedure
Standards Applied	OSHA 29 CFR 1910.119, CCPS/AIChE Risk Based Process Safety (2007), Indian Factory Act 1948, Assam State Factory Rules
Project Duration	Procedure developed, reviewed, and formally approved.
iFluids Team Size	Multi-disciplinary HSE and process safety engineers

The Engineering Challenge

iFluids identified that the client needed a structured field methodology to convert safety intent into daily, observable practice, not another audit layer. The scope covered every operating and non-operating zone on site, from cracking and polymer units to loading and unloading bays.

The complex’s leadership recognized a gap common to sites that already run mature Process Safety Management systems: procedures and permits controlled the technical hazards well, but day-to-day worker behavior, how a valve was reached, whether a permit condition was actually verified in the field, how housekeeping was maintained after a job, remained largely undocumented and unmeasured. Without a formal observation methodology, at-risk behaviors such as climbing pipe racks to reach elevated valves, bypassing lockout steps under time pressure, or ignoring a standing alarm on the DCS panel could persist unnoticed until they escalated into an incident.

The client also needed the program to sit inside its existing management system rather than beside it. That meant integrating BBS with the Integrated Management System, Workplace Safety Procedures, confined space entry and hot work permits, and the site’s Cardinal Rules, so that a BBS round would surface Process Safety Management gaps as readily as it surfaced a missing hard hat. Any procedure that treated behavior observation as a standalone checklist exercise would have missed that integration requirement entirely.

There was also a measurement problem underneath the behavioral one. Lost-time cases, medical treatment cases, and first-aid cases sit above the surface of a much larger set of unrecorded at-risk acts, near-miss conditions, and procedural shortcuts, the kind of iceberg pattern well documented in process safety literature. Without a structured observation tour, the client had no consistent way to see that larger base, meaning corrective action stayed reactive, triggered by an incident rather than by an early behavioral signal.

iFluids’ Approach and Methodology

iFluids Engineering delivers Behaviour Based Safety programs that translate CCPS Risk Based Process Safety principles into a field-ready observation cycle, built around structured coaching rather than fault-finding. For this complex, the deliverable was a formally documented, role-mapped BBS Observation Procedure ready for site-wide rollout and training.

The engagement followed a defined methodology:

1. Mapped organisational ownership. iFluids defined responsibilities across the COO/Site Head, Plant Head, Safety Head, Site BBS Steering Committee, and Plant BBS Teams, so accountability for scheduling rounds, gathering data, and closing actions sat with named roles rather than a generic safety department.
2. Structured the field interaction as a six-step cycle. Observers plan and observe the task, approach the crew through the team leader, appreciate safe behavior while discussing any at-risk act observed, secure a genuine agreement to work safely, invite discussion of other safety concerns, and close with thanks, deliberately avoiding the tone of an inspection or audit.
3. Built a structured data flow. Observation data feeds a weekly analysis cycle covering plant, department, and contractor-wise breakdowns, position-wise round compliance, safe-versus-at-risk trends by category, and closure status against assigned action owners.
4. Embedded root-cause analysis. Repetitive or fatality-potential at-risk behaviors are escalated into a Total Quality Management-based improvement loop: identify the critical behavior, identify root causes, generate and evaluate potential actions, develop an action plan, implement it, and confirm the problem is resolved before closing the loop.
5. Issued a standard field observation card. A single form captures reaction of people, position and line-of-fire risk, PPE compliance, tools and equipment condition, procedural adherence, housekeeping, and process safety indicators such as bypassed interlocks or unattended alarms, giving every observer a consistent, auditable record.
6. Wrote a 21-point field discipline for observers. The procedure specifies practical rules that shape whether a BBS round produces honest data or a defensive reaction: observe employees working before initiating any discussion, avoid visible note-taking that puts workers on edge, ask questions rather than deliver lectures, and route observations with fatality potential straight to the HOD and HSE head by phone as well as through the written record.

This structure let the client’s own supervisors and managers run the program, rather than depending on iFluids or any external party to sustain it after handover. It also closed the loop end to end: the BBS work flow moves from observing a critical activity, through identifying the critical behavior and giving direct feedback, to analyzing the barrier preventing safe performance, removing that barrier, and repeating the cycle until safe practice holds.

Technical Decisions and Engineering Rationale

iFluids’ technical judgment shaped how the procedure would actually change behavior in the field, not just document it, centering the design on the Activator-Behavior-Consequence model rather than a bare compliance checklist. That single decision determined whether root causes, not just symptoms, would be surfaced and corrected.

A generic BBS rollout would have stopped at listing unsafe acts. iFluids instead built the procedure around ABC analysis, because consequences that are soon, certain, and positive shape behavior far more strongly than distant or uncertain ones, including negative outcomes like injury. The procedure’s worked example, an operator climbing pipework and handrails to reach an elevated valve with no platform available, illustrates the point: the antecedents included heavy workload, poor task scheduling, insufficient lifts and ladders, and a crew culture that treated climbing as a shortcut worth taking. The consequences reinforcing that behavior were immediate and mostly positive: the job got done faster, breaks came sooner, and production pressure eased, while the risk of a fall remained uncertain and comparatively distant.

That analysis drove a specific engineering trade-off. Rather than relying on a poster campaign or a one-time toolbox talk, the corrective action plan targeted both sides of the equation: antecedent interventions such as better lift and ladder scheduling and severity-of-falls training, paired with consequence interventions such as standardized break lengths and increased observation coverage during the shifts where the behavior was most common. Addressing only the unsafe act, without correcting the antecedents and consequences sustaining it, would have produced a short-lived improvement at best.

iFluids also assigned every action item a named owner, typically a department manager or shift supervisor, and a defined completion window, then built a 30-day follow-up review into the action plan itself. That decision reflected a deliberate rejection of the more common approach, where a BBS round generates a list of findings that gets filed and forgotten. Pairing each root cause with an accountable owner and a review date was what made the ABC framework operational rather than academic.

Deliverables from the Engagement

iFluids delivered a complete, ready-to-train BBS Observation Procedure package, not just a policy document, giving the client every artifact needed to launch and sustain the program internally. Each deliverable maps to a specific standard or methodology referenced throughout the engagement.

Deliverable	Standard / Methodology	Outcome
BBS Observation Procedure (formally documented and revision-controlled)	OSHA 29 CFR 1910.119, CCPS/AIChE RBPS	Approved as Revision B1 and issued for site-wide rollout
Six-step field observation cycle (Observe, Approach, Discuss, Agree, Discuss Other Issues, Thank)	Internal Workplace Safety Procedure alignment	Adopted as the standard method for every BBS round on site
Site-specific Safety Observation Card (seven-category field form)	RBPS-aligned, process-safety inclusive	Issued as the standard data-capture format for plant and non-plant areas
ABC root-cause analysis framework, with a worked field example	TQM-based root-cause methodology	Adopted for diagnosing and correcting repetitive at-risk behaviors
Weekly and position-wise BBS data analysis methodology	RBPS continuous improvement principles	Established as the standing review cadence for the Site BBS Steering Committee

Beyond the documents themselves, the procedure specified the training obligation needed to operationalize it: every level of employee, from the COO/Site Head to contractor supervisors, required induction into the six-step process before conducting or receiving a BBS round, with the Safety Culture task force responsible for maintaining the training calendar. The procedure also defined a governance rhythm: weekly BBS observation analysis to check the program’s functioning, monthly reviews with the site’s Risk Based Process Safety steering team, and a fixed cycle for revisiting the procedure itself, so the deliverable remained a living document rather than a one-time report.

Lessons and Applicability

The engagement reinforced that a BBS program only holds up if it is engineered into the site’s existing safety management system from the outset, not bolted onto it after launch. That principle applies to any high-hazard facility running mature Process Safety Management, not only cracker and polymer operations.

Two decisions carried the most weight. First, mapping ABC analysis to real field scenarios, rather than presenting it as an abstract behavioral model, gave supervisors a method they could apply directly to the next at-risk act they observed. Second, tying the observation card’s process-safety category, covering bypassed interlocks, exceeded operating limits, and unattended alarms, to the same form used for PPE and housekeeping meant DCS operators and process engineers were included in the program alongside field crews, not treated as exempt from it. We are a global authority in process safety and risk engineering, and that perspective shaped a procedure built to function as an extension of the client’s Risk Based Process Safety framework rather than a parallel behavioral initiative.

The same structure is directly applicable to other integrated petrochemical, refining, and gas processing sites across India and Southeast Asia that already operate under OSHA-aligned or equivalent process safety management systems and need a field-level mechanism to close the gap between procedural compliance and daily worker behavior.

Conclusion and Next Steps

iFluids Engineering delivered a fully documented, standards-aligned BBS Observation Procedure that gave this Assam petrochemical complex a structured, sustainable method for correcting at-risk behavior before it becomes an incident. The engagement produced a revision-controlled procedure, a site-specific observation card, an ABC root-cause framework, and the data-analysis methodology needed to keep the program active long after handover.

For engineering teams running high-hazard facilities, the lesson carries directly: behavior observation only works when it is designed as part of the plant’s Risk Based Process Safety framework, not layered on top of it. Facilities considering a similar program should start with the same question iFluids asked at this site: which specific at-risk behaviors, mapped to which specific consequences, are most likely to precede the next incident.

Explore iFluids Engineering’s Behaviour Based Safety methodology and process safety management framework, or contact iFluids Engineering to discuss a BBS observation program for your facility. For related engineering support, see our engineering design and consulting services.