Integrate the Wing IG Combine aspects of steps: The previous 4 steps were ongoing previous 4 with 23-26. listed independently for "inspection support of clarity. In practice, as 6.5 steps" WIT CCIP matures, some of these steps may be blended/combined. Produce an Wing IG Review discrepancies from The command chain is 1-2 days inspection report and WIT all IG staff and WIT responsible for fixing members. Adjudicate deficiencies. IG staff different viewpoints, assign should not be tasked to OPRs. Draft Report. Publish conduct root cause 7.1 report. analysis. The IG report should be treated as if it were a MAJCOM-level report. Enter IG Wing IG Using the data collected It will take several Approx. 3 deficiencies into during inspections, load iterations before Wing IG inspections IGEMS report and significant/critical members become deficiencies into IGEMS proficient in IGEMS. Use 7.2 the help option to gain better user knowledge. Use IGEMS to track and close deficiencies. Develop and Wing IG Incorporate key Wing Make information on the 2 weeks manage a CCIP performance matrix and CCIP dashboard useful to dashboard for the MICT data, providing real Wing CC. Consider 7.3 Wing CC data to the Commander classification and Wing in the format of his/her Commander's preferences. choosing. Form the CIMB Wing IG Create wing-level briefing to Potential topics include: 2 Weeks to (Commander's inform wing leadership on Overview of open prepare, Inspection the status of the Wing deficiencies, top concerns 2 hour brief Management Inspection Program, (i.e.. of each Group/CC, trends Board) pull applicable reports from in MICT, trends seen MICT, sort open deficiencies during unit inspections, to identify trends and Gatekeeper calendar, and 8.1 deficiencies requiring upcoming Wing external coordination inspections. support, functional coordination, FAM, etc.). Also, a thorough review of internal and external inspections will provide background for discussion.
6.5 Integrate the previous 4 "inspection steps" Wing IG with support of WIT Combine aspects of steps: 23-26. The previous 4 steps were listed independently for clarity. In practice, as CCIP matures, some of these steps may be blended/combined. ongoing 7.1 Produce an inspection report Wing IG and WIT Review discrepancies from all IG staff and WIT members. Adjudicate different viewpoints, assign OPRs. Draft Report. Publish report. The command chain is responsible for fixing deficiencies. IG staff should not be tasked to conduct root cause analysis. The IG report should be treated as if it were a MAJCOM-level report. 1-2 days 7.2 Enter IG deficiencies into IGEMS Wing IG Using the data collected during inspections, load report and significant/critical deficiencies into IGEMS It will take several iterations before Wing IG members become proficient in IGEMS. Use the help option to gain better user knowledge. Use IGEMS to track and close deficiencies. Approx. 3 inspections 7.3 Develop and manage a CCIP dashboard for the Wing CC Wing IG Incorporate key Wing performance matrix and MICT data, providing real data to the Commander in the format of his/her choosing. Make information on the CCIP dashboard useful to Wing CC. Consider classification and Wing Commander's preferences. 2 weeks 8.1 Form the CIMB (Commander's Inspection Management Board) Wing IG Create wing-level briefing to inform wing leadership on the status of the Wing Inspection Program, (i.e.. pull applicable reports from MICT, sort open deficiencies to identify trends and deficiencies requiring external coordination support, functional coordination, FAM, etc.). Also, a thorough review of internal and external inspections will provide background for discussion. Potential topics include: Overview of open deficiencies, top concerns of each Group/CC, trends in MICT, trends seen during unit inspections, Gatekeeper calendar, and upcoming Wing inspections. 2 Weeks to prepare, 2 hour brief
Tab%206%20CCIP%20Capability%20Action%20Plan%20v4.docx