1 / 14

Streamlining C305 Work Control Processes to Enhance Efficiency and Quality

The current work control process in the C305 area is plagued by inadequate expertise, leading to increased cycle times and inefficiencies. This review outlines key problems such as slow supervision and excessive paper handling, which contribute to a subpar quality of work. To remedy these issues, we propose a robust go-forward plan that includes enhancing staffing, standardizing workflows and transitioning to an electronic work authorization system. The desired outcome is to streamline operations, reduce review times, and maintain best practices while minimizing the degradation of our skilled workforce.

verda
Télécharger la présentation

Streamlining C305 Work Control Processes to Enhance Efficiency and Quality

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. C305 Manning Plan and WAF Processing

  2. Current Work Control Process

  3. Problems in the Current Work Control Process Problem Area – Inadequate Expertise Generating WAF = Inefficiency + Low Quality

  4. Problems in the Current Work Control Process Problem Area – This review is done with paper and “sneaker net” = SLOW - Review burdens first line supervisors = no supervision of work - Change churns the process significantly sending paper back to C305/400

  5. Problems in the Current Work Control Process Problem Area – Cycle Time is 2.5 days at best – not acceptable for an FMA

  6. Current Go Forward Plan • Make C305 more Robust • Increase military and civilian manning • Hire core civilians • Co-locate in trailers by drydock with project teams • Standardize WAFs to eventually eliminate Shop Reviews (currently 10% done) • Transition to Electronic WAF/WP

  7. Current C305Project Support Team

  8. Limitations with Current Go Forward Plan • Budget Realities and FTE limitations • Enlisted billets difficult to obtain • Poor QOL for sailors in C305 • Process would still be lacking • No Cell Concept/Lack of Flow • NOT HIGHLY LEANED

  9. RO appropriately sent back to drawing board!

  10. New Concept of Operations Developed • Goals: • Streamline Process • Accelerate Work Authorization to the shops • Minimize Shop Supervision time reviewing WAFs • Maintain and Build on Current Best Practices • Prevent Further Degradation of Trade Work Force (minimize FTEs) • Break Down Department Barriers • Develop Strong Project Management/Schedule Link to Planning Products

  11. Proposed Concept

  12. Benefits C420 has invested significant time in a particular AWR – generating the WAF from the AWR is minor (5 minutes) Consistent with other FMAs LEAN • Embedded Element Tasked to: • Assist in WAF Development • Tie Project Schedules to Planning Products • Complete Master WAF DB • Maintain CIM Database • Continue Master/Bundled WAFs • Conduct LWC/AWC reviews • Expand Proj Mgmt Concepts Other Benefits – Reduces Pressure on C305 manning, Probably no need for Trailer City (further thought required), Doubles TOT presence on ships, Improved QOL

  13. C305 Embedded Element Embedded Element Staffing: 3 SMEs acting in Proj Sup Like Capacity 1 LCPO 2 MMs 2 FT/ET 2 additional personnel Qualified and Designated to: Sign for LWC/AWC concurrence Authority based on experience/quals

  14. What I need • Re-direct current plans for LEAN in C305 • Efforts should focus on Flow/Layout: • C420 + C305 WP Element Area • C305 TOT Area • This will have a cost associated with it • Use trailer money! • No New Billets • Fast Implementation (needs to be fully functioning in December to support new year workload)

More Related