TABLE OF CONTENTS
In this section an overview is given of the Asset Manager of the platform. An Asset is usually represented by a Container within the platform. The tasks of the Asset Manager in the platform are the following:
- Create and edit Containers (which represents an asset) in a certain Space
- Create and edit Containers Types
- Add properties to a Container
- Manage all available Containers and their permissions
- View properties, permissions, tags and metadata of a Container Type
- Define relations between Containers using filters
- Edit filter for Containers
To access the Asset Manager within the platform click here:
This is a broad term. For example, in business administration (German: Betriebswirtschaftslehre) it is used to refer to something of value that is owned or held by an organization. Another example is in the sense of infrastructure asset management, for which even the ISO 55000 standard exists. In IoT platforms, the term asset is typically used to refer to what physical thing it augmented or integrated with technology. For example, a machine would typically be referred to as an asset. In the platform, assets are represented via containers.
Is of one particular container type. Has meta-data that adheres to the JSON Schema of the container type. Independently from the container type, it has zero, one or more filters that govern its content. Also independently from the container type, it has a set of tags.
All containers need to be of a container type. A container type has a JSON Schema for the meta-data JSON documents of all containers of that type.
A persistent set of criteria to dynamically select resources at runtime. The criteria in a filter are either all linked via boolean AND (“matches all of the following criteria”), or all are linked via boolean OR (“matches any of the following criteria”). Filters can be reused.