For IT Partners

Leave PLC integration and field work to us.
Focus on your platform.

DONG-IN ENSIS takes care of the OT scope in smart factory and AI factory projects, from control panel design and build to PLC integration and a standard data API.

Propose a partnership → Partnership models
Pain Points

If your projects keep
stalling in the field

Every site has different PLC brands and protocols
Installing and maintaining data gateways is a burden
You cannot take electrical safety responsibility for panel modifications
Collected data comes in different formats for each machine
You lack staff for on-site installation and commissioning
Your platform is ready, but you need plant sites to deploy it
Partnership Model

Three ways
to work together

MODEL 01

OT scope delivery

We handle control panels, PLCs and site installation in your projects.

  • Panel design · build · installation
  • PLC · drive · sensor integration
  • Commissioning · maintenance
MODEL 02

Data integration

Equipment data collected by our panels is delivered to your platform through a standard API, ready for MES integration, monitoring and AI analytics.

  • Standard data structure
  • REST API · WebSocket
  • MES · AI · digital twin
MODEL 03

Joint proposals

We find manufacturing customers and funding programs together and propose jointly.

  • Joint customer development
  • Joint government program bids
  • Joint sales with demo equipment

DONG-IN ENSIS

Field data · OT

  • Panel design · build · installation · commissioning
  • PLC · drive · sensor integration
  • Encrypted data transfer · DataHub (cloud or on-premise)
  • PLC control link for AI setpoints (in pilot)
  • Standard data model + API

IT PARTNER

Platform · services

  • MES · ERP · EAM integration
  • AI analytics · predictive models
  • Digital twins · dashboards
  • Customer-facing platform operation
Data

Different machines,
one data structure

Data is delivered as equipment → sensor → value → status, so adding machines does not mean rewriting your integration.

  • 01Grouped by machinesite_id and equipment_id tell you which site and which machine the data comes from.
  • 02Every sensor, one formatTemperature, current or vibration, each sensor reports value, unit and status the same way.
  • 03Status from thresholdsEach sensor is judged against its own warning and alarm thresholds; if any sensor is in warning, the machine is too.
// Example payload (for illustration) { "site_id": "PLANT-01", "equipment_id": "PUMP-01", "timestamp": "2026-10-07T09:30:00+09:00", "status": "warning", "sensors": [ { "id": "bearing_temp", "value": 48.2, "unit": "°C", "status": "normal" }, { "id": "motor_current", "value": 31.6, "unit": "A", "status": "normal" }, { "id": "vibration", "value": 4.8, "unit": "mm/s", "status": "warning" } ] }

Actual fields and update intervals are agreed in a technical meeting.

Developer Resources

Review the integration
before we meet

Check the data structure and integration approach ahead of the technical meeting. Detailed specifications are provided in the meeting (NDA if needed).

Sample data is for illustration only; actual fields and values vary by site and project.

Process

How a partnership starts

STEP 1

Inquiry

Share your solution and target project

STEP 2

Technical meeting

Integration scope and roles (NDA if needed)

STEP 3

Demo · test

Verify integration with demo equipment and test data

STEP 4

Joint project

Customer deployment, joint proposal and delivery

FAQ

Frequently asked questions

How are roles split between DONG-IN ENSIS and your company?

We handle the field side (OT): panel design, build and installation, PLC, drive and sensor integration, data transfer to the cloud or customer servers, and standardized data. MES, AI analytics, digital twins and customer-facing services stay with your solution, while we focus on delivering reliable field data. See partnership models →

Which PLCs do you support?

We are not tied to any single brand. For new equipment we build the Intelligent Control Panel around a PLC that supports MQTT and connect it directly, without a separate gateway. For third-party PLCs already on site (e.g., Mitsubishi, LS, Siemens) we only read data, choosing OPC UA, Modbus TCP or the vendor's own protocol through a gateway, in that order. We confirm the model and protocol during the site survey and propose the method for each project.

Can sites with existing control panels be integrated?

Yes. We check the existing panel and PLC during the site survey and propose the best approach: replacing it with an Intelligent Control Panel, a new installation, or integrating with the existing equipment. Motors, pumps and other machines stay as they are.

What data can we receive?

Motor winding temperature (U·V·W), bearing temperature, speed, voltage, current and energy, vibration, ambient temperature and humidity, and run-status signals. Each sensor comes with value, unit and a status (normal, warning, alarm) based on thresholds, so your system can use it without extra processing. Get sample data →

How is the data delivered?

REST API for machine and sensor lists, latest values and history; WebSocket for real-time values and status changes; CSV export for testing and analysis. Endpoints, authentication and update intervals are agreed in the technical meeting. Get the integration overview →

What happens to data when the connection drops?

Equipment control continues on the site PLC. Readings taken while the connection is down are stored in the control panel and resent automatically, oldest first, once the connection is back. Timestamps are recorded on site and every message carries a sequence number, so the server can detect duplicates and gaps.

Is the data format standardized?

Yes. Data follows the DONG-IN ENSIS OT data specification, which defines the MQTT topic structure, message format and standard tag naming, and is versioned. Data arrives in the same structure regardless of equipment brand or site. The detailed specification is provided in a technical meeting after an NDA.

Can setpoints calculated by our AI be applied to equipment control?

For an AI result to change how equipment runs, a PLC program has to receive that value. On Intelligent Control Panels whose PLC program we develop, we are piloting (PoC) control that sends AI-optimized setpoints back to the site PLC and applies them to motor operation. Interlocks and final control stay with the site PLC, and existing third-party PLCs are read-only. Scope and method are agreed in the technical meeting.

Can data traffic affect equipment control?

Control and communication are separated by design: control logic runs as a higher-priority task than data transmission, and the control and data networks are separated. Traffic and control-cycle criteria are agreed per project and confirmed during commissioning.

Do we need to redo the integration when machines are added?

No. Every machine is delivered in the same structure (site, machine, sensor, value and status), so the same integration code keeps working as machines and sensors are added.

What if the customer requires an on-premise system?

DataHub and the dashboard can be installed on the customer's server inside their network, using their existing server or one we supply. It uses the same data structure and API as the cloud option, so your system integrates the same way within the plant network.

How do you handle security reviews?

MQTT traffic between the site and the cloud or customer servers is encrypted with TLS, and interlocks and final control stay with the on-site PLC, so the server never controls machines directly. Accounts, permissions and data retention are defined in the project contract, and the network setup follows the customer's security policy. See security overview →

How are firmware and security certificates managed for installed panels?

As a rule, we keep a register of each installed panel's PLC model, firmware and program versions, and certificate expiry. Firmware and program changes are tested beforehand and made with the customer's approval, and remote access is only through a customer-approved secure connection (VPN). Operating details are agreed in the contract to fit the customer's security policy.

How are marine control panels approved by classification societies?

The Schneider Modicon M262 controller used in our panels holds an EU RO mutual-recognition certificate (hardware) accepted by KR, DNV, ABS, LR and other societies. The control panel and application software are approved for each vessel through the classing society's drawing approval and a surveyor-witnessed factory acceptance test (FAT).

Can we test before signing a contract?

Yes. Start by checking the structure in your system with our sample data, then verify the actual integration with your platform using demo equipment and test data. Scope and schedule are set in the technical meeting.

Who is responsible for on-site work and electrical safety?

We design, build, install, commission and maintain the panels. As an OT engineering company that has built control panels for 35 years, we take responsibility for the field work that panel modification and installation require. A standard project takes 9 to 15 weeks, depending on site conditions.

Can we sell together or join government programs?

Yes. We can find manufacturing customers together and, as a registered smart-factory supplier, join government support programs jointly. Joint proposals using demo equipment are also possible. See the joint sales model →

How are data ownership and contracts handled?

Each project contract defines the roles and responsibilities of the customer, your company and DONG-IN ENSIS, data ownership and use, and retention. An NDA can be signed from the technical meeting stage if needed.

Partnership Inquiry

Propose a partnership

Tell us about your solution and how you would like to work together.

  • ResponseWithin 1–2 business days (KST)
  • Next stepTechnical meeting, partnership deck on request
  • E-maildongin@donginmne.com
Consent to collection and use of personal information
Items: company, name, position, phone, e-mail, message · Purpose: to review and respond to your inquiry · Retention: 1 year after the inquiry is resolved (or as required by law)
You may decline, but we will not be able to receive your inquiry. See our Privacy Policy for details.