RFP Attach 2 - PWS With Attachments 1 Dec 2010.docx

Section C. PERFORMANCE BASED WORK STATEMENT As of 01 Dec 2010 Contract number:

Delivery Order Number:

Contracting Officer Representative (COR).

Department of Defense Activity Address Code (DoD AAC)

Lorton, VA 22079

Department of Defense Activity Address Code (DoD AAC)

Lorton, VA 22079

Fax Number:

Table of Contents

Contract Title.

Defense Research Engineering Network III (DREN III) Contract.

Background.

The High Performance Computing Modernization Program (HPCMP) was established in 1992 in response to Congressional direction to modernize Department of Defense (DoD) high performance computing (supercomputing) capabilities. The HPCMP was assembled out of a collection of small, high performance computing departments, each with a rich history of supercomputing experience that had independently evolved within the DoD’s Military Services.

The HPCMP is chartered to establish, provide, and maintain leading edge High Performance Computing (HPC) capability for scientists and engineers engaged in DoD science and technology missions. The Defense Research Engineering Network (DREN), a component of the HPCMP, provides high performance wide area network services in support of DoD scientists and engineers and provides network and security support to other Federal Agencies where it’s in the best interest of the Government.

DREN is a sophisticated, robust, high performance communications network that incorporates the best capabilities of both DoD and the commercial telecommunications infrastructure. DREN has become DoD’s premier Wide Area Network (WAN) communication service provider for research, development, test and evaluation.

DREN enables scientists and engineers at defense laboratories, test centers, universities, and industry sites throughout the United States to use HPCMP computing resources. DREN provides secure gateways to existing Federal and civilian networks, allowing access to the program’s resource centers from a wide variety of facilities. The network links customer sites to HPCMP’s DoD Supercomputing Resource Centers (DSRC) and Affiliated Resource Centers (ARC). Additional background material on HPCMP can be found at http://www.hpcmo.hpc.mil.

The networking services of DREN are currently provided by a virtual WAN built on a commercial communications network and provide digital data transfer services between defined Service Delivery Points (SDP) that comprise DREN. SDPs are specified in terms of bandwidth requirements, physical interface, and transport protocols.

DREN’s Internet Protocol (IP version 6 and version 4) service for video, audio, imaging, and digital data connects to other research and academic networks at private and public Internet Exchange Points (IXP). DREN today has a mix of more than 225 sites at DS-3 through OC-48 rates. The HPCMP will continue to upgrade DREN by establishing connectivity at new sites, increasing bandwidth at existing sites, as well as inserting technology across the network.

Objectives.

The objective of this contract encompasses state-of-the-art WAN data transfer and related services to support DREN customers. DREN’s primary mission is to support the research and development communities of the DoD. The primary customer support within DoD focuses on Science and Technology (S&T), Test and Evaluation (T&E), and Modeling and Simulation (M&S). DREN also provides transit, network, and security support to other Federal Agencies and academia.

Synopsis of Future Network.

DREN III is expected to be a sophisticated, robust, high performance WAN employing the latest commercially available technology. DREN is a high performance network, serving its customers with the latest services available in the industry – with technological refreshment infusion ongoing through the life of the contract. The DREN III network is expected to continue advancing this concept systematically throughout its operational life.

The DREN III network will be required to provide services based on Ethernet and optical technology with protocols including IPv6 and IPv4. Optical capabilities and services represent the way forward for high capacity and high performance as well as scalable internal and external interchange for an ever increasing demand.

DREN services shall be delivered to a DREN customer site at a physical interface called a SDP. The SDP is where the provider’s service network ends and the customer premises network begins (see Figure 6.8.1a). Interconnectivity is required internally between DREN locations as well as externally with DoD, Federal, research, academic, and other Government-designated networks at both private and public IXPs. All DREN customer locations require the ability to reach the Internet via DREN connectivity which will be provided by the Contractor.

The DREN network is engineered to support applications to include, but not limited to, video, audio, imaging, distributed storage, and digital data services. Demands of the DREN III network will be even higher as it must be engineered to meet the ever-increasing complexity of the DREN customers’ mission requirements in a distributed and interactive computing environment while meeting more stringent security and separation requirements.

The architecture must incorporate a complex design of multiple routing and security domains in order to address the needs of groups of DREN customers and applications that have a consistent over-arching governance – Information Assurance (IA) governance in particular – and other relationships requiring different levels of separation and protection of the traffic from other traffic traversing the network. These groups are hereinafter referred to as “collectives”. Further, more exclusive subsets of these groups of applications or connections--referred to as “communities of interest”--require separation, connectivity, or traffic handling refinements within these collectives, adding some complexity to the overall design. (For a more detailed discussion of “separation and protection” and “collectives” refer to Attachment D and Attachment E, respectively.)

The current DREN serves more than 225 service delivery points. Cutover to the replacement network is expected to be essentially transparent to the existing DREN customers. The current SDP sites and their associated bandwidths are identified in Attachment B.

DREN III Program Objectives.

Data transport service requirements for DREN III are derived from customer requirements for remote computer operations and the need to engage in collaborative initiatives in distributed and interactive environments. Many DREN customers employ applications that require enormous computing capabilities. The corresponding network traffic to support these HPC and distributed collaborative environment capabilities is projected to require constant increases in bandwidth throughout the life of the contract.

Therefore, DREN III services will support the following:

a. Collaboration and effective pooling of resources.

b. Real-time scientific visualization.

c. Rapid access to multi-media libraries and large distributed computational resources using meta-computing approaches.

d. Access for DREN sites to the Internet, national research and education networks, national and regional optical networks, and various R&D network test beds.

e. Connectivity between DoD Shared Resource Centers for large scale distributed computing, distributed mass storage file systems, and archival storage.

f. Very large single stream data rates between user desktops and large scale computational systems, databases, libraries as well as other systems.

g. Special dedicated connectivity between members of a Collective or Community.

h. Shorter term dedicated (virtual) connectivity builds for special projects, exercises, and demonstrations.

Scope.

DREN is a “SERVICES” contract providing a robust, high capacity, low latency network capability in support of DoD S&T, Research Development Test & Evaluation (RDT&E) Communities. The service shall be engineered to support applications to include, but not be limited to, video, audio, imaging, distributed storage, and digital data connections provided both internally among directly-connected DREN customers and externally to other DoD, Federal, research and academic networks both at private and public IXP.

Continuity of DREN Services.

The Contractor shall provide all labor, management, supervision, supplies, materials, equipment, and tools not otherwise provided as Government furnished property to perform the non-personal services required to acquire state of the art WAN services to support DREN III. Current DREN networking capability is being provided under the DREN telecommunications services contract administered by the Contracting Officer. This procurement will enable continuation of DREN network capability.

Service Locations and Duty Hours.

The Contractor shall provide WAN services on a 24 hour, seven (7) day a week basis. Locations supported under the current DREN contract are specified in Attachment B, although service to all existing locations may not be ordered under this solicitation. Additional locations may be added as fully negotiated modifications to the base contract. Locations can be both within and outside CONUS.

Performance Requirements.

The Contractor shall deliver the services set forth in this PWS pursuant to issuance of delivery orders. The Contractor, acting independently, not as an agent of the Government, shall furnish all management, personnel, equipment, software, services, travel, and other items necessary to successfully deliver the indicated services. DREN WAN services shall be delivered to Government designated locations referred to as SDP Sites. The Contractor shall implement and operate the services required in this PWS. The Contractor shall comply with the standards identified in Attachment F in performance of the services provided under this PWS.

Task 1. Enterprise Management Controls.

Subtask 1. Program Management.

The Contractor shall provide planning, direction, coordination, and control necessary to accomplish all requirements contained in this contract. The Contractor shall determine and establish the project organization that shall provide overall management of the contract work. The Contractor shall designate a key individual who is responsible for the cost, schedule, and technical performance on the contract and who shall serve as a primary point-of-contact for both management and technical matters. In addition, the Contractor shall conduct program review meetings and produce documentation to keep the Government informed on the status of all tasks. References to “the Government” in this PWS shall be interpreted to mean an authorized Government representative as designated by the Contracting Officer.

Subtask 2. Program Management Office.

The Contractor shall establish and operate a Program Management Office (PMO) to provide management and operations support to the Government and to act as a single point of contact for Government management and administration of the DREN contract. The Contractor shall provide a central coordination point for all DREN problems not resolved at the local site or DREN Network Operations Center (NOC).

The minimum normal business hours for the PMO shall be Monday through Friday from 8:00 AM to 5:00 PM Eastern Time (ET). The PMO shall be established upon contract award and be fully operational within thirty (30) business days following contract award. The PMO shall coordinate with designated Government representatives on an ongoing basis and act as a source of information and assistance for this contract. The PMO and NOC shall have video-teleconferencing (VTC) capabilities compatible with VTC capabilities used by the HPCMP Office (HPCMPO).

Subtask 3. Project Management Planning and Control.

The Contractor shall develop a plan of action and schedule for meeting the requirements set forth in this contract. The Contractor shall include the following in all such planning activities: risk management practices, procedures, and tools that will be used to control resources; schedules and procedures for developing deliverables and providing services required under the contract.

Subtask 4. Progress Reporting.

The Contractor shall participate in weekly status meetings with the Government on accepted and proposed network modifications and deliver progress reports on a quarterly basis. The quarterly progress report will identify significant activities, problems, and accomplishments during the preceding three months. The quarterly report shall also identify significant areas of technology improvement within the Contractor’s core infrastructure.

Subtask 5. Support for the DREN Configuration Control Board (CCB).

The Contractor shall support preparation for and execution of DREN CCB meetings by:

1. Assisting in the development of weekly meeting agendas by tracking unresolved issues;

j. Planning and tracking of approved network modifications and upgrades;

k. Planning and tracking all SDP installations, SDP plans, as well as SDP upgrades, modifications and terminations;

l. Generating meeting minutes and addressing action items.

All Configuration Management records must be kept current and accurate.

Subtask 6. DREN Technical Advisory Panel.

The DREN Technical Advisory Panel (TAP) is a working group under the DREN Project Manager (PM). The TAP consists of HPCMP personnel, Service and key site representatives, and significant community of interest representation. Proposed major network modifications, upgrades and improvements shall be vetted through the DREN TAP for discussion before final approval by the HPCMPO DREN PM and DREN contracting officer. The Contractor shall participate and assist in TAP activities as needed. The Contractor shall support preparation for and execution of the meetings by:

1. Assisting in the development of agendas by identifying issues, problems, and/or opportunities to improve services and systems;

n. Participating in subcommittees, working groups, or other planning and support activities identified in the coordination meetings; and

o. Generating meeting minutes.

These TAP meetings shall take place at a location determined by the Government.

Subtask 7. Operational and Management Review.

The Contractor shall conduct regular quarterly reviews that shall address the current status of technical and programmatic progress, significant infrastructure changes within the DREN boundaries, and significant technology changes within the larger network infrastructure. Each review, at a minimum, shall focus on achievements since the last review, the success of risk management activities, unresolved issues, action items, and problems. The Contractor shall support preparation for and execution of the meetings by:

1. Assisting in the development of agendas by identifying issues, problems, and/or opportunities to improve services and systems;

q. Participating in subcommittees, working groups, or other planning and support activities identified in the coordination meetings; and

r. Generating meeting minutes.

These review meetings shall take place at a location determined by the Government.

Subtask 8. Annual Planning and Design Review.

The Contractor shall conduct an annual review meeting to address the status of available contract services and to assess the potential for changes that can enhance technology, reduce costs, improve end-user services, or enhance administrative and management systems for the DREN. The Contractor shall prepare and present analyses and data to support the Planning and Design Review including, as necessary, the following:

1. Current network design and engineering data;

t. Equipment lifecycle status;

u. Network and security metrics;

v. Growth analyses and resource allocations;

w. Planned transmission network growth;

x. Trend analyses and projections;

y. Security measures and impact;

z. Advanced planning data and contingency plans;

aa. Interfaces with other networks; and

ab. Analyses of changes in technology and/or potential service improvements that may enhance DREN services or reduce costs.

Annual design reviews shall address the current status of technical and programmatic progress, significant infrastructure changes within the DREN boundaries, and significant technology changes within the larger network infrastructure.

The Contractor shall provide a restricted web site to post the above data and present its capability to the Government for approval.

Subtask 9. Annual DREN Networking and Security Conference.

The Contractor shall conduct an Annual DREN Networkers Conference to inform DREN site personnel on topics including network performance and status and plans for the coming year. The conference will be open to DREN site points of contact and users located at the DREN SDPs, HPCMP management personnel, Government network management, and security personnel and support, and Contractors with a role in operation or management of DREN services at the network or SDP level. The Contractor shall perform the following tasks to conduct the Annual Networkers Conference at no additional costs to the Government:

1. Obtain the facility;

ad. Arrange for all scheduled speakers;

ae. Notify DREN site points of contact;

af. Develop a list of attendees and register them upon entrance into the conference;

ag. Provide all necessary audio/visual equipment;

ah. Provide DREN network access for attendees; and

ai. Develop a record of the conference and provide the record to attendees.

The Contractor will recover costs associated with this conference through the registration fees of the attendees. The Contractor shall make every effort to minimize the conference fees. After the conclusion of the conference the Contractor shall provide a record of the conference attendees, fees collected, and expenditures in support of the annual Conference. This conference shall take place at a mutually agreed location. The first conference location will be provided at contract award. Each consecutive year’s location will be announced at the conclusion of the previous annual conference.

Subtask 10. Other Conferences.

The Contractor shall coordinate other Conferences, which shall be separately priced, on an as negotiated basis. Once ordered, the Contractor shall perform the following tasks to support such conferences:

1. Obtain the facility;

ak. Arrange for scheduled speakers;

al. Notify points of contact;

am. Develop a list of attendees and register them upon entrance into the conference;

an. Provide all necessary audio/visual equipment;

ao. Provide network access for attendees; and

ap. Develop a record of the conference and provide the record to attendees.

Such Conferences shall take place at a location approved by the Government.

Task 2. Implementation and Transition.

The Contractor shall perform the necessary planning and actions to successfully implement and transition the DREN SDPs. During transition, the Contractor shall establish and maintain full interoperability with the existing DREN at Contractor-provided inter-network gateways (traffic exchange points) until all sites are transitioned. During and subsequent to transition, the Contractor shall establish and maintain high performance Internet transit service, as well as regional IP transit, via peering arrangements with major Tier 1 and Tier 2 service providers.

The Contractor shall manage the transition of an existing DREN SDP for which a Delivery Order is issued to the DREN III. The transition of existing DREN SDPs shall be completed in two phases. Phase I shall include those sites identified for the Initial Performance Capability (IPC) demonstration; Phase II shall include all other existing SDPs for which a Delivery Order is issued. The Contractor shall provide for Government approval, an individual plan for each phase that identifies all task activities and schedule milestones associated with the activities described below. After contract award, the Government will provide to the Contractor all releasable engineering and technical data from the existing contract to assist in development of these plans.

Subtask 1. IPC Transition Planning (Phase I).

The Contractor shall develop and submit the general approach, along with a timeline and site selections for the IPC demonstration. A proposed plan for the IPC demonstration shall be submitted by the Contractor in addition to the Proposal in response to this solicitation. The initial draft plan shall demonstrate an overall reasonable, logical and realistic methodology for the transition, as well as processes to be used, and projected schedules or timelines. The plan shall also specifically include the Contractor’s approach to selection and transition of ten (10) initial sites for Government approval. The Contractor shall identify geographically disparate sites from the categories listed in Attachment B. The ten sites selected shall contain at a minimum two (2) from category A, two (2) from category B, three (3) from category C, as well as one (1) new DREN III IXP. The remaining two (2) sites can be selected from any of the above.

An updated draft of the IPC plan will be submitted within thirty (30) calendar days following contract award. The Government shall review and provide comments to the Contractor on the draft plan not later than five (5) working days following receipt of the plan. The Contractor shall submit a final IPC plan within fifteen (15) days following receipt of Government comments. The Government will provide comments or accept the final Plan within five (5) working days following receipt of the Plan.

The Contractor’s plan shall include sections detailing the testing procedures, applications and equipment to be used for acceptance testing of individual SDPs, as well as for an aggregate test. The section addressing an aggregate SDP test plan shall detail procedures, applications and equipment for simultaneous operation of all SDPs under test. At a minimum, the procedures shall include:

1. Demonstration of the operation of the Digital Data Transfer Services to comply with subtask 6.4.2.

ar. Demonstration of successful completion of routine service configurations as described in Subelement 6.23.1.1.1;

as. Additional criteria to verify the services required by SDPs, as set forth in the Contractor's proposal incorporated as part of the contract upon award.

Subtask 2. Comprehensive Implementation and Transition Plan (CITP) (Phase II).

The Contractor shall prepare and submit a CITP detailing the planning, processes, and activities for Phase II transition. A draft CITP shall be due within thirty (30) days after acceptance of the final report following successful completion of the IPC demonstration. The Government shall review and provide comments to the Contractor on the draft plan not later than five (5) working days following receipt of the plan. The Contractor shall submit a Final CITP within fifteen (15) days following receipt of Government comments. The Government will provide comments or accept the final plan within five (5) working days following receipt of the Plan.

Throughout Phase II, for tracking purposes, the Contractor shall continue to update and revise (as applicable) appropriate sections of the Final CITP to account for the work being performed and completed.

The CITP shall include, as a minimum, the elements described below.

Element 1. Transition.

The Contractor’s plan shall provide details for transitioning services from the existing contract to the follow-on DREN contract. The Contractor shall use a Government-provided inventory of customer locations, facilities, and services as the basis for development of the plan. The Contractor shall ensure the plan describes all aspects of the transition process, including logistics, emergency procedures, and database and operation support system requirements and uses. The Contractor shall include in the plan gateways interconnecting the new DREN III–including Internet transit service and regional IP transit–with the existing DREN II–including Internet transit service and regional IP transit–to ensure a transparent transition with minimum effects on service quality and availability.

The plan shall include gateways supporting high performance data transfer greater than or commensurate with existing capacity today between DREN and other non-Contractor networks, both Government and non-Government, to ensure minimum impact on service quality and availability during transition. The plan shall include procedures for conducting site surveys. The Contractor shall describe the approach for serving as the single point of contact during service transition, and the activities and functions it will perform to coordinate activities with Government personnel and other Contractors as necessary. The Contractor shall also describe an approach for coordinating with site personnel and carriers to resolve service troubles encountered during implementation and site cutover.

Element 2. Interoperability.

The Contractor’s plan shall provide detail for interoperating with other telecommunications networks and services. The Contractor shall describe an approach for interfaces and interoperability in terms of the full range of applicable communications functions, including addressing plans, access control, network management, signaling, and timing and synchronization. The Contractor shall also specify interfaces and inter-connectivity between the DREN network and other networks, and define its approach for working with the service providers for these other networks.

The Government will provide an autonomous system number (ASN), IP address blocks, and domain names that will be used for the DREN community between internal and external networks. The Contractor shall be responsible for managing the administration of these items. The Contractor shall establish and maintain high performance Internet transit service, as well as regional IP transit, via peering arrangements with major Tier 1 and Tier 2 service providers. The Contractor also shall provide detail for interoperating with other Government and non-Government networks. The Contractor shall describe gateways to support high performance data transfer between DREN and other Government and non-Government networks.

Element 3. Security.

The Contractor’s plan shall detail the approach for implementing the security requirements detailed in Paragraph 12 of this PWS.

Element 4. Implementation Schedule.

The Contractor’s plan shall provide an implementation schedule for completing the transition. The Contractor shall develop milestones for all facets of the engineering, implementation, and testing activities required to implement and deploy services to each end-user SDP, to include establishing Internet transit service. The Contractor's implementation schedule shall conform to the priorities established by the Government for cutover of specific end-user SDPs. Schedule data shall be provided using Microsoft Project application software.

Element 5. Cutover.

The Contractor shall describe an overall approach for cutover of services at all SDPs. The Contractor shall consider impact to communities of interest under consideration, performance issues, and other concerns such as security.

Element 6. Customer Notification.

The Contractor shall identify its approach for notifying site communications personnel of pending service cutovers and of pending Contractor-conducted testing thirty (30) calendar days in advance of the date cutover and/or testing activities will begin. The Contractor shall describe its approach for notifying site communications personnel of procedures for using services during initial cutover, and procedures for using new services as they are deployed over the life of the contract. The Contractor shall also describe its approach for supporting site communications personnel in the resolution of end user troubles during the transition period.

Element 7. SDP Site Surveys.

Upon execution of a delivery order by the Contracting Officer, the Contractor shall conduct CONUS and OCONUS site surveys at each SDP as identified in Attachment B. The Contractor shall contact the site POC at least fifteen (15) calendar days prior to the survey. The Government will provide a list of site POC’s after contract award. Site survey results shall be posted for access by HPCMP management and network personnel within five (5) working days following the survey.

Element 8. Master SDP Plan.

The Contractor shall provide a Master SDP Plan that documents all standard requirements and processes for installing equipment in buildings and on a facility to support delivery of DREN service to a location. The Master SDP Plan shall detail all vendor and industry standards pertaining to installation and maintenance of the SDP and site and equipment requirements, e.g., power, HVAC, plumbing, floor loading, storage, etc, as identified in Attachment G.

The Contractor shall also address standard processes and procedures proposed to support upgrades, e.g., WAN connections, new interfaces or services, to an existing SDP; for problem identification and resolution; termination or restoration of an existing SDP; training, etc. The Master SDP Plan shall reference and shall support the SDP Acceptance Test Plan described in Subtask 6.4.2.

A Draft Master SDP Plan shall be submitted as part of the Draft CITP within thirty (30) days after acceptance of the IPC Demonstration Report. The Government shall respond with comments and recommendations. The Contractor shall submit a proposed Final Master SDP Plan within fifteen (15) calendar days of receiving comments and recommendations from the Government.

The Contractor shall update, revise and maintain the Master SDP Plan throughout the life of the contract.

Element 9. Internet Services During Transition.

During the transition the Contractor shall provide high performance Internet transit service, as well as regional IP transit, in accordance with requirements established in Subtask 6.13.7, Gateways, to support DREN sites during and after transition. The data transfer rates at these IXPs shall be sufficient to support intra-regional traffic exchanges between the DREN and the Internet and between the DREN and other Tier 1 and Tier 2 networks. The Contractor shall not use another Tier 1 network, i.e. the network provider from whom a DREN customer is transitioning, for transit of DREN traffic to another Tier 1 or Tier 2 ISP during the transition.

Task 3. Implementation and Transition Actions.

Subtask 1. Phase I Actions.

The IPC will demonstrate and prove the Contractor’s proposed process for the installation and testing of the block of SDPs, as well as the initial ramp-up of other capabilities such as on-line reporting of the DREN services environment. The Contractor shall utilize only Contractor-provided resources; no Government CPE shall be utilized. Native IP multicast, both IPv6 and IPv4, shall be available during this phase.

Upon direction of the Contracting Officer, the Contractor shall execute the approved IPC Plan that governs the actions associated with the installation of the set of SDPs identified for the IPC demonstration.

The Government may delay the start of the aggregate SDP test, at no further cost to the Government, but such delay may not exceed ten (10) workdays.

Upon completion of the activities described above, the Contractor shall prepare and post for Government approval an IPC Acceptance Report documenting all results of the execution of the test(s). This report shall document the full completion of the IPC demonstration and at a minimum shall include a copy of acceptance reports for each of the individual SDPs, the aggregate SDP test and other Government-approved tests. The Contractor will be reimbursed at the completion of an acceptable IPC and upon Government acceptance of the IPC demonstration report. During the IPC, the Government will collaborate with the Contractor to prioritize the remaining DREN II sites identified as candidates for transition in Phase II to the DREN III network. However, no additional Delivery Orders will be issued by the Government until the IPC demonstration has been accepted by the Government.

Subtask 2. Phase II Actions.

Following completion and acceptance of the IPC demonstration report and upon direction of the Contracting Officer, the Contractor shall execute the revised and approved CITP that governs the actions associated with the installation of the Phase II set of SDPs.

The Government may issue one or more delivery orders to initiate the transition of SDPs that currently comprise the DREN. The transition of these remaining sites is collectively referred to as Phase II. Phase II provides for the implementation and testing of existing SDPs to be transitioned and any additional DREN service capabilities not completed in conjunction with the IPC demonstration. A discrete delivery order will be issued for an individual site, i.e., one site per delivery order, although multiple customers or enclaves may be supported by an SDP at an individual site. Delivery orders for the transition of SDPs during Phase II may be issued individually or in groups or bundles, i.e., multiple delivery orders.

The Contractor shall install and document ordered SDPs during Phase II in accordance with the Government-approved Final Master SDP Plan detailed in 6.2.2.8 and implement the Acceptance Test plan for individual SDPs detailed in the CITP. The results of such testing shall govern acceptance of each individual SDP during this phase. Upon completion of the SDP Acceptance Test, the Contractor shall submit Individual SDP Reports to address site-specific details, including any variance from the standards documented in the Master SDP Plan. The Individual SDP Report shall be due within fifteen (15) Calendar days of completion of the test as outlined in section 6.4.1. Individual SDP Reports for the IPC set of SDPs shall be created or updated and submitted in accordance with the Final Master SDP Plan prior to acceptance of any Phase II Individual SDP Reports.

Throughout Phase II, the Contractor shall continue to update and revise (as applicable) the CITP to account for the work being performed and completed.

Subtask 3. Transition Review.

The Contractor shall monitor and report on the efficiency and effectiveness of transition on a monthly basis. In addition, the Contractor shall conduct weekly status meetings on the progress of transition until all existing DREN SDPs have been transitioned to the DREN III contract. These weekly status meetings shall be conducted by VTC or conference bridge provided by the Contractor.

After transition of the SDPs identified for the IPC, the Contractor shall conduct regular quarterly reviews until Phase II transition is complete. Each review, at a minimum, shall focus on achievements since the last review, the success of risk management activities, unresolved issues, action items, and problems.

The Contractor shall support preparation for and execution of the meetings by:

1. Assisting in the development of agendas by identifying issues, problems, and/or opportunities to improve services and systems;

au. Participating in subcommittees, working groups, or other planning and support activities identified in the coordination meetings; and

av. Generating meeting minutes.

The quarterly review meetings shall take place at a location determined by the Government.

Task 4. Install, Modify, Terminate, and Restore SDPs.

The Contractor shall install, modify, terminate, and restore SDPs in accordance with the terms of the applicable Delivery Order and the PWS. The Contractor shall be responsible for obtaining, provisioning and maintaining all equipment and software for each SDP.

Subtask 1. Individual SDP Reports.

Upon execution of a delivery order or delivery order modification by the Contracting Officer, the Contractor shall conduct as necessary a site survey and post the results for access by HPCMP management and network personnel within five (5) working days following the survey.

A Draft Individual SDP Report shall be submitted no later than fifteen (15) calendar days after completion of the SDP Acceptance Test. The Draft Individual SDP Report shall address site-specific details, including any variance from the standards documented in the Master SDP Plan and incorporated elements and standards identified in Attachment G. The Draft Individual SDP Report shall also include an as-built diagram of all equipment and cabling to support the SDP and the results of the SDP Acceptance Test. The Government shall review and provide comments and recommendations. The Contractor shall submit a proposed Final Individual SDP Report within fifteen (15) calendar days of receiving comments and recommendations from the Government. .

The Individual SDP Report shall be submitted in an electronic form agreed to by the Government and either encrypted or password protected for transmission purposes only. The Individual SDP Report shall be updated and maintained throughout the life of the contract including documenting modifications to the SDP.

Subtask 2. Acceptance Test Plan.

When a new SDP is ordered, the Contractor shall validate the proper installation and operation of a DREN SDP with its ordered service and interfaces in accordance with the approved SDP Acceptance Test Plan. The objective is to ensure that an ordered DREN SDP with one or more interfaces is configured correctly and will operate in accordance with DREN III service requirements. Successful testing in accordance with the approved plan will result in an "active” SDP with services and interfaces that meet the requirements specified in this PWS.

The Acceptance Test Plan, originally created during transition and detailed in the CITP, shall identify all reference SDP(s), e.g., SDP 0, and any additional reference test points on the Contractor network. The Test Plan shall specify the physical location and describe the configuration(s) and capabilities of all reference SDPs and test points. The Test Plan shall identify all applications or hardware supported at each of the reference SDPs and test points. The Test Plan shall also describe the signal flow(s) between the SDP under testing and the reference SDPs or test points that may be utilized during testing.

The Acceptance Test Plan shall identify the location(s) and personnel involved in acceptance testing, identifying conditions under which an individual or agency might be involved or not involved in testing.

The Test Plan shall describe initial acceptance testing of an SDP and testing conducted to accept an upgrade or new service ordered for an existing SDP, to include personnel, applications and hardware involved in each.

The Acceptance Test Plan shall specify the information included in the report generated for each SDP under testing. The Contractor shall submit an acceptance test report for each SDP within five (5) calendar days following testing. At a minimum, the Test Plan shall specify and the report shall include:

1. Day and date of testing.

ax. Reference testing location(s).

ay. Domain Name Service (DNS) name of the SDP under testing.

az. The latitude and longitude of the SDP under testing.

ba. Line-of-sight (LOS) distance in kilometers between the reference testing location(s) and the SDP under testing.

bb. Type of service(s) or interface(s) tested.

bc. Test equipment or applications used.

bd. Service Performance, e.g., latency, throughput, packet loss, etc., to be measured.

be. Metrics captured.

The Acceptance Test Plan shall provide a table detailing each test performed during the initial Acceptance Test following installation of an SDP. The table shall identify the PWS reference and description for each characteristic of a service or interface to be tested.

The Contractor shall submit a sample test plan for Government approval with this proposal.

The Government reserves the following rights:

1. To witness the SDP Acceptance Test;

bg. To delay the start of the SDP Acceptance Test, at no additional cost to the Government, but such delay will not exceed two (2) workdays; and

bh. To require the Contractor to rerun, at no additional cost to the Government, all or any portions of the SDP Acceptance Test in the event that the SDP fails to satisfy any of the test criteria.

Subtask 3. SDP Modification.

The Contractor shall provide a description of required changes for each SDP modification or upgrade action. In the event that a site survey is required to document the required changes, the Contractor shall contact the Government-identified Site POC at least fifteen (15) calendar days prior to the survey to schedule the visit.

Each description shall address the following:

1. Transmission media construction such as cabling, repeaters, and conduits.

bj. Building modifications, if any, necessary to install equipment and run cables.

bk. Storage space requirements.

bl. Staging area requirements.

bm. An analysis of the impact on active SDPs at this site and at other sites, including identification of any actions needed to prevent negative impact.

On completion of modification or upgrade the Contractor shall submit "as built" site drawings and diagrams.

Subtask 4. Acceptance Procedures.

Following installation of the SDP, the Contractor shall execute the acceptance tests in accordance with the Government-approved SDP Acceptance Testing procedures.

Subtask 5. Termination / Restoration.

Upon request of the Government, the Contractor shall deactivate and remove the SDP. The Contractor shall identify that equipment or cabling that shall be removed and any that shall be abandoned in place.

In the event that a site…