Organize assets

Question and objective

How do users find all relevant resources for a machine or line? Assets give technical data and applications an understandable operational context.

Implementation in Bytefabrik

Asset management builds on StreamPipes. Assets can be organized hierarchically and linked to platform resources. For Manufacturing Insights, Bytefabrik extends this context with assignments of the required data and analysis views.

Best practices for the structure

Start at the level where your team makes decisions. One possible structure is plant, line, and station. Model only those subunits that need their own data association or analysis.

Use production names and stable identifiers. Assign relevant datasets, dashboards, and connections, and identify owners in your operating documentation. After equipment changes, check that the structure still matches the actual installation.

What to consider

A hierarchy is initially an organizational structure, not an automatic calculation rule. Line metrics are not necessarily obtained by adding station values. Each analysis must also verify which events its filters actually associate with the asset.

Avoid duplicate assets for the same machine simply because different teams need their own dashboards. Shared equipment context makes reuse easier.

Machines and assets describes the initial assignment of a source. Additional foundations: Apache StreamPipes Assets.