Phone: 022-6625852   Email: info@java-electrindo.com
Indonesia-wide service coverage
SCADA · IoT · IIoT

Pahami mesin.
Hubungkan datanya.
Understand machines.
Connect their data.

Dari sensor dan PLC ke dashboard lokal, lalu ke cloud bila dibutuhkan. Bangun pemantauan yang jelas sumbernya, berguna untuk tim, dan sesuai kondisi pabrik.From sensors and PLCs to a local dashboard, then to the cloud when needed. Build monitoring with clear data sources, practical team benefits and a design that fits the plant.

Lokal dahuluLocal firstData berkualitasData qualityAkses terkontrolControlled access

Integrasi monitoring industri oleh Java Electrindo. Perangkat dan lingkup akhir ditentukan melalui survei.Industrial monitoring integration by Java Electrindo. Final equipment and scope are established through a survey.

Industrial IoT illustration: textile machine, instruments, PLC, edge computer, local server and optional cloud.
Ilustrasi generatif AI · diagram teknis terperinci ada di bawah.AI-generated illustration · the detailed technical diagram is below.
01

IoT, IIoT, dan SCADA: saling melengkapiIoT, IIoT and SCADA: complementary roles

Mulai dari keputusan yang perlu dibuat, lalu tentukan data dan sistemnya.Start with the decision that needs to be made, then choose the data and system.

IoT · perangkat terhubungIoT · connected devices

Sensor, meter, atau perangkat mengirimkan data melalui jaringan. Contoh: suhu ruangan dan pemakaian air. IoT tidak selalu memerlukan cloud.Sensors, meters or devices exchange data over a network. Examples include room temperature and water usage. IoT does not always require a cloud.

IIoT · konteks industriIIoT · industrial context

Penerapan IoT untuk mesin dan operasi industri. Nilai harus punya satuan, waktu, kualitas, konteks batch, dan rancangan keandalan yang sesuai proses.IoT applied to industrial machines and operations. Values need units, time, quality, batch context and reliability designed for the process.

SCADA · supervisi prosesSCADA · process supervision

Menampilkan proses, alarm, dan histori; fungsi supervisi dapat mencakup kendali yang dirancang khusus. PLC dan sistem keselamatan tetap memegang fungsi lokalnya.Presents process views, alarms and history; supervision can include specifically engineered control. PLCs and safety systems retain their local functions.

Contoh sederhana: meter membaca energi → gateway memvalidasi → histori menyimpan → dashboard membantu tim melihat pemakaian per shift.A simple example: a meter reads energy → a gateway validates → history is stored → a dashboard helps the team review usage per shift.
02

Pilih tempat data bekerjaChoose where the data works

Bandingkan tiga rancangan. Pilihan ini mengubah penjelasan diagram, bukan menghubungkan ke mesin.Compare three designs. These controls change the explanation, without connecting to equipment.

LANTAI PRODUKSI / OTPRODUCTION FLOOR / OT

01 · PLC / Sensor

Sumber terverifikasi. Pembacaan melalui antarmuka yang disetujui.Verified sources. Acquisition uses approved interfaces.

02 · Edge / Gateway

Validasi, waktu, satuan, dan antrean penyimpanan lokal.Validation, timestamps, units and a persistent local queue.

03 · Server LAN

Dashboard dan histori lokal, sesuai rancangan.Local dashboard and history, according to the design.

04 · Cloud

Opsional: ringkasan lintas lokasi dan akses jarak jauh.Optional: multi-site summaries and remote visibility.

Modbus / OPC UAMQTT / HTTPS · TLSJalur keluar melalui firewall / DMZ bila diperlukanOutbound path through a firewall / DMZ where required
Kontrol lokal: sensor ↔ PLC / interlock ↔ aktuator. Jalur keselamatan mengikuti rancangan mesin.Local control: sensors ↔ PLC / interlocks ↔ actuators. Safety functions follow the machine design.

Hybrid: operasional lokal, visibilitas lintas lokasiHybrid: local operation, multi-site visibility

Dashboard dan histori yang disediakan di LAN tetap dapat digunakan saat internet putus, selama listrik, jaringan, dan layanan lokal sehat. Data terpilih dikirim ke cloud melalui jalur yang disetujui.The LAN dashboard and history remain available through an internet outage while local power, networking and services remain healthy. Selected data goes to the cloud over an approved path.

Monitoring dan kendali jarak jauh adalah lingkup berbeda. Diagram ini adalah contoh pemantauan. Perintah ke mesin memerlukan otorisasi, interlock, analisis risiko, pengujian, dan audit tersendiri.Monitoring and remote control are separate scopes. This diagram illustrates monitoring. Machine commands require their own authorization, interlocks, risk analysis, testing and audit trail.
03

Apa yang terjadi ketika internet putus?What happens when the internet drops?

Sinkronisasi yang baik punya antrean, tanda terima, dan identitas data—bukan sekadar mengirim ulang.Good synchronization has a queue, acknowledgements and record identities—not just retries.

SIMULASI EDUKASI · BUKAN DATA LIVEEDUCATIONAL SIMULATION · NOT LIVE DATA
Catatan dibuat di lokalRecords created locally120
Sudah diterima cloudAcknowledged by cloud120
Menunggu di antreanWaiting in the queue0
Kondisi lokalLocal conditionAktifActive
120 catatan contoh telah diterima cloud. Antrean lokal kosong.All 120 example records have been acknowledged by the cloud. The local queue is empty.
  1. Simpan sebelum mengirimPersist before sending

    Gateway mencatat event ID, sequence, waktu sumber, dan payload ke antrean disk dengan kapasitas terukur.The gateway saves an event ID, sequence, source timestamp and payload to a sized disk queue.

  2. Ulangi secara terkendaliRetry with limits

    Saat sambungan pulih, kirim bertahap dengan backoff dan pantau kapasitas. Hapus antrean hanya setelah tanda terima sesuai kontrak aplikasi.After recovery, replay in batches with backoff and watch capacity. Remove queued records only after the application contract confirms receipt.

  3. Cegah duplikasi & data menyesatkanPrevent duplicates and misleading data

    Gunakan event ID untuk deduplikasi; pisahkan waktu sumber dari waktu terima. MQTT QoS 1 bisa mengirim duplikat; retained message bukan histori.Deduplicate by event ID and keep source time separate from receive time. MQTT QoS 1 can deliver duplicates; a retained message is not a history store.

Contoh menghitung kapasitas antreanExample queue sizing

Misal 10 perangkat × 1 catatan tiap 10 detik × 6 jam putus = 21.600 catatan. Jika satu catatan tersimpan rata-rata 500 byte, payload sekitar 10,8 MB desimal, belum termasuk indeks, transaksi, dan cadangan kapasitas. Uji ukuran aktual dan tentukan kebijakan saat penuh.For example: 10 devices × one record every 10 seconds × a 6-hour outage = 21,600 records. At an average stored size of 500 bytes, payload is about 10.8 MB decimal, excluding indexes, transactions and capacity headroom. Measure actual sizes and define what happens when storage fills.

TexSyncJAVA ELECTRINDO · TEXTILE SYSTEMS

Ruang kerja digital untuk operasi tekstilA digital workspace for textile operations

TexSync adalah produk Java Electrindo untuk sektor tekstil. Hubungkan pembahasan IIoT dengan kebutuhan sehari-hari operator, tim produksi, dan teknisi: mengikuti proses, membaca histori, serta meninjau kondisi mesin.TexSync is a Java Electrindo product for the textile sector. Connect IIoT concepts to the daily needs of operators, production teams and technicians: following a process, reviewing history and understanding machine conditions.

Situs TexSync menampilkan contoh ilustratif. Akses dashboard dan integrasi mesin mengikuti akun, modul, serta lingkup implementasi.The TexSync website includes illustrative examples. Dashboard access and machine integration depend on the account, module and implementation scope.

Dye ControllerDye Controller

Untuk menelusuri profil suhu batch pencelupan: pemanasan, penahanan, dan pendinginan. Kebutuhan data mencakup identitas batch, waktu, suhu, dan status mesin.For reviewing a dyeing batch temperature profile: heating, holding and cooling. Required data includes batch identity, time, temperature and machine state.

Stanter · finishingStanter · finishing

Untuk pemantauan suhu per chamber dan tren lini penyempurnaan kain. Jumlah kanal dan koneksi PT100 / I/O diverifikasi pada perangkat dan proyek yang digunakan.For per-chamber temperature monitoring and finishing-line trends. Channel counts and PT100 / I/O connectivity are verified for the actual device and project.

PLC / SensorGateway & validasiGateway & validationTexSyncOperator · Produksi · TeknisiOperators · Production · Technicians

Alur di atas adalah contoh integrasi yang direncanakan per proyek, bukan janji bahwa setiap mesin langsung kompatibel. Knitting, Weaving, dan Quality Control ditampilkan sebagai modul yang direncanakan pada situs TexSync, bukan fitur yang otomatis tersedia.The flow above is an integration example designed per project, not a promise of instant compatibility with every machine. The TexSync site lists Knitting, Weaving and Quality Control as planned modules, not automatically available features.

04

Mulai dari satu masalah yang bisa diukurStart with one measurable problem

Contoh berikut bersifat ilustratif. Tidak ada klaim penghematan, output, atau data pelanggan nyata.The examples below are illustrative. They do not claim real customer savings, output or readings.

Tekstil · kualitas prosesTextiles · process consistency

Pertanyaan: kapan suhu menyimpang dari profil batch? Gunakan suhu, setpoint, batch ID, dan waktu. Tampilkan tren, status kualitas data, dan riwayat alarm; cocokkan dengan referensi mesin.Question: when did temperature depart from the batch profile? Use temperature, setpoint, batch ID and time. Show trends, data quality and alarm history; compare against machine references.

Energi · pemakaian per shiftEnergy · usage per shift

Pertanyaan: bagian mana yang menggunakan energi saat idle? Baca kWh kumulatif dan status produksi; periksa reset / rollover meter. Hitung selisih kWh per shift, bukan menjumlah angka kumulatif.Question: which area consumes energy while idle? Read cumulative kWh and production state; account for meter resets / rollover. Calculate per-shift kWh differences instead of summing cumulative readings.

Retrofit · downtime berulangRetrofit · recurring downtime

Pertanyaan: gangguan apa yang paling lama menghentikan mesin? Gunakan run / stop, fault, dan reason code yang disepakati. Bedakan stop terencana, idle, gangguan, dan komunikasi terputus.Question: which disturbances stop a machine for longest? Use agreed run / stop signals, faults and reason codes. Distinguish planned stops, idle, faults and communication loss.

Contoh OEE: angka harus punya definisiAn OEE example: numbers need definitions

Availability = waktu berjalan / waktu produksi terencana. Performance = waktu siklus ideal × total unit / waktu berjalan. Quality = unit baik / total unit. Contoh 90% × 88% × 98% = 77,6% OEE setelah pembulatan. Tetapkan satuan, stop terencana, batas shift, reject, dan referensi kecepatan. Jika penyebut nol atau data tidak valid, tampilkan N/A; jangan memaksakan 0% atau 100%.Availability = run time / planned production time. Performance = ideal cycle time × total units / run time. Quality = good units / total units. Example: 90% × 88% × 98% = 77.6% OEE, rounded. Define units, planned stops, shift boundaries, rejects and the ideal speed reference. With a zero denominator or invalid data, show N/A instead of forcing 0% or 100%.

05

Satu angka membutuhkan konteksA number needs context

Jangan berhenti pada nilai 82.4. Ketahui dari mana, kapan, satuannya apa, dan apakah masih layak digunakan.Do not stop at the value 82.4. Know where it came from, when, its unit and whether it is still usable.

CONTOH SKEMA PESAN · DATA SINTETISEXAMPLE MESSAGE SCHEMA · SYNTHETIC DATA
{
  "schema_version": 1,
  "event_id": "edge01-bootA-001208",
  "device_id": "dye-01",
  "tag": "temperature",
  "value": 82.4,
  "unit": "degC",
  "source_ts": "2026-11-12T03:00:00Z",
  "quality": "good",
  "sequence": 1208,
  "batch_id": "DEMO-001"
}

MQTT topic: plant/demo/dye-01/telemetry

Identitas & waktuIdentity & time

Event ID harus unik, termasuk setelah restart. Waktu UTC + zona tampilan memudahkan penyelarasan; tandai jam sumber yang tidak andal.Event IDs must remain unique after restarts. UTC timestamps plus a display time zone aid alignment; flag unreliable source clocks.

Kualitas terlihat jelasVisible quality

LIVE: masih segar. STALE: melewati batas umur. INVALID: gagal validasi. OFFLINE: jalur sumber tidak tersedia. Simpan nilai terakhir beserta statusnya.LIVE: fresh. STALE: past its age threshold. INVALID: failed validation. OFFLINE: source path unavailable. Keep the last value together with its status.

Alarm punya siklus hidupAlarms have a lifecycle

Pisahkan aktif, diakui operator, dan kembali normal. ACK tidak berarti gangguan selesai. Gunakan delay / deadband sesuai proses dan uji notifikasi.Separate active, operator-acknowledged and returned-to-normal states. ACK does not mean a fault is resolved. Use process-appropriate delays / deadbands and test notifications.

Pilih protokol berdasarkan sumber dan kebutuhanChoose a protocol to match the source and need
ProtokolProtocolPeranRoleYang harus diverifikasiWhat to verify
Modbus RTU / TCPPembacaan register meter, PLC, atau VFD.Register acquisition from meters, PLCs or VFDs.Alamat dan unit ID, tipe data, endianness, scaling, izin baca, serta beban polling. Modbus klasik tidak menyediakan autentikasi / enkripsi bawaan.Addresses and unit IDs, data type, endianness, scaling, read access and polling load. Classic Modbus has no built-in authentication / encryption.
OPC UAPertukaran data terstruktur dari server yang mendukungnya.Structured exchange from a supporting server.Endpoint, sertifikat / trust list, security policy, role pengguna, kualitas, serta timestamp. Tidak otomatis tersedia di semua PLC.Endpoint, certificates / trust lists, security policy, user roles, quality and timestamps. It is not automatically available on every PLC.
MQTTTelemetri publish / subscribe melalui broker.Publish / subscribe telemetry through a broker.TLS, identitas perangkat, ACL per topic, QoS, last will, retensi, dan penyimpanan antrean. QoS bukan backup histori.TLS, device identity, per-topic ACLs, QoS, last will, retention and queue persistence. QoS is not a history backup.
HTTPS APIIntegrasi aplikasi, ringkasan, dan sinkronisasi antar sistem.Application integration, summaries and inter-system sync.TLS, otorisasi, validasi skema, batas laju, retry, timeout, dan idempotency pada penerimaan.TLS, authorization, schema validation, rate limits, retries, timeouts and idempotent ingestion.
06

Tools mengikuti pekerjaan, bukan sebaliknyaChoose tools for the job

Ini contoh komponen arsitektur, bukan daftar alat yang wajib dipasang atau klaim stack yang digunakan TexSync.These are architecture options, not a mandatory installation list or a claim about the TexSync stack.

Integrasi & pemetaanIntegration & mapping

Node-RED

Mengolah alur dan mapping data; editor dan API admin harus diamankan terpisah dari tampilan operator.Transforms flows and maps data; secure its editor and admin API separately from the operator view.

Dokumentasi resmi ↗Official documentation ↗
Broker MQTTMQTT broker

Eclipse Mosquitto

Mendistribusikan pesan; atur autentikasi, ACL topic, TLS, serta persistence sesuai kebutuhan.Routes messages; configure authentication, topic ACLs, TLS and persistence for the requirements.

Dokumentasi resmi ↗Official documentation ↗
Penyimpanan & retensiStorage & retention

Database / historian

Simpan timestamp, kualitas, dan identitas event. Tentukan kapasitas, retensi, backup, dan uji pemulihan.Stores time, quality and event identity. Define capacity, retention, backups and recovery tests.

Visualisasi & konteksVisualization & context

Grafana / HMI / aplikasi

Grafana membaca data source; database menyimpan histori. Pilih layar, alarm, dan akses berdasarkan peran tim.Grafana queries data sources; the database stores history. Choose displays, alarms and access for each team role.

Dokumentasi resmi ↗Official documentation ↗
07

Dari survei ke sistem yang bisa dirawatFrom survey to a maintainable system

Mulai dari satu mesin / area, buktikan kualitas data, lalu perluas secara terukur.Start with one machine / area, prove the data quality, then scale deliberately.

  1. 01

    Survei & tujuanSurvey & purpose

    Catat model PLC / meter, dokumen antarmuka, jaringan, penanggung jawab, dan keputusan yang ingin dibantu.Record PLC / meter models, interface documentation, networking, owners and the decisions to support.

  2. 02

    Peta tag & izinTag map & permissions

    Tentukan register / node / topic, satuan, scaling, interval, status kualitas, alarm, serta izin baca / tulis.Define registers / nodes / topics, units, scaling, intervals, quality states, alarms and read / write permissions.

  3. 03

    Pilot baca-sajaRead-only pilot

    Bandingkan pembacaan dengan HMI atau instrumen referensi. Ukur beban komunikasi tanpa mengganggu kontrol.Compare readings with the HMI or a reference instrument. Measure communication load without disrupting control.

  4. 04

    Uji kegagalanFailure testing

    Uji internet putus, sumber offline, data invalid, reboot gateway, antrean penuh, dan replay tanpa duplikasi.Test internet loss, offline sources, invalid data, gateway restart, queue saturation and duplicate-free replay.

  5. 05

    Uji penerimaanAcceptance testing

    Sepakati batas keterlambatan, toleransi pengukuran, alarm, akses, laporan, kapasitas, serta kriteria lulus / gagal.Agree on latency limits, measurement tolerances, alarms, access, reports, capacity and pass / fail criteria.

  6. 06

    Serah terima & rawatHandover & maintain

    Simpan konfigurasi, inventaris, backup teruji, prosedur restore, pemilik akses, dan jadwal tinjauan.Retain configuration, inventory, tested backups, a restore procedure, access owners and a review schedule.

Siapkan untuk konsultasi: model controller, register map / protokol yang tersedia, daftar nilai penting, jumlah mesin, kebutuhan histori, pengguna lokal / jarak jauh, dan batas akses jaringan. Jangan kirim password atau kunci rahasia.For a consultation, prepare: controller model, available register map / protocols, important values, machine count, history requirements, local / remote users and network access limits. Do not send passwords or secret keys.
08

Rancang keamanan sejak jalur data pertamaDesign security from the first data path

Ketersediaan proses dan keselamatan menjadi bagian dari keputusan teknis.Process availability and safety are part of the technical decisions.

Pisahkan OT dan akses luarSeparate OT from external access

Batasi jalur antar zona dengan aturan firewall. Gunakan gateway / DMZ sesuai analisis risiko. Jangan membuka port PLC atau broker tanpa proteksi ke internet.Restrict inter-zone paths with firewall rules. Use a gateway / DMZ according to risk analysis. Do not expose PLC ports or an unprotected broker to the internet.

Identitas dan hak minimumIdentity and least privilege

Berikan akun perangkat terpisah, izin topic / API terbatas, serta TLS dengan validasi sertifikat. Akses remote manusia melalui jalur terkontrol dan MFA bila didukung.Use separate device accounts, limited topic / API permissions and TLS with certificate validation. Human remote access uses controlled paths and MFA where supported.

Backup yang bisa dipulihkanBackups that can be restored

Lindungi konfigurasi, historian, dan kunci. Verifikasi restore di area uji; sesuaikan pembaruan dengan kompatibilitas dan jadwal produksi.Protect configuration, historian data and keys. Verify recovery in a test area; align updates with compatibility and production windows.

Pantau kualitas sistemMonitor system quality

Pantau umur data, antrean, disk, sinkronisasi waktu, sertifikat, dan log akses. Kirim alarm yang perlu tindakan, dengan pemilik tindak lanjut yang jelas.Monitor data age, queues, storage, clock sync, certificates and access logs. Send actionable alerts with a clear response owner.

Referensi teknis dan batas penjelasanTechnical references and scope

Materi ini merangkum pendekatan implementasi; bukan klaim sertifikasi atau pengganti analisis keselamatan mesin. Diagram dan contoh data disederhanakan. Persyaratan perangkat, keamanan, dan jaringan diverifikasi pada proyek.This material summarizes implementation approaches; it is not a certification claim or a replacement for machine safety analysis. Diagrams and example data are simplified. Device, security and network requirements are verified per project.

Ditinjau 12 November 2026. Rujukan NIST yang dipakai adalah Rev. 3 final; Rev. 4 masih berupa draf publik pada tanggal tinjauan.Reviewed 12 November 2026. The NIST reference used is final Rev. 3; Rev. 4 remains a public draft on the review date.

FAQ

Pertanyaan sebelum mulaiQuestions before you start

Apakah semua mesin lama bisa langsung dihubungkan?Can every legacy machine connect straight away?

Belum tentu. Periksa port, protokol, register map, kondisi kelistrikan, dan izin produsen. Retrofit sensor atau gateway bisa dipertimbangkan setelah survei; jangan menebak alamat register.Not necessarily. Check ports, protocols, register maps, electrical condition and manufacturer permissions. Additional sensors or a gateway may be considered after a survey; do not guess register addresses.

Apakah cloud sama dengan halaman website ini?Is the cloud the same as this website page?

Halaman ini menjelaskan layanan. Sistem cloud industri membutuhkan backend, identitas perangkat, penyimpanan, akses, dan pemantauan yang dirancang khusus. Hosting website atau halaman dashboard saja tidak otomatis menyediakan semua fungsi itu.This page explains the service. An industrial cloud system needs a designed backend, device identity, storage, access controls and monitoring. Website hosting or a dashboard page alone does not automatically provide those functions.

Apa hubungan TexSync dengan Java Electrindo?How does TexSync relate to Java Electrindo?

TexSync adalah produk tekstil Java Electrindo. Situsnya memperkenalkan ruang kerja Dye Controller dan Stanter. Kesesuaian mesin, paket, akun, dan integrasi perlu dikonfirmasi untuk proyek yang dimaksud.TexSync is a Java Electrindo textile product. Its website introduces Dye Controller and Stanter workspaces. Machine suitability, package, account and integration need confirmation for the intended project.

Apakah internet putus berarti kontrol mesin berhenti?Does internet loss stop machine control?

Tidak seharusnya pada rancangan kontrol lokal yang sesuai. Namun fungsi yang memang membutuhkan cloud dapat terhenti. Uji ketergantungan nyata, kondisi fail-safe, dan pemulihan pada tahap commissioning.It should not in an appropriately designed local control system. Functions that intentionally depend on the cloud may stop. Test actual dependencies, fail-safe behavior and recovery during commissioning.

JAVA ELECTRINDO

Mulai dari data yang benar-benar dibutuhkan.Start with the data that matters.

Diskusikan mesin, proses tekstil, atau utilitas yang ingin dipantau. Tentukan batas lokal dan cloud sebelum memilih alat.Discuss the machines, textile processes or utilities you want to monitor. Define local and cloud boundaries before choosing tools.