Developer Documentation
  • Documentation Overview
  • Development Introduction
  • Getting Started
  • Fundamentals
    • Deploy an App via Pre-defined Sidecar
      • Sidecar Tutorial: Server-side
      • Sidecar Tutorial: Client-side
      • Sidecar Tutorial: Docker & Deploy
    • Deploy an App with Eureka
    • Design Guidance
  • Authentication
    • Accessing data exposed by the platform
    • Single Sign-On
      • Angular
      • Vue
      • Java Spring: Accepting JWT
      • Python Django: Accepting JWT
    • User and Role Identification
  • APIs | Data Integration
    • Submodel Index
    • Masterdata
    • Transactional data
  • Docker Information
    • Ruby Stack
    • Golang Stack
    • Node JS Stack
    • Java Spring Stack
    • Python Stack
  • Connect to the Platform
    • Integrate using Eureka Rest APIs
    • Use our Pre-built sidecar
    • Production deployment
  • Add-on Features
    • IApps-Navigation
  • Testing
  • FAQs | Troubleshooting
  • Registration
    • Application pre-requisites
      • Basic Requirements
    • Register Developer Account
    • Submit basic application info
    • Onboard Application
      • Submit Appstore details
        • App basic information
      • Configure Application
        • App Permission
        • App Data
        • AAS Instance
        • Licensing
        • Access Rights
        • Account Info
        • Terms Of Use
        • Pricing
      • Publish and test
        • Deploy
        • Register into Service Discovery
    • Publish to Marketplace
  • User Experience
  • The business model - How do I get paid?
  • References
    • IndustryApps - Intro
    • What is an Asset Administration Shell?
    • What is ECLASS?
      • How is ECLASS and Concept dictionary are used
    • Industry 4.0 standards
    • Customer Terms of Use
      • Subscription Order
    • Solution provider Terms of Use
      • Contract regions
      • Submission Form ( Solution provider)
Powered by GitBook
On this page
  1. References

What is an Asset Administration Shell?

The Digital twin standard for Industry 4.0

PreviousIndustryApps - IntroNextWhat is ECLASS?

Last updated 2 years ago

The Asset Administration Shell (AAS), a key concept of Industry 4.0 and is used to describe an asset electronically in a standardized manner (see also the layers paragraph). Its purpose is to exchange asset-related data among industrial assets and between assets and production orchestration systems or engineering tools. In summary the administration shell:

  • integrates the asset into Industrie 4.0 communication (e.g. virtual representation of physical object)

  • is addressable in the network and identifies the asset unambiguously (e.g. product is now integrated part of information process)

  • provides a controlled access to all information of the asset (e.g. layers)

  • is the standardized and secure communication interface

  • can integrate intelligent and also non-intelligent („passive“) assets (without a communication interface), e.g. via bar codes or QR codes

  • represents the entire life cycle of products, devices, machines and plants.

(from the Platform Industry 4.0 Details of the Asset Administration Shell, from idea to implementation report)

This means that apart from describing an asset in a standardized way, it can also communicate in an I4.0 compliant manner by using a standard for communication (need for standardization is important). With all parties involved having access to the connected world and all information is defined in a harmonized way (same language), information can be shared in the value chain where the asset can be followed during its life cycle.

IndustryApps follows all prescribed standards for Digital twins and Semantics

Click here for

Details of Asset administration shell
Concepts and Applications of the I4.0 Asset Administration ShellARC Advisory Group
Logo
Asset Administration shell and communication mode