/
2019-10-25 Lutron Lighting System Setup Meeting notes

2019-10-25 Lutron Lighting System Setup Meeting notes

Date

Oct 25, 2019

Participants

  • @Cynthia Schwarz (Unlicensed)

  • @David Lacy

  • @Evan Weinstein

  • Larry Brandolph

  • Kamren Nizami

  • Ray Lauff (ITS)

  • Adam Ferrero (ITS)

  • Bill Barnes (PDG)

  • Paul Rudalavage (Lutron)

  • Sean Clouser (ITS)

  • Jim Weber (Lutron)

  • Jim (EJ Electric)

Goals

Discussion topics

Notes

Notes

Networking for the lights themselves

  • we have four quantum processors controllers in the building and each one has an IP and a data line

  • right now all scheduling is managed from those controllers

  • ITS has an “Environmental Control Network” and this is where they should live.

  • Bill provided the addresses back in May and they seem to be on the right network

    • 1st floor: 10.124.44.80

    • 2nd floor: 10.124.44.81

    • 3rd floor: 10.124.44.82

    • 4th floor: 10.124.44.83

Server requirements

  • Can’t repurpose an existing server because it needs to exist on the back-office server and configured to the vendor

  • Question: Is SQL Server an actual requirement?

    • By default, use SQL Express

  • Can we use a workstation instead of a server?

    • Depends on the level of service/performance that we want

    • Might see latency from IIS server on a workstation

  • What is the server there and meant to do?

    • Monitoring abilities

    • historical reports of performance

      • how much are rooms occupied?

      • how much are we saving because of dimming or turning lights off

    • Most of the work it does is receive information from the server.

    • Can control things virtually from the user interface - can go through and make programming change

  • How long does it retain the usage data?

    • retains granular data on hour by hour functionality for several weeks, starts to consolidate and compact the data the longer in history the data has been there.

  • If the server is offline, what happens?

    • It may be possible to cache data locally and send it up to the server

    • All of the lights will continue to work in the event of a server outage

  • Does this system need to be considered “highly available”? ***Or really, how long does the controller cache the information?***

  • Requirements from Evan:

    • Really about the advanced functionality, i.e. being able to lock out certain functionalities

      • The wall switches would continue to work and the schedules would continue

      • But to change any of these, we need the server

    • In the future, integrate with Scatasystems? - one system for the entire campus for building management - yes, they are compatible for this

  • How many hubs can be managed on one server - A Quantum system can have up to 16 processors and up to 10 Quantum systems can go on one server.

  • Vendor Access?

    • can support remotely when and how we need it

  • Feeds up to the server - unicast. Processors need to talk multi-cast to each other

Windows Server

  • SQL Server Express

  • IIS

  • 16 GB RAM

  • 500 GB Storage

  • recommend SSD

  • Windows Server 2019 is being tested, but not fully vetted.

Timeline

  • We can bring this online around January 2020

  • Schedule a follow up meeting end of December to discuss the timeline for setup in January.

  • Schedule a follow up with Lutron Commissioning Agent

  • Lutron Commissioning Agent will need to install some thing

  • Training will be scheduled once server is up and running

ToDo

  • Need to talk about how to put a server on the Facilities Management Subnet

    • Adam may have some thoughts about this

  • Commissioning person will need access to the network that the processors are on

    • Can connect directly to the processor or connect to any port on the network

    • Identify a jack that can be put on that network where they can connect to the VLAN - Evan will identify and communicate this to Adam’s team



Action items

Decisions