CEG Regions 3-7 PWS - DRAFT.pdf

01Nov2020/Version 7

PERFORMANCE WORK STATEMENT

Commercial Ethernet Gateway (CEG) – Continental United States (CONUS) Regions 3-7

01 November 2020

Table of Contents

1. Contracting Officer Representative (COR)

2. Contract or Task Order Title

3. Background

4. Objectives

5. Scope

6. Performance Requirements

6.1 Task 1 - Program Management:

6.1.1 Subtask 1 - Comprehensive Implementation Plan

6.1.2 Subtask 2 - Project Status and Reporting

6.2 - Task 2 - Network Service Capabilities

6.2.1 Subtask 1 - Commercial Enterprise Ethernet Gateways (CEG)

6.2.2 Subtask 2 - DODIN Customer Access Site Services

6.3 Task 3 - Network Service Management

6.4 Task 4 - Security - Reserved

6.5 Task 5 - Site Implementation Services (Optional)

6.5.1 Subtask 1 - Service Delivery Point (SDP) Extension Provisioning

6.5.2 Subtask 2 - Demarc Infrastructure Modifications

6.5.3 Subtask 3 - VLAN Modifications

6.5.4 Subtask 4 - Customer Access Service (EVC) Upgrade Modifications

6.6 Additional Services and Requirements

6.6.1 - Temporary Service

6.6.2 - Expedited Service

6.6.3 - Telecommunications Service Priority (TSP)

6.6.4 - National Security and Emergency Preparedness (NS/EP) ................................................................... 15 15

6.6.5 - Circuit Cessation and Disconnection

7. Performance Standards. (Unless otherwise stated, all time is in Calendar Days)

8. Incentives

9. Place of Performance

9.1 Alternate Place of Performance - Contingency Only

10. Period of Performance

11. Delivery Schedule. (Unless otherwise stated, all time is in Calendar Days.)

12. Security Requirements

12.1 Facility Security Clearance

12.2 Security Clearance and Information Technology (IT) Level

12.3 Investigations Requirements

12.4 Visit Authorization Letters (VAL)

12.5 Security Contacts

12.6 Information Security and other miscellaneous requirements

13. Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI)

14. Other Pertinent Information or Special Considerations

15. Section 508 Accessibility Standards

16. Attachments

Attachment A - CEG -DISN Node and Customer Access Site List Attachment B - CEG Design Document Attachment C - CEG Technical Implementation Standards Attachment D - CEG Notice of Completion Template Attachment E - CEG GFI and Contract Deliverable Timeline Attachment F - CEG Region 3-7 Pricing Schedule

PERFORMANCE WORK STATEMENT (PWS)

As of 01 November 2020

Contract Number: TBD Task Order Number: TBD Contractor Name: TBD Tracking Number:

Follow-on to Previous Contract and Task Order Number:

1. Contracting Officer Representative (COR).

a. Primary COR.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

E-Mail Address:

b. Alternate COR (ACOR).

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

E-Mail Address:

2. Contract or Task Order Title.

Commercial Ethernet Gateway (CEG) – Continental United States (CONUS) Regions 3-7

3. Background.

In May 2016 the Department of Defense (DOD) Chief Information Officer directed the DOD to migrate to Ethernet-based services to reduce telecommunications costs. Since that time the Defense Information Systems Agency (DISA) has been modernizing the DOD Information Network (DODIN) to facilitate Ethernet connections to that network and enable the replacement of legacy point-to-point Public Switched Telephone Network, time division multiplexing-based circuits.

4. Objectives.

The objectives of this contract are to:

1. Establish Commercial Ethernet Gateways (CEG) from the Commercial Service Provider’s (CSP) owned, leased and operated network(s) to the DODIN in accordance with the instructions shown in Attachments A and B for the CEG DISN Core Sites. CEGs shall employ virtualization using virtual local area network (VLAN) (802.1Q) between the DISN Joint Provider Edge Router (J-PE) and the CSP’s PE routers using, diverse, high bandwidth links. The CSP’s CEG design must meet the performance and availability requirements in the PWS. Table 4-1 shows the CEG regions and the states that are included in each region.

2. For the Customer Access Sites, provision > 1 GB connections to the CSP’s Ethernet Network. Perform functional and performance testing to demonstrate compliance with PWS requirements. Attachment A provides a list of potential Access Site locations.

3. Provide additional Customer Access Sites and/or move or upgrade service for Customer Access Sites within the region.

Region States

3 DC, KY, MD, OH, VA, WV

4 AL, AR, FL, GA, LA, MS, NC, SC, TN

5 CA, NV

6 AZ, CO, ID, MT, NM, OK, OR, TX, UT, WA, WY

7 IA, IL, IN, KS, MI, MN, MO, ND, NE, SD, WI

Table 4-1: CEG CONUS REGIONS and Associated States

5. Scope.

The Government requires commercially provided network solutions and services where the Contractor designs, furnishes, installs, tests, maintains, and sustains the CEG and Customer Access Site capabilities described in Attachment B for both DOD and authorized non-DOD operations at various locations representatively shown in Attachment A. Figure 5-1 provides an overview of a notional CEG Regional architecture.

Figure 5- 1 Notional CEG Regional Architecture

Customer Access Sites not listed in Attachment A may be added to a region during the life of the contract and sites listed on Attachment A may or may not be ordered. All CEGs and Customer Access Sites will be awarded by individual task orders (TOs) and assigned a command communications service designator (CCSD) and a communications service authorization (CSA). The Contractor will deliver services per the prices defined in Attachment F for all TOs awarded. TOs will be awarded utilizing Integrated Defense Enterprise Acquisition System (IDEAS). Contractor shall register with the DISA Global Service Desk for access to IDEAS. The Contracting Officer (CO) will assist with coordination for access. Once registered, Contractor can access IDEAS to download orders and modifications sent directly to the Contractor, and to upload jeopardy notices and completion notices. An order or modification sent to the Contractor in IDEAS is considered the official issuance of the order or modification by the Government.

Payment for service provided under this contract shall be made using the Delivery Ticket Invoice (DTI) payment method. Payments will be provided automatically by the Government. The Contractor shall not submit separate invoices for services provided under this contract to Defense Information Technology Contracting Organization (DITCO). Outage credits shall be submitted to DITCO by a paper check from the Contractor.

6. Performance Requirements.

6.1 Task 1 - Program Management:

Task 1 provides the Program Management requirements for the delivery of the services described in Tasks 2-5.

Offerors are encouraged to use existing designs, systems and processes as long as they meet the requirements described in this Task.

6.1.1 Subtask 1 - Comprehensive Implementation Plan

The Contractor shall provide a Comprehensive Implementation Plan (CIP), a living document that shall be maintained by the Contractor throughout the Period of Performance (PoP) of the contract. An Initial CIP shall be provided as part of the Contractor’s proposal and will be evaluated to determine the technical acceptability of the Contractor’s design, as well as their implementation and support (also called Operations and Maintenance (O&M)) approaches. The CIP format is Contractor determined but the proposed CIP approach must demonstrate the Contractor’s capability to plan and manage the contract requirements throughout the PoP. The Contractor’s ability to manage life-cycle CIP revisions and provide design data, implementation status, and operational performance data to the Government will also be evaluated. The Government understands that certain types of data (e.g. actual schedule dates) cannot be provided in the initial CIP, but where possible, actual data that describes the offeror’s proposed approach shall be provided (e.g. proposed CEG and Access Site Design, Test Plans/Procedures, O&M Processes, etc.).

Upon award, the Government will provide feedback to the Contractor during the initial In-Process Review (IPR) and the Contractor shall deliver a Final CIP not later than 30 days after contract award. CIP updates shall be provided to the Government not less than monthly and whenever changes are made to the Gateway or Access Site design, when new sites are added, or when sites are disconnected. The Contractor’s CIP change process should be described in their proposal and should specifically address how updates will be provided. The following paragraphs provide additional information about the CEG requirements and the data required in the CIP.

6.1.1.2 Gateway Design: There shall be a minimum of two (2) gateways installed in each region. Gateways can be installed at the Government Gateway locations listed in Attachment A or on the Contractor’s site as long as the Network to Network Interface (NNI) meets the requirements of Attachment B. If an onsite survey is required of the Government location prior to the installation of the Gateway, the Contractor shall state this in their proposal and include pricing if applicable for this survey(s) in their cost proposal as a non-recurring cost (NRC). Note that in the event that the Government facility does not have infrastructure needed to support the CEG installation, the Contractor shall be required to provide the infrastructure and may include this cost in their cost proposal as a NRC. The following data shall be provided in the Initial CIP showing the logical and physical architecture proposed at the gateway sites:

a. Diagrams showing where the equipment will be installed, what demarcation point (demarc) infrastructure will be needed (e.g. electrical power connections, rack space, HVAC load, etc.) and how the equipment will be connected to the DOD equipment in accordance with Attachment B. If the Contractor proposes to install CEG equipment in their owned or leased facility, so state and provide the address and a description of the facility including physical security information.

b. Tables showing the make and model number of all equipment that will be installed as well as operating system versions and its configuration for each device. If the Contractor intends to use more than one configuration at a Gateway they shall provide drawings and data for each configuration to be used that can be correlated back to each as-built data provided per subparagraph a. above.

c. Contractor shall show how the equipment used on this contract meets the requirements outlined in the Contractor’s Supply Chain Risk Management (SCRM) Plan outlined in Paragraph 14.g.

6.1.1.3 Access Site Design and Ordering: Access Sites are connected to Gateways via the Contractor’s proposed e-line service (also referred to herein as an Ethernet Virtual Circuit (EVC)). The following data shall be provided in the Initial CIP and all subsequent updates showing the logical and physical architecture proposed at the Access Sites:

a. Diagrams showing how the equipment will be installed (e.g. Rack Elevation and Cabling), what demarc infrastructure will be needed (e.g. electrical power connections, rack space, etc.) and how the equipment will be connected to the DOD customer site equipment in accordance with Attachment B.

The Contractor is responsible for connecting the EVC to the DoD customer network and the diagrams should clearly show this connection. These diagrams shall represent the proposed Access Site design in the Initial CIP but the Contractor shall be responsible for providing as-built data for every Access Site in the monthly CIP updates that indicate the rack locations and connection details for every installed device.

b. The Gateway location to which the Contractor is proposing to home the Access Site. The Government requires this information as a prerequisite to issuing the TO for any/all Access Sites in order to make the VLAN assignments described in PWS 6.2.1.4. If the contractor can make this assignment as part of the initial/final CIP they are encouraged to do so. If the Gateway homing assignment cannot be made at that time it should be made as early as possible in the design process but in every instance the homing assignment is required prior to the issuance of the TO.

c. Tables showing the make and model number of all equipment that will be installed as well as operating system versions and its configuration for each device. If the Contractor intends to use more than one configuration at Access Sites, they shall provide drawings and data for each configuration to be used that can be correlated back to each as-built data provided per subparagraph a. above.

d. Contractor shall show how the equipment used on this contract meets the requirements outlined in the Contractor’s Supply Chain Risk Management (SCRM) Plan outlined in Paragraph 14.g.

After contract award, the Government may order and the Contractor shall provide Access Services for locations included in Attachment A. All orders will be issued via a TO at the firm fixed price proposed by the Contractor in Attachment F. When requested by the COR, the Contractor shall provide, at no additional cost, the CIP information described in PWS 6.1.1.5 that is required by the Government to develop the TO for the new service. This information shall be provided within 5 business days of the request but Contractors are encouraged to provide the Access Site homing information per 6.1.1.3b as soon as possible.

Requests for this information does not obligate the Government to order the service.

Additionally the Government may order additional Access Services in a region for locations not listed on Attachment A. If the firm fixed price CLINs on this contract are not applicable for the additional Access Services being requested, the Contractor shall include a firm fixed-price quote for services being requested, which will be negotiated with the Contracting Officer as part of TO issuance. The quote shall explain in detail why an existing firm fixed price CLIN on this contract is not applicable for the new Access Service request.

For Access Sites, the Government will ensure that the Contractor has access to the site to install any required equipment and that Government infrastructure (e.g. rack space, power, local fiber, etc.) is made available for the installation and operation of the service. If Government infrastructure is not available, the Government may elect to order Site Implementation Services from the Contractor as described in paragraph 6.5.

6.1.1.4 Implementation Process: The CIP shall describe the process the Contractor will use to survey, install, and test and make operational Gateways and Access Sites delivered under this contract. This shall include:

a. Detailed and realistic schedule for implementation of the proposed Gateways, including timeframes needed to survey (where applicable), provision, install, activate, test, submit test results, and obtain Government acceptance. Schedule shall demonstrate the Contractor’s capability to meet the Acceptable Quality Level (AQL) for Gateway Delivery listed in Paragraph 7 Performance Standards.

The Initial CIP submitted with the proposal shall have notional dates. Actual dates will be negotiated at the initial IPR and used in the updated schedule delivered with the Final CIP. Contractors are responsible for providing all infrastructure (e.g. rack space, power, local fiber) at Gateway Sites that is necessary to implement their proposed CEG architecture and shall factor any onsite survey requirements into their schedule.

b. Gateway Test Plan/Procedures that demonstrate that the Contractor’s Gateway meets the technical and performance requirements of this PWS. Upon approval, this plan/procedure will be used at all Gateways and test results provided to the Government for review and approval prior to proceeding with Customer Access Site installations. Test Procedures shall demonstrate that the EVC is connected to the DoD customer network and that test traffic can be passed from the customer network, through all Contractor installed equipment, across the EVC to the Gateway NNI (i.e. the Contractor’s interface with the DISN).

c. Detailed and realistic schedule for installation of the Customer Access Sites. Surveys of Access Sites are expected to be performed virtually via email, teleconferencing, phone calls and other electronic methods but on-site surveys may be conducted at the Contractor’s discretion. Costs for all survey activities shall not be separately priced (i.e. cost shall be included in the Contractor’s MRC for the Access Site EVC). Any and all visits to survey, provision, install, activate, and test, the proposed dates and duration of these visits for each site shall be clearly shown on the schedule. The schedule shall meet the AQL for Ethernet Virtual Connection (EVC) Delivery listed in Paragraph 7 Performance Standards. The Initial CIP submitted with the proposal shall have notional dates for all Access Sites listed on Attachment A. Actual dates will be negotiated at Task Order Issuance and used in the updated schedule delivered with the Final CIP or subsequent CIP Update(s) as applicable.

d. Test Results for Gateways that follow the approved Test Plan/Procedure described above. Test Results shall be provided to the Government within two business days of successful test completion.

e. Customer Access Site Test Plan/Procedures that demonstrate that the access site solution proposed by the Contractor meets the technical and performance requirements of this PWS. This plan/procedure shall be used by the Contractor at all Customer Access Sites.

f. Test Results for each installed Access Site that follows the approved Test Plan/Procedure described above. Access Site Test Results shall be provided in accordance with Paragraph 6.1.2.3 below within two days after completion of testing.

g. The process to notify designated Government personnel of planned surveys, installation work, changes in site implementation, site concurrence and acceptance, Contractor testing, and maintenance or repair.

h. The Contractor’s approach for resolving issues that surface at the site during Contractor installation and testing.

6.1.1.5 Data Delivery Process: The Government intends to issue TOs for all work performed. For every Gateway or Access Site EVC ordered, describe how you will provide the following information prior to Task Order (TO) issuance:

a. Contractor Name (include Point of Contact (POC) name and contact info)

b. Proposed Gateway Assignment (for EVCs)

Once the Contractor provides the information specified above, the Government will issue a TO which will provide the VLAN ID and a CCSD to the Contractor. The Contractor is responsible for tagging the new circuit with the CCSD as part of the installation process. Describe how Contractor will collect and ensure that the following information is included in the CIP Update following the completion of the installation:

c. Contractor Customer Circuit ID

d. Contractor CEG NNI (Trunk) ID

e. Planned Completion Date

f. Contractor Operations Center (OC) /24/7 Trouble Reporting contact info

g. Customer physical demarcation point (demarc) address

h. Rack/shelf/slot/port – for Contractor equipment EVC connection to site including description of patch panel cross connects and slot/port of connection on customer equipment (i.e. meet me point).

6.1.1.6 Operations and Maintenance: The CIP shall describe the Contractor’s approach to performing both planned and unplanned maintenance on Gateways and Access Sites during the PoP of the contract. This approach shall include:

a. The service delivery methodology (e.g. service request process, delivery timeframe, test and acceptance process, etc.) being proposed to support the requirements of this contract.

b. Contractor’s O&M organization and process, including Operations Center (OC) facilities (primary and alternate), capabilities, diversity and redundancy that will be utilized to provide CEG and Customer Access Services. The plan shall address continuity of operations (COOP), emergency/disaster response, DISA Global Operations Command coordination procedures, escalation, and maintenance processes (planned and unplanned) for CEG and Customer Access Sites.

c. The Contractor’s process for notifying Government of maintenance activities. For maintenance activities that will require an outage, the Contractor shall describe its approach to follow the DISA Authorized Service Interruption (ASI) process described at https://www.disa.mil/DGOC/GNSC/ASI and specifically outlined in DISAC 310-70-1 Chapter 10 which is downloadable at that link.

d. Process to discontinue, upgrade and/or move existing EVC service at an Access Site. The Government will provide a minimum of 30 calendar days from the date of task order to disconnect a Customer Access Site.

A detailed timeline showing the timing and the data required for CIP Initial and Final versions as well as required updates is provided in Attachment E.

6.1.2 Subtask 2 - Project Status and Reporting

6.1.2.1 In-Progress Reviews (IPR)

The Contractor and Government shall conduct an initial IPR within 10 business days after award to discuss the Initial CIP. The Contractor shall brief the detailed approach for performance, functional work relationships, programmatic and technical compliance, identification of critical path and key dependencies, and all risk elements and proposed mitigation. In addition, the Contractor shall provide a comprehensive briefing of the proposed implementation method, planned activities, and proposed schedule. The briefing shall also identify the Contractor’s existing capacity and capabilities in place to satisfy the requirements. The Government will provide its schedule for Gateway and Access Site TO release to include delivery of the Government Furnished Information (GFI) that the Contractor will require to implement the installation and testing of the Gateways and Access Sites. The Contractor’s proposed schedule will be adjusted based on the TO and GFI delivery dates and included in the Final CIP or most recent CIP Update which shall be delivered not later than 30 days after contract award or Task Order award as applicable.

Following the initial IPR, subsequent IPRs shall be conducted monthly until completion of the contract. Once CEGs are operational, the Contractor shall provide the following data in the IPR:

• Access Site installation status - CIP Schedule vs Actual o IPR shall identify any/all Site Implementation Services (Task 5) required to install a Customer

Access Site.

o Once the Contracting Officer has authorized implementation services to proceed by issuance of a

TO modification, the Contractor shall provide status of implementation services until completed.

• CEG Availability o Explain any CEG downtime

• CEG Bandwidth Utilization o Provide details of periods where CEG utilization exceeds 80% for more than five minutes

• Customer Access Site Availability – include all downtime even for planned maintenance (e.g. ASI).

When applicable, IPR discussion topics and decisions will be reflected in subsequent CIP updates. The IPR may be conducted virtually using the Contractor’s collaboration tool.

DELIVERABLE: Comprehensive Implementation Plan (Final) https://www.disa.mil/DGOC/GNSC/ASI

DELIVERABLE: Implementation Plan Updates DELIVERABLE: Gateway Test Results DELIVERABLE: Access Site Test Results DELIVERABLE: In-Progress Review (IPR)

6.1.2.2 Monthly Progress Report (MPR)

The Contractor shall ensure a MPR is submitted that addresses adherence to the CIP, billings, progress, status, and any problems or issues encountered in the performance of this contract, in a format mutually agreed upon with the Government. The MPR shall describe tasks, listing of active sites, progress and financial status, and identify problems, accomplishments and issues from the reporting period of the MPR. The MPR shall provide a listing of all active sites and the service availability for each site. At a minimum, this data shall include:

- Description of activities and deliverables during the current month. The description shall include problem definitions and recommendations for program resolution. Particular attention shall be given to risk management activities.

- Trips, technical visits, and related results for the report period.

- The project schedule showing any proposed changes, the reasons for the changes, and the potential impacts on the program.

- Listing of active sites for the month and the monthly service level availability for each site to include a listing of the sites (including CCSD) that did not meet the Performance Standard AQLs and the applicable outage credit due to the Government.

- Identification of key personnel and personnel reassignments including personnel added or removed from the contract and the subtasks and projects they will or did work on.

- Self-assessment of performance with respect to the PWS AQLs.

DELIVERABLE: Monthly Progress Report (MPR)

6.1.2.3 - Service Delivery and Acceptance Reporting Upon installation and successful completion of testing, the Contractor shall send all circuit test results, for both Gateways and Access Sites, to the COR and Contracting Officer for review and acceptance. DISA will review test results with the customer activity and notify DITCO and the Contractor within 72 hours of acceptance or the need for correction and retest. Within two business days of notification of acceptance, the Contractor shall provide a Notice of Completion (NOC). A completion notice must include the information shown in Attachment D. Unless deviations are identified, completion notice will serve as Contractor's confirmation that service was provided in accordance with this PWS and its associated TO. A follow-up completion notice will be required when deviations are cleared. Failure of Contractor to provide completion notice may result in delay in payment. DITCO’s preferred method of receiving a completion notice is via IDEAS.

DELIVERABLE: Notice of Completion (NOC) in Attachment D Format

6.2 - Task 2 - Network Service Capabilities DISA has a requirement for a robust, redundant, survivable, net-centric solution to meet the DOD’s telecommunications requirements. This task requires the Contractor to establish CEGs at the gateway locations identified in Attachment A. The gateways shall comply with the design requirements contained in the DISA CEG Design Document (Attachment B). DISA’s requirement is to have an enterprise solution to efficiently aggregate Ethernet circuits from a CSP and to ultimately decommission the existing point-to-point TDM circuits.

Virtualization using VLAN (802.1Q) between the DISN J-PE and the CSP PE routers over a high bandwidth link is the desired CEG solution.

As part of this contract, the Contractor shall install, test, and maintain NNIs between DISN Gateway Sites in Attachment A, and its network. The Contractor’s network shall be capable of operating with the access interfaces and virtual service requirements defined in this PWS. Once the Contractor’s Gateway infrastructure and equipment has been installed and tested to verify DISN connectivity and performance, the individual Customer Access Sites will be provisioned under this contract using the tested and approved gateways. Attachment A shows the potential Access Sites to be ordered under this contract but this list can change during the life of the contract and Contractor’s should demonstrate how their CEG design is scalable and can accommodate new Access Site requirements in a region.

Note that this PWS includes 5 separate regions. Each region has a list of allowable Gateway locations and the Contractor shall establish an NNI to at least two (2) of the listed locations in each region.

6.2.1 Subtask 1 - Commercial Enterprise Ethernet Gateways (CEG)

6.2.1.1 Commercial Ethernet Gateways (CEG) Overview: The Contractor shall provide, install, test, and maintain a CEG between the DISN J-PE routers and the CSP’s facilities as described in Attachment B. The Contractor’s CEGs shall connect to two or more of the DISN Gateway Site locations listed in Attachment A for the CEG locations listed therein. Equipment can be hosted on the Government site or in a Contractor’s hosting facility. Regardless of the equipment location, the connections shall be configured to meet all technical and performance requirements and specifications described in Attachment B.

The Contractor’s network and CEG solution shall:

1. Have the capability to rapidly respond to changes in DOD mission capacity demands

2. Enable a DISN on-ramp for Off-Campus customers to access DISN services via CSP’s Ethernet Services

3. Enable elimination of existing point-to-point lease services via the CSP’s Ethernet Services and CEG

The Contractor shall provide written test results for every installed CEG (see Task 1 Subtask 1 and PWS 6.1.2.3) that demonstrate that all the CEG technical and performance requirements specified herein have been met. The following paragraphs provide additional CEG requirements.

For Subtask 1, the Government will ensure that the Contractor has access to the site to install any required infrastructure and equipment. As stated in paragraph 6.1.1, the Contractor shall identify all implementation activities in the CIP prior to the start of any installation work.

6.2.1.2 Ethernet Network to Network Interface (NNI) Services: The high capacity trunk between the DISN J-PE and the CSP PE is referred to as the NNI. The Contractor shall provide, install, test, and maintain an NNI between the DISN J-PE router and the CSPs CEG interface. NNIs shall meet the technical requirements listed in Attachment B. It is incumbent upon the Contractor to ensure that their CEG design has sufficient capacity for all of the Customer Access Sites in the region. Thus, CSPs shall determine the number of gateways required and the size of the NNIs necessary to carry traffic in the region. CSPs shall consider growth in the region when determining the number and location of gateways and NNIs within a gateway. Offerors shall state the amount of additional bandwidth that will be available at each gateway in the proposal. Offeror’s design shall scale sufficiently to support the addition of new access sites during the PoP of the contract and gateway rerouting of at least 30% of access site traffic during an outage.

6.2.1.3 NNI Operation: The Contractor shall operate these NNIs at no additional cost to the Government (no usage billing). The Contractor must meet the NNI design requirements described in Attachment B.

6.2.1.4 VLAN Assignments: VLAN assignments shall be in accordance with Attachment B and all assignments are to be provided by DISA unless otherwise agreed to in advance by DISA IE. VLAN assignment requirements are applicable to both the CEG NNI interface and to customer access EVCs provided under Subtask 2. All VLAN assignments should be documented in the TO and the CIP prior to implementation on-site.

In certain scenarios (e.g. when Government requires encrypted VLAN and does not have its own convergence router), the Contractor may be required to create multiple VLAN(s) when the EVC is installed.

The Contractor may also be required to add/delete/change VLAN assignments on operational EVC(s). If the VLAN add/delete/change can be accomplished remotely (i.e. via remote configuration of the Contractor’s premise equipment), the Offeror shall provide this service at no additional cost to the Government. The Government will request this action using the Contractor’s service delivery process described in paragraph 6.1.1.6. The delivery timeframe shall not exceed five (5) business days from the service request date. The Government will issue an after the fact TO to reflect any VLAN assignment add/delete/changes.

If the add/delete/change requires a dispatch to the site (e.g. to modify hardware or to make physical connections), the Contractor shall follow the procedures described in Task 5 Subtask 3.

In no case shall VLAN adds/deletes/changes result in a change to the MRC for the affected EVCs.

6.2.1.5 Service Levels: Contractors shall demonstrate that its CEG design will meet or exceed the gateway service levels requirement specified in Attachments A and B.

For Subtask 1, the Government will ensure that the Contractor has access to the site to install any required infrastructure and equipment. As stated in paragraph 6.1.1, the Contractor shall identify all implementation activities in the CIP prior to the start of any installation work.

6.2.2 Subtask 2 - DODIN Customer Access Site Services

6.2.2.1 Access Site Overview: The Contractor shall provide E-line services for DOD sites in a region as ordered by the Government via a TO. The proposed E-line services shall meet the performance specifications in Attachment B paragraph 2.5. Note that references to “Latency” mean Round-Trip Latency throughout this PWS.

For this Subtask, the Government will ensure that the Contractor has access to the site to install any required equipment and that Government infrastructure (e.g. rack space, power, and local fiber) is made available for the installation and operation of the service. As required by Task 1 Subtask 1, the Contractor shall identify infrastructure requirements in the CIP prior to the start of any installation work. As also stated in Task 1 Subtask 1, the Contractor shall provide test results for all Customer Access Sites that demonstrate that the technical and performance requirements of the PWS and Attachment B have been met. The Contractor shall test every access site installed and provide the results per Task 1 Subtask 1 and Paragraph 6.1.2.3 to show that the site meets the technical and performance requirements specified herein. The following paragraphs provide the technical description and requirements for Customer Access Service.

6.2.2.2 Ethernet Network Access Interface (Layer 2 E-Line): For this requirement, E-Line is defined as an Ethernet (optical or electrical) interface handoff between the Contractor and the customer's equipment at the defined demarc to enable the establishment of Layer 2 service over the Contractor’s network. E-Line service shall be provided in accordance with the design requirements outlined in Attachment B.

6.2.2.3 CSP Owned Aggregation Device at Off Campus Lease Locations: There will be sites where DOD activities currently have multiple, separate point to point circuits in place. These separate circuits must be aggregated onto separate Layer 2 E-Lines being provisioned by the CSP. To accommodate those instances, the CSP shall provide an aggregation device at every Access Site delivered under this contract. Attachment B Paragraph 2.10 provides a description of the required capability. Attachment B Paragraph 2.1.1 and the figures therein, provide the minimum requirements for this device and show the various use cases that this device (also called a Vendor Edge device) must support. Unless otherwise specified, the requirements in Task 3 apply to all CSP on premise devices including any CSP provided aggregation devices.

6.2.2.4 Customer Access Service Diversity: Attachment B Paragraph 2.9ff provides the technical requirements that CSPs shall meet for diversity. The following describes the diversity options that the Contractor must be able to provide for access sites services ordered under this PWS:

a) No Diversity: This is an E-Line with no diversity required. The Contractor shall build the E-Line between the Customer Access Site to one CEG (i.e. location-A (Loc A) to location-Z (Loc Z)). VLAN tags will be pushed on that E-Line as described in 6.2.1.4.

b) Gateway Virtual Diversity: When requested, Offerors shall provide virtual diversity across the Offeror’s network. Virtual diversity can be ordered on two or more E-Lines but the Government location (Location- A) would always be the same for all E-Lines. The Offeror shall route one or more Government defined VLANs to one CEG and one or more VLANs to a different CEG (i.e. two different Location Z). The Offerors edge device does not need to be diverse – i.e. CSP can use a single Edge Device. Gateway Virtual Diversity will be specified in the orders for two or more E-Lines and there shall be no additional cost beyond the proposed cost of the E-Line Service to meet this diversity requirement.

c) Physical Diversity: In this scenario the Government will order two or more E-Lines and request that they be physically diverse. There are two options under this scenario:

i. E-Lines ordered to the same location A demarc (eg Loc A1 to Loc Z1 and Loc Z2). In this scenario the CSP shall provide and install a separate edge device and terminate one of the E-Lines on that device and the other E-Line on a diverse device.

ii. E-Lines ordered to two or more demarcs e.g. Loc A1 to Loc Z1; Loc A2 to Loc Z2. In this scenario the CSP shall install edge devices and E-Line service at two diverse locations. If the CSP already has an existing edge device installed at one of the demarcs in support of this PWS, that device can be used to support one of the E-Lines. For E-Lines ordered as physically diverse, the offeror shall provide 100% physically diverse paths for two E-Lines (or the two different bound E- Lines if so ordered) to two location diverse CEGs (Loc Zs). For physically diverse orders, 100% of the cabling shall be buried unless no other option available (requires advance approval by the Government). The closest point between two cables shall never be less than 50 feet. For these orders, Offerors are required to provide fiber path drawings in advance of installation for Government review and approval. These drawings should be submitted as a CIP Update as described in Task 1 Subtask 1.

Physical Diversity will be specified in the orders for E-Line service and may include additional NRCs for equipment and installation. Services under this subtask will be negotiated and ordered on a firm fixed price basis by the Contracting Officer. Unless otherwise specified in the order, the Government will be responsible for base cabling at all demarcs and for Local Layer2/3 engineering up to the Contractor’s edge device(s).

6.3 Task 3 - Network Service Management

The Contractor shall provide service management on the CEG and all installed access services. The CSP’s Operations Center shall have circuit visibility and the capability to resolve any service outage to meet AQLs and provide data to DISA as described herein. DISA will work with the CSP to establish this data feed. At a minimum, the CSP shall meet the following service management requirements:

1. The Contractor shall have the ability to perform continuous network monitoring/management and keep the Government continuously informed of all activities that impact or have the potential to impact the DODIN or DODIN service.

2. CSP Network management systems shall have the ability to interface with the DISA-Enterprise Operations Center (EOC) network monitoring tools and, where prescribed by the Government, to provide near real time network situational awareness. DISA utilizes standards-based SNMP (v2c and v3) and Syslog feeds for situational awareness. DISA can also ingest an XML formatted WSDL via a standard web services interface or a JSON interface.

3. Report status and tracking data in near real time related to request fulfillment, trouble management, configuration management, and comparable processes to the DISA-EOC as described in Task 1 Subtask 1.

4. The Contractor shall ensure that Contractor furnished equipment will not cause interference with or be degraded by the performance of co-located systems or other systems and equipment.

6.4 Task 4 - Security - Reserved

6.5 Task 5 - Site Implementation Services (Optional)

DISA may, on a case-by-case basis, require, and the Contractor shall provide, implementation services in order for the CSP to be able to install its equipment and connect that equipment to the CSP’s and/or the customer’s network.

For example, there may be insufficient rack space or electrical power to support the addition of the CSPs equipment.

There may also be a need for low-voltage inside and outside plant wiring to be installed in order to extend service from the commercial demarc to the customer’s service delivery point (SDP). New sites that are ordered throughout the life of the contract may require these services and, in that event, the following requirements apply as do the site implementation requirements listed in Attachment C.

6.5.1 Subtask 1 - Service Delivery Point (SDP) Extension Provisioning When authorized by DISA, the Contractor shall provide, telecommunications transport service, sometimes called inside plant (ISP) or outside plant (OSP) cabling, between a TELCO DEMARC and a customer-defined SDP at another location on the base/camp/post/station. This on-base extension could include line termination equipment such as repeaters, modems, line drivers, media converters, required to extend service from the TELCO demarc to the customer defined SDP via base cabling infrastructure. The base cabling infrastructure may consist of a copper or fiber distribution system. DISA may specify on the TO the equipment to be supplied, or the Contractor may discover equipment required during a virtual or onsite site survey. All line termination equipment supplied by the Contractor shall be in accordance with the applicable ANSI standards and meet the requirements of paragraph 14g below. The Contractor shall document the details of any equipment or ISP/OSP that are installed at user locations in the CIP in accordance with paragraph 6.1.1. The Contractor shall provide all materials, equipment, parts, and services necessary to extend the service as described in the TO. Provisioning the extension between the TELCO DEMARC and the Customer SDP will require virtual site survey and coordination with the base/camp/post/station communication activity to determine/secure base cable assignments for the on campus extension and determine if any line conditioning or media conversion equipment is required to complete the extension to the user SDP. The Contractor will also be required to coordinate with the customer POC listed in the TO to determine if cabling or equipment installation is required within the customer’s premise building. Provisioning the on-base extension may also require coordination with other vendors providing service between the regulated TELCO DEMARC and the customer SDP.

Services under this subtask will be negotiated and ordered on a firm fixed price basis by the Contracting Officer. The SDP Extension Provisioning CLIN will authorize the Contractor to install SDP extensions if authorized by a Government technical representative and included on a TO. If virtual surveys are deemed insufficient, the Contractor must coordinate with the Contracting Officer for inclusion of the onsite Site Survey (See PWS 6.5.5. Task 5 Subtask 5). All such facilities and equipment including warranties thereon shall become the property of the Government upon acceptance. Contractor is responsible to account for the property in accordance with FAR 52.245-2.

6.5.2 Subtask 2 - Demarc Infrastructure Modifications

As stated in paragraph 6.2.2., for Access Sites, the Contractor shall identify infrastructure requirements in the CIP prior to the start of any installation work at an access site. If DISA determines that existing Government demarc infrastructure (e.g. rack space, power, local fiber) is insufficient to enable the Contractor to install and/or operate the services being provided under Task 2 Subtask 2, DISA may require, and the Contractor shall provide, infrastructure modifications services. The services anticipated under this subtask include: providing and installing additional rack space; extending electrical services from building power panels to racks where CSP equipment is to be installed;

installing ISP cabling and patch panels in the demarc to support circuit cross connections and facilitate use of base cabling infrastructure. All equipment supplied by the Contractor under this subtask shall be in accordance with the applicable ANSI standards and meet the requirements of paragraph 14g below. The Contractor shall document the details of any equipment or ISP/OSP that are installed at customer locations in the CIP in accordance with paragraph

6.1.1. The Contractor shall provide installation and maintenance of any installed equipment. Services provided under this subtask will require virtual site survey and coordination with the base/camp/post/station communication activity to determine the modifications required to support the CSP equipment installation. The Contractor will also be required to coordinate the proposed modifications with the customer POC in the order to determine if the proposed modifications comply with base regulations. Providing infrastructure modifications may also require coordination with other vendors providing service to the base customer.

Services under this subtask will be negotiated and ordered on a firm fixed price basis by the Contracting Officer. The Demarc Infrastructure Modification CLIN will authorize the Contractor to install Infrastructure Modifications if authorized by a Government technical representative and included on a TO. If virtual surveys are deemed insufficient, the Contractor must coordinate with the Contracting Officer for inclusion of the onsite Site Survey. All materials and equipment including warrantees thereon shall become the property of the Government upon acceptance.

6.5.3 Subtask 3 - VLAN Modifications

As stated in paragraph 6.2.1.4, there may be a requirement for the Contractor to visit a site to modify an existing device interface to support a VLAN modification. If DISA determines that a VLAN modification is required that necessitates a site visit, DISA may require, and the Contractor shall provide, VLAN Modifications services. The services anticipated under this subtask include: reconfiguring an existing CSP owned device to provide additional physical connections to a SDP, reconfiguring the device to separate VLANS across the separate interfaces; installing ISP cabling and patch panels in the demarc to support connections required to separate the VLANs and facilitate use of base cabling infrastructure. All equipment supplied by the Contractor under this subtask shall be in accordance with the applicable ANSI standards and meet the requirements of paragraph 14g below. The Contractor shall document the details of any equipment changes or ISP/OSP that are installed at customer locations in the subsequent CIP Update in accordance with paragraph 6.1.1. The Contractor shall provide installation and maintenance of any installed equipment. Services provided under this subtask may require virtual site survey and coordination with the base/camp/post/station communication activity to determine the availability of Government owned/managed ISP/OSP required to support the VLAN modification.

Services under this subtask will be negotiated and ordered on a firm fixed price basis by the Contracting Officer. The VLAN Modification CLIN will authorize the Contractor to install VLAN Modifications if authorized by a Government technical representative and included on a TO. If virtual surveys are deemed insufficient, the Contractor must coordinate with the Contracting Officer for inclusion of the onsite Site Survey. All materials and equipment provided under this subtask shall become the property of the Government upon acceptance.

6.5.4 Subtask 4 - Customer Access Service (EVC) Upgrade Modifications Government may request and the Contractor shall provide a proposal to upgrade customer access service bandwidth.

Services under this subtask will be negotiated and ordered on a firm fixed price basis by the Contracting Officer. The EVC Upgrade Modification CLIN will authorize the Contractor to complete the bandwidth upgrade if authorized by a Government technical representative and included on a TO. If virtual surveys are deemed insufficient, the Contractor must coordinate with the Contracting Officer for inclusion of the onsite Site Survey. All materials and equipment provided under this subtask shall become the property of the Government upon acceptance

6.5.5 Subtask 5 – Onsite Site Surveys

In some cases, Task 5 Subtasks 1-4 may require the Contractor to conduct an onsite site survey. This may be required when a physical inspection of the site infrastructure is required in order to develop a design for the service being ordered under the Task 5 Subtask, and onsite government personnel with the requisite expertise or tools are unavailable to support the requirement. Onsite surveys will be ordered on a firm-fixed-price basis for a four hour period and DISA will negotiate the quantity of survey units ordered in instances where the survey requires more than one person or a period longer than 4 hours. Proposed onsite Site Survey CLIN price should be inclusive of travel costs (i.e. costs for travel, lodging and subsistence will not be separately reimbursed by the government). All onsite Site Surveys will be authorized in advance by a Government technical representative and included on a TO.

For all Task 5 efforts, the Government will ensure that the Contractor has access to the site to install any required equipment. As stated in paragraph 6.1.1, the Contractor shall identify infrastructure requirements in the CIP prior to the start of any installation work.

6.6 Additional Services and Requirements

6.6.1 - Temporary Service DISA may order service on a temporary basis (equal to or less than 90 days in duration). . All TOs issued for Temporary Service will be identified as "Temporary" and a disconnect date, 90 days or less, will be identified. A TO issued to disconnect an existing circuit within 90 days will not be considered an order for temporary service.

6.6.2 - Expedited Service DISA may order and the Contractor shall provide service on an expedited basis.