Draft PWS MBSS.pdf

NAVAL OCEANOGRAPHIC OFFICE

MULTI-BEAM SONAR SYSTEM LIFE CYCLE MAINTENANCE

PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

The Naval Oceanographic Office (NAVOCEANO) currently operates six multi-mission ships, operating world-wide on a 24/7 basis. These ships’ sonar equipment provides a critical segment of the data that is used to meet research mission requirements in support of Department of Defense, Navy, and other governmental agencies.

NAVOCEANO’s fleet includes T-AGS 60 class ships and Hydrographic Survey Launch (HSL) boats that currently have Kongsberg Multi-Beam Sonar Systems (MBSS) installed.

2.0 SCOPE

NAVOCEANO has a continuing need for life-cycle maintenance for the sonar systems and related equipment on their T-AGS 60 class ships and Hydrographic Survey Launch (HSL) boats that operate world-wide on a 24/7 basis.

This contract will include both supplies and services for a five-year ordering period.

These supplies and services will be in support of the following systems to include previous and future models:

• EM2040 single-RX Multi-beam Sonar System

• EM2040 dual-RX Multi-beam Sonar System

• EM710 Multi-beam Sonar System

• EM712 Multi-beam Sonar System

• EM122 Multi-beam Sonar System

• EM124 Multi-beam Sonar System

• EC150 Acoustic Doppler Current Profiler

• EK80 Split-Beam Fisheries Sonar System

• SBP120 Integrated Multi-beam Subbottom Profiler

• SBP29 Integrated Multi-beam Subbottom Profiler

• K-SYNC Sonar Synchronizer

• NAVOCEANO System Integration Laboratory (SIL) – Simulators for Kongsberg Sonar System

• HIPAP 501 Acoustic Positioning System

• HIPAP 502 Acoustic Positioning System

• Seatex SEAPATH 330+ INS System

• KPOS-11 KFDD DPS Interface to ISS-60

2.1 CONTRACT TYPE

Commercial indefinite delivery indefinite quantity (IDIQ) type contract with a five (5) year ordering period.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all support tasks that will be required throughout the contract life. The contractor will provide necessary resources and knowledge to support the listed tasks. Specific objectives will be dependent on the base contract and any task orders (TO) written against the base contract. The contractor will complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

3.1. PROGRAM MANAGEMENT

The contractor will work closely with the Sonar Project Lead Engineer, COR and various TPOCs to provide holistic support of the tasks as identified below.

3.1.1 Program Support

Program support shall include coordination of meetings, developing agenda items, attending high-level meetings, generating minutes, and tracking action items. Program support will require significant coordination and interface with various DOD and non-DOD activities located in and out of Continental United States (CONUS). The Contractor shall organize and host periodic Program Status Reviews (PSRs) as required by the Government. An agenda shall be issued with each PSR or meeting, 14 days in advance for review by the Government, and within 7 days after receiving comments back from the Government (CDRL A001). Draft meeting minutes shall be distributed within 7 days of the last day of the PSR, final minutes shall be distributed within 30 days (CDRL A002).

3.1.2 Program Support Documentation

The PM shall be responsible for ensuring that all program management contract deliverables are tracked and submitted on time throughout the life of contract. In conjunction with each PSR, or at a minimum biannually, the contractor will provide a progress report summarizing technical services, configuration management, maintenance, trial card status, travel, financial status, and training provided for MBSS support (CDRL A003). The contractor’s report shall include significant accomplishments or events, the status of any on-going efforts, including any problems or areas of concern, areas where Government intervention is required and upcoming events. The contractor shall submit the report ten (10) working days prior to PSR or the completion of the reporting period.

3.2. TECHNICAL SUPPORT

3.2.1 24/7 On-Call Technical Support

The contractor shall provide technical support and assistance via telephone, fax, email and/or web based applications on an as-needed basis. Technical support shall be available 24 hours a day and supported by technical personnel familiar and competent with all systems. Technical assistance will be necessary for the Government to report problems with any and all equipment. The contractor shall initiate technical assistance response no later than two (2) hours after receipt of technical support request. Technical assistance shall be provided through the most effective means available to the Government. This support shall address both software and hardware problems and is applicable to all systems covered under this contract.

3.2.2 Configuration & Monitoring Support

3.3.2.1 MBSS Configuration & Monitoring Support Maintenance

The contractor shall provide sonar configuration and monitoring maintenance services on all contractor-developed applications and documentation used in all operational aspects of the following systems:

• EM2040 Single and Dual-RX Multi-beam Sonar System

• EM122 Multi-beam Sonar System

• EM124 Multi-beam Sonar System

• EM710 Multi-beam Sonar System

• EM712 Multi-beam Sonar System

• SBP120 Integrated Multi-beam Subbottom Profiler

• SBP29 Integrated Multi-beam Subbottom Profiler

• EK80 Split-Beam Fisheries Sonar System

• K-Sync Sonar Synchronizer

• NAVOCEANO SIL – Simulators for Kongsberg Sonar System

• HIPAP 501/502 Acoustic Positioning System

• KPOS-11 KFDD DPS Interface to ISS-60

• Seatex SEAPATH 330+ INS System

• EC150 Acoustic Doppler Current Profiler

The services shall include all applications used for control of the sonar, data collection, and real-time quality assurance.

The services shall include providing the latest version of application and firmware updates (CDRL A005), resolution of problem reports, installation instructions, documentation updates (including technical manuals as applicable) and incorporation of corrections into existing sonar application versions used by the Government. This maintenance does not cover new releases or upgrades of third party software or hardware. The contractor shall specify the necessary requirements for upgrades to third party operating system software and hardware. Changes to external system interface specifications shall be implemented such that external systems are not adversely affected whenever possible. Product obsolescence issues shall be identified and recommended solutions shall be developed. The contractor shall notify the

Government six (6) months in advance, prior to the release of supported software on a newer commercial off the shelf

(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.3 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 Applications for Configuration Monitoring and Maintenance of MBSS

3.2.3.1 MBSS Custom Application Maintenance

The contractor shall provide application maintenance and upgrades for custom applications developed for

NAVOCEANO. The maintenance includes providing updates and the latest version of the application and documentation for the following and new custom applications developed under this contract:

• Kongsberg Datagram Router

• UNISIPS Data Converter

• EMX Simulator

• Sonar Datagram Viewer

• Draft Calculator

Updates shall enhance system performance, improve usability or fix deficiencies that have been sufficiently tested prior to delivery to ensure system still functions as specified. If a change is required to a custom application that is beyond the scope that can be considered maintenance, the change will be submitted as a new proposal under 3.2.3.2 MBSS

Application Development.

3.2.3.2 MBSS Application Development

The contractor can propose custom applications to facilitate sonar maintenance and monitoring that the Government will review in consideration of an order under this contract. This includes current proposed custom applications (Kongsberg

Echosounder monitor for automated acoustic monitoring or the SIL PU and KSYNC Simulator) as well as applications yet to be considered. All proposed applications shall be ordered through a task order prior to development or costs being accrued by the Government. Custom applications will be maintained under section 3.2.3.1 once deployed.

3.2.4 Configuration Management

The contractor shall maintain a configuration management program that provides for configuration identification, control and status reporting (CDRL A006). The configuration management program will assure that all systems, components and software versions are in accordance with their correct and known baseline configuration, that no unauthorized changes are made to these configurations, that authorized changes are properly documented and that a history of configuration changes is maintained. The contractor shall notify the Government of any contractor initiated proposed changes to the product baseline to allow the Government time to evaluate the change and determine if the change is in the best interest of the Government. The approved product baseline of Government owned systems shall not be changed without the approval of the Government and shall be implemented through the Engineering Change

Proposal (CDRL A007).

The configuration management program shall be maintained on a SharePoint Portal, made accessible by the contractor, the Government and other agencies related to the MBSS project, as needed. The Portal shall be designed jointly by the contractor and the Government, and shall be set up and maintained on a server at the contractor facility. Access to make changes to the interface, including uploading data and modifying information, will be restricted to specific personnel determined and agreed upon by the contractor and the Government. The portal shall be set up to allow information to be uploaded or downloaded as required and configured with pre-defined as well as configurable reporting templates that can be printed as needed. Any equipment required for the Government to access the portal shall be provided by the contractor. The portal shall be updated every 30 days with latest information available. The portal shall include, but not be limited to, the following MBSS related information:

• SW History/Configuration

• RMAs/Contracts/Delivery Orders

• BIST Results

• Impedance Sweeps

• Trip Reports

• Trial Card Database

• PSR/Meeting Notes

• Kongsberg Documentation

• Training Material

• Schedules

• SW Installation Files

• Historical Information

• Depot Repair Status

To ensure the data in the portal is being maintained and updated as required, there will be periodic audits of the

SharePoint Portal, usually coinciding with scheduled PSRs.

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 as required in support of the operation, maintenance, and upgrades of all systems. Program management, risk management, logistics, administrative and technical support are also required to assure that all systems remain an effective and supportable asset, for both current capability and the development of future capabilities. System

Engineering Support will be further defined at the task order level when a requirement is identified. The contractor shall provide a quote for each System Engineering requirement to be evaluated by the Government. All System

Engineering Support activities shall be summarized in the progress report (CDRL A003).

3.2.6 Hardware Support

3.2.6.1 Technology Refresh

As current MBSS technology becomes obsolete, the contractor shall inform the Government of the development and integration of new technology into any or all of the existing Government-owned systems. The Government reserves the right to upgrade technology as deemed necessary. The contractor shall provide a quote for each technology refresh requirement to be evaluated by the Government. Any new technology/equipment proposed and the government determines required, will be added to the base contract by modification.

3.2.6.2 Depot Repair

The contractor shall provide depot repair and maintenance for all systems specified in the contract, including any serviceable sub-assemblies or modules such as circuit boards, power supplies, etc. Repair shall be performed at the contractor’s facility and will be further defined at the task order level when necessary.

When the Government determines the need for depot repair, the COR/ACOR/Technical POC will contact the contractor for a Return Material Authorization (RMA). The Government will ship, at its expense, defective items to the contractor’s facility utilizing the RMA, providing any available description of the problem. All material turned over to the contractor will be considered Government Furnished Property (GFP) and all GFP procedures and requirements shall be followed.

The contractor shall evaluate the defective item and provide a firm-fixed price quote for the required repair within 4 weeks of receipt. The estimate shall include, but is not limited to, a minimum of the following information: a description of the evaluation findings, the estimated time to repair and/or replace, and availability of a refurbished product (equal to or better than the defective item). The Government reserves the right to select the proposed repairs or replacement of the item upon receipt of the evaluation findings and prior to the commencement of services. No repairs or work shall be conducted until an order is issued with the agreed upon firm-fixed price. If additional work or repairs are discovered during the repairs that will result in additional costs, the contractor shall stop the repair work and provide the information along with a quote for the additional work to the Contracting Officer. The Contracting Officer will determine if this work is within scope of the original repair and will determine the appropriate action to take. No repairs or work shall be conducted that would result in a charge to the Government without an active task or delivery order issued by the Contracting Officer.

The RMA number will be used to track and identify all depot repairs throughout the repair process. The contractor will provide a means of tracking all repairs by RMA number, including on the SharePoint Portal. All repaired items will be shipped back to the Government’s facility at Stennis Space Center, MS at contractor expense unless otherwise specified by the Government. In addition to the active tracking of RMAs via the portal, the contractor shall provide a Depot Repair

Report that includes status of all open RMAs and a history of the repairs to date for each contract year (CDRL A008). The

Depot Repair Report shall be provided at PSRs or as requested by the Government.

3.2.6.3 Spares

The contractor shall provide a list of all field replaceable spare parts for each system specified in the contract and any subsequent upgrades. The spare parts list shall be updated as parts become obsolete or upgraded through the life of the contract through a modification to the base contract. Any spares or other hardware identified as being required in support of the sonar systems will be added to the spare parts list through modificaiton to the base contract. All prices in the spare parts list shall be firm-fixed prices and applicable for the remaining duration of the base contract. Specific spare parts, quantity and prices, will be requested through a request for quote and ordered through a delivery order as deemed necessary by the Government and will be identified based on fluctuating mission requirements.

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. This service shall cover all hull-mounted shipboard sonar systems onboard the vessel including those aboard HSLs that are detached to the ship and in the local vicinity. The checkout shall include:

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

b) Upgrading all multi-beam system applications and firmware as needed

c) Updating and delivering configuration documents (application history)

d) Upgrading all spare boards to the latest firmware versions as needed

As time allows, the engineer shall assist shipboard personnel in troubleshooting and repairing any problems noted during the system checkout. The contractor will include all travel time and onsite work performed and Field Service

Trip Report (CDRL A009).

3.2.7.2 Field Service Support

Technical support services will be necessary for field support, ashore and at-sea. Field service support will be further defined at the task order level. When requirements for field services are identified, the Government will request a quote for evaluation. Field service support shall be charged on a daily basis according to the type of service required

(ashore/at-sea). Any travel required for field service will be funded via the Travel CLIN. All Field Service Support activities shall be summarized in the Field Service Trip Report (CDRL A009).

3.2.7.3 Seapath MRU Calibration

NAVO will be responsible for shipping the equipment intended for calibration to the contractor facility and return to the desired location. The contractor shall perform calibration and provide a full calibration report and maintain a calibration database for all NAVO owned Seapath MRU’s. The turnaround time after the contractor receives the MRU shall be no greater than 2 weeks. Firmware and minor hardware updates to the MRU shall be provided as part of the calibration process. All material turned over to the contractor will be considered Government Furnished Property (GFP) and all GFP procedures and requirements shall be followed.

3.3 TRAINING SUPPORT

3.3.1 Training

The Government may request training on any/all of the systems, hardware, software, etc. The contractor shall provide training material (CDRL A011) and a course evaluation form following each training period. The completed course evaluation forms shall be provided to NAVOCEANO within 15 days after course completion. Training sessions shall be coordinated with the COR/ACOR/Technical POC. Course evaluations shall be at least 90% trainee satisfaction.

3.3.1.1 MBSS Training Course Development

The contractor shall develop training material at the request of the Government for specific training courses for any of the systems that comprise the MBSS. The training focus could be operator, maintenance or theoretical (or combination) and could be structured for a general training audience or for specific expertise, such as hydrographers, technicians or engineers. The course could include classroom or hands-on training, or a combination of both and could be tailored for field training or for training at a facility. The course materials shall include a training and lesson plan, outlining the course objectives and providing a detailed daily plan. The course requirements will be further defined at the task order level. Draft course material shall be provided minimum 30 days prior to course execution for government review.

4.0 TRAVEL

Travel will be required in support of this PWS and includes various CONUS and outside the continental United States

(OCONUS) sites and ships. Travel will be identified at the order level and will be priced as FFP. When a travel requirement is identified, the Government will provide the location and dates as early as possible. These dates and location are subject to change up until the day of travel due to the nature of NAVOCEANO’s mission. All travel changes after the issuance of an order shall be through modification unless otherwise authorized by the Contracting

Officer. Upon the identification of travel requirements, a RFQ will be provided to the contractor. The Contractor shall provide a FFP quote for the travel requirement, the quote shall only include those travel cost authorized by the U.S.

Joint Travel Regulations (JTR). All modifications that require changes to the contractor’s price due to Government caused delays or changes will be subject to the quoted prices or actual receipts, subject to the circumstances. OCONUS

Deployment Reports shall be provided for each OCONUS trip (CDRL A014).

4.1 LOCATIONS

Ship field support under this contract will be performed onboard NAVOCEANO vessels which are deployed worldwide. Other travel may also be required to various field locations. As specified at task order level, travel will be required by specific personnel, and the contractor shall be prepared to travel, at a minimum, to the following sample locations: United States, Japan, Singapore, Korea, Africa, Europe, Canada, The Philippines, UAE, Bahrain, and other locations CONUS, and OCONUS.

4.1.1 OCONUS Travel

All contractor employees that will travel CONUS or OCONUS shall be prepared with any required standard travel documents (i.e. proper identifications, passports, etc.). There shall be no contractor travel delays do to personnel not having required standard travel documents. The Government is not responsible for the costs associated with contractor employees preparation for travel (i.e. identification, passports, vaccinations, luggage, clothing, etc.). The Contractor is responsible for knowing all entrance requirements to the OCONUS travel location. The Government will provide advance notice to OCONUS travel when possible to allow sufficient time to process required clearances. Sufficient advanced notice is not always possible, in these cases, the Contractor shall coordinate with the appropriate Government personnel to expedite authorizations.

Contractor personnel shall follow all local laws and customs of the travel location. DoD Theater and Country entrance requirements can be found in the DoD Foreign Clearance Guide (https://www.fcg.pentagon.mil/). The DoD Foreign

Clearance Guide contains specific Contractor requirements. The use of Aircraft and Personnel Automated Clearance

System (APACS) maybe required for certain OCONUS locations. Clauses for OCONUS travel, services, and deliveries are included in this contract. Clauses specific to certain countries, regions, or DoD Theaters will be applicable to the task orders. Contractor shall be aware of these clauses as they may contain additional requirements for travel in or through these areas such as the requirement to use Synchronized Predeployment & Operational Tracker (SPOT) to obtain a Letter of Authorization (LOA). Additional information on current foreign travel information can be found through the U.S. Department of State.

5.0 CONTRACT ADMINISTRATION

5.1 CONTRACT POINTS OF CONTACT

The Government and Contractor points of contacts POC’s will be provided separately. The Contractor shall provide at minimum the Program Manager information and the individuals responsible for the following:

https://www.fcg.pentagon.mil/

Contractor Signature Authority for contract, modifications, and orders

Individual(s) to receive Order RFQ’s and modification requests

Other primary and secondary Contractor POC’s

5.2 PROGRAM MANAGER

In addition to the Program Management tasks in this PWS, the contractor shall assign a technical single point of contact, also known as the Program Manager (PM) who will work closely with the Government Contracting Officer’s

Representative (COR). Located in the contractor’s facility, the PM will be ultimately responsible for ensuring that the contractor’s performance meets all Government contracting requirements with over all company resources necessary for contract performance. The PM shall have 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. In support of open communication, the Contractor will have, unless otherwise directed, quarterly meetings with the COR and periodic reviews with the Project Engineer

(PE) – these can be via email, telephone, or other virtual means if not in conjunction with a scheduled PSR.

5.3 TASK ORDERING PROCESSING

This contract includes requirements that will be ordered on a yearly basis for continued sustainment support as well as requirements with quantities or deliveries that have not been identified. The services and supplies that this contract has established firm fixed prices may be ordered without requesting a quote from the contractor such as, but not limited to, Program Management Support and 24/7 On-Call Technical Support. Other requirements will require the Government to issue a RFQ.

5.3.1 Ordering Request For Quotes

The Government may issue an RFQ formally on a SF 1449, SF 18, by email, or verbally. The RFQ will be provided to the Contractor by the NAVSUP Contracting Office only. The RFQ will provide either a description of the required supplies or a PWS of the services required. All services will be performance-based FFP.

5.3.2 Contractor Quotes

The Contractor shall respond within 5 business days to all RFQ’s. The Government may require at times a shorter response time due to urgency; the Contractor shall make every attempt to respond to an RFQ when requested. Quotes shall be provided only to the NAVSUP contracting office by an authorized contractor representative. Quotes will be evaluated for technical acceptability, if required, and an evaluation on the price to determine it fair and reasonable if it was not already determined fair and reasonable. Contractor may be requested to provide supporting documents to assist in the evaluation of the quote.

5.3.3 Delivery & Task Orders

Only the NAVSUP Fleet Logistics Center Norfolk site Mechanicsburg is authorized to issue orders. Orders may be issued in the following forms: SF1449, DD1155. Verbal orders, including text message and email, are authorized when provided by a warranted contracting officer. All verbal orders by phone or text message will be followed-up by an email confirming the order then by a confirming order on a SF1449 or DD1155. An email is not required if an

SF1449 or DD1155 is issued before an email can be provided. Orders placed under this contract must contain the following information:

(i) Date of order.

(ii) Contract number and order number.

(iii) For supplies and services, line item number, subline item number (if applicable), description, quantity, and unit price or estimated cost and fee (as applicable). The corresponding line item number and subline item number from the base contract shall also be included.

(iv) Delivery or performance schedule.

(v) Place of delivery or performance (including consignee).

(vi) Any packaging, packing, and shipping instructions.

(vii) Accounting and appropriation data.

(viii) Method of payment and payment office, if not specified in the contract (see 32.1110(e)).

(ix) North American Industry Classification System code (see 19.102(b)(3)).

5.4 CONTRACT ADMINISTRATION DOCUMENTATION

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

5.4.1 Contract and Task Order Status Report

A Quarterly Progress Report will be developed and submitted quarterly (CDRL A003). The contractor will submit the report ten (10) working days prior to PSR or the completion of the reporting period. Quarters will be based on the fiscal year beginning in the month of October.

The prime will be responsible for collecting, integrating, and reporting any subcontractor reports.

(a) Contract Status Report - A quarterly contract status report to include TOs will be provided to the COR. The report will include, as a minimum, the following items and data:

1. Period of performance

2. Period of reporting

3. List all TOs written against the basic

4. List all contract level Modifications, date of modification, sentence summary, and if applicable, list the total modification funding amount

5. List total Travel expended (current and cumulative)

6. List total Material delivered and invoiced (current and cumulative)

7. List total contract ceiling amounts

8. List total remaining contract ceiling amounts

5.4.2 Task Order Closeout Report

Every Task Order (TO) will require a closeout report (CDRL A012). The Report shall be submitted electronically as an e-mail attachment; hard copies are required only upon request. The report will include, at a minimum, the following information:

(a) Final Invoice - Invoice marked “FINAL”.

(b) Deliverable status -- Percentage job complete, any outstanding issues, CDRL status, list of any items/services under workmanship/manufacturer warranty, etc.

(c) Government Property - All Contractor-acquired Property (CAP) and GFP provided on order will either be consumed or returned to the Government. A final inventory list will be required accounting for all GFP.

Contractor will incorporate information and receipts obtained from the initial disposition inventory list. For property being returned, the contractor shall include on the inventory list the following minimum information:

part numbers, NSN nomenclature, quantity, and condition of each item (i.e., Condition A, F, etc.). Paperwork validating official receipt by Government is required for returned items.

6.0 QUALITY ASSURANCE

6.1 QUALITY ASSURANCE SYSTEM

Upon contract award, the contractor shall have and maintain a quality assurance process that meets contract requirements and program objectives while ensuring customer satisfaction and defect-free products/process. The quality system will be documented and contain procedures, planning, and all other documentation and data necessary to provide an efficient and effective quality system based on their internal auditing system. The quality system shall be made available to the Government for review at both a program and worksite services level during predetermined visits. Existing quality documents that meet the requirements of this contract may continue to be used. The Contractor shall also require any subcontractors to possess a quality assurance and control program commensurate with the services and supplies to be provided as determined by the contractor’s internal audit system.

The Government reserves the right to disapprove the Contractor’s and/or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet contractual requirements at either the program or worksite services level. The Government reserves the right to participate in the process improvement elements of the contractor’s quality assurance plan as needed. At minimum, the contractor’s quality system will meet the following key criteria:

• Establish capable processes

• Monitor and control critical product and process variations

• Establish mechanisms for feedback of field product performance

• Implement and effective root-cause analysis and corrective action system Continuous process improvement

6.2 QUALITY CONTROL

Unless otherwise directed, the Contractor is responsible for all quality control inspections necessary in the performance of the various tasks as assigned. The Government reserves the right to perform any inspections deemed necessary to assure that the Contractor provided services, documents, and material meet the prescribed requirements and to reject any or all services, documents, and material in a category when nonconformance is established.

6.3 PERFORMNACE REQUIREMENTS SUMMARY

7.0 DOCUMENTATION AND DELIVERABLES

7.1 CONTRACT DATA REQUIREMENT 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. Attachment _1__ 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.

CDRL Description PWS Reference Paragraph

A001 PSR/meeting Agenda 3.1.1

A002 PSR/meeting minutes 3.1.1

A003 MBSS PSR / quarterly progress report 3.1.2; 3.1.5; 5.4.1

A004 Release Notes and Documentation Updates 3.3.2.1

A005 Software/Firmware Updates 3.3.2.1; 3.2.2.3

A006 Configuration Status Report 3.2.4

A007 Engineering Change Proposal 3.2.4

A008 Depot Repair Report 3.2.6.2

A009 Field Service Trip Report 3.2.7.1; 3.2.7.2

A010 GFP Status Report 9.0

A011 Training and lesson plan and training material 3.3.1

A012 Task Order Closeout Report 5.4.2

A013 OCONUS Deployment Reports 4.0

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 in a format approved by the receiving Government representative. All data will be provided in an editable format compatible with NAVOCEANO corporate standard software configuration as specified below. Contractor will conform to standards within 30 days of contract award unless otherwise specified.

The initial or future upgrades costs of the listed computer programs are not chargeable as a direct cost to the

Government.

Deliverable Software to be used

a. Word Processing Microsoft Word

b. Spreadsheet/Graphics Microsoft Excel

c. Presentations Microsoft PowerPoint

d. 2-D Drawings/Graphics/Schematics (new data products)

2-D Drawings/Graphics/Schematics (new data products)ector (CGM/SVG), DWG, PDF

e. 2-D Drawings/Graphics/Schematics (new data products)

Raster (CALS Type 1, TIFF/BMP, JPEG, PNG), PDF, DWG

f. Computer Aid Design (CAD) Drawings AutoCAD/Visio

8.0 SECURITY

8.1 INFORMATION SYSTEM SECURITY:

The highest classification of all information on this contract is UNCLASSIFIED.

8.1.1 Information Security

The contractor will provide adequate security for all unclassified DoD information passing through non-DoD information system including all subcontractor information systems utilized on contract. Unclassified DoD information will only be disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be 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).

8.1.2 Safeguards

The contractor shall protect Government information and shall provide compliance documentation validating they are meeting this requirement. The contractor and any subcontractors shall abide by the following safeguards:

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

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

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

(d) Encrypt all information that has been identified as controlled unclassified information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as thumb drives and compact disks, using the best available encryption technology.

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

(f) Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer

Security (TLS). Encrypt organizational wireless connections and use encrypted wireless connection where available when traveling. If encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using at least application-provided password protection level encryption.

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

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

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

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

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

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

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

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

8.1.3 Compliance

The contractor will include in their quality processes procedures that are compliant with information security requirements.

8.2 SECURITY REQUIREMENTS

Document Number Title

DoD 5220.22-M DoD Manual - National Industry Security Program

Operating Manual (NISPOM)

DoDI 5220.22 DoD Directive - National Industrial Security Program

DoD Manual 5200.02 DoD Manual - Personnel Security Program

DoDI 8500.01 DoD Directive - Cybersecurity

SECNAVINST 5510.36B DoN Instruction – Information Security Program

DoD Manual 5200.01 Vol’s 1-3 DoD Manual – Information Security Program

FIPS PUB 201-2 Federal Information Processing Standards Publication

201-2- Personal Identity Verification (PIV) of Federal

Employees and Contractors, August 2013

Form I-9, OMB No. 1615-0047 US Department of Justice, Immigration and Naturalization

Services, Form I-9, OMB No. 1615-0047 - Employment

Eligibility Verification

8.2.1 The scope of the contract will be limited up to UNCLASSIFIED. Performance of work will require access to unclassified data and computer resources within NAVOCEANO’s controlled workspaces and aboard T-AGS vessels.

8.2.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 an 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.

8.3 ACCESS CONTROL OF CONTRACTOR PERSONNEL

8.3.1 Physical Access to Government Facilities and Installations

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

(a) The majority of Government facilities require contractor personnel to have an approved visit request on file at the facility/installation security office prior to access. The Contractor will initiate and submit a request for visit authorization to the COR/DOCOR in accordance with DoD Manual 5220.22M, National Industrial Security

Program Manual not later than one (1) week prior to visit - timeframes may vary at each facility/installation. For visitation to all govt. locations, visit request documentation will be forwarded directly to the on-site facility/installation security office (to be identified at task order level) via approval by the COR/DOCOR or designated Government representative.

(b) Depending on the facility/installation regulations, contractor personnel will present a proper form of identification(s) and vehicle proof of insurance or vehicle rental agreement.

8.3.2 Identification and Disclosure Requirements

Contractors will take all means necessary to not represent themselves as Government employees. Contractors will comply with the following requirements for identification and disclosure purposes:

(a) Contractor personnel and their subcontractors will be clearly identifiable while on Government property as a contractor by visibly wearing appropriate identification/security badge.

(b) Contractor personnel and their subcontractors will immediately disclose and identify themselves as contractors (non-Government personnel) during meetings, telephone conversations, in electronic messages, or in correspondence related to this contract.

(c) If a contractor has designated space or an office located within Government facilities (on Department of the

Navy or other Government installations), such as offices, separate rooms, or cubicles, the entrance of the space will be clearly identified with Contractor supplied signs, name plates or other identification, showing that these are work areas for Contractor or subcontractor personnel.

8.3.3 Government Badge Requirements

While on government installations/facilities, contractors will abide by each site’s security badge requirements.

Various government installations are continually updating their security requirements to meet Homeland Security

Presidential Directive (HSPD-12) identification standards. Contractors are responsible for obtaining and complying with the latest security identification requirements for their personnel as required and are responsible for meeting the following:

(a) Upon issuance of badge, the contractor assumes full responsibility for the proper use of the identification badge and will be responsible for the return of the badge upon end of contract or termination of services.

(b) At the completion of the base contract or TO, the contractor will forward to the applicable security office all

Government badges issued under the contract and a list of any unreturned badges with a written explanation as to why the badge is missing.

8.3.4 Common Access Card (CAC) 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…