Asset Organization

An Asset configuration will frequently form the backbone of an ICONICS deployment. It allows for a hierarchical structure for data and a superior means of accessing and organizing your system. These are the basics to understand how it works, and how to get started with it.

Step through the relevant parts of an asset configuration, including what to think about when designing and how to organize it to be most effective.

One of the powerful features of Assets are the ability to associate commands with them, allowing users to directly interact with the asset to view data and perform actions. These commands are frequently used for navigation within applications, control or toggling properties of assets, or triggering reports and transactions related to that asset.

The Asset configuration environment fully supports defining asset templates, allowing for easier and more consistent asset deployments. These templates strike the right balance between consistency between assets and unique identification of assets to allow them to be most useful to your application.

The Asset configuration is not just a server-side function, it also has a runtime viewer component that allows you to work with your assets as a client as well. This covers the addition of an asset tree into a traditional SCADA dashboard.

The Bulk Asset Configurator (BAC) is vital to scaling out the deployment of assets for large enterprise applications. It leverages an Excel file mapped to your asset templates to allow for rapid configuration of thousands of assets. The BAC is also well suited to long-term project management, as it allows for simple redeployments and configuration updates.

A collection of tips, tricks, and other suggestions for how to get the most out of your asset configuration.