Building Apps on Factory Data

Build customized industrial applications through AI conversations. Applications can use factory data and include built-in capabilities such as role-based access control, version management, and external deployment.

Building a Tier0 App

Create a project before building an application.

• Project is used to categorize applications and manage application access control.
• Applications in one project can work as related functional modules of a complex system.
• Data in each project is independent from other projects.

Writing Prompt

Make sure your prompt covers at least the following aspects for the agent to generate an application that better fits your requirements.

• Application Purpose: What is the purpose of the application?

  Create an equipment maintenance application for factory technicians.

• Application Data: What data does the application use and where is it?

  Platform Plan

  Connect data to UNS and state the UNS topic in the prompt.

  The application should use equipment status, alarm records, and maintenance history from the xxx UNS model.

  Builder Plan

  Agent will automatically simulate data for startup during initialization.

• Application Function: What does the application do?

  The application should allow users to monitor equipment conditions, submit maintenance requests, and track repair progress.

When you are on Builder

The Builder plan does not currently support UNS, but simulated data is available. For more specific data integration needs, please contact our team at [email protected].

To build applications faster

Templates of common industrial applications are provided in Library. You can use a template and change features on top to build an application much faster.

Access Control

Role-based access control is applied on both project and application.

• Project roles
  • Can Edit: Full access to the project except deleting it.
  • Can Launch: Can only see the project in Launchpad and use allowed applications inside.
• Application roles
  • Automatically generated by agent based on business logic of the application.
  • Can only be assigned after added as a member of the project.

If you want to assign your own roles

State the roles and permission scope in the prompt, and the agent will compare them with auto-generated roles. When your role is in conflict with the generated role, the agent will confirm with you.

Application role assignment is a MUST

To access an application, you must have application roles assigned. Even project owner cannot see the application in Launchpad without application roles.

Version Management

Applications exist on Tier0 in 3 shapes.

• Draft: The latest state of the application. Changes on this version will not affect other versions if not deployed.
• Snapshot: Saves the application at the time of taking the snapshot. Deploying a snapshot version takes down the current Active version.
• Active: The current online version of the application.

Version switch

• Deploy a draft, the active application updates to a newer version.
• Deploy a snapshot, the active application rolls back to an earlier version.

Export to External

Once the application is ready, you can export it from the Preview page for external third-party environments or Tier0 Enterprise.

• Download Source Code: Export source code of the application for secondary development.
• Export Bundle: Specifically exported for local import on Tier0 Enterprise.

Next

• Analyze UNS Data — Analyze UNS data with Marimo Notebook and Python.
• Best practice: connecting industrial protocols - Examples of common data source connections.