Master Data
Manage reference data including OEMs, equipment models, components, and positions.
Overview
Master Data in MineSync defines the reference records that the rest of the system depends on. This includes equipment manufacturers (OEMs), equipment models, machine families, component catalogs, machine positions, and work activities. Master data is global -- it is shared across all tenants but can only be created and modified by Admin users.
Key Concepts
Data Hierarchy
Master data follows a structured hierarchy:
OEM (e.g., Caterpillar)
└── Equipment Model (e.g., 793F)
└── Machine Family (e.g., Mining Trucks)
Component Catalog (e.g., Engine > Fuel System > Fuel Pump)
└── Machine Position (e.g., LH-Front, RH-Rear)Global vs Tenant Data
Master data records are not tenant-scoped. An OEM or equipment model created by one admin is visible to all tenants. This avoids duplication and ensures consistency across organizations.
How to Use
OEMs (Original Equipment Manufacturers)
OEMs represent equipment manufacturers such as Caterpillar, Komatsu, or Liebherr.
| Field | Description |
|---|---|
| Name | Manufacturer name (required, unique) |
| Code | Short code (auto-generated from name if not provided, max 10 characters) |
| Logo URL | URL to manufacturer logo |
| Website | Manufacturer website |
| Description | Free-text description |
| Contact Info | Structured contact information |
Actions: Create, update, soft-delete (sets isActive to false), find-or-create (for imports).
Equipment Models
Equipment models are linked to an OEM and optionally to a machine family.
| Field | Description |
|---|---|
| Name | Model name (required, unique per OEM) |
| Display Name | Human-friendly name for UI display |
| OEM | Parent manufacturer (required) |
| Family | Machine family category |
| Description | Free-text description |
| Image URL | URL to model image |
| Specs | JSON object for technical specifications |
Actions: Create, update, soft-delete.
Machine Families
Machine families categorize equipment types and support hierarchical nesting (e.g., Mining > Trucks > Haul Trucks).
| Field | Description |
|---|---|
| Code | Unique identifier code |
| Display Name | Human-readable name |
| Parent | Optional parent family for nesting |
| Icon | Icon identifier for UI display |
| Sort Order | Display ordering |
Actions: Create, update, soft-delete.
Component Catalog
The component catalog defines the parts and assemblies that can be tracked on equipment. Components support a parent-child hierarchy (e.g., Engine > Turbocharger).
| Field | Description |
|---|---|
| Name | Component name |
| Code | Unique identifier code |
| Category | Grouping category |
| Parent | Optional parent component |
| Default Target Hours | Expected life in operating hours |
| Sort Order | Display ordering |
Actions: Create, update, soft-delete. Components with active usage in profiles or maintenance logs cannot be deleted.
Machine Positions
Machine positions define where a component is installed on a piece of equipment (e.g., LH-Front, RH-Rear).
| Field | Description |
|---|---|
| Code | Unique position code |
| Display Name | Human-readable label |
| Category | Grouping category |
| Sort Order | Display ordering |
Work Activities
Work activities define the types of maintenance or operational tasks that can be logged.
| Field | Description |
|---|---|
| Code | Unique activity code |
| Display Name | Human-readable label |
| Category | One of: Maintenance, Operations, Inspection |
| Sort Order | Display ordering |
Common Questions
Can I delete master data that is in use?
Soft-delete (deactivation) is used. Records are marked as inactive rather than physically deleted, so existing references remain valid.
Who can modify master data?
Only users with the Admin role can create, update, or delete master data records.
Do master data changes affect other tenants?
Yes. Because master data is global, changes are visible to all tenants. Create new records rather than modifying existing ones if the change is tenant-specific.
How do I import master data in bulk?
Use the backup import feature or the "find-or-create" OEM endpoint during data imports. The system will match existing records by name before creating new ones.