Training built by practitioners, for operators.

Who it is for

Terminal operators, shift supervisors, depot managers who work with or alongside a TAS but were never formally trained on how it functions end-to-end.

What it covers

How a TAS authorization works from ERP order to BOL print. Driver and vehicle registration. Bay and product assignment. Preset loading and batch control. BOL printing and ERP posting. Alarm handling and exception management. The operator's role in a safe loading sequence.

Format

1–2 days on-site. Can be delivered at the terminal on your own system.

Outcome

Operators understand the full loading sequence, can handle common exceptions without supervisor escalation, and know what to do when the TAS flags a problem.

Who it is for

Automation engineers, IT leads, and TAS administrators responsible for configuring, maintaining, or integrating FuelFACS systems.

What it covers

FuelFACS system architecture. Product and recipe configuration. Driver, vehicle, and customer master data management. Bay and meter configuration. ERP integration points — order feed, goods movement posting, billing trigger. Alarm configuration and rationalization. Common failure modes and how to diagnose them. API MPMS volume correction configuration.

Format

2–3 days. On-site preferred; remote possible for theory modules.

Outcome

Engineers can configure, maintain, and troubleshoot FuelFACS without vendor dependency for routine tasks.

Who it is for

IT leads, ERP administrators, and integration managers responsible for the connection between the terminal's ERP (SAP, Navision, Dynamics 365, Oracle, JDE) and its TAS.

What it covers

The canonical data flows — master data (products, customers, vehicles), transactional flows (orders, authorizations, BOLs, goods movements), reconciliation feeds. Common integration failure modes. How to diagnose a posting failure. ISA-95 / IEC 62264 as the architectural model. The difference between a real-time and a batch integration, and when each is appropriate.

Format

1–2 days. Can be adapted to the specific ERP in use.

Outcome

Integration teams understand the full data lifecycle between ERP and TAS — and can diagnose and document integration failures without waiting for the TAS vendor.

Who it is for

Terminal operators, metering engineers, and operations managers responsible for custody-transfer metering accuracy and regulatory compliance.

What it covers

Measurement principles — positive displacement, turbine, Coriolis, ultrasonic. API MPMS volume correction (11.1 temperature correction, 12.1.1 tank volume calculation). Meter proving fundamentals — what a prover does, how to interpret a proving report, when to prove. Common metering errors — air entrainment, meter wear, temperature compensation failures. Reading a calibration certificate. What the BOL should contain and why.

Format

1–2 days. Can include a practical session at the metering skid.

Outcome

Operators and engineers understand why the meter reads what it reads, what good looks like, and what a variance between meter and tank gauge means operationally.

Who it is for

Terminal safety officers, instrumentation engineers, operations managers, and anyone responsible for overfill prevention compliance.

What it covers

API 2350 5th edition — scope, tank categories (1/2/3), Levels of Concern (CH/AOPS/LAHH/LAH/MWL), response-time arithmetic (5-minute / 75-mm rule), the independence principle for LAHH instrumentation, AOPS vs MOPS, the 12 site engineering questions from the Sbridge quick reference. Common gaps found on real terminals during walk-downs.

Format

1 day. Includes a practical walk-around component at the tank farm if delivered on-site.

Outcome

Participants can assess their terminal against the 5th edition, identify the most common gaps, and brief a senior engineer on remediation priorities.

Who it is for

Terminal operators, maintenance technicians, and supervisors who work in or near Zone 1/2 and Zone 21/22 classified areas.

What it covers

Why hazardous area classification exists. The zone classification system (Zone 0/1/2 gas/vapor, Zone 20/21/22 dust). What ATEX equipment marking means (Ex IIB T4, IP ratings, protection concepts). What you can and cannot bring into a classified zone. Hot work permits and isolation procedures. Recognising ATEX-rated equipment and checking it is appropriate for the zone.

Format

1 day awareness. Deeper engineering content (zone drawing, equipment selection) delivered in partnership with IPEM for projects that require it.

Outcome

Operational staff know what a zone classification means, can identify compliant equipment by marking, and understand the permit-to-work implications.

ATEX zone drawing, equipment selection engineering, and DSEAR/ATEX Directive compliance assessments are delivered in partnership with IPEM (Industrial Projects Engineering & Management, Sfax) for engagements that require formal engineering sign-off.

Who it is for

Terminal operators and shift supervisors who use SCADA/HMI screens daily but have never been formally trained on what they are reading or how the system works.

What it covers

What SCADA does and what it does not do. How to read a P&ID on an HMI screen. Understanding alarm priorities and what to do with them (ISA-18.2 / EEMUA 191 principles). The difference between a process alarm and a safety alarm. What a SCADA historian is and why it matters for incident investigation. How HMI screens are structured and what to trust when two readings disagree.

Format

1 day. Delivered on-site on your own SCADA system where possible.

Outcome

Operators use SCADA purposefully rather than reactively — and know which screens matter, which alarms are actionable, and what to call when something looks wrong.

Who it is for

Automation engineers, integrators, and IT teams evaluating or beginning to work with Inductive Automation's Ignition SCADA platform.

What it covers

Ignition architecture — Gateway, Designer, Clients. Tag structure and OPC-UA integration. Basic screen building. Database historian configuration. Alarm pipeline configuration. The Perspective module for mobile/web HMI. How Ignition connects to PLCs (Siemens, Allen-Bradley, Schneider Electric).

Format

2–3 days. Practical lab sessions included.

Full Inductive Automation certification training requires an Ignition-certified trainer. Sbridge delivers introductory and integration-focused content; formal Ignition certification courses are referred to Inductive Automation's certified training network.

Who it is for

Terminal managers, operations directors, and senior engineers who need to understand what AI actually does in an industrial context — not the marketing version, the operational version.

What it covers

What AI means in a terminal context (predictive maintenance, anomaly detection, simulation, natural language reporting). What it does not mean (replacing operators, autonomous control). How large language models work and what they are useful for operationally. Prompt engineering for operational use — how to use AI tools to write procedures, summarise reports, and draft communications. AI-assisted data analysis — what is realistic on real terminal data. The OptiLoad™ discrete-event simulation approach as a specific AI application for capacity planning.

Format

1 day. No technical prerequisites — aimed at decision-makers, not developers.

Outcome

Participants can evaluate an AI vendor's claims, identify where AI tools would genuinely help their operation, and brief their board or leadership on AI in realistic terms.

Who it is for

Operations managers, depot directors, and IT leads at terminals that are still primarily manual or paper-based and are beginning a digitalization journey.

What it covers

Why digitalization initiatives fail (and it is rarely the technology). How to map a process before automating it. Change management in an industrial environment — why operators resist new systems and how to design adoption into the project. The maturity ladder from spreadsheets to BulkStock™ to full TAS to Digital Twin — and how to choose the right rung. How to scope a first digital project so it pays back quickly. How to measure the result against a documented baseline.

Format

1–2 days. Can be delivered as a workshop with the client's leadership team.

Outcome

Leadership teams leave with a practical digital transformation roadmap, a clear understanding of sequencing and risk, and a realistic scoping framework for the first project.

Who it is for

Project managers, engineering leads, and client-side project owners managing terminal automation, TAS integration, or digitalization projects.

What it covers

Project phases for an automation project (Assessment, Design, Integrate, Commission, Optimize). How to write a scope that does not grow. FAT and SAT — what they are, how to plan them, what to check. How to manage a vendor delivering a TAS or SCADA system. Change management and scope control. Commissioning and handover documentation. How to write a project brief that a vendor can actually price.

Format

1–2 days.

Outcome

Client-side project owners can run or supervise a terminal automation project without being dependent on the vendor to define the scope, the milestones, or the acceptance criteria.

Who it is for

Engineers and managers working on software integration, dashboard, or digital twin projects who want a structured delivery approach without bureaucratic overhead.

What it covers

Scrum fundamentals applied to industrial software projects. How to write user stories for an operations team. Sprint planning and backlog management for a terminal integration project. How to run a retrospective that actually improves delivery. Agile in a regulated context — when you need the documentation and when you do not.

Format

1 day.

Outcome

Teams deliver software and integration projects in predictable sprints rather than open-ended delivery timelines.