PWS_15-00040.pdf

PR: FD2060-15-00040 PWS REVISION: 0 1

Performance-based Work Statement for

AN/ALR-56C Test Program Set Support

On The

AN/ALM-246 TISS

Date 10 October 2014

1.0 Description of Services.

1.1 Objective(s). This performance 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.2 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 overt 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.

PR: FD2060-15-00040 PWS REVISION: 0 2

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 called the 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 thoughly, 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 charateristics distribution. As a result, parameter limits and/or test approaches have to be changed.

1.3 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 may include the maintenance of the test fixtures, DR resolutions, preparation of software updates, and technical documentation.

The contractor shall provide on-site maintenance and support for the TPS (hardware and software) associated with AN/ALM-205B, DTS-70, Agilent 3070, and Versatile Depot

Automatic Test Station (VDATS) test stations. Contractor shall identify verticality issues within

SRU/LRU testing (to include the TEWS Intermediate Support Station [TISS]) and recommend required changes.

2.0 Services Summary.

Table 1 shows the services summary.

Performance Objective PWS

Reference

Performance Threshold

Document the Status, Contractor Progress and

Contractor Travel in monthly reports.

4.8

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.

Analyze deficiency reports submitted, provide a Report of

Findings and perform preferred solution identified in the ROF.

4.3 A Report of Findings must be

submitted within ten business days of being notified of the issue or receipt of exhibit if required.

TPS Upgrade 4. and 4.3 The TPS shall be updated to test LRUs and SRUs that had Deficiency Reports

(DR) for AN/ALR 56C RWR. There should not be no more than 2 test failures within a quarter. Failures should be documented within the ROF.

Table 1: Services Summary

PR: FD2060-15-00040 PWS REVISION: 0 3

3.0 Government Property and Services.

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

http://farsite.hill.af.mil

3.2 Government Property to be Provided. Government property to be provided includes 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 Attachment B for Government Property Listing.

GOVERNMENT FURNISHED PRODUCTS (GFP)

The contractor is authorized on a no cost, non-interference basis, the use of Government owned equipment and specialized test equipment located at the contractor facility. The following GFP items will be required during the execution of this activity. The attached listing of GFP items will be used to enhance the updating of the TPS for TEWS Intermediate Support Station (TISS).

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 http://farsite.hill.af.mil/ http://www.dcma.mil/aboutetools.cfm

PR: FD2060-15-00040 PWS REVISION: 0 4

condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All materials generated under the contract becomes 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. This contract will be for 12 Months.

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, see section 6) to AFLCMC/WNYECB and 408 SCMS/GUEA within ten business days of receipt of submission or receipt of exhibit if required. ROF shall be delivered to AFLCMC/WNYCC/WNYECB and 408 SCMS/GUEA in accordance with section 6.2 Appendix B and (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).

PR: FD2060-15-00040 PWS REVISION: 0 5

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 . A test plan shall 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 thirty (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. Any recommended changes to the TOs and/or any recommended hardware change(s) to the Interface Test Adapter (ITA) shall be delivered. (CDRL A005, DI-MCCR-80700, Computer Software Product End Item, 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

PR: FD2060-15-00040 PWS REVISION: 0 6

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.

5.1.1 Definition of Mission-Essential Services: In accordance with DFARS 252.237-

7023(a)(1), Continuation of Essential Contractor Services, “ ‘Essential contractor service’ means a service provided by a firm or individual under contract to DoD to support mission-essential functions, such as support of vital systems, … associated support activities, … and similar services provided to foreign military sales customers under the Security Assistance Program.

Services are essential if the effectiveness of defense systems or operations has the potential to be seriously impaired by the interruption of these services, as determined by the appropriate functional commander or civilian equivalent.”

5.1.2 Designation of Services as Mission-Essential: In accordance with DFARS 237.7602(a), The Continuation of Essential Contractor Services / Policy, DFARS 252.237-7023(a)(2), and

Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, the Functional Commander (FC) 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 performance of the contract/order. The

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

5.2.2 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, but not limited to, DoD 5220.22-M, National

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

Security (OPSEC) Program Manual.

PR: FD2060-15-00040 PWS REVISION: 0 7

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 ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-M to protect U.S.

Government interests.

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 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 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 information and/or CUI and classified items.

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 including potential or actual unauthorized disclosure or compromise of classified information and/or CUI.

5.3 Environmental Management System (EMS)

5.3.1 Applicability. These services shall be performed only at the Contractor’s facility;

therefore, the EMS requirement does not apply.

5.4 Green Procurement Program (GPP)

5.4.1 Under Secretary of Defense (USD) Memorandum, Establishment of the DoD Green

Procurement Program, dated August 27 2004, establishes the requirement for a GPP. The GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally-preferable products and services. In accordance with FAR 23.404, Agency

Affirmative Procurement Programs, the GPP requires 100% of purchases of Environmental

Protection Agency (EPA)-designated products, included in the Comprehensive Procurement

Guidelines (CPG) list, contain recovered materials unless the item cannot be acquired competitively within a reasonable timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price. In accordance with FAR 23.101, Sustainable Acquisition Policy /

Definition, the GPP requirement applies to all acquisitions, including services, using U.S.

Government appropriated funds.

5.4.2 The prime Contractor shall ensure subcontractors comply with the GPP requirement.

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

PR: FD2060-15-00040 PWS REVISION: 0 8

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

5.5.3.1 In accordance with AFI 91-204, Safety Investigations and Reports, paragraph 2.4.6.1.1, the Contractor shall report mishaps involving damage or injury to USAF interests. In accordance with AFI 91-204, paragraph 1.3.1.1, damage or injury includes: 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 USAF operations.

5.5.3.2 In accordance with AFI 91-204, paragraph 2.4.6.1.1, the Contractor shall ensure the

USAF [Safety Office] and the applicable contract management authority are notified of mishaps.

The Contractor shall contact the MFT [Contracting Officer’s Representative (COR), if available, or another MFT member] by telephone within 48 business hours. The MFT will notify the

Safety Office and the PCO.

5.5.3.3 In accordance with AFI 91-204, paragraph 2.4.6.1.2, the Contractor shall cooperate with

USAF safety investigations.

5.5.4 Safety and Health Plan

5.5.4.1 The Contractor shall submit a Safety and Health Plan to the PCO prior to contract (basic or order, as applicable) award. The MFT will forward the plan and this PWS to the Safety

Office. In accordance with Air Force Pamphlet (AFPAM) 91-210, Contract Safety, paragraph

6.4, the Safety Office will review the plan and this PWS to determine if safety requirements are correctly addressed. The Contractor shall establish and maintain a safety program in accordance with OSHA, ESOH, the contract/order Appendix C (Industrial Safety Requirements), and the

Safety and Health Plan.

5.5.4.2 If, during the performance of the contract/order, revision to the Contractor’s Safety and

Health Plan become necessary, the Contractor shall inform the PCO. If required by the

Government, the Contractor shall submit a revised plan to the PCO. The same process of review and negotiation, if applicable, involved in the original submission will apply to any revision submitted after contract/order award. Any revision to the Safety and Health Plan must be reviewed by the Safety Office.

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

PR: FD2060-15-00040 PWS REVISION: 0 9

5.6 Inspection of Services

5.6.2 In accordance with FAR 52.246-5, the Contractor shall maintain an inspection process acceptable to the Government. The Contractor and shall maintain records of inspections which shall be made available to the Government as long as the contract requires.

5.7 Trafficking in Persons

5.7.1 The Contractor shall comply with FAR 52.222-50, Combating 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 below.

http://www.state.gov/j/tip

5.7.2 In accordance with the Defense Contingency COR Handbook section on Combating

Trafficking in Persons, the COR must inform the PCO if the Contractor fails to comply with the requirements of FAR 52.222.50. The PCO must convey the information to DoD Combat

Trafficking in Persons (CTIP) Law Enforcement and Support / Office of Under Secretary of

Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).

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) [currently $150,000.00].

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

http://www.ecmra.mil

5.9 Invoicing/Payment and Receipt/Acceptance

5.9.1 In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports, the Contractor shall submit/process payment requests (invoices, http://www.state.gov/j/tip http://www.ecmra.mil/

PR: FD2060-15-00040 PWS REVISION: 0 10

Receiving Reports or combos) and receipt/acceptance documents via Wide Area Workflow

(WAWF). Additional information regarding WAWF is available at the site below.

https://wawf.eb.mil

5.9.2 CDRL deliverables may be submitted using WAWF or be submitted directly to the applicable MFT member in accordance with the CDRL. The CDRL will determine submittal requirements; however, separately priced data must be accepted in WAWF in order for the

Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order for the contract line item to be closed out.

5.9.3 Services will be accepted by the Program Manager or Engineer.

6.0 Appendices.

6.1 Appendix A, References.

Publication Title of

Publication

Date of Publication Section(s) that Apply

AFI 10-403 Deployment

Planning and

Execution

20 September 2012

Change 1 – 29 April 2013 http://www.e-publishing.af.mil/

Paragraph

1.9.1.33

AFI 91-204 Safety

Investigations and

Reports

9 August 2012 reissued 8 April 2013

Paragraphs

1.3.1.1, 2.4.6.1.1-

2.4.6.1.2

AFMC/CV Policy

Letter

Conformance with

Air Force

Environmental

Management

System (EMS)

Requirements for

Contracts

Performed on Air

Force Installations

1 Aug 07

Entire

AFPAM 91-210 Contract Safety 14 February 1994 certified current 6 January 2012

Pages 7-9

Assistant

Secretary of the

Conformance with

Air Force

11 Dec 06 Entire https://wawf.eb.mil/ http://www.e-publishing.af.mil/

PR: FD2060-15-00040 PWS REVISION: 0 11

Air Force Policy

Letter

Environmental

Management

System (EMS)

Requirements for

Contracts

Performed on Air

Force Installations

None Defense

Contingency COR

Handbook

Version 2

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

Section on

Combating

Trafficking in Persons in

Chapter 8, Monitoring the

Contractor

DoD 5200.2-R Personnel Security

Program

1/1/87

Change 1 - 2/12/1990

Change 2 - 7/14/1993

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

1.html

DoDD 4715.1E Environmental, Safety, and

Occupational

Health (ESOH)

March 19, 2005

DoDD 5205.02E DoD Operations

Security (OPSEC)

June 20, 2012

DoD Manual

5205.02-M

DoD Operations

Security (OPSEC)

Program Manual

November 3, 2008

E.O. 13423 Strengthening

Federal

Environmental, Energy, and

Transportation

Management

January 24, 2007 http://www.gpo.gov/fdsys/pkg/FR-2007-01-

26/pdf/07-374.pdf

E.O. 13514 Federal

Leadership in

Environment, 5 October 2009 http://www.whitehouse.gov/assets/documents/ http://www.acq.osd.mil/dpap/ccap/cc/corhb/Files/DCCOR_Handbook_2012.pdf http://www.acq.osd.mil/dpap/ccap/cc/corhb/Files/DCCOR_Handbook_2012.pdf http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.gpo.gov/fdsys/pkg/FR-2007-01-26/pdf/07-374.pdf http://www.gpo.gov/fdsys/pkg/FR-2007-01-26/pdf/07-374.pdf http://www.whitehouse.gov/assets/documents/2009fedleader_eo_rel.pdf

PR: FD2060-15-00040 PWS REVISION: 0 12

Energy, and

Economic

Performance

2009fedleader_eo_rel.pdf

FAR and supplements

Federal

Acquisition

Regulation http://farsite.hill.af.mil

Sections applicable to contract and

PWS

OSD

Memorandum

Enterprise-wide

Contractor

Manpower

Reporting

Application

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

Public Law 91-

Occupational

Safety and Health

Act of 1970

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

SAF/AQ

Memorandum

Implementation of

FY11 NDAA

Section 8108, Contractor

Inventory

Nov 13 2012 https://cs.eis.af.mil/airforcecontracting/knowledge

_center/Documents/AFFARS_Library/5337/2012-

11-13_saf-aq-memo.pdf

USD

Memorandum

Establishment of the DoD Green

Procurement

August 27 2004 http://www.wbdg.org/pdfs/dod_gpp_082704.pdf http://www.whitehouse.gov/assets/documents/2009fedleader_eo_rel.pdf http://farsite.hill.af.mil/ http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.acq.osd.mil/dpap/policy/policyvault/Enterprise-wide_Contractor_Manpower_Reporting_Application_memorandum.pdf http://www.osha.gov/pls/oshaweb/owadisp.show_document?p_id=2743&p_table=OSHACT http://www.osha.gov/pls/oshaweb/owadisp.show_document?p_id=2743&p_table=OSHACT http://www.wbdg.org/pdfs/dod_gpp_082704.pdf

PR: FD2060-15-00040 PWS REVISION: 0 13

Include the following if referenced.

Publication Title of

Publication

Date of Publication Sections that

Apply

AFI 31-113 Installation

Perimeter Access

Control

26 Jan 2012

AFI 31-401 Information

Security Program

Management

1 November 2005

Change 1 - 19 August 2009

AFJI 63-108 Government-

Industry Data

Exchange

Program (GIDEP)

15 May 1980

AS5553A

Fraudulent

/Counterfeit

Electronics Parts;

Avoidance, Detection, Mitigation, and

Disposition

Revision A

2013-01-21 none Department of

Defense Guide to

Uniquely

Identifying Items

Assuring

Valuation, Accountability and Control of

Government

Property, Version 2.5

September 15, 2012 www.acq.osd.mil/dpap/UID/attachments/DoD

UIDGuideVer2_5.pdf

DoDI 1100.22 Policy and

Procedures for

Determining

Workforce Mix

April 12, 2010

Enclosure 2, paragraph 5.b

DoDI 5200.01 DoD Information

Security Program and Protection of

Sensitive

Compartmented

Information

October 9, 2008

Change 1 - 13 Jun 2011 http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/ http://www.acq.osd.mil/dpap/UID/attachments/DoDUIDGuideVer2_5.pdf http://www.acq.osd.mil/dpap/UID/attachments/DoDUIDGuideVer2_5.pdf http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html

PR: FD2060-15-00040 PWS REVISION: 0 14

DoDM 5200.01 DoD Information

Security Program:

Overview, Classification, and

Declassification

February 24, 2012

Volume 1

DoD 5220.22-M

National Industrial

Security Program

Operating Manual

(NISPOM)

February 28, 2006

Change 1 - March 28, 2013

GIDEP

Operations

Manual S0300-

BT-PRO-010

Government-

Industry Data

Exchange

September 2009 http://www.gidep.org/

Chapter 2, Participation

Requirements

JTR The Joint Travel

Regulations /

Volume 2 /

Department Of

Defense

Civilian Personnel

10/01/12 http://www.defensetravel.dod.mil/site/travelre g.cfm

Volume 2

MIL-HDBK-263B Military

Handbook:

Electrostatic

Discharge (ESD)

Control Handbook for Protection of

Electrical And

Electronic Parts, Assemblies, and

Equipment

(Excluding

Electrically

Initiated

Explosive

Devices)

31 July 1994 Entire

MIL-STD-129P Department of

Defense /

Standard Practice

/ Military Marking for Shipment and

Storage

15 December 2002

Change 1 - 15 January 2004, Change 2 - 10 February 2004, Change 3 - 29 October 2004, Change 4 - 19 September 2007 http://www.acq.osd.mil/log/sci/ait/MIL-STD-

129PCH4.pdf

MIL-STD-130N Department of 17 December 2007 Entire http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.gidep.org/ http://www.defensetravel.dod.mil/site/travelreg.cfm http://www.defensetravel.dod.mil/site/travelreg.cfm http://www.acq.osd.mil/log/sci/ait/MIL-STD-129PCH4.pdf http://www.acq.osd.mil/log/sci/ait/MIL-STD-129PCH4.pdf

PR: FD2060-15-00040 PWS REVISION: 0 15

Defense /

Standard Practice

/ Identification

Marking of U.S.

Military Property

Change 1 – 16 November 2012 http://www.acq.osd.mil/dpap/pdi/uid/docs/MI

L-Std130N_Ch1.pdf

MIL-STD-2073-

1D

Department of

Defense /

Standard Practice for Military

Packaging

15 December 1999, Notice 1, 10 May 2002

MIL-STD-147E Department of

Defense Standard

Practice /

Palletized Unit

Loads

16 May 2008

MIL-STD-1686C Department of

Defense Standard

Practice /

Electrostatic

Discharge Control

Program for

Protection of

Electrical and

Electronic Parts, Assemblies and

Equipment

(Excluding

Electrically

Initiated

Explosive

Devices)

25 Oct 1995

OI 31-001 Security Program

Management

20 Jan 2011 Entire

RAFB IDP

31-101

Robins Integrated

Defense Plan

January 2012 Entire http://www.acq.osd.mil/dpap/pdi/uid/docs/MIL-Std130N_Ch1.pdf http://www.acq.osd.mil/dpap/pdi/uid/docs/MIL-Std130N_Ch1.pdf

PR: FD2060-15-00040 PWS REVISION: 0 16

6.2 Appendix 2: 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:

PR: FD2060-15-00040 PWS REVISION: 0 17

Estimated Hours to Complete:

Materials Required:

Estimated Material Costs:

Material Lead Times:

TDY Required:

TDY Justification:

Estimated TDY Costs:

Documentation Changes:

Hardware Changes:

Comments:

Approved Project Manager

Signature:

DATE

Approved with

Action Items

Customer Signature: Date:

Estimated Date of

Completion:

Disapproved