MICANTS Gabor Karsai Greg Nordstrom Chris vanBuskirk Jon Doyle Vera Ketelboeter George Bloor Russ Currer Vanderbilt/ISIS MIT Boeing Idea Services Benoit Dawant Karlkim Suwanmongkol Patrick Norris Jonathan Sprinkle

CACE/MICANTS [10/00] MICANTS Goals How to useHow to use Agents/Negotiation technology to solve complex resource management problems in (Autonomic) Logistics to solve complex resource management problems in (Autonomic) Logistics To demonstrate the feasibility of the technology through real-life example(s)To demonstrate the feasibility of the technology through real-life example(s)

CACE/MICANTS [10/00] Roles Vanderbilt/ISIS MIC, implementation, and demonstration MIT Concepts, algorithms Boeing Modeling, domain knowledge Idea Services Domain expertise and scenarios, customer interface

CACE/MICANTS [10/00] Background Agents/Negotiation Technology Constraints manages Constraints manages CONFLICT negotiation Mutually acceptable, Negotiated solution satisfies Objective: “Good enough solutions/soon enough”

CACE/MICANTS [10/00] Vision: Agent-supported Maintenance Process discrepancy report MMCO Flight Schedule Shop Maintenance Schedule Assign mechanic negotiate W/C OIC Goal:Assistance through offering negotiated options options approve report options approve negotiate options approve Autonomic response MMCO (sister squadron) Agents: “Helpers” for the users “Wired” to implement CO’s intent, business rules, and user guidance Negotiate solutions autonomically Offer options for approval Commander’sIntent CAUTION: Simplified picture

CACE/MICANTS [10/00] MAPLANT: MAPLANT: MAintenance PLanning AgeNTs

CACE/MICANTS [10/00] Agents for the users Maintenance Control Chief’s Agent Receives and logs gripes Negotiates with MALS and W/C-s Barters with sister squadron Shows canni options Event status display Event/AC assignments AC status over time “What-if”s Maintenance Control Chief’s Agent Receives and logs gripes Negotiates with MALS and W/C-s Barters with sister squadron Shows canni options Event status display Event/AC assignments AC status over time “What-if”s Work Center Supervisor’s Agent Schedules calendar-based MAs Proposes schedule(s) Schedule displays (with options) Work Center Supervisor’s Agent Schedules calendar-based MAs Proposes schedule(s) Schedule displays (with options) Helper “agents” Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers) MALS Helper “agents” Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers) MALS Current prototype

CACE/MICANTS [10/00] How does it work? What can it do? M/C Startup Event Status Board (M/C) Event times EVT/AC assignment A/C status (OK, down, repair) M/C Startup Event Status Board (M/C) Event times EVT/AC assignment A/C status (OK, down, repair) Current prototype W/C Startup Schedules calendar-based MAs  Input:  Job list with time and MOS requirements  Worker pool with qualifications  Output:  Jobs scheduled and assigned to workers W/C Startup Schedules calendar-based MAs  Input:  Job list with time and MOS requirements  Worker pool with qualifications  Output:  Jobs scheduled and assigned to workers Constraint-based scheduling:  Task “start-after”s, “ends- before”-s, and durations  Task precedence  Resource constraints  Alternatives/flex assignments Helper startup Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers) Helper startup Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers)

CACE/MICANTS [10/00] How does it work? What can it do? M/C receives gripe/diagnosis Status Board: shows conflicts Selection: A/C + Gripe Options: Standard procedure (MALS) Barter (with other M/C) Canni (if possible) Evaluation: Check effects on flight schedule Changes: Accept/refuse proposed MA AC to event assignment M/C receives gripe/diagnosis Status Board: shows conflicts Selection: A/C + Gripe Options: Standard procedure (MALS) Barter (with other M/C) Canni (if possible) Evaluation: Check effects on flight schedule Changes: Accept/refuse proposed MA AC to event assignment Current prototype W/C operation: Reactive (re-)scheduling  Input:  New job with time and MOS requirements  All “old” jobs  Output: (for approval)  Multiple schedule options for new job W/C operation: Reactive (re-)scheduling  Input:  New job with time and MOS requirements  All “old” jobs  Output: (for approval)  Multiple schedule options for new job MALS: Reply with time for part availability MALS: Reply with time for part availability Sister squadron M/C: Reply with time for part availability Sister squadron M/C: Reply with time for part availability A/C in maintenance: Reply with time parameters A/C in maintenance: Reply with time parameters

CACE/MICANTS [10/00] How does it work? What can it do? M/C “smarts” Shows/warns about conflicts with flight schedule Keeps track of current/pending MAs Displays available options when “repairing” AC/EVT allocations Detects A/C in repair that can be utilized in canni Can arrange barter with other M/C’s agent “What-if” Effect of the selected MA on the flight schedule Suggests possible optimizations Swaps (possibly with other squadron) “Milking” M/C “smarts” Shows/warns about conflicts with flight schedule Keeps track of current/pending MAs Displays available options when “repairing” AC/EVT allocations Detects A/C in repair that can be utilized in canni Can arrange barter with other M/C’s agent “What-if” Effect of the selected MA on the flight schedule Suggests possible optimizations Swaps (possibly with other squadron) “Milking” Current prototype W/C “smarts”  Rapid schedule generation  Multiple schedule options  Options are evaluated/ranked  Flexible schedule choices  Tentative scheduling choice, confirmed later W/C “smarts”  Rapid schedule generation  Multiple schedule options  Options are evaluated/ranked  Flexible schedule choices  Tentative scheduling choice, confirmed later Initial data from warehouse: Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers) Initial data from warehouse: Aircraft (health status) Mission (events, flight schedule) Jobs (maintenance actions) Workers (maintainers)

CACE/MICANTS [10/00] The details Current prototype Scenario walk-through (Greg Nordstrom) Demo (Chris vanBuskirk) WE APPRECIATE YOUR INPUT! PLEASE TELL US WHAT YOU THINK! WE APPRECIATE YOUR INPUT! PLEASE TELL US WHAT YOU THINK!

CACE/MICANTS [10/00] Summary/Discussion Agents that negotiate and offer choices to users Scheduling, operational choices,optimization User-driven tools Input side: guidance Output side: choices In between: automatic when feasible Plans: Strengthening the implementation(robustness,GUI,etc.) Refinement of functionalities (metrics, etc.) Guidance input capability Optimization capability (with user customization) Cooperation with flight scheduling Discussion: YOUR feedback