PWSfinal_7_Jul_16.doc

Performance-Based Work Statement (PWS) for

AN/ALR-56C Test Program Set Support on the

AN/ALM-246 TISS

PR Number: FD2060-16-00014 Date: 7 July 2016

1.0 Description of Services: This Performance-Based Work Statement (PWS) defines the technical Engineering support services and deliverable products required by Boeing to investigate and resolve Deficiency Reports (DR) concerning the ALR-56C Test Program Sets (TPS) which run on the AN/ALM-246 TEWS Intermediate Support Station (TISS) and provide Test Program Set (TPS) updates. The objectives for the contractor to accomplish is to perform a DR investigation, submit Report of Findings (ROF) identifying potential fixes/solutions, perform the fix once agreed to by the Government, testing the fix, and packaging the fix for distribution. The Government shall receive monthly status updates on the work accomplished. Additionally the contractor shall provide telephone support, conduct an acceptable Contractor Safety Program and do not delay Mishap Notification and Reporting when required. The TISS is used to maintain the AN/ALR-56 Radar Warning Receiver (RWR) for the F-15C/D/E aircrafts. Over the past several years, numerous Deficiency Reports (DRs) have been reported for the ALR-56C system but were actually TPS issues. Verticality testing issues have been identified as a significant cause. With the current operations tempo every effort must be made to reduce shop flow time and DR’s that restrict carcass from being available to the war fighter.

1.1 Objective(s): This PWS describes the services that will help resolve issues experienced both by the Depot and Intermediate level maintenance for the AN/ALR-56C RWR. The contractor shall identify the sources of deficiencies in both the TPS software and hardware. Analysis and solutions performed will be documented in a report of findings and monthly status reports. The contractor shall then modify the TPS, perform a sell off and provide deliverables per the Contract Data Requirements List (CDRLs).

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by providing support to resolve problems encountered with the operation and use of intermediate and depot support equipment used to support AN/ALR-56C including Automatic Test Equipment (ATE), Interface Test Adapters (ITA), Test Program Set (TPS), and related documentation. The support will include DR resolutions, preparation and delivery of software updates, and technical documentation.

1.3 Background: The ALR-56C is the Radar Warning Receiver (RWR) portion of the F-15 Tactical Electronic Warfare System (TEWS). Originally developed in the 1987, the ALR-56C continues to be used today. Although there have been some redesigns to the system to avert obsolescence, similar parts are constantly being incorporated as the original parts become harder to find or purchase for the rest of the system. This results in a system that performs its function on the aircraft, but occasionally tests differently due to due to minor part characteristic deltas. These deltas result in test/fault isolation issues with the Test Program Sets (TPS). The ALM-246, or TISS, is the Line Replaceable Unit (LRU) tester used both in the field and at the Depot in order to maintain the ALR-56C. The TISS has had some major hardware/software upgrades. Both the TISS hardware and the TPS were developed and upgraded by the Aircraft Integrator, Boeing Company. Thus, Boeing has maintained its expertise. The Depot also repairs the Shop Replaceable Units (SRU) and uses a multitude of test stations. Many of these stations are being replaced by a newer test station VDATS resulting in the rehost of the SRU TPS. The introduction of new test equipment sometimes requires a new approach to how a specific test is performed resulting in changes to a TPS. These approaches are checked thoroughly, but as with any changes there are asset limitations which limit the amount of TPS testing that can be performed and many not represent a true SRU/LRU characteristics distribution. As a result, parameter limits and/or test approaches have to be changed.

2.0 Services Summary

Document the Status and Contractor Progress in monthly reports.

4.9

The contractor submitted monthly status reports shall be technically accurate and complete with no more than one technical error and no more than five typographical errors. Errors must be corrected and the report shall be resubmitted to the Government No Later Than (NLT) 15 working days after receipt of Government comments.

3.0 Government Property and Services

3.1 Government Property: Government Property will be provided.

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property. The FAR and applicable supplements can be accessed at the site http://farsite.hill.af.mil.

3.2 Government Property to be Provided: Government property to be provided includes items provided under contract F33657-01-D-0026 D/O 0124 which is already at the contractor facility to support this effort. Government Property will be use with the new contract on a non-interference basis. See Appendix B of the contract for Government Property Listing.

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property: In accordance with DFARS 252.245-7002, Reporting 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, theft, loss due to lack of security, 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/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 use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.3.3 Return of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government in accordance with current GFE loan/lease agreements upon completion of the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All materials generated under this contract become the property of the Government and shall be returned to the Government than upon completion of the contract. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

3.4 Government System(s): Access to Government systems will not be required to perform tasks under the contract/order.

4.0 Technical Requirements: The following requirements are indicative, but not all inclusive, of the type of work that will be required throughout the performance of this tasking. All tasking shall be provided by 408 SCMS/GUEA or its appointed representative. All requests for assistance by Air Force organizations must go through and be approved by 408 SCMS/GUEA or its appointed representative.

4.1 Period of Performance

4.1.1 Period of Performance: The period of performance for the contract/order shall be five years; a one year basic with four one year options.

4.1.2 Place of Performance: These services shall be performed at contractor facility.

4.2 Engineering Support: When requested by 408 SCMS/GUEA or its appointed representative, the contractor shall provide support either by telephone or email to resolve problems encountered by field personnel concerning the operation and use of the TISS with respect to the ALR-56C. All transactions will be documented in the Monthly Status Report. (CDRL A001, DI-MGMT-80368A, Status Report).

4.3 Engineering Investigations: The contractor shall provide support to resolve problems encountered while using AN/ALR-56C TPS on the TISS. The support will include DR investigations and resolutions, resolution selloff, preparation of software updates, recommended Technical Order (TO) or Interface Test Adapter (ITA) changes and technical documentation.

4.4 Deficiency Reports: The contractor shall analyze deficiency reports submitted by 408 SCMS/GUEA or its appointed representative and provide a Report of Findings (ROF) to AFLCMC/WNYECB and 408 SCMS/GUEA within ten business days of receipt of submission or receipt of exhibit if required (CDRL A002 DI-MISC-80508B, Technical Report Study/Services). Status/update of investigation shall be provided to AFLCMC/WNYECB, 408 SCMS/GULB and 408 SCMS/GUEA via the Monthly Status Report (CDRL A001, DI-MGMT-80368A, Status Report).

4.5 Incorporation of DR Resolution into TPS: After receiving approval by 408 SCMS/GUEA or the appointed representative, the contractor shall perform/incorporate the preferred solution identified in the ROF. The contractor shall also develop a test plan defining how the resultant product will be tested. The test plan shall be delivered to AFLCMC/WNYCC/WNYECB and 408 SCMS/GUEA. (CDRL A003, DI-NDTI-80566A, Test Plan).

4.6 TPS Selloff: Once the solution has been incorporated into the TPS, and the test plan has been approved, the contractor shall perform a selloff using the approved test plan. The selloff shall be performed at the contractor’s facility. The contractor shall notify the 408 SCMS/GUEA and AFLCMC/WNYCC/WNYECB 30 calendar days prior to the test date, to allow for Government observation/participation. Upon completion of a selloff, the contractor shall prepare and submit a test report to AFLCMC/WNYCC/WNYECB and 408 SCMS/GUEA. Acceptance of the Test Report by 408 SCMS/GUEA or its appointed representative shall imply concurrence with the product thus far and indicate the contractor shall continue with TPS delivery. (CDRL A004, DI-NDTI-80809B, Test Report).

4.7 TPS Delivery: Upon successful completion of Selloff, the updated software, including all documentation related to the TPS (source code, executable code, Version Description Documents, Test Requirements Documents, Software Specifications (if changed) and Software Confidence Test Report), shall be delivered. The TPS shall be updated to test LRUs and SRUs that had Deficiency Reports (DR) for AN/ALR 56C RWR. There should not be more than 2 test failures within a quarter (CDRL A005, DI-MCCR-80700/T, Computer Software Product End Item). Any recommended changes to the TOs and/or any recommended hardware change(s) to the Interface Test Adapter (ITA) shall also be delivered (CDRL A006, DI-MISC-80508B, Technical Report-Study/Services).

4.8 Data Accession List (DAL): All data and software developed under this task shall become property of the Government. The contractor shall provide a DAL listing all data and software developed by the contractor in accomplishment of this task. The contractor shall provide the Government access to any of this data or software at the request of the Government. The Government's access to the contractor's data is not limited to that contained in the DAL. (CDRL A007, DI-MGMT-81453A, Data Accession List).

4.9 Status Reports: The contractor shall provide technically accurate monthly status reports detailing work accomplished and progress achieved for tasks performed during that period. The report shall include schedules (projected vs. actual), work accomplished during the reporting period, man-hours (projected vs. expended), technical problems, technical progress, funds expended, funds remaining and any other data the contractor deems relevant. The contractor submitted monthly status reports shall be technically accurate and complete with no more than one technical error and no more than five typographical errors. Errors must be corrected and the report shall be resubmitted to the Government No Later Than (NLT) 15 working days after receipt of Government comments. This report shall be made available to AFLCMC/WNYECB, 408 SCMS/GULB and 408 SCMS/GUEA. (CDRL A001, DI-MGMT-80368A, Status Report).

4.10 Management Plan: The contractor shall establish a single point of contact for the overall effort of this task. This individual will interface with the Government program manager to determine specific support requirements, coordinate task support activity, and deliver all task deliverables in accordance with (IAW) the CDRLs.

4.11 Contractor Travel: No Contractor travel shall be required to perform this task.

5.0 General Information.

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

5.2 Security Requirements

Knowledge and/or generation of classified information and/or Controlled Unclassified Information (CUI) are required for performance of the contract/order. The Contractor shall ensure applicable Contractor personnel have security clearances at the SECRET level.

5.2.1 Government Security Regulations: The contractor shall ensure personnel, information system, property and facility, security requirements are met. The contractor shall comply with Government Security regulations including DoD 5200.2-R, Personnel Security Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM); DoDD 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual; and AFI 31-101, Integrated Defense.

5.2.2 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 ensure compliance with DoDD 5205.02E, DoD Manual 5205.02-M, and other applicable Government security regulations including procedures to protect classified and/or controlled unclassified information, Government projects and/or programs.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or 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.4 Security Clearance: The Contractor shall ensure applicable Contractor personnel have security clearances at the Secret level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified and/or controlled unclassified information. Contractor inability to obtain and/or maintain proper employee security clearance shall not constitute an excusable delay in contract performance..

5.2.5 Security Incident or Violation: The Contractor shall immediately notify the Facility and/or Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified and/or controlled unclassified information.

5.2.6 Security of Contractor System(s): The Contractor shall ensure the security of automated information systems at the Contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified and/or controlled unclassified information.

5.2.7 Access to government System(s): Access to Government systems(s) will not be required to perform tasks under the contract/order.

5.3 Environmental Management System (EMS): Services will be performed at the contractor’s facility; therefore, the local EMS requirements do not apply to this effort. This statement does not exempt the Contractor from any other Federal, State or local statute or requirement.

5.4 Green Procurement Program (GPP): Green Procurement Program (GPP): Under Secretary of Defense (USD) Memorandum, Establishment of the DoD Green Procurement Program, dated August 27 2004, establishes the requirement for a GPP. Green procurement is the purchase of environmentally preferable products and services and shall be managed in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). OSHA and ESOH requirements shall be incorporated into the Contractor’s safety program.

5.5.2 Voluntary Protection Program (VPP): The USAF is a participant in the OSHA VPP. Contractor personnel performing work on a USAF installation shall participate in the local VPP. Additional information regarding VPP is available at the site below.

http://www.osha.gov/dcsp/vpp/index.html

5.5.3 Mishap Notification/Investigation: In accordance with AFI 91-204, Safety Investigations and Reports, the Contractor shall report mishaps involving damage or injury to USAF interests. The Contractor shall ensure the USAF is notified of mishaps. The Contractor shall contact the Contracting Officer’s Representative (COR), if available, or another MFT member by telephone within four business hours and the Contractor shall cooperate with USAF safety investigations.

5.6 Inspection of Services: Inspection of Services will be accomplished in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government reserves the right to inspect Contractor performance.

5.7 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

5.8 Contract Manpower Reporting

5.8.1 In accordance with the Secretary of the Air Force for Acquisition (SAF/AQ) Memorandum, Implementation of FY11 NDAA [National Defense Authorization Act] Section 8108 [of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Act, 2011], Contractor Inventory, dated Nov 13 2012, the Contractor shall provide an annual count of Contractor personnel performing work if the DoD is the requiring activity, if the acquisition is using U.S. Government appropriated funds, and if the acquisition is equal to or greater than the Simplified Acquisition Threshold (SAT).

5.8.2 In accordance with the Office of the Secretary of Defense (OSD) Memorandum, Enterprise-wide Contractor Manpower Reporting Application, dated Nov 28 2012, the Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract at the Enterprise-wide Contract Manpower Reporting Application (eCMRA) site below. Reporting shall be conducted for each fiscal year (FY), which extends October 1 through September 30. While inputs may be made any time during the FY, all data shall be reported no later than October 31 of the following FY. The Contractor may direct questions to the help desk at the eCMRA site:http://www.ecmra.mil

5.9 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area Work Flow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) in accordance with all applicable clauses located in the basic contract. Acceptance will be performed by the Engineer.

6.0 Appendices.

6.1 Appendix A, References.

reissued 8 April 2013 http://www.e-publishing.af.mil/

Paragraphs

1.3.1.1, 2.4.6.1.1-

2.4.6.1.2

certified current 6 January 2012 http://www.e-publishing.af.mil/

Pages 7-9

Version 2

September 2012 http://www.acq.osd.mil/dpap/ccap/cc/corhb/Files/DCCOR_Handbook_2012.pdf

Section on Combating Trafficking in Persons in Chapter 8, Monitoring the Contractor

Change 1 - 2/12/1990

Change 2 - 7/14/1993

Change 3 - 2/23/1996 http://www.dtic.mil/whs/directives/corres/pub1.html

Entire

http://www.dtic.mil/whs/directives/corres/pub1.html

Entire

Entire

Entire

Sections applicable to contract and PWS

Nov 28 2012 http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf

Entire

as amended through January 1, 2004 http://www.osha.gov/pls/oshaweb/owadisp.show_document?p_id=2743&p_table=OSHACT

Entire

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5337/2012-11-13_saf-aq-memo.pdf

Entire

August 27 2004 http://www.wbdg.org/pdfs/dod_gpp_082704.pdf

Entire

6.2 Appendix B: Report Of Findings Form

Report of Findings Form

UUT Name:

UUT Type: (Analog/RF, Digital, Hybrid)

CPIN:

Rev:

Rev Date:

DR, MIP, etc #:

Investigator:

Report Date:

Test Station:

Number of Modules

Number of Effected Modules

Size of Source Code

UUT Run Time

Test language of effected Modules (ATLAS, CVI, LASAR, etc).

UUT Complexity

ITA Set Complexity

Tester Complexity

Software Complexity

Note: Complexity levels are Simple, Medium, Complex, and Very Complex.

Details of Problem:

Recommended Solution:

Assumptions:

Estimated Hours to Complete:

Materials Required:

Estimated Material Costs:

Material Lead Times:

TDY Required:

TDY Justification:

Estimated TDY Costs:

Documentation Changes:

Hardware Changes:

Comments:

Date:

Date:

Estimated Date of Completion:

Disapproved

PR: FD2060-16-00014 PWS