DSFS_PWS_Rev_RFI.pdf

Distribution Statement: E 1

Performance Work Statement (PWS) for

Air Force (AF) Distributed Common Ground System (DCGS)

Systems Release Field Support (DSFS)

16 Feb 2025

Distribution Statement E: Distribution authorized to DoD components only (Critical Technology and Direct Military Support) (20 Nov 13). Other requests for this document shall be referred to

AF DCGS Data Management Office, AFLCMC/HBG, 235 Byron St, Suite 19A, Robins AFB, GA 31098-1670.

Distribution Statement: E 2

Table of Contents

1.0 Description of Services:

1.1 Radio Frequency Intelligence (RFINT)

1.2 DCGS Open Architecture (OA) Platforms

1.3 Objective(s)

1.4 Benefit to United States Air Force (USAF)

2.0 Services Summary

3.0 Government Property: Government property will not be provided

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance (PoP)

4.1.2 Place of Performance

4.1.3 DSFS Locations and Support. Note: Government reserves the right to not exercise support for some sites in any particular ordering period based upon mission needs

4.1.4 Reserved

4.1.5 Reserved

4.1.6 Reserved

4.1.7 Collaborative Support Locations

4.2 DSFS Breakout of Requirements

4.2.1 Sensor Resource Manager (SRM) Position (Centralized sites)

4.2.2 Low Band System (LBS) Software (SW) Support (formally known as Communications Intelligence (COMINT))

4.2.3 High Band System (HBS) SW Support (formally known as Electronic Intelligence (ELINT) . 17

4.2.4 Maintenance Technician (MT) Position (site based and transitional support for SMCB 2.0) ... 19

4.3 Contract Data Requirements List (CDRL)

4.3.5 Quality of CDRL Deliverable

4.3.6 Receipt of CDRL Deliverable

4.4 Travel and Per Diem

4.5 Cybersecurity Requirements

4.6 Program and Management Objectives

4.7 Single Point of Contact (POC)

Distribution Statement: E 3

4.8 Maintenance Data Collection Systems

4.9 Configuration Management (CM)

4.10 Quarterly Program Reviews

4.11 Management and Program Objectives of the DSFS Program

4.12 Skills and Experience Profiles

4.13 Process Improvements

4.14 Availability Requirements

4.15 Metrics

4.16 Informal Maintenance Training

4.17 Informal Technical Training

4.18 Data Rights

4.19 Contracting Officer’s Representative (COR) and Contracting Officer’s Representative-Subject Matter Expert (COR-SME)

4.19.1 COR

4.19.2 COR-SME

4.20 Contractor Responsibilities (Program Management)

4.21 Contractor Training

4.22 Contract Notification and Technical Expert Status (TES) Package

4.23 Technical Expert Status Accreditation (TESA) Post Award

4.24 Personnel Access

4.25 Limited Use of Data and Information

4.26 Over and Above Work Procedures

4.27 Supervision of Contractor Employees

4.28 Performance Assessment Report (PAR)

4.29 Meetings

4.29.1 Contractor Meetings

4.29.2 Contractor’s Program Multi-Functional Team (MFT)

4.29.3 DSFS Site Lead Roles and Responsibilities

4.30 Associate Contractor Agreement (ACA)

4.31 Contractor Initial Manpower Transition Plan

5.0 General Information

5.1 Continuation of Mission Essential (ME) Services During a Crisis

Distribution Statement: E 4

5.1.1 Designation of Services as ME

5.1.2 ME Contractor Services Plan

5.2 Program Execution During Surges

5.3 Deployment Requirement

5.4 Other Requirements

5.5 Security Requirements

5.5.1 Security Regulations

5.5.2 Operations Security (OPSEC)

5.5.3 Communications Security (COMSEC)

5.5.4 Security Clearance

5.5.5 Security Incident or Violation

5.5.6 Access to Government System(s)

5.5.7 Access to Government Facility or Military Installation

5.5.8 Display of Identification (ID) Badges

5.5.9 Physical Security

5.5.10 Key Control

5.5.11 Lock Combinations

5.5.12 Common Access Card (CAC)

5.6 Environmental Management System (EMS)

5.7 Agency Affirmative Procurement Programs

5.8 Safety Requirements

5.8.1 Contractor Compliance

5.8.2 Mishap Notification/Investigation

5.8.3 Safety and Health Plan/Program

5.8.4 Voluntary Protection Program (VPP)

5.9 Inspection of Services

5.10 Contractor Manpower Reporting

5.11 Invoicing/Payment and Receipt/Acceptance

5.12 Contractor Personnel Relocation

5.13 Trafficking in Persons

5.14 Personnel Substitutions

Distribution Statement: E 5

5.15 Conduct of Contractor Personnel

5.16 Performance Based Contract

5.17 Government Responsibilities

5.18 On-Call Support

5.19 Performance Flexibility

5.20 Quality Management System (QMS)

6.0 Appendices

6.1 Appendix A, References

6.2 Appendix B, Acronyms

Distribution Statement: E 6

1.0 Description of Services:

1.1 DSFS Services

Distributed Common Ground System (DCGS), Systems Release Field Support (DSFS) services, support the sustainment of Intelligence, Surveillance and Reconnaissance (ISR) systems used for collection, correlation of data, and collaboration of signals of interest from airborne, ground, and other systems to provide near real time actionable intelligence to the DCGS analysts, the warfighter, Combatant Commanders, national mission partners, and others.

1.2 DCGS Open Architecture (OA) Platform

1.2.1 AF DCGS transitioned to an Open Architecture (OA) site based platform System Mission Capability Bundle (SMCB) 2.X and is in the process of transitioning to hub based Systems Team Radio Frequency Minimum Viable Capability Release (ST RF MVCR) 3.X. We are currently unable to identify when the transition to ST RF MVCR 3.X will be complete. The DSFS contract will support the transition from site to hub-based services, the transition to National Mission Partner Internet Protocol (IP) addresses, to sensor agnostic software/services, the transition from some OEM software to primarily Government Off The Shelf (GOTS) and National Mission Partner (NMP) software/services, incorporation of artificial intelligence, machine learning, cloud based services, U2 divestiture (uncertain when this will happen, current plan is for last operational mission to fly before Oct 2025), and other changes across the Period of Performance (PoP)/span of the contract, and other changes that have yet to be identified. This may include support for Project Nexus - the convergence of Battle Management Command and Control (BMC2), Intelligence, Surveillance and Reconnaissance (ISR), and targeting capabilities in a common digital environment. DSFS must remain flexible as we transition DCGS systems/software for Great Power Competition. GPC may involve the connection to Advanced Battle Management System (ABMS) and Combined Joint All Domain Command & Control (CJADC2), Department of the Air Force Battle Network (DAFBN), National Mission Partner clouds and networks, DCGS Digital, and infrastructure/services to counter Denied, Degraded, Intermittent and Limited (DDIL) communications at DGS-4, DGS-5, and PCS. Due to the complexity and uncertainness of these changes this PWS is broken into 4 separate timeframes each with separate underlying requirements. These are SMCB 2.0 (site based – Option One), SMCB 2.0 and ST RF MVCR 3.X (Partial Site Based with Hub – Option Two), ST RF MVCR 3.X (Fully Hub based Option Three), and after U2 operational missions cease (Option Four).

Additional options that may fall under these overarching options will be discussed and must be planned for with separate CLIN giving the government significant flexibility over the course of the contract. This PWS reflects the most up to date information we have.

1.2.1.1. Sensor Management - The Maintenance Technician (MT) position exists at the sites and will transition from the sites to the East Coast Hub (ECH @ Langley AFB, VA) and West Coast Hub (WCH @ Beale AFB, CA) and the position redesignated as the Sensors Resource Management (SRM) position. Due to space limitations existing workstations may need to be moved to other facilities at Langley and Beale AFB. MT and SRM positions will be captured under a separate CLIN. The transition to ST RF MVCR 3.0 is currently underway but we are unable to identify when this will complete. Individual sites will transition support to the hubs as sites Transition to Operations (TTO). Under ST RF MVCR 3.X, one SRM will be capable of

Distribution Statement: E 7 supporting multiple missions at multiple sites simultaneously (at this point we are uncertain what the limitation (software and human)) will be. The MT position will remain at PCS (this may be centralized if the U2 were extended and we did not to start divestment in 2025, it is dependent on the network). The MT position will be priced as a separate CLIN for each site (SMCB 2.0).

We currently expect all MT and SRM positions to go away with the divestment of the U2 and ASIP sensor Oct 2025. There is a possibility that the U2 will not start divestment Oct 2025 so this must be planned for in this contract. Separate CLIN will be created for MT and SRM positions to allow the government the flexibility to transition from MT to SRM and to remove all MT and SRM requirements on the contract when no longer required. Intent is for future sensors to not require sensor management from DCGS. If a new sensor were to require sensor management from DCGS, we would use these same CLIN to reintroduce SRM at Langley and Beale and possibly MT to PCS.

1.2.1.2. Software Support - High Band System (HBS) and Low Band System (LBS) Software (SW) support will also transition from sites to the hubs with ST RF MVCR 3.X. With the possible exception of PCS, we expect software support to be centralized at the ECH/WCH. We require separate CLIN for each site as we are uncertain when the site software support will transition to the hubs. This is NOT a software development contract.

1.2.1.3. Hardware Maintenance - As of 1 March 2023, 1D7XX AFSC personnel (blue suit maintenance) at most DCGS sites are responsible for all Open Architecture (OA) hardware maintenance (touch maintenance). DSFS will provide on-site maintenance support at DMS-MD, DMS-GA, DMS-TX, and PCS (based on blue suit and network capabilities we may transition on-site support at PCS to hub-based support from ECH/WCH) where we do not have blue suit maintenance. Each site with hardware maintenance will be treated as a separate CLIN. With the transition from Crew Communications to Enterprise Collaboration Capability (ECC) we intend for the DFSF at DMS-GA, DMS-MD, DMS-TX and possibly PCS to maintain the on-site portion of ECC.

1.2.2 DCGS is the Combat Air Force Weapon system for planning, direction, collection, processing, exploitation, production, and dissemination to conduct problem centric, sensor agnostic analysis. It is an Information Technology (IT)-based, distributed ISR weapon system that interconnects platforms, sensors, shooters, Processing, Exploitation and Dissemination (PED) crews and Analysis and Exploitation Teams (AET) to provide critical intelligence to the warfighter, Combatant Commanders, coalition partners, national mission partners, all US military services, and others. It is designed to provide intelligence information across the entirety of the AF ISR enterprise using a structured, agile approach.

1.2.3 The DCGS Platform provides the baseline Hardware (HW), enterprise Software (SW) and services for the weapon system applications to run on. DSFS shall maintain and sustain Radio Frequency Intelligence SW applications (Apps) across the applicable DCGS Sites.

1.3 Objective(s)

This PWS describes the DSFS services required to support the AF DCGS. The DSFS services includes but will not be limited to support for the following: Electronic Intelligence (ELINT) software and services, Communications Intelligence (COMINT) software and services, NMP software and services, Multi-Source Correlation System (MSCS) – transitioning to hub based

Distribution Statement: E 8 and cloud based services; Joint Signal Processor (JSP); RF Sensor Simulators; and other systems. As DCGS prepares for Great Power Competition support for Denied, Degraded, Intermittent and Limited (DDIL) communications may be required for DGS-4, DGS-5, and PCS. This does not necessarily mean we will need personnel at these sites. Our primary strategy is to provide support for DDIL requirements remotely from the East and West Coast hubs with blue suit support for limited disconnects. A separate CLIN will be used if a minimal support capability is required at DDIL sites (this should be priced). Contractor will provide emergency response capability from ECH/WCH. The DSFS structure shall be responsible and accountable for, but not limited to the following:

• Sustainment responsibilities essential for maintaining DCGS HW and SW, specifically:

o System maintenance o Integration o Configuration management (PWS paragraph 4.9) o User training (PWS paragraph 4.16 and 4.17) o System administration for OEM, Government Off the Shelf (GOTS), Free Open

Source Software (FOSS), and Commercial Off the Shelf (COTS) SW o Program management o Hardware support is only required for sites indicated in PWS para 4.1.3.

o COTS SW support in accordance with Software Version Description

Documents (SVDD) for the DSFS systems. These documents will be provided to the contractor.

• Performs Sensors Resource Management (SRM) duties (Centralized) for the enterprise until the

U2 divests

• Performs Maintenance Technician (MT) duties (Site based - SMCB 2.0). Will continue to be performed at PCS until U-2 divests or centralized support is possible.

• Performs Low Band System (LBS) SW and High Band System (HBS) SW duties.

Our desire is for individuals to be able to support both bands. However, this is not a requirement.

• Possession of detailed technical knowledge and demonstrates operation proficiencies of the DCGS Radio Frequency Intelligence systems and associated sub-systems

• Responsible for providing HW and SW deficiency analysis (related to DCGS Radio Frequency Intelligence HW and SW)

• Responsible for providing HW and SW corrective actions (related to DCGS Radio Frequency Intelligence HW and SW)

• Responsible for providing HW and SW configuration management (related to DCGS Radio Frequency Intelligence HW and SW)

• Responsible for following all security direction during mission operations, integration, sustainment, and training activities

• Follows all policies, processes and procedures as prescribed by the Government Program Management Office (PMO) and site leadership. Where conflicts occur, or in the absence of site guidance, the DSFS personnel shall default to specified Government PMO requirements or guidance as well as Department of Defense (DoD) and other Government agency instructions

Other service objectives include (PWS para 2.0):

Distribution Statement: E 9

• Maintain an Ao level of 99.5% minimum

• Provide qualified contractor personnel

• Meet quality and receipt of Contract Data Requirements List (CDRL) requirements

• Provide timely and accurate Contractor manpower reports

• Adhere to the Contractor’s Quality Management System (QMS).

Distribution Statement: E 10

1.4 Benefit to United States Air Force (USAF)

This acquisition will benefit the USAF through maintaining required weapon system availability to support operations and sustainment of ISR systems for the collection, correlation of data, and collaboration of signals of interest in order to provide near real time actionable intelligence to the warfighters; thereby enabling the USAF to fly, fight, and win in air, space and cyberspace.

2.0 Services Summary

This Service Summary identifies the performance objectives that will be monitored and the performance thresholds in which these objectives will be evaluated. Metrics regarding the evaluation of these performance objectives can be found in the Quality Assurance Surveillance Plan (QASP).

Performance

Objective

PWS

Reference Performance Threshold

DSFS Operational Availability (Ao) (Service/Subsystem)

4.14

4.15

The Contractor shall maintain DSFS Ao at a minimum uptime ratio (UTR) of 99.5% for each RF system and overall RF systems at each DSFS location.

Availability shall not fall below this threshold for more than four hours in any continuous 24 our period.

Quality of CDRL Deliverable

4.3.5

4.20.2

The Contractor shall meet the quality content requirements specified in the Contract Data Requirement List (CDRLs) of the PWS at a rate of 95% of the time. There shall be no more than one rejection of any deliverable. There shall be no more than two total rejections of deliverables per contract year. The Government will reject a deliverable if any technical errors or five or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

Receipt of CDRL Deliverable

4.3.6 There shall be no more than two late submissions 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.

Contractor Personnel Qualifications

4.12

4.21

Contractor/subcontractor personnel shall meet, at a minimum, the qualifications (both technical and management) identified in the PWS.

Distribution Statement: E 11

Performance Objective

PWS

Reference

Performance Threshold

Contractor Manpower Reporting

5.10 Within 30 calendar days of contract award, the

Contractor shall establish a record for the contract in SAM (System for Award Management) including Contract Data, Contact Data and Location Data.

The Contractor shall provide a count of contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than 30 days after the completion of the period of performance.

Management of Contractor Personnel

4.12

4.20

4.21

Contractor/subcontractor personnel shall meet, at a minimum, the qualifications (both technical and management) identified in the PWS. The Government expects the Contractor to provide a reasonable mix of skills and experience to fulfill the requirement by providing distinct categories of entry, mid-level, and expert personnel within each defined role. Upon identification of any shortcomings that will impact tasks assigned under this contract, the Contractor shall undertake corrective action and notify the Government within 15 calendar days.

Adherence to Contractor QMS

5.20 The Contractor shall submit a Quality Control Plan

(QCP) and be 100% compliant with the QMS.

3.0 Government Property: Government property will not be provided.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance (PoP)

Any supplies or services to be furnished shall be ordered by issuance of delivery orders or task orders. Such orders may be issued from date of award through five years. The Contractor shall

Distribution Statement: E 12 not be required to make any deliveries or provide any services after the period of performance of the last order issued under the contract. The PoP applicable to each task shall be specified in each individual order.

4.1.2 Place of Performance

These services, as defined in Section 1.3 of this PWS, will be performed at AF DCGS locations worldwide. These locations are in the Continental United States (CONUS) and Outside the

CONUS (OCONUS).

4.1.3 DSFS Locations and Support. Note: Government reserves the right to not exercise support for some sites in any particular ordering period based upon mission needs.

Option One Site Based only Site Designation On-Site

Support Fixed Hours of coverage

Surge hours of Coverage

On-Call Response time

DGS-1 MT 16/7 8/7

Langley AFB, VA LBS/HBS 16/7 8/7 Note: 1, 2, 12, 16 No

Hardware

DGS-2 MT 16/7 8/7

Beale AFB, CA LBS/HBS 16/7 8/7

DGS-4 MT 16/7 8/7

Ramstein AB, Germany LBS/HBS 16/7 8/7

DGS-5 MT 16/7 8/7

Hickam AFB, HI LBS/HBS 16/7 8/7

DGS-IN MT

Terre Haute, IN LBS/HBS 8/5 up to

24/7

1.5 hrs

Note: 9, 12, 16 No

DGS-KS MT

Witchita, KS LBS/HBS 8/5 up to

24/7

1.5 hrs

DGS-MA MT

Distribution Statement: E 13

Cape Codd, MA LBS/HBS 8/5 up to 24/7

1.5 hrs

DMS-GA N/A

Fort Eisenhower, GA LBS

Only 16/7 8/7

Note: 11, 12, 14 Hardware 16/7 8/7

DMS-GE N/A

Darmstadt, AB, GE N/A Note: 7, 14, 16 N/A

DMS-HI N/A

Within 20 miles of

DGS-5

N/A

Note: 8, 14, 16 N/A

DMS-MD N/A

Fort Meade, MD LBS

Only 16/7 8/7

Note: 11, 12, 14 Hardware 16/7 8/7

DMS-TX N/A

San Antonio, TX LBS

Only 16/5 8/5

&24/2

1.5 hrs

Note: 5, 11, 12, 14 Hardware 16/5 8/5 &24/2

1.5 hrs

DMS-UT N/A

Salt Lake City, UT LBS

Only 8/5 up to

24/7

1.5 hrs

Note: 12, 14, 16 No

PCS MT 16/7 8/7

N/A LBS/HBS 16/7 8/7

Note: 1, 2, 4, 11, 12 Hardware 16/7 8/7 Langley AFB Centralized

SRM

Langley AFB, VA LBS/HBS Note: No

Beale AFB Centralized SRM Beale AFB, CA LBS/HBS Note: No

DGS-X MT 12/5 4/5&16/2

Langley AFB, VA LBS/HBS 12/5 4/5&16/2

Distribution Statement: E 14

Note: 1, 2, 12, 13, 16 No

Option 2 Partial Site Based With Hub

Support Fixed Hours of coverage

Surge hours of Coverage

On-Call Response time

DGS-1 N/A

Langley AFB, VA LBS/HBS 16/7 8/7 Note: 1, 12, 15, 16 N/A

DGS-2 N/A

Beale AFB, CA LBS/HBS 16/7 8/7 Note: 1, 12, 15, 16 N/A

DGS-4 N/A

Ramstein AB, Germany LBS/HBS 16/7 8/7 Note: 1, 12, 15, 16 N/A

DGS-5 N/A

Hickam AFB, HI LBS/HBS 16/7 8/7 Note: 1, 12, 15, 16 N/A

DGS-IN N/A

Terre Haute, IN LBS/HBS 8/5 up to

24/7

1.5 hrs

Note: 9, 12, 15, 16 N/A

DGS-KS N/A

Witchita, KS LBS/HBS 8/5 up to

24/7

1.5 hrs

Note: 9, 12, 15, 16 N/A

DGS-MA N/A

Cape Codd, MA LBS/HBS 8/5 up to

24/7

1.5 hrs

Note: 9, 12, 15, 16 N/A

DMS-GA N/A

Fort Eisenhower, GA LBS 16/7 8/7 Note: 11, 12, 14 Hardware 16/7 8/7

DMS-GE N/A

Darmstadt, AB, GE N/A Note: 7, 14, 16 N/A

DMS-HI N/A

Distribution Statement: E 15

Within 20 miles of

DGS-5

N/A

Note: 8, 14, 16 N/A

DMS-MD N/A

Fort Meade, MD LBS 16/7 8/7 Note: 11, 12, 14 Hardware 16/7 8/7

DMS-TX N/A

San Antonio, TX LBS 16/5 8/5

&24/2

1.5 hrs

Note: 5, 11, 12, 14 Hardware 16/5 8/5 &24/2

1.5 hrs

DMS-UT N/A

Salt Lake City, UT LBS 8/5 up to

24/7

1.5 hrs

Note: 12, 14, 16 N/A

PCS MT 16/7 8/7

N/A LBS/HBS 16/7 8/7

Note: 2, 4, 11, 12 Hardware 16/7 8/7 Langley AFB Centralized

SRM 16/7 8/7 1.0

Langley AFB, VA LBS/HBS 16/7 8/7 1.0 Note: 1, 2, 10, 16, 17 N/A Beale AFB Centralized SRM 8/7 16/7 1.0 Beale AFB, CA LBS/HBS 8/7 16/7 1.0 Note: 1, 2, 10, 16, 17 N/A

DGS-X MT/SRM 12/5 4/5&16/2

Note: 1, 2, 12, 13, 16 N/A

Option Three Fully Hub Based

Support Fixed Hours of coverage

Surge hours of Coverage

On-Call Response time

DGS-1 N/A

Langley AFB, VA N/A Note: 16 N/A

DGS-2 N/A

Beale AFB, CA N/A Note: 16 N/A

DGS-4 N/A

Distribution Statement: E 16

Ramstein AB, Germany N/A Note: 16 N/A

DGS-5 N/A

Hickam AFB, HI N/A Note: 16 N/A

DGS-IN N/A

Terre Haute, IN N/A Note: 16 N/A

DGS-KS N/A

Witchita, KS N/A Note: 16 N/A

DGS-MA N/A

Cape Codd, MA N/A Note: 16 N/A

DMS-GA N/A

Fort Eisenhower, GA N/A Note: 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-GE N/A

Darmstadt, AB, GE N/A Note: 7, 14, 16 N/A

DMS-HI N/A

Within 20 miles of

DGS-5

N/A

Note: 8, 14, 16 N/A

DMS-MD N/A

Fort Meade, MD N/A Note: 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-TX N/A

San Antonio, TX N/A Note: 5, 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-UT N/A

Salt Lake City, UT N/A Note: 14, 16 N/A

PCS MT 16/7 8/7

N/A LBS/HBS 16/7 8/7

Note: 1, 2, 4, 11, 12 Hardware 16/7 8/7 Langley AFB Centralized

SRM 16/7 8/7 1.0

Langley AFB, VA LBS/HBS 16/7 8/7 1.0

Distribution Statement: E 17

Note: 1, 10, 15, 16, 17 N/A Beale AFB Centralized SRM 8/7 16/7 1.0 Beale AFB, CA LBS/HBS 8/7 16/7 1.0 Note: 1, 10, 15, 16, 17 N/A

DGS-X MT/SRM 12/5 4/5&16/2

Note: 1, 2, 12, 13, 16 N/A

Option Four U-2 Operational Missions Cease

Site Designation On-site Support

Fixed Hours of coverage

Surge hours of Coverage

On-Call Response time

DGS-1 N/A

Langley AFB, VA N/A Note: 16 N/A

DGS-2 N/A

Beale AFB, CA N/A Note: 16 N/A

DGS-4 N/A

Ramstein AB, Germany N/A Note: 16 N/A

DGS-5 N/A

Hickam AFB, HI N/A Note: 16 N/A

DGS-IN N/A

Terre Haute, IN N/A Note: 16 N/A

DGS-KS N/A

Witchita, KS N/A Note: 16 N/A

DGS-MA N/A

Cape Codd, MA N/A Note: 16 N/A

DMS-GA N/A

Fort Eisenhower, GA N/A Note: 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-GE N/A

Darmstadt, AB, GE N/A

Distribution Statement: E 18

Note: 7, 14, 16 N/A

DMS-HI N/A

Within 20 miles of

DGS-5

N/A

Note: 8, 14, 16 N/A

DMS-MD N/A

Fort Meade, MD N/A Note: 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-TX N/A

San Antonio, TX N/A Note: 5, 11, 12, 14 Hardware 8/5 1.5 hrs

DMS-UT N/A

Salt Lake City, UT N/A Note: 14, 16 N/A

PCS N/A

N/A LBS/HBS 16/7 8/7 1.0

Note: 1, 4, 11, 12 Hardware 16/7 8/7 1.0 Langley AFB Centralized

N/A

Langley AFB, VA LBS/HBS 16/7 8/7 1.0 Note: 1, 10, 16, 17 N/A Beale AFB Centralized N/A Beale AFB, CA LBS/HBS 8/7 16/7 1.0 Note: 1, 10, 16, 17 N/A

DGS-X N/A

Note: 1, 12, 13, 16 N/A

Note 1 - MT and SRM positions will end with U-2 last operational mission Note 2 - MT position is site based sensor management and will be provided if the U2 does not divest by award of this contract.

Note 3 – LBS, HBS and SRM (if the U-2 has not divested) are provided remotely from the ECH and WCH Note 4 - PCS-FSK is located within 75 miles of PCS. It requires DCGS workstation support remotely, via phone, or touch labor (hands-on) support via PCS DSFS positions.

Note 5 - DMS-TX 24/5 Hours of Coverage is not a traditional Monday through Friday, eight hour shift operation. The 24/5 Hours of coverage may be obtained in any form or combination of days and hours during the week to meet mission needs.

Note 6 – MT (if the U-2 has not divested, LBS and HBS will be provided at site unless services are capable of being provided from ECH and WCH.

Note 7 – DMS-GE is located at Darmstadt, AB, GE, approximately 80 miles from DGS-4. It requires systems support remotely and via phone. DGS-4 blue suit are responsible for the hardware.

Note 8 – DMS-HI is located within 20 miles of DGS-5. It requires systems support remotely and via phone. DGS-5 blue suit are responsible for the hardware.

Note 9 – ANG personnel provide MT position

Distribution Statement: E 19

Note 10 – Surge at Centralized sites should not be based on war as they are already providing 24/7 support for the enterprise. Surge will be based on factors that reduce/eliminate operational capability at one of the Centralized sites.

Examples include: hurricane, fire, earthquake, pandemic, etc.

Note 11 – At sites without Blue Suit maintenance support, contractor may be required to provide hardware maintenance/touch labor. Hardware maintenance/touch labor includes preventive maintenance inspections, hardware fault isolation, hardware resets, hardware remove and replace, hardware configuration, and collaborative maintenance including supporting vendors for warranty support.

Note 12 – Fixed hours of coverage may change based on U-2 mission changes. Hours of Coverage is not a traditional Monday through Friday, eight hour shift operation. The hours of coverage may be obtained in any form or combination of days and hours during the week to meet mission needs.

Note 13 – DGS-X mission requires testing days, nights, and weekends. In addition, DGS-X can be used for Continuity of Operations Plan (COOP). Surge requirements are to go from 12/5 to 16/7 hours of coverage, which requires the addition of 4 hours x 5 days a week to get to 16/5 and an additional 16 hours x 2 days, for the remainder of the week. DGS-X requires at least one Low Band Senior Mid-Level, one High Band Senior Mid-Level, and one SRM/MT Expert (one person capable of doing both functions if the U-2 has not divested).

Note 14 - DMS sites do not have an MT/SRM position. Sensor management is provided by Core, PCS, or ECH/WCH Centralized Remote support Note 15 - SRM is provided by Remote Centralized support from Langley and Beale

Note 16 - HW maint is provided by blue suit or another contract

Note 17 - The contractor will provide flyaway support for DDIL and other contingencies

4.1.4 Reserved.

4.1.5 Reserved

4.1.5.1 Reserved

4.1.5.2 Reserved.

4.1.6 Reserved.

4.1.7 Collaborative Support Locations

DCGS will establish RF Collaborative support. Collaborative support is defined as centralized, remote, and on-call support.

4.1.7.1 Centralized support will be provided from two geographic locations; Langley AFB, VA and Beale AFB, CA for LBS and HBS. Current plan is to transition to centralized support from the ECH and WCH prior to contract award. Tactics, Techniques, and Procedures for SRM, LBS, and HBS will be developed and provided by current contract. SRM will be provided by contractor if the U-2 does not divest by the award of this contract. MT will be provided at PCS by contractor if the U-2 does not divest by the award of this contract.

4.1.7.2 On-call support will be provided from the remaining DGS and DMS sites based on available manning, expertise, and in coordination with the assigned centralized location and the DCGS Operations Center (DOC).

4.1.7.3 Surge at Centralized sites should not be based on war as they are already providing 24/7

Distribution Statement: E 20 support for the enterprise. Surge will be based on factors that reduce/eliminate operational capability at one of the Centralized sites. Examples include: hurricane, fire, earthquake, pandemic, etc.

4.1.7.4 Fly away support for DDIL at DGS-4, DGS-5, and PCS will be provided by contractor.

4.2 DSFS Breakout of Requirements

4.2.1 Sensor Resource Manager (SRM) Position (Centralized sites) (required if U-2 does not divest by the beginning of the contract)

The Contractor shall be responsible and accountable for SRM support for the following:

Distribution Statement: E 21

• Manages multiple airborne RF sensor missions for 2 or more Core sites and associated DMS sites and their processes simultaneously from the ECH or WCH

• Operates and interfaces with multiple aircraft, airborne sensors, sites, networks, systems, and operations and maintenance personnel

• Provides updates to Sensor Resources Management processes

• Provides sensor troubleshooting and airborne fault resolution; identifies, resolves, and communicates issues with LBS, HBS, infrastructure, enterprise services, other RF systems; support and recommend updates to RF systems, SW, and networks

• Provides technical and engineering support for sensors and networks

• Creates, updates, and responds to Incident tickets

• Manages data encryption changes and implementation

• Monitors the RF enterprise and networks health/status (Sensor, platform, network paths to include crypto, DCGS RF systems, and RF related enterprise services)

• Provides comprehensive analysis, diagnostics and fault isolation for the RF systems and networks associated with ground components

• Provides comprehensive analysis, diagnostics and fault isolation for the RF sensors and associated End-to-End Sensor paths, and systems defined in paragraph 1.3

• Subject Matter Expert (SME) that provides RF and networks sustainment support during system upgrades

• Coordinates efforts for sensor/system and network restoration

• Supports post upgrade SW/HW efforts in accordance with (IAW) tech data, Tactics, Techniques and Procedures (TTPs), and Operating Instructions (OIs). Provides OJT to AFP and identifies RF and networks sustainment support improvements that reduce logistics footprint

• Provides RF process and network improvements/recommendations

• Create Mission Debriefs in DCGS provided system; provide systems status (includes sensor) to operations and maintenance personnel prior to takeoff; update operations and maintenance personnel with status if required during mission; obtains inputs from associated sites operations and maintenance personnel after mission concerning sensor and systems performance; completes RF portion of end to end mission debrief and closes debrief if appropriate.

• Pre-mission responsibilities o Ensures RF and networks systems readiness, system/mission configuration relative to the sensor and communication link o Performs RF and networks pre-mission tasks (system reboots, ground rings, etc.)

o Completes RF, network, and COMSEC data input for mission templates

• Mission execution responsibilities o Provides real-time RF and networks assistance to flightline maintenance personnel (aircraft and sensor), pilot, maintainers, operators and users o Documents issues with RF End-to-End process/systems o Monitors RF sensors, DSFS systems, and networks; using Government provided tools, takes appropriate action to restore sensors, DSFS systems, networks paths/capabilities, and processes by performing process resets, power cycles, collaborative maintenance, etc.

Distribution Statement: E 22

• Post-mission responsibilities o Evaluates RF sensor/ground and networks anomalies such as maintenance actions and Incident tickets o Submits RF and networks Incident tickets and performs SW maintenance actions as required o Completes RF End-to-End mission debriefs (incorporates mission/system issues encountered by DGS and DMS operations and maintenance personnel) and ensures appropriate maintenance personnel are aware of issues

• Specific Position Requirements o Personnel who’s operational or maintenance duties require them to have National Mission

Partner (NMP) accounts must meet Counter Intelligence polygraph requirements.

o Entry level acceptable minimums

Certifications

• DoD 8570.1 (IAT Level II or IAM Level I)

Personal Qualifications

• Associates’ Degree in Technical Field or ≥5 years of DCGS experience

• TS/SCI Security Clearance

Experience

• ≥3 yrs of Information System Security Management

• ≥2 yrs of DCGS experience o Mid-level acceptable minimums Certifications

• DoD 8570.1 (IAT Level II or IAM Level I) Personal Qualifications

• Associates’ Degree in Technical Field or ≥7 years of DCGS experience

• TS/SCI Security Clearance Experience

• ≥5 yrs of Information System Security Management

• ≥5 yrs of DCGS experience

• ≥2 yrs performing this position, or a similar RF sensor management position o Expert level acceptable minimums

Certifications

• DoD 8570.1 (IAT Level II or IAM Level I)

Personal Qualifications

• Bachelors' Degree in Technical Field

• TS/SCI Security Clearance

Experience

• ≥10 yrs of Information System Security Management

• ≥10 yrs of DCGS experience

• ≥5 yrs performing this position, or a similar RF sensor management position

Distribution Statement: E 23

4.2.2 Low Band System (LBS) Software (SW) Support (formally known as Communications Intelligence (COMINT))

The Contractor shall be responsible and accountable for LBS SW Support for the following:

• Manages/supports LBS SW and processes

• Maintains LBS SW to operate and interface with multiple sensors, sites and systems

• Provides LBS technical and engineering SW support

• Provides system administration for LBS SW components

• Performs system administration support to the Planning and Direction, Collection, Processing and Exploitation, Analysis and Production, and Dissemination (PCPAD) processes

• Creates, updates, and responds to LBS Incident tickets

• Provides comprehensive analysis, diagnostics and fault isolation for the RF

SW/systems associated with ground components

• Supports SRM or MT in comprehensive analysis, diagnostics and fault isolation for the

RF system/sensors and associated End-to-End network paths

• RF SME that provides sustainment support during system upgrades

• Supports data encryption changes and implementation

• Supports post upgrade efforts IAW tech data, TTPs, and OIs. Provides OJT to AFP and identifies sustainment support improvements that reduce logistics footprint

• Performs Time Compliance Technical Order (TCTO), Time Compliance Network Orders

(TCNO), etc as directed

• Pre-mission responsibilities o Supports SRM or MT for LBS system readiness, system/mission configuration relative to the sensor or communications link o Supports LBS pre-mission tasks (system reboots, ground rings, etc.)

• Mission execution responsibilities o Provides real-time RF assistance/support to the SRM or MT, maintainers, operators and users o Collects LBS information for mission debrief

• Post-mission responsibilities o Evaluates LBS anomalies such as maintenance actions and Incident tickets o Submits LBS Incident tickets and performs SW (HW through collaborative support) maintenance actions as required o Provides LBS information for mission debrief to SRM or MT

• Specific Position Requirements o Personnel at NSA sites and those who’s operational or maintenance duties require them to have National Mission Partner (NMP) accounts must meet Counter Intelligence polygraph requirements.

o Low Band - Journeyman Entry level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications

Distribution Statement: E 24 o Associates’ Degree in Technical Field or ≥5 years of DCGS experience o TS/SCI Security Clearance

• Experience o ≥1 yr of COMINT Mid-level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Associates’ Degree in Technical Field or ≥7 years of

DCGS experience o TS/SCI Security Clearance

• Experience o ≥2 yrs of COMINT

• Additional Experience (one of the following) o ≥1 yr of AF DCGS experience o ≥1 yr of AF RF

Expert level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥3 yrs of COMINT o ≥3 yrs of AF DCGS experience o ≥3 yrs of AF RF o Low Band - Senior Entry level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥5 yrs of COMINT o ≥5 yrs of DCGS experience o ≥5 yrs of RF

Mid-level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥10 yrs of COMINT

Distribution Statement: E 25 o ≥10 yrs of DCGS experience o ≥10 yrs of RF

Expert level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level III or IAM Level II)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥15 yrs of COMINT o ≥15 yrs of DCGS experience o ≥15 yrs of RF

4.2.3 High Band System (HBS) SW Support (formally known as Electronic Intelligence

(ELINT))

The Contractor shall be responsible and accountable for HBS SW Support for the following:

• Manages/supports HBS SW and processes

• Provides system administration for ELINT SW

• Maintains all HBS SW to operate and interface with multiple sensors, sites and systems

• Provides HBS technical and engineering SW support

• Creates, updates, and responds to HBS Incident tickets

• Performs system administration support to the PCPAD process

• Provides comprehensive analysis, diagnostics and fault isolation for HBS SW/systems associated with ground components

• Supports SRM or MT in comprehensive analysis, diagnostics and fault isolation for the system/sensors and associated RF End-to-End network paths

• HBS SME that provides sustainment support during system upgrades

• Provides HBS process and data link improvements/recommendations

• Supports data encryption changes and implementation

• Supports RF post upgrade efforts IAW tech data, TTPs, and OIs. Provides OJT to AFP and identifies sustainment support improvements that reduce logistics footprint

• Performs TCTO, TCNO, etc as directed

• Pre-mission responsibilities o Supports SRM or MT for HBS readiness, system/mission configuration relative to the sensor or communications link o Supports HBS pre-mission tasks (system reboots, ground rings, etc.)

• Mission execution responsibilities o Provides HBS real-time assistance/support to the SRM or MT, maintainers, operators and users o Collects HBS information for the mission debrief

• Post-mission responsibilities o Evaluates HBS anomalies such as maintenance actions and Incident tickets o Submits HBS Incident tickets and performs maintenance actions as required

Distribution Statement: E 26 o Provides HBS information for mission debrief to SRM or MT

• Specific Position Requirements o Personnel who’s operational or maintenance duties require them to have National Mission Partner (NMP) accounts must meet Counter Intelligence polygraph requirements.

o High Band - Journeyman Entry level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Associates’ Degree in Technical Field or ≥5 years of

DCGS experience o TS/SCI Security Clearance

• Experience o ≥1 yr of ELINT

Mid-level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Associates’ Degree in Technical Field or ≥7 years of DCGS experience o TS/SCI Security Clearance

• Experience o ≥2 yrs of ELINT

• Additional Experience (one of the following) o ≥1 yr of AF DCGS experience o ≥1 yr of AF RF

Expert level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥3 yrs of ELINT o ≥3 yrs of AF DCGS experience o ≥3 yrs of AF RF o High Band - Senior Entry level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥5 yrs of ELINT o ≥5 yrs of DCGS experience

Distribution Statement: E 27 o ≥5 yrs of RF

• Mid-level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level II or IAM Level I)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥10 yrs of ELINT o ≥10 yrs of DCGS experience o ≥10 yrs of RF

Expert level acceptable minimums

• Certifications o DoD 8570.1 (IAT Level III or IAM Level II)

• Personal Qualifications o Bachelor's Degree in Technical Field o TS/SCI Security Clearance

• Experience o ≥15 yrs of ELINT o ≥15 yrs of DCGS experience o ≥15 yrs of RF

4.2.4 Maintenance Technician (MT) Position (site based) (required if U-2 does not divest by the beginning of the contract)

The MT position shall be responsible and accountable for the following:

• Manages multiple airborne RF sensor missions and processes simultaneously at a

Core site

• Operates and interfaces with multiple aircraft, airborne sensors, sites, networks, systems, and operations and maintenance personnel

• Provides updates to Maintenance Technician position processes

• Provides sensor troubleshooting and airborne fault resolution; identifies, resolves, and communicates issues with LBS, HBS, infrastructure, enterprise services, other RF systems; support and recommend updates to RF systems, SW, and networks

• Provides technical and engineering support for sensors and networks

• Creates, updates, and responds to Incident tickets

• Manages data encryption changes and implementation

• Monitors the RF system and networks health/status (Sensor, platform, network paths to include crypto, DCGS RF systems, and RF related enterprise services)

• Provides comprehensive analysis, diagnostics and fault isolation for the RF systems and networks associated with ground components

• Provides comprehensive analysis, diagnostics and fault isolation for the RF systems associated with End-to-End network paths/DSFS systems

• SME that provides RF and networks sustainment support during system upgrades

Distribution Statement: E 28

• Monitors the networks connections between the RF sensors and ground equipment

• Coordinates efforts for sensor/system and network restoral

• Provides RF process and network improvements/recommendations

• Create Mission Debriefs in DCGS provided system; provide systems status (includes sensor) to operations and maintenance personnel prior to takeoff; update operations and maintenance personnel with status if required during mission; obtains inputs from operations and maintenance personnel after mission concerning sensor and systems performance; completes RF portion of end to end mission debrief and closes debrief if appropriate.

• Pre-mission responsibilities o Ensures RF system and networks readiness, system/mission configuration relative to the sensor or communication link o Performs RF and network pre-mission tasks (system reboots, ground rings, etc.)

o Completes RF, network, and COMSEC data input for mission templates

• Mission execution responsibilities o Provides real-time RF and networks assistance to flightline maintenance personnel (aircraft and sensor), pilot, maintainers, operators and users o Documents issues with RF End-to-End processes/systems o Monitors RF sensors, DSFS systems, and networks; using Government provided tools takes appropriate action to restore sensors, systems defined in paragraph 1.3, networks paths/capabilities, and processes by performing process resets, power cycles, collaborative maintenance, etc.

• Post-mission responsibilities o Evaluates RF sensor/ground and networks anomalies such as maintenance actions and Incident tickets o Submits RF and networks Incident tickets and performs SW maintenance actions as required o Completes RF End-to-End mission debriefs (incorporates mission/system issues encountered by DGS and DMS operations and maintenance personnel) and ensures appropriate maintenance personnel are aware of issues

• Specific Position Requirements o Entry level acceptable minimums

Certifications

• DoD 8570.1 (IAT Level II or IAM Level I)

Personal Qualifications

• Associates’ Degree in Technical Field or ≥5 years of DCGS experience

• TS/SCI Security Clearance

Experience

• ≥3 yrs of Information System Security Management

• ≥2 yrs of DCGS experience o Mid-level acceptable minimums Certifications

• DoD 8570.1 (IAT Level II or IAM Level I) Personal Qualifications

Distribution Statement: E 29

• Associates’ Degree in Technical Field or ≥7 years of DCGS experience

• TS/SCI Security Clearance Experience

• ≥5 yrs of Information System Security Management

• ≥5 yrs of DCGS experience

• ≥2 yrs performing this position, or a similar RF sensor management position o Expert level acceptable minimums Certifications

• DoD 8570.1 (IAT Level II or IAM Level I) Personal Qualifications

• Bachelors' Degree in Technical Field

• TS/SCI Security Clearance

Experience

• ≥10 yrs of Information System Security Management

• ≥10 yrs of DCGS experience

• ≥5 yrs performing this position, or a similar RF sensor management position

4.3 Contract Data Requirements List (CDRL)

4.3.1 Efforts to be performed will be provided under the contract.

4.3.2 Ensure all reports, data, and requested information are produced and delivered to the Government as required by the CDRL, PWS, and covered by this IDIQ contract. The Contractor shall notify the Government of any missing documentation by the date required by the CDRL.

4.3.3 The Contractor shall consolidate monthly financial reports into an integrated program level document and delivered to the Government as required by the CDRL.

Note: Actual CDRL requirements will be directed by the contract/order. The CDRL list (para 4.3.4) is for reference only.

4.3.4 Command and Control Intelligence, Surveillance, and Reconnaissance (C2ISR) Division CDRLs

CDRL TITLE SUBTITLE DID PWS

SECTION

A001 DATA ACCESSION LIST

(DAL)

N/A DI-MGMT-81453B/T 4.6,

4.20.11, A002 CONFERENCE MINUTES N/A DI-ADMN-81250B/T 4.10,

4.29.1 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205931 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=206486

Distribution Statement: E 30

CDRL TITLE SUBTITLE DID PWS

SECTION

A003 PRESENTATION

MATERIAL

N/A DI-ADMN-81373/T 4.10

A005 CONTRACT FUNDS

STATUS REPORT (CFSR)

N/A DI-MGMT-81468/T 4.20.13

A006 CONTRACTOR’S

PROGRESS, STATUS AND

MANAGEMENT REPORT

N/A DI-MGMT-81928/T 4.14,

4.15.1, 4.20.10, 4.20.14

A020 PROGRAM

MANAGEMENT PLAN

N/A DI-MGMT-81797/T 4.29.2

A026 TECHNICAL REPORT –

STUDY/SERVICES

PLAN OF ACTION AND

MILESTONES

DI-MISC-80508B/T 4.11.5,

4.13.1

A039 DEFICIENCY REPORT

(DR)

N/A DI-ALSS-81535A/T 4.13.3

A043 FUNDS & MAN HOURS

EXPENDITURE REPORT

Man-Hour Expenditure Report DI-FNCL-80331A/T 4.20.9

A047 ACCIDENT/INCIDENT

REPORT

N/A DI-SAFT-81563/T 5.8.2

A052 PERFORMANCE AND

COST REPORT

N/A DI-FNCL-80912/T 5.10

A055 QUALITY PROGRAM

PLAN

N/A DI-QCIC-81722/T 5.20

A057 CONTRACTOR’S

PROGRESS, STATUS AND

MANAGEMENT REPORT

TOTAL CASE INCIDENT

RATE {TCIR}/DAYS

AWAY, RESTRICTED

AND/OR TRANSFERRED

{DART} RATE, OR INJURY

AND ILLNESS RATES,

ANNUAL REPORTING

DI-MGMT-81928/T 5.8.2

A060 PERSONNEL REPORT CONTRACTOR

MANPOWER REPORTING

DI-MISC-81419/T 4.20.12,

4.31

4.3.5 Quality of CDRL Deliverable

There shall be no more than one rejection of any deliverable. There shall be no more than two total rejections of deliverables per contract year. The Government will reject a deliverable if any technical errors or five or more minor errors are found within the deliverable. A technical error is defined as the format not being IAW the CDRL or the content not being accurate and complete http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205854 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205536 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204779 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=277009 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204915 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205946 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204896 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=206489 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205200 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=275526 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=204779 http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205901

Distribution Statement: E 31

IAW the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.3.6 Receipt of CDRL Deliverable

CDRL deliverables will be submitted into the Government’s ISR Ground SharePoint (Intelink).

The Contractor shall gain access approval through the Government. There shall be no more than two late submissions 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.

4.4 Travel and Per Diem

4.4.1 Travel requirements will be identified in the course of this contract. The Government Procuring Contracting Officer (PCO) will identify these requirements. Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Government PCO prior to costs being incurred and a minimum of…