Wind Turbine Troubleshooting
Chris is the go to person for issues relating to the wind turbines.
The wind turbines sit in a larger context of building- and energy-management-related servers and networking infrastructure, which is touched on in separate documentation.
In general, the task of troubleshooting wind turbine issues consists of:
- Determining if the problem is on our energy information vendor's end (Lucid); are their systems all working correctly?
- Determining if the problem is on the turbine vendors' ends (GE for Turbine #2 and Vestas for Turbine #1); are their own systems working correctly?
- Determining if the problem is related to vendor connectivity into local turbine-related systems, on the part of GE, Vestas, or Lucid
- Determining if the problem is related to sending data out of our systems to Lucid, documented /wiki/spaces/itskb/pages/26127144
- Determining if the problem is related to network connected to any of our networking infrastructure, including
- Point to point turbine data link
- Leased fiber (Jaguar) in the case of Vestas
- Internal hardware (including the firewall) linking turbine-related equipment together
- Determining if the problem is with the vendor equipment installed on site, including SCADA, database, and other systems in the data center, which may require a hard reset
Equipment installed locally that comes into play includes:
- ALC WebCTRL server, 137.22.198.51
- GE, turbine #2, SCADA database back-end, 10.22.80.249 (KG: Changed this to .249 which I think is correct based on network traffic. It was .259 which is impossible.)
- Vestas, turbine #1, SCADA database back-end, 10.105.128.2
- Vestas SCADA system itself, 10.106.128.220
- GE SCADA system itself, 10.119.152.227
Other systems potentially in play:
- Siemens Perigee Server, 137.22.198.50
- Lucid BuildingOS, IP:13.83.71.72
Richard Goerwitz
2021