Roles

This section introduces the core roles in the Nexus Platform and how they interact with it. While one person may perform multiple roles, defining them separately clarifies ownership, access control, and workflows.

Roles in the Nexus platform

Operator

The Nexus operator is responsible for creating and maintaining applications and data collection while devices stay healthy and secure. This is done using the Nexus Portal, where typical tasks are:

• Monitoring devices

  • Investigating alarms for detection of issues

  • Log analysis for root-cause analysis (AI powered)

  • Dashboards for monitoring data flow and custom applications

• Device Management

  • Provisioning new devices

  • Configuring security

  • Deploying functionality

• Modelling

  • Setting up Asset Hierarchies to model physical processes and collect data

  • Manage modules in the Module Store

  • Create applications as combinations of modules

Data Scientist

The Data Scientist is responsible for turning normalized plant data into actionable insights and deployable models that flow back into operations while ensuring traceability and quality.

Nexus ensures that collected data is consolidated in the cloud, in any data store (Fabric, Data Lake, SQL). This enables the data scientist to use the tool stack they’re most comfortable with (Python, R, Data Bricks, SQL).

Typical tasks are:

• Exploring time-series data with ISA-95 context and metadata using query and visualization tools

• Performing feature engineering and experimentation (notebooks/ML frameworks)

• Developing analytical or processing models with the preferred toolchain

• Continuously improving models using an MlOps lifecycle.

Reporting Stakeholder

The Reporting Stakeholder is responsible for delivering trusted, easy-to-understand metrics and reports to internal and external stakeholders. This includes both scheduled and ad-hoc reports and is potentially done using the Nexus Portal dashboards or query tools directly, or using connected BI tools, where typical tasks are:

• Aggregating time-series data with ISA-95 context and metadata

• Building or scheduling recurring reports and alerts for stakeholders

• Reviewing KPIs and trends with drill-downs

Developer

The Developer is responsible for extending Nexus with additional custom modules, data connectors and data stores, if required. This includes scripted automation like CI/CD pipelines, for example when new modules are created. Additionally, custom integrations to external systems , and integrations while keeping deployments repeatable and observable. This is done using the Nexus Portal, Module Store, SDKs, and the API/CLI (often automated via CI/CD), where typical tasks are:

• Building custom data connectors and edge/cloud modules

• Creating applications as combinations of versioned modules

• Defining configuration schemas, secrets, and health checks

• Automating provisioning, security, and deployments at scale

• Integrating with enterprise systems (APIs, UNS/MQTT, data contracts)

• Monitoring telemetry, logs, and diagnostics; iterating safely with rollbacks