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
  • User Instance events steps
  • Allow access through Single Sign-on
  • Utilising User Data
  • User Roles

User Experience

PreviousPublish to MarketplaceNextThe business model - How do I get paid?

Last updated 2 years ago

The users on IndustryApps choose applications according to primary apps or Add-on apps categories, each application chooses its type during app onboarding. There are various pricing options available such as fixed cost / Factory based, Dynamic cost / factory based on users or number of machines with subscriptions.

Once the user will be notified of the required data permissions for utilising the application. The applications which the user has added onto their accounts are organised into categories and sub-categories.

According to each sub-category the user will see the registered applications with their dedicated account.

User Instance events steps

The following sequence of events should be taken into account for application development on IndustryApps. Depending on the users instance state with the designated application, different designation takes place for each user. In this case, an Instance is referring to unique data belonging to each user such as:

  • Users name (i.e euser).

  • Factory selected.

  • Language selected.

  • Company code.

  • Role permissions.

Allow access through Single Sign-on

If your application has Single Sign-on (SSO) enabled, restricted resources in the application will be available without requiring a secondary login by the user. The required JWT would be forwarded to the right locations so that the user would have a seamless interaction with the platform, loading their instance on the platform as shown below.

Utilising User Data

Once the user instance has been loaded either through an existing instance or by generating a new instance, the application can utilise the data accordingly and present functionality as appropriate.

User Roles

Vendors can define user roles for each application, with permissions set for each role (described as a module) with a dedicated description. See the example below for a visual representation:

Once user role permissions have been defined, the administrator on the users account can dedicate a role for each of their accounts. The user navigates to their administration panel to dictate roles accordingly.

Additional information about user context as described above .

Additional information about utilising API data through the platform .

can be found in Authentication
can be found in API Data Integration
Example of a loading Machine data for a maintenance application in instance
Applications > {App Name} > Access Rights
Administration > Admin > Group Master > Add/Edit Group