36C10A-19-R-0008-020.pdf

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Enterprise Satellite Program Office

Enterprise Satellite Communications Operations

Date: July 12, 2019

Amended August 9, 2019

TAC-20-52908

PWS Version Number: 1.0

Contents

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.1.3 QUALITY CONTROL PLAN

5.1.4 KICK-OFF MEETING

5.1.5 MONTHLY CONFERENCE CALLS

5.1.6 TRANSITION PLANS

PHASE IN PLAN

PHASE-OUT PLAN (OPTIONAL TASK)

5.2 ENTERPRISE SATCOM REQUIREMENTS

5.2.1 SPACE SEGMENT BANDWIDTH REQUIREMENT

5.2.2 HUB EQUIPMENT

5.2.3 VSAT TERMINALS

VEHICLE MOUNTED UNITs (VMUs), MAN PORTABLE UNITs (MPUs), and FIXED TERMINALS

FIRST-RESPONDER SATELLITE UNITS

RUGGEDIZED STORAGE CONTAINERS

5.3 TWO-PHASE ENTERPRISE SATCOM TRANSITION AND DEPLOYMENT... 21

5.4 ENTERPRISE SATCOM OPERATIONS

5.4.1 HELP DESK SUPPORT

5.4.2 HUB OPERATIONS

5.4.3 VSAT AND FRU OPERATIONS

5.4.4 EMERGENCY OPERATIONS SUPPORT

5.4.5 NATIONAL DRILLS & FIELD SUPPORT

NATIONAL DRILLS SUPPORT

ON-SITE FIELD SUPPORT

5.5 ENTERPRISE SATCOM MAINTENANCE

5.6 AUTHORITY-TO-OPERATE (ATO) SUPPORT

5.7 TRAINING REQUIREMENT

5.7.1 VSAT AND FRU TRAINING

5.7.2 ANNUAL REFRESHER VSAT AND FRU TRAINING (Option Years only)

5.8 OPTIONAL TASKS

5.8.1 UPGRADE TERRESTRIAL LINK TO 50MB (OPTIONAL TASK)

5.8.2 UPGRADE TERRESTRIAL LINK TO 100MB (OPTIONAL TASK)

5.8.3 ADDITIONAL VEHICLE MOUNTED UNIT (VMU) VSAT TERMINALS

(OPTIONAL TASK)

5.8.4 ADDITIONAL FIRST-RESPONDER SATELLITE TERMINALS

(OPTIONAL TASK)

5.8.5 INCREASE BANDWIDTH SURGE CAPABILITY TO 6MHz (OPTIONAL

TASK)

5.8.6 INCREASE BANDWIDTH SURGE CAPABILITY TO 8MHz (OPTIONAL

TASK)

5.8.7 INCREASE BANDWIDTH SURGE CAPABILITY TO 12 MHz (OPTIONAL

TASK)

5.9 OPTION PERIODS

5.9.1 OPTION PERIOD 1

5.9.2 OPTION PERIOD 2

5.9.3 OPTION PERIOD 3

5.9.4 OPTION PERIOD 4

5.9.5 OPTION PERIOD 5

5.9.6 OPTION PERIOD 6

5.9.7 OPTION PERIOD 7

5.9.8 OPTION PERIOD 8

5.9.9 OPTION PERIOD 9

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

6.1.2 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

6.1.4 TRUSTED INTERNET CONNECTION (TIC)

6.1.5 STANDARD COMPUTER CONFIGURATION

6.1.6 VETERAN FOCUSED INTEGRATION PROCESS (VIP)

6.1.7 PROCESS ASSETT LIBRARY (PAL)

6.1.8 AUTHORITATIVE DATA SOURCES

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 SERVICE LEVELS

6.5.1 SERVICE LEVEL FRAMEWORK

6.5.2 SERVICE LEVEL REQUIREMENTS

SYSTEM SERVICE LEVEL REQUIREMENT (SLA)

OPERATIONS / MAINTENANCE SLA

HELP DESK SLA

TRAINING SLA

6.6 FACILITY/RESOURCE PROVISIONS

6.7 GOVERNMENT FURNISHED PROPERTY

6.8 SHIPMENT OF HARDWARE OR EQUIPMENT

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM

SECURITY/PRIVACY LANGUAGE

1.0 BACKGROUND

Within the last decade, there have been significant hurricanes and tropical depressions, which have impacted the United States (U.S.): Sandy, Irene, Matthew, Jose, Florence, Maria, Irma Harvey and Isaac. Hurricane Isaac was responsible for significant devastation of the U.S. East Coast. Hurricane Harvey caused an estimated $125 Billion worth of damage and hurricane Florence an estimated $40 billion dollars’ worth of damage to the Gulf Coast states. More recently Texas, Florida, and Puerto Rico have been severely impacted. In almost all cases, because of these storms, service to our patients was disrupted due to the damaging effects. There has also been attention given to the risk of a potential Pandemic disease outbreak.

In 2013 and again in 2017 the Federal Emergency Management Agency (FEMA) released the Federal Continuity Directives (FCD-1 and FCD-2) requiring all federal executive branch departments to be able to perform all National Essential Functions (NEFs) during all hazards, emergencies or situations that may disrupt normal operations.

In light of these facts and close evaluation of after-action reports, the Office of Information and Technology (OIT) identified a need to develop an Enterprise Satellite Communications (SatCom) infrastructure. The Enterprise SatCom Infrastructure consists of the Very Small Aperture Terminal (VSAT) hubs, VSAT terminals, First- Responder Units (FRU) operating on the same space segment (Ku-Band transponder bandwidth), and a terrestrial segment (teleport collocation services) to support VA continuity of operations for data, voice, and video communications. As OIT continues to integrate regional and national data processing centers, it becomes even more critical that the Veterans Health Administration (VHA), Veterans Benefits Administration (VBA), and National Cemetery Administration (NCA) implement comprehensive contingent communications networks in support of consolidated operations.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements For Cryptographic Modules”

4. FIPS Pub 199. Standards for Security Categorization of Federal Information and Information Systems, February 2004

5. FIPS Pub 200, Minimum Security Requirements for Federal Information and

Information Systems, March 2016

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and

Contractors,” August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

8. Carnegie Mellon Software Engineering Institute, Capability Maturity Model®

Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010

9. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

10. Public Law 109-461, Veterans Benefits, Health Care, and Information

Technology Act of 2006, Title IX, Information Security Matters

11. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

12. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, http://www.va.gov/vapubs/

13. VA Handbook 0710, Personnel Security and Suitability Security Program, May 2, 2016, http://www.va.gov/vapubs

14. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008

15. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility

Standards,” July 1, 2003

16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016

17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”

18. An Introductory Resource Guide for Implementing the Health Insurance

Portability and Accountability Act (HIPAA) Security Rule, October 2008

19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017

20. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

21. VA Directive 6500, “Managing Information Security Risk: VA Information

Security Program,” September 20, 2012

22. VA Handbook 6500, “Risk Management Framework for VA Information

Systems – Tier 3: VA Information Security Program,” March 10, 2015

23. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008

24. VA Handbook 6500.2, “Management of Breaches Involving Sensitive

Personal Information (SPI)”, July 28, 2016

25. VA Handbook 6500.3, “Assessment, Authorization, And Continuous

Monitoring Of VA Information Systems,” February 3, 2014

26. VA Handbook 6500.5, “Incorporating Security and Privacy in System

Development Lifecycle”, March 22, 2010

27. VA Handbook 6500.6, “Contract Security,” March 12, 2010

28. VA Handbook 6500.8, “Information System Contingency Planning”, April 6,

29. OI&T Process Asset Library (PAL), https://www.va.gov/process/ . Reference

Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

30. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

31. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014 http://www.va.gov/vapubs/ http://www.va.gov/vapubs http://www.va.gov/vapubs https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

32. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

33. VA Handbook 6510, “VA Identity and Access Management”, January 15,

34. VA Directive 6300, Records and Information Management, February 26,

35. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

36. NIST SP 800-37 Rev 1, Guide for Applying the Risk Management

Framework to Federal Information Systems: a Security Life Cycle Approach, June 5, 2014

37. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

38. OMB Memorandum, “Transition to IPv6”, September 28, 2010

39. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, October 26, 2015

40. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, March 24, 2014

41. OMB Memorandum M-06-18, Acquisition of Products and Services for

Implementation of HSPD-12, June 30, 2006

42. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

43. OMB Memorandum 05-24, Implementation of Homeland Security

Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, August 5, 2005

44. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3,

45. OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation, May 23, 2008

46. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

47. NIST SP 800-116 Rev 1, Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access, June 2018

48. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

49. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, June 2017

50. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

51. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile

Devices (Draft), October 2012

52. Draft National Institute of Standards and Technology Interagency Report

(NISTIR) 7981 Mobile, PIV, and Authentication, March 2014

53. VA Memorandum, VAIQ #7100147, Continued Implementation of Homeland

Security Presidential Directive 12 (HSPD-12), April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514) https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514

54. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

55. VA Memorandum “Mandate to meet PIV Requirements for New and Existing Systems” (VAIQ# 7712300), June 30, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846

56. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017, https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017 .pdf

57. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

58. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name System Infrastructure, August 22, 2008

59. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)

60. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

61. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

62. Executive Order 13834, “Efficient Federal Operations”, dated May 17, 2018

63. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August

2, 2001

64. VA Directive 0058, “VA Green Purchasing Program”, July 19, 2013

65. VA Handbook 0058, “VA Green Purchasing Program”, July 19, 2013

66. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

67. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

68. VA Memorandum, “Implementation of Federal Personal Identity Verification

(PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

69. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

70. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015;

https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

71. “Veteran Focused Integration Process (VIP) Guide 3.1”, April 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

72. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846 https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411

73. “POLARIS User Guide”, Version 1.9, March 2017, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

74. VA Memorandum “Use of Personal Email (VAIQ #7581492)”, April 24, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

75. Attachment A – SatCom Locations

76. Attachment B – VSAT Master Inventory List

77. Attachment C – VSAT Equipment Configuration

78. Attachment D – Location for Ruggedized Storage Containers

3.0 SCOPE OF WORK

The Contractor shall replace the existing SatCom equipment and provide a managed service for the Department of Veterans Affairs (VA) Enterprise SatCom infrastructure. The Contractor shall provide satellite transponder access, operation, Radio Frequency (RF) chain components, teleport collocation services, hub operation and hub hardware / firmware components, VSAT and First Responder Units required to deliver private dedicated Enterprise SatCom services agency wide.

The Contractor’s managed service shall provide the following services:

A. Program management support.

B. Transition plans delineating the Phase-In and Phase-Out approaches.

C. Operate and maintain satellite transponder and terrestrial operations (with exception of VSATs. VSATs will be operated by VA personnel).

D. Emergency support during nationally declared disasters.

E. Support hardware and software maintenance.

F. Vulnerability remediation.

G. Support on-site and remote training.

H. Perform updates/replacements of hardware and software.

I. Authority to Operate (ATO) Documentation Support.

J. Remote and on-site support.

K. Help desk services.

L. Engineering support to make changes as required by Government security directives.

M. Provide Lifecycle Refresh

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The period of performance (PoP) shall consist of one 12-month base period followed by nine 12-month option periods (if exercised).

There are ten (10) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, four are set by date:

https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

New Year's Day January 1 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities and at VA facilities as listed in Attachment A

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the period of performance (PoP). The contractor shall include all estimated travel costs in the firm-fixed price line items. These costs will not be separately reimbursed by the Government.

VA anticipates a total of six (6) discretionary visits per year (Base and Option periods) with duration of two (2) days each. The Contractor shall account for no more than two

(2) personnel per trip. Historically this has been to a location within the 48 contiguous states although Puerto Rico and Hawaii, and Alaska are within the service area.

Travel to Enterprise SatCom locations requires prior approval from the Contracting Officer’s Representative (COR).

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP shall take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated monthly thereafter. The Contractor shall update and maintain the VA Project Manager (PM) approved CPMP throughout the period of performance.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the VA PM and COR with Monthly Progress Reports in electronic form in Microsoft Word and Microsoft Excel formats. Each report shall reflect project progress status as of the last day of the preceding month. Each Monthly Progress Report shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

Deliverable:

A. Monthly Progress Report

5.1.3 QUALITY CONTROL PLAN

The Contractor shall provide a Quality Control Plan that contains, at a minimum, the items listed below and shall be submitted to the CO and COR for acceptance not later than the post award conference.

The Contractor shall provide a plan that includes:

A. A description of the Quality Control Plan to cover all services listed on the performance requirements metrics (See section 6.4 Performance Metrics Section). The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspectors.

Additionally, control procedures for any government-provided keys or lock combinations must be included.

B. A description of the methods to be used for identifying and preventing defects in the quality of service performed.

C. A description of the records to be kept to document inspections and corrective or preventive actions taken.

The records of inspections shall be kept and made available to the CO and the COR, when requested, throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

A. Quality Control Plan

5.1.4 KICK-OFF MEETING

The Contractor shall schedule and a provide proposed agenda for the Kick-Off Meeting to be held within ten (10) business days after contract award or as agreed upon between the Enterprise SatCom Program Office (ESPO), Contracting Officer and the Contractor. In the Kick-Off Meeting the Contractor shall address post-award topics and provide a presentation to the ESPO team of the Contractor’s plan and approach for meeting all PWS requirements. This shall include review of the CPMP and any outstanding comments from the Contracting Officer, COR/PM on the CPMP.

The Kick-Off Meeting shall be a virtual meeting. At the conclusion of the Kick-Off Meeting the Contractor shall provide the VA PM and COR with the minutes.

Deliverable:

A. Kick-Off Meeting Minutes

5.1.5 MONTHLY CONFERENCE CALLS

The Contractor shall setup and coordinate on behalf of the VA PM monthly conference calls with representatives from the ESPO and the COR. The purpose of these monthly conference calls is to keep the ESPO team abreast of the current status of activities being performed on this contract, discuss pending issues (including actions being taken to resolve problems), and to provide project related recommendations. The Contractor shall document the relevant information resulting from these monthly conference calls in the Monthly Progress Report (refer to Section 5.1. 2).

5.1.6 TRANSITION PLANS

PHASE IN PLAN

The Contractor shall participate in Phase-In discussions/meetings and work closely with ESPO staff and the current out-going VSAT Contractor(s) to work out any residual transitioning topics to kick start this contract. The Contractor(s) shall replace all equipment and services within 160 calendar days of December 1, 2019.

The Contractor shall provide a detailed transition plan that includes:

A. Roster of key POCs with name, role, email address, and telephone numbers.

B. Transition timeline with key milestones.

C. Procedural manuals/guidelines.

D. Templates used in day-to-day operations.

E. Itemized list of additional equipment to be provided.

F. Estimated downtime by site and units (hub or terminal).

G. Process for transfer of on-hand inventory, if applicable.

H. Transition checklist.

I. Signed turnover agreements, if applicable.

J. System design plan.

K. Network architecture plan.

A. Phase-In Transition Plan

PHASE-OUT PLAN (OPTIONAL TASK)

At the end of this contract, the Contractor is expected to participate in Phase-Out discussions/meetings and work closely with ESPO staff and the incoming Contractor(s) to work out any residual transitioning topics require to help kick start the future contract.

The Contractor shall provide a detailed Phase-Out Transition Plan that includes:

A. Roster of key POCs with name, role, email address and telephone numbers.

B. Transition timeline with key milestones.

C. Procedural manuals/guidelines.

D. Templates used in day-to-day operations.

E. Itemized list of additional equipment to be provided.

F. Estimated downtime by site and units (hub or terminal).

G. Process for transfer of on-hand inventory, if applicable.

H. Transition checklist.

I. Signed turnover agreements, if applicable.

J. System design plan.

K. Network architecture plan.

A. Phase-Out Transition Plan

5.2 ENTERPRISE SATCOM REQUIREMENTS

VA currently utilizes Enterprise SatCom infrastructure inclusive of the satellite transponder operation, Radio Frequency (RF) chain components, teleport collocation services, hub operation, and hub hardware / firmware components required to deliver private dedicated Enterprise SatCom services agency-wide. VA Enterprise SatCom infrastructure consists of two ground stations referred to as hubs. One hub serves as the primary hub and the other serves as the redundant hub. VA Enterprise SatCom infrastructure also consists of 229 terminals (VSATs). Of these 229 terminals, two are fixed and 227 are mobile. These are deployed throughout VA enterprise networks (refer to Attachment A). The Contractor’s VA Enterprise SatCom infrastructure managed service shall provide all equipment and services to replace the existing system with a new Enterprise SatCom infrastructure and provide operations support including continuity of operations and deployment of all systems to enable mobile communications. The Enterprise SatCom infrastructure shall operate to provide voice, video and data communications services via IP (Internet Protocol) to support Veterans’ medical care and emergency communications.

Currently (Contractor may determine different hub locations), Two Enterprise SatCom hubs are deployed at Southbury, Connecticut (UT) and Brewster, Washington (WA). Addresses for the CT and WA Facilities are identified below:

Enterprise SatCom Hub Site #1 2120 River Road Southbury, CT 06488

Enterprise SatCom Hub Site #2 66c Teleport Dr.

Brewster, WA 98812

If the Contractor chooses to move hub operations to a different location, the Contractor shall ensure continuity of services of all existing systems and be operational with no impact to the mission during the transition phase. Details shall be provided in the Phase-In Transition Plan. The Contractor shall be responsible for moving and re-install all Government owned equipment to the new teleport location and allocate up to 90 days for Government to provide the terrestrial links between the two VSAT ground stations and the VA Network.

As part of the VSAT hubs operation, the Contractor shall replace a primary and a secondary ground station (hub) for redundancy purposes. As part of redundancy, these VSAT hubs must be at least 500 miles apart geographically and reside in different time zones. Each hub location shall meet the following physical commercial facility (hub) security requirement to include providing controlled access with locked doors, surveillance camera system (with sufficient video storage up to 48 hours), security wired fence surrounding the hub premise, visitor access control point (all visitors must be log in prior to entrance), and visitor escort within the premise. Government equipment shall be located within a locked enclosure accessible by only authorized personnel.

All Control terrestrial links (, inband and out of band management) to and from the Hub equipment shall be encrypted with FIPS 140-2, level 2 or better NIST certified 256-bit encryption.. All satellite communications equipment will be FIPS 140-2, level 2 NIST certified or better. All Wireless Access Points will be FIPS 140-2, level 2 NIST certified or better. Proof of certification and configuration is required.

The Contractor shall update and maintain software, hardware, and licenses for the new Enterprise SatCom infrastructure by supporting existing and future circuit requirements. The Contractor shall provide and maintain the dedicated private satellite network operating on at least 36 MHz of space segment on the transponder defined in Section 5.2.1

For informational purposes, the current hub baseline is the following:

A. The outbound carriers operate at a throughput of 17.5 Mbps.

B. There are thirteen inbound carriers that operate between one to four Mbps

The inbound and outbound bandwidth shall be reconfigurable to accommodate larger carriers, dependent on need and link budget calculation. The Government may request the transponder inbound and outbound settings be adjusted several times (historically there has been no more than five occasions a year) during the course of the contract. These changes shall occur within two hours of the request. However, more than five may be required.

The Contractor shall provide a 20 Mb terrestrial link with upgrade options for 50Mb and 100Mb to the Internet at each hub location so the VSAT units can have direct Internet access. The Contractor shall provide Network Address Translation (NAT) and/or Port Address Translation (PAT) to permit private IP addresses on the VSAT terminals to access the Internet.

The Contractor shall provide all back-end services required for the operation of Session Initiation Protocol (SIP) phones connected to the remote terminals (VSATs). The SIP and analog phones must operate 100% independently of the VA Network.

The Contractor shall provide a 100Mb Ethernet interface (copper RJ45) for accessing into a VA Network at each hub location. The demarcation point of responsibility shall be the Network Security Operations Center (NSOC) managed firewall located at each hub location (refer to Figure 1 - Primary hub Topology diagram). This is the boundary of the Enterprise SatCom Infrastructure and demarcation point for direct access to the VA Network. The Government will provide the terrestrial links between the two VSAT ground stations and the VA Network.

In order to provide the terrestrial links the Contractor shall coordinate with the Government to install Government owned and operated equipment at each of the ground station locations. The Government owned equipment will consist of a router, firewall, and an intrusion detection system. This will take approximately 8U Contractor provided rack space units at each location that must be physically secured in a locked enclosure.

A. Proof of Encryption Configuration and Certification.

5.2.1 SPACE SEGMENT BANDWIDTH REQUIREMENT

The Contractor shall provide, at a minimum, a dedicated, non-pre-emptible 36 MHz Ku Band transponder for use by the Enterprise SatCom infrastructure throughout the period of performance of this contract. The 36MHz may be provided by one or more satellites.

The Government reserves the right to reject a satellite based on estimated service life and security concerns. The VA will not accept the usage of Chinese or Russian built or operated satellites. The VA will not accept the usage of a satellite that is past its projected life expectancy and with less than 15% station keeping propellent available.

Should a satellite be past it's expected life expectancy and still have transponder redundancy and have more than 15% of station keeping propellent it would still be acceptable. The Ku Band satellite footprint shall cover Alaska, Hawaii, CONUS, Puerto Rico, and US Virgin Islands. The Government currently leases a full 36 MHz transponder on satellite AMC-21 in position 125.0 degrees West. Contractor shall provide proof of satellite coverage statement from satellite service provider.

A. Proof of satellite coverage statement

5.2.2 HUB EQUIPMENT

The Contractor shall provide new hardware and software to replace the current Enterprise SatCom hubs. The current hub equipment list to be replaced is identified in Attachment B. The current HUBs shall be disposed in accordance with current government regulations. The new hub and modem combination shall support dynamic bandwidth allocation and the latest compression algorithms. The Contractor shall deliver a Maintenance Plan and an Installation Plan (to include installation and configuration of all equipment) for Government approval detailing the delivery, installation, configuration, testing and maintenance activities for 2 hubs and 229 modems. The replacement hubs must meet or exceed the following characteristics;

A. DVB-S2 Downstream Carrier or better B. Adaptive TDMA Upstream Carrier or equal or better C. FIPS 140-2 Level 2 NIST Certified or better D. QoS (Quality of Service) Allocation Fairness E. 16-Channel Demodulator Hub Line Card or better F. SCAP (Security Content Automation Protocol) scans and compliance mitigation G. 256-bit AES Link Encryption H. Provide Terminal to Terminal connectivity for voice and video calling.

I. Each of the two hubs must be fully redundant J. OTA software upgrades K. Efficient bandwidth allocation mechanisms L. Ability to aggregate links from multiple terminals (VSATs and FRUs) into a single data stream (as in a Multilink PPP type connection).

Deliverables:

A. Maintenance Plan B. Installation Plan

5.2.3 VSAT TERMINALS

The Contractor shall replace the existing Enterprise SatCom network hardware and software. The existing Enterprise SatCom network consists of 229units, comprised of:

• 131 mobile vehicle mounted auto-deploy/acquire units (VMUs); see 5.2.3.1

• 48 mobile standalone auto-deploy/acquire terminals called Man Portable

Units (MPUs) VSATS; see 5.2.3.1

• 48 mobile standalone manual point units called FRUs; see 5.2.3.2

• 2 fixed terminals. See 5.2.3.1

The auto-deploy systems (both MPUs and VMUs) currently have 1.2M antennas.

The FRUs have 0.9M antennas and the fixed terminals have 1.8-meter antennas.

It is up to the contractor to choose the antenna sizes to meet our specifications.

Each new VSAT terminal shall include equipment, shipping, installation, activation and initial 2-day training.

Deliverables:

A. VSAT Operational Test Plan (all types) B. 229 VSAT Terminals C. VSAT Equipment Acceptance Checklist (all types)

VEHICLE MOUNTED UNITs (VMUs), MAN PORTABLE UNITs (MPUs), and

FIXED TERMINALS

The replacement MPUs, VMUs and fixed terminals shall meet or exceed the following characteristics for each individual VMU and MPU:

A. The MPU and VMU type terminals shall be capable of transmitting at least - 8Mb up and - 12Mb of down throughput in support of VSAT IP traffic.

B. The fixed location antenna terminals shall be capable of transmitting at least

- 12Mb up and - 16Mb of down throughput in support of VSAT IP traffic.

C. DVB-S2 Downstream Carrier or better D. Adaptive TDMA Upstream Carrier or better

E. FIPS 140-2 Level 2 NIST Certified or better F. QoS (Quality of Service) Allocation Fairness G. SCAP (Security Content Automation Protocol) scans and compliance mitigation (see attached) H. 256-bit Link Encryption I. The modem must securely support a separate private and public network concurrently.

J. Router capable is supporting multiple routing protocols and support an internal switch of at least 16 - 100Mb Power Over Ethernet (POE) switch ports capable of supporting multiple virtual local area networks.

K. The routers shall support current SSH encryption for remote access and all other incoming protocols (Telnet, Radius, SNMP, HTTP, HTTPS) with the ability to enable or disable protocols independently.

L. Two FIPS 140-2 level 2 or better, NIST certified wireless access points, one for VA connectivity and one for non-VA connectivity.

M. Multifunction Device (copier/printer) – HP Color LaserJet Pro M281CDW or equal.

N. Ruggedized storage container similar to one described in sections 5.2.3.3 case for each Multifunction Device.

O. 4 SIP phones P. 4 Analog phones

1. Provide commercial telephone services for each VSAT unit consisting of:

a. Each number will be a toll-free number (eg 1-800 / 866 / 877)

b. Unlimited call (air) time

c. Utilize e911 locator services

Q. 1 video conferencing unit complaint with Session Imitation Protocol standards

(SIP). This includes a flat panel display of at least 18 inches measured diagonally.

R. Router must provide DHCP services S. Support multiple Virtual local area networks (VLANS) T. Support Quality of Service (QoS)mechanisms for different IP based services U. Ability to aggregate data from multiple terminals into a single data string (As in a Multilink PPP connection).

V. Capable of supporting cellular connectivity. For example, the VA utilizes

Plum Laboratories Plum Cases. VA requires either the ability to interconnect with the Plum Case or the VSAT unit be upgradeable to support internal 3G/4G or better connectivity.

The Contractor shall replace the hardware on the existing vehicle mounted auto-deploy/acquire units (VMUs) that are more than 5 years old, as indicated on Attachment B. The Contractor has the option of reusing the VMUs 5 years old or newer providing they upgrade the router and modem to meet the government requirements. The VA will be responsible for the disposal of the removed equipment. The GFE VMUs will be provided “As-Is” without any support or warranty. The VMU inventory will be included in attachment B. The Contractor shall be responsible for maintaining any of the government equipment that is reused. The Contractor shall complete refresh of any equipment or software on the network before it reaches its published end of support/end of life.

The Contractor shall replace the existing hardware and software within 160 calendar days of December 1, 2019. The current Enterprise SatCom system consists of 224 mobile VSAT terminals and 2 fixed terminals.

As part of final equipment acceptance, the Contractor shall complete a contractor provided VSAT Equipment Acceptance Checklist (to include results of the testing utilizing the approved operation test plan) and submit for VA approval. The Contractor shall set up and demonstrate to the receiving VA personnel that the terminal is complete, functional, and free of damage. The Contractor shall provide a VSAT Operational Test Plan for approval prior to performing an operational test of each component and the receiving VA personnel will verify the operation of each component. After the successful testing of each component the receiving VA personnel will sign the Equipment Acceptance Checklist document and submit it to the COR.

FIRST-RESPONDER SATELLITE UNITS

The Contractor may provide new FRUs or use the existing FRUs providing the Contractor modify the existing FRUs to meet the requirements below. The Contractor has the option of reusing the FRUs components 5 years old or newer (as indicated on Attachment B) providing the router and modem are upgraded the to meet the government requirements. The GFE FRUs will be provided “As-Is” without any support or warranty. The FRU inventory will be included in attachment B. If the Contractor chooses to modify and use existing FRUs, the Contractor shall be responsible for continued maintenance until the FRUs are replaced. The Vendor shall complete refresh of any equipment or software on the network before it reaches its published end of support/end of life.

The Ku-Band FRU man-portable terminals shall:

A. Be capable of transmitting at least - 6Mb up and - 8Mb of down throughput in support of VSAT IP traffic.

B. Weigh less than 50 pounds per storage container. The solution may provide up to two containers, each weighing less than 50 pounds.

C. Built in a ruggedized fashion to meet the below specification. Technical specifications shall be provided, and the following test standards apply:

Test: Operating range:

Shock Drop Height – 45 inches

Temperature -10 to 120 Degrees Fahrenheit

Rain < 100 mm per hour

Wind < 30 miles per hour (not anchored)

Humidity 0 to 100% (condensing)

D. Encompass a setup time that does not exceed fifteen minutes.

E. Operate with alternate sources of power.

F. Run on an included battery (such as an Uninterruptable Power Supply) for

30 minutes (refer to item (B) above).

G. Support concurrent voice, video, and data using IPv4 and IPv6.

H. Compatible with and use the same bandwidth as the other VSAT units.

I. Have an audio and visual assisted manual pointing unit or an automated mechanism for azimuth and elevation guidance.

J. Have at least two RJ45 Ethernet interfaces.

K. Capable of operation on 12VDC or 120VAC power.

L. Include GPS, Compass, and level sensor.

M. Remote Transmit Frequency Range (950 to 2400 MHz) N. Remote Receive Frequenc y Range (950 to 2150 MHz) O. Have 2 ports of analog phone capability.

P. The modem must securely support a separate private and public network concurrently.

Q. Include 4 SIP (VOIP) phones and phone service.

2. Provide commercial telephone services for each VSAT unit consisting of:

d. Four numbers for operation using SIP phones

e. Each number will be a toll-free number (eg 1-800 / 866 / 877)

f. Unlimited call (air) time

g. Utilize e911 locator services

R. Be airline checkable.

S. Antenna Dish size must be compatible with the above identified requirements.

T. Able to be connected to an external Ethernet switch via RJ45 copper Ethernet connection.

U. Ethernet connection and wireless connection shall be able to be used simultaneously.

V. DVB-S2 Downstream Carrier or better W. Adaptive TDMA Upstream Carrier or better X. FIPS 140-2 Level 2 or better NIST Certified or better Y. QoS (Quality of Service) Allocation Fairness Z. 256-bit Link Encryption AA. Router must provide DHCP services BB. Support multiple Virtual local area networks (VLANS) CC. Support Quality of Service (QoS)mechanisms for different IP based services DD. Ability to aggregate data from multiple terminals into a single data string (As in a Multilink PPP connection).

EE. Capable of supporting cellular connectivity. For example, the VA utilizes

Plum Laboratories Plum Cases. VA requires either the ability to interconnect with the Plum Case or the VSAT unit be upgradeable to support internal

FF. 3G/4G or better connectivity. The VA prefers the ability to use both technologies concurrently on the same unit.

GG. Two FIPS 140-2, Level 2 or better, NIST certified wireless access points, one for VA connectivity and one for non-VA connectivity.

As part of final equipment acceptance, the Contractor shall complete a contractor provided VSAT Equipment Acceptance Checklist (to include results of the testing utilizing the approved operation test plan) and submit for VA approval. The Contractor shall set up and demonstrate to the receiving VA personnel that the terminal is complete, functional, and free of damage. The Contractor shall provide a FRU Operational Test Plan for approval prior to performing an operational test of each component and the receiving VA personnel will verify the operation of each component.

After the successful testing of each component the receiving VA personnel will sign the Equipment Acceptance Checklist document and submit it to the COR.

Each new or modified First Responder Unit (FRU) shall include equipment, ruggedized hard sided shipping container (if the modified FRU does not fit existing FRU cases, see section 5.2.2.4), shipping, installation, activation and initial training.

RUGGEDIZED STORAGE CONTAINERS

The Enterprise SatCom VSAT user community has identified a need for ruggedized storage containers. The Contractor shall provide 40 ea. new ruggedized and padded plastic storage containers equipped with wheels, a handle, pressure relief valve and lock attachment points. The VA currently desires and uses Pelican model 1660 cases.

This type and size of case or equal is required. These storage containers shall be shipped to the VSAT locations designated in Attachment D These containers and locations are not associated with Section 5.2.2.3.

A. 40 ea. Ruggedized Storage Containers

5.3 TWO-PHASE ENTERPRISE SATCOM TRANSITION AND DEPLOYMENT

The Contractor shall transition the currently existing SATCOM system and deployment of the new Enterprise SATCOM system in two phases. Phase-One timeframe shall be completed by December 1, 2019. Phase One transition support with the incumbent contractor shall end no later than December 1, 2019. Phase-One Operations shall consist of concurrent operations to transition the new Enterprise SATCOM system along with the existing SATCOM system (terminals and satellites). The new Contractor shall be responsible for operating and maintaining the existing SATCOM system. During the Phase One period the Contractor shall begin deployment and operations of the new SATCOM system as new terminals and hubs become available for deployment. In Phase two transition, the Contractor shall no longer have access to the previous satellite service and will transition satellite service of any existing SATCOM terminals to the new Enterprise SATCOM satellite service. Phase two shall begin on December 1, 2019 and not exceed 160 calendar days with the completion of all new terminals identified in section 5.2 into operational status.

5.4 ENTERPRISE SATCOM OPERATIONS

5.4.1 HELP DESK SUPPORT

The Contractor shall provide Help Desk support throughout the PoP for the entire VA Enterprise SATCOM Infrastructure. The Contractor help desk representative shall identify and log the caller’s issue, understand the problem, and provide problem resolution.

The requirement of the Help desk support services includes but not limited to:

A. Shall provide help desk toll free call number(s).

B. Shall document a Monthly Help Desk Report to the ESPO PM, and serve as the first tier of support for any required equipment replacements due to operational failure and any software upgrades that become required.

C. Shall maintain a Contractor Trouble Ticket system, and records of all trouble ticket resolutions.

D. Shall provide e-mail and telephone help desk customer support from 7:00 AM to 9:00 PM Eastern Time (ET) Monday through Friday.

E. Shall respond to 24x7 emergency telephone requests within two hours of initial call;

F. Shall respond to at least 80 percent of initial e-mail requests made during regular business hours within one hour and the remainder within three hours.

G. Shall respond to non-emergency email requests sent after hours (after 9:00 PM ET) on the next business day.

H. Shall provide a response/acknowledgement within one business day for all customer inquiries.

I. Shall maintain a Help Desk application to track trouble tickets and assist with troubleshooting.

J. Shall host monthly Enterprise SatCom Support Team calls to assist with workflow and issue resolution.

K. Shall provide summary help desk information in the Monthly help desk Report for all Tier 1, 2 and 3 help desk activities, to include:

1. Number of response calls (trouble tickets processed) for each month

2. Type of Tier support of each call

3. Unit and Location of the caller

4. Reason for call and resolution

5. Response time and resolution activities

6. Problems encountered in restoring units to operational readiness

7. Timeliness of Response Calls

N. Shall interface with Enterprise SatCom operators.

O. Shall support national independent field testing of Enterprise SatCom units by annotating work orders placed during the tests.

P. Shall interface with field OI&T help desks.

Q. Shall support local OI&T staffs with Enterprise SatCom configurations and other Enterprise SatCom technical issues.

R. Shall maintain current inventory of all Enterprise SatCom Equipment in the automated inventory system.

T. Shall perform on-site installation of equipment, and report equipment inventory for remote (downlink) Enterprise SatCom locations and networking systems equipment at the hub locations.

U. Shall perform on-site installation, inventory configuration and training for equipment changes or upgrades of Enterprise SatCom units supplied by the Government.

V. Shall establish an Enterprise SatCom equipment inventory database to insure accurate accountability for all Enterprise SatCom components; the inventory database must have a field for recording instances of broken equipment. Broken equipment must be reported in the Monthly Testing Reports.

Deliverables:

A. Monthly Help Desk Report B. Quarterly Enterprise SatCom Inventory Reports

5.4.2 HUB OPERATIONS

The Contractor shall provide hub Operations at locations to be determined by the awardee.

The Contractor shall perform remote monitoring to ensure full operations of these hubs on 24x7x365 basis. The Contractor shall provide at least 99.99% uptime availability for hub operations and shall be reported in the Monthly Progress Report (5.1.2). The Contractor is expected to work on-site only in troubleshooting, emergency, or maintenance situations.

The Contractor shall support the following hub operations services:

A. Provide and manage bandwidth allocation for a minimum of 36 MHz dedicated, non-pre-emptible transponder bandwidth, and ensure compatibility with existing Enterprise SatCom infrastructure and bandwidth services as currently provided by the Enterprise SatCom Program Office

(ESPO).

B. All satellite modem to modem connectivity shall be Advanced Encryption Standard (AES) link encrypted via link encryption

C. Assign and manage all multiple inbound and outbound carrier channels;

voice service hardware.

D. Provide up-link frequency assignments to each remote terminal (VSAT and First Responder Terminal).

E. Provide down-link frequency assignments to each remote terminal (VSAT and First Responder Terminal).

F. Provide longitude and latitude assignments for each remote terminal

(VSAT and First Responder Terminal).

G. Provision hub Radio Frequency (RF) and networking resources for changes in remote site demographics and support special requests for hub re- provisioning in the event of emergency operations requirements.

H. Provide a secure VA accessible web portal with Dashboard listing all VSATs, VSAT type, operational status (off-line; on-line; failed; waiting repair), last date online and their last known GPS coordinates.

I. Provide near real-time VSAT GPS coordinates for internal VA mapping purposes via on-line transfer.

J. Provide secure VA accessible web portal showing VSAT locations on a map.

K. Monitor and analyze the Enterprise SatCom network performance data to…