Case Study & Next Steps

1. Case Study & Next Steps Rob Coulter

2. Case Study • North American operator • Transportation, gathering, marketing and storage • Crude Oil, LPG • 3,000+ miles of active gathering and mainline pipeline systems

3. Project Goals • Reduce the latency of critical control and process data (<15 sec) • Improve leak detection performance (reduce false alarms) • Enable a Measurement Upgrade Project • Ease the migration and integration of new pipeline acquisitions • Provide better, faster, and more accurate information to lines of business • Provide the ability to play back any level of field information into leak detection and training applications • Enable/Integrate automatic cathodic protection rectifier measurement data • Provide secure remote access to field devices • Be ready to implement a level of security as recommended by the US National Institute of Standards and Technology (NIST) • Provide an architectural framework where all systems can access all of the real time SCADA information • Do all of this without affecting the operational safety, security, or integrity of the primary SCADA Host application.

4. Project Steps • Upgrade Field Communications Hardware • Install appropriate “edge of network” devices while maintaining all current poll/response processes. • Install and Configure a Message Broker • Implement poll/response processes in the “edge of network” devices in parallel with legacy poll/response from the SCADA Host application. At this point the system can support both the publish and subscribe transport as well as the legacy poll response. • Transition the SCADA Host Application to be a client of the Message Broker • Elimination (on a device by device basis) of the poll/response mechanism currently used to a pure publish and subscribe transport – by the completion of this phase the latency goals for all directly connected devices should be met • Leverage Infrastructure and Data Analytics for Other Business Applications • Provide the ability to start looking at other data and/or devices that currently reside in the field locations. Start to access additional information that is not currently required by operations and is therefore left stranded in the field and use it for better threat detection, planning and logistics, and preventive maintenance.

5. Phase 1 • Review of Current Operational Infrastructure 3 days • SCADA and enterprise IT • Identify first implementation target • Identify future needs of data consumers / producers • In-depth examination of existing equipment 7 days • PLC’s, RTU’s, flow computers, smart transmitters, cathodic protection rectifiers, tank gauge transmitters, etc. • Protocols in use and protocol capabilities • Physical device communications capabilities (Ethernet, RS-232, RS-485, USB, etc.) • Network topologies and security mechanisms • Full data-mapping • MQTT Proof of Technology simulation

6. Migration Strategy • Provide a high level transition timeline • Identify and document any risks and issues • Identify other data producers / consumers • Provide a recommendation on Gateway/Edge devices or direct device enablement to provide MQTT message transport to a selected field device • Provide future state topology for OT/IT integration • Provide a recommendation on next steps

7. Satisfying Multiple Applications

8. Next Steps Consider how this technology could help your organization Join mqtt.org Contact your IBM representative or one of the firms represented here today