TUBA SMPS SOW DRAFT 6-3-24.pdf

STATEMENT OF WORK

The tasking under this Statement of Work (SOW) falls under Product Service Code R425.

Engineering Services for Signature Measurement Programs System Development and Operations in support of the Naval Surface Warfare Center Carderock Division

(NSWCCD)

1.0 INTRODUCTION

The mission of the Signatures Department of the NSWCCD is to assure that surface ships, submarines, and other Navy vehicles have signature characteristics, which will ensure their operational superiority over other Navies. In support of the mission, Codes 70 conducts research and development (R&D) in the fields of underwater acoustic and non-acoustic signature identification, control, and reduction. It supports the Fleet in establishing signature requirements and oversees fundamental research and applied research in hydro-acoustics, structural acoustics, mechanical vibrations, target strength reduction, electromagnetics, Radar Cross Section (RCS) reduction, infrared reduction, electro-optical (EO) detection, and advanced signal processing. As a result of this work, recommendations are made for the reduction of the signatures of existing classes of ships and submarines, and guidance is provided on how to incorporate advanced signature identification and control technologies into the design and construction of new vessels.

Code 70 conducts full-scale and model-scale acoustic, vibration, radar cross section, electromagnetic, infrared, and EO measurements on ships and submarines. To accomplish the tasks, new techniques, data acquisition systems, tracking systems, and processing methodologies are developed for measuring the characteristics of signatures, including radiated noise, target strength, sonar self-noise, RCS, infrared (IR), and EO. From this work, operational and maintenance guidance is provided to the Fleet.

2.0 OVERVIEW

The scope of the effort discussed herein, shall require the contractor to provide scientific, engineering, technical management, and associated fabrication support services for NSWCCD Codes 70 Navy and Ship Signatures Programs. Contractor analytical and technical efforts shall be required in all stages of Navy and Marine signature programs from concept formulation, engineering analysis and development, operational test and evaluation, through implementation, upgrade, life cycle support, and system retirement. Specific program support shall include:

2.1 TUBA Program support in the areas of Fleet Systems Operations, Shipboard Installation, Acoustic Sensor Groom and Calibration, Data Acquisition and Analysis, In Service Engineering Agent (ISEA) duties, System Development, System Engineering Management, Test and Evaluation (T&E), Signal Processing, Mainframe Sonar and Sensor Certification, Cyber Information Technology (IT) and Information Assurance (IA).

2.2 Submarine and Surface Ship Signature Trials Programs support in the areas of Trials Planning and Execution, Equipment and Transducer Development and Maintenance, Shipboard Installation, Temporary Alterations/Operational Alterations (TEMPALT/OPALT) and Shipboard Alteration (SHIPALT) Development, and related Systems Support, Logistics, Operations, T&E, and Technology Development.

2.3 Vibration Monitoring Program support in the areas In Service Engineering Agent (ISEA) duties, TEMPALT/OPALT Shipboard Alteration Development, OPALT Integrated Logistics Support (ILS), Shipboard Installation, Vibration Monitoring System Development and maintenance, System Engineering Management, T&E, Cyber IT and IA; and other existing or emerging Signature Measurement projects.

2.4 Acoustic Intelligence (ACINT) Reconstruction Measurement Analysis and Data Archival (ARMADA) program support in the areas of advanced signal processing and software design, information system design and implementation, Knowledge Management System (KMS) design and implementation, database development, and Cyber IT and IA.

3.0 IMPLEMENTATION

The contractor shall provide the personnel, material, expertise, and facilities necessary to accomplish the task assignments within the task areas described in this Statement of Work (SOW). These efforts will be implemented through the issuance of written Technical Instructions (TIs) to the contractor as needed through the Contracting Officer’s Representative (COR). The COR will provide the classified information and technical data necessary for task performance and will provide information on ship schedules for those tasks requiring visits to fleet units. TIs will identify any Government Furnished Information (GFI) and/or Government Furnished Property (GFP) necessary for task performance.

3.1 The contractor shall perform Cyber IT and IA tasking in accordance with DoD Directive (DoDD) 8140.01 “Cyberspace Workforce Management” dated 5 October 2020, and DoD Manual (DoDM) 8140.03 “Cyberspace Workforce Qualification and Management Program” dated 15 February 2023.

3.2 The contractor shall perform SHIPALT installations in accordance with Naval Sea Systems Command (NAVSEA) TS9090-310G “Alteration to Ships Accomplished by Alteration Installations Teams” dated 12 February 2015.

4.0 SCOPE OF WORK

The contractor shall perform specific tasks within the following areas:

4.1 FLEET SYSTEMS OPERATIONAL SUPPORT

The contractor shall perform core infrastructure and direct shipboard support activities for Fleet Systems, including TUBA Program support. Technical efforts cover pre-installation support, system documentation, fleet training, shipboard technical assistance, and test equipment support.

The contractor shall develop and validate groom procedures, groom data collection system, and groom report software. The contractor shall perform calibration and data gathering procedure development and validation. The contractor shall perform on-site system/sonar groom support, measurements, analyses, and verifications in support of system and platform certification. The contractor shall perform Data Acquisition, Reduction and Analysis support by developing collection and reduction procedures and techniques, testing and validating procedures, and reviewing data reduction and analysis results. Typical tasks and deliverables shall include the following:

4.1.1 Installation planning, operational logistics support, asset planning, and operational metrics analysis. Conduct Pre-Installation conference support and shipcheck planning. On-site system problem analysis, troubleshooting, and corrective maintenance. Conduct TUBA website and database support, operational support document updates, metrics reporting, and arrangement.

4.1.2 Groom, calibration, and certification procedure development, documentation and verification. Groom and calibration problem analysis and corrective action. Perform specification development and validation. System test and performance evaluation criteria development. Design, fabrication, calibration, and validation of groom test equipment.

4.1.3 Automated Groom Data Collection System hardware and software, at-sea data collection monitoring software, and report generation software development, integration, and testing.

4.1.4 System grooming and calibration monitoring. Groom and calibration technical support. Submarine Surveillance Equipment Program (SSEP) groom and calibration personnel training. Groom support material tracking, configuration management (CM), maintenance, and repair.

4.1.5 System Operation and Maintenance (O&M) procedures, manuals, and support documentation development, including development of documentation in Interactive Electronic Technical Manual (IETM) format. Fleet and Submarine SSEP personnel training.

System training material development and fleet personnel training. Training manuals, operator guides, and training material development. System O&M Computer Based Training (CBT) development and upgrades.

4.1.6 Operational Data Gathering Procedure development, documentation, and verification.

4.1.7 Sonar calibration and trial support. Onboard Technical Trial Director support.

Onboard sound vessel support, sound equipment operations, and underwater communication system support. Sound equipment maintenance, upgrade, and sustainment.

4.1.8 TUBA data reduction procedures, reporting requirements, techniques and equipment capability analysis. Data acquisition and reduction problem analysis and resolution. Hardware, software, and firmware analysis, evaluation, and specification development. Data reduction report review, problem analysis, and corrective action recommendations development.

4.2 SYSTEM INSTALLATION

The contractor shall develop procedures to install fleet systems, develop drawing packages to document installation configurations, and perform system installations. Typical system installation support and deliverables shall include the following:

4.2.1 Installation planning, requirements analysis and support documentation development including Memorandum of Agreement (MOA) preparation in accordance with local installation command requirements. Support Regional Maintenance and Modernization Coordination Office (RMMCO) approval process and check-in / check-out requirements.

4.2.2 Perform System Ship Alteration (SHIPALT, OPALT, TEMPALT, Alteration and Improvement (A&I), Engineering Change (EC) Instruction (ECI), and Field Change (FC)) installation documentation development and validation, in accordance with NAVSEAINST 4720.14, Temporary Alterations to Fleet Submarines; NAVSEA S90970-AA-MME- 010/SSN/SSBN, Technical Requirements Manual For Temporary Submarine Alterations;

and/or NAVSEA SL720-AA-MAN-030, Navy Modernization Process Management and Operation Manual (NMP MOM). The contractor shall perform installations in various locations including: US and foreign naval bases, shipyards, and controlled industrial areas;

and the contractor shall perform installations in all required spaces, including nuclear engineering spaces, engine room and other restricted spaces, tanks, and compartments inboard or outboard. The contractor shall support installation schedules required to meet submarine schedule deadlines or ship movements, which includes working third shift and weekends when required. The contractor access to required spaces shall not present constraints that significantly impact other ongoing shipboard work, crew operations, or prohibit the ability to meet installation schedules and cost constraints.

4.2.3 Prepare Technical Data Packages (TDPs) to support equipment installation in accordance with Naval Sea Systems Command (NAVSEA) TS9090-310G “Alteration to Ships Accomplished by Alteration Installations Teams”.

4.2.4 Alteration Installation Team (AIT) certified SHIPALT, OPALT, TEMPALT, ECI, A&I, and FC installations, checkout, and performance validation. The AIT shall be outfitted with all required hand tools, Personal Protective Equipment (PPE), General Purpose Electronic Test Equipment (GPETE), special purpose electronic test equipment, Installation and Check-Out (I&C) spares, special alignment equipment, etc., required to accomplish the alteration/system checkout. For those skills that require specific training, qualification and/or certification (e.g. welding, electrical connector assembly, Submarine Safety (SUBSAFE), Signal Security (SIGSEC), Telecommunications Electronics Material Protected from Emanating Spurious Transmissions (TEMPEST), Passive Countermeasure Systems (PCMS) installation, Level 1, fiber optic cable/equipment installation, etc.), AIT members performing these functions shall be fully qualified and/or certified.

4.2.5 Conduct ship checks and pre-installation baseline testing and reporting of ship check and baseline testing results.

4.2.6 Development of Installation and Checkout (I&C) procedures.

4.2.7 Fabrication of fixtures and foundations for installation, removal, and relocation of ships equipment.

4.2.8 System installation kit assembly, integration, staging, and packaging.

4.2.9 Installation problem analysis, recommendations development, and reporting of post-installation checkout results.

4.3 IN-SERVICE ENGINEERING AGENT (ISEA) SUPPORT

The contractor shall perform ISEA and logistic support in order to maintain operability, preparedness, and availability of physical system assets for installation and additional fleet support efforts. The contractor shall maintain critical configuration management information, analyze system reliability data, and perform ILS efforts. The contractor shall perform updates to life-cycle documentation. The contractor shall perform installation planning analysis to ensure fleet installations and fleet-support units are adequate to accomplish mission goals. The contractor shall perform supply and repair support for fleet systems. Typical ISEA support tasks and deliverables shall include:

4.3.1 Development and updating of Configuration Management (CM) plans. Logistics support documentation development and maintenance, such as Configuration Baseline Status Reports (CBSR), ISEA Management Plans, and Commercial Off the Shelf (COTS) Obsolescence surveys.

4.3.2 Logistics database development and maintenance, trouble report management, fleet problem on-site analysis, troubleshooting, and corrective maintenance. Logistics support requirements analysis and recommendations development. CM and inventory tracking database support.

4.3.3 Planned Maintenance System (PMS), Maintenance Index Page (MIP), and Maintenance Requirements Card (MRC) requirements analysis, procedures development, and documentation verification and Reliability Centered Maintenance (RCM) analysis.

4.3.4 Perform inventory tracking, system refurbishment, upgrade, repair, and preparation. Conduct test equipment maintenance, calibration, CM, and repair. Conduct system packaging, shipping, and tracking support.

4.3.5 Supply support for repair and replenishment of system components and onboard repair parts. Equipment configuration planning and maintenance. System obsolescence component replacement analysis, planning, design, and development support. Supply and logistics support for the shipping, receiving and transportation of systems, components, and repair parts.

4.3.6 Perform media management functions, including provisioning, configuration, and verification of storage media. Provide media qualification tracking, logistics support, packaging, shipping, and stowage. Support Classified media handling, tracking, and reporting in Base Inventory Tracking System (BITS).

4.3.7 EC and FC kit support material fabrication and documentation. EC and FC kit assembly, packaging, documentation, verification, and installation.

4.3.8 Conduct hydrophone and transducer calibration, test, refurbishment, repair, and inventory tracking. Conduct DT-369 Calibrated Reference Hydrophone (CRH) engineering and logistic support. Fabricate, repair, and/or refurbish hydrophone mounts and brackets.

4.4 SYSTEMS ENGINEERING, DEVELOPMENT, TEST, AND EVALUATION

The contractor shall perform engineering analysis, design, and validation efforts that apply to TUBA systems. The contractor shall perform interface testing, EC and EC Proposal (ECP) validation, and FC and FC Proposal (FCP) validation. The contractor shall develop, test, and document accomplishment of functional requirements and performance. Typical tasks and deliverables shall include:

4.4.1 TUBA system, sensor, and sonar interface specification, design, testing, and performance analysis. Sensor acoustical, electrical, and support data signal path analysis.

Acoustic data collection system functional requirements, detailed design development, and analysis. System and subsystem specification development and analysis. Playback and Analysis system development, support, upgrades, and sustainment.

4.4.2 Analysis of sonar system and sensor upgrades for TUBA impact. Impact analysis of operational requirements on system design.

4.4.3 System engineering development, T&E and lifecycle support development.

System enhancement, requirement, design, code, and test documentation analysis.

4.4.4 System software design, development, testing, validation, and software modification. EC and FC upgrade preparation and validation. Temporary EC (TEC) and Temporary FC (TFC) development, testing, installation, and validation.

4.4.5 ECP, EC, FCP and FC analysis, development, prototyping, T&E, and documentation. Hardware change development, installation, test and certification, and related documentation development. Independent Validation and Verification (IV&V) for enhancements to system hardware or software resulting from ECs or FCs.

4.4.6 Prototype and production system T&E. Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) plans, test procedures, and test reports for system development. T&E test fixture, harness and related component development, fabrication, installation, and modification. PCAs and FCAs to ensure compliance with development standards and specifications.

4.4.7 CM/Quality Assurance (QA) plans and procedures analysis for compliance with development standards. System safety, reliability, and maintainability analysis.

4.4.8 Execute baseline engineering support services and Technical Direction Agent (TDA) support functions. Collaborate with the technical community on sonar system interfaces, specifications, and functions. Conduct system performance specification determinations.

4.4.9 Cyber Security IT/IA related support functions. Support Security Technical Implementation Guides (STIGs) configuration efforts, scans, remediation, and reporting.

Accreditation planning, management, and Certification and Accreditation (C&A) documentation support.

4.4.10 Design working groups, formal Preliminary Design Review (PDR), Critical Design Review (CDR), and Test Readiness Review (TRR) meeting attendance to provide problem analysis and corrective action recommendations.

4.4.11 Participation in unit and integration testing, and review of the associated informal documentation of this testing. System development process review to report issues and problems and develop recommendations for resolution. Hardware design change review for engineering analysis to validate changes that fulfill system requirement.

4.4.12 Hardware and software test plans and procedures development in support of analysis and review for applicability to development standards. Participate in hardware component and system testing and provide engineering analysis and evaluation for compliance with test documentation. Provide independent testing of hardware and/or software modifications for compliance with specifications.

4.4.13 Unmanned Undersea Vehicle (UUV) payload development, upgrade, installation, test, evaluation, and operational transition support.

4.4.14 Support the development, testing, performance validation and evaluation, installation, upgrade, and operation of alternative sensor and system applications.

4.5 MAINFRAME SONAR AND SENSOR CERTIFICATION SUPPORT

The contractor shall perform research and engineering to support TUBA certification of submarine sensors, data paths, collection systems, and processing systems. The contractor shall perform systems engineering, analysis, and evaluation efforts to demonstrate TUBA measurement capabilities. The contractor shall evaluate developing sensor, signal transmission, and signal processing technologies that may improve signature measurement and analysis systems. The contractor shall perform engineering and testing support of certification of new sensors and systems. Typical mainframe sonar certification support and deliverables shall include:

4.5.1 Sonar system and sensor interface test support.

4.5.2 Verification of Acoustic Rapid COTS Insertion (A-RCI) upgrades for Technology Insertion (TI), and Advanced Processor Build (APB), and other updates pertaining to acoustic and/or support data signal paths and/or signature data outputs. Sonar Interface Requirements Specification (IRS) and Interface Design Document (IDD) development, review, comment, update, and verification support.

4.5.3 Sensor, sonar, and system certification requirements definition, certification plan, test plan, and certification report development. Towed and Hull Mounted sensor certification support, performance assessment, testing, and reporting. Full-scale R&D trial support, measurement methodology testing, and sensor self-noise assessments. TUBA Generic Certification support.

4.5.4 Measurement R&D methodology and feasibility reports. Measurement technology R&D, including scientific, statistical, mathematical and data science methods, equipment, processing, visualization, and toolsets.

4.5.5 Sensor and array performance, accuracy, and health monitoring modeling and research. Sensor performance and technical parameter reports. System functional requirements and design review documentation.

4.6 SIGNATURE TRIALS SUPPORT

4.6.1 Ship Signature Trials, TUBA certification, Sonar Calibration (SOCAL), Technical Evaluation (TECHEVAL), Operational Evaluation (OPEVAL), and dockside and full-scale evaluation trial hardware configuration, installation, operation, and removal. Off-

Hull (interface) Testing, Sea Trials Readiness Acceptance Testing (STRAT), Weapons System Accuracy Trials (WSAT), installation planning, requirements definition for data acquisition, data analysis, and post event data reduction.

4.6.2 Technical trial support and on-line monitoring system operator support.

4.6.3 Support vessel preparation and at-sea trial support.

4.6.4 Dockside calibration support including software development, system setup and operations, CM, and hardware maintenance and logistics.

4.6.5 Trial equipment installation control drawing and TEMPALT documentation development and verification. Objective Quality Evidence (OQE) development in support of NAVSEA S9070-AA-MME-010/SSN/SSBN, Technical Requirements Manual for Temporary Submarine Alterations.

4.6.6 T&E facility support, test support equipment definition, preparation, installation, and procedure development for operation and maintenance.

4.6.7 Trial/test plans and procedures analysis, preparation, and development.

4.6.8 Trial equipment and systems design, development, CM, and pre-test to validate T&E procedures.

4.6.9 Trial data acquisition, validation, reduction, analysis, and resolution.

4.6.10 Data acquisition, reduction and analysis approaches, techniques, and concept development and documentation

4.6.11 Trial equipment ILS, maintenance, and tracking.

4.7 VIBRATION MONITORING SUPPORT

4.7.1 Provide technical engineering recommendations toward the improvement of existing vibration monitoring systems, future vibration monitoring systems, and other systems associated with Vibration Monitoring Development.

4.7.2 Support the design of vibration monitoring system hardware to include, electrical design, cable management, and power distribution. Support the various vibration monitoring system requirements, including Grade B evaluation and certification, Electromagnetic Interference (EMI), shipboard volume storage and locker replacement, and low smoke cabling requirements.

4.7.3 Provide technical support with system interfaces to shipboard power systems, including 440V power distribution, receptacles, and panels.

4.7.4 Support structural vibration related system design, development, fabrication, installation and removal, maintenance, ILS, material tracking. Support TEMPALT/OPALT development in support of existing and emergent vibration related systems.

4.8 ACINT RECONSTRUCTION MEASUREMENT ANALYSIS AND DATA

ARCHIVAL (ARMADA) AND PROCESSING, EXPLOITATION, AND

DISSEMINATION (PED)

4.8.1 The Contractor shall design, develop, test, implement, update, and maintain databases, data repositories, or other data archives to support signatures-related and other technology programs and systems, including acoustical, RCS, IR, EO, and other signature databases. Support shall include developing and implementing data storage and retrieval concepts. In addition, the Contractor shall design, develop, test, implement, update, and maintain information systems and websites to support signatures-related and other technology programs and systems. This support shall include developing and updating information systems and databases for development, maintenance, and analysis of program information (e.g., asset and equipment status, reliability, parts and provisioning, field action requirements, engineering drawings, action item tracking, and other required management systems).

The tasking defined in Task areas 4.8.2 thru 4.8.10 will require access to Top Secret Sensitive Comparted Information.

4.8.2 Design, develop, and implement common data formats and interfaces between systems and software supporting the Office of Naval Intelligence (ONI)’s PED system.

Assess deployment of ARMADA and PED systems, including legacy toolsets.

4.8.3 Design, develop, and implement Fleet Data Reduction Center (DRC) system modifications, improvements and new design implementation and demonstration.

4.8.4 Develop system architecture that efficiently and effectively supports PED processes at ONI and at remote sites (DRCs, CTFs) to include data acquisition, processing (qualitative and quantitative), curation, automation, and trend analysis. Assess data flow within the system, across networks, nodes, workstations, processing stacks, and security domains. Support ingestion of data from the following sources: submarine (TUBA), unattended sensors, Maritime Patrol and Reconnaissance Aircraft (MPRA) employed sensors, autonomous vehicle sensors, surface ship sensors, and other non-submarine sources.

4.8.5 Design, develop, and support the following: TUBA Processing System (TPS) Compute Cluster development, ACINT Lab Network and Architecture Design Cross Domain System (CDS) updomain capability, ACINT Knowledge Management System (AKMS) database prototype development, Artificial Intelligence (AI)/Modeling Language (ML) evaluation, tools assessment and implementation.

4.8.6 Develop, apply, and maintain advanced signal processing tools, algorithms, and playback systems. Assess new methodologies, including measurement techniques, equipment, procedures, and supporting sensor principles. The contractor shall provide engineering support for Mission View, TPS Enhancements, the Qualitative Analysis and Assurance System (QAAS) Trainer and Playback System Enhancements, ACINT 21 Updates and Enhancements, QAAS Three-Dimensional Signal Processing (3DSP) Enhancements, Tracker (TRK) Implementation and Enhancements, Advanced Localization Trackers, Track Automation and Energy Detection Tools.

4.8.7 Design and develop Information Systems (ISs) including system architecture and design, testing, implementation, updates, and maintenance of the ISs to meet lifecycle needs of ARMADA and PED signature analysis systems and other related signature analysis systems. IS designs must address government defined computational, storage, networking, logistics and support requirement.

4.8.8 Design, develop (including system architecture and design), test, implement, update, and maintain Knowledge Management Systems (KMSs) to meet lifecycle requirements of ARMADA and PED systems and other related signature analysis systems.

Contractor KMS designs shall include creating, uploading, indexing, and serving ARMADA and other related signature analysis systems data products and analysis outputs.

4.8.9 Design, develop (including architecture and design), test, implement, update, and maintain database(s) to meet the requirements of ARMADA. The database(s) shall include storage and access of ACINT and other signature data, application programming interfaces for ARMADA and PED software, and interfaces with the KMS. The database and data curation tools shall support comparisons, trending, recollection, and data exchange.

4.8.10 Design, develop, test, implement, integrate, maintain, and upgrade acoustic signal processing software to meet the collection, technical, computational, analytical, and processing requirements of ARMADA and PED. The design and development shall include research and implementation of new and existing algorithms on state-of-the-art hardware and software frameworks.

4.9 TECHNOLOGY DEVELOPMENT

4.9.1 Provide technical engineering support for the modification and maintenance of an overall NSWCCD Science and Technology (S&T) Strategy/Roadmaps. Prepare and facilitate strategic planning meetings and workshops. Facilitate technical strategic planning sessions directed at assessment and prioritization of future technologies and concepts. Apply strategic planning processes using structured decision analysis and decision conferencing methods. Assemble results from each strategic planning session into a draft report.

4.9.2 Conduct technical studies and analyses on ship systems science and technology and ship system engineering topics. Topics shall be selected by NSWCCD from a range of advanced hull, mechanical and electrical systems, signatures measurement and management technologies and concepts under development at NSWCCD for future ships and ship systems. The studies and analyses shall include review and revision of ship system materials and fabrication procedures, analysis of offshore Navy and marine industry equipment casualties, submarine structural systems design and analyses, naval architecture, advanced signature measurement, and a range of advanced ship systems logistics issues.

4.10 PROGRAM MANAGEMENT

The contractor shall provide technical project management support in accordance with the technical tasking outlined in the SOW.

4.10.1 The contractor shall provide the management necessary for the efficient and effective administration and control of work performed under the Task Order. The contractor shall manage tasks to meet cost, schedule, and performance of each Technical Instruction (TI). This tasking shall include standard, urgent, complex, or other support situations in fulfillment of customer needs.

4.10.2 The contractor shall provide scheduling, tracking, reviewing, and estimating of projects assigned.

4.10.3 The contractor shall resource material, facilities, personnel, and services for assigned projects.

4.10.4 The contractor shall schedule, prioritize, and track all projects and report any discrepancies or conflicts to the designated Government representative for resolution.

4.10.5 The Program Manager is responsible for the delivery of the Contracting Officer’s Management Report DI-MGMT-81864 and the Program Management Review (PMR) DI- MGMT-81861A, which will be applicable to all tasking across the SOW.

4.10.5.1 Task Order Kick-Off Meeting - The Contractor shall attend a Post-Award Conference (PAC) within 15 days after Task Order award either by phone or NSWCCD.

Specific time and date for PAC shall be coordinated with the Contracting Officer’s Representative (COR). The purpose of the PAC is for the contractor to review and demonstrate management procedures, provide progress assessments, review technical and other specialty area status, establish schedule dates for near term critical meetings/actions, and present management, key personnel, and program ramp-up.

4.10.5.2 Quarterly Program Management Review (PMR) Meetings - The Contractor shall conduct PMRs at Government or contractor facilities or by other means (i.e. teleconference) as agreed to by the Contracting Officer. Reviews requiring demonstration and/or examination of equipment shall be conducted at the contractor’s facility. All such reviews shall be included in the program schedule and may be held concurrently with the Government’s approval. The following topics shall be addressed at each PMR:

Review of pertinent technical, schedule, and cost aspects of each authorized technical effort under this Task Order, including an overview of the work to be accomplished in the next month; current and anticipated technical and implementation problems; review of each subcontractor’s technical progress on all assigned tasks; and substantiation of assumptions made and methodologies used in arriving at recommendations or conclusions.

4.10.5.3 The Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance (PoP). Action item documentation, assignment of responsibility for completion, and due dates shall be determined prior to adjournment of all reviews.

5.0 PHASE-IN AND PHASE-OUT

A 60-day transition period shall be scheduled upon award (phase-in) and the 60-day period immediately prior to contract end date (phase-out) to allow for orderly TO transition. In order to maximize the effectiveness of the transition process, an initial meeting between the PCO (or its delegated representative) and Contract Managers for both contractors shall be held to address phase-in and phase-out requirements and responsibilities not later than five days into the phase in/phase out period, and subsequent meetings will be held as determined by the PCO but not less than weekly thereafter.

5.1 Phase-In. During the phase in period, incoming contractor personnel will be permitted to observe current operations of the outgoing contractor. The incoming contractor shall ensure that its phase-in operations do not hinder or interfere with normal operations of the phase-out contractor, and that maximum effort is made to avoid loss of productivity. By the end of the phase-in period, the contractor shall have assumed full responsibility for all work requirements under the TO. The incoming contractor shall be 100 percent staffed by no later than 60 days after TO award.

5.2 Phase-Out. A 60-day transition period shall be scheduled immediately prior to the end of this TO, including options. If the contractor is not awarded the subsequent TO for these services, the contractor shall permit his successor to observe and become familiar with any and all operations under this contract. The contractor shall remain responsible and liable for the completion of all requirements of this contract that begin on or before the final day of this contract (i.e. no drop off in execution near the end of the POP). The contractor shall not defer any requirements for the purpose of avoiding responsibility and transferring such responsibility to the successor contractor or the Government. The contractor shall fully cooperate with the successor contractor and the Government, and shall not interfere with their work or duties. The contractor shall provide the PCO with a phase out plan not later than 60 days prior to the contract end date.

This plan shall detail disposition action for all furnishings, equipment, and documentation

(CDRL TBD).

6.0 GOVERNMENT FURNISHED PROPERTY (GFP)

Government Furnished Property (GFP). The list of GFP provided under this TO is provided as an attachment in Section J. Additional GFP may be provided when there is a requirement for special or specific Government material/equipment in the performance of specific tasking. The contractor shall provide a GFP baseline report quarterly (CDRL TBD).

Transfer of GFP. All GFP provided the Contractor is the property of the U.S. Government and shall not be transferred to any individual or agency, public or private, without the express written approval of the PCO. GFP shall only be used to execute requirements under this Task Order. All GFP shall be returned to the Government at the conclusion of the Task Order unless otherwise directed by the COR.

7.0 GOVERNMENT FURNISHED INFORMATION (GFI)

GF Information (GFI) includes technical documents, drawings, and electronic media files or data.

GFI shall be handled in accordance with its classification markings. Copies of all physical and electronic GFI shall be returned to the Government at the completion of the associated task or at the end of the Task Order.

8.0 SECURITY

The contractor shall require access to Government facilities and classified information as specified in the DD Form 254 Department of Defense Contract Security Classification Specification, during the performance of this Task Order. All key and non-key contractor personnel shall hold or be capable of obtaining a clearance commensurate to the Government facility or classification identified in the DD Form 254 and Personnel Requirements, prior to being granted access to the facility or classified information. All services performed under this contract require a minimum of a SECRET clearance.

9.0 PLACE OF PERFORMANCE

Work performed under this Task Order is anticipated to be performed both on-site at NSWCCD (West Bethesda, MD and Olney, MD) and at the contractor facilities. The contractor may also be required to support periodic on-site integration at other sites where fleet assets are located as outlined under travel requirements in 10.0.

For contractors required to provide on-site support at NSWCCD, the Government will provide the contractor with proper identification, a workspace and access to the Navy networks required for task execution.

9.1 GOVERNMENT FACILITIES

Several NSWCCD facilities including Buildings 31, 15, and 3 are secure and house secure workspaces, workstations, and networks. The secure facilities workspaces, workstations, and networks will be made available to contractor personnel as specified within individual TIs.

9.2 NETWORKED SYSTEMS

As required, the Government will also ensure that Navy network systems and systems used to develop software and interfaces in support of the SOW are available for use/connection by the contractor located at NSWCCD as identified in the TIs. Systems may include:

Unclassified Navy/Marine Corps Intranet (NMCI) or follow-on network unclassified computers (laptops or desktops) for use at NSWCCD by on-site personnel.

Classified Secret Internet Protocol Router Network (SIPRNET) or follow-on network classified computers (laptops or desktops) for use at NSWCCD by on-site personnel.

Unclassified Research, Development, Testing, & Evaluation (RDT&E) and classified (RDT&E) development systems for on-site personnel for data analysis and system engineering on-site at NSWCCD (Lab 118).

10.0 TRAVEL

Contractor personnel may be required to travel to Government facilities located in the Continental United States (CONUS) and out of the Continental United States (OCONUS).

All required travel under this Task Order shall be requested of, or authorized by, the COR in writing to include electronic mail, prior to the date the travel is required and shall include the appropriate order number; the number of persons traveling; the number of days for the trip; the reason for the travel; and indicate any anticipated high or unusual costs.

Travel requirements (e.g. location, frequency, number of travels) and funds authorized for travel use only, will be specified in the TI and provided by the COR. All travel funds authorized under this Task Order shall directly relate to efforts required for completion of required tasks specified under the SOW.

The contractor shall submit all trip reports within five working days from the last day of travel, or submit the trip report(s) with the Monthly Status Report, identified at section 9.0, in the month the trip(s) occurred.

The contractor shall ensure that travel costs are in accordance with Federal Acquisition Regulation (FAR)31.205-46 Travel Costs and adhere to the Joint Travel Regulations at http://www.defensetravel.dod.mil/site/travelreg.cfm.

The estimated travel over the potential five (5) year period of performance (inclusive of options) may include the following locations: Groton, CT; Norfolk, VA; Kings Bay, GA; Bangor, WA;

Seattle, WA; San Diego, CA; Pearl Harbor, HI; Fort Lauderdale, FL; Key West, FL; Dahlgren, VA; Dam Neck, VA; Boston, MA; Newport, RI; Patuxent, MD; Keyport, WA; Dahlgren VA;

Orlando, FL; Manassas, VA; Yokosuka, Japan; Rota, Spain; Bethesda, MD; Andros Island, Bahamas; Perth, AUS; Faslane, UK; and Guam.

11.0 CONTRACTOR FACILITY

The contractor must have facilities within 35 miles of NSWCCD which meet the safeguarding requirements specified by DD Form 254 and sufficient space to meet the off-site labor personnel split provided by the Government.

12.0 INFORMATION SECURITY AND COMPUTER SYSTEM USAGE

In accordance with U.S. Navy policy, any personnel, including the Contractor, who utilizes DoD-owned systems, shall assume responsibility for adherence to restrictions regarding internet and e-mail usage. Navy policy prohibits racist, sexist, threatening, pornographic, personal business, subversive or politically partisan communications. All personnel, including the Contractor, are accountable and must act accordingly. DoD computer systems are monitored to ensure that the use is authorized, to facilitate protection against unauthorized access, and to verify security procedures, survivability, and operational security. During monitoring, information may be examined, recorded, copied, and used for authorized purposes. All information, including personal information, placed on or sent over a DoD system may be monitored. Use of a DoD system constitutes consent to monitoring. Unauthorized use may result in criminal prosecution.

Evidence of unauthorized use collected during monitoring may be used as a basis for recommended administrative, criminal, or other adverse action.

13.0 PORTABLE ELECTRONIC DEVICES (PEDs)

The Contractor shall be compliant with Naval Sea Systems Command (NAVSEA) Instruction (NAVSEAINST) 2200.1, NAVSEANOTE 2200, and CARDEROCKDIVINST 5239.6C (or their subsequent revision) provided as attachments in Section J.

14.0 ELECTRONIC SPILLAGES

Electronic spillages (ES) are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system (IS), media or hardcopy document possessing insufficient security controls to protect the data at the required classification level, thus posing a risk to national security (e.g. sensitive compartmented information (SCI) onto collateral, Secret onto Unclassified, etc.). The contractor's performance as it relates to ES will be evaluated by the Government. Electronic spillage reflects on the overall security posture of the Government and demonstrates a lack of attention to detail with regard to the handling of classified information of IS security discipline. In the event that a contractor is determined to be responsible for an electronic spillage, all direct and indirect costs incurred by the Government for electronic spillage remediation will be charged to the contractor. The incidence will be reflected in the contractor’s performance rating.

NSWCCD command security will be responsible for the corrective action plan in accordance with the security guidance reflected on the DD Form 254 Department of Defense Contract Security Classification Specification. Command security will identify the Contractor facility and contract number associated with all electronic spillages during the investigation that involve Contractor support. Command security will notify the contracts division of the Contractor facility name and contract number, incident specifics, and associated costs for cleanup. The Contractor shall assist the PCO as the PCO deems necessary to capture the costs of the spillage cleanup.

The Contractor responsible for taking Information Security Awareness training annually via their Facility Security Officer (FSO) as part of the mandatory training requirements. If a spillage occurs additional training will be required to prevent recurrence.

15.0 NON-PERSONAL SERVICES/INHERENTLY GOVERNMENTAL FUNCTIONS

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The Government will not direct the hiring, dismissal or reassignment of contractor personnel. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception that personal services are being provided.

If the contractor feels that any actions constitute or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the PCO immediately in accordance with FAR clause 52.243-7 Notification of Changes.

Inherently-Governmental Functions are not within the scope of this Task Order. Decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government. The Contractor may be required to attend technical meetings for the Government;

however, they are not under any circumstances, authorized to represent the Government or give the appearance that they are doing so.

16.0 TRANSFERRING CLASSIFIED DATA

The contractor shall ensure that personnel transferring classified data to removable media have the proper training and approval to perform Media Transfer Agent functions in accordance with CARDEROCKDIVINST 5510.12 (or subsequent revision), provided as an attachment in Section J. The contractor shall ensure that personnel designated as Media Transfer Agents have the appropriate security clearance in accordance with the attached Contract DD Form 254 Contract Security Classification Specification.

17.0 CONTRACTOR PERSONNEL IDENTIFICATION

The contractor shall obtain identification badges from the Government for all contractor personnel requiring regular access to Government property. The identification badge shall be visible at all times while employees are on Government property. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to applicable regulations concerning the use and possession of the badges. The contractor shall ensure that all identification badges issued to contractor employees are returned to the appropriate Security Office within 48 hours following completion of the Task Order, relocation, or termination of an employee or upon request by the PCO. All contractor personnel shall identify their company affiliation when answering or making telephone calls and sending e-mail and when attending meetings relating to the performance of this TO.

18.0 COMMON ACCESS CARD (CAC)/PUBLIC KEY INFRASTRUCTURE (PKI)

Contractor personnel assigned to perform work under this contract may require access to Navy Information Technology (IT) resources (e.g., computers, laptops, personal electronic devices/personal digital assistants (PEDs/PDAs), NMCI, RDT&E networks, and Navy Web servers requiring Common Access Card (CAC) Public Key Infrastructure (PKI).

Contractor personnel (prime, subcontractor, consultants, and temporary employees) requiring access to Navy IT resources shall submit a completed System Authorization Access Request Navy (SAAR-N), OPNAV 5239/14 (Rev 9/2011) form or latest version thereof, and have initiated the requisite background investigation (or provide proof of a current background investigation) prior to accessing any Navy IT resources. The contractor shall submit SAAR-N forms to the COR via the contractor's Facility Security Officer (FSO). The FSO shall grant access prior to a SAAR being submitted in Employee Status Manager (ESM). For those contractors that do not have an FSO, SAAR-N forms shall be submitted directly to the COR or designated SAAR-N Government Sponsor. Copies of the approved SAAR-N forms may be obtained through the COR/ACOR or designated SAAR-N Government Sponsor.

In order to gain and/or maintain access to Navy IT resources, the contractor shall ensure completion of initial and annual IA training, monitor expiration of requisite background investigations, and initiate re-investigations as required. If requested, the contractor shall provide to the COR or designated SAAR-N Government Sponsor documentation sufficient to prove that it is monitoring/tracking the SAAR-N requirements for its employees who are accessing Navy IT resources. For those contractor personnel not in compliance with the requirements of this clause, access to Navy IT resources will be denied or revoked.

19.0 TERMINATION OF EMPLOYEES WITH NSWCCD BASE ACCESS

The contractor shall ensure that all contractor employees who have a NSWCCD badge turn in the badge to the appropriate Security Office within 48 hours of termination of their employment or performance under this Task Order. The above requirement shall be made a part of the standard employee facility clearance procedures for all separated personnel. NSWCCD Security shall be notified of all changes in contractor personnel requiring NSWCCD base access.

For involuntarily separated personnel and those separated under adverse circumstances, the contractor shall notify NSWCCD Security in advance of the date, time, and location where the NSWCCD representative may retrieve the NSWCCD badge prior to the employee departing the Contractor’s facility. In the event the employee is separated in his or her absence, the contractor shall notify NSWCCD Security of the separation and make arrangements between the former employee and NSWCCD Security for the return of the badge.

20.0 INFORMATION ASSURANCE WORKFORCE

20.1 Cyberspace Workforce Qualifications

Per DFARS 252.239-7001, Information Assurance Contracting Training and Certification, all personnel performing cyber functions must be trained and qualified. In addition, personnel shall maintain the appropriate security clearance per SECNAV M-5510.30C to perform the tasks associated with their assigned positions. Note: The Information Assurance Workforce is also known as Cyberspace Workforce (CWF), the Cyberspace Information Technology/Cybersecurity Workforce (Cyber IT/CSWF, and the Cybersecurity Workforce).

All positions with cyber functions, whether primary or as additional/embedded duties, shall have an Information Assurance category and level identified within the Special Skills section of each Technical Instruction (TI) or applicable matrix in the Statement of Work (SOW), or Performance Work Statement (PWS).

The contractor is required to:

a. Earn and maintain appropriate baseline certification as identified in DoD 8570.01-M for the position and tasking being performed prior to the period of performance.

b. If…