GPS.gov Sustainment, Operations, and Maintenance

Performance Work Statement

Project Summary

Project Name GPS.gov Sustainment, Operations, and Maintenance

Contract Number TBD

Program Manager John Dukes john.e.dukes@noaa.gov 301-541-3715

Project Manager John Dukes

Customer/User National Coordination Office (NCO) for Space-Based Positioning, Navigation, and Timing

Project Dates 09/01/2026 - 08/31/2027-Base Year 09/01/2027 – 08/31/2028 – Option Year 1 09/01/2028 – 08/31/2029 – Option Year 2 09/01/2029 – 08/31/2030 – Option Year 3 09/01/2030 – 08/31/2031 – Option Year 4

Revision History

Release Date Comments and reasons for document changes

Draft June 2, 2025 - Original document

Rev 0.1 Jun 10, 2025 - Updates and revisions

Rev 0.2 February 2, 2026 - Updates and revisions

Table of Contents

1. Background 4

2. Objective 4

3. Tasks 4

3.1 Task 1 – GPS.gov Maintenance 4

3.2 Task 2 - GPS.gov Enhancements and Feature Development 5

3.3 Task 3 - Content Governance and Training 5

4. Type of Order 5

5. Period of Performance 5

6. Place of Performance 5

7. Technical Requirements and Standards 5

7.1 Coding Standards and Requirements 5

7.2 Ownership of Developed Code 6

7.3 Security Standards 6

8. Other applicable conditions 7

8.1 Key Personnel 7

8.1.1 Project Manager/Scrum Master 7

8.3 Post Award Conference 8

8.4 Project Management Plan 8

8.5 Monthly Status Report 8

8.6 Progress Meetings 8

8.7 General Report Requirements 9

8.8 Protection of Information 9

8.9 Recognized Holidays 9

9. Deliverable Schedules 10

9.1. Contract-wide Deliverables 10

10. Performance Metrics 10

1. BACKGROUND

The National Coordination Office (NCO) is the permanent staff of the National Executive Committee for Space-Based Positioning, Navigation, and Timing (PNT). It supports the Committee by coordinating GPS-related information across federal agencies, fostering interagency collaboration, and resolving issues. The NCO's primary communication tool is its website, GPS.gov, which serves as the centerpiece of its public outreach and education efforts, providing timely GPS-related information, resources, and data to the public and federal stakeholders.

However, the current site faces challenges, including outdated technology, limited user engagement, and accessibility issues. As digital technologies evolve, the NCO must adopt user-centered design, agile delivery practices, and adhere to federal digital policies to ensure government information is accessible anytime, anywhere, and on any device.

2. OBJECTIVE

The objective of this order is to sustain and maintain the GPS.gov website by ensuring stable operations, compliance with federal web standards, and incremental feature enhancements. The work includes routine maintenance, security updates, content management support, training for contributors, coordination with NOAA's hosting services, and the implementation of up to three low-to-moderate complexity features to improve usability and accessibility. This effort ensures that GPS.gov remains a reliable, accessible, and user-friendly resource for federal stakeholders and the public.

3. TASKS

3.1Task 1 – GPS.gov Maintenance

The contractor shall maintain the Drupal-based platform by providing security, performance, and accessibility updates in coordination with NOAA’s Web Operations Center (WOC). Services will include, but are not limited to:

● Apply Drupal core and module updates, including security patches and baseline system changes.

● Coordinate with WOC to ensure reliable hosting, secure deployment, and version control using contractor-compatible CI/CD or approved manual processes.

● Maintain compliance with federal digital standards, including Section 508 and USWDS alignment.

● Monitor and address accessibility issues, technical errors, and deprecated content modules.

3.2Task 2 - GPS.gov Enhancements and Feature Development

The contractor shall implement up to three low-to-moderate complexity system changes (updates) to improve usability, content access, or backend efficiency, using existing Drupal architecture and approved design components. Services may include, but are not limited to:

● Update existing components and content types for displaying content.

● Minor updates to the admin user interface.

● Ensure all updates are accessible, responsive, and tested across devices and browsers.

● Conduct user acceptance testing (UAT) and make necessary refinements prior to release.

3.3Task 3 - Content Governance and Training

The contractor shall assist the Government content managers in methods to improve content quality, structure, and editorial workflow and provide quarterly refresher training in effective content management and publishing practices. Services shall include, but are not limited to:

● Assist the Government content manager on methods to configure Drupal editorial workflows with defined roles and approval processes for publishing.

● Update existing training materials for live sessions, and recordings to support both new and experienced content contributors. Provide refresher training sessions each quarter.

● Maintain documentation outlining content types, templates, and publishing standards.

● Provide editorial guidance to content managers that supports plain language, accessibility, content length limits, and readability best practices.

4. TYPE OF ORDER

Firm Fixed Price (FFP)

5. PERIOD OF PERFORMANCE

The period of performance shall be for one, twelve-month base year and four option years period.

6. PLACE OF PERFORMANCE

Work will be performed off-premise at the contractor’s facility or remotely, if approved in writing by the Contracting Officer’s Representative (COR).

7. TECHNICAL REQUIREMENTS AND STANDARDS

7.1Coding Standards and Requirements

Tasks and deliverables as part of this order shall adhere to the following Web development standards and best practices:

● Use the US Web Design System and NOAA Style and Design Guidance as a starting point for any design work

● Drupal coding standards

● Section 508 accessibility requirements, specifically WCAG 2.0 AA

● Federal, DOC, NOAA Web Policies, including metadata standards

● Simplicity and Efficiency: Code shall be written clearly and concisely and shall adhere to current

W3C Web standards (HTML 5, CSS, WCAG 2.0 AA). Code shall also minimize server load and optimize data/file connections.

● Readability: Code written as part of this contract will be owned by NOAA. As such, others must be able to read the code provided by the Contractor with minimal effort. Code shall be well commented, consistent, follow coding conventions, and shall use intuitively-named variables.

● Modular/Extensible: Code written as part of this contract must be reusable and modifiable. There shall be no hard-coded assumptions. There will be no use of hacks or workarounds unless approved by the NOAA team.

● Documented: The contractor shall deliver accurate and detailed documentation formatted for accessibility and in conformance with Section 508 of the Rehabilitation .

● Implementation coded for SEO.

● Implementation complies with the DOC password policy. Support of two factor authentication

(2FA) with Common Access Card (CAC) preferred.

● Websites will adhere to the HTTPS-Only Federal requirement and be protected with an SSL implementation that complies with Federal requirements and NOAA OCIO IT Guidance.

● APIs developed under this order shall follow the RESTful JSON architectural style. Any APIs developed shall include the following activities:

● Assist in the definition of requirements for the API.

● Implement, test, and assist in the deployment of the API.

● Perform knowledge transfer with NOAA personnel on how the API was implemented (via code review, etc…).

● Contribute to best practices developer guidelines for APIs.

● Develop analytics capability to track API usage.

● Test API output.

● Create visual presentation of API output.

● Demo API functionality to stakeholders.

● within the website that promotes the API, along with supporting documentation for

● utilizing the API, including the following:

○ Overview.

○ Description and Lists of Query Fields.

○ Sample queries with explanations.

7.2Ownership of Developed Code

The Government owns all contractor-developed custom code/IT intellectual property.

7.3Security Standards

The system supported under this task is rated FISMA Moderate. The suitability or risk level for this work has been determined to be Medium. As such, the contractor shall pre-screen their employees to eliminate anyone who does not meet the criteria outlined in 48 CFR 1337.110–70 (b), CAR 1352.237-70 - Security Processing Requirements—High or Moderate Risk Contracts (APR 2010).

● Web servers shall be configured and hardened.

● The OCIO security team will scan the initial Drupal implementation and subsequent code changes before deployment.

● Computer Security incidents: If an intrusion by an unauthorized party is detected, or a security incident is detected, the contractor shall notify the NOAA Computer Incident Response Team (N-CIRT) via the web at: https://www.csp.noaa.gov/noaa/ncirt/itsecreport.xhtml

● All code will be committed to the project version control system that is backed up regularly

● Two-factor authentication module shall be configured to support two-factor authentication for website administrative dashboards.

● ICAM SAML 2FA will be used for any user authentication.

8. OTHER APPLICABLE CONDITIONS

8.1KEY PERSONNEL

Before replacing any individual designated as Key by the Government, the Contractor shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer. The Contractor shall not replace Key Contractor personnel without approval from the Contracting Officer. The Contracting Officer will notify the contractor within 10 working days after receipt of all required information of the decision on substitutions, and the contract will be modified to reflect any approved changes.

The following Contractor personnel are designated as Key for this requirement.

8.1.1 Project Manager/Scrum Master

The Contractor shall provide a Project Manager (PM) who shall be responsible for all Contractor work performed under this Performance Work Statement (PWS). The Project Manager shall serve as the single point of contact for the Government, including the Contracting Officer (CO) and Contracting Officer’s Representative (COR), and is designated as Key Personnel under this contract. The Contractor shall identify the PM and any designated alternate(s) in the proposal. In the PM's absence, only one alternate may assume full authority for all contract-related matters. The PM and any alternates shall be able to read, write, speak, and understand English fluently. The Contractor shall not replace the Project Manager without prior approval from the Contracting Officer.

The Project Manager shall be available to the COR by phone between 8:00 a.m. and 5:00 p.m., Monday through Friday, and shall respond to requests for discussion or resolution of technical issues within 24 hours of notification.

The Project Manager shall also serve as the Scrum Master, responsible for:

● Planning and overseeing Scrum implementation and sustainment efforts;

● Facilitating Scrum ceremonies (e.g., sprint planning, reviews, retrospectives);

● Ensuring the Scrum Team adheres to Agile practices and remains in a continuous "ready-to-release" state;

● Supporting the Product Owner in backlog management, prioritization, and clarity of backlog items;

● Promoting empirical planning, user-centered delivery, and continuous improvement;

● Guiding the organization in effective Scrum adoption and Agile maturity;

● Improving team communication with external stakeholders to optimize value delivery.

Minimum Requirements:

● PMP or Scrum Master certification;

● At least 3 years of experience serving as a Scrum Master; or

● A master’s degree in Computer Science, Information Systems, or a related technical discipline;

● Demonstrated experience with Drupal 10 development and Agile delivery environments.

8.3POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than 14 calendar days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and discuss the Contractor's draft management plan. The Post Award Conference will be held virtually.

8.4PROJECT MANAGEMENT PLAN

The Contractor shall provide a Project Management Plan (PMP) outlining the roles, responsibilities, communication methods, and timeline for completing the tasks defined in this PWS. This includes identifying the Project Manager as the primary point of contact for the Government and describing how task progress, risks, and coordination with the NOAA Web Operations Center will be managed. The plan shall be concise and submitted within 15 calendar days of award, with updates provided as needed throughout the period of performance.

8.5MONTHLY STATUS REPORT

The Project Manager shall provide a Monthly Status Report to the Contracting Officer and COR via electronic mail. This report shall include a summary of all work performed, an assessment of technical progress, schedule status, and any contractor concerns or recommendations for the previous reporting period.

8.6PROGRESS MEETINGS

The Project Manager shall be responsible for keeping the COR informed about contractor progress throughout the performance period of this contract, and ensure contractor activities are aligned with OSC objectives. At a minimum, the Project Manager shall review the status and results of contractor performance with the COR virtually as requested by the Government. Additionally, the Project Manager shall be available to meet with the COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues.

8.7GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with NOAA workstations (e.g., Windows XP and Microsoft Office Applications).

8.8PROTECTION OF INFORMATION

Contractor access to proprietary information is required under this PWS. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the Privacy Act, OMB M06-16 (PII) and other pertinent laws and regulations governing the confidentiality of privileged information and Safeguarding Sensitive But Unclassified (SBU) (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a Non-Disclosure Agreement.

8.9RECOGNIZED HOLIDAYS

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus

Day President’s Day Veteran’s Day

Memorial Day Thanksgiving Day

Independence Day Christmas

Day Juneteenth

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

It is understood and agreed between the Government and the contractor that observance of such days by Government personnel shall not otherwise be a reason for an additional period of performance or entitlement to compensation except as set forth within the contract.

9. DELIVERABLE SCHEDULES

9.1. CONTRACT-WIDE DELIVERABLES

Item PWS Referen ce

Deliverable/Event Due Distribution

8.3

Kick-Off Meeting

NLT 14 calendar days from date of award

CO, COR, PM

8.4

Project Management Plan

NLT 15 calendar days from date of Kick-Off Meeting

CO, COR, PM

3 8.5 Monthly Status Meeting NLT 10th of each month CO, COR, PM

4 3.2 User Acceptance Testing Report for Enhancements

Upon delivery of each enhancement COR, PM

3.3

User Training and Documentation

Upon delivery of each enhancement and prior to contract expiration

COR, PM

10. PERFORMANCE METRICS

The Contractor shall monitor performance against the established schedule, deliverables, risks, and resource support outlined in the approved PMP. The Contractor shall report any deviations in the bi-weekly Status Report.

PERFORMANCE

OBJECTIVE

PERFORMANCE

STANDARD

ACCEPTABLE

PERFORMANCE

STANDARD

SURVEILLANCE

METHOD

Contractor Project Management

The Status Report shall be turned in punctually to the COR, clearly articulate all outstanding issues and problems, and give an accurate summary of the work completed during the reporting period.

Two (2) or less instances or observations where significant errors or omissions were identified.

The Report shall be delivered on time 100% of the time.

100% Inspection of Deliverables

Write Once, Run Everywhere Development Approach

The contractor shall adopt a technology approach that allows the Government to own and maintain only one code base for the website.

The website is 95% functional on iOS and Android devices with a single code base.

of Responsive Design Checker

Agile Development

The contractor shall adhere to an Agile development philosophy, allowing for incremental releases of functionality prioritized by the NCO.

The contractor will consistently deliver the Government approved functionality on agreed upon intervals.

Schedule Adherence

The contractor shall maintain perfect schedule adherence with respect to provision of project deliverables or shall notify the COR of an anticipated schedule overrun three (3) business days in advance of the associated milestone or deliverable date.

The contractor shall maintain perfect schedule adherence or provide the COR with notice of a schedule overrun within the pre-defined period of three (3) business days.

Documentation

The contractor shall maintain complete documentation of all project deliverables on a project collaboration site provided by the Government.

All project deliverables will be documented and accessible on a project collaboration site.

Compatibility

The finalized website will be 100% functional on NOAA network and mobile devices.

The website is fully functional NOAA environment mobile devices.

At a minimum, the following metrics shall be included:

PERFORMANCE

OBJECTIVE

PERFORMANCE

STANDARD

ACCEPTABLE

PERFORMANCE

STANDARD

SURVEILLANCE

METHOD

Contractor Project Management

The Status Report shall be turned in punctually to the COR, clearly articulate all outstanding issues and problems, and give an accurate summary of the work completed during the reporting period.

Two (2) or less instances or observations where significant errors or omissions were identified.

The Report shall be delivered on time 100% of the time.

Write Once, Run Everywhere Development Approach

The contractor shall adopt a technology approach that allows the Government to own and maintain only one code base for the website.

The website is 95% functional on iOS and Android devices with a single code base.

of Responsive Design Checker

Agile Development

The contractor shall adhere to an Agile development philosophy, allowing for incremental releases of functionality prioritized by the NCO.

The contractor will consistently deliver the Government approved functionality on agreed upon intervals.

Schedule Adherence

The contractor shall maintain perfect schedule adherence with respect to provision of project deliverables or shall notify the COR of an anticipated schedule overrun three (3) business days in advance of the associated milestone or deliverable date.

The contractor shall maintain perfect schedule adherence or provide the COR with notice of a schedule overrun within the pre-defined period of three (3) business days.

Documentation

The contractor shall maintain complete documentation of all project deliverables on a project collaboration site provided by the Government.

All project deliverables will be documented and accessible on a project collaboration site.

Compatibility

The finalized website will be 100% functional on NOAA network and mobile devices.

The website is fully functional NOAA environment mobile devices.