Every engineer remembers the moment theoretical knowledge meets the reality of an operational industrial site. For me, that transition happened when I stepped into the world of Industrial IoT.
Around mid-2023, I joined PT. Mosfet Interlock Indonesia. Coming in, I knew that industrial systems were critical and demanding, but seeing how hardware, industrial protocols, and edge software connect in real life was an entirely different experience.
Starting at Mosfet
When I started at Mosfet, my primary focus shifted toward understanding how real physical assets communicate with software systems. I was introduced to tools and protocols that would soon become daily essentials: Node-RED, industrial network topologies, Modbus, and MQTT.
Rather than learning these concepts in an abstract sandbox, I was thrown straight into an active, high-stakes environment: the Smartship Monitoring System project for tanker vessels.
First Time Diving into the Smartship Monitoring Project
Ships are massive and complex industrial environments. At first, I struggled to understand how the onboard network topology actually worked.
How were instruments installed across different compartments interconnected? How did legacy devices tie back to a central panel or junction box? And most importantly for my role at the time: how were we supposed to connect our Smartship edge devices to existing Modbus equipment without disrupting the vessel’s active operations?
Fortunately, I was not navigating this alone. Senior colleagues patiently guided me through the fundamentals of onboard installation and workflow. Even more impactful, my boss actively joined field activities with us. Seeing leadership get hands-on—programming systems on-site and explaining practical working patterns and integration logic firsthand—made a massive difference in how quickly I could absorb the technical context.
Learning the Basics of Industrial Communication
As the project progressed across different vessels, I began to see the wide variety of devices and systems that keep an industrial ship running. The equipment I encountered was not confined to a single subsystem; it was spread across distinct operational areas, each with its own communication requirements and characteristics.
On the bridge, I regularly worked around navigation equipment and Voyage Data Recorder (VDR) systems communicating over NMEA-based protocols. This was my first introduction to how navigational instruments handle data exchange under their own specialized standards.
Moving down to the Cargo Control Room, I often encountered systems such as HANLA and Load Com, which handle cargo, ballast, and AMS data. Each of these setups had its own data flows and hardware interfaces that had to be understood before we could bring them into our monitoring system.
Meanwhile, in the Engine Control Room, my work revolved more closely around PLCs and systems from Kongsberg. This environment introduced me to core marine automation and machinery control, which operated quite differently from either navigation or cargo systems.
With each installation, I grew to appreciate that different systems rely on different communication methods. Across these areas, the interfaces and protocols I worked with included Modbus RTU over RS485, RS232, Modbus TCP, and NMEA.
Understanding which equipment was in use, where each system was situated, and how each device communicated became a crucial part of my journey in mastering shipboard data integration.
A Small IP Address Concern with a Siemens S7-1500
One particular experience from those early days remains vivid. We needed to integrate our Smartship system with an onboard Siemens S7-1500 PLC using Node-RED running on our edge device.
When connecting Node-RED to the PLC for the first time, I felt genuinely nervous because the integration was being done on a vessel that was actively in service. My biggest anxiety at that moment was network configuration: I was worried that our Smartship gateway device and the ship’s PLC might have conflicting IP addresses, or that incorrect subnet settings might cause communication issues.
With guidance from my senior, we carefully identified the PLC’s existing IP address and verified the subnet settings. I opened the Node-RED flow, opened the S7 Read node configuration, and entered the IP parameters into the configuration panel.
When I deployed the flow and saw the connection status turn green, the data streamed into Node-RED without major issues. It was a huge relief. Looking back, it was a straightforward configuration step, but when you are a junior engineer dealing with live industrial assets, that first successful communication handshake is a genuine milestone.
From Reading Data to Understanding the Pattern
At that early stage of my career, my grasp of data handling was still developing. In Node-RED, my main responsibility was establishing the connection to the field device, ensuring reliable polling, and forwarding the raw telemetry payload via MQTT.
I did not yet have a deep understanding of data parsing or how complex data structures should be normalized. Once the payload was dispatched over MQTT, our IT team handled the downstream parsing and database ingestion. Knowing where my responsibility ended and where the next team took over helped keep our edge flows lean, while giving me clear visibility into the end-to-end data pipeline.
Learning Through Multiple Vessels
As we completed installations across several vessels, the initial confusion began to clear up. What once felt like an unpredictable maze of shipboard cables and unknown equipment gradually revealed recurring patterns:
- Communication protocols might vary between serial and Ethernet, but the fundamental logic of addressing, polling cycles, and signal conditioning remains consistent.
- Physical wiring errors, loose terminals, or incorrect baud rates account for a significant portion of communication drops.
With each vessel, I gained confidence. I reached a point where I could troubleshoot communication hiccups independently without needing a senior standing right over my shoulder. Even so, I made it an absolute rule to maintain strict communication discipline: whenever an issue occurred on-site, I always reported the findings and discussed the proposed action with the relevant senior or team before making changes. In industrial engineering, independent thinking must always go hand-in-hand with teamwork and accountability.
What I Learned
Reflecting on my early period at Mosfet, this experience laid the foundation for my approach to Industrial IoT:
- Fundamentals matter more than buzzwords: High-level IoT dashboards are only as reliable as the physical RS485 loop, network configuration, and protocol handshake underneath them.
- Field experience accelerates learning: You can read manuals for months, but diagnosing a real PLC or transmitter on a ship teaches you lessons you never forget.
- Respect the domain and safety boundaries: Industrial environments are not software playgrounds. Being cautious about IP conflicts or wiring is not a weakness; it is a necessary engineering mindset.
- Growth is built on repetition and collaboration: Nobody starts as an expert. Growth comes from observing senior engineers, asking questions, paying attention to recurring patterns across sites, and doing the work thoroughly every single day.
This was my introduction to Industrial IoT—grounded in real vessels, real hardware, and the patient mentorship that helped me find my footing.