Skip to content
SYNGETICTECHNOLOGIES

Industrial integrations

Custom Integrations for Complex Manufacturing Environments

Six integration areas. One engineering standard. Built by people who understand the process behind the data.
SVC-01 · 01/06

Equipment Connectivity

PLCs, CNCs, controllers and OPC UA servers.

Discuss this integration

What we integrate

  • OPC UA servers
  • PLC tags and data blocks
  • CNC states, programs and alarms

Common technical challenges

  • Every controller exposes data differently
  • Tag names only the line engineer understands
  • Machine states inferred from several signals

How we approach it

  • Read-only access at agreed sampling rates
  • Tag map reviewed with process engineers
  • Local buffering — no data lost on outages

Typical deliverables

  • Connector per machine
  • Tag dictionary
  • Health monitoring
SVC-02 · 02/06

Metrology & Inspection

ZEISS PiWeb, CMM results, inspection and lab data.

Discuss this integration

What we integrate

  • ZEISS PiWeb measurement data
  • CMM result files
  • Inspection and lab databases

Common technical challenges

  • Part IDs differ from production
  • Re-inspections and overrides
  • Tolerances change with revisions

How we approach it

  • Map characteristics to part features
  • Reconcile IDs with agreed rules
  • Keep every attempt, nominal and tolerance

Typical deliverables

  • Metrology connector
  • Characteristic mapping
  • Inspection schema
SVC-03 · 03/06

MES & ERP

Work orders, routings, serials, lots and production records.

Discuss this integration

What we integrate

  • Work orders and operations
  • Serial numbers and genealogy
  • Material lots and batches

Common technical challenges

  • Data built for planning, not analysis
  • Timestamps that don't match machine events
  • Heavily customised data models

How we approach it

  • Use MES IDs as the context backbone
  • Align transactions to equipment events
  • Document every field mapping

Typical deliverables

  • Order and lot extraction
  • Traceability model
  • Mapping documentation
SVC-04 · 04/06

Legacy Systems

SQL Server, Access, PostgreSQL, CSV, Excel and old exports.

Discuss this integration

What we integrate

  • SQL Server and PostgreSQL
  • Access and desktop applications
  • CSV, Excel and proprietary exports

Common technical challenges

  • Undocumented schemas
  • Mixed units, dates and time zones
  • Systems you can't change or load

How we approach it

  • Profile data before transforming it
  • Read-only, incremental extraction
  • Keep original records for audit

Typical deliverables

  • Data dictionary
  • Incremental extractors
  • Validation reports
SVC-05 · 05/06

Custom ETL Pipelines

Extract, validate, normalise and deliver — reliably.

Discuss this integration

What we integrate

  • Batch and streaming flows
  • Unit, time and ID normalisation
  • Delivery to databases, APIs and files

Common technical challenges

  • Silent data loss when sources change
  • Clock drift and late events
  • Pipelines nobody else understands

How we approach it

  • Idempotent stages with checkpoints
  • Versioned schemas and contract tests
  • Metrics, logs and alerts on every run

Typical deliverables

  • Pipeline code
  • Automated tests
  • Runbook and dashboards
SVC-06 · 06/06

OEM Integrations

Connectors that feed data straight into your software.

Discuss this integration

What we integrate

  • Your ingestion APIs and SDKs
  • Your data model
  • Your customers' source systems

Common technical challenges

  • Every site has different systems
  • Integrations compete with the roadmap
  • One-off scripts that are hard to support

How we approach it

  • Built to your conventions
  • Reusable logic, per-site configuration
  • Tested and documented for your team

Typical deliverables

  • Packaged connector
  • Site config templates
  • Handover docs

Engineering standards

How Every Integration Is Engineered

Same principles, whatever the source.
P-01

Read-only by default

No writes to production unless explicitly approved.

P-02

Provenance everywhere

Every value traces back to its source record.

P-03

Configuration over code

Site mappings live in config, so connectors are reusable.

P-04

Tested at the boundaries

Contract tests catch silent schema changes.

P-05

Observable

Health checks, logs and metrics in production.

P-06

Documented

Runbooks and mappings are part of the deliverable.

Product and protocol names on this page describe the types of systems we work with. They do not imply vendor certification or a commercial partnership with the vendors concerned.

Deployment & Security

Architected Around Your Infrastructure — Not Ours.

Your data stays where your security rules say it stays. Every architecture is validated with your IT and OT owners — nothing is assumed secure by default.

Deployment specification

SY-DEP · template

Hosting
On-premise Linux or Windows, or an IT-approved host.
Packaging
Docker or native services.
Storage
Local databases for buffering and raw records.
Network
Restricted IT/OT and air-gapped, explicit flows.
Machine access
Read-only wherever possible.
Interfaces
Internal APIs between agreed endpoints.
Retention
Configurable for raw and delivered data.
Operations
Logging, health checks, monitoring.

OT zone

Industrial Equipment

Controllers · instruments

  • Read-only access where appropriate
  • Agreed sampling rates

OT zone

OT Network

Cell / area zone

  • Existing segmentation respected
  • No changes to control logic

Integration boundary

Approved Integration Boundary

Customer-defined

  • Explicit ports and directions
  • Reviewed by your IT/OT owners

Integration boundary

Syngetic Connector

On-prem service

  • Local buffering & retries
  • Logs and health metrics

Platform zone

Customer Platform

On-prem or approved host

  • Internal API delivery
  • Configurable retention
Illustrative topology. Actual network paths, permissions, and hosting are defined with — and validated by — the customer’s IT and OT owners for each deployment.

A system your platform can't reach yet?

Tell us what it is. We'll tell you how we'd connect it.