PWS JRE-JTEP - 22 Aug 2011.doc - - 08-23-2011.doc

Performance-Based Work Statement For The

Contractor Logistics Support

Of The

Rugged and Semi Rugged Joint Range Extension Gateway (JRE-GW) System

AN/TYQ-123(V)1, AN/TYQ-123(V)2

Fixed Joint Range Extension Gateway (JRE-GW)

Transparent Multi-Platform Gateway (TMPG) Equipment Package (JTEP), AN/FSQ-225

Transportable Joint Range Extension Gateway (JRE-GW)

Transparent Multi-Platform Gateway (TMPG) Equipment Package (JTEP)

AN/TSQ-235

And the

Joint Range Extension (JRE) software

PR: FD2060-11-30608

27 April 2011

Prepared by: Martin Okaiwele

WR-ALC/GRWBBA

460 Richard Ray Blvd., Suite 200 Robins AFB, GA 31098-1813 Table of Contents

DESCRIPTION OF SERVICES

SERVICES SUMMARY

GOVERNMENT FURNISHED EQUIPMENT AND SERVICES

23.1 Needed Equipment

23.2 Government Furnished Equipment

23.2.1 Return of GFE

23.2.2 Repair of GFE

23.2.3

MILSTRIP

23.2.4 SIPRNET Access

GENERAL INFORMATION

44.1 Control Data Requirement and Mandatory Regulations

44.1.1 Status Reports (A002)

44.1.2 Software Version Description (A003)

44.1.3 System Requirements Document (A004)

44.1.4 Interface Control Document (A009)

44.1.5 Parts Approval Request (A005)

44.1.6 GIDEP Alert/Safe-Alert Reports (A007), DI-QCIC-80125B and DI-QCIC-80126B

44.1.7 Engineering Change Proposal (ECP) (A008)

54.1.8 Technical Manual/Technical Order Updates (A010) and (A011)

54.1.9 Test Plans and Procedures (A012), DI-NDTI-80566A and (A013), DI-NDTI-80603A

54.1.10 Test/Inspection Report (A014) DI-NDTI-80809B

54.1.11 Reports/Records of Meetings/Minutes (A018) DI-ADMN-81505

54.1.12 Installation and Fielding Plan (A001) DI-MGMT-81118

54.1.13 Provisioning (A015)

54.2 Specific Work Requirements

54.2.1 Software BCC Requirements

54.2.1.1 Acceptance Criteria

54.2.1.2 Technical Support

64.2.1.3 Problem Report/Change Request Investigation

64.2.1.4 Test Environment Support

64.2.1.5 Independent Validation and Verification Support

64.2.1.6 Software Maintenance and Update

64.2.1.7 Software Enhancement

74.2.1.8 Documentation/TR Fixes

84.2.1.9 Provisioning

94.2.1.10 Training

94.2.2 Test

94.2.2.1 Support Test Working Group (TWG) Meetings

94.2.2.2 Support Test Readiness Reviews (TRR)

94.2.2.3 Retest & Regression Testing

94.2.2.4 Developmental Test (DT)

104.2.2.5 Air Force System Interoperability Test (AFSIT)

104.2.2.6 Operational Testing

104.2.3 System Refresh

104.2.4 Repair Services

104.2.4.1 Surge/MICAP Repairs

104.2.4.2 Critical Items

104.2.4.3 Over and Above Repairs – Work Request

114.2.5 Information Assurance

114.2.5.1 Contractor Responsibilities

114.2.6 Interoperability Systems Management and Requirements Transformation (i-SMART/e-SMART)

124.2.6.1 Documentation of JRE Implementation of MIL-STD-6016 in i-SMART/e-SMART

124.2.6.2 Documentation of JRE Implementation of MIL-STD-3011 in i-SMART/e-SMART

124.2.6.3 Documentation of JRE Implementation of MIL-STD-6020 in i-SMART/e-SMART

124.2.6.4 Government Responsibility Regarding i-SMART/e-SMART

124.2.7 Program Management

124.2.8 Hardware Engineering Change Proposal

124.2.9 Configuration Management

134.2.10 JRE/JRE-GW/JTEP Website

134.2.11 Database Management

134.2.12 Meeting Support

134.2.12.1 Program Management Review (PMR)

134.2.12.2 Fielding Meetings

134.2.12.3 IA Implementation Status Meetings

134.2.12.4 Teleconferences

134.2.12.5 Configuration Control/Review Boards

134.3 General Work Requirements

144.3.1 Depot Repair Overview

144.3.1.1 Depot Repair Process

144.3.2 Receiving/Inspection of Hardware

144.3.3 Incoming testing

154.3.4 Final Acceptance Testing

154.3.5 Depot Turn Around Time

154.3.6 Obsolete Parts

164.3.7 Quality

164.3.7.1 Contractor Inspection

164.3.7.2 Corrective Action for Defects Reported

164.3.7.3 Deficiency Reporting (DRs)

164.3.7.4 Test Equipment Calibration

164.3.8 Condemnation

174.3.9 SRU or LRU

174.3.10 Accessory and Component Reuse, Repair and Replacement

174.3.11 Production Problems

174.3.12 Extraordinary Repair Actions (ERAs)

184.3.13 Missing on Induction (MOI)

184.3.14 Replacing Failed/Missing SRU when Repairing a LRU

184.3.15 System Safety

184.3.16 Finishing

194.4 Handling

194.5 Help Desk

194.6 Subject Matter Expert (SME) Support

194.6.1 CONUS JRE/JRE-GW/JTEP SME Field Support

204.6.1.1 Limited Field Support

204.6.1.2 Full On-equipment Maintenance Field Support

204.6.2 Labor Hours

204.7 Emergency Exercises While on Base

204.8 Security Requirements

204.9 Green Procurement Program (GPP)

APPENDICES

215.1 Applicable Documents

22Appendix A

22Terms Explained

24Appendix C

24Table 2

24Reference Documents

1 DESCRIPTION OF SERVICES

This Performance-Based Work Statement (PWS) is written in accordance with AFI 63-124 and provides detailed information for Contractor Logistics Support (CLS) of the rugged and semi-rugged Joint Range Extension Gateway (JRE-GW), the Fixed and Transportable JRE-GW Tactical Equipment Package (JTEP) and the JRE software. The JRE software provides near real time beyond line-of-sight (BLOS) Link 16 connectivity and routing throughout a theater of operations, between theaters, and from theaters to rear-area Command and Control (C2) centers and provides the ability to link two dissimilar data link networks (Link 16 and Situational Awareness Data Link (SADL)). The JRE-GW is a communications router that provides the capability to pass timely secure Link-16/Tactical Data Link-J series messages (TADIL-J) data via long haul means beyond line-of-sight (BLOS). The transportable JTEP also provides AF Control and Reporting Centers (CRC) near real time beyond line-of-sight (BLOS) Link 16 connectivity and routing throughout a theater of operations and between theaters. The fixed JTEP provides Air National Guard Air Defense Fighter Interceptor Wings with the capability of communicating with their SADL as well as Link 16 equipped aircraft and routing that information to the Air Defense Sectors for Homeland Security. 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, Information Assurance (IA) and field support for the JRE/JRE-GW/JTEP program. 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 SADL 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 authorized hardware configurations for repair under this PWS are listed in Table 1.

2 SERVICES SUMMARY

4.3.1.1,

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

Expedited repair and shipment of

Critical items 4.2.4.2 4.3.5 The contractor shall respond to the PMS within one (1) working day of the request with the estimated delivery date of the critical item.

Configuration control of design and

Functional capabilities 4.1.8 4.2.9 The contractor shall track and inform System Engineer/Program Manager of configuration changes.

Submission of Engineering Change

Proposal 4.1.8 4.2.8 The contractor shall submit an ECP for all Class 1 changes to the baseline configurations (Table 1). The contractor shall notify the government of all Class 2 changes, including all substitute parts changes, through Document Change Notices (DCN).

3 GOVERNMENT FURNISHED EQUIPMENT AND SERVICES

3.1 Needed Equipment

The contractor will be authorized to requisition Government Furnished Equipment (GFE) items upon approval of AFMC Form 8s. These items shall be delivered to the contractor within 60 calendar days After Contract Award (ACA).

3.2 Government Furnished Equipment

See Attachment A.

The contractor shall provide management and secure storage space for Government Furnished Equipment (GFE) provided under this contract. The contractor shall provide Government access to the GFE list from the JTEP website.

3.2.1 Return of GFE

All reparable GFE items shall be returned in serviceable “A” condition. The contractor shall return all GFE prior to the period of performance expiring. Packaging and Shipping of returned GFE will be IAW best commercial practices. The contractor shall contact the Government PM within 30 days of task completion for GFE disposition instructions.

3.2.2 Repair of GFE

The contractor shall coordinate the repair of GFE items. GFE items will fall into one of three categories, MILSTRIP Repair, Contractor Repair, and Consumables. See GFE listing (attachment A)

3.2.2.1 All Contractor Repairable GFE items will be repaired to serviceable “A” condition by the contractor.

3.2.2.2 All consumable GFE items will be disposed of IAW local regulations and procedures and replaced with serviceable “A” condition items.

3.2.2.3 All MILSTRIP Repairable GFE items that require repair are to be handled through the military supply system utilizing appropriate MILSTRIP authority IAW contract language specified in this performance work statement. Return of items for repair shall be coordinated with the appropriate item manager identified in the military supply system. Items shall be shipped to repair locations as specified by the item managers. The contractor shall requisition replacement items by submitting a funded MILSTRIP requisition to the source of supply for that item.

3.2.3 MILSTRIP

GFE items identified in attachment A are authorized MILSTRIP authority under this provision IAW Appendix B MILSTRIP.

3.2.4 SIPRNET Access

The Government will support the continued availability of SIPRNET at the contractor’s facility.

4 GENERAL INFORMATION

This PWS provides detailed information for CLS of JRE-GW/JTEP systems and the JRE software. The information contained in this section is not intended to be all inclusive or to detract from procedures outlined in specifications and other directives listed in Appendix B of this PWS. Workmanship shall be in accordance with contractor’s standard repair procedures and acceptance criteria in accordance with best industry practice.

The contractor shall provide the necessary labor, materials, facilities and equipment required to analyze, troubleshoot, repair, overhaul and test JRE-GW/JTEP, assemblies, parts and the JRE Software that is 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 JRE-GW/JTEP to the user. Repair, overhaul and replacement shall include JRE-GW/JTEP subassemblies and major assemblies up to and including the complete JRE-GW/JTEP. Software problems to be corrected shall include, but are not limited to priorities 1 and 2, (priority 1: (a) prevent the accomplishment of an operational or mission essential capability or (b) adversely affect technical cost or schedule risks to the life cycle support of the JRE/JRE-GW/JTEP and there is no work-around solution known).

The extent of repair required to return an item to a serviceable condition shall be determined by the inspection, test, bench check, and required disassembly.

Items input for repair shall be in a wide range of conditions, consisting of but not limited to:

· Engineering Manufacturing Development (EMD) assets

· Items which are beyond the ability of field level skill to repair

· Items received which may vary in age and condition.

Contractor furnished material or parts used for replacement shall equal or exceed the quality of the original material or parts. The material or parts shall be entirely suitable for restoration of the end item for its intended purposes.

The contractor shall provide repair services for the all JRE-GW/JTEP items listed in Table 1. 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 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 SADL and Link 16 terminal platform variants.

The contractor shall maintain repair capabilities in a separate area of the manufacturing facility, and/or co-located with other functions. Both Line Replaceable Unit (LRU) and Shop Replaceable Unit (SRU) test equipment will be available to perform testing during in-plant depot repairs. If necessary, manufacturing test equipment will be used to perform Acceptance Test Procedures (ATP) or troubleshooting of identified JRE-GW/JTEP repair items. The depot repair processes and organizations that fulfill the supportability requirements will maintain ISO 9001-2000 certification or equivalent. The in-plant depot shall be staffed with the necessary personnel to include Production Engineers, Test Technicians, Production Control Coordinators, Rework personnel, Inspectors, Program, Finance, and Contracts personnel who will handle repairs, paperwork, and database entry from receipt of a repairable to preparation for shipping.

The contractor repair facilities shall be environmentally controlled to the extent deemed necessary by the contractor to ensure the highest quality product.

The contractor shall provide repair services to establish in-plant JRE/JRE-GW/JTEP support capability for non-warranty hardware to provide the Intermediate (LRU-level) and Depot (SRU-level) repair services defined within this PWS. The long-term goals are to maximize the operational availability and reliability of JRE/JRE-GW/JTEP systems and hardware while minimizing government logistics support investments required to achieve desired system life cycle with predictable and affordable sustainment costs.

The contractor will provide depot repair support for JRE-GW/JTEP hardware (and installed software) listed in Attachment B. Each LRU and SRU will be repaired at either the contractor’s or a subcontractor’s facility. When assets are repaired at subcontractor facilities, the contractor will maintain asset visibility and tracking. Separate Department of Defense Address Activity Code (DoDAAC) will be issued for the contractor’s facility.

The contractor shall provide block cycles upgrades to the JRE software. The block cycle upgrade will consist of ONLY Government approved Change Requests (CRs). During the block cycle time period, appropriate testing shall be performed.

The contractor’s Program Management will provide the interface between the subcontractors and the Government Program Office.

3.1 Control Data Requirement and Mandatory Regulations

Data - Reports IAW DD 1423s and mandatory regulations as cited below:

3.1.1 Status Reports (A002)

For the term(s) of the exercised basic contract and options(s), the contractor shall maintain a history of repair data for non-warranty JRE-GW/JTEP hardware, in contractor format. In addition, the contractor shall document the status of JRE block cycle changes, to include, but 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 Risk Matrix shall be updated with each monthly CSR.

· Methods of meeting CR requirements

· Testing status and ATO/ATC status

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, monthly SME 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).

(CDRL A002 and DI-MGMT-80368A)

3.1.2 Software Version Description (A003)

The contractor shall document, update, and submit a Software Version Description to the Government upon completion of each final Block Cycle Change (BCC). DI-IPSC-81442A

3.1.3 System Requirements Document (A004)

The System Requirements Document (SRD) describes the top-level requirements for JRE-GW/JTEP system. Any changes to the SRD shall be properly documented and delivered to the Government at the end of the effort. (DI-IPSC-81431A)

3.1.4 Interface Control Document (A009)

The contractor shall document, update, and submit any changes to the Interface Control Document. (DI-CMAN-81248A)

3.1.5 Parts Approval Request (A005)

Parts not identified in the Technical Data Package as suitable replacement parts are considered nonstandard parts. Nonstandard parts that are used in any repair must be approved by WR-ALC/GRWEDA via submittal of DI-MISC-80071E, as required.

3.1.6 GIDEP Alert/Safe-Alert Reports (A007), DI-QCIC-80125B and DI-QCIC-80126B

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.

3.1.7 Engineering Change Proposal (ECP) (A008)

The contractor shall submit Class 1 ECP for all changes to the baseline configurations (Table 1). 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).

3.1.8 Technical Manual/Technical Order Updates (A010) and (A011)

The contractor shall update and deliver any changes to Technical Manuals, Technical Orders or Engineering Drawings/Data as part of this effort as described in Section 4.2.1.8.

3.1.9 Test Plans and Procedures (A012), DI-NDTI-80566A and (A013), DI-NDTI-80603A The contractor shall provide test plans and procedures to support Government Developmental Testing or any hardware/software testing performed as part of this effort.

3.1.10 Test/Inspection Report (A014) DI-NDTI-80809B

The contractor shall deliver test/inspection reports that result from any testing performed as part of this effort.

3.1.11 Reports/Records of Meetings/Minutes (A018) DI-ADMN-81505 The contractor shall provide reports/records of meetings described in Sections 4.2.2.1, 4.2.2.2.

3.1.12 Installation and Fielding Plan (A001) DI-MGMT-81118

The contractor shall support (1) 3 day fielding meeting annually and provide a detailed Installation and Fielding Plan.

3.1.13 Provisioning (A015)

The objective is for the contractor to identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability objectives in accordance with the Air Force Initial Provisioning Performance Specification (IPPS) and Contract Data Requirements Lists (CDRLs).

3.2 Specific Work Requirements

3.2.1 Software BCC Requirements

The contractor shall provide technical support, software maintenance/upgrades, and enhancements for the JRE software. 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 JRE software are in compliance with the approved System Requirements Document (SRD). (CDRL A004, DI-IPSC-81431A, System Requirements Document)

3.2.1.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:

1) Successful conduct of Developmental Test (DT)/Joint Interoperability Test (JIT)/Air Force System Interoperability Test (AFSIT)/Operational Test (OT) to include Force Development Evaluation (FDE), Operational Utility Evaluation (OUE), etc./Regression Test, etc

1) No priority one, 2A or 2B (as defined by IEEE/EIA 12207.2 Annex J) problem reports open as specified per delivery order

1) 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.

3.2.1.2 Technical Support

The contractor shall provide technical support for problem report/change request investigation and change proposal development, test environment support, and Independent Validation and Verification (IV&V) support. In addition, the contractor may be tasked to monitor technology as it progresses and make recommendations to the Government for inclusion in the current baseline version of the software application. Recommendations shall include performance, schedule, and cost components.

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

3.2.1.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 JRE-GW/JTEP 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 JRE/JRE-GW/JTEP 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. The support equipment includes non-prime system equipment necessary to support the operation of the Gateway such as cryptographic equipment, modem, etc.

3.2.1.5 Independent Validation and Verification Support

The contractor shall provide technical expertise on the JRE software for Government IV&V of the JRE-GW/JTEP systems, as required.

3.2.1.6 Software Maintenance and Update

The contractor shall make corrective changes, improvements, or upgrades to the software on a block cycle basis as directed by the Government in order to:

1) Correct identified defects and deficiencies.

2) Improve performance or other attributes, or adapt the software to a modified environment.

3) Incorporate new technologies, functionalities, and security upgrades.

3.2.1.6.1 Software Updates

The contractor shall update the JRE gateway manager software to ensure interoperability with the latest hardware/software configuration of Situational Awareness Data Link (SADL), Multifunctional Distribution Information System (MIDS), PRC-117, PSC-5 and other communication systems interfaced with JRE/JRE-GW/JTEP systems.

3.2.1.6.2 Testing and Approval

New software shall successfully complete Government testing and receive Government approval of all related documentation. The contractor shall be responsible for the development of JRE software capabilities caused by hardware/software configuration changes of SADL, MIDS, PRC-117, PSC-5 and other communication systems. The contractor shall support Government testing as well as the fielding of these capabilities. The contractor will perform interoperability developmental testing and shall fix any Trouble Reports (TRs) identified as a result of the Government developmental test effort. In addition, the contractor shall support any Government test activity associated with required field level operation testing.

3.2.1.7 Software Enhancement

The contractor shall enhance the software to incorporate new requirements or capability (including adapting the software to new operating environments (i.e. porting)) on a per delivery order basis as directed by the Government. An enhancement shall be defined as a new requirement or additional capability that changes a product.

3.2.1.8 Documentation/TR Fixes

The contractor shall update and maintain applicable software documentation when affected by software maintenance/upgrade or enhancement delivery order efforts. The contractor shall provide additional documentation when required for larger upgrade and enhancement delivery orders as directed by the government.

The contractor will work with the Government to identify and fix hardware and software TRs. The contractor shall make corrections to software documentation. The contractor shall resolve all CAT I (Priority 1A through 1E) and CAT II Priority 2A & 2B software and hardware defects (per TO 00-35D-54). Priorities 1A through 1C are considered Emergency Conditions; Priorities 1D through 2B are considered Urgent Conditions.

(Government expectation is that the contractor shall maintain the IA baseline established at CT&E. TR fixes generated by IA self-assessments, CT&E, vendor security updates and/or IAVA/TCNOs that have a CAT I will be fixed Other IA vulnerabilities will be discussed with the Government who will determine if the vulnerability will be fixed.

4.2.1.8.1 Technical Orders/Technical Manuals. The contractor shall provide the government with any required TOs in accordance with TMCR-86-01N.

4.2.1.8.2 Engineering Data: The contractor shall develop/produce/maintain and prepare for delivery a Technical Data Package (TDP) that accurately depicts approved changes to the JRE-JTEP systems. The TDP changes shall represent the approved, tested, and accepted configuration of the changed systems. TDP data includes, but is not limited to, changes to Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP changes integrated with existing data shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the changed product without additional design engineering effort or recourse to the original design activity or any third party. All engineering product definition data created as a result of this contract shall be considered a part of the TDP. The TDP shall be prepared for delivery in accordance with the CDRL specifying Data Item Description (DI-SESS-81000D) DD Form 1423. [DI-SESS-81000D/T].

4.2.1.8.3 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with WR-ALC/ENGLDC for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following: [DI-ADMN-81249A, DI-ADMN-81250A]

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.2.1.8.4 In-Process Review (IPR) of the TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The contractor shall notify WR-ALC/ENGLDC a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

[DI-ADMN-81249A, DI-ADMN-81250A]

4.2.1.8.5 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.2.1.8.6 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced under this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All approved engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All approved engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All approved engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering

Orders EO’s generated as a result of the preliminary data review.)

d. Revisions to existing drawings when the contractor is the current design activity shall result in the delivery of the entire document with no regards to how minor or major the revision.

[CDRL A010 and A011 Technical manual/Technical Order Updates]

3.2.1.9 Provisioning

Contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 should be used as a guide. Format must be consistent with existing government Provisioning data system (D220). The following Data Item Descriptions (DIDs) apply:

DI-ALSS-81529 Provisioning Technical Documentation (PTD)

Specific PTD to be submitted:

- Provisioning Parts List (PPL)

- Common and Bulk Items List (CBIL)

- Short Form Provisioning Parts List (SFPPL)

- Design Change Notices (DCNs)

- Spares Acquisition Integrated with Production (SAIP)

- Long Lead Items List (LLIL)

- Statement of Prior Submission (SPS)

DI-ALSS-81557 Supplemental Data For Provisioning (SDFP).

DI-ALSS-81530 SE Recommendation Data (SERD) – Standard/Modified Hand Tools List

Specific Summaries to be delivered:

- Support Equipment Recommendation Data (SERD)

- Standard Modified Hand Tools List [CDRL A015 Logistics Management Information Summary (LMI) Data Products, A016 Supplemental Data For Provisioning (SDFP),and A017 LMI Summaries]

3.2.1.10 Training

The contractor shall provide three training classes per years for a maximum of eight students per year. The contractor shall also, in conjunction with the Government, assess the need for any further 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 JRE/JRE-GW/JTEP system and maintenance environments and provide such update training when deemed necessary. Provide training for newly-assigned on-site maintenance personnel.

3.2.2 Test

The contractor shall support the combined testing process (combined test for JRE, JRE-GW, and CRC/NORAD JTEP) of JRE software and JRE-GW/JTEP systems for the execution of Government developmental test (DT), Air Force Systems Interoperability Testing (AFSIT), Joint Interoperability Testing (JIT) and Force Development Evaluation (FDE). The contractor shall develop test documentation based on requirements in the SRS, including test plans, procedures, scripts, scenarios, to support the execution of internal contractor test and evaluation, and to provide a baseline for Government-executed developmental testing.

[CDRL A012 and A013 Test Plan and Procedures]

[CDRL A014 Test/Inspection Report]

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

3.2.2.2 Support Test Readiness Reviews (TRR)

The contractor shall support TRR telecom as part of the TWG monthly / weekly telecons. In addition, the contractor will support one CONUS 1 day telecom with two test engineers.

3.2.2.3 Retest & 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 test duration; Four trips total; 20 man-days total.

3.2.2.4 Developmental Test (DT)

The contractor shall provide 2 engineers, each making 2 trips of 12 days each for a combined DT for JRE, JRE-GW, and the Transportable and Fixed JTEP systems. The contractor shall prepare and deliver DT test plans and procedures, SRS, SVD prior to DT and in accordance with the contract CDRLs and the Integrated Master Schedule (IMS). Two days travel for each trip is included in 12 day test duration; Four trips total; 48 man-days total.

3.2.2.5 Air Force System Interoperability Test (AFSIT)

The contractor shall support one 13 day combined AFSIT for JRE, JRE-GW, and the Transportable and Fixed JTEP systems. The contractor will supply up to two engineers to support AFSIT. 2 travel days for each trip is in addition to the 13 day testing duration; two trips total; 30 man-days total.

3.2.2.6 Operational Testing

The contractor shall support one combined Operational Test (FDE, OUE, OT, etc) for JRE, JRE-GW, and the Transportable and Fixed JTEP systems. The contractor shall provide a delta training course for up to 8 students at the FDE location prior to test. The contractor will supply one training instructor for 5 days for the delta training course and 14 days of FDE test support for a total of 19 continuous days including travel; one trip total.

3.2.3 System Refresh

The contractor shall work with the Government to identify system refresh strategies that may be implemented over the life of the contract. The contractor shall provide cost estimates and schedules to the Government for each strategy. If the Government accepts the contractors cost estimate and schedule, they will notify the contractor and the subtask statement, schedule, and cost estimate will become and addendum to this Statement of Work.

3.2.4 Repair Services

The contractor shall provide the necessary labor, materials, facilities and equipment required to analyze, troubleshoot, repair, overhaul and test JRE-GW/JTEP sets, 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 JRE-GW/JTEP to the users.

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

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.

3.2.4.2 Critical Items

Critical items of any category shall be expedited to the extent possible, as directed by the Production Management Specialist (PMS) through the Procuring Contracting Officer (PCO).

3.2.4.3 Over and Above Repairs – Work Request

3.2.4.3.1 Authorization

Written authorization for repair of recoverable items not listed, or engineering services not identified must be received from WR-ALC/GRWEDA 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).

3.2.4.3.2 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. These activities may include, but are not limited to:

· Engineering 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

3.2.5 Information Assurance

The contractor will support the JRE/JTEP IAM in completion of the DIACAP process for JRE/JTEP in preparation for obtaining an Authority to Operate (ATO) and Authority to Connect (ATC) from the Air Force Designated Approving Authority (DAA). In the event the DAA grants an Interim Authority to Operate (IATO) or Interim Authority to Connect (IATC) the contractor shall support the government IAM on IA actions until the ATO/ATC is granted. This involves providing system documentation and artifacts for input into the Certification and Accreditation (C&A) Workflow portion of the Enterprise Information Technology Data Repository (EITDR) (A006, DI-MISC-80508B, Technical Report-Study/Services).

3.2.5.1 Contractor Responsibilities

· The contractor shall implement IA controls as defined by DoD (8500.2, Information Assurance (IA) Implementation) and the DIACAP Knowledge Service, as well as specific IA controls required by the Air Force IAW AFI 33-210.

· The contractor shall determine with the government which DISA Security Technical Implementation Guides (STIGs), Security Readiness Reviews (SRRs), and Security Checklists are applicable to JRE/JRE-GW/JTEP’s C&A.

· The contractor must be fully knowledgeable of the system’s security features to support IA-related activities until a full ATO and ATC are granted.

· The contractor shall provide the Government with all test results via secure means as these test results might be classified.

· The contractor shall use manual or automated method to document the findings (vulnerabilities) on a classified network/SIPRNet in order for the Government (PMO) to generate a Plan of Action & Milestones (POA&M).

· The contractor shall regularly analyze and test all software source code included in the system via static analysis tools that are consistent with the DISA STIGs and the AF Software Assurance Center of Excellence (ASACoE).

· The contractor shall analyze the findings so as to identify any latent defects and attribute vulnerability categorization codes and review the test results and analysis report with the Government. The contractor shall deliver results of the source code analysis via the IDE or via secure channels if required.

· With the Government’s approval, contractor shall fix findings in accordance with Government approved priorities and schedule. The contractor must provide software free from all CAT I risks and satisfactorily mitigate all CAT II findings to achieve an ATO. (Ref. DoD 8510.01, DIACAP)

· The contractor shall obtain Government approval for the inclusion of all third party software (e.g., open-source, freeware, mobile code, source code or binaries) proposed for use on JRE/JRE-GW/JTEP prior to its use or integration, and meet the requirements defined in the current DISA Application Security and Development Security STIG (Technical Implementation Guide). Approval is accomplished by either selecting a product already approved for use on Air Force networks from an appropriate list or by following the Air Force Network Integration Center (AFNIC)/External Volume Serial Number (EVSN) instructions for obtaining an approval for use of such software. The contractor shall document the evaluation/approval status for each third party software item in a Software Evaluation Summary Form.

3.2.6 Interoperability Systems Management and Requirements Transformation (i-SMART/e-SMART)

3.2.6.1 Documentation of JRE Implementation of MIL-STD-6016 in i-SMART/e-SMART

The contractor shall identify the number of messages capable of being generated by JRE and shall add the messages that the JRE/JRE-GW/JTEP creates to the i-SMART/e-SMART data repository. The i-SMART process is now available via the following web site: http://www.ismart.us.

3.2.6.2 Documentation of JRE Implementation of MIL-STD-3011 in i-SMART/e-SMART

The contractor shall document how it has implemented MIS-STD-3011 into the JRE/JRE-GW/JTEP wherever it is less than the full implementation.

3.2.6.3 Documentation of JRE Implementation of MIL-STD-6020 in i-SMART/e-SMART

The contractor shall document how it has implemented MIS-STD-6020 into the JRE/JRE-GW/JTEP wherever it is less than the full implementation.

3.2.6.4 Government Responsibility Regarding i-SMART/e-SMART

The Government will provide the contractors with the necessary i-SMART/e-SMART training and access to relevant database repositories in order to facilitate accomplishment of the above tasks.

3.2.7 Program Management

The contractor shall provide internal management and control on all matters related to this PWS, from conception to final completion. A Program Manager (PM) shall be designated to serve as contractor’s focal point for the Government and will ensure successful fulfillment of all PWS requirements within the agreed upon schedule. The contractor PM shall report program status monthly in accordance with contract requirements. The report shall include milestone/task status, future plans, contract delivery status, and report preparer as defined in DI-MGMT-80368A.

(CDRL A002, DI-MGMT–80368A, Status Reports)

3.2.8 Hardware Engineering Change Proposal

Neither design nor functional capabilities shall be changed, modified or altered except when an Engineering Change Proposal (ECP) is submitted and approved in accordance with EIA 649. The contractor shall submit to WR-ALC/GRWEDA 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. ECPs generated and approved under a formal retrofit program may be implemented under this contract. However, costs associated with implementation shall be funded by the retrofit program. The authorized hardware configurations for repair under this PWS are listed in Table 1.

3.2.9 Configuration Management

The contractor shall manage and apply Configuration Management (CM) to hardware, software and documentation developed and delivered under this contract.

The contractor will maintain a formal configuration management system for the JRE/JRE-GW/JTEP 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 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 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 JRE program office CRB to review configuration changes as required. See Sec 4.2.12 for specific meeting support requirements.

Changes to the configuration(s) 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(s). The authorized hardware configurations for repair under this PWS are listed in Table 1.

(CDRL A008, DI- CMAN‑80639C, Engineering Change Proposal)

3.2.10 JRE/JRE-GW/JTEP Website

The contractor shall manage, and update the password-protected, multi-level access JRE/JRE-GW/JTEP web site to post all appropriate JRE/JRE-GW/JTEP information such as CDRLs, informal/formal documentation, IPT information, and work-in progress information. The contractor shall coordinate Website access with the Government program office.

3.2.11 Database Management

The contractor shall maintain a database of USAF JRE/JRE-GW/JTEP hardware and software configurations, referenced by serial number of each system, including versions of all software, hardware, location, points of contact (POC), and documentation items covered under this PWS. In addition, the contractor shall maintain a database for documenting deficiency reports, baseline change requests, and engineering change requests. Information from these databases shall be provided to the Government upon request, but no more than once per quarter.

3.2.12 Meeting Support

The contractor shall provide meeting support as identified in the below paragraphs. The contractor shall prepare and deliver agendas, presentations, meeting minutes and action item logs for Government approval in accordance with the contract CDRLs. The Government shall notify the contractor 30 days prior to any meeting requiring the contractor to provide meeting deliverables.

[CDRL A018 Reports/Records of Meetings/Minutes]

3.2.12.1 Program Management Review (PMR)

The contractor shall conduct and administratively support four Program Management Reviews. All PMRs shall be at Robins AFB, GA and last 3 days. The contractor shall provide to the Program Management Office (PMO) suggested agenda topics 10 days prior to the scheduled meeting. 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.