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
  • Adding your own Digital Twin Model
  • Adding a Submodel Instance
  1. Registration
  2. Onboard Application
  3. Configure Application

AAS Instance

How to share information back to Digital twin.

PreviousApp DataNextLicensing

Last updated 2 years ago

Interoperability is a critical feature of Industry 4.0. Assets in Industry 4.0 should be able to share information along both horizontal and vertical value chain with no limitations over technology frameworks or protocols or evolving standards.

IndustryApps enables this feature by simply ensuring every application is able to not just read data from a digital twin but able to share information back to Digital twin. This section explains how you can inject your own SubModel back into as Asset.

Every Application in IndustryApps has ability to share information back to its Digital Twin. This allow solutions to interoperate and deliver additional value to our customers.

Adding your own Digital Twin Model

Here you can publish and add your own Digital Twin. This is relevant if your solution works with a specific hardware like an IoT sensor or a specific gateway. You can build Digital twin of your asset and ship them to your customers to also have a simple plug and play experience.

This section if only relevant for solutions with dependency on specific Hardware assets like IoT. For all others please see Submodel instances

Adding a Submodel Instance

This is where you add your own Sub model instance to existing Asset. APIs documentations on how to inject an AAS is provided under the Developer documentation section. Delivering data back to Digital twin would allow other applications to react to changes.

For eg: Lets assume you have an OEE application that measure machine state and productivity in real time. if you publish the result back to Digital twin, then another solution which offers say Maintenance or Production scheduling can offer alerts and notifications to customers or even specific functionalities to make it the solutions inclusive.

Sharing information back to Digital Twin.
Adding your AAS instance