3 PWS 1300796882_CRTrev2.docx

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based contract will be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein will be referred to as Performance Work Statement (PWS):

SHORT TITLE: NCTS Yokosuka, Japan RTMS Engineering Integration Support

1.0 PURPOSE

1.1 SCOPE

This PWS covers Regional Telephony Management System (RTMS) subject matter expert (SME) support services required by Navy Information Warfare Center Atlantic (NIWC Atlantic), Unified Capabilities Voice Solutions (UCVS) Integrated Product Team (IPT). This support encompasses SME services for Unique Communications’ CAIRS.NET system (which PMW 790 identifies as RTMS and the remainder of this PWS will refer to the CAIRS.NET system as RTMS) configuration, integration, data migration and System Operational Verification Test (SOVT) support for Navy Computer and Telecommunication Station (NCTS) Yokosuka, Japan telephony system.

NOTE: Website and e-mail addresses referenced within the PWS and CDRL forms are subject to change. For any website and e-mail address not working during time of performance, the contractor shall contact the Contracting Officer’s Representative (COR) or Contracting Officer for latest website and e-mail address. An incorrect website or e-mail address does not alleviate a contractor from required reporting or access requirements.

1.2 BACKGROUND

NIWC Atlantic UCVS IPT has been tasked by Shore and Expeditionary Integration Program Office (PMW 790) to deploy the RTMS system at NCTS Yokosuka, Japan.

2.0 PLACE(S) OF PERFORMANCE

The contractor shall provide support from the following location which does not including any travel identified in Para 11.0:

a. Contractor’s Facility

2.1 GOVERNMENT FACILITIES

No Government facilities (i.e., office space or lab space) are assigned and provided on this contract.

2.1.1 Access to Government facilities

NIWC Atlantic and other Government installations have restricted access. Contractors are limited to access during certain days and times as specified in the Work Schedule requirements of this contract. If access to the assigned Government facility is restricted due to safety/security exercise, an Executive Order, or an administrative leave determination applying to the local activity (e.g., inclement weather), the contractor, in agreement with the COR, shall make alternative work arrangements. The contractor shall adjust work schedule or work at an alternate location. If alternate work arrangements cannot be accommodated, the contractor shall notify the COR of the inability to access the assigned facility prior to charging their time to the contract as direct cost provided such charges are consistent with the contractor’s accounting practices. The ability to work at an alternate location that is not a Government or contractor facility site is dependent on the contractor having an alternative work site agreement with the employee. The ability to work at an alternate location may not be an option for certain support services.

2.1.2 Training Requirements and Exercise Support

Contractor personnel working full-time or partially at a Government facility shall complete all applicable training requirements as specified under Mandatory Training, PWS Para 8.0. Contractor personnel may also be required to participate in safety, security (e.g., Anti-Terrorism Force Protection (AT/FP)), and operational training exercises (possibly two per year). Applicable contractor personnel shall support and participate in the training exercise which may include role-playing and reacting to exercise injects based on the situation or exercise objectives.

2.1.3 Alternate work locations from Government facilities

Due to the type tasking, support from an alternative worksite is not allowed by contractor personnel working onsite at NCTS Yokosuka, Japan.

2.2 CONTRACTOR FACILITIES

The contractor can have its facility location anywhere as long as the location does not present a hardship to complete work required on task. The contractor shall have real-time communication between the contractor personnel supporting the efforts and government personnel available at time of award.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all non-personal services tasks that will be required throughout the contract. The contractor shall provide necessary resources with knowledge and experience as cited in the personal qualification requirement to support the listed tasks. The contractor shall perform requirements in accordance with Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS) that do not include performance of inherently Government functions. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

3.1 RELEVANT EXPERIENCE

The contractor shall have relevant experience with engineering and subject matter expertise (SME) in the areas of Naval Enterprise Voice and Unified Capabilities, specifically with the Telephony RTMS system deployed by PMW 790 and UCVS IPT across Navy Marine Corp Intranet (NMCI) networks and ashore telephony sites.

The contractor shall provide management support for this task by attending all RTMS NCTS Yokosuka planning meetings, answering any RTMS data calls and coordinating all onsite support prior to traveling to NCTS Yokosuka.

The contractor shall provide RTMS installation support while onsite at NCTS Yokosuka and shall configure the RTMS system and integrate the RTMS system with the Avaya Communication Manager 7 (CM 7) at NCTS Yokosuka. The contractor shall test the RTMS configuration and CM 7 integration to ensure successful operational capability.

3.3.2 RTMS Migration

The contractor shall convert and migrate the telephony user database into the RTMS system so the RTMS system can provide operational telephony management at NCTS Yokosuka.

3.3.3 RTMS Testing and SOVT

The contractor shall test all operational functionality for the NCTS Yokosuka RTMS system to ensure operational performance, and the contractor shall troubleshoot, mitigate, and resolve any issues found during the RTMS testing to ensure RTMS is properly working before contractor departure. The contractor shall assist the government’s execution of the System Operational Verification Test (SOVT) and resolve any RTMS issues that may be found during the SOVT.

3.3.4 Training

The contractor shall ensure that the warfighter and technical support community are provided with adequate instructions resulting in the attainment and retention of knowledge, skills, and attitudes regarding the RTMS system.

4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

4.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

The contractor shall adhere to the following requirements when the IT support services and/or supplies are applicable to the requirement:

4.1.1 Ensure that no production systems are operational on any research, development, test and evaluation (RDT&E) network.

4.1.2 Follow DoDI 8510.01 when deploying, integrating, and implementing IT capabilities.

4.1.3 Migrate all Navy Ashore production systems to the Navy, Marine Corps Intranet (NMCI) environment where available.

4.1.4 Work with Government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).

4.1.5 Follow SECNAVINST 5239.3C & DoDI 8510.01 prior to integration and implementation of IT solutions or systems.

4.1.6 Register any contractor-owned or contractor-maintained IT systems utilized on contract in the Department of Defense IT Portfolio Registry (DITPR)-DON.

4.1.7 Ensure all IT products and services recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, Title 36 Code of Federal Regulations Part 1194 – Electronic and Information Technology Accessibility Standards unless otherwise exempt in accordance with the latest regulation.

4.1.8 Only perform IT work specified within the limitations of the contract.

5.0 CONTRACT ADMINISTRATION

Administration of the work being performed is required; it provides the Government a means for contract management and monitoring. Regardless of the level of support, the ultimate objective of the contractor is ensuring the Government’s requirements are met, delivered on schedule, and performed within budget.

5.1 CONTRACTING OFFICER’S REPRESENTATIVE (COR) DESIGNATION

A COR will be is utilized on this contract and identified in Section C.

5.2 CONTRACT MONITORING AND MAINTENANCE

The contractor shall have processes established in order to provide all necessary resources and documentation during various times throughout the day including business and non-business hours in order to facilitate a timely contract response or modification in particular during urgent requirements.

5.2.1 Contract Administration & Documentation

Various types of administration documents are required throughout the life of the contract. At a minimum, the contractor shall provide the following documentation:

5.2.1.1 Contract Status Report (CSR)

The contractor shall develop a Contract Status Report (CSR) (CDRL A001) and submit it bi-annual on the 10th day of the 6th and 12th month after award. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports as applicable. The contractor shall report on various contract functions: performance, schedule, financial, business relations, and staffing plan/key personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. This CDRL includes a Staffing Plan (CDRL A001 Attachment 1 of Exhibit A) and Government-furnished property (GFP) Template (CDRL A001 Attachment 3 of Exhibit A).

5.2.1.2 Enterprise-wide Contractor Manpower Reporting Application Pursuant to NMCARS 5237.102-90, the contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the DoD via a secure data collection website – Enterprise-wide Contractor Manpower Reporting Application (eCMRA). Contracted services under the following Product/Service Codes (PSC) are excluded from reporting:

The contractor shall completely fill-in all required data fields using the following web address: https://www.ecmra.mil/. Reporting inputs consists of labor hours executed during the contract period of performance within each Government fiscal year (FY) which runs from October 1 through September 30. While inputs may be reported any time during the FY, the contractor shall report all data in the applicable FY no later than October 31 of each calendar year. The contractor shall send notice to the COR and Contracting Officer after the applicable eCMRA data has been successfully entered. For reporting questions, contractors may contact the help desk email accessible through the eCMRA login webpage.

5.2.1.3 WAWF/PIEE Invoicing Notification and Support Documentation Pursuant to DFARS 252.232-7003 and 252.232-7006, the contractor shall submit payment requests and receiving reports using DoD Wide Area Work Flow (WAWF) application (part of the Procurement Integrated Enterprise Environment (PIEE) e-Business Suite) which is a secure Government web-based system for electronic invoicing, receipt, and acceptance. The contractor shall provide e-mail notification to the COR when payment requests are submitted to the WAWF/PIEE and if requested, the contractor shall include cost back–up documentation (e.g., delivery receipts, time sheets, & material/travel costs, etc.) to the invoice in WAWF/PIEE. When requested by theCOR, the contractor shall directly provide a soft copy of the invoice and any invoice supporting documentation (CDRL A002) directly to the COR within 24 hours of request to assist in validating the invoiced amount against the products/services provided during the billing cycle.

5.3 CONTRACT PERFORMANCE MANAGEMENT

Contractor performance standards and requirements are outlined in the contract QASP. The ability of a contractor to perform to the outlined standards and requirement will be captured in the Contractor Performance Assessment Reporting System (CPARS). In support of tracking contractor performance, the contractor shall provide the following documents: Cost and Schedule Milestone Plan (CDRL A003) submitted 10 days after contract award and CPARS Draft Approval Document (CDAD) Report (CDRL A004) submitted NLT 10 days at the conclusion of the contract.

6.0 DOCUMENTATION AND DELIVERABLES

The contractor shall screen all electronic deliverables or electronically provided information for malicious code using DoD approved anti-virus software prior to delivery to the Government.

6.1 CONTRACT DATA REQUIREMENTS LIST (CDRL)

The following listing identifies the data item deliverables required under this contract and the applicable paragraph of the PWS for which they are required. Section J includes the DD Form 1423s that itemize each Contract Data Requirements List (CDRL) required under the contract. The contractor shall establish a practical and cost-effective system for developing and tracking the required CDRLs generated under each task. The contractor shall not develop any CDRL classified TOP SECRET with SCI.

6.2 ELECTRONIC FORMAT

At a minimum, the contractor shall provide deliverables electronically by e-mail; hard copies are only required if requested by the Government. To ensure information compatibility, the contractor shall guarantee all deliverables (i.e., CDRLs), data, correspondence, and etc., are provided in a format approved by the receiving COR. The contractor shall provide all data in an editable format compatible with NIWC Atlantic corporate standard software configuration as specified below. Contractor shall conform to NIWC Atlantic corporate standards within 30 days of contract award. The initial or future upgrades costs of the listed computer programs are not chargeable as a direct cost to the Government.

6.4 INFORMATION SYSTEM COMMUNICATION

The contractor shall have broadband Internet connectivity and an industry standard email system for communication with the Government. The contractor shall be capable of Public Key Infrastructure (PKI) client side authentication to DOD private web servers. Unless otherwise specified, all key personnel on task shall be accessible by e-mail through individual accounts during all hours. The contractor shall have an information system capable of meeting all security requirements identified under Para 8.4.

7.0 QUALITY

7.1 QUALITY SYSTEM

Upon contract award, the prime contractor shall have and maintain a quality system that meets contract requirements and program objectives while ensuring customer satisfaction and defect-free products/process. The contractor shall have an adequately documented quality system which contains processes, procedures, planning, and all other documentation and data necessary to provide an efficient and effective quality system, which includes an internal auditing system.

8.0 SECURITY

8.1 ORGANIZATION

8.1.1 Security Classification

All work performed under this contract is “unclassified.” A facility security clearance (FCL) is not required; therefore, DoD Contract Security Classification Specification, DD Form 254, does not exist. Pursuant to DoDM 5200.01 – Volume 4, Controlled Unclassified Information (CUI), the contractor shall safeguard any sensitive Government information.

8.2 PERSONNEL

Personnel investigations are not required since contractor personnel are performing unclassified work and do not require access to Government installations/facilities, Government IT systems and IT resources, or NIWC Atlantic information.

8.2.1 Access Control of Contractor Personnel

8.2.1.1 Physical Access to Government Facilities and Installations Contractor personnel shall physically access Government facilities and installations for purposes of site visitation, supervisory and quality evaluation, work performed within Government spaces (either temporary or permanent), or meeting attendance. Individuals supporting these efforts shall comply with the latest security regulations applicable to the Government facility/installation.

(a) The majority of Government facilities/installations require a CAC for access. Contractor personnel shall carry proper form of identification(s) and vehicle proof of insurance or vehicle rental agreement for any liability issues. For admission to NIWC Atlantic facilities/installations, all contractor personnel must have the COR or sponsor initiate access. For contractor personnel requiring a Confidential, Secret, or TS security clearance, a visitor authorization request (VAR) must be submitted via Joint Personnel Adjudication System (JPAS) to the applicable Security Management Office (SMO). For Charleston and other remote locations excluding Tidewater, the contractor shall send VAR to SMO 652366 and for Tidewater locations send VAR to SMO N65580. If faxing a VAR versus using JPAS, the contractor shall submit their request on company or agency letterhead to (843)218-4045 for SMO 652366 or (757)541-5860 for SMO N65580. For visitation to all other Government locations, the contractor shall forward visit request documentation directly to the on-site facility/installation security office.

(b) Contractor employees who make repeated deliveries to JB Charleston military installations and do not require access into NIWC Atlantic facilities or access to IS shall obtain a base access card. Only contractor employees that are able to obtain a card will be eligible for entrance on base. At Joint Base (JB) Charleston, the contractor shall obtain the required access card via the Defense Biometric Identification System (DBIDS) from the JB Charleston Badge and Pass Office. Contractors with employees that that are no longer employed shall return the employee’s access card directly to the COR or to the local NIWC Atlantic Security Office with COR notification within five (5) days from the last day of employment. Contractors who do not have a DBIDS card or CAC will receive a one-day pass for each day access is required. Information about DBIDS is found at https://dbids-global.dmdc.mil/enroll#!/.

(c) All contractor persons engaged in work while at Government facility/installation shall be subject to inspection of their vehicles at any time by the Government, and shall report any known or suspected security violations to the Security Department at that location.

(d) The contractor shall notify the COR and appropriate NIWC security personnel within 24 hours from the time contractor employee gives notice of departure or are removed unexpectedly from contract support. For contractors in direct support of NIWC Atlantic, see the Contractor Check-in and Check-out (CICO) Procedures requirements listed in Para 8.2.2.5.

8.2.1.2 Identification and Disclosure Requirements

All contractor and subcontractor employees located on and off Government installations shall take all means necessary to not represent themselves as Government employees. All contractor personnel shall follow the identification and Government facility disclosure requirement:

(a) Contractor employees shall be clearly identifiable as a contractor while on Government property by wearing appropriate badges.

(b) Contractor personnel and their subcontractors shall identify themselves as contractors or subcontractors during meetings, on attendance meeting list/minutes, at the beginning of telephone conversations, in electronic messages including their electronic digital signature, and all correspondence related to this contract.

(c) Contractors occupying facilities within Department of the Navy or other Government installations (such as offices, separate rooms, or cubicles) shall clearly display and identify their space with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

8.2.2.3 Government Badge Requirements

While on Government installations/facilities, contractors shall abide by each site’s latest security badge requirements and if a Government-issued picture badge is issued, the contractor shall prominently display it (above the waist or in accordance with on-site instructions).

(a) The contractor shall submit valid paper work (e.g., site visit request, request for picture badge, and/or SF-86) to the applicable Government security office via the COR who will validate the need authorizing contractor performance within the applicable Government installation/facility.

(b) The contractor shall assume full responsibility for the proper use and security of the identification badge and is responsible for the return of the badge upon termination of personnel or expiration or completion of the contract.

8.2.2 Mandatory Training

In addition to training requirements and certifications required specific to a labor category, certain contractor personnel (including subcontractors) regardless of security classification shall complete required mandatory training in accordance with NAVWARSYSCOM Code 80330 mandatory training webpage: https://wiki.spawar.navy.mil/confluence/x/jwDsAQ. Contractors without access to the training webpage shall coordinate with the COR concerning the latest mandatory training as specified on the training webpage. The following table is a sample of contractor mandatory training that is subject to change in accordance with the NAVWARSYSCOM website:

8.2.3.1 The contractor shall be responsible for verifying applicable personnel receive all required training within the specified due dates. The contractor shall track and annotate all mandatory training required and completed for each employee in the Staffing Plan which is part of the CSR CDRL.

8.2.3.2 The contractor shall complete mandatory training annually between 1 October and 30 September utilizing the Total Workforce Management System (TWMS). For some personnel, attendance of Government face-to-face training is allowed if COR concurs with training schedule. For training taken via Defense Information Systems Agency / Navy Knowledge Online (DISA/NKO), the contractor shall forward a copy of the certificate to ssclant_mandatory_tr.fcm@navy.mil who will upload or ensure each completed training is recorded in TWMS.

8.2.3.3 The contractor shall educate employees on the procedures for the handling and production of classified material and documents, and other security measures as described in the PWS in accordance with DoD 5220.22-M.

8.3 OPERATIONS SECURITY (OPSEC) REQUIREMENTS

Security programs are oriented towards protection of classified information and material. Operations Security (OPSEC) is an operations function which involves the protection of any critical information – focusing on unclassified information that may be susceptible to adversary exploitation. OPSEC requirements are applicable when contract personnel have access to classified information or unclassified Critical Program Information (CPI)/sensitive information. Pursuant to DoDD 5205.02E and SPAWARINST 3432.1, NIWC Atlantic’s OPSEC program implements requirements in DoD 5205.02-M – OPSEC Program Manual and SPAWARSYSCENLANTINST 3070.1B.

8.3.1 Local and Internal OPSEC Requirement

Contractor personnel, including subcontractors if applicable, shall adhere to the OPSEC program policies and practices as cited in the SPAWARINST 3432.1 and existing local site OPSEC procedures. The contractor shall develop their own internal OPSEC program specific to the contract and based on SPAWARSYSCEN Atlantic OPSEC requirements. At a minimum, the contractor’s program shall identify the current SPAWARSYSCEN Atlantic site OPSEC Officer/Coordinator.

8.3.2 OPSEC Training

Contractor shall track and ensure applicable personnel receive initial OPSEC training within 30 days of contract award and annual OPSEC awareness training in accordance with requirements outline in the Security Training, Para 8.2.3. OPSEC training requirements are applicable for personnel during their entire term supporting this NIWC Atlantic contract.

8.3.3 NIWC Atlantic OPSEC Program

Contractor shall participate in NIWC Atlantic OPSEC program briefings and working meetings, and the contractor shall complete any required OPSEC survey or data call within the timeframe specified.

8.4 INFORMATION SYSTEM SECURITY

8.4.1 Electronic Communication

The contractor shall have broadband Internet connectivity and an industry standard email system for communication with the Government. The contractor shall be capable of Public Key Infrastructure (PKI) client side authentication to DoD private web servers. Unless otherwise specified, all key personnel on task shall be accessible by e-mail through individual accounts during all hours.

8.4.2 Information Security

Pursuant to DoDM 5200.01, the contractor shall provide adequate security for all unclassified DoD information passing through non-DoD information system including all subcontractor information systems utilized on task. The contractor shall disseminate unclassified DoD information within the scope of assigned duties and with a clear expectation that confidentiality is preserved. Examples of such information include the following: non-public information provided to the contractor, information developed during the course of the contract, and privileged contract information (e.g., program schedules and contract-related tracking).

8.4.2.1 Safeguards

The contractor shall protect Government information and shall provide compliance documentation validating they are meeting this requirement in accordance with DFARS clause 252.204-7012. The contractor and all subcontractors shall abide by the following safeguards:

(a) Do not process DoD information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control.

(b) Protect information by at least one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control.

(c) Sanitize media (e.g., overwrite) before external release or disposal.

(d) Encrypt all information that has been identified as controlled unclassified information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as portable hard drives and digital optical disks, using DoD Authorized Data-at-Rest encryption technology. NOTE: Thumb drives are not authorized for DoD work, storage, or transfer. Use GSA Awarded DAR solutions (GSA # 10359) complying with ASD-NII/DOD-CIO Memorandum, “Encryption of Sensitive Unclassified Data-at-Rest on Mobile Computing Devices and Removable Storage.” The contractor shall ensure all solutions meet FIPS 140-2 compliance requirements.

(e) Limit information transfer to subcontractors or teaming partners with a need to know and a commitment to at least the same level of protection.

(f) Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS). Encrypt organizational wireless connections and use encrypted wireless connection where available when traveling. If encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using at least application-provided password protection level encryption.

(g) Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

(h) Do not post DoD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts).

(i) Provide protection against computer network intrusions and data exfiltration, minimally including the following:

1. Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

2. Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services.

3. Prompt application of security-relevant software patches, service packs, and hot fixes.

(j) As applicable, comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, critical program information (CPI), personally identifiable information, export controlled).

(k) Report loss or unauthorized disclosure of information in accordance with contract requirements and mechanisms.

8.4.2.2 Compliance

Pursuant to DoDM 5200.01, the contractor shall include in their quality processes procedures that are compliant with information security requirements.

8.5 ENHANCED SECURITY CONTROLS

The contractor shall not process, store, or transmit Government controlled unclassified information (CUI) on any information system and IT asset that is owned, or operated by or for, the contractor.

9.0 GOVERNMENT FURNISHED INFORMATION (GFI)

For the purposes of this contract, Government Furnished Information (GFI) includes manuals, technical specifications, software, software licenses, maps, building designs, schedules, drawings, test data, etc. provided to contractors for performance on this contract. Depending on information contained in a document, the contractor shall comply with additional controls (e.g., completion of a Non-Disclosure Agreements, etc.) for access and distribution. The Government will mark any CUI which includes unclassified covered defense information and unclassified controlled technical information provided to the contractor. For any missing markings, contractor shall request appropriate marking from the Government.

GFI is not anticipated on this contract.

10.0 GOVERNMENT PROPERTY

As defined in FAR Part 45, Government property is property owned or leased by the Government which includes Government-furnished (GFP) and Contractor-acquired property (CAP); however, CAP is not applicable on fixed-priced contracts. GFP includes material, equipment, special tooling, and special test equipment.

GFP will not be provided on this contract.

11.0 TRAVEL

11.1 LOCATIONS

The contractor shall be prepared to travel to the locations cited in the below table. Prior to any travel performed in support of this contract, the contractor shall obtain COR or Contracting Officer concurrence.

Travel to foreign countries outside of the contiguous United States (OCONUS) is required. Prior to travel, the contractor shall meet all necessary travel requirements for their company and personnel to support work in the noted foreign OCONUS sites.

11.2 OCONUS TRAVEL REQUIREMENTS

Pursuant to SPAWARSYSCENLANTINST 12910.1B, DoDI 3020.41, and the latest DoD Foreign Clearance Guide requirements, the contractor shall travel to OCONUS sites to support deployed forces.

11.2.1 General OCONUS Requirements

The contractor shall ensure compliance with applicable clauses and travel guide requirements prior to traveling to each of the specified travel locations. The contractor shall be responsible for knowing and understanding all travel requirements as identified by the applicable combatant command (CCMD) and country. The contractor shall be responsible for submitting applicable deployment forms and/or OCONUS deployment packages (CDRL A005) to the COR or Contracting Officer and NIWC Atlantic Deployment Manager no later than 30 days prior to travel. For all OCONUS travel, the contractor shall submit an official OCONUS Travel Form (SPAWARSYSCENLANT 12990/12) and shall ensure all OCONUS travel has an approved Aircraft and Personnel Automated Clearance System (APACS) request. The COR or Contracting Officer will provide a blank travel form after contract award.

11.2.2 OCONUS Immunization Requirements

Pursuant to DoDI 6205.4, SPAWARSYSCENLANTINST 12910.1B, and any additional DON specific requirements, contractor employees who deploy to OCONUS locations both shore and afloat shall require up to date immunizations.

11.2.3 OCONUS Training

Contractor personnel (including subcontractors) shall complete Antiterrorism Training as well as any regional specific training in accordance with Official OCONUS Travel webpage: https://wiki.spawar.navy.mil/confluence/x/DIvYAQ. Contractors without access to the SPAWAR webpage shall coordinate with the COR concerning mandatory training as listed on the training webpage.

12.0 SAFETY ISSUES

12.1 OCCUPATIONAL SAFETY AND HEALTH REQUIREMENTS

The contractor shall be responsible for ensuring the safety of all company employees, other working personnel, and Government property. The contractor is solely responsible for compliance with the Occupational Safety and Health Act (OSHA) (Public Law 91-596) and the resulting applicable standards, OSHA Standard 29 CFR 1910 (general), 1915 (shipboard/submarine) and 1926 (shore), and for the protection, safety and health of their employees and any subcontractors assigned to the contracts. Without Government assistance, the contractor shall make certain that all safety requirements are met, safety equipment is provided, and safety procedures are documented as part of their quality management system. If performing within Government facilities, contractor shall immediately report any accidents involving Government or contractor personnel injuries or property/equipment damage to the Contracting Officer and COR. Additionally, the contractor is responsible for securing the scene and impounding evidence/wreckage until released by the Contracting Officer or on-site COR.

13.0 SUBCONTRACTING REQUIREMENTS

If the prime contractor is planning to utilize subcontractor(s) on this contract, the prime contractor shall identify the applicable subcontractor(s) at contract award. Post award subcontractor additions (i.e. subcontractor additions to the contract after issuance of the contract) are governed by FAR 52.244-2 Alt I, which notification and/or consent may be required.

14.0 ACCEPTANCE PLAN

Inspection and acceptance is performed by the COR on all services, data, and non-data deliverables in accordance with the Quality Assurance Surveillance Plan (QASP), Attachment #A.

15.0 OTHER CONDITIONS/REQUIREMENTS

No other conditions or requirements are applicable.

16.0 APPLICABLE DOCUMENTS

The contractor shall ensure all work accomplished utilizes the latest, relevant industry practices and standards when applicable unless otherwise indicated by text. In accordance with Defense Acquisition Policy, maximum utilization of non-Government standards will be made wherever practical.

16.1 REQUIRED DOCUMENTS

The contractor shall utilize the following mandatory documents in support of this contract. The documents referenced in this paragraph list the minimum version dates; however, the contractor shall meet requirements for any referenced document including subsequent updates applicable at time the contract request for proposal is posted.

Change 2

16.2 GUIDANCE DOCUMENTS

The contractor shall have knowledge and utilize the following guidance documents in support of this contract. The documents referenced in this paragraph list the minimum version dates; however, the document’s effective date of issue is the contract’s request for proposal issue date.

16.3 SOURCE OF DOCUMENTS

The contractor shall obtain all applicable documents necessary for performance on this contract. Many documents are available from online sources. Specifications and commercial/industrial documents may be obtained from the following sources:

Copies of Federal Specifications may be obtained from General Services Administration Offices in Washington, DC, Seattle, San Francisco, Denver, Kansas City, MO., Chicago, Atlanta, New York, Boston, Dallas and Los Angeles.

Copies of military specifications may be obtained from the Commanding Officer, Naval Supply Depot, 3801 Tabor Avenue, Philadelphia, PA 19120-5099. Application for copies of other Military Documents should be addressed to Commanding Officer, Naval Publications and Forms Center, 5801 Tabor Ave., Philadelphia, PA 19120-5099.

All other commercial and industrial documents can be obtained through the respective organization’s website.

[END OF PWS]

THE FOLLOWING IS NOT PART OF THE PWS –

USE FOR VALIDATION AND PACKAGE REVIEW ONLY

[To be deleted by Contracting Officer only prior to incorporation in CWS]

LIST OF EXHIBITS & ATTACHMENTS

Exhibit A -- CDRLs - DD FORM 1423 Attachment #A – Quality Assurance Surveillance Plan (QASP)

[Ver dtd 20 Jul 18] 1 of 14