Skip to content

Flex IntelligenceIntelligence

Maritime AI that checks whether it adds up.

Flex Intelligence reads what comes in, from emails and shipping instructions to claims and invoices, and understands it in the context of your bookings, voyages and containers. It flags what needs attention, suggests the next step and leaves the decision with your people.

Illustrative intake: Shipping instruction, booking BKG 771204. Booking BKG 771204, Found; Vessel / voyage Nordic Star · KO-2418, Matches booking; Container UMLU 482113-7, On this booking; Gross weight 24,800 kg, Differs from booking. Suggested: ask the shipper to confirm the weight.

What Flex Intelligence is

The AI layer that checks whether it adds up.

Flex Intelligence reads what comes in, from emails and shipping instructions to claims and invoices, and checks it against your bookings, voyages and containers. It summarises, flags what needs attention and suggests the next step, so insight comes sooner: before, during and after the work.

What it takes care of

  • Reading emails and documents
  • Checking them against the record
  • Summaries and alerts via Teams or SMS
  • Suggested next steps
  • Forecasts, such as empty container imbalance

Where it stops

Flex Intelligence does not decide on its own: your people approve. And it is only as good as the record it checks against, which is why it sits on top of the other layers.

Flex Maritime Logistics, layer by layer

  1. Flex IntelligenceYou are hereAI that reads, checks and flags what needs attention. Your people decide.
  2. Flex PerformanceKPIs and reporting in Power BI and Microsoft Fabric: how are we performing?
  3. Flex ConnectAPIs, EDI and events that link Flex Run with customers, carriers, ports, customs and data providers.
  4. Flex RunThe maritime ERP layer: bookings, voyages, cargo, containers and finance in one record.
  5. Microsoft Dynamics 365ERP, CRM, security and the Microsoft cloud
    Finance & Operations · ERPSales · CRM

Each layer builds on the one below. Insight is only as good as the record underneath.

Flex runs only on Microsoft Dynamics 365 Finance and Operations. It is not a standalone system.

Why Flex Intelligence

Generic AI reads a document. Flex Intelligence checks the operation.

Extracting text from a bill of lading is only the first step. The value is in combining it with your maritime context and business rules, so an exception is caught before it becomes a transaction.

  1. Reads a B/L number from a claim form

    Confirms the B/L exists and the container belongs to it

  2. Extracts fields from a shipping instruction

    Compares the instruction with the booking and highlights discrepancies

  3. Lists the parties named in booking documents

    Screens those parties and alerts on potential matches

  4. Captures the lines of a depot invoice

    Matches each line to the expected cost and flags variances

Hands holding a printed shipping document beside a laptop and a tablet, with container cranes outside the office window

Context first

Intelligence needs a record to check against.

Flex Intelligence is only as good as the context it works with. Flex Run holds the maritime record, Flex Connect brings in outside data such as AIS and sanctions lists, and Flex Performance shows where attention is needed.

The maritime record lives inFlex Run

AI agents for shipping

A claims agent at work, from email to approval.

A cargo claim arrives by email with a form and photos. The agent reads it, links it to the right B/L, voyage and container, checks the evidence and prepares the claim. The claims desk approves before anything changes in Dynamics 365.

  • Every step is visible, with the source document kept next to the claim
  • Missing evidence becomes a prepared request, not a surprise later
  • Nothing is created without a person approving it
The full cargo claims management workflow

Built from reusable building blocks

  • Document intake
  • Email intake
  • Entity recognition
  • Operational validation
  • Exception detection
  • Recommendations
  • Workflow actions
  • Notifications & external data
  1. Email and evidence received: Claim form and six photos arrived
  2. Information read and structured: B/L, container, claim amount and damage identified
  3. B/L confirmed: B/L UMLB 240183 found in Dynamics 365
  4. Container validated: Belongs to this B/L and voyage KO-2418
  5. Evidence and exceptions checked: Survey report missing, request prepared
  6. Action prepared in D365: Claim staged for review
  7. Claim created in Dynamics 365, audit trail recorded

Maritime AI in practice

Two more processes, the same rule: people decide.

We develop Flex Intelligence around concrete maritime workflows. These examples show the pattern: read, check in context, suggest, and let the responsible team decide.

Illustrative workflow

Reading and screening booking parties

From booking documents to screening results and alerts.

  1. 01ReadParties are read from the booking documents that arrive by email.
  2. 02ScreenEach party is screened against external sanctions lists, such as OFAC, through Flex Connect.
  3. 03Check againFuzzy matching and multiple checks help separate real matches from false positives.
  4. 04AlertPotential matches are sent for review via Microsoft Teams or SMS.

In the Compliance Center

Parties
Read from documents
Results
Screening and checks
Status
Review and decision

The compliance team decides.

How screening services connect
Booking vetting and sanctions screening, step by step
Illustrative workflow

Forecasting empty container imbalance

How many, when and where, by container type.

  1. 01CombineVessel and voyage data, AIS positions, empty stock, bookings and booking forecasts.
  2. 02ForecastProject stock by location, type and date, and calculate shortages and surpluses against minimum stock.
  3. 03RecommendRanked options for the next move, with the trade-offs shown.
  4. 04ReviewPlanners review quantities, timing and destinations before moves are created.

Ranked option

How many?
Quantity by type
When?
Departure and arrival
Where?
Surplus to shortage

Planners stay in control.

The planning view in Flex Performance
Empty container repositioning, step by step

AI governance

An AI agent never becomes a superuser.

Governance is part of the architecture. For each use case we define what an agent may read, which services it may call, which actions require human approval and how everything is recorded.

  1. 01

    Identify

    Which user, application or agent is acting?

  2. 02

    Authorise

    Which data and services may it use?

  3. 03

    Constrain

    Which rules, guardrails and limits apply?

  4. 04

    Approve

    Which actions require a human?

  5. 05

    Record

    What was requested, decided and executed?

Autonomy follows risk

  1. Observe

    Reads approved documents, events and context. Does not change transactions.

  2. Advise

    Interprets information, flags exceptions and recommends the next step.

  3. Act within boundaries

    Calls permitted services, with human approval where policy or risk requires it.

More intelligence never means less control.

On the Microsoft foundation

  • Microsoft Entra IDIdentity for users, applications and agents
  • Dynamics 365 securityRoles, segregation of duties and data security
  • Microsoft FoundryGuardrails such as Prompt Shields
  • Audit trailLogging, monitoring and review

Two moments where it helps

At intake

Before data enters the processReceive emails and documents, structure them, check them and prepare a clean record in Flex Run.

In analysis

After the work is recordedSummaries, insights, suggested actions and alerts via Microsoft Teams or SMS, based on what Flex Run holds.

Other applications we work on

  • Quote intelligence
  • Shipping instruction intake
  • Exception control
  • Depot and terminal invoices
All ten maritime workflows in Flex in Action
01

What is Flex Intelligence?

Flex Intelligence is the intelligence and automation layer of Flex Maritime Logistics. It combines documents, emails, events, external information, business rules and maritime context to understand situations, flag exceptions, prepare recommendations and trigger controlled actions.

02

Is it just bill of lading OCR or generic AI?

No. Reading and extracting information is only one part. Flex Intelligence combines what it reads with your maritime context. In claims intake, for example, it can check whether a B/L exists, whether the container belongs to it and whether the evidence is consistent before it prepares an action.

03

Do AI agents act on their own?

Autonomy follows risk. An agent can observe, advise or act within defined boundaries. A low-risk notification can be automated; a commercial, compliance or financial action can require validation or explicit approval first. Every request, decision and action is recorded.

04

How is our data protected, and which Microsoft technology does it use?

An agent never gets unrestricted access to your ERP. It receives only the documents and business services it is permitted to use, through governed interfaces, and its actions are logged for review. This builds on the Microsoft foundation: Microsoft Entra ID for the identity of users, applications and agents, Dynamics 365 security for roles and data access, and Microsoft Foundry guardrails such as Prompt Shields. The exact services depend on your architecture and use case.

05

Does Flex Intelligence work without Flex Run?

Flex Intelligence is designed around the maritime context in Flex Run on Dynamics 365, which is what lets it check whether information adds up. The architecture uses APIs and integrations, so connections to other systems are possible. Whether it fits your landscape is something we assess together.

06

Where do we start?

With one process that costs your team time every week, such as claims intake, shipping instructions or booking vetting. We map the documents, context and rules, define what the agent may do and run it with your people approving.

Pick one process. We walk through it with your own documents.

Bring a claim, a shipping instruction or a booking you handle every week. We map what an agent may read and check and where your team approves, then reuse what works for the next process.