If the scope of the LCSP includes multiple ACAT S programs, are modification programs which have their own ACAT designation separately identified and tracked in this section? Figure 7-1 (Evolution of the O&S Cost Estimate S for the system): Is the sources and as of date for the clearly stated and “Legacy System” value a general support description of the legacy system to include total inventory of legacy system, age of legacy system, average annual flying hours of legacy system, type(s) of legacy support (e.g., total CLS, total organic, specifics on any partnering arrangements, etc.) included? If applicable, have any caveats to the current system cost data been annotated? (Note: Caveats may include, but not limited to: when system steady state will be reached, reliability maturity attained, any support goals are envisioned to be met, etc.) Are the program events listed consistent with the current phase of the program? (Note: Column titles (i.e.: CDD, MS A, MS B, APB, etc.) are given as examples. It is expected that these columns should be added to reflect any major changes in the product support strategy that affect the O&S Cost Estimate or at a minimum the O&S Estimate at the time of any major program milestones.) Section 7.1.3 (O&S and Disposal Cost Drivers): S Has the program identified major cost drivers to include understanding what causing the cost driver and if/how cost drivers could be changed to reduce O&S costs? Section 7.2 for programs with a documented S – affordability goal, does the LCSP state the affordability goal to include where it is officially stablished (i.e.: SAR report, ADM, etc.)? (Note: If no affordability goals established, is it stated in this section of the LCS with supporting rationale as to why?)
If the scope of the LCSP includes multiple ACAT programs, are modification programs which have their own ACAT designation separately identified and tracked in this section? S Figure 7-1 (Evolution of the O&S Cost Estimate for the system): Is the sources and as of date for the “Legacy System” value clearly stated and a general support description of the legacy system to include total inventory of legacy system, age of legacy system, average annual flying hours of legacy system, type(s) of legacy support (e.g., total CLS, total organic, specifics on any partnering arrangements, etc.) included? If applicable, have any caveats to the current system cost data been annotated? (Note: Caveats may include, but not limited to: when system steady state will be reached, reliability maturity attained, any support goals are envisioned to be met, etc.) Are the program events listed consistent with the current phase of the program? (Note: Column titles (i.e.: CDD, MS A, MS B, APB, etc.) are given as examples. It is expected that these columns should be added to reflect any major changes in the product support strategy that affect the O&S Cost Estimate or at a minimum the O&S Estimate at the time of any major program milestones.) S Section 7.1.3 (O&S and Disposal Cost Drivers): Has the program identified major cost drivers to include understanding what causing the cost driver and if/how cost drivers could be changed to reduce O&S costs? S Section 7.2 – for programs with a documented affordability goal, does the LCSP state the affordability goal to include where it is officially stablished (i.e.: SAR report, ADM, etc.)? (Note: If no affordability goals established, is it stated in this section of the LCS with supporting rationale as to why?) S