/
Frequency of Unplanned Assignment Interruption (FUAI)

TIC 4.0

Frequency of Unplanned Assignment Interruption (FUAI)

KPI

Fields

Type

Description

Purpose

Fields

Type

Description

Purpose

ID (KPI identifier)

M

FUAI

GRAMMAR

KPI name

M

Frequency of Unplanned Assignment Interruption

GRAMMAR

KPI type

M

OperationalPerformance

GRAMMAR

KPI base unit of measurement

O

Number of qualifying interruption events over a terminal-defined reporting window (e.g., vessel visit, week, month).

GRAMMAR

Applicable to

 

CHE, STS, RTG

 

Also known as

O

 

TIC Description

Definition

M

Frequency of Unplanned Assignment Interruption (FUAI) measures the frequency (count) of which unplanned equipment faults occur, over the reporting windown, that interrupt an active assignment and require corrective maintenance action.

Here, assignment refers to the active job instruction.

TIC Description

Further Detail

O

FUAI is different than just asset downtime, which is tracked under CHE Downtime. FUAI is focused on assignment interruption frequency, not how long the asset remains unavailable.

FUAI is complementary to duration-based metrics such as Unplanned Assignment Interruption Duration (UAID).

An FUAI event is recorded when:

  • an unplanned equipment fault is logged by Operations, telematics, or maintenance systems, and

  • the fault interrupts an active assignment due to the absence of an immediately available, functionally equivalent replacement unit.

Each qualifying occurrence is counted as one event, regardless of the duration of the interruption.

1. Key characteristics

  • Each qualifying unplanned fault is counted as one event, even if the resulting interruption is brief.

  • No filtering is applied between engineering-related or operations-related faults.

  • Repetitive faults shall be recorded individually and shall not be grouped.

  • Planned maintenance, inspections, and planned equipment swaps are excluded.

  • Faults that are absorbed without interrupting the assignment (e.g., immediate substitution) are not counted.

  • Subsystem faults are included in the FUAI count of the parent equipment and shall not be tracked separately.

2. Fault classification (recommended)

To support consistent analysis while avoiding subjective filtering, FUAI events may be classified into:

  • FUAI(Eng): technical faults causing functional failure of the equipment

  • FUAI(Ops): operational or external faults (e.g., emergency stop activation)

This classification supports reliability and improvement discussions without changing the core FUAI count.

3. Standard outputs

While FUAI is a single KPI, it can be reported using the following standard outputs (similar to how GMPH can be reported for a vessel visit or across a period of time):

  • FUAI.period (aggregate):
    Total number of qualifying FUAI events over the reporting window (e.g., vessel visit, shift, week, month).

  • FUAI.by-type (optional):
    FUAI reported as FUAI(Eng) and FUAI(Ops) for engineering and operational analysis.

  1. Intended use

FUAI is intended to support:

  • reliability analysis

  • maintenance strategy evaluation

  • identification of recurrent faults and bad actors

  • comparison of interruption frequency across assets or subsystems

FUAI should not be used alone to assess operational impact. Metrics such as UAID are required to understand the consequences of failures on assignments and throughput.

  1. Data points

  • FUAI(Eng): technical faults causing functional failure of the equipment

    • che|@|fault|type = component

  • FUAI(Ops): operational or external faults (e.g., emergency stop activation)

    • che|@|fault|type = operational

  • Event ID:

    • che|@|fault|event|tic40codeid

  • Assignment ID:

    • tos|jobinstruction|orderassigment|id

  • Asset (failed):

    • che|@|id|metaelements|value

  • Failure timestamp:

    • che|@|fault|event|timestamp

  • Cause code:

    • che|@|fault|event|tic40codename

  • Vessel / Berth:

    • tos|@|carrier|id|metaelements|value

    • tos|@|terminal|@|berth|@|id|value

  • Events (count):

    • che|@|fault|counter

  • Equipment running hours: 1,200

    • che|@|on|totalcounter

TIC Description

Required Information

M

  1. Event ID – unique.

  2. Assignment / Job ID – the interrupted job instruction.

  3. Failing Asset ID – CHE that triggered the stop.

  4. Failure notification time: timestamp + source (Ops console or telematics).

  5. Spare-available at failure (Y/N): if Y and no gap, FUAI = 0 (do not count).

TIC Description

SUBJECT

 

CHE

 

CONCEPT

 

 

 

Value

 

totalcounter, totaltimer

 

Related standards

O

 

TIC Description

Related TIC 4.0 definition

O

Unplanned Assignment Interruption Duration (UAID)

TIC Description

Example

 

Example of How to Report FUAI

Event Report

  • Event ID: EV-2025-011

  • Assignment ID: A-2145

  • Asset (failed): RTG-07

  • Failure timestamp: 10:12

  • Spare available: N

  • Cause code: HYD-FLT

  • Vessel / Berth: HN123 / B2

  • Shift / Date: Night / 2025-11-04

Period Summary

  • Period: 2025-11-01 to 2025-11-07

  • Scope: Terminal (all vessels)

  • Events (count): 12

  • Equipment running hours: 1,200

  • FUAI (events per running hour): 0.010

Example in the context of the grammar:

  • Event ID: EV-2025-011

    • che|@|fault|event|tic40codeid = EV-2025-011

  • Assignment ID: A-2145

    • tos|jobinstruction|orderassigment|id = A-2145

  • Asset (failed):

    • che|@|id|metaelements|value = RTG-07

  • Failure timestamp:

    • che|@|fault|event|timestamp = 10:12

  • Cause code: HYD-FLT

    • che|@|fault|event|tic40codename = HYD-FLT

  • Vessel / Berth:

    • tos|@|carrier|id|metaelements|value = HN123

    • tos|@|terminal|@|quay|@|berth|@|id|value = B2

  • Period: 2025-11-01 to 2025-11-07

  • Scope: Terminal (all vessels)

  • Events (count): 12

    • che|@|fault|counter = 12

  • Equipment running hours: 1,200

    • che|@|on|totalcounter = 1200

Operator:

(che|@|fault|counter = 12) / (che|@|on|totalcounter = 1200) = 0.010

  • FUAI (events per running hour): 0.010

 

TIC Description

Example in the context of the grammar

M

  • Event ID: EV-2025-011

imagen-20260220-134832.png

  • Assignment ID: A-2145

imagen-20260220-135000.png

  • Asset (failed):

imagen-20260220-135033.png

  • Failure timestamp:

imagen-20260220-135145.png

  • Cause code: HYD-FLT

imagen-20260220-143219.png

 

  • tos|@|carrier|id|metaelements|value = HN123

imagen-20260220-143406.png

 

  • tos|@|terminal|@|quay|@|berth|@|id|value = B2

 

imagen-20260220-143319.png

 

  • Events (count): 12

imagen-20260220-143447.png

  • che|@|on|totalcounter = 1200

imagen-20260220-143532.png

 

TIC Description

Search tags

M

emergency maintenance, assignment interruption, CHE downtime, CMMS, unplanned, impact

Technical

Version / Date

M

20260204

Technical

Internal TIC Version

M

R0.1

Technical

 

Created by

Edited by

Review / Approve

Published

@RBS EMEA

@Francisco Blanquer Jaraiz

 

 

 

 

 

 

 

© Copyright - TIC 4.0 All rights reserved | Design web by Fundación Valenciaport