9001-0003.doc

HQ AFSPC

CONTRACT INFORMATION

SATCOM SYSTEMS BRANCH

745 Space Center Dr

Colorado Springs, CO 80915

(5 Mo + 1 Opt Yr)

STATEMENT OF WORK

SATCOM SYSTEMS POLICIES AND TACTICS, TECHNIQUES AND PROCEDURES (TT&P)

FOR

SATCOM SYSTEMS BRANCH HQ AFSPC/LCOZ

21 July 2005

REVISION 01

9001-0003

1.0 DESCRIPTION OF SERVICES: The services provided by this Task Order provide specific Satellite Communications (SATCOM) systems related Contract Advisory and Assistance Services and Engineering and Technical Assistance (CAASETA) to the SATCOM Systems Branch of the Mission Systems Division, Headquarters Air Force Space Command (HQ AFSPC/LCOZ). The Advisory and Assistance Service (A&AS) requirements described in this task order fall into one or more of the following CASSETA categories: Management and Professional Services, Studies, Analyses and Evaluations, or Engineering and Technical Services. All services requested under this task order are non-personal in nature. This task order supports the LCOZ functional mission and is generated through the Contracting Officer (CO).

1.1. ORGANIZATION BEING SUPPORTED:

HQ AFSPC/LCOZ, SATCOM Systems

150 Vandenberg St., Suite 1105

Peterson AFB, CO 80914-4630

1.2 MISSION: Satellite Communications Systems Branch (LCOZ): Functions as the SATCOM System Expert (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. LCOZ mission responsibilities include the following:

1.2.1 SSE for assigned Military SATCOM (MILSATCOM) systems, specifically the Milstar, Single Channel Transponder System (SCTS), Air Force Satellite Communications System (AFSATCOM), and Advanced Extremely High Frequency (AEHF) SATCOM systems

1.2.2 Transition of AFSATCOM, SCTS, and Milstar SSE mission responsibilities to the 614th Space Communications Squadron (SCS) (14th AF) effective 1 October 2005.

1.2.3 Support to the SOM in accordance with CJCSI 6250.01 and USSTRATCOM Strategic Command Directive for SATCOM System Experts, and execution of SOM delegated tasks with regard to the above systems

1.2.4 Critical database management of SATCOM resources supporting wartime contingency operations for the SOM, Joint Staff, and Unified Combatant Commanders (UCCs).

1.2.5 Allocation of satellite communications capacity and usage resources, to ensure the President, UCCs and deployed forces have access to survivable, reliable worldwide communications.

1.2.6 Provision of 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.2.7 Participation in mission area planning to address SATCOM system issues

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

1.3 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.3.1 Operation and maintenance of existing legacy SATCOM Systems, migration of SATCOM services from legacy systems to AEHF and evolving Extremely High Frequency (EHF) satellite and terminal systems, including those systems impacted by the Joint Tactical Radio System (JTRS) program and within the context of the HQ AFSPC/LCOZ mission.

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

1.3.3 Provision of Military Satellite Communications (MILSATCOM) network operation and configuration expertise to support the execution and establishment of MILSATCOM 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.3.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 MILSATCOM 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.3.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 IP data.

1.3.6 SATCOM resource allocation and operations planning for Milstar, AEHF, evolving EHF systems, satellite terminals, and their associated systems and technologies. Support also includes planning, integrating, configuration, and operational management/optimization of EHF SATCOM systems within the organizational framework of HQ AFSPC/LCOZ and appropriate 14AF 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.3.7 Development and implementation of technical solutions as required by the government for the day-to-day and long-range operations management and planning of MILSATCOM systems. 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.3.8 Transition of the AEHF system into full operations through support of the AEHF Operational 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 OTG supports the transition of the full end-to-end system to achieve Initial Operational Capability (IOC) and Full Function Capability (FCC)

1.3.9 Transition of SATCOM system related contract Advisory and Assistance Services (A&AS) from incumbent contractors to the successful CAASETA vendor and as further defined/described within the specific requirements and scope of this task order. The Government expects that the transition of existing SATCOM System related A&AS services will commence 30 days prior to their expiration. Expiration dates for existing services are listed in paragraph 1.5. The transition period will optimally be 30 days, but may be reduced depending on award date of this task order and expiration of existing services.

1.4 BACKGROUND:

1.4.1 Some existing Milstar and EHF A&AS Task Orders performed by others will incrementally transition to CAASETA.. The government expects that all contractor A&AS support for HQ AFSPC/LCOZ will be complete by July 2005 or transitioned to CAASETA.

1.4.2 The AEHF satellite system will enable worldwide assured access and interoperability amongst warfighters of Service Commanders, service, or agency with the capability to communicate with each other within various tactical networks and the Defense Information System Network (DISN) regardless of their different needs, equipment, EHF terminal types and missions. AEHF satellite system will provide these communication services to US strategic and tactical forces during all levels of conflict and across a spectrum of mission areas that includes land, air and naval warfare; special operations; strategic nuclear operations; strategic defense; theater missile defense; space operations; and intelligence.

1.4.3 AEHF backward compatibility and interoperability with the Milstar satellite crosslinks and Milstar terminals will enable the formation of an integrated EHF System. In addition to US forces, the AEHF system will be available to International Partner (IP) and coalition forces. Even though the system is integrated, the IP and coalition users will not have access to the legacy Milstar services in the combined Milstar/AEHF system.

1.4.4 The Transformational Communications Architecture (TCA) was initiated to transform future satellite communications by combining National Reconnaissance Office (NRO) Relay, National Aeronautics and Space Administration (NASA) Tracking and Data Relay Satellite System (TDRSS) and DoD MILSATCOM AEHF and Advanced Wideband System (AWS) systems, using advanced laser communications technology to satisfy future national Intelligence, Surveillance and Reconnaissance (ISR) relay, Airborne ISR (AISR), and MILSATCOM forecasted needs. Since the legacy AEHF Extended Data Rate (XDR) waveform will be implemented through the TSAT to provide continuity of service and provide backward compatibility with legacy systems/terminals, it is expected that Transformational Communications (TC) systems will be made available to IP and coalition forces. This shared use of resources and must be considered in our planning.

1.5 SERVICE REQUIREMENTS DEFINED IN THIS TASK ORDER INCLUDE THE FOLLOWING SUB-TASKS:

Expiration date for incumbents Period of Performance or Sub-Task start date for new tasks is indicated below. The Government reserves the option to adjust the Period of Performance for any sub-task.

Task 1. Project Management and Administration (upon award) Task 2. Phase-In (New Requirement Initially upon award, then incrementally- 30 days Prior to Expiration of POP for Existing Task Orders)

Task 3. AEHF System Operational Test Support (New Sub-Task–1 April 2005)

Task 4. Milstar/AEHF System Consolidated Operations Concept (SCOC) (New Sub-Task–1 April 2005)

Task 5. Milstar/AEHF System Apportionment Policies and Procedures (existing effort expires 31 March 2005)

Task 6. Requirements Traceability/EHF System Mission Matrix (existing effort expires 1 April 2005)

Task 7. AEHF Web Site (existing effort expires 20 April 2005)

Task 8. AEHF Data Management Plan (ADMP) (upon award)

Task 9. AEHF and TSAT Operations Transition Support

1.5.1 TASK 1: Project Management and Administration.

1.5.1.1 General

1.5.1.1.1 The Contractor shall develop and operate 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.

1.5.1.1.1.2 Information, program documentation, databases and software provided to the contractor during the transition and phase-in process shall be maintained in the TIC by the contractor. Where information has been provided in hard copy the contractor shall convert the information to soft copy in Microsoft Word, PDF, or database formats as appropriate.

1.5.1.1.1.3 Deliverables: The contractor shall include a monthly update to contents of the TIC in a database supplied with the Monthly Status Report.

1.5.1.1.2 Meeting/Conference Support. The Contractor shall support meetings and conferences on an as-required basis. Government estimate of this requirement is 12 meetings/conferences.

1.5.1.1.2.1 Conference Facilities. The Contractor shall make available conference facilities to support meetings as defined within the subtasks in this Task Order. The Contractor shall ensure that facilities include video projection equipment. In addition, the Contractor will provide administrative assistance (security, telephone, limited reproduction facilities, etc.) to support meetings. Meetings will be working group activities; number of meetings is not expected to exceed 12; facilities must accommodate groups of up to 50 people and the meetings could be held up to the classified SECRET level.

1.5.1.1.3 Office Automation and Network Support - The Contractor is responsible for establishing access to the Internet, e-mail accounts and all corporate network services. Contractor facilities will not be granted any special access to the “.mil” domain.

1.5.1.1.3.1 SIPRNET connectivity - The Contractor shall establish Secure Internet Protocol Network (SIPRNET) connectivity (if needed for task order performance) for personal computer (PC) based machines. The Contractor shall assure local systems are properly accredited. The Contractor shall also establish access to classified web pages on the SIPRNET as necessary to support the requirements of this task order. The Contractor shall ensure capability is established for transmission and reception of e‑mail from Government sites approved by the government as specified in the approved communications plan. The Contractor shall be responsible for the secure facility to maintain SIPRNET Access.

1.5.1.2 Deliverables:

1.5.1.2.1 Deliverables (General) - Contractor deliverable requirements shall include trip reports, meeting minutes, technical reports, studies, analysis reports, problem resolution reports, recommendation reports, and briefing materials in the performance of this task order. All deliverables are the products of on-going activities and shall become the sole property of the Government. (CDRL 0008, 0009A, 0009B, 0027, 0028, 0030, 0034A, 0034B, 0034C, 0034D, 0036A, 0036D, 0037).

1.5.1.2.1.1 Use of Existing Materials - While innovation and creativity is required, the Contractor shall normally make maximum use of deliverables produced as a result of previous contractual efforts, existing products and briefings to the extent practicable before developing new materials and briefings. The Contractor is responsible for ensuring that no copyright infringements or other such violations occur when developing products and briefings.

1.5.1.2.2 Task Assignment Plan (TAP). A TAP for each task to be performed in this Statement of Work shall be provided by the Contractor within 30 days of contract award. The TAP may be functionally consolidated and/or submitted in the contractor/s format. (CDRL 0028)

1.5.1.2.3 Monthly Status Reports (MSR). MSRs shall be submitted beginning no later than 45 days after contract award. The MSR shall then be delivered to the QAE by the 10th of each month. (CDRL 0030)

1.5.1.2.3.1 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 accepted by the government with the TOP. The project schedule will identify (flag) any new milestone dates developed as work progresses and delivery date accelerations/slippages. In addition, the Monthly Status Report shall itemize the cumulative labor hour/category and associated funding expended/remaining on each sub-task, as well as the funds expended during the respective period of performance by labor hour/category.

1.5.1.2.3.2 The MSR shall also contain an current TIC inventory listing all relevant program documentation material, software, and deliverables up to and including Secret information relating to this task order contained in the TIC.

1.5.1.2.4 Technical Information Center (TIC). The Contractor shall develop and operate 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)

1.5.1.2.5 Presentation Material. Each presentation shall be written in Powerpoint - Microsoft Office 2000 and delivered on appropriately marked zipped disk or CDROM (for large presentations). One hard copy and one soft copy shall be delivered to the Quality Assurance

Evaluator (QAE). E-mail submission is desired for unclassified presentation material less than 2 Mb in size. Government estimate is four (4). (CDRL 0008)

1.5.1.2.6 Working Group (WG) Minutes. WG meetings held within contractor facilities or at other facilities shall be documented by conference minutes. WG minutes are to be provided in draft and final forms. Draft and final minutes shall be provided in soft copy via e-mail. The

Contractor shall also distribute WG Minutes via e-mail to Government approved organizations. The Contractor shall be responsible for supporting up to 12 meetings, lasting up to three (3) days each. For meetings held within their own facilities, the Contractor shall provide a meeting room, overhead projection equipment, and administrative assistance (security, telephone, limited reproduction facilities, etc.). Meetings will be working group activities; number of meetings to be supported will not exceed 12; facilities must accommodate groups of up to 50 people; and meetings could be held up to the classified SECRET level. (CDRL 0009A)

1.5.1.2.7 Government Furnished Equipment (GFE). GFE will be incorporated into this statement of work by task order modification when GFE is transferred to contractor. All property and materials provided by the government during the performance of this task order will remain the property of the government and will be returned to the government upon QAE request or end of task order performance. The Contractor shall maintain an inventory of GFE which will also be provided to the government monthly and at end of task order performance. (CDRL 0037)

1.5.2 Task 2: Task Order Phase-In

The government plans to transition A&AS support presently provided by others, to this CAASETA Task Order. The Contractor shall provide continuity of support to successfully transition A&AS work described in this Task Order from others to the appropriate sub-tasks, avoiding unfavorable impact to the AFSPC mission. The Contractor shall perform the following tasks:

1.5.2.1 Develop a Master Phase-In-Plan (PIP) for assuming/transitioning the work identified in each sub-task identified in paragraph 1.5 of this Task Order. The Contractor’s PIP shall consider timing and incumbent contractors planning as reflected in the incumbent’s Phase-Out-Plan (POP). The PIP shall be submitted to the government not later than 10 calendar days after Task Order award. The Contractors transition team for sub-task 2 shall begin work NLT 30 days prior to expiration of the period-of-performance (POP) for incumbent contractors. Contractor’s actual performance of sub-tasks shall begin upon the expiration of incumbents POP.

1.5.2.1.1 Upon approval of the Master PIP by the government the Contractor shall implement the plan. Implementation of the PIP shall be incrementally phased to coincide with the start of each sub-task. Incremental phase-in and transition of work to this CAASETA Task Order shall begin with a Transition Team in-place, a 30 day transition period from incumbent contractors, and authorization from the Contracting Officer to begin transition of the work.

1.5.2.1.2 Transfer of government records, data, and property. The PIP shall provide for the transfer of historical records, data and government property as incrementally time phased actions to coincide with the start of each sub-task. The PIP shall contain an inventory of items approved by the government for transfer. Supporting historical data shall be identified by sub-task and shall include, but not be limited to the following actions:

Continuity of all Subtask Requirements

Transition/transfer of Government Property

Transition/transfer of Classified Information

Data Base Transition/transfer

Software Transition/transfer

1.5.2.1.3 The Contractor shall participate in joint transition meetings when the transfer of government records, data, and property shall be discussed, and issues resolved. Incumbent contractor phase-out and CAASETA contractor phase-in actions will be synchronized at the joint transition meetings and transition actions adjusted as necessary. Meetings will be scheduled according to the government approved PIP and attended by the incumbent contractor, CAASETA Prime and Appropriate Sub-Contractors, and the government.

1.5.2.1.4 At turnover, the CAASETA Contractor shall receive and inventory government records, data, and property which is in the incumbent contractor’s possession and identified for transfer. All government records, data, and property will be delivered by the incumbent contractor to the CAASETA Contractor not later than 30 days after receiving authorization from the contracting officer to perform the turnover. The CAASETA Contractor shall provide a receiving report to the government acknowledging receipt of all transferred material. The material shall be added to the TIC or GFE inventory, as appropriate.

1.5.2.2 Deliverables

1.5.2.2.1 Phase-in-Plan - Not later than 10 calendar days after Task Order award. (CDRL 0034D)

1.5.3 TASK 3 – AEHF System Operational Test Support

1.5.3.1 The Contractor shall provide support to AFSPC/LCOZ 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 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/LCOZ in the testing functions that we are involved with as the Satellite System Expert (SSE) in the following areas:

- Supports TEMP development

- Clarifies and interprets requirements into testable and measurable scenarios

- Reviews the ORD and translates those requirements into testable activities

- Provides scenarios to test Concept of Operations (CONOPs) applicability

- Supports AFOTEC during all OT&E planning and execution

- Facilitates development of operational test scenarios for OT&E

1.5.3.1.1 The performance capabilities and characteristics required of the AEHF system are identified in the Joint Requirements Oversight Council (JROC) validated AEHF Operational Requirements Document for Milestone B (ORD-II). The Key Performance Parameters (KPPs) for the AEHF system are: Coverage, Capacity, Protection, Access and Control, and Interoperability. System thresholds and objectives are also described in the ORD. Measures of Effectiveness (MOE) developed from the Critical Operational Issues (COI) as identified by AFOTEC (the lead OTA) and AFSPC (the lead user) during their operational test strategy development are contained in the Test and Evaluation Master Plan (TEMP) Section 4.

1.5.3.1.2 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 Meetings or Working Groups, Initial Operational Capability (IOC) reviews, and other Technical Interchange Meetings (TIMs) and operational user meetings. The Government expects 12 meetings during the task order POP. The Contractor will assist LCOZ in support to AFSPC/XO during the development of tests and for the operational trial periods associated with each Mission Control Segment (MCS) increment deliverables. They will support LCOZ in assisting AFOTEC with the 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 Apportionment process

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

1.5.3.1.3 In addition to the previously mentioned considerations, the Contractor should be capable of supporting LC in the certification and accreditation process. Security certification and accreditation will be integrated into the overall 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). It will occur before any sensitive or classified operational traffic is transported or handled by the AEHF 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. The Contractor should be familiar with the System Security Authorization Agreement dated 05 April 2004. They will assist or provide recommendations for future operations testing in support of the site accreditations.

1.5.3.1.4 The compilation of the previously mentioned activities is defining the Operational Trial Period (OTP) for each Mission Control Segment (MCS) Increment deliverable. Communications management is a complex task involving the analysis of apportionments and allocations, development of communications plans, execution of these plans, monitoring system performance, and management of assets in accordance with changing user requirements and operational environments. The MCS will support the communications planner, defined as one who analyzes, plans, manages, and controls assigned Milstar/AEHF assets in support of Joint and Service-unique operations. The MCS must be capable of interfacing with existing Joint equipment and systems. As an objective, the MCS must be integrated into the Joint comm management architecture. The MCS must provide the capability for the Communications Planner to support both Joint and Service-unique missions at all levels of the communications management hierarchy, from the Joint Chiefs of Staff (JCS) to the terminal operator. In support of AFOTEC, the Contractor will define the OTP based on the capabilities of the MCS increments. The results of the tests will prove the specific capabilities within that increment by defining what capabilities will be tested, the length of the test and who or what organizations will be participating in the tests. The document will define input and exit criteria with measures of effectiveness to prove the operational capability of the increment delivery. The goal is to prove the effectiveness while minimizing the impact to the user. The evaluation results of the above described efforts will be combined at the end of testing to determine the readiness of MCS for Milstar/AEHF communications planning and implementation. These tests may require that the contractor provide some level of technical support or understanding and be able to communicate those results to AFOTEC, LCOZ and the development community.

1.5.3.1.5 The Contractor shall participate in the AEHF Operational Transition Group (OTG) Working Group and its subcommittees. This group meets at least monthly in a telephone conference, and quarterly in a larger forum with the operational community. Participation may require travel to Omaha NB, Washington DC, Los Angeles CA, or Ft. Gordon GA. Contractor will be required to prepare briefing materials to support meeting agenda.

1.5.3.2 Deliverables:

1.5.3.2.1 Strawman outline of the OTP document with timelines for future increment fielding and draft actions/tests. Delivered within 30 days after task start date. (CDRL 0037).

1.5.3.2.2 Compile the technical requirements relating to the MCS capabilities into a format that facilitates a research function. An MS Access database equivalent may be a possible solution – Delivered in 90 days after task start date. (CDRL 0037).

1.5.3.2.3 Draft OTP document which addresses MCS Increment 3 deliverable within 270 days of task start. (CDRL 0037)

1.5.3.2.4 Comment Resolution Matrix for Draft Concept 15 days after community suspense for review of document. (CDRL 0034A)

1.5.3.2.5 Preliminary OTP document (30 Days after government approves the resolution of comments) (CDRL 0037)

1.5.3.2.6 Trip Reports. Government estimates four (4). (CDRL 0009A)

1.5.3.2.7 Presentation Materials Government estimates four (4). (CDRL 0008)

1.5.3.2.8 Meeting Minutes Government estimates four (4). (CDRL 0009A)

1.5.4 TASK 4 – Milstar/AEHF Systems Control and Operations Concept (SCOC)

1.5.4.1 The Contractor shall support the development of a combined Milstar/AEHF Systems Control and Operations Concept (SCOC), referred to as the M/A SCOC. This document will use the current Milstar SCOC as a starting point. The M/A SCOC will replace the Milstar SCOC in the US Strategic Command (USSTRATCOM) Department of Defense Consolidated SCOC (C-SCOC) as Appendix I to Annex G, “Individual SCOCs.” Development of the M/A SCOC will be developed in accordance with the USSTRATCOM C-SCOC Annex D, “Generic Template for a SCOC,” with additional specific requirements as described below.

1.5.4.1.1 The purpose of this SCOC is to describe the Milstar and AEHF operational concept for use, define operational capabilities, identify issues that must be addressed when considering the use of EHF communications, and to convey a clear understanding of how Unified Combatant Commanders (UCCs) will use and control the systems. The SCOC constitutes a baseline that applies to all of the users accessing the system as well as the system/service's supporting SATCOM management and control community. UCCs and users will develop supplements to the SCOC along with specific Operating Instructions (OI) and Network OIs (NOI) to address unique planning, organizational, and operational requirements. Any specific policies adopted by UCC/users must conform to those set forth in the SCOC.

1.5.4.1.2 In addition, the M/A SCOC identifies system policies and procedures for EHF communications resource management and user resource employment, as required by Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6250.01B, “Satellite Communications” and the

USSTRATCOM C-SCOC. The contractor shall also develop an annex to SCOC to address the Functional Concept for Advanced Extremely High Frequency (AEHF) resource monitoring. This document will provide guidance on troubleshooting, policing, and analysis of satellite communication resources. The Resource Monitoring Functional Concept annex will define monitoring responsibilities and capabilities for management, planning and operations organizations. The organizations involved will include the USSTRATCOM AEHF SATCOM Operational Manager (SOM), Unified Combatant Command (UCC) communication planners, Global and Regional SATCOM Support Centers (GSSC and RSSCs), and the Satellite Command and Control Centers (SC2Cs).

1.5.4.1.2.1 The contractor will work with the EHF communications planning community to evaluate the current Milstar resource monitoring process for strategic and tactical users. The contractor will explore, evaluate, and incorporate these lessons learned into the AEHF Resource Monitoring document. The contractor will work with the satellite developer to apply key AEHF concepts to resource monitoring. These concepts include Data Item Groups (DIGs), Mission Planning Element (MPE) data distribution, communications terminal control using the AEHF planning tool, and the source and distribution methods for Low Data Rate (LDR), Medium Data Rata (MDR), and Extended Data Rata (XDR) resource monitoring information. The government expects this effort may require up to three trips to Los Angeles CA or Omaha NE.

1.5.4.1.3 The Contractor must have a knowledge of strategic and tactical missions employing EHF communications, knowledge of Milstar and AEHF system capabilities, knowledge of CJCSI 6250.01B for SATCOM resource management and knowledge of current Milstar apportionment policies, procedures, and processes.

1.5.4.1.4 As a minimum, the following documents must be considered when developing a combined SCOC document: (1) EHF Communications Planning and Management CONOPS; (2) EHF Mission Matrix; (3) Milstar Systems Control and Operations Concept (MSCOC); (4) EHF Apportionment Policies and Procedures; (5) Frequency Planning CONOPS; (6) Legacy System to AEHF Transition Plan; (7) AEHF Fencing CONOPs; (8) Distributed Data Management Concept for EHF Communications Planning. The Contractor must identify the best way to include these documents into the SCOC to minimize repetition of information as well as the best way to consolidate information applicable to day to day communications management.

1.5.4.1.5 The Contractor shall participate in the AEHF Operational Transition Group (OTG) Working Group and its subcommittees. This group meets at least monthly in a telephone conference, and quarterly in a larger forum with the operational community. Participation may require travel to Omaha NB, Washington DC, Los Angeles CA, or Ft. Gordon GA. Contractor will be required to prepare briefing materials to support meeting agenda.

1.5.4.2 Deliverables:

1.5.4.2.1 Outline of EHF System Control and Operations Concept - Deliver an outline for the Milstar/AEHF SCOC within 45 days after task order implementation. (CDRL 0027)

1.5.4.2.2 First draft of the Milstar/AEHF SCOC - Deliver 220 days after task start. The draft MILSTAR/AEHF SCOC shall be reviewed by LCOZ and distributed to the community for review and comment. (CDRL 0027)

1.5.4.2.3 Compile comments from First Draft release and prepare a Comments Resolution Matrix (CRM). Deliver CRM 30 days after suspense for review of document. (CDRL 0034A)

1.5.4.2.4 Second draft of the Milstar/AEHF SCOC - Deliver 30 days after CRM resolution. (CDRL 0027)

1.5.4.2.5 Compile comments from Second Draft release and prepare a Comments Resolution Matrix (CRM). Deliver CRM 30 days after suspense for review of document. (CDRL 0034A)

1.5.4.2.6 Trip Reports. Government estimates seven (7). (CDRL 0009A)

1.5.4.2.7 Presentation Materials. Government estimates four (4). (CDRL 0008)

1.5.4.2.8 Meeting Minutes. Government estimates four (4). (CDRL 0009A)

1.5.4.2.9 Outline of Resource Monitoring Functional Concept Annex – Deliver an outline no later than 7 July 2005. (CDRL 0027)

1.5.4.2.10 First draft of the Resource Monitoring TTP Annex – Deliver first draft, consisting of a Fence Controller Resource Monitoring (RM) Functional Concept Overview, no later than 1 August 2005. This draft TTP Annex will be used in a briefing format to present Fence Controller RM to the Operations Transition Group’s August 2005 conference. (CDRL 0027)

1.5.4.2.11 Second draft of the Resource Monitoring TTP Annex – deliver second draft, encompassing the entire scope of resource monitoring for LDR, MDR and XDR waveforms, no later than 1 December 2005. (CDRL 0027)

1.5.4.2.12 Comment Resolution Matrix (CRM) for second draft release – deliver CRM 30 days after suspense for review of document. (CDRL 0034A)

1.5.4.2.13 Third draft of the Resource Monitoring TTP Annex – deliver third draft, encompassing entire scope of resource monitoring for LDR, MDR and XDR waveforms, no later than 1 February 2006 (CDRL 0027)

1.5.5 TASK 5 – Milstar/AEHF Apportionment and Cutover Policies and Procedures

1.5.5.1 The Contractor shall support the AEHF SSE in developing new apportionment policies and procedures to generate a combined Milstar/AEHF apportionment using the AEHF Mission Planning Element (MPE). The policies/procedures must consider multiple phases of constellation configurations as AEHF is launched into the Milstar constellation. This mixed constellation will be supporting war fighters who will be using a mixture of legacy (LDR/MDR only) and upgraded XDR-capable terminals. The Contactor will use the current EHF Apportionment Policies and Procedures document as an initial starting point to continue the development and refinement of AEHF Apportionment Policies and Procedures. The Contractor shall review all current Milstar apportionment policy documentation for applicability to the AEHF system. As a minimum this effort shall include the following:

1.5.5.1.1 Develop combined Milstar/AEHF Apportionment Policies and Procedures Document (this document shall become part of the combined Milstar/AEHF SCOC). Since Frequency Planning will a critical part of an AEHF apportionment, the use of frequency planning tables as part of a loading analysis study will be considered. Other AEHF functionalities such as fencing and privileged terminal tables will also be analyzed for inclusion in the document. An additional consideration for the apportionment planning for AEHF will be teleports. The Apportionment Policies and Procedures Documents must consider how to address the apportionment allocation of ports at teleport terminals. As a minimum, the following documents will be considered when developing a combined Milstar and AEHF Policies and Procedures document: (1) EHF Communications Planning and Management CONOPS; (2) EHF Mission Matrix; (3) Milstar Systems Control and Operations Concept (MSCOC); (4) EHF Apportionment Policies and Procedures; (5) Frequency Planning CONOPS; (6) Legacy System to AEHF Transition Plan; (7) AEHF Fencing CONOPs; (8) Distributed Data Management Concept for EHF Communications Planning; (9) AEHF Apportionment time line and Work Breakdown Schedules; (10) DOD Teleport Strategic Directive.

1.5.5.1.2 Continue to refine EHF/AEHF Work Breakdown Schedules (WBS) and apportionment time lines created under previous Task Orders. The Work Breakdown Schedule (WBS) is a schedule of all activities that are performed to accomplish an apportionment. The detailed WBS shows the responsible agency for an activity, agencies that accomplishes a given task, why it’s needed, what products are produced and who gets the product. It also contains any external inputs or projected predecessors and any special tools required to perform a given task. The Contractor shall continue to develop and update a timeline and identify and review processes and milestones for transition of EHF data into the AEHF MPE, and a schedule for the apportionment process to occur given new documentation and new planning tools. The Contractor shall include a review of procedures and documentation for applicability to timeline. The WBS will be produced using Microsoft Excel and the apportionment timelines will be produced in both Microsoft Project and Adobe Acrobat formats.

1.5.5.1.3 Continue working with AMPE developer to facilitate a tool review process and recommend changes regarding MPE design effort. The Contractor will become familiar with the MPE tool as it relates to generating/ distributing apportionment data bases and terminal images. The Contractor shall attend MPE Pre-operational testing, Informal Factory Familiarization (IFF), confidence demonstrations and other MPE related meetings.

1.5.5.1.4 The Contractor may be required to travel in support of this effort. Four trips to either

Gaithersburg MD and/or Los Angeles are anticipated in support of MPE developer design reviews and non-interference testing observations.

1.5.5.1.5 The Contractor shall participate in the AEHF Operational Transition Group (OTG) Working Group and it's subcommittees. This group meets at least monthly in a teleconference, and quarterly in a larger forum with the operational community. Participation may require travel to Omaha NB, Washington DC, Los Angeles CA, or Ft. Gordon GA. Contractor is required to prepare briefing materials to support meeting agenda.

1.5.5.2 Deliverables:

1.5.5.2.1 First Draft Combined Milstar/AEHF Apportionment Policies and Procedures - Deliver 45 days after Task Order implementation (CDRL 0036D)

1.5.5.2.2 Compile comments from First Draft release and prepare a Comment Resolution Matrix - Deliver15 days after community suspense for review of document. (CDRL 0034A)

1.5.5.2.3 Preliminary Draft Combined Milstar/AEHF Policies and Procedures - Deliver 30 days after CRM resolution. (CDRL 0036D)

1.5.5.2.4 Compile comments from Preliminary Draft release and prepare a Comment Resolution Matrix - Deliver 15 days after community suspense for review of document. (CDRL 0034A)

1.5.5.2.5 Revised Preliminary Combined Milstar/AEHF Policies and Procedures Document - Deliver 30 days after CRM resolution. (CDRL 0036D)

1.5.5.2.6 Technical Report - Update to EHF/AEHF WBS and apportionment timelines. Government estimates 4.

(CDRL 0034B)

1.5.5.2.7 SATCOM Document Review. AMPE tool development/testing reports. Government estimates 4. (CDRL 0036C)

1.5.5.2.8 Trip Reports. Government estimates eight (8). (CDRL 0009A)

1.5.5.2.9 Presentation Materials. Government estimates four (4). (CDRL 0008)

1.5.5.2.10 Meeting Minutes. Government estimates four (4). (CDRL 0009A)

1.5.6 TASK 6 - Requirements Traceability/EHF Mission Matrix

1.5.6.1 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 Operational Requirements Documents, 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.5.6.1.1 The Contractor will be required to analyze data entered into the databases to determine if inconsistencies and/or gaps exist between operational requirements, design requirements, and evolving CONOPS. The Contractor is required to generate reports to display information for different acquisition and operational management personnel.

1.5.6.1.2 The Contractor will be required to 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.

1.5.6.1.3 The Contractor must have knowledge of strategic and tactical missions employing EHF communications, knowledge of Milstar and AEHF system capabilities, knowledge of CJCSI 6250.01B for SATCOM resource management and knowledge of current Milstar apportionment policies, procedures, and processes.

1.5.6.1.4 The Contractor will be required to 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.

1.5.6.1.5 The Contractor shall participate in the AEHF Operational Transition Group (OTG) Working Group and its subcommittees. This group meets at least monthly in a telephone conference, and quarterly in a larger forum with the operational community. Participation may require travel to Omaha NB, Washington DC, Los Angeles CA, or Ft. Gordon GA. Contractor is required to prepare briefing materials to support meeting agenda.

1.5.6.2 Deliverables:

1.5.6.2.1 Provide reports from data base as required to support QAE requests - Deliver once a month or as needed to support program decisions. Government estimates four (4) additional to monthly delivery. (CDRL 0036D)

1.5.6.2.2 Provide document review comments to QAE - Deliver once a month to support program decisions. Government estimates four (4)additional to monthly delivery. (CDRL 0036A)

1.5.6.2.3 Trip Reports. Government estimates four (4). (CDRL 0009A)

1.5.6.2.4 Presentation Materials. Government estimates 4. (CDRL 0008)

1.5.6.2.5 Meeting Minutes. Deliver once a month or as needed to support program decisions. Government estimates four (4) additional to monthly delivery. (CDRL 0009A)

1.5.7 TASK 7 - AEHF Web Site

1.5.7.1 The Contractor shall continue support of an unclassified AEHF Web Site. The primary purpose of the website is to provide a repository of information required across the AEHF acquisition and operational communities pertinent to AEHF management and system fielding. The web site shall be updated with official documents, working group meeting agendas and minutes, Operational Transition Group (OTG) project schedules, and other government provided information necessary to educate/inform the AEHF community. The documents shall be uploaded to the site in any format, i.e. Adobe .pdf, Microsoft Office PowerPoint, Word, Excel and Microsoft Project. In addition to the document repository, a separate link shall be available to access a calendar of AEHF related meetings/telecons/events. The calendar shall be easily accessible in a Microsoft Office-like format. It shall be easily downloaded and viewed by the user. The calendar inputs should provide information on the name of the meeting, the location, the POC and the ability to attach or embed any other supporting information like the agenda, the security POC, and briefs.

1.5.7.1.1 Since the information on this website will be unclassified but For Official Use Only (FOUO), there must be a method to validate access to the website. Only approved users will be permitted to access the site with a unique user name and password. The users must be assigned a privilege level for use on the site. There will be users that will need more privileged access than others. Some users will only be allowed to view or download the documents while others may be able to upload documents, provide admin oversight, etc. All users accessing the site will be approved by the QAE or a representative. In addition, there shall be a periodic backup of the data on the site and protection of the information against hackers and viruses.

1.5.7.1.2 After the site is operational to the satisfaction of government, the Contractor will provide admin support on a weekly basis. This will include processing access requests, uploading documents, updating the calendar, site maintenance and related activities. When the site is operating satisfactorily, this should not exceed five (5) hours per week.

1.5.7.2 Deliverables

1.5.7.2.1 Security and Protection Plan - Within 15 days of contract execution, provide a methodology for site access by the users to include a privilege breakdown. The plan shall be in MS Word or PowerPoint format (or both) and will provide the procedures utilized for users’ access, how the user names and passwords will be provided and the proposed privilege levels. In addition, this plan will address the security and protection capabilities of the data on the website. This will also address where the site will be hosted and security requirements related to this. When approved, those procedures will be executed. (CDRL 0034C)

1.5.7.2.2 Website Structure - Within 30 days of contract execution, provide proposal for website construction, further details as to where it will be hosted, and initial screenshots. This deliverable will provide examples of the user access request, the method used to store and access information, the proposed calendar function and any other proposed capabilities that the contractor develops. A screenshot or working example of these capabilities can be used if available. The developer will provide initial proposals for tests that will confirm the proof of concept. The developer will provide recommendations for the admin support of the site. When the format is approved, final development will commence.

(CDRL 0034C)

1.5.7.2.3 Active Website - Within 180 days of contract execution, documents should be loaded and the calendar will be operational. Testing will occur to determine functionality. Initial users will be notified of the Uniform Resource Locators (URL) and the procedures to access the site. (CDRL 0034C)

1.5.7.2.4 Upon full deployment of the website, the Contractor will supply weekly admin support which will do the initial processing of the user access requests, addition of users to the website access list with the appropriate privilege, uploading documents, updating the calendar, maintenance to the website, and responding to user questions. (CDRL 0034C)

1.5.8 TASK 8 - AEHF Data Management Plan

1.5.8.1 The Contractor shall prepare the final version of the AEHF Data Management Plan (ADMP) using the government furnished Final Draft ADMP (November 04). Completion of this document is critical to the AEHF Mission Planning Element (MPE) design efforts as well as influencing the Milstar/AEHF System Consolidated Operations Concept (SCOC).

1.5.8.1.1 The Contractor shall work with government and AEHF contract team representatives to incorporate information to include detail on the data structure and data elements required for communications planning at…