DRAFT_WICS_PWS_80__28_May_13.pdf

PDF 429 KB Posted

Attached to
8(a) set-aside
Solicitation number
FA2550-13-R-8001
Issued by

About this file

Wing Information Communications Support (WICS) DRAFT Performance Work Statement 28 May 2013.

View the file

Other files

Show all 15

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DRAFT WICS PWS For Official Use Only (FOUO) Page A-1

FA2550-13-R-8001

SCHRIEVER AIR FORCE BASE (SAFB), COLORADO

WING INFORMATION & COMMUNICATIONS SUPPORT

(WICS)

DRAFT

PERFORMANCE WORK STATEMENT (PWS)

22 May 2013

DRAFT WICS PWS For Official Use Only (FOUO) Page A-2

Table of Contents WICS Scope Program Management and Quality

1.0 Program Management and Quality

1.1 General Management

1.2 Contract Performance Measurements

1.3 Personnel Management

1.4 Training

1.5 Contingencies and Emergency Support

1.6 Reimbursable Travel

1.7 Interface with Associate Contract

1.8 Program Management Support

1.9 Administrative Support

1.10 Phase-In/ Phase-Out

1.11 Projected Changes and Upgrades

Operations

2.0 Operations

Information and Communication Systems Maintenance

3.0 Information and Communication Systems Maintenance

3.1 Maintenance Operations Center (MOC)

3.2 Standard Maintenance Practices

3.3 MILSATCOM

Software and Database Support

4.0 Systems and Software Support

4.1 Systems Management

4.2 GBS System Administration

Technical Support and 50SW Configuration Management

5.0 Technical Support

5.1 Technical Analysis

5.2 Modification Support

5.3 Testing, Validation, and Verification Support

5.4 Meeting Support

5.6 50 SW Command, Control, Communications, and Computers (C4) Installation Standards and Configuration Management

Wing Information Assurance (IA) and Information/Communication Systems Support

6.0 Wing IA and Information/Communication Systems Support

6.1 50 SW Wing Level IAO

6.2 Computer Systems Support and Information Assurance Services

Security Support

7.0 Security

7.1 Contract Security Representative

7.2 Information Security Program

7.3 Personnel Clearance Requirements

7.4 Industrial Security

7.5 Operations Security

7.6 Physical Security

DRAFT WICS PWS For Official Use Only (FOUO) Page A-3

7.7 Resource Protection

Safety

8.0 Safety

8.1 Industrial Safety Program

8.2 System Safety

Logistics Support

9.0 Supply and Logistics Support

9.1 Supply Support

9.2 Logistics Support

Civil Engineering

10.0 Civil Engineering

10.1 Facility Management and Services

10.2 Emergency Management

10.3 Environmental Management

10.4 Energy Management

DRAFT WICS PWS For Official Use Only (FOUO) Page A-4

WICS Scope

The Wing Information and Communication Support (WICS) Performance Work Statement (PWS) describes the services required to operate, maintain, and logistically support 50th Space Wing (50 SW) information and communications systems identified herein. The 50 SW supports multiple programs and resources under the auspices of Air Force Space Command (AFSPC).

The scope of this PWS include potential changes to the 50 SW missions and services that may require support to a level yet to be determined (TBD). In addition, during the life of the WICS contract outside agencies may locate to Schriever Air Force Base (SAFB) that may require support under this PWS.

SAFB

SAFB is home to the 50 SW. Support is required for various Information and Communications systems and other associated organizations.

Tinker AFB, OK (OKC) The Defense Enterprise Computing Center (DECC) at Tinker AFB, OK (hereafter referred to as OKC) houses the GBS “Primary” Satellite Broadcast Manager (SBM) equipment and provides GBS Global Information Grid (GIG) network connectivity.

Mechanicsburg, PA (MECH) The DECC at Mechanicsburg, PA (hereafter referred to as MECH) houses the GBS “Backup” Continuity of Operations (COOP) Satellite Broadcast Manager (SBM) equipment and provides GBS GIG network connectivity.

Defense Satellite Communications System (DSCS) 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 DSCS to transmit space operations and early warning data to various systems and users.

For the purposes of this acquisition, the DSCS resources consist of, but are not limited to:

o Dual AN/GSC-52 terminals at SAFB o Four AN/USC-28 spread spectrum multiple access (SSMA) MODEMs o AN/MSC-66 Digital Communications Satellite Subsystem (DCSS) o OM-88 MODEMs o Interconnect Facility o AN/FRC-181 MILSTAR Command Post Terminal o S-790/FRC-181 EHF Antenna Support Shelter (EHFASS)

Global Broadcast Service (GBS) is a space-based, world-wide, high-capacity broadcast system that provides a one-way, high-speed flow of high-volume national security essential information to forces garrisoned, deployed, or on the move with small receive-only GBS terminals. GBS managed information consists of unclassified and classified video, audio, data, imagery and other information product types. GBS is divided into three segments: broadcast, space, and receive.

The broadcast segment consists of:

o Communications connectivity

DRAFT WICS PWS For Official Use Only (FOUO) Page A-5 o GBS Satellite Broadcast Manager (SBM) o Mission unique equipment (MUE) o Computer and operations center capabilities to collect, organize, control, and transmit

GBS source provider video and data products to supporting satellite uplink facilities.

The space segment consists of:

o GBS mission payloads on Ultra High Frequency (UHF) Follow-on (UFO) o Wideband Global SATCOM (WGS) satellites accessed through DISA Teleport

Gateways o Leased commercial satellites. The receive segment consists of tactical GBS unique receive terminals consisting of an antenna Received Broadcast Manager (RBM).

For the purposes of this acquisition, the GBS resources for which operations and maintenance shall be performed include:

o GBS Operations Center (GBSOC) at SAFB o GBS SBM mission unique equipment (MUE) at the Tinker AFB, OK (OKC) and

Mechanicsburg, PA (MECH) Defense Enterprise Computing Centers (DECC) facilities

Future Requirements (subject to change and not limited to):

The following is a summary of potential 50 SW requirements growth. These may require support to a level yet to be determined. This list is provided as information only and is subject to additions, deletions, and/or other changes.

• TBD

DRAFT WICS PWS For Official Use Only (FOUO) Page A-6

Chapter 1 Program Management and Quality

1.0 Program Management and Quality

The contractor shall manage the resources, personnel and services necessary to provide program management and quality, operations, maintenance, database and software support, technical support, Information Assurance (IA) and information/computer systems support, security, safety, logistics, and civil engineering support as described in this PWS. The contractor shall provide qualified, certified, and trained personnel within required timeframes and during normal and all contingency scenarios at all locations identified in this PWS. The contractor shall notify the Government Management Team (GMT) of all issues it considers not within the scope of this contract. The GMT consists of the Program Manager (PM), the Contracting Officer (CO), and the responsible Contracting Officer Representative (COR).

1.1 General Management

The contractor shall monitor program status and resolve problems with minimum impact to costs and operations performance through Contract Data Requirements Lists (CDRL) (CDRLs XXXX

- XXXX).

CDRL XXXX - Program Management Plan CDRL XXXX - Contract Performance Report CDRL XXXX - Contract Work Breakdown Structure CDRL XXXX - Contract Funds Status Report CDRL XXXX - Contract Manning Report

1.1.1 Notice

The contractor shall advise the GMT immediately of any problems affecting the contractor’s performance or impacting mission accomplishment.

1.1.2 Documentation

The contractor shall be responsible for creating, maintaining, delivering, and disposing of government-required documents, records and reports used for accomplishment of WICS requirements. If requested by the GMT, the contractor shall provide the original record or a reproducible copy of any such record within five working days of receipt of the request. All documentation, products and data developed in support of the WICS contract are the property of the US Government.

1.1.3 Contract Changes

To support an ongoing effort to maintain a PWS that reflects current site and contract conditions, the contractor shall provide quarterly PWS language changes, (CDRL XXXX). These changes include all changes to requirements identified in this PWS. The contractor shall identify equipment list changes as described in paragraph 9.1.2.3.1.

CDRL XXXX - PWS Changes

DRAFT WICS PWS For Official Use Only (FOUO) Page A-7

1.1.4 Coverage Hours

For contractor tasks that are required during normal duty hours, the contractor shall adopt a work schedule that mirrors the government’s federal work/holiday schedule.

1.2 Contract Performance Measurements

PWS performance parameters are based on meeting 50 SW mission objectives. The Services Summary (SS) is found in PWS Section TBD. The contractor shall demonstrate compliance with the SS.

1.3 Personnel Management

The contractor shall be responsible for the following aspects of personnel management.

1.3.1 Program Manager

The contractor shall provide a Program Manager (PM) designated in writing to the Contracting Officer (CO). The PM shall have full authority to act for the contractor on all matters relating to daily operations of the WICS contract. The contractor shall ensure mission requirements are fulfilled in an efficient and timely manner. The PM or authorized designee shall be available at all times for discussions via teleconference within one hour of notification and/or on-site within four hours of notification. The PM shall be able to read, write, speak, and understand English.

1.3.2 Contracting Manager

The contractor shall provide a Contracting Manager designated in writing to the CO. The Contracting Manager or authorized designee shall have the authority to review and sign all contract actions. The Contracting Manager shall be available during normal duty hours for discussions via teleconference within two hours of notification.

1.3.3 Contractor Employees

The contractor shall be responsible for personnel selection, supervision, assignment, and transfers. All contract employees who interface with the Government, either electronically or in person, shall be able to read, write, speak, and understand English. The contractor shall be responsible for selecting 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 contract. The contractor shall not employ persons for work on the WICS contract if such employees are identified to the contractor by the CO as potential threats to the health, safety, security, general well-being or operational mission of the installation and its population. The contractor shall not employ any person who is an employee of the United States Government if employing that person would create a conflict of interest. The contractor shall consider retainability of employees as part of its overall responsibility of managing the contractor workforce, especially for functions with unique qualifications, extensive training requirements, and/or security concerns.

1.3.3.1 Contractor Point of Contacts

The contractor shall maintain a listing of all key contractor management personnel, as well as, points of contacts for each site and/or system. This list shall be maintained and provided to the GMT within 30 days of contract award and when changes occur.

1.3.3.2 Contractor Conduct

Contractor personnel shall be under the direction and control of the contractor PM. They shall be subject to regulations and directives governing the activities of personnel on government installations. The site and/or installation commander may direct the contractor, in writing, to

DRAFT WICS PWS For Official Use Only (FOUO) Page A-8 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. In addition, when a mishap occurs or improper behavior is displayed by an employee, the Government reserves the right to require immediate removal of the individual from the site/installation.

1.3.3.3 Contractor Privileges

Contractor site/installation privileges are based on currently approved support agreements, as identified in PWS Section TBD, Appendix TBD of the contract. The Government retains the right to withdraw privileges at any time, without penalty.

1.4 Training

The contractor shall maintain training records for personnel, and grant the Government access to those records upon request.

1.4.1 Ancillary Training

The contractor shall participate in ancillary training as required by the work being performed and IAW applicable documentation (instructions, standards, etc.). The contractor shall establish and maintain a training document or database, or use the existing IMDS database, to track contractor ancillary training requirements. At a minimum, the document or database will reflect training due dates, training completion dates and projected due dates. The document or database will be available for government review upon request.

1.4.2 Training and Education Costs

The Government will provide for initial training and/or materials for new or modified information and communication systems and support systems. The contractor shall attend government provided specialized training (e.g., not commercially available) as directed.

Government contract actions will be initiated on a case-by-case basis if overtime is required. The contractor shall refund to the Government training and education costs for employees, who resign, are terminated or otherwise unable to perform duties they were trained for within 12 months of completion of such training or education for reasons within the employee’s control (this applies when government funds are utilized for training).

1.5 Contingencies and Emergency Support

Unless otherwise directed by the CO, the contractor shall ensure continued support at all 50 SW locations and other locations as identified in this PWS in the event of emergencies (to include natural, man-made and other emergencies), and shall continue support during all defense readiness conditions (e.g., Defense Condition (DEFCON)), threat conditions (e.g., FPCON), and alarm conditions (e.g., Alarm Black) except when there is a direct and immediate life threatening situation (e.g., the need to take shelter during a missile attack). The contractor shall prepare, review/update (minimum annually) and deliver a management contingency plan, (CDRL XXXX). The contractor shall increase the level of support during wartime and other contingencies as directed by the Government. The Government may negotiate an equitable adjustment for any additional hours worked. The contractor shall ensure that mission essential contractor personnel are identified IAW DOD Instruction (DODI) 3020.37. The contractor shall identify their mission essential contractor personnel to the Government through (CDRL XXXX).

CDRL XXXX - Management Contingency Plan CDRL XXXX - Mission Essential Contractor Personnel Designation

DRAFT WICS PWS For Official Use Only (FOUO) Page A-9

1.5.1 Exercise/Inspection Support

The contractor shall fully participate in all 50 SW exercises/inspections to the level dictated by the scenarios in progress. The contractor shall fully participate in all host base exercises and inspections, except as determined by the site commander. This support will be required on a non-mission interference basis during normal contractor duty hours. The contractor shall not increase manpower or man-hours during exercise participation unless specifically stated in this PWS or authorized by the CO.

1.5.2 Expected Delays

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

1.6 Reimbursable Travel

The contractor shall be responsible for all employee travel arrangements by commercial means.

Contractor employee travel shall be IAW current Joint Federal Travel Regulations.

Transportation may be provided by the military depending on access to bases and availability of commercial transportation. The contractor shall obtain written concurrence from the PMD, or the CO, for travel using CLIN TBD. E-mail is acceptable for written authorization when commercial travel is used.

1.7 Interface with Associate Contract

The contractor shall establish and maintain effective working relationships with associate contractors IAW Section TBD, Appendix TBD of the PWS. The contractor shall participate in contractor forums as directed by the Government.

1.8 Program Management Support

1.8.1 Quality Assurance (QA)

The contractor shall have a quality program in place to ensure all contract requirements are met.

The Government does not require the contractor to assign a Quality Assurance Manager (QAM) at each location identified in this PWS.

1.8.1.1 Inspection of Services

According to the Federal Acquisition Regulation (FAR) clauses §§52.246-4 & 52.246-5, the Government will evaluate the contractor’s performance under this contract. Government personnel will record all surveillance observations. When an observation indicates defective performance, the contractor shall initial the observation acknowledging that he or she has been made aware of the defective performance.

1.8.1.2 Quality Control Program

The contractor shall establish, through an independent function, a quality program, which shall encompass all aspects of the contract. The contractor shall include any applicable Communications Quality Control Check sheet (CQCC) that would be utilized by the various work centers. The contractor shall implement the quality program through a Quality Program Plan (QPP). The QPP shall be submitted IAW CDRL XXXX and accepted by the CO.

CDRL XXXX - Quality Program Plan

1.8.1.2.1 Quality Status Reports (QSR)

DRAFT WICS PWS For Official Use Only (FOUO) Page A-10

QSRs shall be generated on a monthly basis. Details of audits and inspections accomplished, significant deficiencies noted, trend analysis of contract performance and status of all issues yet to be resolved shall be provided. QSRs shall be distributed to the contractor's program management and government representatives, (CDRL XXXX), concurrently. At a minimum, the QSRs must include metrics, which verify whether the performance standards in the Services Summary have been met.

CDRL XXXX - Quality Status Reports

1.8.2 Management Information System

The contractor shall provide the Government access to a management information system, which consolidates all program metrics, data and knowledge. The management information system shall provide centralized access and document management, and organize documents to a single secure location that is accessible to authorized users. It shall be searchable and allow generated user interfaces based on user permissions, and include workflow tools to assist in continuous improvement of WICS artifacts.

1.8.3 Reviews, Meetings and Briefing Support

The contractor shall participate in and support conferences, seminars, and reviews in order to support the program management requirements. The contractor shall provide staff support for the development of program reviews. The contractor shall take notes and prepare conference minutes as required. The contractor shall be required to interface with various organizations or agencies and travel as needed to support these requirements

1.8.3.1 Program Management Reviews (PMR)

The contractor shall provide a PMR to the Government monthly for the first six months after contract start and quarterly thereafter. The PMRs will be held in the Colorado Springs, CO area (location will be determined by the Government). For all PMRs, the contractor shall provide the briefing content to the Government CO and 50 SW PMD at least three duty days prior to the PMR, (CDRL XXXX). The contractor shall present the first PMR within 30 days of contract start.

CDRL XXXX - Program Management Review

1.9 Administrative Support

The contractor shall provide the following support IAW Table 1-1, General Tasks:

Table 1-1 General Tasks

Para

D E C C

G B S O C

S A F B

S C S

Records Management Program Records Custodian 1.9.2.1 X X AF Records Information Management System (AFRIMS) 1.9.2.2 X X

FOIA/PA 1.9.2.3 X X

1.9.1 Publications Support

DRAFT WICS PWS For Official Use Only (FOUO) Page A-11

1.9.1.1 Contractor Operating Instructions/Operating Procedures Upon contract award, Operating Instructions (OI)/ Operating Procedures (OP) used by the incumbent contractor will be provided to the successor contractor. The successor contractor shall use, change, or develop their own. The contractor OIs/OPs shall be implemented, maintained, and complied with. All OIs/OPs required for compliance will be accepted by designated government personnel and shall be accessible when requested by the Government. Contract OIs/OPs, (CDRL XXXX), will address contract wide direction/policy. Site-Specific OIs/OPs, (CDRL XXXX), will address site-specific direction/policy. All OIs/OPs, once accepted by the Government will become directive in nature. All OIs/OPs will become the property of the Government and will be incorporated into the WICS Master Library

CDRL XXXX – Contract Operating Instructions/Operating Procedures CDRL XXXX - Site Specific Operating Instructions/Operating Procedures

1.9.1.2 New Directive Publications

The contractor shall review new/updated publications (draft and final) to assess technical content and impact to the WICS contract. The contractor shall notify the CO within 30 days of receipt if there are associated costs or potential risk impacts to the WICS contract.

1.9.1.3 Master / Bidder’s Library

The contractor shall establish and maintain a master library at a single central location, in electronic format wherever possible, containing all publications required in the performance of this PWS. The master library shall be maintained IAW AFI 33-360, AFPD 21-3, and TO 00-5-1.

The contractor shall maintain the latest basic publications, revisions, changes and supplements.

As an exception to provided guidance, the contractor shall maintain publications, which are rescinded or replaced until the replacement document has been accepted. The contractor shall maintain and provide a Master Document List (MDL), (CDRL XXXX), identifying all documents and data contained in the master library. A complete copy of the master library shall be provided as a Bidder’s Library, (CDRL XXXX), within 30 days of CO request. The contractor shall maintain the master library through the end of the contract.

CDRL XXXX – Master Document List CDRL XXXX – Bidder’s Library

1.9.2 Records Management Program

The contractor shall manage all data created for Government use or legally controlled by the Government, in support of the functional activity or required by Department of Defense Directive (DoDD) and AF publications, in accordance with 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 Instructions (AFI) 33-321, AFI 33-322, AFI 33-364, Air Force Manual (AFMAN) 33-363, AFMAN 37-104, and the Air Force Records Disposition Schedule (RDS) 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 (NAC). The contractor shall accomplish the following duties:

1.9.2.1 Records Custodian (RC):

The contractor shall provide RCs to support the requirements at each 50 SW location identified in this PWS. The contractor shall perform RC duties in order to comply with the DoD, AF Governing Directives and Air Force Records Information Management System (AFRIMS).

https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

DRAFT WICS PWS For Official Use Only (FOUO) Page A-12

1.9.2.2 Air Force Records Information Management System (AFRIMS) The contractor shall manage the AFRIMS data. The contractor shall update the AFRIMS database. The contractor Records Manager (RM) shall review the AFRIMS file plan from unit RCs and ensure compliance with official guidance within ten duty days of receipt of file plan.

1.9.2.3 Freedom of Information Act and Privacy Act

Any Freedom of Information Act (FOIA) or Privacy Act (PA) requests received by the contractor shall be forwarded to the 50 SW FOIA Manager IAW DoD 5400.7-R_AFMAN 33-302 and AFI 33-332 no later than the next workday after receipt.

The contractor shall ensure personal privacy data is protected to prevent unauthorized disclosure and ensure proper disposal.

1.10 Phase-In/ Phase-Out

1.10.1 Phase-In Plan

Upon award, the Government will provide the successful contractor the incumbent contractor’s Phase-Out Plan. The successful contractor shall deliver a Phase-In Plan, (CDRL XXXX), which complements the incumbent’s Phase-Out Plan. The contractor shall meet with the Government phase-in team to review implementation of the Phase-In Plan. The contractor shall have a complete certified, qualified, trained, and cleared workforce available in each work center (without any degradation in service) no later than contract start.

CDRL XXXX- Phase-In Plan

1.10.2 Phase-Out Plan

The contractor shall develop and implement a transition plan for Phase-Out, (CDRL XXXX).

The contractor shall establish procedures with the successors to ensure a smooth transition of all requirements. The contractor shall maintain overall contract responsibility until the completion of the contract period of performance (PoP). The contractor shall ensure all responsibilities are transferred without any degradation in service.

CDRL XXXX – Phase-Out Plan

1.11 Projected Changes and Upgrades

The 50 SW anticipates requirements growth (mission and equipment) throughout the WICS PoP.

Additionally, the 50 SW anticipates that existing systems (e.g., information, communications, and mission support) will be replaced with new systems during the WICS PoP, as identified in the Scope section of this PWS. These systems and equipment may require support to a level

TBD.

DRAFT WICS PWS For Official Use Only (FOUO) Page A-13

Chapter 2 Operations

2.0 Operations

The contractor shall perform operations activities for 50 SW locations as identified in the following chapter and in Table 6-1 IAW technical publications.

2.1 DSCS Earth Terminal Operations

The contractor shall operate the DSCS earth terminals and associated sub-systems and components located within the DSCS facility, including future upgrades, IAW Defense Information System Agency (DISA) Circular 800-70-1, DISA (EUR & PAC) DEFSTA messages, DISA (EUR & PAC) SATSTA Messages, DISA Provisioning Notices, DISA Provisioning Publications and all Technical Publications. The contractor shall comply with all instructions received from DISA, Area Operating Centers or the DSCS Operations Centers (DSCSOC) and the local TCF. The contractor will be held responsible for complying with all instructions received via the Global Terrestrial Critical Control Circuit (GT3C), and providing all requisite reports and information requested.

2.2 Milstar Air Force Command Post Terminal Operations

The contractor shall provide continuous in-facility support for operations of the MILSTAR Air Force Command Post Terminal. The contractor will provide continuous in-facility monitoring and network management of the MILSTAR Air Force Command Post Terminal.

2.3 Global Broadcast Service Operations

The contractor shall plan, schedule, direct, organize, coordinate, and execute all actions necessary to conduct operations and sustain the operability of the GBSOC at SAFB and remote administration of the DECC-PIP at NAS Sigonella, Italy from the GBSOC. Operations shall be conducted IAW publications listed in PWS Section TBD, Appendix TBD.

2.3.1 GBS Operations Center Operations

2.3.1.1 Hours of Operation

The contractor shall operate the GBSOC 24/7.

2.3.1.2 System Monitoring

The contractor shall track and monitor the overall performance of the GBS SBM and GBS NAS Sigonella DECC-PIP. The contractor shall monitor the performance of SBM broadcast functions for system and software problems, and operating condition of GBS components. The contractor shall monitor the broadcast rate of product delivery (files and streams) from the SBM to the RBMs. The contractor shall monitor all files ready for broadcast (queued), being broadcasted (transmitting), completed broadcast (sent), and status of web crawls.

2.3.1.3 Satellite Management

The contractor shall coordinate satellite payload configuration and spot beam pointing change requests. The contractor shall support GBS satellite management functions and resolution of satellite coverage, broadcast, and resource conflict issues by coordinating with GBS Theater Information Managers (TIMs) and the Regional SATCOM Support Center.

2.3.1.4 Content Management

DRAFT WICS PWS For Official Use Only (FOUO) Page A-14

The contractor manage content of GBS broadcasts by adding, editing, deleting, and viewing individual source accounts/profiles, file and streaming programs provided by sources, and mission information. The contractor shall coordinate with responsible TIMs to assign video streams to satellite transponders and to determine the appropriate data rate.

2.3.1.5 Broadcast Management

The contractor shall manage the GBS broadcast and broadcast content from the GBSOC to ensure the specified products are broadcast via the appropriate uplink facility according to schedule. The contractor shall monitor and manage GBS broadcast schedules. The contractor shall support the TIM in maintaining the accuracy of the Electronic Program Guide, Tuning Guide, and Product Catalog. The contractor shall process requests for broadcast of the GBS banner. The contractor shall prepare and distribute Mission Data Sheets to support end-user received suite configuration. The contractor shall set and monitor prioritized flow control of dynamically allocated bandwidth. The contractor shall execute GBS broadcast remote deny actions. The contractor shall manage validated GBS Mission Requests (GMR) and Satellite Access Requests (SAR) received from the GBS TIMs.

2.3.1.6 System Administration

The contractor shall provide system administration for the GBS SBM MUE equipment, databases, and applications and the NAS Sigonella DECC-PIP. The contractor shall manage GBS user and machine-to-machine accounts and access for the SBM and GBSOC mission support systems that includes but is not limited to Integrated Network Management System (INMS), Remedy, and Joint Deficiency Reporting System (JDRS). The contractor shall maintain and perform reviews of audit logs for security vulnerabilities and systems maintenance. The contractor shall collect and maintain contact information on each GBS user and source provider and assign users and assign the information to RBMs, units, sources and missions. The contractor shall provide DECC COOP real-world and exercise activation system administration functions under the GBSOC area of responsibility (AOR). The contractor shall establish a GBS RS Smart Card management program to include Smart Card purchase, end-user authorization verification, distribution, entitlement, and un-assignment. System administrators with elevated privileges must be certified IAW AFMAN 33-285. Contact Wing IA 8570 monitor for guidance.

2.3.1.7 End User Help Desk Service

The contractor shall provide end user Help Desk and technical assistance support through telephone consultation and problem resolution to fielded GBS receive suite end users from the GBSOC. The contractor shall provide Help Desk operators who are fully qualified on all aspects of GBS program provisioned receive suites to include both physical and operational.

2.3.1.8 Service Desk Support

The contractor shall operate the GBSOC Service Desk as the operational focal point for GBS daily broadcast and operations services. The contractor shall provide event and incident management troubleshooting, coordination tracking, notification, and reporting of service interruptions, circuit outages, approved changes, and scheduled maintenance. The contractor shall provide request fulfillment services from the GBS user community using consistent and repeatable methods, for which pre-defined approval methods exists, such as establishing SBM user accounts and issuing Smart Cards. The contractor shall report health and status information through the proper chain of command as determined by GBSOC Command and Control (C2).

The contractor shall log, prioritize, investigate, resolve, and report problems using a service management system. The contractor shall maintain daily operations logs that shall include

DRAFT WICS PWS For Official Use Only (FOUO) Page A-15 support problems, outages, and mission-impacting occurrences. The contractor shall maintain situational awareness of GBS terrestrial and SATCOM services through the Integrated Network Management System (INMS) and other sources. The contractor shall assist in resolution of source provider issues. The contractor shall provide Service Desk knowledge management base repository for knowledge identification and control. The contractor shall develop and maintain email distribution lists to inform targeted GBS groups. The contractor shall use GBSOC portal capabilities for posting system status information requiring wide dissemination. The contractor shall maintain a baseline of GBS Broadcast Segment circuit connectivity between sources, DECC, and satellite ground terminals. The contractor shall schedule, track, report, and execute Authorized Service Interruption (ASI) requests under the GBSOC area of responsibility.

2.3.1.9 Documentation

The contractor shall develop Standard Operating Procedures that address all aspects of GBSOC operations.

2.3.1.10 Training

The contractor shall administer a training program to maintain sufficient levels of fully-qualified and proficient operators through an approved certification/qualification process.

2.3.1.11 Software Updates

The contractor shall distribute Information Assurance Vulnerability Alerts (IAVA) updates directly to the GBS NAS Sigonella DECC-PIP. The contractor shall coordinate Satellite Broadcast Manger (SBM) software updates and distribution. The contractor shall distribute over-the-air software updates to Receive Broadcast Manager (RBM). The contractor shall monitor fielded RBM IAVA status.

2.3.2 50 SCS GBS Relocation Support The contractor shall provide required support to all 50 SW units, as identified in this PWS, when relocated to their back-up facilities. During emergencies, exercises, and scheduled events the contractor shall perform relocation operations in support of the 50 SW, to include relocating and bringing the back-up facility to a fully operational capability within 24 hours of notification, unless otherwise specified below. The contractor shall be required to provide pre-relocation support at the back-up facility prior to the full relocation team’s arrival, where applicable.

2.3.2.1 GBSOC Relocation Support

For GBSOC, the alternate operating location resides at TBD. The government estimates one planned relocation per year, approximately one week in duration. Planned relocations will be conducted IAW the GBSOC Continuity of Operations Plan (COOP).

2.3.2.2 GBS DECC Relocation Support

For GBS DECC, the primary site at OKC will relocate to the fully redundant secondary facility at Mechanicsburg, PA. The government estimates one planned relocation per year, approximately one week in duration. Planned relocations will be conducted IAW the GBS

DECC COOP.

DRAFT WICS PWS For Official Use Only (FOUO) Page A-16

Chapter 3 Information and Communication Systems Maintenance

3.0 Information and Communication Systems Maintenance

The contractor shall perform corrective and preventive maintenance of all 50 SW information and communications equipment and systems identified in table 3-1 IAW technical publications.

The contractor is responsible to respond to equipment outages 24/7 unless specified otherwise.

Table 3-1 Information and Communication Systems Listing G

B S O C

O K C

M E C H

S A F B

Global Broadcast Service AN/TSR-8 GBS Receive Suite X AN/TSR-9 GBS Receive Suite X AN/TSR-10 GBS Receive Suite X

GBS MUE X X

MILSATCOM

AN/GSC-52A(V)2/G DSCS Medium Earth Terminal X AN/USC-28 Spread Spectrum Multiple Access Anti-Jam (SSMA-AJ) Modem

X

AN/GSC-51 DSCS FDMA Control System X AN/MSC-66 Digital Communications Satellite Subsystem X Crypto Equipment X OM-88 (V)/G AS Modem Group X Interconnect Facility (ICF) Equipment X AN/FRC-181 MILSTAR Command Post Terminal X S-790/FRC-181 Extremely High Frequency Antenna Support Shelter (EHFASS) X

3.1 Maintenance Operations Center (MOC)

The MOC serves as the 24/7 central point of contact for 50 SW operations and maintenance and is located at SAFB. The contractor shall operate the 50 SW MOC IAW Air Force Space Command Instruction (AFSPCI) 21-108, Chapter 6, paragraph 6.1 thru 6.1.11.4 and 6.2.6.

Additionally the contractor shall:

• Document and report system or equipment status according to AFI 21-103, Chapter 6.

• Up-channel incident and status reporting as directed by the Government

• Transfer problem resolution responsibility between maintenance agencies and track resolution status, as required.

• Receive Mission Impact Reports (MIR), notify maintenance personnel as required and document equipment status/malfunctions into the MPR government provided database.

• Enter maintenance data into IMDS for IMDS reportable systems.

• Enter maintenance data into the MPR database for non-IMDS reportable systems as identified by the Government.

DRAFT WICS PWS For Official Use Only (FOUO) Page A-17

• Assign, track, and document status for all Job Control Numbers (JCN), track equipment and maintenance status, request assistance from supporting agencies, coordinate maintenance and supply requests and disseminate information.

• Monitor power outages impacting mission operations and equipment.

• Process Urgent Depot Level Maintenance (UDLM) requests within X minutes of receipt and Emergency Depot Level Maintenance (EDLM) requests within 5 minutes of receipt IAW TO 00-25-108, applicable supplements and 50 SW Instruction 21-106.

• The contractor shall review and update open outage data in applicable Maintenance Information Systems daily for all assigned 50SW mission systems.

3.2 Standard Maintenance Practices

The contractor shall maintain equipment and systems as identified in technical publications unless identified in the associated paragraphs. The contractor shall identify, investigate, analyze and correct all equipment malfunctions or out of tolerance conditions. The contractor shall direct and monitor maintenance actions and report equipment or system scheduled or unscheduled status changes to the MOC. The contractor shall 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. When required, the contractor shall submit requests for downtime to the government in order to accomplish corrective and preventive maintenance.

3.2.1 Corrective Maintenance

The contractor shall 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 technical orders. Not all equipment requiring organizational level maintenance has assigned SMR codes.

The contractor will reference technical publications for specific guidance.

3.2.2 Preventive Maintenance Inspection (PMI) Performance

The contractor shall perform all PMIs IAW applicable technical publications.

3.2.3 Corrosion Control

The contractor shall perform organizational level corrosion control on all 50 SW 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 Methods and Procedures Technical Order (MPTO) 00-33A-1001 (paragraph 6.2.3).

3.2.4 Test, Measurement, and Diagnostic Equipment (TMDE)

The contractor shall 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, host base PMEL directives. The contractor shall maintain the Master Inventory Listing of owning activity TMDE provided by the supporting PMEL. The contractor shall operate and establish controls to ensure all TMDE is repaired, calibrated, and certified. The contractor shall perform organizational level maintenance on TMDE. The contractor shall transport TMDE between the work-center and the PMEL facility. The contractor shall follow-up on all TMDE in PMEL over 30 days.

3.2.5 TO Accounts and Technical Publication Sets

The contractor shall establish and maintain technical order accounts and technical publication sets as required, for all assigned equipment IAW TO 00-5-1. The contractor shall establish all sub-accounts through the 50 SW Technical Order Distribution Office (TODO). The contractor shall have a technical publication set in each work center under contractor control. The technical

DRAFT WICS PWS For Official Use Only (FOUO) Page A-18 publication set shall include technical orders, commercial manuals, DISA circulars, and other DISA guidelines and directives required for work center use. The contractor shall verify technical documentation and initiate Air Force Technical Order (AFTO) Form 22 change requests when documentation discrepancies are found IAW TO 00-5-1. These technical publication sets shall contain all site-specific documentation required for that site. The contractor shall provide documentation support services for the following types of material (but not limited to):

• Drawings.

• Vendor submittals.

• Commercial manuals.

• Military and DoD standards (limited collection).

• ICD

3.2.6 Job Data Documentation (JDD)

The contractor shall enter all maintenance actions into IMDS. If IMDS connectivity is interrupted, the contractor shall document maintenance actions and ensure input into IMDS as soon as connectivity is restored. In addition, the MOC will provide the work centers with IMDS Equipment Inventory List (EIL) to the system or subsystem level. The contractor shall verify the EIL semi-annually to verify that the IMDS data is consistent with physical resources under the contractor’s control. Work centers shall notify the MOC if changes are required. The MOC will update the EIL with applicable information. IMDS data is identified as Equipment Designator, Equipment ID, System Reference Designator (SRD), and Work Unit Codes associated with the equipment. The contractor shall accomplish historical data documentation in IMDS IAW MPTO 00-33A-1001, paragraph 7.6.

3.2.7 Deficiency Reports

The contractor shall perform deficiency reporting originator duties IAW TO 00-35D-54 using the Joint Deficiency Reporting System (www.jdrs.mil) or other automated information system as directed by the government.

3.2.8 Cannibalization

The contractor shall identify and obtain cannibalization authorization from the 50 SW Chief of Maintenance (COM).

3.2.9 Organizational Maintenance of Radomes and Base Rings

The contractor shall provide organizational level maintenance of the Military SATCOM (MILSATCOM) radomes and base rings.

3.2.10 Depot Assistance

The contractor shall initiate requests, coordinate, support and provide status of all depot maintenance activities IAW TO 00-25-108 and 50 SWI 21-106.

3.2.10.1 The contractor shall verify depot maintenance actions are complete. The contractor shall review and forward the AFTO Form 217 (or equivalent) to the appropriate unit maintenance officer (MA) or COM IAW TO 00-25-108 and 50 SWI 21-106.

3.2.11 Uninterruptible Power Supplies (UPS)

The contractor shall operate and provide daily visual inspection of UPS and battery room for alarms, overheating of rooms or battery leaks.

http://www.jdrs.mil/

DRAFT WICS PWS For Official Use Only (FOUO) Page A-19

3.2.12 EMI

The contractor shall eliminate EMI within their control as covered under the Spectrum Interference Resolution Program (AFI 10-707 and AFSPC Supplement 1 to AFI 10-707). The contractor shall assist in the investigation and isolation of EMI outside of their control. The contractor shall investigate, identify, and report all electromagnetic interference that impacts mission supports IAW documents listed in PWS Section TBD, Appendix TBD.

3.2.13 Crypto Equipment

The contractor shall provide trained personnel to perform organizational maintenance on all cryptographic equipment at the locations identified in Table 7-1 and IAW with applicable Air Force COMSEC General Publications (AFKAG) and COMSEC directives.

3.2.14 Self-Sufficiency Program

The contractor shall coordinate all self-sufficiency efforts with the 50 SW COM.

3.2.15 Certification of Special Equipment

The contractor is authorized to use local purchase procedures identified in PWS Chapter 9, Paragraph 9.1.3, for certification of special equipment (e.g. cranes, lifts, climbing gear) IAW equipment specifications, AFOSH, OSHA, International, Federal and/or State standards, whichever is most stringent.

3.3 MILSATCOM

3.3.1 DSCS

The contractor shall maintain threshold and performance objectives IAW DISA Circulars. The contractor shall maintain the DSCS Earth Terminals and associated sub-systems and components located within the DSCS facility, including future upgrades, IAW Chapter 3 of this PWS and DISA Circular 800-70-1.

3.3.1.1 Master Station Log

The contractor shall maintain a Master Station Log.

3.3.1.2 High-Altitude Electromagnetic Pulse (HEMP)

SAFB MILSATCOM Building 700 is a HEMP certified facility. The contractor will not make any modifications to the facility or equipment HEMP protection features without obtaining written authorization from the SAFB HEMP Program Manager. The contractors shall perform initial and annual refresher HEMP training. Training material will be provided by the SAFB HEMP Program Manager. Contractor will document training in their training program.

3.3.2 Milstar Air Force Command Post Terminal

The contractor shall provide continuous in-facility support for operations, monitoring, network management and maintenance of the Milstar Air Force Command Post Terminal at SAFB. The contractor shall maintain threshold and performance objectives IAW the Joint Operational Requirements Document-Milstar Communications System.

3.3.3 Global Broadcast Service

For DECC locations, the contractor will provide on-call support with a two hour on-site response time. When directed by the government, the contractor shall modify the work schedule to support maintenance requirements.

DRAFT WICS PWS For Official Use Only (FOUO) Page A-20

Chapter 4 Software and Database Support

4.0 Systems and Software Support

The contractor shall provide systems management and operations verification support to all 50 SW communications, mission and mission support systems identified in Table 8-1 and IAW publications listed in PWS, Section TBD, Appendix TBD or commercial manuals if not specified in Appendix TBD.

4.1 Systems Management

4.1.1 The contractor shall troubleshoot and analyze problems by executing all government approved procedures/processes necessary to restore operations.

4.1.2 Software and Database Installation and Checkout (I&C)

The contractor shall install, checkout, and de-install as needed all changes/updates to all 50 SW mission systems and peripheral devices. The contractor shall implement these changes into operational systems.

4.1.2.1 The contractor shall submit an Authorized Service Interruption (ASI) request to the government identifying resources and schedule requirements for required software updates. The contractor shall provide a realistic installation timeline to the Government and shall adhere to the government-approved installation schedule.

4.1.2.2 The contractor shall notify the government immediately of any problems with an Installation and Checkout and make recommendations for corrective actions to include de-install of the package to return the system to the operational configuration if directed by the applicable government configuration control authority. The contractor will document installation problems in an installation problem report, (CDRL XXXX).

CDRL XXXX – Installation and Checkout Problem Report

4.1.3 Systems Performance Trending and Analysis

The contractor shall monitor performance data of systems. The contractor shall analyze any trends which indicate degradation of equipment or that the system is not performing to specifications (e.g. error codes, error messages, and invalid output products). The contractor shall notify the Government of negative trends and make recommendations for modifications of operating system parameters to optimize overall system performance and meet current and future operational needs. Once identified, all applicable supporting data will be submitted to the government. The contractor shall enter the problem into the government approved problem report database within 1 business day.

4.2 GBS System Administration

Systems administration services refer to the support of operating systems software, applications software, systems management software, systems security software and supporting software structure to include firmware.

4.2.1 The contractor shall manage systems computers, workstations, terminals, and associated equipment to allow users access to data and computer applications software. The contractor shall perform user account management (create, modify, delete, and set access privileges), as approved by the government. The contractor shall maintain and perform reviews of audit logs for security vulnerabilities and system maintenance.

DRAFT WICS PWS For Official Use Only (FOUO) Page A-21

4.2.2 The contractor shall perform data storage and file management IAW daily, weekly, and monthly government identified procedures for mission systems listed on Table 8-1.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .