DICE PWS - Synopsis Copy.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

DIGITAL INTEGRATION FOR COMBAT ENGAGEMENT (DICE) SUPPORT

20 July 2012 (1000)

1 Table of Contents

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

2 SPECIFIC TASKS

2.1 MANAGEMENT SUPPORT

2.2 ENGINEERING SUPPORT CAPABILITIES

2.3 ANALYSIS SUPPORT

2.4 AUTOMATED DATA PROCESSING (ADP) SUPPORT

2.5 REPORTS MANAGEMENT AND DOCUMENTATION SUPPORT

2.6 MANAGEMENT

2.7 TEST CAPABILITY ACTIVITIES

2.8 SYSTEM SUPPORT

2.9 PROJECT EXECUTION

2.10 QUALITY CONTROL PROGRAM

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 GENERAL

4.2 TELEPHONE SERVICE

4.3 FACILITIES, SUPPLIES AND SERVICES

4.4 INFORMATION

5 GENERAL INFORMATION

5.1 CONTRACTOR IDENTIFICATION IN THE GOVERNMENT WORKPLACE

5.2 INDUSTRIAL SECURITY

5.3 LOCATION(S) OF WORK

5.4 HOURS OF OPERATION

5.5 RECORDS

5.6 SAFETY REQUIREMENTS

5.7 KICK-OFF MEETING AND PERIODIC PROGRESS MEETINGS

5.8 CONTRACTOR TRAVEL

5.9 REQUIRED QUALIFICATIONS

5.10 DELIVERABLES

6 APPENDICES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B - ESTIMATED WORKLOAD DATA

APPENDIX C - APPLICABLE PUBLICATIONS & INSTRUCTIONS

SECTION 1

1 DESCRIPTION OF SERVICES.

1.1 Introduction.

This is a non-personal services contract managed by the AFISRA AFDICE Program

Management office. As per Federal Acquisition Regulation (FAR) 37.101 “Nonpersonal services contract means a contract under which the personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administartion, to the supervision and control usually prevailing in relationships between the Government and its employees. Therefore, the Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. The contractor shall notify the

Contracting Officer (CO) immediately if they perceive any actions which constitute personal services. These services shall not be used to perform, any inherently

Governmental functions. As per FAR 2.101, inherently Government function means, as a matter of policy, a function that is so intimitately related to the public interest as to mandate performance by Government employees.

1.2 Background.

1.2.1 The former Joint Digital Integration for Combat Engagement (JDICE) (now known as

Air Force Digital Integration for Combat Engagement (AFDICE) located at Nellis AFB, Nevada, was originally tasked by SAF/XC, Global Cyberspace Integration Center

(GCIC) (now known as the AF Command and Control Integration Center (AFC2IC), and th

Command and Control Wing (CCW) to integrate, develop, and evaluate Joint Data

Network (JDN) Tactics Techniques and Procedures (TTP)’s for combat identification

(CID), special programs, and emerging capabilities. During this time, JDICE #1 priority was to identify, test, and validate data exchange systems and architectures that, when integrated with actionable Intelligence, Surveillance and Reconnaissance (ISR) information and the application of innovative TTPs, would enhance CID for the tactical warfighter.

1.2.2 AFDICE performed operational mission support and a wide variety of Joint Research, Development, Test, and Evaluation activities in its integration mission, support, personnel, and equipment to develop, test, evaluate, document, and distribute standardized TTP, associated architectures, and related processes and or solutions.

1.2.3 AFDICE performed the following tasks and functions:

1.2.3.1 Identified National, non-traditional and service specific data collection and intelligence

(ISR) capabilities for integration into the JDN.

1.2.3.2 Coordinated current and future technological efforts to identify, fuse, correlate, and track tactically actionable/relevant data derived from traditional and non-traditional sources.

SECTION 1

1.2.3.3 Researched, developed, and recommended digital data exchange architectures in support of situational awareness and CID for the tactical warfighter.

1.2.3.4 Tested and validated the Air Force Intelligence Surveillance Reconnaissance Agency

(AFISRA) developed and approved TTPs and data exchange architectures.

1.2.3.5 Validated interoperability solutions for JDN to promote horizontal and vertical integration for joint combat effectiveness across various security levels and chains of command.

1.2.3.6 AFDICE will continue to be the focal point pursue these and other tasks in support of enabling the integration and interoperability of ISR information, capabilities and resources. AFISRA will be the

Government tasking authority for AFDICE.

1.3 Scope.

1.3.1 This PWS describes the tasks and capabilities required to provide technical and analytical support to the AFISRA, the Air Force (AF), Department of Defense (DoD) and other

Government agencies. The contractor shall perform analysis of architecture and operations to determine baseline capabilities; conduct gap analysis in regard to end-state vision provided by AFISRA’s operational requirements and develop recommended solutions based on gap analysis for desired modernization and integration of ISR data link capabilities. Services will be requested by Task Order(s) (TOs) issued by the CO.

Work shall be accomplished at Nellis AFB, NV and any other locations specified in the

TOs. A TO is required for the contractor to initiate any work under this contract. This overall support is required for the following: The contractor shall provide on-site and virtual System Administration support to configure, update and manage all servers and systems with configuration control updates for all applications supported with

Government authorization.

1.3.2 The contractor shall recommend TTPs, provide training, and perform installation preparation based on the locations stated above.

1.3.3 The contractor shall perform systems engineering to include research and development leading to the integration, test, installation, evaluation and training for sustainment and enhancement of existing data link technologies, including but not limited to commercial of the shelf (COTS)/ Government off the shelf (GOTS).

SECTION 2

2 REQUIREMENTS.

General. The contractor shall perform tasks to be specified in each individual TO, in the areas identified below in order to furnish the Government with the required services and support. The contractor shall manage and support simultaneous TO(s) at various stages of development and completion at any given time throughout the life of the basic Indefinite Delivery Indefinite

Quantity (IDIQ) contract.

2.1 Program Management Support.

2.1.1 The contractor shall provide a technical lead to function as the Program Manager (PM).

2.1.2 The contractor shall provide recommendations to the Government on all technical aspects pertaining to the successful accomplishment of the Digital Integration for Combat

Engagement (DICE) mission.

2.1.3 The contractor shall recommend innovative TTPs for improving data exchange system connectivity to improve situational awareness and CID for the tactical warfighter.

(Contract Data Requirements List (CDRL) A007)

2.2 Engineering Support Capabilities.

2.2.1 The contractor shall provide primary engineering support in the identification of unique information in advanced programs efforts to include all aspects of DICE related test design and test plan development integrating advanced technology evaluations for

Government weapons systems. (CDRL A002)

2.2.2 The contractor shall provide primary engineering support to the Government for the identification of unique information to support emerging capabilities and efforts to include but not limited to: identification and integration of new or unexploited information systems, unique friendly, enemy, or neutral information sources;

development of associated TTP for the timely, accurate, and complete forwarding of tactically actionable and relevant information via Tactical Data Link (TDL); migration of

Governmet CID information into the JDN.

2.2.3 The contractor shall provide primary engineering support to the Government for the identification of unique information to support CID efforts to include but not limited to:

identification and integration of unique friendly, enemy, or neutral information sources;

prioritization of reporting criteria; support in the development of associated TTP for the timely, accurate, and complete forwarding of tactically actionable and relevant information via TDL to simultaneously support time sensitive targeting and situation awareness efforts; integration of identified advanced programs and emerging capability information in the support of CID; migration of CID information into the JDN.

2.2.4 The contractor shall provide Joint Interface Control (JIC) support to identify the datalink architecture and network design parameters needed to connect the various operational units within the JDN. JIC support shall include Program JDN expertise, Joint Multi-TDL operational infrastructure point of contact for inter-service coordination. The contractor shall support the utilization of and training on operational equipment configurations.

When not included in Operational Tasking Data Links (OPTASKLINK); the JIC support shall provide any additional information for operations directly to participants via alternate procedures, assume the role of network manager for Government TDL operations, and develop architectures for events and verify correct inclusion in other architectures that DICE Government entities will participate in.

2.2.5 The contractor shall perform systems engineering to include research and development , testing and evaluation to recommend the integration, test, installation, evaluation and training for sustainment and enhancement of existing data link architecture and network design to support emerging capabilities, advanced programs missions, ISR (traditional and non-traditional) integration, and interoperability in support of CID into JDN, this includes but is not limited to COTS/GOTS. (CDRLs A001 and A003)

2.3 Analysis Support.

2.3.1 The contractor shall provide the overall supervision, conduct, and support of data management efforts to include but not limited to the following:

2.3.1.1 Database expertise in the design implementation, integration of multi-tiered applications that access relational database management systems, research, development and implement of current and future database software updates and upgrades; ensure compliance with Government software quality goals.

2.3.1.2 Configuration management and qualification testing of delivered software products;

develop and implement barcode management software to perform inventory and control of the Government Data Media Library; provide custom analysis tools for the assessment of test data; design and implement Distributed Applications with Microsoft

SQL Server; ensure database security by establishing data access rights for all users.

(CDRLs A004 and A007)

2.3.2 The contractor shall develop and coordinate the evaluations, recommend new areas of evaluation for incorporation into evaluation planning efforts, and formulate special studies, to support the Government DICE capability. (CDRL A001)

2.3.3 The contractor shall review and develop technical documentation such as test plans, technical and test reports, trade studies, and technical memorandums. The contractor shall baseline the master test system prior to conducting operational test of other systems.

(CDRLs A001 and A002)

2.4 Automated Data Processing (ADP) Support.

2.4.1 The contractor shall develop and integrate ADP equipment and software for the implementation of operational requirements and coordinate with the Government

Contracting Officer’s Representative (COR).

2.4.2 The contractor shall provide technical support for all applicable ADP systems.

2.4.3 The contractor shall ensure the operational capability of all hardware and software platforms meets or exceeds established DoD and military operational standards as provided by the Government COR.

2.4.4 The contractor shall coordinate all equipment and software maintenance requests by the

Government, to include coordinating with other agencies, as necessary. This shall include but not limited to preparing, shipping, and receiving equipment deployed for test events and researching components needed for recording test data.

2.4.5 The contractor shall establish configuration control procedures, to ensure no programs or data are modified without Government COR coordination and documentation. The contractor shall record data in accordance with (IAW) applicable Government standards as identified in each individual Task Order. (CDRLs A001, A003 and A005)

2.5 Reports Management and Documentation Support.

2.5.1 The contractor shall document, disseminate, and ensure finished DICE products, this shall include but not limited to briefings, test results, TTP, architecture designs, and Data

Change Requests (DCRs) (classified/unclassified). The contractor shall use

COTS/GOTS products to maintain, track, and update applicable DICE publications.

(CDRLs A001, A002, A006 and A007)

2.5.2 The contractor shall ensure the Configuration Management Plan (CMP) is kept current.

Evaluate and edit material for content, and coordinate the trafficking and inspection of proofs and negotiate revision of materials to be published; review and edit a wide range of electronic media for structure, comprehensibility, organization, completeness, correctness, irretrievability, graphical design and convert into a standardized format;

prepare documents for publishing: CD labeling and packaging, binding and report coverings, paper quality; coordinate publishing budget estimates and oversee production process; ensure that all material meet internal quality standards and applicable

Department of Defense (DoD) DICE capability, policies and standards, while maintaining the current classified and unclassified AFDICE websites. (CDRL A005)

2.6 Management.

2.6.1 The contractor shall ensure overall responsiveness, cost control and reporting, adherence to schedule, ability to adapt to schedule changes, responsible and cooperative behavior, data management, technical quality of work, management of contractor team’s efforts including level of understanding of the DoD capability, mission and commitment to customer satisfaction.

2.6.2 The contractor shall ensure risk identification and mitigation associated with this requirement.

2.7 Test Capability Activities.

2.7.1 The contractor shall work with Government agencies to perform analysis of test capabilities to include but not limited to: identifying test capability requirements, documenting existing test capabilities, identifying shortfalls, performing trade off analyses and recommending approaches to solve issues. (CDRL A001)

2.7.2 The contractor shall perform mission area research, monitor and report on program related meeting, and provide recommendations for continuing Government DICE involvement in assorted projects. (CDRL A001)

2.7.3 The contractor shall work with applicable DoD organizations to perform standards and conformance testing to include writing, scheduling, conducting the testing and provide post test analysis to applicable DoD organizations IAW military standards. (CDRL

A001)

2.8 System Support.

2.8.1 The contractor shall provide system administration support that shall include but not limited to configure, update and manage all servers and systems with configuration control updates for all applications supported. The contractor shall document all changes in the Configuration Management Plan. (CDRL A005)

2.8.2 The contractor shall provide all required software licenses within 90 working days before expiration. (CDRL A003)

2.8.3 The contractor shall provide system, server and application level functional and security patch integration ensuring all information security notices are completed and reported.

2.8.4 The contractor shall provide information security oversight and management for monitoring the operational and functional security of systems to include but not limited to site and user operations.

2.8.5 The contractor shall provide technical support for all of AFDICE’s and all other applicable Government entities’ operational, testing, and sustainment equipment needs as stated in each individual Task Order. This shall include but not limited to coordinating integration on all DoD networks.

2.9 Project Execution.

2.9.1 The contractor shall perform the following tasks:

2.9.1.1 Provide field operations support such as deployment/redeployment, tracking, requesting/scheduling of all resources and overseeing general field test operations needed to achieve stated test objectives.

2.9.1.2 Work with AFISRA/AFDICE Program Manager to conduct all site surveys which perform site preparation such as defining site-specific installation, integration, preparation of environmental permit plans and integration of AFDICE and/or applicable

DICE equipment with equipment available from other agencies or host areas. (CDRL

A001)

2.9.1.3 Provide field equipment support such as identifying and preparing test equipment and calibrating test instrumentation and site support equipment with on-site equipment and power.

2.9.1.4 Provide field communications and frequency management support such as the installation, testing and operation of communication equipment and data links.

2.9.1.5 Provide computer operation support such as system design, analysis of alternative equipment designs, integration of equipment and equipment upgrades for field deployments. (CDRLs A001 and A005)

2.9.1.6 Coordinate airspace and range management support.

2.9.1.7 Conduct system software validation and verification. (CDRL A002)

2.9.1.8 Run computer models, simulations, analyze and characterize the resulting output and provide technical and test reports. (CDRLs A001 and A002)

2.9.1.9 Develop and deliver mission briefings and debriefings and review and update DICE documentation. (CDRLs A006 and A007)

2.10 Quality Control Program.

2.10.1 The contractor shall establish and maintain a quality control system that ensures research and development services on communications system is performed IAW this contract, applicable laws and regulations IAW best commercial practices. The contractor shall develop and implement a Quality Control Plan (QCP), which describes in detail an inspection system to cover all services listed in the Service Summary, specific areas to be inspected on both a scheduled and unscheduled basis. The contractor shall provide the

Contracting Officer (CO) the QCP for review and approval within 30 working days of contract award. (CDRL A008)

SECTION 3

3 SERVICES SUMMARY (SS).

1. The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The SS provides information on contract requirements, the expected level of contractor performance and the expected method of

Government validation and confirmation of services provided. These thresholds are critical to mission success. Procedures as set forth in the applicable Inspection clause in the contract will be used to remedy all deficiencies. TO specific service summaries will be included with each individual TO.

Performance Objective PWS PARA Performance Threshold

SS # 1.

The contractor shall conduct quality analysis and provide supportive documents.

2.3 The contractor shall provide draft analysis

documents. No more than two (2) major revisions per each report are acceptable. Final technical and test reports shall incorporate all

Government provided recommendations and comments. Submission of final report requiring any revision is unacceptable

SS#2. The contractor shall test, verify and document the test results to include features and capabilities.

2.2.1,2.3, 2.7 The contractor shall provide technical and test reports for all tests. Tests shall be conducted

IAW test plans and failure to provide test reports which accurately describe the utilized testing process and results is unacceptable.

(CDRL A001)

SS#3. The contractor shall manage and update all servers and systems supported.

2.4, 2.8 There shall be no lapse in service or adverse mission impact as a result of contractor’s failure to manage, update and maintain systems. Failure to install within 60 working days or otherwise directed DoD Information

Security requirement of new update release is unacceptable.

SS#4.

The contractor shall develop and provide site-specific installation and integration plan of AFDICE and/or other applicable DICE equipment in conjunction with site survey.

2.9 Plan shall include all equipment, software and

power requirements. Documents shall be provided within five (5) working days after site survey.

SS#5.

The contractor shall track expiration dates of all licenses.

2.8.2 Zero required licenses shall expire during the

year due to contractor error. Notification of expiration is due within 90 work days of expiration date.

SECTION 4

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 General.

The Government will provide the facilities, equipment, records, and service listed for contractor personnel. All Government property used by the contractor shall be accounted for IAW the

Government property clause and the general provisions of the contract.

4.2 Telephone Service.

The Government will provide continental United States (CONUS) Defense Switched Network

(DSN) telephone service for official business use only in support of contract requirements.

4.3 Facilities, Supplies and Services.

The Government will provide office space, supplies, computer equipment, access to military local area network (LAN) services (classified and unclassified), telephone and fax (local, DSN, and long distance), electronic mail, LAN support, reproduction facilities, and facilities to store classified working papers and data (media disks, hard drives, etc…). The contractor shall provide a National Agency Check for on-site employees to be granted LAN access.

4.4 Information.

The Government will provide the following information: access to relevant Government organizations, information and documentation, manuals, texts, briefs, and associated materials as required and available.

SECTION 5

5 GENERAL INFORMATION.

5.1 Contractor Identification in the Government Workplace.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. The contractor shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation.

5.2 Industrial Security.

DD Form 254. Overarching security requirements and contractor access to classified information shall be as specified in the DD Form 254, Department of Defense Security

Classification attached to the contract/task order, if applicable. The contractor shall have a final

U.S. Government issued TOP SECRET security clearance and be DCID 6/4 eligible with a current Single Scope Background Investigation (SSBI).

5.3 Location(s) of Work.

The work to be performed under this contract will be performed at the designated Government facility located in Nellis AFB, Nevada and/or other locations that will be identified in specific

TOs.

5.4 Hours of Operation.

5.4.1 Normal Hours of Operation. The contractor shall perform the services required under this contract during the following hours: 0800-1700, Monday through Friday (excluding federal holidays.

5.4.2 Recognized Holidays. The contractor is not required to provide services on the following days: New Year’s Day, Martin Luther King Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Days, Thanksgiving Day and

Christmas Day. If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday.

5.5 Records.

The contractor shall create, maintain and dispose of only those Government required records that are specifically cited in this PWS or required by the provisions of mandatory Applicable

Publications and Instructions (Reference Appendix C). If requested by the Government, the contractor shall provide the original record or a reproducible copy of any such record within five

(5) work days of receipt of the request. (CDRL A001)

5.6 Safety Requirements.

In performing work under this contract, the contractor shall:

5.6.1 Conform to the safety requirements contained in the contract for all activities related to the accomplishment of the work.

5.6.2 Take immediate precautions as the CO may reasonably require for safety and mishap prevention purposes.

5.6.3 Record and report promptly (within one hour) to the CO or COR, all available facts relating to each instance of damage to Government property or injury to either contractor or Government personnel.

5.6.4 In the event of an accident/mishap, take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence until released by the accident/mishap investigative authority through the CO.

5.6.5 If the Government elects to conduct an investigation of the accident/mishap, the contractor shall cooperate fully and support Government personnel conducting the investigation.

5.7 Kick-off Meeting and Periodic Progress Meetings.

The contractor shall develop and execute an initial kick-off meeting as required in each individual TO. The CO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the

CO will appraise the contractor of how the Government views the contractor's performance and the contractor shall apprise the Government of problems being experienced. Appropriate action shall be taken to resolve outstanding issues. The contractor shall provide minutes of these meetings to the Government within five (5) work days after meeting. (CDRL A009)

5.8 Contractor Travel.

5.8.1 The contractor shall travel to attend meetings, gather information and participate in events in support of tasks listed in the PWS as required in each individual TO. Actual expenses shall be IAW Joint Travel Regulations and shall be approved by the

Government prior to travel. The contractor shall not exceed the travel allocation. Where feasible, the contractor shall use teleconferencing; electronic media transfers of data and use the Letter of Identification (LOI) to the maximum extent possible to support the Air

Force to reducing costs. The contractor shall provide a trip report five (5) working days after conclusion of travel. (CDRL A009)

5.8.2 The contractor shall perform travel to various locations within the continental United

States (CONUS). The contractor shall perform overseas travel (OCONUS) if required.

All travel shall be performed IAW the Joint Travel Regulation (JTR). The contractor shall not commit to travel without prior approval of the Government. Costs for travel shall be billed on a strictly cost reimbursable basis IAW, the regulatory implementation of Public Law 99-234, FAR subpart 31.205-46 entitled Travel Costs and the limitation of funds specified in this contract.

5.9 Required Qualifications.

This section is a layout of the minimum requirements for each of the position. The contractor shall meet the following qualifications:

5.9.1 The contractors shall complete and maintain at least a TS/SCI security clearance.

5.9.2 Joint Data Network Integration:

The contractor shall have an extensive background in multi-Service network design; Joint

Service data link capable systems and associated architectures. The contractor shall maintain knowledge of current systems and associated software updates and upgrades required for position. The contractor shall review and develop technical documentation such as test plans, trade studies, architecture diagrams, and technical memorandums. (CDRLs A001 and A002)

5.9.3 Analysis Support:

The contractor shall be familiar with: Air Defense System Integrator (ADSI) Version 10.X+;

Multi- TDL Display System (MTDS), Joint Range Extension (JRE), MSCS, Multi-Source

Correlator Tracker (MSCT) and Force XXI Battle Command, Brigade and Below (FBCB2), Trusted Manager II, Radiant Mercury, and other applicable and associated data networks, hardware and software.

5.9.4 Reports Management and Documentation Support:

The contractor shall have experience in the AFTTP 3-1 process and cycles, Joint publications and the DCR process, activities and test and evaluation reporting formats.

5.10 Monthly Status Report.

The contractor shall develop and provide an electronic monthly status report to the Government no later than 15 th work day of every month. The monthly status report shall contain all activities conducted in the previous month. This report shall convey the status of all TOs awarded as of contract inception as well as cumulative contract. (CDRL A010)

5.11 Deliverables.

Reports and other data required in this PWS shall be submitted IAW the CDRL in Exhibit 01 of the contract.

CDRL # Data Item Number Data Item Description PWS Para. Delivery Schedule

A001 DI-MISC-80508 Technical and Test

Reports – Study Service

2.2.5, 2.3.2, 2.3.3, 2.4.5, 2.7.1, 2.7.2, 2.7.3, 2.9.1.2, 2.9.1.5, 5.5, 5.9.2

Shall be provided NLT five

(5) work days after

Government request to the

Government COR

A002 DI-NDTI-80566 Test Plans 2.2.1, 2.3.3, 2.9.1.7, 2.9.1.8, 5.9.2

Shall be provided NLT 30 work days after Government request to the Government

COR

A003 DI-MCCR-80700 Computer Software

Product End Item

2.2.5, 2.4.5, 2.8.2 Shall be provided NLT 90 work days after Government request to the Government

COR

A004 DI-IPSC-81437 Database Design

Description

2.3.1.2 Shall be provided NLT 60

work days after Government request to the Government

COR

A005 DI-CMAN-80858 Contractor’s Configuration

Management Plan

2.4.5, 2.5.2, 2.8.1, 2.9.1.5

Shall be provided NLT 60 work days after Government request to the Government

COR

A006 DI-ADMN-81373 Presentation Material 2.9.1.9 Shall be provided NLT three

(3) work days after

Government request to the

Government COR

A007 DI-ADMN-80925 Revision to Existing

Government Documents

2.1.3, 2.3.1.2, 2.5.1, 2.9.1.9

Shall be provided NLT five

(5) work days after

Government request to the

Government COR.

A008 DI-CMAN-80789 Quality Control Plan 2.10.1 Shall be provided NLT 30 working days after contract award to the Government

COR. After receipt, the

Government will provide comments within 15 working days draft receipt. Contractor shall provide final copy to

Government within five (5) working days after draft provided to contractor.

A009 DI-ADMN-81505 Report, Record of

Meeting/Minutes

5.7, 5.8 Shall be provided NLT five

(5) work days after meeting to the Government COR.

A010 DI-MGMT-80368A Monthly Status Report 5.10 Shall be provided NLT the th work day of every month.

SECTION 6

6. APPENDICES

A. Acronyms and Abbreviations List

B. Historical Workload Data

C. Applicable Publications and Instructions

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

ADP Automated Data Processing

AF Air Force

AFB Air Force Base

AFDICE Air Force Digital Integration for Combat Engagement

AFI Air Force Instruction

AFISRA Air Force Intelligence, Surveillance, & Reconnaissance Agency

AFMAN Air Force Manual

ATC Authority to Connect

ATO Authority to Operate

C&A Certification and Accreditation

CCW Command and Control Wing

CDRL Contract Data Requirements List

CFR Code Federal Regulation

CID Combat Identification

CIK Crypto Ignition Key

CMP Configuration Management Plan

CO Contracting Officer

COMSEC Communication Security

CONUS Continental United States

COR Contracting Officer’s Representative

COTS Commercial Off the Shelf

CRO COMSEC Responsible Officer

DAA Designated Approving Authority

DCR Data Change Requests

DICE Digital Integration for Combat Engagement

DoD Department of Defense

DSN Defense Switched Network

FAR Federal Acquisition Regulation

GCIC Global Cyberspace Integration Center; now known as the AF

Command and Control Integration Center (AF2IC)

GOTS Government Off the Shelf

IA Information Assurance

IATO Interim Authority to Operate

IATT Interim Authority to Test

IAW In Accordance With

ISR Intelligence Surveillance Reconnaissance

JDICE Joint Digital Integration for Combat Engagement

(now known as AFDICE)

JDN Joint Data Network

JIC Joint Interface Control

LAN Local Area Network

MTC Multi-TDL Capability

MSCS Multi-Source Correlation System

NAC National Agency Check

NDA Non-Disclosure Agreement

OSHA Occupational Safety and Health Act

OPTASKLINK Operational Tasking Data Link

PBSA Performance Based Service Acquisition

PWS Performance Work Statement

QA Quality Assurance

QASP Quality Assurance Surveillance Plan

QCP Quality Control Plan

SS Services Summary

SSAA System Security Authorization Agreement

SSBI Single Scope Background Investigation

SVRO Secure Voice Responsible Officer

TO(s) Task Orders

TDL Tactical Data Links

TTPs Tactics, Techniques, and Procedures

USAF United States Air Force

APPENDIX B – HISTORICAL WORKLOAD DATA

The historical workload data provided is for informational purposes only and is based upon historical data. Contractors shall propose based on their own technical approach.

HISTORICAL EVENTS:

1. Distributed Common Ground Systems (DCGS) Data Link Optimization and Tactics, Techniques, and Procedures (TTP) development. (October 2008 - September 2009) Engineering and Engineering

Support Services at five (5) core Distributed Ground Site(s) (DGS). Test preperations, test executions, technical and test reports, site specific TTP development, publishing, and training. (3840 hours)

Joint Digital Integration for Combat Engagement (JDICE) through indefinite delivery indefinte quantity (IDIQ) contract modification was tasked to address optimization of data link operations within the AF DCGS enterprise. JDICE was selected based on its roles and authorities under

SAF/XC as the integration, development and evaluation agent for Joint Data Network (JDN) TTP for combat identification, advanced programs and emerging capabilities. The primary objective;

optimize the data link operations of the AF DCGS enterprise and the DGS Data Link Operator

(DLO) in accordance with theater requirements and AF DGS CONOPS. Areas addressed included data link systems, architecture, datalink and security guard equipment configuration, DLO crew procedures, COCOM/MAJCOM ROE, training, and TTP development.

2. Multiple Source Correlation System's (MSCS) Risk Reduction Study. Specified test event at

JDICE lab and DCGS core sites (5 Sites) (February - July 2010). Engineering and Engineering

Support Services. Test preps, test executions, test reports. (1920 hours)

The overall purpose of the risk-reduction events were to confirm the MSCS’ ability to transmit specific track types via the MSCS Multi-TDL Capability (MTC) link architecture to a distant-end Joint Range Extension (JRE). Sixty-eight (68) specific links with 16 compatible tracks were selected to verify transmission integrity for inclusion in the DGS DLO TTP. In addition, four (4) track specific type changes were sent to verify the MTC link. The primary objective for the risk reduction event was: (1) successfully transmit specific link 16 track types from the

MSCS to a distant-end JRE via an IP connection using the MTC protocol. (2) Intent: Ensure integrity of the data across the IP connection using the MTC protocol.

3. TDL, Subject Matter Expert, Liaison, for Tactical Data Dissemination for new Quick Reaction

Capabilities. (October 2009 - September 2010) (1920 hours)

4. Primary Scope: Develop, coordinate and implement JINDI CONOPS, TTP, Training, STANDARDIZATION/EVALUATION documentation; and JDICE SME for AFISRA development of standardized Data Link Operator (DLO) development and optimization across AF-DCGS, other

AFISRA DLO Initiatives, and new rapid fielding Quick Reaction Capabilities tactical data link integration.

5. All listed items are required to plan, train, execute, analyze, and report for DICE. Funding comes from Air Force ISR Agency (AFISRA) and other DoD entities. Unique costs include those funds necessary for the following:

Transportation, travel, and per diem for the DICE team

Provisions for data collection, data reduction, analysis, and test reporting services

Manpower for the DICE team

B. Estimated Workload

Table B-1: DICE Estimated Workload – Base Year Summary

Category Hours/Estimated Cost

Senior Analyst/Engineer Level 1 1,920

Senior Analyst/Engineer Leve1 2 11,040

Software Engineer/Analyst Level 1 1,920

Government Travel $100,000.00

Table B-2: Estimated Workload - Option 1 Year Summary

Category Hours/Estimated Cost

Senior Analyst/Engineer Level 1 1,920

Senior Analyst/Engineer Leve1 2 11,040

Software Engineer/Analyst Level 1 1,920

Government Travel $100,000.00

Calculations based off a 12 month period = 1920 hours

Travel calculated based off the number of previous trips

Table B-3: An Example of Workload Activity -

Category Category

QRC TDD/TDL Integration TDL Test

Advanced CID TDD/TDL IBS TDD Automation Integration

National Intelligence Community TDD COCOM TDD/TDL Integration

NT-ISR TDD/TDL

Table B-3: An Example of Workload Activity - DICE IGCE Estimated Types of Workload is a list of possible additional workload to be added to the DICE contract as requirements dictate.

FOR ESTIMATTION PURPOSES ONLY. THIS SHOULD BE CONSIDERED AS AN

ADDITION TO EITHER THE BASE YEAR AND/OR OPTION YEAR. THE

Category Category

QRC TDD/TDL Integration TDL Test

Advanced CID TDD/TDL IBS TDD Automation Integration

National Intelligence Community TDD COCOM TDD/TDL Integration

NT-ISR TDD/TDL

APPENDIX C - APPLICABLE PUBLICATIONS and INSTRUCTIONS

The contractor shall comply with all publications, regulations and operating instructions provided by the Government when they pertain to the procedures for materials expediting herein and where the contractor is authorized by the PWS to accomplish the work specified in the publication, regulation or operating instructions. The publications prescribe DoD policies, use of materials, procedures and processes applicable to the work requirements. The contractor shall acquire and work on the latest version of the publication(s). Below is the primary list but not all inclusive list of applicable publications.

Publication/Instruction - Title Applicable

Paragraph/Chapter

PWS

Paragraph Chairman Joint Chiefs of Staff Manual (CJCSM) 6120.01

Series

Entire Document 2.7.3

CJCSM 3115.01 Series Entire Document 2.7.3

Military Standard (MIL-STD) -6016 Series Entire Document 2.7.3

MIL-STD-3011 Series Entire Document 2.7.3

MIL-STD-6011 Series Entire Document 2.7.3

MIL-STD-6020 Series Entire Document 2.7.3

MIL-STD-6018 Series Entire Document 2.7.3

Air Force Instruction 33-101 Entire Document 2.4.5