PerformanceWorkStatement_NAVOCEANO_SMENC_DRAFT.docx

DOCX document 51 KB Posted

Attached to
Hydrographic and Bathymetry Production Submarine Electronic Nautical Chart (SMENC) Support Services
Solicitation number
N0018925R0007
Issued by

About this file

This is a Performance Work Statement (PWS) for Hydrographic and Bathymetry Production Submarine Electronic Nautical Chart (SMENC) support services at the Naval Oceanographic Office (NAVOCEANO). The PWS outlines requirements for contractor support in collecting, editing, quality controlling, gridding, and managing hydrographic and bathymetric data for ocean and littoral zone depths.

The contract includes a one-year base period (June 2025-2026) with four one-year options and one six-month option, to be performed at NAVOCEANO in Stennis Space Center, MS. Key tasks include SMENC dataset preparation and compilation, shallow water dataset preparation, Digital Bathymetry Database Variable (DBDB-V) data load/administration, and data management. Contractors must complete individual project efforts within 15 business days and provide weekly and monthly status reports. Personnel must have relevant education/experience qualifying for OPM Physical Science Series standards and knowledge of UNIX/LINUX systems, geology, GIS, and mapping techniques. The work requires SECRET clearance and will be performed on-site without travel requirements. The government will provide workspace, equipment, hardware, software, and system access necessary for task completion.

View the file

Other files

On GovTribe

Work with this file

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

Text version

PERFORMANCE WORK STATEMENT

NAVAL OCEANOGRAPHIC OFFICE (NAVOCEANO)

HYDROGRAPHIC AND BATHYMETRY PRODUCTION

SUBMARINE ELECTRONIC NAUTICAL CHART (SMENC)

1.0 BACKGROUND:

The Naval Oceanographic Office (NAVOCEANO), Hydrographic Department collects, edits, quality controls, grids, and databases a wide variety of high-resolution hydrographic and bathymetric data. This information provides the most complete worldwide coverage of ocean and littoral zone depths.

2.0 SCOPE:

2.1 The contractor shall support several projects requiring discovery, extraction, management, integration, processing, editing, conversion, gridding, and quality control of hydrographic and bathymetric data.

2.2 Tasks shall include the following:

2.2.1 Submarine Electronic Nautical Chart (SMENC) Dataset Support: Contractor shall gather, extract, grid, edit, and quality control available source hydrographic and bathymetric data for the compilation of products to support the generation of SMENC datasets. Production support efforts consist of two subtasks, dataset preparation and dataset compilation, each of which has defined deliverables.

2.2.1.1 General Dataset Preparation: The contractor shall extract, combine, and edit hydrographic and bathymetric data.

2.2.1.1.1 Data extraction will consist of extracting data from in-house database resources based on a predefined area of interest (AOI) assigned at the Task Order level and data searches of data from publicly available sources for the given AOI converting the data from chart datum to mean sea level (MSL), and nominalize and convert data as necessary.

2.2.1.1.2 Data combination will consist of loading the extracted data files into Pure File Magic (PFM) file format.

2.2.1.1.3 Data editing will consist of reviewing PFM files, identifying features and hazards, addressing sensor systematic errors, and invalidating dataset outliers to provide accurate statistical gridded depth values. The contractor will also follow a template to keep a detailed log to document information from preparation through compilation.

2.2.1.1.4 The contractor shall hold a review, at a minimum, after the preparation and the compilation.

2.2.1.2 Shallow Water Dataset Preparation: Contractor shall gather, extract, grid, edit, and quality control all available source hydrographic and bathymetric data for the compilation of products to support the generation of shallow water datasets. Production support efforts consist of two subtasks, each of which has defined deliverables.

2.2.1.2.1 Data extraction will consist of extracting data from in-house database resources based on the area of interest (AOI) and converting the data from chart datum to mean sea level (MSL).

2.2.1.2.2 Data combination will consist of loading the extracted data files into PFM file format.

2.2.1.2.3 Data editing will consist of reviewing PFM files, identifying features and hazards, applying tides as defined at the Task Order Level, addressing sensor systematic errors, and invalidating dataset outliers to provide accurate statistical gridded depth values.

2.2.1.2.4 Final product generation involves producing required file formats and associated metadata and preparing for distribution to the customer. All deliverables will be defined by product and customer.

2.2.1.3 Dataset Compilation: The contractor shall extract, combine, contour, and generate final deliverables.

2.2.1.3.1 Data extraction will consist of extracting single beam sonar data from in-house database resources and NP4 provided sources based on the area of interest.

2.2.1.3.2 Data combination will consist of verifying dataset preparation package, adding and quality controlling single beam sonar data sources, creating gridded files, and data deconfliction.

2.2.1.3.3 Contouring of the gridded files will make use of automated contouring where multibeam coverage is available and hand contouring where multibeam coverage is lacking.

2.2.1.3.4 Final product generation involves producing required file formats and associated metadata in the correct resolutions and units to include Category Zones of Confidence (CATZOCs) of the data, completing the log file, and preparing for distribution to the customer.

2.2.2 Digital Bathymetry Database Variable (DBDB-V) Data Load: The contractor shall provide support for DBDB-V data load and administration.

2.2.2.1 The contractor shall assure the quality of incoming gridded datasets for database ingest.

2.2.2.2 The contractor shall populate the database with all incoming gridded datasets from Hydrographic Department production processes.

2.2.2.3 The contractor shall maintain the database such that the most recent or most accurate information is available for use.

2.2.2.4 The contractor shall provide documentation on datasets loaded which includes instituting version control, maintaining the historical load catalog and dataset backups.

2.2.2.5 The contractor shall assist with the preparation, testing, and the quality assurance of new releases of DBDBV.

2.2.2.6 The contractor shall maintain documentation on procedures processes used to complete these efforts.

2.2.3 Data Management: Contractor shall provide support (as described below) for the discovery, preparation and archival of hydrographic and bathymetric data within NAVOCEANO database resources and shall provide support for the QA of these database resources. For Public resources: Utilizes possible data sources (websites, etc..) that NP4 provides, contractor will research the available data, download, conduct preliminary process and archive the data utilizing NP4 established processes. Contractor may also perform the same tasking on non-public resources. At no time is the contractor performing outside of an NP4/NAVO approved process and therefore should not have the ability to claim intellectual rights.

2.2.3.1 The contractor shall locate and obtain (discovery) hydrographic and bathymetric data for inclusion within NAVOCEANO database resources. These data include those collected on NAVOCEANO survey operations as well as those that are were collected external to NAVOCEANO.

2.2.3.2 The contractor shall archive hydrographic and bathymetric data, associated metadata, and derived products within database resources.

2.2.3.3 The contractor shall identify abnormalities or errors within database resources and work with the Hydrographic Department to repair.

2.2.3.4 The contractor shall maintain documentation on procedures processes used to complete these efforts.

3.0 BACKGROUND:

3.1 PERFORMANCE PERIOD:

The resultant task order will consist of a one-year base period, four (4) one-year option periods, and one (1) six-month option period (to account for the FAR 52.217-8 “Option to Extend Services” clause). The performance periods are as follows:

· Base Period: 21 June 2025 through 20 June 2026

· Option I: 21 June 2026 through 20 June 2027

· Option II: 21 June 2027 through 20 June 2028

· Option III: 21 June 2028 through 20 June 2029

· Option IV: 21 June 2029 through 20 June 2030

· Option V: 21 June 2030 through 20 December 2030 ***

*** Option V represents services covered under FAR 52.217-8 “Option to Extend Services” – which shall not exceed six (6) months.

3.2 RECOGNIZED HOLIDAYS/GOVERNMENT CLOSURE:

Federal law (5 U.S.C. 6103) establishes the public holidays for federal employees. Any other day designated by federal statute, executive order, presidential proclamation and/or local determinations relating to adverse weather conditions, national emergencies, administrative closings, or similar Government directed facility closings may require office closure. During such periods of closure, contractor employees will not be allowed to work nor will the contractor be compensated, however, offsite work is allowed, with Contracting Officer's (KO) approval, on a case-by-case basis when mutually agreed upon by the Government and the contractor.

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

3.3 HOURS OF OPERATION:

The contractor is responsible for performing support services during an 8-hour workday between the hours of 0700 and 1630, Monday through Friday, or during core business hours when the provided Government workplace is open, except as stated in Section 3.2 “Recognized Holidays/Government Closure. The contractor must always maintain an adequate work force for the uninterrupted performance of all tasks defined within this performance work statement when the Government facility is not closed for the aforementioned reasons. The stability and continuity of the work force are essential.

4.0 PLACE OF PERFORMANCE:

The contractor shall perform services at the Government site:

Naval Oceanographic Office (NAVOCEANO) 1002 Balch Boulevard Stennis Space Center, MS 39525

NOTE: Performance under the resultant task order will NOT require travel by the contractor.

5.0 PERSONNEL EDUCATION/EXPERIENCE REQUIREMENTS:

5.1 Contract personnel associated with this effort shall have the following level of education and experience:

5.1.1 All contractor personnel conducting SMENC and Shallow Water production support efforts shall have, at minimum, the combination of education and experience required to qualify for the Office of Personnel Management (OPM) General Schedule Qualifications Standard, General Physical Science Series 1301. These personnel shall also have base knowledge of the IT system utilization and related sciences more specifically of the UNIX / LINUX based operating systems, geology, seafloor process, tectonics, and geomorphology along with Geographic Information Systems (GIS), mapping techniques, contouring and gridding methods.

5.1.2 All contractor personnel conducting DBDB-V data load / administration and data management efforts shall have, at minimum, the combination of education and training required to qualify for the Office of Personnel Management (OPM) General Schedule Qualifications Standard, Physical Science Technician Series 1311 at or above the GS4 level. These personnel shall also have base knowledge of the IT system utilization and related sciences more specifically of the UNIX / LINUX based operating systems, relational databases, Geographic Information Systems (GIS) and geospatial datasets.

6.0 PROGRAM MANAGEMENT:

6.1 The contractor shall provide program and project management support as follows:

6.1.1 The contractor shall assign a Program Manager (PM)/Contract Manager (CM) to act as the single primary interface with NAVOCEANO COR. The PM/CM specifically has the responsibility of interfacing with the COR on all matters pertaining to this Performance Work Statement (PWS). The PM/CM shall direct the individual contractor employee’s effort through the company’s internal management system; this management system shall provide project progress visibility to assure on-time completion of all requirements.\

6.1.2 The contractor shall utilize standard processes based on industry best practices wherever applicable.

6.1.3 The contractor shall sponsor quarterly program management reviews to monitor contractor performance and discuss any issues that the contractor and/or NAVOCEANO are experiencing with the project referenced herein with the COR and Contracting Office. NAVOCEANO COR will schedule this review; submit a suggested agenda to the contractor who shall be responsible for all briefing slides and materials.

6.1.4 The contractor shall support other NAVOCEANO briefings and meetings as applicable by providing feedback and documentation/numbers concerning any efforts.

7.0 DELIVERABLES:

Specific deliverables are required for each task area (mentioned in each subsection of section 2). Deliverables shall be submitted to the COR. In addition to task area deliverables, administrative deliverables are also required. Additional deliverables are specified and/or defined throughout SECTION 8 (SMENC Production Support) per identified requirement.

7.1 The COR will accept or reject the deliverables in writing or via email.

7.1.2 The COR will have thirty (30) business days to complete its review of the deliverables. If notification of acceptance is not provided to the contractor within thirty (30) business days, the deliverables will be deemed accepted.

7.1.3 In the event of the rejection of any deliverable, the contractor shall be notified in writing by the COR, giving the specific reason(s) for rejection. The contractor will be allowed five (5) business days to correct the rejected deliverable and return it to the COR.

7.1.4 The contractor shall also submit a monthly status report by the 15th of each month. This report shall be in sufficient detail such that it allows NAVOCEANO to determine and assess the contractor’s technical progress. The format of this report must be reviewed by the COR. Each report shall address information taking place during the previous month including projects assigned / completed / pending for each task, number of hours expended per task, accomplishments per individual for each task, number of projects completed on schedule, number of projects delayed and reasoning, and all problems or issues encountered.

7.1.5 The contractor shall submit weekly status emails by close of business on the first day of each week. Each weekly report shall cover the previous workweek including an overall summary of project activity specific to each task. The stage of each project shall be reported. Any problems or issues encountered shall be reported to the COR.

8.0 SMENC PRODUCTION SUPPORT:

8.1 SMENC dataset preparation efforts will vary in complexity between projects. Each individual project effort shall not exceed fifteen (15) business days barring major issues with software, hardware, or the actual effort. Issues that could affect production timelines need to be communicated with COR.

8.1.1 SMENC dataset preparation deliverables include fully edited PFM files, hazard / feature identification files, navigation files, log files, coverage files by CATZOC, and all associated metadata. Detailed listings of file types and content will be provided by the COR.

8.1.2 Final acceptance will consist of reviewing the dataset preparation package to ensure the following:

8.1.3 Datasets have been edited such that all dataset outliers have been removed.

8.1.4 Uncertainty of gridded values is appropriate for loaded and edited data.

8.1.5 All available multibeam sonar data have been incorporated.

8.1.6 Metadata regarding the datasets included in the effort has been annotated in a log file.

8.1.7 Data backups are stored at the designated location.

8.2 SMENC dataset compilation efforts will vary in complexity between projects. Each individual project effort shall not exceed fifteen (15) business days barring major issues with software, hardware, or the actual effort. Issues that could affect production timelines need to be communicated with the COR.

8.2.1 SMENC dataset compilation deliverables include fully edited gridded files compiled from all sources (multibeam, single beam, hand contours, and other data), swath coverage vector files with CATZOC, contour vector files, hard copy / digital plot files, and project documentation. Detailed listings of file types and content will be provided by the COR.

8.3 Final acceptance will consist of reviewing the dataset compilation package to ensure the following:

8.3.1 Datasets have been edited such that all dataset outliers have been removed.

8.3.2 Single beam sonar data have been incorporated and deconflicted with multibeam sonar data.

8.3.3 Contours are drawn into sparse data coverage areas are appropriate based on all available data.

8.3.4 Product area has been deconflicted with surrounding product data.

8.3.5 Uncertainty of gridded values is appropriate for loaded and edited data.

8.3.6 All data sources are organized and reside at the designated location.

8.3.7 Metadata regarding the datasets included in the effort has been annotated in a log file.

8.3.8 Digital plot, project documentation, and product deliverables have been prepared.

8.3.9 Data backups are stored at the designated location.

8.4 Shallow Water Bathymetry in Support of SMENC:

8.4.1 Shallow water dataset preparation efforts will vary in complexity between projects. Each individual project effort shall not exceed fifteen (15) business days barring major issues with software, hardware, or the actual effort. Issues that could effect production timelines need to be communicated with the COR

8.4.1.1 Shallow water dataset preparation deliverables include fully edited PFM files, hazard / feature identification files, navigation files, log files, coverage files by CATZOC, and all associated metadata. Detailed listings of file types and content will be provided by the COR.

8.5 Final acceptance will consist of reviewing the dataset preparation package to ensure the following:

8.5.1 Datasets have been edited such that all dataset outliers have been removed and tides have been applied.

8.5.2 Uncertainty of gridded values is appropriate for loaded and edited data.

8.5.3 All NAVOCEANO and trusted source multibeam sonar data have been incorporated.

8.5.4 Metadata regarding the datasets included in the effort has been annotated in a log file.

8.5.5 Data backups are stored at the designated location.

8.8 Digital Bathymetry Database Variable (DBDB-V) Data Load and Administration:

8.8.1 DBDB-V load graphics shall be generated once per database version.

8.8.2 Process and procedure documentation shall be generated or updated once per task order. The format for these documents shall be agreed upon by the COR and contractor’s PM/CM.

8.8.3 DBDB-V load records shall be provided once per database version.

8.8.4 DBDB-V load metrics shall be provided to the COR once every twenty (20) business days.

8.9 DATA MANAGEMENT

8.9.1 Process and procedure documentation shall be generated or updated once per task order. The format for these documents shall be agreed upon by the COR and contractor’s PM/CM.

8.9.2 Data Management metrics shall be provided to the COR once every twenty (20) business days.

9.0 GOVERNMENT PROVIDED RESOURCES:

9.1 NAVOCEANO shall provide working space, office equipment, hardware, and software necessary for the completion of the assigned tasks.

9.1.1 All materials furnished to the contractor and any materials purchased with the Government funds in support of this effort will be returned to NAVOCEANO as directed, or upon completion of this project.

9.1.2 All data and software provided to the contractor shall only be used under the terms of fulfilling their contractual obligations. All data and software shall be transitioned back to NAVOCEANO upon project completion or contract performance period. Upon delivery all original and derived data and products are returned to NAVO and removed from contractor holdings

9.1.3 In addition to the equipment and property mentioned above, the following shall be provided by

NAVOCEANO:

9.1.4 Standard Operating Procedures (SOPs) for SMENC production support and Shallow water bathymetry production support efforts. Guidance documents will be provided for DBDB-V data load / administration and data management tasking.

9.1.5 Computer accounts to unclassified and classified systems within the scope of the work and necessary for the completion of this effort including NAVOCEANO's classified and unclassified scientific network and Navy Marine Corps Intranet (NMCI) systems.

9.1.6 System access for scientific workstations will be provided by NAVOCEANO within thirty (30) business days of the contractor completing all required security training, security application paperwork, and system access requests.

9.1.7 Access to the data holdings necessary for the completion of this effort.

9.1.8 Access to data holdings will be granted upon receipt of required scientific computer accounts.

9.1.9 Designated NAVOCEANO personnel to provide tasking familiarization and to coordinate / facilitate project efforts.

9.1.10 Familiarization for new contract employees shall consist of SOP review and software orientation. The duration of this familiarization shall be at the discretion of NAVOCEANO and shall not exceed five (5) business days

Deliverable
Frequency
Format
Due Date
Mission Priority
Monthly Status Report
Monthly
MS Word
15th business day following the close of calendar month
High
Weekly Status Report
Weekly
MS Word
Close of business on the first day of each week
High
SMENC dataset preparation efforts as described in PWS
Individual Project Effort Final Acceptance
As described in PWS
NTE fifteen (15) Business Days
High
SMENC dataset compilation efforts as described in PWS
Individual Project Effort Final Acceptance
As described in PWS
NTE fifteen (15) Business Days
High
Final Quality Control Plan Approval
Once
Word, Excel
Thirty (30) days after contract award
High

10.0 SECURITY REQUIREMENTS:

10.1 The scope of work outlined in this PWS (and resultant task order) will be limited to SECRET. A DD Form 254, Department of Defense (DoD) Contract Security Classification Specification is applicable to this action and a draft version of this document will be included in any resultant solicitation and the finalize version of this document will be included in the resultant task order. Performance of work will require access to classified data and computer resources within NAVOCEANO’s controlled workspaces. Facility Level Clearance shall be the same or above contract requirement. Security clearances are required at time of award.

10.1.2 All contract personnel shall comply with the directives and policies established in 32 CFR Part 17 “National Industrial Security Program, Operating Manual”, SECNAVINST 5510.30C “Personnel Security Program”, and SECNAVINST 5510.36B “DoN Information Security Policy”. All contractors will be required to obtain and maintain a SECRET clearance.

10.1.3 All contractors require non-critical sensitive information access as defined in the reference listed above. All contract personnel shall complete applicable cybersecurity training, sign non-disclosure agreements, and complete System Authorization Access Request Navy (SAAR-N) forms before accessing any Navy Information Technology resources. All training and documentations shall be forwarded to the COR immediately upon assignment. Failure to provide the required documentation shall result in delaying the individual’s start date.

10.1.4 The contractor shall ensure the required security training, security application paperwork, and system access requests for all new employees are submitted to NAVOCEANO in sufficient time such the required facility and system access credentials can be provided by NAVOCEANO prior to the contractor reporting to the facility.

10.1.5 All contract personnel shall in-process with the Navy Command’s Security Manager and Information System Security 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.

10.1.6 All information, products delivered, or services performed may not be disclosed by any means without prior approval of the authorized 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.

10.1.7 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 nonsensitive positions, with sensitive information, and/or on Government IT systems. The contractor shall insert this section 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.

10.2 Physical Security: The contractor shall be responsible for safeguarding all Government property provided for contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

10.2.1 Key Control: The contractor shall establish and implement methods of making sure all keys/key cards issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

NOTE: All references to keys include key cards. No keys issued to the contractor by the Government shall be duplicated. The contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

10.2.2 In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the contractor.

10.2.3 The contractor shall prohibit the use of Government issued keys/key cards by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

10.2.4 Lock Combinations: The contractor will be provided the combination to the X-series lock and the passcode to the intrusion detection system. The contractor shall be required to periodically open the space and secure the space, depending on the schedules of the Government personnel in the space. The contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the contractor’s Quality Control Plan.

10.2.5 IT Systems Access: When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information System Security 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. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources.

10.2.6 When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual cybersecurity training, and maintain a current requisite background investigation. The contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

10.2.7 The potential consequences of any requirements under this clause including denial of access for a proposed contractor employee who fails 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 section 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.

11.0 QUALITY CONTROL/ASSURANCE:

11.1 The contractor shall perform inspections prior to requesting acceptance of the work by NAVOCEANO. Contractor-performed inspections are independent of those performed by the Government.

11.2 The contractor’s Program Manager shall attend meetings with the COR and other NAVOCEANO personnel to resolve quality considerations and problems that may arise in the course of the work.

11.3 The contractor shall submit a Final Quality Control Plan (QCP) to the COR for approval within thirty (30) days after contract award. The QCP will outline the contractor’s inspection system and method(s) of documentation.

11.4 Quality Assurance. The COR will inspect for compliance with Contract terms throughout the Contract period. Evaluation will be based on the Contractor’s compliance with the requirements set forth in the Quality Assurance Surveillance Plan (QASP). The Government will monitor the Contractor's performance under this Contract by performing surveillance using the QASP. The QASP is used primarily to determine if the Contractor is performing all required outputs. The QASP also indicates for contractors the importance of each required service.

11.5 DFARS 222.17 mandates including surveillance for ensuring compliance with Combatting Trafficking in Persons (CTIP) in the QASP. The COR will monitor the contractor’s performance regarding trafficking in persons through the checklist for auditing compliance with CTIP policy found at DFARS PGI 222.17. Such noncompliance with FAR clause 52.222-50, Combating Trafficking in Persons, will be brought to the immediate attention of the contracting officer. See the DoD CTIP website (https://ctip.defense.gov) for further information.

12.0 CYBERSECURITY/INFORMATION SECURITY:

Contractor shall protect DoD classified and sensitive/controlled unclassified data regardless of the location or ownership of the transport media, including, but not limited to mobile computing devices and removable storage media, whether Government furnished or contractor owned/leased. Contractor shall comply with all current cybersecurity and information security policies, procedures, and statutes applicable to DoD information technology, including the DoD Instruction 8500.01, Cybersecurity, 14 March 2014, Change 1, 7 October 2019.

13.0 IDENTIFICATION REQUIREMENTS:

All contractor personnel performing under this statement of work shall identify themselves as a contractor employee to avoid creating any impression that they are Government officials. Such identification shall be made in all meetings attended, when answering Government telephones, on all e-mails, and when working in other situations where their contractor status is not obvious to third parties. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

14.0 IT SYSTEMS ACCESS:

14.1 When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Cybersecurity 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. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least thirty (30) days prior to the individual’s start date. Failure to provide the required documentation at least thirty (30) days prior to the individual’s start date shall result in delaying the individual’s start date.

14.2 When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual cybersecurity training, and maintain a current requisite background investigation. The Contractor’s Facility Security Officer (FSO) shall contact the Defense Counterintelligence Security Agency (DCSA) for guidance when reinvestigations are required.

14.3 The potential consequences of any requirements under this clause including denial of access for a proposed contractor employee who fails 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.

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