AME Package Flow

AME = Aircraft Maintenance Execution. An AME package is the ERP container for everything that happens against an aircraft between two flights (or between an arrival and a release). Operationally it's often called a tech log. In the DB it lives at FLOG_TLGMN_TECH_LOG_HDR and its package number (TLGMN_TECHLOG_NO) looks like LC-000056-2020 or VP-000485-2014.

This is the hottest table in line-maintenance operations. Every sign-off, every consumed part, every discrepancy closure hangs off it.

The five phases of an AME package

  Arrival ──▶ Snag capture ──▶ Task execution ──▶ Part/resource reconciliation ──▶ Release

Phase 1 — Package open (arrival)

A tech log opens when the aircraft hits a station. The header row captures:

TLGMN_AIRCRAFT_REG_NO — which aircraft
TLGMN_ACT_ARRIVAL_DATETIME + TLGMN_UTC_ACT_ARR_DATETIME — when
TLGMN_FROM_STATION + TLGMN_JRNLOG_TO_STATION — where from/to
TLGMN_TECHLOG_CATEGORY — the class of log (1-Repair, 2-Scheduled, etc.)
TLGMN_FIRST_FLIGHT_FLAG — is this the first flight of the day
TLGMN_CREATED_BY + TLGMN_CREATEDDATE — audit stamps

From that moment, the package is the accumulator for everything done on this turn.

Phase 2 — Snag capture

Crew write-ups and inspection findings enter as snags in FLOG_TLGSNG_TECH_LOG_SNAG_DTL (keyed by TLGSNG_TECHLOG_NO → the parent tech log). Each snag that requires formal action is elevated to a full Discrepancy in DP_DISCP_DISCREPANCY_DTL.

For hero aircraft 1132: across its 1,040 tech logs, 1,825 snag rows were captured. Ratio of snags per package is high — this aircraft flies a lot.

Phase 3 — Task execution

This is the meat of the package.

The canonical Task table is FLOG_TLGWU_WORK_UNIT_DTL (keyed by TLGWU_TRACK_ID). In this data drop the header table is empty (probably because the operator exported from sign-off detail rather than the master header). But the downstream records still exist and are queryable by TECHLOG_NO:

Task sign-offs — FLOG_TLGTSO_TSK_SNOFF. Each task that's completed gets a sign-off row recording who (TLGTSO_EMP_NO), when, with what skill, and whether it's a primary or additional sign-off.
Sub-task sign-offs — FLOG_TLGSTSO_SUBTSK_SNOFF. Steps within a task.
Part consumption — FLOG_TLGPC_PART_CONSUMP_DTL. Every part used or swapped, with TLGPC_PART_NO, quantity, and TLGPC_STOCK_STATUS.
Resource consumption — FLOG_TLGRC_RES_CONSUMP_DTL. Labour or facility hours booked.
Execution comments — FLOG_TLGEC_EXCOMM_HIST — free-text notes from the technician.
Sign-off comments — FLOG_TLGSC_SOCOMM_HIST — commentary at sign-off.
Employee actuals — FLOG_TLGEA_EMP_ACTUALS_DTL — time-sheet reconciliation.

For hero 1132: 13,232 task sign-offs, 125,857 sub-task sign-offs, 2,389 part consumption events, 781 resource consumption rows. That's one aircraft across the dataset window — real operational density.

Phase 4 — Discrepancy resolution / deferral

Any discrepancies raised during the package must be either closed (resolved) or deferred before the aircraft can be released. See Discrepancy Lifecycle for the state machine.

Resolution actions land in DP_RESLHST_DISC_RESOL_HIST
Deferrals land in DP_DPDEF_DISC_DEFERRAL_DTL

Phase 5 — Certificate of Release (COM)

When every open task is signed off and every discrepancy is either closed or legitimately deferred, the package is cleared for release. A Certificate of Maintenance — CertificateOfMaintenance at FLOG_TLGCOM_TECH_COM_DTL — is issued. That's the legal document that says "this aircraft is airworthy and can be released to the crew".

The COM is signed by a certifying staff member whose skill authority covers the work performed. Skills are tracked in FLOG_TLGSKL_COM_SKILL_DTL.

Aircraft can't legally depart the station without a valid COM on file.

Related support tables

Material requests — FLOG_FLMR_MAT_REQ_DTL: when a task needs a part not currently on hand, a material request is raised to stores.
Issue/Return — fl_tlissret_issue_dtl: tracks parts issued from stores and subsequent returns.
Bench-stock consumption — flog_rbsc_bench_stk_cons_dtl: low-cost uncontrolled items (fasteners, safety wire) consumed against a task.
Document attachments — FLOG_TLGDA_DOC_ATTACH_DTL: photos, reports, service bulletins attached to the package.
Parameter updates — flog_tlgpm_param_upd_dtl: flight hours, cycles, calendar time advanced as a result of the work.

Tracing one tech log end-to-end

Given a tech-log number, the Brain assembles the full picture via the knowledge graph:

Header row in FLOG_TLGMN_TECH_LOG_HDR (one row).
All snags: FLOG_TLGSNG_TECH_LOG_SNAG_DTL WHERE TLGSNG_TECHLOG_NO = X.
Each snag's discrepancy: join via DISCP_MAINT_REPORT_NO.
Each discrepancy's resolution/deferral chain.
All task sign-offs: FLOG_TLGTSO_TSK_SNOFF WHERE TLGTSO_TECHLOG_NO = X.
All part consumption: FLOG_TLGPC_PART_CONSUMP_DTL WHERE TLGPC_TECHLOG_NO = X.
Certificate of Maintenance (if issued): FLOG_TLGCOM_TECH_COM_DTL.

The graph walk is done for you — see the traversal in the Step 3 report.