PWS_Technical_Support_for_Avionic_Subsystems_23_Apr_14.docx

DOCX document 74 KB Posted

Attached to
F-16 Operational Flight Program Support Federal contract opportunity
Solicitation number
FA8224-14-R-0110
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Hill Air Force Base

About this file

PWS 23 April 2014 Basic

View the file

Other files for this federal contract opportunity

Other files attached to F-16 Operational Flight Program Support, newest first.
File Type Posted
Redacted_J A.pdf PDF
PWS_Technical_Support_for_Avionic_Subsystems_Task_Order_1_23_Apr_14.docx DOCX document
ESA_CDRL_A003_A004_ESA_signed.pdf PDF
FA8224-14-R-0110_Solicitation.doc DOC document
ESA_CDRL_A001_A002_signed.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE-BASED

WORK STATEMENT

FOR

Technical Support for Avionic Subsystems

309th Software Maintenance Group

Hill AFB, UT

(518 SMXS)

23 April 2014

Table of Contents

SECTION 1 – PURPOSE3
SECTION 2 – SCOPE3
SECTION 3 – ENGINEERING AND TECHNICAL SUPPORT3
SECTION 4 – SERVICES SUMMARY4
SECTION 5 – GENERAL INFORMATION4
SECTION 6 – APPENDICES4

1.0 Purpose

1.1. The purpose of this Performance Based Work Statement (PWS) is to acquire technical assistance required to support aircraft wiring modification, subsystem hardware modification, and Operational Flight Program (OFP) software modification specific to the Commercial Central Interface Unit (CCIU), Commercial Data Entry Electronics Unit (CDEEU), Digital Video Recorder (DVR), Advanced Color Programmable Display Generator (ACPDG) and the Advance Color Multi-Function Display (ACMFD). Technical assistance will support capability upgrade preliminary design, leading to critical design, trial verification installation, manufacturing and test, and, if needed, follow-on production support.

2.0 Scope

2.1. 518 SMXS/MXDED requires F-16 on-call technical support for the OFP, Board Support Package (BSP), and hardware changes in the CCIU, CDEEU, DVR, ACPDG and ACMFD that will support capability upgrades development. In addition, technical expertise on the internal and external components of the CCIU, CDEEU, DVR, ACPDG and ACMFD Line Replaceable Unit(s) (LRUs) may be required to support aircraft wiring design and implementation. In addition to the primary support location at Hill AFB, Utah, the Contractor shall be available to provide on-call technical support to the Air National Guard Air Force Reserve Test Centers (AATC Tucson, AZ; Edwards AFB, CA; Eglin AFB, FL; and Nellis AFB, NV).

3.0 Engineering and Technical Support

3.1. On call tasking and reporting requirements of this contract are accomplished through the Government Representative (GR) or alternate. The Contractor shall provide on-call technical support as requested by the Government. The on-call technical support shall be provided during normal business hours and at other times with 48 hours’ notice as requested by the GR. Acknowledgement of Government need will be provided within one (1) business day. Phone support through conference call shall be provided within forty-eight (48) hours of Government notification. If technical support is too complex for a 48-hour turn around, the Contractor shall provide notification that support will not be available within 24 hours and provide estimated timetable for assistance. On-call technical services request by the Government and response from the Contractor shall be via telephone or e-mail.

3.1.1. The Contractor shall provide on-call technical support on five (5) separate aircraft subsystems as required to support aircraft wiring modification, subsystem hardware modification, and software modification specific to the following:

· Commercial Central Interface Unit (CCIU)

· Commercial Data Entry Electronics Unit (CDEEU)

· Digital Video Recorder (DVR)

· Advanced Color Programmable Display Generator (ACPDG)

· Advance Color Multi-Function Display (ACMFD)

3.2. Status Reports

The Contractor shall provide a monthly status report summarizing work performed according to paragraphs 3.1, 3.4.1.1 through 3.4.1.7. Report is due by the tenth (10th) day of the following month. (CDRL A004)

3.3. Review Meetings

The Contractor shall attend and participate in program management reviews, information briefings, or other meetings as requested by the GR. Meeting minutes shall be submitted to the GR or alternate, fifteen (15) days after meeting is held. Unless determined otherwise, the maximum amount of attendance requiring travel shall be no more than four (4) per year. (CDRL A003)

3.4. Additional Engineering and Technical Services

3.4.1. Technical support shall include the following activities on a separately priced Task Order:

3.4.1.1. The Contractor shall provide answers to questions concerning operation of software running in the contractor supplied system. (CDRL A004)

3.4.1.2. The Contractor shall recommend software code change to alter operation of the system as described by the GR. (CDRL A004)

3.4.1.3. The Contractor shall recommend test procedures to help resolve malfunctions that have been identified in the system. (CDRL A004)

3.4.1.4. The Contractor shall recommend software code changes to implement an additional function of the system that has been identified by the GR. (CDRL A004)

3.4.1.5. The Contractor shall generate new software for applicable systems in order to satisfy requirements identified by the GR. The software is to be delivered as determined by the GR. (CDRL A001)

3.4.1.6. The Contractor shall supply Version Description Documents (VDD), Software Design Documents (SDD), Software Requirements Specification (SRS), Interface Control Documents (ICD), and User Manuals for software operating in the system as requested by GR. The Contractor shall also supply any updates to the above as requested by GR. The contractor shall deliver documents and updates as determined by the GR. (CDRL A002)

3.4.1.7. The Contractor shall supply other engineering services in support of this PWS on separately defined and priced Task Orders. The contractor shall deliver documents and updates as determined by the GR. (CDRL A002) Software Testing The contractor shall attend software testing accompanied by a government representative, as requested by the GR. (CDRL A001 and A002)

4.0 Services Summary (SS)

Performance Objective
PWS Para
Performance Threshold
The contractor shall generate new software for applicable systems in order to satisfy requirements identified by the GR.
3.4.1.5 and 3.4.2
The software is to be delivered as determined by the GR. (CDRL A001)

The contractor shall supply Version Description Documents (VDD), Software Design Documents (SDD), Software Requirements Specification (SRS), Interface Control Documents (ICD), and User Manuals for software operating in the system as requested by GR. The contractor shall also supply any updates to the above as requested by GR

3.4.1.6, 3.4.1.7 and 3.4.2
The contractor shall deliver documents and updates as determined by the GR. (CDRL A002)
The contractor shall attend and participate in program management reviews, information briefings, or other meetings as requested by the GR.
3.1 and 3.3

Meeting minutes shall be submitted to the GR or alternate, fifteen (15) days after meeting is held. (CDRL A003)

The Contractor shall provide a monthly status report summarizing work performed according to paragraphs 3.1, and 3.4.1.1 through 3.4.1.7.

3.1, 3.4.1.1 through 3.4.1.7
Report is due by the tenth (10th) day of the following month. (CDRL A004)

5.0 General Information

5.1. Security Requirements

Contractor shall not release or remove system documentation, data, or reports generated by or through use of Government systems. The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID’s, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. All requests for information shall be forwarded to 518 SMXS/MXDED. The 518 SMXS/MXDED or the Government Program Manager will assist Contractor in processing the necessary DoD forms to obtain base or area badges for access to Government facilities.

5.2. Travel. The Contractor may be required traveling to support the objectives of this PWS. The allowable baseline for airfare cost is the “lowest priced airfare available to the Contractor as outlined in FAR 31.205-46(b) & (c). The Contractor shall obtain Contracting Officer approval/authorization prior to all travel. The Contractor is responsible for making all necessary travel arrangements.

5.3. Data Rights. The government shall have unlimited rights to all intellectual property created by the contractor, and/or its subcontractor, under this contract. The government may use such items for any other purpose as stated in the Defense Federal Acquisition Regulation Supplement (DFARS) definition of “unlimited rights”.

5.4. Manpower Labor Reporting

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract as a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk at http://www.ecmra.mil.

Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

Contractor shall use the Unit Identification Code (UIC): FF5120.

6.0 Appendices

APPENDIX A

ACRONYMS AND ABBREVIATIONS

AATC
Air National Guard Air Force Reserve Test Centers
ACMFD
Advance Color Multi-Function Display
ACPDG
Advance Color Programmable Display Generator
AFMC
Air Force Materiel Command
BSP
Board Support Package
CCIU
Commercial Central Interface Unit
CDEEU
Commercial Data Entry Electronics Unit
CDRL
Contract Data Requirements List
CRMA
Contractor Manpower Reporting Application
DFARS
Defense Federal Acquisition Regulations Supplement
DoD
Department of Defense
DVR
Digital Video Recorder
FY
Fiscal Year
GR
Government Representative
HAFB
Hill Air Force Base
ICD
Interface Control Documents
LRU
Line Replaceable Unit
OFP
Operational Flight Program
PWS
Performance-Based Work Statement
SDD
Software Design Documents
SRS
Software Requirements Specification
UIC
Unit Identification Code
VDD
Version Description Documents

image1.png

File details come from the government source that posted it. Updated .