3 PWS REVISED.docx

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based task order 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: SPAWAR MAINTENANCE ENGINEERING SUPPORT CENTER (MESC) PERFORMANCE BASED LOGISTICS – ORGANIC (PBL-O) INTEGRATED LOGISTICS SUPPORT (ILS)

1.0 PURPOSE

Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic)

1.1 SCOPE

The effort provides support for the analysis, reporting, and Course of Action (COA) development for End of Life and Sustainment for Obsolescence Management, Spares management, Demilitarization and Disposal of Legacy Command, Control, Communication, Computers, Information, Surveillance and Reconnaissance (C4ISR) equipment as a result of the Technical Refresh for NAVSUP WSS Performance Based Logistics – Organic (PBL-O) support at the Maintenance Engineering Support Center (MESC) in Norfolk, VA, in order for C4ISR platforms to maintain their warfighter capabilities.

This PWS covers primarily support for Afloat and Ashore Tactical Networks. The support will include at a minimum the following areas: Logistics Engineering, Technical, and ILS. This support is primarily for use by Code 43350 for the C4ISR Family of Systems (FoS).

Note: In accordance with the Fleet Forces Command (FFC) and Naval Sea Systems Command (NAVSEA) Joint Industry-Navy Improvements Initiative (JINII) and in accordance with current SPAWARSYSCEN Atlantic (SSC Atlantic) Installation Management Office (IMO) Policy, the scope of this contract specifically excludes system installation related tasks involving U.S. Navy property (ships, shore stations) and excludes installation related tasks funded with U.S. Navy Funds.

NOTE: Work will not be performed in Afghanistan.

2.0 PLACE(S) OF PERFORMANCE

The site requirements below identify contractor employee office location(s) and the location of Government provided facilities, if applicable. Travel locations (i.e., temporary duty sites) are not specified in this section. If applicable, travel locations are specified under task order PWS Para 11.0.

The contractor shall provide support at the following location:

a.

c.

e.

2.1 GOVERNMENT FACILITIES

Government facilities (i.e., office space or lab space) are provided to those labor categories that would otherwise adversely affect the work performance if they were not available on Government site. Labor categories with supplied Government facilities shall be located at SPAWARSYSCEN Atlantic in Norfolk, VA.

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 Contractor shall be able to apply an ILS approach to the management and technical activities needed to influence operational and materiel requirements and design specifications for logistics support to include all Program Manager Warfare (PMW) -160 and Naval Sea Systems Command (NAVSEA) current and legacy programs – Consolidated Afloat Network Enterprise Services (CANES), Global Command and Control Joint and Maritime GCCSM/J, M, Navy Tacticial Command Supply System NTCSS, SupplyCombined Enterprise Regional Information Exchange System (CENTRIXS), Distributed Common Ground System – Navy (DCGS-N), Expeditionary Fast Transport (EPF) formerly Joint High Speed Vessel (JHSV), Integrated Shipboard Network System (ISNS), Submarine Local Area Network (SUBLAN), and other legacy Information Technology (IT) based systems..

The principal objectives of lifecycle (acquisition) logistics are to ensure that support considerations are an integral part of the system’s design requirements, that the system can be cost effectively supported through it life-cycle, and that the research and development facilities and infrastructure elements necessary to the design, development, initial fielding, and operational support of the system are identified, developed, acquired, and supported.

3.1 INTEGRATED LOGISTICS SUPPORT

The Contractor shall be able to apply an Integrated Logistics Support (ILS) approach to the management and technical activities needed to influence operational and materiel requirements and design specifications for logistics support. The principal objectives of lifecycle (acquisition) logistics are to ensure that support considerations are an integral part of the system’s design requirements, that the system can be cost effectively supported through it life-cycle, and that the research and development facilities and infrastructure elements necessary to the design, development, initial fielding, and operational support of the system are identified, developed, acquired, and supported.

3.1.1 Logistics Engineering Support

3.1.1.1 Mockup Support: The contractor shall develop, document, validate, and maintain system mockups for specific system/equipment in accordance with specific system/equipment specification(s) for testing de-installed assets. (CDRL: A001)

3.1.1.2 Equipment Support: The contractor shall evaluate, recommend, or develop, validate, document and store test stations, test jigs and fixtures, test program sets, Pre-Faulted Modules (PFMs), and Fault Insertion Devices (FIDs). (CDRL: A001)

3.1.1.3 Testing Support: The contractor shall develop test procedures, perform the tests and provide documentation to the government of the results. The test procedures shall describe the proposed tests and inspections in sufficient depth to prove that equipment/system are thoroughly evaluated for conformance to the requirements of equipment/system specification(s). The contractor shall test for: Workmanship; Telecommunications and Electrical Machinery Protected from Emanations Security (TEMPEST); Electromagnetic Interference (EMI) /Electromagnetic Compatibility (EMC); all Environmental Factors; Maintainability; Reliability; Connectivity; Availability; Supportability; and final inspections as defined in system/equipment specifications. The testing shall consider partitioning to enhance fault isolation, initialization of circuitry under test control, module interface for test access and control, circuit controllability and examination, test point placements, and Built in Test (BIT) fault isolation approach. The contractor shall submit the results of all the tests and inspections using the applicable guidelines and reporting procedures. The contractor shall perform the required calibration of any test equipment. (CDRL: A001)

3.1.1.4 Systems Sustainment Support: The contractor shall provide sustainment support in developing, maintaining, documenting, integrating and installing upgrades to shore/afloat systems per program requirements. The contractor shall provide the capability to manage network objects such as host computers, routers, local and wide area networks. (CDRL: A001)

3.1.2 Maintenance Engineering Support

3.1.2.1 Fleet Support Services: The contractor shall provide ad-hoc fleet technical assist support for systems for problems beyond Afloat and Shore personnel capability. The contractor shall use the priorities established by PBL-O Helpdesk. (CDRL: A001)

3.1.2.2 Urgent Fleet Support Services: The contractor shall support emergent fleet needs for Afloat and Ashore Tactical Networks Systems Casualty Reports (CASREP’s) and significant incidents with C4I casualties. The contractor shall provide rapid response in support of CASREPs as required by the Joint Fleet Maintenance Manual (JFMM), Commander United States Fleet Forces Command Instruction (COMUSFLTFORCOMINST) 4790.3 series. (CDRL: A001)

3.1.2.3 Technical Support: The contractor shall determine the actions necessary to satisfy inventory stocking needs for items and projecting out-year requirements for repair and procurement. The contractor shall allocate material for managing assets, processing customer orders, and developing and managing repair workload. The contractor shall manage repairs which includes identifying, scheduling and funding requirements. (CDRL: A001)

3.1.2.4 Interim Maintenance Support: The contractor shall provide on-site services for equipment/systems and perform troubleshooting, disassembly/assembly, modification, repair, and rebuild. (CDRL: A001)

3.1.3 Critical Continuity Requirements: The proposed contractor, in the response to the solicitation, should provide the Government with the breadth and depth of personnel proposed to accomplish the work and have a minimum of 20 years of direct work related experience in all aspects of this request. Technical qualification will be directly related to how recent the knowledge is of MESC operational requirements in each of the areas described above. While price is important in a best value procurement, the most successful contractor for this critical work will provide the least impact to transition of work, and will propose staff who have recent relevant knowledge of MESC requirements.

3.1.4 Key Personnel: No resumes are required. Responders may elaborate on the technical and experience qualifications of staff proposed to perform the work.

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 software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B.

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 task order 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 REPRESENTATIVE (COR) DESIGNATION

The COR for this task order is identified in task order clause 5252.201-9201.

5.2 CONTRACTOR 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 A005) and submit it monthly at least 30 days after contract award on the 10th of each month. Only one report is submitted per contract. The prime shall be responsible for collecting, integrating, and reporting all subcontractor reports. 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 Personnel Listing (CDRL A001 Attachment 2 of Exhibit A) necessary for additional data collection as applicable.

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). The Product/Service Codes (PSC) for contracted services excluded from reporting are as follows:

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 task order 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 Invoicing Notification and Support Documentation Pursuant to DFARS clause 252.232-7003 and 252.232-7006, the contractor shall submit payment requests and receiving reports using DoD Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) application (part of the Wide Area Work Flow (WAWF) 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 iRAPT/WAWF 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 iRAPT/WAWF. When requested by the COR, the contractor shall directly provide a soft copy of the invoice and any invoice supporting documentation (CDRL A003) 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.4 CONTRACTOR PERFORMANCE MANAGEMENT

Contractor performance standards and requirements are outlined in the contract/task order 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 A005) submitted 10 days after contract award and CPARS Draft Approval Document (CDAD) Report (CDRL A006) submitted monthly.

6.0 DOCUMENTATION AND DELIVERABLES

6.1 CONTRACT DATA REQUIREMENTS LIST (CDRLs)

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.

Classification (up to S/TS or unclassified)

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 SPAWARSYSCEN Atlantic corporate standard software configuration as specified below. Contractor shall conform to SPAWARSYSCEN 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.3 PERIOD OF PERFORMANCE will be one year from date of award.

7.0 QUALITY

The contractor shall provide quality support in accordance with the basic contract requirements.

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. The contractor shall make their quality system available to the Government for review at both a program and worksite services level during predetermined visits. Existing quality documents that meet the requirements of this contract may continue to be used. The contractor shall also require all subcontractors to possess a quality assurance and control program commensurate with the services and supplies to be provided as determined by the prime’s internal audit system. The Government reserves the right to disapprove the contractor’s and/or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet contractual requirements at either the program or worksite services level. The Government reserves the right to participate in the process improvement elements of the contractor’s quality assurance plan or quality system, and development of quality related documents. At a minimum, the contractor shall ensure their quality system meets the following key criteria:

· Establish documented, capable, and repeatable processes

· Track issues and associated changes needed

· Monitor and control critical process, product, and service variations

· Establish mechanisms for feedback of field product and service performance

· Implement and effective root-cause analysis and corrective action system

· Establish methods and procedures and create data used for continuous process improvement

7.2 MANAGE QUALITY COMPLIANCE

7.2.1 General

The contractor shall have quality processes or a Quality Management System (QMS) processes in place that coincide with the Government’s Manage Quality processes which address Quality Control, Quality Assurance, Software Quality, and/or project Quality System tasks. The contractor shall use best industry practices including, when applicable, ISO/IEC 15288 for System life cycle processes and ISO/IEC 12207 for Software life cycle processes. As applicable, the contractor shall also support and/or participate in Acquisition Milestones, Phases, and Decision Points, which are standard elements of the Defense Acquisition System and support DoDD 5000.01 and DoDI 5000.02. The contractor shall provide technical program and project management support that will mitigate the risks to successful program execution including employment and objective evidence of Lean Six Sigma, Risk Management, and System Engineering methodologies; and System and Software Engineering best practices.

8.0 SECURITY

8.1 ORGANIZATION

8.1.1 Security Classification

As specified in the DoD Contract Security Classification Specification, DD Form 254, the contractor shall perform classified work under this task order. At time of task order award, the contractor shall have a SECRET facility clearance (FCL).

8.1.1.1 U.S. Government security clearance eligibility is required to access and handle classified and certain controlled unclassified information (CUI), attend program meetings, and work within restricted areas unescorted. Access to SCI is limited to U.S. Government Facilities or other U.S. Government sponsored SCI Facilities (SCIFs) authorized on the DD254. The contractor shall not generate any SCI deliverables.

8.1.1.2 This task order allows for various levels of security to support specific PWS tasks. The following table outlines the minimum required security clearance per task. The contractor shall provide personnel meeting the specific minimum personnel clearance (PCL) to support the PWS tasks listed below

8.1.2 Security Officer

The contractor shall appoint a Facility Security Officer (FSO) to support those contractor personnel requiring clearance and/or access to Government facility/installation and/or access to information technology systems under this task order. The FSO is typically key management personnel who is the contractor’s main POC for security issues. The FSO shall have a U.S. Government security clearance equal to or higher than the FCL required on this/task order. The FSO shall be responsible for tracking the security requirements for all personnel (subcontractors included) utilized on task order. Responsibilities include tracking all personnel assigned Government badges and entering/maintaining personnel security mandatory training information within the Staffing Plan document, which is an attachment to the contract status report (CSR) (CDRL A001), and if applicable, updating and tracking data in the CSWF Report (CDRL CSWF NOT APPLICABLE FOR THIS TO).

8.2 PERSONNEL

The contractor shall conform to the security provisions of DoDI 5220.22/DoD 5220.22-M – National Industrial Security Program Operating Manual (NISPOM), SECNAV M-5510.30, DoD 8570.01-M, and the Privacy Act of 1974. Prior to any labor hours being charged on task order, the contractor shall ensure their personnel (including administrative and subcontractor personnel) have obtained and can maintain favorable background investigations at the appropriate level(s) for access level required by this task order, and if applicable, are certified/ credentialed for the CSWF. A favorable background determination is determined by either a Tier 1 (T1) investigation, Tier 3 (T3) investigation, or Tier 5 (T5) investigation and favorable Federal Bureau of Investigation (FBI) fingerprint checks. Investigations are not necessarily required for personnel performing unclassified work who do not require access to Government installations/facilities, Government IT systems and IT resources, or SPAWARSYSCEN Atlantic information. Cost to meet these security requirements is not directly chargeable to the contract.

NOTE: If a final determination is made that an individual does not meet or cannot maintain the minimum security fitness requirements, the contractor shall permanently remove the individual from SPAWARSYSCEN Atlantic facilities, projects, and/or programs. If an individual who has been submitted for a fitness determination or security clearance is "denied," receives an "Interim Declination," or unfavorable fingerprint, the contractor shall remove the individual from SPAWARSYSCEN Atlantic facilities, projects, and/or programs until such time as the investigation is fully adjudicated or the individual is resubmitted and is approved. All contractor and subcontractor personnel removed from facilities, projects, and/or programs shall cease charging labor hours directly or indirectly on the contract.

8.2.1 Personnel Clearance

The majority of personnel associated with this TO shall possess a SECRET personnel security clearance (PCL). Some of the individual TOs issued against this TO will require personnel to possess higher clearance levels such as TOP SECRET. These programs/tasks include contractor personnel having the appropriate clearances required for access to classified data as applicable. Prior to starting work on the task, contractor personnel shall have the required clearance granted by the DoD CAF and shall comply with IT access authorization requirements. In addition, contractor personnel shall possess the appropriate IT level of access for the respective task and position assignment as applicable per DoDI 8500.01, DoD Instruction for Cybersecurity. Any future revision to the respective directive and instruction will be applied as a TO modification. Contractor personnel shall handle and safeguard any Controlled Unclassified Information (CUI) and/or classified information in accordance with appropriate Department of Defense, Navy, and SPAWARSYSCEN Atlantic security regulations. The contractor shall immediately report any security violation to the SPAWARSYSCEN Atlantic Security Management Office, the COR, and Government Project Manager.

8.2.1.1 The following labor categories shall meet or exceed the required personnel clearances (PCL) listed below:

8.2.2 Access Control of Contractor Personnel

8.2.2.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.

8.2.2.2 Identification and Disclosure Requirements

Regardless if a contractor is physically located on Government installation or not, the contractor and subcontractor employees shall take all means necessary to not represent themselves as Government employees. All contractor personnel shall follow the identification and Government facility disclosure requirement as specified in contract clause 5252.237-9602, Contractor Identification.

8.2.2.3 Government Badge Requirements

Some contract personnel shall require a Government issued picture badge in accordance with contract clause 5252.204-9202, Contractor Picture Badge. While on Government installations/facilities, contractors shall abide by each site’s security badge requirements. Various Government installations are continually updating their security requirements to meet Homeland Security Presidential Directive (HSPD-12) identification standards. Contractors are responsible for obtaining and complying with the latest security identification requirements for their personnel. Contractors shall submit valid paper work (e.g., site visit request, request for picture badge, and/or SF-86 for CAC) to the applicable Government security office via the COR or Contracting Officer. The contractor (FSO is applicable) shall track all personnel holding local Government badges at the contract level.

8.2.2.4 Common Access Card (CAC) Requirements

Some Government facilities/installations (e.g., Joint Base Charleston) require contractor personnel to have a CAC for physical access to the facilities or installations. Contractors supporting work that requires access to any DoD IT/network also requires a CAC. Granting of logical and physical access privileges remains a local policy and business operation function of the local facility. The contractor is responsible for obtaining the latest facility/installation and IT CAC requirements from the applicable local Security Office. When a CAC is required to perform work, contractor personnel shall be able to meet all of the following security requirements prior to work being performed:

8.2.2.5 Contractor Check-in and Check-out Procedures

All SPAWARSYSCEN Atlantic contractor personnel requiring or possessing a Government badge and/or CAC for facility and/or IT access shall have a SPAWARSYSCEN Atlantic Government sponsor and be in compliance with the most current version of Contractor Check-in and Check-out Instruction and Forms as posted on the Command Operating Guide (COG) website. Throughout contract performance, the contractor shall provide necessary employee information and documentation for employees hired, transferred, and/or terminated in support of this contract within the required timeframe as cited in the Check-in and Check-out instructions. The contractor (FSO, if applicable) shall ensure all contractor employees whose services are no longer required on this contract return all applicable Government documents/badges to the appropriate. If the contractor does not have access to the SPAWARSYSCEN Atlantic COG website, the contractor shall get all necessary instruction and forms from the COR.

8.2.3 Mandatory Training

Contractor personnel (including subcontractors) shall complete all applicable required mandatory Government training in accordance with COMSPAWARSYSCOM Code 8.0.3.3.0 mandatory training webpage: https://wiki.spawar.navy.mil/confluence/display/HQ/Employee+Mandatory+Training. Contractors without access to the SPAWAR webpage shall coordinate with the COR concerning mandatory training as listed on the training webpage.

8.2.3.1 The contractor shall be responsible for verifying applicable personnel receive all required training. The contractor shall report individual contractor personnel training status by completing and updating the contract status report (CSR) (CDRL A001 Attachment 1 of Exhibit A), Training tab.

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. Pursuant to DoDD 5205.02E and SPAWARINST 3432.1, SPAWARSYSCEN Atlantic’s OPSEC program implements requirements in DoD 5205.02-M – OPSEC Program Manual and SPAWARSYSCENLANTINST 3070.1B. Note: OPSEC requirements are applicable when contract personnel have access to classified information or unclassified Critical Program Information (CPI)/sensitive information.

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 and annual OPSEC awareness training. In addition to online OPSEC training provided through the Total Workforce Management System (TWMS), training may be provided by the Government or a contractor’s OPSEC Manager. Contractor training shall, as a minimum, cover OPSEC as it relates to contract work, discuss the Critical Information applicable in the contract, and review OPSEC requirements if working at Government facilities. The contractor shall ensure any training materials developed by the contractor shall be reviewed by the SPAWARSYSCEN Atlantic OPSEC Officer, who will ensure it is consistent with SPAWARSYSCEN Atlantic OPSEC policies. OPSEC training requirements are applicable for personnel during their entire term supporting this SPAWARSYSCEN Atlantic contract.

8.3.3 SPAWARSYSCEN Atlantic OPSEC Program

Contractor shall participate in SPAWARSYSCEN 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.

9.0 GOVERNMENT FURNISHED INFORMATION (GFI)

Government Furnished Information (GFI) is Government owned intellectual property provided to contractors for performance on a task order. For the purposes of this task order, GFI includes manuals, technical specifications, maps, building designs, schedules, drawings, test data, etc. 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.

GFI is utilized on this task order. Any applicable document (PWS Para 16.0) not available online, the Government will provide document as GFI listed in the table below. The contractor shall inventory all GFI by tracking distribution and location and provide a GFI inventory to the Government. The contractor shall use the GFI provided to support this task order only – use of GFI document(s) to support other projects beyond this task order is not allowed. Unless otherwise specified, all GFI will be provided by the Government by the estimated delivery date listed in the table below, and the contractor shall return all GFI to the Government at completion of the task order. If a contractor requires additional GFI other than what is listed, the contractor shall submit a request to the COR within 30 days after task order award.

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). Government property is material, equipment, special tooling, special test equipment, and real property.

GFP will not be provided and CAP is not anticipated on this task order.

10.1 GOVERNMENT-FURNISHED PROPERTY (GFP)

As defined in FAR Part 45, GFP is property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract. GFP includes spares and property furnished for repair, maintenance, overhaul, or modification. GFP includes Government-furnished equipment (GFE), Government-furnished material (GFM), Special Tooling (ST) and Special Test Equipment (STE).

GFP will not be provided on this task order.

10.1.1 Government-Furnished Equipment

GFE will not be provided on this task order.

10.1.2 Government-Furnished Material

GFM will not be provided on this contract.

10.1.3 Special Test Equipment

STE will not be provided on this contract.

10.1.4 Special Tooling

ST will not be provided on this contract

10.2 CONTRACTOR-ACQUIRED PROPERTY (CAP)

As defined in FAR Part 45, CAP is property acquired, fabricated, or otherwise provided by the contractor for performing a contract and to which the Government has title but has not yet performed receipt and acceptance. CAP consists of Contractor-acquired equipment (CAE), Contractor-acquired material (CAM), ST, and STE.

CAP is not anticipated on this task order.

10.3 TRANSPORTATION OF EQUIPMENT/MATERIAL

No transportation of equipment/material is required by the contractor on this contract.

11.0 TRAVEL

11.1 LOCATIONS

The contractor shall be prepared to travel to the following locations. Prior to any travel taken in support of this task order, the contractor shall obtain COR concurrence

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.

12.2 SAFETY EQUIPMENT

The contractor shall provide their personnel with any safety equipment required to perform work under this contract and the equipment must be in satisfactory working order. Personal safety equipment includes items such as hard-hats, safety shoes, safety gloves, goggles, hearing protection, non-flammable clothing for hot work personnel, gas/oxygen detectors for confined spaces, face shields, and other types of safety equipment required to assure a safe work environment and compliance with applicable federal, state and local safety regulations.

12.3 SAFETY TRAINING

The contractor shall be responsible to train all personnel that require safety training. Specifically, where contractors are performing work at Navy shore installations, that requires entering manholes or underground services utility the contractor shall provide a qualified person as applicable in 29 CFR 1910 or 29 CFR 1926 or as recommended by the National Institute for Occupational Safety and Health (NIOSH) Criteria Document for Confined Spaces. Also, when contractors are required to scale a tower, all applicable personnel shall have Secondary Fall Protection and Prevention training.

13.0 SUBCONTRACTING REQUIREMENTS

13.1 APPROVED SUBCONTRACTORS

Subcontracting requirements are in accordance with the basic contract. If the prime contractor is planning to utilize subcontractor(s) on this task order, the applicable subcontractors shall be specified at task order award. Per FAR clause 52.244-2, if a subcontractor (includes tier 1, tier 2, tier 3, etc.) is proposed by a prime and is not approved on the basic contract, formal justification is required and subject to Government approval.

14.0 ACCEPTANCE PLAN

Inspection and acceptance is performed by the COR on all services, data, and non-data deliverables in accordance with the QASP, Attachment…