Skip to content

Workflows

This page is the short workflow map for ALB during a session.

Use these pages for the detailed planning behavior:

  1. Open ALB and select the timeline for the destination and runway setup you care about.
  2. Pick the layout that gives you the best runway-side planning picture.
  3. Use EAT:LT as the normal planning method.
  4. Monitor the landing timeline and sequence conformance.
  5. Use Advance 1, Resequence, or operational corrections only when the aircraft is no longer following the expected landing order.

Fallback workflow: EAT:AR

  1. Use EAT:AR only when you deliberately want the older rough flow method.
  2. Watch the via-fix streams rather than treating the landing timeline as the main driver.
  3. Adjust per-stream AR when the release picture is no longer right.
  4. Use Advance 1 or Resequence when a specific aircraft needs a local sequence correction.

Standalone

  • Use ALB as your own picture.
  • Choose the timeline and layout you want.
  • EAT:LT is still the recommended default unless you deliberately choose the fallback AR method.

Peer

  • Open Peers and confirm who else is connected.
  • If another controller is FMR, treat shared planning controls as theirs unless you have explicitly coordinated otherwise.
  • Keep using local display controls such as timeline choice, via-fix visibility, and layout selection.

FMR

  • Claim manual FMR with .alb fmr <ICAO>.
  • Choose the correct timeline, layout, EAT mode, and ETA policy for the airport.
  • In normal modern operation, monitor and correct the EAT:LT landing picture rather than continuously tuning AR values.
  • Use hold-related EAT actions only when the aircraft is already in hold and the operational prerequisites are met.

Backend seqsync operation

Backend seqsync is the backend transport layer that shares canonical per-aircraft sequence state from the FMR to peers.

Recommended use:

  • use normal unless load management or controlled testing requires otherwise
  • use throttled if backend or peer load is caused by SET2 bursts, but all aircraft should remain canonical
  • use horizon if far-floating aircraft are creating unnecessary churn and only operationally relevant aircraft need canonical synchronization
  • use suspend only as an emergency or deliberately degraded mode when canonical SET2 TX must stop temporarily

Important limits:

  • seqsync commands do not change FMR ownership
  • they do not change EAT:AR versus EAT:LT
  • they do not change ETA policy, backend transport health, or scratchpad fallback state
  • they do not create peer-owned resequencing

In suspend, peers may retain the last backend-owned overlay until recovery resync, explicit DEL, FMR ownership change, or local reset.

Hold / EAT

  • Use HLW* if this ALB instance should be allowed to write accepted hold timing back to the holding list after canonical EAT has been accepted locally.
  • Treat HLS as legacy or compatibility state rather than as a normal modern top-row workflow control.
  • In backend-primary healthy operation, canonical per-aircraft EAT authority comes from backend SEQ/SET2+AC.
  • The final /HOLD_EAT/HHMM/ write is the aircraft-visible side effect of that authority path.
  • If you need to assign a specific EAT, use .alb seat <Callsign> <HHMM>.
  • Treat SEAT as legacy, fallback, or compatibility handling rather than as the normal backend-primary authority path.

See EAT Coordination for the hold/EAT meaning and Retired: Scenarios for the retired scenario workflow.

Useful commands

Open ALB:

.alb open

Close ALB:

.alb close

Reload the current config file:

.alb reload

Claim or resign manual FMR:

.alb fmr <ICAO>

Set planned landing rate:

.alb plr <rate>

Set arrival spacing for one via-fix:

.alb ar <ViaFix> <minutes>

Set hold EAT for an aircraft already in hold:

.alb seat <Callsign> <HHMM>

Show backend seqsync mode and queue status:

.alb seqsync status

Change backend seqsync mode:

.alb seqsync normal
.alb seqsync throttled
.alb seqsync horizon
.alb seqsync suspend