Oil and Gas
Monitor tank farms, loading bays and stations in a web browser. YTCC collects data over Modbus TCP, OPC UA, DNP3 and IEC 60870-5-104, shows tank levels, pumps and valves with ready-made symbols and logs every command.
Monitor the tank farm and loading operations
At a fuel terminal or tank farm, operators watch tank levels, temperatures, pump and valve states, loading bay operations and the gas detection system together. A high level or a pump fault has to be noticed in time, and a lost link to a remote station has to show.
YTCC talks to PLCs and remote units as master over Modbus TCP, DNP3 and IEC 60870-5-104 and as OPC UA client and server, and its MQTT client takes data from gateways. The DNP3 driver runs over TCP, UDP and serial lines and can use TLS and Secure Authentication v5. When communication with a device is lost, one alarm is raised per device and its signals go to "no connection" quality.
You draw tank farm screens in the screen editor with ready-made tank, pump, valve and tanker truck objects; tank fill levels are bound to signals and the high and low level lines change color when crossed. Expressions in internal tags compute derived values, for example the volume of a vertical cylindrical tank from its level with one multiplication. Alarm definitions use multi-level thresholds, hysteresis and delays, and you gather alarms by tank, area or system in nested groups; chattering alarms and alarm floods are detected.
A command is refused while communication is down, and the result can be read back for verification. The sending user, signal, value, result and times go into the audit log, and refused commands are logged too. User roles decide who may write to which signal, and the server enforces the permission.
A sample YTCC screen for Oil and Gas
A sample screen made for a fictional fuel terminal tank farm: tanks in their bunds, pumps and loading bays, the tank inventory, a loading chart and the alarm list on one page.
Frequently asked questions
Which protocols does YTCC use with devices in oil and gas facilities?
As master: Modbus TCP, DNP3 and IEC 60870-5-104. As client: OPC UA and MQTT, and as an OPC UA server too. Other field protocols are listed on the Platform page.
Can DNP3 communication be secured?
The DNP3 driver can use TLS and Secure Authentication v5. It runs over TCP, UDP and serial lines.
Can I see who sent which command?
Yes. For every command the sending user, signal, value, result and times go into the audit log, and refused commands are logged too. You can download the command history as Excel or CSV.
YTCC. Your trusted control center for energy and industrial SCADA.
Download YTCC and build your first screen.