PWS_REV_3.pdf

PR: FD2060-16-90715 PWS REVISION: 3 1

Distribution Statement D : Distribution authorized to the Department of Defense and U.S. DoD contractors only. Other requests shall be referred to AFLCMC/WNY.

Performance-Based Work Statement for

THE CONTRACTOR LOGISTICS SUPPORT

OF THE

Joint Air Defense Systems Integrator (JADSI)

AN/TSQ-214(V1A)

FD2060-16-90715

28 February 2018

Distribution Statement D : Distribution authorized to the Department of Defense and U.S.

DoD contractors only. Other requests shall be referred to AFLCMC/WNY.

PR: FD2060-16-90715 PWS REVISION: 3 2

1.0 Description of Services: This Performance-Based Work Statement (PWS) is written in accordance with AFI 63-101 and provides detailed information for Contractor Logistics

Support (CLS) of Joint Air Defense System Integrator (JADSI) (AN/TSQ-214(V1A)).

JADSI is a COTS solution that has proven itself as an optimal solution to current Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance

(C4ISR) tactical data transfer issues. JADSI receives, processes, correlates, forwards, and displays up to 12,000 tracks from local radars, tactical data links, and intelligence sources with minimal operator interaction. The system is designed to receive and process all incoming data; allow the operator to display all or selected parts of the tactical situation, and automatically forward all or selected data (elements/tracks). The JADSI is unique in its ability to process four different types of information. JADSI also provides the warfighter a real-time common tactical picture thereby providing essential decision information to commanders.

Tactical Data Links

Radar data

Intelligence information

Non-real-time information

There are 900 systems that have been delivered to US joint, Department of Homeland

Security, and coalition forces. The Air Force has approximately 203 systems deployed to operational components of every Area of Responsibility (AOR). It is an integral component of every Aerospace Operations Center (AOC), Global Command & Control System (GCCS)-

Air Force (AF), Joint Services Work Station (JSWS) and Theater Battle Management Core

Systems (TBMCS).

Work performed under this PWS includes all actions necessary to return the end items to a serviceable condition. The contractor shall provide repair services, engineering services, software updates, logistics, and field support for JADSI program. The contractor shall also provide 24 hour Help Desk support.

National Stock Numbers (NSNs) and Part Numbers are subject to change as the baseline changes at the system level. Such configuration changes may drive Contract Line Item

Number (CLIN) additions and/or deletions, as mutually agreed to between the government and contractor. Functional capabilities shall not be changed, modified, or altered except when an Engineering Change Proposal (ECP) has been submitted by the contractor and approved by the Government. The contractor shall repair items to serviceable condition to the latest hardware/software configuration approved and funded by the government for that item to ensure interoperability between JADSI and Link 16 terminal platform variants. The contractor will determine the most cost effective means of repair for each COTS hardware item consistent with meeting required system performance criteria and availability of technical data and spares. The period of performance (POP) shall be an 8 month basic with four annual (12 month) ordering periods with the option to extend 6 months.

1.1 Objective(s):

PR: FD2060-16-90715 PWS REVISION: 3 3

1.2 Benefit to United States Air Force (USAF): JADSI provides the ability to provide real-time information, i.e. air superiority, deep strike, missile defense, close air support, interdiction, etc., to all air and ground platforms within the Continental United States and Outside the

Continental United States supporting operations like Operation Enduring Freedom, Operation

Noble Eagle, and Presidential travel. JADSI provides the warfighter air and surface surveillance tracks, threats, and Precise Participant Location and Identification messages digitally communicated between Situational Awareness Data Link and Link-16 Networks resulting in situational awareness.

1.3 Background: The USAF JADSI systems are currently being supported on an Air Force contract (FA8523-12-D-0003). This contract was awarded 27 September 2012 and is set to expire 28 September 2017 with the option to extend 6 months.

2.0 Services Summary:

Performance Objective PWS

Reference

Performance Threshold

Maintenance and repair of items

4.5.1

4.5.2

4.10.1

The contractor shall repair 100% of items to serviceable condition within the established turnaround time. The contractor will notify the

Program Office of any repair taking longer than 30 calendar days.

24 Hour Technical Support

Desk

4.13

Response time by a SME is not greater than 4 hours. Resolution for all instances that can be resolved over the phone must occur in less than 48 hours. If resolution requires on-site assistance, the

Contractor shall submit a plan of action along with the travel approval request within 48 hours.

Resolution that requires on-site assistance must occur within 48 hours of technician arrival.

Deficiency Report (DR)

Investigations

4.11.3

For investigations conducted during the period of performance of this contract identify root cause

IAW TO 00-35D-54. Provide initial responses within 5 calendar days for a CAT I DR and 15 calendar days for a CAT II DR.

Expedited repair and shipment of critical items

4.5.3

The contractor shall respond to the PMS within one (1) business day of the request with the estimated delivery date of the critical item.

Configuration control of design and functional capabilities 4.8

The contractor shall track and inform System

Engineer/Program Manager of configuration changes before implementation. Program Office

PR: FD2060-16-90715 PWS REVISION: 3 4

must approve proposed changes before they are implementated.

Submission of

Engineering Change

Proposal

4.7

The contractor shall submit an ECP for all Class 1 changes to the baseline configuration within 30 calendar days. The contractor shall notify the government of all Class 2 changes, including all substitute parts changes, through Document

Change Notices (DCN) within 5 business days of implementation.

Completion of

Software Block Cycle

4.4.2

The contractor shall provide technical support, software maintenance/upgrades, and enhancements for the JADSI software.The contractor shall address all approved DRs and complete all required testing within the allowed block cycle time period.

Compliance with

Safety and Health Plan 5.5.4

100% compliance

Conduct acceptable

Contractor Safety

Program

5.5.3

No more than 2 Class C mishaps per contract year, Zero Class A or B mishaps

Mishap Notification and Reporting

5.5.3

The contractor shall telephonically notify the

Safety office within four (4) hours of all mishaps or incidents to DOD property entrusted by this contract, or DoD property damages or employee injuries as a result of the contract operation. No more than 1 instance of late mishap notification per contract year.

Contractor Manpower

Reporting

5.8 - 5.8.3 Within 30 calendar days of contract award, the

Contractor shall establish a record for the contract in eCMRA including Order Data, Contact Data and Location Data. The Contractor shall submit the annual report no later than October 31 of the following fiscal year.

Quality of CDRL deliverable

4.17 The Contractor shall deliver all data/reports

associated with all CDRLs, with no more than one

(1) rejection of each deliverable. There shall be no more than one (1) total rejection(s) of deliverables per month. The Government will

PR: FD2060-16-90715 PWS REVISION: 3 5

reject a deliverable if one (1) or more technical errors or five (5) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of

Government rejection, in accordance with the associated DD Form 1423 instructions/requirements.

Receipt of CDRL deliverable

4.17 The Contractor shall deliver all CDRLs with no

more than one (1) late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the

Government.

3.0 Government Property and Services

3.1 Government Property: Government will authorize Government Furnished Equipment

(GFE) items upon approval of AFMC Form 8. These items will be delivered to the contractor within 60 calendar days After Contract Award (ACA). GFE authorized during the period of performance (POP) shall be documented upon receipt and upon turn–in to the appropriate

Government representative. The contractor shall be responsible for establishing a secure storage for the GFE. All GFE shall be returned in serviceable “A” condition. The contractor shall return all GFE prior to the period of performance expiring. The contractor shall contact the

Government Program Manager (PM) within 30 days of task completion for GFE disposition instructions. Return of items for repair shall be coordinated with the appropriate Item Manager identified in the military supply system.

3.2 Government Property to be Provided:

3.3 Loss of Government Property: The Contractor shall use the Defense Contract

Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government

Property” toolset can be accessed from the DCMA home page External Web Access

Management application at http://www.dcma.mil/aboutetools.cfm.

PR: FD2060-16-90715 PWS REVISION: 3 6

Unless otherwise provided for in this contract, the requirements of the previous paragraph of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the

Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to—

(i) Theft;

(ii) Inadequate storage;

(iii) Lack of physical security; or

(iv) “Acts of God.”

This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

4.0 Technical Requirements

4.1 Period and Place of Performance:

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will be for base period of 8 months and 4 annual (12 month) ordering periods, with the option for a 6 month extension if necessary.

4.1.2 Place of Performance: These services will be performed at Ultra Electronics Advanced

Tactical Systems facility in Austin, TX.

4.2 Item Unique Identification (IUID): The IUID Program requires each qualifying AF 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 AF inventory and those currently under contract but not currently in the AF inventory. For assets under contract, IUID requirements are specified in DFARs 252-211.7003 and DODD 4100.39-

M, Federal Logistics Information System. All assets subject to marking must be recorded in the

DoD IUID Registry.

4.2.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-130, DoD Standard Practice

Identification Marking of US Military Property. The plan must be approved by the systems engineer prior to implementation.

PR: FD2060-16-90715 PWS REVISION: 3 7

4.2.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 Verfication column which indicates pass/fail for each item’s Data Matrix Symbol Quality.

4.3 Control Data Requirement and Mandatory Regulations: Data - Reports IAW DD

1423s and mandatory regulations as cited below:

4.3.1 Status Reports: Minimum reporting necessary to convey schedule, program progress, problems, and risks shall be supplied monthly. This data item shall include actual costs to date and estimated completion date for repairable items. These reports shall summarize tasks concluded since the previous status report and the tasks started, the tasks in progress, percentage completed, and the tasks planned to start during the next reporting period. This includes establishing and maintaining a schedule of reviews and a complete status of contract data deliverables, which are either due, in review, in revision, or completed. Any project concerns that are or may impact resources, schedule, or cost shall be reported along with the projected impact of the concern The contractor shall establish a method for identifying and correcting potential and actual deficiencies in quality of service performed before the level of performance becomes unacceptable. The inspection system shall contain processes for corrective actions

(A001, DI-MGMT-80368A, Status Reports).

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

Software Version Description to the Government within 30 days of completion of each final

Block Cycle Change (BCC) (A002, DI-IPSC-81442A, Software Version Description).

4.3.3 Parts Approval Request: Nonstandard parts, as defined as non-Mil-Standard or commercial equivalent that are used in this repair must be approved by AFLCMC/WNYK

(A005, DI-MISC-80071E, Parts Approval Request).

4.3.4 Alert/Safe-Alert Reports: Contractor shall submit all appropriate data requirements to the Government Industry Data Exchange Program (GIDEP) as it is generated. The contractor shall screen each Alert or Safe received from GIDEP to determine if the device or process for which the Alert is issued, is used in the manufacture of the unit and take appropriate action.

Contractor shall adhere to the policies and directives of GIDEP (A006, DI-QCIC-80125B, GIDEP; A007, DI-QCIC-80126B, GIDEP).

4.3.5 - Technical Manual/Technical Order: The contractor shall update and deliver any changes to a Technical Manual or Technical Order as part of this effort as defined in the TMCR

(TM-86-01M), Air Force Technical Manual Contract Requirements.

4.4 Specific Work Requirements

4.4.1 - Program Management: The contractor shall assign a program manager to plan and execute the tasks required in this PWS. The program manager shall be the single POC for the

PR: FD2060-16-90715 PWS REVISION: 3 8

Government. The program manager will be present, via telecom or in person, for all meetings and discussions that involve key personnel. The contractor shall support and document monthly management reviews. The contractor shall plan, manage and direct the JADSI contractor logistic support efforts through an Integrated Management Plan per this PWS. Contractor shall provide identification of all work to be accomplished, the Integrated Master Schedule for this work, and the functional organization charged with the responsibility for performance of the work. The contractor shall identify, assess, and manage risks. Particular attention shall be paid to risks associated with the contractor not meeting the requirements of the contract. Risk management shall be fully integrated with all elements of the program (A00A, DI-MGMT-80004A, Management Plan).

4.4.2 - Software BCC Requirements: The contractor shall provide technical support, software maintenance/upgrades, and enhancements for the JADSI software. The contractor shall address all approved DRs and complete all required testing within the allowed block cycle time period.

The contractor shall execute structured software engineering and program management processes that facilitate effective and high-quality software development. The contractor shall ensure that all changes, upgrades, and enhancements to baseline versions of the JADSI software are in compliance with the approved System Requirements Document (SRD). The Contractor shall evaluate/analyze all Software deficiencies (i.e. software deficiency reports, problem reports, enhancements, and candidate software upgrades). The Contractor shall conduct detailed analyses and provide a proposed solution with alternatives to include at a minimum:

Identification of changes to the

System and software requirements

System and software design

Software code

Hardware impacts (i.e. processor throughput and memory)

Cost

Schedule

Test products & environment

Independent Verification and Validation (IV&V) requirements

The contractor shall have the capability to provide software updates, fixes, and corrections which will be negotiated as the requirements are identified. The contractor shall incorporate change requests for the BCC and deliver BCC products, including the technical data packages that meet the operational needs of the user. Changes to lower level specifications shall be documented in applicable System/Subsystem Specifications, Software Requirements Specifications, and

Interface Requirements Specifications. The contractor shall coordinate software change efforts with JADSI program office (A011, DI-IPSC-81443A, Software User’s Manual; A00F, DI-IPSC-

81440A, Software Test Report; A00G, DI-IPSC-81439A, Software Test Description; A00D, DI-

IPSC-81441A, Software Product Specification; A00J, DI-SESS-80639D, Engineering Change

Proposal; A00K, DI-SESS-80643D, Specification Change Notice).

4.4.2.1 Acceptance Criteria: The contractor shall ensure that all contractor-delivered products meet the following criteria for Government acceptance of software corrective changes, upgrades, and enhancements:

PR: FD2060-16-90715 PWS REVISION: 3 9

a) Successful conduct of Formal Qualification Test (FQT) / Regression Test

b) No priority one, two, or three (as defined by IEEE/EIA 12207.2 Annex J) problem reports open as specified per delivery order.

c) Changed, upgraded, or enhanced software is compliant with MIL-STD-6016

d) Government approval of the deliverables, to include documentation required for each block cycle.

Additional specific acceptance criteria may be established on a per block cycle basis. The

Government will determine when these criteria have been met and document this determination in the Government Independent Assessment Report (A00L, DI-NDTI-80566A, Test Plans;).

4.4.2.2 Technical Support: The contractor shall provide technical support to field operations and customer inquiries such as resolving operational questions and maintenance problems.

Requests for assistance and actions taken shall be logged into the maintenance database (A009, DI-MISC-80508B, Technical Report-Study/Services).

4.4.2.3 Problem Report/Change Request Investigation: The contractor shall investigate problem reports and change requests. The contractor shall develop subsequent recommendations for change proposals. Recommendations shall include performance, schedule, and cost components (A00J, DI-SESS-80639D, Engineering Change Proposal).

4.4.2.4 Test Environment Support: The contractor shall provide and maintain a test environment capable of testing past, current, and future software configurations. The contractor shall document and control the configuration of each test environment the contractor utilizes, to include but not be limited to all elements of equipment, software, and human or automated processes present in each test environment. The contractor shall establish and maintain a factory test bed/development environment for support and developmental testing of the JADSI systems.

The test bed will be located at the contractor’s facility and will be capable of supporting a wide range of efforts including Factory Acceptance Testing (FAT), factory training in JADSI operation and maintenance, software security scans and accreditation, formal test program support (i.e., supporting Air Force System interoperability Testing, Joint interoperability testing, and Operational testing as directed by the SPO). The Government will provide resources appropriate to ensure that the factory test bed is fully capable of interoperating with other

Government and contactor test organizations. (A00L, DI-NDTI-80566A, Test Plans;)

4.4.3 Testing and Approval: The contractor shall test customer-directed changes to software design, code, integration, and test products for any software changed Computer Software

Configuration Items (CSCIs). The contractor shall maintain software development folders/files;

in electronic format. The contractor shall perform unit and component Requirements Based

Testing and all testing as identified in the Software Project Plan (SPP) and the Software

Development Plan to verify code changes and that the changes meet the requirement specifications. The contractor shall conduct any verification to ensure software and hardware is ready for Government witnessed CSCI and System level Formal Qualification Test (FQT). New software shall successfully complete interoperability testing and receive Government approval of

PR: FD2060-16-90715 PWS REVISION: 3 10

all related documentation. The contractor shall perform and document any new software development in accordance with the following documents MIL-STD-498, MIL-STD-973, MIL-

STD-1815A and ESC-DIR-116. The contractor shall be responsible for successful testing completion as well as the fielding of these capabilities. The contractor shall perform interoperability developmental testing and shall fix any Trouble Reports (TRs) identified as a result of the developmental test effort. In addition, the contractor shall support any Government test activity associated with required field level operation testing (A00P, DI-IPSC-81427B, Software Development Plan; A00D, DI-IPSC-81441A, Software Product Specification (SPS);

A002, DI-IPSC-81442A, Software Version Description; A00R, DI-MCCR-80700, Computer

Software Product End Items).

4.4.4 Support Test Working Group (TWG) Meetings: The contactor shall support monthly telecom Test Working Group (TWG) meeting until 8 weeks prior to a scheduled test, and then weekly telecom until each test is concluded. Support will consist of (2) test engineers. Meeting support will be limited to 1 hour per meeting.

4.4.5 Support Test Readiness Reviews (TRR): The contractor shall support TRR telecom as part of the Support Test Working Group (TWG) monthly / weekly telecoms. In addition, the contractor will support one CONUS 1 day telecom with two test engineers (A00S, DI-ADMN-

81505, Report, Record of Meeting Minutes).

4.4.6 Retest and Regression Testing: The contractor during the course of testing may be required to provide retest and/or regression testing. The contractor shall support (2) retest/regression events of 3 days duration, each including travel to a CONUS test facility with

(2) test engineers. Two days travel for each trip is in addition to the 3 day testing duration; four trips total; 20 man-days total. All traveling expenses shall be directed and approved by the

Procurement Contracting Officer (PCO).

4.5 General Repair Services: The PWS defines the general repair services of JADSI system as shown in paragraphs 4.5.1 and 4.5.2.

4.5.1 Repair Services: The contractor shall provide the necessary labor, materials, facilities and equipment required to analyze, troubleshoot, repair, overhaul and test JADSI assemblies, parts and the Operating System Software that are maintained or repaired under this contract.

These services also include alignment, adjustment, calibration, testing, movement, storage and reporting status related services to the repair and return of JADSI to the users. The contractor shall repair 100% of items to serviceable condition within the established turnaround time. The contractor shall keep the Program Office apprised of repairs taking longer than 30 calendar days.

Work performed under this work specification includes all actions necessary to return a reparable item to a serviceable condition. SRUs and subassemblies shall be repaired to meet the requirement of the associated specifications and shall successfully pass the associated ATPs prior to being returned to the Government.

PR: FD2060-16-90715 PWS REVISION: 3 11

4.5.2 Surge/MICAP Repairs: For all items identified as SURGE/MICAP requirements under the subject contract, the government hereby waives the requirement for final paint/touch-up, government witnessed acceptance test procedures (ATP) and final inspections at the contractor and its suppliers. This waiver shall remain in effect as long as the government has an immediate need for surge requirements. Any waived procedures will be performed at the next opportunity the system is available at the vendor facility.

4.5.3 Critical Items: Critical items of any category shall be expedited to the extent possible, as directed by the Production Management Specialist (PMS) through the PCO. The contractor shall respond to the PMS within one (1) business day of the request with the estimated delivery of the critical item.

4.6 Over and Above Repairs – Work Request: Over and Above work that arises within the parameters of this PWS may be encountered. It is recognized by the parties hereto that during the performance of this contract, engineering services and other system support not forecast, may be required hereunder, and shall be independently estimated and priced on a case-by-case basis.

These activities may include, but are not limited to:

Services in support of:

1. System Analysis

2. Failure Analysis

3. Diminishing Source Problems

4. Improved Item Replacement Program (IIRP)

5. R & M Improvements

6. Data Evaluation Analysis

7. Software Updates/Corrective Maintenance (ECPs)

8. Hardware ECPs

9. Deficiency Reports

4.6.1 Authorization: Written authorization for repair of recoverable items not listed, or engineering services not identified must be received from AFLCMC/WNYK through the PCO prior to commencement of required activity. Authorization to proceed will be provided by work request approved by the Administrative Contracting Officer (ACO).

4.6.1.1 - Engineering Services: It is recognized by the parties hereto that during the performance of this contract, engineering services and other system support not forecast, may be required hereunder, and shall be independently estimated and priced on a case-by-case basis.

The overall objective of all engineering services is to ensure safe operation of the systems while maintaining operational readiness of the end items to meet mission requirements. Engineering

Support includes tasks for Engineering and Technical Support Management,- Deficiency and

Mishap Investigation Support, Data Analysis, Configuration Management, Technical Program

Management Support and Safety - Hazardous Materials Management Program, Safety Support to Engineering and Notification of Hazard Risks Changes, and Engineering Task Orders -

Engineering Task Order Management, Analytical Engineering, System Integration Engineering, Performance Engineering, General Engineering Services Extended Support for Mishap

PR: FD2060-16-90715 PWS REVISION: 3 12

Investigation, Technical Manuals (Preliminary Technical Order Maintenance), Failure Analysis, Diminishing Source Problems, R & M Improvements, Software Updates/Corrective Maintenance

(ECPs) and Item Unique Identification (IUID) implementation.

4.6.1.2 System Refresh: The contractor shall work with the Government to identify system refresh strategies that may be implemented over the life of the contract. Thiswill be incorporated by contract modification and a separate Statement of Work will be incorporated.

4.7 Engineering Change Proposal (ECP): The Contractor shall update and submit for

Government approval any ECP that shall impact design or functional capabilities of JADSI configurations. Especially for any Class I changes required to the baseline hardware and software configurations. ECP classification shall be as defined by MIL-HDBK-61A/ EIA 649.

The contractor shall submit to AFLCMC/WNYK any change notice, design change notice, engineering order, engineering change order, engineering change notice, specification change notice or that would affect the configuration of the item. Any changes made without written approval from the contracting agency shall require removal at the contractor’s expense. An ECP is a permanent change to the item configuration, and is reflected in the delivered data package

(A00J, DI-SESS-80639D, Engineering Change Proposal). The contractor shall submit an ECP for all Class 1 changes to the baseline configuration within 30 calendar days. The contractor shall notify the Government of all Class 2 changes through Document Change Notices (DCN) within 5 business days of implementation.

4.8 Configuration Management: The contractor shall maintain hardware and software configuration control under this contract. Contractor shall also maintain a formal CM system for the JADSI program that includes, as a minimum, the following processes: Configuration

Identification, Configuration Status Accounting, Configuration Control, Configuration

Verification/Audits, Contract Data Management, Deficiency Reporting and Investigating, and

Engineering Data Management. The Government expectation for Configuration Management is that the contractor shall develop and implement a Configuration Management Plan (CMP), establish a Configuration Control Board (CCB) with appropriate representation (e.g. IA) with results addressed at the Government’s Configuration Review Board (CRB) for final approval, prepare engineering change proposals (ECP), and notice of revisions (NOR), support the activities (for example, meetings, creation and/or review of engineering data, etc.) of the

Government configuration control boards, as required by the Government, and meet with the

JADSI program office CRB to review configuration changes as required. The contractor shall track and inform the System Engineer/Program Manager of configuration changes before implementation. Program Office must approve proposed changes before they are implementated. Changes to the configuration shall be made only when identified by an approved change. Examples of such changes are ECPs generated as the result of diminishing sources and preferred spares. Records shall be maintained which readily and systematically account for configuration changes from the baseline configuration (A00J, DI-SESS-80639D, Engineering

Change Proposal).

4.9 Reviews and Meetings

PR: FD2060-16-90715 PWS REVISION: 3 13

4.9.1 Technical Interchange Meetings (TIMS): The contractor shall conduct TIMs as required to analyze technical problems, issues, or risks that might have an impact on the success of this CLS effort. Procurement Contracting Officer (PCO) will schedule a Post-Award

Orientation Conference with the contractor and ensure that everything that needs to be done on time and with schedule is discussed and recorded and that the contractor is held accountable.

The contractor shall establish, update and maintain a master action item log with actions resulting from reviews or meeting that have been designated by the Government or contractor for tracking. Contractor shall coordinate teleconference with the program office as required to discuss programmatic and technical issues, to include IA issues. Contractor shall provide managerial and technical support as required for teleconferences. The contractor shall also report monthly schedule and any other information in contractor format (A00T, DI-ADMN-

81249B, Conference Agenda; A00U, DI-ADMN-81250B, Conference Minutes; A001, DI-

MGMT-80368A, Status Reports).

4.10 General Work Requirements: Contractor shall furnish, repair, replace or provide new components, equipment and materials shall conform to original equipment manufacturer (OEM) specifications. The new components and material shall be of the same exact manufacturer, class, grade, type, and function as those being replaced unless otherwise approved by the contracting officer. The contractor may recommend substitutions; however, the contractor must obtain approval from the PCO prior to purchasing or installing any component or material. The contractor shall provide all written specifications and details of the proposed material, component or equipment to the PCO or authorized approval authority as designated by the PCO.

4.10.1 Depot repair Overview: The contractor shall repair 100% of items to serviceable condition within the established turnaround time. Both LRU and SRU test equipment will be available to perform testing during in-plant depot repairs for the length of the contract. If necessary, manufacturing test equipment may be used to perform Acceptance Test Procedures

(ATP) or troubleshooting of JADSI repair items on a not to interfere basis.

4.10.2 Depot Repair Process: The contractor’s adherence to quality standards referenced in

AFMC Form 807 approved repair processes will ensure that all repaired hardware meets the same performance standards as the original units to ensure that form, fit, function, and interchangeability are maintained for the length of the contract. The contractor shall perform analysis and make recommendations to the Government for Depot spares replenishment and for the repair of failed Depot equipment.

4.10.3 Receiving and Inspection of Hardware: Upon receipt at the contractor’s facility, the unit will be confirmed to be in agreement with the incoming paperwork for contractual status, funding, and COMSEC CONTROLLED ITEM (CCI) documentation, if required. The contractor then generates the repair forms required for internal processing, and enters applicable data into the contractor’s appropriate database, as well as the WAWF asset tracking system provided by the government.

The contractor will notify the government in writing (Email or facsimile) upon receipt of items that are misidentified, misdirected, received incomplete, or missing components/subassemblies.

PR: FD2060-16-90715 PWS REVISION: 3 14

The Government will then provide authorization to repair, or disposition instructions to return

LRUs received incomplete or missing SRUs back to the customer identified on documentation received with the item. Return will be made via Report of Discrepancy, Standard Form 364.

Missing SRUs are to be furnished by the customer. If the SRU is in “A” condition, the SRU will be inserted into the LRU as a ‘ship-in-place’ and the LRU repair will be completed.

The end items shall be handled and stored in such a manner as to prevent damage and theft. The contractor shall secure and process end items returned for repair in accordance with the contract

DD Form 254 requirements. When shipping containers are received that meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, they shall be reclaimed, stored, and protected for reuse. Unserviceable containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158. Repaired units will be shipped using “Best Commercial Practices”. Any misdirected or misidentified shipments shall be processed for disposition via Government Bill of Lading.

4.10.4 Incoming Testing: The contractor will test the returned hardware to identify the cause of the failure. If the failure is not verified, the user may be contacted for further information. If the unit still cannot be verified as a failure, it will be routed to final inspection. If the failure is verified, rework will be performed until the item is operational. Inspection will be performed as required during the rework cycle. Final testing, inspection, quality review, and

Government/Customer Source Inspection sample will be performed prior to returning the item to the directed location.

If a failed asset is subcontractor manufactured, it is returned to the vendor for repair. The contractor performs incoming inspection and testing before the repair is sent to the vendor subcontractor when required. After the repaired item is returned, the contractor’s depot performs final testing as appropriate. The contractor’s depot has secure storage available for repair items containing CCI, embedded or removable. In addition, the contractor’s depot has a secure area where units are stored awaiting disposition, funding, warranty status, or other directions. The contractor will provide safekeeping of Government assets in their possession. The contractor has assigned COMSEC Account Numbers and will receive, store, and ship COMSEC assets in accordance with the DD Form 254, security classification guide and National Industrial Security

Operating Manual (NISPOM).

4.10.5 Acceptance Testing Procedure: The contractor shall develop and provide the necessary acceptance test plan and test result for each of JADSI item. Contractor shall also provide the quality assurance requirements information necessary to enable future repair of an interchangeable item that duplicates the physical and performance characteristics of the original product. There shall be no additional design engineering effort or recourse to the original design activity. The Government must approve the ATP. Acceptance test procedures shall demonstrate that the JADSI item to be returned to the Government is in serviceable condition. The contractor shall verify through appropriate testing and examination that certain basic functional requirements of this PWS are met. These tests shall be conducted on all items repaired as a condition of acceptance of the equipment by the Government (A00L, DI-NDTI-80566A, Test

Plans).

PR: FD2060-16-90715 PWS REVISION: 3 15

4.10.6 Turn Around Time: Turn Around Time (TAT) shall be 45 calendar days for LRUs and

SRUs beginning from the date the items are received. Actual repair TAT is measured from

Contractor(s)’s induction of the repairable item and funded delivery order to date of shipment.

Joint Chief of Staff (JCS) SURGE backorders and MICAPs will take precedence over the routine schedule. In the event that a repairable item is required by the Government on an emergency basis to fill MICAP/SURGE backorders, the PCO/Government will notify the contractor in writing (E-mail or facsimile preferred) as soon as the need is identified. In these situations, the contractor will use any means possible to expedite the repair process to meet government

SURGE and MICAP requirements. MICAP/SURGE repairs could affect TAT on repair services; therefore relief on TAT may be requested for these items. The contractor is authorized to swap SRUs between LRUs for the purpose of expediting deliveries. The contractor is authorized to repair any reparable SRU for which funding has been provided. Should the contractor have on hand reparable SRUs for which an order has not been issued, contractor shall notify the PCO/Government for disposition instructions and/or to fund the order. All repaired end items shall be final inspected by the contractor’s Quality Assurance Department, or designee, and submitted to the Government Contracting Officer Representative (COR) for

Contract Quality Assurance (CQA) and Acceptance at Origin on a Material Inspection and

Receiving Report (WAWF). Upon completion of all inspections, all ports, vents, and openings shall be covered with plugs, caps, or sealed in plastic bags to prevent entry of foreign matter or contamination into the end item.

4.10.7 Packaging: When shipping containers are received that meet the requirements of the

AFMC Form 158, Packaging Requirements, and are suitable for return shipment of serviceable assets, they shall be reclaimed, stored and protected for reuse. Unserviceable containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form

158, Packaging Requirements. (MIL-STD-2073-1d, 10 May 02, Standard Practice for Military

Packaging and MIL-STD-129P(4), 19 Sep 07, Military Marking for Shipment and Storage).

Please see Appendix B for JADSI Repair Candidates.

4.10.8 Obsolete Parts: Contractor shall monitor, identify, and verify subsystem and component obsolescence through market research. Review JADSI items for potential impact resulting from change in obsolescence issues to include impact and identify alternate items and/or alternate supplier sources. Replacement parts or re-design will be recommended to minimize impact.

4.11 Quality

4.11.1 Contractor Inspection: The contractor’s inspection system shall be established and maintained IAW contract. The 807 will not be attached to the contract, but its information will be inputted into the contract AFMC FORM 807, or equivalent.

4.11.2 Corrective Action for Defects Reported: When reported, contractor shall assist the local DCMA/PCO in evaluating exhibits to determine the root cause for deficiencies reported from field and depot organization.

PR: FD2060-16-90715 PWS REVISION: 3 16

4.11.3 Deficiency Reporting (DRs): The contractor shall initiate and track deficiency reports and recommend appropriate corrective actions to the Government. The contractor shall comply with USAF TO 00-35D-54 for processing deficiency reports for hardware and software. The contractor shall provide initial responses within 5 calendar days for a CAT I DR and 15 calendar days for a CAT II DR. The contractor’s inspection system shall include the complete processing of Material Deficiency Reports (MDRs) and Quality Deficiency Reports (QDRs) IAW AFMC

FORM 807 including evaluation of DR contract repair exhibits at no additional cost to the government. Timely correction and reporting of defects found and corrective action to prevent repeated discrepancies shall be an integral part of the contractor’s quality procedures. Corrective action shall extend to the performance of all contractors’ vendors. (A00V, DI-PSSS-81534A, Teardown Deficiency Report; A00W, DI-OCIC-80736, Quality Deficiency Report; A001, DI-

MGMT-80368A, Status Reports; A00X, DI-MISC-80711A, Scientific and Technical Report).

4.11.4 Test Equipment Calibration: The calibration standards for calibrating the test equipment used in the repair test/sell-off phase shall be traceable to the National Institute of

Standard Technology (NIST) IAW NIST SP250.

4.11.5 Condemnation: The contractor is not authorized to condemn items without prior approval of the PCO. Unless authorized by the PCO, the contractor shall not be allowed to repair items where the cost of parts and labor exceeds 75 percent of the replacement cost of the item as shown in the stock-list catalog. Uniform criteria for estimating repair cost used in determining economical repair of equipment shall be IAW TO 00-20-3. All items condemned that contain precious metals and/or all scrap-bearing precious metals shall be reported to the

Defense Reutilization and Marketing Service, DRMS-SM, Federal Center 74 N. Washington, Battle Creek, MI 49017-3084 for disposition instructions unless other specific instructions are furnished by PCO. Condemned items shall be disposed of and demilitarized in accordance with

DoD Publication 4160.21-1-M-1 “Defense Demilitarization Manual” (A00Y, DI-ILSS-80620, Government Furnished Equipment Repair Status Report).

4.11.6 Production Problems: For the purpose of resolving repair or rework problems as they occur, the contractor shall report them to AFLCMC/WNYK through the ACO/PCO.

4.11.7 System Safety: System Safety involves the application of engineering and management principles, criteria, and techniques to optimize all aspects of safety within the constraints of operational effectiveness, time, and cost. The contractor shall maintain all aspects of safety requirements addressed in AFI91-202 and Military Standard 882. System Safety principles and practices must be used to identify and eliminate or reduce hazards to acceptable levels over the operational life of the system or end item. The contractor shall maintain the Hazardous Materials

Management Program (HMMP) and the System Safety Program (SSP) throughout the contract period of performance. (A012, DI-SAFT-80102C, Safety Assessment Report (SAR); A00Z, DI-

SAFT-81626, System Safety Program Plan (SSPP); A010, DI-MGMT-81398C, Hazardous

Materials Management Program (HMMP) Plan).

PR: FD2060-16-90715 PWS REVISION: 3 17

4.11.8 Finishing and Marking: The Contractor shall repair damaged protective finish to the extent necessary to provide adequate protection during usage. The Contractor shall replace damaged markings, identification and decals. Minor cosmetic defects (scratches, nicks, dents, etc) not considered to affect the installation or operation of the repaired item, shall not require correction. The contractor will package and mark assets for delivery IAW with AFMC Form

158, Packaging Requirements. Workmanship shall be in accordance with TO 00-25-234 or contractor’s standard repair procedures and acceptance criteria.

4.12 Handling: Handling of equipment shall be in accordance with AFMC FORM 807.

Reusable containers shall be retained protected and stored for reuse. The contractor shall package, handle, store, and transport materials using best commercial practices to ensure effective use of space for packaging, handling, and transportation consistent with transportability on commercial and military aircraft. The contractor shall provide packaging and preservation methods (i.e. dehumidified, etc.) to protect material against corrosion, physical and mechanical damage and other forms of degradation.

The contractor shall implement, when applicable, an Electrostatic Discharge Control Program for all Electrostatic Sensitive Devices IAW MIL-STD-129P, Marking for Shipping and Storage;

MIL-STD-1686C, ESD Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment; MIL-HDBK-263B, Electrostatic Discharge Control Handbook for

Protections of Electrical and Electronic Parts, Assemblies, and Equipment (excluding

Electrically-Initiated Explosive Devices). A contractor ESD program approved by the local

Government Representative may be used. Contractor shall annotate the applicable receiving document with National Stock Number, Part Number, and Serial Number (DD1348 and

DD1149). Contractor shall annotate applicable serial numbers on each DD Form 250, Material

Inspection and Receiving Report. Contractor shall use Wide Area Workflow (WAWF) to annotate serial number on each invoice, Material Inspection and Receiving Report.

4.13 - Help Desk: The contractor shall provide technical assistance as required by providing a

24-hour, 7-day help desk service to on-site service technicians to call for assistance in resolving operational questions and maintenance problems. Requests for assistance and actions taken shall be logged into the maintenance database. Response time (defined as the time span from when a user calls in with an issues to when the user actually speaks with a Subject Matter Expert) for all calls shall be less than 4 hours. Resolution for all instances that can be resolved over the phone must occur in less than 48 hours. Resolution that requires on-site assistance must occur within

48 hours of technician arrival.

4.14 - Training: The contractor shall, in conjunction with the Government, assess the need for operations training for new or modified operational capabilities associated with each software update and provide such update training if deemed necessary. The contractor shall, in conjunction with the Government, assess the need for training for in-house or on-site hardware or software maintenance personnel to ensure that they remain current with the JADSI system and maintenance environments and provide such update training when deemed necessary. Provide training for newly-assigned on-site maintenance personnel.

PR: FD2060-16-90715 PWS REVISION: 3 18

4.15 Cybersecurity: The contractor shall sustain cybersecurity for the JADSI, its subsystems, components and support systems/equipment IAW DoD Instruction (DoDI)

8500.01, Cybersecurity and DoDI 8510.01, Risk Management Framework (RMF) for DoD

Information Technology (IT).

4.15.1 Transition to the Risk Management Framework (RMF): JADSI shall transition to the cybersecurity requirements identified in DoD Instruction (DoDI) 8500.01, Cybersecurity and

DoDI 8510.01, Risk Management Framework for DoD Information Technology (IT). The

Government will determine the JADSI impact values based on the Committee on National

Security Systems Instruction (CNSSI) No. 1253, “Security Categorization and Controls Selection for National Security Systems.” Once determined the Government in conjunction with the

Integrated Product Team (IPT) and the contractor will tailor the security controls.

Based on these designations, the contractor shall:

1) Conduct a gap analysis between the tailored security controls provided by the

Government and what is currently IMPLEMENTED on the JADSI.

2) Prepare a Plan of Action and Milestones (POA&M) identifying those gaps to include:

Security control reference and enhancement numbers (if applicable) that are Not

Applicable (NA) or Non-Compliant (NC). For security controls identified as NC, the contractor shall provide a valid risk-based rationale.

Estimated funding or manpower (i.e., full-time equivalents) resources required to resolve the gap

Any external dependencies and needs including government furnished equipment, material or services

Any technical requirements, responsibilities, milestones, interfaces, subcontracts and license agreements, equipment, tools, documentation, testing, training, and facilities impacted by the transition

3) Provide the POA&M to the Program Manager and Information System Security

Management (ISSM) via secure channels (e.g.