Draft PWS Sonar Maintenance.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

Sonar Maintenance and Sustainment

PART 1 – GENERAL INFORMATION

1.1 General

This is a firm-fixed-price (FFP) contract for commercial supplies and services to procure next-generation sonar systems and provide life-cycle maintenance support. The Government shall not exercise supervision or control over the contract service providers performing the services herein.

1.2 Background

The Naval Oceanographic Office (NAVOCEANO) operates a global fleet of six multi-mission ships, with a seventh vessel under construction. This fleet operates on a 24/7 basis. The sonar equipment on these ships provides critical data to meet the mission requirements of the Department of Defense (DoD) and other government agencies. NAVOCEANO’s fleet includes T-AGS 60 class ships, Hydrographic Survey Launch (HSL) boats, and several unmanned platforms which currently have Kongsberg Multi-Beam Sonar Systems (MBSS) installed. In addition, NAVOCEANO currently operates several HUGIN Autonomous Underwater Vehicles (AUVs), with plans to procure more.

1.3 Scope of Work

NAVOCEANO has a continuing need for life-cycle maintenance for the sonar systems and related equipment on its T-AGS 60 class ships, Unmanned Surface Vehicles (USVs), AUVs, and HSLs.

The Government anticipates an Indefinite Delivery Indefinite Quantity (IDIQ) type contract to include both supplies and services over a five-year ordering period. The contractor shall provide all necessary personnel, equipment, tools, materials, and supervision to install, integrate, validate, and maintain the equipment listed below.

These supplies and services will support the following systems, including all previous and future models:

· EM 124 Multi-beam Sonar System (or equivalent)

· EM 712 Multi-beam Sonar System (or equivalent)

· EM 2040/EM 2042 Single and Dual-RX Multi-beam Sonar System (or equivalent)

· EM 2040C MKII Multi-beam Sonar System (or equivalent)

· EM 304 MKII Multi-beam Sonar System (or equivalent)

· EK80 Split-Beam Sonar System (or equivalent)

· SBP29 Integrated Multi-beam Sub-bottom Profiler (or equivalent)

· HIPAP 502 Acoustic Positioning System (or equivalent)

· Seatex SEAPATH 385 INS System with MRU5+ (or equivalent)

· Acoustic Doppler Current Profiler (ADCP) Systems (EC150, CP300, EC38, or equivalent)

· HUGIN AUVs (Edge, Superior, Endurance and associated sensor systems)

· HUGIN Launch and Recovery System (LARS)

· HUGIN Acoustic Positioning Operator Station (APOS)

· HUGIN Operator Station (HOS)

· HUGIN Payload Operator Station (POS)

· HUGIN Post Mission Analysis (PMA) Stations

· K-SYNC Sonar Synchronizer

· KPOS-11 KFDD DPS Interface to ISS-60

· Maritime Broadband Radio (MBR 144/179/189) cNODE Transponders and Modems

· Seafloor Information System, SIS, (Full & Remote) Applications (any supported version)

· TD50 3D Visualization Tool

· NAVOCEANO System Integration Laboratory (SIL) Simulators and Hardware

1.4 Period and Place of Performance

1.4.1 The period of performance will consist of a five year ordering period.

1.4.2 The specific period of performance for each effort will be defined in the corresponding Task Order.

1.4.3 Services shall be performed at NAVOCEANO headquarters at Stennis Space Center, MS, and aboard its ships, which are deployed worldwide. Performance under this contract will require travel.

1.5 Program Management

1.5.1 The contractor shall assign a Program Manager (PM) to serve as the single point of contact for the NAVOCEANO Contracting Officer's Representative (COR). The PM is responsible for all communications pertaining to this PWS and will direct contractor employee efforts.

1.5.2 Due to the complexity of the AUV systems, NAVOCEANO will assign an Assistant COR (ACOR) to manage all contracting responsibilities for the HUGIN AUVs. The contractor may, at its option, assign an Assistant PM (APM) to coordinate with the PM, COR, and ACOR.

1.5.3 The contractor shall host quarterly Program Management Reviews (PMRs) to monitor performance and address issues. The COR will schedule the reviews and provide a suggested agenda, for which the contractor shall prepare all briefing materials.

1.5.4 The contractor shall use industry best practices and support other NAVOCEANO briefings as required by providing relevant data and documentation.

PART 2 – DEFINITIONS & ACRONYMS

2.0 DEFINITIONS & ACRONYMS

PART 3 – SPECIFIC TASKS

3.1 Program Management

The contractor shall work closely with the NAVOCEANO Sonar Project Lead Engineer, COR, and ACOR to provide holistic support for the tasks defined herein.

3.1.1 Program Support

The contractor shall coordinate meetings, develop agendas, generate minutes, and track action items. This support requires significant interface with DoD and non-DoD activities, both CONUS and OCONUS.

· Program Status Reviews (PSRs): The contractor shall organize and host periodic PSRs as required by the Government. An agenda shall be submitted for Government review 14 days in advance (CDRL A001). The agenda should include the following information:

· Meeting Attendees

· Meeting Objectives

· Agenda Items (topic, allocated time, lead, and notes/objectives)

· Reference Documents (reports, previous PSR minutes, etc) Draft minutes shall be distributed within 7 days of the PSR, with final minutes distributed within 30 days (CDRL A002). The minutes should include the following:

· Attendees

· Meeting Summary and Key Decisions

· Discussion Details by Agenda Items

· Action Item Register

· Program Manager (PM): The PM shall be the contractor's technical single point of contact, located at the contractor's facility, and work closely with the COR. The PM is responsible for ensuring performance meets all contract requirements and will have the authority to approve task order proposals in emergent situations. Responsibilities will also include, but not be limited to, the following: personnel management; management of Government material and assets; and personnel and facility security.

3.1.2 Program Support Documentation

The PM shall ensure all CDRLs are tracked and submitted on time. In conjunction with each PSR (or at a minimum, biannually), the contractor shall provide a progress report (CDRL A003) summarizing technical services, configuration management, trial card status, maintenance, travel, and financial status. This report is due ten (10) working days prior to the PSR or the completion of the reporting period and should include the following information:

· Executive Summary (overall status, significant accomplishments, problem areas or concerns, areas requiring government intervention and upcoming events & key activities for next reporting period)

· Technical Services Summary (dates, services provided, summary of actions & outcome, and associated task order)

· Configuration Management (baseline changes, portal status)

· Maintenance Activities (application maintenance, depot repair status, and trial card status)

· Travel Summary (past and planned travel performed under the contract period)

· Financial Status (expenditures of funded task orders, contract billing status, and contract overhead tracking)

· Training Summary (courses developed and/or training provided during contract period)

3.2 Technical Support

3.2.1 24/7 On-Call Technical Support The contractor shall provide 24/7 technical support via telephone, email, or web-based applications. A response shall be initiated no later than two (2) hours after a request is received. This support shall address hardware and software problems for all systems covered under this contract.

3.2.2 Configuration & Monitoring Support

3.2.2.1 MBSS Configuration & Monitoring Support Maintenance

The contractor shall provide configuration and monitoring maintenance services for all contractor-developed applications and documentation for the systems listed in Section 1.3 of this PWS, including all the sensor systems installed on the HUGIN AUVs listed below (or equivalent):

· HISAS 1032 Dual RX Sonar

· Edgetech Sub-bottom Transmitter DW-216

· Sonar IMAGENEX 837A 6000m

· Magnetometer OFG SCM 6000m

· Altimeter

· EM 2040 MK2 Multibeam Echosounder

· Cathx Ocean Color UHD Camera and Laser Profiler

· WetLabs Turbidity Sensor

· Methane, Carbon Dioxide, and Oxygen Sensors

· Nortek DVL

· Sunstone INS w/Micro Navigation

· Terrain Navigation

· AML CTD Sensor

· Digiquartz Depth Sensor

· Seatex Seapath 130 MRU Services shall include providing the latest application and firmware updates (CDRL A005), resolving problem reports, and updating documentation. The contractor shall notify the Government six (6) months prior to a supported software release on a new COTS operating system. When new releases are created, they shall be delivered on suitable media with instructions for installation and supporting technical documentation describing the new release (CDRL A004).

3.2.2.2 MBSS Trial Card Database

The contractor shall utilize and maintain a trial card tracking system that identifies systematic software and hardware problems, failures, enhancements, and tracks actions or updates associated with each trial card. The contractor will make all reasonable efforts to correct the problem identified in a trial card submitted by the Government. The contractor will also periodically create new releases of the programs that correct errors and incorporate minor changes that do not adversely affect the operational capability as requested by the Government or other customers using the programs (CDRL A005). The contractor shall provide status of open Trial Cards on a shared portal and at all Programs Status Reviews.

3.2.3 Custom Application Support

The contractor shall provide life-cycle support for custom software applications developed for NAVOCEANO. This support is divided into two distinct categories: Application Maintenance and Application Development.

3.2.3.1 Application Maintenance

The contractor shall provide ongoing maintenance for all Government-approved custom applications, including those listed below and any subsequently developed under this contract.

· Kongsberg Datagram Router

· UNISIPS Data Converter

· SIL Sonar Simulator

· Sonar Record Viewer

· Draft Calculator Maintenance support includes bug fixes, security patches, minor usability enhancements, and updates to ensure compatibility with system changes. All updates shall be fully tested to verify that they correct the intended deficiency without negatively impacting existing functionality.

Scope Limitation: Maintenance is limited to changes that do not introduce significant new features or alter the fundamental purpose of the application. Any request that requires substantial new functionality shall be classified as "Application Development."

3.2.3.2 Application Development

The contractor shall support the development of new custom applications as required by the Government. This includes maturing existing proposals (e.g., the Kongsberg Echosounder Monitor for automated acoustic monitoring) or developing entirely new applications to meet emerging needs.

Process:

1. Proposal: Development of a new application may be proposed by either the contractor or the Government.

2. Authorization: All new development efforts require a formal proposal and a funded Task Order issued by the Contracting Officer before work can commence. No costs shall be accrued by the Government prior to an order.

3. Transition to Maintenance: Upon formal acceptance by the Government, a newly developed application will be added to the list in Section 3.2.3.1 and supported under the Application Maintenance clause for the remainder of the contract.

3.2.4 Configuration Management

The contractor shall maintain a configuration management program to provide for identification, control, and status reporting. The approved product baseline for Government-owned systems shall not be changed without Government approval via an Engineering Change Proposal (ECP) (CDRL A007).

3.2.4.1 Configuration Status Report (CDRL A006) shall be provided annually to include the information below:

· Software History & Configuration

· RMAs, Contracts, & Delivery Orders

· Built In Self Test (BIST) Results & Impedance Sweeps

· Trip Reports & Project Status Review Meeting minutes

· Trial Card Database Status

· Technical Documentation & Training Materials

· Schedules & Depot Repair Status

· Shipboard system configuration files

3.2.4.2 SharePoint (or equivalent) Portal: This program shall be maintained on a contractor-hosted shared portal accessible to the Government. The portal is intended as an immediate snapshot of configuration status to be updated throughout the reporting year. The portal will be designed jointly and contain, at a minimum, and shall be periodically audited to ensure data integrity. The recommended structure for the portal should include the following:

· Homepage: Dashboard View (quick links, program calendar, key metrics/highlights, tasks, recent activity, key contacts, etc.)

· Site Architecture: Libraries and Lists (program management and deliverables, technical and engineering library, software and firmware releases, field service reports, etc.)

· Tracking and Status: Using Links and Lists (RMA depot repair tracker, trials card database, master system configuration, training and resources, raw data (up to CUI) and historical archives, etc.)

3.2.4.3 Engineering Change Proposal (ECP) is a formal mechanism used to request and document a change to an established baseline. ECPs can be initiated by the government or the contractor. ECPs shall include the following information:

· Class of change (major or minor)

· Type of change (hardware, firmware, software, other)

· Description of change

· Reason for change

· Impact analysis

· Implementation Plan

· Estimated cost

· Final review and disposition

3.2.5 System Engineering Support

The contractor shall provide System Engineering services in the areas of mechanical, electrical, acoustic, systems, software, human factors, safety, manufacturing, testing, quality control, configuration management, and documentation. This support will be initiated at the Government's request to support the operation, maintenance, and/or upgrades of all systems included in this contract. Program management, risk management, logistics, administrative, and technical support are also to be provided to ensure all systems remain effective and supportable for both current and future capabilities.

System Engineering Support will be defined in individual Task Orders when a requirement is identified by the Government. The contractor shall provide a firm-fixed-price proposal for each requirement, based on the engineering day rate and hardware rates specified in this contract. This proposal shall include a detailed Basis of Estimate (BOE), including estimated hours, hardware, materials and any other direct costs.

All designs, documentation, and other data developed under this System Engineering Support shall become the property of the Government. The contractor shall be required to deliver all such data in a format and timeframe as specified in the Task Order. All System Engineering Support activities shall be summarized in the monthly progress report (CDRL A003), and shall include a summary of the activities performed, the results, and the cumulative hours and costs.

3.2.6 Hardware Support

3.2.6.1 Technology Refresh and Lifecycle Management

The contractor shall proactively monitor and manage the technology lifecycle of all hardware and software components within the MBSS. On an annual basis, or as requested by the Government, the contractor shall submit a Technology Refresh Plan. This plan shall identify components that are projected to become obsolete, lose manufacturer support, or fail to meet performance or security requirements within the next three (3) years.

Upon identifying a need for a technology refresh, or at the Government's direction, the contractor shall provide a detailed, firm-fixed-price proposal for the development and integration of the new technology. The proposal must include:

a. A technical description of the proposed solution and its integration into the existing system.

b. A schedule for implementation, including testing and validation.

c. A BOE detailing all labor, material, and other direct costs.

d. An analysis of the impact on system performance, reliability, and cybersecurity posture.

The Government reserves the right to accept, reject, or request modification to any proposal. The Government is under no obligation to procure the technology refresh from the contractor.

3.2.6.2 Depot Repair

The contractor shall provide depot repair for all systems specified in this contract at the contractor's facility.

· RMA Issuance: When a repair is needed, the Government POC will request a Return Material Authorization (RMA) from the contractor.

· Shipment: The Government will ship the defective item to the contractor's facility. All such items are considered Government Furnished Property (GFP).

· Evaluation & Quote: The contractor shall evaluate the item and provide a repair quote detailing the findings, estimated time, and cost. No work shall commence without an active task or delivery order.

· Tracking & Return: The RMA number will be used to track the repair, with status available on the shared portal. Repaired items will be shipped back to the Government at the contractor's expense unless otherwise specified.

· A Depot Repair Report (CDRL A008) shall be provided at all PSRs. This report shall include the following information:

1. Executive Summary (new, closed and open RMAs)

2. Status of open RMAs

3. History of closed RMAs for current contract year

4. Each RMA status shall include the item description, date received by the contractor, date shipped to the government, total turn-around time, summary of repair action, and final task/delivery order

3.2.6.3 Spares and Obsolescence Management

The contractor shall deliver a Recommended Spare Parts List (RSPL) for each system configuration as a contract deliverable (CDRL A010). The RSPL shall, at a minimum, include part number, description, unit price, manufacturing lead time, and a recommended on-hand quantity based on Mean Time Between Failure (MTBF) data or engineering analysis.

The contractor shall update and redeliver the RSPL annually, or upon Government request, reflecting any changes due to system upgrades or parts obsolescence. Specific spare parts will be ordered via delivery order against the currently approved RSPL. For parts not listed on the RSPL, the Government may issue a Request for Quote (RFQ). The contractor is required to notify the Government of any Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues affecting spare parts and provide proposed resolutions.

3.2.7 Technical Assist

3.2.7.1 MBSS Field Groom and System Checkout

The contractor shall complete system checkouts and field grooms on a per-vessel basis as directed by a Task Order. This service shall cover all hull-mounted shipboard sonar systems onboard the vessel, including those aboard HSL and/or USVs detached to the ship and in the local vicinity. The checkout shall include, at a minimum:

a) Dockside and at-sea performance testing that evaluates and validates the system is performing within appropriate specifications.

b) Upgrading all multi-beam system applications and firmware to the latest approved version.

c) Updating and delivering configuration documents (e.g., application history, version lists).

d) Upgrading all on-board spare boards to the latest approved firmware versions.

The field service engineer shall assist shipboard personnel in troubleshooting and repairing problems noted during the system checkout. All travel and on-site work shall be documented in the Field Service Trip Report (CDRL A009).

3.2.7.2 Field Service Support

The contractor shall provide technical support services for field support, ashore and at-sea, in response to Government requirements. When a need for field services is identified, the Government will issue a request for a firm-fixed-price proposal. The contractor's proposal shall include a BOE detailing the labor hours, travel, and a description of the work to be performed.

Field service support may include, but is not limited to, system troubleshooting and casualty analysis, corrective maintenance, system optimization, and informal training for Government personnel. All Field Service Support activities shall be summarized in the Field Service Trip (FST) Report (CDRL A009).

The Field Service Trip Report shall include the following at a minimum:

· Trip Summary (vessel/site, location, trip dates, purpose of visit, overall results, executive summary)

· Background/Reason for visit

· Daily activity log

· System Status (prior to and after FST)

· Recommendations and Follow-on actions

· Acknowledgement of Service (to be signed by the Government)

· Relevant Appendices/Attachments (such as: BIST Log Files, photos of HW repair, key performance data, plots) For the HSL sonar systems acceptance testing, the contractor shall be responsible for the execution and logistics needed to proficiently perform and execute the acceptance testing, i.e. procuring boat driver, boat lift, boat slip, etc.

3.2.7.3 HUGIN AUV Field Groom and System Checkout

The contractor shall complete system checkouts and field grooms on a per-AUV basis, as directed by a Task Order. This service shall cover the HUGIN AUV and its associated ancillary equipment, including launch and recovery systems (LARS) and operational support systems.

The checkout shall include, at a minimum:

a) Dockside and at-sea performance testing that evaluates and validates the AUV is performing within appropriate specifications.

b) Upgrading all AUV and data collection system applications and firmware to the latest Government-approved version.

c) Updating and delivering all relevant configuration documents.

d) Upgrading all on-board spare boards and components to the latest Government-approved firmware versions.

The field service engineer shall assist shipboard personnel in troubleshooting and repairing any problems noted during the AUV system checkout. All travel and on-site work shall be documented in the Field Service Trip Report (CDRL A009).

3.2.7.4 System Acceptance Test Support

For major installations and equipment life-cycle replacement (LCR) the contractor shall provide System Acceptance Test (SAT) Plan (CDRL A013) for review prior to installation. The contractor shall execute the SAT Plan at sea with the government as a witness. Any failures must be documented and corrective action must be identified (warranty repair, trial card, system replacement, etc.). The contractor shall provide a System Acceptance Report (CDRL A014) detailing the conduct of SAT plan execution, test results, and any corrective actions required.

3.3 Training Support

The Government may order training services for any systems, hardware, or software covered under this contract via a Task Order. In response to a Government requirement, the contractor shall provide a firm-fixed-price proposal that details the scope, schedule, and cost for either developing a new training course, delivering an existing one, or both.

3.3.1 Course Development and Delivery

When directed, the contractor shall develop new training courses tailored to specific systems, audiences (e.g., operators, maintainers, engineers), and formats (e.g., classroom, hands-on, shipboard). For any new or substantially modified course, the contractor shall develop and deliver a Training Plan and Training Materials Package (CDRL A011). These materials shall be delivered to the Government for review and approval no later than thirty (30) days prior to the scheduled training event. CDRL A011 shall include the following at a minimum:

· Part 1: Training & Lesson Plan

1. Course Overview (Title, description, target audience, course duration, prerequisites, learning objectives)

2. Course Materials Provided (description of all course materials to be provided as appendices)

3. Detailed Daily Plan / Course Outline (Day, duration, topics, learning objectives, instructional method, assessment method)

· Part 2: Appendices (The Training Materials)

1. Presentation Slides (PowerPoint or PDF slide deck)

2. Student Guide

3. Practical Exercises/Lab Handouts

4. Final Assessment

5. Course Evaluation Form

3.3.2 Instructor Qualification and Administration

All training shall be conducted by instructors who are certified and demonstrably qualified on the subject matter being taught. The contractor shall provide course evaluation forms to all students. The completed evaluation forms shall be collected by the contractor and delivered to the COR/ACOR within fifteen (15) days after course completion. All training events shall be coordinated with the designated Government technical point of contact.

4.0 TRAVEL

Travel may be required in support of this PWS, including CONUS and OCONUS sites and ships. All travel shall be authorized via a Task Order.

When a travel requirement is identified, the Government will issue a Request for Quote (RFQ). The contractor shall provide a Firm-Fixed-Price (FFP) proposal for the specified itinerary. This proposal shall be based exclusively on the allowances and regulations set forth in the U.S. Joint Travel Regulations (JTR).

Due to the nature of NAVOCEANO’s mission, travel dates and locations are subject to change. Should a Government-directed change or delay occur after the Task Order is issued that impacts the cost, the contractor shall immediately notify the Contracting Officer. The FFP Task Order shall be modified to adjust for the cost difference. This adjustment will be based on the actual, allowable costs incurred by the contractor in accordance with the JTR, supported by receipts.

4.1.1 OCONUS Travel

The contractor is solely responsible for ensuring its employees possess all required standard travel documents (e.g., proper identification, passports, visas) for CONUS and OCONUS travel. The contractor shall ensure there are no travel delays due to personnel lacking required documentation. The Government is not responsible for any costs associated with contractor employee travel preparation (e.g., passport fees, vaccinations, luggage, clothing).

The contractor is responsible for knowing and complying with all entrance and theater clearance requirements for any OCONUS location. This includes monitoring the DoD Foreign Clearance Guide (FCG) (https://www.fcg.pentagon.mil/) for all traveler requirements. The use of the Aircraft and Personnel Automated Clearance System (APACS) may be required for certain OCONUS locations, and the use of the Synchronized Pre-deployment & Operational Tracker (SPOT) may be required to obtain a Letter of Authorization (LOA). The contractor shall ensure all deploying personnel understand and comply with all applicable local laws, customs, and DoD directives for the travel location.

PART 4 - GOVERNMENT FURNISHED PROPERTY / EQUIPMENT / RESOURCES

Not Applicable

PART 5 – SECURITY REQUIREMENTS/INFORMATION TECHNOLOGY (IT) SYSTEMS ACCESS

The overall classification of this contract is CUI (Controlled Unclassified Information). Contractor does not require access to classified information in the performance of this contract. All contract personnel shall comply with the directives and policies established in 2 CFR Part 117 “National Industrial Security Program Operating Manual” and SECNAVINST 5510.36B “Department of the Navy (DoN) Information Security Program.” The contractor shall require logical and physical access to Naval Oceanographic Office facility. A Tier 1 (T1) background investigation is required IAW SECNAVINST 5510.30C and DoN CIO Memorandum dated 8 Sep 2020 regarding IT Level designation. Upon award of the contract (or within 30 days of contract award) the Contract Company will provide the Security Office with a Resume and OF306 of contract personnel to begin the T1 investigation or to verify the contractors have the required investigation for the contract. Please reach out to the COR to get Personnel Security Specialist contact information.

"ALL AUTHORIZED USERS OF DOD INFORMATION SYSTEMS SHALL RECEIVE INITIAL IA AWARENESS ORIENTATION AS A CONDITION OF ACCESS AND THEREAFTER MUST COMPLETE ANNUAL IA REFRESHER AWARENESS TRAINING TO MAINTAIN AN ACTIVE USER ACCOUNT."

5.1 Information Security

To the extent the contractor receives or is given access to proprietary data, data protected by the Privacy Act of 1974, or other unclassified or CUI privileged technical, business, or financial information under this contract, the contractor shall treat and protect such information IAW any restrictions imposed on such information. Access includes the functions of data handling, storage, electronic transmission and physical distribution.

5.2 Physical Security

The contractor is responsible for knowledge of and compliance with all OPNAV and local site instructions, policies, and procedures regarding physical security in the performance of this contract. The contractor shall safeguard all Government property in assigned work areas and secure all Government material in the contractor’s possession when not under direct physical control of contractor employees.

5.3 IT System Access

5.4 Security Requirements

5.4.1 The scope of the contract will be limited up to CUI (Controlled Unclassified Information). Performance of work will require access to unclassified data and computer resources within NAVOCEANO’s controlled workspaces and aboard T-AGS vessels.

5.4.2 Positions on this contract are designated as noncritical-sensitive National Security Position IAW SECNAVINST 5510.30C. For the duration of the contract, all contractors shall be required to be a US citizen and have a favorably adjudicated NACLC or Tier 3 (T3) investigation to obtain a favorable determination for assignment to a non-critical sensitive position. A favorable adjudication by the Defense Counterintelligence and Security Agency (DCSA) based on a NACLC or T3 investigation results in a SECRET clearance eligibility determination even though access to classified information is not required for this contract. Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. This Noncritical-Sensitive National Security Position designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified by DON as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably adjudicated NACLC or Tier 3 (T3) investigation to obtain a favorable determination for assignment to an non-critical sensitive position. Each contractor employee is required to complete:

1. SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

2. Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

3. Original Signed Release Statements

Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period.

All contract personnel shall comply with the directives and policies established in DoD 5220.22-M “National Industrial Security Program, Operating Manual”, SECNAVINST 5510.30C “DoN Personnel Security Program”, and SECNAVINST 5510.36B “DoN Information Security Policy”. Additionally, contractors will meet the standards and qualifications outlined in SECNAV Manual 5239.20A “Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management” and DoD Directive 8140.1 “Cyber Workforce Management”. All contractors require non-critical sensitive information access as defined above.

All contract personnel shall complete applicable cybersecurity training, and complete System Authorization Access Request Navy (SAAR-N) forms before accessing any Navy Information Technology resources. Non-disclosure agreements (NDAs) and SAAR-N forms shall be forwarded to the Contract Officer Representative (COR) prior to the individual’s start date and forwarded to the Navy Command’s Security manager upon contractor arrival to the command. If the contractor does not have a Common Access Card (CAC), they must obtain one prior to the start of the contract. Applicable cybersecurity training must be completed and completion forms must be forwarded to the COR when the training has been done. Failure to provide the required documentation may result in delaying the individual’s start date or result in individual’s removal from the task.

The contractor shall ensure the required security training, system access requests, and site visit requests for all new employees are submitted to NAVOCEANO in within 5 days of an employee being approved to work on the contract.

All contract personnel shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.

Per guidance in the current Application Security and Development STIG, ensure that all software designers, developers and testers performing work under this contract are provided training on secure design, coding, and testing principles/practices, known security flaw types and methods, newly-discovered vulnerability types and methods, and detection/correction methods on at least an annual basis.

All information, products delivered, or services performed may not be disclosed by any means without prior approval of the authorized Contract Officer Representative (COR). Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or other person or entity; publication of technical or scientific papers; advertising and or other proposed public release.

The potential consequence for failing to meet any of the requirements listed above includes a determination on untrustworthiness and denial of access for the proposed contractor employee. Failure to obtain a favorable trustworthiness determination in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees for working in non-sensitive positions, with sensitive information, and/or on Government IT systems. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have physical access to a federally controlled facility and/or access to a federally-controlled information system/network and/or access to Government information.

5.5 Common Access Card Requirements

Some Government facilities/installations (NAVOCEANO, some ship port locations) require contractor personnel to have a Common Access Card (CAC) for physical access to the facilities or installations. Contractors supporting work that requires access to any DoD IT/network also requires a CAC. Granting of logical and physical access privileges outlined above. The Contractor is responsible for obtaining the latest facility/installation and IT CAC requirements from the applicable local Security Office. When a CAC is required to perform work, contractor personnel will be able to meet all of the following security requirements prior to work being performed:

In accordance with Directive-Type Memorandum (DoD Manual 1000.13 Volume 1), issuance of a CAC will be based on the following four criteria:

1. Eligibility for a CAC - to be eligible for a CAC, Contractor personnel’s access requirement will meet one of the following three criteria: (a) individual requires access to multiple DoD facilities or access to multiple non-DoD Federal facilities on behalf of the Government on a recurring bases for a period of 6 months or more, (b) individual requires both access to a DoD facility and access to DoD network on sire or remotely, or (c) individual requires remote access to DoD networks that use only the CAC logon for user identification.

2. Verification of DoD affiliation from an authoritative data source - CAC eligible personnel must be registered in the Defense Enrollment Eligibility Reporting Systems (DEERS) through either an authoritative personnel data feed from the appropriate Service or Agency or Contractor Verification System (CVS).

3. Completion of background vetting requirements according to FIPS PUB 201-1 and as outlined above.

4. Verification of a claimed identity - all personnel will present two forms of identification in their original form to verify a claimed identity. The identity source documents must come from the list of acceptable documents included in Form I-9, OMB No. 1615-0047, Employment Eligibility Verification. Consistent with applicable law, at least one document from the Form I-9 list will be a valid (unexpired) State or Federal Government-issued picture identification (ID). The identity documents will be inspected for authenticity, scanned, and stored in the DEERS.

PART 6 – PERFORMANCE REQUIREMENTS SUMMARY AND QUALITY CONTROL

6.1.2 The COR will inspect for compliance with Contract terms and conditions throughout the Contract period. The Government will monitor the Contractor's performance by performing surveillance using the performance requirement summary (PRS). The PRS is used primarily to determine if the Contractor is performing all required outputs. The PRS also indicates for contractors the importance of each required service.

6.3 Performance Requirements Summary

3.2.3.1 MBSS Custom Application Maintenance

3.2.6.2 Depot Repair

3.2.6 Hardware

3.2.2.2 Trial Card Database

3.2.1 On-Call Technical Support

3.3.1 Training

PART 7

DOCUMENTATION AND DELIVERABLES SCHEDULE

7.1 Contract Data Requirements Listings (CDRLs)

The following CDRL listing identifies the data item deliverables required under this contract and the applicable section of the PWS for which they are required. The below list includes the DD Form 1423s that itemize each Contract Data Requirements List (CDRL) required under the base contract. The contractor will establish a practical and cost-effective system for developing and tracking the required CDRLs generated under each task.

7.2 Electronic Format

At a minimum, the deliverables will be provided electronically by email; hard copies are only required if requested by the Government. To ensure information compatibility, the contractor will guarantee all deliverables (i.e., CDRLs), data, correspondence, and etc., are provided…