9002-0020.doc

HQ AFSPC

CONTRACT INFORMATION

Information Assurance (IA) technical support system engineering services

360 Command View Colorado Springs, CO 80915

(1 Base Yr and 2 Opt Yrs)

STATEMENT OF WORK

CAASETA Task Order A4A6-0145

INFORMATION ASSURANCE TECH SUPPORT

FOR

SATCOM SYSTEMS BRANCH, HQ AFSPC/A6MZ

29 Mar 07 (Revised) 9002-0020

1.0 DESCRIPTION OF SERVICES: Contractor services are required to provide Information Assurance (IA) technical support system engineering services in support of Headquarters Air Force Space Command (HQ AFSPC) Satellite Communications (SATCOM) Systems Branch (A6MZ) functions. This effort will support responsibilities assigned to AFSPC as the SATCOM System Expert (SSE) for assigned Military SATCOM (MILSATCOM) systems.

1.1 ORGANIZATION BEING SUPPORTED:

HQ AFSPC/A6MZ

150 Vandenberg St, Ste 1105

Peterson AFB CO 80914

1.1.1 Mission: HQ AFSPC/A6MZ, the SATCOM Systems Branch, functions as the SSE for systems assigned by US Strategic Command (USSTRATCOM) in its role as the SATCOM Operational Manager (SOM) in accordance with the Chairman Joint Chiefs of Staff Instruction (CJCSI) 6250.01, Satellite Communications. HQ AFSPC/A6MZ mission responsibilities include the following:

1.1.1.1 SSE for assigned Extremely High Frequency (EHF) and Protected MILSATCOM systems, including the Milstar, Advanced EHF (AEHF), and Transformational Satellite (TSAT) systems.

1.1.1.2 Support to the SOM in accordance with CJCSI 6250.01 and USSTRATCOM Strategic Command Directive 714-2, SATCOM System Experts Responsibilities; and execution of SOM delegated tasks.

1.1.1.3 Establish management structures that will enable seamless integration between system segments and resolve operational issues.

1.1.1.4 Provision operational, policy and technical support to refine SATCOM system requirements; design systems; and plan communications operations for existing and emerging commercial and advanced military satellite communication systems.

1.1.1.5 Participate in mission area planning to address SATCOM system issues.

1.1.1.6 Primary office tasked with focusing SATCOM systems to ensure integration into the Global Information Grid (GIG).

1.1.1.7 The SOM and SSE are directed by Joint Staff to develop concepts and implement policies to optimize satellite resource availability to the Unified Combatant Commands (UCCs) and other users.

1.2 SCOPE OF SERVICES REQUIRED: Following is a description of the overall broad and general efforts that are required from the contractor. The Contractor shall support:

1.2.1 Security and Information Assurance of SATCOM services from legacy systems to the evolving SATCOM systems.

1.2.2 Provision of essential non-personal technical analysis, consulting, and software and engineering support services in support of the HQ AFSPC/A6MZ mission.

1.2.3 Security and Information Assurance of MILSATCOM network operation and configuration expertise to support systems security; and policy and control procedures supporting customers in Department of Defense (DoD) and non-DoD Agencies, Joint Staff, UCCs and Services in both the joint and international and coalition operational environments.

1.2.4 Support to the assigned SSE systems in the execution of SSE responsibilities as outlined in Joint Staff and USSTRATCOM directives. This support is associated specifically with activities necessary to the security of system resources, analyze network security requirements, and propose and implement technical solutions necessary for policy development, day-to-day and long-range information assurance, and security of MILSATCOM systems in the legacy and future EHF system environments.

1.2.5 Analysis of user missions, requirements, apportioned resources, and the security capabilities of present/future systems to meet the current and planned operational requirements. The contractor shall develop information assurance concepts that meet the validated requirements of US strategic and tactical warfighters. These efforts shall include existing or planned systems architectures, technology advances, system/subsystem constraints, standards, and other considerations during all phases of systems design and development. Also, the force structure of International Partner (IP) and coalition users shall be considered and baseline security policy documents developed to support migration/transition of legacy operations to AEHF and evolving EHF systems. Deliverables, where appropriate, shall be coordinated with user organizations to ensure information assurance compliance. In addition, although the basic concepts may be similar, individual country participants may have special or unique requirements that may need to be addressed separately. Information for each country may not be shared with another and the contractor must protect the separation of US Only and IP data. Current IP members include Canada, United Kingdom, and the Netherlands.

1.2.6 SATCOM information assurance planning for the SATCOM systems. Support also includes planning, integrating, configuration, and operational management/optimization of security procedures for the MILSATCOM systems within the organizational framework of HQ AFSPC/A6MZ and other organizations such as HQ AFSPC/A6I, A4, A3, A5, USSTRATCOM, and the Space and Missile Systems Center (SMC). These systems provide the President and Secretary of Defense, the Unified Combatant Commanders and deployed strategic and tactical forces with worldwide survivable and protected communications.

1.2.7 Development and implementation of technical solutions as required by the government for the day-to-day and long-range SATCOM security management and enforcement. The functions include, but are not limited to, interfacing with the user community to adequately understand their requirements, planning for information assurance and security of system/network upgrades/transitions to meet validated requirements.

1.2.8 Security of the SATCOM systems into full operations through support of Security Working Groups and Operational Transition Groups (OTG).

1.3 SPECIFIC REQUIREMENTS:

1.3.1 REQUIREMENT 1: SATCOM Security Architecture Analysis. (50%) The Contractor will support A4/A6 in the certification and accreditation process, and the contractor will assist or provide recommendations for testing in support of the site accreditations. Security certification and accreditation will be integrated into the overall Developmental and Operational Testing and Evaluation (DT&E and OT&E) process. Security accreditation will be conducted as defined in DoD 5200.40, DoD Information Technology Security Certification and Accreditation Process (DITSCAP), or the DoD Information Assurance Certification and Accreditation Process (DIACAP) as defined in DoD CIO Memo, "Interim DoD Information Assurance (IA) C&A Process Guidance,” 6 July 2006. Accreditation will occur before any sensitive or classified operational traffic is transported or handled by a new system. Testing for security and protection will commence during each DT&E and/or OT&E test period. The testing will include all available components to include cryptographic (crypto) equipment and test keys.

1.3.1.1 The contractor shall review, comment, coordinate and recommend concurrence or non-concurrence for security documents such as System Security Authorization Agreements (SSAAs), Interim Approval to Test, Letter of Assurances, Security Classification Guide Challenges, and Engineering Change Proposals; develop briefings and information papers on security issues for leadership and the protected SATCOM community; review and comment on network architectures (planning tool and key management tool networks) as well as satellite architectures; and work with all stake holder Designated Approval Authorities (DAAs) to assure an understanding of accreditation boundaries, and organizational roles and responsibilities.

1.3.2 REQUIREMENT 2: Engineering Working Groups. (50%) In order to ensure future systems are safe, secure and operationally feasible, the contractor must be knowledgeable of protected SATCOM systems satellite payload and bus operations, Strategic and Tactical end-user SATCOM operations, and Transmission Security (TRANSEC) and Communications Security (COMSEC) processes.

1.3.2.1 The contractor shall support and participate in engineering working groups such as the Advance EHF Security Engineering working group, International Partner AEHF Security Working Group, System Security Engineering working group, TSAT “Face to Face” working group, EPS security working groups and ad-hoc working groups to work specific information assurance issues. Government estimates up to 18 working group meetings per year, and anticipates travel as indicated in section 4.2. Contractor will be required to present briefs and provide technical discussions to US and IP participants at these working groups

1.4 ADDITIONAL DELIVERABLES

1.4.1 Monthly Status Report. The contractor shall provide a monthly status report (MSR). As a minimum, the Monthly Status Report shall contain a narrative description of the work accomplished during the previous month and identify any significant accomplishments, slippages in delivery dates of deliverables, new delivery dates agreed with government representatives, and/or problems. Work accomplished and deliverable status will be plotted against the project schedule. The project schedule will identify (flag) any new milestone dates developed as work progresses and delivery date accelerations/slippages. In addition, the MSR shall itemize (in tabular and graphical format) the cumulative labor hours and associated funding expended/remaining on each specific requirement. The MSR shall also contain a current Technical Information Center (TIC) inventory listing, showing all relevant program documentation material, software, and deliverables up to and including Secret information relating to this task order contained in the TIC. (CDRL 0030)

1.4.2 Technical Information Center (TIC). The Contractor shall develop and maintain a TIC containing soft copies of all relevant program documentation material, software, and deliverables up to and including Secret information relating to this task order provided by the government or developed or obtained by the contractor. The contractor shall deliver the TIC to the government at the end of task order performance, and shall submit an updated TIC inventory with the MSR. (CDRL 0037)

2.0 SERVICE DELIVERY SUMMARY.

Deliverables are completed in an accurate and timely manner.

(2). No more than two (2) sets of corrections/edits are required on any one document;

(3). All corrections are accomplished within two (2) working days.

Contractor successfully meets requirements of Task Order.

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES:

3.1 GOVERNMENT FURNISHED PROPERTY (GFP).

3.1.1 HARDWARE: None

3.1.2 SOFTWARE: None

3.2

GOVERNMENT FURNISHED RESOURCES.

3.2.1 FACILITIES, SUPPLIES, AND SERVICES: None.

3.2.2 GOVERNMENT FURNISHED INFORMATION:

3.2.3 Documentation. Copies of necessary reference materials will be provided to the contractor. All materials will remain the property of the Government and will be returned to the QAE upon request or at the end of the Task/Delivery Order period of performance.

3.3 MATERIALS AND OTHER DIRECT COSTS (ODCs).

3.3.1 The contractor may need to purchase open market materials (such as binders, Compact Disks, student handouts, etc…) in support of these efforts. All items shall be purchased in a manner that is “most advantageous to the government.”

3.3.2 The QAE shall approve all contractor purchases costing less than $500. Any item exceeding this dollar threshold will require approval of the Contracting Officer prior to purchase.

3.3.3 Any software purchased in support of this task order shall remain property of the government. The Contractor shall be required to provide an inventory of all materials purchased or provided by the Government, which shall be referred to as "Government Furnished Property." The contractor shall provide an itemized listing of the materials purchased. This listing shall be provided at the task order ending period of performance.

4.0 GENERAL INFORMATION.

4.1 SECURITY. Provisions outlined in the basic DD 254 apply to this task order. TS/SCI clearance will be required. SCI billets will be available.

4.1.1 Access to Government Property and Facilities: The contractor will be allowed non-escorted access to Government buildings on Peterson AFB and other sites consistent with Task requirements. Access to Government facilities, documents, and systems shall be in accordance with the basic award DD254. Occasional access to the SIPRNET from the A6MZ facility can be arranged through the QAE. The Government will allow access to SIPRNET e-mail and approved SIPRNET Web sites.

4.2 TRAVEL. The following trips are estimated to support this task:

* Each year plan for one trip to ONE of the IP countries.

4.2.1 Any travel required to fulfill the tasks in this SOW shall be performed in accordance with FAR 31.205-46. For overseas travel, contractor personnel accompanying government travelers will be included in the Country Clearance Request IAW the Foreign Clearance Guide.

4.2.2 Task performance will require local travel (within 50 miles radius of Peterson AFB) between the contractor’s office, HQ AFSPC/A6MZ, Schreiver AFB, and Cheyenne Mountain AFB. The contractor shall fund all local travel.