47QMCA25Q0009_SOW_2025-06-12.pdf

I. STATEMENT OF WORK – June 12, 2025

1. Introduction

The General Services Administration, Office of Fleet Management’s (GSA Fleet) mission is to provide safe, reliable, and low cost vehicles solutions to assist Federal agencies in effectively and efficiently meeting their mission. The objective of this acquisition is to receive standardized OEM (Original Equipment Manufacturer) build-level and engineered data for government vehicles from a commercially available software service.

GSA Fleet has struggled with manual vehicle data entry, which creates significant data integrity challenges during the new vehicle load process, as well as for the intake of consolidated agency-owned vehicles into the fleet. The current new vehicle load process relies heavily on marshallers to manually input technical details for each vehicle, leading to potential errors and incomplete information. The proposed customer-driven consolidation plan would also rely on manual entry of critical vehicle details and could potentially face the same data integrity issues. Receiving standardized vehicle information as part of this acquisition will support greater data integrity and streamline the overall vehicle data ingest process.

2. Scope of Work

The scope of this contract includes a commercially available software service for vehicle data standardization for government-owned vehicles to include build-level data sourced from direct connections to OEMs, and vendor engineered data. Data must be provided via a secure, real-time Application Programming Interface (API) integration. GSA Fleet requires data standardization services to support the data ingest process for a variety of vehicle types, including, but not limited to, passenger vehicles, light trucks, medium-duty and heavy-duty vehicles, trailers, buses, and ambulances. Provided data fields should be accurate, comprehensive, and suitable for use in fleet management and audit processes.

3. Tasks

The Contractor must provide all labor, resources, management, and oversight to accomplish the following tasks:

3.1. Standardized Vehicle Data Transfer

GSA will provide the Contractor with a daily list of VINs to return vehicle attribute/specifications data via an API call in a secure manner, as specified in

3.1.2. Technical Details.

The Contractor will then provide the corresponding OEM build-level and/or engineered data for each VIN in the approved API format.

GSA strongly prefers build-level data sourced directly from original equipment manufacturers (OEMs) through established data partnerships or direct integrations. Where OEM-sourced data is unavailable, the Contractor will supplement with engineered data. In such cases, the Contractor must clearly indicate the source of each data element (e.g., "OEM-derived" or "engineered").

3.1.1. Minimum requirements

The Contractor must at a minimum:

3.1.1.1. Provide OEM build-level data for GSA-supplied VINs for light duty vehicles from the following manufacturers:

● Ford

● General Motors (GM)

● Hyundai

● Nissan

● Stellantis

● Subaru

3.1.1.2. If OEM build-level data is unavailable for GSA-supplied VINs (beyond the minimum required in 3.1.1.1.), the Contractor must provide engineered vehicle data

3.1.1.3. Indicate source of each vehicle data field (e.g., "OEM-derived" or "engineered")

3.1.1.4. If certain vehicle data for data fields are not available for a given vehicle, the Contractor must state an exception and return an error or exception code.

3.1.1.5. Must provide vehicle data Monday through Friday, excluding Federal Holidays, in a structured format as specified in 3.1.2.

Technical Details.

3.1.1.6. Provide an initial list of all OEMs for which they can supply build-level data at the start of the agreement. Additionally, the Contractor must notify GSA Fleet of any changes to this list, including the addition of new OEMs or removal of existing ones, throughout the term of the agreement.

3.1.2. Technical Details

GSA requires the Contractor to be able to support the automated and secure exchange of required vehicle data via restful API. GSA will supply daily VIN queries to the Contractor’s API, and the Contractor will respond in real-time with vehicle data in a structured format such as JSON. The Contractor must also support the ability to test API endpoints and data accuracy in GSAFleet.gov’s development and staging environments.

4. Deliverables

5. Government-Furnished Information

GSA will provide the contractor information relative to the work done hereunder which is the property of the Government and is subject to relevant protection from disclosure as marked. This includes, but is not limited to, lists of VINs requiring attribute decoding, sample vehicle records, API integration documentation, and security protocols necessary to establish secure access to GSAFleet.gov development and production environments.

6. IT Security

The contractor must comply with "2100.1 CIO GSA Information Technology (IT) Security Policy". This IT Security Policy applies to all GSA Federal Employees and GSA contractors or contractors, who manage, maintain, operate, or protect GSA systems or data, all GSA IT systems, and any GSA data contained on or processed by IT systems owned and operated by or on behalf of any of the Services or Staff Offices. The contractor must adhere to all GSA administrative, physical, and technical security controls to ensure all of the Government’s security requirements are met.

SOW

Reference

Description Deliver to Due

3.1 Standardized Vehicle Data

Transfer

Contracting Officer Representative (COR)

Daily

3.1.1.6 List of OEM with Build-Level

Data

Contracting Officer Representative (COR)

At contract inception, and upon any future updates to list

3.1.2 Optional API Test

Environment

Contracting Officer Representative (COR)

Weekly https://www.gsa.gov/directives-library/gsa-information-technology-it-security-policy-16 https://www.gsa.gov/directives-library/gsa-information-technology-it-security-policy-16 https://www.gsa.gov/directives-library/gsa-information-technology-it-security-policy-16

7. Section 508 Requirements

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public who have disabilities must have access to, and use of, information and data that is comparable to people without disabilities.

E201 Application

E201.1 Scope. ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E205 Electronic Content

E205.1 General. Electronic content shall comply with E205.

E205.2 Public Facing. Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

E205.3 Agency Official Communication. Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:

● A. An emergency notification;

● B. An initial or final decision adjudicating an administrative claim or proceeding;

● C. An internal or external program or policy announcement;

● D. A notice of benefits, program eligibility, employment opportunity, or personnel action;

● E. A formal acknowledgement of receipt;

● F. A survey questionnaire;

● G. A template or form;

● H. Educational or training materials; or

● I. Intranet content designed as a Web page.

E205.4 Accessibility Standard (WCAG 2.0). Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (Incorporated by reference, see 702.10.1).

E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents. For non- Web documents, wherever the term "Web page" or "page" appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term "document" shall be substituted for the terms "Web page" and "page". In addition, in Success Criterion in 1.4.2, the phrase "in a document" shall be substituted for the phrase "on a Web page".

E206 Hardware

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E208 Support Documentation and Services

E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E301 General

E301.1 Scope. The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

503 Applications

503.1 General. Applications shall conform to 503.

8. Data Ownership

All data collected by the contractor under this contract is the property of the Government and cannot be shared or used for commercial purposes.

The Contractor must return decoded data directly to GSA and is prohibited from storing or reusing government VINs or related data outside the scope of contract performance. No third-party data reselling or analytics derived from government VIN inputs is permitted.

9. Place of Performance

The tasks under this contract will be performed via secure API integration and associated electronic data exchange. All outputs will be returned electronically through real-time API responses or approved testing environments.

10. Period of Performance

The contract includes a 12-month base period with four 12-month option periods.

Base: TBD Option Period 1: TBD Option Period 2: TBD Option Period 3: TBD Option Period 4: TBD