Copyright Chris van Buskirk, Mar 2001 MAPLANT Status Report MICANTS March 2001

Copyright Chris van Buskirk, Mar 2001

MAPLANT Status Report

MICANTS

March 2001


MICANTS Timeline

April 2001: – SNAP integration– Practice run

May 2001:– PI review & customer demonstration

Late Summer 2001:– Initial assessment milestone


Recent Progress

Architectural refinements

Refined Scheduler I/O Requirements

GUI Experiments (e.g. MS-Project)


MAPLANT Context Diagram

Bold = For May demo


MAPLANT Input Data Flight schedule (note: hardcoded example data for demo)

– A/C types needed for events (i.e. day/night/radar)– Sortie times (start, end, duration)– Event Priorities– Pit/turn info – Mission types – Ordnance

Maintenance plan– Special inspection types– Side numbers– Due dates– Usage-based inspections

Repair manual Inspection manual

– Job type– Task breakdowns– Task duration– Personnel requirements– Task sequencing requirements– Equipment requirements

Bold = In today’s demo


MAPLANT Input Data (cont.) Guidance

– Shift length– Shift start– Holidays

Maintenance schedule– Shift-level (coarse grain) granularity– “Locked” maintenance actions

Technical directives Aircraft inventory

– Type– BUNO– Side number– Status & EOC codes– Frame number– Engine number– Lifecounts

MAFs Roster

– Manpower, skill level, qualifications, MOS Support equipment inventory

– Type, location Bold = In today’s demo


Scheduler refinements

Scaled up to five week look aheadAdded shift-related guidance modelAdded flight ops tempo considerations

Types of constraints currently encoded– Mgmt of maintainer resources– Task sequencing (not using today)

– Guidance (holidays, shift properties)

– Flight schedule requirements


What is being demonstrated Automatic generation of five-week look-ahead

reflecting:– Aircraft special inspection requirements

– 1 7-day inspections– 21 14-day inspections– 4 28-day inspections– 177 total maintenance actions

– Aircraft type, availability and status– 2 Day aircraft, 8 Night aircraft, 1 Radar aircraft

– Flight ops requirements– All night A/C must be available every Wednesday night

– Maintenance guidance (shift durations and holidays)

Iterative refinement– Phase 1: Shift-level granularity– Phase 2: Tasks scheduled down to the hour (configurable)

Integrated MS Project®-based reporting


Demo assumptions, limitations Can fly A/C if not performing a maintenance task

– Need the actual specs here Simulation of flight schedule effects

– Can turn on/off demanding night missions tempo one day per week

– Working w/ ISI on FltSched content refinements– Working w/ ISI to review alternative FS-related report for

suitability Only 7-, 14- and 28-day inspections considered

– No sequencing constraints on task execution have been defined yet

Manpower availability– Simplified modeling of tasks’ skill requirements– Accurate distribution of MOS codes and special quals across

workcenters not modeled


Demo script

Sequence of events:1. User starts MAPLANT from command line

“Create five-week look-ahead”

2. Problem summary displayedUser verifies, selects “OK” to continue

3. Pause to discuss shift, holiday guidance4. Pause for to discuss mechanics info5. Pause for to discuss flight schedule info6. MAPLANT generates coarse-grain schedule7. MAPLANT generates fine-grain schedule8. Repeat, adding flight schedule considerations9. Repeat, varying guidance (add holiday)


Scene 1: 5 Week Schedule


Scene 2: Night Operations


Scene 3: Change of Command


The Other Output: Aircraft Availability

Availability data:– Fly days– Flight times, durations– Aircraft info (ID, type)

Flexible reporting options1. “Native” output format is .xml2. Web-based calendar display3. PDA-type display4. VoiceXML (“1-800” voice-on-demand) output

An example of each report format follows…


Aircraft Availability Reporting1. XML format


XSL Transforms

Can install a program at a URL address which– detects capabilities of the client’s

browser– reformats the raw data for display on

the client device (i.e. a live snapshot of the system)


Aircraft Availability Reporting2. Web-based calendar format


Aircraft Availability Reporting3. PDA format


Aircraft Availability Reporting

Try it yourself! Dial: 1-800-555-8965 Developer ID: 62782 Pin: 2782

Try it yourself! Dial: 1-800-555-8965 Developer ID: 62782 Pin: 2782

4. VoiceXML (voice-on-demand) format

MAPLANT


To Do Input the real flight schedule Input accurate manpower requirements/quals Incorporate tool/SE constraints Other detailed models of business

– A/C requirements for 2p2t2

– Realistic/representative monthly scheduled maintenance load

– Etc…

Implement AircraftAvailabilityReport generation algorithms

Scheduler refinements– Currently: binary outcome

– Next: • Weighted constraints and guidance• “Anytime” behavior


To understand more… MAPLANT data schemas and instances

– http://www.isis.vanderbilt.edu/projects/micants/mag13/data/

Schema definition language (XML schema standard)– http://www.w3.org/XML/Schema.html

Data instance language (XML standard)– http://www.w3.org/TR/REC-xml


MAPLANT screen shots follow…


Schedule: 5 Weeks


Schedule: Wednesday night flights

scheduled


Schedule: extra holiday

Documents

Copyright Chris van Buskirk, Mar 2001 MAPLANT Status Report MICANTS March 2001