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
  • Technology fit:
  • Architecture & Security fit:
  • Business Model Fit:
  1. Registration

Application pre-requisites

Fit to Industry 4.0

PreviousRegistrationNextBasic Requirements

Last updated 2 years ago

This section provides details of basic requirements for Application to be on boarded on IndustryApps.

Technology fit:

The product should be cloud ready and following a scalable architecture - Target of IndustryApps is make your product accessible to global customer - not with the classical approach of local consulting and premise deployments. Please refer to for details

Architecture & Security fit:

Our customers are Industrial manufacturers and leading companies. It is important to be transparent in terms of security and architectural components enabled in your solution. IndustryApps will be providing you with a basic questionnaire and performing some assessment to ensure your product fit.

Business Model Fit:

IndustryApps target is to offer a mode where your solution can be deployed as plug & play at customer instance and all master data requirements are automatically loaded. The customer experience we want to offer is customer is able to use your solution as soon as they subscribe. The only exception will be if there are specific additional data requirements.

The platform allows your product to operate in a Plug and play method by offering you all the master data and transactional data over a standard API. But if your solution cannot be offered this way and require specific customization or local infrastructure then it may not be a possible fit.

basic requirements