3. WICS II PWS (21 CS rqts only) - 31 Jul 25.docx

Schriever Space Force Base, Colorado

Wing Information & Communications Support

(WICS-II)

Performance Work Statement FA255021C0005 25 April 2024

Note: Requirements not planned to be included in the consolidated effort have been removed

WICS-II PWS

Contract FA255021C0005

Table of Contents

Government-Furnished Equipment (GFE), Property (GFP) and Information (GFI) . 66

Appendix A WICS-II CDRL Requirements 71 Appendix B Acronyms 72 Appendix C Definitions 78 Appendix D Publications and Forms 92 Appendix E Mission Essential Contractor Services 93

Chapter 1 Background and Contract Scope

1.0 Background

The mission of Space Base Delta 1 (SBD 1), is to enable and empower combat-ready space and homeland defense operations through mission critical global support to protect and defend our Nation. SBD 1 currently operates and supports satellite operation centers at Schriever Space Force Base (SSFB), Colorado, remote tracking stations and other command and control facilities around the world. SBD 1 personnel monitor satellites during launch, put satellites in their proper orbits following launch, and operate the satellites while they are in orbit. They ensure effective and efficient satellite operations and proper disposal of the satellites at the end of life.

SBD 1 operates and supports satellite programs including the Global Positioning System (GPS), Defense Satellite Communication Systems (DSCS), Wideband Global SATCOM (WGS), Military Strategic and Tactical Relay (MILSTAR), Defense Meteorological Satellite Program, Space Based Space Surveillance (SBSS), Operationally Responsive Space, Advanced Extremely High Frequency (AEHF), Mission Impact Reporting (MIR), Space Digital Integrated Network (SDIN) and Global Command and Control System (GCCS) and the worldwide Satellite Control Network (SCN) supporting 185 satellites.

1.1 Scope

The scope of this contract encompasses all services required to support the operation, maintenance, and logistics of the SSFB Installation information and communications systems as these exist at the time of contract award and as they evolve over the course of contract performance. This effort includes the ability to provide support to various SSFB Installation information and communications systems and associated tenant organizations. During the performance of this contract, the contractor shall provide non-personal services in support of operations, mission systems maintenance and maintenance management, logistics management, communication support, security and emergency notification systems, testing and all other requirements within the WICS II Performance Work Statement (PWS). Support also includes potential future requirements, emerging technologies, system growth, and new/upgraded equipment as needed.

1.2 Overview of Principle Systems

1.2.1 Global Broadcast Service (GBS): GBS is a satellite communication based, worldwide, high-capacity broadcast system that provides a one-way, high-speed flow of high-volume national security information to forces garrisoned, deployed, or on the move with tactical GBS satellite receive suites (RS). GBS provides a content priority-based delivery of classified and unclassified video and data products. GBS is a Defense Information Systems Agency (DISA) Core Data Center (CDC)-centric architecture providing centralized Satellite Broadcast Manager (SBM) system for continuous operations, management, and control of DISA dedicated assets assigned to GBS and GBS Mission Unique Equipment (MUE). The GBS Operations Center (GBSOC) is the centralized service center that provides broadcast and event management, troubleshooting, coordination, reporting, and overall status and situational awareness of the GBS system and services. Additionally, the GBSOC provides GBS RS end-user service desk support. Under the WICS-II contract, GBS resources include the following:

· GBSOC at SSFB

· GBS Continuity Operations (COOP) at Peterson Space Force Base (PSFB), Colorado - GBS COOP at Hill Air Force Base (HAFB), Utah

· GBS SBM at Tinker Air Force Base, Oklahoma (OKC): The DISA CDC, formally known as DECC, houses the GBS “Primary” SBM equipment and provides GBS Department of Defense Information Network (DoDIN) network connectivity.

· GBS SBM at Mechanicsburg, Pennsylvania (MECH): The DISA CDC houses the GBS “Backup” COOP SBM equipment and provides DoDIN network connectivity.

1.2.2 Wideband Global SATCOM (WGS): WGS is used for high priority command and control communication such as the exchange of wartime information between defense officials and battlefield commanders. The military also uses WGS to transmit space operations and early warning data to various systems and users. Under the WICS-II contract, WGS resources at SSFB include the following:

· Dual AN/GSC-52(V)5 WGS Earth Terminals

· Four AN/USC-28 Spread Spectrum Multiple Access (SSMA) Anti-jam (A/J) modular- demodulator (MODEMs)

· AN/MSC-66 Digital Communications Satellite Subsystem (DCSS)

· OM-88 MODEMs

· Interconnect Facility

1.2.3 Family of Advanced Beyond Line-of-Sight Terminal (FAB-T): FAB-T (formerly referred to as MILSTAR) is used for high priority, secure and jam resistant worldwide communications to meet the requirements of the Armed Forces of the United States. Under the WICS-II contract, FAB-T resources at SSFB include, but are not limited to, the following:

· AN/FRC-191(V)1 FAB-T Command Post Terminal

· 10FT Antenna System Tower

· Data Set Manager

1.2.4 Global Command and Control System (GCCS): The GCCS mission system is comprised of Uniplexed Information and Computing System (UNIX) and Internet Protocol (IP) based operating systems. GCCS supports the following sites:

· SSFB, Colorado

· PSFB, Colorado

· Buckley Space Force Base (BSFB) Colorado

· United States Air Force Academy (USAFA), Colorado

· F.E. Warren AFB, Wyoming

· Malmstrom AFB (MAFB), Montana

· Los Angeles AFB (LAAFB), California

· Vandenberg SFB (VSFB), California

1.2.5 Space Digital Integrated Network (SDIN): The SDIN mission system consists of a combination of Circuit-to-Packet (CTP) technology, Routed Networks and Synchronous Optical Network (SONET), High-Altitude Electromagnetic Pulse Protected networks. SDIN supports the following sites:

· SSFB

· PSFB

· BSFB

· VSFB

· Eglin AFB, Florida

· Cheyenne Mountain Space Force Station (CMSFS), Colorado

· Cape Cod Space Force Station (SFS), Massachusetts

· Cavalier AFS, North Dakota

· Clear AFS, Alaska

· Dahlgren Naval Air Station (NAS), Virginia

· Diego Garcia Air Station (AS)

· Site R, Socorro AS, New Mexico

· Kwajalein AS, Republic of the Marshall Islands

· Maui AS, Hawaii

· Royal Air Force Base, Fylingdales, United Kingdom (UK)

· Millstone Lincoln Labs, Offutt Air Force Base (OAFB), Nebraska

· Thule Air Base (AB), Greenland

1.2.6 Mission Impact Reporting (MIR): MIRs are the only and singularly important feedback mechanism to determine how the SCN is performing day-to-day, satellite contact by satellite contact and is the primary tool used to debrief SCN operations. MIRs feed multiple SCN performance metrics as mandated in the Headquarters (HQ) United States Air Force (USAF) “2002 Satellite Control System Operations Requirements Document” when calculating contact success rate and enables the SBD 1, USAF, and USSF SpOC at tactical and strategic levels in executing resource management decisions for space access.

Chapter 2 Program Management

2.0 Program Management

Provide all personnel, tools, materials, transportation, supervision, and other items necessary to perform WICS-II PWS requirements. The Contractor’s furnished materials and equipment shall include vehicles, vehicle fuel, tools, custodial supplies, office administrative supplies and equipment, and any other supplies and materials not furnished by the Government, which the Contractor believes necessary to perform these requirements.

2.1 Government Management Team (GMT)

Notify the GMT of any problems affecting the contractor’s performance impacting mission accomplishment or any issues the contractor considers not within the scope of this contract. The GMT consists of the Contracting Officer (CO), the Government Program Manager (GPM), the Contracting Specialist and the Contracting Officer’s Representative (COR).

2.1.1 Provide a Program Management Plan, (Contract Data Requirements List (CDRL) A101 – Program Management Plan). Provide an overview of the general approach and methodology to implement and oversee the performance of the WICS-II PWS.

CDRL A101: Program Management Plan

2.2 Coverage Hours

Contractor coverage must mirror the respective Government work center hours, to include Federal holidays, unless otherwise identified within the PWS.

2.3 Mission-Essential Contractor Services

Ensure continued support of all locations identified in this PWS during crises, as required by DoDI 1100.22, policy and procedures for determining workforce mix, and, unless otherwise directed by the CO. Provide CDRL A102 - Mission-Essential Contractor Services Plan IAW Defense Federal Acquisition Regulation Supplement (DFARS) 252.237-7023, Continuation of Essential Contractor Services, for providing assurance of continuation of mission essential services during crises conditions. See Appendix E, which identifies mission essential areas on this contract.

CDRL A102: Mission-Essential Contractor Services Plan

2.4 Exercise/Inspection Support

2.4.1 Fully participate in all SBD 1 exercises/inspections to the level dictated by the scenarios in progress. This support will be required on a non-mission interference basis during normal contractor duty hours.

2.4.2 Not be required to increase manpower or man-hours during exercise participation unless specifically stated in this PWS or authorized by the CO.

2.4.3 The contractor may experience delays entering and/or exiting the base due to exercises, increased security, base closure or late reporting due to weather conditions. Anticipate exercises on a quarterly basis. In all cases, ensure mission essential work center coverage while minimizing potential harm to contractor employees.

2.5 Contractor Manpower Reporting

2.5.1 Report ALL contractor labor hours at all sites (including subcontractor labor hours) required for performance of services provided under this contract. Reporting shall be accomplished for the Space Acquisition Management-Directive (SAM-D Schriever) formerly known as 50th Contracting Squadron (50 CONS), DoD activity address code (DoDAAC) number FA2550, via a secure data collection site. The contractor is required to fill in all required data fields at http://www.SAM.gov.

2.5.2 Reporting inputs will be for the labor executed during the period of performance (PoP) for each government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year.

2.6 Personnel Management

2.6.1 Contractor Program Manager

2.6.1.1 Identify in writing, email is sufficient, to the CO and GPM, any individual designated to act as the Contractor Program Manager (CPM).

2.6.1.2 The CPM or designee shall have full authority to act for the contractor on all matters relating to daily operations of the WICS-II contract.

2.6.1.3 Advise the GPM immediately or within 15 minutes, of any problems that affect the contractor’s performance.

2.6.1.4 The CPM or designee shall be available at all times for discussions via teleconference.

2.6.2 Contracting Manager

2.6.2.1 Identify in writing, an email is sufficient, to the CO and GPM, any individual designated to act as the Contracting Manager.

2.6.2.2 The Contracting Manager or designee shall have the authority to act on behalf of the company in all matters relating to contract performance and to review and sign all contract actions.

2.6.2.3 The Contracting Manager shall be available Monday through Friday, between the hours of 0800-1500 Mountain Standard Time (MST), for discussions via teleconference.

2.6.3 Contractor Employees

2.6.3.1 All contract employees who interface with the government, either electronically or in person shall be able to read, write, speak, and understand English.

2.6.3.2 Select personnel who are fully certified and/or qualified/trained and have the necessary security clearances to provide the government the services required by the WICS-II PWS.

2.6.3.3 Identify/introduce themselves as contractor personnel and display distinguishing badges or other visible identification for meetings with government personnel, appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

2.6.4 Contractor Conduct

2.6.4.1 The contractor employees shall be subject to regulations and directives governing the activities of personnel on government installations.

2.6.4.2 The installation commander may direct the contractor, in writing, to remove any employee from the installation when retention of such employee endangers life, property, security, or where such an employee violates reasonable and necessary base regulations or displays improper behavior.

2.6.5 When a mishap occurs or an employee displays improper behavior, the Government reserves the right to immediately remove an individual from the installation.

2.7 Contractor Reimbursable Travel

2.7.1 Travel may be required to perform the services required by this PWS. This may include Government directed travel and COOP. All travel requirements shall be pre-approved by the GPM or CO and is on a strictly cost reimbursable basis. Costs associated with contractor travel and billing shall be in accordance with Federal Acquisition Regulation (FAR) 31.205-46, Travel Costs. The contractor shall be responsible for all employee travel arrangements by commercial means. Contractor employee travel shall be IAW current Joint Travel Regulations. Transportation may be provided by the military depending on access to bases and availability of commercial transportation. The contractor shall travel using the lowest cost mode transportation commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid. Travel within the El Paso County area will not be reimbursed.

2.7.2 Submit a Travel Authorization Request (TAR) to the GPM or CO and receive approval prior to booking travel arrangements. The TAR shall include trip number, traveler name, travel dates, trip destination(s), description of trip, and estimated trip costs, e.g. airfare, lodging, per diem, rental car, etc. The TAR amount will be the approved trip reimbursable cost. The TAR requires recommendation from the COR and CPM or designee and approval by the GPM or CO. The TAR may be in contractor format.

2.7.3 Submit a cost report within 30 days of conclusion of trip. The trip report will contain trip number, traveler name, trip location, actual travel dates, and detail actual costs compared to estimated costs. Costs over the approved TAR amount must be justified and receive approval prior to submission of cost voucher. The cost report may be in contractor format.

2.8 Local Purchase

Purchases may be needed in the performance of the PWS requirements. All purchase actions require a recommendation from the COR. Purchases will be coordinated and approved through either the GPM or the CO. Purchases shall be handled IAW contractor policy and procedures and formally documented IAW DFARS 252.244-7001. Purchases will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

2.8.1 Special Purpose Vehicles and Equipment

When the need arises to utilize special purpose vehicles, one-time use vehicles or equipment, notify the government. When directed by the Government, directly lease the required special purpose vehicles, subject to the cost limitation directed by the Government, with the cost of the lease allocable to the appropriate FY. All lease actions require recommendation from the COR, coordination and approval through either the GPM or the CO.

2.8.2 SDIN Technical Refresh Local Purchase

Purchase, install, configure, integrate and test technical refresh equipment as part of a future requirement for SDIN technical refresh. Using the contractor’s purchasing system IAW DFARS 252.244-7001, any equipment or supplies purchase will be coordinated through the SDIN Program Manager, and the GPM, and approved by the CO prior to commitment of funds. To obtain approval for purchasing equipment, the contractor must provide adequate supporting documentation to the CO. The contractor will be provided authority to use Government sources of supply, such as General Services Administration (GSA) schedules, to obtain the best value for the Government. Documentation must be provided with cost vouchers when invoicing for reimbursement.

2.9 Quality Management

Have an independent quality program, encompassing all aspects of the contract; ensuring service delivery meets or exceeds performance requirements in the PWS. Implement the quality program through a Quality Control Plan (QCP) (CDRL A103). The QCP shall be submitted and accepted by the GPM, Quality Assurance Manager and CO.

CDRL A103: Quality Control Plan

2.10 Training

2.10.1 Contractor Specialized Training

2.10.1.1 Conduct a qualification or certification training program for contractor personnel. Create, update and conduct a position certification/qualification training program to ensure contractor personnel are certified/qualified to perform operations and maintenance requirements identified as requiring certification/qualification.

2.10.1.2 Ensure personnel are properly trained and have appropriate DoD approved cybersecurity baseline certification(s) before performing any network operations tasks. Provide the GMT copies of the appropriate certification(s) prior to being given privileged access to the network and/or assuming cybersecurity responsibilities and ensure they remain in good standing. All contractor personnel shall complete and sign a formal statement of assigned cybersecurity responsibilities. Immediately remove personnel not in good standing from cybersecurity tasks. Maintain the currency of employees by providing initial and refresher training as required to meet the PWS requirements.

2.10.1.2.1 Be certified IAW Methods and Procedures Technical Order (MPTO) 00-33A-1001, Department of Defense Directive (DoDD) 8140.01, Department of Defense (DoD) 8570.01-M, Air Force Manual (AFM) 17-1303 and DoD Approved 8570 Baseline Certifications.

2.10.1.2.2 Contractor personnel working on SDIN and GCCS networks shall be certified at the IAT Level II.

2.10.1.2.3 Have personnel certified at the Information Assurance Management (IAM) Level II to maintain the Risk Management Framework (RMF) package.

2.10.1.2.4 The certification/qualification program is to be contractor self-contained, requiring no technical or materiel support from the government and is subject to government review.

2.10.2 Ancillary Training

2.10.2.1 Participate in ancillary training as required by the work being performed and IAW applicable documentation (instructions, standards, etc.).

2.10.2.2 At a minimum, the following courses via the Air Force myLearning application, Computer Based Training (CBT), or classroom attendance shall be completed within thirty (30) days after contract award (Table 2-1 – Ancillary Training). Other training may be required at the request of the COR. The training records shall contain, at a minimum, the completed/signed formal statement of assigned cybersecurity responsibilities and copies of the appropriate certifications.

Table 2-1 – Ancillary Training

2.10.3 Training Records

2.10.3.1 Maintain training records for personnel. All training records shall be made available for COR review upon request. Establish and maintain a training document or database, or use the existing maintenance information systems database, to track contractor training requirements. The document or database will, at a minimum, reflect training due dates, training completion dates and projected due dates.

2.10.4 Training and Education Costs

The Government will provide training and materials as new or modified systems come online. Specialized government provided training (e.g., not commercially available) may be required as directed.

2.11 Program Management Support

2.11.1 Self Inspection/Management Program

Utilize the current government self-inspection/management program, i.e., Management Internal Control Toolset (MICT) or its follow-on system. The contractor shall establish MICT accounts and maintain up-to-date compliance checklists for use during assessments. Applicable check lists/sheets shall be utilized, and pertinent data shall be entered into the MICT system.

2.11.2 Management Information System

Provide government access to a single management information system, whether government- owned or contractor-owned, for management, organization, and consolidation of all CDRLs, program documents, metrics, data, and knowledge. It shall be searchable and allow generated user interfaces and include workflow tools to assist in continuous improvement of WICS-II artifacts.

2.11.3 Meeting Support

Support the government during reviews and meetings, to include providing impact assessments for operations, maintenance, and logistics to SBD 1 personnel. Meetings include, but are not limited to, teleconferences, Utility Outage Board, Modification Control Boards (MCB), Operations Review Boards (ORB), Cybersecurity, Cyber Readiness (CR) and Operations Review Panels (ORP) as defined in unit operating instructions (OIs) and/or policies.

Participate in and/or, support conferences, technical and operational meetings, working groups and reviews with coordination with the COR. Some meetings are scheduled weekly or monthly, others are ad hoc meetings to discuss immediate emergencies, which may be on or off SSFB. Provide the appropriate personnel as required by the agenda to clarify technical details, determine solutions or recommendations, or for other technical expertise. Examples of these meetings are: Command and Control (C2) Working Group for GCCS, and MCB meetings to review, discuss and receive approval for new requirements.

2.11.3.1 Program Management Review (PMR)

Provide PMRs to the government IAW CDRL A105 – Program Management Review. The PMR will be held in the Colorado Springs, CO area (location will be determined by the GMT). For all PMRs, the contractor shall provide the briefing content to the CO and GPM at least three duty days prior to the PMR. The contractor shall present the first PMR within 30 days of contract start. PMR’s shall be presented monthly for the first 3 months, and quarterly thereafter.

CDRL A105: Program Management Review

2.11.3.2 Multi-functional Team (MFT)

A bi-weekly MFT meeting will be held to review current contract and operational events. Inputs shall be provided to the GPM for the MFT. Contractor attendance at these meetings is required (location to be determined by the GMT).

2.11.4 Administrative Support

2.11.4.1 Documentation

2.11.4.1.1 Responsible for creating, maintaining and delivering Government-required documents, records, and reports used for accomplishment of WICS-II requirements.

2.11.4.1.2 Provide the original record or a reproducible copy of record within five working days of receipt of request

2.11.4.1.3 All documentation, products, and data developed in support of the WICS-II contract are the property of the US Government.

2.11.5 Publications Support

2.11.5.1 Contract/Work Center Operating Instructions (OIs)/Standard Operating Procedures (SOPs) Upon contract award, OIs/SOPs used by the incumbent contractor will be provided to the successor contractor. The successor contractor shall use, change, or develop their own OIs/ SOPs (CDRL A106: Contract/Work Center OIs/SOPs). The OIs/SOPs shall be implemented, maintained, and complied with. All OIs/SOPs required for compliance will be accepted by and accessible to the GMT. Contract OIs will address contract wide direction/policy. Work center OIs/SOPs will address work center specific direction/policy/ procedures. All OIs/SOPs, once accepted by the GMT, will become directive in nature. Annually review all OIs/SOPs to ensure they are accurate and update when necessary. All OIs/SOPs become the property of the government, will be maintained by the contractor and will be incorporated into the WICS-II Master Document List (MDL)/Bidders’ Library (BL).

CDRL A106: Contract/Work Center OIs/SOPs

2.11.5.2 New Directive Publications

Review new/updated publications (draft and final) to assess technical content and impact to the WICS-II contract. Notify the CO within 30 days of receipt if there are potential risks to the WICS-II contract.

2.11.5.3 Master Document List (MDL)/Bidder’s Library (BL)

Provide a complete MDL/BL IAW CDRL A108: MDL/BL. The MDL/BL encompasses all publications/documents required to perform the requirements of the PWS. Maintain the MDL for the duration of the contract performance. The MDL/BL (CDRL A108) shall be delivered, within 30 days of CO request.

CDRL A108: Master Document List (MDL)/Bidder’s Library (BL)

2.11.6 Records Management Program

Manage all data created for government use or legally controlled by the government, in support of the functional activity or required by DoDD and AF publications, IAW the DoDD and AF records management procedures in DoDD 5015.2, DoD 5015.2-STD, Air Force Policy Directive (AFPD) AFPD 33-3, Air Force Instruction (AFI) AFI 33-322, and the Air Force Records Disposition Schedule located at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm or their subsequent replacements. All contractor records management personnel shall possess a valid National Agency Check with Local Agency and Credit Check (NACLC).

2.11.6.1 Records Custodian (RC)

At SSFB GBSOC, Technical Control Facility (TCF) and Military Satellite Communications (MILSATCOM), perform RC duties in order to comply with the DoD, AF governing directives, to include the Air Force Records Information Management System (AFRIMS).

2.12 Phase-In/Phase-Out

2.12.1 Phase-In Plan

Upon award, the government will provide the successful contractor a phase-out plan from the incumbent contractor. The successful contractor shall deliver a phase-in plan (CDRL A110 - Phase-In Plan) which complements the incumbent’s phase-out plan. The GMT will meet with the contractor to review implementation of the phase-in plan. The plan shall identify that a complete certified, qualified, trained, and cleared workforce will be available no later than contract start, ensuring no degradation in service.

CDRL A110: Phase-In Plan

2.12.2 Phase-Out Plan

Develop and implement a transition plan for phase-out (CDRL A111 - Phase-Out Plan). Establish procedures with the successors to ensure a smooth transition of all requirements. Maintain overall contract responsibility until the completion of the contract PoP. Ensure all responsibilities are transferred ensuring no degradation in service.

CDRL A111: Phase-Out Plan

Chapter 3 Global Broadcast Service (GBS) Operations

3.0 Operations

Perform 24/7 on-site operations activities, unless identified in the following paragraphs. Plan, schedule, direct, organize, coordinate, and execute all actions necessary to conduct continuous operations and sustain the operability of the GBSOC at SSFB. Conduct remote administration, from the GBSOC, of the GBS MUE at OKC and MECH. Maintain the equipment IAW applicable TOs, manuals, and OIs/SOPs.

3.1 Global Broadcast Service Operations Center (GBSOC)

Maintain a GBSOC controllable SBM operational availability (Ao) threshold of 99.00%.

3.2 Broadcast Management

3.2.1 Monitor and maintain real-time situational awareness of the GBS broadcast.

3.2.2 Monitor the status of uplink sites for outages that affect GBS broadcasts.

3.2.3 Maintain situational awareness of satellite beam pointing.

3.2.4 Monitor GBS broadcast bandwidth allocation and assist with resolution of bandwidth allocation issues.

3.2.5 Assist the Regional SATCOM Support Centers (RSSC), Wideband SATCOM Operations Centers (WSOC), and Combatant Command (CCMD) Theater Information Managers (TIM) with satellite coverage coordination, broadcast issues, and resolving resource conflicts.

3.2.6 Monitor the broadcast rate of product delivery from the SBM to Receive Broadcast Manager (RBM), and status of products queued, transmitted and sent.

3.2.7 Manage the GBS broadcast content to ensure the specified products are available via the appropriate uplink facility according to schedule. This includes assigning video streams to satellite transponders and determining appropriate data rates.

3.2.8 Support TIMs in maintaining the accuracy of the Electronic Program Guide, Tuning Guide, and Product Catalog.

3.2.9 Perform web crawl reception troubleshooting to resolve anomalies; perform verification checks on each web crawl every 180 days at a minimum to ensure accurate data.

3.2.10 Process requests for broadcast of the GBS banner and troubleshoot anomalies.

3.2.11 Prepare and post Mission Data Sheets to support end-user RS configuration.

3.2.12 Coordinate with TIMs to disable and re-enable GBS RSs.

3.2.13 Execute GBS broadcast remote deny actions.

3.2.14 Set and monitor government prioritized flow control of dynamically allocated bandwidth.

3.2.15 Manage over-the-air broadcasting of Information Assurance Vulnerability Alert releases, and software and system updates to fielded RBMs.

3.3 End User Support

3.3.1 Provide consultation and problem resolution to fielded GBS RS end users from the GBSOC. Respond to GBS end-user service requests for configuring RSs, troubleshooting broadcast reception issues, and understanding the GBS broadcast and broadcast products.

3.3.2 Respond within 15 minutes to service request calls from GBS fielded RS end users. For GBS non-DoD fielded RS users, support is limited to the status of the satellite, beam coverage, and requesting GBS traffic content routed to the SATCOM downlink broadcast string.

3.3.3 Issue CypherCast Windows Client (CWC) and Kencast licenses for fielded GBS RS.

3.4 GBSOC Service Desk

3.4.1 Operate the GBSOC service desk, as the operational focal point for GBS daily broadcast services.

3.4.2 Provide event and incident management troubleshooting, notification and reporting of service interruptions, impairments, or anomalies for systems, circuits, equipment, approved changes, and scheduled maintenance within the GBSOC area of responsibility.

3.4.3 Log, prioritize, investigate, resolve and report problems with GBS services. Respond to and initiate corrective action, within 5 minutes or notification, for incidents, problems, and outages affecting GBS services.

3.4.4 Use and maintain data in a government service management system to document events, incidents, fault isolation actions, status tracking, status reporting, and related GBSOC activities.

3.4.5 Monitor the performance of SBM functions for system and software problems, and operating condition of GBS components.

3.4.6 Fulfill requests from the GBS user community using consistent and repeatable methods for which pre-defined approval exists, such as establishing SBM user accounts and issuing Smart Cards.

3.4.7 Manage the GBS RS Smart Card program to include procurement, storage and distribution, and provide end-user authorization verification, entitlement, and removal.

3.4.8 Report GBS health and status information within the GBSOC area of responsibility through the proper chain of command as determined by GBSOC C2 relationships and reporting procedures established IAW GBSOC OIs and associated reporting guidance. This includes but is not limited to the GBS Event Message (GEM), GBS Advisory Message (GAM), Operations Capability (OPSCAP) reporting, and Commander’s Critical Information Requirements (CCIR) reporting.

3.4.9 Maintain daily operations logs that shall include support problems, mission-impacting occurrences, and GBSOC significant events, at a minimum.

3.4.10 Support information assurance (IA) activities and Information Assurance Vulnerability Management (IAVM) processes to include alerts for hot fixes and system updates.

3.4.11 Assist in resolution of source product provider issues, i.e. news and sports networks.

3.4.12 Report GBS equipment deficiencies to the COR utilizing established reporting procedures and guidance IAW GBSOC OIs.

3.4.13 The GBSOC provides Tier-1 analytical service desk support up to their expertise level and if the anomalies cannot be resolved, then the GBSOC engineers provide Tier-2 support up to their expertise level. Once the GBSOC engineer’s expertise level has been exceeded, the anomalies are elevated to Tier-3 located at Ogden/OKC. Tier-2 work closely with Tier-3 until the anomalies have been resolved and all GBS services are restored.

3.4.14 Manage source integration of new File Transfer Services (FTS) sources into the SBM by adding, editing, deleting and reviewing individual accounts and profiles.

3.4.15 Establish and maintain a Service Desk knowledge management repository for knowledge identification and control.

3.4.16 Post, review, and update information in a configuration-controlled manner on the SBM Non-Classified Internet Protocol Router Network (NIPRNet) and Secret Internet Protocol Router Network (SIPRNet) web portals requiring wide dissemination to the GBS operational community. Managed content shall include but is not limited to announcements, downloadable documents and other resources, forms, frequently asked questions, useful web links, and point of contact (POC) information.

3.4.17 Reserved

3.4.18 Maintain a baseline of GBS Broadcast Segment circuit connectivity between sources, SBMs, and uplink sites.

3.4.19 Schedule, track, report, administer, and execute Authorized Service Interruption (ASI) requests under the GBSOC area of responsibility.

3.4.20 Support GBS sustaining engineering periodic testing of GBS software to include antivirus updates, security updates, and patch updates.

3.4.21 Provide GBSOC test points of contact, participate in test-based meetings, review test plans, assist test participants under routine service desk calls, rebroadcast and over-the-air software update files, and transmit log files for active test days.

3.4.22 Support a transfer of SBM production (on-line) operations between GBS SBMs no less than once annually. The transfer schedule may be disrupted by a SBM COOP event, other government directed activities, such as real-world missions, test activities, or security patches, or software installs. The SBM transfer will consists of a complete operations transfer from the production SBM actively supporting the GBS broadcast to the non-production (off-line) SBM.

3.4.23 Conduct and document GBS SBM system checks remotely from the GBSOC at a minimum of every 24-hour period.

3.4.24 Provide GBS System Information Systems Security Officer (ISSO) support to the GBS Program Office ISSO, the GBS Program Office Information System Security Manager (ISSM), IAW AFI 17-130.

3.4.25 Collect and report operational metrics for the GBSOC area of responsibility (AOR), to include the GBS SBM, SBM Infrastructure, SBM MUE, GBS transport system, and GBSOC, in the monthly status report (CDRL A201 - GBS Monthly Status Report).

CDRL A201 – GBS Monthly Status Report

3.5 System Administration

3.5.1 Provide system administration GBS servers, databases, and applications under the GBSOC area of responsibility.

3.5.2 Perform equipment and application administration on SBM Virtual Operating Environment (VOE) servers and SBM MUE.

3.5.3 Perform privileged and authorized user account management (create, modify, delete, and set access privileges) for:

3.5.4 User access to SBM Application web-based interface.

3.5.5 User non-login SBM accounts for content provider file ingest.

3.5.6 SBM VOE administrator privileged user service accounts.

3.5.7 Administrator accounts for SBM MUE managed by the GBSOC.

3.5.8 Maintain user accounts and access for Information Technology Service Management (ITSM) system (currently remedy), and other GBSOC support systems.

3.5.9 Maintain and perform reviews of audit logs for security vulnerabilities and system maintenance.

3.5.10 Perform GBS SBM and MUE database management and backups.

3.5.11 Troubleshoot and report software and database related problems.

3.5.12 Perform real world and exercise SBM transfer system administration functions under the GBSOC AOR.

3.5.13 Perform limited functional system administration for the GBSOC NIPRNet and SIPRNet workstations. Personnel with a privileged user account are required to possess a minimum Information Assurance Technical (IAT) Level 2 certification IAW Air Force Manual (AFMAN) 17-1301, COMPUTER SECURITY (COMPUSEC).

3.6 Configuration Management (CM)

3.6.1 Provide GBSOC related Operations & Maintenance (O&M) support for system engineering, configuration management, technical data management, and software sustainment activities GBSOC AOR.

3.6.2 Provide O&M support to engineering and configuration management change processes, to include monitoring Engineering Review Board and Deficiency Review Board actions.

3.6.3 Coordinate GBS and GBSOC system configuration changes with the GBS sustainment and operational organizations.

3.6.4 Perform source data provider integration actions as required by the GBS source integration processes IAW the current Global Broadcast Service (GBS) TIM Standard Operating Procedures (SOP), GBS CONOPS and SBM Operator’s Guide GBS-SBM-001.

3.6.5 Support configuration management of IAVM processes.

3.6.6 Coordinate SBM software updates and distribution.

3.7 Transfer of Operations (TOOP)

3.7.1 CDC SBM Recurring

Support a transfer of SBM production (on-line) operations between the primary CDC, which is located at OKC, and the alternate CDC located at MECH GBS SBMs. The government will be responsible for the decisions to TOOP at least once a FY. The transfer may be disrupted by a SBM COOP event or other government directed activities, such as real-world missions, test activities, security patches or software installs. The SBM transfer will consist of a complete operations transfer from the production SBM actively supporting the GBS broadcast to the non- production (off-line) SBM.

3.7.2 CDC SBM Tabletop Exercise

Conduct a government planned tabletop exercise with personnel who would be involved in an actual TOOP to include DISA once per year IAW SLA 943-USAF-GBS. Typically, tabletop exercises are conducted within one hour.

3.8 GBSOC Contingency Operations

3.8.1 Relocate and provide limited GBSOC operations within one hour of the government directive to relocate to the contingency location at Schriever SFB. Perform limited GBSOC operations using contingency SIPRNet and/or NIPRNet terminal(s) and phones provided by the government. The duration of the contingency relocation will normally not exceed 72 hours. The loss of access to the GBSOC at SSFB or loss of SIPRNet and/or NIPRNet connectivity preventing or limiting GBSOC operations will drive the government decision to direct contractor support of GBSOC operations to relocate to the contingency location. Contractor operations from the contingency location may be a precursor to a GBSOC COOP. Document contingency relocation and operations procedures.

3.8.2 GBSOC COOP (Real World Emergency)

Relocate the GBSOC mission essential functions (MEFs) with government provided GBSOC COOP capabilities within 12 hours of the government directive to COOP Mission Essential Services, and in collaboration with and under the guidance of the 21st Communications Squadron (21CS). The COOP location is at Buckley SFB, CO. Alternate COOP locations may be indicated and directed by the government based on mission needs. Additional time allowances for COOP capabilities will be considered for alternate COOP locations. The contractor will provide pre-relocation, relocation site operations, and return to normal operations support. The contractor will perform GBSOC MEFs once the GBSOC COOP is operational in response to real-world emergencies.

3.8.3 GBSOC COOP (Exercise)

A COOP exercise shall be performed at least once a FY for a duration of no more than seven days; the government will determine the duration of the exercise.

3.8.4 GBSOC COOP (Maintenance)

A COOP maintenance run will be performed at a minimum every quarter at the primary COOP site to ensure SIPR accounts are still active and to perform functions checks on equipment.

Chapter 4 Mission Systems Maintenance and Reporting

4.0 Mission Systems Maintenance

Perform corrective and preventive maintenance of mission systems identified in Table 4-1 – Mission System Listing IAW technical publications. The contractor is responsible to respond to equipment outages 24/7 unless specified otherwise.

Table 4-1 - Mission Systems Listing

Mission System Listing

Global Broadcast Service

AN/PSR-11 GBS Suitcase Portable Receive Suite AN/PSR-12 GBS Rucksack Portable Receive Suite

X

AN/TSR-11 GBS Transportable Ground Receive Suite X

GBS Satellite Broadcast Manager (SBM) Mission Unique Equipment (MUE)

Facility Uninterruptible Power System (UPS)/ System Bypass Module (SBM) Building 702 (during normal duty hours only)

X

MILSATCOM

AN/FRC-191(V)1 Family of Advanced Beyond Line-of-Sight Terminal (FAB-T) Command Post Terminal

FAB-T Data Set Manager

X

FAB-T 10FT Antenna System Tower

X

AN/GSC-52B(V)5 WGS Earth Terminal

X

AN/MSC-66 Digital Communications Satellite Subsystem

X

AN/USC-28 Spread Spectrum Multiple Access Anti-Jam (SSMA-AJ) Modem

X

Crypto Equipment

X

Interconnect Facility (ICF) Equipment

X

MD-1366/U Communication Modem

X

OM-88 (V)/G AS Modem Group

X

OM-88 A(V)1/G Protected Anti-Scintillation (AS) Anti-Jam (AJ) Wideband Net-Centric System (PAAWNS)

PAAWNS Management Component Site-Node

(PMC-S)

X

UPS/SBM Building 700

X

4.1 Maintenance

4.1.1 Mission System Maintenance

4.1.2 Repair maintain and align all equipment IAW technical order (TO)/technical manual (TM) or commercial manuals. In the event no AF TOs/TMs exists, conform to the item TO, TM, or vendor manual, in that order.

4.2 Standard Maintenance Practices

4.2.1 Identify, investigate, analyze and correct all equipment malfunctions or out of tolerance conditions. Direct and monitor maintenance actions and report equipment or system scheduled or unscheduled status changes to the Maintenance Operations Center (MOC). Report any equipment or system outages to the MOC within 15 minutes, update the MOC every two hours during extended unscheduled outages, and notify the MOC once the action is completed. Submit requests for downtime to the government in order to accomplish corrective and preventive maintenance as required.

4.3 Corrective Maintenance

4.3.1 Initiate organizational level corrective maintenance and respond to outages impacting mission within 5 minutes. Organizational level maintenance is limited by the source, maintainability, and recoverability (SMR) code as defined in the applicable system TOs. Not all equipment requiring organizational level maintenance has assigned SMR codes. The contractor will reference technical publications for specific guidance. The SBD 1 Chief of Maintenance (SBD 1/CoM) must approve all SMR change request.

4.4 Preventive Maintenance Inspection (PMI) Performance

4.4.1 Perform all PMIs IAW applicable technical publications.

4.5 Corrosion Control

4.5.1 Perform organizational level corrosion control on equipment to minimize the effects of corrosion IAW TO 1-1-689-1, TO 1-1-689-3, TO 31Z-10-37, TO 1-1-700 and MPTO 00-33A- 1001.

4.6 Test, Measurement, and Diagnostic Equipment (TMDE)

4.6.1 Comply with the Air Force Metrology and Calibration Program IAW AFI 21-113, TO 00- 20-2, TO 00-20-14, TO 33K-1-100 series, TO 33-1-27, and Precision Measurement Equipment Laboratory (PMEL) directives.

4.6.2 Operate, maintain and establish controls, for the master inventory listing of owning activity, to ensure all TMDE are repaired, calibrated and certified. Perform organizational level maintenance on TMDE. Transport TMDE between the work-center and the PMEL facility. Follow-up on all TMDE in PMEL over 30 days.

4.7 TO Accounts and Technical Publication Sets

4.7.1 Establish and maintain TO accounts and technical publication sets as required, for all assigned equipment IAW TO 00-5-1. Establish all sub-accounts through the SBD 1 Technical Order Distribution Office. Have a technical publication set in each work center under contractor control. The technical publication set shall include TOs, commercial manuals, DISA circulars, and other DISA guidelines and directives required for work center use. Verify technical documentation and initiate Air Force Technical Order (AFTO) Form 22, Technical Manual Change Recommendation, when documentation discrepancies are found IAW TO 00-5-1. These technical publication sets shall contain all work center documentation required for the performance of the requirements. Provide documentation support services for the following types of material (but not limited to):

a. Drawings.

b. Vendor submittals.

c. Commercial manuals.

d. Military and DoD standards (limited collection).

4.8 Job Data Documentation

4.8.1 Enter all maintenance actions into a maintenance information system. If the maintenance information system is not accessible, document maintenance actions on an AFTO Form 349 and ensure input into maintenance information systems when it is accessible.

4.9 Deficiency Reports

4.9.1 Perform deficiency reporting originator duties IAW TO 00-35D-54 using the Joint Deficiency Reporting System (www.jdrs.mil) or other automated information system.

4.10 Cannibalization

4.10.1 Identify and obtain cannibalization authorization from the SBD 1/CoM.

4.11 Depot Assistance

4.11.1 For equipment identified in Table 4-1 – Mission System Listing, initiate requests, coordinate, support and provide status of all depot maintenance activities. Verify depot maintenance actions are complete. Review and forward the AFTO Form 217 (or equivalent) to the appropriate unit maintenance officer or SBD 1/CoM IAW TO 00-25-108 and AFSPCI21- 108_50SWSUP.

4.12 Electro-Magnetic Interference (EMI)

4.12.1 Eliminate EMI as covered under the Spectrum Interference Resolution Program. Assist in the investigation and isolation of EMI. Investigate, identify, and report to the COR all electromagnetic interference that impacts mission support IAW applicable documents.

4.13 Crypto Equipment

4.13.1 Perform organizational maintenance on all cryptographic equipment at the locations identified in Table 4-1 – Mission System Listing and IAW with applicable Air Force Communications Security (COMSEC) General Publications (AFKAG) and COMSEC directives.

4.13.2 Perform trained primary and alternate…