Crew Union & Labour Agreement Compliance
Crew Management › Crew Compliance & Certification · 20 L4 steps · 5 phases · 6 decision gates · Updated 2026-03-19 13:36
📊
Process Flow Diagram (BPMN)
📋
L4 Process Steps
| Step | Step Name | Role / Swim Lane | System | Input | Output | KPI | Dec? | Exc? |
|---|---|---|---|---|---|---|---|---|
Phase 1 1.1 |
Ingest ratified CBA language into rule repository | Labour Relations Analyst | Jeppesen Crew Management | Ratified CBA document or amendment notice from union | Rule change requests logged in Jeppesen crew scheduling rule library | CBA rule ingestion initiated within 5 business days of ratification | N | N |
| 1.2 | Configure duty/rest limits in scheduling engine | Crew Scheduling Systems Administrator | Jeppesen Crew Management | CBA duty/rest rule change requests; FAR Part 117 regulatory minimums | Updated Jeppesen rule set with CBA contractual duty time and rest limits | 100% of CBA rest rules coded and tested within 10 business days of ratification | N | N |
| 1.3 | Configure premium pay triggers and trip rig rules | Crew Pay & Labour Systems Analyst | SAP S/4HANA Finance (FI/CO) | CBA pay schedule, premium pay provisions, trip rig and guarantee rules | Configured pay rules in SAP with all premium triggers (IROPS reassignment, hotel substitution, min-day guarantee) | Pay rule configuration accuracy ≥99.5%; zero retroactive pay adjustments attributable to misconfiguration in first post-implementation payroll cycle | N | N |
| 1.4 | Validate rule configuration against CBA source text | Labour Relations Manager | Jeppesen Crew Management | Configured Jeppesen scheduling rules and SAP pay rules; original CBA text | Validation sign-off memo or change request list | Zero CBA violations attributable to misconfiguration within 90 days of new rule deployment | Y | N |
Phase 2 2.1 |
Run pre-publication CBA compliance scan on draft schedule | Crew Scheduling Analyst | Jeppesen Crew Management | Draft pairing solution from Jeppesen optimizer | Compliance report flagging CBA rule violations by article and step number | Compliance scan completed ≥2 hours before schedule publication deadline; scan must cover 100% of published pairings | N | N |
| 2.2 | Adjudicate violations and determine waiver or remediation | Labour Relations Analyst | Jeppesen Crew Management | Compliance scan violation report | Decision per violation: remediate, obtain union waiver, or escalate | 100% of violations resolved or formally waived before schedule publication; adjudication cycle ≤4 hours | Y | Y |
| 2.3 | Remediate non-compliant pairings or assignments | Crew Scheduling Analyst | Jeppesen Crew Management | List of violations requiring remediation; available crew pool and reserve positions | Revised compliant pairings or crew assignments | Remediation cycle ≤90 minutes; crew coverage maintained ≥97% post-remediation | N | N |
| 2.4 | Monitor real-time crew duty times and rest windows | Crew Tracking Specialist | IBS Software iCrew | Live flight departure/arrival data; crew check-in and check-out events via ACARS | Real-time duty time dashboard; automated alerts for crews approaching CBA or FAR Part 117 limits | Duty limit alerts triggered ≥60 minutes before contractual limit; zero post-facto exceedances reported in monthly audit | N | N |
| 2.5 | Decide on duty extension or crew replacement during IROPS | Duty Manager | IBS Software iCrew | Duty limit alert; flight delay status; qualified reserve availability at station | Documented decision: CBA extension invoked with crew consent, or replacement crew assigned | Crew replacement or extension decision made ≥45 minutes before departure; 100% of CBA waiver invocations logged with timestamp and crew consent reference | Y | Y |
Phase 3 3.1 |
Log and acknowledge crew grievance within CBA window | Labour Relations Coordinator | SAP SuccessFactors (Employee Central) | Written grievance submitted by crew member or union representative | Grievance case record with CBA article citation, incident timestamp, and acknowledgement sent to filer | 100% of grievances logged within 24 hours of receipt; formal acknowledgement delivered within CBA Step 1 filing window (typically 72 hours) | N | N |
| 3.2 | Investigate grievance and retrieve corroborating data | Labour Relations Analyst | IBS Software iCrew | Grievance case record; referenced duty period, flight, or pay event | Investigation dossier with duty logs, pay records, system-generated timestamps, and CBA article analysis | Investigation completed within CBA Step 1 response window (typically 14 calendar days); 100% data retrieval from duty records for incidents ≤24 months old | N | N |
| 3.3 | Assess grievance merit and issue management response | Labour Relations Manager | SAP SuccessFactors (Employee Central) | Investigation dossier; CBA articles cited in grievance | Merit assessment and formal Step 1 management response delivered to union | Management response delivered within CBA Step 1 deadline 100% of the time; grievance upheld rate ≤15% | Y | N |
| 3.4 | Escalate unresolved grievance to arbitration | Labour Relations Director | SAP SuccessFactors (Employee Central) | Grievance not resolved at Steps 1–3; arbitration demand notice from union | Arbitration brief, hearing schedule confirmed, award recorded in case management system | Arbitration win/settlement rate ≥60%; average cost per arbitration case ≤$15,000 | N | Y |
Phase 4 4.1 |
Execute monthly CBA compliance audit across all domiciles | Labour Compliance Auditor | AWS Redshift | Prior month's schedule execution data, payroll run outputs, duty logs from iCrew | Monthly compliance dashboard showing violation rate by CBA article, crew category, and domicile | Audit completed by day 5 of the following month; CBA violation rate ≤0.5% of all duty periods in scope | N | N |
| 4.2 | Distribute compliance report to union per CBA schedule | Labour Relations Manager | Tableau | Monthly compliance dashboard from AWS Redshift | Formatted union-facing compliance report delivered by CBA-stipulated deadline | Report delivered by 10th of the month 100% of the time; zero data discrepancies disputed by union within 30 days of delivery | N | N |
| 4.3 | Determine if corrective action plan is required | Labour Relations Manager | SAP SuccessFactors (Employee Central) | Monthly compliance report; union objections or formal notices if any | Corrective Action Plan (CAP) initiated or formal closure memo issued | CAP initiated within 5 business days of audit finding confirmation; 100% of open CAPs closed within 60 days | Y | Y |
Phase 5 5.1 |
Trigger CBA expiry alert and negotiation readiness review | Labour Relations Director | SAP SuccessFactors (Employee Central) | CBA expiry date calendar alert (18-month advance trigger) | Negotiation readiness checklist; data extraction scope and timeline defined | Negotiation preparation formally initiated ≥18 months before CBA expiry; zero missed expiry dates across all bargaining units | N | N |
| 5.2 | Extract historical compliance and cost data for bargaining | Labour Analytics Specialist | AWS Redshift | 3-year historical duty records, grievance case data, payroll actuals, IATA peer benchmarks | Bargaining data package: cost impact modelling of proposed rule changes, violation trend analysis, peer carrier benchmarks | Data package completed ≥12 months before CBA expiry; benchmark dataset covers ≥5 comparable peer carriers | N | N |
| 5.3 | Validate bargaining data package for negotiation | Labour Relations Director | Power BI | Draft bargaining data package from Labour Analytics | Approved bargaining data package or supplemental data extraction requests | Data package formally approved ≥10 months before CBA expiry; zero material data gaps surfaced at the bargaining table | Y | N |
| 5.4 | Implement ratified CBA rules in scheduling and pay systems | Crew Scheduling Systems Administrator | Jeppesen Crew Management | Ratified new or amended CBA document; confirmed effective date | Updated Jeppesen scheduling rules and SAP pay configuration; parallel-run test results; go-live sign-off | System implementation completed ≥14 calendar days before CBA effective date; zero pay errors attributable to new CBA rules in first post-implementation payroll cycle | N | N |
📋