Nexeed
    • Introduction
    • User manual
      • Basic setup
      • Product tab
      • Configurator tab
      • Editor tab
      • Comparison tab
      • Query tab
      • Importer tab
      • Scopes tab
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • SPECS/SetupSpecs-services
        • SPECS/SetupSpecs-web
      • Migration from previous versions
        • To 2025.01.02
        • To 2023.02.00
        • From MES to 2023.01.00
        • From MES to 2023.02.00
        • Cleanup FILES and FILE_SYSTEMS table
        • Resources mapping from MES to IAS
      • Setup and configuration
        • pq/setupspecsbackend
        • pq/setupspecsui
        • Resource limitation
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Guide to Setup Specs service logs
      • Backup and Restore
      • Logging and monitoring
        • Implemented logging
        • Module health verification endpoints and k8s probes
      • Known limitations
        • Deployment
        • Multitenancy capability
        • Size limit for import files
    • Developer documentation
      • Concepts
        • Dataset structure
        • Release management
        • Scopes
    • API documentation
      • HTTP API
      • Async API
Setup Specs
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Setup Specs
  • Developer documentation
  • Concepts
  • Dataset structure

Dataset structure

The dataset structure is a hierarchical representation of type data, including various members and their attributes. Below is a description of the most important elements of the structure:

TypeData

  • PartitionType: Type of the partition. 0 = LocationSpecific, 1 = ProcessSpecific 2 = ApplicationSpecific"

  • PartitionId: Name of the dataset. Could be the location id of a station or a alias name

Members

The Members array contains multiple objects, each representing a different part of the dataset. Each member can have nested members or array elements.

Example member structure

{
  "Members": [
    {
      "Members": [
        {
          "Value": "DefaultValSub",
          "Id": "da66c822-db86-48ae-9bb7-35e29db8467d",
          "Name": "SubVar_1",
          "DefinitionScopeValue": 9,
          "RevisionDate": "2025-01-31T10:56:27.9085735+01:00"
        },
        {
          "Value": "DefaultSubVar_2",
          "Id": "b760b529-37ad-49de-ad69-e221356d8b63",
          "Name": "SubVar_2",
          "DefinitionScopeValue": 9,
          "RevisionDate": "2025-01-31T10:56:27.90858+01:00"
        }
      ],
      "Id": "c798351c-994c-42e3-8fa6-58f27ca025b8",
      "Name": "SubStructureSimple",
      "DefinitionScopeValue": 0,
      "RevisionDate": "2025-01-31T10:56:27.9085675+01:00"
    }
  ]
}

Important attributes

  • Value: The value of the member.

  • Id: Unique identifier for the member.

  • Name: Name of the member.

  • RevisionDate: Can be ignored as the revision number is stored only in the top level. The other revision fields below in the hierarchy exists only for downward compatibility.

ArrayElements

Members can also contain ArrayElements, which are arrays of objects. Each object in the array can have its own members and attributes.

Example array element structure

{
  "ArrayElements": [
    {
      "Members": [
        {
          "Value": 44,
          "Id": "72110524-cccb-43e3-943c-a6f029123e4c",
          "Name": "BelowArrayParam1",
          "DefinitionScopeValue": 9,
          "RevisionDate": "2025-01-31T10:56:27.9086096+01:00"
        },
        {
          "Value": 23,
          "Id": "9f8c6abf-b129-41f6-a28b-e8e6042e7a59",
          "Name": "BelowArrayParam2",
          "DefinitionScopeValue": 9,
          "RevisionDate": "2025-01-31T10:56:27.9086134+01:00"
        }
      ],
      "Id": "c4a3cb53-6397-4173-8004-bb018c5853f5",
      "Name": "SubFolderBelowArray",
      "DefinitionScopeValue": 0,
      "RevisionDate": "2025-01-31T10:56:27.9086058+01:00"
    }
  ]
}

Root

The root element of the dataset structure.

  • Id: "827a1107-1e8b-4985-b8ed-754a2e2d68d5"

  • Name: "Root"

  • DefinitionScopeValue: 0

  • Revision: 20894494

  • RevisionComment: "test"

  • RevisionDate: "2025-01-31T09:56:27.914303"

Query

The query object contains the search parameter for queering the dataset.

  • area: "Test_Area_Ali"

  • family: "Fam3"

  • type: "Product1"

  • variant: "04"

  • partitionType: "ApplicationSpecific"

  • id: "TestDataset_1"

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses