2.1.1-Attachment A SOW.pdf

Office of Asset and Facilities Management

U.S. Department of Homeland Security 500 12th ST, SW, Washington, D.C. 20024

28 April 2026

STATEMENT OF WORK FOR:

Coworking Space Request

Overview

Request to obtain coworking space funding for a 12-month term at multiple locations nationwide, to support the U.S. Immigration and Customs Enforcement (ICE). The required coworking sites and initial workspace allocations for over 300 FTEs at 90 locations (type to be confirmed) are listed below.

Scope of Work

To provide flexible workspace (private offices and/or workstations) for assigned ICE personnel at approved coworking locations across the listed cities, as coordinated with approved vendor and ICE

POC.

SCOPE:

• Term: 12 months of coworking space use, starting upon approval/award.

• Locations: See full site list below.

• Workspace Details: Each site will offer a mix of workstations and private offices.

• Services Included:

o Desk or private office o Wi-Fi access o Printing privileges (per-site monthly limits) o Ability to scale up or down based on Government need o Fulfillment of satisfactory office spaces for no less than 97% of associated personnel

(currently 321 of 330 at time of solicitation/award)

Locations (by State):

o AL: Huntsville, Montgomery o AZ: Casa Grande, Chandler, Concho, Eloy, Mesa, Phoenix, Scottsdale, Tucson o CA: Long Beach, Morgan Hill, Rocklin, Sacramento, San Bernadino, San

Diego, San Francisco, Santa Ana o CO: Colorado Springs o CT: Hartford o DE: Wilmington o FL: Bradenton, Ft. Myers, Gainesville, Jacksonville, Miami, Niceville, Orlando, Sarasota, Tampa, West Palm Beach o GA: Atlanta, East Point, Leesburg o HI: Honolulu o IL: Chicago, Rock Island o IN: Indianapolis o KS: Kansas City, Manhattan o KY: Louisville o LA: Baton Rouge o MA: Boston, Burlington o MD: Baltimore, Frederick o ME: Caribou, Portland, Scarborough o MI: Grand Rapids o MN: Fort Snelling o MO: Kansas City, St. Louis o MS: Gulfport, Vicksburg o MT: Savage o NC: Cary, Charlotte, Raleigh o NE: Omaha o NH: Manchester o NJ: Mt. Laurel, Newark o NY: New York o OH: Brooklyn Heights, Westerville o OR: Portland, Roseburg o PA: Allentown, Altoona o PR: San Juan o RI: Crawford o SC: Columbia, Summerville o SD: Hot Springs, Mitchell o TN: Knoxville, Nashville, o TX: Austin, Bryan, El Paso, Houston, San Antonio o UT: West Valley City o VA: Norfolk, North Chesterfield o VT: Derby, Williston o WA: Seattle o WI: Maynes o WV: Martinsburg, Milton o WY: Casper

Note: Full physical addresses to be requested as needed; only operational locations will move forward.

Note: Any alternative building for a given location must be within 45 miles of the listed city it is being used as an alternative for.

Note: List of cities is subject to change based on Government need.

Required Contract Language

OCIO/ Data Management Unit (DMU) - Data Ownership Contract Requirements Language

1. Accessibility of Government-owned Data

All stored program data associated with this acquisition shall be owned by the Government.

As such, it shall be made accessible to the Government in accordance with the Minimum Data Access Capability described below. This accessibility is required to allow full data transparency, flexibility in performing data analytics, and integration with data from other government programs.

In addition to the Minimum Data Access Capability, the Government prefers, but does not require, that program data be accessible via Enhanced Access Capabilities as described below.

Definition of “program data”: Program Data refers to any data resulting from ICE and DHS organizational activity. Examples of such data include but are not limited to administrative data resulting from human resource, management, and financial actions, as well as operational data resulting from performance of the ICE mission.

Definition of “associated with this acquisition”: Program Data is associated with an acquisition if it is created by DHS organizational activity that is facilitated by the contractor. Examples of how a contractor might facilitate organizational activity follow:

o Program data is stored by contractor personnel o Program data is stored by software that is managed, developed, or used by the contractor o Program data is stored in a repository that is managed, developed, or used by the contractor

2. Minimum Data Access Capability

• The current version of all Program Data is accessible to the Government within 24 hours of request, as well as on any pre-defined schedule as required by the Government.

Data access can occur by various means, provided that Government security requirements are met, and data is accessible in a format that is acceptable to the Government. Examples include but are not limited to APIs that are consumable by the Government, files made available for Government download (e.g., Excel Spreadsheets), or direct database query by federal or contractor personnel.

• The contractor shall format program data accessed by the Government to anticipate the maximum file size of any data to be accessed. File size shall be small enough to assure rapid processing by government applications.

• The contractor shall provide the means for the Government to interpret accessible Program Data as follows:

o Data elements and groupings of data elements shall be clearly identifiable by labels embedded in the data itself, or by a separate schema or file layout which allows such elements and groupings to be identified.

In the case of a relational database schema defined through Data Definition Language (DDL), data elements would be represented as columns, and groupings of data would be represented as tables. In addition, relationships between tables would be described as foreign key relations.

o Labels or names used to identify data elements and groupings of data elements shall be approved by the Government. In addition, each label or name shall be associated with a government approved definition which describes the content of data held therein.