Libanio de Souza (Smar) discusses integrating ROM into an existing pilot plant at Petrobras CENPES facility. The ease of integration made implementing ROM a great success.

1. 1
Março 2012
© 1994 – 2011 Fieldbus Foundation
Interoperable ROM DCS Integration
Libanio de Souza
(Smar DCS Integration Leader)

2. 2
Março 2012
© 1994 – 2011 Fieldbus Foundation
Start Point
DCS system with H1 and Profibus Equipment integrated with
Smar DFI302 controllers and Smar I/O cards.

3. 3
Março 2012
© 1994 – 2011 Fieldbus Foundation
Final Solution : Interoperable ROM DCS Integration
DCS system with H1 and Profibus Equipment integrated with
Smar DFI302 controllers and Smar I/O cards
+ Wireless Hart; ISA - SP100 Devices; H1 devices;
conventional devices; ROM devices from diferrent manufactures.

4. 4
Março 2012
© 1994 – 2011 Fieldbus Foundation
Tools for interoperability
Field Device A
Enhanced
DD Tokenizer
DD
Binary A
CFF
Source A
Interoperable ROM DCS Integration
ROM Device

5. 5
Março 2012
© 1994 – 2011 Fieldbus Foundation
Association Block Concept
The Association Block is used to support the modular ROM
devices.
Interoperable ROM DCS Integration

6. 6
Março 2012
© 1994 – 2011 Fieldbus Foundation
Association Block Concept
Standardization
Without loosing
flexibility to
describe
different hardwares
Smar DF302
ROM device
Rack/ Slot
Interoperable ROM DCS Integration

7. 7
Março 2012
© 1994 – 2011 Fieldbus Foundation
Association Block Concept
Standardization
Without loosing
flexibility to
describe
different hardwares
STHAL IS
ROM device
Card number
Interoperable ROM DCS Integration

8. 8
Março 2012
© 1994 – 2011 Fieldbus Foundation
The Association Block is used to configure
the hardware components. Each application requires different
combination of hardware modules.
Interoperable ROM DCS Integration

9. 9
Março 2012
© 1994 – 2011 Fieldbus Foundation
The Association Block is
also used to monitoring
the actual installed
hardware components.
Expected/Actual/Status
per hardware
component.
Interoperable ROM DCS Integration

10. 10
Março 2012
© 1994 – 2011 Fieldbus Foundation
The component configured in the Association Block point to a
transducer block that represent that type of hardware module.
Interoperable ROM DCS Integration

11. 11
Março 2012
© 1994 – 2011 Fieldbus Foundation
For each hardware type
there is a transducer block
with a number of I/O
points with a defined
direction for each I/O
point.
Interoperable ROM DCS Integration

12. 12
Março 2012
© 1994 – 2011 Fieldbus Foundation
VAR_NAME : I/O name in the transducer.
CHANNEL_TAG : association with I/O name ( VAR_NAME) in the
Function Block.
Interoperable ROM DCS Integration

13. 13
Março 2012
© 1994 – 2011 Fieldbus Foundation
New Function Blocks with
one I/O parameter with
multiples I/O values inside.
One variable carries up to
64 binaries values.
Interoperable ROM DCS Integration

14. 14
Março 2012
© 1994 – 2011 Fieldbus Foundation
MAI_16 and
MAO_16 for
multiples analog
values
Interoperable ROM DCS Integration

15. 15
Março 2012
© 1994 – 2011 Fieldbus Foundation
Interoperable ROM DCS Integration
MBI_64 and MBO_64 for multiples binary values.

16. 16
Março 2012
© 1994 – 2011 Fieldbus Foundation
Interoperable ROM DCS Integration
Flexible Function
Block supporting new
data type (multiples I/O
data type).

17. 17
Março 2012
© 1994 – 2011 Fieldbus Foundation
Interoperable ROM DCS Integration
The same link concept
of H1, now is used for
the new data type
carring 16 or 64 I/O
values.