Draft_SOW.docx

DOCX document 73 KB Posted

Attached to
Mapping and Cartographic Services Federal contract opportunity
Solicitation number
EA-133C-17-RQ-0277
Issued by
Department of Commerce National Oceanic and Atmospheric Administration

View the file

On GovTribe

Work with this file on GovTribe

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

Text version

STATEMENT OF OBJECTIVES

Mapping and Cartographic Services

U.S. Department of Commerce National Oceanic & Atmospheric Administration Office of Coast Survey Marine Chart Division

1. Program Goals and Objectives

The Marine Chart Division (MCD) of the Office of Coast Survey (OCS), National Ocean Service (NOS), National Oceanic & Atmospheric Administration (NOAA), a bureau of the U.S. Department of Commerce, maintains a Nautical Chart System (NCS) that underpins production of NOAA nautical charts, which are tools for safe, efficient and environmentally sound navigation in U.S. waters. Our mission is to provide charts and chart products for use in the maritime transportation system that moves over two thirds of all consumer goods purchased in the United States.

MCD’s current Nautical Chart System consists of two production systems that maintain and generate nautical chart products for commercial and recreational mariners. The Nautical Chart System I (NCS I) and the Nautical Chart System II (NCS II) are being used in tandem to create all of MCD’s products and maintain MCD’s suite of 1024 charts.

NCS I

Raster products - multiple formats

-Raster Nautical Charts (RNC’s) distributed electronically in various file formats
-Print On Demand (POD) charts, are paper charts available for purchase through POD agents
-Raster chart tile sets which provide the base for a seamless RNC chart server and web service for Geographic Information System (GIS) users

The vast majority of raster charts (98%) are produced using software from Bentley Systems and output in a raster format. The latest version of Bentley Map Enterprise Select Series 3 software is used to support production of nearly all raster products, with the exception of a handful of charts built through the Chart Template Process of the NCS II system. All raster products feed into all other raster formats that are processed by the Format and Distribution System (FADS) Branch.

The NCS I system (Bentley software) will be retired when all raster charts have been converted to Chart Templates from the NCS II system. Chart Templates are created from the Nautical Information System (NIS) database and are also output in a raster format. The current timeline for all raster charts to be converted to chart templates is 4-5 years.

NCS II

Vector products - multiple formats

-Electronic Nautical Charts (ENC’s) distributed electronically
-ENC’s Direct to GIS
-ENC’s Online
-NCS II Chart Templates

ENC’s are produced using ArcGIS Maritime Solution software that has been developed by ESRI for Hydrographic Office users. MCD is in the process of migrating ENC production from cell-based (Amoeba) to a seamless single Nautical Information System (NIS) Database solution, the Nautical Chart System II (NCS II). The migration of ENC’s to the NIS database is expected to conclude in 2018. ENC’s are downloadable online in various GIS/CAD formats and viewable through the ENC Online website.

MCD is approximately two-thirds through the migration of all ENC’s to the NIS which will allow all vector and raster production from a single Nautical Information System (NIS) database solution. The remaining work to be finished before the NCS II system is fully capable to output all products, is to complete the creation of the chart template suite.

The NCS I and NCS II programs conform to special work instructions, guidelines, Standard Operating Procedure’s (SOP’s), Task Assistant Manager (TAM’s) documentation, specifications and standards contained in the MCD Nautical Chart Manual (NCM), Chart 1 Nautical Chart Symbols, Abbreviations, and Terms publication, MCD websites and Document Registries. ENC production also conforms to the International Hydrographic Organization Standard S-57, Transfer Standard for Digital Hydrographic Data, Edition 3.0 including Appendix B.1, the ENC production specifications and the most current version of Appendix B.1 Annex A, Use of the Object Catalog for ENC.

Through the use of a Product Library, individual updated feature objects from the seamless database will be correctly replicated to the appropriate product geo-databases. This system will be capable of receiving and processing data from various sources, and have enough versatility to build nautical products needed by the maritime community to support safe navigation, including ENC, Raster, and support public Paper chart products as well as producing weekly Critical updates. In addition, this system will be used to build NCS II chart templates in support of raster products and to support the transition effort from NCS I to NCS II.

2. Overview of Activities and Results

The services are required to supplement the MCD nautical charting program existing staff, processes for continual maintenance of nautical source application, and modernization of existing raster and vector chart files. The Contractor shall prepare a management plan describing the performance and management of this work, including use of resources and personnel to be furnished in the performance of compilation within the traditional Bentley paper chart NCS I system and the ArcGIS Electronic Navigational Chart (ENC) NIS database NCS II system for MCD. The plan shall address workload expansion, mitigation for instances of high personnel turnover, and labor categories and rates Adequate experienced personnel are required at all times in all areas. The plan shall address changes in charting policy, technology, software, (the transition from NCS I to NCS II) and equipment that will occur during the life of this contract. The plan shall address personnel training on existing MCD software and changes in technology, software and equipment during the life of this contract.

The Contractor shall provide all services necessary to receive, review and process source data for the following:

A. Maintenance of Bentley Map based vector and raster files

B. Maintenance of ArcGIS based vector files for Electronic Navigational Chart cells in the NIS database through application of source data

C. Creation and Maintenance of ArcGIS based Templates for Electronic Navigational Chart cells in the NIS database through application of source data

3. Detail of Activities and Results

A. Maintenance of Bentley Map based vector and raster files

Contractors will provide program support to the Marine Chart Division’s Raster Nautical Chart suite sufficient to update and maintain nautical chart source data through the use of the Bentley MAP Enterprise software system. Bentley MAP Enterprise software is a desktop Geographic Information Systems (GIS) product for viewing and editing. MCD uses Bentley MAP to edit and manipulate geo-referenced chart composite files which consist of raster plate (.cit) files and vector design (.dgn) files for a suite of over 1000 nautical charts and nautical chart products. Bentley MAP integrates MCD’s IRASB software, Critical database, Hydro survey and Geographic Cell schema’s in order to provide critical updates for Notice to Mariner’s and to perform routine maintenance within MCD’s raster suite. Program support includes all services necessary to analyze, review and process source data into the chart composite files according to the Nautical Chart Manual and acceptable hydrographic practices.

Source data consists of, but is not limited to:

· Blue Prints (BP’s) – Consisting of various formats in analog or digital form from various private or Government agencies and providing data for various types of surveys which may include but are not limited to U.S. Army Corps of Engineers (USACE) channel surveys, private agency drawings for bridges, overhead and submerged pipelines and cables, wharfs, piers, harbor facilities, etc.

· Database Data (DB’s) – Consisting of reports from U.S. Power Squadrons on the conditions of chart features that are found to be inconsistent with real world conditions. Features consist of but are not limited to, land and water features such as tanks, wind turbines, water depths, piers, ramps, buildings, obstructions, rocks, wrecks, platforms, towers, cables, etc.

· Letters (L’s) – Consisting of various formats in analog or digital form from various private or Government agencies (Internal and External) and providing data for various types of land and water information. Letters are typically associated and referenced to other types of data which include but are not limited to, Blue Prints, Letters, Field Exams, Geographic Cells, Hydrographic surveys, and Chart Forwards. Letters typically contain the metadata and analog data to be used in reference and conjunction to other source data for proper compilation. Letter information may include but not be limited to USACE Channel Condition Reports (CCR’s) and tabulations, authorization of new charts or chart cancellations, MCD chart policy letters, USACE anchorages and basins, overhead and submerged cables and pipelines, bridges, wrecks, boundaries and limit lines, tides, chart forwards, channel legends, platforms, shoals, rocks, obstructions, wrecks, tanks, towers, stacks, buildings, geographic names, fish havens, aquaculture, landmarks, etc.

· Digital Data (DD’s) – Consisting of various digital formats from various private or Government agencies (Internal and External) and providing data for various types of land and water information. DD’s are typically associated and referenced to other types of data which include but are not limited to, Blue Prints, Letters, Field Exams, Geographic Cells, Hydrographic surveys, and Chart Forwards. DD’s contain the digital form of the data to be ingested into Bentley Map composite files or the NIS.

· Field Exam (FE’s) – Consisting of various formats of analog and digital data from various private or Government agencies and providing data for Hydrographic surveys of limited scope. FE’s are investigations of specific features, such as obstructions, rocks, and wrecks, or basic hydrographic surveys of limited extent.

· Hydrographic Survey (H’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for hydrographic conditions. A Hydrographic Survey is a complete and thorough survey of the seafloor. For charting purposes, a Hydrographic survey must be adequate to supersede all prior surveys of the same area. A Hydrographic survey verifies or disproves the existence of all charted or reported features of significance.

· W Survey (W’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for hydrographic conditions. W surveys are outside source surveys that have not been acquired under an official Hydrographic Surveys Division (HSD) project and may be evaluated for use in nautical charting.

· Geographic Cell (GC’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for topography, including but not limited to, shoreline, low water line, land-water interfaces, man-made features, etc. GC’s may also consist of near shore Topobathymetry. Topobathymetric data (“topobathy”) are a merging and rendering of both topography (land elevation) and bathymetry (water depth) to provide a single product useful for nearshore mapping and a variety of other applications.

B. Maintenance of ArcGIS based vector files for Electronic Navigational Chart cells in the NIS database through application of source data

Contractors will provide program support to the Marine Chart Division’s NIS sufficient to update and maintain ENC source data. This includes all services necessary to analyze, review, and process source data into the ENC cells in the NIS database according to the Nautical Chart Manual and acceptable hydrographic practices. ENCs are produced using ArcGIS Maritime Solution software that has been developed by ESRI for Hydrographic Office users. NOAA is in the process of migrating ENC production from a cell-based to a single database solution (NCSII). Through the use of a Product Library, individual updated feature objects from the seamless database will be correctly replicated to the appropriate product geo-databases. This system receives and processes source data from various private and Government agencies to build nautical products needed by the maritime community to support safe navigation, including ENC, Raster, and Paper as well as producing weekly Critical updates.

Source data consists of, but is not limited to:

· Blue Prints (BP’s) – Consisting of various formats in analog or digital form from various private or Government agencies and providing data for various types of surveys which may include but are not limited to U.S. Army Corps of Engineers (USACE) channel surveys, private agency drawings for bridges, overhead and submerged pipelines and cables, wharfs, piers, harbor facilities, etc.

· Database Data (DB’s) – Consisting of reports from U.S. Power Squadrons on the conditions of chart features that are found to be inconsistent with real world conditions. Features consist of but are not limited to, land and water features such as tanks, wind turbines, water depths, piers, ramps, buildings, obstructions, rocks, wrecks, platforms, towers, cables, etc.

· Letters (L’s) – Consisting of various formats in analog or digital form from various private or Government agencies (Internal and External) and providing data for various types of land and water information. Letters are typically associated and referenced to other types of data which include but are not limited to, Blue Prints, Letters, Field Exams, Geographic Cells, Hydrographic surveys, and Chart Forwards. Letters typically contain the metadata and analog data to be used in reference and conjunction to other source data for proper compilation. Letter information may include but not be limited to USACE Channel Condition Reports (CCR’s) and tabulations, authorization of new charts or chart cancellations, MCD chart policy letters, USACE anchorages and basins, overhead and submerged cables and pipelines, bridges, wrecks, boundaries and limit lines, tides, chart forwards, channel legends, platforms, shoals, rocks, obstructions, wrecks, tanks, towers, stacks, buildings, geographic names, fish havens, aquaculture, landmarks, etc.

· Digital Data (DD’s) – Consisting of various digital formats from various private or Government agencies (Internal and External) and providing data for various types of land and water information. DD’s are typically associated and referenced to other types of data which include but are not limited to, Blue Prints, Letters, Field Exams, Geographic Cells, Hydrographic surveys, and Chart Forwards. DD’s contain the digital form of the data to be ingested into Bentley Map composite files or the NIS.

· Field Exam (FE’s) – Consisting of various formats of analog and digital data from various private or Government agencies and providing data for Hydrographic surveys of limited scope. FE’s are investigations of specific features, such as obstructions, rocks, and wrecks, or basic hydrographic surveys of limited extent.

· Hydrographic Survey (H’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for hydrographic conditions. A Hydrographic Survey is a complete and thorough survey of the seafloor. For charting purposes, a Hydrographic survey must be adequate to supersede all prior surveys of the same area. A Hydrographic survey verifies or disproves the existence of all charted or reported features of significance.

· W Survey (W’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for hydrographic conditions. W surveys are outside source surveys that have not been acquired under an official Hydrographic Surveys Division (HSD) project and may be evaluated for use in nautical charting.

· Geographic Cell (GC’s) - Consisting of various formats of analog and digital data from various private or Government agencies and providing data for topography, including but not limited to, shoreline, low water line, land-water interfaces, man-made features, etc. GC’s may also consist of near shore Topobathymetry. Topobathymetric data (“topobathy”) are a merging and rendering of both topography (land elevation) and bathymetry (water depth) to provide a single product useful for nearshore mapping and a variety of other applications.

C. Creation and Maintenance of ArcGIS based Templates for Electronic Navigational Chart cells in the NIS database through application of source data

Contractors will provide program support to the Marine Chart Division to build paper chart templates to support the transition effort from NCS I system to NCS II system and to provide maintenance of the NCS II system. Nautical chart products intended for paper and raster application are created by extracting nautical data from the NIS into individual product file geodatabases (FGDB’s) and Map Documents (MXD’s) in a similar manner as ENC products. Program support includes all services necessary to analyse, review and process chart templates which are created using predefined definition queries and Areas Of Interest (AOI’s) set in the Product Library, extracting data from the ArcGIS NIS that is related to the selected paper chart into Chart Template product FGDB’s. The chart template FGDB’s will undergo feature symbolization, representation, annotation, patterning, notation, stylization, gridding, creation of surround elements, and chart finishing in accordance with established SOP’s and Task Assistant Manager (TAM’s) documentation. The resulting finished FGDB’s and their corresponding MXD’s will undergo contractor peer review to measure and correct the chart templates against the existing ENC’s and raster paper charts for accuracy, precision and correctness according to the standards set herein and upon passing peer review, delivered to the Government.

4. Deliverables

A. Maintenance of Bentley Map based vector and raster files

Deliverable - Updated raster plate (.cit) files and vector design (.dgn) files for each chart panel of each type of source application listed below

Estimated Number of Source Documents per Year
Delivery Date
Deliver to
Reference
Blue Prints
1
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
DataBase Data (DB)
14
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
Letters
1803
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
Digital Data
1602
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
Field Exam
15
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
GC
132
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
Hydro
125
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
W
26
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A
Forwards
15
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, A

B. Maintenance of ArcGIS based vector files for Electronic Navigational Chart cells in the NIS database through application of source data

Deliverables - Updated File Geodatabases (FGDB’s of Checkout Replicas or Edit Versions extracted from the NIS) for each chart panel of each type of source application or combination of source applications listed below

Estimated Number of Source Documents per Year
Delivery Date
Deliver to
Reference
Blue Prints
1
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
DataBase Data (DB)
14
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
Letters
1803
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
Digital Data
1602
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
Field Exam
15
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
GC
132
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
Hydro
125
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
W
26
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B
Forwards
15
Within 10 days of assignment or within an establish delivery schedule
COR
Section 3, B

C. Creation and Maintenance of ArcGIS based Templates for Electronic Navigational Chart cells in the NIS database through application of source data

Deliverables - NCS II Template for each chart. The template shall follow the MCD SOP’s for creating NCS II chart templates and be baselined against the existing RNC

Estimated Number of Templates per Year

Delivery Date
Deliver to
Reference
Template Map Documents (MXD’s) and Template Geo-Database files (GDB’s) for each chart panel requested
10
Within 25 days of assignment or within an establish delivery schedule
COR
Section 3, C

5. Quality and Performance Standards:

All services shall be provided at a level of quality that consistently meets the requirements set forth herein. Any and all interaction with the public must be coordinated and approved by the COR. The performance standards associated with the areas of responsibility are included in the description below and the following publications:

Quality

NOS/OCS/MCD Nautical Chart Manual Policy-Charting http://www.charts.noaa.gov/nauticalchartmanual/

Chart 1 Nautical Chart Symbols, Abbreviations, and Terms publication
http://www.nauticalcharts.noaa.gov/mcd/chartno1.htm
International Hydrographic Organization Standard S-57, Transfer Standard for Digital Hydrographic Data, Edition 3.0 including Appendix B.1
http://www.iho-ohi.net/english/home/
NCS II SOP for Creating Templates
Online, continually maintained version available from Office of Coast Survey

Performance Standards

The contractor shall have 10 business days from the date the Government assigns a typical source document application to the contractor to complete and submit the source document application for Government review for activities A and B.

Atypical source documents may require more than 10 business days to complete, and undergo a more thorough examination for the establishment of delivery dates. The contractor shall have 5 business days to notify the Government if the contractor estimates a particular source document application will take longer than the specified 10 days or established delivery date. In such cases, the Government will re-assess the level of effort necessary to complete the source application and notify the contractor of the new due date to complete the source application and submit for Government review.

The contractor shall have 25 business days from the date the Government assigns a typical NCS II chart template for compilation and submit the NCS II template for Government review for activity C.

Atypical chart templates that may require more than 25 business days to complete and submit for review, may undergo a more thorough examination for the establishment of delivery dates which may require further adjustment. The contractor shall have 5 business days to notify the Government if the contractor estimates a particular source document application will take longer than the specified 25 business days or established delivery date. In such cases, the Government will re-assess the level of effort necessary to complete the source application and notify the contractor of the new due date to complete and submit for Government review.

The Government may also have time-sensitive critical source document applications that will need to be applied sooner than the stated 10 business days. In such cases the Government will notify the contractor that the time sensitive source document application is required to completed and submitted in 2 business days. The Government anticipates approximately 30-time sensitive critical source document applications a year.

All source delivery dates will be established and managed through the use of the Document Source Registry (DREG) and the Geo-Referenced Source Registry databases (GREG). All source document application errors, returns, due date change requests, and any delays in submitting source document applications for review will be tracked by the Government on a monthly basis through the use of DREG and GREG. DREG and GREG will be used in conjunction with monthly progress reports to monitor and assess contract performance.

The criteria the Government will use to define errors in contractor source documentation application are as follows: Unacceptable due to critical correction errors; unacceptable due to non-critical correction errors; unacceptable due to both critical and non-critical correction errors. A critical correction error will be defined in three ways:

A. The contractor submits a source document application and does not write a Notice to Mariner report and the Government identifies that a Notice to Mariner report should have been generated by the contractor B. The contractor submits a source document application which required a Notice to Mariner report and the Government identifies an error with the Notice to Mariner report generated by the contractor.

C. The Government identifies a critical error in the contractor source document application that requires a Notice to Mariner report to be generated if the chart were to be published.

The Contractor shall have 2 business days to correct all source document application errors called for by the Government. If the contractor feels the corrections called for by the Government will take longer than 2 days because of difficulty or the amount of corrections precludes the source application from being completed within the 2-day standard timeframe, the contractor shall forward an extension request to the Government for approval through the use of the DREG and GREG.

All source document applications will be reviewed to determine adherence to the standards listed herein. The contractor shall be required to comply with these standards and specifications for both deliverables (ENC and Raster) submitted to MCD for review.

The contractor is responsible for identifying any piece of source that has inconsistencies/problems or any unresolved conflicts not covered by the Nautical Chart Manual, Chart 1, or any references listed in section 3. When a contractor identifies this type of source document, they are required to notify a MCD Reviewer or Government designated Point of Contact (POC) for clarification within 5 business days. The MCD reviewer or POC may in turn forward this issue to the Quality Assurance Standards and Plans Branch or the Nautical Data Branch where a decision will be reached. The source item will be put on hold until further documentation is generated to address the issue identified by the contractor.

The Government will provide the contractor documentation citing the reasons for any correction errors called for in the contractor’s source document application by way of reference to the relevant nautical charting standards.

The Government will review all source document applications submitted by the contractor which require critical corrections within 15 business days. The Government will review all source document applications submitted by the contractor which do not require critical corrections (non-critical) within 20 business days unless the size and/or difficulty of the source application requires a non-standard amount of time for review such as some geographic cells and hydrographic surveys.

6. Monthly Progress Report

Each invoice shall be accompanied by a progress report that clearly summarizes the following:

A. Activities and accomplishments during billing period B. Anticipated activities/accomplishments during next 30-days C. An on-going list of deliverables required and submitted (as set forth in this SOW)

Each report shall separately identify each activity and project including performance objectives, accomplishments, and costs incurred during the reporting period. The report may include additional information, including findings and recommendations that would assist the Government in evaluating progress under this contract.

7. Government supplied Space / Supplies / Property

The Government will determine which tasks within this SOW must be performed on-site and those which can be performed at Contractor off-site facilities. The Government will provide limited on-site work space with assigned Government Furnished Equipment, telephone, standard office supplies and equipment as Government resources and budget may allow. Access to Government network and information will follow NOAA security policy for CAC card and 2-factor authentication. The Contractor is required to furnish all hardware and software necessary to produce contract deliverables when approved and performed at off-site contractor facilities.

8. Recognized Holidays

The Contractor is NOT required to work on the following days:

New Year’s DayLabor Day
Martin Luther King Jr.’s BirthdayColumbus Day
President’s DayVeteran’s Day
Memorial DayThanksgiving Day
Independence DayChristmas Day

In addition to the days designated as holidays, the Government observes the following days:

· Any other day designated by Federal Statute

· Any other day designated by Executive Order

· Any other day designated by a President's Proclamation

9. Hours of Operation/Place of Performance

The contractor is responsible for conducting business between the hours of 6:30 a.m. - 6:30 p.m. Monday through Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this statement of work when the Government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the work force are essential.

Remote work may at times be authorized and will be monitored by the Task Manager, Division Chief, Deputy Division Chief, or Branch Chief and must comply with the Department of Commerce Information Technology Requirement (CITR) 0008: Remote Access.

10. Security

The Assessment and Authorization (A&A) requirements of Clause 48 CFR 1352.239-72 do not apply, and a Security Accreditation Package is not required.

OCS data management policy requires that any contract work performed off-site will be performed on copies of the OCS data which has been determined to be “public” data. OCS always maintains the authoritative (master) version of all data and information. All deliverables undergo extensive quality assurance (automated and manual reviews) before being incorporated into production systems. Any requested tasks performed on actual authoritative data will be performed on-site. When deliverables are electronically transmitted, they must be conveyed through government issued VPN accounts and government furnished equipment, which is currently covered by an existing government Certification and Accreditation (C&A) package, NOAA6501 or through secure transmission such as Secure FTE site or DOC Accellion.

The contractor is required to meet the DOC IT Security Program Policy (ITSPP) and Commerce Information Technology Requirements (CITRs) (available at: https://connection.commerce.gov/policy/20140528/it-security-program-policy-and-commerce-information-technology-requirements).

The government will provide the necessary computer equipment and information to perform this contract for on-site work performed. The contractor must request the additional requirements from the Contracting Officer Representative (COR) when issued GFE requires additional hardware or software. The Contractor is required to ensure the GFE is connected to either NOS internal networks or the Internet, at a minimum of once every two weeks and be operated for approximately 2 hours while connected to allow for the Government to perform the necessary configuration management and vulnerability management of the GFE.

It is a mandatory requirement for every NOAA IT user (government, contractor, associate, or temporary personnel) to complete the NOAA Information Technology Security Awareness Course every year. Temporary personnel include visitors, guest workers, etc. who plan to work at a NOAA site and use NOAA IT resources. Both new and temporary employees must take the course within three days after initial issuance of NOAA IT equipment and annually.

The contractor must consider IT Security controls throughout the lifecycle of this contract as outlined in NIST Special Publication 800-64 (http://csrc.nist.gov/publications/nistpubs/800-64-Rev2/SP800-64-Revision2.pdf).

Disclosure of the information/data, in whole or in part, by the contractor can only be made after the contractor receives prior written approval from the Contracting Officer. Whenever the contractor is uncertain with regard to the proper handling of information/data under the contract, the contractor shall obtain a written determination from the Contracting Officer. The contractor shall not present itself in any way as a representative of the Office of Coast Survey or the Government.

Cloud services are NOT authorized in support of this contract.

For application/software product development, appropriate vulnerability planning needs to be included during the assessment of needs and requirements. This includes secure coding practices, code review, code scanning for vulnerabilities and supporting documentation. If the contractor solutions use a contractor developed or government furnished [mobile/web] application/ database/ network operating systems to be deployed, the contractor must process the project through the OCS SDLC process and coordinate with OCS ITSB for deployment within OCS approved solution which is compliant with agency policies:

· The DOC ITSPP and DOC CITRs may not specifically identify [mobile/web] application/ database/ network operating systems, may be applicable and will require comply with these requirements. DOC policies are controlled unclassified information (CUI) and are restricted to only authorize personnel.

All electronic provided information by the contractor must undergo malicious software scanning using a commercial anti-virus and anti-spyware software to ensure the information is free of known malicious software. The contractor must work with the COR and the OCS ISSO prior to sending the information to establish a secure method for transfer. One option could be a file encrypted with a password using a product like WinZip. The contractor must encrypt any sensitive information that will be sent electronically (i.e., email), sensitive information includes but not limited to:

· All information describing the implementation, configuration, settings, etc. for solution being developed,

· The source code and database schema,

· The vulnerability scanning, secure baselines scanning, mitigation results,

· The secure baseline deviations,

· Internet Protocol, subnet mask and similar identification.

The contractor includes the necessary product support and supporting documentation for the hardware and/or software that allows the OCS Help Desk to complete the OCS sanitization process (compliant with the NIST Special Publications 800-88 Guidelines for Media Sanitization, http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf) of the hardware and/or software upon the disposal of the product.

The contractor is required to comply with all DOC and NOAA IT security requirements for taking any type of information technology component(s) on international travel. This includes mobile phone(s), mobile devices (laptop, tablets, etc.) or other mobile or portable technology (thumb drives, USB drives, etc.). Notification must be given to the OCS Help Desk and OCS Deputy Director to allow time for processing the international travel request for approval by the NOS Assistant Chief Information Officer for Government owned, Contractor owned or individual personally owned technology.

The contractor is required to comply with the Department of Commerce’s Commerce Acquisition Manual’s (CAM) 1337.70 Personnel Security Requirements (http://oam.eas.commerce.gov/docs/CAM1337.70%28Security%29.pdf).

In compliance with instructions contained in Homeland Security Presidential Directive 12 (HSPD-12), the contractor shall comply with Department of Commerce Personal Identity Verification (PIV) procedures when the contractor requires physical access to MCD facilities and/or access to controlled information systems. Completion of a National Agency Check with Inquiries (NACI) with a favorable suitability determination, and completion of two security training modules is required for access to all MCD facilities.

MCD retains the right to require removal of contractor personnel, regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, conflict with the interests of the Government.

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