Profile Trees

So sub profiles can be used to build trees of profiles. With one profile as the root node and an arbitrary branching/nesting 'below' it.

Node Profiles and Profile Networks

By combining the nesting and chaining of profiles, you have the ability to build complex profile networks.

Each profile that integrates other profiles then acts as a collecting/binding node in your profile network, i.e. as vertical integration and the profile chains as horizontal integration. By 'vertical' we mean that you can build tree-like layers of profiles and with 'horizontal' that you can walk along a profile chain within a layer, so to speak.

In order to optimally support the concepts of vertical and horizontal networking (and the integration of your employees), Lobster_data now offers the add-on modules Workflow and DataCockpit. Take a quick look at them. It's worth it. You can find a concrete example in section Automated Workflows (→ Vertical integration with sub profiles). Connect. Control.

Simple Application Example (Vertical Integration)

Even though profile nets can be a complicated subject, they are a great simplification for many users in classic application cases, and as a result offer a significantly increased clarity/traceability. The following is an example of a classic EDI case.

Classical EDI: Sequential data enhancement.

Lobster_data Multi Source: Parallel collection of several sources in the source structure. This approach is more compact and clearer and allows a simple decomposition of a problem into sub problems. In addition, better encapsulation is possible and service profiles can be offered. For example, have your SAP expert create a profile once for accessing the SAP system. Afterwards, any user can integrate it, even without SAP knowledge.

Industry 4.0 and IoT

But even beyond this rather classic example, this concept offers enormous advantages in the increasingly emerging topics of IoT and Industry 4.0, in order to master the complexity involved. You solve one sub-problem in a service profile here, another sub-problem in another service profile there, and finally you drag everything into a clearly structured bundling profile. If you implement your service profiles cleverly, it is also possible to reuse them for solving other problems. Simple, dynamic and scalable integration for your own Industry 4.0 needs using all your legacy systems and without the need for a rigid, centralised and monolithic software. Quickly build smart networks for your individual data needs, also for small and medium-sized businesses.

Please refer to the corresponding section in the introduction to Lobster_data and specifically section Automated Workflows (→ Vertical integration with sub profiles).