DSM
Data Source Mapper
Connect SQL databases and real-time tags so transactional and field data can move under explicit rules.
The problem
MES, ERP, WMS and equipment data use different names, structures and update cycles. One-off integrations are difficult to trace, govern and reuse.
The outcome
Use mappings, transaction groups and schedules to create an inspectable, retryable and independently deployable data exchange.
Operational context
Make mappings, transactions and retries visible.
DSM makes tables, tags, direction, transformation and update conditions explicit so data exchange no longer hides inside one-off integration code.
- 01SQL sources and destinationsRead and write PostgreSQL and MariaDB through a consistent interface without binding the data flow to one database.
- 02Transaction groupsTreat multiple field updates as one unit of work with explicit consistency and failure boundaries.
- 03Mapping governanceMake table fields, tags, direction, transformation and update conditions explicit instead of hiding them in custom code.
Core capabilities
From product module to reusable operational capability.
The codebase includes PostgreSQL and MariaDB sources, destinations and transaction-group services. Enterprise-specific data models and consistency rules are defined during implementation.
SQL sources and destinations
Read and write PostgreSQL and MariaDB through a consistent interface without binding the data flow to one database.
Transaction groups
Treat multiple field updates as one unit of work with explicit consistency and failure boundaries.
Mapping governance
Make table fields, tags, direction, transformation and update conditions explicit instead of hiding them in custom code.
Flexible deployment
Run independently or alongside the core as a modular monolith while preserving a path to later isolation.
Data and responsibility flow
Every step stays visible, verifiable and governable.
- 01Read source data or real-time tags
- 02Transform fields through mapping rules
- 03Write the destination as a transaction group
- 04Record the result and retry recoverable failures
Use cases
Start with one high-value loop.
- Send work orders to the equipment layer
- Write equipment results back to MES
- Synchronize recipes and batch parameters
- Map master data across systems
Responsibility boundary
DSM is a governed exchange layer, not an unrestricted database replication tool. Sensitive tables, write scope and credentials must follow least-privilege configuration.
Current technical baseline: The codebase includes PostgreSQL and MariaDB sources, destinations and transaction-group services. Enterprise-specific data models and consistency rules are defined during implementation.