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
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
Maintenance Planning & Product Support Management Assessment Criteria Program Office Requirement Guidance C/S/A Yes No Reviewer Comments (if N/A state here) Does the LCSP-defined maintenance concept indicate a relationship to the CONOPS/ICD/CDD/ CPD in order to support the maintenance concept chosen? Has the user defined the maintenance concept (e.g., level of maintenance, techniques, skills, tools, operational constraints, Human Systems Integration (HSI), etc.) as documented in the CONOPS/ICD/CDD/ CPD and is the information used as the basis for the initial maintenance planning activity and documented in the Life Cycle Sustainment Plan/Lifecycle Management Plan (LCSP/LCMP) (LCMP allowed with MDA approval)? DoDD 4151.18 para. 3.1; IPS Element Guidebook; AFI 33-200 2.14.10; AFI 63-101/20-101 chap 7.13; DoDI 5000.02 Enclosure 6 C Does the LCSP document how Product Support Analysis was used to develop the maintenance plan/concept? Is Product Support Analysis used to develop and optimize maintenance planning requirements for effective, suitable, and affordable maintenance and is it documented in the LCSP/LCMP? MIL HDBK 502A; AFPAM 63-128 chap 10; AFMAN 63-119; BBP 3.0 C Do the selected KPPs and KSAs support achieving the program's maintenance requirements? Review ICD to identify maintenance requirements and support KPPs and KSAs. DoDD 4151.18 para. 3.1; IPS Element Guidebook; AFI 33-200 2.14.10; AFI 63-101/20-101 chap 6; DoDI 5000.02 Enclosure 6 S
Does the LCSP defined the maintenance concept to include the relationship with how the maintenance alternatives (AoAs) were evaluated (in order to support concept chosen)? (Note: Not mandatory for inclusion in the LCSP; however, will evaluate if included) Develop preliminary Maintenance Planning and Management Concept: Conduct a maintenance AoA for each design alternative. Analyze new and historical technological solutions. Support PSM market research/trade studies activities. S Does the LCSP include verbiage to document how support planning and system-level analyses were utilized to select maintenance functions? Support planning for and conduct of system-level analyses (e.g., Tradeoff analysis and Functional analysis to identify operation and maintenance functions). S Does the LCSP include evidence that 10 USC areas are addressed (Core, SORA, DSOR and 50/50)? If it does, are these in compliance with required timelines (Core Analysis by MS-A, DSOR Decision by MS-B, Core Requirement determination by MS-B)? Note: LZSA will provide impact to 50/50 posture if DLM cost information is provided (for contract DSORs). Is the DSOR process on schedule or completed (e.g., Core Analysis, Candidate Depot Determination, and Depot Maintenance Inter-service (DMI))? Are maintenance planning and analyses consistent with statutory and regulatory requirements (Title 10 USC 2464 (CORE), Title 10 USC 2460 (Definition of Depot Maintenance), 2466 (50/50 limit on contracted maintenance), and 2474 (encouraging public/private partnerships through 50/50 CITE exemption))? AFI para 7.13; Title 10 USC 2460, 2464, 2466, 2366a&b, DoD 5000.2 and DoDD 4151.18 C
Does the LCSP indicate how supportability of maintenance concepts and levels are established? (Note: Not mandatory for inclusion in the LCSP; however, will evaluate if included) Accessibility, Human Factors Engineering (HFE), diagnostics, repair, and sparing concepts for all maintenance levels are established. DoDD 4151.18, S Is the program executing the DSOR Decision? Or is there an approved WAD or workload shift DSOR? DSOR Decision Compliance: Is the program executing the DSOR Decision? Has depot activation planning been started? AFI para. 7.13 C Is Depot Maintenance Activation included in the LCSP with language consistent with the current life cycle stage (Initial Plan, DMAWG establishment, Charter, DMAP, and Integrated Master Schedule)? Is the depot activation funding identified in the lifecycle cost estimate and approved in the Program Objective Memorandum (POM) to support the Depot Maintenance Activation Plan (DMAP) requirement? AFI 65-601 Vol 1; AFMCI 21-101 1.2, 1.3 S Captured in previous DA assessment criteria – additional explanation of requirement. Is there an approved Depot Maintenance Activation Working Group (DMAWG) charter? AFMCI 21-101 para 1.1, 1.2, 1.3 S Captured in previous DA assessment criteria – additional explanation of requirement. Has the Depot Maintenance Activation Plan (DMAP) been signed and submitted to AFMC/A4? AFMCI AFI S
Captured in previous LORA assessment criteria - additional explanation of requirement. (Note: Not mandatory for inclusion in the LCSP; however, will evaluate if included) A LORA has been conducted using resource and frequency data developed from maintenance task analysis performed using RCM analysis data to determine lifecycle maintenance of depot repair tasks. Retain the LORA to support depot activation budgets and SORA. SAE AS 1390, S Does LCSP indicate how the maintenance concept/strategy uses Condition Based Maintenance (CBM/CBM+) strategy/ concepts to include how the program will acquire and manage necessary data to populate the supply and maintenance systems that support CBM+ concept? CBM or CBM+ strategy is used to determine maintenance decisions to reduce scheduled maintenance and manpower requirements, while reducing operation and sustainment costs and ensuring the appropriate maintenance is performed and detailed enough to be implemented. AFI para. 5.4.20.5 S Attachment B: Supply Support Supplemental Checklist
Provisioning: Is a provisioning plan in place using Air Force RBS models (to meet program availability/sustainment requirements)?? Have programs planned to provision items, catalog, and procure initial spares? If transitioning to organic, is full provisioning planned? If CSWS, will common parts be provisioned at a minimum? DoD 4140.01,v2, AFI AFMCI 23-101 C Provisioning: Does the provisioning plan fit in with overall strategy? Ensure the provisioning plan makes sense with the overall sustainment strategy (e.g., organic, CLS, CSWS, etc.). Does it lead to the purchase of initial spares? Will strategy support program’s KPPS/KSAs? AFI para 7.18 S GFP: Has GFP been attached to the contract using the DoD Fillable Form? DoD form is the only contractual authorization for a contractor to possess GFP. PGI C GFP: Are mandatory clauses included in the contract for GFP? Mandatory DFAR clauses must be included in all cost and T&M contracts and any contract with GFP. DFARS 211.274-6 C GFP: If the contractor will manage and possess Government-owned spares, is a CFO reporting requirement included? Until the APSR is stood up, contractors must report transactions on this material for the AF financial statements. CFO Act C Industrial Base: Does the LCSP address industrial base constraints (e.g., raw materials, source materials, DMSMS, counterfeit parts, supply chain risk management identified constraints/risks, etc.) faced by the program? The LCSP should address mitigation of industrial base constraints to ensure that the system(s) can be supported, upgraded, and updated during its life cycle to AFI para 4.27 C
IUID (Post Milestone C only): Does the LCSP include an annex with the program’s approved IUID Implementation Plan? Ensure IUID requirements are integrated into integrated product support. AFI para 4.25 and para 7.7.5. C Demilitarization/Disposal: Does the LCSP document demilitarization, disposal and reclamation support requirements for the program NLT Milestone C? LCSP should forecast funding well enough in advance to support execution of these activities throughout each weapon system’s life cycle. AFI para 7.20.2 C Unique Tooling (MDAP only): Does the LCSP include an annex with the program’s Preservation and Storage of Unique Tooling Plan? (For MDAP Program’s Only) Plan should include the identification of any contract clauses, facilities, and funding required for the preservation and storage of such tooling and shall describe how unique tooling retention will continue to be reviewed during the life of the program. AFI para 7.7.5 C Attachment C: PHS&T Supplemental Checklist
Is there information in the LCSP on new and modified items being procured (via DI-PACK-80120 and Provide documentation within the LCSP that satisfy the assessment criteria. AFMCI HQ AFMC Packaging and Materials Handling Policies and Procedures S Does the LCSP contain information on unit, intermediate, and shipping containers being marked IAW MIL-STD-129? Provide documentation within the LCSP that satisfy the assessment criteria. AFMCI HQ AFMC Packaging and Materials Handling Policies and Procedures; Military Marking for Shipment and Storage C Does the LCSP contain information about items requiring special storage requirements (e.g., freezers for storage of composites, HAZMAT, and shelf life items and/or nuclear)? Provide documentation within the LCSP that satisfy the assessment criteria. AFMAN Preparing Hazardous Material for Military Air Shipments S Does LCSP contain PHS&T requirements associated with hazardous materials and/or wastes? Provide documentation within the LCSP that satisfy the assessment criteria. AFMAN Preparing Hazardous Material for Military Air Shipments S Attachment D: Technical Data Supplemental Checklist
Technical Data Assessment Criteria Program Office Requirement Guidance C/S/A Yes No Reviewer Comments (if N/A state here) Has Table 3-1 been completed with a description of plans for the acquisition of technical data rights? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C Has Figure 7.1 in section 5.2 been completed to show the health of technical data and does all other documentation regarding technical data support the color chosen? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C Does the LCSP include a Technical Data/Data Management Strategy with subjects such as discussion of specific data items required to be managed throughout the program's life cycle; design, manufacture, and sustain the system; re-compete for production, sustainment or upgrade; program's approach to managing the data during acquisition and sustainment (e.g., access, delivery, format); contracting strategy for technical data and intellectual property rights; requirements/need for a priced option/source selection criteria; discussion of any unique circumstances; etc.? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C Have product and software data requirements been documented and has funding been identified to acquire and maintain needed data? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C
Has a BCA been conducted to assess the cost and merit for purchasing Technical Data, as well as the amount of Technical Data to purchase across the lifecycle of the program (e.g., unlimited, Government Purpose, etc.)? If so, what were the findings? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C What Technical Data has been ordered using contract statements of work, Contract Data Requirement Lists (CDRLs), Data Item Descriptions (DIDs), and appropriate contract clauses? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C Has a review been completed to ensure that data requirements are addressed completely and consistently in all appropriate sections of the RFP (e.g., Sections B, C, H, I, J, K, L, and M) to communicate internal consistency and to eliminate inadvertent omissions? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C What are the program’s method(s) for delivery of the types of technical data? Provide documentation within the LCSP that satisfy the assessment criteria. DoD DFARS Subpart 227.7103.2, AFI 61-202, TO 00-5-3, and LCSP Outline C
Has the program completed a TOLCVP and attached it to the LCSP? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline; TO-00-5-3 C Has the program completed a TO Milestone Schedule, which includes IPRs, Val/Ver, and deliveries? Provide documentation within the LCSP that satisfy the assessment criteria. LCSP Outline C Has the program documented an initial acquisition concept and determined the preliminary engineering/products support data needed? Provide documentation within the TOLCMP and/or TOLCVP. TOLCMP Outline C Is there a documented process for processing recommended changes? Provide documentation within the TOLCMP and/or TOLCVP. TO-00-5-3 C Has the program documented how users will submit changes to technical data? Provide documentation within the TOLCMP and/or TOLCVP. TO-00-5-3 C Has the program determined what format the tech data will be delivered in (e.g., S1000D, SGML, XML, etc.)? (Note: If using IETM, AF standard is S1000D.) Provide documentation within the TOLCMP and/or TOLCVP. TO 00-5-3; TOLCMP Outline C Has the program provided a TO concept of operations? Provide documentation within the TOLCMP and/or TOLCVP. TO 00-5-3; TOLCMP Outline S If the program is using S1000D, has it planned for a Common Source Data Base (CSDB)? Provide documentation within the TOLCMP and/or TOLCVP. TO-00-5-3 S If the program is using S1000D, is the strategy, structure, and format in compliance with AF policy and procedures? Provide documentation within the TOLCMP and/or TOLCVP. TO-00-5-3 S Has the program identified any waivers to TO policy and procedures? Provide documentation within the TOLCMP and/or TOLCVP. TO-00-5-3 2
Attachment E: Support Equipment Supplemental Checklist Support Equipment Assessment Criteria Program Office Requirement Guidance C/S/A Yes No Reviewer Comments (if N/A state here) Does the LCSP link the program's Support Equipment strategy to the system's maintenance concept? SERDs will be submitted for O- and D-levels of maintenance. The LCSP should reflect that the program has thought through the process for SERDs and Support Equipment management for O- and D-levels. C Is the program planning for and acquiring SE/ATS, which is, to the maximum extent possible, common and interoperable with other services and across multiple systems and munitions? LCSP should include a statement that the program has considered common SE and ATS within their requirements development and fielding AFI para 7.17.1 C Does the LCSP show the program obtaining SE/ATS Product Group SERD approval prior to procurement of peculiar SE/ATS? Does the LCSP include the system submitting waivers to the SE and ATS Product Groups prior to the approval of peculiar SE over recommended common SE? SERDs must be routed through the Product Groups for review for commonality with other systems. If a weapon system chooses to use a piece of peculiar SE over a recommended piece of common, they must submit a waiver to the product group and have its approval before proceeding with the approval and acquisition of the piece of equipment. AFI para 7.17.2.6 S Does the LCSP show the program utilizing the AF/AFLCMC Support Equipment Recommendation Data (SERD) Process? The PM must use the SERD Process to evaluate SE. AFI para 7.17.2.5, AFMCMAN C
Does the program have a DMSMS plan for Support Equipment? As SE becomes obsolete, has the program considered its SE within its DMSMS plan? S Have all FIAR requirements been met for GFE? Has the program ensured all SE related GFE is loaded in the appropriate IT systems of record for management of FIAR compliance? To loan equipment items, program offices must receive approval for the loan request and have an appropriately documented contract (clauses, SOW language, GFP attachment), FAR 52.245-1 DFARS 252.211-7007 Standard Process: Accountability of GFE C Area all SE/ATS listed in system of record (AFEMS)? The program office is accountable for all purchased/acquired items until it is delivered to the gaining unit and added to the unit’s Accountable Property System of Record (APSR). AFI 23-101 C Is an annual inventory conducted to ensure FIAR compliance? Perform annual inventory of Government Furnished Equipment (GFE) on loan to the contractor. Standard Process: Accountability of GFE C Has the PM identify what IT system will be used to manage and track common and peculiar support equipment? LCSP Sample Outline S Has PM identified how common and peculiar Support Equipment will be managed and tracked throughout the lifecycle of the program? LCSP Sample Outline Attachment F: CRS Supplemental Checklist
Computer Resource Support Assessment Criteria Program Office Requirement Guidance C/S/A Yes No Reviewer Comments (if N/A state here) For Platform IT (PIT) and Automated Information Systems (AISs): Who will be/is the software/ system support activity in the Operations and Support phase? Are all applicable agreements completed with supporting activities completed? Pre-milestone B, identify organizations supporting hardware/software sustainment and agreements in place to provide support. In the LCSP, recommend noting compliance with DoDI 5000.75 and/or DoDI 5000.02 with regard to supporting organizations and agreements. DoD PSM Guidebook DoDI 5000.02 section 6 DoDI 5000.75 Section 4 S For PIT and AISs: Has a process for obsolescence management been established (e.g. planning for technical refresh)? Pre-milestone B, document strategy for maintaining supportable hardware and identify technical refresh or upgrade intervals. In the LCSP, recommend noting considerations for obsolescence management. DoD PSM Guidebook USAF Weapon Systems Software Management Guidebook DAU Integrated Product Support Element Guidebook S
For PIT and AISs: Have considerations for using Open System Architecture (OSA) been identified? Pre-milestone A, identify OSA objectives included in the acquisition strategy and clarified throughout the acquisition process into sustainment. Pre-O&S: Identify that IT OSA objectives are outlined in acquisition documentation. In the LCSP, recommend noting considerations for OSA. DoDI 5000.02 Enclosure 3 AFLCMC OSA Standard Process Guide S For PIT and AIS: What support software (e.g. test software) is required? Have provisions been made to establish any required System Integration Labs (SILs)? Post-milestone B, identify computer resources required to test/support system software and/or other product support processes. Identify support strategy for those supporting resources if owned by the program. In the LCSP, recommend noting compliance with DoDI 5000.02, regarding test software and other supporting software. Address funding for SIL and data needed for transition to organic software support. DoD PSM Guidebook Integrated Product Support Element Guidebook DoDI 5000.02 Enclosures 4 S
For AISs: What is the hosting strategy? Is the hosting strategy in line with the Air Force hosting strategies? Has Continuity of Operation (COOP) requirements been considered? Pre-milestone C, outline COOP strategy in the case of emergencies. In the LCSP, recommend noting compliance with AFI 10-208. Pre-milestone B, the system hosting strategy has been outlined and considers Air Force hosting strategies IAW AFI 63-101. In the LCSP, recommend noting compliance with DoDI 5000.75, DoDI 5000.02, AFI 63-101, and AFI 10-208, with regard to hosting and infrastructure strategy. DoD PSM Guidebook DoDI 5000.02 enclosure 5 AFI10-208 Air Force Continuity of Operations (COOP) Program appendix A, paragraph A6.2.2. DoDI 5000.75 appendix 4D AFI 63-101 chapter 8, table 8.1 S
For AISs: Are all requirements to connect to the Air Force network, to include cybersecurity requirements, complete? Pre-milestone C, outline approach for ensuring key cybersecurity / IA compliances are met IAW AFI17-130 Air Force Cybersecurity Program Management and AFI 17-101 Risk Management Framework for Air Force Information Technology In the LCSP, recommend noting compliance with DoDI 5000.02, DoDI 5000.75, AFI17-130, and AFI17-101. DoD PSM Guidebook DoDI 5000.02 Enclosure 14 DoDI 5000.75 Appendix 4A, Table 4 AFI 17-101 Risk Management Framework for Air Force Information Technology AFI17-130 Air Force Cybersecurity Program Management S For AISs: Have architectural and specification documents been delivered, and maintained for accuracy? Pre-milestone A, Architectural Documentation Supporting the Clinger-cohen Act, Organizational Execution Process and the Development and Delivery Process (specifically supporting Modernization) are Complete and up to date (also required in the ISP). In the LCSP, recommend noting compliance with DoDI 5000.02, DoDI 5000.75, and AFMAN DoD PSM Guidebook DoDI 5000.75 Section 4 DoDI 5000.75 appendix 4A DoDI 5000.02 enclosure 1, Table 2 DoDI 8330.01; Interoperability of IT, Including NSS AFMAN 63-144 chapter 3 S