DRAFT_PWS.pdf

PERFORMANCE WORK STATEMENT

FOR

CHINA LAKE VOIP INFRASTRUCTURE (CLVI) MODERNIZATION

9 May 2019

Prepared by:

UNITED STATES NAVY

Naval Air Warfare Center Weapons Division 7.2.4T00D

1 INTRODUCTION

1.1 BACKGROUND

This project arose out of the need to increase our telephone capability in some areas on NAWS China Lake where the remote SL-100s are already at maximum subscriber capacity. Several solutions were reviewed and we’ve determined that the cheapest and most efficient method to increase capacity is to begin the migration from the antiquated SL-100 technology to state-of-the-art VOIP technology. The initial phase, which requires the most significant infrastructure upgrade, can be accomplished with available current year funds. Subsequent phases can be accomplished within normal funding allocations in future years until all SL-100s have been removed from service and decommissioned. All technology is already in use at many USN and USMC bases so proofing of concept is not required. The new optical network will distribute a highly available Base Area Network (BAN) across China Lake while connecting local exchange carriers (e.g., Public Switched Telephone Network, Defense Switched Network, etc.) at established points of presence.

1.2 SCOPE

This Performance Work Statement (PWS) establishes and defines the requirements for the contractor to engineer, furnish, install, secure, test (EFIST), and make operational a turnkey (Unified Communications (UC) compliant solution for the modernization of the existing communication infrastructure at China Lake. The contractor shall also provide all ancillary components, site and facility preparation, labor, training, supporting equipment, software, firmware, licenses, power, grounding, and interfaces associated with these systems for a complete turnkey solution.

The initial scope will focus on the creation of an Assured Services Local Area Network (ASLAN) with a CORE Layer 2/3 switch, the installation of VOIP Telephone Switch software on virtual servers, and the installation Passive Optical Network (PON) technology to distribute VOIP and/or POTS telephone service at Weapons Survivability Lab (WSL) and Supersonic Naval Ordinance Research Track (SNORT).

1.3 PERFORMANCE OBJECTIVES

1.3.1 The performance objectives are:

1.3.1.1 The EFIST of a VOIP telephone switch with 1500 licenses.

1.3.1.2 The EFIST of a PON network consisting of the following:

1.3.1.2.1 An Optical Line Terminal distribution shelf such as the Tellabs 1150E or similar. It must support high-density enterprise needs and fit in 19" racks within the data communication center. Must be able to provide service directly from a VOIP telephone switch, application servers and unified communications systems, specifically targeting pure VoIP, IP video and IP/Ethernet data service delivery.

Must support ESU2 equipped in simplex or duplex for high availability. Must have OLT distribution shelves to support common software and common hardware and provide options for multiple 10 GbE and 1 GbE Ethernet uplinks. Must be capable being equipped with G-PON, Ethernet, ADSL2+ and VDSL2 service cards, supporting both Passive Optical LAN and Multiservice Access architectures depending on government needs.

1.3.1.2.2 Optical Network Terminals such as the 4-Port Gigabit Ethernet Tellabs 142R and 24-port Gigabit Ethernet rack mounted Tellabs 729 or similar.

- ONTs must be supported from the OLT and allow service-level VLANs segregate and secures data flow to each client device.

o Must support traffic classification per IEEE 802.1p, IEEE 802.1q and even DSCP for voice o Must Support Dynamic Bandwidth Allocation for burst upstream traffic o Must Support Type-B PON protection for redundant path to ports, modules or OLT o Must support Link Layer Discovery Protocol (LLDP) for automated provisioning, power management and enhanced 911 location service

- The 4-port ONT must provide the optical to electrical conversion providing the PON to Ethernet transition. The ONTs must support voice (both analog and VoIP), and data and video (both RF and IP). Analog voice must be supported with SIP agents at RJ-11 POTS ports or VOIP voice can be supported over RJ-45 data ports.

- The 24-port ONT These ONTs support voice (both analog and VoIP), data and all forms of IP video (security, conference). Analog voice must be supported with SIP agents at a standard RJ-21 50-pin connector (e.g., RJ-21), and VOIP voice supported over RJ-45 data ports.

1.3.1.3 This project will require GFE virtual server space within the Data Center and the use of RTD&E and customer fiber optic cable as government furnished equipment. The installation vendor will provide the software, hardware, installation, and training on the new systems.

2. SPECIFICATIONS

Table 1: Minimum OLT specifications should include the following; final determination will be made based on final architecture design

Height 15.75"/9 RU Width 19" Depth 12" Fan units 3.50"/2 RU Power Source External rectifier Multiservice slots 14 Shelf backplane capacity* 1.12 Tbps* Bandwidth slot capacity 80 Gbps* Total G-PON ports 56 Total ONTs served Up to 1,792 Total Ethernet ports served Up to 7,168 Ethernet Switch Unit slots 2 10 GbE interfaces (with dual ESUs) 4 1 GbE interfaces (with dual ESUs) 8

*Shelf and slot capacity calculated based on shelf being equipped with next generation ESU and next generation 10G XG-PON service module

Table 2: Minimum ONT specification include the following:

ONTs Services Size Mounting Interfaces Features 4-Port Gigabit Optical Network Terminals

• VoIP/POTS

• IP Video/RF Video

• data

• 8.6 in/220 mm

• 6.6 in/168 mm

• 1.3 in/34 mm

• indoor

• desk or wall

• free-standing

• vertical/ horizontal

• secure /lockable

• (4) 10/100/1000

• (2) POTS

• (1) RF video

• local

- power

- battery

24-Port Gigabit Optical Network Terminals

• VoIP/POTS

• IP Video

• data

• 1.7 in/43 mm H

• 17.3 in/439 mm W

• 17.5 in/279 mm D

• indoor

• rack mount

• comm. closet

• IDF or zone box

• (24) 10/100/1000

• (24) POTS

• remote or local

- power

- battery

• PoE

3 PERFORMANCE REQUIREMENTS

3.1 GENERAL REQUIREMENTS

The contractor shall be responsible to EFIST and make operational a completely functional VOIP and PON system in the locations identified in the attachments with the required programming, interfaces, hardware, software, software licenses, ancillary equipment, power, parts, databases, and material for all identified users, services, and requirements.

All equipment hardware and software installed must be listed on the DISA Approved Products List at the time of contract award and the expiration date must be valid through the period of performance.

The contractor shall use, to the greatest extent possible, existing software licenses from the AS-5300 and SL-100s and/or any Commercial Off-the-Shelf Software (COTS) products available from the Department of the Navy (DON) Enterprise Software License (ESL) agreements for any software required to support their proposed solution.

The contractor shall be responsible for replacing and correcting any hardware, software, applications, data, configurations, material, or services omitted and/or installed in contractor error without any extra expense or delay to the Government. The contractor shall not be responsible for replacing or correcting existing Government property, software, or facility problems, outside the scope of this PWS.

3.1.1 DOD UNIFIED CAPABILITIES REQUIREMENTS

All proposed UC system hardware and software shall be configured in compliance with the latest version of the DoD Unified Capabilities Requirements (UCR), applicable Military Unique Deployment Guide (MUDG), and Security Technical Implementation Guide (STIG).

3.1.2 JOINT INTEROPERABILITY TEST COMMAND CERTIFICATION

All proposed UC system hardware and software shall have received Joint Interoperability Certification (JITC) in accordance with the latest version of the DoDI 8100.4, Unified Capabilities before the system can be connected to the DoD Information Network (DODIN). All proposed system hardware and software shall have a valid JITC certification by Test Readiness Review (TRR). Connection to the DODIN will not be authorized until certification is updated and the system is fielded in accordance with the certification letter and JITC deployment guides associated with the system. A non JITC certified system maybe proposed if a road map and plan of actions and milestones to achieve JITC certification is provided in the offeror’s proposal. Additionally, the offeror shall provide a mitigation plan in the event that the proposed system does not achieve the required JITC certifications by TRR.

If JITC certification expires on any proposed system during the period of performance the offeror shall provide a road map and plan of actions and milestones for extending JITC certification prior to the TRR.

3.1.3 DOD RISK MANAGEMENT FRAMEWORK FOR DOD INFORMATION TECHNOLOGY

Before the UC hardware and software can be connected to the DODIN, all system hardware, software, and ancillary equipment shall receive Cyber Security accreditation in accordance with the latest version of the DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT). In addition, the contractor shall assist the Government by providing, developing, and submitting any necessary system documentation, settings, specifications, and hardening (STIGs, vulnerability scans, testing and installing patches, and vulnerability mitigation) required to for the Government Assessment and Authorization (A&A) package.

3.1.4 NETWORK INFORMATION ASSURANCE PROVISIONING AND CONFIGURATION

The contractor shall coordinate with the designated VOIP/PON Project Manager, Cyber Security Representative, and Engineer prior to implementation to determine all cyber security requirements are applied to all system components to ensure cyber compliance. At a minimum, the contractor shall provide the following items for Government review: System Configuration Hardware/Software Baseline, Network/security configurations, system and equipment warranties, software license agreements, software upgrades, and all documentation required to support the A&A and CCB processes. The contractor, in coordination with the VOIP/PON Project Manager and Cyber Security Representative, shall perform all recommended cyber settings, programming, and configurations of components being provided to ensure compliance with all cyber requirements.

3.2 SYSTEMS PERFORMANCE REQUIREMENTS

3.2.1 ENTERPRISE UNIFIED CAPABILITIES

The contractor shall propose a voice and PON solution and shall include any Basic User License fees, terminal numbers, and/or licenses associated with the installation

Each new voice gateway shall be fully wired to the Main Distribution Frame (MDF), Intermediate Distribution Frame, or 110 Blocks as appropriate, will be equipped with all required common control and power cards, and will be connected to the assigned local session controllers (LSC). The contractor shall EFIST and make operational any new cards required to support a mixture of analog and ISDN Primary Rate Interface (PRI). The contractor shall provide all associated hardware for the installation of multi-purpose gateways. The contractor shall test all ports, cables, and jumpers after installation is complete.

The wired subscriber port capacity shall be provided as pre-wired hardware (i.e., shelves, drawers, common control circuit packs, etc.) and must have the ability to be activated only through the use of basic switch translations and the installation of subscriber port and/or trunk circuit packs.

The contractor shall provide 26 VOIP replacement phone sets at the time of systems cutover. The replacements are provided to support the operations and maintenance of the voice network after Government acceptance. An additional 24 VOIP phones shall be provided as spares for future adds/moves/changes.

ENGINEERING DESIGN PACKAGE

As part of the Materials and Equipment List the contractor shall provide the manufacturers’ recommended minimum essential spare parts for equipment and systems provided under this PWS in order to alleviate system downtime in the event of a critical hardware failure. The minimum essential spares shall be identified separately in the Materials and Equipment List. The contractor shall restock any spare parts utilized during the warranty period.

TEST AND EVALUATION

Test and Evaluation (T&E) is an integral part of the systems engineering process. Testing of the CLVI solution shall be performed in two phases, the System Acceptance Test (SAT) and the Government Acceptance Test (GAT).

3.3.1 SYSTEM ACCEPTANCE TEST

SAT is vendor performed testing that occurs prior to Test Readiness Review. The Government may observe some SAT tests; however, it is not required. It is expected that the vendor will install and test subsystems and components without connection to the DoDIN. This implies that complete testing of a subsystem cannot be completed in all cases. The vendor has latitude to schedule and execute these tests.

3.3.2 GOVERNMENT ACCEPTANCE TEST

Government Acceptance Test (GAT) is all testing performed after TRR. This testing consists of a combination of government and vendor executed tests. GAT testing will be final testing and all connections and interfaces shall be established during this time. All tests not completed during SAT shall be completed during GAT.

3.3.3 SYSTEMS ACCEPTANCE TEST PLAN

The Contactor shall prepare a Systems Acceptance Test (SAT) Plan that encompasses all system and sub-system test activities planned for each system. The following areas shall be emphasized in the SAT Plan:

Test Event, Purpose of the Test, Date of Test (Start and End), Location of the Test, Need for Government Test Support, Schedule of Individual Test Events, and Tests Procedures. The Contactor shall provide Test procedures, as individual appendices to the SAT Plan, for each system and sub-system delivered under this PWS. The Test Procedures shall include all test cases and test scripts to successfully complete all system and sub-system test.

3.3.4 CUTOVER

The contractor shall be responsible for performing the cutover from the legacy SL-100 to the VOIP switch for all phone lines affected by phase 1. This shall include capturing and validating existing system’s database and subscriber information, transferring information, configuring, and deploying the new system to the end-user device. This information includes, but is not limited to, dial plans, subscriber features and capabilities, call lists, settings and configurations. The cutover shall also include hardware, cabling, and patching of existing subscribers and services. Cutover methods utilized shall minimize service-affecting outages and be described in detail in the Cutover Plan.

CUTOVER PLAN

The contractor shall develop a detailed Cutover Plan. The Cutover Plan shall provide the overall plan including the schedule, required government resources, system outages, and fall back plan. In addition, the plan shall contain the system specific detailed procedures, The contractor shall conduct service-affecting cutovers of systems outside normal duty hours with minimal downtime as designated by the TSO.

During system cutover, the contractor shall track, manage and support all on-site trouble tickets directly related to the cutover to include the creation of tracking reports for active and closed tickets, answering TSO questions, correcting deficiencies, and coordinating with the TSO to prioritize trouble tickets. An electronic and paper copy of the trouble ticket log shall be maintained on site for Government inspection during cutover and shall be turned over to the Government after resolution and closure of all Trouble Tickets directly attributable to the contractor’s solution.

SYSTEM OUTAGES

Any work requiring system downtime shall occur during off-duty/weekend hours, be kept to a minimum, and not occur without specific acceptance from VOIP/PON Project Manager and the site TSO. The contractor shall submit a system recovery/fallback plan for review and acceptance for all scheduled outage. The system recovery/fallback plan shall be provided as part of the Cutover Plan

3.3.5 PROJECT INSPECTION AND ACCEPTANCE

The contractor shall notify the Government upon completion of all tasks under this PWS. Final inspection and acceptance is the responsibility of the COR. Acceptable performance is achieved when all hardware, software, components, and equipment have been provided and installation, integration, testing, demonstration, preventative maintenance, and training are completed. Any defects or other failures undetected prior to Government acceptance does not relieve the contractor from the responsibility for correcting those defects or other failures to meet contract requirements. The Government will provide formal acknowledgement that all terms of the task order have been accepted upon successful completion of requirements of the PWS, receipt of all contract deliverables, and successful completion of the PRR.

3.4 SITE SPECIFIC REQUIREMENT

3.4.1 Building 00033

Install and configure a VOIP telephone switch and associated hardware, software and peripherals in the Data Center. Utilize GFE VMware servers

Install and configure a GFE CORE ASLAN L2/L3 switch in a GFE cabinet, to include the installation of Ethernet or FOC cabling between the VOIP telephone switch, L2/3 switch, and PON OLT.

Install and configure an Optical Line Terminal and DC power supply to include the associated hardware and software in the same GFE cabinet as the ASLAN switch, and to include the Ethernet or FOC cross connects to the ASLAN and base OSP FOC

3.4.2 Building 02664

Install and configure two 4-port Optical Network Terminals connected to the ASLAN to provide service to the G450s and laptops

Install and configure two Media Gateways connected to the ASLAN and to the SL-100 to provide trunking between the VOIP telephone switch and the SL-100

Provide two laptops connected to the ASLAN via the ONTs for the purposes of provisioning devices, and administering the VOIP and PON network

3.4.3 Building 25010 SNORT

Install and configure one 4-port ONT connected to the ASLAN to provide service to the G450s

Install and configure one media gateway connected to the ASLAN and the SNORT CO MDF to replace the SNORT SL-100 currently servicing 68 telephones

3.4.4 WSL Site

Building 31686

Install and configure one 4-port ONT connected to the ASLAN and install and configure two VOIP telephones to replace existing POTS

Building 31196

Install and configure one 4-port ONT connected to the ASLAN, one media gateway connected to the ONT and to the facility IDF to extend 90 POTS telephone service to 21 facilities

Building 31325

Install and configure one 24-port ONT connected to the ASLAN. Extend 24 VOIP telephones using WSL data premise wiring to replace existing POTS services.

3.5 E911 SYSTEM

The contractor proposed solution shall support the E911 interface requirements for China Lake.

Emergency services for China Lake are provided by on-base response teams but the Regional Dispatch Center is located in San Diego. The existing SL-100 voice network interface to the E911 system for China Lake is three (3) DIOD PRI circuits connected to the Ridgecrest Frontier Central Office.

4 PLACE OF PERFORMANCE

The place of performance is Naval Air Weapons Station China Lake, CA.

5 PERIOD OF PERFORMANCE

The period of performance shall be no greater than twelve (12) months from the date of contract award however the contractor should strive to complete the project within six months due to funding restrictions.

6 ADDITIONAL REQUIREMENTS

6.1 WARRANTY

The contractor shall provide a full, unlimited one-year warranty for all contractor provided hardware/software, materials, and workmanship. The warranty shall begin immediately upon Government acceptance of all items delivered under this PWS.

In addition, the contractor shall provide, as a separately priced option exercisable by the Government, an additional one-year extended service agreement that includes hardware/ software/firmware, materials, emergency off-site technical assistance, on-site technical assistance and maintenance support services for the installed system components following the initial one-year warranty period. All services provided under the extended service agreement shall be commensurate with the services provided during the initial one-year warranty period. The extended service agreement shall begin at the completion of the initial one-year warranty period in the event the Government exercises the option.

6.1.1 WARRANTY RESPONSE SUPPORT

The contractor shall provide response support functions during the warranty period. The contractor shall provide a toll-free, telephone hotline(s) for maintenance actions and technical support and for processing warranty claims and. The contractor shall issue initial Return Material Authorization (RMA) to authorize return of defective items and begin tracking through the hotline service. The contractor shall be responsible for all manufacturing defects and support hardware and software assets prior to Government acceptance.

When a problem is identified, the contractor shall respond within established guidelines. Response Support functions include Trouble Ticket reporting that identifies problem/resolution which will be reported to, and monitored by the CLVI Program Office. All issues reported to the program will include at a minimum: date/time received, identification of the issue, resolution [to include changes to Hardware, Software, and/or Tactics, Techniques, and Procedures (TTPs)], and date/time resolved. Issues that cannot be resolved remotely may be elevated to initiation of Field Service Support. Response time, diagnosis time, and resolution time are the metrics for response support. Response time is the time elapsed before the contractor responds to a request for assistance. Diagnosis time is the time elapsed from the response time to identification of the cause of the problem. Resolution time is the time elapsed from the request for assistance to resolution of customer request and closure of helpdesk ticket. The contractor shall meet the response support metrics identified in Table 3.

Table 3 – Response Support Metrics

RESPONSE SUPPORT FUNCTION THRESHOLD OBJECTIVE

Response Time 8 Hours 4 Hours

Diagnosis Time 16 Hours 8 Hours

Resolution Time 24 Hours 12 Hours

6.1.2 WARRANTY RETURN MATERIAL AUTHORIZATION RESPONSE TIME

The contractor shall implement a Return Material Authorization (RMA) and Warranted Item Replacement approach that includes RMA processing time and Turnaround Time (TAT) for all items under warranty. The contractor shall purchase and store an adequate quantity of spares necessary to meet the TAT which is approved by the Government.

6.2 MANPOWER AND TRAINING

6.2.1 TRAINING

TRAINING PLAN

The contractor shall prepare and provide a Training Plan to include strategy, methods, and resources to deliver training. The training must include the VOIP switch operation and maintenance, to include system administration and adds/moves/changes to telephone sets. The Training Plan shall also identify training resource requirements for both the OEM and the receiving units.

TRAINING MATERIALS

The training materials used during the training classes should include OEM operations and maintenance manuals

6.3 RESIDENT SERVICE SUPPORT SPECIALISTS (OPTION)

As a proposed separately priced option, the contractor shall provide one (1) Resident Service Support Specialist (RS3) qualified on the Passive Optical Networking and VOIP telephone switch as on-site full-time subject matter expert to provide maintenance and technical support for at least three (3) months from Final Government Acceptance. The RS3 shall be responsible for assisting with maintenance as needed, assisting with all warranty repairs, component replacements, and the return of all parts. In addition, the RS3 shall be responsible for assisting base telecommunication personnel with technical support that includes systems configuration and training during the option period.

6.4 GREY MARKET ITEMS, LICENSE TRANSFERABILITY, AND END USER

TERMS AND CONDITIONS

In order to minimize the risk of the Government purchasing counterfeit products or unauthorized secondary market equipment, which would not be supported by the Original Equipment Manufacturer (OEM), and to ensure that the Government purchases only equipment that is genuine (i.e., not counterfeit), authorized (e.g., not gray market, includes appropriate licenses, etc.), and supported (e.g., warranty and support services) by the OEM, when it submitted its proposal, the contractor, for:

Hardware: Certifies that it is a Manufacturer Authorized Partner/Reseller as of the date of the proposal and that it continues to have the certification/specialization level required by the Manufacturer to support both the product sale and product pricing, to the extent required by the applicable performance work statement (PWS), and in accordance with the applicable Manufacturer certification/specialization requirements. Unless otherwise specified, contractor warrants that all products provided under this contract are new. By submitting any proposal under this contract, contractor confirms that it has sourced all Manufacturer products it will provide from Manufacturer or through Manufacturer Authorized Partners only, in accordance with Manufacturer's applicable policies in effect at the time of contract award. Contractor agrees that it will provide a list of serial numbers for any hardware provided or installed. Failure to provide this information may result in delays to acceptance and payment. The Government will use this information to confirm with the Manufacturer or OEM that the hardware is (1) genuine (not counterfeit) and (2) authorized hardware that has been sourced and provided in accordance with the Manufacturer’s applicable policies (e.g., not gray market or diverted). If the Manufacturer indicates that the hardware meets these two requirements, the Government will notify the contractor. If the Manufacturer indicates the hardware does not meet these two requirements, the Government may reject the hardware, revoke acceptance, or pursue any other available and appropriate remedies under the contract.

Software: Certifies that it is a Manufacturer Authorized Partner/Reseller as of the date of award and that it continues to have the certification/specialization level required by the Manufacturer to support both the product sale and product pricing, to the extent required by the applicable performance work statement (PWS), and in accordance with the applicable Manufacturer certification/specialization requirements. Unless otherwise specified, contractor shall warrant that all products are new, or, in the case of downloadable software, that all software is sourced from the OEM or Authorized Reseller. By submitting its proposal contractor confirms that it has sourced all Manufacturer products it will provide from Manufacturer or through Manufacturer Authorized Partners only, in accordance with Manufacturer's applicable policies in effect at the time of this contract. Contractor shall certify that it has notified the software Licensor that the United States Navy (Buyer) will be the Licensee. Contractor shall have provided, with any proposal, a copy of the End User License Agreement (EULA), Terms of Service (TOS), or other similar legal instrument or agreement and warrants that all Manufacturer software is or will be licensed originally to Buyer as the original Licensee authorized to use the Manufacturer Software. Note the provisions of FAR 52.212-4(u) apply.

Maintenance: If, during performance of any maintenance required under this contract, the contractor provides replacement hardware or software, then the above Hardware, Software, or both requirements, including all required certification and compliance requirements, apply. The contractor shall ensure that the Government shall have full rights and entitlements to any software maintenance procured under this contract for software for which it has been identified as the original licensee or for which a license is subsequently transferred to the Government.

Hardware, Software, and/or Maintenance: If contractor is not a Manufacturer Authorized Partner as of the date of the submission of its proposal then, as applicable, contractor shall submit with its proposal a document, from the Manufacturer, that identifies the Vendor by name and states the following:

(1) that the products proposed (including hardware, software, and/or support services) are genuine (i.e., not counterfeit and not unauthorized secondary market/gray market products) (note: all items, including part numbers where applicable, shall be listed in the document);

(2) that Vendor has the certification/specialization level required by the Manufacturer to support both the product sale and product pricing, in accordance with the applicable Manufacturer certification/specialization requirements;

(3) that Vendor will be able to receive from Manufacturer, and that Manufacturer will not deny, the support services required to support the product(s);

(4) that Vendor has the authority to transfer to the government all appropriate software licenses associated with the product(s) at no additional cost to the Government; and

(5) that Manufacturer will not deny required warranty support for the product(s).

The Government’s remedies for contractor’s failure to provide conforming products or services consistent with the above requirements are detailed in FAR 52.212-4, with emphasis on paragraphs (a), (m), and (u).

This contract contains the clauses, terms, and conditions acceptable to the Government. Any hardware, software, or maintenance provided under this contract that contains conflicting terms or conditions, including but not limited to an End User License Agreement (EULA), Software License Agreement (SLA), Purchaser User Rights (PUR), Product User Rights (PUR), Software User Rights Agreement (SURA), Support Agreement, Maintenance Agreement, or any other vendor-specific or OEM-specific agreement regardless of how titled or described, may be considered unacceptable. Contractor is on notice that if they choose to submit a document containing terms and conditions, they are required to demonstrate that those terms and conditions do not conflict with, or differ from, this contract’s terms and conditions, as well as any statute or regulation (e.g., Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS)). Contractor must provide the Government with an opportunity to review, modify, and approve any relevant EULA, SLA, SURA, PUR, or any other similar OEM-specific agreement, related to items procured under this contract for which the Government will be the licensee or will otherwise take title to. Compliance with this section is a component of technical acceptability for any proposal and for final project acceptance. Vendor-specific or OEM-specific terms and conditions that conflict with statutory or regulatory requirements, or are otherwise is advantageous to the Government as noted above, may be determined unacceptable.

7 SECURITY REQUIRMENT

The contractor shall coordinate with the VOIP/PON PM to obtain access to NAWS China Lake.

7.1 ACCESS CONTROL REQUIREMENTS

All contractor personnel shall be in compliance with the NAWS China Lake Access Control policy.

Personnel shall be cleared and authorized for access aboard the installation and into base facilities by the installation security office. Any of the following identified shall result in an unfavorable outcome: on a national terrorist watch list; in the United States illegally; subject to a current debarment order from any military installation; a prisoner on work release or parole; a registered sex offender; convicted of a felony within the previous two years; or determined by the Installation Commander to be a detriment to the safety, security, or good order and discipline of the installation.

7.2 VENDOR SCREENING

The vendor shall return a completed SECNAV Form 5512 and NAWS Access Badge Form NAWS5530/1 in order to identify all contractor personnel requiring access to NAWS China Lake, base facilities, and/or handling government assets. This form includes personal identification information for respective contractor personnel and shall be either: hand delivered to the Base Telecommunications Office or sent in a password protected document to raymond.w.richards1@navy.mil. If the vendor screening form is sent via email, the password shall be provided and sent in a separate email. The Contractor shall provide a completed form to the TSO no later than two weeks prior to the start of work for processing and vetting by the NAWS China Lake Security Office. The Security Office will respond with any favorable or unfavorable screening outcomes as they are received. Any personnel receiving an unfavorable outcome will not be authorized access to the Installation for the purpose of performing work related to this contract.

All required escorts shall be provided by Base Telecommunications. It is the contractor’s responsibility to secure any facility the contractor is given a key and unescorted access to anytime they exit the facility.

Base Telecommunications will exercise security supervision over all contractor personnel working on this project and will provide security support to the contractor. The contractor shall comply with all emergency rules and procedures established for this base. All personnel aboard the base are subject to random inspections of their vehicles, personal items, and of themselves. Consent to these inspections is considered to have been given upon entrance to the base and its facilities. Photography, videotaping, and/or audio recordings aboard the base are strictly prohibited without proper authorization by the local base authorities.

8 ADMINISTRATIVE AUTHORITY

8.1 CONTRACTING OFFICER

The Contracting Officer (KO) for this contract is Cheryl McGuire. Only the Contracting Officer has the authority to authorize deviations from the terms and conditions of this contract, including deviations from the specifications and requirements stated herein. In the event the contractor does deviate, without the issuance of a duly executed contract modification, such deviation shall be at the risk of, and any costs related thereto shall be borne by the contractor.

8.2 CONTRACTING OFFICER’S REPRESENTATIVE

The Contracting Officer’s Representative (COR) and Project Manager for this project is Raymond Richards. The COR/PM is responsible for the day-to-day contract oversight and coordination while ensuring that the contract is executed properly and reporting any deviation to the Contracting Officer.

The COR is limited to providing program specific clarifications to the contractor's listed key personnel for this contract, and does not have the authority to take any action, either directly or indirectly, that would change the pricing, quality, place-of-performance, delivery schedule, or any other terms and conditions of this contract or to direct work that goes beyond the scope of this contract’s PWS. If the contractor perceives that the COR or any other Government personnel is requesting an effort outside the existing scope of this contract, the contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the contractor under such direction until the Contracting Officer has issued a contractual change or otherwise resolved the issue.

8.3 TECHNICAL SUPPORT OFFICER

The local Technical Support Officer for this project is Raymond Richards. The TSO reports to the Government’s Project Manager and serves as the local, on-site Government representative. The TSO is limited to providing on-site answers to questions which are program specific for this contract. The TSO does not have the authority to take any action, either directly or indirectly, that would change the pricing, quality, place-of-performance, delivery schedule, or any other terms and conditions of this contract or to direct work that goes beyond the scope of this contract’s PWS. If the contractor perceives that the TSO or any other Government personnel is requesting an effort outside the existing scope of this contract, the contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the contractor under such direction until the Contracting Officer has issued a contractual change or otherwise resolved the issue.