Skip to main content
LSA (Life-Saving Appliances) and FFA (Fire-Fighting Appliances) are the equipment that matters when nothing else does. Lifeboats, life-rafts, EEBDs, fire pumps, fire detection panels, fixed fire-fighting systems, breathing apparatus, immersion suits, lifebuoys — every item has a maintenance schedule, an inspection regime, and a flag-state-specific service requirement. A PSC inspector who finds an out-of-service lifeboat winch can detain the vessel. A flag inspector who finds an expired EEBD canister can issue a deficiency. The LSA / FFA Surveillance pipeline keeps every one of these items visible against its schedule and against the relevant flag-state requirements.

​
Where the data comes from

LSA / FFA service must be done by approved stations, so the authorisation list is itself a critical data source — service performed at a non-authorised station is invalid and must be re-done.

​
What’s tracked

Each equipment item carries:
  • Type and certification (SOLAS-approved, MED-marked, manufacturer)
  • Last service date and service type
  • Next service due date and type
  • Service interval (typically annual + 5-year overhaul + 10-year hydrostatic)
  • Service provider (approved station)

​
The three views

The LSA templates produce three complementary views:
Every LSA/FFA item with last service date, next due date, and the service type. The list view a Chief Officer reads to plan the next service round.
Flag circulars often add requirements above SOLAS — e.g. extra CO₂-system testing intervals, additional EEBD mustering exercises. This view surfaces the flag-state-specific overlay so the schedule reflects what this vessel’s flag actually requires, not just the IMO baseline.
The dashboard view — what’s been serviced when, what’s coming up, what’s overdue. Plus the supporting documentation (service reports, certificates) for each completed service.

​
Service-window classification

Same expiry-window logic the other pipelines use: Δdays=Dnext_service−Dtoday\Delta_\text{days} = D_\text{next\_service} - D_\text{today} LSA/FFA service windows are tighter than other expiry tracking because the service requires a shore-based approved station — you can’t service a lifeboat at sea. A service due within 14 days needs a port call within 14 days; if the schedule doesn’t allow it, the service slips and the equipment goes overdue.

​
Saturday routine

Saturday routines are the SOLAS-required weekly checks: lifeboat lighting, lifebuoy checks, fire-detection panel test, fire-pump start, etc. They aren’t part of the major-service schedule but they’re a leading indicator of LSA/FFA care. A vessel that consistently misses Saturday routines is a vessel where the smaller LSA/FFA items will start to drift. The pipeline tracks Saturday routine submission via the PMS pipeline and cross-references it with the major-service compliance.

​
Flag-state overlay

Different flags impose different service intervals and additional checks. The flag-overlay view pulls the relevant flag circulars from the flag-circulars corpus and produces an overlay:
  • Panama: Marine Notice 13-2018 — additional CO₂ system release-mechanism testing
  • Singapore: SCN 03 of 2023 — EEBD muster requirements during port stays > 24h
  • Marshall Islands: MN-2-011-44 — life-raft maintenance station authorisation list
  • Liberia: Marine Operations Note — semi-annual fire-pump performance verification
The overlay re-classifies items where the flag requirement is more stringent than the SOLAS baseline. A vessel can be SOLAS-compliant but flag-non-compliant — the overlay catches that.

​
Maintenance station compliance

LSA/FFA service is typically done by approved stations — not every shore facility can certify a lifeboat or recharge a CO₂ cylinder. The pipeline tracks:
  • Station approval status (active, lapsed, conditional)
  • Authorisation per flag (some stations approved by some flags)
  • Service-quality history (any rework events)
A service performed at a non-authorised station is invalid — the equipment must be re-serviced. The pipeline flags station-mismatch events explicitly.

​
Worked example

MV POSUN, Panama-flagged, end-of-April LSA/FFA review: Plus the Panama overlay:
  • CO₂ release-mechanism testing required quarterly under Marine Notice 13-2018; last done 2026-01-08, next due 2026-04-08 — overdue 22 days.
Verdict: CRITICAL — bridge EEBDs overdue today (must not be used at sea), CO₂ release-mechanism testing 22 days overdue under flag rules. Recommendations:
  1. Bridge EEBDs — service at next port (3 days). Until then, mark as out-of-service and use engine-room EEBDs for any bridge-area emergency.
  2. CO₂ release-mechanism testing — schedule with approved station at next port; this is flag-specific so a SOLAS-only inspection won’t catch it but a Panama flag inspector will.
  3. Fire-pump performance — book service for next port (within 11 days of due date).
The pipeline:
  1. Flags the bridge EEBD overdue to the Master with the temporary mitigation note.
  2. Generates the next-port service work-list.
  3. Routes the flag-overlay finding to the Marine Superintendent with the specific Marine Notice citation.

​
What the senior review contains

  1. Equipment service status table — every item with last service, next due, verdict.
  2. Overdue list — focused view, severity-ranked.
  3. Flag overlay findings — items where flag-state requirements are more stringent than SOLAS.
  4. Saturday routine compliance — weekly check submission rate.
  5. Maintenance-station status — authorisation gaps, service-quality history.
  6. Next-port service plan — items due within port-call window, prioritised.
  7. Escalation decision — to whom, and why.

​
Escalation triggers

​
Why LSA/FFA needs its own pipeline

LSA/FFA tracking sits awkwardly across the other pipelines. PMS handles it generically but doesn’t know about flag-state overlays; certificates tracks SoC but not the underlying service. Defects sees the failures after the fact. None of the other pipelines fully reflect the urgency of safety equipment — a 14-day overdue lifeboat winch has different commercial consequence than a 14-day overdue paint-locker inventory. The dedicated pipeline keeps the visibility and the priority right.
The single most consequential improvement most fleets can make on LSA/FFA is keeping the maintenance-station authorisation list current. A station that was approved last year may not be this year — service performed at a lapsed station has to be re-done. The pipeline cross-references the station list at the time of service to surface this immediately.

​
References

Templates: lsa-management

LSA-management suite — equipment service history, flag-specific requirements overlay, and service records with upcoming dates.

Related: PMS

LSA / FFA service items also live in PMS — the saturday-routine view is shared.

Related: Flag circulars

Flag-specific service overlay depends on a current flag-circulars corpus.

Related: Compliance

LSA / FFA findings appear in PSC and SIRE inspections — the compliance pipeline tracks those outcomes.