Follow

Project Manager Guide Glossary

Glossary of DECK Support Terms:

  • AcquiSuite Network Requirements DHCP:  
    1. The AcquiSuite needs to be able to access to DNS server for the purposes of resolving the following URL’s IP address: http://data.deckmonitoring.com/
    2. For the IP address that resolves from the above URL, the AcquiSuite needs to be able to communicate on port 80.
    3. The AcquiSuite needs to be able to sync its clock with a time server. By default, this is time.buildingmanageronline.com, but if this is not a reachable destination from the network, the network administrator will need to provide a valid alternative time server, internal or external, that the AcquiSuite will be able to reach (protocol can be rdate or NTP). 
  • Data Points:  Is a set of measurements on a single member of a statistical population, or a subset of those measurements for a given individual. In addition, in statistical graphics, a "data point" may be an individual item with a statistical display; such points may relate to either a single member of a population or to a summary statistic calculated for a given subpopulation. In short a data point is a measurement of a system variable.
  • Deploy: The process used to confirm that the devices are mapped properly, the dashboard is built, and the various pages load.  Please note site deployment is generally done within hours of the site being enabled for the first time (sometimes prior to getting permission to operate).  What this means is that we only do basic data analysis "does this look reasonable for the time of day, location, etc." 
  • Device:  A device is a piece of hardware that aggregates input / output data or measures variables from different environments. A device can also be a piece of gateway that communicates with other devices in a system.
    1. For the IP address that resolves from the above URL, the AcquiSuite needs to be able to communicate on port 80.
  • Modbus RTU:  This is used in serial communication & makes use of a compact, binary representation of the data for protocol communication. The RTU format follows the commands/data with a cyclic redundancy check checksum as an error check mechanism to ensure the reliability of data. Modbus RTU is the most common implementation available for Modbus. A Modbus RTU message must be transmitted continuously without inter-character hesitations. Modbus messages are framed (separated) by idle (silent) periods.
  • Modbus TCP/IP or Modbus TCP: This is a Modbus variant used for communications over TCP/IP networks, connecting over port 502.[2] It does not require a checksum calculation as lower layers already provide checksum protection.
  • Modbus: A high-level protocol for industrial networks developed in 1979 by Modicon (now Schneider Automation Inc.). Providing services at layer 7 of the OSI model, it defines a request/response message structure for a client/server environment. Modbus runs over various data links including its own Modbus+ token passing network and serial links such as RS-232 and RS-485.
  • Offset:  When DECK technicians calculate the necessary value required to “zero-out” negative generation values that are a result of reversed/“flipped” CT’s or CT leads that were terminated with reversed polarity.  This process requires the evaluation of Historical Data from Raw CSV’ Downloads that’s provided by the Generation Meter.
  • QA: A more in depth error checking process - generally done 2 or 3 days after the site has been running.  This allows for more nuanced errors to be located and corrected.  Some examples of these errors would be an improperly calibrated meter or loose connections inside the com wire.  These issues generally won't present until a few full days of data is present.
  • Raw CSV Download:  The file that is obtained by clicking the first icon on the left (looks like a pie-chart over a spreadsheet) in the “Downloads” tab.  This file is in a format utilized most commonly by Excel or other spreadsheet programs.  This data type is the sole method by which DECK technicians and customers can evaluate the historical data generated by any device that reports through the AcquiSuite Gateway device.  Referring to the Raw CSV is an excellent method of verifying the operation of the AcquiSuite, any device, and as a result some of the operational features of the DECK Dashboard & application.  By method of comparison, CSV files are instrumental in troubleshooting various elements of a monitoring system.
  • RS485: is a standard defining the electrical characteristics of drivers and receivers for use in balanced digital multipoint systems. The standard is published by the Telecommunications Industry Association/Electronic Industries Alliance (TIA/EIA). Digital communications networks implementing the EIA-485 standard can be used effectively over long distances and in electrically noisy environments. Multiple receivers may be connected to such a network in a linear, multi-dropconfiguration. These characteristics make such networks useful in industrial environments and similar applications. Also known as – EIA-485,TIA/EIA-485.
    1. The AcquiSuite needs to be able to access to DNS server for the purposes of resolving the following URL’s IP address: http://data.deckmonitoring.com/
    2. The AcquiSuite needs to be able to sync its clock with a time server. By default, this is time.buildingmanageronline.com, but if this is not a reachable destination from the network, the network administrator will need to provide a valid alternative time server, internal or external, that the AcquiSuite will be able to reach (protocol can be rdate or NTP)
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk