Skip to content
Whether driven by policy shifts, data ownership issues, or strategic independence, you need a solid plan to build a robust and secure remote monitoring setup.
Here are five essential tips to help you get started.
Tip 1: Choose the Right Data Source
The first step is identifying where your data will come from. Options include pulling directly from controllers or PLCs, accessing the local control system, or retrieving data from a local historian already installed on the FPSO. Ideally, you want to get as close to the instrumentation as possible to ensure accurate and timely data. However, doing so might add load to the control system, which could impact operations. This might even not be allowed by the FPSO owner.
If a local historian is used, remember it becomes another point of potential failure. Whatever source you choose, make sure it supports an open or proprietary interface for real-time data,OPC UA is a strong choice here. Just ensure the implementation is complete enough to serve your intended use.
Tip 2: Plan Your Data Collector Carefully
Your data collector should ideally be installed offshore on the FPSO itself. Reliability is key, so think about redundant connectors to your data source. You’ll also need a data buffer capable of storing enough data samples to handle even the longest expected communications outage, factoring in both tag volume and sampling frequency.
Hardware planning is crucial. Offshore installation and cabling require lead time, especially given the logistics involved. Don’t underestimate the time it takes to procure, ship, and install equipment in offshore environments.
Tip 3: Take Network Security Seriously
From the start, take a proactive approach to cybersecurity and engage the IT departments early. Identify all firewall ports that will need to be opened and be prepared to explain and justify them to IT security authorities. This includes not just the ports for data flow but also those needed for remote server maintenance, software upgrades, and security patching.
Using proxy servers can significantly enhance the security of communications between offshore and onshore environments. It’s important to get security right the first time,retrofitting later leads to unwelcome project delays.
Tip 4: Select an Onshore Timeseries Database That Fits
Once the data is collected, it needs to be stored and analysed. Traditional process historians like AVEVA PI or Aspen IP.21 are powerful but come at a high cost. If you’re working on a small or medium-scale integration, open-source timeseries databases such as Prometheus, TDengine, or InfluxDB might offer a more cost-effective solution. And of course, make sure you size storage space appropriately with sufficient spare for growth.
It’s all about matching the scale and complexity of your project with the right level of investment and functionality.
Tip 5: Choose the Right Analytics and Visualisation Tool
Finally, how will you make sense of all this data? End-user analytics and visualisation tools are typically an afterthought, but it shouldn’t be this way.
IT departments generally default to using Grafana or Power BI, because they’re “on hand”, however, they weren’t designed specifically for industrial, real-time process data. If you want to go beyond basic dashboards and get into true operational insights, it’s worth looking into new-generation platforms designed with industrial applications in mind.
One example is Eigen Ingenuity, which offers analytics and visualisation features tailored specifically for process data in industrial environments. This kind of tool can make a real difference in how effectively your team can monitor, troubleshoot, and optimize operations.
Setting up an FPSO remote monitoring system isn’t just a technical challenge, it’s a strategic investment in visibility, safety, and performance. By carefully choosing your data sources, building resilient infrastructure, taking cybersecurity seriously, and selecting tools that truly fit your needs, you can build a monitoring system that works for today and scales for tomorrow.
