App (Cloud Foundry)¶
The term app denominates multiple different software artifacts. In MindSphere an app can consist of a single service (functionality and deployed as an instance) or a combination of multiple services that might rely on multiple Backing Services (e.g. MongoDB, RabbitMQ). Especially, in the cloud software uses micro services oriented architectures and patterns that lead to services that have a strict set of functionality and communicate with other services. An app might consist of 5 services, but only one has a frontend (e.g. website).
Aspects are data modeling mechanisms for assets. Aspects group the data points based on logical sense. For example, the pump skid has an aspect e.g. "Energy_consumption" that contains the data points: "power", "current", "voltage" etc. An Aspect is specified in Asset Manager and its name can be freely chosen, but should bring together a logical grouping of data points and a physical asset.
An asset is a digital representation of a machine or an automation system with one or multiple automation units (e.g. PLC) connected to MindSphere. MindSphere data collection and data provisioning is based on so called (virtual) assets. This can be anything such as a pump, motor, PLC, an entire tool machine, a production line, a robot, a crane, a car, a windmill and so on. The data of an asset is collected and sent to MindSphere to make that data available for further processing and analytics.
Asset Identifier is an identifier assigned by the manufacturer of the device, to which MindConnect Nano will be connected. After the onboarding process, MindConnect Nano is connected to this device. The serial number identifies the asset to which the data belongs.
Asset Manager is a web-based Graphical User Interface (GUI) for for asset configuration. According to these configurations, the following functions are available: assets can be created, onboarded, modified, cloned, moved, deleted or offboarded.
An asset type is a sort of a product line made by a manufacturer.
Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, content delivery and other functionality to help businesses scale and grow. Explore how millions of customers are currently leveraging AWS cloud products and solutions to build sophisticated applications with increased flexibility, scalability and reliability.
AWS native Services¶
AWS Native Services are services that can be provided as a Custom Service in Cloud Foundry. For an example a customer can provide AWS Kinesis from an own AWS account with the given address and credentials to a space in Cloud Foundry.
Backing Service (Cloud Foundry)¶
A Backing Service is any service an app may consume over the network as part of its normal operation. Examples include data stores (such as PostgreSQL), messaging/queuing system (e.g. RabbitMQ), caching system (such as Redis) and logging services. A Backing Service can be also described as a “factory” which produces Service Instances based on Service Plans.
Buildpack (Cloud Foundry)¶
Buildpacks provide framework and runtime support for your applications. Buildpacks typically examine user-provided artifacts to determine what dependencies to download and how to configure applications to communicate with bound services. For example Java and nodejs are considered to be buildpacks.
Cloud Foundry Runtime¶
Cloud Foundry Runtime is an already configured and provisioned environment that is in production.
Cloud Foundry Org¶
An org is a development account that an individual or multiple collaborators can own and use. All collaborators access an org with user accounts. Collaborators in an org share a resource quota plan, applications, services availability, and custom domains.
Cloud Foundry Space¶
Every application and service is scoped to a space. Each org contains at least one space. A space provides users with access to a shared location for application development, deployment, and maintenance. Each space role applies only to a particular space.
Cloud Foundry Routes¶
The Cloud Foundry Gorouter routes requests to applications by associating an app with an address, known as a route. We call this association a mapping. Use the cf CLI cf map-route command to associate an app and route.
Components represent built-in functionalities in MindSphere. Components are: Asset Manager, Fleet Manager, Settings, UTC Reporting. For the complete list and description of available components, refer to the MindSphere documentation.
Containers are isolated environments on a shared operating system. Unlike VMs, containers do not bundle a full operating system, but only required libraries and settings for running the intended software. Containers are isolated on the kernel layer. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same regardless of where it is deployed.
Data points refer to elements (variables), which allow values to be obtained from data sources (OPC UA or S7 etc.). They are combined into a relevant aspect. For example, "temperature" and "torque" are data points of the aspect "Energy_consumption". Data points are configured in Asset Manager. In Fleet Manager, their values are visualized as time series.
A data source is a physical element of a device, which can be monitored by MindSphere, e.g. OPC UA Server or S7.
Developer (Cloud Foundry)¶
Individual person that develops apps deploys them to the Development System for testing purposes. A developer may configure assets, data access and using the Fleet Manager for testing on different levels.
Development System (Cloud Foundry)¶
The Developer Services Offering provides a PaaS environment for developing and testing apps. Underlying technology for the PaaS is Cloud Foundry. The Development System is an access to Cloud Foundry with certain limits depending on the package purchased. A customer receives a Cloud Foundry Org with a specific amount of memory, developers and routes.
In the Development System a customer can use Backing Services in form of Service Plans. General access is provided through the Cloud Foundry CLI and the Developer Cockpit.
Docker is a container platform that eases configuring, creating and sharing specific development environments and packaging software to be deployed everywhere. Docker provides a runtime and image format and a command line interface.
Droplet (Cloud Foundry)¶
A Droplet is an archive within Cloud Foundry that contains the application ready to run on Diego. A droplet is the result of the application staging process. The process in Cloud Foundry by which the raw bits of an application are transformed into a droplet that is ready to execute.
In Fleet Manager, an event is a change of a data point state. Events are used for requests. With a rule it is possible to define a request which will be created in MindSphere when the event is triggered. Besides monitoring a rule, an event description (e.g. "The limit is exceeded, this may indicate damage in the pump."), the resulting action (e.g. "Please contact your hotline.") and priority ("urgent", "important" or "info") can be defined. See also request and rule.
Fleet Manager is a visualization tool which provides an overview of existing assets and their information (asset name, customer name, location). Fleet Manager displays your configured assets, aspects with data points in charts, a list of all requests, etc.
MindConnect Elements are devices for transferring data and allow connectivity to MindSphere such as MindConnect Nano, MindConnect IoT2040 or MindConnect FB.
MindSphere is the Siemens Industrial IoT operation system comprising the core cloud services and applications, whereas the MindConnect Element provides secure and easy connectivity from the field or machine to MindSphere. In MindSphere, submitted data by a MindConnect Element is processed and stored for analysis and further management purposes. For more information, refer to the MindSphere documentation.
Organization is the part of hierarchical asset configuration in Asset Manager. Within organization, areas/assets are specified. As the administrator (OEM), you manage organizations, their customers and assets. As the user of an organization, you can access the assets assigned only to this organization. In the context of MindSphere, an organization can be anything and is defined by the administrator depending on their requirements: customer, cost center, branch etc.
Production System (Cloud Foundry)¶
The Production System is in terms of technology equivalent to the Development System. The difference is that a Product System can be used commercially for providing customers access to the running apps.
Requests are the messages which log asset incidents based on predefined rules. You can create manual requests as well as requests for the regular acquisition of measured quantities with measuring series. See also event and rule.
With rules, you can configure an automatic monitoring of data points on events. For example, a request will be created automatically by the system, if a value exceeds or falls below a threshold (edge trigger). See also event and request.
(Backing) Service Instance¶
Service Plan (Cloud Foundry)¶
A Service Plan is a specification of a Backing Service in terms of memory, storage space, number of instances (for clusters), number of concurrent connections and additional NFRs like High Availability.
Settings is a web-based Graphical User Interface (GUI) for user, organization and role configuration.
Time series is a sequence of measurements which are produced by data sources over time. Analysis and visualization tools (e.g. Fleet Manager) can retrieve collected time series and present it to the user after processing. In Asset Manager, the measurements, that have to be collected, can be specified.
A tenant is basically a representation of a real-world organization. It has users, data, assets, entities, and many kinds of other properties.
Tenant for Production System depends on the user of the app. This could be either a tenant from the provider or a tenant from a customer.
User-Provided Service (Cloud Foundry)¶
User-Provided Services enable you to create and manage service instances for services hosted outside Cloud Foundry (e.g. AWS Kinesis). The benefit of having a user-provided service is that developers do not need to hard-code credentials for a service instance in the application.
A Virtual Machine (VM) imitates dedicated hardware and runs an operating system. Software running inside the VM and end users have the same experience as on a dedicated system. IaaS providers use a so called hypervisor which provides the VM with the configured hardware which is provided by the host. In the IaaS environment the type of hardware can be almost anything that is available in a data center.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.