SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

22
SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001

Transcript of SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Page 1: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

SNAP-MAPLANTIntegration Effort

Strategy Meeting – 2 Mar 2001

Page 2: 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.

Page 3: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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.

Page 4: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Outstanding Questions

Page 5: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

What/if we will do with ordnance

Are filling this column in yet?

No ordnance for May

Page 6: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

What other things will T&R codes affect

Which T&R codes?

relation w/ Pedro’s LUT

Page 7: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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 fragswill add new tag to FS

fuel?

(a) pri (b) time/dur (c) type [t&r + lut later] (d) pits/turns

Page 8: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Must get “pit”, “hot-pit” type stuff precisely defined to model turnaround times. initially no night flights & most

preventive maint happens during night shift

Page 9: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

2p2t2 & resource requirements must be specified

Page 10: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

We will be shooting for 5-week lookahead?

need typical MA scheduled plan

Page 11: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

{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

Page 12: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Planned inspections will come from where?

Lt. Martin

Page 13: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Aircraft inventory/status will come from where? not current AMRRs, but one w/

only one engine out

Page 14: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Personnel roster will come from where? From last MMP?

Page 15: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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?

Page 16: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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.

Page 17: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Will be ignoring TDs?

yes, ignore

Page 18: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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.

Page 19: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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)

Page 20: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

Fallback

Meet the SNAP IAM

Run MAPLAN w/ and w/o FS inputs (but no on-line iteration between maint/ops)

Page 21: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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.

Page 22: SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.

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)