PWS.pdf

PR: FD2060-18-30255 PWS REVISION: 0 1

Performance Based Work Statement

Situation Awareness Data Link

(Software Maintenance)

FD2060-18-30255

23 July 2018

Revision History

PR: FD2060-18-30255 PWS REVISION: 0 2

Number/Date History of Changes Revision 25 Jun 18 Original N/A

1.0 DESCRIPTION OF SERVICES

The Air Force Life Cycle Management Center, Common Avionics & Electronic Warfare

Division, Airborne Communications Element (AFLCMC/WNYBBA), hereafter “program office”, proposes the award of a long-term sole source contract for software maintenance of the

Situation Awareness Data Link/Enhanced Position Location Reporting System (SADL/EPLRS, SADL). This contract will provide software maintenance as required to include various types of receiver/transmitter units as currently fielded (RT-1719, RT-1720) and currently in development

(RT-1915, RT-1922.) The exact amount of software maintenance requirements are unknown due to the need for rapid remedial action in support of the warfighter.

2.0 SERVICES SUMMARY (SS)

Performance

Objective

PWS

Reference

Performance Threshold

Software

Sustainment

Support

5.2.1 Software products shall be marked and delivered IAW

the DD Form 1423 or equivalent. Delivered software products meet all requirements as specified by an agreed to Software Requirements Specification and contains fixes and/or enhancements agreed to by a Software

Configuration Control Board.

All software products must be accurate and complete with no more than one major deficiency and 5 minor deficiencies per software delivery.

All deficiencies must be responded to within 30 calendar days of notification.

User Support 5.1.1 Provide SADL-related technical support to the operational user. Respond to support requests received during non-business hours within one standard business day, excluding national holidays.

PR: FD2060-18-30255 PWS REVISION: 0 3

Deficiency

Report (DR)

Investigations

5.1.2 Investigate and identify root cause of SADL deficiency

reports IAW TO 00-35D-54. Provide initial response to program office within 5 calendar days.

3.0 GOVERNMENT PROPERTY 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:

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

3.2 Government-Furnished Property (GFP), including/Government-Furnished Equipment

(GFE), is authorized and will be managed in accordance with PWS paragraph 3.1.

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, inadequate storage, theft, 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:

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

3.4 Return of Government Property: All Government-Furnished Property (GFP) remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All GFP shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All property acquired or otherwise provided by the Contractor for accomplishment of contract/order requirements becomes the property of the Government and shall be returned to the Government upon http://farsite.hill.af.mil/ http://farsite.hill.af.mil/ http://www.dcma.mil/aboutetools.cfm http://www.dcma.mil/aboutetools.cfm

PR: FD2060-18-30255 PWS REVISION: 0 4

completion of the contract/order. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DD) Form 1423, Contract Data Requirements List

(CDRL), and deliverables become the property of the Government upon receipt.

3.5 Government Systems

3.5.1 The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract/order. The Contractor shall ensure Contractor personnel who require access to a Government Automated Information System (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 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.

3.5.2 Wide Area Workflow (WAWF)

3.5.2.1 In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports, the Contractor shall submit/process payment requests (invoices, Receiving Reports or combos) and receipt/acceptance documents using WAWF.

3.5.2.2 CDRL deliverables may be submitted using WAWF or be submitted directly to

Government personnel 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.

3.5.2.3 Contractor personnel shall register to access Wide Area Workflow-Receipt and

Acceptance (WAWF-RA) at: https://wawf.eb.mil/.

4.0 GENERAL INFORMATION

4.1 Continuation of Mission-Essential Services During a Crisis

4.1.1 Definition of Mission-Essential Services: In accordance with DFARS 252.237-7023(a), Continuation of Essential Contractor Services / Definitions, “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.”

4.1.2 Designation of Services as Mission-Essential: In accordance with DFARS 252.2377023(a) and Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph https://wawf.eb.mil/ https://wawf.eb.mil/

PR: FD2060-18-30255 PWS REVISION: 0 5

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.

4.2 Inspection of Services

4.2.1 In accordance with FAR 52.246-4, Inspection of Services – Fixed Price, and/or FAR

52.246-5, Inspection of Services - Cost-Reimbursement, the Government reserves the right to inspect Contractor performance.

4.2.2 In accordance with FAR 52.246-4 and/or FAR 52.246-5, the Contractor shall maintain an inspection process acceptable to the Government.

4.2.3 In accordance with FAR 52.246-4 and/or FAR 52.246-5, the Contractor shall maintain records of inspections which shall be made available to the Government as long as the contract requires.

4.3 Environmental Management System (EMS)

4.3.1 Executive Order (E.O.) 13423, Strengthening Federal Environmental, Energy, and

Transportation Management, and E.O. 13514, Federal Leadership in Environment, Energy, and

Economic Performance, establish the requirements for an EMS and obligate federal agencies to implement sustainable practices.

4.3.2 In accordance with the Secretary of the Air Force (SAF) Policy Letter, Conformance with

Air Force Environmental Management System (EMS) Requirements for Contracts Performed on

Air Force Installations, dated 11 Dec 06, and the Air Force Materiel Command/Vice Commander

(AFMC/CV) Policy Letter, Conformance with Air Force Environmental Management System

(EMS) Requirements for Contracts Performed on Air Force Installations, dated 1 Aug 07, Contractor personnel who perform work on any USAF installation shall comply with the EMS requirements established by the installation.

4.3.3 The prime Contractor shall ensure subcontractors comply with the EMS requirement.

4.4 Green Procurement Program (GPP)

4.4.1 The Under Secretary of Defense Memorandum, Establishment of the DoD Green

Procurement Program, dated August 27, 2004, establishes the requirement for a GPP. In accordance with FAR 23.101, Sustainable Acquisition Policy / Definition, the GPP requirement applies to all acquisitions, including services, using appropriated Government funds. 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

PR: FD2060-18-30255 PWS REVISION: 0 6

competitively within a reasonable timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.

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

4.5 Security Requirements

4.5.1 Knowledge and/or generation of classified and/or sensitive, but unclassified, information are required for performance of the contract/order. The Contractor shall ensure applicable

Contractor personnel have security clearances at the Secret level.

4.5.2 Government Security Regulations: The Contractor shall ensure personnel, information, system, facility, and international security requirements are met. The Contractor shall comply with Government Security regulations including, but not limited to, DoD 5200.2-R; 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 AFI 31-101, Integrated Defense.

4.5.3 Operations Security (OPSEC)

4.5.3.1 The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. Critical Information is defined as information about USAF missions or activities the adversary needs to achieve their goals.

4.5.3.2 The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-

M including procedures to protect classified and/or sensitive, but unclassified, Government projects and/or programs.

4.5.3.3 The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

4.5.4 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified and/or sensitive, but unclassified, information in accordance with DoD 5220.22-M. Applicable equipment shall be safeguarded, maintained, and operated in accordance with DoD 5220.22-M.

4.5.5 Security Clearance

4.5.5.1 The Contractor shall ensure applicable Contractor personnel have security clearances at the Secret level for proper accomplishment of contract/order requirements. Contractor personnel shall not be authorized access to classified and/or sensitive, but unclassified, information and/or materials or be permitted to work on classified and/or sensitive, but unclassified, projects and/or programs without a proper security clearance and a need-to-know.

PR: FD2060-18-30255 PWS REVISION: 0 7

4.5.5.2 The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. The Contractor shall ensure Contractor personnel submit a United States (U.S.) Office of Personnel Management

Standard Form 85P, Questionnaire For Public Trust Positions, (fingerprint card if available) to the Government Security Office.

4.5.5.3 Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified and/or sensitive, but unclassified, information.

4.5.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 and/or sensitive, but unclassified, information.

4.5.7 Access to Government System: The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract/order. The Contractor shall ensure

Contractor personnel who require access to a Government AIS have a DNACI conducted in accordance with DoD 5200.2-R. The Government will provide system access subject to approval of the DD Form 2875. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account will be closed.

4.5.8 Common Access Card (CAC): The Contractor shall ensure applicable Contractor personnel complete a DD Form 1172-2 (Application for Department of Defense Common

Access Card – DEERS Enrollment) to obtain a CAC required for performance of some of the tasks under the contract/order.

4.5.9 Access to Government Facility

4.5.9.1 The Contractor shall ensure Contractor personnel who require access to a Government facility comply with the security procedures of the facility.

4.5.9.2 If Contractor personnel require repeated access to a Government facility over the life of the contract/order, the Contractor shall ensure they complete, as applicable, a DD Form 1172-2 to obtain a CAC or an Air Force Materiel Command (AFMC) Form 496 (Application for AFMC

Identification Card) to obtain a Contractor identification card. The DD Form 1172-2 or AFMC

Form 496 shall be submitted to the PCO or as directed by AFLCMC/WNYBBA.

4.5.9.3 Upon completion/termination of the contract/order or transfer/termination of the

Contractor personnel, the CAC or Contractor identification card shall be returned to the PCO or as directed by AFLCMC/WNYBBA.

4.6 Safety and Health Requirements

PR: FD2060-18-30255 PWS REVISION: 0 8

4.6.1 Contractor Responsibility: The Contractor shall ensure all safety and health requirements are met. The Contractor is responsible for the safety and health of all Contractor and subcontractor personnel.

4.6.2 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596 as amended by Public Law 101-552, 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 and Health Program.

4.6.3 Mishap Notification/Investigation: In accordance with AFI 91-204, Safety Investigations and Reports, paragraph 2.12, the Contractor shall promptly report mishaps involving damage or injury to the USAF and cooperate with USAF safety investigations. The Contractor shall notify

Program Manager by telephone within four (4) hours. After regular duty hours, the Contract shall notify Robins AFB Command Post at 478 327-2612.

4.7 Packaging

4.7.1 The Contractor shall package replenishment spares and/or repair parts in accordance with the contract (basic or order, as applicable) AFMC Form 158, Packaging Requirements;

MILSTD-129P (4), Department of Defense Standard Practice / Military Marking for Shipment and

Storage; MIL-STD-130N, Department of Defense Standard Practice / Identification Marking of

U.S. Military Property; MIL-STD-2073-1D, Standard Practice for Military Packaging; and/or other applicable Government packaging requirements.

4.7.2 In accordance with MIL-STD-2073-1D, shipping containers, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reuse. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.7.3 The Contractor shall ensure that classified material is shipped in accordance with DoD

5220.22-M.

4.8 ITEM UNIQUE IDENTIFICATION (IUID) REQUIREMENTS: The IUID Program requires each qualifying USAF asset to be uniquely identified with a permanent marking that can sustain its information throughout the life of the asset. The program addresses two categories of assets—those already in the USAF inventory and those currently under contract but not currently in the USAF inventory. For assets under contract, IUID requirements are specified in DFARS

252-211.7003, Item Identification and Valuation and Department of Defense (DoD) 4100.39-M, Federal Logistics Information System (FLIS). All assets subject to marking must be recorded in the DoD IUID Registry. CDRL deliverables identified in paragraph 4.8.1 and 4.8.2 shall only be required when explicitly identified in a delivery order or when delivering assets with a value over

$5,000.

PR: FD2060-18-30255 PWS REVISION: 0 9

4.8.1 IUID Marking Plan. The Contractor’s IUID Marking Plan shall fully detail and document the strategy and scope to be used to meet MIL-STD-130N. The plan must be approved by

AFLCMC/WNYBBA prior to implementation. (DI-MGMT-81803, CDRL A004)

4.8.2 IUID Marking Activity and Verification Report. The contractor shall provide an IUID

Marking Activity and Verification Report. A key attribute for the report is the Verification column which indicates pass/fail for each item’s Data Matrix Symbol Quality. (DI-

MGMT81804A, CDRL A005)

4.9 Contract Manpower Reporting Requirement

4.9.1 In accordance with the SAF/AQ Memorandum, Implementation of FY11 NDAA Section

8108 [of Public Law 112-10 of the Department of Defense and Full-Year Continuing

Appropriations Act, 2011], Contractor Inventory, the Contractor shall provide an annual count of

Contractor personnel performing services for the DoD if the DoD is the requiring activity, if the acquisition is equal to or greater than the Simplified Acquisition Threshold (SAT) [currently

$150,000.00], and if the acquisition is using Government appropriated funds.

4.9.2 The Contractor shall report all Contractor labor hours, including subcontractor labor hours, required for performance of the services provided under the contract by accessing the Contract

Manpower Reporting Application (CMRA) site below and selecting the Department of the Air

Force option.

http://www.ecmra.mil

4.9.3 User manuals are available at the CMRA site.

4.9.4 Inputs shall be made for each Government Fiscal Year (FY) which extends from 1 October to 30 September. While inputs may be made any time during the FY, all data shall be reported no later than 31 October of the following FY.

4.9.5 Information from the CMRA site is considered to be proprietary in nature if the Contractor name and contract number are associated with the direct labor hours and direct labor dollars. At no time will data be released to the public with the Contractor name and contract number associated with the data.

4.10 Trafficking in Persons

4.10.1 The Contractor shall comply with FAR 52.222-50, Combating Trafficking in Persons.

Additional information about Trafficking in Persons is available at the Department of State’s

Office to Monitor and Combat Trafficking in Persons site at: http://www.state.gov/j/tip.

4.10.2 In accordance with the Department of Defense COR Handbook section on Combating

Trafficking in Persons, the COR(s) must inform the PCO if the Contractor/subcontractor and/or

Contractor/subcontractor personnel fail to comply with the requirements of FAR 52.222.50. The http://www.ecmra.mil/ http://www.ecmra.mil/ http://www.state.gov/j/tip http://www.state.gov/j/tip

PR: FD2060-18-30255 PWS REVISION: 0 10

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.0 SERVICES: This PWS defines the tasks required for software maintenance for SADL. The information contained in this section is not intended to be all inclusive or to detract from procedures outlined in specifications and over directives listed in the appendices of this PWS.

Workmanship shall be in accordance with contractor’s standard repair procedures and acceptance criteria in accordance with best industry practice.

5.1 Required Minimum Services: Required minimum services comprise the services that must be effectively performed for contract success in a constrained funding or operational environment.

5.1.1 User Support: Provide SADL-related technical support to the operational user.

5.1.1.1 This service includes operation of a help desk, platform integration support, maintaining the Radio Set Identification database, providing cryptographic support and training support as directed by the COR from the Contractor site. Respond to support requests received during nonbusiness hours within one standard business day, excluding national holidays.

5.1.1.2 The Contractor shall provide user support on Government sites in the realm of exercise/test support as directed by the COR. The Contractor shall provide any requests for support on Government sites to the COR for approval utilizing the travel approval procedures in

Paragraph 5.2.2.

Funding Type: Cost Plus Fixed Fee.

5.1.2 Deficiency Report (DR) Investigations: The contractor is responsible for investigating and identifying root causes of SADL deficiency reports in accordance with TO 00-35D-54. The contractor shall provide initial response to the program office within five business days. More than six DR investigations during a calendar year will require concurrence of the program office and the PCO.

5.2 Mission Enhancing Services: Mission enhancing services include those services which provide enhanced capabilities, repairs, and assistance but are undefined at this time. They will be coordinated, approved, and funded by the program office and the primary contracting officer prior to the beginning of the period of performance.

5.2.1 Software Support: Software products shall be marked and delivered IAW the DD Form

1423 or equivalent. Delivered software products shall meet all requirements identified or targeted for the Block Cycle Change and contains fixes and/or enhancements agreed to by a Software

Configuration Control Board.

PR: FD2060-18-30255 PWS REVISION: 0 11

5.2.1.1 All software products shall be accurate and complete with no more than one major deficiency and 5 minor deficiencies per software delivery. All deficiencies shall be responded to within 30 calendar days of notification.

Major Deficiency: Software does not correct a targeted deficiency of Urgent priority or higher, or leads to the submission of a new deficiency report submitted as defined by TO 00-35D-54.

Minor Deficiency: Software delivery does not correct a targeted deficiency of Routine priority, Watch Item, or agreed upon Software Problem Report, or causes a deterioration of system performance that does not lead to the submission of a new deficiency report, as defined by TO

00-35D-54.

5.2.1.2 Delivered software shall be designated and managed as Computer Software

Configuration Items (CSCIs) which will be established by the sustainment contractor. The contractor shall provide sustainment support to the government software manager on the software baseline. The software manager will assign CSCIs with a Computer Program

Identification Number (CPIN) for tracking CSCIs, CSCI changes, and customer requisition activities. The contractor and program office will adhere to requirements outlined in TO 00-5-16 for proper software distribution and release users under the Computer Program Identification

Number (CPIN).

5.2.1.3 Contractor shall provide engineering/software support at the Contractor’s facility and at other locations as directed by the COR. The Contractor shall provide software support and development to satisfy requirements for the link-16 embedded gateway, enhanced key management/modern algorithm, external time reference, and all block cycle changes directed by the COR. The Contractor will maintain SADL Support Equipment, Windows Forward Air

Controller, and the SADL Host Driver applications as directed by the COR.

5.2.1.4 Block Cycle Change Requirements: The Contractor shall develop/deliver software changes for radio equipment and support applications in accordance with PWS paragraph

5.2.1.1-5.2.1.2

5.2.1.4.1 Host Rekey via Black Interface: Contractor shall add a capability to remotely rekey the

SADL radio via the Ethernet interface through encrypted means (Black Rekey).

5.2.1.4.2 Military Standards (MIL-STD) Compliance Investigation: Contractor shall investigate

Interface Change Proposals accepted and approved in MIL-STD-6016E, MIL-STD-6017C, and

MIL-STD-3011B and correct deficiencies and impacts to the SADL system. Impacts to SADL networks and platforms as well as a plan to correct identified deficiencies and impacts shall be provided to the program office. The Government will approve the corrective plan prior to the

Contractor starting work to correct identified deficiencies and issues.

5.2.1.4.3 Operational Tactical Interface for SADL (OTIS): Contractor shall correct deficiencies identified in the Contractor developed document “Description of OTIS Deficiency Reports”

PR: FD2060-18-30255 PWS REVISION: 0 12

dated 04 Sep 2014. Release OTIS software shall also be capable of performing capabilities added/modified to the SADL baseline as of the date of this document.

5.2.1.4.4 Link Management System (LMS): Contractor shall develop phase one of the LMS

SADL initiative. This shall include the overall system design, changes to support equipment software display, and support equipment ability to monitor multiple need lines.

5.2.1.4.5 LMS Maintenance/IA:

The contractor shall work with the SADL Program Office and USAF C2 Office to determine the most efficient manner to update the LMS Computer Application and meet specific Information

Assurance (IA) / Cybersecurity requirements. This includes, but not limited to the following:

i. Correct deficiencies identified since previous release.

ii. Address the LMS-related static code analysis scan findings as mutually agreed upon by the

SPO and the Contractor.

iii. Support the USAF IA Assessment of the revised LMS software, providing reports as required,

iv. Update the LMS User Guide as required

5.2.1.4.6 MIL-STD-6016F Compliance Investigation:

The Contractor shall update the SADL Supplemental Interface Control Document (ICD) and

Gateway Control Application Program Interface (API) documents to incorporate the changes defined in MIL-STD-6016F that affect platform interoperability. The Contractor shall investigate

Interface Change Proposals (ICP) accepted and approved in MIL-STD-6016F and correct any deficiencies and impacts to the SADL system. The contractor shall also coordinate with the F-16

Program Office to incorporate any required changes to the F-16 ICD to address MIL-STD-6016F interoperability improvement.

The Contractor shall update the radio software and various host applications that are affected by the MIL-STD-6016F ICPs. This includes, but not limited to:

i. SADL Radio Software

ii. SADL Control Application

iii. SSE/LMS

iv. Host Driver

v. OTIS

vi. SERA

5.2.1.4.7 Windows 10 Compliance:

The Contractor shall ensure proper interoperability of SADL radio software and its applications with Microsoft Windows 10 Operating System (OS) and update the various host applications, installation applications and user guides as necessary, that are impacted by migrating to Windows

10. Any IA requirements for these applications would be in addition to Windows 10 interoperability changes and are not part of this effort. Admin rights are still required to install the

SADL applications on the target computers. This includes but not limited to:

PR: FD2060-18-30255 PWS REVISION: 0 13

i. SSE/LMS

ii. SADL Control Application

iii. Host Driver

iv. eProgrammer

v. OTIS

vi. SERA

vii. Virtual URO

viii. SADL Key Management

The KOK-23 driver is GFE to OEM Raytheon and addressing the unsigned driver issue is not part of this effort.

5.2.2 Travel: All travel requests require prior written coordination with the COR, and approval by the assigned Government PCO or Government Contracting Specialist. Coordination shall include number of travelers and an estimated cost breakdown across different expense types (i.e., Airfare, Vehicles, Hotel, Per Diem, etc.). Coordination will be accomplished with a minimum of ten working day notice in non-emergency situations. The number of trips shall be limited to the minimum number required to accomplish the work assignments in accordance with assigned tasks. Actual expenses are limited by the Government Joint Travel Regulations.

Funding Type: Cost Plus No Fee.

5.2.3 Meeting Support: The Contractor shall provide support to Semi-annual Program

Management Reviews, annual user’s meeting, and other collaborative meetings when directed by the COR.

5.3 Over And Above Work – Work Request

Over and Above Work will be in accordance with DFARS PGI 217.77. Written authorization for software maintenance not identified in Paragraphs 5.1 and 5.2 of the PWS must be received from

AFLCMC/WNYBBC through the PCO prior to commencement of required activity. The contractor shall submit a work request to identify the over and above work and, as appropriate, the Government authorizes the contractor to proceed.

5.4 Quality Management System: The Contractor shall ensure the quality of services through a quality and/or inspection system. In order to meet the government’s quality requirements, a contractor’s QMS should be robust enough and resourced adequately to execute four key quality functions: 1) Detection of quality program problems and defects; 2) Identification of root causes for quality related problems/defects; 3) Correction of root causes related to detected problems/defects; and, 4) Follow-up to ensure quality related problems/defects do not recur; a mature QMS requires the contractor be the proactive party on quality issues. The goal is to obtain performance reflective of continuous improvement with no reliance on COR’s surveillance to detect problems/defects, determine root causes, or ensure quality related problems/defects do not recur.

PR: FD2060-18-30255 PWS REVISION: 0 14

6.0 Data Deliverables:

6.1 Status Reports: For the term(s) of the exercised basic contract and options(s), the contractor shall maintain a history of software maintenance and support data in contractor format. This shall include but is not limited to: Progress/status reporting; a running history of progress in meeting schedules including a brief description of activities and accomplishments during each reporting period; a Risk Matrix, maintained by the contractor that identifies design, schedule, technical, resources, and other program element risks. The contractor shall use the monthly status reports to propose updates and changes, and document slippages to the deliverables schedule. The contractor shall provide help desk contact reports, software, equipment and licensing issues, and information requests to the Government as part of the monthly status report. The Government acceptance of the monthly status reports does not indicate concurrence with the content or proposed changes to schedule(s). DI-MGMT-80368A (CDRL A002)

6.2 Engineering Change Proposals: The contractor shall submit Class 1 ECPs for all changes to the baseline. The ECPs submitted shall be technically accurate, complete, clearly written, and systematically account for the proposed configuration changes. The contractor shall notify the government of all Class 2 changes, including all substitute parts changes, through Document

Change Notices (DCN), (DI-CMAN-80639C) (CDRL A006)

6.3 Software Version Description: The contractor shall document, update, and submit a Software

Version Description in Contractor format to the Government upon completion of each software version directed by the COR and delivered in accordance with paragraph 5.2.1. DI-IPSC-81442A

(CDRL A003)

6.4 Interface Control Document: The contractor shall document, update, and submit an Interface

Control Document upon completion of any required changes to existing Interface Control

Documents, and upon completion of any new Interface Control Documents. DI-CMAN-81248A

(CDRL A001)

6.5 System Level Specification: The Contractor shall document, update, and submit system level specifications (SSS) for delivered SADL firmware products. The SSS shall contain the requirements for a system. Requirements pertaining to subsystems may be contained within the document or within a separate subsystem document. If a separate subsystem document is developed, requirements shall be traced between the documents.

7.0 FUNDING STRUCUTRE:

7.1 Funding Approach: This contract is designed with multiple contract types at the service level.

The program office will coordinate with the contractor in order to determine the proper deliverable scope and schedule within budgetary restrictions.

7.2 User Support and Deficiency Report (DR) Investigations are considered high priority services that will be funded, whereas Software Sustainment Support and Non-Recurring

Engineering services will be scoped and funded by the program office in conjunction with the

PR: FD2060-18-30255 PWS REVISION: 0 15

contractor to fix the largest number of prioritized deficiency reports, software limitations & anomalies within schedule and budget restrictions.

7.3 Software Sustainment Support and Non-Recurring Engineering requirements should retain a

30-day lead time prior to project initiation in order to allow the contractor necessary start up time, unless they are required as a result of a Deficiency Report (DR) Investigation.

8.0 APPENDICES

8.1 Appendix A, References

Publication Title of Publication Date of Publication Sections that

Apply

AFI 10-403 Deployment Planning and Execution

20 September 2012 Paragraph

1.9.1.33.2

AFI 31-101 Integrated Defense 8 Oct 2009 Entire

AFI 91-204 Safety Investigations and

Reports

9 August 2012 Paragraph

2.12

AFMC/CV

Policy Letter

Conformance with Air

Force Environmental

Management System

(EMS) Requirements for

Contracts Performed on

Air Force Installations

1 Aug 07 Entire

None Air Force Contracting

Voluntary Protection

Program Support Guide

May 2009 Entire

None Department of Defense

COR Handbook

March 22, 2012 Section on

Combating

Trafficking in Persons in

Chapter 8, Monitoring the

Contractor

DoD 5200.2-R Personnel Security

Program

1/16/87, Change 1, 2/12/1990, Change 2, 7/14/1993, Change 3, 2/23/1996 http://www.dtic.mil/whs/directives

/corres/pdf/520002r.pdf

Entire http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf

PR: FD2060-18-30255 PWS REVISION: 0 16

DoD 5220.22-M

National Industrial

Security Program

Operating Manual

(NISPOM)

February 28, 2006 Entire

DoDD 4715.1E Environmental, Safety, and Occupational Health

(ESOH)

March 19, 2005 Entire

DoDD

5205.02E

DoD Operations Security

(OPSEC) Program

June 20, 2012 Entire

DoD Manual

5205.02-M

DoD Operations Security

(OPSEC) Program

Manual

November 3, 2008 Entire

E.O. 13423 Strengthening Federal

Environmental, Energy, and Transportation

Management

January 24, 2007 Entire

E.O. 13514 Federal Leadership in

Environment, Energy, and

Economic Performance

5 October 2009 Entire

FAR and supplements

Federal Acquisition

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

Sections applicable to

Contract and

PWS

MIL-STD-

129P(4)

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

Entire

MIL-STD-130N Department of Defense

Standard Practice /

Identification Marking of

U.S. Military Property

17 December 2007 Entire

MIL-STD2073-

1D

Standard Practice for

Military Packaging

15 December 1999, Notice 1, 10 May 2002

Entire

Public Law

91596

Occupational Safety and

Health Act of 1970

December 29, 1970 through last amendment

Entire http://osha.gov/

SAF/AQ

Memorandum

Implementation of FY11

NDAA Section 8108, Nov 13 2012 Entire http://farsite.hill.af.mil/ http://farsite.hill.af.mil/

PR: FD2060-18-30255 PWS REVISION: 0 17

Contractor Inventory

SAF Policy

Letter

Conformance with Air

Force Environmental

Management System

(EMS) Requirements for

Contracts Performed on

Air Force Installations

11 Dec 06 Entire

Under Secretary of Defense

Memorandum

Establishment of the

DoD Green Procurement

Program

August 27, 2004 Entire