FieldServer for OEM Overview

Copyright © 2014 Sierra Monitor Corporation

FieldServer for OEMs 2015.r2

• Founded in 1979 • Publicly listed - SRMC • HQ in Milpitas, Silicon Valley • Sales offices around the world

Sierra Monitor Corporation

PROTECT Fire & Gas

Detection Solutions

CONNECT Protocol

Gateways

SMC addresses the industrial and commercial facilities management market

with Industrial Internet of Things (IIoT) solutions that connect and protect high-

value infrastructure assets

Copyright © 2015 Sierra Monitor Corporation 2

3

IIoT Solutions Architecture


4

Market Leader


5

Trusted OEM Supplier


http://images.google.com/imgres?imgurl=http://www.discretewireless.com/interfaceimages/client/siemans.jpg&imgrefurl=http://www.discretewireless.com/clients/index.asp&h=113&w=150&sz=6&hl=en&start=16&tbnid=vqyD9P-4eJ-5fM:&tbnh=72&tbnw=96&prev=/images?q=Siemens+Building+Technology&gbv=2&svnum=10&hl=en

http://www.toshiba.com/tai/index.jsp

http://www.lutron.com/default.asp

http://ats.stulz.com/

http://www.rockwellautomation.com/encompass/

6

• Multiple Devices • AC Controls – HVAC Roof Top units • Boiler Controls – Steam – Hot Water • Energy BTU Flow Meters • Energy Electricity Demand Metering • Energy Management Systems - Panels • Commercial Dehumidifiers • Chillers • Lighting Control Systems • Fire Alarm Panels • Fume Hood Controllers • Security Panels • Air Handlers • Motorize Window Shading • Variable Frequency Drives • Control Systems • Distributed Control Systems • Gas Panels • Power Managers • Programmable Logic Controllers • Temperature Controllers

Buildings - “A Connectivity Dilemma”


Building Automation Protocols

7 Copyright © 2015 Sierra Monitor Corporation

8

Real-world Protocol “Soup”

Building Automation

Industrial Automation

Proprietary Fire Alarms

Utility/Energy

BACnet MS/TP BACnet/IP LonWorks KNX Metasys N2 Carrier McQuay ……

Modbus RTU Modbus TCP/IP Modbus + PROFIBUS GE-EGD EtherNet/IP DF1 ……..

CrestNet Siemens Canatal Weightronics Russelectric Honeywell …….

Siemens Edwards Notifier Vesda Simplex Fike Gamewell …….

EnergyWise DNP 3.0 DNP Ethernet SNMP XML M-Bus …….

FieldServer “speaks and converts” more than 140 protocols Unlocking information from valuable devices and assets


LOST revenue opportunities • Manufacturers that do not support automation protocols

has a big competitive disadvantage

Development COST of network protocols are high. • Often manufacturers core competence

does not include networking.

Development TIME for each protocol is long • 1-2 years from start to finish

High RISK of initial failure • Achieving product stability takes time

Implications for OEMs

FieldServer OEM approach provides rapid, cost-effective and reliable protocol implementation

for new and legacy devices


Example: Initial Protocol Development Cost

Protocols Development Time

in Months Engineering Labor Cost

Protocol Licensing

Software Development

Cost

BACnet MSTP 16 $208,000 $15,000 $223,000

BACnet IP 10 $130,000 $5,000 $135,000

KNX 16 $208,000 $20,000 $228,000

LonWorks 16 $208,000 $20,000 $228,000

Metasys N2 14 $182,000 $20,000 $202,000

Man Years 6 $1,016,000 +

$200,000 for HW development +

$100,000 for product certification +

Equipment for QA testing +

ONGOING SUPPORT


FieldServer OEM Solutions: Delivering Results

Accelerated Time-to-Market

Reduced Cost

Risk Reduction


• Industry leading implementation of 140+ different protocols Support beyond building automation

• Robust certified protocols BACnet BTL Certified, LonMark, ODVA, KNX, M-Bus…

• Multi-protocol support in any gateway Cost-effective implementation

• Complete turnkey solution with preprogrammed/tested solutions FieldServer technicians program all configurations

Ensures shortest time-to-market and eliminates trial and error

• “On-ramp” to the Industrial Internet of Things (IIoT) cloud Integration with dash boards, analytics, and other cloud applications

• The best support in the industry Custom User manuals

Webinar training for OEMs first line of support

Best practices from over 140,000 installed gateways

Why FieldServer?


13

BACnet/IP Backbone Example

BACnet IP BACnet MS/TP MODBUS RTU 140+ Other Protocols

?

How can I connect?


• ProtoNode Gateway External protocol gateway Supporting Serial, Ethernet, LonWorks, KNX, M-Bus translation BACnet BTL-Certified LonMark-Certified TUV and CE approved

• ProtoCarrier Gateway New and legacy products that need protocol support and

that cannot be redesigned Connects to RS485 or RS232 or Ethernet port of OEM’s device Supporting Serial, Ethernet, LonWorks, KNX protocol translation. BACnet BTL-certified LonMark-Certified TUV and CE approved

• ProtoCessor Embedded Gateway Two modules: FFP and ASP All use a common hardware and software interface OEM implements a Serial TTL ProtoCessor socket Supporting Serial, Ethernet, and LonWorks protocol translation BACnet BTL-certified LonMark-Certified

Flexible FieldServer OEM Options

Most flexible solution and fastest time to market

Fast time to market, housed in OEM enclosure

Full integration into OEM product: lowest cost


15

• Multiple BACnet Routing Connections BACnet/IP & BACnet MS/TP

BACnet MS/TP & BACnet Ethernet

BACnet MS/TP & BACnet MS/TP

BACnet/IP & BACnet/IP

BACnet/IP & BACnet Ethernet

• Ease of Use Web Based configuration: one page set and forget

NAT support with secondary BACnet/IP connection for routing between public and private IP networks

Foreign Device Registration (FDR)

BACnet Broadcast Management Device (BBMD) for a connection between different subnets

• Ease of Installation DeviceFind™ discovery feature for automatically finding connected devices

MDIX to use any Ethernet cable for commissioning & installation

DHCP to automatically obtain IP setting from the network

ToolBox to find and diagnose Routers on your network

Wide range of input power requirements AC or DC

NEW: FieldServer BACnet Router Stand-alone FieldServer

Software Option


16

BACnet Router Options

With BBMD the FieldServer BACnet Router can move data from the RS-485 trunk through firewalls and different subnets to the BACnet Client

The FieldServer BACnet Router can have up to 32 devices per RS-485 port. With two RS-485 ports 64 devices can be connected without the use of a line driver

Highlights • BTL Certified • Lowest cost per node • Highest speed • Single page configuration • DeviceFind™ discovery


17

• Easy to use

• One page configuration

• Fast start-up Up running “out of the box”

BACnet Router Configuration


18

• Unique DeviceFind™ feature

• BACnet router automatically detects all devices connected

No more “missed” devices

• Shortened start-up time

DeviceFind™ Discovery


19

BACnet Router Differentiation

BACnet Router Vendor BTL Serial ports

Device discovery

BACnet Ethernet

Devices supported

FieldServer Yes 2 Yes Yes 254 Contemporary Controls No 1 No Yes 127 Loytec No 1 No No 127 Control Solutions No 1 No No 127 Cylon No 1 No No 127 ADF Web No 1 No Yes 127 Cimetrics No 1 No No 127


FieldServer Protocol Translation Engine Field Side

Serial or Ethernet or LON Field

Network

Slave Master

• CSV mapped registers are stored and maintained in specific register locations in gateway

• If the gateway is a Master it will poll the OEM’s host devices and maintain the data array, with the latest values

•On the Field Side, gateway waits for a poll request from Front end to serve up the latest registers stored

OEM’s Device 1

• Common host protocol •Memory registers of OEM’s device gets

mapped to the desired field protocol properties via CSV config file

•Multiple host devices can be mapped to one or multiple Field networks

• CSV config file gets downloaded to gateway over Ethernet

Serial or Ethernet or LON

OEM’s Device 3

OEM’s Device 2

Device Side

Master or Slave

Slave or Master

ProtoCessor ProtoCarrier ProtoNode

Gateway


• FFP Modules BMS and IA Co-processors Supports common host software/hardware interface to OEM’s devices

• ProtoCessor socket 2x10 headers (TX-RX, 5v power, and ground)

High performance FFP ProtoCessor • 32 bit ARM 9 processor • 128 Mbyte RAM and 512 Mbyte

• Supports 1000’s of OEM’s preprogrammed product Profiles • Stores entire FieldServer protocol library

• CM/EMI/ESI protection on RS485 port • Optional Bluetooth via USB on Level II & III • SD card support for data logging on Level III

DIP switches for setting MAC Address, Node-ID, baud rate, selecting from multiple pretested stored configurations, enabling Auto-Discovery of known profiles

ProtoCessor Embedded Gateway


ProtoCessor Device/Field Supported Protocols

Field Supported Protocols: •Modbus TCP •AB EtherNet/IP •BACnet IP •GE-SRTP/GE-EGD •Modbus RTU/ASCII •BACnet MS/TP •AB DF1 •DNP3 Serial/Ethernet • SNMP •Metasys N2 • LonWorks •XML •Many more…

FFP-ETH

FFP-LON

ProtoCessor Device Protocols: •Modbus RTU/ASCII •BACnet MS/TP •AB DF1 •DNP3 Serial •Metasys N2 • PSP (ProtoCessor Simple

Protocol) • Custom OEM drivers

ProtoCessor Host Socket communication to OEM’s Serial TTL port

OEM Device

ProtoCessor TTL Socket

FFP-485

ProtoCessor TTL Socket


Complete Documentation for Embedding

ProtoCessor TTL socket

• Common hardware interface for ProtoCessor modules

• 2 x 10 pin headers

• TX, RX, 3.3 - 5V, and 0V


ProtoCarrier Device/Field Supported Protocols

Device Supported Protocols: •Modbus TCP •AB EtherNet/IP •BACnet IP •GE-SRTP/GE-EGD •Modbus RTU/ASCII •BACnet MS/TP •AB DF1 •DNP3 Serial • SNMP •Metasys N2 •KNX • LonWorks • PSP Protocol • Custom OEM drivers

Field Supported Protocols: •Modbus TCP •AB EtherNet/IP •BACnet IP •GE-SRTP/GE-EGD •Modbus RTU/ASCII •BACnet MS/TP •AB DF1 •DNP3 Serial/Ethernet • SNMP •Metasys N2 • LonWorks •XML •Many more…

ProtoCarrier supports more device protocols


• Preprogrammed OEM protocol gateways

• Dynamically supports multiple RS-485 and Ethernet known OEM Devices/Profiles Auto-Discovery or Web Configurator

• Automatically builds configuration files known OEM Devices/Profiles

• Product hardware options:

• Power requirement: 9-30Vdc or 12- 24Vac.

• Current draw @ 12V is 250 mA (max)

ProtoNode Gateways


• Multi protocol support

• Multi device support

• Static and Dynamic configuration

• TUV and CE approved

• Fastest time to market

• Largest protocol library available

• Largest point count available 10,000+

The Power of the ProtoNode


On-Site Configuration Options

Auto-Selector STATIC

• Pre-defined installations • DIP switch selections • Multiple protocols • Multiple products • No mix of products

Auto-Discovery DYNAMIC

• Plug-n-Play installations • Discovers devices • Multiple protocols • Multiple products • Mix of serial products

Web-Configuration DYNAMIC

• Fully flexible installations • Selectable devices • Multiple protocols • Multiple products • Any mix of products


• Supports 3 Products: Mascot II

NT 80 – 850

NT 1000 Boilers

• Provides Modbus RTU to: BACnet MS/TP

BACnet/IP

LonWorks

Auto-Selector Example: LAARS

Modbus RTU

BACnet MS/TP

BACnet/IP

BMS System


• Auto-Sector = Pre-Defined Static Configurations One part number supports:

• Multiple FIELD protocol options

• Multiple product lines

• Multiples of the same types of products (LAARS Ex: 1 through 8)

• Configurations are DIP switch selectable

Store up to 1000 pretested configurations • 1 device to 1 protocol = 1 configuration

• BACnet = 8 configs, Metasys N2 = 8 configs, Modbus TCP/IP = 8 configs For a total of 24 unique configurations

• Auto Selector configurations are NOT dynamic. Does NOT support mix of different products

Auto-Selector: Summary


Auto-Discovery Process


Auto-Discovery Configuration: • Auto-Discover serial products

Serial Protocols

Ethernet Protocols

Modbus RTU

Supports any mix of RS-485 meters: • Including multiples of any meters

• BACnet MS/TP • Metasys N2 • AB DF1

• BACnet/IP • AB EtherNet/IP • Modbus TCP/IP

Auto-Discovery Example: Electro Industries


• Auto-Discovery = Multiples of Mixed Serial Products One part number supports:



• Any mix of multiple serial products

Dynamically builds configuration from Device Profiles • 1 product = 1 Device Profile

• Store 1000 different profiles

• Auto-Discovery configurations are dynamic Provides support for ANY mix of different products Limitation: only supports serial products

Auto-Discovery: Summary


Serial Protocols

Ethernet Protocols

Modbus RTU

Supports any mix of RS-485 meters: • Including multiples of any meters

• BACnet MS/TP

• Metasys N2 • AB DF1

• BACnet/IP • AB EtherNet/IP • Modbus TCP/IP

Web-Configuration Example: Electro Industries

Modbus TCP/IP

Two methods of configuration: • Auto-Discover supported RS-485 meters • Web-Configurator for Modbus TCP/IP and RS-485 meters


Web-Configurator:

• Offers Modbus RTU / Modbus TCP Profiles for all 9 EIG meters.

• Used for Ethernet meters (Modbus TCP meters cannot be Auto-Discovered).

• Can also be used for any RS-485 meters (with or without Modbus RTU Auto-Discovery).

• Dynamically builds the required Configuration file.

Web-Configuration Example: Electro Industries


• Web-Configuration = ANY mix of products One part number supports:


• Multiple HOST protocol options, Serial + Ethernet


• Any mix of multiple products

Dynamically builds configuration from Device Profiles • 1 product = 1 Device Profile

• Store 1000 different profiles

• Used when OEM products do not have unique identifiers

• Auto-Configuration configurations are dynamic Provides support for ANY mix of different products Easy additions to existing installations

Web-Configuration: Summary


36

On-ramp to the IIoT

Cloud FieldServer connect any asset to the cloud

Device Level FieldServer connect any asset to any asset

Carrier DataLink

Fike Cheetah

KNX LonWorks® M-Bus

Profibus DP Slave Modbus RTU

Allen Bradley DH+

BACnet MS/TP

Metasys N2

IP Connectivity FieldServer connect any asset to IP

SNMP

BACnet IP

XML

DNP3 Ethernet

HTTP REST

Secutron

Veeder-Root

XML JSON


FieldServer Cloud Solution

Protocol X Protocol Y

IP Protocol Z

FieldServer InSite™ • Webserver with local

website • Auto generated apps • Configuration • Monitoring • Alarms • Custom apps

FieldServer Gateway

IP Cloud Protocol

SMC OpenSite™ • Same apps as “local

cloud” • Aggregation of many

gateways • Dashboards • Analytics • Long term trending • Advanced security • Custom apps

Cloud Engine for Visualization, Storage

and Analytics

SMC Cloud OpenSite™

IP Cloud Protocol

FieldServer Gateways

…


• The OEM provides the register list for all controllers

• FieldServer programs all the OEMs different controllers for required protocols

• FieldServer creates a specific part number for the OEM • First test sample is shipped with all the

configurations/Profiles for different OEM product line • Meeting scheduled – one hour Startup review to walk

through validation of configurations (phone or webinar) • FieldServer provides a custom user manual

that the OEM can provide to their customers explaining how to install their products and the various protocols

OEM Engagement Process

Over 190 OEMs selected FieldServer OEM products as their platform


39

• Accelerated Time-to-market Cut time-to-market by more than 50-90% Very little protocol knowledge is required

• Reduced Cost Development cost reduced by more than 70% Little or no engineering is required – no new headcount One SKU supports multiple controllers and multiple protocols

• Risk Reduction Turn-key and pre-tested implementation minimize errors Customized documentation reduces start-up problems – no trial and

error On-going support ensures products are up-to-date with latest

standards Strong driver library with over 140 different protocols implemented

FieldServer OEM Summary


Thank You!


Business

FieldServer for OEM Overview