TIO AUTOPLAT · Data layer · Standalone system

MaindataProduction-grade master data governance

A master data system built for day-to-day production operations. Customers, materials, suppliers and organizations are modeled on a canvas that references standards and code tables; the code center and code-request approval keep requesters and approvers separate, with a full trail; match and merge, relations and version history close the loop, and subscriptions deliver every change reliably downstream. Deployed and run on its own, and works with DataHub governance.

1
set of coding rules across the enterprise
1
golden record shared by every system
100%
changes traced, replayable at any point in time
Separated
request and approval duties

Multiple codes for one thing is a hidden cost

Scattered coding rules, codes requested in spreadsheets, distribution patched with ad-hoc interfaces: master data lacks a system that runs every day.

One thing, many codes
The same customer or material has different codes in ERP, CRM and MES, so reports never reconcile.
Uncontrolled distribution
Downstream systems pull and transform on their own; nobody knows who uses which version.
History is unclear
How often a field changed, who changed it and what it looked like on a given day cannot be answered.

How a golden record is born

Source records → match → merge → assign a code → distribute. Conflicting fields are resolved by rules, and every step is recorded.

  • Match
  • Merge
  • Code
  • Distribute
  • Golden record
  • CUST-000128
  • ERP
  • CRM
  • MES
  • WMS
  • AIDA Q&A
1. Match2. Merge3. Code4. Distribute
ERPChengdu Precision Machinery Co., Ltd.
Phone: 028-8xxx-1201Address: Tianfu Ave, High-tech Zone
CRMPrecision Machinery (Chengdu)
Phone: 028-8xxx-1201Address: North Tianfu Ave
MESChengdu Precision Machinery
Phone: —Address: 88 North Tianfu Ave, High-tech Zone
→ ERP
→ CRM
→ MES
→ WMS
→ AIDA Q&A

Built for daily production operations

From code request to distribution, every step has an owner and a trail; requesters and approvers are separated, and illegal transitions are blocked.

Requester
01
Request code
System
02
Duplicate check
04
Assign code
05
Record active
06
Distribute
Approver
03
Approve
Request and approval separated
Code center, request center and approval form one coding and control process, with segregated duties and a full trail.
Daily record maintenance
Records are maintained as part of daily operations; active, disabled and restored states are explicit, and only active records flow downstream.
Prebuilt object packs
Common master data objects come prebuilt, shortening modeling at project start.

Six capabilities

01
Canvas entity modeling
Define entities, attributes, rules and relations on a canvas that references standards and code tables; preview, publish and version.
02
Code center and approvals
Unified coding rules; requests are de-duplicated automatically, and create, change, reject and resubmit all go through approval, with freeze and unfreeze.
03
Lifecycle management
Active, disabled and restored states are explicit; only active records can be used, and illegal transitions are blocked.
04
Built-in quality
Checks run before writes and block bad data; works with the DataHub quality console.
05
Match and merge
Matching rules produce candidates that are merged into golden records manually or automatically, with traceable merge history.
06
Subscription and open access
Subscribe by entity and push downstream via webhook, API, Kafka or database, with lineage and audit recorded.

Point-in-time replay

Drag the timeline to see the record as it was. Rollbacks append history instead of overwriting the past.

  • 2025-03
  • Created
  • Chengdu Precision Machinery
  • 2025-08
  • Merged CRM record
  • Chengdu Precision Machinery Co., Ltd.
  • 2026-01
  • Address changed
  • Chengdu Precision Machinery Co., Ltd. · 88 North Tianfu Ave
  • 2026-06
  • Credit grade updated
  • Chengdu Precision Machinery Co., Ltd. · Credit A
as-of 2026-06 · Credit grade updated
CUST-000128 · Chengdu Precision Machinery Co., Ltd. · Credit A

Reference master data structure

SourcesERP · MES · WMS · CRM · SCM
CollectionBatch import · interface sync · CDC
ManagementModels · codes · data maintenance · integration
GovernanceStandards · quality rules · security levels
DistributionSubscription · exchange · scheduling · open APIs
ValueSharing · quality · cost · risk · decisions

Real console screens

Entity modeling, relations and version history in one workbench.

  • Entity modeling
  • Entities, attributes, rules and relations defined visually on a canvas.
  • Relations
  • Define relations between entities and maintain instance links.
  • Version history
  • Query any record's state at a point in time.
Entity modeling

Entities, attributes, rules and relations defined visually on a canvas.

Runs on its own, works with DataHub

Maindata is a standalone master data system; when connected to DataHub, master data joins its quality, lineage and open-service chain and can be referenced by AIDA data questions and AIHub Wiki.

Keep master data running right, every day

Book a demo and see Maindata handle code approvals, match and merge, and subscription distribution.