Transcript Major Projects and the Specification process

Major Projects
Specification Issues
Ron Bernstein
Echelon Corporation
©2003 Echelon
Projects
2
Army Corps of Engineers
3

Specifications in final stages
– Calls for open, LonMark, LonWorks implementation
– Identifies building and integration requirements in different spec docs

Final release due “fall 2003”
– Industry review meeting held in July
– Bacnet camp there in force, lots of issues, all addressed by USACE

Proceeding according to plan

For a copy of the spec email: Joe Bush at
[email protected]

What We Learned
– Extremely thorough analysis of the market
– Spec addresses extensive details on the right way to implement
LonWorks
– Long process – over 2 years
LONWORKS Open System Specifications

4
Reference material available:
– Army Corps of Engineers
NYC Schools

Scope
– 1600 buildings
– Upgrades to existing pneumatic systems
– 5 year or more project
– Phase 1 to write comprehensive specifications

The Spec
– Has two components



5
Building level
Enterprise connectivity
Bidders on the buildings cannot bid on the enterprise and vise versa

Due out fall 2003

What we learned
– Get IT group involved early in the process
– Consulting Engineer was main influencer and has major responsibility
– Need for detail level training and education
City Of Chicago
6

Scope
– 487 buildings
– Global Building Monitoring System
– Spec crafted by Teng
– 5 year plan to integrate city buildings into central enterprise monitoring system
– LonWorks key part of specification
– Open Systems mandated by the city
– 7 year project – could go to 10

Status
– RFP released in June
– Bids due Sept. 30 2003

Issues
– Single vendor or team for entire project
– Must come up with creative financing
– Relegates bidders to larger companies or “creative teams”
State of Louisiana
7

Scope
– Open Systems with LonWorks for all State buildings – Police, City, Universities,
etc
– Open to competition
– 100s of buildings

Status
– 9 – 10 buildings already bid, won and installed
– Many more in the works
– Big winner, local Invensys rep
– JCI has won at least 2 buildings
– Honeywell rep involved in multi-building integration

Issues
– Original spec developed 3-4 years ago
– Finger pointing on Enterprise Integration “not part of original scope of work”
– Spec needs rework to address – too many missing pieces
– Working with state design/construction team to revamp spec
Specifying an Open System
8
How Do You Ensure Openness
When Specifying An Open System
9

Make sure you are getting a true open system

Verify you will not be locked in on any level of the system

Encourage multi-subsystem integration for maximum
efficiency

Start from good open specification framework (see
references)

Define and understand users expectations

Learn the technologies, options, and market directions
Specifying An Open System
Network Components
10

Nodes or Devices
– The controllers on the
network

Infrastructure
– The wire the nodes
connect to
– The routers that pass
the data
– Termination
– When are gateways
necessary?
• Tools




Design Tools
Commissioning Tools
Database issues
Plugins
• Host Interface
 PC Based
 Web Based
 Flexibility and Choices
 Enterprise Connectivity
 Large project architecture
 Design for the future
 Scalability issues
LONWORKS Open System Specifications

Reference material available:
– Echelon OSA Website : http://osa.echelon.com

Open System Specification Framework and Design Guide
– http://osa.echelon.com/Program/PDFs/guidelines/OpenSpecFramework.pdf
11
LONWORKS Open System Specifications

Reference material available:
– LonMark Website: http://www.lonmark.org/products/guides.htm

12
LonMark Building Automation System Master Specification
Ten Questions To
Open Systems
13
The Questions
1. Can the devices from different manufacturers be installed and commissioned
on the same physical wire and be capable of true peer to peer communication?
"All devices (nodes) on the network shall be capable of true peer to peer
communication, without requiring a host or zone controller."
2. Have the devices been tested for interoperable compliance? "All devices
(nodes) on the network shall conform to the LonMark Interoperability Standards
version 3.0 or higher and be LonMark tested and certified for compliance on the
open systems network."
3. Is the integrator meeting the requirements for the network infrastructure? “The
network infrastructure shall conform to the published guidelines for wire type,
length, number of nodes per channel, termination, and other relevant wiring and
infrastructure criteria.”
14
The Questions
4. Are the network management and commissioning tools available from multiple sources
and can all the nodes be installed with these tools? If a node needs custom configuration,
is there a plugin available for use in a standard tool. "All devices (nodes) on the network
shall be able to be installed and configured using a standard network management tool
such as LonMaker for Windows or other LNS based tool. No non-open tool set for
installation or configuration will be accepted. All tools must be generally available for
purchase to any integrator from multiple sources."
5. Are the front end tools proprietary and closed? "Any host PC interface shall use openly
available software packages that are non-exclusive. No closed software will be accepted.
Software must be generally available on the market from multiple sources."
6. Who is doing the work on your building? “Integration of the controls network shall be
performed by a qualified network integrator. A qualified network integrator must have
attended at least 40 hours of training and have prior successful open systems jobs
experience.”
15
The Questions
7. Do you have control over your building? “All configuration tools, installation tools, Plugins,
databases, software shall remain with the job and be owned by the property. All software tools shall be
properly licensed and conveyed at contract sign-off.”
8. Are your tools open? “No exclusive or non-open integration tools, devices, or host software shall be
used as part of this open system.”
9. How are you connecting to your data network? “If Internet or IP connectivity is specified all devices
connecting to the LAN shall use the IP protocol. Any LAN to LON gateways or routers shall use the
standard IP protocol stack and shall be transparent to the devices on the network (layer 3 routing).”
10. What controls are you using? “The control system shall be installed using the best available
products from the currently available suppliers that meets the system specification. Controllers from
multiple manufactures are encouraged.”
Bonus Question:
11. Are you certain your network was designed and installed correctly? “System integrator shall
provide a protocol analyzer log summary for each channel for a minimum of 48 hours showing system
performance. The statistical summary shall show that all bandwidth utilization and error limits are
within acceptable range and that there are no network traffic problems, node communication problems,
or system sizing problems.
16
Resources
17

LonMark Organization
– www.lonmark.org

LonUsers Organizations
– Located world wide
– www.lonusers.info

Open Systems Alliance
– http://osa.echelon.com

LonTalkProtocol Details
– www.ansi.org
– www.iso.org

White Papers, Documentation, and more
– www.echelon.com

Chip Manufacturers
– www.toshiba.com
– www.cypress.com

LonWorks Distributors
– www.engenuity.com
Contact Information
Echelon Corporation
Ron Bernstein
550 Meridian Avenue
San Jose, CA 95126
1-888-ECHELON
408-328-3800 Fax
[email protected]
Channel Manager, Americas
204 N. El Camino Real #E242
Encinitas, CA 92024
858-756-9923
408-790-3492 fax
[email protected]
www.echelon.com
osa.echelon.com
www.lonmark.org
18