Spotlight

Preparing for API RP 1173

Overview:
Many companies are preparing to
implement API RP 1173
Based on previous management
systems, many will make 3 crucial
mistakes in how they adopt it
These mistakes will increase
complexity & cost, while diminishing
the systems effectiveness

Are you ready?

3 common mistakes to avoid in
preparing for API RP 1173
Thus many companies will implement RP
1173 in combination with other MSs such
as ISO 9001 for quality, ISO 14001 for
environmental, Lean for cost control, and
many more. The problem with this
approach is that good performance in all
of those areas requires doing the same
things. This leads to substantial
duplication, overlap and complexity. A
better approach is to utilize a single
integrated MS with no duplication that
meets all external requirements.

The American Petroleum Institute issued

their recommended practice 1173, which
establishes a pipeline safety
management system framework for
companies operating hazardous liquids
and gas pipelines within the US.
Much like many management system
frameworks before it, 1173 establishes
requirements that when applied, should
reveal and manage risk, promote a
learning environment, and continuously
improve pipeline safety and integrity.

most of the value of having a

management system is lost because, in
practice, it becomes a reactive rather
than proactive system.

3. Ignoring the effect of culture

A Management system cannot be
effective in isolation its success
depends on the type of culture that will
either suppress or embrace it. Many
management systems including APIs RP
1173 have recognized this dependence
and emphasized leadership and culture.
Despite their emphasis though, their
approach continues to emphasize a
separate safety culture. This approach
typically fails to really address cultural
issues, often creating more confusion and
limiting the potential of the management
system.

Figure 1: Common approach using multiple

management systems

2. Treating the MS like an additional

procedure rather than a system

3 Mistakes Companies Will Make

There is no single approach for
implementing a MS that is ideal for all
companies, but there are some
approaches that will not work for any
company. Our experience shows that
these are some of the most common
ways to sabotage your MSs effectiveness
and introduce additional complexity.

1. Thinking that more is better

APIs RP 1173 is a Pipeline Safety
Management System. While safety is an
important objective, most companies also
seek good performance in quality,
environmental performance, cost, etc.
Wilson Perumal & Company Inc.
(972) 716-3930
One Galleria Tower
13355 Noel Road, Suite 1100

Party due to the same mentality driving a

belief that you need a MS for safety
separate from one for quality,
environmental, and others, many
companies will implement RP 1173 as a
series of additional processes necessary
to safely operate their pipeline.

Making API RP 1173 Count

This translates into how the system is

developed, implemented and managed in
three ways. 1) There is typically less
involvement from the correct
stakeholders because ownership is
blurred. 2) There is less room to
accommodate for risk and prioritization
at the business unit level. 3) The system
is not utilized systematically, and thus

Implementing any MS requires a

significant commitment of resources, so
if you are thinking of implementing RP
1173, make sure that commitment is
worthwhile. Call us today to avoid
making the same mistakes others will
make. We can help you avoid those
mistakes while finding the optimal
solution for your organization.

Figure 2: Example results of MS Performance

Assessment

www.wilsonperumal.com
contact@wilsonperumal.com