Wiki·domain·domain/work-center-and-facility.md

Work Center and Facility

The physical side of the MRO. Where maintenance happens.

The hierarchy

Organization Unit (OU)
    │
    ├── Station (airport / field location)
    │       │
    │       └── Logical Work Centers assigned to it
    │
    └── Logical Work Centers
            │
            ├── Physical Facilities (hangars, shops, benches)
            ├── Certified users authorised for it
            └── Certificate applicability (what skills this WC can certify)

Logical work centers

BAS_WCLOG_WC_LOGICAL_WC_DTL — 1,352 rows. Each row is a logical team/capability within the MRO:

  • Engine Test Cell
  • Avionics Repair Shop
  • Wheel & Brake Shop
  • Sheet Metal
  • Composites
  • NDT (Non-Destructive Testing)
  • Upholstery
  • etc.

Every task in an AME package or SWO is assigned to a work centre. Employees belong to work centres. Certificates are issued by work centres.

Physical facilities

BAS_WC_FAC_FACILITY — 46,388 rows. This is the catalogue of physical assets:

  • Hangars (H1, H2, …)
  • Test benches (Engine-1 bench, Hydraulic-3 bench, …)
  • Tools (torque wrenches, leak-test rigs)
  • Jigs and fixtures
  • Calibration equipment

Facilities are housed in work centers. The FAC_* prefix distinguishes facility rows.

User-to-work-center mapping

BAS_WC_WCUSR_WC_USER_MAP — 1.46M rows. Cross-reference of every employee authorised to work in each work centre. One employee typically maps to multiple WCs (they have multiple skills), and one WC has many authorised employees.

This is a big table for a reason: multiply ~6K employees × ~10 WCs each = 60K rows per airline per year of authorisations, across a multi-year dataset.

The join is used when the ERP asks: "is this employee authorised to sign off this task at this work centre?"

Certificate applicability per work center

BAS_WC_WCCERA_WC_CERT_APPL — 2,917 rows. Which work centres can issue which certificates. An avionics shop can certify avionics-related airworthiness releases; an engine shop can't.

Tied into the Certificate of Maintenance generation — a COM's issuing WC must be one that's certified for the task type.

OU-level work center detail

BAS_WC_WCOUDT_OU_LEV_WCDET — 844 rows. Some work-centre attributes vary by Organization Unit (e.g. operating hours, cost centre). This table scopes those.

Warehouse mapping

BAS_WC_WCWHM_WH_MAP — 1,585 rows. Each work centre has one or more warehouses it draws parts from. When a task on a WC's aircraft needs a part, the issue/return comes from the mapped warehouse.

Stations

CM_STNDTL_STATION_DTL — 113 rows. Airports where line maintenance happens. Referenced by TLGMN_FROM_STATION on every AME package.

Stations are typed by ICAO/IATA code. They're important for operational dashboards ("how many discrepancies at CDG last month?") and for routing.

How the physical layer plumbs into transactions

  • AME packages tie to a station via TLGMN_FROM_STATION. Work inside the package references work centres via task-level assignments.
  • Shop WOs tie to a primary work centre via swoh_primary_wc_code and have routing events to secondary WCs via swo_swortng_routing_dtl.
  • Sign-offs carry an implicit WC via the employee who signed off (looked up through WorkCenterUser).

Scaling

In a large operator:

  • Typical line stations: 5–50
  • Typical work centres: 50–500
  • Typical facilities: 5,000–50,000
  • Typical active employees: 2,000–15,000

Our dataset sits comfortably within that envelope.

See also