9001-0025.doc

HQ AFSPC

CONTRACT INFORMATION

SATCOM Systems Branch

745 Space Center Dr

Colorado Springs, CO 80915

(Base + 2 Opt Yrs )

STATEMENT OF WORK

AEHF SSE Policy and CONOPS SUPPORT For SATCOM Systems Branch, HQ AFSPC/A6MZ 27 Mar 07 (Revised) 9001-0025

1.0 DESCRIPTION OF SERVICES: Contractor services are required to provide essential policy and Concept of Operations (CONOPS) support 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 the Advanced Extremely High Frequency (AEHF) Military SATCOM (MILSATCOM) system.

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 MILSATCOM 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 Migration of SATCOM services from legacy systems to the AEHF system.

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 Provision of MILSATCOM network operation and configuration expertise to support systems integration; 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 apportion system resources, analyze network requirements, and propose and implement technical solutions necessary for policy development, day-to-day and long-range operations management, and planning of MILSATCOM systems in the legacy and future EHF system environments.

1.2.5 Analysis of user missions, requirements, apportioned resources, and the capabilities of present/future systems to meet the current and planned operational requirements. The contractor shall develop operational 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. The force structure of the international/coalition users shall be considered and base line policy and planning 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 design compliance. In addition, although the basic concepts may be similar, the country participants may have special or unique requirements that may need to be addressed separately. Information for one country may not be shared with another and the contractor must protect the separation of US Only and International Partner (IP) data.

1.2.6 SATCOM resource allocation and operations planning for the AEHF system. Support also includes planning, integrating, configuration, and operational management/optimization of the AEHF system within the organizational framework of HQ AFSPC/A6MZ and other appropriate organizations. 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 AEHF operations management and planning. The functions include, but are not limited to, interfacing with the user community to adequately understand their requirements, planning resource apportionment, and system/network upgrades/transitions to meet validated requirements.

1.2.8 Transition of the AEHF system into full operations through support of the AEHF Operational Transition Group (OTG).

1.2.9 Contractor will participate in acquisition, technical, and sustainment working group meeting as needed. Contractor shall present, support, and defend A6MZ issues/concerns in lieu of government attendance. Participation at the working groups may require travel. The contractor will be expected to provide briefings for the working groups. See paragraph 4.2 for travel requirements.

1.3 SPECIFIC REQUIREMENTS:

1.3.1 DELETED

1.3.2 REQUIREMENT 1: AEHF/Milstar Policies and Procedures. This task will require the contractor to use the AEHF MPE system with draft CONOPS, policies/procedures to evaluate operational readiness of AEHF segments. As a minimum this effort shall include the review and assessment of the following documents:

- Milstar/AEHF Apportionment Policies and Procedures Document

- Milstar/AEHF Systems Control and operations Concept (SCOC)

- AEHF Data Management Plan (ADMP)

- AEHF Resource Monitoring annex to the SCOC

1.3.2.1 The contractor shall provide technical reports to the government with recommendations on changes required to policy and/or MPE software. In addition to the documents listed above, technical reports shall encompass other AEHF documents as necessary. Government approval of recommendations shall result in either modifications to documentation, and/or deficiency reports written against the MPE software. The total estimated number of technical reports is 12 per year. (CDRL 0036)

1.3.2.2 As policy document modifications are identified, the contractor shall maintain a comment resolution process the resolves comments within CONOPS and/or policy/procedure documents. Comments resolution process shall be reported to the government as required. (CDRL 0036)

1.3.2.3 Contractor access to MPE will be at A6MZ office.

1.3.3 REQUIREMENT 2: Integrated Test Team Support. The contractor shall provide support to AFSPC/A6MZ in the evaluation and development of operational test documents for the AEHF System. Multi-service Operational Test and Evaluation (MOT&E) will be conducted to obtain an assessment of the operational effectiveness and suitability of AEHF to support the DoD’s global communications and information infrastructure. The evaluation will include the interoperability of AEHF contract deliverables (AEHF satellite and new Mission Control Segment (MCS) components) with other systems in the terminal and control segments which they must operate with, and will provide information on the impacts that the added capability of AEHF will have on the communications and information infrastructures. MOT&E is an end-to-end system test. The contractor will support AFSPC/A6MZ in the testing functions that we are involved with as the SSE in the following areas:

- Supports Test and Evaluation Master Plan (TEMP) development

- Clarifies and interprets requirements into testable and measurable scenarios

- Reviews the Operation Requirement Document (ORD) and translates those requirements into testable activities

- Provides scenarios to test CONOPs applicability

- Supports Det-4 Air Force Operational Test and Evaluation Center (AFOTEC) during all OT&E planning and execution

- Facilitates development of operational test scenarios for OT&E

- SPO Factory Testing

1.3.3.1 The contractor shall provide support to AEHF SSE review of AEHF test documents to include development and operational Test Plans, Test Descriptions and Test Reports. The contractor shall attend Integrated Test Team (ITT) Meetings or Working Groups, Initial Operational Capability (IOC) reviews, and other TIMs and operational user meetings. The Government expects monthly meetings. The contractor will assist A6MZ in support to AFSPC/A3 during the development of tests and for the operational trial periods associated with each MCS increment deliverables. They will support A6MZ in assisting AFOTEC with developing Measures of Effectiveness to meet the ORD requirements. This will require that the contractor have knowledge of, but not limited to, the following:

- Knowledge of the Mission Planning Element and its purpose

- Knowledge of Milstar and AEHF Missions

- Knowledge of the EHF Apportionment process

- Knowledge of the IOC Plan and methods to overcome the limited XDR terminal fielding constraints

- MPE software training and familiarization for Milstar/AEHF SSE personnel

1.3.3.2 The contractor shall provide support services for the AEHF MPE Increment 3 and 5.1 Help Desk located with-in the A6MZ office. This support/services will include:

- Access to Help Desk personnel Monday-Friday, 0730-1630 MST. Access is either through email, website, voice mail, or direct contact within the A6MZ office.

- Weekly Summary reports of all calls received and resolution of questions/issues

- Support to Working Groups (WGs) and TIMs to provide recommendations for: development/operational test events; training curriculum; policies/procedures

- Support to configuration management boards to defend Deficiency Reports (DRs) as required

- Provide support for transition to sustainment Help Desk.

- Interface with SPO and MPE Developer to resolve user concerns

1.3.3.3 Through participation in test and transition working groups, the contractor shall develop recommended events that will support operation test/evaluation documents. These documents may be developed as part of AFSPC/A3 Operational Trial Periods (OTPs) or AFOTEC sponsored Operational Utility Evaluations (OUEs).

1.3.4 REQUIREMENT 3: AEHF Operational Working Groups

1.3.4.1 Operational Transition Group Management. The contractor shall provide non-personal services in support of the AEHF Operations Transition Group (OTG). The OTG will provide a forum for the operational community to determine what is required to ensure that the transition from Milstar to AEHF occurs smoothly, on schedule and supports warfighter needs. This user forum will focus on operational events which impact new mission capability at defined transition milestones. The contractor shall manage the OTG and Steering Committee meetings. This includes distributing meeting notice, tracking attendees, coordinating with briefers to obtain and print briefing materials, updating status of OTG Action Items from previous meetings and capturing and distributing meeting minutes. The contractor shall coordinate facility requirements and meeting support. Estimate OTGs to be conducted 2-4 times per year.

1.3.4.1.1 Operational Transition Integrated Schedule. The contractor shall provide updates to the Integrated Transition to Operations Schedule (ITTOPS). This schedule addresses the entire AEHF System, and identifies the critical paths associated with key transition events. Reviews of the ITTOPS occur monthly; updates occur as required.

1.3.4.2 The contractor shall provide non-personal services in support of the Protected SATCOM Working Group. This forum provides an opportunity for the operational community to discuss viability of current and future CONOPS, policies and procedures associated with Protected SATCOM Systems. The contractor shall manage the Protected SATCOM Working Group meetings along with 614 SCS and A6MZ personnel. This includes distributing meeting notice, tracking attendees, coordinating with briefers to obtain and print briefing materials, updating status of Action Items from previous meetings and capturing and distributing meeting minutes. The contractor shall coordinate facility requirements and meeting support for up to secret level meetings. Estimate Protected SATCOM Working Group meetings to be held twice a year in tandem with OTG.

1.3.5 REQUIREMENT 4: Requirements Traceability Matrix/Mission Matrix. The Contractor shall continue maintenance of the Requirements Traceability/EHF Mission Matrix databases that have been built in Rational Pro. These databases contain a compilation of unclassified operational requirements as documented in the Milstar and AEHF ORD, design specification requirements from AEHF system specifications, and operational requirements identified through Joint and Service level concept documents. These databases must continue as new CONOPs documents are evolved, and as new design requirements are approved for AEHF. In addition, a classified database must be generated using the same data structure created for unclassified data in order to capture classified ORD requirements.

1.3.5.1 The Contractor will analyze data entered into the databases to determine if inconsistencies and/or gaps exist between operational requirements, design requirements, and evolving CONOPS. The Contractor shall generate reports to display information for different acquisition and operational management personnel. Estimate no more than 12 per year. (CDRL 0037)

1.3.5.2 The Contractor will support the efforts of AFOTEC in development of operational test documents by generating reports that document traceability between ORD requirements, design requirements, and operational tasks. This effort will also include participation in various System Level Test Meetings. Estimate no more than 6 reports per year. (CDRL 0037)

1.3.5.3 The Contractor will review CONOPS documents, design specifications, and test documents, and provide a technical report to the QAE on changes required to be added to the Rational Pro database, and or data structure changes required to accommodate new data types. Estimate no more than 6 per year. (CDRL 0037)

1.3.6 REQUIREMENT 5: JTF-GNO Interface. The contractor shall support interaction and working group participation relating to integration of SATCOM systems and the Global Information Grid (GIG). Contractor will need to coordinate directly with Joint Task Force Global NetOps (JTF-GNO) staff to identify and support development of concept of operations, communications planning tool recommendations, and policies and procedures needed to successfully integrate SATCOM into the GIG.

1.3.7 The following table expresses anticipated relative level of effort for specific requirements as a percentage of total task order labor effort:

1.4 ADDITIONAL DELIVERABLES

1.4.1 Monthly Status Report. The contractor shall provide a Monthly Status Report (MSR). As a minimum, the MSR 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 accepted by the government with the Task Order Proposal (TOP). 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 funded, planned, and cumulative, labor hours and associated funding expended/remaining on each sub-task, as well as the labor hours and funds expended during the respective period of performance. (CDRL 0030)

1.4.2 Technical Information Center. The Contractor shall develop and maintain a Technical Information Center (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, 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 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: None

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.

A Bidder’s Library will be provided with this SOW, to include the following:

- Milstar/Advanced EHF Communications Resource Policies and Procedures

(supersedes Milstar/AEHF Apportionment Policies and Procedures Document referenced in SOW paragraph 1.3.2)

- Milstar/AEHF Systems Control and Operations Concept (SCOC)

- AEHF Data Management Plan (ADMP)

- AEHF Resource Monitoring annex to the SCOC

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.

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. 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:

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.