Industrial Roots

1
Industrial Roots

• Benson Hougland, Opto 22
• Arlen Nipper, Arcom
• Jeff Smith, SensorLogic

2
The Industrial Roots of M2MA Case History

• Benson Hougland
• Vice President
• Opto 22

3
The Lessons Learned

• When considering options for device connectivity
  in M2M, consider these attributes
• Reliability
• Experience
• Versatility
• Simplicity
• Most importantly, look at the entire picture

4
Connecting Remote Assets
5
All things considered

• Business processes
• Alarms and notifications
• Reporting
• Real-time viewing
• Host application
• Hosted or On-premise
• Communications
• Device connectivity

6
Components of an M2M app
Hosted or on-premise software application
Wireline orwireless network
Device connectivity
Asset, machine, or environment
AnalogDigital Serial
7
Choosing device connectivity
Hosted or on-premise software application
Wireline orwireless network
Device connectivity
Asset, machine, or environment
8
True cost of remote failure?
9
Industrial Systems
Designed from experience for extreme environments
Low or no tolerance for failure Withstands
widely varying environmental conditions Less
susceptible to RF and EMI noise No user
intervention required Low cost, versatile,
reliable
10
Industrial Requirements
Industrial RemoteInput/Output Systems
Built-in networking multiple protocols
Simple andeasy-to-use
Intelligent, modularand versatile
Rugged and Robust
11
The Lessons Learned, Redux

• When considering options for device connectivity
  in M2M, consider these attributes
• Reliability
• Experience
• Versatility
• Simplicity
• Most importantly, look at the entire picture

12
Thank you

• Benson HouglandVP Marketingbensonh_at_opto22.comht
  tp//m2m.opto22.com

13
(No Transcript)
14
SCALematics The Transition to M2M Technologies

• Arlen Nipper
• President
• Arcom

SCALematics SCADA, Telemetry, and Telematics
Technologies
15
The M2M Evolution
In a Perfect Storm of technology adoption, M2M
is leveraging modern Internet technologies and
infrastructures with mature IT middleware and
solutions to address the Enterprises desire for
better utilizing operational assets and their
associated information.
16
7 Technologies Impacting M2M

• Open Protocols and Data Representation
• One to Many Data Distribution Models
• Scalability/Availability
• Device Management
• Tools on Platforms versus Coding on Operating
  Systems
• Security
• Mature IT Solutions

17
Open Protocols and Data Representation

• Embracing TCP/IP protocol standards

• Well understood and documented
• Diagnostic and trouble shooting tools readily
  available
• Flexible network topologies (physical network
  independence)
• Leverages available public infrastructures

• XML data representation

• Accepted as a de-facto standard across the
  enterprise
• Many available tools (editors, databases,
  visualization, transformation)

18
One to Many Data Distribution

• (Breaking out of the SCALematics Data Cage)

M2M technologies let customers implement
infrastructures with a focus on making data
useful and widely accessible within the
enterprise. Historically, SCALematics systems
concentrated on executing projects getting
proprietary data from point A to point B
resulting in a One to One data ownership.
19
Scalability/Availability
M2M technologies and devices combine to provide
superior network scalability with associated
availability. The same infrastructure fabric
can be applied from barbwire to broadband with a
common backend architecture and tooling. This is
in contrast to the patchwork quilt of
SCALematics distinct islands of automation for
each network topology and application.
20
Device Management
M2M devices provide the notion and ability to
perform large scale device management. This is an
absolute requirement for changing business needs
in conjunction with lifetime device stewardship
(OS updates, application updates, security
updates, etc). Gone are the SCALematics days of
software management with a tube of EPROMS.
21
Tools on Platforms
Many M2M platforms offer Tools to develop
applications running on Platforms. A good
example of this is the Java development tooling
and an associated MIDP profile running across
multiple hardware platforms (but perhaps
different operating systems). This approach is
in contrast to the SCALematics approach where
historically applications were hand coded to
run on single, specific operating systems. Often
this resulted in a fixed point in time solution
that was problematic (if not impossible) to
change over time.
22
Security!
The good news is that M2M networks utilize open
networks and data transport standards. The bad
new is that M2M networks utilize open networks
and data transport standards.
M2M infrastructures offer the latest technologies
with regards to network security and associated
authentication and data encryption. Gone are
the SCALematics days of Security by Obscurity.
23
Mature IT Solutions
Due to the fact that M2M infrastructures are
utilizing available internet technologies and
tooling, mature IT tooling can be incorporated
into the backend solutions. In many cases this
greatly reduces the associated application
development costs and provides an associated long
term availability of the product in both sales
and support.

• Middleware
• Development Environments
• Databases
• Web Services

SCALematic solutions tended to produce custom
point in time backend solutions that were
problematic with regards to both long term
availability and support.
24
(No Transcript)
25
Industrial Roots
Jeff Smith Founder and CTOSensorLogic
26
(No Transcript)
27
(No Transcript)