Robert Neches & Pedro Szekely, USC ISI, © 2000 CAMERA, http://www.isi.edu/camera/
Logistics Working GroupLogistics Working Group
CAMERA - MICANT CoordinationCAMERA - MICANT Coordination
Robert Neches, Pedro SzekelyRobert Neches, Pedro SzekelyUniversity of Southern CaliforniaUniversity of Southern California
Information Sciences InstituteInformation Sciences InstituteMarina del Rey, CaliforniaMarina del Rey, California
Gabor Karsai, Benoit Dawant Gabor Karsai, Benoit Dawant Vanderbilt UniversityVanderbilt University
Russ CurrerRuss CurrerIdea ServicesIdea Services
Robert Neches & Pedro Szekely, USC ISI, © 2000 CAMERA, http://www.isi.edu/camera/
What Makes True Logistics What Makes True Logistics a Good Negotiation Testbed?a Good Negotiation Testbed?
Dynamic, continuous process:Simultaneous long-range, short range and execution 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 loops First demonstration of feedback loops in a large-scale negotiation processin a large-scale negotiation process
First demonstration of feedback loops First demonstration of feedback loops in a large-scale negotiation processin 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 actions in light of the flight schedule
SNAP supplies daily flight schedule to MAPLANT which in turn generates a daily maintenance plan
2. Scheduling/planning of long-term, strategic, scheduled maintenance actions w.r.t. long-term flight schedule
SNAP supplies n-week flight schedule to MAPLANT which uses that to generate a long term maintenance plan
3. Scheduling flight operations based on plane availability
MAPLANT provides a "best effort" estimates for the number of available aircrafts over time. SNAP creates a schedule based on these estimated generation rates.
4. Scheduling flight operations based on plane availability and capabilities
MAPLANT provides a "best effort“ estimates for the number aircrafts, their capabilities, other attributes, and negotiable and non-negotiable constraints associated with them. SNAP creates a schedule based on this.
5. Negotiation between MAPLANT and SNAP
The two systems interact using a well-defined messaging protocol to facilitate negotiation between the flight schedule and maintenance schedule. The objective is to explore trade-offs between the two aspects to achieve global optimization w.r.t. some metric (e.g., generation rate, 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
OPSMaintenance
Guidance
MAPLANT SNAP
First Cut Plan
Refined Ops Plan
Approx. Maintenance Plan (A/C status)
Refined Maintenance Plan
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. flight hour guidance)
MICANT: scope initial MAPLANT coverage of maintenance issues(portions of T&R manual, Mission Essential Systems List) in order to determine scenario specifics
Week of Dec 18: VTC to define interfaces (probably XML DTDs), flesh out 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
Top Related