Assets

what are assets? an asset is a logical representation of a physical component in your production environment such as a machine, line, tank, sensor, or entire facility in factry historian, assets are used to organize measurements, events, and metadata in a way that reflects your actual production setup why does it matter? assets provide structure and context to your data without them, your measurements would just be flat lists with names, which can be hard to navigate and hard to relate to real world equipment for some people in the plant therefore, setting up a proper asset hierarchy is key for making data available to many stakeholders in your organization with assets you can assign measurements docid\ xqwlemdcnfff3 0h gmms , calculations docid\ opiodkgnngyjedx6zkg d and events docid 0ith2zlcais5yywhsdtje to specific equipment dashboards and reports become more intuitive ("show me all data for line 3") you can filter and drill down in a structured way how does it fit in the system? assets form a hierarchical structure that mirrors your plant layout each asset in the tree can have, regardless of its level a set of asset properties, which are mapped to measurements or calculations one ore more events linked to it metadata such as asset type, tags, or status children or parent assets this hierarchy is used in visualizations, dashboard variables, and alerts example let's say you have a site with a production line and a storage tank each of these, and their parents (enterprise, site, area, line) or children (mixer) are assets the mixer has a level asset property, and a batch event (see events docid 0ith2zlcais5yywhsdtje ) linked to it the storage tank has material and level asset properties docid\ cr6hbrdsl8fsuvlvm20if when you use it you’ll interact with assets when designing your asset model during system setup, and when equipment is added or changed assigning new data to machines or lines creating dashboards per area or line, or when quickly browsing data ad hoc attaching events such as batches or alerts to specific equipment most user facing features such as dashboards, events, and calculations are asset aware common misconceptions an asset is not just a label it has structure and can be queried and filtered assets are not always one to one with physical machines sometimes they are logical groupings such as "packaging area" measurements can be linked to multiple assets, but that should be done carefully to avoid confusion best practices use your real world equipment and layout as a starting point when designing the asset hierarchy apply consistent naming, especially when dealing with similar lines or repeated structures consult industry standards like isa 95 when designing the asset hierarchy keep the hierarchy shallow and focused avoid unnecessary nesting enrich assets with metadata such as asset type, manufacturer, or production line use the bulk importing functionality more information creating an asset docid\ m0fam6gdf1dq5eaaimenn bulk asset creation and editing docid\ wre04qni2tob9hy lku6s trending assets properties docid\ nfccwy9aovwf8xpvni13k