Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
Logistics Working GroupCAMERA - MICANT CoordinationLogistics Working GroupCAMERA - MICANT Coordination
Robert Neches, Pedro SzekelyRobert Neches, Pedro Szekely
University of Southern CaliforniaUniversity of Southern California
Information Sciences InstituteInformation Sciences Institute
Marina del Rey, CaliforniaMarina del Rey, California
Gabor Karsai, Benoit DawantVanderbilt UniversityGabor Karsai, Benoit DawantVanderbilt University
Russ CurrerRuss Currer
Idea ServicesIdea Services
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
What Makes True Logisticsa Good Negotiation Testbed?What Makes True Logisticsa Good Negotiation Testbed?
Dynamic, continuous process:Simultaneous long-range, short range andexecution concerns
–Six-month to year goals for Marine Expeditionary Units(MEUs): you, your aircraft, data, systems and 2k friends
–Build/maintain weekly and daily schedules
–Repair schedules on five minutes notice
Strong good-enough / soon-enough pressures(same reasons)
Contrast to traditional optimization
–Cannot elicit full evaluation function in advance
–Frequent need to change constraints to handle problem
VERY high military payoffs: Money, Lives
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
Key Ideas of a Joint DemonstrationKey Ideas of a Joint Demonstration
First demonstration of feedback loopsin a large-scale negotiation processFirst demonstration of feedback loopsin a large-scale negotiation process
First demonstration of feedback loopsin a large-scale negotiation processFirst demonstration of feedback loopsin a large-scale negotiation process
Commander’sIntent
Commander’sIntent
Mission-SensitivePlanning
Mission-SensitivePlanning
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
CAMERA / MICANTS Integration PlanCAMERA / MICANTS Integration Plan
1.
Scheduling/planning of short-term,tactical, corrective maintenance actionsin light of the flight schedule
SNAP supplies daily flight schedule to MAPLANTwhich in turn generates a daily maintenance plan
2.
Scheduling/planning of long-term,strategic, scheduled maintenanceactions w.r.t. long-term flight schedule
SNAP supplies n-week flight schedule toMAPLANT which uses that to generate a longterm maintenance plan
3.
Scheduling flight operations based onplane availability
MAPLANT provides a "best effort" estimates forthe number of available aircrafts over time. SNAPcreates a schedule based on these estimatedgeneration rates.
4.
Scheduling flight operations based onplane availability and capabilities
MAPLANT provides a "best effort“ estimates forthe number aircrafts, their capabilities, otherattributes, and negotiable and non-negotiableconstraints associated with them. SNAP createsa schedule based on this.
5.
Negotiation between MAPLANT andSNAP
The two systems interact using a well-definedmessaging protocol to facilitate negotiationbetween the flight schedule and maintenanceschedule. The objective is to explore trade-offsbetween the two aspects to achieve globaloptimization w.r.t. some metric (e.g., generationrate, CRP, etc.)
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
Insights and New DirectionsInsights and New Directions
Services rendered by negotiation
–Control systems
–Decision support
Dimensions of scaling to explore
–Speed: tie to replanning during missions
–Size: coordinating much larger organizations
–Planning horizon: very long-range planning
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
Rough Demo ScenarioRough Demo Scenario
OPS
Maintenance
Guidance
MAPLANT
SNAP
First Cut Plan
Refined Ops Plan
Approx. MaintenancePlan (A/C status)
Refined MaintenancePlan
Robert Neches & Pedro Szekely, USC ISI, © 2000
CAMERA, http://www.isi.edu/camera/
Tasks and TimelineTasks and Timeline
CAMERA: implement SNAP initial assessment milestones (esp. flighthour guidance)
MICANT: scope initial MAPLANT coverage of maintenanceissues(portions of T&R manual, Mission Essential Systems List) inorder to determine scenario specifics
Week of Dec 18: VTC to define interfaces (probably XML DTDs), fleshout schedule based on scenario specifics
Jan: coordination meeting
Feb: Status review: GO vs. DEFER decision on scheduling
If decision is GO, then:
–Issue invitations to major constituents for high-profile demo in April
–Schedule March integration and first rehearsal meeting
–April: provide major demonstration at MCAS Yuma and/or other venues