39162d23695847db8c42e7a6c8fd9dcc
Request for Collaboration (RFC) 2028 Dress Rehearsal and 2030 Census Decennial as a Service (D-X)
COMMERCE, DEPARTMENT OF > US CENSUS BUREAU
New
Rejected
Quick analysis
U.S. Census Bureau RFC seeking industry collaboration for a single‑integrator, turnkey Decennial‑as‑a‑Service (D‑X) model spanning nationwide logistics/warehousing, device lifecycle management, UEM/cellular services, security/continuous monitoring, and integration with Census enterprise platforms.
Scope scale is very large (e.g., ~360k smartphones; ~300k sq ft secure warehouse; high‑volume kitting/shipping/returns; carrier‑agnostic eSIM/UEM). Security posture calls for FedRAMP‑authorized services, NIST SP 800‑53 Rev.5 compliance, ATO, and continuous monitoring/Tier 3 response.
Trace’s core strengths (SATCOM/LEO, NSA TI/CDS, MPE/edge/JADC2, OCONUS logistics/FSR, OCC) only partially overlap this logistics‑ and mobility/UEM‑centric requirement. No direct past performance with Census or equivalent civilian decennial device‑logistics programs is evidenced.
The RFC references possible procurement via MAS or other vehicles, indicating accessible competition paths, but the single‑integrator model and scale favor large logistics/telecom/system integrators with FedRAMP UEM and nationwide warehouse/carrier ecosystems in place.
Scope summary
- Single‑integrator, turnkey Decennial‑as‑a‑Service model across device lifecycle and logistics (nationwide including U.S. territories and remote/island locations).
- FedRAMP‑authorized services, NIST SP 800‑53 Rev.5 compliance, ATO, continuous monitoring, and Tier 3 security response.
- Large‑scale logistics/warehousing, kitting, staging, shipping/returns, reverse logistics, chain‑of‑custody, and real‑time asset visibility (example ~300,000 sq ft secure warehouse).
- UEM/MDM with cross‑platform governance, eSIM support, carrier‑agnostic cellular management, surge capacity, local optimization, and coverage/performance monitoring.
- Integration across logistics, UEM, cellular, and asset systems; integration with Census enterprise platforms for operational visibility.
- Surge/desurge capability referencing 2020 Census peaks (50k–70k devices staged; 100k+ devices shipped/week).
- Operational support for deployments (including remote sites), device readiness validation, maintenance/repair/replacement, and secure end‑of‑life disposition.
Dimension scores
Total
- 42/100
Technical Fit
- 11/20
RFC emphasizes nationwide logistics/warehousing, device/UEM lifecycle, cellular carrier management, and FedRAMP‑authorized as‑a‑service operations. Trace has adjacent managed IT, OCONUS logistics/lifecycle sustainment, OCC monitoring, and enterprise/tactical IT (company_profile), but lacks evidenced large‑scale CONUS device logistics/UEM programs. Limited potential tie‑in via ‘satellite’ mention and remote locations aligns to Trace SATCOM, but that is ancillary to the core requirement (evidence ledger).
Past Performance
- 6/20
No evidence of Census/DoC decennial device‑logistics past performance. Trace has relevant adjacent IT O&M, logistics/sustainment, and managed services with DoD/DISA/Army/USAF (company_profile). This transfers partially but is not direct to the decennial D‑X scope (evidence ledger).
Vehicles / Contract Access
- 7/10
RFC references potential procurement via MAS or other vehicles (evidence ledger). Trace holds GSA MAS (company_profile). However, the final vehicle is not yet specified and this is a special notice, not a task order on a known Trace‑held vehicle. Access is likely but not guaranteed.
Competitive Position
- 3/15
Single‑integrator, large‑scale logistics/UEM/cellular ecosystem with FedRAMP requirements and major warehouse capacity strongly favors large logistics/telecom/SI incumbents. Trace lacks documented equivalent civilian decennial scale and FedRAMP boundary ownership. Competitive position therefore appears weak (evidence ledger + company_profile).
Risk
- 4/15
High risk: new civilian agency relationship; very large scale and immovable timelines; FedRAMP/ATO boundary likely required; nationwide warehouse/logistics/carrier ecosystem; integration across multiple enterprise systems (evidence ledger). These represent substantial execution and compliance risks for Trace absent major teaming.
Strategic Value
- 8/10
Would open a new agency relationship (U.S. Census Bureau/Department of Commerce) with high‑visibility national impact and potential for significant revenue if pursued successfully (evidence ledger).
Compliance
- 3/10
No set‑aside barriers (open), but the RFC calls for FedRAMP authorization, NIST SP 800‑53 Rev.5, ATO, and continuous monitoring/Tier 3 response (evidence ledger). Company profile does not show Trace owning a FedRAMP‑authorized service boundary or nationwide warehouse/carrier capabilities; substantial teaming would be required.
Concerns
- Scale and surge demands (hundreds of thousands of devices; 100k+/week shipments) exceed Trace’s documented delivery infrastructure.
- FedRAMP authorization/ATO boundary likely required; Trace’s profile does not show ownership of a FedRAMP‑authorized platform.
- Nationwide secure warehousing footprint (≈300k sq ft) and sophisticated reverse‑logistics/chain‑of‑custody systems are not evidenced in Trace profile.
- Single‑integrator model concentrates risk in broad domains (logistics, UEM, cellular, security operations) requiring deep partner ecosystem.
- New agency (U.S. Census Bureau) and civilian mission unfamiliarity increase capture and execution risk.
- Incomplete document extraction limits certainty on evaluation criteria and mandatory thresholds.
Teaming opportunities
- Prime‑level nationwide logistics/warehouse provider(s) with secure facilities (~300k sq ft) and reverse‑logistics/chain‑of‑custody systems.
- FedRAMP‑authorized UEM/MDM platform and operations provider (e.g., Workspace ONE/Intune equivalent) with ATO support and continuous monitoring.
- Cellular/MVNO aggregator with eSIM management and multi‑carrier optimization/surge capacity across all states/territories.
- Asset management and integration platform(s) capable of real‑time visibility and integration with Census enterprise systems.
- Census/DoC decennial program experience to strengthen credibility and meet operational nuances.
Competitive position
- Leverage Trace’s OCC for 24/7 continuous monitoring, incident escalation, and surge coordination aligned to D‑X’s monitoring/Tier 3 expectations.
- Offer satellite/LEO backhaul options for remote/island logistics coordination and field operations continuity where terrestrial coverage is weak (ties to ‘satellite’ mention).
- Adapt Trace’s OCONUS logistics/lifecycle sustainment practices to CONUS+territories with partner‑provided secure warehousing and reverse logistics.
Bid/No bid factors
- Single‑integrator requirement and scale likely favor large logistics/telecom/SI incumbents.
- FedRAMP/ATO boundary ownership appears mandatory; Trace lacks an in‑house FedRAMP‑authorized service offering in profile.
- Secure warehousing capacity and nationwide reverse‑logistics at cited scale are not evidenced in Trace profile.
- UEM/cellular ecosystem leadership is central to scope; Trace’s strengths are SATCOM/defense IT rather than enterprise mobility at national census scale.
Documents
Download all
CENSUS D-X RFC 4.14.2026.pdf
Download
CENSUS D-X RFC 4.14.2026.pdf
Download
Summary
Follow-up Request for Collaboration (RFC) to a prior D‑X RFI concerning Dress Rehearsal 2028 and the 2030 Decennial Census "Decennial-as-a-Service" (D‑X). The extraction is heavily fragmented but the file references service areas including U.S. territories and satellite support, mentions UEM and end-to-end/as-a-Service concepts, and includes response submission instructions and possible procurement vehicle references (e.g., MAS); it implies an RFP or further solicitation may follow.
- Follow-up RFC to a D‑X RFI focused on 2028 Dress Rehearsal and 2030 Census Decennial-as-a-Service (D‑X).
- Issuing organization: U.S. Census Bureau (document title and URL to 2030 Census page present).
- Mentions service coverage including U.S. territories and explicit reference to 'satellite' — indicates potential multi‑geography or non‑terrestrial comms considerations.
- Contains the acronym 'UEM' (present in text) and multiple mentions of end-to-end / as-a-Service delivery models — relevant to cloud/managed service and device/endpoint management capabilities.
- Response submission instructions are included and reference a deadline as 'Thurs 14 ... EST' — aligns with the folder-level due-date context; submission expects COMPANY NAME in subject/filename.
- Mentions procurement vehicles (MAS or other) and corporate ability statements — signals non-restricted competition or multiple vehicle routes may be considered.
- Text repeatedly notes 'prepare for D‑X', scale and architecture considerations — suggests requirements will include scalability, architecture design, and operational readiness for a large federal census event.
- Document extraction is incomplete and many lines are redacted/fragmented, limiting visibility into precise requirements, evaluation criteria, performance locations, and security/clearance needs.
CENSUS D-X RFC 4.21.2026 Revised.pdf
Download
CENSUS D-X RFC 4.21.2026 Revised.pdf
Download
Partially reviewed: Too large
Summary
Partially reviewed (selected sections 1 and 3 only; file flagged too_large) RFC from the U.S. Census Bureau describing the Decennial-as-a-Service (D‑X) follow-on collaboration request to inform acquisition planning for the 2028 Dress Rehearsal and 2030 Decennial. The RFC seeks a single-integrator, turnkey, nationwide equipment and endpoint lifecycle management as-a-service solution (FedRAMP-authorized, NIST SP 800-53 Rev. 5, ATO‑authorized) covering device lifecycle, logistics/warehouse operations, UEM/cellular services, security/continuous monitoring, and integration with Census enterprise platforms.
- Customer: U.S. Census Bureau (Decennial program) — mission: 2028 Dress Rehearsal and 2030 Decennial
- Program model: single-integrator, nationwide as-a-service equipment & endpoint lifecycle management ecosystem
- Security/compliance: requires FedRAMP authorization, NIST SP 800-53 Rev. 5 compliance, and ATO authorization; continuous monitoring and Tier 3 security response expected
- Scope areas called out: device/equipment asset management; logistics, warehousing, and deployment operations; mobility/UEM and cellular services; security & continuous monitoring; OEM-agnostic equipment-as-a-service
- Nationwide place-of-performance: all U.S. states and U.S. territories, including remote/island locations and deliveries to field offices, temporary sites, and individual residences
- Estimated device scale: cited support for ~360,000 smartphones, ~20,000 tablets, ~20,000 laptops with need to surge/desurge
- Warehouse sizing: example assumption ~300,000 sq ft of secure warehouse space (additional nonsecure space for GFM anticipated)
- Logistics expectations: high-volume provisioning, kitting, staging, order fulfillment, carrier-agnostic delivery/returns, reverse-logistics, chain-of-custody and real-time asset visibility
- Mobility/cellular specifics: UEM/MDM for cross-platform governance, eSIM support, carrier flexibility and surge capacity, local carrier optimization, coverage/performance monitoring
- Surge history/expectation: references 2020 Census peaks (50k–70k devices staged, 100k+ devices shipped/week) and requirement for robust surge staffing/facility/supply-chain plans
- Integration needs: end-to-end integration across logistics, UEM, cellular, and asset management systems and integration with Census enterprise platforms for incident/asset/fulfillment visibility
- Operational deliverables: site deployment/install support (including remote locations), device provisioning and readiness validation, equipment maintenance/repair/replacement and secure end-of-life disposition
Technical details
Entry: sync
Review status: Up to date
Logical upstream opportunity: 31964
Notice lineage:
- 39162d23695847db8c42e7a6c8fd9dcc (posted 2026-04-21) - current
- dc8216bbfe0c4d05958ca7c4447b93c9
Last synced: 2026-04-21T19:18:22.108802+00:00
Last analyzed: 2026-04-21T19:20:09.398104+00:00
Latest package fingerprint: 84326d5728d71b0edaa05925dded51477eb54e2796db61837103a048b4348313
Latest package notice: 39162d23695847db8c42e7a6c8fd9dcc
Latest package documents: 2
Evidence limitations- CENSUS D-X RFC 4.21.2026 Revised.pdf: partially reviewed (too large)
- 2026-04-21T19:18:22.116629+00:00: 39162d23695847db8c42e7a6c8fd9dcc with 2 docs
Labels
Human notes
No human notes yet.