draft_1.C-LGIP_PWS_20201117.pdf

DRAFT

FA820321R0002

17 November 2020

C-LGIP PWS

PERFORMANCE WORK STATEMENT

FOR

COMPREHENSIVE-LANDING GEAR INTEGRITY PROGRAM

1.0 PURPOSE

1.1 This Performance Work Statement (PWS) provides the Government’s key major program objectives and contract deliverables, in general terms, for the Comprehensive-Landing Gear Integrity Program (C-LGIP) indefinite-delivery indefinite-quantity (IDIQ) contract.

It is not intended to be an all-inclusive list of required engineering services and shall not limit the Contractor in addressing those areas the Contractor foresees as being crucial to the success of the program.

2.0 BACKGROUND

2.1 The Air Force Landing Gear Systems Engineering Office has worked a number of integrity programs on a limited number of weapon systems with limited scope in the past.

In 2017, the C-5 fleet was grounded due to age-based failures. These failures highlighted the need for a comprehensive landing gear integrity program across all United States Air Force (USAF) managed weapon systems. The deliverables of the C-LGIP will enable 417 SCMS to proactively manage both the safety and the supportability risks associated with all USAF landing gear systems within the 417 SCMS Chief Engineer’s authority.

3.0 SCOPE

3.1 The scope of the C-LGIP is to establish tools and technical data necessary to ensure integrity throughout each landing gear system’s remaining operational service life and to ensure appropriate supply chain measures are being taken to provide optimal service to the using commands. The C-LGIP IDIQ contract will develop and execute objectives for all of the landing gear systems under the delegated engineering authority held by the 417 SCMS Chief Engineer.

3.2 Landing gear integrity programs must utilize AFI63-101/20-101 Integrated Life Cycle Management, MIL-STD-1530 Aircraft Structural Integrity Program (ASIP), and MIL- STD-1798 Mechanical Equipment and Subsystems Integrity Program (MECSIP). Air Force ASIP and MECSIP requirements specify that structural and functional integrity shall be maintained for the life of the aircraft to ensure Operational Safety, Suitability, and Effectiveness (OSS&E) of the weapon system. This requires that the design service life and service history for all landing gear parts be known and monitored. However, these criteria have not been efficiently tracked and monitored. Aircraft operational loads and fatigue spectrum have shifted over time, and the remaining service life of landing gear parts needs to be analyzed. Additionally, the service history and condition of all landing gear parts need to be understood, to enable the supply chain to take proactive steps to ensure uninterrupted spares supportability by the 417 SCMS.

3.3 The C-LGIP scope does not include advisory and assistance services, management or professional support, policy development, or engineering services for parts over which the 417 SCMS Chief Engineer does not hold authority.

3.4 A list of C-LGIP example objectives is provided in Section 4. This list is intended to help inform the Contractor of potential types of engineering services that may be on a task order. Specific requirements will be identified at the task order level and all associated program management activities to accomplish the services are required. This list is meant to provide potential offerors with a better idea of the types of work to be accomplished on this contract. It is not comprehensive and should not be interpreted as limiting the scope of the C-LGIP to only the identified objectives.

4.0 EXAMPLE OBJECTIVES

4.1 Landing Gear Integrity Program Recommended Practices

The Contractor shall develop a document, which maintains an open architecture that defines USAF enterprise LGIP practices and methodologies. Inputs to the document will come from technical deliverables of past LGIPs as well as lessons learned as they are encountered and/or developed in the course of executing C-LGIP. The intent of this living document is to capture best practices over the course of the contract and set the standard for executing USAF Landing Gear Integrity Programs.

4.2 Integration of C-LGIP Data into Siemens Teamcenter

The Contractor shall organize, provision, and configure Teamcenter so complete Engineering Bill of Materials (E-BOMs) are available for each weapon system.

Furthermore, all deliverables derived from the C-LGIP effort will be delivered to USAF via Teamcenter under the appropriate E-BOM object. Finally, the Contractor will be responsible for integration of existing USAF engineering data (CAD files, mishap reports, engineering and technical reports, stress analysis, FEA models, pictures, etc.)

into Teamcenter.

4.3 Probabilistic Age Assessment

The Contractor shall perform a probabilistic age analysis of all landing gear, under 417 SCMS Chief Engineer authority, currently in service or in supply. The Contractor shall develop a plan to address cases where parts have complete, partial, or no procurement history.

4.4 Landing Gear Modeling

The Contractor shall develop verified 3D solid models for all landing gear assemblies and their associated components under 417 SCMS Chief Engineer authority.

4.5 Landing Gear Structural Analysis

The Contractor shall verify original equipment manufacture’s (OEM) structural analysis using Finite Element Analysis. The Contractor shall convert static stress manual into electronic format.

4.6 Safe-Life Risk Assessment using OEM Spectra

The Contractor shall establish remaining safe-life for landing gear by determining probability for fatigue failure of structural assemblies and their associated components based on OEM.

4.7 Fatigue Spectrum Determination

The Contractor shall plan, coordinate, and execute on-aircraft load survey activities (including identification of target aircraft and instrumentation requirements), as well as collect and analyze fleet usage spectrum data.

4.8 Design Life Risk Assessment using Operational Spectra

The Contractor shall establish remaining service life for landing gear components by determining probability for failure of structural and functionally critical assemblies and their associated components based on operational spectra gathered during the fatigue spectrum determination task. The analysis shall include safe-life, redundancy, inherently improbable, leak-before-burst, or any other design methodology applicable to the component design. The Contractor shall confirm the methodology used when the component was designed (e.g. safe-life, redundancy, fail-safety, remaining cycles, or other applicable life assessment), and determine whether that is best methodology for evaluating the parts remaining life. Additionally, a second safe-life risk assessment must be conducted against safety-critical parts at Least Material Condition (LMC)

4.9 Analytical Condition Inspection (ACI)

The Contractor shall develop and execute a plan in accordance with AFMCI 21-102, Analytical Condition Inspection Programs, to determine the condition of landing gear assemblies and their associated components in service.

4.10 Brake Control System Reliability, Availability and Maintainability (RAM) Analysis

The Contractor shall conduct a RAM analysis of the brake control system for both legacy and redesigned assemblies and their associated components that are currently in service by inspection, evaluation and tracking of parts. RAM analysis shall include functional testing as deemed necessary to validate design configuration.

4.11 RAM Analysis

The Contractor shall conduct a RAM analysis of all landing gear parts under 417 SCMS Chief Engineer authority that are currently in service by inspection and evaluation of parts and maintenance records.

4.12 LGIP Recommendations and Implementation Plan

The Contractor shall provide supply chain and engineering recommendations based on the inputs from all other tasks to improve the integrity and RAM of landing gear systems.

These recommendations shall include implementation plans for a proactive supply chain to improve asset availability. Types of questions that may be answered are: What should be done to prevent potential safety issues (driven by fatigue, corrosion, wear, etc.)? What should be done to improve supportability (ensuring parts are available on time, in the appropriate quantities)? What should be done to improve the economics of the landing gear supply chain? The Contractor shall provide a landing gear systems master plan to be integrated with the respective System Program Office master plan.

4.13 Integrity Monitoring

The Contractor shall perform follow-on integrity monitoring of landing gear systems that have previously had integrity tasks completed. Active monitoring is required to ensure integrity is maintained after initial analysis. Monitoring may include activities such as periodic ACIs and RAMs, re-baselining probabilistic age assessments, re-baselining fleet spectrum data, integration with CBM+ efforts, etc.

4.14 Reverse Engineering for Weapon Systems with Proprietary Engineering Data

The Contractor shall perform reverse engineering efforts to create Air Force-owned landing gear engineering data when little or no engineering data is available. Types of efforts in a reverse engineering requirement may include; development of 3D models/drawings, loads gathering activities, fatigue spectrum determinations, static stress analyses, design service life and safe-life evaluations, etc. Reverse engineering efforts are not expected on components that are traditionally proprietary on all weapon systems (e.g.

wheels, brakes, antiskid, etc.).

5.0 PERIOD AND PLACE OF PERFORMANCE

5.1 The contract ordering period is anticipated to be 19 years with a period of performance (PoP) of 20 years. Individual task orders may take from one to eight years. It is anticipated that the Government may work four to five task orders concurrently.

5.2 The majority of the work will take place at the Contractor’s facility. Other places of performance may include aircraft PDM lines at various Air Force bases, Landing Gear Overhaul Depot at multiple locations, and various Active Duty, National Guard, and/or Reserve Base locations.

6.0 GOVERNMENT FURNISHED PROPERTY

6.1 Government furnished property (GFP) may be provided for specific task orders to facilitate contract performance. If GFP is identified and utilized on a task order, the Contractor must conform to the provisions of AFI 31-101 for safeguarding the GFP.

6.2 Control of GFP will be accomplished IAW FAR Part 45 and through the incorporation of supply information in the individual task order. There is no GFP at the basic contract level. All GFP, if required, will be provided at the task order level with post-award monitoring accomplished by the assigned administrative office.

6.3 The Air Force may provide the Contractor access to electronic systems and data subject to compliance with applicable statues and regulations. Representative systems include:

JEDMICS, D200, D035, D043, e-mail, AF Form 202, LAN, and REMIS. If access is provided, the Contractor shall agree to and comply with the applicable system restrictions (non-disclosure agreements, security clearance requirements, etc.).

6.4 The Government will provide the best available historical data for original landing gear loads spectrum and fatigue life calculations. It may be necessary for the Contractor to enter into agreements with the aircraft OEM or landing gear OEM for data usage rights.

6.5 Technical data stamped with Distribution B, and provided by the Government for the purpose of soliciting C-LGIP proposals or execution of C-LGIP task orders, is approved by the 417 SCMS chief engineer to be provided by the Contractor to their sub-contractors. If the data is marked as Export Controlled the Contractor shall confirm their subcontractor holds a current certified DD2345 prior to providing them with the data, and the Contractor shall include a copy of “Notice to Accompany the Dissemination of Export-controlled Technical Data” (Enclosure 5, DoDD 5230.25) with every distribution.

This approval is not applicable to aircraft level technical orders, technical data provided by System Program Offices (SPOs) or other data to which the 417 SCMS landing gear office is not the engineering source authority.

7.0 OPERATING CONSTRAINTS

7.1 The primary operating constraint for the C-LGIP effort is the availability of GFP. It is anticipated a landing gear shipset may not be available at contract award due to pending scheduling arrangements with the Landing Gear Depot production facility. Additionally, unforeseen scheduling issues could arise between the Contractor, aircraft PDM, Active Duty units, and Landing Gear Overhaul Depot which could affect the Contractor’s ability to accomplish SOO tasks.

7.2 It is expected that subcontracting efforts will be completed, funded, and directed by the Contractor.

7.3 Contractor and subcontractor personnel performing services in support of C-LGIP tasks may encounter varying amounts of procurement and engineering data which will need to be protected from inadvertent or deliberate release. The Contractor shall not divulge any information about files, data, processing activities, schedules, user information, or any information which is proprietary to another contractor to anyone who is not authorized to have access to such information. If uncertain what can be released and to whom, the Contractor shall contact the Government Procuring Contracting Officer (PCO) for direction prior to releasing information similar to the types identified above.

7.4 Contractor and subcontractor personnel performing services in support of C-LGIP tasks may lead to actual or potential Organizational Conflicts of Interest (OCIs) as defined in FAR Subpart 9.5. The Contractor shall notify the PCO within 24 hours of becoming aware of an actual or potential OCI, and shall submit a plan to avoid or mitigate the identified OCI to the PCO within seven calendar days. The PCO will unilaterally determine if the Contractor’s plan is acceptable or if the identified OCI cannot be satisfactorily avoided or mitigated. If an OCI cannot be satisfactorily avoided or mitigated, the PCO may affect other remedies as they deem necessary, including potentially prohibiting the Contractor and/or subcontractor from participation in future Government acquisitions which may be affected by the OCI.

7.5 The Contractor shall include the content of paragraphs 7.3 and 7.4 in all subcontracts when the subcontractor may be required to obtain: (1) electronic access to any Federal information systems; or (2) physical access to any Air Force or Department of Defense controlled facilities.

8.0 GENERAL REQUIREMENTS

8.1 The PCO is the only person authorized to obligate the Government and is the only person authorized to make changes to this contract and its supporting documents, to include any subsequent task orders. In the event the Contractor implements any change(s) at the direction of any person other than the PCO, the change(s) will be considered to have been made without authority and any costs and/or liabilities incurred will be solely at the Contractor’s expense.

8.2 In the event of a task order delay or an apparent change in the level of effort, the Contractor cannot bill the Air Force for any expenses outside of those already directly agreed upon in the task order (i.e., no “marching army” costs or increased labor costs can be claimed on a request for equitable adjustment or similar). Any additional expenses contemplated must be negotiated in advance with the PCO and, if the PCO determines such expenses are appropriate, must be incorporated into the contract via contract modification.

8.3 Data rights for each task order will be identified at the order level using a Government Rights in Data (GRID) document which will be added as an attachment to the order. The completed GRID document will satisfy the requirements of, and expand upon, DFARS clauses 252.227-7013, 252.227-7015, 252.227-7017 and 252.227-7028. Each task order will include its own unique GRID attachment. The Government will assume unlimited data rights unless the Contractor, using the GRID document, expresses a claim in their proposal to providing data to the Government with less than unlimited data rights.

For any proposed limitations (if any) on technical data deliverables, and/or rights in technical data, in the Offeror’s proposal (e.g. Restricted Rights, Limited Rights, Specifically Negotiated License Rights) the Contractor shall describe how, even with these limitations in place, the Government will be able to: 1) maintain full and open competition on future contracting actions and 2) allow the government to independently perform tasks associated with the Comprehensive Landing Gear Integrity Program after the contract period is complete.

8.4 Reasonable time must be allowed for Government technical reviews and approvals. The Integrated Master Schedule and SOW must address airworthiness activities for flight tests and allow for Engineering Review Boards.

9.0 SECURITY

9.1 The Contractor shall ensure all Contractor employees obtain identification badges as required. Contractor personnel shall comply with directives pertaining to operation of privately owned vehicles on Hill AFB per AFI 91-207, USAF Traffic Safety Program.

9.2 The Contractor shall comply with all security, force protection, and antiterrorism requirements enforced at each installation.

a) Communications Security

b) All communications with DoD organizations are subject to Communications Security (COMSEC) review.

c) The DoD authorizes the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations.

d) The Government advises the Contractor that at any time they place a call to, or receive a call from, a DoD organization, they are subject to COMSEC procedures.

e) The Contractor assumes the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information.

10.0 ENVIRONMENTAL

10.1 The Contractor shall be knowledgeable of and comply with all applicable Federal, State, and Local laws, regulations, and requirements regarding environmental protection.

10.2 In the event environmental laws and regulations change during the term of this contract, the Contractor shall be required to comply with such laws when they come into effect.

If there is an increase or decrease in cost as a result of the change, the Contractor shall inform the PCO of the change and the PCO will determine if an equitable adjustment is required.

11.0 SUBCONTRACTING

11.1 Subcontracting plan requirements will be accomplished IAW FAR subpart 19.7 (The Small Business Subcontracting Program) and the relevant contract clauses. Submit Individual Subcontract Reports (ISRs) and Summary Subcontract Reports (SSRs) using the Electronic Subcontracting Reporting System at https://www.esrs.gov (eSRS).

11.2 The Contractor shall be responsible for the management of any and all subcontractors performing work in support of contract objectives.

11.3 All C-LGIP contractors shall demonstrate commitment to Small Business Participation.

The Government has set a minimum overall Small Business subcontracting goal (first-tier) of 10% of the total contract amount which the Contractor agrees to achieve. Small Business Participation will be monitored (via CDRL A026 for Small Business concerns or via eSRS for all others) to ensure the Contractor’s Small Business Participation commitments are being met. The requirement to demonstrate commitment to Small Business Participation, which is required from all offerors, is not to be confused with the Small Business Subcontracting Plan.

12.0 QUALITY ASSURANCE (SERVICES SUMMARY)

12.1 The Government will perform quality assurance surveillance and will evaluate the Contractor’s performance in accordance with the Services Summary in Table 1 of the

Appendix. This does not relieve the Contractor of the responsibility for quality control, nor does it limit the Government’s rights under any of the terms of the basic contract.

12.2 The absence of any contract requirement from the Services Summary (since the Air Force may otherwise identify quality criteria) does not detract from its enforceability nor limit the rights or remedies of the Air Force under any other provision of the contract.

12.3 The Contractor shall, on a non-interference basis, allow Government audits to be performed on Contractor maintained files at the PCO’s request.

12.4 Formal contract deficiencies may require corrective action. Discrepancies will be tracked to ensure resolution and to document repeat occurrences. It is the Contractor’s responsibility to marshal resources to address discrepancies and prevent recurrence.

12.5 Annual and end-of-task-order reviews will be accomplished through the Contractor Performance Assessment Reporting System (CPARS). CPARS will be completed per the requirements of FAR Part 42 and within the CPARS system framework:

https://www.cpars.gov/index.htm.

13.0 QUALITY CONTROL

13.1 Quality control is the Contractor’s responsibility. The Contractor shall ensure their processes allow the Government to perform quality assurance as outlined in Section 12.

13.2 The Contractor shall develop, submit, and implement a Quality Control Plan to identify and prevent, or ensure non-recurrence of, defective services (See CDRL A012). The Contractor shall update its Quality Control Plan based on the results of internal quality audits pursuant to task order quality metrics or objectives.

14.0 CONTRACTOR PERSONNEL

14.1 Engineering experience and expertise are required among all of the categories listed in paragraph 14.2. This experience or expertise shall be held either directly, through partnerships, or through subcontractors.

14.2 Experience categories:

a) Landing Gear Mechanical Systems, Structures, and Processes – Integration, concept, design, analysis, manufacture, qualification, airworthiness certification, implementation, and sustainment. Repair and overhaul concepts, process improvement, technology insertion, and manufacturing technology.

b) Rolling Stock and Brake Control System (Wheels, Brakes, Tires, and Antiskid) – Integration, design, qualification, airworthiness certification, implementation, sustainment, Hardware-In-The-Loop simulation, antiskid software, and hydraulic components.

c) Aircraft Structural Integrity Program (ASIP) and Mechanical Equipment and Subsystems Integrity Program (MECSIP) – Implementation and management of ASIP and MECSIP requirements, including: defining structural/mechanical integrity requirements, design life analyses (with consideration to all design methodologies), testing, development of sustainment philosophies, and development/incorporation of ASIP/MECSIP Master Plans. Aircraft instrumentation, calibration, on-aircraft loads gathering, and signal/data processing.

d) Siemens Teamcenter Product Lifecycle Management (PLM) Software – Integration, implementation, requirements identification, fit/gap analysis, business and system use case analysis.

e) Reverse Engineering – Management of successful aerospace reverse engineering projects from conception to implementation.

f) Business/Data – Program management, configuration management, technical data revision, maintenance strategies, feasibility analysis, information systems, and logistics planning/provisioning

14.3 Qualifications for personnel labor categories to be used for proposals are provided in Table 2, Labor Categories in the Appendix. Labor hour may only be billed in each category if personnel meet the minimum education and experience required in that category.

14.4 The capability of the Contractor to meet the staffing requirements identified in Table 3, Minimum Mandatory Personnel (Core Staff) and Table 4, Required Experience in the Appendix will be evaluated prior to award of the IDIQ and each task order. The Contractor shall not be entitled to bill the Government to maintain this minimal staffing.

14.5 The Contractor shall identify a single Program Manager (PM) as the overall point of contact for management of the program. The PM will be responsible for accomplishing the basic contract and task order objectives utilizing the Contractor’s resources (support, personnel, subcontractors, time, etc.).

14.6 Additionally, for each task order, the Contractor shall identify a task order POC that has been assigned responsibility for all task order specific objectives.

14.7 The selection, hiring, reassignment of duties, transfer, supervision, management, control, and termination of Contractor employees in performance of this PWS shall be the responsibility and prerogative of the Contractor; subject to the minimum qualifications and labor categories identified in Tables 3 and 4 of the Appendix. The specified qualifications represent a minimum individual requirement in terms of academic achievement, or experience, or both for a particular individual in a given category.

14.8 The Contractor shall provide the Government with a filled in version of Table 5 in the Appendix as part of their basic proposal. The first and last name, firm, and category number of which requirement (from Tables 3 and 4) that employee is meeting, shall be included in the provided table.

14.9 In the event of staffing transition or loss that prevents the Contractor from meeting the requirements of Tables 3 and 4 at any time during the contract, the Contractor will submit to the PCO a “get well plan” in writing for PCO approval. The “get well plan” will include the Contactor’s plan to meet the requirement in Tables 3 and 4, how the transition of knowledge will occur and the timeframe until the Contractor will fully meet the staffing requirements.

14.10 Waivers for labor category requirements, a particular staffing requirement or a request to meet an “or equivalent” requirement may be submitted to the PCO for approval. The PCO has the discretion whether or not to grant the requested waiver.

14.11 When Contractor employees visit USAF facilities, each employee will wear a name tag/badge above the waist, clearly visible, which also identifies their status as a contractor, the entire time they are at the USAF facility.

15.0 CONTRACTOR MANPOWER REPORTING

15.1 The Contractor shall report ALL Contractor labor hours (including subcontractor and teaming partner labor hours) required for performance of services provided under this contract for the 417 SCMS via a secure data collection site. The Contractor shall register this contract and input all required information at https://www.sam.gov, or its equivalent.

15.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year.

16.0 ORDERING PROCEDURES

16.1 A Statement of Objectives (SOO) will be provided for each task order and will address the specific requirements for the specified weapon system. Engineering services on each task order may be awarded as funded contract line item numbers (CLINs) or as option CLINs, which may be exercised and funded separately at the Government’s discretion, in support of the program objectives.

16.2 The Contractor shall use this PWS, together with the task order SOO and other applicable portions of the Fair Opportunity Proposal Request (FOPR), as the basis for preparing their proposals. The Contractor shall ensure their proposal addresses all aspects of the C-LGIP FOPR. Proposals shall include a Statement of Work (SOW), a Work Breakdown Structure (WBS), and an Integrated Master Schedule (IMS), plus any other submittals required by the FOPR. The SOW, WBS and IMS must specify in clear, understandable terms the work to be performed by the Contractor to accomplish the SOO objectives. If a teaming arrangement is proposed, the Contractor shall include a copy of the most recent teaming agreement, signed by all parties, with their proposal.

The Contractor shall provide details in their proposal specifying which employee(s), or subcontractor(s), will be performing each task. All IMS elements shall also include a reference to the relevant task order CLIN or subCLIN.

16.3 All FOPRs will contain, at a minimum: (1) response time for preparation of proposals,

(2) Government estimated price range, (3) notional and/or preferred CLIN structure, (4) pricing arrangement, (5) data requirements, (6) SOO, (7) Evaluation Criteria, and (8) applicable clauses.

16.4 The objective of a FOPR SOO is to obtain a price proposal and a technical proposal based on the work that is to be accomplished. Task order price proposals shall include pricing support which identifies the proposed labor by categories (see 16.9), hours per category per Fiscal Year (FY), and the fully burdened labor rate per category per FY.

16.5 The Contractor’s proposal provided in response to the FOPR will be considered the final offer. The Government will not accept Final Proposal Revisions unless expressly requested by the Government for a particular FOPR. After receiving the Contractor’s proposal, if the Government determines negotiations and/or exchanges are necessary, the Contractor may be requested/allowed to revise their proposal. However, the Government will not conduct discussions (including formal opening and closing of discussions), unless otherwise stated by the Government. Task orders, if issued, will be awarded to the offeror whose proposal is determined to be reasonable and to provide the best value to the Government. This determination will be based on an integrated and subjective evaluation of the Contractor’s proposal.

16.6 Unless noted otherwise in the FOPR, the time frame for receipt of proposals will be as follows:

a) Projects estimated at under $500,000 – 7 calendar days

b) Projects estimated between $500,000 & $1,000,000 – 14 calendar days

c) Projects estimated between $1,000,000 & $5,000,000 – 21 calendar days

d) Projects estimated over $5,000,000 – 28 calendar days

16.7 The cost of preparing any quotation or proposal in advance of receiving a task order for a PWS/SOO is to be considered a bid and proposal (B&P) cost. This cost, therefore, is only chargeable to the appropriate indirect cost account. Under no circumstances are such B&P costs to be considered as direct costs chargeable to or reimbursable under a task order that may be issued. The Government reserves the right to not award a task order after issuing a FOPR. Regardless of whether a task order is awarded or not, the Government shall not be responsible for the Contractor’s B&P costs.

16.8 The Government will identify in the FOPR SOO which of the following price arrangements will be used for the engineering services CLIN(s) of each objective: Firm Fixed Priced (FFP) or Cost Plus Fixed Fee (CPFF). A DD Form 1155 will be utilized by the Government to issue task orders. A Standard Form 30 will be used to modify task orders as needed.

16.9 All engineering services CLINs shall use labor categories identified in Table 2, and supplemented by Tables 3 and 4, of the Appendix to this PWS.

16.10 All CPFF engineering services will be completion type IAW FAR 16.306(d)(1) unless otherwise stated in the individual task order.

16.11 For CPFF arrangements the Contractor will submit a voucher for the effort expended and payment will be made on the basis of actual costs incurred. The fee for each CPFF arrangement shall be established as a firm dollar amount, not as a percentage.

16.12 Additional terms and conditions supplementing those of the basic contract will be identified at the task order level, if applicable.

16.13 Any requested Government Furnished Property (GFP), Government Furnished Material (GFM), or Government Furnished Information (GFI) must be identified in the response to the FOPR and be agreed upon prior to award of the task order.

16.14 The Technical Proposal will be incorporated into the order as an attachment. For purposes of this evaluation and contract, the technical proposal may also be referred to as the contractor’s Statement of Work (SOW).

17.0 CONTRACT MANAGEMENT

17.1 The Contractor’s technical proposal will form the basis from which the Contractor shall manage the program and prepare all project status reports.

17.2 The Contractor shall provide a Contractor Management Plan (See CDRL A015) as the initial task order of the IDIQ. Any changes made to the Contractor Management Plan shall be reflected in the Contractor Management Plan submitted with each future task order proposal.

17.3 The Contractor shall participate in a quarterly in person program status review meeting (See CDRL A001).

17.4 The Contractor shall establish a project folder on the 417 SCMS/GUEA shared drive for each awarded task order. At a minimum, the Contractor shall post the following:

a) Final Quarterly Program Management Review (PMR) slides

b) Final Monthly Status Reports

c) Final Meeting Minutes

d) Project Schedule

e) All project deliverables

f) Significant data, analysis, and communications related to each specific project

17.5 The Contractor shall provide all resources, property, personnel, tools, indirect support material, software, or other indirect equipment necessary to provide the necessary engineering sustainment services.

18.0 CONTRACT ON AND OFF RAMP PROVISIONS

18.1 On Ramp. Consistent with FAR 16.504(c)(1)(ii)(A), it is in the Government’s best interest that there remain an adequate number of C-LGIP contractors eligible to compete for task orders at all times during the term of the C-LGIP Basic Contract. Over time, the total number of C-LGIP contractors may fluctuate due to various reasons including industry consolidation, significant changes in the marketplace or advances in technology, general economic conditions, the Government's exercise of the Off Ramp provision, or other reasons. Recognizing this, the Government intends to periodically review the total number of C-LGIP contractors participating in the C-LGIP ordering process, and the number of qualified contractors available in the market place, and determine whether it would be in the Government’s best interest to initiate an “open season” to add new contractors to the C-LGIP Basic Contract. The On Ramp provision is a discretionary unilateral authority of the Government.

18.2 Off Ramp. All C-LGIP contractors are encouraged to be active in reviewing FOPRs and submitting proposals when there is a reasonable chance for award, or submitting a well explained No Bid response. The C-LGIP PCO will review the Contractor's overall performance, the Contractor’s participation, the Contractor’s adherence to contract terms and conditions, and compliance with other key contract provisions such as reporting requirements. If a C-LGIP contractor does not actively submit proposals in response to FOPRs, fails to respond or provides No Bid responses to consecutive FOPRs, no longer wants to participate, has continued poor performance, or does not meet the minimum mandatory requirements, the Government reserves the right to terminate the contract of that C-LGIP contractor or enact this provision and "off ramp" them from the contract. The intent of this provision is to ensure there are a sufficient number of qualified C-LGIP contractors actively participating to facilitate adequate competition and ensure success of the C-LGIP program.

APPENDIX

Table 1 – Services Summary.

Performance threshold note for all deliverables: Gross inaccuracy of data (such as major errors, omissions, and/or misrepresentations) resulting in a failure to meet deliverable requirements may negatively affect the contractor’s CPARS rating regardless of subsequent correction.

Performance Objective Reference Paragraph

Performance Threshold Method of

Surveillance Program Management

Reviews, Monthly Reports, Meeting

Minutes

(CDRL 001, 002, 003)

17.4

Shall be submitted within one business day of the due date with one allowable draft. Deficiencies shall be corrected within five business days.

100% Inspection

WBS & IMS Updates

(CDRL 004, 005)

16.2

The critical path and critical task assignment shall not vary from the proposed task order IMS and WBS without Government pre-approval.

100% Inspection

Test Plans

(CDRL 006)

4.7

Shall be submitted within one business day of the due date with two allowable drafts. Deficiencies to be corrected within 15 calendar days.

100% Inspection

Reports (CDRL 007, 008, 009, 010, 011, 012, 013, 014, 015, 016, 017, 018)

4.1-4.14

Shall be submitted within one business day of the due date with two allowable drafts. Deficiencies shall be corrected within 30 calendar days.

100% Inspection

Digital Models

(CDRL 019)

4.4

No more than five minor errors per digital model. No major deficiencies shall be accepted. All deficiencies shall be correct within 30 calendar days.

Random Sampling

Computer Generated Engineering Products

(CDRL 020)

4.3, 4.5, 4.7, 4.8

Shall be submitted within one business day of the due date with two allowable drafts. Deficiencies to be corrected within 30 calendar days.

Random Sampling

Technical Reviews

(MACC, SRR, CCB,

ERB, TRR) (CDRL 021,

022, 023, 024, 025)

4.7 On time with two allowable drafts.

Deficiencies to be corrected within 10 business days.

100% Inspection

Small Business Participation (CDRL 026 for small business primes and eSRS for all others)

11.3

Shall be submitted by the due date with no more than one exception per task order. Deficiencies shall be corrected within five business days.

100% Inspection

Table 2 – Labor Categories.

The Contractor’s employees must meet or exceed the requirements listed for the Contractor to bill that employee’s labor hours at the provided category level. Listed education levels are Baccalaureate of Science (BS), Masters of Science (MS), and Doctor of Philosophy (PhD).

Principal Senior Entry Intern Description Provides highly specialized programmatic oversight and sign off support

Provides specialized oversight and support

Provides specialized support

Provides support

Program Manager

15 years of experience in program management

7 years of experience in program management

2 years of experience in program management

0-2 years of experience in program management

Engineer (& Scientists)

A PhD, MS, or BS degree in engineering (or a science field) plus 10, 12, or 15 years of engineering experience respectively (Engineering degrees must be ABET accredited)

A PhD, MS, or BS degree in engineering (or a science field) plus 2, 5, or 7 years of engineering experience respectively (Engineering degrees must be ABET accredited)

A degree in engineering (or a science field).

(Engineering degrees must be

ABET

accredited)

Working toward completion of BS in engineering or a science field

Technician 15 years of experience in a technical field

7 years of experience in a technical field

2 years of experience in a technical field

0-2 years of experience in a technical field

Logistician 15 years of experience as a logistician

7 years of experience as a logistician

2 years of experience as a logistician

0-2 years of experience as a logistician

Table 3 – Minimum Mandatory Personnel (Core Staff).

To meet these minimum mandatory personnel requirements, the Contractor shall have on staff for this program a separate employee who meets the requirements of each category.

The Contractor will be considered minimally qualified if they meet the requirements of each category with at least 80% of the stated experience levels and provide a plan to meet the stated experience within 2 years of contract award.

Category Position Title Expertise

Level Requirement

1 Program Manager Principal

7 years of experience managing cost, schedule, and performance of multiple successful, DOD contracts over 1 million dollars

Engineer - Mechanical Systems

Principal 10 years of landing gear specific experience

3 Engineer - Structural Principal 10 years of landing gear specific experience

Engineer or Technician - Instrumentation & Test

Senior 7 years of experience focused on instrumentation and test, including aircraft structural components

5 Engineer - PLM Senior 7 years of PLM development, integration and implementation of Teamcenter

Engineer - Computational Analysis

Senior

7 years of experience performing finite element analysis on aircraft structures, 5 years of experience using ANSYS Mechanical, 5 years of experience performing fatigue analysis, and 2 years of experience using Ncode

Engineer - Statistical Analysis or Reliability Engineering

Senior 7 years of statistical modeling experience

Engineer or Technician - Drafting and Modeling

Senior 7 years of drafting experience using 3D modeling software and 5 years using SolidWorks

Table 4 – Required Experience.

The required experience below can be fulfilled by Core Staff or by additional personnel.

Categories identified below can be met by personnel that fulfill other roles and requirements. The Contractor will be considered minimally qualified if they meet the requirements of each category with at least 80% of the stated experience levels and provide a plan to meet the stated experience within 2 years of contract award.

Category Experience Requirement

9 Materials & Processes An engineer or technician with 7 years of experience with landing gear materials and processes

10 MECSIP & ASIP

An engineer with 7 years of experience with ASIP & MECSIP requirements

11 Reverse Engineering An engineer with experience managing multiple successful aerospace reverse engineering projects (requiring airworthiness approval)

12 Signal Processing An engineer or technician with 5 years of signal processing expertise

13 Contracting A program manager, logistician, or equivalent with 7 years working directly with Government DOD contracting

14 Logistics A program manager, logistician, or equivalent with 7 years of Air Force supply chain logistics experience

Table 5 – Key Personnel.

The Contractor’s proposal shall include the following table, filled in with the Contractor’s employees that meet each of the requirements in Tables 3 and 4 (with the provided example data removed). The table size may be adjusted to meet the Contractor’s needs.

Category Name Labor Category Firm

1, 13, 14 John Smith Principal Program

Manager XYZ Company

4, 12 Jane Doe Principal Engineer XYZ Company 8 William Johnson Senior Technician ABC Company