1 / 22

SNAP-MAPLANT Integration Effort

SNAP-MAPLANT Integration Effort. Strategy Meeting – 2 Mar 2001. Vision Statement. Production of flight schedules that maximize the ability of maintenance to support command objectives. Production of long-term maintenance schedules that balance planned maintenance and operational needs.

kacia
Download Presentation

SNAP-MAPLANT Integration Effort

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SNAP-MAPLANTIntegration Effort Strategy Meeting – 2 Mar 2001

  2. Vision Statement • Production of flight schedules that maximize the ability of maintenance to support command objectives. • Production of long-term maintenance schedules that balance planned maintenance and operational needs.

  3. Scenario • Scene1: easy to support • Scene2: ops overstresses maint, maint does best, return failure to ops to drive lesser demands, ops re-runs schedule w/ new A/C up on day X constraints.

  4. Outstanding Questions

  5. What/if we will do with ordnance • Are filling this column in yet? • No ordnance for May

  6. What other things will T&R codes affect • Which T&R codes? • relation w/ Pedro’s LUT

  7. What portions of FS are important to maintenance? • event times/dur, A/C type, [T&R] • Are missions prioritized? How do we know which are training and which are fragswill add new tag to FS • fuel? •  (a) pri (b) time/dur (c) type [t&r + lut later] (d) pits/turns

  8. Must get “pit”, “hot-pit” type stuff precisely defined to model turnaround times. •  initially no night flights & most preventive maint happens during night shift

  9. 2p2t2 & resource requirements must be specified

  10. We will be shooting for 5-week lookahead? •  need typical MA scheduled plan

  11. {boolean,AAR} responses • Previously some talk about “D-5 is going to be down after all” messages. • simply the tuple! • ops must consider monthly flt hr requirements

  12. Planned inspections will come from where? • Lt. Martin

  13. Aircraft inventory/status will come from where? •  not current AMRRs, but one w/ only one engine out

  14. Personnel roster will come from where? • From last MMP?

  15. How will we model the health of downed A/C (an attribute--expected time to repair--of the inventory list)? • Also, will we be scheduling these maint actions? (Don’t have manuals) • Will DW be providing MAF dumps?

  16. Will we consider tools/SE (which)? • Goal: model the inventory and resource constraints imposed by this (Martin will help). • Borrowing from sister squadron? • Tech training ½ day Monday.

  17. Will be ignoring TDs? • yes, ignore

  18. Should be able to start the negotiation iterations from either maintenance or ops? • yes • Russ Note: Make sure you have the whole squadron modeled @80% capacity.

  19. FS schema & String “day|night” problem • Pedro will supply alternative datastructure for FS info (includes pits/turns) • Pedro will set me up w/ CVS account for source access • Getting rid of day birds at Yuma now (16 plane, 400-500hr/mo)

  20. Fallback • Meet the SNAP IAM • Run MAPLAN w/ and w/o FS inputs (but no on-line iteration between maint/ops)

  21. Due to the turnover • Shooting for Apr 30th if possible? Open question. ISIS had been shooting for middle of May. Turnover, however is June 1. • Make sure you practice the presentation (w/ ISI). Must impress new CO.

  22. Integration • Run SNAP @ Vandy on Apr 13th, then run MAPLANT with and without SNAP output. • Russ needs to lay down scenario assumptions • Need input data from Lt. Martin(get Beatrice involved)

More Related