Description
Building data sent from a CopperCube that is not correctly mapped to Kaizen buildings will be discarded! However, the trend log data still remains in the CopperCube and can be re-sent to the Kaizen Vault via the Coppercube’s ‘Send Historical Data’ feature.
Note: Due to high trash volumes – we are no longer able to buffer data in our Trash. As of May 2015, our policy is any data sent to the trash is automatically deleted.
This KBA discusses the reasons why your data may land in Trash, and how you can ensure that your CopperCube to Kaizen setup is done correctly to prevent this.
Why should I care?
The data collected by your CopperCube includes Trend Log samples, Objects, Controller Database Backups, and Events. All this data is sent to Kaizen for storage, but the CopperCube only stores a copy of the Trend Logs locally. The purpose of using Kaizen in conjunction with your CopperCube is to ensure your data is safely stored on cloud servers, where it can be viewed and analyzed into useful information. If the data your CopperCube sends to the Kaizen servers, lands in Trash instead of Kaizen’s database, it is lost!
Why would my data go into Trash?
Data only lands in Trash, if the receiving server cannot determine the building(s) to which the data belongs.The receiving server uses the device mapping information it receives from Kaizen and the CopperCube. If these two sources do not agree, as to how the CopperCube data maps to Kaizen buildings then some data is going to land in Trash. There are several reasons why data ends up in the Trash:
- Kaizen does not know that the CopperCube has been deployed. If a CopperCube is not deployed to a client, then it cannot be assigned to any of the client’s buildings.
- A receiving building has not be created, within Kaizen, for the client – so the CopperCube’s data has no where to go.
- The client’s receiving building has no device mappings defined, associating some or all of the CopperCube’s controllers (devices) to the building.
- The building’s device mappings are incorrect. Either the wrong CopperCube has been selected, the wrong CopperCube Site Name has been entered, or the range of devices is incorrect. *Note: the CopperCube’s device Inclusion Range may be divided into sub-ranges (each assigned to a different building), but if any controllers are not accounted for, their data will land in Trash.
Before configuring your CopperCube to send data, you need to ensure one or more buildings are set up in Kaizen to receive the data. This process is explained in this How-to Article. As indicated in the article, you MUST ensure the Site Names used in the CopperCube and Kaizen are EXACTLY THE SAME
Note: If this data was not intended for Kaizen, then please disable CopperTree Intake Server as a data destination within your CopperCube
What can I do to ensure that the data is being sent to Kaizen correctly?
- Ensure your CopperCube is deployed to your client.
- Ensure your client buildings have been created.
- Ensure your CopperCube is mapped to those buildings.
- Then set up your CopperCube to collect the devices you have mapped to those buildings. Use the SAME Site names you used in Kaizen.
- Enable transmission to Kaizen.
- Select your trend logs for collection. Double-check that ALL the device ranges have been accounted for and mapped to a building.
- Allow the CopperCube time to collect all the Trend Logs and BACnet Objects. Typically 24 hrs.
- Invest the time to verify your data is arriving in Kaizen and under the correct buildings.
- If there are problems, invest the time to resolve the issues. Work with Customer Solutions to determine if your data is landing in the Trash. If so, they can usually recover this data.
- Do not assume your setup is correct. If you haven’t verified ALL your data is arriving, then some of it could be LOST!
What is the CopperTree policy for handling data in the trash?
Our policy is all data sent to Trash is automatically deleted. We are unable to buffer this data, due to the high volume of data we experience being sent to trash.
