CENSUS D-X RFC 4.21.2026 Revised.pdf

Request for CollaboraƟon (RFC)

2028 Dress Rehearsal and 2030 Census Decennial as a Service (D-X)

April 14, 2026

(REVISED – APRIL 21, 2026*)

This revised RFC removes all Help Desk related scope and terminology. References to incidents, Ɵckets, case management, HR or Safety, and other ITSM concepts have been eliminated to align its D-X requirement with its intended logisƟcs and XaaS-domain focus. These removals are reflected in the updated document.

*All changes are made using Track Changes.

Version 2.0

Purpose of This Follow-up Request for CollaboraƟon The U.S. Census Bureau (USCB) is issuing this Request for CollaboraƟon (RFC) to follow on the insights gained from the iniƟal Decennial-as-a-Service (D-X) Request for InformaƟon (RFI) SAM noƟce #13PDRD25Q00000007 on 8/14/25, to gather addiƟonal industry input on areas not fully addressed in the original RFI responses. As we conƟnue refining our acquisiƟon strategy, the USCB remains commiƩed to transparency, open communicaƟon, and meaningful collaboraƟon with industry partners. Accordingly, this RFC is designed to:

Address capability areas not fully addressed in the original RFI Validate assumpƟons and operaƟonal models held by the government Encourage industry to share best pracƟces, risks, and integraƟon strategies Strengthen alignment between government expectaƟons and commercial capabiliƟes Support a more informed, evidence-based acquisiƟon approach

The detailed scope and operaƟonal descripƟons provided in the iniƟal D-X RFI conƟnue to serve as the baseline for this RFC. Please consider that informaƟon when assessing capability gaps or dependencies.

The Census Bureau values industry experƟse and seeks to ensure that the D-X soluƟon is shaped through open dialogue, shared understanding, and collaboraƟve problem-solving.

This RFC seeks industry partners capable of delivering a single fully integrated, naƟonwide equipment and endpoint lifecycle management ecosystem, operaƟng under a single-integrator model, to support logisƟcs, equipment handling, cellular services, site deployments, and operaƟonal support funcƟons necessary for the 2028 Dress Rehearsal and 2030 Decennial Census operaƟonal readiness across all states and U.S. territories.

BACKGROUND

The objecƟve of the D-X program is to deliver a complete, as-a-service soluƟon for centralized management of standard equipment and mobile devices that ensures cybersecurity compliance, operaƟonal efficiency, cost transparency, and end-to-end lifecycle accountability, while meeƟng all schedule milestones for the 2028 Dress Rehearsal and 2030 Decennial Census, including site deployment and teardown Ɵmelines, mobile device deployment cycles, ATO approvals, and system go-live dates. The D-X soluƟon must be a turnkey, FedRAMP-authorized, NIST SP 800-53 Rev. 5-compliant, ATO-authorized, as-a-service operaƟonal ecosystem, coordinated under a single-integrator model, and including but not limited to the following capabiliƟes:

Devices, equipment and asset management services o End-to-end management of all standard equipment and devices provided as-a-service, including but not limited to mobile devices, peripherals, networking gear, printers/MFPs, and paper data capture equipment o Mobile device provisioning, configuraƟon, and deployment o Equipment maintenance, repair, replacement and compliant disposiƟon o Inventory accuracy, chain-of-custody tracking, and real-Ɵme asset visibility

LogisƟcs, Warehousing, and Deployment OperaƟons o Warehousing (secure and nonsecure), kiƫng, staging, and order fulfillment for mobile devices and other equipment, with support for flexible delivery opƟons such as informed delivery to individual residences, delivery rerouƟng, and a range of alternaƟve delivery methods proposed by industry to meet large-scale, distributed Census operaƟonal needs.

o Shipping, returns, and reverse-logisƟcs workflows that incorporate flexible delivery and return capabiliƟes, including informed delivery noƟficaƟons, delivery rerouƟng, scheduled pickup windows, carrier-agnosƟc drop-off opƟons, and other alternaƟve delivery/return methods appropriate for naƟonwide and U.S. territory based field operaƟons, supporƟng deliveries to and from field offices, regional census offices, satellite operaƟonal sites, and individual employees’ residences across all states and U.S. territories.

o Support for site deployments across all states and U.S. territories, including remote and island locaƟons, including installaƟon of vendor supplied equipment, peripherals, and other site-based infrastructure required to establish fully operaƟonal field offices.

Mobility, Unified Endpoint Management (UEM), and Cellular Services o UEM for device configuraƟon, compliance, patching, and security baselines, and cross-plaƞorm governance to ensure that all mobile devices, regardless of operaƟng system or management plaƞorm, follow the same security baselines, configuraƟon standards, compliance requirements, and lifecycle controls.

Mobile Device Management (MDM) for device enrollment, policy enforcement, compliance monitoring, and lifecycle controls o CoordinaƟon of mobile device provisioning throughout deployment cycles, including device setup, and readiness checks to ensure assets are fully operaƟonal.

o Cellular service acƟvaƟon, eSIM management, coverage opƟmizaƟon, and surge capacity o IntegraƟon of mobility, idenƟty, and security baselines across all devices

Security, Compliance, and ConƟnuous Monitoring o FedRAMP-authorized, NIST SP 800-53 Rev. 5-compliant hosƟng and security controls, with conƟnuous monitoring and reporƟng aligned to federal requirements o ConƟnuous monitoring, vulnerability management, and incident response coordinaƟon o IntegraƟon of mobility, idenƟty, and endpoint security baselines across all devices and plaƞorms o Incident detecƟon, escalaƟon, and Tier 3 security response coordinated with Census security operaƟons o Secure data handling, media saniƟzaƟon, and compliant disposiƟon processes OperaƟonal Support, Maintenance, and ITSM IntegraƟon o Tier 3 technical support and engineering-level issue resoluƟon integrated with the Government’s ITSM plaƞorm o Incident, request, and change management workflows aligned to Census processes and cross-vendor escalaƟon paths o Performance monitoring, SLA tracking, and escalaƟon governance across all XaaS service areas

ReporƟng, AnalyƟcs, and AutomaƟon o Real-Ɵme dashboards for inventory, logisƟcs, deployments, cellular usage, and support performance o PredicƟve analyƟcs for demand planning, device health, and operaƟonal readiness o AutomaƟon to streamline provisioning, updates, and service workflows

Program, Vendor, and Contract Management o Centralized coordinaƟon under a single-integrator model o Governance model that oversees and coordinates all Everything-as-a-Service providers and government systems o Risk management, performance oversight, and conƟnuous improvement

Transparency and CollaboraƟon

This noƟce is part of our broader effort to build a collaboraƟve, transparent, and industry-informed acquisiƟon environment for D-X. The Census Bureau may work to support a fair, informed, and well-aligned acquisiƟon process through the following:

Publishing relevant operaƟonal plans, schedules, milestones, and mission constraints, as available, to help industry tailor responses to the realiƟes of Census field operaƟons on the 2030 Decennial Census Website (hƩps://www.census.gov/programs-surveys/decennial-census/decade/2030/2030-census-main.html).

Engaging in two-way, iteraƟve communicaƟon, including follow-up quesƟons, reverse vendor days, and other collaboraƟve forums, to explore ideas, clarify concepts, and refine approaches with industry when possible.

InviƟng industry feedback on feasibility, risks, and alternaƟves, and ensuring vendors have equal access to the informaƟon needed to develop well-informed responses.

AddiƟonal InformaƟon for Industry The following areas were not fully addressed in the original RFI and require input to support planning, integraƟon, and acquisiƟon strategy development.

For the purposes of this RFC, “Everything-as-a-Service (XaaS)” refers to a fully managed, subscripƟon-based service model in which vendors deliver the tools, technology, processes, people, and outcomes required to support Census operaƟons. This includes OEM-agnosƟc soluƟons, integrated service delivery, predictable pricing, and end-to-end lifecycle management across mulƟple service domains. The Census Bureau uses XaaS to describe a unified ecosystem of managed services that collecƟvely supports the 2028 Dress Rehearsal and 2030 Census.

Managed Service Integrator (MSI) Model

The USCB is considering a single-integrator model in which one Managed Service Integrator (MSI) provides end-to-end orchestraƟon across all D-X service domains. This MSI would coordinate mulƟple XaaS providers and ensure unified governance, interoperability, and accountability across logisƟcs, mobility, devices, warehousing, asset management, cellular services, site deployments, and support operaƟons. The USCB is seeking industry insight into MSI models, governance structures, and best pracƟces for managing a large, mulƟ-vendor ecosystem under a single-integrator construct.

AssumpƟons:

Demonstrated experience coordinaƟng many different operaƟonal areas, such as logisƟcs, devices, mobility, cellular services, site deployments, and support, so they funcƟon as one integrated service.

Proven tools and processes to keep all systems and vendors aligned, sharing accurate data, and working together smoothly across the enƟre operaƟon.

Can manage and support Decennial Census operaƟons across all states and U.S.

territories, including remote and island locaƟons, making sure equipment, deployments, logisƟcs, cellular services, and support all work together smoothly at naƟonwide scale.

Takes responsibility for delivering consistent, end-to-end service outcomes across all operaƟonal areas, not just managing individual vendors

Command Center AssumpƟons

The D-X vision includes a Command Center that provides a real-Ɵme operaƟonal cross-domain layer that provides conƟnuous visibility, coordinated response, and cross-domain decision support across the D-X ecosystem. It unifies data from logisƟcs, asset management, endpoint management, cellular services, and help desk other XaaS-domain workflows into a single operaƟonal view, enabling leadership and operaƟons teams to monitor service health, track incidents and requests across departments track cross-domain condiƟons and workflow acƟvity, and take acƟon without switching between systems.

AssumpƟons:

Provides a unified operaƟonal picture that enables real-Ɵme monitoring of service health, incident trendsservice-tower condiƟons, and cross-domain workflow status across all D-X service areas XaaS domains.

Enables proacƟve operaƟonsmanagement, including endpoint health monitoring, vulnerability tracking, and field service coordinaƟon, by leveraging integrated data and automated alerƟng across all Ɵers XaaS towers.

Supports coordinated incident response and case rouƟng acrossresponse and workflow rouƟng across IT, HR, Safety, LogisƟcs, and field operaƟonsother D-X service domains, ensuring that leadership and operaƟonal teams can track progress and take acƟon from a single environment.

Operates on a common data foundaƟon that may support AI-driven automaƟon, allowing the system to autonomously resolve requests, execute mulƟ-step workflows, and complete end-to-end acƟons within established policies.

Data Interoperability and IntegraƟon

D-X will rely on a combinaƟon of mulƟple commercial and government systems working together seamlessly. To achieve this, the USCB must understand how vendors approach data integraƟon, API frameworks, synchronizaƟon, and real-Ɵme visibility across disparate plaƞorms, including those operated by federal partners. We are seeking industry insight into best pracƟces, integraƟon paƩerns, and potenƟal challenges associated with building a unified operaƟonal ecosystem that spans both commercial and government environments.

AssumpƟons:

Integrates commercial and government systems into a unified operaƟonal ecosystem that supports seamless data exchange and coordinated service delivery.

Applies federal and commercial best pracƟces to ensure data quality, synchronizaƟon, and real-Ɵme visibility across diverse plaƞorms and partner environments.

Provides end-to-end integraƟon across logisƟcs, UEM, cellular, and asset management systems to enable consistent, mission-ready operaƟons.

OEM-AgnosƟc Device and Equipment As-a-Service Models

The USCB is evaluaƟng OEM-agnosƟc as-a-service models for mobile devices (smartphones, tablets, laptops), office equipment (printers, mulƟfuncƟon devices), paper data-capture equipment (scanners, leƩer openers, guilloƟnes), and office networking equipment (access points, servers, and related infrastructure). These models may include brand-specific or equivalent configuraƟons where required. The USCB seeks industry input on how such as-a-service offerings are typically structured commercially, including provisioning approaches, service levels, lifecycle services, refresh strategies, and performance management. The USCB also requests informaƟon on risks, dependencies, and constraints that should be considered when implemenƟng an enterprise-scale, mulƟ-vendor as-a-service model.

AssumpƟons:

Bundles diverse equipment categories, including mobile devices, office and paper data capture equipment, scanners, and networking hardware, into a unified, scalable, OEM-agnosƟc program that delivers provisioning, kiƫng, and lifecycle services.

Predictable pricing, refresh cycles, and service-level commitments that are in alignment with other large-scale as-a-service programs, including break/fix services, rapid replacement SLAs, inventory pooling, buffer stock strategies, and secure end-of-life disposiƟon.

Supports enterprise-scale device volumes, including approximately 360,000 smartphones, 20,000 tablets, and 20,000 laptops, with the ability to surge or de-surge inventory and services based on operaƟonal tempo and field deployment needs.

Provide cellular service for all mobile devices naƟonwide across all states and U.S.

territories by leveraging the best-performing local carriers in each area, supported by performance monitoring, availability metrics, and rapid carrier remediaƟon pathways.

Support carrier flexibility through eSIM or equivalent technologies, supporƟng local area code assignments where possible and allowing devices to switch carriers or profiles dynamically to maintain coverage, performance, and operaƟonal conƟnuity.

Support OEM-agnosƟc service delivery of mission-specific requirements for brand-specific or equivalent equipment (e.g., printers, scanners, access points, servers), while ensuring consistent provisioning, configuraƟon, support, and lifecycle management across all equipment types.

Integrate with the USCB’s enterprise plaƞorms to support incident management, asset tracking, request fulfillment, and performance reporƟng, enabling unified visibility across all vendors and equipment categories.

Warehouse OperaƟons CapabiliƟes as a Service

Warehouse operaƟons are central to D-X, supporƟng receiving, storage, picking, packing, kiƫng, and shipping for hundreds of thousands of assets. The USCB is exploring warehouse operaƟons as a managed service to improve throughput, accuracy, and scalability. We are seeking industry insight into operaƟonal models, automaƟon technologies, and quality-control pracƟces that support high-volume federal deployments.

AssumpƟons:

Provides warehouse operaƟons as a managed service, including secure and nonsecure storage, receiving Government-Furnished Material (GFM), consumables, kiƫng, staging, order fulfillment, and support for flexible delivery and return opƟons such as informed delivery, rerouƟng, secure locker pickup, carrier-agnosƟc drop-off, scheduled pickups, and prepaid/QR-code return labels.

o ~ 300,000 square feet of secure warehouse space may be required to support the storage, kiƫng, staging, and distribuƟon of mobile devices, equipment, and related materials.

o AddiƟonal nonsecure space will be needed for Government Furnished Materials (GFM), the volume of which is not yet known

UƟlizes diverse naƟonwide shipping methods, returns, and reverse-logisƟcs workflows that maintain chain-of-custody, provide real-Ɵme asset visibility, and support high-volume throughput using automaƟon, roboƟcs, and opƟmizaƟon technologies across all operaƟons.

Supports delivery of mobile devices, accessories, and vendor-provided equipment to field offices, regional census offices, temporary operaƟonal sites, and individual employees’ residences.

Delivers coordinated site deployment and readiness services, including provisioning, aiding equipment installaƟon, and full field office readiness validaƟon throughout deployment cycles.

Surge Readiness and Scalability

The Decennial Census requires rapid, high-volume scaling during peak operaƟonal periods. As previously shared, during the 2020 Census, vendors staged, provisioned, and kiƩed 50,000– 70,000 mobile devices at peak and shipped more than 100,000 devices per week in advance of in-field data collecƟon. To achieve full geographic office coverage, site deployment teams established approximately 25–30 new operaƟonal sites per week across mulƟple waves. As we prepare for D-X, the USCB must understand how vendors plan for surge staffing, facility expansion, supply chain acceleraƟon, device provisioning, and large-scale logisƟcs under similar or greater Ɵme-compressed condiƟons. We are seeking industry input on surge models, lead Ɵmes, and proven strategies for supporƟng mobilizaƟons of this magnitude.

AssumpƟons:

Design and execute surge models capable of supporƟng peak volumes similar to the 2020 Decennial Census requirements (e.g., 50,000–70,000 devices staged at peak, 100,000+ weekly shipments, and 25–30 new site deployments per week).

Deliver commercial strategies, staffing models, and facility expansions to enable rapid scale-up and scale-down during Ɵme-compressed mobilizaƟons, and what lead Ɵmes are typically required to achieve these peak census volumes.

Deliver and manage mulƟple provisioning models, including Zero Touch Mobility, and other large-scale approaches, that support distributed Census operaƟons while maintaining quality, accuracy, and configuraƟon consistency during high-volume surges.

Sustainability and Reuse Models

Sustainability is a priority for the USCB. D-X will require environmentally responsible approaches to device reuse, kit reuse, and recycling. We are seeking industry insight into sustainable pracƟces, cerƟficaƟons, and reuse models that can be applied at naƟonal scale.

AssumpƟons:

PrioriƟze the reuse of mobile devices, accessories, kits, and Government-Furnished Material (GFM) consumables, supported by environmentally responsible lifecycle and disposiƟon pracƟces.

PrioriƟze sustainability pracƟces or cerƟficaƟons consistent with large-scale federal operaƟons.

Risk IdenƟficaƟon and MiƟgaƟon

Given the scale and complexity of D-X, the USCB is proacƟvely idenƟfying risks that could impact service delivery, integraƟon, or operaƟonal readiness. We are seeking candid industry insight into potenƟal risks, dependencies, and miƟgaƟon strategies based on commercial experience with large, mulƟ-domain service environments.

Encouraging Open Dialogue The goal of the Census Bureau, regarding the D-X program, is to facilitate candid, construcƟve discussions with construcƟve feedback. It is through these ongoing engagements we plan to work with industry on the following:

IdenƟfy gaps or assumpƟons in the government’s current approach Consider alternaƟve models or architecture IdenƟfy and integrate leading industry best pracƟces

Suggest areas where addiƟonal government transparency would improve soluƟon design

Provide opportuniƟes for informaƟon exchanges, or collaboraƟve workshops as deemed necessary

Our goal is to ensure that the D-X acquisiƟon is informed by real-world experƟse, proven commercial pracƟces, and shared understanding.

DISCLAIMER AND IMPORTANT NOTES

This RFC issued solely for planning purposes only and does not consƟtute as a Request for Proposal (RFP) or a promise to issue a Request for Proposal (RFP) in the future. Further, the USCB is not seeking proposals and will not accept unsolicited proposals at this Ɵme. Interested parƟes are advised that the U.S. Government will not pay for any informaƟon or administraƟve costs incurred in response to this RFC; all costs associated with responding to this RFC will be solely at the interested party’s expense. Not responding to this RFC does not preclude parƟcipaƟon in any future RFP, if any is issued. Lastly, this RFC does not commit the Government to contract for any supply or service whatsoever. The Government is not obligated to respond to any submissions received under this RFC.

Any organizaƟon responding to this noƟce should ensure that its response is complete and sufficiently detailed to allow the Government to determine the organizaƟon’s qualificaƟons to perform the work. Respondents are advised that the Government is under no obligaƟon to acknowledge receipt of the informaƟon received or provide feedback to respondents with respect to any informaƟon submiƩed. The Government may contact individual respondents for addiƟonal follow-up or to request addiƟonal informaƟon. AŌer a review of the responses received, a pre-solicitaƟon synopsis and solicitaƟon may be published.

AŌer a review of responses, the Government may at its discreƟon contact any respondent to obtain clarificaƟon on informaƟon provided.

RESPONSE SUBMISSION INSTRUCTIONS

Interested vendors shall submit a response no later than Thursday, May 14, 2026, at 4:00 PM EST. All submissions shall be sent to pithy.t.sar@census.gov and paul.w.boesch@census.gov.

The email subject line shall include the following description: “Census D-X RFC Response- COMPANY NAME”.

The overall submission shall be prepared in Microsoft Word, using Times New Roman, 12-point font. The submission shall follow the section page limitations identified below.

Section Title Maximum Page Count A Company Overview Information 1 B Integrated Service Delivery and OperaƟonal

CoordinaƟon

C AcquisiƟon Approach and EvaluaƟon ConsideraƟons

D Closing Thoughts and Feedback 3

The USCB is seeking practical responses over conceptual or marketing-driven answers.

Company Overview InformaƟon:

All interested companies shall provide the following information:

Business name, company website, and headquarters address.

Name of company representative, business title, and contact information.

Unique Entity ID.

Socio-economic status, business size, and size standard/applicable.

Applicable and available North American Industry Classification System (NAICS) codes related to this acquisition.

Applicable and available GSA contracting vehicle and include contract numbers, agency, POC, and KO. Examples include GWACs, GSA Federal Supply Schedules, MAS, Other Transaction Agreement (OTA), Direct Award, or other Best in Class (BIC) vehicles related to this acquisition.

Brief description of your relevant core corporate abilities that relate to the requirements stated in RFC.

Integrated Service Delivery and OperaƟonal CoordinaƟon:

1. Given the nationwide scale of D-X and the need to manage logistics, warehousing, mobile devices, site deployments, cybersecurity, support services, and overall operational performance as one coordinated service across all states and U.S.

territories, describe your organization’s ability to deliver this full scope as a unified, as-a-service solution. Identify how you would ensure everything works together smoothly.

2. Describe your experience delivering nationwide as-a-service solutions that combined any of the following: logistics, device management, site deployments, cybersecurity, and support operations into one coordinated service across all states and U.S. territories.

Include examples where these services were delivered under a unified performance and accountability model. Additionally, describe how you coordinated across service areas to meet strict operational schedules and milestones.

3. Describe your experience supporting delivery and return workflows that serve a distributed operationally driven organization, including field offices, regional offices, temporary operational sites, and individual employees’ residences across all states and U.S. territories. Include examples of how you managed flexible delivery options, chain-of-custody, identity verification, and return logistics at this scale.

4. Explain how your organization integrates multiple service areas, such as logistics, device provisioning, site readiness, security, and support services, into a single ecosystem with shared data, coordinated workflows, and unified reporting. Describe the tools, processes, and governance structures you use to maintain consistency, quality, and accountability across all service areas and partners.

AcquisiƟon Approach and EvaluaƟon ConsideraƟons:

1. If the USCB were to move forward with a solicitaƟon for these services, idenƟfy evaluaƟon factors that may be most effecƟve in determining capability in meeƟng the full scope and objecƟves described through this RFC? Provide specific capabiliƟes, performance areas, or qualificaƟons that may be emphasized in the evaluaƟon and describe why.

2. The USCB intends to streamline and innovate this requirement and resultant solicitaƟon, evaluaƟon, and award. Please review the Periodic Table of AcquisiƟon InnovaƟons at hƩps://acquisiƟongateway.gov/periodic-table and idenƟfy innovaƟve techniques that may provide value to the USCB and describe why.

3. The USCB is seeking industry feedback to refine the requirements and idenƟfy the appropriate acquisiƟon approach. Specifically, the USCB welcomes input on the type of requirement approach that makes the most sense for this effort (e.g., Statement of ObjecƟves (SOO), Performance Work Statement (PWS), etc.), as well as recommendaƟons related to contract type structure, performance metrics, and industry best pracƟces related to this effort. This feedback will assist the USCB in shaping the most appropriate procurement framework and in developing complete and effecƟve requirements for any future solicitaƟon. Provide recommendaƟons and describe why.

Closing Thoughts and Feedback:

1. Were there any objecƟves, assumpƟons, or service descripƟons in this RFC that may benefit from addiƟonal clarificaƟon or refinement. What specific informaƟon would help industry beƩer understand the USCB’s intent and provide more informed input?

2. Is there addiƟonal informaƟon about your organizaƟon’s experience, capabiliƟes, or operaƟonal strengths, parƟcularly in delivering large, integrated, naƟonwide service models, that would help the USCB beƩer understand your ability to support the objecƟves described in this RFC?

3. Is there anything important to this effort that the USCB has not asked about but should consider? Please limit your response to informaƟon specific to this RFC.

CONFIDENTIALITY

InformaƟon submiƩed must be available at no cost or obligaƟon to the Government.

Submissions become Government property and will not be returned, including any proprietary informaƟon; any informaƟon you consider proprietary should be clearly marked as such.

The Government may consider addiƟonal communicaƟon as part of the ongoing market research and may reach out at a later date requesƟng more informaƟon. Service providers who do not respond to this Market Research form are not excluded from any resulƟng solicitaƟon(s).