Emergency_Response_2_PWS_-_RevD.pdf

417 SCMS/GUEA

Performance Work Statement

For

Landing Systems Emergency Response Contract

PREPARATION DATE: 18 July 2019

REVISION NUMBER: N/A

PREPARING ORGANIZATION: 417 Supply Chain Management Squadron, HILL AFB UT 84056

LS Emergency Response PW 417 SCMS/GUEA

- 2 -

SECTION I - DESCRIPTION OF SERVICES

1.0. Scope

1.0.1. The 417th Supply Chain Management Squadron, Landing Gear Engineering (GUEA) is periodically tasked to provide urgent technical assistance or support to other organizations in terms of mishap or failure analysis, system safety evaluation (SSE), Failure Modes and Effects Criticality Analysis (FMECA), and short term remediation and fleet stabilization efforts. Many of these taskings are small in nature (under 100 man-hours or $25,000) and are urgent with little or no lead time. Constraints (examples include the need for testing that cannot be accomplished organically, or the need for rapid overhaul process development to mitigate fleet groundings) may drive GUEA to require contractor support. Under this contract, if GUEA determines that contractor support is needed, GUEA is able to task the contractor to provide the technical support necessary to respond to these urgent requests for engineering assistance.

As indicated, this contract is intended to accommodate relatively small taskings, usually needed on an urgent basis, that were not program requirements and were not included in the Applied Technologies for Landing Systems 3

(ATLAS 3) contract.

1.0.2. The objectives and requirements identified within this Performance Work Statement (PWS) are described in general landing systems specific terms. Each Task Order (TO) will address specific task requirements, project scheduling, and other related performance criteria, as applicable. Engineering services for each task order are expected to be fully funded. This requirement will have a single 4 year ordering period with a 5 year performance in support of the objectives in Paragraph 1.0.4.

1.0.3. The contractor shall provide all resources, property, personnel, tools, indirect support material, software, or other indirect equipment necessary to provide engineering sustainment services for emergency response activities.

The Air Force's primary consumer for contractor Landing Systems services is the Landing Gear Engineering Office, 417 Supply Chain Management Squadron (SCMS).

1.0.4. Emergency Response objectives are to: (a) identify mishap/failure root cause, (b) determine fleet applicability and safety concerns, and (c) provide interim fleet stabilization options. This contract will not be utilized for long term mishap response investigation and resolutions as identified in ATLAS 3.

1.0.5. Emergency Response requests fall into one of three areas: (1) Mishap Support, (2) Production Support, and

(3) Test Support. The contractor shall provide technical support to respond to requests for engineering assistance.

1.0.5.1. Mishap support: This may include telephone or field support, failure analysis, antiskid support and analysis, structural analysis, system simulation, Hardware-in-the-Loop testing, Safety Investigation Board support, and system/software modeling.

1.0.5.2. Production support: This may include Material Review Board support for the overhaul shop, stress analysis, on-site shop support, analysis review and critique, and technical support for production issues. This will not include any type of manufacturing or production of an item, only up to the initial production process.

1.0.5.3. Test support: This may include technical and logistical support for testing efforts, on-site support for landing gear tests, analysis and data review, and report writing.

1.0.6. Emergency Response's scope does not include advisory and assistance services (refer FAR 2.101), management or professional support, policy development, or engineering services for which the program office is responsible (e.g. design services for weapons systems that aren't beyond Full Rate Production).

1.0.7. Travel within 48 hours may be required upon notification.

1.0.8. This requirement is not mission-essential.

LS Emergency Response PWS 417 SCMS/GUEA

- 3 -

1.1. Emergency Response Sustainment Categories

1.1.1 . Services performed by the contractor will fall under six Landing Gear areas or depot operations, supporting Air

Force Landing gear assets:

(a) Landing Gear Structures

(b) Rolling Stock (Wheels and Brakes)

(c) Antiskid

(d) Materials

(e) Processes

(f) Business/Data

1.2. Specific Tasks

1.2.1. Specific projects the contractor may perform include (to be defined at TO level):

(a) System safety evaluation analyses

(b) Failure Modes and Effects Crit icality Analysis (FMECA)

(c) Short term remediation

(d) Fleet stabilization plan

(e) Problem identification studies

(f) Briefing materials as required

(g) Short-Term Mishap response investigation/resolution

(h) Risk/Impact identification to OSS&E

A project may include a combination of tasks the contractor may perform in a series or in parallel to support the specific objective(s) of a Task Order (TO) while some tasks may only tangentially support the objective(s).

1.3. Task Order Operations

1.3.1. Work will not start until task order award and direction from the contracting officer. The Statement of

Objectives (SOO) shall be released by the contracting officer. Upon contractor receipt of the SOO, the contractor shall respond within 48 hours with the required Statement of Work and labor allocation per labor category. Negotiated hours for the task order will be finalized by the contractor and contracting officer.

1.3.2. The objective of the task order SOO is to identify objectives and project magnitude to elicit a Statement of Work (SOW) from the contractor, and receive labor allocations (i.e. binding prices).

(i) The Air Force will transmit a Request for Order Proposal (RFOP) and SOO to applicable contractor. A

RFOP/SOO should identify: (a) problem statement; (b) order objectives; and (c) deliverables (end-state) required.

1.3.3. The contractor will respond by submitting a SOW proposing their solution and labor allocation per labor category for the project. The contractor's SOW and associated price proposal should identify: (a) proposed solution; (b) Integrated Master Schedule (identifying critical paths); and (c) labor allocations per labor category.

(a) Proposed solution: Explain solution and its relationship to the (i) overarching problem, (ii) SOO's objectives, (iii) identified deliverables, and (iv) subcontracting/teaming arrangements for tasks.

(b) Integrated Master Schedule (identifying critical paths): Explain solution's time-frame and relate the schedule to the problem, objectives, and deliverables; emphasize critical tasks, paths, and key moments.

- 4 -

(c) Labor allocations: Provide labor allocations per labor category, such that pricing for the task is defined.

1.4. Project Submissions

1.4.1. The contractor's SOW submissions will form the basis from which the contractor shall manage the program and prepare all project status reports.

1.4.2. The contractor shall provide progress reports on each task order during monthly project review meetings and upon request from USAF weapon system landing gear engineers/program managers. The contractor shall establish project folders in both hard copy and electronic version containing the progress reports and minimum information listed below. Both hard copy and electronic need to be generally accessible to the Emergency

Response Program Manager and USAF weapon system landing gear engineers/program managers. At a minimum, each project folder will contain the following:

(a) Contract documents, including original SOW and all updated versions highlighting any deviations

(b) Microsoft Project schedule with the complete project timeline and clearly identified critical path

(c) Quad Charts for monthly reviews

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

(e) Monthly financial status (broken down into applicable categories; labor, material; et al)

(f) Deliverables

1.4.3. To support the specific order objective, contractors may be required to provide additional Contract Data

Requirements Lists (CDRLs) in addition to the typical submissions. Additional CDRL requirements will be clearly identified in the applicable RFOP and/or SOO.

- 5 -

LS Emergency Response PWS

SECTION II - SERVICE SUMMARY

2.1. Services shall be rendered in conformance with this PWS and demonstrate accomplishment of contract objectives in accordance with thresholds established in the Quality Assurance Plan.

2.2. The Air Force may identify and utilize a different quality standard or threshold as indicated in a particular

RFOP or TO. Thresholds are utilized to establish a quality standard that is measured prior to intervention (contract performance) and post intervention to determine the effectiveness of the contractor's performance.

2.3. Surveillance will be conducted monthly throughout the performance of work; and, must be accomplished by

Program Manger prior to exercise of an Option (i.e. severable phase of completion) or upon TO completion (refer

Section V for additional information).

Services Summary Table:

Reference Performance Objective/Elements Standards/AQL

TO Integrated Master Schedule (IMS)

Submission Timeliness:

The contractor shall provide deliverables in accordance with

TO IMS

Deliverables are provided on time in accordance with the TO IMS, unless the contractor identifies a valid delay, provides timely notice in advance of the delay, and an extension is granted by the Government.

TO PWS/SOW Submission Quality:

Deliverables shall be provided with minimal need for re-work

Deliverables are provided to meet specific task order requirements in no more than two draft releases and one final releases.

TO PWS/SOW Submission Review:

Deliverables shall be provided to Government only after contractor’s internal review process has been accomplished (as defined by contractor’s Quality Control Plan)

Each release (draft or final) shall have been vetted through the contractor’s review.

TO PWS/SOW Specific to TO

The intent of this element is to acknowledge that there will likely be TO-specific requirements that will be monitored during the course of TO execution

Specific to TO

PWS Section 5. Surveillance:

Formal contract deficiencies resolution shall be addressed in accordance contractor’s Quality Control Plan

CM/TOPOC responds w/in seven days

Generally, no more than three formal deficiencies per TO (inclusive of options); however, limit may be tailored at TO level

The type of deficiency shall not be repeated

SECTION III - GOVERNMENT FURNISHED PROPERTY

3.1 Government Furnished Property (GFP)

3.1.1. The Air Force does not anticipate furnishing any real property to facilitate contract performance; however, if identified and utilized on a TO, the contractor must conform to the provisions of AFI 31-101 for safeguarding the

GFP. All records, files, documents, and work papers provided by the Air Force or generated by the contractor in support of the contract are Government property and shall be maintained and disposed of per Air Force Manual

(AFMAN) 37-139.

3.1.2. GFP may be provided as required and identified in the specific task order. 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 specified by the 417 SCMS in the task order with post-award monitoring accomplished by the Contracting Officer's Representative (COR).

3.2. Data

3.2.1. The Air Force may provide access to electronic systems and data pursuant to TO accomplishment, subject to compliance with applicable statutes and regulations. Examples of electronic systems and data include:

JEDMICS, D200, D035, D043, e-mail, Form 202, etc. If access is provided, the contractor must agree to and

- 6 -comply with the applicable system restrictions (non-disclosure agreements, security clearance requirements, etc.).

- 7 -

LS Emergency Response PWS

SECTION IV - GENERAL INFORMATION.

4.1. Authority

4.1.1. Procuring Contracting Officer's (PCO) Authority. The PCO is the only person authorized to approve changes in any of the requirements under this PWS and any provisions contained elsewhere in this contract. In the event the contractor implements any such change at the direction of any person other than the PCO, the change will be considered to have been made without authority.

4.2. Data Rights

4.2.1. All data shall be developed and provided as identified in each task order in accordance with the data right clauses contained in the basic contract. Unless the contractor expresses a claim in their proposal to providing data to the Government with less than unlimited data rights, the Government will assume unlimited data rights (see DFARS 252.227-7013 for definition of data rights). In some cases, the contractor may be required to provide proprietary data for government use. This will be specified in the individual task order.

4.2.2. Data generated during an Emergency Response task order will be provided to all contractors on ATLAS

3 if a long-term project is spun-off from the recommended outcome and the acquisition strategy for the long-term project anticipates the use of ATLAS 3. This information will be provided to the contractors as soon as the government is contemplating a long-term solution change.

4.3. Contractor Personnel

4.3.1. Landing gear systems engineering experience and expertise are required among the six landing gear sustainment categories (refer para. 1.1.).

4.3.2. The contractor shall identify a single Contract Manager (CM) as the overall point of contact for management of the program. The CM will be responsible for accomplishing the contract and task objectives utilizing the contractor's resources (support, personnel, sub-contractors, time, etc.) effectively.

4.3.3. The contractor shall identify a single Principle Engineer (PE) as the point of contact for all task order technical solutions and objective accomplishments.

4.3.4. The selection, hiring, assignment of duties, 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 Table 4.0.

below. 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. The contractor shall ensure all contractor employees wear appropriate attire, depending on particular job assignment, and will wear a name tag/badge consisting of individual's name, position, and company. The name tag/badge will be worn above the waste and clearly visible the entire time on the Air Force Base to identify they are a contractor employee.

4.3.5. Academic achievement level shall have been obtained at a regionally accredited (college, university, vocational school) institution in consequence of rigorous study of the applicable subject. Levels of achievement are: (a) Baccalaureate of Science (BS); (b) Masters of Science (MS); and, (c) Doctor of Science (PhD).

4.3.6. A waiver to a particular minimum qualification level may be requested by the contractor. For all labor categories not identified as "Junior'' a waiver request must be submitted in writing articulating adequate technical justification for the waiver and the projected benefit to the Air Force in the event the waiver is approved. The Government has the complete discretion whether to grant the requested waiver. For all labor categories identified as "Junior'' no waiver is required.

- 8 -

4.3.7. The contractor shall maintain a readily available staff of personnel consistent with the level identified in Table 4.1. -Staffing Standards and Figure 4.0. - Staff Structure.

Table 4.0. - Labor categories

Responsible for managing the contract's multiple TOs and disciplines pursuant to overarching contract objectives. This individual will be responsible for planning and staffing the projects, as well as achieving overall technical, quality, and schedule performance requirements.

Provides assistance to the Contract Manager and engineers with activities such as data collection, analysis, and reporting to support contract, task, and technical objectives.

Provides highly specialized engineering oversight and support which requires knowledge of landing gear aircraft structures, materials, designs, and analytical techniques.

Provides specialized engineering oversight and support which requires knowledge of landing gear aircraft structures, materials, designs, and analytical techniques.

Provides specialized engineering support which requires knowledge of landing gear aircraft structures, materials, designs, and analytical techniques.

Provides engineering support in the field of landing gear aircraft structures, materials, designs, and analytical techniques.

knowledge of landing gear systems such as hydraulics, brakes, antiskid, controls, etc.

15 years experience in direct landing gear or aerospace program management

3- years experience in project management.

PhD or MS or BS in Mechanical, Structural, Aerospace, or Materials

Engineering plus 10, 12, or 15 years experience, respectively, with USAF landing gear.

Engineering plus 2, 5, or 7 years experience, respectively, with USAF landing gear.

Engineering.

BS or working towards completion of BS in Mechanical, Structural, Aerospace, or Materials

Structural, Aerospace, Materials, Electrical, or Controls plus 10, 12, or 15 years experience, respectively, with USAF landing gear rolling stock.

- 9 -

· Provides specialized engineering oversight and gear systems such as hydraulics, brakes, antiskid, controls, etc.

systems such as hydraulics, brakes, antiskid, controls, etc.

landing gear systems such as hydraulics, brakes, antiskid, controls, etc.

knowledge of landing gear overhaul, repair, or manufacturing processes.

gear overhaul, repair, or manufacturing processes.

overhaul, repair, or manufacturing processes.

landing gear overhaul, repair, or manufacturing processes.

knowledge of Mechanical, Aerospace, Electrical, IT, Quality, or Materials Engineering.

support which requires knowledge of

Mechanical, Aerospace, Electrical, IT, Quality, or Materials Engineering.

PhD or MS or BS in Mechanical, Structural, Aerospace, Materials, Electrical, or Controls plus 2, 5 or 7 years experience, respectively, with

USAF landing gear rolling stock.

Electrical, or Controls.

Aerospace, or Materials, Electrical, or Controls.

Industrial, Chemical, or

Environmental Engineering plus 10, 12, or 15 years experience, Industrial, Chemical, or

Environmental Engineering plus 2, 5, or 7 years experience, Industrial, Chemical, or

Environmental Engineering.

Aerospace, Materials, Industrial, Chemical, or Environmental

Aerospace, Electrical, or Materials

Engineering plus 10, 12, or 15 years experience, respectively.

Engineering plus 2, 5, or 7 years experience, respectively.

- 10 -which requires knowledge of Mechanical, Aerospace, Electrical, Quality, IT, or Materials

Mechanical, Aerospace, Electrical, Quality, IT, or Materials Engineering.

Provides highly specialized oversight and support in the areas of landing gear inspection, maintenance, overhaul, quality, or testing.

Provides specialized oversight and support in the areas of landing gear inspection, maintenance, overhaul, quality, or testing.

Provides specialized support in the areas of landing gear inspection, maintenance, overhaul, quality, or testing.

Provides support in the areas of landing gear inspection, maintenance, overhaul, quality, or testing.

support in the areas of USAF landing gear life cycle analysis or logistics.

Provides specialized oversight and support in the areas of USAF landing gear life cycle analysis or logistics.

USAF landing gear life cycle analysis or logistics.

Provides support in the areas of USAF landing gear life cycle analysis or logistics.

support in the areas of program cost, schedule and performance.

Provides specialized oversight and support in the areas of program cost, schedule and performance.

program cost, schedule and performance

PhD or MS or BS in Mechanical, of BS in Mechanical, Aerospace, Electrical, or Materials Engineering.

15 years experience in applicable inspection, maintenance, overhaul, quality, or testing.

7 years experience in applicable quality , or testing.

2 years experience in applicable quality, or testing.

Training in applicable inspection , maintenance, overhaul, quality, or testing.

15 years experience in logistics.

7 years experience in logistics.

2 years experience in logistics.

Training in logistics

15 years experience in logistic s.

7 years experience in logistics.

2 years experience in logistics.

- 12 -

Table 4.1. - Staffing Standards

Provides support in the areas of program cost, Training in logistics.

schedule, and performance.

Academic and experience One Contract Manager criteria (Table 4.0.) meeting (para 1.1., Table

4.0.) criteria

Academic and experience One Principal Engineer per criteria (Table 4.0.) division (Structural, Systems, etc.), one

Principal Technician, and one Principal Logistician meeting (para 1.1., Table

Academic and experience One Senior Engineer criteria (Table 4.0.) per division meeting (para 1.1 ., Table

Figure 4.0. - Staff Structure

- 13 -

4.4. Security

4.4.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.

4.5. Environmental

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

4.5.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 Procurement Contracting Officer (PCO) of the change and the PCO will determine if an equitable adjustment is required.

4.6 Sub-contracts

4.6.1 The contractor shall be responsible for the management of any and all sub-contractors performing work in support of contract objectives.

- 14 -

Section V - Quality Surveillance

5.1. Contractor's Quality Plan

5.1.1. The contractor shall develop and implement a quality section in each SOW. The CM will be generally responsible for contract's quality program and the PE will be responsible for the TO quality accomplishment.

5.1.2. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. In addition, the contractor shall develop quality control procedures addressing the areas identified in Section II, Service Summary. The contractor shall update the quality section as applicable noting the results of internal quality audits that may be performed pursuant to TO quality metrics or objectives.

5.2. Surveillance

5.2.1. The contractor shall support Air Force quality assurance surveillance. The Air Force (or a DCMA representative) will periodically evaluate the contractor's performance IAW Paragraph 2.3. (monthly review of contractor's submissions), the contract's Quality Assurance Surveillance Plan and PWS Section II, or RFP/TO criteria as identified. For those requirements listed in Section II, the Contracting Officer's Representative (COR) will follow the methods of surveillance specified in PWS Section II, or RFP/TO criteria as identified. The COR is the Air Force's authorized representative for the Contracting Officer (CO) and will participate in the administration of this contract.

5.2.2. The COR may inform the CM or PE in person when discrepancies occur and may request corrective action. The COR will make a notation of the discrepancy on the Quality Surveillance Form, table 5.0. below with the date and time the discrepancy was observed and will request the CM or PE initial the entry on the surveillance checklist. The CM or PE shall initial next to the defective performance observation indicating acknowledgment of deficiency. The initialing of the observation does not necessarily constitute contractor concurrence with the observation, only acknowledgment that the contractor is aware of the defective performance.

5.2.3. The absence of any contract requirement from the service 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.

5.2.4. The contractor shall on a non-interference basis allow Government audits to be performed on contractor maintained files. Contractors shall expect the Surveillance form, table 5.0, below, to be utilized on a monthly basis to inspect the Status Reports, subsequent to completion of TO options, and/or TO completion. Results of the surveillance will be input into the PPIRS/CPARS system annually.

5.2.5. In the event that a defect occurs the CM or PE shall respond to the concern within one week, 7 calendar days after Quality Surveillance Form's initialed by CM, indicating: (a) cause of the defect; (b) resolution plan with time line; and (c) plan to mitigate recurrence. If the CM/PE disagrees with the observation they shall so state and the CO will determine whether the discrepancy is valid. Valid discrepancies will be tracked to ensure resolution and to document repeat occurrences. It is the CM's responsibility to marshal resources to address valid discrepancies (fewer than 3 errors per TO-inclusive of

Options) and prevent recurrence (no more than one repeated valid discrepancy-inclusive of all TO's contractor has performed work on).

- 1 -

TABLE 5.0: Quality Surveillance Form

Quality Surveillance Form

Date of Surveillance:

COR Conducting Surveillance:

Contract Manager's Comments (& Initials) Regarding Surveillance:

Final Disposition (Completed by Contracting Officer):

Process (ISO 9001, et al.);

Availability (per TO); Reliability