Skip to main content
Version: 2.7

HumanOS® Runtime Manual

The HumanOS® Runtime is a generic software framework allowing to build dynamic and flexible applications in different domains, such as ICT and IoT.

Terminology

  • HumanOS® stands for Human Operation System
  • HumanOS® Runtime: Runtime environment and SDK for HumanOS® based services and applications
  • HumanOS® IoT Gateway: IoT application running on an edge device. Typically provides connectivity between two or more systems (e.g., CNC Machines to MES platforms)
  • HumanOS® IoT Platform: Micro-service based IoT platform. Typically comes with a management interface (Web-Frontend) and different micro-services to access surrounding systems, like Active Directory, CNC Machines, ERPs, etc.
  • UHAL: Ubiquitous Hardware Abstraction Layer is a part of the HumanOS® Runtime dedicated to access machines and low-level systems.
  • PeMiL: Pervasive Middleware Layer is part of the HumanOS® Runtime coordinating internal data models, communication, and workflows.
  • PeSeL: Pervasive Service Layer is part of the HumanOS® Runtime providing access to other high-level system to HumanOS® data models, like OPC-UA Server, REST API, etc.

Requirements

Hardware

HumanOS® Runtime hardware requirements depend on the configuration applied. It is recommended to configure a maximum of 20 machines per instance for the following reasons:

  • better performance
  • better resilience as not all data flow is interrupted when one instance shuts down
  • better log readability

One instance with the mentioned 20 connected machines with approx. 15 data points (with historization) and a simple data correlation processor and one service connected (e.g. datalogger) will require at least

  • 1 core
  • 2 GB Ram
  • 10 GB diskspace

So the final recommendation for the system configuration in minimum is On Linux

  • 1 core
  • 2 GB Ram
  • 20 GB diskspace

On Windows

  • 2 core
  • 4 GB Ram
  • 40 Gb diskspace

Software

HumanOS® Runtime requires at least Windows 8.1 or Windows Server 2016. Every linux distribution that supports dotnet 6+ should work, however only debian 10+ is supported. Plugins which depend on COM/DCOM (like heidenhain), extended powershell/wsh commanding (like active directory), CIFS/SMB communication (like andron) or CIM/WIM access (like hostcontrol) will also not work. Keep in mind, that some functions may have a different behaviour on linux, like time precision with only supports 1 microsecond resolution, whereas on windows the support is 100 nanoseconds.

Index

  1. Architecture

  2. Basic Configuration

  3. Generic Information Model Nodes

    1. Agents and Skills
    2. AlarmEventPools
    3. Commands
    4. DataNodes
    5. Constants
    6. EntityCollections
    7. Rules
    8. Processing Networks
    9. Workflows
    10. Timers
  4. Device Information Model

  5. Plugins

  6. Instantiation of Schema

  7. Historization

  8. Problem Resolving