MAPLANT

1. MAPLANT A Decision Support Tool for Aircraft MaintenanceChris van BuskirkJune 28th, 2002 DARPA IXO ANTS - Complexity and Dynamics Workshop

2. Goals of the Presentation 2. Explain MAPLANT’s Scheduling Problem c.set the stage for PM session to explore the possibilities for collaboration b. scheduling techniques/algorithms a. data formats for our repository of real-world scheduling data 1. Quick introduction to the problem domain and the end-user application software

3. Goals of the Project • Develop efficient, distributed algorithms for solving maintenance logistics problems • Localized concerns should be a key concept of the software architecture • Related concerns must communicate with one another during the problem-solving process • Devise an architecture that, under run-time constraints, may not be able to satisfy all individual concerns, yet produces acceptable solutions--from a global perspective. • Measure success based on performance of real systems in production environments

4. Architecture: Simplified Domain MAPLANT Encoder Scheduler Decision Space

5. Test Bed Environment • Marine Air Group 13 • Marine Attack Squadron 513 • Marine Attack Squadron 214 • Marine Attack Squadron 311 • Marine Attack Squadron 211 • 11th Marine Expeditionary Unit • 31st Marine Expeditionary Unit

6. The Business FlightOperations AircraftMaintenance LegacyComputingSystems FlightExecution

7. The CACE1 Toolset 11010011000110010100 … SNAP ISI / USC MAPLANT ISIS / Vandy DataWarehouse& ReportingLLD LegacyComputingSystems MSAR ISI / USC http://www.cacey.com

8. The Business FlightOperations AircraftMaintenance LegacyComputingSystems FlightExecution

9. Maintenance Organization Naval Regulation Commander’s Intent Domain Expertise Maintenance/Material Control Avionics Airframes Powerline ToolRoom CorrosionControl Ordnance Life Support SeatShop MaintAdmin QA

10. The Problem • Long-Term Planning Tool:Analysis of the effect of (a) operational tempo, (b) operator-defined guidance and (c) resource availability on the upcoming maintenance workload AND analysis of the ability to support various operational scenarios (~5 week planning horizon).

11. Inputs Considered Tools/GSE:Realistic O-level tool inventory and GSE availability Personnel Roster: Full complement (+200 maintainers) Ranks, quals by workcenter (10 WCs) • Maintenance Guidance:4790/NAMP regulations, shift durations, holidays, spares strategy desired aircraft utilization, fall-back margins, rules of thumb, … Aircraft Status:(~17 jets) 5 Week Look Ahead Schedule w/i 10 minutes MAPLANTScheduler Possible Maintenance Actions: All calendar-based, usage-based and phased maintenance inspections currently modeled plus a facility for defining any idiosyncratic inspection types. Flight Schedule:based on squadron guidance for the upcoming planning period (from SNAP) • Upcoming Aircraft Inspections:5 week planning horizon (thousands of maintenance actions) • Operational Deviations:Extra [one-of] workloads.

12. ROT: Example Strategies • When possible, stagger execution of those tasks having a resource consumption level that is unusually high. • Attempt to run concurrently those jobs that share work (e.g. remove wing on AC-03). • Retain 60% of day-shift mechanics for unexpected events. • Prefer to keep $X number of spare/backup jets which flying at tempo $Y

13. Architecture: Actual Data Warehouse 1.Inputs Guidance Guidance Knobs A/C Status UpcomingInspections 2. Assignments & Projections 3. Risk analysis CFSA Project Flt Hours Projected Maint CFSA View PFSA Flt Hours Analysis Maint Manuals Overlap Margins 5.Results 4. Maintenance Scheduler Maintenance Schedule Schedule View Resource Margins Scheduler Encoder Aircraft Availability MntPlan View SNAP Tools/SE Roster

14. Example MAPLANT Screens

15. Screen: A/C Status

16. Screen: Flight Schedule

17. Screen: Upcoming Inspections

18. Screen: Upcoming Inspections

19. Screen: Roster

20. Screen: Shift Guidance

21. Screen: Utilization Guidance

22. Screen: Maintenance Sched

23. Screen: Guidance Violated

24. Scheduler Slides Here Gabor Szokoli …

25. Future Directions • Shift-Change Decision Support: support unscheduled maintenance activities (requires many more manuals!) • Vertical Extensions: add new decision support tools targeted at higher levels in the command chain (requires interaction with new customers) • Horizontal Extensions:add support for new equipment type/model/series (requires support from new customers; e.g. F-18 & C-130)

26. Future Directions • System of Systems Negotiation Protocols:continue developing interaction protocols between related software systems in the CACE toolset • Maintenance vs. Aircraft Configuration & Capabilities (MAPLANT-MSAR) • Maintenance vs. Operational Issues (MAPLANT-SNAP)

27. Future Directions: CSP • Unified flight & maintenance scheduler (distributed) • Constraint Libraries: • Add more [reified] [domain-specific] soft constraints • In the interest of safety, minimize the number of shift changes that a task must endure • In general, start phase inspections in time to finish before the weekend (to avoid accumulating SCIR hours) • Stateful/shareable resources • Multi-capability resources • Explore intelligent constraints that adapt behavior based on the state of the search

28. Future Directions: CSP • Optimizing Searches: • Make use of the branch and bound search facility • GUIs/tools allowing for user-influenced searches • Labeling Heuristics: • Domain-specific heuristic strategies for variable selection and value selection • Strategies for switching labeling mode based on state of the search (e.g. time to deadline)

30. ---------------------------------- Appendix A

31. Guidance Fleet Info Gives AC types (day, night, radar) Aircraft Assignment 1 Each AC has: 1. Min, Max, Pref for month 2. Can/Cannot fly for each day of mo. 3. Optional deadline with min, max, and pref (takes precedence over month until it is satisfied) Assign the AC’s to flights, by assigning to the most desperate AC’s first (based up Guidance info), using the FS for supporting information, and the Guidance for driving information. G AC Run until all AC’s have reached their minimum, or until no further sorties can be assigned. FS 2 Assign the AC’s to flights, but this time utilize the preference of the airplane, instead of a hard (min) constraint. Similarly, use the Guidance as driving info, and FS to collaborate. Run until all AC’s have reached their preference, or until no further Sorties can be assigned. FS with detailed sortie info 3 Now, use the FS as the driver, to make sure that all sorties are assigned, but utilize Guidance to make sure that max is not exceeded. Run until all sorties have been assigned, or until no further Sorties can be assigned. Flight Schedule

32. MAPLANT/IAM-1Operational scenario • 1. Maintenance Control Tunes Parameters • Aircraft Status Tweaks • Intentionally remove jets from the pool • Mark downed jets with expected up times • Partial Flight Schedule Assignment (PFSA) • Define/Modify Guidance • 2. Workload Projection • Complete Flight Schedule Assignment (CFSA) • Day-By-Day Projection of Accumulated Flight Hours per A/C • Project Scheduled Maintenance Workload(dues windows)

33. MAPLANT/IAM-1Operational scenario (cont.) • 3. Risk Analysis & Approval of Flight Schedule • CFSA Analysis (possibly override and re-iterate) • Resource Margins • Overlap Margins • Phase-Phase • 56-Phase (w/i and across a/c) • Engine-Phase • Engine-56 • Aircraft Utilization Rates • 4. Schedule Computation • Produces • Maintenance Schedule • Aircraft Availability Projection • Considering • PFSA Constraints • Resource Availability • Resource Margins • Phase-Phase Overlaps • Engine-Phase Overlaps

34. ---------------------------------- Appendix B

35. User-Influence Search Example • CycleAgent.ozComputes a plan of “operational flows” that conform to management’s desired flight-hour goals for the upcoming month, while simultaneously considering the risk of sortie cancellations due to committing to certain flow patterns given the projected status of the fleet throughout the month.

36. Definitions • Turnaround Inspection:safety inspection required when plane lands and the pilot relinquishes control of the jet to its plane captain (requires a minimum two hour break before the plane can be assigned to subsequent sorties) • Hot-Pit:less detailed procedure for turning the plane in preparation for its next sortie; requires that the same pilot fly the second sortie (i.e. a gas-and-go) • Spare:backup aircraft to be used in the event of some unexpected problem with the primary side number

37. Definitions • Operational Flow:A description of the sequence of pits and turns to be executed throughout some flyday. • 2p2t2 • 6t4p4 • 2t2t2

38. The Scenario • This code will compute a plan of operational flows, then measure its goodness in two dimensions: • Agreement with the stated monthly flight hour goals • Degree of risk of not carrying out the plan as stated