1 / 55

Section 7 – Database Support

Section 7 – Database Support. Corporate DB. Niagara AX Web Supervisor. Trane Summit Network. Legacy Network. Database Integrations. Export using: .pdf .csv .txt SQL queries Oracle queries Java Email SNMP Web Services HTML XML OPC. KEY. Data Flow Direct.

giles
Télécharger la présentation

Section 7 – Database Support

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Section 7 – Database Support

  2. Corporate DB Niagara AX Web Supervisor Trane Summit Network Legacy Network Database Integrations • Export using: • .pdf • .csv • .txt • SQL queries • Oracle queries • Java • Email • SNMP • Web Services • HTML • XML • OPC KEY Data Flow Direct Data Flow through Web Supervisor

  3. DB Integration – Why? • Make BAS data part of the Enterprise • Financial management • Asset management • Enterprise Resource Planning (ERP) systems • IT information systems • Make BAS data available to other systems • Work order management • Capital improvement systems • Energy management

  4. Data Integration Methodologies Using: • Exporters using: • .pdf • .csv • .txt • Custom JAVA exporter • SQL Queries • Oracle Queries • Email • Java DB Connectivity • SNMP • Web Services • HTML • XML • OPC • oBIX

  5. DB Interface Definitions/Uses • Exporters – design to move data from matrix formats in JENEsys™ generally to Microsoft applications such as Access or Excel • DB Queries (SQL, BQL, Oracle) – allow JENEsys™ stored data to be retrieved by standardized query languages. • Queries allow the user to specify a description of the desired result set, but it is left to the devices to perform the physical operations that produce the result

  6. DB Interface Definitions/Uses • SNMP – Simple Network Management Protocol – an open Internet standard – SNMP exposes data on the managed system (JENEsys™). This data can be queried (monitored) and written to (controlled) by the management system • XML – eXtended Markup Language – a fee-free, open Internet standard whose purpose is to help information systems share structured data via the Internet • Standardizes JENEsys data so any database application, program or system can read, share and communicate with the JENE. • XML allows sharing of information between new and legacy data applications without spending any money on s/w acquisition

  7. DB Interface Definitions/Uses oBIX - OASIS Open Building Information Exchange • From an industry point of view • Open Standard Protocol, XML based • From a Tridium point of view • The primary use of oBIX is to enable Niagara R2 systems to communicate with Niagara AX (JENEsys™) – based systems • R2 Development ended with launch of AX in 2005 but R2 systems are widely installed and continue to be sold by some OEMs – notably TAC/Invensys

  8. Section 7 Takeaways • Methods of DB Integration are numerous • Integration methods generally have a license fee associated with them • Most DB Integrations require: • Inclusion of PC-based Web Supervisor software on the network • Transfer of data to Web Supervisor from the JENEsys™ platform • This requires a communication protocol to be licensed on the JENEsys™ platform – BACnet or Fox • Fox is the primary protocol used Niagara to Niagara IP communication

  9. Questions: Section 7 ? ? ? ?

  10. Section 8 – Key Sales Points

  11. Value $ Total Building Solutions 3rd Party application integration Legacy Integration DB Integration Facility Management Power Demand Management Energy Management Software BAS Software Service Parts Control Systems Chillers Mechanical Equipment Competition Value Pyramid

  12. Sales Benefits • Preserves customer investment in legacy systems • Extend the life of existing control systems • Saves customer money by deferring product replacement • Makes legacy systems and new Trane systems part of an integrated BAS network - “Embrace not Replace”…. • Legacy driver applications allow sharing of data from one system to another, allows greater flexibility for the customer when choosing equipment or services

  13. Sales Benefits • Future proof technology – open solution • Customer owns the IP and programming tools • Multi-tier enterprise level system allows user to extend beyond HVAC control. (Lighting, Security, Energy Modeling, etc) • Highly Scalable. Stand alone small building to multiple instances all communicating together

  14. Lynxspring™ Benefits to Trane • JENEsys™ products and related services complement not compete with Trane controls and equipment • JENEsys™ enhances Trane’s position as solution providers (equipment, service, control, energy reduction, information, etc) by delivering flexible hardware and software options to meet your customer needs. • JENEsys™ product help expand existing Trane offerings (equipment sales, service, etc) • Lynxspring provides secure access to Niagara technology and outstanding support of your technical and sales efforts

  15. Section 8 Takeaways • JENEsys™ adds planks to Trane’s value pyramid • Key sales point is the preservation of client’s investment in controls and equipment • JENEsys™ provides a future proof benefit to users • JENEsys™ provides user with the freedom of choice • Choice between Embrace or Replace

  16. Questions: Section 8 ? ? ? ?

  17. Section 9 – Legacy Solutions

  18. Eliminate the Integration “Gotchas” • Integration team requires someone with specific knowledge of the target control system. This can be a client employee, integration team member or a third party • Integration may require 3rd party devices be installed in the target system • The end client needs to provide Integration team with a list of points in the target system that require integration and the list needs to clearly indentify monitor points (read) and control points (read/write). • End client needs to provide the integration team with access to the system during the life of the integration project – including any maintenance period

  19. Client Vs. Server ArchitectureN2 Integration Examples CLIENT TYPE SERVER TYPE Ethernet LAN N2 Manager Standard Browser PDA/Cell N2 System Bus N2 System Bus JENE Manages N2 Devices This is a “Client” Type License JENE is Managed by N2 Master This is a “Server” Type License

  20. Open Client Drivers

  21. Open Server Drivers

  22. Legacy Client Drivers

  23. Legacy Client Drivers

  24. Driver Notes • Note 1 • Contact Lynxspring for Information • Note 2 • Driver published by independent developer

  25. Niagara Legacy • Niagara R2 is the original O/S supported by Tridium • Stopped development in 2005 • Continue to sell and support this O/S • Vykon contractors • TAC Invensys dealers • Staefa dealers • JENEsys™ O/S is AX • Method to communicate R2 to AX is through the oBIX driver • If an opportunity is specified “Niagara”, be sure to determine if it is R2 or AX • Call Lynxspring for clarification if necessary

  26. NiCS - NIagara Compatibility Statement • Licensing model for Niagara OEMs to define levels and types of interoperability • Two primary interactions • Sharing of data between stations (application) • Ability of the programming tool to engineer the station • Limits are for security or competitive reasons • JENEsys™ and tools are completely open • Any Niagara-certified technician can work on the system • Customers can always get the stations and programming tools (by others) opened up for Trane Implications: Service of the system

  27. Section 9 Takeaways • Qualify your opportunities • Clearly identify the target systems • Develop a plan • Eliminate “gotchas” • Know which drivers are off-the-shelf pricing and which require consultation with Lynxspring • Be aware of differences in Niagara R2 and AX • NiCS – Who can service the system(s)

  28. Questions: Section 9 ? ? ? ?

  29. Section 10 – Solution Examples

  30. Testimonials Using JENEsys™ we can sell more Trane controls, not less.  And we have just touched the surface of the potential that can be reached by combining the JENEsys™ solution with standard Trane controls.  The JENEsys product opens up more options. For example, we have the option of better integration to competitors' systems. This opens up opportunities for more Trane controls to be sold, and helps connect us with new customers to broaden our base of potential service contracts.  …Steve Brimeyer of Trane Des Moines

  31. Testimonials Lynxspring products have increased both our controls and equipment business by allowing us to integrate into other people’s systems. This has resulted in both increased equipment and service business. We now are able to talk to customers that we couldn’t talk to in the past. We are doing a job right now with a school district that has four Johnson schools and one Honeywell. Before Lynxspring we would not have been considered. With Lynxspring, we have the job. …Kevin Hauser at Harshaw Trane

  32. Testimonials The Lynxspring product has helped us secure new business as well as expand our horizons on existing or new Summit. The product has made it possible for us to respond to requests from customers to integrate other competitive systems into our Summit Workstation.  Recently, Lynxspring assisted us with integration information from Network8000 through Lynxspring to Summit and we have responded favorably to the customer.  We have also used it to expand from our Summit system on a campus of one of the Energy Industry customers to pick up two JCI buildings and integrate the information through our Summit workstation. …From Al Connelly at the Hunton Group (Houston Trane)

  33. Testimonials Lynxspring has “top graded” our capabilities by providing Trane Arkansas with a larger tool set and more flexibility. As a result our people got better. We were also better able to focus on retrofit and service opportunities. Also, we had lost out to Niagara™ on some campus and government contracts and Lynxspring let us come back to compete for those jobs. …Frank Mayfield of Trane Arkansas

  34. Arkansas Trane’s Frank Mayfield’s Case Study

  35. Tactic #1: Target Competitive Controls Systems as Service Opportunities • Use knowledge of competitive controls to expand share of service customers • Meet the owner’s need for comfort, reliability, efficiency • Start with maintaining the incumbent system • Leverage the lament: “It’s not working now and it’s never worked!” | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  36. Tactic #2: Map the Migration Path • System Migration is going from proprietary to open • System Migration is site specific • Plan for spare parts through integration to become independent of the incumbent • Promote an open vision • Web enabled • Competitive bidding for expansion and service • Single seat operation • Virtual services • Sell the vision | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  37. Tactic #3: Make the building work better • Selectively apply systems knowledge to enhance building operation • Define your performance with the building stake holders • Some items to consider for fast improvement: • Throttling ranges of VAV controller • Reset setpoints to relax the system • Nail humidity problems | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  38. Tactic #4: Overthrow the incumbent • System crash issues • Central Plant Efficiency • System Obsolescence • Parts not available, not reasonable about $ • Workstation operating system (OS/2, win95) • Single source for controls and equipment • Is there hostility towards the incumbent? • Plant the flag, Install the integration platform | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  39. Chenal Country Club • 800 point Siemens' System 600 • Long standing equipment relationship • Took advantage of poor performance of the incumbent to get the control service contract. • Sold integration with JENE prior to major expansion and upgrade of facility • Siemens to JENE to Summit (BACnet) • Spec read “connect to existing Summit system” | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  40. Cypress Plaza • Longstanding equipment relationship • Andover OS/2 front end crashed • Andover bid $15,000 to replace • We cut their number and wound up paying some tuition • There is still an orange box on the wall • Building has renewed 3 times since Integration • Mediocre relationship between owner and Andover went sour | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  41. Andover • RS232 interface, dependent upon their building level panel for data • Long update times, takes patience to operate • Tough to support, have to reload data in segments | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  42. Siemens • Ditto from Andover, low fidelity integration • Be careful of taking on a new hospital with Div 17 integrations • Comfortable with SCU’s and MBC’s | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  43. TAC Vista • 2 communications link configurations • Classic (LonWorks) • Lon (LonMark) • Once you touch a classic network with a 3rd party tool the network is in jeopardy • TAC LonMark is very well behaved • Easy tunneling through JENE and ProBuilder with Menta engineering software | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  44. Johnson Controls • JENE has both N2 Server and Client • Our initial jobs were using FX 40, “Johnson JACE”, N2 driver and everything else Niagara | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  45. Other AX Drivers • BC Network 8000 • CSI INET • BACnet MSTP – Alerton, Delta, Reliable, KMC, etc. | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  46. Niagara Framework • Distech • Carrier One • Staeffa • Invensys • Honeywell • Vykon • Know the rules of access for other Niagara based systems • Know the vendor specific tools | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  47. Caveat Integrator • Must have a “native guide” • Tools for set up and programming legacy unit controllers need to evaluated and maintained • Integrations occur at different levels within competitive system architectures, understand the “where and how” • Know the pitfalls, manage customer expectations • Andover, CSI, JCI, Siemens Div 17 elements raise the bar • Avoid one offs & don’t get spread too thin • Know what’s important: schedules and setpoints carry large weight for everyday operators | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  48. Caveat Vendor • Know the facts that threaten the credibility of the incumbent • Clients sometimes will “keep dancing with the one that brought us” • Most of Trane Arkansas’ JENE installations have a Summit front end • Compliment the ICS story • Step into the role of “best of breed” solutions provider | 2008 WEBINAR on SYSTEM INTEGRATION with a TRANE Focus|

  49. Arkansas Trane History with System Integration • Andover • Alerton • Echelon (Distech, Viconics, HVAC equipment) • Johnson • KMC • Siemens | 2008 Lynxspring Partner Conference | Paradigm Return to Energy Savings |

  50. The Untouchables • Novar • TAC classic network | 2008 Lynxspring Partner Conference | Paradigm Return to Energy Savings |

More Related