Document Page: First | Prev | Next | All | Image | This Release | Search

         (4) Field reporting/briefing requirements: Daily SITREPs too often
         from directorates. Should be on as required basis.
  
        m. Regarding commodity and aircraft acceleration - aircraft are
        expedited primarily to user requests, which is normal business at an A[C.
        Acceleration can only be done on commodities if the reps and money are
        available, along with components to do the repairs. Lead times are often
        too excessive to enable a buildup within six months.

        n. Regarding effectiveness of analysis tools - analysis tools were
        ineffective. Since WSMIS RAM was discontinued in July, REMIS is the only
        source of NMCS, NMCM rates. The volume of paper and response time of REMIS
        is completely unacceptable.

       o. Regarding various maintenance concepts - most acted fairly
       independently. We need to get a better bauble on available repair location
       capabilities, especially MAJCOM capability to deploy and set up queen Bee
       type activities.
       
       p. Regarding the need for a push logistics system - the requisition
       system teas too many delays inherent to it. We can see requirements in a
       message, fax, or telecon before 16 shows up as a requisition; however, the
       entire system is set up to only respond to a valid requisition. A lot; of
       this can be overcome by reviewing our WRSK requirements, since this is the
       first real opportunity we have bad in decades to validate them with actual
       experience over a sustained period of time.

       q. Regarding organization of CLSS units - properly organized, but they
       are misunderstood. Also, we need more dedicated in-house engineers, working
       everyday with their deployment weapon system; i.e., the SPM does not control
        the CLSS, Q AFLC/HQ does...they are not a depot field team, they are a
       combat Repair organization.
       7. WR-ALC/TI Comments:

            a. Surge
 
  	  (1) Background: There were problems with surge requirements sent
       from off base production managers to WR-ALC/TI as source of repair. There
       were several instances where we received surge requirements from Tinker and
       the need date would be the same day. When we contacted the off-base
       production manager, we found out there was a lag time of three to five days
       from the time be sent the request to his battle staff and the time it was
       actually sent to WR-ALC Battle Staff. As a workaround, the surge requests
       were faxed and then matched up with the official request when it came
       through the normal channels.

                (2) Action Required: Surge requirements should receive top              
       priority when being sent from one ALC to another.       

Document Page: First | Prev | Next | All | Image | This Release | Search