BICES_PWS_DRAFT.docx

SAF/AA CMO

U.S. BICES Program Office

Performance Work Statement (PWS) for

U.S. BICES SETA SUPPORT

1.0 INTRODUCTION/BACKGROUND: SAF/AA, Capability Management Office (CMO), Battlefield Information Collection and Exploitation Systems (BICES) Program Office (BPO) is tasked with the execution of the U.S. BICES and U.S. BICES-X (eXtended) program. U.S. BICES/U.S. BICES-X is the designated Department of Defense (DoD) Coalition Intelligence Information Sharing capability for DoD, the Services, and the Combatant Commands (and their component commands). As such, the U.S. BICES/U.S. BICES-X program ensures U.S. commanders at all levels are equipped with functionality and services for the timely and efficient sharing, collaboration, dissemination of intelligence with NATO, coalitions, and key partner nations. The services provided cross the spectrum of military operations (peacetime, crisis and conflict) as an enduring and sustainable capability for DoD and its foreign partners. To facilitate this effort, the U.S. BICES-X Enterprise is utilizing cross-domain sharing solutions which are federated to both streamline and maximize the ability of U.S. forces to operate in any theater of operations with allies and partner nations. The scope of this effort involves extensive coordination with the Combatant Commands, Services, and members of the Intelligence Community (IC) to provide intelligence support to operations, define capability requirements, and design, validate, and implement enhanced and sustainable technological solutions.

2.0 TASK ORDER OBJECTIVE: The objective of this task order is to provide SAF/AA CMO, BICES Program Office (BPO) with Systems Engineering and Technical Assessment (SETA) and subject matter expertise (SME) for delivering U.S. BICES/U.S. BICES-X intelligence information sharing capabilities and services to DoD and operational commanders on a global basis.

3.0 REFERENCE: Federal Acquisition Regulation (FAR) Subpart 37.2 – Advisory and Assistance Services

4.0 TASK REQUIREMENTS: The contractor shall provide the functional support, materiel required and connectivity (including global mobile access, when required) to fulfill this task order as described in the following tasks and subtask(s).

4.1 Task 1– Command and Partner Engagement: In coordination with the BPO, liaise with Combatant Commands, IC agencies, DoD components and U.S. partner nations to help shape intelligence sharing with coalition partners. This involves implementing information sharing processes applicable to on-going U.S. missions, and support to operational planning and execution where emerging world events impact the security of the nation. This requires devising potential technical solutions for intelligence information sharing where none currently exist, or improving on existing solutions should they prove incapable to providing adequate support to analysts and decision makers. Frequently, this effort involves closely working with command and subcomponent elements to ensure that the correct and proper information flow is determined and technical solutions are implemented. The Contractor shall provide Monthly Status Reports; Trip Reports; and Meeting Minutes for all meetings performed under this task.

4.1.1 Subtasks. The contractor will provide SME (SETA) support to BPO for coordination with all Combatant Commands and DoD Service Components.

4.1.1.1 Provide technical and intelligence operations advice to U.S. European Command (USEUCOM) and its components regarding the use of U.S. BICES and U.S. BICES-X; U.S. African Command (USAFRICOM) and its components regarding the use of U.S. BICES and the AFRICOM Data Sharing Network (ADSN) as a component of U.S. BICES-X; and the NATO Special Operations Headquarters regarding the use of U.S. BICES, BICES and NATO Special Operations Forces (SOF) BICES networks. Provide similar advice, as required, to NATO through the appropriate DoD components. Advise both USEUCOM and USAFRICOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.2 Provide technical and intelligence operations advice to U.S. Central Command (USCENTCOM) and its components regarding the use of U.S. BICES and the CENTCOM Partner Network (CPN) as a component of US BICES-X. Advise USCENTCOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.3 Provide technical and intelligence operations advice to U.S. Special Operations Command (USSOCOM) and its components regarding the use of U.S. BICES and U.S. BICES-X in support of SOCOM’s Global SOF Network. This advice extends to the Theater Operations Commands embedded within each Combatant Command as well as other special operations forces (when so directed). Advise USSOCOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.4 Provide technical and intelligence operations advice to U.S. Southern Command (USSOUTHCOM) and its components regarding the use of U.S. BICES and U.S. BICES-X SOUTH as a component of US BICES-X. Advise USSOUTHCOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.5 Provide technical and intelligence operations advice to U.S. Northern Command (USNORTHCOM) and its components regarding the use of U.S. BICES and U.S. BICES-X as applicable to the USNORTHCOM mission. Advise USNORTHCOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.6 Provide technical and intelligence operations advice to U.S. Pacific Command (USPACOM) and its components regarding the use of U.S. BICES and the Asia Pacific Intelligence Information Network (APIIN) as a component of US BICES-X. Provide similar advice and support to United States Forces Korea (USFK) and United States Forces Japan (USFJ) as required. Advise USPACOM on the use and employment of the U.S. BICES-X Enterprise to support Command requirements.

4.1.1.7 Provide technical and intelligence operations advice to the United States Navy (USN) regarding the integration and use of U.S. BICES and U.S. BICES-X as the DoD designated Coalition Intelligence Information Sharing capability. Advise USN on the use and employment of the U.S. BICES-X Enterprise to support Service requirements.

4.1.1.8 Provide technical and intelligence operations advice to the United States Marine Corps (USMC) regarding the integration and use of U.S. BICES and U.S. BICES-X as the DoD designated Coalition Intelligence Information Sharing capability. Advise USMC on the use and employment of the U.S. BICES-X Enterprise to support Service requirements.

4.1.1.9 Provide technical and intelligence operations advice to the United States Army (USA) regarding the integration and use of U.S. BICES and U.S. BICES-X as the DoD designated Coalition Intelligence Information Sharing capability. Advise USA on the use and employment of the U.S. BICES-X Enterprise to support Service requirements.

4.1.1.10 Provide technical and intelligence operations advice to the United States Air Force (USAF) regarding the integration and use of U.S. BICES and U.S. BICES-X as the DoD designated Coalition Intelligence Information Sharing capability. Advise USAF on the use and employment of the U.S. BICES-X Enterprise to support Service requirements with a particular emphasis on intelligence surveillance and reconnaissance (ISR) applications and services.

4.1.1.11 Provide advice and assistance with the drafting of Memorandum of Understanding (MOU) and Communications and Information Technology Support Agreements (CITSA) between the BPO and Combatant Commands, Services, or other DoD entities delineating the roles and responsibilities of each party regarding the use and sustainment of U.S. BICES/U.S. BICES-X. In addition, facilitate Combatant Command requirements for bi-lateral information sharing solutions with partner nations by coordinating required legal documentation such as Acquisition and Cross-Servicing Support Agreements (ACSA).

4.1.2 Knowledge Skills and Abilities (KSA). All Contractor personnel supporting Task 1 and its subtasks shall have the following experience and qualifications: At least 10 years of military intelligence experience, 5 of which must be in support to coalition or bilateral military information sharing activities.

4.1.2.1 For Subtasks 4.1.1.1,. 4.1.1.2, 4.1.1.4, 4.1.1.5, 4.1.1.6, and 4.1.1.11: At least 3 years’ demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts. Demonstrated experience working at the Joint Staff, at a Combatant Command, or with NATO preferred.

4.1.2.2 For Subtask 4.1.1.3: At least 3 years’ demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts and a minimum of three years working with or in support of special operations. Demonstrated experience working at the Joint Staff, at a Combatant Command, or with NATO preferred.

4.1.2.3 For Subtasks 4.1.1.7, 4.1.1.8, 4.1.1.9, and 4.1.1.10: At least 3 years’ demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts and a minimum of three years working within or in direct support of the relevant Service. Demonstrated experience working at the Service Headquarters or a major Service command preferred.

4.2 Task 2- Technical Architecture. Develop architectural concepts and technical solutions for delivering U.S. intelligence information globally, with an efficient, cost-effective approach that delivers an enduring intelligence environment and the agility to provide coalition connectivity, or communities of interest rapidly in support of mission objectives. The conceptual design of this environment is called US BICES eXtended (US BICES-X) Enterprise, which has as its foundation and core operating principles, the US BICES program. This global intelligence information sharing environment must be designed to maintain interoperability between the U.S. information enterprise and U.S. partner nations within the AORs of each participating command. The environment must maximize the use of cross-domain security (CDS) and multi-level security (MLS) solutions. The environment must also link to the Defense Intelligence Information Environment, the Joint Information Environment (JIE), and support the Mission Partner Environment (MPE) framework. The overall environment will provide the equivalent of a U.S. multinational intelligence network, connecting all U.S. allies and its coalition partner nations with the DoD. The Contractor shall provide Monthly Status Reports; Trip Reports; and Meeting Minutes for all meetings performed under this Task. The Contractor will also coordinate the development and annual update of the U.S. BICES-X Enterprise Global Architecture Design document for the BPO. Additionally, the Contractor will assist the BPO with reviewing and, as required, provide comments on all U.S. BICES-X Enterprise design documents (e.g., System Design Document (SDD)) produced by the U.S. BICES-X (Core) and U.S. BICES-X (ES) contractors.

4.2.1 Subtasks: The contractor will provide SME (SETA) support to BPO for the design and development of the U.S. BICES-X Enterprise with specific emphasis placed on the evaluation, analysis and recommendation of CDS and MLS capabilities. This subtask also includes assisting the BPO with oversight of Information Security across the enterprise.

4.2.1.1 Provide senior engineering and lead architect support in the evaluation, analysis and design of the U.S. BICES-X Enterprise.

4.2.1.2 Assist the BPO with oversight and management of the implementation, fielding, and sustainment of the U.S. BICES-X Enterprise.

4.2.1.3 Provide the BPO with technical advice and architectural design recommendations in assessing and evaluating appropriate interfaces between the U.S. BICES-X Enterprise and NATO and/or foreign partner systems and networks.

4.2.1.4 Provide the BPO with technical advice and architectural design recommendations in assessing and evaluating appropriate interfaces or integration points between the U.S. BICES-X Enterprise and the emerging DI2E, JIE and MPE constructs.

4.2.1.5 Provide certified Information Security Specialists to assist the BPO with coordination for the accreditation of the U.S. BICES-X Enterprise and any related interfaces. This includes providing oversight of accreditation documentation, Security Test and Evaluation (ST&E), and reporting of any security related concerns.

4.2.2 Knowledge Skills and Abilities: All Contractor personnel supporting Task 2 and its subtasks shall have the following experience and qualifications:

4.2.2.1 For Subtasks 4.2.1.1 thru 4.2.1.4: At least 10 years demonstrated engineering experience in the design, testing, implementation, and sustainment of complex intelligence or information sharing systems; at least five years demonstrated experience working in support of military intelligence; at least 3 years demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts; one to two years demonstrated experience working with multi-level security solutions supporting coalition environments. Demonstrated experience working at the Joint Staff, at a Combatant Command, or with NATO preferred.

4.2.2.2 Subtask 4.2.1.5: CISSP Certification mandatory. At least 10 years demonstrated experience supporting technical security of military systems with a minimum of two years’ experience in coalition operations. Must have a working knowledge of coalition or bilateral military information sharing efforts.

4.3 Task 3 - Network Implementation. Design and architect key networking capabilities to connect the U.S. with its allies and partner nations in the US BICES-X environment. This includes implementing various transport capabilities and immediate ad hoc physical networks to support operations in austere and extreme environments to share intelligence with partner nations. This is a global effort, extending the US BICES-X environment anywhere it is needed for immediate capability requirements, such as voice and data services, complex applications, and field deployments for end users. The Contractor shall provide Monthly Status Reports; Trip Reports; and Meeting Minutes for all meetings performed under this Task.

4.3.1 Subtasks

4.3.1.1: Provide technical advice and recommendations on network solutions to federate the U.S. BICES-X Enterprise in support of DoD direction to utilize US BICES/US BICES-X as the Coalition Intelligence Information Sharing capability for DoD, the Services, and the Combatant Commands (and their component commands).

4.3.1.2: In conjunction with the BPO, work with the Combatant Commands and Services to identify networking solutions to support the extension of U.S. BICES/U.S BICES-X to support military operations in any theater of operations. This includes recommendations on the deployment of U.S. BICES/U.S. BICES-X aboard naval vessels, aboard aircraft, in austere locations, and, as required, with partner nation forces.

4.3.1.3: Provide advice and guidance on networking solutions and options for supporting USSOCOM and special operations forces in the execution of their global mission.

4.3.1.4: Provide advice and recommendations for network solutions enabling the flow of ISR across U.S. BICES and U.S. BICES-X to include: live streaming video; large format imagery products; and post-product PED (Processing, Exploitation and Dissemination) reporting. This may include working with foreign partner nations to facilitate the two-way sharing of ISR.

4.3.2 Knowledge Skills and Abilities: All Contractor personnel supporting Task 3 and its subtasks shall have the following experience and qualifications:

4.3.2.1 At least 10 years demonstrated network engineering experience in the design, testing, implementation, and sustainment of information sharing network solutions to include knowledge of satellite and terrestrial communications; at least five years demonstrated experience working in support of military intelligence with specific experience supporting special operations forces; at least 3 years demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts. Demonstrated experience working with the Joint Staff, Combatant Commands, or with NATO preferred.

4.2.2.2 Demonstrated experience working with network solutions for ISR.

4.4 Task 4– Requirements Management, Configuration Management and Change Management: Assist the BPO with the execution and development of U.S. BICES-X Enterprise Requirements Management, Configuration Management and Change Management processes. The Contractor shall provide Monthly Status Reports; Trip Reports; and Meeting Minutes for all meetings performed under this Task.

4.4.1 Subtasks: Provide SME (SETA) to assist the BPO with the management and execution of the U.S. BICES-X Enterprise Requirements Management, Configuration Management, and Change Management Lifecycle Processes.

4.4.1.1 Provide advice and recommendations for the U.S. BICES-X Requirements Management (RM) process. Coordinate and manage the collection of all U.S. BICES-X requirements and facilitate the prioritization, validation, and approval/disapproval process for these requirements. Ensure that BPO staff, customer/stakeholders and US BICES-X (Core) and (ES) contractors are familiar with the RM process. Develop updated processes for review as necessary or when directed.

4.4.1.2 Provide advice and recommendations for the U.S. BICES-X Configuration Management (CM) process. Assist the BPO with management of the CM process, to include reviewing and validating equipment baselines and assisting the BPO with asset audits. As directed, serve as the Secretary for U.S. BICES/U.S. BICES-X Configuration Control Boards (CCB). Ensure that BPO staff and US BICES-X (Core) and (ES) contractors are familiar with the CM process. Develop updated processes for review as necessary or when directed.

4.4.1.3 Provide advice and recommendation for the US BICES-X Change Management process. Assist the BPO with management of the Change Management process, to include review of applicable governance, alignment with enterprise development efforts. As directed, serve as Secretary for U.S. BICES-X Change Management Boards (CMB). Ensure that BPO staff and US BICES-X (Core) and (ES) contractors are familiar with the Change Management process. Develop updated processes for review as necessary or when directed.

4.4.2 Knowledge Skills and Abilities: Contractor personnel supporting Task 4 and its subtasks shall have the following experience and qualifications:

4.4.2.1 At least 10 years of military intelligence experience 5 of which must be in support to coalition or bilateral military information sharing activities. At least 3 years demonstrated experience in requirements and/or configuration/change management. At least 3 years’ demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts. Demonstrated familiarity of or ITIL certification highly desirable. Demonstrated experience working with the Joint Staff, Combatant Commands, or with NATO preferred.

4.5 Task 5 – Intelligence, Surveillance and Reconnaissance (ISR) Support. Support the extension and sharing capability of ISR services and capabilities across the U.S. BICES-X Enterprise. This is a complex task that leverages the previous tasks for requirements, capability, and implementation. Included in this effort is the need for liaisons with allies and partner nations to coordinate and collaborate on acquisition strategy and execution of ISR related information sharing capability. This effort is primarily concentrated on existing programs within NATO or European partners to include the NATO Joint ISR program and related initiatives such as Multi-sensor Aerospace-ground Joint Intelligence, Surveillance and Reconnaissance Interoperability Coalition (MAJIIC); however, much of the detail resulting from that effort will be repeated throughout the international implementation of the US BICES-X environment. The Contractor shall provide Monthly Status Reports; Trip Reports; and Meeting Minutes for all meetings performed under this Task.

4.5.1 Subtasks: The contractor will provide SME (SETA) support to BPO for the design and development of ISR capabilities across the U.S. BICES-X Enterprise. Recommended services and capabilities shall cover the full scope of ISR to include live streaming video, geospatial display, post-product reporting mechanisms, and tools to support Processing, Exploitation and Dissemination (PED) at the operational and tactical levels.

4.5.1.1. Provide research, analysis and recommendations on tools and services that enhance the implementation and sustainment of ISR across the U.S. BICES-X Enterprise.

4.5.1.2 Provide research, analysis and recommendations on tools and services to support the PED process at both the operational and tactical levels. This includes working with U.S. BICES-X network engineer experts to identify solutions for tactical operations support in austere operating environments.

4.5.1.2. Assist the BPO with recommendations on how U.S. BICES-X ISR services can interface with the NATO Joint Intelligence, Surveillance and Reconnaissance (JISR) program.

4.5.1.3 Assist the BPO with recommendations on the role of U.S. BICES-X ISR services in the MAJIIC program and other coalition information sharing efforts as required.

4.5.2 Knowledge Skills and Abilities: All Contractor personnel supporting Task 5 and its subtasks shall have the following experience and qualifications:

4.5.1.1 At least 10 years of military intelligence experience 5 of which must be in support to coalition or bilateral military activities. At least 3 years demonstrated experience in ISR programs. At least 3 years’ demonstrated experience deploying or actively supporting coalition or bilateral military information sharing efforts.

4.5.1.2 Demonstrated experience supporting ISR services and capabilities with the Joint Staff, Combatant Commands, or with NATO.

4.5.1.3 Demonstrated knowledge of the NATO JISR program.

4.5.1.4 Demonstrated knowledge of the MAJIIC program.

4.6 Deliverable(s): The Contractor shall provide task order deliverable(s) to the COR in a format mutually agreed upon by the Government and the Contractor.

4.6.1 Project Plan - A Project Plan (PP) will be developed and milestones established for tracking the technical progress of this project. The final PP will be presented at a Contract Kickoff Meeting to be organized by and held at the contractor’s facility. Upon approval of the PP, the contractor shall set a project schedule baseline so that subsequent updates reflect the true status of the project. Updates to the PP and schedule will be provided as changes occur. The “true” picture of the project actual versus planned will be used in the contract’s Final Report.

4.6.2 Monthly Status Reports - Regular monthly status and progress reports shall be provided in a format that provides a summary of the task objective, progress made since the last report, issues, and planned effort for the next period. Reports shall be submitted electronically by the 15th of the month for the previous month. The report shall include a graphic that shows, as a minimum, the planned spending rate, the actual spending to date, and the funds provided. The monthly report shall also include the total amount billed, the total amount paid, the date and amount of the last payment, and the date and amount of the latest invoice.

4.6.3 Trip Reports – Reports on all trips shall be provided in a form that provides the purpose of the trip, key personnel contacted, a summary of all meetings or activities, key actions resulting from the event(s), and any recommendations. Trip Reports are due within 7 business days of the end of the travel. The report shall be provided electronically at the unclassified level.

4.6.4 Meeting Minutes - Minutes from project meetings shall be documented to include general information related to the meeting, decisions made, attendees, issues, and action items assigned. Formal meetings that are conducted using video teleconferencing or conference calls shall be similarly documented. Meeting minutes should be submitted within 10 days of the completion of the meeting and should also include copies of any briefing slides presented at the meeting. The report shall be provided electronically at the appropriate level of classification.

4.6.5 Final Report - A final report that documents overall accomplishments and deliverables shall be provided to the BPO and the Contracting Officer. The final report will provide a summary of the contract, lessons learned, and any recommendations.

4.7 Key Positions: All positions within this requirement are designated as ‘key’ for the overall success of the task order.

4.8 Services Summary: Attachment A

5.0 GOVERNMENT FURNISHED PROPERTY

5.1 Government Provided Equipment/Office: Workstations/ADP equipment, office space, etc., will be made available for Contractor personnel.

6.0 DATA: The Government has unlimited rights to all deliverables of this task order to include intellectual property rights.

7.0 TRAVEL:

7.1 The Contractor shall be required to travel to attend meetings in support of tasks listed above to fulfill PWS requirements. All trips will be in accordance with regulatory requirements and actual travel shall be coordinated and pre-approved by the Government COR in writing at least three weeks prior to scheduled travel. In exigent circumstances, short-notice travel may be verbally approved by the COR with written follow-up no later than 48 hours after. Trips scheduled below are subject to change. The Government will only reimburse allowable costs in accordance with FAR 31.205-46. The Contractor shall be required to provide travel receipts to the COR for all allowable costs. Travel projections are subject to change based on Government requirements.

7.2 Local travel to attend meetings within the local city or base of assignment commuting vicinity shall be considered a cost of doing business and shall not be separately reimbursed.

8.0 SECURITY INSTRUCTIONS: A DD-254 will be required for this TO requirement.

8.1 Physical Security. The Contractor shall safeguard all Government property and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment and materials shall be secured.

8.2 Performance under this PWS shall require a Top Secret/SCI clearance (to include SI, TK, G, and HCS) and NATO SECRET. Personnel security investigations will be completed within at least the previous five years before the end of the period of performance (PoP) to allow for access to government facilities at the Top Secret level and for access to Sensitive Compartmented Information (SCI) as appropriate. There may be special program access requirements in support of this TO.

8.3 Classified Information. For all TO requirements with classified work or access to classified information, the Contractor shall:

8.3.1 Clearance Requirements - DD Form 254. Comply with, coordinate and complete a DD Form 254, Department of Defense Contract Security Classification Specification requirements. Upon execution of award, the CO will sign the DD Form 254 for incorporation into the TO. The BPO will provide security classification guidance for contract performance. The Government will oversee handling and storage of classified information and provide appropriate storage capability for all classified material. All classified information shall be returned to the government upon termination of the TO.

8.3.2 The Contractor shall have the required facility clearance at the time of proposal. Contractor personnel shall have appropriate clearances prior to commencing work on any TO unless otherwise approved in writing by the CO. The Contractor shall also complete visit requests for each individual that will be performing work on a TO in the Defense Security Service (DSS) Joint Personnel Adjudication System (JPAS) prior to performance start unless otherwise approved in writing by the CO.

8.3.2.1 The Contractor shall notify the servicing Information Protection Office of contract award within 30 days after basic contract award. The notification shall include:

• Name, address, and telephone number of company representatives

• The contract number and contracting agency

• The highest level of classified information to which Contractor employees require access

8.3.2.2 The contractor must possess a facility security clearance at the classification level of Top Secret/SCI prior to submitting a proposal. ACC Industrial Security guidelines stipulate that facility clearances must be specific and that Contractor employee security clearances cannot be higher than the facility clearance of the company. Facility clearances shall match the clearance level required of Contractor employees. For example, if a TO effort requires Contractor employees to have Top Secret clearances, then the company facility clearance shall be Top Secret and shall be upgraded prior to performance on the TO, unless otherwise directed by the CO. Local security clearance requirements will apply to each TO.

8.3.3 Visitor Group Security Agreement (VGSA). The contractor shall enter into a long term visitor group security agreement if contract performance is on base for 90 days or more. This agreement shall outline how the contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation. Enter into a long term VGSA through the host base Information Security Program Manager, when applicable. Provide the information requested by the Notification of Government Security Activity and Visitor Group Security Agreements Clause, AFFARS 5352.204-9000. Visitor Groups shall safeguard all collateral classified information IAW DoD 5200.1-R, Information Security Program; AFI 31-401, Information Security Program Management; AFI 31-601, Industrial Security Program Management, and other directives deemed necessary by the servicing Information Protection office. In addition to the items required by AFFARS 5352.204-9000, the VGSA shall outline how the Contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation, the use of security forms and conducting inspections required by DoD 5220.22-R, Industrial Security Regulation, and protection of high value pilferable property.

8.3.4 Security Training. Provide employees with training required by DoD 5200.1-R, Information Security Program Regulation and AFI 31-401, Information Security Program Management. The Contractor shall also provide initial and follow-on training to their Contractor personnel who work in Air Force controlled/restricted areas IAW AFI 31-101, Air Force Installation Security Program. This training shall be provided by an appointed security manager for the on-base Visitor Group. The security manager may be a full time or an additional duty position.

8.3.5 Pass and Identification Items. Ensure the pass and identification items required for contract performance are obtained for employees and non-Government owned vehicles prior to the TO start date.

8.3.6 Retrieving Identification Media. Retrieve all identification media, including vehicle passes, when the contract expires or from employees who depart for any reason before the contract expires, e.g., terminated for cause, retirement, etc.

8.3.7 Traffic Laws. Ensure all Contractor employees comply with base traffic regulations.

8.3.8 Weapons, Firearms and Ammunition. Not possess weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on any installation or any office/working location covered under this contract.

8.3.9 For Official Use Only (FOUO). Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting and safeguarding FOUO material.

8.3.10 Reporting Requirements. Report to an appropriate authority (i.e., CO, PM, COR) any information or circumstances which they are aware of that may pose a threat to the security of DoD personnel, Contractor personnel, resources and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.

8.3.11 Controlled/Restricted Areas. Implement local base procedures for entry to Air Force controlled or restricted areas where Contractor personnel shall work. The Government will complete an AF Form 2586, Unescorted Entry Authorization Certificate, completed and signed by the sponsoring agency’s Security Manager, before a Restricted Area Badge will be issued. Contractor employees shall have a favorably completed National Agency Check plus written Inquiries investigation before receiving a Restricted Area Badge. Interim access may be granted IAW AFI 31-501, Personnel Security Program Management. Contractor personnel must have appropriate clearances prior to commencing work on any TO unless otherwise approved in writing by the CO.

8.3.12 Key Control. Establish and implement procedures to ensure all keys issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall not duplicate any keys issued by the Government.

8.3.12.1 The Contractor shall immediately report to the COR or PM any occurrences of lost or duplicated keys within two days of occurrence.

8.3.12.2 In the event keys are lost or duplicated, the Contractor may be required, upon written direction of the CO, to re-key or replace the affected lock or locks with no additional cost to the Government. The Government may replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the Contractor.

8.3.12.3 The Contractor shall not loan issued keys to any other persons nor allow access by use of issued keys to other persons not associated with performance of work at the contract work site.

8.3.13 Lock Combinations. Control access to all Government-provided lock combinations to prevent unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

8.3.14 Theater/Country Clearances. Obtain special theater and/or country clearances, and comply with theater/country specific requirements, for applicable OCONUS work. These requirements will be identified in the TO PWS. The Electronic Foreign Clearance Guide at https://www.fcg.pentagon.mil/fcg.cfm states the requirements for travel to specific countries.

8.3.15 Restricted/Formerly Restricted Data. Obtain a final U.S. Government clearance at the appropriate level before obtaining access to RESTRICTED DATA and FORMERLY RESTRICTED DATA.

8.4 Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access will be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances.

8.5 The Contractor shall provide a National Agency Check with Inquiries (NACI) for all contractor employees who are to be provided access to Government e-mail/internet, LAN/WAN and other Government information networks.

8.6 Clearance Requirement. If access to classified information is a requirement at the Contractor’s facility, a SF 312 Non-Disclosure Agreement (NDA) initiated by the company’s Facility Security Officer (FSO) is required. The Contractor must possess or obtain a facility security clearance at the appropriate classification level for the work prior to performing contract work.

8.7. Listing of Employees. The contractor shall maintain a current listing of employees. The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Contracting Officer, Program Manager, and (SSA). An updated listing shall be provided when an employee's status or information changes.

9.0 TRANSITION PLAN: In the event a follow on contract is required, and the prime contractor does not win the next award, the Contractor shall prepare a plan for transition to the new personnel and provide it to the COR for review not later than 60 days before the end of the period of performance.

10.0 ADMINISTRATION CONSIDERATIONS:

10.1 Performance Schedule: The Contractor shall perform this task from 11 March 2015 through 31 January 2016.

10.2 Potential Place of Performance: The Contractor shall work at the following locations to perform and accomplish tasks identified in this purchase order:

· SAF/AA CMO, 11242 Waples Mill Road, Fairfax, VA

· OUSD(I) US BICES PMO, Sequoia Plaza, 2101 Washington Blvd, Arlington, VA (Alternate: Pentagon)

· HQUSSOCOM, MacDill AFB, Tampa FL (Alternate: HQUSCENTCOM, MacDill AFB)

· HQUSPACOM, Camp Smith, Wahiawa, HI (Alternate: USPACOM JIOC Makalapa, Pearl Harbor, HI)

· RAF Molesworth, Hangar 84,Cockbrook Lane, Molesworth, England PE28 0QB (Alternate: HQUSEUCOM, Patch Barracks, Stuttgart GE)

· WR ALC Det 1 / DGS-X, 50 West Flightline Drive, Bldg 338,Joint Base Langley-Eustis,Hampton VA

· Intelligence Systems Support Office (ISSO) Ft Washington, 10530 Riverview Road, Fort Washington, MD

10.2.1 Telework: Telework shall be permitted for this task order. If permitted, the Contractor shall follow their corporate guidance with regard to telework capabilities and frequency.

10.3 Duty Hours: Normal duty hours are 0800-1700, Monday through Friday. Federal Holidays will be observed.. Because performance of this requirement will be accomplished at various OCONUS locations, a list of the federally recognized OCONUS holidays will be provided at the task level. Recognizing the unique nature of this requirement, the Project Manager may approve alternate work hours for individual tasks. The Contractor may work compressed work schedules, with coordination/approval of the Program Manager/COR. Extended work hours may be required in support of military operations or crisis planning. No overtime premium will be payable under this contract.

10.4 Base Shutdown/Inclement Weather: The Contractor will follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. During inclement weather, and if it is determined the applicable place of performance is closed, the Contractor is required to assign personnel to work at other approved locations when possible. The website for guidance regarding status of performance locations is [http://www.opm.gov/status/].

10.5 Kickoff Meeting. Contractor shall attend a kick off meeting specific to the TO requirement with the COR and the Administrative CO within thirty (30) days of contract award.

10.6 Contractor Inventory. In accordance with Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Action, 2011.

10.6.1 The Contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this task order via the secure Contractor Manpower Reporting Application (CMRA) data collection site. The Contractor is required to completely fill in all required data fields at: http://www.ecmra.mil. Reporting inputs shall 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 anytime during the FY, all data shall be reported not later than 31 October *of each calendar year. The Contractor may direct questions to the CMRA help desk.

NOTE *: Reporting Period: Contractors are required to input data by 31 Oct of each year.

10.6.2 Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contractor 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.

10.6.3 User Manual: Data for the AF services requirements must be input at the AF CMRA link. However, user manuals for Government personnel and Contractors are available at the U.S. Army CMRA link at http://www.ecmra.mil.

Attachment A: Services Summary

Table 2 - Services Summary

a) qualified personnel are on the job at TO Start unless previously negotiated by the CO and.

b) the mission is not impacted due to position vacancies or personnel qualifications

a) Vacancies are filled with qualified personnel within 14 days of vacancy, unless approved in writing or otherwise directed in advanced by the CO

AND

b) there is no mission impact due to position vacancies or unqualified personnel.

Develop and submit all required deliverables

a) 100% of CDRL deliverable requirements are met and received on time.

b) critical information is accurate.

a) 100% of Government-directed travel and/or representation is completed unless previously negotiated by the CO, and

b) 95% of travel reports are submitted on time.

Note: IAW FAR 52.212-4, Contract Terms and Conditions, the government reserves the right to inspect or test services that have been tendered for acceptance. The government may require reperformance of any nonconforming services at no increase in contract price. If reperformance will not correct the performance issue or is not possible, the government may seek an equitable price reduction or contractual processes will begin to terminate the contract. Past performance history will be reported in Contractor Performance Assessment Reporting System to reflect satisfactory or unsatisfactory performance.

PWS