Reviewer Comments 6. Integrated Schedule C/S/A Yes No (if N/A state here) Are the planned significant program activities, C major logistics/sustainment events and major activation activities for sites identified in the program IMS (e.g., provisioning activities, depot activation, technical data/order development, etc.)? Are significant tasks required to resolve product S support issues identified in 9.4 (for either red or yellow assessments) captured in the Product Support Schedule (Figure 6-1)? Are there additional schedule details and/or task S level implementation plans for the individual product support elements included as an annex to this LCSP? S Are product support strategy events synchronized to support acquisition events and to influence decision points? Reviewer Comments 7. Cost and Funding C/S/A Yes No (if N/A state here) Does the LCSP state that information contained in S the LCSP aligns with official program documents (e.g. SAR, PB, or POM), briefings, reports, etc. at whatever point in time the LCSP is being written/updated? Is planned lifecycle product support costs adequate to support LCSP stated strategy? Does the LCSP identify the source of the S information used to include who provided the data and the date and title of the source document(s) to ensure traceability of the information? If a legacy system exists, was historical actual S costs obtained from an official data source (e.g. AFTOC, ABIDES, the legacy system program office, etc.) and was the historical legacy system actual costs/data included the point in time “as of” when the LCSP is first written? Legacy system data should remain static from the first drafting of the initial LCSP so as not to have a “moving target”.
6. Integrated Schedule C/S/A Yes No Reviewer Comments (if N/A state here) Are the planned significant program activities, major logistics/sustainment events and major activation activities for sites identified in the program IMS (e.g., provisioning activities, depot activation, technical data/order development, etc.)? C Are significant tasks required to resolve product support issues identified in 9.4 (for either red or yellow assessments) captured in the Product Support Schedule (Figure 6-1)? S Are there additional schedule details and/or task level implementation plans for the individual product support elements included as an annex to this LCSP? S Are product support strategy events synchronized to support acquisition events and to influence decision points? S 7. Cost and Funding C/S/A Yes No Reviewer Comments (if N/A state here) Does the LCSP state that information contained in the LCSP aligns with official program documents (e.g. SAR, PB, or POM), briefings, reports, etc. at whatever point in time the LCSP is being written/updated? Is planned lifecycle product support costs adequate to support LCSP stated strategy? S Does the LCSP identify the source of the information used to include who provided the data and the date and title of the source document(s) to ensure traceability of the information? S If a legacy system exists, was historical actual costs obtained from an official data source (e.g. AFTOC, ABIDES, the legacy system program office, etc.) and was the historical legacy system actual costs/data included “as of” the point in time when the LCSP is first written? Legacy system data should remain static from the first drafting of the initial LCSP so as not to have a “moving target”. S