SIS Integration Is Messy

AMS OPs OPC ENGIN. SOE.

SOE Bus
Engineering Bus
OPC Bus

Safety Bus
Serial Bus

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 1

 33 Integration With DCS
 Integration with DCS must be easier, cheaper and less risky
– Don’t want to use OPC
• OPC Mirror
• Mapping of points
• Redundant Servers
• 3rd party software is risky
• documentation and testing of interface is eliminated
• failure mode of solution
– Don’t want to use Modbus
• hardware and software is a pain as stated above
 Other desires
– Eliminate SOE integration; time synch, etc
– Eliminate Overall Alarms Management System
– Eliminate Separate Engineering Know-how and workstations
– Lower inventory costs – fewer parts
– Fewer parts to maintain
– Easier/faster training
– Simplified maintenance

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 2

 Flexible Architecture
 Be able to spread over a wide geographical area
without a high entry price at each location

 Be able to expand on-line

 Be able to have large applications or small

applications with the same components

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 3

 Ease Of Use
 Make it easy to deploy a SIS safely
– not very easy with many current suppliers
– make it easy to deploy
– minimize system maintenance

 Make Regulatory Compliance Easy

– Equipment to be certified to IEC 61508
– make it easy for me to follow IEC 61511

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 4

 What is Required is
“Integrated yet Separate”

Customers want “Integrated”

SIS
? DCS

IEC61511 specifies “Separate”

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 5

 Strategy
 Build a SIS that takes advantage of digital
communications to increase diagnostic coverage
 Extend PlantWeb Technologies to SIS (Device
Alerts, AMS Diagnostics etc)
 Monitor the entire loop – from measurement to
final element
 Use Industry Standard Protocols
 Deliver the “Integrated yet Separate” requirement

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 6

 Digital Communications have great
potential
 Safer than systems of the past due to knowledge
of the health of the field devices using smart
digital protocols

HEALTH

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 7

 Technology Adoption
Ref: Geoffrey Moore Inside the Tornado’, 1995

betamax

Inn Ea Ea La La
ov rly rly te gg
ato Ad Ma Ma ard
rs op jo r jor s
t er i ty i ty
s
One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 8
 HART or FIELDBUS First? = will adopt

All will use not all will

HART do Ff

DCS Community DCS Community

most will few will do

use HART Ff

SIS Community SIS Community

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 9

 HART or FIELDBUS First? = will adopt

All will use not all will

HART do Ff

DCS Community DCS Community

t h e n F i el db us
H A RT firs t,
IO N:
CONCLUS most will few will do
use HART Ff

SIS Community SIS Community

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 10

 Requirements For SIS
Requirements Desires
 Safety  Common Look and Feel for
 Availability Engineering with DeltaV
 TUV SIL approval
 Configuration using CEM (Same
as design documentation)
 Be unchanged when DeltaV
upgrades
 Mix Safety and Process in same
location
 Must consider health of field
devices
 Support for H1
 Must be easy to deploy and
 Cost position must competitive with
maintain major player offerings
 Easy integration with DeltaV
 Use same security database as
DeltaV
 Transparent connection to DeltaV
HMI

One Step Beyond, Sales Training, Emerson Confidential 2003, Slide 11