Attachment 1- Performance Work Statement.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

Captain of the Port (COTP) Boundary Geospatial Dataset Production Support Services

1.0 GENERAL

1.1 BACKGROUND

The United States Coast Guard Navigation Center (NAVCEN) is responsible for the dissemination of authoritative maritime safety information and supporting geospatial data used by Coast Guard operational units, mariners, and interagency partners. NAVCEN maintains the national Port Status application, which organizes named ports, harbors, rivers, canals, channels, bays, and other waterways under the responsible Coast Guard Captain of the Port (COTP).

The Port Status application currently identifies approximately 525 individual ports and waterways. NAVCEN requires a complete and standardized geospatial polygon dataset that represents the operational geographic extent of each listed port or waterway, associates each feature with the responsible COTP, and supports Coast Guard information systems and public-facing dissemination platforms.

The Contractor shall use the Coast Guard Waterways Harmonization model and the Harmonized Waterways Dataset Explorer as the principal production methodology and geospatial reference for this effort. This requirement concerns the geographic representation of ports and waterways listed in the Port Status application; it does not establish, amend, or replace legal COTP jurisdictional boundaries.

1.2 SCOPE

The Contractor shall produce, validate, and deliver a complete, publication-ready national geospatial dataset representing the ports and waterways identified in the Government-furnished Port and Waterway Production Inventory. The Government anticipates approximately 525 inventory items. Each inventory item shall be represented by an individual polygon or, when appropriate and approved by the Government, a multipart polygon.

The approximately 525 inventory items are individual ports and waterways organized under the responsible COTP. They are not approximately 525 separately established COTP zones. The Contractor shall not create, revise, or interpret the legal outer jurisdictional boundaries of a COTP zone except as necessary to associate each inventory item with the responsible COTP identified by the Government.

Within five business days after award, the Government will provide a baseline Port and Waterway Production Inventory derived from the NAVCEN Port Status application. The baseline inventory shall establish the contract production quantity and shall identify, at a minimum, the Government-approved Port Status name and responsible COTP for each item. Changes made to the public Port Status application after the baseline inventory is issued shall not change the contract scope unless incorporated by written direction of the Contracting Officer.

The Contractor shall use existing Harmonized Waterways geometry when it adequately represents the geographic extent of an inventory item. When an inventory item does not directly correspond to an existing Harmonized Waterways feature, encompasses multiple features, represents only a portion of an existing feature, or requires supplemental geometry, the Contractor shall create the required geometry using the Waterways Harmonization model, Government-approved supplemental data, and the decision process established in this PWS.

Work under this PWS is limited to source review, cross-referencing, geospatial production, harmonization, attribution, quality control, validation, documentation, and delivery. No modification of the NAVCEN Port Status application, software development, system hosting, system operations, production deployment, future capability development, or standards development is included.

1.3 OBJECTIVE

The objective of this effort is to produce a single, standardized, authoritative geospatial dataset representing every port and waterway contained in the Government-approved production inventory. Each feature shall be constructed using the Waterways Harmonization model, associated with the responsible COTP, and attributed so the textual Port Status record can be reliably linked to the corresponding geographic polygon.

The resulting dataset shall reduce ambiguity, improve consistency, and support ingestion, publication, maintenance, and archival by NAVCEN.

1.4 APPLICABLE DOCUMENTS

1.4.1 Compliance Documents

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

• 14 U.S.C. § 541

• 33 U.S.C. § 1221 et seq.

• 33 CFR Part 62

• 44 U.S.C. § 3501

1.4.2 Reference Documents

The following documents may be helpful to the Contractor in performing the work described in this document:

• 33 CFR Part 3

• OMB Circular A-16

• Executive Order 12906

• Federal Geographic Data Committee (FGDC) / National Spatial Data Infrastructure (NSDI) standards

1.4.3 Authoritative Production Sources and Source Precedence

The following Government sources shall be used to define and produce the contract deliverables:

• Authoritative source for the listed port or waterway name and responsible COTP assignment: NAVCEN Port Status application

• Principal geospatial source, parent geometry, and production-method model: Harmonized Waterways Dataset Explorer

• Government-furnished Port and Waterway Production Inventory - the contract baseline identifying the specific inventory items required for delivery.

• Government-furnished data dictionaries, technical specifications, supplemental geospatial data, and written technical determinations approved by the Contracting Officer or COR acting within delegated authority.

In the event of a production-source conflict, the Government-furnished Port and Waterway Production Inventory shall control the items required for delivery; the NAVCEN Port Status application shall control the approved display name and responsible COTP assignment; and the Harmonized Waterways Dataset shall serve as the principal source for parent geometry, standardized waterway names, identifiers, and source lineage. Missing geometry, ambiguous geographic extents, uncertain endpoints, one-to-many or many-to-one source relationships, and other material conflicts shall be entered in the Port and Waterway Decision Register and submitted to the COR for written technical resolution. No technical resolution may change contract scope, price, or period of performance without written direction from the Contracting Officer.

1.5 PERFORMANCE REQUIREMENTS SUMMARY

This contract includes a Performance Requirements Summary (PRS) at PWS 9.0. The PRS is a primary tool for surveillance, inspection, and acceptance of services by the COR in conjunction with applicable contract clauses. The PRS may not be changed or modified without prior written approval of the Contracting Officer.

https://navcen.uscg.gov/port-status https://navcen.uscg.gov/port-status https://experience.arcgis.com/experience/04af2119543d4245b1ea5b5484e136be/ https://experience.arcgis.com/experience/04af2119543d4245b1ea5b5484e136be/

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 TASK ONE - SOURCE DATA REVIEW, INVENTORY CROSSWALK, AND HARMONIZATION

The Contractor shall review the Government-furnished Port and Waterway Production Inventory and cross-reference every inventory item against the NAVCEN Port Status application and the Harmonized Waterways Dataset Explorer. The Contractor shall identify the corresponding Harmonized Waterways feature or features, applicable identifiers, standardized and alternate names, responsible COTP, available geometry, source lineage, and any discrepancy requiring Government resolution.

The Contractor shall prepare a Source Crosswalk that accounts for every inventory item and identifies whether the proposed geometry has a direct one-to-one relationship with an existing Harmonized Waterways feature, requires a combination of multiple features, requires subdivision of an existing feature, requires supplemental geometry, or requires Government adjudication. The Contractor shall also establish and maintain a Port and Waterway Decision Register documenting each material ambiguity, source conflict, proposed interpretation, Government decision, decision date, and affected feature identifier.

2.2 TASK TWO - TECHNICAL METHODOLOGY, DATA SCHEMA, AND REPRESENTATIVE PILOT

The Contractor shall submit a proposed technical methodology, data schema, quality-control approach, and representative pilot dataset before beginning full national production. The pilot shall contain a Government-selected sample of approximately 15 to 25 inventory items and shall include, to the extent represented in the production inventory, coastal, river, canal or channel, Great Lakes, offshore or multipart, Alaska or territorial, and complex one-to-many or many-to-one examples.

The pilot shall demonstrate the Contractor’s application of the Waterways Harmonization model, use of existing parent geometry, creation of supplemental geometry, attribution, source lineage, topology validation, and decision-register process. The Contractor shall not begin full national production until the COR provides written technical approval of the methodology, schema, and pilot. Such approval does not authorize a change in contract scope and does not constitute final acceptance of later production data.

2.3 TASK THREE - PORT AND WATERWAY GEOSPATIAL DATASET PRODUCTION

The Contractor shall produce a polygon or Government-approved multipart polygon for each item in the Government-furnished Port and Waterway Production Inventory. Each feature shall represent the operational geographic extent of the corresponding Port Status location and shall be developed using the Harmonized Waterways Dataset as the principal parent geometry and the Waterways Harmonization model as the production methodology.

The Contractor shall retain existing Harmonized Waterways geometry, identifiers, standardized naming relationships, and source lineage to the greatest extent practicable. When modification or supplemental production is required, the Contractor shall apply a consistent process for determining the geographic beginning and end of the feature, creating a generalized polygon representing the applicable port or waterway area, incorporating approved authoritative geometry, and linking the resulting feature to the correct inventory item and COTP.

The Contractor shall not independently add, remove, rename, consolidate, subdivide, reassign, or materially alter an inventory item without written Government approval. The Contractor shall submit production data in incremental packages so the Government can review methodology and quality throughout the period of performance rather than only at the end of national production.

2.4 TASK FOUR - QUALITY ASSURANCE AND VALIDATION

The Contractor shall conduct internal quality assurance and validation to confirm that every item in the Government-furnished production inventory is represented in the delivered dataset and assigned to the correct COTP. Validation shall include inventory completeness, names and identifiers, COTP assignments, source lineage, geometry validity, topology, attribute consistency, duplicate detection, and comparison against applicable Harmonized Waterways parent geometry and Government-approved decisions.

The Contractor shall provide automated and manual validation results, an error log, the disposition of each error, and a Validation Matrix that accounts for every inventory item and identifies its corresponding delivered feature. All identified critical and major deficiencies shall be corrected before final delivery.

2.5 TASK FIVE - DELIVERY OF PUBLICATION-READY DATA

The Contractor shall deliver the final, validated national Port and Waterway Geospatial Dataset in the formats and structure specified in Attachment 1. The final package shall include the complete geospatial dataset, Source Crosswalk, Port and Waterway Decision Register, Validation Matrix, metadata, data dictionary, source-lineage documentation, validation results, and production documentation sufficient to support Government review, ingestion, publication, maintenance, and archival.

The Contractor is responsible for delivery of publication-ready data. The Contractor is not responsible for modifying the NAVCEN Port Status application, publishing data into a Government production system, or operating a Government system unless separately authorized in writing by the Contracting Officer.

3.0 CONTRACTOR PERSONNEL

3.1 Qualified Personnel

The Contractor shall provide qualified personnel with the knowledge, experience, and technical capability necessary to perform all requirements of this PWS.

3.2 Key Personnel

The following positions are designated as Key Personnel: Project Manager, GIS Analyst, and Cartographer.

Before replacing a person designated as Key, the Contractor shall notify the Contracting Officer at least 15 business days in advance, provide written justification, and submit the proposed substitute’s qualifications. A substitute shall possess qualifications equal to or greater than those of the person being replaced unless otherwise approved by the Contracting Officer. The Contractor shall not replace Key Personnel without Contracting Officer approval.

3.2.1 Minimum Key-Personnel Qualifications

• Project Manager: At least five years of experience managing geospatial data-production projects of comparable complexity, including schedule management, quality control, risk management, and Government or enterprise stakeholder coordination.

• GIS Analyst: At least five years of professional GIS experience, including polygon production, geodatabase design, attribute-schema implementation, topology validation, metadata, source lineage, and use of Esri geospatial tools or equivalent capabilities.

• Cartographer: At least three years of professional cartographic or hydrographic experience, including delineation and generalization of port, waterway, coastal, or maritime features and preparation of data suitable for operational and public display.

3.3 Project Manager

The Contractor shall provide a Project Manager who is responsible for all Contractor work performed under this PWS and serves as the single point of contact for the Contracting Officer and COR. The Contractor shall identify the Project Manager and any authorized alternate in its proposal. During an absence of the Project Manager, one designated alternate shall have full authority to act for the Contractor on matters relating to this requirement. The Project Manager and alternate shall be able to read, write, speak, and understand English.

The Project Manager shall be available to the COR by telephone or electronic collaboration between 0800 and 1700 Eastern Time, Monday through Friday, excluding Federal holidays, and shall respond to requests for discussion or resolution of technical problems within four business hours of notification.

3.4 Employee Identification

Contractor employees visiting Government facilities shall comply with all Government identification, visitor-badge, escort, and access-control requirements and shall identify themselves as Contractor personnel whenever their status is not readily apparent. On-site work is not anticipated under this PWS.

3.5 Employee Conduct

Contractor employees shall comply with applicable Government regulations, policies, and procedures when accessing Government facilities, systems, information, or collaboration environments. Contractor personnel shall maintain professional conduct and shall not engage in conduct that reflects discredit on the United States, the Department of Homeland Security, or the Coast Guard.

3.6 Removal of Employees for Misconduct or Security Reasons

The Government may, through the Contracting Officer, direct the Contractor to remove an employee from Government facilities, systems, or contract performance for misconduct, security, or suitability reasons.

Removal does not relieve the Contractor of its responsibility to continue providing the services required by the contract. The Contracting Officer will provide a written explanation supporting the removal request to the extent permitted by law and policy.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

The requirements office anticipates Tier 1, Low Risk, Non-Sensitive physical or logical access, with SF85 processing as applicable. No on-site Government work is required. HSPD-12 credentialing or logical access shall be required only when necessary for access to Government facilities, systems, data, or collaboration environments and as directed by the Contracting Officer or security office.

Check Applicable Box

Tier Investigation Risk Form

X 1 Low Risk, Non-Sensitive, Physical/Logical Access (HSPD-12 Credentialing) SF85

2 Moderate Risk, Public Trust SF85P

3 Non-Critical Sensitive, L, Confidential and Secret Information SF86

4 High Risk, Public Trust SF85P

5 Q, Top Secret, Compartmented Information, Critical Sensitive, Special Sensitive SF86

4.2 PERIOD OF PERFORMANCE

The period of performance for this contract is six months from the date of award.

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities. No routine on-site Government work is required.

4.4 HOURS OF OPERATION

[RESERVED]

4.5 TRAVEL

Contractor travel is not required for this requirement.

4.6 POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and COR no later than five business days after award. The conference will be held by teleconference or electronic collaboration and will address technical and contracting objectives, Government-furnished resources, the baseline production inventory, security and access, the draft Project Plan, the pilot, and the review and acceptance process.

4.7 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the Post Award Conference. The plan shall include, at a minimum: the work breakdown structure; production methodology; schedule and milestones; role of Key Personnel; source-review and decision process; pilot approach; incremental-delivery plan; quality-management plan; risk register; communication approach; and procedures for maintaining data integrity and schedule performance. The Contractor shall provide a final Project Plan to the COR no later than five business days after the Post Award Conference.

4.8 BUSINESS CONTINUITY PLAN

[RESERVED]

4.9 PROGRESS REPORTS

The Project Manager shall provide a weekly progress report to the Contracting Officer and COR by electronic mail. The report shall include: work completed during the reporting period; inventory-item counts by status;

deliverables submitted or accepted; schedule status; planned work for the next reporting period; unresolved Decision Register items; risks, issues, and corrective actions; Government actions or decisions needed; and Contractor concerns or recommendations. Labor-hour, direct-cost, or travel reporting shall be included only when required by the contract type, pricing arrangement, or written direction of the Contracting Officer.

4.10 PROGRESS MEETINGS

The Project Manager shall be available to meet with the COR upon request to present deliverables, discuss progress, review production metrics, exchange information, and resolve technical issues. Meetings will be conducted by teleconference or electronic collaboration unless otherwise directed.

4.11 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in accessible electronic formats with read/write capability using applications compatible with DHS workstations. Unless otherwise approved, narrative documents shall be delivered in Microsoft Word format, tabular working files in Microsoft Excel or comma-separated-value format, and final archival documents in PDF format when requested.

4.12 DATA RIGHTS AND INTELLECTUAL PROPERTY

Rights in data, software, and other deliverables shall be governed by the clauses incorporated into the contract. The Contractor shall deliver all custom geospatial data, metadata, crosswalks, decision registers, validation records, data dictionaries, documentation, and other materials developed specifically for this requirement with the rights required by the contract. The Contractor shall identify in its proposal any preexisting, proprietary, licensed, or third-party material it intends to use. The Contractor shall not incorporate material that restricts Government use, publication, maintenance, modification, or redistribution of the final dataset without prior written approval from the Contracting Officer.

4.13 PROTECTION OF INFORMATION

The Government anticipates that all source data required for performance of this PWS will be publicly available or will be provided by the Government as information approved for public use. The contractor is not expected to receive, collect, process, store, transmit, or retain Controlled Unclassified Information, Personally Identifiable Information, Sensitive Personally Identifiable Information, classified information, proprietary information, or other sensitive Government information

The contractor shall manage all data used or created under this contract in a manner that preserves its integrity, accuracy, completeness, availability, provenance, and traceability. The contractor shall protect source data, working files, draft datasets, crosswalks, decision registers, quality-control records, and final deliverables against unauthorized alteration, corruption, accidental deletion, and loss. The contractor shall maintain sufficient backup and version-control procedures to permit recovery of current contract work and identification of material changes made during performance.

Public availability of the source data does not authorize the contractor to represent draft or unaccepted products as official Coast Guard data. The contractor shall not publish, distribute, publicly display, or otherwise release contractor-created draft datasets, working files, Government comments, discrepancy records, or unaccepted deliverables without prior written approval from the Contracting Officer. Following Government acceptance and authorization for public release, the final dataset may be presented and made available for public download as directed by the Government.

The contractor shall maintain source lineage for each delivered feature and shall document the public source, source date, applicable identifier, geometry-production method, and any Government-approved modification or interpretation. The contractor shall use Government-furnished and publicly available data solely for purposes consistent with performance of this contract and shall not alter an authoritative source record.

If the contractor encounters information that is marked as, appears to contain, or is reasonably suspected of containing CUI, PII, SII, classified information, proprietary information, or other nonpublic sensitive information, the contractor shall stop processing the affected information, prevent further dissemination, and immediately notify the COR and Contracting Officer. The contractor shall not resume processing until written direction is provided by the Contracting Officer.

At contract completion, the contractor shall deliver all required source crosswalks, working documentation, quality-control records, metadata, final datasets, and archival packages to the Government. The contractor shall dispose of remaining Government-furnished or contract-generated working copies as directed by the Contracting Officer and consistent with applicable contract clauses.

4.14 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act, classified to 29 U.S.C. § 794d, requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), the ICT shall be accessible to people with disabilities. All applicable electronic content and ICT delivered under this requirement shall conform to the applicable revised Section 508 Standards at 36 CFR Part 1194, including Appendix A, Appendix C, and Appendix D, and to DHS accessibility policy and instructions incorporated into the solicitation or contract.

This PWS does not require development of a web application, software platform, or hardware product.

Applicable electronic-content deliverables include reports, data dictionaries, metadata, validation matrices, instructions, map products, and other documentation. Contractor-created map images or visualizations shall include meaningful alternative text or an equivalent accessible text or tabular description. Raw geospatial data shall be accompanied by accessible documentation sufficient to identify the data structure, attributes, purpose, and means of use.

The Offeror shall provide an Accessibility Conformance Report based on the applicable Voluntary Product Accessibility Template when required by the solicitation’s Section 508 determination or when the Offeror proposes a commercial or Contractor-developed ICT product. Requests for exceptions or alternative approaches shall be submitted to the Contracting Officer for determination under applicable DHS policy.

5.0 GOVERNMENT-FURNISHED RESOURCES

The Government will provide the information, data, and documents necessary for performance of this requirement, including, as applicable:

• The baseline Port and Waterway Production Inventory derived from the NAVCEN Port Status application.

• Access to the NAVCEN Port Status application and the Harmonized Waterways Dataset Explorer.

• Available Harmonized Waterways data, identifiers, data dictionaries, metadata, and source-lineage information.

• Government-approved supplemental geospatial data and technical documentation.

• Government decisions resolving items recorded in the Port and Waterway Decision Register.

• Government-approved delivery locations, collaboration methods, and acceptance tools or checklists.

The Contractor shall use Government-furnished resources only for performance of this contract and shall not release them to outside parties without prior written consent of the Contracting Officer. The Government will identify any limitations, handling requirements, or access restrictions applicable to specific resources.

6.0 CONTRACTOR-FURNISHED PROPERTY

The Contractor shall furnish all facilities, labor, materials, equipment, software, licenses, storage, connectivity, and services necessary to fulfill this requirement, except for the Government-furnished resources identified in PWS 5.0.

7.0 GOVERNMENT REVIEW, ACCEPTANCE, AND CORRECTION

The COR will review deliverables against this PWS, the approved Project Plan, Attachment 1, the baseline production inventory, the approved pilot, and the Government-approved Port and Waterway Decision Register. Acceptance shall be based on objective completeness, schema, geometry, topology, attribution, documentation, and validation requirements and not solely on visual or subjective review.

7.1 Deficiency Classifications

• Critical deficiency: An error that materially misrepresents the geographic extent or COTP assignment of an inventory item; omits a required inventory item; prevents the dataset from being opened, validated, or ingested; corrupts the dataset; or causes unauthorized disclosure, loss, or compromise of Government information.

• Major deficiency: A geometry, topology, attribute, metadata, source-lineage, documentation, or formatting error that materially affects operational usability, publication readiness, maintenance, or traceability but does not meet the definition of a critical deficiency.

• Minor deficiency: A nonmaterial formatting, spelling, or documentation issue that does not affect geographic accuracy, inventory completeness, COTP assignment, ingestion, publication, or maintenance.

7.2 Review Period

Unless another period is identified in PWS 8.0 or approved in the final Project Plan, the COR will have seven business days to review a deliverable and provide acceptance or consolidated comments. The review period begins when the complete deliverable is received at the approved delivery location. An incomplete submission does not begin the Government review period.

7.3 Rejection, Correction, and Resubmission

When a deliverable is not acceptable, the COR will provide written notice identifying the deficiency, the affected requirement, and the basis for nonacceptance. The Contractor shall correct critical and major deficiencies at no additional cost and resubmit the deliverable within five business days unless a different correction period is approved in writing. The Contractor shall provide a comment-disposition record identifying each Government comment and the corrective action taken.

7.4 Acceptance Standard

A deliverable is acceptable when all required files and documentation are present, required inventory items are accounted for, automated and manual validation requirements are satisfied, no unresolved critical or major deficiencies remain, and the deliverable conforms to the approved technical methodology, schema, and Government decisions. Acceptance of an interim deliverable does not waive the Government’s right to require correction of latent errors discovered during national integration or final validation.

7.5 Authority

The COR may provide technical comments and acceptance decisions within delegated authority. Only the Contracting Officer may change contract scope, price, period of performance, or other contractual terms.

8.0 DELIVERABLES

The Contractor shall provide the deliverables identified below. All days are calendar days unless expressly identified as business days. The Contractor shall not begin full national production until Deliverable 6 is approved in writing by the COR. Due dates may be changed only by written direction of the Contracting Officer or as otherwise permitted by the contract.

Item PWS Reference Deliverable / Event Due By Distribution / Approval

1 4.6 Post Award Conference Within 5 business days after award Contracting Officer and COR

2 4.7 Draft Contractor Project Plan At the Post Award Conference Contracting Officer and COR

3 4.7 Final Contractor Project Plan Within 5 business days after the Post Award Conference COR approval

4 4.9 Weekly Progress Reports Weekly throughout the period of performance Contracting Officer and COR

5 2.1 Source Crosswalk, Source Gap Analysis, and Initial Decision Register Within 30 days after award COR review

6 2.2 Technical Methodology, Data Schema, QA Plan, and Representative Pilot Dataset Within 45 days after award COR approval required before full production

7 2.3 First Incremental Production Package Within 75 days after award COR review

8 2.3 Second Incremental Production Package Within 105 days after award COR review

9 2.3, 2.4 Complete Draft National Dataset and Contractor QA Package Within 135 days after award COR review

10 2.4 Corrected National Dataset and Government Comment-Disposition Record

Within 10 days after receipt of consolidated Government comments

COR review

11 2.5 Final Publication-Ready Dataset and Complete Documentation Package

No later than 15 days before the end of the period of performance

COR final acceptance

Item PWS Reference Deliverable / Event Due By Distribution / Approval

12 4.13 Return or Destruction Certification, if requested No later than the end of the period of performance Contracting Officer and COR

PERFORMANCE WORK STATEMENT LAST UPDATED: 7/14/2026

9.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

The PRS establishes measurable performance standards for Government surveillance and acceptance. The COR will use the surveillance methods below in conjunction with the contract’s inspection clauses. Failure to meet an AQL may result in rejection, correction and resubmission, increased surveillance, corrective-action planning, consideration in contractor performance evaluations, or other remedies available under the contract.

Service Output Performance Standard Acceptable Quality Level (AQL) Surveillance Method Remedy for Nonconformance

1. Weekly Progress Reports

(PWS 4.9)

Reports accurately state completed work, production counts, schedule status, risks, decisions needed, and next-period work;

submitted by the approved weekly due date.

No more than one late report during the period of performance, and no report more than two business days late. No material misstatement of status.

Review of reports, schedule, production metrics, meeting records, and deliverable status.

Corrected report; corrective-action plan for recurring lateness or inaccurate reporting; consideration in performance evaluation.

2. Source Review and Crosswalk (PWS 2.1)

Every baseline inventory item is accounted for and cross-referenced to the applicable source geometry or documented as requiring a decision.

100% inventory accounting; zero unresolved critical omissions before pilot approval.

Inventory-to-crosswalk reconciliation, source sampling, and review of the Decision Register.

Rejection and correction at no additional cost; increased sampling or surveillance.

3. Methodology, Schema, and Pilot (PWS 2.2)

Pilot demonstrates the approved Waterways Harmonization method, schema, attribution, lineage, geometry, topology, and QA process.

Zero critical deficiencies and no unresolved major deficiencies before approval to begin full production.

Automated schema and topology tests;

source-to-feature review; visual inspection; review of methodology and QA records.

Withhold approval for full production;

correction and resubmission at no additional cost.

4. Incremental Production Packages (PWS 2.3)

All scheduled inventory items are delivered with complete attribution, valid geometry, traceable lineage, and required QA records.

100% of scheduled items delivered;

zero critical deficiencies; major-deficiency rate not greater than 1% of reviewed features.

Automated validation, inventory reconciliation, risk-based sampling, source comparison, and Decision Register review.

Rejection or partial rejection; correction and resubmission; increased surveillance and sampling.

5. Draft National Dataset and

QA (PWS 2.4)

The complete baseline inventory is represented and the Contractor provides validation evidence for all features.

100% inventory completeness; zero critical deficiencies; major-deficiency rate not greater than 0.5% before Government comment resolution.

Full inventory reconciliation; automated topology and schema validation; targeted source-to-feature inspection; review of error and disposition logs.

Correction and resubmission; corrective-action plan; consideration in performance evaluation.

6. Final Publication-Ready Dataset (PWS 2.5)

All required files, features, attributes, metadata, documentation, and validation records are delivered by the contractual due date and conform to Attachment 1.

100% required deliverables; zero unresolved critical or major deficiencies; on-time final delivery.

Final acceptance checklist, ingestion/opening test, metadata and documentation review, inventory reconciliation, and validation results.

Nonacceptance; correction at no additional cost; other contractual remedies, including performance evaluation impacts.

ATTACHMENT 1 - PORT AND WATERWAY GEOSPATIAL DATA SPECIFICATION AND

ACCEPTANCE CHECKLIST

A1.1 Purpose

This attachment establishes the minimum technical, documentation, quality-control, and acceptance requirements for the Port and Waterway Geospatial Dataset. The approved pilot may refine implementation details, field lengths, controlled values, or naming conventions, but shall not reduce the requirements of this attachment without written Contracting Officer approval.

A1.2 Required Delivery Formats

• Esri File Geodatabase containing the authoritative production feature class and related tables.

• GeoJSON export in World Geodetic System 1984 (WGS 84), EPSG:4326, suitable for public dissemination and system integration.

• Comma-separated-value or Microsoft Excel exports of the Source Crosswalk, Decision Register, Validation Matrix, data dictionary, and error/comment-disposition logs.

• Metadata and narrative documentation in editable Microsoft Office format and PDF when requested.

• Any additional Government-approved format identified during pilot approval.

The Contractor shall ensure that exports preserve the intended feature-to-record relationship, character encoding, identifiers, and null-value handling. Where a format imposes technical limitations, the Contractor shall document the limitation and obtain COR approval for the proposed implementation.

A1.3 Spatial Reference and Geometry

• The public-delivery dataset shall use WGS 84, EPSG:4326. A Government-approved projected coordinate system may be used for editing, measurement, and quality control when documented in the methodology.

• The authoritative geometry type shall be polygon. Multipart polygons are permitted when necessary to represent a single inventory item and when the relationship is documented.

• Geometry shall be valid and free of null geometry, unintended self-intersections, unclosed rings, duplicate features, orphaned parts, and invalid multipart structure.

• Features shall not contain unintended overlaps, gaps, slivers, spikes, or discontinuities created by the production process. Shared or coincident geometry shall be handled consistently.

• The Contractor shall not densify, simplify, generalize, buffer, clip, merge, or split source geometry in a manner that materially changes the represented operational extent without documentation and Government approval.

• International boundaries, territorial seas, offshore areas, islands, disconnected water bodies, and other complex geometry shall be treated in accordance with Government-furnished data and approved decisions.

A1.4 Minimum Attribute Schema

The final schema shall be approved through the pilot. At a minimum, each inventory record or feature shall include the following information, with field names and lengths finalized in the approved data dictionary:

Data Element Minimum Requirement

FEATURE_ID Unique, persistent Government-approved identifier for the delivered feature.

INVENTORY_ID Identifier linking the feature to the baseline Port and Waterway Production Inventory.

PORT_STATUS_NAME Government-approved display name from the baseline Port Status inventory.

STANDARD_NAME Standardized Harmonized Waterways name, when applicable.

ALTERNATE_NAME Alternate or historical name, when applicable.

COTP_NAME Responsible Captain of the Port.

SECTOR_UNIT Responsible Sector, Marine Safety Unit, or other applicable unit.

DISTRICT Applicable Coast Guard District, when furnished or approved.

FEATURE_TYPE Controlled value identifying port, harbor, river, canal, channel, bay, waterway, anchorage area, or other approved type.

HWD_ID Applicable Harmonized Waterways identifier or identifiers.

Data Element Minimum Requirement

HWD_RELATIONSHIP Controlled value identifying one-to-one, merge, split, partial-use, supplemental, or other approved relationship.

GEOM_METHOD Controlled description of how the geometry was produced.

SOURCE_LINEAGE Primary source or sources used to create or validate the feature.

DECISION_ID Decision Register identifier, when a Government decision applies.

QA_STATUS Controlled value showing validation status.

EFFECTIVE_DATE Applicable source or Government-approved effective date.

VERSION Dataset or feature version identifier.

NOTES Concise explanatory information when needed.

A1.5 Source Crosswalk and Decision Register

The Source Crosswalk shall contain one record for every baseline inventory item and shall identify its corresponding delivered feature, applicable Harmonized Waterways feature or features, relationship type, source lineage, production status, and any Decision Register reference. The Decision Register shall document each material ambiguity or source conflict, the Contractor’s analysis and recommendation, the Government’s written technical decision, the decision date, and the affected inventory and feature identifiers.

A1.6 Metadata and Documentation

• Dataset-level and feature-class metadata describing purpose, scope, source lineage, spatial reference, production date, contact information, use limitations, processing steps, validation, and maintenance considerations.

• A complete data dictionary defining each field, data type, length, domain, nullability, controlled value, and example.

• A production-method document explaining source selection, geometry creation, harmonization, generalization, multipart handling, supplemental geometry, topology, and QA procedures.

• A version history identifying material changes between pilot, incremental, draft, corrected, and final deliveries.

• An accessible user/read-me document describing the contents and organization of the final delivery package.

A1.7 Quality-Control and Validation Requirements

• Reconcile the final dataset against 100% of the baseline inventory.

• Run automated geometry-validity, topology, required-field, domain, identifier-uniqueness, and null-value tests.

• Compare each feature to its applicable Harmonized Waterways parent geometry and document material deviations.

• Perform manual cartographic and source-lineage review of every feature created through merge, split, partial-use, supplemental, or Government-decision methods.

• Perform risk-based manual review of direct one-to-one features at a sampling rate approved in the pilot.

• Correct all critical and major deficiencies before final submission and document the disposition of detected errors.

• Provide machine-readable and human-readable validation results with the draft and final packages.

A1.8 Final Acceptance Checklist

• ☐ All baseline inventory items are present in the Source Crosswalk and Validation Matrix.

• ☐ Every inventory item is linked to a delivered feature or an approved documented multipart/relationship structure.

• ☐ All features contain the required attributes and valid controlled values.

• ☐ COTP assignments and Port Status names match the Government-approved baseline inventory.

• ☐ Geometry opens successfully, is valid, and passes the approved topology checks.

• ☐ Harmonized Waterways identifiers, relationships, and source lineage are present where applicable.

• ☐ All Government decisions have been incorporated and linked through the Decision Register.

• ☐ No unresolved critical or major deficiencies remain.

• ☐ Required metadata, data dictionary, methodology, validation results, and accessible read-me documentation are present.

• ☐ File names, folder structure, version identifiers, and delivery formats conform to the approved pilot and

Project Plan.

• ☐ The final package is delivered by the contractual due date and can be opened, inspected, and ingested using Government-approved tools.