Transcript TridiumTalk Niagara AX 3.1

“Open System Solutions…a
Framework for Success”
September 2007
Steve Lucas – Sales Manager, Vykon Security
Scott Muench - Technical Sales Manager
© 2007 Tridium, Inc.
Agenda






2
Open Systems Overview
The Technology - Niagara Framework
Example Solution
Integrator Toolkit
Summary of Benefits
Q&A
What Customers Want
Systems
Security
Enterprise
Energy
MODBUS
LEGACY
Fire
CFO
Lighting
Open System
Framework
XML SQL
HTTP HTML
Facility
Management
ODBC SNMP
JDBC
FTP
SMTP
WAP
HVAC
And More
3
From
boiler room to board room – Brings value to the operation
Maintenance
Open System Framework
4
Open System Life Cycle Costs






5
Do they cost more or less than closed systems?
How much does it cost to acquire? (Initial Capital Investment)
What’s it cost to keep? (Ongoing Maintenance)
How does it help or hinder me in day to day activities? (Impact
upon Operations)
If I need to change, modify or enhance it, what does it cost and
how quickly can it be done? (Reconfiguration/Enhancement
Costs)
Is it worth anything when I’m done with it? (Residual Value)
Key Elements of Openness

Device connectivity


User Interface Connectivity




Can a standard browser be used for Access?
Can alarms, messages etc. be emailed, transferred to standard devices
such as browsers, phones, servers, PDAs?
Can I give anyone access without additional licenses fees?
Access to products for initial purchase and expansions




6
How many products of importance to my application can a given
technology or system communicate with?
Where can I buy these products?
Where can I get them installed or serviced?
How many suppliers?
Is it a competitive situation?
Key Elements of Openness

Third party development of complimentary enterprise
applications


Public interfaces (“APIs”) to allow 3rd party access to data


Does the system in question support the “lion’s share” of relevant standard
communication protocols?
Compatibility with standard databases

7
Are there published interfaces that makes it easy to access system data?
Support for accepted standard protocols


Can independent developers create new products and applications that
work coherently with the system?
Can data from the system be easily shared with common database
formats used throughout my enterprise?
The Customer Test



The end use customer is where the buck stops with open
systems.
They choose the systems, they pay for them, they live with
them.
Open systems gives the end user the ultimate freedom of
choice.





8
Manufacturer of choice
Protocol of choice - BACnet, LonTalk, Modbus, SNMP, OPC, and many
proprietary devices or systems.
Local contractor of choice
Choice to select add-on applications and devices from third party suppliers
Choice to extend the capabilities of the system through standard software
interfaces
Open System Framework Model
IBM
HTTP HTML XML
ODBC
OPEN
SMTP
JDBC
FTP
CORBA SOAP SNMP
Internet
Remote
Browser User
Interface
Niagara Web
Supervisor
Ethernet, TCP/IP, BACnet, XML, HTTP
JACE-5
Controller
JACE-5
Controller
Optional RF Link
Access
Controller
Power
Management
Lighting
Control
LonWorks Field Bus
Multi-Function
Sensor
LonWorks Field Bus
HVAC
Controls
LonWorks
Application
Devices
Niagara
JACE-NP
with embedded
Web UI Services
LonWorks
Application
Devices
CCTV
LonWorks
Application
Devices
9
LonWorks
Application
Devices
Asset
Management
Power, Gas,
and Water
Meter RF Link
Local
Browser User
Interface
The Technology - Niagara Framework







10
Unifies heterogeneous devices, protocols, data via a robust
component model foundation
Internet standards built in
Scalable, embeddable solution – same software can be used in small
low cost devices and at enterprise app level
Real time – connects real time data from field devices to enterprise
applications, provides local control execution
Integrated tools support programming for non-programmers: domain
experts build end-use applications with a graphical tool – no coding
Connects disparate devices for coordinated peer-to-peer control in the
field independent of any central server
Open development platform (extensive open APIs) allows partners to
independently develop differentiated products and apps
Comprehensive, flexible platform for developing
Internet-enabled solutions
Web-server with dynamic
data/e-mail alarming, etc.
Internet connectivity –
TCP/IP, HTTP, SNMP
Internet connectivity
Data logging, archiving
Information
management
Real-time control
loops/ schedules/ alarming
Java Component Object Model
LON, OPC, MODBUS, BACnet, Legacy,
etc.
Integrated, graphical dev toolset
12
User interface/data
Presentation
Control functions
Data normalization
Device-level
communications
Open System Solution - Example
13
Integration – Tenant A
14
Integration – Tenant C
15
Integration - Occupancy
16
Multiple Occupants
17
Return to Unoccupied
18
Application Development Tool
19
Control Functions



20
Supervisory Control
 Global algorithms
 Schedules
 Data Integration
Access System Logic
Business Rule Processing
Integrated Presentation Tools
21
Driver Framework
22
Benefits of Open Systems Solution


23
Open Architecture
 Maximum freedom of choice for end users
 Competitive marketplace
 Ease of systems integration / interoperability
 Reduced installation / upgrade costs
Niagara Framework
 Solutions focused, open framework architecture
 Capability to support many different communication protocols –
legacy and open standards
 Integrated application development tools to customize solutions
 Scalable, embedded solution with built in internet standards
Q&A



We would like your feedback on today’s TridiumTALK
If you have any further questions, comments or topic suggestions,
please email them to [email protected]
Exhibiting at ASIS – Booth # 107 – stop by and see us!
Steve Lucas
24
Rick Weisensale
Scott Muench