Visit Planning

A visit is a planned, multi-day maintenance event. Where an AMEPackage handles a turn between flights, a visit handles the aircraft in the hangar for a week to a month. Typical examples:

A-check — monthly, ~1 day, minimal downtime
C-check — every 18–24 months, 1–3 weeks
D-check — every 6–10 years, 3–6 weeks, full structural inspection

Visits are built from hundreds of task cards from the TaskMaster, grouped into a cohesive visit package (VisitPackage) that planners can manage as one unit.

The visit in the data

In the dataset, visits live primarily in SWO_Visit_Lvl_Info (the top-level visit info, ~3,500 rows) and cascade into:

SWO_Visit_Lvl_Cmp_config — component configurations this visit applies to
SWO_Visit_Lvl_Cmp_cfg_dtl — detailed config rows (~249K rows, capped in our load)
SWO_Visit_LLP_Info — life-limited parts tracked in this visit
SWO_VISIT_CFG_DTL_REV_BASELINE — baseline revision records (what was planned vs what changed)
SWO_Visit_DFT_COMP_Draft_DTL — draft-state detail before the visit goes live
swo_visit_cmpl_dtl — completion details
swo_visit_dft_plan_eo_dtl — draft Engineering Order plans
swo_visit_plan_eo_dtl — live EO plans

Anatomy of a visit plan

A visit package, when planned, looks like:

VisitPackage (one row, the top-level event)
  ├── Configurations — which components the visit affects
  ├── LLP tracking — life-limited part replacement scheduled
  ├── Task bundles — drawn from TaskMaster + ModelEffectivity
  ├── Engineering Orders — mandatory SBs/ADs rolled in
  ├── Related Shop WOs — components that'll be removed & sent to shop
  └── Baseline revisions — each time the plan is re-baselined

The task bundles come from:

BAS_TSK_TSK_TASK_MASTER — the catalogue of known tasks
bas_tsk_tskd_task_details — task detail / steps
bas_tsk_tskme_mdl_effect — which models each task applies to (effectivity)
bas_tsk_tskp_spare_part — spare parts that task consumes

Visit EO (Engineering Order) handling

Engineering Orders are mandated work — Airworthiness Directives (ADs) from the regulator, Service Bulletins (SBs) from the manufacturer, company-specific modifications. Visits bundle applicable EOs in:

swo_visit_plan_eo_dtl — the EOs planned into this visit
swo_visit_pln_eotsk_dtl — the tasks generated by each EO
swo_visit_eo_cmpl_pos_dtl — completion status

Amendments

Plans change. The amendment tables track that:

swo_wsa_amend_hdr — amendment header (reason, approver)
swo_wsacg_amend_config_dtl — config impact of the amendment
swo_wsatsk_task_amend_dtl + swo_wsatsk_amend_task_impacted_dtl — which tasks are added/removed/modified
swo_wsati_amend_maint_lvl_dtl — maintenance-level impact
swo_wsaref_reference_dtl — references cited for the amendment

Baseline management

A visit is "baselined" when the plan is locked in. Subsequent changes roll into revised baselines tracked in SWO_VISIT_CFG_DTL_REV_BASELINE and swo_wobsl_baseline_wo_hdr. This gives a full audit of "what did we originally plan vs what did we do?"

Link to line work and shop work

A visit isn't isolated — it generates:

Multiple AMEPackage rows for work done on the airframe
Multiple ShopWorkOrder rows for components removed and sent to repair in parallel

All coordinated through the visit's visit_id.

What a visit looks like operationally

Day 0 the aircraft arrives at the base. Line maintenance hands off to visit planning. The hangar team:

Starts stripping interior and panels
Kicks off task execution against the pre-baselined task list
Removes components requiring shop repair — each generates an SWO
Executes engineering orders mandated for this visit
Finds unscheduled defects — these become Discrepancy records that extend or amend the visit
Reassembles, tests, paints
Issues the release certificate

A typical C-check produces thousands of sign-off rows, tens of part consumption events, and a dozen or more shop work orders in parallel.

Planning horizon

Visit planning runs ~12 months ahead of execution for C-checks (to schedule the hangar slot and pre-order parts). Amendment activity typically peaks in the 30–90 days before the visit starts.