Attachment L-2 MILSATCOM CSMC PWS Amendment 3.docx

HEADQUARTERS AIR FORCE SPACE COMMAND

MILITARY SATELLITE COMMUNICATIONS (MILSATCOM) MISSION CAPABILITY SERVICES

Performance Work Statement

23 September 2009

TABLE OF CONTENTS

SUPPORT

Printer configuration may change page numbers.

1.0. DESCRIPTION OF SERVICES

This Performance Work Statement (PWS) provides for various Advisory and Assistance Services (A&AS) and Non-Advisory and Assistance Services (Non-A&AS) to Headquarters Air Force Space Command (HQ AFSPC) Military Satellite Communications (MILSATCOM) Mission Capability Team. This TO will serve as a vehicle to provide further broadened technical and analytical tools, support or improve policy development, management, and administration, or improve the operation of systems supporting MILSATCOM missions. MILSATCOM also requires various forms of support during several phases of planning, programming, acquisition, and implementation cycles of various government systems that will need to complement the Government's technical expertise in accomplishing its mission. All services requested under this PWS are non-personal in nature.

1.1. Scope. In rendering the foregoing services, outputs may take the form of information, advice, opinions, alternatives, analyses, evaluations, recommendations, training and/or services to complement the Government’s technical expertise in accomplishing its mission. MILSATCOM has a continuing requirement for contracted support, both advisory and assistance services (A&AS) and non-advisory and assistance services (non-A&AS). The A&AS primarily comprises three major categories of services: Management, Operational and Professional Support Services; Studies, Analyses, and Evaluations; and Engineering and Technical Services. The non-A&AS primarily comprises two major categories of services: Information Management and Engineering Services. However, all services rendered under this TO require thorough knowledge and understanding of all facets of the MILSATCOM mission and those missions that rely on SATCOM.

1.2. Mission. The mission of AFSPC is to defend the United States through the control and exploitation of space. This is accomplished by operating space systems; providing support from space to terrestrial forces; operating ballistic missile forces as a deterrent against nuclear attack; providing assured mission capability, including ground control support for designated Department of Defense (DoD) satellites through all levels of conflict; providing warning of a space ballistic missile attack; providing the ability to protect friendly satellites and to negate enemy spacecraft; and maintaining the Intercontinental Ballistic Missile (ICBM) force, people and materiel. The mission of AFSPC includes specific responsibilities as the Air Force component of US Strategic Command (USSTRATCOM) for space and ICBM forces and as an Air Force Major Command (MAJCOM). These responsibilities are interrelated and entail specific relationships with other commands and agencies, both United States and Allied.

1.2.1. The MILSATCOM Capabilities Team was created in January 2008 to consolidate resources supporting all aspects of MILSATCOM. The team optimizes resources from multiple HQ AFSPC directorates to form one capabilities team. The MILSATCOM Capabilities Team provides operational requirements, architectures, databases, and engineering/programmatic guidance for MILSATCOM systems and operational policy and funding guidance to units and organizations supporting MILSATCOM programs/system. Specifically, the team is tasked to develop, update, document, and staff military requirements for MILSATCOM satellite systems, terminals, and supporting command and control infrastructure, support fielded operational systems, and support transition of systems from acquisition to operational use. The team also functions as the Protected Consolidated-SATCOM System Expert (C-SSE) and SATCOM System Expert (SSE) for systems assigned by US Strategic Command (USSTRATCOM) in its role as the SATCOM Operational Manager (SOM) in accordance with (IAW) the Chairman Joint Chiefs of Staff Instruction (CJCSI) 6250.01, Satellite Communications.

1.2.2. The MILSATCOM Capabilities Team currently supports the following programs:

Protected MILSATCOM Systems Milstar Advanced Extremely High Frequency (AEHF) Interim Polar Systems (IPS) Enhanced Polar Systems (EPS) Ultra High Frequency Follow-On (UFO/E/EE) Fleet EHF Package (FEP) Command Post Terminal (CPT) Family of Advanced Beyond Line-of-Sight-Terminal (FAB-T) Advanced EHF Universal System Test-Terminal (AUST-T) Command and Control System Consolidated (CCS-C) Backup Satellite Operations Center-Vandenberg (BSOC-V) Ground Essential Minimum Communication Network (GEMS) Minuteman MEECN Program (MMP) Secure Mobile Anti-Jam Reliable Tactical Terminal (SMART-T) Single Channel Anti-Jam Man-Portable Terminal (SCAMP) Navy Extremely High Frequency (EHF) Satellite Communications Program (NESP) Navy Multi-Band Terminal (NMT) Joint Tactical Radio System (JTRS) Satellite Mission Control Subsystem (SMCS) Advanced SMCS (A-SMCS) Enhanced SMCS (E-SMCS) Teleports

Wideband MILSATCOM Systems Defense Satellite Communications System (DSCS) Wideband Global SATCOM (WGS) Global Broadcast Service (GBS) Family of Advanced Beyond Line-of-Sight Terminals (FAB-T) Ground Multi-band Terminal (GMT) Defense Satellite Communications System (DSCS) Terminals Modernization Enterprise Terminal (MET) AF Wideband Enterprise Terminal (AFWET) Joint Tactical Radio System (JTRS) Command Control System – Consolidated (CCS-C) Backup Satellite Operations Center – Vandenberg (BSOC-V) DSCS III Service Life Extension Program (SLEP) Airborne Integrated Terminal Group (AITG) Teleports

Narrowband MILSATCOM Systems Ultra High Frequency Follow-On (UHF/FO) Fleet Satellite (FLTSAT) Multi User Objective System (MUOS) Follow On Terminal (FOT) Airborne Integrated Terminal Group (AITG) Joint Tactical Radio System (JTRS) Teleports

Associated current and future DoD, Civil and Commercial SATCOM Systems and systems as applicable; this includes future MILSATCOM programs in pre-planning stages.

1.3. Requirements. The contractor shall assist the Government in performing technical analyses; planning, programming, and budgeting assessments; systems security; current and future operations; technical analysis and support; and assistance in solving problematic issues and concerns experienced by requirements, development and operations communities. In rendering the foregoing services, outputs may take the form of information, advice, opinions, alternatives, analyses, evaluations, recommendations, training and/or services to complement the Government’s technical expertise in accomplishing its mission. These services provide support, assistance, advice, or training for the efficient and effective management and operation of MILSATCOM organizations, activities, programs or systems. The requirement includes assistance in the areas of Requirements, C-SSE and Operations.

1.3.1. Requirement 1: Consolidated-SATCOM System Expert (C-SSE) Support.

Period of Performance Begins 16 September 2010

1.3.1.1. Joint Task Force Global NetOps (JTF-GNO) Interface. Coordinate with staff to identify and support development of concept of operations, communications planning tool recommendations, and policies and procedures for integration of SATCOM into the Global Information Grid (GIG) at working groups.

1.3.1.2. Technical and Acquisition Working Group Support. Brief MILSATCOM Capability Team issues/concerns at multiple working groups for acquisition, technical and sustainment for development and fielding of new Protected Systems. (Approximately 24 meetings per year.) (CDRLS: 0006, 0007, 0030)

1.3.1.3. Protected Systems Technical Support. Provide technical assessments, XDR and future waveforms data collection, data configuration control and MPSS and future program data base population for MILSATCOM and the 614th Space Communications Squadron with AEHF-EHF/XDRXDR/future waveforms-related technical issues including XDR and future waveforms SDB requirements. Support EPS and applicable system constellation deployment plans, apportionment planning/execution and XDR and future waveforms communications planning; provide technical assessments for XDR and future waveforms SDB communications requirements and technical assessments of new and changed AEHF, EPS or future system SATCOM requirements for MILSATCOM and the Operational SSE; provide technical assessments on Teleports, EPS and future systems. Populate MPSS and future system planning and operational databases for MILSATCOM and the 614th SCS. Identify XDR (including EPS)/future waveforms specific data to; identify inputs from the 614th SCS, the Defense Information Systems Agency, Terminal Program Offices (TPO), SPOs and MPSS and future system developer to XDR /future waveforms data for integration with current LDR and MDR collection and configuration control process. Populate MPSS and future system data bases with XDR EPS/future waveforms data. Develop Data Base Change Requests (DBCRs) and XDR and EPS/future waveforms configuration control process/procedures. Participate in configuration control board meetings when XDR operations are on the agenda (approximately 12 meetings annually). (CDRL: 0030)

1.3.1.4. Present XDR/future waveforms topics at Technical Interchange Meetings (TIMs) and working groups to support the identification and management of AEHF-EPS/XDRXDR/future waveforms data, SDBs and technical assessments. Provide a spreadsheet, technical report, briefing or verbal answer for operational questions or issues that may arise approximately six times per year. (CDRLS: 0006, 0030)

1.3.1.5. Protected SATCOM Roadmap. Provide updates and analysis for the Protected SATCOM Roadmap, addressing current and future (2012-2025) EHF SATCOM capabilities. Develop reports and briefing materials from analysis of Roadmap capability gaps identifying mission area impacts and recommendations for capability gap coverage. Perform quarterly reviews of schedules and interim updates to the Roadmap document. The schedule for this product is tied to programmatic changes and updates may occur on a more frequent basis. (CDRLS: 0006, 0030)

1.3.1.6. CONPLAN Development and Tracking. Produce periodic reports, studies, and briefings (approximately three of each). Develop and update a database to track Joint Strategic Capability Plan (JSCP) approved scenarios. This database will be used to develop scenarios as requested by USSTRATCOM for loading analysis and for development of AOR specific I-Plans and CONPLANS. (CDRL: 0030)

1.3.2. Requirement 2: Joint Capabilities Integration and Development System (JCIDS) Support. This requirement will be charged to Research, Development, Technology and Engineering Funds (3600).

Period of Performance Begins 1 October 2010

1.3.2.1. Requirements. Draft requirements documentation using established methodology and guidelines contained in DoD, Joint Chiefs of Staff, and AF instructions for the MILSATCOM programs identified in paragraph 1.2.2 and for future and emerging programs. Respond to changes in the CJCSI requirements documentation which require additional analysis and additional Operational Architecture products. [In-progress requirements documents adjustments needed to meet the changes to CJCSI documentation will occur approximately two to three times per month.] (CDRL: 0030)

1.3.2.1.1. Develop key performance parameters for Analysis of Alternatives (AoAs), Mission Need Statement (MNS), Concept of Operations (CONOPS), Mission Area Initial Capabilities Documents (MA ICDs), Initial Capabilities Documents (ICDs), Capability Development Documents (CDDs), Capability Production Documents (CPDs), senior leadership intent, Service & Joint requirements council memos, studies, and other efforts in support of the JCIDS or acquisition processes. (Note: Actual document titles and/or format are subject to change as directed by CJCSI revisions.) (Estimated number of documents to support MILSATCOM is: 4-AoAs; 5-ICDs; 6-CDDs; 7-CPDs, and 7-CONOPS.) (CDRL: 0030)

1.3.2.1.2. Facilitate working groups and processes leading to validation of requirement sets. (MILSATCOM will require working groups for each major program that meet quarterly at a minimum. Working groups are two to three days in duration with approximately 25 attendees per working group. Focused sub-groups are anticipated to meet weekly in support of producing JCIDS products. ) (CDRLS: 0002, 0003, 0004, 0006, 0007, 0030)

1.3.2.1.3. Maintain a comment resolution process to resolve comments within time periods specified within the Joint Capabilities Integration and Development System (JCIDS) process and address and resolve military and civil concerns generated during the requirements development process. Implement shared processes and common infrastructure toward the full implementation of the Urgent and Compelling requirements process. Extend the Urgent and Compelling Process to encompass all applicable MILSATCOM programs. (CDRL: 0030)

1.3.3. Requirement 3: Requirements Support.

Period of Performance Begins 1 October 2010

1.3.3.1. Acquisition Fielding Analysis. Evaluate MILSATCOM acquisition and fielding progress to deliver operational warfighter capability and civil services, including program schedules, funding profiles and integrated system synchronization for various satellite versions, control segment upgrades, and user equipment fielding. Participate in design reviews, configuration control processes, test and evaluation planning, transition planning, and specification development for those programs listed in 1.2.2. (Estimated number of meetings in support of this effort is four per quarter per major program (approximately 1-2 days in duration) for the term of this TO.) (CDRL: 0030)

1.3.3.2. Architecture.

1.3.3.2.1. Develop and document DoDAF and CJCSI directed architecture products for the MILSATCOM family of systems, including the space segment, control segment upgrades, and warfighter terminal and terminal equipment (approximately 10 architectures per system-level document for an estimated five systems). Both Mission-level CONOPS and System CONOPS form the basis for the architecture. All necessary and available CONOPS documents shall be provided post-TO award. (CDRL: 0030)

1.3.3.2.2. Draft specific Operational Views, Technical Views, and Systems Views required by appropriate DoD, Joint Staff, Air Force, and MAJCOM directives and policy (approximately 11 different architecture products needed per CDD and CPD produced). Provide architecture products IAW the most current DoD guidance/requirements [for example, Operational Views (OV)-1, OV-2, OV-3, OV-4, OV-5, OV-6; Systems Views (SV)-2, SV-4, SV-6, and Technical Views (TV)-1, TV-2]. Assist with completion of these architectures. Work with the program developer staff to provide clarification of OV’s as they flow into the creation of SV’s. (Changes to these architecture views and associated documentation will be ongoing based on each specific program’s place is in its developmental lifecycle. Initially, the work will be intense as operational views are created but will taper off when work transitions to OV to SV integration issues.) (CDRL: 0030)

1.3.3.3. Emerging Threats. Provide appropriate input to the requirements development process for both analytical studies and monitoring developmental and operational tests conducted by various DOD/Joint/Service organizations through evaluation of emerging threats to space-based MILSATCOM and its augmentations. (CDRL: 0030)

1.3.3.4. PPBS Support. Develop utility/effectiveness, cost benefit of various alternatives and operational concepts/controls, and other input required for capability fielding, evaluating DoD MILSATCOM planning, programming and budgeting activities identified by HHQ and warfighter organizations to ensure space-based MILSATCOM acquisition and fielding are mutually supportive or complementary to those actions. (CDRL: 0030)

1.3.3.5. Air Force SATCOM Database (SDB). Maintain Air Force SDB entries gathering MAJCOM/Agency requirements throughout the year including supported mission, type of information exchange, duty cycle, data rate, and protection and identification of redundant entries, consolidation of requirements, presentation to panels/boards, and approval receipt of the Quality Assurance Evaluator (QAE). (CDRLS: 0006, 0007, 0030)

1.3.3.6 Systems Planning, Installation, and Deployment Support for Command and Control Systems – Consolidated (CCS-C) Develop and update all required documentation, briefings and databases necessary to support the MILSATCOM Capability Team, SMC, and the 50th Space Wing with planning installation, employment, and upgrades of the CCS-C to support on-orbit satellite command and control of MILSATCOM satellites. Some deliverables and technical support areas may be required including Concept of Operations, Training Plan and Training Planning Teams, System Information Assurance, Computer Resources Lifecycle Management Plan, Test and Evaluation Master Plan, System Interoperability Studies and Full Operational Capability Plan. Timing of requirements will be entirely driven by the progression of MILSATCOM programs. (CDRL: 0030)

1.3.3.7 Technical Support for the Back-up Satellite Operations Center - Vandenberg (BSOC-V) Develop and update operational plans and designs for the BSOC-V, and provide technical input and management to upgrades and sustainment of the BSOC-V at Vandenberg Air Force Base (AFB). Develop and update Concept of Operations, Employment Plans, Training Plans, Computer-Aided Designs (CAD), and System Capability Analysis documents. Coordinate development and maintenance of the Site Activation Task Force (SATAF) at Vandenberg AFB, CA to support the MILSATCOM Capability Team and SMC in operational, systems engineering/integration, build out, sustainment, and programmatic actions necessary to implement, upgrade, and sustain applicable facets of CCS-C at AFSPC and Air Education and Training Command units located at Vandenberg AFB, CA and the Vandenberg Tracking Station where the BSOC-V is located. (CDRL: 0030)

1.3.4. Requirement 4: C-SSE System Engineering and International Partner Support. Period of Performance Begins 9 October 2010

1.3.4.1. Security Working Groups. Support security working groups for protected SATCOM systems satellite payload and bus operations, Strategic and Tactical end-user SATCOM operations, and Transmission Security (TRANSEC) and Communications Security (COMSEC) processes. Develop briefings for the Advance EHF Security Engineering working group, International Partner AEHF Security Working Group, System Security Engineering working group, “Face to Face” working groups, security working groups, security classification guide IPTs, and ad-hoc working groups on work-specific information assurance, security classification and/or crypto modernization issues. Provide input for technical discussions with US and IP working group participants. (Approximately 18 working group meetings per year.) (CDRLS: 0006, 0007, 0030)

1.3.4.2. Fencing CONOPS. Recommend and prepare inputs to the EHF Fencing CONOPS as emerging developments occur utilizing Strategic Directives and other SATCOM policy documents and SATCOM system technical documents that affect payload resource management. (Approximately one Fencing CONOPS update annually dependent upon apportionment process developments.) Provide technical reports from analysis of Fencing CONOPS information and briefings for working groups. (Approximately three reports annually.) Provide technical reports on studies and briefings of the Fencing Capabilities and Interoperations with existing and future systems, evaluation of fielding plans’ impacts of future programs to existing and planned fencing, and evaluation of operational impact to future programs related fencing concepts, dependent upon program development progress. Develop input to the Interface Control Working Group, Inter-Operability Working Group, and the Legacy Terminal Working Group. (CDRLS: 0006, 0030)

1.3.4.3. Legacy Terminal Network Transition Plan (LTNTP). Update the LTNTP and provide recommendations for directed network transition during tracking of upgraded terminal installs. Develop a proposed composite schedule for network transition through analysis of terminal fielding schedules from all service Terminal Program Offices. Provide recommendations on the LTNTP for transition working groups, the AEHF Transition Steering Committee (ATSG) and subsequent transition committees for fielding all EHF capable terminals. Provide recommendations on available dates for network transitions to EHF. Provide quarterly updates to the LTNP and technical reports or briefings of LTNTP information to working groups. (Approximately four reports annually). (CDRL: 0030)

1.3.4.4. Nuller Policies and Procedures. Provide approximately two technical reports and recommendations on potential changes to policy and/or MPSS/future systems software which will result in either modification to Nuller Policies and Procedures documentation and/or deficiency reports written against the MPSS and future systems software (approximately one update per year). Respond to emerging or urgent taskings for testing, studies, meetings, and operational SATCOM needs. Develop short notice system technical reports, test plans, analyses or briefings. Provide system engineering analysis for constellation deployment plans, terminal certification, and operational implications. Prepare routine and quick reaction technical reports, test plans, and studies in draft and final forms. (Approximately 12 quick reaction reports and studies annually.) (CDRLS: 0006, 0030)

1.3.4.5. Loading Analysis Study (LAS). Provide four LASs each year consisting of two interim reports, one final report, and supporting briefings. Depict the impact of transitioning existing Milstar networks and adding additional networks and users to the AEHF, EPS, and future systems. Determine required network resources on the uplink. Downlink and crosslink the XDR and future systems. Establish the Internet Protocol (IP)-based network configuration, incorporate survivability requirements such as scintillation and any signal interference to terminals due to the proximity of different satellite beams. Address International Partners utilization and their resource allocation in relation to US operations. Compile US warfighter requirements and assign to specific satellites based on the current USSTRATCOM satellite fielding plan or AFSPC recommended fielding plans. Address satisfaction of Thule Air Base requirements by SATCOM systems. Address recommended timeframes delineated by specific years based on the fielding of terminals. Evaluate effects of an AEHF, EPS, and future program constellation and any remaining operational Milstar or UFO-E satellites. Evaluate appropriate loading for each system for possible contingency situations and provide recommendations on Transmission Security (TRANSEC) key to channel mapping or other implemented security measures analyzing crosslink loading. Develop briefings for various forms on LASs. (CDRLS: 0006, 0030)

1.3.4.6. Endurance Mission Support. Provide briefings, studies and point papers in support of Distributive Command and Control Nodes (DC2N) development and implementation at multiple working groups supporting implementation and continuation of the Endurance Mission support as related to AEHF, EPS and other current and future MILSATCOM systems. (CDRLS: 0006, 0030)

1.3.4.7. Download and assess the current SDB database and upload technical assessments applying the latest version of SDB-MT and procedures in the SDB-MT Tool Kit and Users Manual. (CDRL: 0030)

1.3.4.8. Provide XDR EPS and future waveforms-related apportionment planning, allocation, communications planning and constellation deployment issues, including XDR/future waveforms frequency planning, fencing, crypto planning and other protected system unique payload issues. Provide recommendations to configure AEHF, EPS, and future system payloads and antennas to support both backward compatibility and XDR/future waveforms operations including placement of satellites and availability of XDR/future waveforms capable terminals and networks. Support apportionment meetings (estimated six per year): the Network Configuration Planning Meeting for finalization of net configurations and allowance of resource assignments within resource participants/partitions; Apportionment Planning Meetings; Constellation Re-Configuration Planning meetings; Readiness Reviews; Cutover Reviews and other AEHF-related meetings for apportionment cutover. Develop apportionment cutover and constellation deployment with MILSATCOM and Operational SSE. Access MPSS and future mission planning software systems to assist communications planners with XDR/future waveforms Network planning. Develop and provide reports describing meetings in support of the Joint SATCOM Panel (JSP) and meetings with XDR/future waveforms operations as significant topics of discussion. Reports shall also address any significant protected system issues discussed, resolved, and/or open for action. (Twelve JSP telecoms/meetings per year and an annual review.) (CDRLS: 0006, 0007, 0030)

1.3.4.9. Dual Operations Study. Document implications of operating both MPE and future system planning elements. Provide technical papers, briefings and mitigation plans and procedures to address various issues/concerns with working in a dual operations environment, addressing all levels of communication planning, both strategic and tactical, and all terminal types and operations. Present dual operations issues and mitigation procedures at the Operations Transition Working Group or Users Forums. (CDRLS: 0006, 0030)

1.3.4.10. Future Waveforms Education. Provide future waveforms training to system communications planners involved with planning crypto, payload tables and tactical and strategic communications networks; review existing materials and most relevant and understandable materials on new capabilities/functions provided by future waveforms. Provide the Mission Planning Element (MPE) and future system planning element with differences between system waveforms and capabilities. Provide briefing materials based on different levels of communications, payload, crypto, strategic net and tactical net planning, including screen shots of the most representative screens for each planning level from the communications planning tool. Provide an understanding of all entry fields on each screen for each planning process, who enters data for fields, and who can modify data. (CDRLS: 0006, 0030)

1.3.4.11. International Partner (IP) Certification and Accreditation (C&A). Develop C&A support for IPs applying the DoD Information Assurance Certification and Accreditation Process (DIACAP) or the DoD Information Technology Security Certification & Accreditation Process (DITSCAP). Participate in meetings related to C&A, develop IP relevant C&A documents and review, comment and coordinate on IP developed C&A. Provide a comment resolution matrix (CRM) for each document and IP Document review of IP developed C&A. (CDRLS: 0006, 0007, 0030)

1.3.4.12. Teleport Support. Monitor and track teleport implementation, and provide periodic loading analysis. Participate in CONOPS reviews to meet strategic and tactical requirements. Attend meetings and Teleport working groups. Provide omments on technical documents and CONOPS, and assist with the development of policy and procedure. (CDRL: 0006)

1.3.4.13. Additional International Partner (IP) Integration. Provide analysis addressing technical, programmatic, and diplomatic impacts on effects of adding IPs onto protected systems with mission impacts to US warfighters, security implications, and logistics and satellite resource management. (CDRL: 0030)

1.3.4.14. International Partner (IP) Concept of Support (CONSUP). Upon receipt of official international agreements, provide recommendations for the structure of the CONSUP, as overarching or specific to each system. Modify and update the CONSUP to reflect the most current design of protected systems and the new systems either as standalone documents, i.e., specific to a system, or as an overarching concept document. (CDRLS: 0006, 0030)

1.3.4.15. Coalition Network Interoperability Plan (CNIP). Upon receipt of official international agreements, develop a CNIP for each protected system as IPs are integrated into that systems operations. The IP CNIP study shall provide detailed information on conduct of operations between US forces, IP forces and other allies. Address types of networks and associated network parameters, network owners, members and types of terminals available for use, baseband equipment and settings for operations, security issues, how network members obtain resources, and interoperability procedures for Coalition forces. The IP CNIP shall provide the method for incorporating other allied forces into networks and addresses resource and terminal sources and terminal operators for allied forces when performing coalition operations. The plan shall also address support required by IPs from the Global SATCOM Support Center (GSSC), Regional SATCOM Support Centers (RSSCs) and standard operating procedures (SOPS) for operations and support and shall specify how communications planning shall be performed in support of IPs. (CDRLS: 0006, 0030)

1.3.4.16. GSSC Operating Instructions. Develop, in coordination with the GSSC IPA, operating instructions (OIs) for each protected system with the GSSC as the focal point for IP support. (CDRL: 0030)

1.3.4.17. International Planning (IP) Planning Tool Policies and Procedures. Develop, as part of the SI 714-09 and systems annexes, policies and procedures for IP use of Protected SATCOM systems, augmenting communications during operations and interfacing with UCCs and other DoD users. This portion of SI 714-09 shall be developed without redaction for US functionality. (CDRL: 0030)

1.3.4.18. International Partner (IP) Coverage Assessment. Perform coverage assessments as requested by the QAE to provide answers to the operational resource impact of IPs introduced into a protected system. Initial assessments shall address IP resource allocation loading and impact to the system of interest. (CDRL: 0030)

1.3.5. Requirement 5: International Partner System Transition. This requirement will be charged to Research, Development, Technology and Engineering Funds (3600).

Period of Performance Begins 9 October 2010

1.3.5.1. International Partner System Transition. Develop an integrated schedule section in the Protected Systems Operations Working Group (PSOWG) identifying events and deliverables to transition AEHF operations to IPs. Upon receipt of official international agreements, coordinate with the applicable MILSATCOM contractor team to develop the System Transition Management Plan (STMP) addressing IP transition to operations for those programs’ segments. Develop and maintain the IP STMP to systematically transition the IPs into operations. Attend meetings for International Partner participation in the fielding of Protected SATCOM systems (estimated six per year). Provide a comprehensive schedule of events to bring IPs into protected operations and address capabilities IPs receive and at what point in time. This schedule is used to develop a critical path and dependency depiction. Data developed shall be housed on a Government web site and integrated into existing ITTOPS and Enterprise Schedule. (CDRLS: 0006, 0007, 0030)

1.3.6. Requirement 6: Consolidated-SATCOM System Expert (C-SSE) Policies and Procedures Support.

Period of Performance Begins 30 October 2010

1.3.6.1. Database Population. Identify specific data to populate the AEHF/EPS Mission Planning Element (MPE) and future system planning systems. This includes data from the SDB Administrator, Terminal Program Offices (TPO), SPOs and MPE and future program developer awardees. Populate MPE and future system data bases with XDR data and develop XDR configuration control procedures. Identify and manage XDR data through Technical Interchange Meetings (TIMs) and working groups. (CDRLS: 0006, 0007, 0030)

1.3.6.2. Protected Systems Policies and Procedures. Provide updates and revisions to current Protected System policies, procedures and CONOPS as system operations and mission requirements evolve based on SI 714-09 Protected Satellite Communications Systems Policies and Procedures, AEHF/Milstar System Guidance, AEHF/Milstar Data Management Plan (DMP), AEHF/Milstar Resource Monitoring, AEHF/Milstar Fencing CONOPS, AEHF/Milstar Frequency Planning, AEHF/Milstar Terminal Data Flow, AEHF Coalition Network Interoperability Plan (CNIP), and the AEHF IP Concept of Support (CONSUP). Develop EPS System guidance documents and future system guidance documents as annexes to SI 714-09 as these programs proceed through development and fielding. Develop technical reports (approximately 12) for either modifications to documentation and/or deficiency reports written against the communication and mission planning software (for example: MPE). Maintain a comment resolution process to resolve comments within CONOPs and/or policy/procedure documents as policy document modifications are identified. Report to the QAE monthly or as requested. Identify recommended changes to either software and/or policy documents and evaluate effectiveness of planning tools to support CONOPS and policies. Support Protected Technical Interchange Meetings (TIMs) and working groups. (CDRL: 0030)

1.3.6.3. Integrated Test Team Support. Provide an assessment of the operational effectiveness and suitability of protected systems to support DoD’s global communications and information infrastructure and operations within International Partner countries and coalition events from Integrated Test Team events. Include the interoperability of protected systems TO deliverables with other systems in the terminal and control segments with which they must operate and shall provide information on impacts of the new protected systems added capability on communications and information infrastructures. (CDRL: 0030)

1.3.6.3.1. Evaluate and develop operational test documents for Protected SATCOM Systems for US and International Partners. Assist with testing functions as the C-SSE for the following: TEMP development, clarify and interpret requirements into testable and measurable scenarios, review the ORD/CDD and the translation of those requirements into testable activities, provide scenarios to test Concept of Operations (CONOPs) applicability, support Responsible Test Organization during all OT&E planning and execution to include facilitating development of operational test scenarios for OT&E, and participate in SPO Factory Testing, Terminal Certification testing, Joint Interoperability testing, International Partner fielding, and coalition events. (CDRL: 0030)

1.3.6.3.2. Develop tests for operational trial periods associated with each Mission Control Segment (MCS) increment deliverables utilizing test documents to include development and operational Test Plans, Test Descriptions and Test Reports and Integrated Test Team (ITT) Meetings or Working Groups (WGs), Initial Operational Capability (IOC) reviews, and other Technical Interchange Meetings (TIMs) and operational user meetings (approximately 24 meetings per year). Includes the Mission Planning Element, Protected SATCOM Missions, the JSCAP planning and allocation process, the IOC Plan and methods, and Training and familiarization of the Mission Planning Element (MPE) and future software. (CDRL: 0030)

1.3.6.3.3. Provide help desk assistance for Responsible Test Organization (RTO) events. Provide weekly summary reports of all calls received and resolution of questions/issues. Provide recommendations to WGs for development/operational test events, training curriculum and policies/procedures. Support configuration management boards in defense of Deficiency Reports (DRs), and interface with the SPO to resolve user concerns. (CDRL: 0030)

1.3.6.4. Protected SATCOM Operational Working Groups (PSOWGs).

Manage the PSOWGs (conducted at least twice a year) and Steering Committee meetings. Distribute meeting notices, track attendees, coordinate briefing materials, print briefing materials, and update status of PSOWG Action Items from previous meetings. Provide and distribute meeting minutes. Coordinate facility requirements and meeting support.

Provide monthly updates to the Integrated Transition to Operations Schedule (ITTOPS). Distribute meeting notices, track attendees, coordinate briefings, print briefing materials, update Action Item status from previous meetings, provide and distribute meeting minutes, and coordinate facility requirements and meeting support for the Protected SATCOM Working Group mandated by SI 714-4. (Protected SATCOM Working Groups held twice a year with the POWG.) (CDRLS: 0002, 0003, 0004, 0005, 0006, 0007, 0030)

1.3.6.5. Requirements Traceability Matrix/Mission Matrix. Maintain Requirements Traceability/EHF Mission Matrix databases built in Rational Pro. Compile unclassified operational requirements as documented in the Protected System ORD and CDDs, design specification requirements from system specifications, and operational requirements identified through Joint and Service level concept documents. Generate a classified database using the same data structure created for unclassified data to capture classified ORD/CDD requirements. Analyze data to identify inconsistencies and/or gaps between operational requirements, design requirements, and evolving CONOPS. Generate reports documenting traceability between ORD/CDD requirements, design requirements, and operational tasks. Attend various System Level Test Meetings. Identify changes to the Rational Pro database and/or data structures to accommodate new data types, applying CONOPS documents, design specifications, and test documents. (CDRL: 0030)

1.3.6.6. Terminal Mission Certification. Develop and support implementation of procedures to certify US developed, commercial and IP terminal that intend to operate on Protected SATCOM satellite. Address technical certification, security accreditation, and operational validation. (CDRL: 0030)

1.3.6.7. Transition Director Support. Plan, analyze, and implement activities with the MILSATCOM Capability Team Transition Director to transition a program/system from development to operations. (CDRL: 0030)

1.3.7. Requirement 7: Operations Support.

Period of Performance Begins 1 December 2010

1.3.7.1. Operations, Sustainment and Engineering Support.

1.3.7.1.1 Provide oversight/general operational and funding guidance for new space programs, both on-orbit and ground/terminal. Provide assistance with solving problematic issues and concerns experienced by management and operational communities, interfacing with National, Civil, DoD and foreign entities. Provide operations, sustainment, and engineering technical analysis and support for MILSATCOM programs/operations. (CDRL: 0030)

1.3.7.1.2. Provide engineering technical analysis and support with, point papers, briefings, and concept development documents for the optimization of MILSATCOM space systems to include Protected, Wideband, Narrowband MILSATCOM Systems, other DOD SATCOM systems and commercial SATCOM systems and attend meetings and conferences. (CDRLS: 0006, 0007, 0030)

1.3.7.1.3. Provide a quick-look report and technical analysis for aforementioned systems at monthly MILSATCOM operations conferences, monthly MILSATCOM Capability and Enterprise meetings, weekly MILSATCOM Integrated Test Team (ITT) meetings, monthly Training Planning Team (TPT) meetings, weekly Integrated Product Team (IPT) meetings, weekly Integrated Concept Team (ICT) meetings, weekly design reviews per system, monthly program management reviews (PMR) for each system, and monthly launch meetings. Approximately 80 percent of meetings may be conducted via dial-in telephone conference. (CDRLS: 0007, 0030)

1.3.7.1.4. Provide recommendations to Integrated Test Teams (ITT), test documentation development, and IOC/FOC plan development. Provide analysis, updates and recommendations for network management and satellite operations issues, and terminal and scheduling issues. Participate in quarterly Transformational Operational Transition Groups involving Milstar and Advanced EHF and future system transition (Ops issues). (CDRL: 0030)

1.3.7.1.5. Provide analysis, updates and recommendations for Mission Planning Element/ACMS, Satellite Mission Control Subsystem (SMCS) to Advanced SMCS (ASMCS) and Enhanced SMCS (ESMCS) terminal and scheduling issues. Participate in quarterly Protected Operational Transition Groups involving Milstar, Advanced EHF and EPS transition, and Ops issues. Provide IOC/FOC plans and recommendations for Protected Systems to the A3, A5 and the AFSPC/CC. (CDRL: 0030)

1.3.7.1.6. Provide annual recommendations/revisions for operational analysis of the System Operations Protection Guide (SOPG) and/or security classification guide(s) (SCG). Guides are classified up to Top Secret/SCI. (CDRL: 0030)

1.3.7.1.7. Provide weekly recommendations, changes and revisions to MILSATCOM documentation including staff packages, requirements documentation, CONOPS, Enabling Concepts, funding recommendations, impact assessments, and operational assessments. (Approximately 30 documents per week.)

1.3.7.1.8. Provide current MILSATCOM terminal analysis and data updates as part of the national program to synchronize ground/terminal segment with space segment and assist with semi-annual Air Staff review of the National Security SATCOM Systems Synchronization Roadmap (NS4R), maintenance data, and terminal capabilities. The anticipated deliverable associated with this is a large series of data workbooks in Excel format. (CDRL: 0030)

1.3.7.1.9. Compile, draft, and brief Status of Resources and Training (SORTS) to the A3 and CV. Provide SORTS Designated Operation Capability (DOC) Statement for three (3) SOPS, four (4) SOPS, 148 SOPS, 50th Operations Support Squadron (50 OSS) and any other unit assigned a MILSATCOM mission. (CDRLS: 0006, 0007, 0030)

1.3.7.1.10. Within one business day of tasking, provide draft comprehensive briefings, reports and advocacy on recommended AFSPC positions. Analyze operations impacts, assist with quick response support for MILSATCOM programs/operations, such as technical support for MILSATCOM operations, requirements development and justification, configuration control, analysis, studies, and program reviews supporting all Protected, Wideband, Narrowband, Commercial and MILSATCOM programs/systems. (CDRLS: 0006, 0030)

1.3.7.1.11. Update the Global Information Grid (GIG) Concepts Document quarterly based on MILSATCOM system changes and recommend changes to the TCA. (CDRL: 0030)

1.3.7.1.12. Update the unclassified Polar, Wideband and Protected Functional Availability Reports (FAR) annually. Attend quarterly meetings, draft reports, coordinate and staff the FAR for A3 approval NLT June 30th of each year. Discuss operational excursions with other organizations by providing gap runs. (CDRLS: 0006, 0007, 0030)

1.3.7.1.13. Provide quarterly MILSATCOM terminal operational assessments, analyses, updates and inputs for fielding and operations concerns for legacy and future MILSATCOM terminal programs. (CDRL: 0030)

1.3.7.1.14. Develop, review and develop a recommended implementation and transition planning for Protected, Wideband, Narrowband MILSATCOM Systems, other DOD SATCOM systems and military use of commercial SATCOM. (CDRL: 0030)

1.3.7.1.15. Update and staff drafts of Joint and Air Force CONOPS for current and future Protected, Wideband, and Narrowband MILSATCOM Systems, other DOD SATCOM systems, and military use of commercial SATCOM annually. (CDRL: 0030)

1.3.7.2 Program Element Monitor (PEM) Support

1.3.7.2.1. Collect and analyze inputs for resource adjustments to the Planning, Programming, Budgeting and Execution (PPBE), including Program Objective Memorandum (POM), Amended POM (APOM), Financial Plan (FinPlan) and other budget drills. This includes operational and developmental aspects of all Protected, Wideband, Transformational, Narrowband, Commercial SATCOM and MILSATCOM Terminal programs, A3M, including planning and budgeting efforts, processing with Automated Business Services System (ABSS), Resource Allocation Programming Information Decision System (RAPIDS) and Commanders Resource Integration System (CRIS). Assist the Government during PEM parades and associated activities by providing advocacy for budgetary decisions. (CDRLS: 0006, 0030)

1.3.7.2.2. Analyze obligations and expenditures, maintain forecasts, prepare reports on the status and availability of funds, and justify and prioritize unfunded requirements. Assist with development, review and recommendation of execution year funding efforts, including Unfunded Requirements (UFR), Budget Execution Review (BER) 1 & 2 and end of year fall-out funding. Provide Open Documents List (ODL) drafts to MILSATCOM quarterly and validate obligations and expenditures. (CDRL: 0030)

1.3.7.2.3. Provide analysis of budgetary relationships and develop approaches to accommodate actions under conditions of short, rapid-changing programs and budgetary deadlines. (CDRL: 0030)

1.3.7.2.4. Provide recommendations annually for development and coordination of Financial Plans (FinPlans) for MILSATCOM programs. (CDRLS: 0030, 0031)

1.3.7.2.5. Develop draft briefings, reports and advocacy on recommended positions for the MILSATCOM Program Objective Memorandum (POM) with resource adjustments for MILSATCOM Capability Team program elements and other PECs assigned/associated with the MILSATCOM enterprise. Develop draft POM options (Point Papers, Quad and supporting charts, and RAPIDS options) and other POM documentation and updates IAW the AFSPC budgetary cycle. (CDRLS: 0006, 0030)

1.3.7.2.6. Provide funding document drafts monthly, analyze operations impacts to budget cuts by Congress, AF/A8 Space Panel, C&I Panel, Logistics Panel and AFSPC/A8/CC/A5/A3. (CDRL: 0030)

1.3.7.2.7. Provide recommended statements within one (1) business day of operational impacts in response to Office of the Secretary of Defense Program Budget Decisions (PBD) and Program Decision Memorandums (PDM), and Congressional marks. (CDRL: 0030)

1.3.7.2.8. Provide inputs for the data call to the annual Air Force Capabilities Review and Risk Assessment (CRRA). Generate draft key MILSATCOM inputs identifying current and future capabilities and associated risks of MILSATCOM systems for these AF level documents. (CDRLS: 0006, 0030)

1.3.7.2.9. Provide recommended disposition of all MILSATCOM data, both electronic and paper, for MSR, FAR, CRRA, MILSATCOM briefings, CONOPS, SORTS reports, and presentations. (CDRLS: 0006, 0030)

1.3.7.2.10. Develop, staff and finalize a contractor transition plan (exit plan) to cover all aspects of this task order providing awardees with full data necessary to execute duties associated with the new position to ensure continuity for the Government if/when contractor work is discontinued. (CDRL: 0030)

1.3.8. Requirement 8: Information Assurance Support.

Period of Performance Begins 5 December 2010

1.3.8.1. SATCOM Security Architecture Analysis. Provide support for certification and accreditation of Protected SATCOM Systems. Provide recommendations for testing in support of site accreditations. Develop, maintain and update MILSATCOM security classification guides (SCG) (for example: Milstar/AEHF SCG, EPS SCG). Develop and maintain redacted SCGs for International partners in accordance with the latest DoD, AF, and HQ AFSPC information protection guidance. Review System Security Authorization Agreements (SSAAs), Interim Approval to Test, Letter of Assurances, Security Classification Guide Challenges, Engineering Change Proposals, Interim Authority to Operate and Authority to Operate security documents. Develop briefings and information papers on security issues for leadership and the protected SATCOM community. Provide comments on network architectures (planning tool and key management tool networks) and satellite architectures. (CDRLS: 0006, 0030)

1.3.8.2. Crypto Modernization. Identify crypto modernization impacts to current and future protected MILSATCOM space, terminal, and mission control systems. Develop Analyses of Alternatives and recertification requests and requirements for modernized devices. Monitor progress of VINSON Advanced Narrowband Digital Voice Terminal (ANDVT) Crypto Modernization (VACM). Interfacing with the Air Force Communications Agency (AFCA), the AF lead for crypto modernization, and the National Security Agency (NSA).