Performance Work Statement.pdf

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

H-1 Sustaining Engineering Support Services

Same title for PWS and QASP

FD2060-21-31353

PR Number

04 October 2021

Prepared by:

AFLCMC/WIUXX

235 Byron Street, Suite 19A

Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use; 15-07-01). Other requests for this document shall be referred to AFLCMC/WIUBC, Robins AFB, GA 31098-1670.

TABLE OF CONTENTS

PR: FD2060-21-31353 PWS REVISION: 0 2

Distribution Statement: C

SECTION TITLE PAGE

SECTION 1 DESCRIPTION OF SERVICES 3

SECTION 2 SERVICES SUMMARY 4

SECTION 3 GOVERNMENT FURNISHED PROPERTY 5

SECTION 4 TECHNICAL REQUIREMENTS 6

SECTION 5 GENERAL INFORMATION 11

SECTION 6 APPENDICES 16

PR: FD2060-21-31353 PWS REVISION: 0 3

1.0 Description of Services

1.1 Objective(s):

A multi-disciplined engineering team with expert knowledge and reach back to corporate Bell resources is needed to provide repair instructions which may require modification support, accident investigation support, re-qualification data, and technical order changes in support of the TH-1 and UH-1 rotary platforms referred to in this document as H-1. Life-cycle sustainability for the H-1 necessitates Bell engineering support available through this contractual agreement. While the government had a full data package delivered with the aircraft in the

1960’s, the data was/has not been maintained over the years to a level that sufficiently captures all design changes since aircraft delivery.

At any given time, the H-1 organic depot acquires engineering assistance to resolve Periodic

Depot Maintenance (PDM) issues beyond the published technical orders. This Original

Equipment Manufacturer (OEM) engineering support contract enable the United States Air Force

(USAF) System Program Office (SPO) engineers access to expertise and engineering data to effectively resolve any PDM issue and manage requirements.

This contract is to obtain engineering support from the Original Equipment Manufacturer

(OEM). This support will provide the United States Air Force (USAF) H-1 System Program

Office (SPO) technical expertise greater than that possessed, access to OEM proprietary data including but not limited to structural/component data, drawings, qualification data, and analysis techniques as required to adequately maintain operational, safety, suitability, and effectiveness

(OSS&E) for the H-1 platform. The specific tasks will require the expertise, analysis techniques, and proprietary data held only by the OEM. The effort regularly delivers the following to the

Government: technical reports, monthly status reports, agendas, minutes, and a final report.

1.2 Benefit to United States Air Force (USAF):

This effort will accomplish sustaining engineering tasks in accordance with individual tasks required to support the existing fielded H-1. These tasks include providing support for resolving associated operational problems and providing technical reports for the H-1.

Tasks include:

- Field Support

- Engineering Change Proposal (ECP) Preparation

- Government System Interfaces

- Sustaining Engineering Tasks

- Project Engineering Management

1.3 Background:

The Air Force UH-1 N model was developed from Bell Model 212 Twin Huey which was first flown in April 1969. The Air Force UH-1N helicopters were manufactured by the Bell

Helicopter Company of Fort Worth, Texas and evolved as a result of a Class V modification

T.O. 1H-1 (U) F-545. The Air Force TH-1H model is the result of three (3) modifications to the

UH-1H. The modifications included engine drive train, structural, and rotor modification as part of the Bell Model UH-1H II (Huey II) kit, as well as avionics upgrade, glass cockpit displays and crashworthy seat modifications. The primary mission of the aircraft is to support undergraduate

PR: FD2060-21-31353 PWS REVISION: 0 4

helicopter pilot training. This effort allows the SPO access to the original equipment manufacturers technical personnel and proprietary data to maintain the OSS&E of the baseline configurations.

2.0 Services Summary (SS):

Performance Objective PWS

Ref

Performance Threshold

Receipt of Contract Data

Requirements List

(CDRL) deliverable

4.2.2 There shall be no more than (2) two late

submission(s) of deliverables per quarter. The

Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the

Government.

Rapid “Urgent” and

Routine “Non-Urgent” response

4.3.3 The contractor’s recommendation for problem

resolution shall be delivered within one business day of receipt of notice of grounded aircraft or a safety mishap issue to include travel plans, if directed. A solution recommendation shall be delivered within three business days of receipt of notice. No more than one late intent for problem resolution is allowed per quarter. For safety or mishaps, no late receipts of recommendations are allowed. For Urgent Engineering Service Task

Requests (ESTR), the contractor shall deliver a response within 24 business hours upon receipt of notice with accurate information for SPO

Engineering to take action. Routine ESTR shall be responded to with proposed solution within (5) five business days upon receipt of ESTR.

Provide Accurate Status

Reports and

Meeting/Conference

Agendas/CDRL

Submissions

4.2.1 There shall be no more than (2) two total

rejection(s) of deliverables per quarter, no more than one rejection per each deliverable. The

Government will reject a deliverable if (1) one or more technical errors or (5) five or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the

CDRL, PWS, or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within (5) five business days of notification of Government rejection.

PR: FD2060-21-31353 PWS REVISION: 0 5

Prepare an agenda and minutes for each

Meeting/Conference

4.2.1 The agenda shall be submitted no later than five (5)

business days prior to the date of the meeting or conference, and minutes no later than five (5) business days after the date of the meeting.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/task order.

3.2 Government Property to be Provided: Contractor shall procure all material and parts necessary for the modification of the end items. Any material and parts purchased under this contract becomes Government property.

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of

Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/task order, loss of

Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.3.2 Reporting Loss of Government Property: The Contractor shall report loss of

Government property in the GFP Module located in the Procurement Integrated Enterprise

Environment (PIEE), https://piee.eb.mil/piee-landing/. Training on how to utilize the GFP module can be found at https://dodprocurementtoolbox.com.

3.4 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/task order, unless the Procuring Contracting Officer

(PCO) directs the Contractor to retain the property for continued use under a successor contract.

All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/task order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/task order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

3.5 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/task order. The contractor shall ensure contractor personnel who require access to a U.S. Government Automated Information System

PR: FD2060-21-31353 PWS REVISION: 0 6

(AIS) have a Department of Defense National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with Department of Defense (DoD) 5200.2-R, Personnel Security

Program. The U.S. Government will provide system access subject to approval of the DD Form

2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the system account will be closed.

4.0 Technical Requirements: The contractor shall be required to perform analysis, compile technical reports, conduct studies and provide support for urgent response requirements for the

USAF H-1 fleet.

4.1 Period and Place of Performance:

4.1.1 Contract/task order Period of Performance (POP): The POP for the contract will extend from date of contract award. Four (4) additional annual ordering period options are available potentially extending the POP through 2027.

4.1.2 Place of Performance: These services will be performed at various locations depending on the task order and requirement. Possible performance locations include the following:

- Contractor Site

- Any military base including CONUS and OCONUS locations

- Other locations to be determined (TBD)

4.2 Contract Data Requirements List (CDRL):

Document

Identifier

DID Title PWS Reference(s)

A001 DI-MISC-80508B Technical Report – Study/Services 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6.5, 4.3.9,

4.4.3.3 A002 DI-MGMT-80368A Status Report 4.4.2, 4.4.3 A003 DI-SESS-8100E/T Product Drawings/Models and Associated

Lists 4.3.6

A004 DI-FNCL-80331A Funds and Man-Hours Expenditure Report 4.4.2 A005 DI-ADMN-81249B Conference Agenda 4.4.3, 4.4.3.1, 4.4.3.2, 4.3.6.1, 4.3.6.2

A006 DI-ADMN-81250B Conference Minutes 4.4.3.1, 4.4.3.2, 4.6.1,

4.6.2 A007 DI-ADMN-81373 Presentation Material 4.4.3, 4.4.3.1, 4.4.3.2

A008 DI-MISC-81943 Trip/Travel Report 4.4.3, 4.4.3.1, 4.4.3.2, 4.4.3.3, 4.4.4, 4.5.1, 4.5.2

A009 DI-MGMT-

80061A/T

Engineering and Technical Services

Accomplishment Report 4.4.3, 4.4.3.1, 4.4.3.2, 4.4.3.3, 4.4.4

PR: FD2060-21-31353 PWS REVISION: 0 7

4.2.1 Quality of CDRL Deliverable: There shall be no more than (2) two total rejection(s) of deliverables per quarter, no more than one rejection per each deliverable. The Government will reject a deliverable if (1) one or more technical errors or (5) five or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within (5) five business days of notification of Government rejection. Upon scheduling a meeting/conference an agenda shall be submitted no later than five (5) business days prior to the date of the meeting or conference, and minutes no later than five (5) business days after the date of the meeting.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area

Workflow (WAWF) or be submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. There shall be no more than (1) late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Engineering Support: The OEM contract is intended to be highly flexible and broad in scope in order to allow quick reaction and adaptation to the demands of a highly dynamic and unpredictable operating environment. The engineering services contract line item supports all engineering services areas. All engineering tasks issued through Engineering Service Task

Requests (ESTR) within the period of performance are intended to be short term projects, estimated at typically less than 100 hours.

4.3.1 Validation of Component Retirement Times (CRT): On an as-needed basis, the contractor shall validate the CRT and overhaul times for USAF H-1 platform components

(prioritized component list shall be provided by SPO engineering through ESTR) using updated usage survey, existing flight loads most representative of each specific aircraft, updated component fatigue strengths, and current damage hypothesis methods (i.e. cycle counting). The contractor shall provide substantiating fatigue data. Existing aircraft/component reliability shall not be affected. The Government will reject a deliverable if (1) one or more technical errors or

(5) five or more minor errors are found within the deliverable. Revisions shall be completed within (5) five business days. (DI-MISC-80508B) (A001)

4.3.2 Proprietary Data: The contractor shall provide to the SPO Engineering access to proprietary data as required to maintain operation, safety, suitability, and effectiveness of the baseline configurations. The contractor shall submit a technical report by the ESTR date. The

Government will reject a deliverable if (1) one or more technical errors or (5) five or more minor errors are found within the deliverable. Errors shall be corrected within (5) five business days.

(DI-MISC-80508B) (A001)

4.3.3 Urgency/Routine Response: When an ESTR has indicated a grounded aircraft in field or programmed depot maintenance work stoppage, the contractor shall make an initial response consisting of the proposed solution, or the status thereof, within (1) one business day with accurate information for SPO Engineering to take action. If required by the contractor, PR: FD2060-21-31353 PWS REVISION: 0 8

Government-owned drawings to support an ESTR will be supplied via electronic means within

(1) one working day. The contractor shall provide drawings as needed to the Government within

(1) one working day.

For routine request, the contractor shall make an initial response with a proposed solution within

(5) five business days. The exception to this shall be Mylar drawings which will be treated on a case by case basis to be defined by the SPO Engineering and contractor. (DI-MISC-8050B)

(A001)

4.3.4 New/Unique Operational Requirements: The contractor shall provide technical support for fielded H-1 platform unique system configuration as originally delivered by Bell or assist with unique systems delivered by Bell but modified by the SPO. This will involve evaluating the impact of unique Air Force mission requirements on basic H-1 platform systems to ensure that established safe baselines are not being compromised. The major systems of concern are electrical, avionics, aeromechanics, structural, mechanical, flight control and dynamic systems. If a unique aftermarket installation is identifiable or the system has been modified by the SPO, the

Government will provide the contractor with all necessary information required to complete the task by attaching these documents to the ESTR. A specific example is the possible implementation of the Boundary Layer Research (BLR) Fast Fin and any impact it makes on

CRT’s. The contractor shall submit a technical report by the specified due date. The report shall contain no more than a total of (5) five typographical errors and/or technical inaccuracies. Errors shall be corrected with (5) five business days. (DI-MISC-80508B) (A001)

4.3.5 Aircraft Sustainment and Reliability/Maintainability Support: This sustainment support primarily comes in the form of responding to service revealed deficiencies and US Air

Force related Technical Order deficiencies. Several forums are used by fielded units to identify problems or deficiencies to the SPO. Some of these are product quality deficiency reports

(PQDR), product improvement working group (PIWG) action items, AFTO 22, AFTO135, AFTO 847, requests from SPO engineering, critical item lists, corrosion prevention advisory board (CPAB) action items, and field or depot requests for engineering support. The contractor shall work with the Government to analyze and develop corrective actions for these design-related supportability and maintenance deficiencies; investigate reliability/maintainability issues identified through PQDR’s, PIWG action items, and initiatives as directed by SPO engineering to determine design and/or technical manual changes required for their improvement; initiate documentation of appropriate design changes under this sustaining efforts.

The contractor shall also conduct assessments on the other components not identified in these forums in order to avert future problems (obsolete parts, aging aircraft studies, etc.), technology insertion or operating and support cost reduction initiatives as directed by SPO engineering. The contractor shall submit a technical report by the specified due date. The Government will reject a deliverable if (1) one or more technical errors or (5) five or more minor errors are found within the deliverable. Errors shall be corrected within five (5) business days. (DI-MISC-80508B)

(A001)

4.3.6 Engineering Data: The contractor shall develop/produce/maintain and deliver a Technical

Data Package (TDP) that accurately depicts the final product. TDP data include, but is not

PR: FD2060-21-31353 PWS REVISION: 0 9

limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicated the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and/or components. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the following American Society of Mechanical Engineers (ASME) standards; AMSE Y14.100-

2013, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with

ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings Models and

Associated Lists (Engineering Data) under this contract. Data set classification code marking

IAW Appendix F of ASME Y 14.100-2013 is required. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD-130N, other applicable documents reference therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be

IAW document 9579777 Revision B (CAGE 98752). The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16, [DI-SESS-81000E/T].

4.3.6.1 Engineering Data Guidance Conference: The contractor shall support and co-chair a guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

[DI-ADMN-81249B, DI-ADMN-81250B]

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor’s drafting practice procedures/TDP drawing formats/CAD programs.

e. The contractor’s quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor’s configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

PR: FD2060-21-31353 PWS REVISION: 0 10

h. Digital Technical Data Package (TDP) deliverables.

NOTE: Guidance Conference may be held in conjunction with other meetings or conferences.

4.3.6.2 In-Process Review (IPR) of the TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted on after the contractor’s quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that

Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR).

Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Forces drawing 9579776

(CAFÉ 98752). These shall consist of the Native, Neutral, Work Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/Memory Device Data.

The Contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to anticipate date of completion point. The IPR shall focus on the contractor’s progress in preparation of the TDP.

The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate

IPR at the subcontractor’s/vendor’s facility. [DI-ADMN-81249B, DI-ADMN-81250B]

4.3.6.3 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.3.6.4 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated in the applicable engineering data within 90 days after engineering release/Air Force concurrence or at interval of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

PR: FD2060-21-31353 PWS REVISION: 0 11

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

4.3.6.5 Engineering Change Proposal (ECP) Preparation: The contractor shall provide the resources required in Government preparation of ECPs. Contractor preparation of ECPs shall not be performed under this contract. The contractor shall submit a technical report by the specified due date. The Government will reject a deliverable if (1) one or more technical errors or (5) five or more minor errors are found within the deliverable. Revisions shall be completed within five (5) business days. (DI-MISC-80508B) (A001)

4.3.7 Project Engineering Management: The contractor shall provide the part-time/full-time services of an individual (PM or Engineer) to serve as the point of contact for H-1 platform technical/design issues and direct the sustaining effort activities described in the PWS.

4.3.8 Flight Testing/Engineering Support: The contractor shall provide qualified test pilots and flight engineers as required by AFLCMC/WIU. The qualified personnel shall be utilized when the Government does not possess the expertise to accomplish the task, such as mishap investigations, re-qualification of components and subsystems. Estimated hours expended for

Flight Test shall not exceed 50 hours in the basic ordering period and 50 hours for each optional year ordering period.

4.3.8.1 The Contractor shall comply with the operating procedures contained in the combined regulation 48 CFR 252.228-7001, entitled “Ground and Flight Risk” and Defense Contract

Management Agency Instruction 8210.2 entitled “Aircraft Operations” in effect on the date of contract award.

4.3.9 Other Services: The contractor shall provide the support services as required for other tasks that may surface during the contract service tenure. These tasks may include providing: on-site weapon system support personnel to field activities, conducting technical studies, investigation of specific failures, analytical studies, feasibility studies, fabrication or procurement of items required to model proposed solution, fabrication of test specimens, conducting testing including flight of aircraft during Program Depot Maintenance, fatigue testing technical report by the specified due date. (DI-MISC-80508B) (A001)

4.4.1 Program Management: The contractor shall be responsible for providing the management, administration, financial control, engineering, manufacturing, procurement, testing, and quality assurance activities associated with this effort. The contractor shall identify a liaison point of contact on all contractual and technical matters. All program management requirements of the contract shall extend to the effort required by this PWS. AFLCMC/WIUC will authorize and convey tasks in writing to the contractor through ESTR. The contractor’s response and expenditures shall be limited to the authorized task requirements.

PR: FD2060-21-31353 PWS REVISION: 0 12

4.4.2 Monthly Status/Financial Report: The contractor shall prepare and submit status reports detailing work performed during the previous month. This requirement is for the basic contract period and any additional ordering periods. The contractor shall identify tasks to be performed during the next reporting period in each status report. The status report shall include financial expenditure information. The financial status shall be reported as both cumulative and for the specific reporting month. (DI-MGMT-80368A, DI-FNCL-80331A) (A002/A004)

4.4.3 Meetings: The contractor shall be responsible for attending/hosting meetings in accordance with (IAW) the following paragraphs. In support of the meetings and conferences, the contractor shall furnish agendas, presentation materials and resulting meeting minutes, as required. At a minimum, the contractor shall participate in semi-annual Program Management Reviews and

PIWG meetings. The contractor shall also participate in the annual CPAB meeting.

(DI-MGMT-80368A) (A002)

(DI-ADMN-81249B) (A005)

(DI-ADMN-81250B) (A006)

(DI-ADMN-81373) (A007)

(DI-MISC-81943) (A008)

(DI-MGMT-8006A/T) (A009)

4.4.3.1 Kick-off Meeting: A kick-off meeting shall be hosted at a location determined by the

Government no later than 30 days after contract award. The purpose of the meeting is to review and evaluate the contractor’s interpretation of the basic contractual requirements and to provide necessary direction and guidance.

(DI-ADMN-81249B) (A005)

(DI-ADMN-81250B) (A006)

(DI-ADMN-81373) (A007)

4.4.3.2 Program Review: The Government and the Contractor shall participate in semi-annual

Program Reviews and technical meetings as defined and required by the Government as needed.

The location of these meetings will be determined by the Government. The kick-off

/requirements review will be conducted no later than (NLT) 30 days after receipt of order at a location determined by the Government. At the Government’s discretion, Program Reviews and the kick-off meeting may be accomplished through alternate means (i.e. teleconference, etc.).

(DI-ADMN-81249B) (A005)

(DI-ADMN-81250B) (A006)

(DI-ADMN-81373) (A007)

4.4.3.3 Final Report: The results of the contract activities shall be documented in a final report.

This report shall detail the activities and evaluations accomplished during the completion of this task. The report shall include trip reports for any trips taken. The contractor shall submit a final report at the completion of the period of performance.

(DI-MISC-80508B) (A001)

PR: FD2060-21-31353 PWS REVISION: 0 13

4.4.4 Travel: The Contractor may be required to travel for the performance of the work described within this PWS. Travel may include locations within the continental United States

(CONUS) and outside the continental United States (OCONUS). The number of trips and personnel traveling shall be limited to the minimum required to accomplish work assignments in accordance with the assigned tasks. Travel will be reimbursed according to the rates outlined in the Federal Travel Regulations for travel within the CONUS; Joint Travel Regulations (JTR) for travel to Alaska, Hawaii and outlying areas of the United States; and the rates established by the

Department of State for traveling OCONUS. Airfare shall consist of no more than coach class seating while vehicle rentals shall be consistent with the most economic and reasonable rates available. In most circumstances, economy class vehicles will suffice. All Contractor travel, when required, shall require prior written approval a minimum of five (5) business days in advance from the Procuring Contracting Officer (PCO) and concurrence by the Program

Manager (PM) prior to costs being incurred. The Government is under no obligation to reimburse the contractor for any travel in which prior written approval from AFLCMC/WIUK, Robins AFB GA has not been received. All travel shall be in accordance with DoD JTR. Trip

Reports shall be submitted to AFLCMC/WIUBC NLT five (5) business days upon return from the trip. (DI-MISC-81943, A008)

5.0 General Information

5.1 Continuation of Mission-Essential Services during a Crisis: The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2. Security Requirements

5.2.1 General: Knowledge and/or generation of classified information and/or Controlled

Unclassified Information (CUI) are required for the performance of the contract/order. The

Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: Department of Defense (DoD) 5200.2-R, Personnel Security

Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program, DoD Manual

5205.02-M, DoD Operations Security (OPSEC) Program Manual, and Robins Air Force Base

Integrated Defense Plan (RAFB IDP) 31-101.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of

USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

PR: FD2060-21-31353 PWS REVISION: 0 14

Government interests. The Contractor shall ensure Contractor personnel who perform work on a

Government facility comply with the OPSEC procedures of the facility.

5.2.4 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22-

M. Applicable equipment shall be safeguarded, maintained and operated in accordance with

DoD 5220.22-M.

5.2.5 Security Clearance: The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the appropriate level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the

Department of Defense (DD) Form 254, Department of Defense Contract Security Classification

Specification.

5.2.6 Security Incident or Violation: The Contractor shall immediately notify the Government

Security Office of any potential or actual security incident or violation.

5.2.7 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The

Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National

Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.8 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.9 Common Access Card (CAC)

5.2.9.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The

Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the

PCO. The Government will provide the Contractor instruction on how to complete a Contractor

Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System

(RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.2.9.2 The Contractor shall immediately report a lost or stolen CAC as directed by local

Government policy. The Contractor shall notify the PCO of any change to the list of

PR: FD2060-21-31353 PWS REVISION: 0 15

contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.3 Environmental Management System (EMS): These services shall not be performed at a

Government facility; therefore, the EMS requirement does not apply.

5.4 Agency Affirmative Procurement Programs: In accordance with FAR 23.404, Agency

Affirmative Procurement Programs, 100% of purchases of Environmental Protection Agency

(EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list

[Comprehensive Procurement Guideline (CPG) Program | US EPA] and/or United States Department of Agriculture (USDA)-designated products included in the bio-based product listings

[http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or bio-based content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.

5.5 Safety Requirements:

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and

Health regulations including, Public Law 91-596 as amended by Public Law 101-552

[Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.5.2 Voluntary Protection Program (VPP): Contractor personnel performing work on a

USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.5.3 Mishap Notification/Investigation: The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations.

The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The

Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within four business hours. The Contractor shall cooperate with Government safety investigations.

5.5.4 Safety and Health Plan: While performing work under this contract the contractor shall comply with all applicable federal, state and local regulations regarding occupational safety and health. The contractor shall notify the Procurement Contracting Officer (PCO), within eight (8) hours of any damage to government property where the dollar value exceeds $500,000.00 and within two (2) workdays, for any damage to government property less than $500,000.00 during the execution of the contract.

https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program#products http://www.biopreferred.gov/ http://www.osha.gov/dcsp/vpp/index.html

PR: FD2060-21-31353 PWS REVISION: 0 16

Mishap notifications shall contain, as a minimum, the following information:

a. Contract, Contract Number, Name and Title of Person(s) Reporting

b. Date, Time and exact location of accident/incident

c. Brief Narrative of accident/incident (Events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed)

h. Other pertinent information

If requested by the designated CO, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office. Contractors will not dispose of contract data related to a mishap until notified to do so by the CO.

5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Service Contract Reporting: In accordance with 10 United States Code 2330a, the

Contractor shall provide an annual count of Contractor/Subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity and if the acquisition is in excess of

$3,000,000.00. The Contractor shall report all Contractor labor hours, including Subcontractor labor hours, required for performance of the services provided under the contract in the System for Award Management (SAM). Reporting shall be conducted for each fiscal year in accordance with the Service Contract Reporting User’s Guide located on the SAM website. The Contractor shall establish a record for the contract/order in SAM no later than 30 calendar days after contract/order award. Additional information and user manuals for government personnel and

Contractors are available at https://www.sam.gov.

5.8 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.9 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about

Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and

Combat Trafficking in Persons. http://www.state.gov/j/tip https://www.sam.gov/ http://www.state.gov/j/tip

PR: FD2060-21-31353 PWS REVISION: 0 17

6.0 Appendices

Unless otherwise specified, the version of the following specifications, standards, handbooks, technical orders, and engineering reports current on the award date of the contract form a part of this PWS to the extent specified herein. Unless otherwise specified, copies and any other supplements thereto required by the supplier in connection with specified procurement functions should be obtained from the Department of Defense Index of Specification and Standards

(DoDISS) or the Information Handling System (IHS). Any documents required by contractors in connection with specific acquisition functions should be obtained from the contracting activity or as directed by the contracting officer. In the event of a conflict between the documents referenced herein and the contents of this PWS, the contents of this PWS shall govern.

Bell must have a Technical Order Distribution Office (TODO) account in order to obtain copies of the referenced H-1 publications. If an account has not been established, the Offeror must establish a TODO account upon contract award by processing an AFTO Form 43, USAF TODO

Assignment or Change Request in accordance with TO 00-5-1. The IBM Lotus version of the

AFTO Form 43 can be downloaded at http://www.e-publishing.af.mil/. Alternatively, prospective contractor TODOs may download and use the pdf version of the AFTO Form 43 at https://techdata.wpafb.af.mil/toprac/form cv cs.htm. All versions of the form include detailed completion instructions.

6.1 Appendix A: References

Publication Title of Publication Date of Publication Section(s) That Apply

DoD

5220.22-M

National Industrial

Security Program

Operating Manual

(NISPOM).

February 28, 2006

Change 1 - March 28, 2013 Entire

DoDD 4715.1E

Environment, Safety, and Occupational

Health (ESOH) March 19, 2005

DoDD) 5205.02E

DoD Operations

Security (OPSEC)

Program June 20, 2012

DoD Manual 5205.02-

M

DoD Operations

Security (OPSEC)

Program Manual November 3, 2008

Public Law 91-596 as amended by Public

Law 101-552

Occupational Safety and Health Act of 1970

December 29, 1970 as amended through

January 1, 2004 http://www.e-publishing.af.mil/ https://techdata.wpafb.af.mil/toprac/forms.htm