Using New Wiring

Methods in SPI

Nezar M. Faitouri

Mangan SPI Group Manager

SPI SME

Agenda

• Foundation Fieldbus

FFB Multi-Input Device

• MOV’s, EIV’s, etc

No Device Panel Configurations

• Ethernet

FTA to IO Card/Controller Connection

• DeltaV

Charms

• Wireless

Wireless devices with Smart Wireless Field Link and

WIOC

FFB Converters

• FFB Converters are Fieldbus Converters to convert

conventional signals to Fieldbus

• Ex: Emerson “848T”, Smar “IF302”, etc

FFB Multi-Input Device

• For SPI: Signals connected to FFB converters are Conventional (regular

Device Panels)

Fieldbus converters are FFB (Multi-Input Device Panels). Should

have SPI function blocks (Ex: 8 AI)

Conventional signals gets associated to the function blocks

The segment IO shows all signals connected to the FFB converter

Signals connected to FFB converters should not be associated to

FFB segments in SPI. Only true FFB devices should be associated

to FFB segments

FFB Multi-Input Device

• Conventional Tag (TE type J)

• Fieldbus Tag (TT type 848T)

FFB Multi-Input Device

• FFB Segment, Tags, Function Blocks, and IO Association

FFB Multi-Input Device

• SPI Fieldbus Loop for 848T:

FFB Multi-Input Device

• SPI Conventional Loop for TE:

FFB Multi-Input Device

• SPI Fieldbus Segment:

FFB Multi-Input Device

• Report Challenges:

Conventional loop does not show the entire connections

(conventional and FFB)

Fieldbus loop does not show the conventional connections

Fieldbus Segments gets crowded with the amount of wiring items

and make it difficult to organize or read the data

• Solutions:

– Utilize the Strip Signal report

– Utilize the Panel Signal report

– Intergraph to enhance/add reports to overcome these challenges

» Option to generate conventional and FFB in one report

» Option to only show 848T (Multi-Input device) connection

on segment drawings (exclude conventional signals)

FFB Multi-Input Device

• Strip Signal Report and Panel Signal Report:

MOV’s, EIV’s, Etc

• These type of Valves and its signals are integrated (One

Device)

• Ex: TOPWORX “DXP0X1YMEB”, MERSON “500”, etc

MOV’s, EIV’s, Etc

• For SPI

Build the standard loop and tags (MOV, ZSC, ZSO, etc)

MOV instrument type profile should not have any wiring

Accessory tags (ZSC, ZSO, etc) should have the instrument type

profile for wiring; however, No device panel defined

MOV’s, EIV’s, Etc

• Build the MOV as a Cabinet

Build the MOV connection strip either as a regular strip or

Apparatus

For simplicity, build the MOV strip as a regular strip

MOV’s, EIV’s, Etc

• Make the necessary connections and signal propagations

• Signal propagation is by drag and drop from domain

explorer to wires or by local signal function

MOV’s, EIV’s, Etc

• Reports:

MOV’s, EIV’s, Etc

• Why not use SPI Device Panels for accessory tags?

Have to edit terminal numbers for each device panel to reflect

MOV connection strip terminal numbers

Accessory tags are not true field devices. They are internal to the

MOV or EIV, etc

Reports shows each accessory as a separate strip instead of one

block (one strip)

It is never recommended to have accessory signals generated

from a MOV device panel (one device panel with multiple

signals)

Ethernet

• Ethernet is a plug in cable that could be used to connect

between FTA’s and IO Cards/Controllers

• Ethernet could also be used with other type of connections

such as Controllers to Systems, etc

Ethernet

• For SPI

For simplicity, Ethernet connection between FTA (IO

Termination) and IO card should not be made.

SPI FTA’s can be associated to IO cards and the Ethernet cable

name can be documented as well (System Cable)

For visibility of drawings, the Ethernet connection can be built

» Regular Cable and Connections between FTA and IO Card

» Connector (Plug) Cable and Connections between FTA and

IO Card

Ethernet

• Connection using a Regular Cable

Cable – Sets – Wires

Regular strip for FTA and IO Strip for IO Card

Ethernet

• Connection using a Connector Cable

Cable – Sets – Wires - Connector

IO strip for FTA and Connector for IO Card

DeltaV - Charms

• The DeltaV Charms allows for Electronic Marshalling in

the Field

• The Electronic Marshalling connection to the Controller is

either via Ethernet or Fiber Optics

DeltaV - Charms

• For SPI:

Use the SPI - DeltaV Charms interface catalog IO card

» 1 IO card per base plate with 1 channel per strip and a sub-

wiring equipment (up to 12 IO cards per baseplate)

Design it:

» Multiple IO cards per base plate with 1 channel per strip (up

to 12 IO cards per baseplate)

» 1 IO card per base plate with multiple channels (up to 12

channels per baseplate)

DeltaV - Charms

• Using SPI Catalog IO Card

Pros:

• Ability to reflect field configuration

• Ability to document card model and

type, TB model using Card and

Strip fields

Cons:

• Every Charm IO will have its own

individual report

• IO Assignment Report

• Strip Reports

• Panel reports

• Having to connect each

channel one at a time

DeltaV - Charms

• Multiple IO Cards per Baseplate

Pros:

• Ability to reflect field configuration

• Ability to document card model and

type, TB model using Card and

Strip fields

Cons:

• Every Charm IO will have its own

individual report

• IO Assignment Report

• Strip Reports

• Panel reports

• Having to connect each

channel one at a time

DeltaV - Charms

• 1 IO Card per Baseplate

Pros:

• One Report for each Charm IO

Baseplate

• IO Assignment

• Strip Reports

• Etc

• Simplicity to connect multiple

channels

• Somewhat, Ability to reflect field

configuration

Cons:

• Somewhat, inability to reflect field

configuration

• Inability to document card model

and type, TB model using Card and

Strip fields

Wireless

• It is unfortunate at the moment that SPI does not support

Wireless; however, when there is a will, there is always a

way

• How to in SPI?

Custom Symbols

Custom Drawings

Connections

• Custom symbols and custom drawings are time

consuming. Not to mention, requires training

• By default, most SPI users know how to make

connections

Wireless

• SPI Wireless using Connections

Using Emerson DeltaV WIOC with an IO type of Wireless

Using Smart Wireless Field Link (Multi-Input Device)

Using Conventional instruments in SPI with an IO type of

Wireless

Wireless

• The Smart Wireless Field Link is developed as a SPI

Multi-Input Device

– It is the only conventional way to have conventional tags

assigned to 1 IO Channel

Wireless

• The connection between Wireless Devices and the Smart

Wireless Field Link is a user defined cross wiring cable

– It is the only way to utilize layouts and change the representation

of the wires (from solid line to dashed line)

Wireless

• Repots:

– Loop Drawing for Wireless Devices

– Loop Drawing for Smart Wireless Field Link

– Panel Strip Signal Report for the Smart Wireless Field Link

Wireless

• Wireless Device Loop (FT or LT)

– Dashed lines represent Wireless

Wireless

• Smart Wireless Field Link Loop

– Dashed lines represent Wireless

Wireless

• Panel Strip Signal

– Dashed lines represent Wireless

Questions