9003-0002.doc

SATCOM Systems Support

CAASETA 9003-0002

11/27/2007

HQ AFSPC

CONTRACT INFORMATION

Provide specific Satelitte Communications (SATCOM) systems related Contracted Advisory and Assistance Services and Engineering Technical Assistance to SATCOM Systems Branch of the Mission Systems Division

8283 Greensboro Drive

McLean, VA 22102-3838

(Base + 1 Opt Yrs)

STATEMENT OF WORK

SATCOM SYSTEMS SUPPORT

FOR

SATCOM SYSTEMS BRANCH HQ AFSPC/A6MZ

1 February 2006 9003-0002

1.0 DESCRIPTION OF SERVICES: The services provided by this Task Order provide specific Satellite Communications (SATCOM) systems related Contracted Advisory and Assistance Services and Engineering Technical Assistance (CAASETA) to the SATCOM Systems Branch of the Mission Systems Division, Headquarters Air Force Space Command (HQ AFSPC/A6MZ). The Advisory and Assistance Service (A&AS) requirements described in this task order falls 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 A6MZ functional mission.

1.1. ORGANIZATION BEING SUPPORTED:

HQ AFSPC/A6MZ, SATCOM Systems

150 Vandenberg St., Suite 1105

Peterson AFB, CO 80914-4630

1.2 MISSION: Satellite Communications Systems Branch (A6MZ): 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. A6MZ 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 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/A6MZ mission.

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

1.3.3 Provision of MILSATCOM network operation and configuration expertise to support the execution and establishment of MILSATCOM systems integration; and policy and control procedures supporting customers in 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 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/A6MZ 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.6 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.7 Transition of the Milstar SSE function from AFSPC/A6MZ to 14AF and the 614th SCS. This support is further defined/described within the specific requirements of this task order. The government plans a phased transition and transfer of the Milstar SSE function during Fiscal Year (FY) 06.

1.3.8 Deleted

1.4 BACKGROUND:

1.4.1 Deleted

1.4.2 Deleted

1.4.3 The AFSATCOM, SCTS and Milstar SSE responsibilities will transition to the 614 SCS effective 1 October 2005. It is the government plan to develop and implement a partial organic capability for Milstar support within 614 SCS/SSE. After 1 October 2005 contractor A&AS support for Milstar will be incrementally reduced as the contractor transitions apportionment, resource management, database support, and related actions to the Milstar SSE.

1.4.4 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, Extremely High Frequency (EHF) terminal types and missions. AEHF satellite system will provide these communication services to U.S. 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.5 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 U.S. 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.5 SERVICE REQUIREMENTS DEFINED IN THIS TASK ORDER INCLUDE THE FOLLOWING SUB-TASKS:

Options for 3, 5, and 9 will end 30 Sep 2006. Option will not be exercised on Sub-task 6 and has been deleted. Options for all other subtasks implemented will end 30 Mar 07.

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.1 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.2 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. The contractor may be requested to provide for Video Teleconferencing Capability. In addition, the contractor will provide administrative assistance (security, telephone, limited reproduction facilities, etc.) to support conduct of 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, email 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 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, 0020A, 0025, 0028, 0030, 0034A, 0034B, 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 thirty 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 Quality Assurance Evaluator (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 (in tabular and graphical format) 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 a current Technical Inventory Center (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). Each presentation shall include a small number of hard-copy (paper) handouts (less than 5 sets), in color, when colors are used to indicate a point of interest. One hard copy and one soft copy shall be delivered to the QAE. E-mail submission is desired for unclassified presentation material less than 2 Mb in size. (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 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-Out

The Government plans to transition this A&AS support to athis succeeding Task Order. The contractor shall provide continuity of support to successfully transition A&AS work described in this Task Order , avoiding unfavorable impact to the AFSPC mission. In the event that the incumbent is not awarded the succeeding task order, the contractor shall perform the following tasks:

1.5.2.1 Develop a Phase-Out-Plan (POP) for transitioning the work identified in each sub-task identified in paragraph 1.5 of this task order. The contractor’s POP shall consider timing and succeeding contractor’s planning . The POP shall be submitted to the government not later than 45 calendar days before sub-task closeout. Upon approval of the POP by the government the contractor shall implement the plan.

1.5.2.1.1 Deleted

1.5.2.1.2 Transfer of government records, data, and property. The POP shall provide for the transfer of historical records, data and government property as to coincide with the start of succeeding task order . The POP 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 TIC 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 succeeding 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, succeeding Prime and Appropriate Sub-Contractors, and the government.

1.5.2.1.4 At turnover, the succeeding 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 succeeding contractor not later than 30 days after receiving authorization from the contracting officer to perform the turnover. The succeeding contractor shall provide a receiving report to the government acknowledging receipt of all transferred material. The material shall be added to the succeeding contractor’s TIC or GFE inventory, as appropriate.

1.5.2.2 Deliverables

1.5.2.2.1 Phase-Out-Plan - Not later than 45 calendar days before Task Order closeout. (CDRL 0034D)

1.5.3 TASK 3. Milstar Master Data Base (MMDB) Maintenance.

1.5.3.1 The SSE is tasked to support the Milstar System Operational Manager (SOM) in the execution of its responsibilities, which are outlined in CJCSI 6250.01B. One of these responsibilities is to prepare the Milstar apportionment recommendation and manage the day-to-day operation of these apportioned resources. These tasks require use and management of large volumes of data that are most efficiently stored in a database. The focus of this sub-task is on performing the technical and operational analyses of user communications requirements, and on managing and maintaining this network related data in the MMDB in support of Milstar apportionment and other Milstar studies. The contractor shall develop an efficient, innovative process to maintain and update the MMDB. Maintenance efforts shall consist of:

1.5.3.1.1 Network Data Collection - The Contractor shall collect Milstar, EHF, and UHF-crossbanded requirements. The contractor shall collect network-related information from (e.g. terminal IDs, terminal activation dates, etc.) from weekly downloads of the SDB done under subtask 5, sources identified in the MMDB Data Dictionary and other authoritative sources (i.e. UCCs, Terminal Program Offices and Service Representatives). Equal emphasis shall be placed upon the collection of Milstar I low data rate (LDR), Milstar II LDR & medium data rate (MDR), UHF-only and UHF cross-banded requirement, implementation, and operations data which the MMDB is capable of storing.

1.5.3.1.2 Data Base Change Requests (DBCRs) - Where there is data that should be captured / updated in the MMDB, the Contractor shall document that data on a Database Change Request (DBCR), identify impacts to operational database(s), and submit the DBCR at the next MMDB Configuration Control Board (CCB). The Contractor shall electronically prepare all MMDB DBCR cover forms using the MMDB Configuration Management System (CMS). At the CCB, the Contractor shall present a hard copy of each DBCR with attachment. The DBCR and /or attachment shall show the difference between what the data is and what it should be and identify any operational database(s) it impacts. A read ahead “draft” copy of unclassified DBCRs shall be provided to the Primary and/or Alternate QAE prior to the CCB. Other copies of DBCRs may be requested at any time.

1.5.3.1.3 Configuration Control Board - The contractor shall be available to host and manage the MMDB Configuration Control Board (CCB) meeting to consider Database Change Requests (DBCRs). CCBs will normally be held on a bi-weekly basis. Based on the number of DBCRs being processed, the CCB may be held more or less frequently. DBCRs, System Deficiency Reports (S/DRs), and technical reports to modify the data content and/or structure of the MMDB shall be presented at the CCB for Government disposition. The Contractor shall provide to 4SOPS a hardcopy of DBCRs that impact the operational database(s). The Contractor shall provide to the QAE two hardcopies of S/DRs that impact the MMDB-to-TSDB interface. The Contractor shall provide a hardcopy of other DBCRs and/or SD/Rs (with attachments). The contractor will also provide a copy of applicable DBCRs to the ACMS database maintainer performing work udder sub-task 6 of this task order.

1.5.3.1.3.1 The Contractor shall maintain a record of DBCRs, S/DRs, 4SOPS inputs, and action items acted upon during the CCB. The record shall include a synopsis of the disposition of the DBCRs, SD/Rs, and 4SOPS inputs; record impacts to operational database(s) and MMDB utilities; and track action items. The Contractor shall update the record for each CCB and have a hardcopy available for each CCB attendee. This record shall be produced to coincide with each quarterly MMDB cycle. An electronic copy of the record shall be provided upon MMDB database delivery.

1.5.3.1.4 Reports - The Contractor shall produce and distribute standard reports after each MMDB delivery. The reports shall be prepared based on data in the MMDB. Examples of these standard reports include, but are not limited to, the COMSEC, Active Terminals, MMP Terminals, and Terminal Data Node reports. The Contractor shall prepare standard reports and distribute reports to addresses approved by the government. Most standard reports (classified and unclassified) shall be provided in a Microsoft Excel spreadsheet and/or Microsoft word format to the QAE.

1.5.3.1.5 The MMDB - The Contractor shall modify the content of the MMDB based upon CCB decisions. Upon Government approval of a data content modification (e.g., DBCR), the MMDB shall be modified. The Contractor shall institute adequate quality control procedures to ensure only Government approved data content changes are made. Configuration control of the MMDB shall be performed in accordance with the Data Management Plan for the MMDB-to-MCPTi. The Contractor shall support Government quality control checks to ensure data quality. The MMDB is operated on Centura database engine, Version 6.1.

1.5.3.1.5.1 The Contractor shall provide the modified version of the MMDB. The Contractor shall deliver the Centura database on CD to the QAE and QAE-approved users. Four (4) deliveries shall be performed during the SOW period. With the release of each MMDB, the Contractor shall produce a Software Version Description (SVD) document that shows the data changes between the old and new versions. The SVD shall be delivered to the QAE and QAE-approved users. Four (4) MMDB data changes SVD deliveries shall be performed during the SOW period.

1.5.3.1.5.1.2 Contractor shall provide an updated MMDB Database Design Description (DBDD) to include change pages to the schema and Data Dictionary when directed by the CCB. The Contractor shall distribute the DBDD to the QAE and QAE-approved users. It’s the government’s intent to limit changes to the MMDB data dictionary and schema during this SOW period.

1.5.3.1.5.1.3 In the event that the Contractor determines that there is a source better than that identified in the MMDB Data Dictionary, the Contractor shall recommend to the QAE a change to the MMDB authoritative source. Upon QAE approval the Contractor shall collect network-related information from the new authoritative source. It’s the government’s intent to limit changes to the data dictionary during this SOW period.

1.5.3.1.6 Meetings - The Contractor shall participate in meetings (e.g., Milstar Transition Working Groups, baseband working groups), or review data/documents/handouts/minutes (e.g., CJCS EAP Vol. VII) where requirement, implementation, and operational issues are significant topics of discussion. It’s anticipated that the Contractor shall need to support eight (8) meetings during the SOW period of performance. For each meeting attended, the Contractor shall provide a Memorandum for Record, in Contractor format, which describes the meeting attended and any significant issues that were discussed, resolved, and/or are open for action. An MFR is not required for meetings attended while on travel since the trip report shall cover these meetings

1.5.3.1.7 Technical Support - The Contractor shall perform technical support analyses and/or review documents/procedures/CONOPS on subjects related to MILSATCOM. The analysis and / or reviews shall be documented in a report format. It is anticipated that there will be eight (8) routine report topics requested during the task order period. The contractor shall prepare routine technical reports in draft and final forms. Reports are to be provided in soft copy.

1.5.3.1.7.1 The Contractor shall use existing data (e.g., the MMDB) to perform quick reaction analyses of similar technical issues. Normally, these analyses would be required in 24 to 72 hours. The results of the analysis shall be documented in a report. The Contractor should plan to support a maximum of ten (10) quick reaction analyses during the task order period. Reports are to be provided in soft copy.

1.5.3.1.8 MMDB Utilities and MMDB database structure - If, during network data collection, the Contractor determines that the network data warrants a change to the MMDB database structure, the Contractor shall document the recommended change on a S/DR, identify impacts to MMDB utilities, and submit the S/DR at the next MMDB CCB. The Contractor shall electronically prepare all S/DR forms using the MMDB Configuration Management System (CMS). At the CCB, the Contractor shall deliver a hard copy of each S/DR with attachment. The Contractor shall provide copies of selected S/DRs. It’s the government’s intention to limit modifications to the MMDB structure.

1.5.3.1.8.1 Upon Government approval of a structure modification (e.g., S/DR), the MMDB shall be modified. The Contractor shall institute adequate quality control procedures to ensure only Government approved data content changes are made. The Contractor shall support Government quality control checks to ensure data quality.

1.5.3.1.8.2 To service and modify the MMDB, the Contractor shall execute and modify the current versions of the MMDB Data Management Utilities (i.e., MMDB Data Configuration Software (MDCS), DIFF, DBUP, and UNLINKED). Any changes to the utility software shall be recorded in Software Deficiency Reports (S/DRs) and presented to the CCB. It’s the government’s intention to not modify the current Data Management Utilities unless absolutely necessary. The Contractor shall develop an emergency update to utility software in the event a critical error is discovered that prevents timely completion of this SOW. It’s anticipated that there would be up to two (2) emergency updates (total) for the MMDB Data Management Utilities. The Contractor and the QAE will mutually agree upon the utilities to be updated and the schedule for updates. In developing each utility software update, the Contractor shall utilize the MMDB system tables to the maximum extent possible. By doing this, future software maintenance should be minimized since the software should dynamically adapt to MMDB data structure changes. This will also provide greater configuration control and higher productivity from a data entry perspective.

1.5.3.1.9 MMDB – MCPT-i Interfaces - The Contractor shall review the current configuration control process for data in the MMDB (to include the interface with the MCPTi operational database) which is documented in the MMDB-MCPTi Data Management Plan. Where improvements to the configuration control process can be made, the Contractor shall provide recommendations to the QAE. The Contractor shall document these recommendations in a technical report. It’s the government’s intention limit any changes to the MMDB-MCPT-i Data Management Plan.

1.5.3.1.10 Quick Reaction Studies, Document Reviews, Engineering and Technical Support Tasks Services - HQ AFSPC/A6MZ requires quick-reaction studies, technical document reviews, and technical ad-hoc support tasks during the period of performance. Response to quick reaction studies, reviews and technical reporting requirements frequently require action by the Contractor within 24 hours. The Government estimates that no more than 8 Quick Reaction tasks may be required during the period of performance. This task requires the Contractor to provide a quick response to meet the needs of the Government such as providing technical and administrative support of conferences and meetings. The Government estimate is for 8 meetings. Rather than create a separate SOW for each situation this task will be used to support those unforeseen needs and provide the cross flow necessary to satisfy Government requirements.

1.5.3.1.11 Orientation of 614 SCS Organic Personnel - 614th SCS personnel may accompany contractor personnel during the execution of this sub-task. The Contractor will be prepared to explain process flow and deliverable creation to 614 SCS personnel. Government personnel will not interfere with normal operations and will largely consist of government personnel "shadowing" contractors as they execute work under this sub-task. No deliverables are associated with this item

1.5.3.2 Deliverables

1.5.3.2.1 Final Configuration Control Board Record (CCB) - A soft copy of the final CCB record for the database maintenance period will be delivered to the QAEs with each MMDB delivery. Four (4) deliveries shall be performed during the SOW period. (CDRL 0009B)

1.5.3.2.2 Milstar Master Database (MMDB) – The contractor shall provide the modified version of the MMDB. The contractor shall deliver the database on the appropriate number of CDs in Centura to the QAE and approved users. Four (4) deliveries shall be performed during the SOW period. (CDRL 0020A)

1.5.3.2.3 Technical Reports/ADHOC Deliverables - The contractor shall prepare routine and quick reaction technical reports in draft and final forms. Typically one soft copy will be required. Most reports will be provided in Microsoft Excel spreadsheet or Microsoft Word formats and forwarded to the Primary and Alternate QAE and other addresses provided by the QAE (via NIPRNET or SIPRNET as appropriate). Standard routine reports are due no later than 5 working days after delivery of the MMDB. Government estimates up to 8 Quick reaction reports and ADHOC deliverables. (CDRL 0036A)

1.5.3.2.4 Comments to Documents - Due 3 to 7 workdays after receipt or unless otherwise directed by the QAE. Contractor to deliver to QAE and QAE-approved distribution. (CDRL 0034A)

1.5.3.2.5 MMDB Database Design Description Document (DBDD) - Database Design Description (DBDD). The contractor shall provide an updated DBDD to include change pages to Data Dictionary and schema when directed by the CCB. The contractor shall type modifications to the MMDB Data Dictionary. Up to two deliveries shall be performed during the task order period. The contractor shall distribute the DBDD to the QAEs and approved users. NOTE: For the purposes of this task order, a DBDD consists only of a Data Dictionary and schema. (CDRL 0020A)

1.5.3.2.6 MMDB Software Version Description Document (SVD) - Software Version Description (SVD) with each delivery of the MMDB. (CDRL 0025)

1.5.3.2.7 Configuration Management System (CMS) Software, Utility Software, Utility Software Source Code - The contractor shall provide the modified version of each application (executable). Up to two (total) emergency deliveries shall be performed during the SOW period. (CDRL 0025)

1.5.3.2.8 Utility Software SVD – Due with the delivery of Utility software. (CDRL 0025)

1.5.3.2.9 Data Management Plan updates - The contractor shall produce a document revision in draft and final forms. Draft and final documents are to be provided in hard copy (2 each) and soft copy (2 each). Data Management Plan for the MMDB and TSDB It’s anticipated that there will be one revision delivered during this SOW period. (CDRL 0034B)

1.5.3.2.10 Presentation Material – Government estimates up to 4. Contractor to deliver to QAE and QAE-approved distribution. (CDRL 0008)

1.5.3.2.11 Meeting Minutes & Trip Report MFRs - For each meeting attended, the contractor shall provide a Memorandum for Record, in contractor format, which describes the meeting attended and any significant issues that were discussed, resolved, and/or are open for action. One soft copy is sufficient. An MFR is not required for meetings attended while on travel since the trip report will cover these meetings. Memoranda for Record shall be delivered NLT five (5) working days after completion of meeting. (CDRL 0009B)

1.5.4 DELETED A6MZ

1.5.5 TASK 5 – SATCOM Data Base (SDB) Technical Assessments

1.5.5.1 Technical Assessments for SDB Requirements Services. Current and future SATCOM requirements, regardless of their satisfaction on DOD-owned, allied or commercial satellites, must be recorded in the SDB. These requirements support the effective planning and operational use of current SATCOM assets, as well as the architectural development of future SATCOM capabilities, programming and budgeting decisions and acquisition program decisions. CJCSI 6250.01B stipulates that the Joint Staff / J6 conducts the requirement review and approval process. During the requirement review process, USSTRATCOM as the Satellite Operational Manager (SOM), performs an operational assessment and AFSPC/A6MZ as the Consolidated Protected and AEHF Satellite System Expert (SSE), and 614SCS/SCZ as the Milstar SSE, perform a technical assessment of the requirements.

1.5.5.1.1 The Contractor shall perform technical assessments for Milstar-related and AEHF SDB communications requirements. IAW CJCSI 6250.01, SOM direction, and DISA procedures, technical assessments of new and changed SATCOM requirements shall be conducted on a periodic basis. Technical assessments shall be prepared for SSE and SOM review prior to Joint SATCOM Panel (JSP) action. For EHF and/or UHF crossbanded requirements, the initial analysis shall determine whether Milstar or AEHF is the appropriate system to support the requirements. When it is determined that Milstar or AEHF is appropriate, these assessments shall, as a minimum, provide a draft technical feasibility and operational feasibility input. Technical Feasibility Assessments shall be prepared in a Contractor format that addresses the items required in a SSE / SOM Input for an SDB requirement detailed report. After SSE and SOM review, these assessments shall be sent to DISA via the TMS-C toolkit. The SSE is also required to do tech assessments on future systems to include, AEHF strategic and tactical networks, Teleports, and TSAT.

1.5.5.1.2 The contractor shall evaluate the procedures for evaluating and coordinating technical assessments and provide recommendations for improving the SDB process. In most cases, technical assessments are submitted by users with missing data and inaccuracies. The reviewer is required to assess it, send it back to the JSP, the JSP in turn sends requirement back to user for corrections and clarifications. The user then resubmits to the JSP, the JSP forwards it back to the reviewer to re-evaluate the requirement. In several instances, the process repeats itself again when the user still didn’t provide all of the data and clarifications requested in the initial review. The solutions could include recommended changes to the SDB process, and/or a more user friendly and interactive TMS-C tool kit. The TMS-C tool kit will be web based in the near future. An up front process where UCCs/users could be provided a template to fill out prior to the official SDB entry should also be considered. An interactive template, which could be web based, could be filled out and sent directly to the reviewer prior to SDB submittal. This may streamline and shorten the current process. The contractor shall provide the government a recommended solution to be presented to the JSP, SOM and DISA for possible approval and implementation.

1.5.5.1.3 In addition to SIPRNET access, the contractor must obtain the appropriate TMS-C access. The new TMS-C 4.0 will require Internet Explorer 6.0 or Netscape 7.0 or greater to operate. This task will require the contractor to download the current database and upload tech assessments. The contractor should be familiar with both search capabilities and report generation. The contractor should be familiar with the TMS-C Software Documentation Discrepancy Report and be able to submit a TMS-C Toolkit Discrepancy / Enhancement Report(s), as necessary. The TMS-C tool kit will become web based in the near future. The Contractor shall support JSP telecoms and the JSP Annual Review.

1.5.5.1.4 The Contractor shall participate in meetings in support of the JSP and in meetings where TMS-C operations are significant topics of discussion. There are anticipated to be twelve (12) JSP telecoms/meetings per year and an Annual Review. For each meeting attended, the Contractor shall provide a Memorandum for Record, in Contractor format, which describes the meeting attended and any significant issues that were discussed, resolved, and / or are open for action. A Trip Report is required for any travel. An MFR is not required for meetings attended while on travel since the trip report shall cover these meetings. Work in support of this task may require travel to Omaha, NE and/or Washington D.C for further discussions on the SSE technical assessment roles and SDB/JSP processes. Maximum number of trips: 4 trips, 3 days each

1.5.5.1.5 During the period of performance, there may arise operational questions or issues that require the contractor to provide a spreadsheet, technical report or verbal answer. We project twenty (20) issues that may arise. On average these issues require approximately two (2) hours per activity.

1.5.5.1.6 Orientation of 614th SCS Organic Personnel. 614th SCS personnel may accompany contractor personnel during the execution of this sub-task. The Contractor will be prepared to explain process flow and deliverable creation to 614 SCS personnel. Government personnel will not interfere with normal operations and will largely consist of government personnel "shadowing" contractors as they execute work under this sub-task. No deliverables are associated with this item

1.5.5.2 DELIVERABLES:

1.5.5.2.1 Technical assessments – Inputs to be downloaded weekly. Completed assessments to be delivered weekly. (CDRL 0037).

1.5.5.2.2 Technical Management Work Plan - Recommendation to improve the tech assessment process – Delivered within 180 days of task start. (CDRL 0034B)

1.5.5.2.3 Trip Reports – Government estimates up to 4. (CDRL 0009A)

1.5.5.2.4 Presentation Materials –Government estimates up to 4. (CDRL 0008)

1.5.5.2.5 Meeting Minutes – Government estimates up to 4. (CDRL 0009A)

1.5.5.2.6 Technical reports – Up to twenty (20) technical reports requiring on average 2 hours per response. (CDRL 0036A)

1.5.6 DELETED A6MZ

1.5.7 TASK 7 - MMDB/ACMS/MCPT-I Data Transition to Advanced Mission Planning Element (MPE)

1.5.7.1 The contractor shall support the AEHF SSE in transitioning data resident in the Milstar Master Database (MMDB), ACMS Long Term Planning (LTP) Scenario, and MCPT-I into the AEHF Mission Planning Element (MPE). To verify effective data transition, the contractor shall support MPE testing as it relates to data translation/transition issues. This support could include but is not limited to reviewing planning tool reports, test plans, and evaluation criteria. The effort shall include the following:

1.5.7.1.2 Comprehensive review of documentation and planning schedules to be provided by MILSATCOM Joint Program Office. These documents will identify the process to transfer the data sets from the MMDB, ACMS, and MCPT-i databases into the data structure of the AEHF MPE. The contractor shall review these documents for completeness, efficiency, control and maintenance of data transfer. The contractor shall provide comments to these documents in a Comment Resolution Matrix format to the QAE. Review of documentation expected to occur two (2) times. Review of schedule expected to occur monthly as program requirements dictate schedule changes.

1.5.7.1.3 Participation in the work effort to perform data transition as documented in an MJPO/AFSPC Memorandum of Understanding (MOU). This document will identify roles and responsibilities for data transition. Work effort is expected to be periodic as MJPO developer completes specific tasks yet to be defined. As a minimum, a quality check of data transitioned to the AEHF MPE is expected to occur monthly throughout the period of performance of this Task Order.

1.5.7.1.4 Participation at working group meetings to discuss details of data transition, as well as quality assurance checks once data is transitioned. This may include preparing and presenting briefings identifying work status, progress, issues, or concerns associated with the data transition effort.

1.5.7.1.5 To perform this task, the contractor must be thoroughly familiar with the MMDB, ACMS and MCPT-I data structures and data content.

1.5.7.1.6 Work in support of this transition may require travel to Sunnyvale, CA, Los Angeles, CA, and Gaithersburg MD or Valley Forge PA, Lockheed Martin site. Maximum number of trips: 4 trips, 3 days each.

1.5.7.2 DELIVERABLES:

1.5.7.2.1 Provide comments to database transition plans in form of Comment Resolution Matrix (CRM). Deliver CRM 30 days after receipt of transition plan documents. Government estimates 4 CRMs required. (CDRL 0034A)

1.5.7.2.2 Presentation Material. Government estimates up to 4. (CDRL 0008)

1.5.7.2.3 Working Group Minutes. Government estimates up to 12. (CDRL 0009A)

1.5.7.2.4 Deleted

1.5.7.2.5 Trip Reports. Government estimates up to 4. (CDRL 0009A)

1.5.8 TASK 8 - Legacy System to AEHF Network Transition Plan

1.5.8.1 The contractor shall support the development of an AEHF network transition plan. The functions include, but are not limited to, interfacing with the legacy satellite communications users to adequately understand their requirements and system analysis to evaluate the interoperability of the new AEHF architecture. The Legacy System to AEHF Transition Plan (LSATP) will require evaluation of current satellite communications systems for the upgrade or modification needed to meet the AEHF architecture. A method to store this data has been developed and is needed to be maintained under this task. This will require a broad range of system knowledge and terminal specific information in order to advise and recommend actions to support the transition plan development. In the same manner, provide assistance for technical support for AEHF fielding.

1.5.8.1.1 The method to store the data mentioned above is a software tool called the Network Information Management Tool (NIM-T). The NIM-T must be maintained by the contractor. It is an ACCESS database that combines the Milstar Apportionment Reports (MAR), the Satellite Database (SDB) and the Milstar Master Database (MMDB). It enables the user to view current and future network requirements with the actual terminal information. It incorporates MS Project that takes a user developed “ideal terminal installation schedule” and builds a network activation schedule based on the composite terminal installs. It also provides a visual representation of possible satellite locations and the known terminal locations.

1.5.8.1.2 The contractor's effort shall include the following:

1.5.8.1.2.1 Updating the “ideal terminal installation schedule” GANTT chart to highlight critical paths for transition. Provide the GANTT charts to the QAE on a quarterly basis, or sooner if any program milestones change significantly.

1.5.8.1.2.2 Maintain the legacy satellite communications system transition database known as the NIM-T. Updates to this database will occur as soon as any new and significant information is received from; Terminal Programs offices, SDB updates; MMDB updates, etc.

1.5.8.1.2.3 Maintain the existing “Legacy System to AEHF Transition Plan” and developing updates as necessary to maintain the current terminal development schedule to include the Army, Navy and AF terminals.

1.5.8.1.3 The AEHF transition plan and planning tool shall, as a minimum, establish a "baseline" schedule using the above information.

1.5.8.1.4 The primary purpose of the transition plan is to address the transition of strategic networks, provide options which prioritize networks and users, identify dependencies required to affect the transition, and include a milestone schedule to transition legacy systems to the AEHF system. The plan and NIM-T, shall also allow for the tracking of tactical networks as deemed necessary by the SSE and Unified Combatant Commanders (UCCs). The intent of this plan is to provide a prioritized, organized, and manageable approach to transition the tactical, strategic and national networks and users to the AEHF system.

1.5.8.1.5 The contractor shall participate in the Operational Transition Group (OTG) Working Group and it's subcommittees. This group meets at least monthly in a teleconference, and semi-annually 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 may be required to prepare briefing materials to support meeting agenda.

1.5.8.1.6 The Contractor shall also prepare a Tactics, Technique and Procedures (TTP) document on AEHF Nuller operations in support of tactical network transitions to AEHF. This document will provide guidance on the utilization of the AEHF communication resources known as the High Resolution Coverage Area, commonly called the Nuller, to Unified Combatant Commanders (UCC) and other users. Effort may require four trips total to either Los Angeles CA or Gaithersburg MA.

1.5.8.1.6.1 The contractor will work with the EHF communication planning community to evaluate the current Milstar Nuller operations for the tactical community. The contractor will explore, evaluate, and incorporate these lessons learned into the AEHF Nuller TTP document. The contractor will work with the AEHF satellite developer and the Mission Planning Element developer to ensure that the procedures developed will coincide with the equipment operation. The contractor will assist the government in the determination of the MPE tool adequacy in the Nuller area to ensure that the MPE provides the information that the Comm. Planners and warfighter needs. The contractor will deliver the document in three phases; a first draft, a final draft, and a final document. The contractor will send the first and final drafts out for community review, collect comments and generate a comment resolution matrix.

1.5.8.1.6.2 The document will include but is not limited to the following concepts; a documented list of existing limitations on Milstar, if any, and the methods to overcome those limitations. Specific procedures will be developed to ensure optimum operations on the Nullers. The document will offer procedures for quickly eliminating or resolving the effects of enemy or friendly jammers.

1.5.8.1.6.3 The contractor will develop and include functional and process diagrams in the document and reporting processes in the event of abnormal operations, friendly jammer or enemy jammer activities. The contractor should be capable of advising the government on the proper testing of the nuller capability in an operational scenario. The operational scenarios should demonstrate the success of the nuller to defeat an enemy jammer while maintaining communications. The contractor should suggest adequate entrance and exit criteria for the scenario. The contractor should be capable of interfacing with the Army Test and Evaluation Command and the Air Force Operational Test and Evaluation Command.

1.5.8.2 Deliverables

1.5.8.2.1 Technical Report - Provide a quarterly GANTT Chart report of all changes made to the NIM-T identified by all input sources, i.e. SDB, MAR updates, terminal program schedule changes, etc. (CDRL 0034B)

1.5.8.2.2 Technical Report - Provide a report within 3-5 working days of any significant changes to network transition planning that result from inputs from SDB, MAR updates, terminal or AEHF program changes. Government estimates up to 4. (CDRL 0034B)

1.5.8.2.3 Interim (DRAFT) deliverables of Legacy System to AEHF Transition Plan that incorporate the terminal schedules - Deliver bi-annually and if any significant changes to network transition planning changes occur. (CDRL 0034B)

1.5.8.2.4 Compile comments to Legacy System to AEHF Transition Plan and prepare a Comments Resolution Matrix (CRM). Deliver CRM 30 days after suspense for review of document. (CDRL 0034A)