1 / 63

Section 11 – Price Sheet Review

Section 11 – Price Sheet Review. JENEsys™ Price Sheet - Multiplier 0.24. Price Sheet Layout. New Part Number, Description, List Price JENEsys™ PC 1000 Controllers, JENEsys™ PC 1000 Driver/License Options 1064 = 64MB Flash RAM 1128 = 128MB Flash Ram

olwen
Download Presentation

Section 11 – Price Sheet Review

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 11 – Price Sheet Review

  2. JENEsys™ Price Sheet - Multiplier 0.24

  3. Price Sheet Layout • New Part Number, Description, List Price • JENEsys™ PC 1000 Controllers, JENEsys™ PC 1000 Driver/License Options • 1064 = 64MB Flash RAM • 1128 = 128MB Flash Ram • JENEsys™ PC 6000 Controllers, JENEsys™ PC 6000 Driver/License Options • 6128 = 128MB Flash RAM • 6256 = 256MB Flash Ram

  4. Price Sheet Layout • JENE PC 1000/6000 Hardware Options • Includes extra Lon cards, extra RS485/232 ports, power modules (Wal-Wart) and modems • JENE Software Revision Upgrades and License Changes • These are for end users licenses – not necessary for operation of originally installed applications • Legacy Drivers

  5. Section 11 Takeaways • Price list is line itemed and will require familiarization; • Different pricing for JENE PC 1000 and JENE PC 6000 components • Common price for hardware adds • If confused, call Lynxspring for pricing assistance and module requirement assistance

  6. Questions: Section 11 ? ? ? ?

  7. Section 12 – Estimating Projects

  8. Legacy Integration Process • Identify legacy systems Identify and understand the use of legacysystems in customer facilities • Acquire system knowledge Acquire knowledge about the design, operation and programming of relevant competitive automation systems • Develop an integration and migration path Develop overall (initial and ongoing) integration and migration path for system improvement and customer satisfaction Utilize a simple project development process!

  9. Identify legacy systems • Identify and understand the use of legacy systems • Interview Customer • Interview Service Providers • Conduct a Site Evaluation • Obtain General Information • Maps, facility addresses, contacts and phone numbers • Obtain individual building information • Size, age, small-scale maps, utility bills, existing vendors, system models, riser diagrams, and points lists • Qualify Pain • Facilities management, operations pain • Occupant pain • Schedule Site Walk Through(s)

  10. Acquire System Knowledge • Site Walk Through – Legacy Integration Considerations (things to pay special attention to) • Available architectural diagrams • Number of devices, addressing of devices • Available points lists • Number of points per device, what do points do? • Available sequences of operations • Will you be integrating at system level or field-bus level? • Will you need to re-create graphics and/or programming? • What is the customers’ interface to the system? • Does the customer have current custom graphics that they desire to duplicated?

  11. Develop integration/migration path • Initial Migration • Cost considerations • Enterprise, system, or unit level integration • Service contracts • Applications, features, and functions • Expected lifespan of existing systems • Full price up front or over time • Expansion considerations • Open platform – tie old to new • Controls contractor and vendor responsibilities • Future flexibility and sustainability • Customer responsibilities • Define metrics of success with controls contractor

  12. Develop integration/migration path • Ongoing Migration • Replacement and upgrade considerations • Replace on failure with new • Keep existing legacy parts inventory • Inventory built when retrofitting / upgrading • Purchase replacements from existing supplier/vendor • Customer responsibilities • Facilitate ongoing purchases from other vendors • Parts, programming, service – as defined by scope

  13. Estimating Integration Elements • Lynxspring hardware/software sizing • Integration Labor Components • Potential Additional Costs

  14. JENE Sizing Considerations • Sizing is black art • Lynxspring sizing estimates differ from others in the Niagara community • Trane will develop its own sizing guidelines with experience • It is better to oversize than undersize • Custom programming will have a severe impact on sizing (Niagara features outside our target use).

  15. JENEsys™ PC 6128: 1500 points 70 devices attached JENEsys™ PC 6256: 2000 points 120 devices attached Sizing Rules of Thumb • JENEsys™ PC 1064 • 500 points • 20 devices attached • JENEsys™ PC 1128 • 1000 points • 40 devices attached

  16. Defining a Point BCU BACnet™ Tracer Summit Software Legacy VAV Link 12 Physical Points 8 Logical Points 12 Physical Points 8 Logical Points 12 Physical Points 8 Logical Points 12 Physical Points 8 Logical Points

  17. Summary: Defining a Point • The Role of a JENE • Discover devices/points on legacy network • Select desired points • “Map” desired points to BACnet • Only “mapped” points count towards sizing

  18. Summary: Defining a Point, Cont. • The Role of a BCU • Graphics • Discover “mapped” points as “non-Trane device” • Tracer Summit graphics don’t require additional BCU capacity to display/control “mapped points” • Trends • Trending “mapped” points does not require additional BCU points (but you do need additional storage for the trends) • Alarming • BCU Points must be created if alarming required • Programming • CPL that references the “mapped” points does not require BCU points • Scheduling • BCU scheduling that references the “mapped” points does not require BCU points

  19. ProBuilder Trane and/or Lynxspring Technical People will access the JENEsys™ integration platform via ProBuilder over the Internet, Intranet or a direct connection PC with ProBuilder Tracer Summit Industry Specific BACnet/IP JENEsysIntegration Platform Tracer BCU Siemens JCI Comm 3 Honeywell Comm 4 Lighting Security LonTalk Other

  20. Integration Labor Components Labor hours must be estimated for some or all of the following: • Deploying JENE • Install hardware • Configure hardware parameters (IP Address, etc) • Station Setup (Drivers, Programming, etc) • Install and configure client driver (legacy field bus) • Install and configure BACnet driver (for export to Tracer) • Discover legacy points • Select points needed based on requirements • Map selected legacy points to BACnet points

  21. Integration Labor Components, Cont. • Use Tracer to discover mapped BACnet points • Use the information • Integration at System Level ($) • Add to graphics • Are we adding graphics for status/control • Add to programming • Adding additional control not previously available • Integration at Field Bus Level ($$$) • Duplicate removed system level control routines in Tracer system • Duplicate removed system level graphics in Tracer system • Supplement graphics/programming as required

  22. Assigning Time to the Components • Estimated time for individual components will vary greatly due to the following factors: • Available documentation about legacy system • Experience with integration projects • Familiarity with Lynxspring product • Expertise with legacy protocol in question • Level of legacy “system-level” programming and/or graphics that need to be duplicated (Note: could be a huge factor) • Estimate the number of labor hours to perform similar tasks in a Tracer Summit system • NOTE: As you perform integrations you can substitute your hours specific to Legacy Integration with a JENE • Apply a multiplier based upon comfort level with the factors outlined above. This may be in the range of 1.1 (highly skilled) – 3.0 (new experience)

  23. Potential Additional Costs • BCU capacity • Do I need additional BCU capacity specifically for integration elements? • Legacy tools • Configuration • Programming • Servicing • Subcontracting • Legacy protocol technician capabilities • Centralized Services and/or other Trane offices • Field Technician “Tuition” • Warrantees and service • Gateways and routers

  24. Pricing Example 1 • Client requires an interface into an American Automatrix PUP system. Interface will connect to a BCU via BACnet IP. There are 200 points and 25 devices in the American Automatrix system. The connection to AA is via RS485. • Estimate the project: • Define the parts and licenses in JENEsys™ that are required • Define the labor required

  25. Pricing Example 1 – Hardware/Software

  26. Example 1 – Labor Considerations • Scenario • Technician • Does not have experience with the PUP system • Is very familiar with JENEsys™ • Trane has reasonable access to the PUP system • Read/Write and Read Only integration points are defined • All American Automatrix devices are the same • Integration must be done on site for PUP components. • BACnet export table can be remote once PUP integration is discovered • Add windshield time and travel costs • If devices are not the same, add 1 hour per each different device

  27. Pricing Example 1 - Labor

  28. Pricing Example 2 N2 to BCU BACnet IP • The client has an N2 network with 64 devices (DX9100, XP, XT and etc) on it. Each device has 20 points and will be exported out to a BCU via BACnet IP. • JENE BACnet IP Server services also requires an installed JENE BACnet IP Client • Estimate the project: • Define which parts and licenses are needed in JENEsys™ that are required. • Define the labor required

  29. Pricing Example 2 – Hardware/Software

  30. Example 2 - Labor Considerations • Scenario • Technician • Knows the JCI system • Is very familiar with JENEsys™ • Trane has reasonable access to the JCI system • Read/Write and Read Only integration points are defined • All JCI devices are the same • Integration must be done on site for N2 components. • BACnet export table can be remote once N2 integration is discovered • Add windshield time and travel costs • If devices are not the same, add 1 hour per each different device

  31. Pricing Example 2 - Labor

  32. Pricing Example 3 Network 8000 to BCU BACnet IP • The client has an Network 8000 with 40 devices (Microzone2 controls) on an ASD bus. Each device has 30 points and will be exported out to a BCU via BACnet IP. • GCM Controllers contain custom programming • JENE BACnet IP Server services requires also an installed JENE BACnet IP Client • Estimate the project: • Define which parts and licenses are needed in JENEsys™ that are required. • Define the labor required

  33. Pricing Example 3 – Hardware/Software

  34. Example 3 - Labor Considerations • Scenario • Technician • Is somewhat familiar with the Network 8000 system • Is somewhat familiar with JENEsys™ • Trane has reasonable access to the Network 8000 system • Read/Write and Read Only integration points are defined • All Network 8000 devices are the same • BCU Programming will be needed to duplicate eliminated GCM programming (custom applications) • Integration must be done on site for Network 8000 components. • BACnet export table can be remote once Network 8000 integration is discovered • Add windshield time and travel costs • If devices are not the same, add 1 hour per each different device

  35. Pricing Example 3 - Labor

  36. Pricing Exercise N2 to BCU via BACnet IP • The client has an N2 network with 6 NCM’s with 80 devices (2 links with 40 devices each) per NCM (total 480 devices). • JENEs will replace the NCMs • Each device has 15 points and will be exported out to a BCU via BACnet IP • Analysis of the N2 network indicates that it is recommended that no more than 64 devices can be attached to an the JENEs RS 485 port. • Estimate the project: • Define which parts and licenses are needed in JENEsys™ that are required. • Define the labor required

  37. Exercise - Labor Considerations • Scenario • Technician • Is very familiar with the JCI system • Is very familiar with JENEsys™ • Trane has complete access to the target system • Read/Write and Read Only integration points are defined • JCI devices are not the same – there are 4 different devices types on the network – but N2 trunks are the same • Integration must be done on site for N2 components. • BACnet export table can be remote once N2 integration is discovered • Add windshield time and travel costs • If devices are not the same, add 1 hour per each different device • Electrician and wiring not included

  38. Pricing Exercise – Hardware/Software

  39. Pricing Exercise - Labor

  40. Pricing Exercise – Hardware/Software

  41. Pricing Exercise - Labor

  42. Section 12 Takeaways • Hardware sizing rules are imprecise • It is better to oversize than undersize the JENEsys™ • For labor estimates, it is important to clarify the information and function of the target system that will need to be integrated • Labor hours should be estimated using component breakdowns, Trane hours for similar tasks and relevant multipliers. • Ensure you account for the costs of special tools and/or subcontracted support • Call Trane St. Paul (1-877-78TRANE) or Lynxspring if you have questions or concerns

  43. Questions: Section 12 ? ? ? ?

  44. Section 13 – Support and Resources

  45. Lynxspring Support • Lynxspring University • Help desk • Customer Secure Site • LBP Group Support • Documentation • Trane Web Site • Documentation • Collateral • PowerPoints

  46. Lynxspring University • Certification training • Post certification training • Niagara in the real world • Sales training • Onsite options

  47. Help Desk • 8:00-5:00 CST • Manned by certified experts • Voice, voicemail, email ticket input options • Web based tracking system • Onsite support options available

  48. LBP Group Support • Sales training and support • First project support • No fee project services • Lynxspring professional services

  49. Lynxspring Professional Services • Long term focus for this service is St Paul • Short Term Lynxspring Support • On site support • Extended remote support • Assistance with programming • On site commissioning support • Lynxspring becomes part of your team • Project quote is delivered up front • You know your costs • Labor rates based on level of expertise of consultant

  50. Trane Web Site • www.lynxpring.com/Trane

More Related