SOW N66001-18-R-0110 Special Projects-Elec Sys (Draft).pdf

PDF 221 KB Posted

Attached to
Special Projects and Electronics Systems
Solicitation number
N66001-18-R-0110
Issued by

About this file

This statement of work outlines requirements for a multiple award indefinite-delivery/indefinite-quantity contract to provide sustainment and technical support services for special projects and electronic systems at the Space and Naval Warfare Systems Center Pacific. Key requirements include management, hardware engineering, software engineering, configuration management, and logistics support for systems such as advanced wireless systems, submarine receivers and surveillance systems, command and control systems, and audiovisual equipment. Work will involve experimental development, demonstrations, maintenance, and upgrades performed in the United States, Alaska, Hawaii, and worldwide. The contract is expected to have a base period of three years with two option periods of two years each and will require secret-level security clearance. Incumbents on the predecessor contract are Science Applications International Corporation and Serco Inc. The estimated level of effort is 465,920 hours over seven years. Release of the solicitation for these services is planned for the fourth quarter of fiscal year 2018.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

N66001-18-R-0110

Statement of Work (SOW)

Code 41170 Special Projects and Electronic Systems Contract

SPAWAR Systems Center Pacific (SSC PACIFIC)

18 June 2018

STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) covers the requirements of SSC Pacific Code 41170, Special Projects and Electronic Systems Branch. Contractor services are required to assist the branch in its execution of sustainment and technical support of Special Projects and Electronic systems. The support includes experimental, demonstration, and developmental technology for the U.S. Navy, e.g. Naval Mine and Anti-Submarine Warfare Command, SPAWAR Program Executive Offices, Commander Third Fleet (C3F), Naval Sea Systems Command, Naval Facilities Command, as well as Department of Homeland Security, Customs and Border Protection, and other Government activities.

The services will include at a minimum the following areas: Management, Hardware Engineering, Software Engineering, Configuration Management and Logistics. The primary systems and efforts to be supported under this contract are listed below. Any replacement, follow-on or interrelated system shall be covered by this SOW. Work will be performed at operational platform sites, shore-based sites, and training activities located in the continental United States (CONUS), Alaska, Hawaii, and other locations worldwide, as specified at the Task Order level.

The following systems and support services will be required under this contract. Systems/Services are listed in order of importance:

Advanced Wireless Systems (AWS) – Microwave Communication Submarine LF/VLF Receiver (SLVR) Submarine Electronic Surveillance Systems and ancillary sub-systems (AN/WLR-8, AN/BRD-7) Command, Control, Communications, Computers & Intelligence (C4I) System Technology Upgrades and Sustainment Services Military Construction C4I Support Audio Visual/Video Teleconferencing Support

2.0 APPLICABLE DOCUMENTS

The following documents are referenced for guidance only and form a part of the statement of work to the extent specified herein. Unless otherwise specified, the issues of the documents below will be those listed in the Department of Defense Index of Specifications and Standards (DoDISS) and supplement thereto, cited in the solicitation. The document to be used shall be the issue in effect at the award of each task order. In the event of a conflict between this statement of work and the documents herein, the text of the statement of work will take precedence. Nothing in this statement of work however, shall supersede applicable laws and regulations, unless a specific exemption has been obtained.

DEPARTMENT OF DEFENSE DOCUMENTS

2.1 DOD 5000.2-M, Department of Defense Manual, Defense Acquisition Management documentation and Reports.

2.2 DOD Directive 5000.1, Defense Acquisition.

2.3 DOD Directive 8570.01, Information Assurance Training, Certification, and Workforce

Management

2.4 DOD INST 5000.2, Defense Acquisition Management Policies and Procedures

2.5 DOD INST 5220.22-M, National Industrial Security Program Operating Manual (NISPOM)

2.6 DOD INST 8570.01-M, Information Assurance Workforce Improvement Program

2.7 DOD-STD-00100D(AR), Engineering Drawing Practices

CHIEF OF NAVAL OPERATIONS / SECRETARY OF THE NAVY

2.8 OPNAVINST 5513.8C, Security Classification Guide for Electronic Warfare Program, JUL 2008 (Applicable Enclosures).

2.9 OPNAVINST 5513.5C Security Classification Guide for Undersea Warfare Program, JUL 2008 (Applicable Enclosures).

2.10 OPNAVINST 4790.4D, Navy Maintenance and Material Management (3M) Plan; Planned Maintenance Subsystems (PMS)

2.11 OPNAVINST 5100.23G Navy Safety and Occupation Health Program Manual

2.12 OPNAVINST 5100.19E Navy Safety and Occupational Health Program Manual for Forces Afloat

2.13 ASN RDA Memorandum, DON Policy on Digital Product / Technical Data of 23 Oct 2004

2.14 ASN RDA Memorandum, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Guidance 27 Jan 2005

2.15 SECNAVINST 5239.2 Cyber Security/Information Assurance Workforce Management, Oversight, and Compliance 17 June 2010

NAVSEASYSCOM / SPAWARSYSCOM

2.16 NAVSEA S0300-BD-PRO-010/020/030, VOLS I, II, III, Integrated Logistics Support (ILS) Procedures Manual for Systems/Equipment.

2.17 NAVSEA SL720-AA-MAN-010/020, VOLS I, II, Fleet Modernization Program (FMP) Management and Operations Manual

2.18 NAVSEAINST 4130.12B, Configuration Management Policy and Guidance

2.19 NAVSEAINST 4720.11C, Shipboard Installations and Modifications Performed by Alteration Installation

2.20 NAVSEAINST 4720.16, Logistics Management Procedures for Configuration Changes Installed

Outside of Depot Level Availabilities

2.21 NAVSEAINST 5000.39, Acquisition and Management of Integrated Logistic Support for Ships, Systems and Equipment.

2.22 NAVSEA S9407-AB-HBK-010, Handbook of Shipboard Electromagnetic Shielding Practices.

2.23 NAVSEA S9074-AQ-GIB-010/248, Requirements for Welding and Brazing Procedure and Performance Qualifications

2.24 NAVSEA STD-407-5287561, Industrial Electromagnetic Compatibility (IEMC) Work Process Instructions

2.25 NAVSEA Technical Specification 9090-100 (series); SHIPALT Technical Liaison Services, Waivers, and Deviations

2.26 NAVSEA Technical Specification 9090-310D (series); Ship Alteration Accomplishment by Alteration Installation Teams

2.27 NAVSEA Technical Specification 9090-600 (series); Ship Alteration (SHIPALT) Installation Drawing (SID) Preparation

2.28 NAVSEA Technical Specification 9090-700 (series); Ships Configuration and Logistics Support Information System (SCLSIS)

2.29 SPAWARSYSCOM, Shore Installation Process Handbook (SIPH Ver.3)

2.30 SPAWARINST 3084.1 SPAWAR 5.9 03 Dec 08 SPEG

2.31 SPAWARINST 4720.1 Policy and Procedures for Installation of C4ISR and Other Electronic

Systems

2.32 JFMM ACN 02-04 Surface Ship and Aircraft Carrier Modernization Program (SHIPMAIN).

NATIONAL SECURITY AGENCY

2.33 National Security Telecommunications and Information Systems Security (NSTISS)

2.34 NSTISSAM TEMPEST /2-95 Red/Black Installation Guidance

MILITARY HANDBOOKS/GUIDEBOOKS

2.35 MIL-HDBK-29612 Guidance for Acquisition of Training Data Products and Services

2.36 MIL-HDBK-61A, Configuration Management Guidance

2.37 MIL-HDBK-217F, Reliability Predictions of Electronic Equipment.

2.38 MIL-HDBK-419A, Grounding, Bonding, and Shielding for Electronic Equipment and Facilities

2.39 MIL-HDBK-454B, General Guidelines for Electronic Equipment

2.40 MIL-HDBK-781A, Reliability Test Methods, Plans and Environments for Engineering, Development, Qualification and Production

2.41 MIL-HDBK-881A, Work Breakdown Structures for Defense Material Items

2.42 MIL-HDBK-46855A, Human Engineering Requirements for Military Systems, Equipment, and

Facilities

2.43 SD-22 Diminishing Manufacturing Sources and Material Shortages, Best Practices and Tools for Implementing a Proactive DMSMS Management Program

MILITARY SEPCIFICATIONS AND STANDARDS

2.44 MIL-PRF-32216A Evaluation of Commercial Off-the Shelf (COTS) Manuals and Preparation of

Supplemental Data

2.45 MIL-STD-130N, Identification of Marking U.S. Military Property

2.46 MIL-STD-2003A (Navy), Electric Plant Installation Standard Methods for Surface Ships and

Submarines.

2.47 MIL-D-23140D, Drawings, Installation Control Electronics Equipment

2.48 MIL-STD-31000, Technical Data Packages

2.49 MIL-M-85337A, Technical Manuals, QA Program Requirements.

2.50 MIL-STD-130N, Identification and Marking of US Military Property

2.51 MIL-STD-40051-1A Preparation of Digital Technical Information for Interactive Electronic

Technical Manuals (IETMs)

2.52 MIL-STD-1472F, Human Engineering

2.53 MIL-STD-2110, Restoration, Overhaul, and Repair of Electronic Equipment.

2.54 MIL-STD-38784A, Manuals, Technical: General Style and Format Requirements.

2.55 MIL-STD-1310H, Shipboard Bonding, Grounding and other Techniques for Electromagnetic Compatibility, Electromagnetic Pulse (EMP) Mitigation and Safety

2.56 MIL-STD-2036, Electronic Equipment Specifications, Preparation of

COMMERICIAL TECHNICAL MANUALS, STANDARDS, SPECIFICATIONS, AND

PRACTICES

2.57 ASME-Y-14.5 Dimensioning and Tolerancing

2.58 ASME-Y14.100 Engineering Drawing and Related Documentation Practices

2.59 ASME-Y14.24, Types and Applications of Engineering Drawings

2.60 ASME-Y14.34, Lists, Associated

2.61 ASME-Y14.35M, Revision of Engineering Drawings and Associated Documents

2.62 IEEE315A: Graphical Symbols for Electrical and Electronic Diagrams

2.63 IEEE/EIA 12207 Software Life Cycle Process

2.64 ISO 9000: Quality Management Systems

2.65 ANSI Z39.18 Scientific and Technical Reports – Elements, Organization, and Design

CYBER SECURITY

2.66 DoDI 5200.02 DoD Personnel Security Program (PSP) Reissues DoD Directive (DoDD) 5200.02

2.67 DoDM 5200.01 DoD Manual – Information Security Program Manual dtd 24 Feb 12

2.68 DoDD 5205.02E DoD Directive – Operations Security (OPSEC) Program dtd 20 Jun 12

2.69 DoD 5205.02-M DoD Manual – Operations Security (OPSEC) Program Manual dtd 3 Nov 08

2.70 DoDI 5220.22 DoD Instruction – National Industrial Security Program dtd 18 Mar 11

2.71 DoDI 6205.4 Department of Defense Instruction, Immunization of Other Than U.S. Forces

(OTUSF) for Biological Warfare Defense dtd 14 Apr 00

2.72 DoDI 8500.01 DoD Instruction – Cybersecurity dtd 14 Mar 14

2.73 DoDI 8510.01 DoD Instruction – Risk Management Framework (RMF) for DoD Information

Technology (IT) dtd 12 Mar 14

2.74 DoDD 8140.01 Cyberspace Workforce Management dtd 11 Aug 15

2.75 SECNAV M-5510.30 Secretary of the Navy Manual – DoN Personnel Security Program dtd Jun

2.76 SECNAVINST 4440.34 Secretary of the Navy Instruction – Implementation of Item Unique

Identification within the DoN, dtd 22 Dec 09

2.77 SECNAVINST 5239.19 Incident Response, dtd Mar 08

2.78 SECNAVINST 5239.20A DON Cyberspace IT and Cybersecurity dtd 10 Feb 16

2.79 SECNAVINST 5239.3C DON Cybersecurity Policy, dtd 2 May 16

2.80 SECNAVINST 5510.30 DON Regulation – Personnel Security Program dtd 6 Oct 06

2.81 DON CIO Memorandum Acceptable Use of Department of the Navy Information Technology

(IT) dtd 12 Feb 16

2.82 SPAWARINST 3432.1 SPAWAR Instruction – Operations Security (OPSEC) Policy dtd 2 Feb

2.83 SPAWARINST 4440.12 Management of Operating Materials and Supplies (OM&S), Government Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory

2.84 SPAWARINST 5721.1B SPAWAR Section 508 Implementation Policy, 17 Nov 09

2.85 COMUSFLTFORCOM/COMPACFLTINST 6320.3A Commander US Fleet Forces

Command/Commander US Pacific Fleet Instruction, Medical Screening For US Govt Civilian Employees, Contractor Personnel, and Guests prior to embarking Fleet Units, of 7 May 13

2.86 Navy Telecommunications Directive (NTD 10-11) System Authorization Access Request

(SAAR) - Navy

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all required support tasks that will be required throughout the contract life.

The contractor shall provide necessary resources and knowledge to support the listed tasks. Specific objectives will be dependent on the basic contract and the task order (TO) written against the basic contract. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

The contractor shall perform the following tasks in accordance with this SOW and each individual task order issued by SSC Pacific:

3.1 Management Support

3.1.1 Provide management support and recommendations for program reviews. This shall include tracking outstanding actions. The contractor shall develop cost estimates, cost comparison analysis, project briefs, and whitepapers.

3.1.2 Collect data, conduct engineering analyses and evaluate engineering parameters associated with long range planning for out-year programs to assist in development, maintenance, and use of an advanced technology base.

3.1.3 Develop, evaluate, revise and make recommendations to management plans, documents, and drawings.

3.1.4 The contractor shall support conferences and meetings by generating and submitting conference/ meeting minutes.

3.1.5 Review maintenance methods and procedures, investigate areas requiring improved or additional personnel maintenance training/techniques, and provide recommendations for minimum maintenance requirements including General Purpose Electronic Test Equipment (GPETE), Special Purpose Electronic Test Equipment (SPETE), and tools required. Recommend revisions to existing technical support documentation.

3.1.6 Ship/transport systems, subsystems, units, components, Field Change Kits (FCK), Engineering Change Proposals (ECPs) and other essential materials to destinations as defined by the individual task order.

3.2 Hardware Engineering

3.2.1 Provide sustainment support in developing, maintaining, documenting, and integrating upgrades.

This sustainment support includes, but is not limited to, developing ILS action item lists;

developing ILS and Configuration Management Plan (CMP) input to the Program Management Plan (PMP); preparing ILS and sustainment updates to Project Execution documents (e.g., SOW template and appendices); prepare ILS inputs for briefings for Program Management Review (PMR) and Periodic Performance Business Reviews (PPBR); maintaining ILS Master POA&M;

providing oversight for preventive maintenance plans (including milestones and schedules), and developing/ and recommending overall maintenance policies and procedures.

3.2.2 Perform on site analysis of system fault symptoms, assess degree of operational impairment/mission degradation, recommend alternate operational modes, as applicable, and effect all necessary repairs.

3.2.3 Perform on site analysis in support of system requirements, assess degree of operational capability to support system requirements, and recommend alternative approaches to satisfying system/functional requirements.

3.2.4 Investigate requirements for, developing, and evaluating (including field-testing) Field Changes

(FCs), Engineering Change Proposals (ECPs), Enterprise Change Requests (ECR), Engineering Change Notices (ECNs), Engineering Change Instructions (ECIs), Engineering Change Orders (ECO), and ShipAlts (SAs). Develop and generate Capability Matrix, Requirements Analysis Document (RAD), Program Management Plan (PMP), MILCON Base Electronic Systems Engineering Plan (BESEP), Integrated Master Plan (IMP), Plan of Action and Milestones

(POA&M) and Resource-Loaded Work Breakdown Structure (RL-WBS), Project Risk Status Report.

3.2.5 Develop and assemble Field Change (FC) Kits including providing all required documentation, such as Field Change Bulletin (FCB), interim PMS, Allowance Parts List (APL), Technical Manual (TM) Change pages.

3.2.6 Proof test changes kits/packages on NAVY Engineering Control Configuration Model (CCM) or on selected operational platforms.

3.2.7 Maintain, repair, modify and test systems and related communication subsystems and audio -video telecommunication systems

3.2.8 Groom, test, checkout, and evaluate systems/equipment.

3.2.9 Develop, analyze, or revise and/or recommend improvements to test methods, practices, and procedures, including test points, test features, and required test equipment.

3.2.10 Develop, analyze, procure, or revise and/or recommend improvements for special test equipment, special tools, special test fixtures, or maintenance related support material items.

3.2.11 Collect and/or correlate system, subsystem, unit, or component level maintenance, reliability, availability, maintainability, or operational performance data.

3.2.12 Perform engineering development of hardware systems. Develop draft engineering plans and specifications, perform risk identification/analysis/mitigation, and perform traceability. The contractor shall suggest an integration solution. Develop a working model of a system or group of systems. Typical associated tasks include, but are not limited to: computer-aided design, design studies and analysis, high-level detailed specification preparation, configuration management, and document control.

3.2.13 Design, analyze, and develop test procedures and review designs of entire systems and subsystems involving both hardware and software considerations.

3.2.14 Perform reliability and Quality Assurance (QA) engineering and perform failure analysis.

3.2.15 Provide fabrication, assembly and manufacturing support.

3.2.16 Perform Failure Reporting, Analysis and Corrective Action Systems (FRACAS), failure analysis, obsolescence analysis, and Reliability and Maintainability (R&M) analysis. The contractor shall also have access to the Supportability Management Assessment Report Tool (SMART).

3.2.17 Perform obsolescence monitoring and management utilizing the guidance provided in the ASN RDA Memorandum, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Guidance (SOW 2.14).

3.2.18 Analyze system operational characteristics, mission objectives, threat, environmental factors, minimum acceptable functional requirements, and technical performance for change and enhancement.

3.2.19 Design and develop engineering development models.

3.2.20 Perform system/equipment tests, Groom, checks, inspections, and certifications including Pre Installation Test and Checkout (PITCO), Pre-overhaul Test and Inspection (POT&I), System Operations and Validation Testing (SOVT).

3.2.21 Conduct testing, such as Operational Test/Development Test (OT/DT), and Acceptance Test

Procedure (ATP) at the system, subsystem, unit, or component level. Evaluate test results against prescribed standards. Identify changes required to Test & Evaluation Master Plan (TEMP), test procedures, or other related documentation.

3.2.22 Perform restoration, calibration, certification, refurbishment, overhaul, or repair of designated equipment/systems.

3.2.23 Procure materials to support urgent Fleet technical assistance requests, and any task or requirement defined in the individual task order.

3.2.24 Perform analysis in the determination of attributable causes of failures and malfunctions and the identification of potential areas for redesign and improvement.

3.2.25 Perform system/equipment upgrades.

3.2.26 Perform value engineering support and collection of data to better assess value-engineering proposals.

3.2.27 Implement Item Unique Identification (IUID) system to identify item or asset for tracking and identification.

3.2.28 Provide Technical Sustainment Support (TSS) to fleet customers by providing timely information and technical assistance through approved enterprise processes relative to customer’s service requests. Provide metrics for time to close tickets and time tickets open.

3.3 Software Engineering

3.3.1 Provide sustainment support in maintaining, documenting, and integrating software upgrades.

3.3.2 Plan, analyze, investigate, sustain software code, test, integrate, implement, evaluate, support, deliver, and load software.

3.3.3 Update, maintain and modify, integrate, and manage configuration of software, including operational, maintenance, and diagnostic programs for installed equipment, support equipment, license fees, and training equipment. This includes Information Assurance & Vulnerability Assessment (IAVA) responses, Security Technical Implementation Guide (STIG) implementation and other security driven changes.

3.3.4 Provide technical representation to the configuration control board for the evaluation and disposition of all proposed changes to the documentation produced.

3.4 Configuration Management & Logistics Support

3.4.1 Develop and review provisioning data in ICAPS format for On-Board Repair Parts (OBRPs), correlate Source Material &Reporting coding, failure history, allowance levels, and provide recommendations for changes to existing provisioning documentation.

3.4.2 Review/write maintenance related data including, but not limited to, failure data from Casualty

Reports (CASREPs), 3M reports, Reliability, Availability & Maintainability reports, and FRACAS/data to determine and recommend corrective actions.

3.4.3 Conduct Physical Configuration Audit/Validations of installations against the specified system baseline engineering drawings including any authorized changes. Gather data and maintain records to update Casualty Status and Reporting’s (CSARs) or other CM documentation as required.

3.4.4 Evaluate equipment/system operability, maintainability, reliability, and logistic support and provide recommendations for revisions, as required to optimize operational and material readiness.

3.4.5 Develop/Evaluate sustainment requirements such as Design Interface, CM, Standardization, R&M, LSA, Level of Repair Analysis, QA, Supply Support/PTD, PHS&T, Computer Resources Support, Engineering Drawings, Facilities, Maintainability &Procurement, Training Safety, Support Equipment, necessary to insure effective and economic support of cognizant equipment/systems. Provide recommendations for changes/revisions to ILS documentation/ requirements.

3.4.6 Evaluate, develop, or revise PMS/Reliability Centered Maintenance documentation.

3.4.7 Verify system/equipment configurations. Correct differences between installed configuration and authorized baseline including approved modifications. Record and report all unauthorized modifications.

3.4.8 Develop, review, audit, or revise training plans, curricula, and training support equipment for designated systems/equipment.

3.4.9 Develop and conduct training programs in installation, operation, and maintenance to support systems/equipment or major modifications to systems/equipment.

3.4.10 Provide media capture (video) of activities during the demonstration event including web-based data collection capabilities to support worldwide data collection at remote sites with limited access.

3.4.11 Develop and conduct specialized training for maintenance service activities, such as Naval Ships

Systems Engineering Station (NAVSSES), Naval Undersea Warfare Center (NUWC), SUPSHIPS, Submarine Surveillance Equipment Program (SSEP), Naval Security Group Activity (NSGA), In-Service Engineering Activity (ISEA), Ship Repair Facilities (SRF), Fleet Training Systems Command Detachment (FTSCDETs), Submarine Training Centers/Facilities, Trident Refit Facilities (TRFs), Trident Training Facilities (TTFs), Shipyards, Submarine Maintenance, Engineering, Planning, & Procurement (SUBMEPP), ), and Intermediate Maintenance Activity (IMAs) to develop competent local expertise to support system/equipment end item users.

3.4.12 Develop, review, or revise technical manuals, engineering drawings and associated parts lists.

3.4.13 Prepare Engineering Change Notices and Instructions, Engineering Change Proposals, Enterprise

Change Requests, Engineering Change Orders and Field Change Packages including supporting technical documentation (MRC/TM Change Pages/FCB/APL), and provide spares and repair parts. Deliver and full-fill ILS requirements for engineering change and field change incorporation, Coordinate engineering change and field change installation with Configuration Data Managers (CDMs). This involves updating and verifying configuration data listings in CDMA-OA and ILS listings in the Weapon System File (WSF).

3.4.14 Prepare and develop ILS products including the submission of the ILS Certification form to the ILS Certification Manager. Resolve ILS Certification validation issues. Provide ILS product maturity projections, risk assessments, status and ILS Certifications. Participate in ILS Certification forums. Provide ILS Certification trends, process health and metrics.

3.4.15 Develop, review, update, submit and maintain the configuration and logistics records in the Configuration Data Manager Database – Open Architecture (CDMD-OA that includes, but is not limited to, submission of work-files for Configuration Overhaul Planning (COP), Installation and Maintenance.

3.4.16 Conduct onsite post change package installation training for end item users.

3.4.17 Develop and maintain inventory control systems for government materials and test equipment.

3.4.18 Provide inspection, test, and calibration of government test equipment.

3.4.19 Develop, analyze, and maintain databases for cataloging, inventory, tracking, and transaction reporting of systems/equipment, materials, test equipment, drawings, parts lists, specifications, program plans, correspondence, OBRP provisioning levels, configuration accounting, and required technical support documentation for designated systems or equipment.

3.4.20 Perform pre-deployment Logistics Assistance Visits (LAV) to designated sites or operational platforms to ensure that all documents, Software, and Hardware represent the desired configuration, and that OBRPs and parts allowances reflect adequate support for that site or platform configuration.

3.4.21 Coordinate with and assist Naval Inventory Control Point (NAVICP), Naval Supply Weapons

Systems Support (NAVSUP WSS) in establishing spare parts support for COTS and MILSTRIP items. This may include acting as focal point for COTS spares procurement.

3.4.22 Develop, implement and maintain a Configuration Management Plan (CMP) and a Performance Based Logistic (PBL) Strategy for product support of weapon systems– Organic Support program.

3.4.23 The CMP and PBL program shall include developing an Integrated Logistics Support Plan (ILSP), Military Construction Logistics Requirements and Funding Plan (LRFP), Acquisition Strategy Plan (ASP), Test & Evaluation Master Plan (TEMP), Configuration Management (CM) Plan, Standardization Program Plan, Reliability & Maintainability (R&M) Program Plan, System Safety Program Plan, Logistic Support Analysis Plan (LSAP), Human Engineering Program Plan (HEPP), Quality Assurance (QA) Plan, Packaging, Handling, Storage, & Transportation (PHS&T) Plan, , Software System Security Plan (SSSP), Technical Manual Plan (TMP), Military Construction Equipment Facility Requirements (EFR) Plan, and Navy Training System Plan (NTSP), User's Logistics Support Summary (ULSS), and Field Change Implementation Plan(FCIP), Allowance Parts Lists (APL), Provisioning Technical Documentation (PTD), and Military Construction (MILCON) documentation support.

3.4.24 Develop, review, or revise Integrated Electronic Technical Manual and Interactive Multimedia

(IETM) Instruction in accordance with approved processes and standards.

3.4.25 Provide warehouse and Inventory Control Support and on-site services for equipment/systems.

The contractor shall establish and maintain warehousing and inventory controls, using government-approved computer-based application software programs for all program material and equipment.

4.0 DATA DELIVERABLES

Data deliverables shall be reviewed IAW “DON Policy on Digital Product/Technical Data, ASN RD&A memo of 23 OCT 2004”. Technical data and computer software delivery requirements will be specified through use of a Contract Data Requirements List, DD Form 1423, at the individual task order level. To ensure information compatibility, the contractor shall guarantee all deliverables (i.e., CDRLs), data, and any other required correspondence are provided in a format approved by the receiving government representative.

5.0 SECURITY REQUIREMENT

5.1 The work to be performed under this contract involves access to, and handling of, classified matter up to and including TOP SECRET/Sensitive Compartmented Information (SCI). Work performed at contractor facilities will be limited to SECRET. Contractor will require access to COMSEC and Secure Internet Protocol Router Network (SIPRNet)SIPRnet.

Contractor personnel assigned to this effort who require access to SCI data and spaces must possess a current SSBI with ICD 704 eligibility (which replaced DCID 6/4 eligibility).

Although there is no requirement for the contractor to access NATO information on the contact per Naval Intelligence Security Policy Directive 17-008 those contractors that are SCI cleared shall be North Atlantic Treaty Organization (NATO) read-on with an entry in the Joint Personnel Adjudication System.

Contractors performing tasks at the Top Secret or below level without SCI access shall only 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.

Applicable documents are as follows SECNAV Manual 5510.30 (Series), Department of Navy Personnel Security Program, SECNAV Manual 5510.36 (Series), Department of Navy Information Security Program, DOD 5200.01 Volumes 1 through 4 (Series), DOD Security Program, DOD 5220.22-M (Series), National Industrial Security Program Operating Manual (NISPOM), and OPNAVINST F3300.53C (Series), Navy Antiterrorism Program.

5.2 Operations Security: All work is to be performed in accordance with DoD and Navy Operations Security (OPSEC) requirements and in accordance with the OPSEC attachment to the DD254.

Applicable documents are as follows National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298, DOD 5205.02-M, DOD Operations Security (OPSEC) Program, OPNAVINST 3432.1A, DON Operations Security, and SPAWARINST 3432.1A, Operations Security Policy.

5.3 The contractor shall appoint a Security Officer who shall be responsible for who shall (1) be responsible for all security aspects of the work performed under this contract, (2) ensure compliance with the National Industry Security Program Operating Manual (DODINST 5220.22M), and (3) ensure compliance with any written instructions from the SSC Pacific Security Officer.

5.4 Contractor and Subcontractor personnel assigned work under this basic contract shall as a minimum be U.S. citizens and have a valid TOP SECRET or SECRET clearance as required in the individual task order.

5.5 If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to Commanding Officer, Attn: Foreign Travel Team, Space and Naval Warfare Systems Center Pacific, 53560 Hull Street, Building 27, 2nd Floor -Room 206, San Diego, CA 92152 for action. A Request for Foreign Travel form shall be submitted for each traveler, in advance of the travel, to initiate the release of a clearance message at least 30 days in advance of departure. Each Traveler must also submit a Personal Protection Plan and have a Level 1 Antiterrorism/Force Protection briefing within one year of departure and a country specific briefing within 90 days of departure. Anti-Terrorism/Force Protection (AT/FP) briefings are required for all personnel (Military, DOD Civilian, and contractor) per OPNAVINST F3300.53C. Contractor employees must receive the AT/FP briefing annually. The briefing is available at Joint Knowledge Online (JKO): https://jkodirect.jten.mil (prefix): course number:

US007; title: Level 1 Anti-terrorism Awareness Training, if experiencing problems accessing this website contact ssc_fortrav@navy.mil. Forward a copy of the training certificate to the previous email address or fax to (619) 553-6863. Sere 100.2 Level A code of conduct training is also required prior to Oconus travel for all personnel. Sere 100.2 Level A training can be mailto:ssc_fortrav@navy.mil accessed at http://jko.jfcom.mil (recommended), https://jkodirect.jten.mil/atlas2/faces/page/login/login.seam, recommended course: prefix: J3T:

course #: A-US1329, for civilian, military, and contractors. Personnel utilizing this site must have a CAC. A Sere 100.2 Level A training disk can be borrowed at the SSC Pacific Point Loma Office or Old Town Campus Office. Specialized training for specific locations, such as SOUTHCOM human rights, or U.S. forces Korea entry training, may also be required; SSC Pacific security personnel will inform you if there are additional training requirements. Finally, EUCOM has mandated that all personnel going on official travel to the EUCOM AOR must now register with the Smart Traveler Enrollment Program (STEP). When you sign up, you will automatically receive the most current information the State Department compiles about your destination country. You will also receive updates, including Travel Warnings and Travel Alerts. Sign up is one-time only, after you have established your STEP account, you can easily add official or personal travel to anywhere in the world, not just EUCOM.

http://travel.state.gov/content/passports/en/go/step.html

5.6 Cybersecurity

Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

5.7 Cyber IT and Cybersecurity Personnel

(i) The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

(ii) The contractor shall be responsible for identifying, tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF) and Cyber IT workforce personnel.

CSWF Report requirements are explained in a following paragraph. Although the minimum frequency of reporting is monthly, the task order can require additional updates at any time.

(iii) Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented below.

When a contractor requires logical access to a government IT system or resource (directly or indirectly), the required CAC will have a Public Key Infrastructure (PKI). A hardware solution and software (e.g., ActiveGold) is required to securely read the card via a personal computer.

Pursuant to DoDM 1000.13-M-V1, CAC PKI certificates will be associated with an official government issued e-mail address (e.g. .mil, .gov, .edu). Prior to receipt of a CAC with PKI, http://jko.jfcom.mil/ http://travel.state.gov/content/passports/en/go/step.html contractor personnel shall complete the mandatory Cybersecurity Awareness training and submit a signed System Authorization Access Request Navy (SAAR-N) form to the contract’s specified COR. Note: In order for personnel to maintain a CAC with PKI, each contractor employee shall complete annual cybersecurity training. The following guidance for training and form submittal is provided; however, contractors shall seek latest guidance from their appointed company Security Officer and the SPAWAR/SSC Atlantic/SSC Pacific Information Assurance Management (IAM) office:

• For annual DoD Cybersecurity/IA Awareness training, contractors shall use this site:

https://twms.nmci.navy.mil/. For those contractors requiring initial training and do not have a CAC, contact the SPAWAR/SSC Atlantic/SSC Pacific IAM office at phone number [insert applicable contract information] (843)218-6152 or e-mail questions to ssc_lant_iam_office.fcm@navy.mil for additional instructions. Training can be taken at the IAM office or online at http://iase.disa.mil/index2.html.

• For SAAR-N form, the contractor shall use OPNAV 5239/14 (Rev 9/2011). Contractors can obtain a form from the SPAWAR/SSC Atlantic/SSC Pacific IAM office at or from the website: https://navalforms.documentservices.dla.mil/. [insert applicable contract information] Digitally signed forms will be routed to the IAM office via encrypted e-mail to ssclant_it_secmtg@navy.mil.

(iv) Contractor personnel with privileged access will be required to acknowledge special responsibilities with a Privileged Access Agreement (PAA) IAW SECNAVINST 5239.20A.

5.8 Design, Integration, Configuration or Installation of Hardware and Software

The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official. Contractors that access Navy IT are also required to follow the provisions contained in DON CIO Memorandum: Acceptable Use of Department of the Navy Information Technology (IT) dtd 12 Feb 16. Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System (DADMS) and is Functional Area Manager (FAM) approved can be used as documented in para 4.2.2. Procurement and installation of software governed by DON Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON CIO Policy and DON ELAs awarded.

5.9 Cyber Security Workforce (CSWF) Report

The following Cybersecurity Workforce (CSWF) Report is required for all service contracts utilizing Cybersecurity (i.e., Information Assurance) personnel supporting the DoD Global Information Grid (GIG) per DoD Instruction 8500.01. DoD 8570.01-M and DFAR’s PGI 239.7102-3 have promulgated that contractor personnel shall have documented current cybersecurity certification status within their contract. The contractor shall develop, maintain, and submit a CSWF Report monthly or as applicable at the task order level. IAW clause DFARS 252.239-7001, if cybersecurity support is provided, the https://twms.nmci.navy.mil/ mailto:ssc_lant_iam_office.fcm@navy.mil http://iase.disa.mil/index2.html https://navalforms.documentservices.dla.mil/ mailto:ssclant_it_secmtg@navy.mil contractor shall provide a Cybersecurity Workforce (CSWF) list that identifies those individuals who are IA trained and certified. Task orders with IA functions will include a requirement for the contractor to report IA certification status and compliance. IA certification will be IAW current Space and Naval Warfare Systems Center Pacific CSWF Certification List. This support shall include generating a Contractor Roster of CSWF personnel.

5.10 Information Technology (IT) Services Requirements

Information Technology (IT) is defined as any equipment or interconnected system(s) or subsystem(s) of equipment, that is used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data of information by the agency. IT includes computers, ancillary equipment, peripherals, input, output, and storage devices necessary for security and surveillance. Electronic and Information technology (EIT) is IT that is used in the creation, conversion, or duplication of data or information. EIT includes:

telecommunication products, such as telephones; information kiosks; transaction machines; World Wide Web sites; multimedia (including videotapes); and office equipment, such as copiers and fax machines.

(1) IT General Requirements

When applicable, the contractor shall be responsible for the following:

• Ensure that no production systems are operational on any RDT&E network.

• Follow DoDI 8510.01 of 12 Mar 2014 when deploying, integrating, and implementing IT capabilities.

• Migrate all Navy Ashore production systems to the NMCI environment where available.

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

• Follow SECNAVINST 5239.3B of 17 June 2009 & DoDI 8510.01 of 12 Mar 2014 prior to integration and implementation of IT solutions or systems.

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

• Only perform work specified within the limitations of the contract/task order.

(2) Acquisition of Commercial Software Products, Hardware, and Related Services

Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

(i) DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program

Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA) dtd 22 Feb 12, contractors that are authorized to use Government supply sources per FAR 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the TO/contract level.

(ii) DoN Application and Database Management System (DADMS)

The contractor shall ensure that no Functional Area Manager (FAM) disapproved applications are integrated, installed or operational on Navy networks. The contractor shall ensure that all databases that use database management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting Navy applications and systems be registered in DoN Application and Database Management System (DADMS) and are FAM approved. All integrated, installed, or operational applications hosted on Navy networks must also be registered in DADMS and approved by the FAM. No operational systems or applications will be integrated, installed, or operational on the RDT&E network.

5.11 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 contract. 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, contract-related tracking).

5.12 IT Position Categories

Pursuant to DoDI 8500.01, DoD 8570.01-M, SECNAVINST 5510.30, SECNAV M-5239.2, and applicable to unclassified DoD information systems, a designator is assigned to certain individuals that indicates the level of IT access required to execute the responsibilities of the position based on the potential for an individual assigned to the position to adversely impact DoD missions or functions. As defined in DoD 5200.2-R, SECNAVINST 5510.30 and SECNAV M-5510.30, three basic DoN IT levels/Position categories exist:

• Tier 5/5R: IT-I (Privileged access)

• Tier 3/3R: IT-II (Limited Privileged, sensitive information)

• Tier 1/1R: IT-III (Non-Privileged, no sensitive information)

Note: The term IT Position is synonymous with the older term Automated Data Processing (ADP) Position (as used in DoD 5200.2-R, Appendix 10).

Investigative requirements for each category vary, depending on the role and whether the individual is a U.S. civilian contractor or a foreign national. The Contractor PM shall assist the Government Project Manager or COR in determining the appropriate IT Position Category assignment for all contractor personnel. All required Single-Scope Background Investigation (SSBI) or Tier 5, SSBI Periodic Reinvestigation (SSBI-PR) or Tier 5R, National Agency Check with Law and Credit (NACLC) or Tier 3/3R adjudication will be performed Pursuant to DoDI 8500.01 and SECNAVINST 5510.30. Requests for investigation of contractor personnel for fitness determinations or IT eligibility without classified access are submitted by SPAWAR/SSC Atlantic/SSC Pacific Security Office, processed by the OPM, and adjudicated by DOD CAF. IT Position Categories are determined based on the following criteria:

Tier 5/5R: IT-I Level (Privileged) - Positions in which the incumbent is responsible for the planning, direction, and implementation of a computer security program; major responsibility for the direction, planning and design of a computer system, including the hardware and software; or, can access a system during the operation or maintenance in such a way, and with a relatively high risk for causing grave damage, or realize a significant personal gain. Personnel whose duties meet the criteria for IT-I Position designation require a favorably adjudication of Single Scope Background Investigation (SSBI) or SSBI- PR or Tier 5/5R. The SSBI or SSBI-PR or Tier 5/5R is updated a minimum of every 5 years.

Assignment to designated IT-I positions requires U.S. citizenship unless a waiver request is approved by

CNO.

Tier 3/3R: IT-II Level (Limited Privileged) - Positions in which the incumbent is responsible for the-direction, planning, design, operation, or maintenance of a computer system, and whose work is technically reviewed by a higher authority at the IT-II Position level to insure the integrity of the system.

Personnel whose duties meet the criteria for an IT-II Position require a favorably adjudication of a Position of Trust National Agency Check with Law and Credit (PT/NACLC) or Tier 3/3R. Assignment to designated IT-II positions requires U.S. citizenship unless a waiver request is approved by CNO.

Tier 1/1R: IT-III Level (Non-privileged) - All other positions involved in computer activities.

Incumbent in this position has non-privileged access to one or more DoD information systems/applications or database to which they are authorized access. Personnel whose duties meet the criteria for an IT-III Position designation require a favorably adjudication of a Position of Trust National Agency Check with Written Inquiries (PT/NACI) or Tier 1/1R.

6.0 Government Furnished Documents

Technical documents identified in the SOW will be made available to the contractor by SSC Pacific. All documents furnished during the life of the contract remain the property of the government, and if removed from SSC SD shall be returned upon completion of the tasking unless otherwise specified in the individual task order.

6.1 Government Furnished Material/Equipment (GFM/GFE)

A listing of Government Furnished Material (GFM) or Government Furnished Equipment (GFE will be specific in each Task Order. All GFM/GFE furnished during the life of the contract remains the property of the government, and if removed from SSC Pacific shall be returned upon completion of the tasking unless otherwise specified in the individual task order.

6.2 Government Furnished Facilities

6.2.1 The contractor will be responsible for establishing and maintaining the contractor support facility. However, tasks under this contract may require specialized facilities to adequately perform them. When such facilities already exists and it is in the governments interest not to require what may be a costly duplication of resources; the government may provide the contractor access to these facilities for use in this tasking.

6.2.2 When Government Furnished Facilities are to be provided, the facilities will be identified in the individual Task Orders issued against this basic contract.

6.2.3 Contractor employees anticipated to be working on-site at SSC Pacific lab environment will be provided a common desk, telephone and computer for use as required. Individuals assigned outside of a lab environment will be provided a desk and a personal computer for work use. A common telephone will be located in the space for use as required. If additional contractor personnel are required to work onsite (full time) at SSC Pacific, each individual will be provided with the necessary equipment required in support of their individual tasking.

7.0 METHOD OF SURVEILLANCE

7.1 The Government will monitor and assess the contractor(s)’s performance against the Acceptable

Quality Level in accordance with the clause at FAR 52.246-5 entitled “Inspection of Services – Cost Reimbursement.” The delivered products will be subjected to Government test and evaluation for performance and accuracy.

7.2 The Government will review the requirements, design, system functionality and performance to determine whether they are appropriate, comprehensive and in sufficient detail to successfully implement the target system. The Government will review requirements analysis reports, system test reports, inspection reports, monthly status reports, financial reports, training evaluations, help desk logs, system error logs, user comments, and other sources to determine if Government requirements and expectations are being met. The Government will monitor the contractor’s responsiveness. The contractor will be required to correct deficiencies.

8.0 MANAGEMENT OF COUNTERFEIT PARTS

Due to the risk in information and communication technology (ICT) supply chains, the Contractor shall employ practices that assure integrity, security, and quality of the products.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .