PWS for Mkt Research.doc

HEADQUARTERS AIR FORCE SPACE COMMAND

MILITARY SATELLITE COMMUNICATIONS (MILSATCOM) MISSION CAPABILITY SERVICES

Performance Work Statement

22 AUGUST 2008

TABLE OF CONTENTS

1.0. DESCRIPTION OF SERVICES

1.1. SCOPE

1.2. MISSION

1.3. REQUIREMENTS

1.3.1. SPACE BASED NAVIGATION SYSTEMS SERVICES

1.3.2. GLOBAL POSITIONING SYSTEM (GPS)

1.4. QUALITY PROGRAM PLAN

2.0. SERVICES SUMMARY

3.0.

GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.0 MATERIAL AND OTHER DIRECT COSTS (ODCs)

5.0. GENERAL INFORMATION

5.1.

SUPERVISION OF EMPLOYEE

5.2.

CONTRACTOR IDENTIFICATION

5.3.

CONTRACTOR/GOVERNMENT COMMUNICATION

5.4.

PRODUCT OWNERSHIP

5.5.

PROPRIETARY DATA

5.6.

DUTY HOURS

5.7.

LEGAL HOLIDAYS

5.8.

SECURITY REQUIREMENTS

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. This contract 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, and 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 contract require thorough knowledge and understanding of space vehicles and guided missiles and military and aerospace equipment and military weapons.

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 of 2008 to pull together the resources supporting all aspects of MILSATCOM from cradle-to-grave. The team synergizes resources from multiple HQ AFSPC directorates to form one capabilities team. The MILSATCOM Capabilities Team provides operational requirements, architecture, databases, and engineering/programmatic guidance for MILSATCOM systems; 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 Consolidated Protected 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 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 EHF (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)

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

Transformational MILSATCOM Systems

Transformation Communication Architecture (TCA)

Transformational Satellite Communications (TSAT)

Transformation Mission Operations System (TMOS)

Family of Advanced Beyond Line-of-Sight Terminals (FAB-T)

Joint Tactical Radio System (JTRS)

Command Control System – Consolidated (CCS-C)

Backup Satellite Operations Center – Vandenberg (BSOC-V)

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 DoD, Civil and Commercial SATCOM Systems and systems as applicable.

1.3. Requirements. The contractor shall perform technical analyses, planning, programming, budgeting, assessments, systems security current and future operations technical analysis and support, and assistance in solving problematic issues and concerns experienced by management, 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, or systems. The requirement includes support for Requirements, C-SSE and Operations.

1.3.1. Requirements Support.

1.3.1.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. Respond to changes in the CJCSI 6212.01 requirements documentation which require additional analysis and additional Operational Architecture products. [It is estimated that the in-progress requirements documents adjustments needed to meet the changes to CJCSI 6212.01 will occur approximately two (2) to three (3) times per month.]

1.3.1.1.1. Develop key performance parameters for Mission Need Statement (MNS), Operational Requirements Document (ORD), 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, and/or previous studies. (The estimated number of documents to support MILSATCOM is: 3 ICDs; 4 CDDs; 7 CPDs, and 2 CONOPS.)

1.3.1.1.2. Facilitate working groups and processes leading to validation of requirement sets. (It is estimated that MILSATCOM will require working groups at least quarterly. The lengths of the working groups are 2-3 days in length with approximately 25 attendees per working group.)

1.3.1.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 to 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.

1.3.1.2. Acquisition and Fielding Analysis. Evaluate and advise MILSATCOM on acquisition and fielding progress to deliver operational warfighter capability and civil services, including evaluation of acquisition strategy, program schedules, funding profiles and integrated system synchronization for the various satellite versions, ground control segment upgrades, and user equipment fielding. Participate in configuration control processes, test and evaluation planning, and specification development for those programs listed in 1.2.2. [The estimated number of meetings in support of this effort is four (4) meetings per quarter (approximately 1-2 days in length) for the duration of this contract.]

1.3.1.3. Architecture.

1.3.1.3.1. Develop and document a draft Operational Architecture (OA) for the MILSATCOM family of systems, including the space segment, ground control segment upgrades, and warfighter terminal and terminal equipment (this will include approximately 10 architectures per system-level document for an estimated 5 systems). Both Mission-level CONOPS and System CONOPS form the basis for the OA. All necessary CONOPS documents shall be provided post-contract award.

1.3.1.3.2. Draft specific Operational Views, Technical Views, and Systems Views required by appropriate DoD, Joint Staff, Air Force, and MAJCOM directives and policy (approximately eight (8) operational architectures are needed per CDD and CPD produced). Assist in providing additional Operational Architecture products based on the lastest changes to CJCSI6212.01 requirements [specifically Operational Views (OV)-2, OV-4, OV-5, OV-7; Systems Views (SV)-2, SV-11, and Technical View (TV)-2] and assist with completion of these architectures. (It is estimated that changes to these documents will occur weekly and then taper off to twice monthly.)

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

1.3.1.5. PPBS Support. Provide 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 is mutually supportive or complementary to those actions.

1.3.1.6. Air Force Satellite Database (SDB). Solicit inputs for supported mission, type of information exchange, duty cycle, data rate, and protection and maintain Air Force SDB gathering MAJCOM/Agency requirements throughout the year, consolidate requirements, present to panels/boards, and receive approval of the Joint SATCOM Panel (JSP).

1.3.1.7. Facilities and Supplies. MILSATCOM will provide five (5) workspaces in the Hartinger Building on Peterson AFB, to include desk space, chairs, computers connected to 21 NET, Secret Internet Protocol Router Network (SIPRNET) access, and use of telephones, copiers and fax machines. All other contractor employees shall work at contractor facilities.

1.3.1.8. Security Clearance. Access to SI/TK/B is required in accordance with the DD 254.

1.3.1.9. Travel. Contractor employees may be required to travel to various locations within the continental United States (CONUS) in performance of this contract. Estimated travel requirements are included below. All contractor travel shall be approved by the Government prior to departure. Any travel required shall be performed in accordance with FAR 31.205-46, Travel Costs.

Travel

(includes travel time)

4 for TEC 3 days

1.3.2. C-Software Systems Engineering (C-SSE) Support.

1.3.2.1. Database Population. Identify specific data to populate the AEHF/EPS Mission Planning Element (MPE), and TSAT planning system. This data is needed for planning and operational data bases and will be used with legacy systems data.

1.3.2.1.1. Identify input to data from the Space Data Base (SDB) administrator, Terminal Program Offices (TPO), SPOs and MPE and TSAT developer.

1.3.2.1.2. Populate MPE/TSAT data bases with XDR data and assist with developing XDR configuration control procedures.

1.3.2.1.3. Support identification and management of XDR data through Technical Interchange Meetings (TIMs) and working groups. (Travel is required.)

1.3.2.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. The following documents form the basis of current Protected System operations: 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); AEHF IP Concept of Support (CONSUP).

1.3.2.2.1. Develop EPS System Guidance document and TSAT System Guidance documents as annexes to SI 714-09 as these programs proceed through development and fielding.

1.3.2.2.2. Develop technical reports (approximately 12) for either modifications to documentation, and/or deficiency reports written against the MPE and TSAT software.

1.3.2.2.3. Maintain a comment resolution process to resolve comments within CONOPs and/or policy/procedure documents as policy document modifications are identified, and report to the QAE monthly basis or as requested.

1.3.2.2.4. Provide recommended changes to either software and/or policy documents, evaluating the effectiveness of planning tools to support CONOPS and policies. MILSATCOM utilizes Protected System Communication Planners as the software planning tool.

1.3.2.2.5. Support modifications to Protected SATCOM systems products at Technical Interchange Meetings (TIMs) and working groups.

1.3.2.3. Integrated Test Team Support. Integrated Test Team events will be conducted to obtain an assessment of the operational effectiveness and suitability of protected systems to support the DoD’s global communications and information infrastructure and operations within International Partner countries and coalition events. The evaluation will include the interoperability of protected systems contract deliverables with other systems in the terminal and control segments with which they must operate and will provide information on impacts of the new protected systems added capability on communications and information infrastructures.

1.3.2.3.1. Evaluate and develop operational test documents for Protected SATCOM Systems for US and International Partners. Support testing functions as the Consolidated Satellite System Expert (C-SSE) as follows: support TEMP development, clarify and interpret requirements into testable and measurable scenarios, review the ORD/CDD and translate those requirements into testable activities, provide scenarios to test Concept of Operations (CONOPs) applicability, support AFOTEC during all OT&E planning and execution, facilitate 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.

1.3.2.3.2. Assist MILSATCOM during development of tests and for the 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 during the year). This assistance includes the Mission Planning Element and TSAT, Protected SATCOM Missions, the JSCAP planning and allocation process, the IOC Plan and methods, and Training and familiarization of the MPE and TSAT software.

1.3.2.3.3. Provide support for Responsible Test Organization (RTO) events as the subject matter expert help desk. RTOs will be conducted in support of incremental software releases prior to system fielding. Support during RTOs includes providing access to the subject matter help desk personnel Monday-Friday, 0730-1630 MST via email, voice mail, or direct contact within MILSATCOM; weekly summary reports of all calls received and resolution of questions/issues; providing recommendations to WGs for development/operational test events, training curriculum and policies/procedures; support to configuration management boards to defend the Directorate of Requirements (DRs); recommendation for Help Desk framework, supported by government personnel; and an interface with SPO to resolve user concerns.

1.3.2.3.4. Develop recommended events that will support operation test/evaluation documents while participating in test and transition working groups and provide briefings for a working group level. These documents may be developed as part of HQ AFSPC Operational Trial Periods (OTPs) or AFOTEC sponsored Operational Utility Evaluations (OUEs). (Travel is required.)

1.3.2.2. Protected SATCOM Operational Working Groups (PSOWGs). The PSOWG provides a forum for the operational community to determine what is required to ensure the transition from legacy to future protected systems is smooth, on schedule and supports warfighter needs. This user forum focuses on operational events which impact new mission capability at defined transition milestones.

1.3.2.2.1. Manage the PSOWG and Steering Committee meetings, distributing meeting notice, tracking attendees, coordinating with briefers for briefing materials, printing briefing materials, updating status of PSOWG Action Items from previous meetings and capturing and distributing meeting minutes. Coordinate facility requirements and meeting support. (Travel is required. PSOWGs are conducted at least twice a year..)

1.3.2.2.2. Provide updates to the Integrated Transition to Operations Schedule (ITTOPS) which addresses the entire System and identifies critical paths associated with key transition events. Reviews of the ITTOPS occur monthly with updates required as needed.

1.3.2.2.3. Distribute meeting notice, track attendees, coordinate with briefers for briefing, print briefing material, update status of Action Items from previous meetings, capture and distribute meeting minutes, and coordinate facility requirements and meeting support for the Protected SATCOM Working Group, mandated by SI 714-4. The forum provides an opportunity for the operational community to discuss viability of current and future CONOPS, policies and procedures associated with Protected SATCOM Systems. (Protected SATCOM WGs are held twice a year in tandem with POWG. Travel is required.)

1.3.2.3. Requirements Traceability Matrix/Mission Matrix. Requirements Traceability/EHF Mission Matrix databases that have been built in Rational Pro and contain a compilation of 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. These databases must continue as new CONOPs documents are evolved, and as new design requirements are approved.

1.3.2.3.1. Maintain the Requirements Traceability Matrix/Mission Matrix and generate a classified database using the same data structure created for unclassified data to capture classified ORD/CDD requirements.

1.3.2.3.2. Analyze data to determine inconsistencies and/or gaps between operational requirements, design requirements, and evolving CONOPS. Generate reports displaying information for different acquisition and operational management personnel.

1.3.2.3.3. Generate reports documenting traceability between ORD/CDD requirements, design requirements, and operational tasks and participating in various System Level Test Meetings.

1.3.2.3.4. Provide a technical report to the QAE on additions to the Rational Pro database and/or data structure changes required to accommodate new data types, applying CONOPS documents, design specifications, and test documents.

1.3.2.4. 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), interacting, participating, and briefing working groups. (Travel is required.)

1.3.2.5. Technical and Acquisition Working Group Support. Present, support, brief and defend MILSATCOM issues/concerns, participating in multiple working groups for acquisition, technical and sustainment to develop and field new Protected Systems. (Approximately 24 meetings per year; travel is required.)

1.3.2.6. SATCOM Security Architecture Analysis.

1.3.2.6.1. Certify and accredit Protected SATCOM Systems and provide recommendations for testing in support of site accreditations. Integrate security certification and accreditation into the overall Developmental and Operational Testing and Evaluation (DT&E and OT&E) process as defined in DoD 5200.40, DoD Information Technology Security Certification and Accreditation Process (DITSCAP) or the DoD Information Assurance Certification and Accreditation Process (DIACAP) contained in DoD CIO Memo, "Interim DoD Information Assurance (IA) C&A Process Guidance,” 6 July 2006. Accreditation must occur before any sensitive or classified operational traffic is transported or handled by a new system. Testing for security and protection which includes cryptographic (crypto) equipment, test keys, and all available components will commence during each DT&E and/or OT&E test period. Maintain and update security classification guides (SCG), in particular the Milstar/AEHF SCG, the TSAT SCG, and in the development of the EPS SCG. Develop and maintain redacted SCGs for International partners in accordance with the latest DoD, AF, and HQ AFSPC information protection guidance.

1.3.2.6.2. Review, comment, coordinate and recommend concurrence or non-concurrence for security documents such as System Security Authorization Agreements (SSAAs), Interim Approval to Test, Letter of Assurances, Security Classification Guide Challenges, Engineering Change Proposals, Interim Authority to Operate and Authority to Operate. Develop briefings and information papers on security issues for leadership and the protected SATCOM community. Review and comment on network architectures (planning tool and key management tool networks) and satellite architectures. Provide an understanding of accreditation boundaries and organizational roles and responsibilities, working with all stake holder Designated Approval Authorities (DAAs).

1.3.2.7. Crypto Modernization. Identify crypto modernization impacts to current and future protected MILSATCOM systems, including space, terminal, and mission control segments. Develop Analyses of Alternatives and recertification requests. Develop requirements for modernized devices and monitor progress of programs such as the VINSON ANDVT Crypto Modernization (VACM). Interface with AFCA, the AF lead for crypto modernization, and NSA, the DoD lead.. Prepare minutes and briefings and complete action items for AFSPC-hosted working groups investigating crypto modernization issues, service level working groups, and joint level working groups such as the Joint Service Crytpo Modernization Working Group (JSCMWG).

1.3.2.8. Security Working Groups. Work under this requirement includes protected SATCOM systems satellite payload and bus operations, Strategic and Tactical end-user SATCOM operations, and Transmission Security (TRANSEC) and Communications Security (COMSEC) processes. Provide briefings to security working groups, such as the Advance EHF Security Engineering working group, International Partner AEHF Security Working Group, System Security Engineering working group, TSAT “Face to Face” working group, EPS security working groups, security classification guide IPTs, and ad-hoc working groups on work-specific information assurance, security classification and/or crypto modernization issues. Provide input to technical discussions with US and IP working group participants. (Approximately 18 working group meetings per year; travel is required.)

1.3.2.9. Fencing CONOPS.

1.3.2.9.1. Recommend and prepare updates 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.)

1.3.2.9.2. Provide technical reports from analysis of Fencing CONOPS information and briefings for working groups. (Approximate number of reports is three annually. Travel is required.)

1.3.2.9.3. Provide a study and briefing on the TSAT Fencing Capability and Interoperations with AEHF and EPS during TSAT development. Evaluate fielding plans of the TSAT for impact to AEHF fencing. Evaluate operational impact to TSAT and EPS related fencing concepts. Provide input to the Interface Control Working Group, Inter-Operability Working Group, and the Legacy Terminal Working Group.

1.3.2.10. Legacy Terminal Network Transition Plan (LTNTP). The purpose 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. Systems utilized for this effort include Milstar, Single Channel Transponder System (SCTS), and UHF follow-on (UFO) EHF package (UFO-E), TSAT and EPS and associated terminal specific information.

1.3.2.10.1. Update the LTNTP and provide recommendations for directed network transition during tracking of upgraded terminal installs.

1.3.2.10.2. Develop a composite schedule for network transition through analysis of terminal fielding schedules from all service Terminal Program Offices. Provide recommendations in the LTNTP for transition working groups, the AEHF Transition Steering Committee (ATSG) and subsequent transition committees for fielding all EHF capable terminals and available dates for network transitions to EHF.

1.3.2.10.3. Provide quarterly updates to the LTNP.

1.3.2.10.4. Provide technical reports or briefings of LTNTP information to working groups. (Approximate number of reports is four annually; travel is required).

1.3.2.11. Nuller Policies and Procedures.

1.3.2.11.1. This requirement utilizes the AEHF Mission Planning Sub System (MPSS) along with the Nuller Policies and Procedures document to assess the viability of MPSS functionality and Nuller Policies. This capability is also included in TSAT.

1.3.2.11.2. Provide technical reports (approximately two) with recommendations on changes to policy and/or MPSS/TSAT software which will result in either modification to Nuller Policies and Procedures documentation and/or deficiency reports written against the MPSS/TSAT software. Update utilizing the comment resolution matrix process if modification of Nuller Policies and Procedures is required. (Approximately one update per year.)

1.3.2.12. System Engineering Analysis. 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; travel may be required.)

1.3.2.13. Loading Analysis Study (LAS). The QAE will determine the software tool for use in developing the LAS. A minimum of four studies will be conducted each year. Study reports shall consist of two interim reports, one final report, and supporting briefings. Format for data from the study will be provided by the QAE.

1.3.2.13.1. Depict the impact of transitioning existing Milstar networks and adding additional networks and users to the AEHF, TSAT and EPS systems with Loading Analysis Studies (LAS), determine required network resources on the uplink, downlink and crosslinks for the XDR and XDR+ system, establish the Internet Protocol (IP)-based network configuration for TSAT, incorporate survivability requirements such as scintillation and any signal interference to the terminals due to the proximity of different satellite beams, address any International Partners on TSAT and their resource allocation in relation to US operations, compile the US warfighter requirements and assign to specific satellites based on the current USSTRATCOM satellite fielding plan or AFSPC recommended fielding plans.. The studies will include the satisfaction of Thule AB requirements on TSAT and EPS.

1.3.2.13.2. Provide recommended timeframes for studies which will be delineated by specific years based on the fielding of terminals. Evaluate the effects of an AEHF, TSAT, and EPS constellation and any remaining operational Milstar or UFO-E satellites. Recommend Transmission Security (TRANSEC) key to channel mapping or other TSAT implemented security measures analyzing crosslink loading. Evaluate appropriate loading for each system for a possible contingency situation. Provide briefings to working groups. (Travel may be required.)

1.3.2.14. Endurance Mission Support. Provide briefings, studies and point papers in support of DC2N development and implementation, participating in multiple working groups to support implementation and continuation of the Endurance Mission support as related to the AEHF, TSAT, and EPS and other MILSATCOM systems. Provide and support SSE issues and concerns. (Travel is required.).

1.3.2.15. Protected Systems Technical Support. AEHF and EPS use the XDR waveform.

1.3.2.15.1. Provide technical assessments, XDR and TSAT /XDR+ data collection, data configuration control and MPSS and TSAT data base population for MILSATCOM and the 614th Space Communications Squadron with AEHF-EHF/XDRXDR/XDR+ related technical issues to include XDR, and TSATXDR/XDR+ SDB requirements. Provide support for EPS and TSAT protected system constellation deployment plans, apportionment planning/execution and XDR and TSAT/XDR+ communications planning.

1.3.2.15.2. Provide technical assessments for XDR and TSAT/XDR+ SDB communications requirements and technical assessments of new and changed AEHF, EPS or TSAT SATCOM requirements for MILSATCOM and the Operational SSE. Provide technical assessments on future systems to include Teleports, TSAT EPS and TSAT.

1.3.2.15.3. Identify XDR including EPS)/XDR+ specific data to populate the MPSS and TSAT planning and operational databases for MILSATCOM the 614th SCS. Identify inputs from the 614th SCS, the Defense Information Systems Agency, Terminal Program Offices (TPO), SPOs and MPSS and TSAT developer to XDR /XDR+ data for integration with current LDR and MDR collection and configuration control process. Populate MPSS and TSAT data bases with XDR EPS/XDR+ data and develop Data Base Change Requests (DBCRs) and XDR and EPS/XDR+ configuration control process/procedures. Attend configuration control board meetings when XDR operations are on the agenda. (Approximately 12 meetings annually.)

1.3.2.15.4. Assist MILSATCOM and the Operational SSE in downloading and assessing the current SDB database and uploading technical assessments applying the latest version of SDB-MT and procedures in the SDB-MT Tool Kit and Users Manual.

1.3.2.15.5. Assist MILSATCOM and the Operational SSE with XDR EPS and TSAT/XDR+ related apportionment planning, allocation, communications planning and constellation deployment issues, including XDR/XDR+ frequency planning, fencing, crypto planning and other protected system unique payload issues. Provide recommendations to configure AEHF and EPS payloads and antennas to support both backward compatibility and XDR/XDR+ operations including placement of AEHF/EPS satellites and availability of XDR/XDR+ 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 plans with MILSATCOM and the Operational SSE. Access the MPSS and TSAT to assist communications planners with XDR/XDR+ Network planning.

1.3.2.15.6. Provide a memorandum for record (MFR) describing meetings in support of the Joint SATCOM Panel (JSP) and meetings with XDR/XDR+ operations as significant topics of discussion. The MFR shall address any significant protected system issues discussed, resolved, and / or open for action. (There are 12 JSP telecoms/meetings per year and an annual review.)

1.3.2.15.7. Present XDR/XDR+ topics at Technical Interchange Meetings (TIMs) and working groups to support the identification and management of AEHF-EPS/XDRXDR/XDR+ 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.

1.3.2.16. Dual Operations Study. The dual operations timeframe is a period of time when some EHF users may operate two different planning tools, the AEHF Mission Planning Element (MPE) and the TSAT Mission Operations System . This period may be indefinite or when/if MPE is fully integrated into TSAT (currently TSAT design has not yet been finalized.)

1.3.2.16.1. Analyze and document implications of operating with both MPE and TSAT.

1.3.2.16.2. 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 meetings such as the Operations Transition Working Group or Users Forums.

1.3.2.17. XDR+ Education. (Travel is required.)

1.3.2.17.1. Provide TSAT XDR+ training to AEHF and TSAT system communications planners involved with planning crypto, payload tables and tactical and strategic communications networks, reviewing existing materials and most relevant and understandable materials on new capabilities/functions provided by XDR+. Training shall provide the Mission Planning Element (MPE) and TSAT differences between system waveforms and capabilities.

1.3.2.17.2. Provide briefing materials based on different levels of communications, payload, crypto, strategic net and tactical net planning. Briefing shall include screen shots of the most representative screens for each planning level from the communications planning tool to provide an understanding of all entry fields on each screen for each planning process, who enters data for fields, and who can modify data.

1.3.2.18. International Partner System Transition.

1.3.2.18.1. Develop an integrated schedule section in the Protected Systems Operations Working Group (PSOWG) identifying events and deliverables necessary to transition AEHF operations to IPs. Upon receipt of official international agreements, coordinate with the TSAT and/or EPS Contractor Team to develop the System Transition Management Plan (STMP) addressing IP transition to operations for those programs’ segments.

1.3.2.18.2. Develop and maintain the IP STMP to systematically transition the IPs into operations and attend meetings (estimated six per year) for International Partner participation in the fielding of Protected SATCOM systems.

1.3.2.18.3. The ITTOPS was developed to coordinate the transition from AEHF to TSAT operations for the US community and identifies events to support IP operational transition, such as, terminal test events. Upon receipt of official international agreements, provide a comprehensive schedule of events necessary to bring IPs into protected EPS and/or TSAT operations and address capabilities IPs receive and at what point in time. This schedule shall be used to develop a critical path and dependency depiction. Data developed will be housed on a government web site and integrated into existing ITTOPS and Enterprise Schedule.

1.3.2.18.4. Elements required for tracking during transition:

Satellite, TSAT , Terminals (IP Variant), Sustainment, Training, Security

Each element shall address the following:

Factory schedules DT/OT Test Events

Training Sustainment Transition

Tech orders Concept Development

Software deliveries Certification and accreditation

Requirements Clarification Policies and Procedures

Database Deliveries Apportionment Cycle

Network Transitions Terminal Fielding Schedules

Site Identification, Site Surveys, Site Installations

Operational Support Cell

Satellite: Constellation deployment and build up, calibrations, MPE: Issues relevant to development of TSAT, locations and order of installs, apportionment timelines, distribution of operational databases, end-to-end data flow Terminal: Fielding of IP terminal types, training, deployment, software delivery concepts, Sustainment: Transition of TSAT IP products into sustainment

1.3.2.18.5. Provide a draft IP ITTOPS to the QAE post award, using the STMP and the ITTOPS as the baseline format for the IP versions of the STMP and ITTOPS. Provide the Final IP ITTOPS post award to the QAE. Revisions may be required (estimated at up to three) until contract end.

1.3.2.18.6. Provide trip and meeting reports five business days after trip or meeting completion (approximately three trips per year).

1.3.2.19. IP Certification and Accreditation (C&A).

1.3.2.19.1. Develop the C&A support for the IPs applying the DoD Information Assurance Certification and Accreditation Process (DIACAP) or the DoD Information Technology Security Certification & Accreditation Process (DITSCAP) and participate in meetings related to C&A. Develop IP relevant C&A documents and review /comment and coordinate on IP developed C&A.

1.3.2.19.2. Provide a comment resolution matrix (CRM) for each document and IP Document review of IP developed C&A.

1.3.2.19.3. Provide trip and meeting reports five business days after trip of meeting completion (approximately two trips per year).

1.3.2.20. 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 which identify mission area impacts and recommendations for capability gap coverage. Quarterly reviews of schedules and interim updates to the Roadmap document will be required, although the schedule for this product is tied to programmatic changes and updates may occur on a more frequent basis.

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

1.3.2.22. Teleport Support. Monitor and track teleport implementation and provide periodic loading analysis and CONOPS review to meet strategic and tactical requirements. Attend meetings and Teleport working groups, review and comment on technical documents and CONOPS, and assist with development of policy and procedure.

1.3.2.23. Additional IP Integration. Provide analysis on effects of adding IPs onto protected systems with mission impacts to US warfighters, security implications, and impact to logistics and satellite resource management.

1.3.2.24. Concept of Support (CONSUP). The International Partner (IP) Concept of Support (CONSUP) provides high-level discussion on DoD support to the IPs during AEHF operations. As part of the growth of the US MILSATCOM capability, additional systems are under development. As a living document, CONSUP provides the development community and IPs with a vehicle to address the integration of IPs into protected system operations. The CONSUP also specifies how communications planning are envisioned for support of the IP.

1.3.2.24.1. Upon receipt of official international agreements, provide recommendations for the structure of the CONSUP, as overarching or specific to each system.

1.3.2.24.2. Modify the CONSUP and update to reflect the most current design of protected systems and the new systems (EPS & TSAT) either as standalone documents, i.e., specific to a system, or as an overarching concept document.

1.3.2.25. Coalition Network Interoperability Plan (CNIP). The IP CNIP is a study providing detailed information on conduct of operations between US forces, IP forces and other allies. Addressed in the plan are 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 provides 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 further addresses support required by IPs from the Global SATCOM Support Center (GSSC), RSSCs and standard operating procedures (SOPS) for AEHF operations and support and also specifies how communications planning is performed in support of IPs.

1.3.2.25.1. Upon receipt of official international agreements, develop a CNIP for each protected system as IPs are integrated into that systems operations.

1.3.2.26. GSSC Operating Instructions. The GSSC provides 24-hour operations’ functions for global support to users. SATCOM support centers provide communications planners, network managers, and users with a single focal point for accessing and managing SATCOM resources. These centers support combatant commands and other users in managing apportioned SATCOM resources and real-time allocation of non-apportioned resources. The GSSC is the focal point of US support to IPs in general and during IP and coalition operations. The GSSC is currently located at Peterson Air Force Base (AFB) in Colorado and an International Partners Annex has been established to provide support to IPs.

1.3.2.26.1. Develop in coordination with the GSSC IPA, operating instructions (OIs) for each of the protected systems with the GSSC as the focal point for IP support.

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

1.3.2.28. 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 develop IP resource allocation loading and the impact to the system of interest.

1.3.2.29. Technical Information Center (TIC). Develop and maintain a TIC containing soft copies of all program documentation material, software, and deliverables up to and including Secret information. Deliver the TIC to the QAE at contract end and submit an updated TIC inventory with the MSR.

1.3.2.30. Security Clearance. Access to TS/SCI is required in accordance with the DD 254. SCI billets will be available.

1.3.2.31. Facilities and Supplies. MILSATCOM will provide workspaces in the Hartinger Building on Peterson AFB, to include desk space, chairs, computers connected to 21 NET, Secret Internet Protocol Router Network (SIPRNET) access, and use of telephones, copiers and fax machines. All other contractor employees shall work at contractor facilities.

1.3.2.31. Travel. Contractor employees may be required to travel to various locations within the continental United States (CONUS) in performance of this contract. Estimated travel requirements are included below. All contractor travel shall be approved by the Government prior to departure. Any travel required shall be performed in accordance with FAR 31.205-46, Travel Costs.

Travel

(does not include travel time)

Each year, one trip to one of the IP countries below:

1.3.3. Operations Support.

1.3.3.1. Operations, Sustainment and Engineering Support.

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

1.3.3.1.2. Provide engineering technical analysis and support, point papers, briefings, and concept development documents for the optimization of MILSATCOM space systems to include Protected, Wideband, Transformation and Narrowband MILSATCOM Systems as well as other DOD SATCOM systems. Attend meetings and conferences. (CDRL 0005, 0008b)

1.3.3.1.3. Provide a quick-look report and technical analysis for the 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% of meetings may be conducted via dial-in telephone conference. (CDRL 0005)

1.3.3.1.4. Provide quarterly Transformational Communications Architecture (TCA) review and recommendations to Transformational Satellite Communications (TSAT) System Integrated Test Team (ITT) and test documentation development, and TSAT IOC/FOC plan development. Provide analysis, updates and recommendations for network management and satellite operations issues and terminal and scheduling issues, participating in quarterly Transformational Operational Transition Groups involving Milstar and Advanced EHF and TSAT transition (Ops issues).

1.3.3.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, participating in quarterly Protected Operational Transition Groups involving Milstar, Advanced EHF and EPS transition (Ops issues). Provide IOC/FOC plans and recommendations for Protected Systems to the A3, A5 and the AFSPC/CC.

1.3.3.1.6. Provide annual recommendations/ revisions (CDRL 0008) 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.

1.3.3.1.7. Provide weekly recommendations, changes and revisions to MILSATCOM…