Atch_3_-_ATS_C2ISR.pdf

AIR FORCE OPERATIONAL TEST & EVALUATION CENTER (AFOTEC)

TEST SERVICES (ATS)

COMMAND, CONTROL, INTELLIGENCE, SURVEILLANCE AND RECONNAISSANCE

(C2ISR) TEST OPERATIONS (CTO) DIVISION

2 March 2017

1.0 SCOPE

This effort shall be conducted pursuant to the provisions of the Air Force Operational Test and Evaluation Center (AFOTEC) Test Services (ATS) contract Performance Work Statement (PWS), paragraph 3. The objective of this Task Order (TO) is to provide engineering technical services in the areas of OT&E concepts, planning, executing, and reporting for all of the programs under AFOTEC Detachment 5 (Det 5) CTO Division. Specifically, the contractor shall review and provide recommendations on systems requirements documents; provide input during systems design and development; identify test capabilities requirements and shortfalls; develop mission task breakdown;

refine test concepts and designs; identify test support resources needs (facilities, instrumentation, and personnel); provide technical expertise to develop the Test and Evaluation Master Plan (TEMP);

develop Operational Test and Evaluation (OT&E) plans; create detailed test procedures; participate in test team deployments; prepare data management and analysis plans; collect and compile evaluation data; provide technical input for operational impact assessments; and submit inputs to OT&E reports and briefings.

1.1 BACKGROUND

The Det 5 CTO Division is tasked with operationally testing and evaluating C2ISR equipment during all phases of program acquisition. The results of these evaluations are used by the Air Force (USAF) to support systems acquisition milestone decisions and provide system users performance data on new systems being employed for their mission. The Det 5 CTO is tasked to plan, conduct, and report on effectiveness, suitability, and mission capability to meet user’s operational requirements. The division supports multiple programs at Edwards AFB, CA and various deployed locations during weapon system

OT&E.

CTO’s programs are primarily focused on multi-million dollar, acquisition category (ACAT) I aircraft modernization programs, but also include ACAT II and ACAT III programs. The major command customer is Air Combat Command (ACC). Current programs include; Global Hawk Block 30, which also carries the Airborne Signals Intelligence Payload (ASIP); Global Hawk Multi-Spectral Intelligence (MSI); the Global Hawk ground station modernization program (GSMP); and the Distributed Common Ground Station (DCGS).

The RQ-4B Global Hawk Block 30 is an ACAT ID program that provides high-resolution Synthetic Aperture Radar (SAR) and Electro-Optical/Infrared (EO/IR) imagery, at long range and high altitudes, with long endurance times over target areas. The Block 30 also carries ASIP to collect signals intelligence (SIGINT) data. The Block 30 underwent an initial operational test and evaluation (IOT&E) in 2010. There were several items related to suitability and the ASIP sensor that need to be re-tested during a follow-on operational test and evaluation (FOT&E).

RQ-4 Global Hawk MSI is an ACAT III program to provide an improved EO/IR imagery sensor to the RQ-4 Block 30. This program will install a new government furnished equipment (GFE) sensor in place of the existing EO/IR sensor package.

RQ-4 Global Hawk GSMP is an ACAT II program to move the Mission Control Element (MCE) and Launch and Recovery Element (LRE) functions to a fixed building site. Additionally, the program will upgrade the command and control system to an open architecture, improve the human-system interface, mitigate diminished manufacturing sources and parts obsolescence issues, and comply with cybersecurity requirements.

DCGS is a combination of eight ACAT III programs used to develop and upgrade the DCGS enterprise.

Under these eight ACAT III programs are individual development programs. The level of operational testing required for each of the individual development programs is determined using the risk assessment level of testing (RALOT) process. When a program is determined to require an operational test it is added to the tasking order and testing is planned according the standard AFOTEC timelines.

Table 1.0 provides the current understanding of major CTO products for scoping proposals. Actual dates, programs, and events are subject to change. Additional CTO programs are expected during the period of performance of this task order.

Table 1.0

RQ-4

Block 30

RQ-4

MSI

RQ-4

ASIP

RQ-4

GSMP DCGS

PID/SOC

Tasking Order May 15 Apr 15 May 15 Feb 15 May 15 Initial Test Design

(OT&E/OA)

Apr 16 Jan 17 May 17 Feb 12

Technical Review Feb 17 Nov 16 Feb 17 Aug 17 Apr 16 Test Concept Briefing May 17 Feb 17 May 17 Nov 17 Jun 16

OA/OUE DMAP &

Plan

N/A Jun 17 N/A Mar 18 N/A

OA/OUE Final Report N/A Nov 17 N/A Jul 18 N/A Test Readiness Briefing Aug 17 Jul 17 Aug 17 TBD TBD OT&E DMAP Sep 17 Jun 17 Sep 17 TBD Sep 16 OT&E Plan Sep 17 Jun 17 Sep 17 TBD Sep 16 OT&E Plan Briefing Sep 17 Jun 17 Sep 17 TBD Sep 16 OT&E Report Apr 18 Nov 17 Apr 18 TBD Jun 17 OT&E Report Brief Apr 18 Nov 17 Apr 18 TBD Jun 17 Project Closeout Jun 18 Jun 18 Jun 20

2.0 APPLICABLE DOCUMENTS

In addition to the test and evaluation guidance contained in the PWS, Section 2.0, the following documents are applicable to this task order. Documents will be made available.

2.1 Program Documentation

2.1.1 Operational Requirements Documents (ORD)

2.1.2 Test and Evaluation Master Plans (TEMP)

2.1.3 Capability Production Document (CPD)

2.1.4 Technical Requirements Document (TRD)

2.1.5 Capability Development Documents (CDD)

2.1.6 Concept of Operations (CONOPS)

2.2 Tests and Evaluation Documentation

2.2.1 Evaluation Frameworks (EF)

2.2.2 Operational Assessment (OA) Plans

2.2.3 OT&E Plans

2.2.4 Test Concepts

2.2.5 Initial Test Design (ITD) Briefings and Documents

3.0 PERFORMANCE REQUIREMENTS

3.1 Management. The contractor shall provide a management structure to accomplish this task order in compliance with the provisions in Section 3.1 of the PWS. (A001, A002)

3.2 Test Capabilities. (A004, A005, A014, A016, A017, A020, B001-B014) The contractor shall:

3.2.1 Perform mission area research.

3.2.2 Perform analysis of test/assessment capabilities. Activities include identifying test/assessment capability requirements, documenting existing test/assessment capabilities, identifying shortfalls, performing trade-off analyses, and recommending approaches to solve issues.

3.2.3 Identify, develop, modify, verify, and/or validate modeling and simulation (M&S) tools such as test support tools that simulate real world entities by means of computer models, hardware-in-the-loop (HITL) simulators, human-in-the-loop simulators, installed system test facilities, and distributed interactive simulations.

3.2.4 Develop accreditation packages. Develop verification, validation, and accreditation (VV&A) plans. Prepare VV&A reports and briefings.

3.2.5 Develop and coordinate cyber-vulnerability and penetration/exploitation test plans and reports IAW appropriate Director, Operational Test and Evaluation (DOT&E) and AFOTEC guidance.

3.2.6 Maintain configuration management of developed and modified tools.

3.2.7 Train government personnel in the operation, interpretation of outputs, and maintenance of contractor-developed test tools, such as computer software, applications, instrumentation, and models and simulations.

3.2.8 Provide Information Technology (IT) support during test support and execution.

3.2.9 Identify, develop, and/or apply analytical techniques, methodologies, and tools for

Integrated Testing and OT&E.

3.2.10 Identify, develop, recommend, and/or integrate test capabilities for ranges (live and virtual), state-of-the-art instrumentation, and ways to use test capabilities to answer operational questions. This knowledge would cover a range of technical fields such as aerodynamics, electronic warfare, M&S, software development and maintenance, and the space environment.

3.2.11 Identify, schedule, and track program activities and deliverables for all tasked programs. Maintain a master schedule for all tasked programs using common project management software. Provide inputs to leadership to manage multiple programs.

3.3 Test/Assessment Planning and Early Influence. (A004, A007, A008, A009, A010, A011, A012, A014, A016, A017, B001-B014) The contractor shall:

3.3.1 Provide operational task breakdown, using a systems engineering process, to show the interlacing and overlapping relationships between the system under test and the family of systems it interacts with.

3.3.2 Review lessons learned and test methods used in the testing and evaluation of similar systems.

3.3.3 Provide input to develop and/or revise the Initial Test Design and subsequent test concepts.

3.3.4 Provide input to develop and/or revise the evaluation framework and/or alternate evaluation framework.

3.3.5 Recommend appropriate test facilities/ranges and identify improvements necessary to create an operationally realistic environment.

3.3.6 Provide input to develop and/or revise the basis of estimate for test resources (e.g.

Test Resource Plan) to accomplish the test/assessment design. Provide logistic planning in support of AFOTEC.

3.3.7 Review for test and evaluation/assessment considerations and develop feedback on program documents, such as the: program management directive, applicable capabilities documents, virtual/system threat assessment report, test and evaluation master plan, systems acquisition management plan (SAMP), lifecycle management plan (LCMP), program protection documents, concepts of operations/employment, and maintenance concepts.

3.3.8 Participate as an Integrated Test Team member to gain knowledge of, and facilitate planning of, developmental, integrated, and operational test activities.

3.3.9 Support the AFOTEC test director in identifying and/or developing integrated test opportunities during developmental testing.

3.3.10 Develop test support documentation such as program introduction document (PID) and statement of capabilities (SOC).

3.3.11 Prepare, submit and/or revise AFOTEC portions of program test documentation, such as test team charters, test and evaluation master plans, integrated test plans, and schedules.

3.3.12 Prepare, submit and or revise AFOTEC OT&E/assessment plans, cyber vulnerability and penetration test plans, joint OT&E/assessment plans, data management and analysis plans, detailed test/assessment procedures, test/assessment planning briefings, and schedules.

3.3.13 Develop Data Management and Analysis Plans (DMAP), test procedures, evaluation methodologies, analysis methods, and schedules. Provide multimedia data file management and archiving. Assure configuration control of any software codes used by or in support of the evaluation activity.

3.3.14 Provide input in developing and revising critical operational issues, measures of effectiveness, and measures of suitability.

3.3.15 Support program, technical, and test readiness reviews.

3.3.16 Develop evaluation methodologies and general analytic techniques, assess data requirements, and review specific tools needed to support the evaluation, such as digital modeling and HITL simulations.

3.3.17 Analyze and submit test/assessment methodologies; test/assessment scenario descriptions; test/assessment measures; test/assessment risk, limitation and mitigation strategies; and test/assessment readiness and support requirements needed to complete the OT&E plan.

3.3.18 Provide input for the development of operational test/assessment scenarios/demonstrations.

3.3.19 Identify candidate operational exercise participation opportunities. Perform site surveys on potential test/assessment sites and develop site preparation requirements, such as defining site-specific installation, integration, preparation of environmental permit plans, and integration of AFOTEC equipment with equipment available from other agencies or host areas.

3.3.20 Provide environmental health and safety planning services for test/assessment programs addressing occupational health, and environmental concerns.

3.3.21 Develop, modify, operate and/or maintain the required automated data collection/reduction systems, to include developing interfaces with existing digital information stored on available databases. Develop, refine, and implement plans to insure interoperability with data from appropriate test facilities/ranges Analyze content for interoperability and compatibility with existing information (data) systems.

3.3.22 Recommend instrumentation requirements, propose instrumentation solutions, and develop instrumentation to collect and store data.

3.4 Test/Assessment Execution. (A004, A007, A008, A009, A010, A011, A012, A016, A017)

The contractor shall:

3.4.1 Provide field operations services, such as deployment and redeployment;

requesting, scheduling, and tracking of test/assessment equipment resources;

identifying and preparing test/assessment equipment; computer systems design and engineering for test/assessment; network administration and system administration for test/assessment support networks and data management; and calibrating test/assessment instrumentation and site support equipment with onsite equipment and power.

3.4.2 Coordinate with existing airspace/range management services, for providing airspace management for manned aircraft and/or unmanned air vehicles and ground vehicles tests, assessments, and field evaluation activities both within the continental United States (CONUS) and outside the continental United States

(OCONUS).

3.4.3 Provide safety support, such as ground, flight, and environmental protection support in compliance with safety, occupational health, and environmental concerns and regulations.

3.4.4 Participate in the execution of test/assessment plans, data management and analysis plans, and detailed test/assessment procedures. Accomplish electronic and/or physical data transfer.

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

Provide test execution oversight and ensure test safety.

3.4.6 Develop and deliver OT&E briefings and debriefings. Review and update OT&E documentation.

3.4.7 Provide evaluation services for special interest items as defined in AFOTECMAN 99-101.

3.5 Test Evaluation. (A004, A016) The contractor shall:

3.5.1 Collect, compile, review, analyze, and evaluate test/assessment data.

3.5.2 Run computer models and simulations and analyze/characterize the resulting output.

3.5.3 Provide contractor raw data used in analysis to the Test Director.

3.5.4 Identify the impact of lost data (due to corruption, instrumentation failure, etc.) on analysis and evaluation of test results.

3.5.5 Conduct studies, analyses and evaluations to include but not limited to comprehensive correlation of test results to the mission decomposition, on operational effectiveness, suitability, and survivability of systems undergoing OT&E/Assessment.

3.5.6 Determine the capability of a system to withstand a man-made environment and quantify the degree of impairment of its ability to accomplish its designated mission. Man-made environments include: natural, nuclear, conventional, cyber-contested, electronic, directed energy, chemical, biological and unconventional operations warfare.

3.6 Test/Assessment Reporting. (A004, A008, A009, A010, A011, A012, A017) The contractor shall prepare:

3.6.1 Provide input to develop and/or revise the final test/assessment report.

3.6.2 Prepare test/assessment documentation for inclusion in test/assessment reports.

3.6.3 Prepare briefings as a part of the report coordination process.

3.6.4 Prepare Quick Look and Lessons Learned reports/briefings.

3.6.5 Provide recommendations for continued AFOTEC involvement.

3.7 Recommended personnel qualification requirements to fulfill Task Order.

3.7.1 Modeling and Simulation SME

3.7.1.1 Bachelor’s Degree desired

3.7.1.2 Must be knowledgeable in modeling and simulation systems

3.7.1.3 Desire experience with Verification, Validation, and Accreditation (VV&A) process

3.7.1.4 Desire experience in live virtual constructive networks

3.7.1.5 Desire experience in GEOINT and/or SIGINT collection systems

3.7.1.6 Desire 2 years test experience

3.7.2 SIGINT SME

3.7.2.1 Bachelor’s Degree desired

3.7.2.2 Must be knowledgeable in DCGS weapon systems

3.7.2.3 Desire 3 years experience as AF DCGS SIGINT Operator

3.7.2.4 Desire 2 years test experience

3.7.3 GEOINT SME

3.7.3.1 Bachelor’s Degree desired

3.7.3.2 Must be knowledgeable in DCGS weapon systems

3.7.3.3 Desire 3 years experience as AF DCGS GEOINT Operator

3.7.3.4 Desire 2 years test experience

3.7.4 Computer Test Support (Cyber/DCGS suitability)

3.7.4.1 Must have CompTIA Security+ Certification

3.7.4.2 Must be knowledgeable in Defense Intelligence Information Enterprise

(DI2E)

3.7.4.3 Desire experience with DCGS weapon systems

3.7.4.4 Desire 2 years test experience

4.0 SURVEILLANCE MATRIX

Contracting Officer Representatives (COR) will use Table 4.1 as a guide when identifying a surveillance matrix in task orders.

Table 4.1 Surveillance Matrix

Performance Objective PWS Ref Performance Threshold Method of Assessment

Item 1: Provide responsive TO and team management including quick response to contingencies, to include timely and accurate TO document and report requirements, customer interaction and feedback, and contributions to meetings and reviews.

All The contractor receives no more than three customer complaints per assessment period. Unsatisfactory performance must be resolved within 10 working days.

Customer complaint as validated by the COR and

PCO.

Item 2: The contractor must effectively monitor funding on each individual TO and effectively control the expenditures of all Other Direct Costs (ODCs).

3.1 The contractor can receive no more

than three total customer complaints (substantiated by the COR and the PCO), to include timely CDRL delivery, per assessment period.

Unsatisfactory performance must be resolved to the action within 10 working days.

Customer complaint as validated by the COR and

PCO.

Item 3: The contractor must be responsive to Government requirements, ensure PWS compliant performance, provide prompt identification and resolution of problems, effectively communicate concerns with the COR and Program Manager, and meet the delivery schedule required in the CDRLs.

All The contractor can receive no more than three total customer complaints (substantiated by the COR and the PCO), to include timely CDRL delivery, per assessment period.

Unsatisfactory performance must be resolved to the action within 10 working days.

Customer complaint as validated by the COR and

PCO.

Item 4: Comply with applicable portions of the DD Form 254 for TO requirements.

All Compliance is mandatory; failure to meet security requirements are unacceptable. Each security incident, inadvertent disclosure and violation must be reported to the government within 1 working day and violations resolved within 30 working days to the government’s satisfaction.

Customer complaint as validated by the COR, PCO and cognizant security authority.

Item 5: Overall Quality of Performance:

the contractor must efficiently perform all PWS tasks, including those requiring contributions to meetings and reviews.

All No more than three total instances of failure to meet PWS requirements, listed in the above items per assessment period.

Customer complaint as validated by the COR and

PCO.

5.0 SCHEDULE, DATA ITEMS, AND OTHER DELIVERABLES

5.1 Base Support/Government Furnished Property (GFP)/Government Furnished Information (GFI). AFOTEC will provide facilities to include working spaces, computer workstations, support equipment, special test and analysis equipment and software, and administrative equipment for contractor personnel at Det 5, Edwards AFB, CA. The contractor is not required to maintain this equipment.Contractor personnel may drive (driver must possess and carry a valid and current state driver’s license) and be a passenger in government vehicles supporting efforts described in this TO.

5.2 Travel Requirements

Travel will be required for a variety of tasks called out in this TO. All travel shall be coordinated with the COR no later than one week, prior to departure. Additionally, during OT&E execution, the contractor will be required to travel to the OT&E execution location for the duration of the OT&E. The travel ceiling for this TO, inclusive of all indirect costs and fee will not exceed $50K per year. All contractor travel will be approved by the COR.

The COR is responsible for obtaining AFOTEC approval.

5.3 Transition

It is anticipated that some important work will be in progress through the phase-in and phase-out periods of this contract. Interruptions or delays to the work would impact the mission. It is essential that attention be given to minimizing any interruption; therefore, the contract must provide for maximum cooperation between successor and incumbent, while also insuring that no work receives inadequate attention during phase-in/phase-out. The contractor shall plan for the transfer of work control, delineating the method for processing and assigning tasks, during phase-in/phase-out.

5.3.1 Phase-In/Phase Out. As a successor, the contractor shall insure a smooth transition with the incumbent contractor(s) during the phase-in period. There will be no phase-in if the successor contractor subcontracts to an incumbent. The contractor shall develop plans for assumption of awarded TOs. The contractor must provide an orderly transition of work acceptance and accomplishment such that any impact to a program is minimized. The phase-in time period is 30 days and is the first month of the period of performance. The phase-out period will be the last 30 days of the current period of performance.

5.4 Deliverables.

Technical Data. All documents shall be marked with: Export Control Warning:

WARNING- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of Department of Defense (DoD) Directive 5230.25. Classified deliverables shall be marked in accordance with Executive Order 13526, DoD 5200.1-R, DoD Manual 5200.01Vol3-8, DoD

Instruction 5210.02, AFI 31-401, AFI 31-407, and ISSO Marking Classification Handbook.

Disseminate in accordance with provisions of DoD Directive 5230.25.

Delivery shall be made by electronic means compatible with AFOTEC software. All reports shall meet Det 5 standards for structure and content. The contractor shall provide the following reports to:

Det 5 AFOTEC/CTO 190 S. Wolf Ave.

Edwards AFB, CA 93524-6835

5.4.1 Funds and Manpower Expenditure Report (A001). Contractor format acceptable, but must be approved by AFOTEC/A-7K, A-7R and COR, first submission only.

Reports are due the tenth day after end of each calendar month reporting period.

5.4.2 Status Reports (A002). Reports shall provide status per work breakdown structure level 2 programs. Det 5 AFOTEC/DMS copy shall cover all task orders assigned to Det 5. Reports are due the tenth day after end of each calendar month reporting period. During test execution, the contractor shall support submittal of daily status reports, as test situations require.

5.4.3 Conference Minutes (A003). A summary of all interchanges shall be documented in Event/Conference Report or Trip Report and submitted to the COR within five working days after local area events and seven (7) workdays after the end of all other events.

5.4.4 Data Accession List (A004). A listing of all documents produced shall be provided. The listing may be provided as attachment to Status Reports (A002).

5.4.5 DoD Architecture Framework Document (A005). Strategic scope/cost activities shall include delivery of Necessary Condition Charts and schedules. For each program assigned under this TO, the EF (a living document) shall be updated as needed.

5.4.6 Site Preparation Requirements and Installation Plan (A006). During test planning, the contractor shall submit documents identifying requirements and activation plans to prepare for test execution.

5.4.7 Environmental and Safety Permits, Plans, and Reports (A007, A008, A009, A010, A011). During test planning, test execution, and test reporting, the contractor shall support the identification, planning, reporting, and obtaining of permits, as required, for all environmental, safety, and mishap requirements.

5.4.8 Presentation Material (A013). During test planning, execution, and reporting, various briefings are required to Division, Detachment, AFOTEC, MAJCOM, Air Staff, and DoD organizations. Briefings will use the standard AFOTEC templates available on the AFOTEC SharePoint and include content as directed in the briefing guides also available on the AFOTEC SharePoint.

5.4.9 Scientific and Technical Reports (A015). During test planning the contractor may be required to submit technical reports on factors related to test planning to support test planning options. During test reporting, contractors shall provide data analysis for inclusion into the final report. In both cases, contractor format is acceptable. Test plans; DMAPs, test reports, and miscellaneous technical reports will be submitted to the COR using the current version of reporting writing software in use in the Division. All submitted test plans and reports will be reviewed and approved through the normal AFOTEC test planning and reporting process. Reproduction copies are not required.

5.4.10 Scientific and Technical Report-Studt/Services (A016). Generally, AFOTEC reviews documents requiring a Comment Resolution Matrix completed at the end of each test activity (OA, IOT&E, FOT&E, etc.), 30 days after report has been submitted. Test Resource Plans (TRP) are reviewed on a semi-annual basis.

Contractors shall review and provide inputs to the COR, current as of date of submittal. Additionally, TRP reviews will include an overall Division level review to ensure a summation of TRPs within the Division cover Division needs.

Detailed test procedures shall be developed and documented in conjunction with test planning activities. Procedures are required prior to the Test Readiness Review.

5.4.11 Accreditation Package (A017, A018, A019, A020). The contractor shall submit a verification, validation, and accreditation (VV&A) package for any model required to support test programs.

5.4.12 Software Documentation (B001-B014). Software documentation, descriptions, reports, end items, manuals, specifications, and reports shall be provided for all software requirements upon delivery of software or integrated system. Drafts shall be provided 30 days prior.

5.4.13 Test Control Communications Capability. Integrated systems, components

(including spares), and upgrades shall be delivered, as required, to Det 5 AFOTEC/CTO, 192 E. Yeager Blvd., Edwards AFB CA 93524.

5.5 Schedule/Period of Performance: Ordering Period is DOA plus 60 months.

6.0 SECURITY

6.1 DD Form 254, Contract Security Classification Specification applies to this TO.

6.1.1 The contractor will require access to classified and special access required source data up to and including Top Secret Special Compartmental Information. Any extracts or use of such data will require the contractor to apply derivative classifications and markings consistent with the source from which the extracts were made IAW DOD 5220.22M, National Industrial Security Manual for Safeguarding Classified Information, and Executive Order 12356.

6.1.2 The contractor will require access to and use of communications security

(COMSEC) materials. The contractor shall maintain COMSEC inventories and control keying material IAW COMSEC guidelines (AFPD 31-1, AFI 33-201 Volumes 1-5 and 9, and DOD 5220.22M). Coordinate with the government COMSEC manager or functional representative on all COMSEC operating instructions, and any required training plans. Maintain any required COMSEC documentation for HQ USAF, AFOTEC, Air Force Flight Test Center (AFFTC), or base-level COMSEC inspections.

6.1.3 Pursuant to DOD 5220.22M, Chapter 6, the contractor shall submit visit requests to AFOTEC. Direct requests must be approved by AFOTEC with coordination by the COR/Test Director prior to travel.

6.2 Safeguarding Information

The contractor shall:

6.2.1 Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act

Program, and AFI 33-332, Privacy Act Program requirements. These regulations set policies and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding official material.

6.2.2 Report to an appropriate authority any information or circumstances, of which they are aware, that may pose a threat to the security of DoD personnel, contractor personnel, resources, and/or classified or unclassified defense information.

Contractor employees shall be briefed by their immediate supervisor upon their initial on-base assignment.

6.2.3 The contractor is prohibited from attaching any computer hardware to the USAF network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the USAF Designated Approval Authority (DAA) representative via the contractor's submission of a written request to the COR. Contractor use of computer modems, thumb drives, and external hard drives on any machine attached to the USAF network is prohibited. Use of commercial internet service providers is prohibited.

6.2.4 Contractor personnel using computer assets shall comply with all computer security requirements. In addition, should contractor personnel require access to computer networks or databases, they shall inform the COR or Alternate COR, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the COR or Alternate COR within one workday of any contractor personnel who no longer require an open account and shall take action to close the computer account with the appropriate office within that same workday.

6.2.5 All contractor personnel who will be using Command, Control, Communications, and Computers (C4) systems belonging to the federal government to generate, process, store, transfer, or communicate information shall attend mandatory C4 systems security training. The format for the training may be either the USAF C4 Systems Security Awareness Training program format or an in-house contractor program that meets DoD requirements, subject to agreement by the COR. The training must be completed within the first thirty calendar days of the start of the contract or within the first 10 calendar days for contracts that have duration of 60 days or less. The contractor shall inform the COR when the training has been completed. The notice shall include the contract number and any applicable task order number, names of contractor personnel who attended and dates of training.

6.2.6 The contractor shall immediately notify the COR of any government system problems or issues which come to their attention which may impact the contractor's or the government's ability to access the systems.

6.2.7 No foreign nationals are authorized to work on this effort without prior written notification to the COR and PCO, and until approval is obtained from the PCO in accordance with current government policy and regulations.

6.2.8 All contractor personnel who require access to C4 systems are required to obtain a

National Agency Check (NAC) consistent with Public Trust Positions (Standard Form 85P or most current form). The contractor may submit a request to the COR that the government grant contractor employee(s) interim access to the C4 network while awaiting the results of a NAC. Interim access to the C4 network will only be granted after the contractor employees obtain at least a local background files check, and have submitted the appropriate documentation to obtain a NAC. These requests will be processed in accordance with government information security regulations and policy, and must include Security Office and DAA representative approval. These requests may be subject to disapproval. In no case will a contractor be given access to the network, including a group account, until a favorable NAC has been completed or interim access granted by the DAA representative. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or DAA representative at the government’s discretion. Any individual who subsequently does not pass the requirements for a full NAC shall not be authorized to work under this effort.

7.0 ATTACHMENTS/MISCELLANEOUS INFORMATION

7.1 Environmental Controls. The contractor shall comply with all environmental requirements imposed by the Federal Government, the USAF, and at locations where services are being performed. Such requirements are delineated in USAF Policy Directive 32-70, “Environmental Quality”, and other laws and regulations.

7.2 Safety Requirements. The contractor shall comply with all safety requirements imposed by the Federal Government, the USAF, and at locations where services are being performed.

Such requirements are delineated in AFPD 91-2, “Safety Programs”, AFI 91-301, “AF Occupational and Environmental Safety, Fire Protection and Health Program”, and AFI 91- 202, “USAF Mishap Prevention Program.”

7.3 Administrative Dismissal for Safety Reasons. The contractor will provide alternate work sites for personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to base or should leave the base during a workday. Local emergency conditions include inclement weather (i.e., snow, tornados, earthquakes, hurricanes, etc.). NOTE: Only the Base or AFOTEC Commander can declare such an emergency (not a Government Director, Division Chief, Site Commander, Program Manager, COR, PCO, etc.).

7.4 Performance of Services during crisis declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander. The performance of these services is not considered to be mission essential during time of crisis. Should a crisis be declared, the PCO or his/her representative will verbally advise the contractor of the revised requirements, followed by written direction.

7.5 Conflict of Interest. In accepting and performing the work required by this TO, and all amendments thereto, the contractor certifies the requirements of clause AFFARS 5352.209- 9000, Organizational Conflict of Interest (OCI) have been or will be adhered to. The contractor must immediately bring any OCI issues to the attention of the PCO for a determination of whether a mitigation plan is required.

7.6 Program Documentation. Current program documentation will be provided or requested through applicable Program Office.

7.7 Specialized Skills Requirement. Four years of operational experience and two years of operational test experience is desired.

8.0 CONTRACTOR FULL-TIME EQUIVALENT REPORTING.

Contractor Full-Time Equivalent Reporting: The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AFOTEC via a secure data collection site. Data may be collected by task order. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contracting Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure website is considered to be proprietary in nature when the contract number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link.

However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

Attachment 1: Security Reference Documents Applicable to All

1. Title 18, U.S. Code Crimes and Criminal Procedures

2. Title 50, U.S. Code War and National Defense

3. EO 12829 National Industrial Security Program -

Note: Source: The provisions of Executive Order 12829 (PDF format), as amended by Executive Order 12885, Vol. 58, No. 240, 16 Dec 1993

4. EO 12968 Access to Classified Information - NOTE: Amended by: EO 13467, June 30, 2008 See: Final rule of March 26, 1997 (62 FR 17683); Final rule of July 1, 1997 (62 FR 36984); EO 13284, January 23, 2003; EO 13311, July 29, 2003; EO 13462, February 29, 2008; EO 13516, October 28, 2009; EO 13539, April 21, 2010; EO 13549, 18 August 2010

5. EO 13526 Classified National Security Information, 29 Dec 09

6. EO 13526 Presidential Implementation Memo, 29 Dec 09

7. EO 13556 Controlled Unclassified Information, 4 Nov 10

8. EO 13587 Structural Reforms to Improve the Security of

Classified/Unclassified Information, 07 Oct 11

9. DoD 5200.1.PH-1 Classified Information Nondisclosure Agreement (SF 312) and Verbal Attestation Briefing Pamphlet

10. DODD 5210.50 Management of Serious Security Incidents Involving

Classified Information

11. DODD 5210.83 DoD Unclassified Controlled Nuclear Information (DoD

UCNI)

12. DoDM 5200.01

VOL. 1

DOD INFORMATION SECURITY PROGRAM:

OVERVIEW, CLASSIFICATION, AND

DECLASSIFICATION

13. DoDM 5200.01

VOL. 2

DOD INFORMATION SECURITY PROGRAM:

MARKING OF CLASSIFIED INFORMATION

14. DoDM 5200.01

VOL. 3

DOD INFORMATION SECURITY PROGRAM:

PROTECTION OF CLASSIFIED INFORMATION

15. DoDM 5200.01

VOL. 4

DOD INFORMATION SECURITY PROGRAM:

CONTROLLED UNCLASSIFIED INFORMATION

(CUI)

SCI Documents

16. EO 12333 United States Intelligence Activities

17. ICD 101 Intelligence Community Policy Systems, Amended 12

June 2009

18. ICD 503 Intelligence Community Information Technology Systems

Security: Risk Management, Certification and Accreditation, Amended 21 July 2015

19. ICD 700 Protection of National Intelligence, 21 Sep 2007 NOTE: Superseded by ICD 700 on 7 June 2012

20. ICD 702 Technical Surveillance Countermeasures, 18 Feb 2008

21. ICD 703 Protection of SCI and Sources & Methods, 21 June 2013

22. ICD 704 Personnel Security Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information, 1 Oct 2008

23. ICPG 704.1 Personnel Security Investigative Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information 2 October 2008

24. ICPG 704.2 Personnel Security Investigative Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information 2 October 2008

25. ICPG 704.3 Denial or Revocation of Access to Sensitive Compartmented Information, Other Controlled Access Program Information, and Appeals Process, 2 October

26. ICPG 704.4 Reciprocity of Personnel Security Clearance and Access Determinations, 2 Oct 2008

27. ICPG 704.5 Intelligence Community Personnel Security Database Scattered Castles, 2 Oct 2008

28. ICD 705 Sensitive Compartmented Information Facilities, 26 May

29. ICS 705-1 Physical and Technical Security Standards for Sensitive Compartmented Information Facilities, 17 Sep 2010

30. ICS 705-2 Standards for the Accreditation and Reciprocal Use of Sensitive Compartmented Information Facilities, 17 Sep

31. IC Tech Spec- for ICD/ICS 705 Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities, 23 Apr 12

32. ICD 707 Center for Security Evaluation, 17 Oct 2008

33. ICPG 707.1 Center for Security Evaluation Construction Security

Review Board, 12 Jun 08

34. ICD 710 Classification Management and Control Marking System, 21 Jun 2013

35. DoDI 5200.01 DoD Information Security Program and Protection of

Sensitive Compartmented Information, 21 Apr 2016

36. DoDM 5105.21 Volumes 1-3 Sensitive Compartmented Information Administrative

Security Manual, 19 Oct 2012

37. DoDD 5143.01 Under Secretary of Defense for Intel (USD(i)), Amended

22 Apr 2015

38. Joint DoD IIS Cryptologic SCI Information Systems Security Standards, 31 Mar 2001

39. AFI 14-302 Control, Protection, and Dissemination of Sensitive

Compartmented Information, 18 Jan 1994

40. AFI 14-303 Release of Intelligence to US Contractors, 01 April 1999

41. AFPD 14-3 Control, Protection, and Dissemination of Intelligence Information, 1 May 1998

42. AFMAN14-304 THE SECURITY, USE AND DISSEMINATION OF

SENSITIVE COMPARTMENTED INFORMATION

(FOUO)

01 May 1999

SAP Documents

43. DoD Instruction 5205.11 Management, Administration, and Oversight of DoD

SAPs, 6 Feb 13

44. DoDD 5205.07 Special Access Program (SAP) Policy, 1 Jul 10

45. SAF/AG Security Pamphlet 5

Security Guide to Conducting Preliminary Inquiries & Formal Investigations (In Special Access Programs), Feb 1998

46. DoDM 5205.07, Vol 1 SAP Security Manual: General Procedures, 18 Jun 15

47. DoDM 5205.07, Vol 2 SAP Security Manual: Personnel Security, 24 Nov 15

48. DoDM 5205.07, Vol 3 SAP Security Manual: Physical Security, 23 Apr 15

49. DoDM 5205.07, Vol 4 SAP Security Manual: Marking, 10 Oct 13

50. AFI 16-701 Special Access Programs, 8 Feb 14

51. AFOTECI 16-701 Special Access Programs, 15 Oct 15

52. AF Sup to DODM 5205.07, Vol 3 AF Manual 16-703, SAP Security Manual: Physical Security, 31 Dec 15

53. Organizational Standard Operating Procedures

54. Organizational Master System Security Plans and

Annexes Collateral Documents

55. DoD 5200.08-R, IC1 May 2009, see also DTM-09-012

PHYSICAL SECURITY PROGRAM

56. DoD 5230.30-M DOD MANDATORY DECLASSIFICATION REVIEW

(MDR) PROGRAM

57. DoD 5220.22-M

NATIONAL INDUSTRIAL SECURITY PROGRAM

OPERATING MANUAL (NISPOM)

58. DoD 5220.22-R Industrial Security Program Regulation

59. AFI 10-245 Antiterrorism, 25 Jun 15

60. AFI 31-101 Integrated Defense (FOUO), 8 Oct 09

61. AFPD 31-1 Integrated Defense, 28 Oct 11

62. AFI 16-1404 Air Force Information Security Program

63. AFI 31-501 Personnel Security Program Management

64. AFI 16-1406 Industrial Security

65. AFI 35-102 Security and Policy Review Process

66. CAPCO Controlled Access Program Coordination Office Marking

Guide

ISOO

67. 32 CFR Parts 2001 and 2003 ISOO, Classified National Security Information; Final Rule

Information Assurance Documents

68. DoD 5400.7-R; IC-1 DOD Freedom of Information Act Program, 11 Apr 06

69. DoD 8570.01-M, IC3 Information Assurance Workforce Improvement Program

70. DODI 4525.8 DOD Official Mail Management

71. DODM 4525.8 DOD Official Mail Manual

72. DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

73. DoDI 8520.03 Identity Authentication for Information Systems

74. DoDI 8510.01 RISK MANAGEMENT FRAMEWORK (RMF) FOR

DON INFORMATION TECHNOLOGY (IT)

75. DoDI 8523.01 Communications Security (COMSEC)

76. DoDI 8520.01 Cybersecurity Activities Support to DoD Information

Network Operations

77. AFMAN 33-282 COMPUTER SECURITY (COMPUSEC)

78. AFMAN 33-283 COMMUNICATIONS SECURITY (COMSEC)

OPERATIONS

79. AFSSI 7700 Emission Security

80. AFSSI 7702 EMISSION SECURITY COUNTERMEASURES

REVIEWS

81. AFI 33-200 Information Assurance (IA) Management

82. AFI 33-212 Reporting COMSEC Deviations

83. AFI 10-712 CYPERSPACE DEFENSE ANALYSIS (CDA)

OPERATIONS AND NOTICE AND CONSENT

PROCESS

84. AFI 33-230 INFORMATION ASSURANCE ASSESSMENT AND

ASSISTANCE PROGRAM

85. AFMAN 33-363 Management of Records

86. AFPD 33-1 Information Resources Management

87. AFPD 33-2 Information Assurance Program

88. CJCSM 6510.01B Cyber Incident Handling Program

OPSEC Documents

89. CJCSI 3213.01D Joint Operations Security, 7 May 12

90. NSDD No. 298 National Operations Security Program, 22 Jan 88

91. DODD 5205.02E DoD Operations Security (OPSEC) Program, Jun 2012

92. DoDM 5205.2-M DoD Directive Operations Security Program Manual, Nov

93. JOINT PUBLICATION 3-13.1 Electronic Warfare, 8 Feb 12

94. DODI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), 28 May 15

95. AFI 10-701 Operations Security (OPSEC), Jun 11

96. Kirtland Sup to AFI10-701 Operations Security (OPSEC)

97. AFI 10-704 Military Deception, Jan 15

98. AFPD 10-7 Information Operations, Aug 14

99. AFOTEC OPSEC Plan, Oct 15 NATO Documents

100. DODD 5100.55 United States Security Authority for North Atlantic Treaty Organization Affairs (USSAN), 27 Feb 06

101. USSAN 1-70 Implementation of the North Atlantic Treaty Organization Industrial Security Procedures, Apr 07

CNWDI- RD/FRD

102. DODI 5210.02 Access to and Dissemination of Restricted Data and Formerly Restricted Data

NC2-ESI

103. AFI 13-502 Safeguarding Nuclear Command and Control Extremely Sensitive, Dec 11

Policy Letters

104. AFMAN-33-302 SECAF Policy, FOIA, 14 Sep 10

105. OUSD(I) Memo, Implementation of Revised Classified National

Security Information Policy, 1 Oct 10

106. National Security National Security Staff – Change in Declassification

Review Policy, 24 Aug 10

107. Air Force HAF/IM Policy, Mandatory Declassification Review

(MDR), 18 Mar 10

108. SAF/AA SAF/AA Policy, RedactXpress, 30 Apr 10

109. SAF/AA SAF/AA Policy, Clarification on Transmission of UCNI over the NIPRNet, 6 Jan 09

110. SAF/AA SAF/AA Policy, CAPCO Markings, 30 May 06

111. SAF/AA North Atlantic Treaty Organization (NATO) Policy

Update, 12 Apr 02

112. AFOTECI 99-103 AFOTEC OT&E Guide