Att - 1 PWS.pdf

PERFORMANCE WORK STATEMENT

TITLE: PMRF Integrated Data Transport Infrastructure Replacement (PIDTIR) Engineering Support PMRF, Kauai

1.0 SCOPE

This is an acquisition for consulting services to provide Multi-Protocol Label Switching (MPLS) Support services efficiency supported by Space and Naval Warfare Systems Center Pacific (SSC Pacific) Code H4HB for the PIDTIR project at Pacific Missile Range Facility (PMRF), Kauai.

The contractor will deliver consulting services to SPAWAR and US Navy PMRF for Phase 3 of their MPLS Implementation and Edge L2/3 Switch upgrade. The work consists of High Level/Low Level Design development, execution of Design Validation Testing and provision of an Onsite Resident Engineer Twelve (12) months from award of

CTO.

The contractor. will support the next steps of that implementation, known as Phase 3, which consists of the following:

• Execution of an extended Design Validation Testing Phase.

• Development of a Network Implementation and Migration Plan (NIMP)

• Preparation and Support during execution of the Network and Migration Implementation Plan.

• Update Low Level Design with As-Built Data

• Knowledge Transfer

• Provision of on-call Professional Services consulting hours for remote post implementation support.

• Continuation of the on-site Resident Engineer from twelve (12) months from award of CTO.

1.1 PLACES OF PERFORMANCE

1.1.1 SSC PAC Pacific C4ISR Department, Building 992, Pearl City, Hawaii

1.1.2 Pacific Missile Range Facilities, Kekaha, Kauai

2.0 APPLICABLE DOCUMENTS

2.1 Juniper Phase I & II High Level Designs (HLD) and Low Level Designs (LLD)

2.2 PMRF PIDTIR Project Schedule

2.3 PMRF ATM Topology and Accreditation Boundary

2.4 Recommended Juniper Training Course List

2.5 Juniper Hardware List

2.6 PMRF Configuration Management Process

2.7 OPNAVINST F3300.53C (Series), Navy Antiterrorism Program

2.8 DOD 5220.22-M (Series), National Industrial Security Program Operating Manual (NISPOM)

2.9 National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298

2.10 DOD 5205.02E (Series), DOD Operations Security (OPSEC) Program

2.11 OPNAVINST 3432.1A (Series), DON Operations Security

2.12 SPAWARINST 3432.1 (Series), Operations Security Policy

2.13 COMSPAWAR M-4720.1 (Version 4.0) Shore Installation Process Handbook (SIPH)

2.14 Attachment 1 – Quality Assurance Surveillance Plan

3.0 PERFORMANCE REQUIREMENTS

3.1 Extended Design Validation Testing (DVT) (CLIN 0001)

Based on the Design Validation Test Plan created during Phase 2, the contractor will conduct up to two (2) weeks of final testing and documentation on the Black and Red networks.

3.1.1 Design Validation Testing Preparation

Provision of up to two (2) weeks of consulting support to prepare for the extended Design Validation Testing of the Black and Red side networks. The Professional Services consultant will provide configuration and connectivity set-up support, as needed, to the Resident Engineer, Manu Kai, SPAWAR and US Navy PMRF Teams to ensure the environment set-up is ready for the Validation Testing to be executed based on a mutually agreed upon schedule.

3.1.2 Extended Design Validation Testing

Provision of up to two (2) consecutive weeks on site to execute the Red and Black Network Design Validation Test cases. At the conclusion, the contractor will produce a final Design Validation Test Plan which incorporates the results captured during the testing process.

3.1.3 Design Validation Testing Results Review

Submit a draft copy of the Design Validation Test results to the government for review. The government will review the draft and to provide feedback to the contractor of any desired changes to the document. If required, the contractor will arrange a meeting to review the DVT Results.

3.2 Network Implementation and Migration Plan (NIMP) (CLIN 0002) Based on the Low Level Design (LLD) of the Project, the contractor will create a Network Implementation Migration Plan document. The NIMP document will provide a recommended approach for implementation of the Project.

3.2.1 White Boarding

At the conclusion of Design Validation Testing (Phase 2), the consultant will facilitate up to a two (2) day white boarding session with SPAWAR, US Navy PMRF and Manu Kai representatives to establish a high level approach for deploying the approved Low Level Design into the US Navy PMRF production environment.

3.2.2 Document Development

The contractor will produce an NIMP document describing:

3.2.2.1 An implementation prerequisite checklist comprising:

3.2.2.1.1 Site readiness

3.2.2.1.2 Device Physical Rack and Stack

3.2.2.1.3 Module placement and wiring

3.2.2.1.4 Configuration procedure(s) for:

3.2.2.1.4.1 Device initial power up

3.2.2.1.4.2 Minimal configuration to access the device

3.2.2.1.4.3 Device upgrade

3.2.2.1.5 An implementation plan (a sequence of procedures) to be followed by the PIDTIR implementation team.

The NIMP will not include actual configuration files for each device; instead it will refer to the configuration templates provided in the LLD.

3.2.2.1.6 Service Network Implementation Templates.

3.2.2.1.7 A migration plan to move from the legacy environment to the Products on the Target Network including related services. The plan will highlight any disruptive activities or activities that require planned maintenance windows; the plan will also highlight (1) Government resource requirements for the migration and (2) requirements for 3rd Party support during migrations plans; and Rollback procedures for migration.

3.2.3 NIMP Review

3.2.3.1 The contractor will submit a draft copy of the NIMP to the government for review. The government will review the draft and to provide feedback of any desired changes to the document. If required, the contractor will arrange a meeting to review the NIMP

3.2.3.2 Professional services engineer will provide NIMP overview presentation

3.3 Network Implementation and Migration Plan Execution (NIMP-E) (CLIN 0003)

3.3.1.1 NIMP Execution will comprise of the following:

3.3.1.1.1 Execution of the steps documented in the NIMP

3.3.1.1.2 Provision of monitoring checks post implementation for (3) three days.

3.3.1.2 If any task does not generate the expected results documented in the NIMP then the contractor will determine the root cause of the problem:

3.3.1.3 Professional services engineer will provide NIMP-E overview presentation

3.4 Low Level Design As Builts (CLIN 0004)

The contractor will update the High Level and Low Level Design documentation, as needed, to match the design as built in the production network.

3.4.1.1 Creation of as Built Documentation

3.4.1.1.1 The contractor will update the Low Level Design configuration and diagram (Visio) detail to match what is deployed into production.

3.4.1.2 Low Level Design/As Built Review

3.4.1.2.1 The contractor will submit a draft copy of the As-built documentation to the government for review. The government will review the draft and to provide feedback to the contractor of any desired changes to the document. If required, the contractor will arrange a meeting to review the As-Built documentation.

3.5 Knowledge Transfer Workshop (KTW) (CLIN 0005)

The contractor will run a “consulting style” Knowledge Transfer Workshop (“KTW”) onsite at government or End-User premises for a maximum of up to five (5) days.

3.5.1.1 KTW Preparation

The contractor will prepare and run a Workshop covering the following topics:

3.5.1.1.1 Network Design Review (i.e. review all layers of the network and interdependencies)

3.5.1.1.2 QoS/CoS concepts and implementation best practices

3.5.1.1.3 System maintenance and troubleshooting overview and best practices

3.5.1.1.4 Troubleshooting Border Gateway Protocol (BGP), Multiprotocol Label Switching (MPLS), QoS/CoS, incident response

3.5.1.1.5 Daily monitoring procedures (i.e. reports, statistics)

3.5.1.2 KTW Delivery

The contractor will deliver the Workshop based on the topics prepared

3.5.1.2.1 KTW Delivery task will be performed on site limited to a single trip to the Services Delivery Location.

3.5.1.2.2 Professional services engineer will perform KTW workshop.

3.6 On-Call Professional Services Support (CLIN 0006)

The Architect will be available in an on-call capacity to answer questions, provide design guidance, and troubleshooting support on the MPLS network for a period of ninety (90) days after implementation of the Juniper MPLS Network.

3.6.1.1 Remote Support

3.6.1.1.1 For a period of up to ninety (90) calendar days subsequent to the Knowledge Transfer session described in section 3.4, will use commercially reasonable efforts to assist with remote telephone, email, and if necessary, through remote screen sharing application or VPN access to facilitate the dialogue. If required the Professional Services resource will interact with Juniper Technical Assistance Center (JTAC) on the delivered implementation in regards to the support case for the environment described in the Project.

3.6.1.1.2 This will help resolve any minor configuration issues, provide assistance in tasks previously described and if necessary provide support with a working knowledge of the customer implementation, and guide the Customer through any real issues raised through the JTAC Case management process.. In all cases the Customer will remain the owner and primary contact for any support issues.

3.6.1.1.3 Consultant will be available up to eight (8) hours per week for a period of ninety (90) calendar days.

3.6.1.1.4 All support provided remotely.

3.7 Resident Engineer (CLIN 0007)

On-site Resident Engineer (RE) providing operational support for a period of (1) year. The contractor will provide a RE with skills and capabilities to provide service as outlined in the skills and capabilities provided below. Specifically, the RE will have knowledge and understanding of the Juniper Networks product family or technology being installed.

3.7.1.1 All support provided onsite.

3.7.1.2 The contractor shall provide engineering and Configuration Management (CM) support In Accordance With (IAW) Enclosure 2.6 for the ATM replacement, iNet, RDN and Tactical SIPRNET portion of the PIDTIR project.

3.7.1.3 The contractorwill provide a RE with the skills and capabilities to provide Services as outlined in this PWS.

Specifically, the RE will have knowledge and understanding of the Juniper product family or technology as described.

3.7.1.4 Experience and expertise in providing or assisting with the following:

3.7.1.4.1 The preparation of Juniper equipment configurations and validation of configurations for new installations, changes within the network, software upgrades etc.

3.7.1.4.2 Development and maintenance of fault diagnosis procedures to support effective fault resolution Development and maintenance of network operational support procedures related to the Juniper products

3.7.1.4.3 Assessing the health of a network based on Juniper products

3.7.1.4.4 Network related testing to ensure that the Juniper products operate correctly

3.7.1.4.5 Implementation, integration & migration planning

3.7.1.4.6 Validation testing of the Juniper products

3.7.1.4.7 Troubleshooting of network issues

3.7.1.4.8 Ongoing, informal, knowledge transfer related to Juniper products

3.7.1.4.9 Acting as a technical liaison with Juniper Customer Service and Engineering groups:

3.7.1.4.9.1 Assisting JTAC with open JTAC cases

3.7.1.4.9.2 Submission of problem reports

3.7.1.4.10 Advice, and demonstration if necessary, of new software updates and hardware features

3.7.1.5 Experience and expertise in producing the following:

3.7.1.5.1 Ad-hoc (as requested) written summary reports on equipment and network problems

3.7.1.5.2 Equipment test plans and results

3.7.1.5.3 Feature and functionality test plans

3.7.1.5.4 Network diagrams

3.7.1.5.5 Operations and support procedures

3.7.1.5.6 Technical input to major

3.7.1.6 On Call

3.7.2 CTP Support

3.7.2.1 The contractor shall provide four (4) weeks of CTP support to complete the PIDTIR implementation:

3.7.2.1.1 Two (2) weeks of preparation time to complete the build-out of the red side infrastructure

3.7.2.1.2 Two (2) weeks of testing and documentation of the rerun of the black side testing and the full red side.

3.8 OTHER REQUIREMENTS

3.8.1 The contractor shall complete a Contractor’s Progress, Status, and Management Report monthly (CDRL

A001)

3.8.2 The contractor shall provide an Integrated Master Schedule fifteen (15) days after the start of the contract

(CDRL A002)

3.8.3 The contractor shall complete a Contractor Roster Report monthly. The report shall list all contractor personnel assigned to execute tasking. (CDRL A003)

3.8.4 The contractor shall provide a Funds and Man-Hours Expenditure Report monthly. This report provides government visibility into contractor expenditures for labor, materials, travel, and other contract charges.

(CDRL A004)

3.8.5 The contractor shall not disclose any information or generated data under this contract to the news media or general public without the consent of the Contracting Officer.

3.8.6 The contractor shall not enter into any negotiation or commitment with the program office and supporting contractor and construction contractor. All support IAW this PWS will be coordinated with this PWS designated Technical POC’s below.

3.8.7 The contractor shall be responsible for obtaining the appropriate and relevant security clearances for all personnel.

4.0 INFORMATION ASSURANCE (IA)

4.1 The Contractor shall ensure that personnel accessing information systems have the proper and current IA certification to perform IA functions in accordance with DoD 8570.01‐M, Information Assurance Workforce Improvement Program, Ref 2.1.5. The Contractor shall meet applicable information assurance certification requirements, including (a) DoD‐approved IA workforce certifications appropriate for each specified category and level and (b) appropriate operating system certification for information assurance technical positions as required by DoD 8570.01‐M. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions. The contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions, reporting current IA certification status and compliance using CDRL Contractor Roster, DI‐MGMT‐81596 in the format prescribed by the COR."

4.2 The work to be performed under this task shall be at the Secret level. The work performed by the contractor will include access to unclassified and up to Secret data, information, meetings, and spaces. The contractor will require access to Communications Security (COMSEC) and Secure Internet Protocol Router Network (SIPRNet). The contractor shall receive the North Atlantic Treaty Organization (NATO) awareness brief and complete the derivative classification training prior to being granted access to SIPRnet; training is provided by the facility security officer. Contractor shall follow security requirements noted in the DD254.

4.3 Anti-Terrorism/Force Protection (AT/FP) Anti-Terrorism/force Protection (AT/FP) briefings are required for all personnel (military, DOD civilian, and contractor) prior to commencement of foreign travel. Contractor employees must receive the AT/FP briefing annually. The briefing is available at Joint Knowledge Online (JKO): https://jkodirect.jten.mil (prefix): JS; course number: US007; title: Level 1 Anti-terrorism awareness training, if experiencing problems accessing this website contact ssc_fortrav@navy.mil. note: per OPNAVINST F3300.53C contractor employees must receive the AT/FP briefing annually.

4.4 As required by National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3, contractors are required to report certain events that have an impact on: 1) the status of the facility clearance (FCL); 2) the status of an employee's personnel clearance (PCL); 3) the proper safeguarding of classified information; 4) or an indication that classified information has been lost or compromised. Contractors working under SSC Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer Representative (COR)/Technical Point of Contact (TPOC), the Contracting Specialist, and the Security's COR in addition to notifying appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office (CSO), or Department Of Defense Central Adjudication Facility (DODCAF) when that information relates to the denial, suspension, or revocation of a security clearance of any assigned personnel; any adverse information on an assigned employee's continued suitability for continued access to classified access; any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information; or any other circumstances of a security nature that would affect the contractor's operation while working under SSC Pacific contracts.

4.5 Operations Security: OPSEC is a five (5) step analytical process (identify critical information; analyze the threat; analyze vulnerabilities; assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical Information or Critical Program Information, and therefore all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the DD254.

5.0 GOVERNMENT FURNISHED INFORMATION/MATERIAL/PROPERTY

5.1 The Government will be responsible for providing the RE (without charge) unrestricted external access to PMRF’s facilities, equipment, resources, and the Internet, internal access to its Intranet, access to the network equipment that the RE will support, and access to any applications and databases that are essential for the RE to perform all duties successfully.

5.2 Place of Performance

5.2.1 Period of Performance for this performance work statement work statement shall be twelve (12) months from award of CTO.

6.0 PERFORMANCE BASED CRITERIA

6.1 The contractor shall provide services and deliverables in accordance with this Performance Work Statement (PWS) and in accordance with the attached task order Contract Data Requirements List (CDRL) DD Form 1423-1.

6.2 Performance Standard

The contractor's performance shall meet all of the requirements of this PWS and comply with all applicable guidance, directives, and standards. The contractor shall deliver all task order data items in accordance with the authorities, content, format, media, marking, applications, quantities, frequency and submission date, delivery method, addressee, and DD250 requirements specified in the CDRL for each data item.

6.3 Acceptable Quality Level

The effectiveness of the contractor's services and/or deliverables will be measured for 100% compliance with the PWS and CDRL requirements.

6.4 Method of Surveillance

The Government will monitor and assess the contractor's performance against the Acceptable Quality Level in accordance with this task order's Quality Assurance Surveillance Plan (QASP).

6.5 Incentive

Failure to meet acceptable quality levels may result in an unsatisfactory past performance report by the Government.

6.6 Inspection/QASP

6.6.1 Inspection of the work shall be accomplished as identified by the Quality Assurance Surveillance Plan (QASP), Attachment (1).

6.6.2 The performance of the contractor and the quality of the work delivered, including any documentary material written or compiled, shall be subject to in-process review and inspection.

6.6.3 Inspections may be accomplished at any work location by any authorized government personnel who shall be permitted to inspect work at all reasonable hours.

6.7 Acceptance

6.7.1 The SSC Pacific Contracting Officer Representative (COR) is responsible for the acceptance of the final deliverable products.

6.7.2 The COR’s final acceptance shall be based upon the AIT Manager’s or designated alternates recommendation, ensuring the delivery order has been satisfactorily completed, all deliverable products have been received and Government Provided Property and all residual materials, (notes, tech manuals, brochures, research material and remaining supplies), have been received.

7.0 DATA DELIVERABLES

7.1 Required CDRL items are listed in section 3.0.

8.0 POC DESIGNATIONS

8.1 Technical Point of Contacts

8.1.1 Jack Munechika (808)471-1976 Email: jack.munechika@navy.mil

8.1.2 Randy Yamada (808)474-6061 Email: randy.yamada@navy.mil

8.2 Contracting Officer’s Representative (COR):

8.2.1 Adel Young (808)474-6062 Email: adel.young@navy.mil

8.2.2 Kevin Chiogioji (808)471-4042 Email: kevin.chiogioji@navy.mil mailto:jack.munechika@navy.mil mailto:randy.yamada@navy.mil mailto:adel.young@navy.mil mailto:kevin.chiogioji@navy.mil