Mission Control to BMS Data Catalog

MQTT Broker

• The MQTT Broker must be deployed as part of the BMS. BCM will act as an MQTT Client and connect to the BMS MQTT Broker
• The BMS must publish to a Metadata topic first where the associated Value topic is written to by BCM.
• The BMS must publish Value Topics indicated that the BMS writes to
• BCM will publish Value Topics indicated that BCM writes to

MQTT Payloads

• Value Topics are to provide JSON payload with a value and timestamp.
  Example Topic: BCM/TPE01/A01/LIQUID/ReturnTemperature/Value
  Example Payload: {"value":37.590332,"timestamp":173101093196}
• Metadata Topics are to provide JSON to describe the datasheet.
  Example Topic: BCM/TPE01/A01/LIQUID/ReturnTemperature/Metadata
  Example Payload: {"pointType":"RackLiquidReturnTemperature", "objectType":"rack", "engUnit":"C", "rackName":"A01", "rackID":"1234abc"}

Retained

Metadata topics must all be retained.

Value topics that are not expected to update every few seconds must be retained (Setpoints and Binary Tags always fall into this category) - consider retaining all messages when possible

Heartbeat

The BMS and BCM will both write to the Heartbeat Value Topic. The BMS will write to the topic initially.

General

• Ensure Metadata Topics include all data shown in the "Metadata Payload Contains (JSON)" column
  • "pointType" is critical
  • Each "pointType" should have the specified Metadata
• "rackName" and "rackID" need to be coordinated between BCM and BMS prior to deployment. Rack Name and ID must allow association of a specific rack between the BMS and BCM.
• "CDUName", "CDUID", "circuitName", "circuitID" (CDU Name and ID, Circuit Name and ID) must be unique for each CDU and Circuit but do not require coordination with BCM. BCM will discover these from the BMS.