Baseline Performance ObjecƟves (BPO)

DraŌ v2

2028 Census Test and 2030 Census

Decennial as a Service (D-X)

September 23, 2026

U.S Census Bureau

D-X Baseline Performance ObjecƟves

Page ii of 54

TABLE OF CONTENTS

1 IntroducƟon

1.1 Background

1.2 Purpose

2 Scope

2.1 Overview

2.2 D-X Service Domains

2.3 D-X Device Requirements

2.4 Out of Scope AcƟviƟes

2.5 D-X OperaƟng Environment

2.5.1 D-X Program Phases

2.5.2 D-X Contract OperaƟng Modes

2.5.3 Geographic and OperaƟonal Coverage

2.5.4 Scale, OperaƟng Environment, and Tempo

2.6 D-X OperaƟonal Baseline

2.7 BPO Framework

3 D-X Service Domain Requirements Framework

3.1 Service Domain 1 BPO Statement – Contract, Program, and MSI Service CoordinaƟon

3.1.1 Contract and Program Management Mandatory Requirements and Constraints

3.1.2 MSI Service CoordinaƟon and Governance Mandatory Requirements and Constraints

3.2 Service Domain 2 BPO Statement – Systems Development and Maintenance

3.2.1 Technical IntegraƟon Mandatory Requirements and Constraints

3.2.2 Data Management, Data Quality, and ReporƟng Mandatory Requirements and Constraints

3.2.3 Command Center OperaƟons Mandatory Requirements and Constraints

3.2.4 SoŌware and Licensing Management Mandatory Requirements and Constraints

3.3 Service Domain 3 BPO Statement – Device, Equipment, and Asset Lifecycle Management Services

3.3.1 Managed Device and Equipment Lifecycle Services Mandatory Requirements and Constraints ... 26

3.3.2 Asset Lifecycle, Accountability and Inventory Management Mandatory Requirements and Constraints 27

3.3.3 Provisioning, Zero-Touch, and Readiness Services Mandatory Requirements and Constraints

3.3.4 Lifecycle Sustainment and Asset Decommissioning/DisposiƟon Services Mandatory Requirements and Constraints

Page iii of 54

3.3.5 Technical and OperaƟonal Support Mandatory Requirements and Constraints

3.3.6 On-site Paper Data Capture (PDC) IT Support Mandatory Requirements and Constraints

3.4 Service Domain 4 BPO Statement - LogisƟcs, Warehousing, Kiƫng, DistribuƟon, Site Deployment and Teardown

3.4.1 Warehousing Mandatory Requirements and Constraints

3.4.2 Kiƫng Mandatory Requirements and Constraints

3.4.3 LogisƟcs, Shipping and Delivery Mandatory Requirements and Constraints

3.4.4 Site Deployment and InstallaƟon Mandatory Requirements and Constraints

3.4.5 Site Teardown and Decommissioning Mandatory Requirements and Constraints

3.5 Service Domain 5 BPO Statement – Mobility, ConnecƟvity, and UEM

3.5.1 ConnecƟvity Services Mandatory Requirements and Constraints

3.5.2 UEM Mandatory Requirements and Constraints

3.5.3 Technical and OperaƟonal Support Mandatory Requirements and Constraints

3.6 Service Domain 6 BPO Statement – Security, Compliance, and ConƟnuous Monitoring

3.6.1 Security, Compliance, and ConƟnuous Monitoring Mandatory Requirements and Constraints

4 Performance Requirements

5 Applicable Standards, RegulaƟons, and OperaƟng Constraints

5.1 Applicable Standards and RegulaƟons

5.2 OperaƟng Constraints

6 Deliverables and Work Products

7 Glossary and Acronyms

8 BPO AƩachments

1 IntroducƟon 1

1.1 Background 2

The United States Census Bureau (USCB), a principal staƟsƟcal agency within the Department of 3 Commerce (DOC), is the naƟon’s leading source of quality data about the people, places, and 4 economy of the United States. The USCB produces the naƟon’s official populaƟon and housing 5 staƟsƟcs and conducts the Decennial Census, as required by ArƟcle I, SecƟon 2 of the United 6 States ConsƟtuƟon. 7

The Decennial Census provides the populaƟon and housing data used for congressional 8 apporƟonment, redistricƟng, and major federal funding decisions. It is one of the Federal 9 Government’s largest and most complex civilian operaƟons. The 2030 Decennial Census will 10 require the mobilizaƟon, deployment, support, tracking, recovery, and accountability of 11 hundreds of thousands of devices, technology assets, equipment items, soŌware licenses, 12 connecƟvity services, Government-furnished materials, and operaƟonal resources. The 13 operaƟons will span the United States and its Territories. 14

To support this mission, the USCB is transforming how criƟcal operaƟonal services are acquired, 15 integrated, and delivered through the Decennial-as-a-Service (D-X) Program. 16

D-X is the USCB’s integrated as-a-service environment that unifies technology, devices, logisƟcs, 17 connecƟvity, and support operaƟons under one coordinated ecosystem. All contractor-provided 18 capabiliƟes, technology, devices, equipment, logisƟcs, mobility, deployment, asset lifecycle 19 management, technical integraƟon, security, and operaƟonal support, are delivered as managed 20 services to enable a seamless and effecƟve 2028 Census Test and 2030 Decennial Census. The 21 D-X soluƟon operates under a Managed Services Integrator (MSI) model, establishing a single 22 point of accountability for the integraƟon, coordinaƟon, and delivery of all as-a-service offerings 23 across the D-X ecosystem. 24

1.2 Purpose 25

The purpose of D-X is to ensure operaƟonal readiness, reduce risk, and provide accountable, 26 end-to-end service-based management of all devices, equipment, and services used across 27 decennial operaƟons. D-X consolidates and delivers all operaƟonal capabiliƟes as-a-service, with 28 centralized accountability, coordinated service delivery, and measurable performance against 29 Government-defined outcomes. 30

D-X provides the structure, automaƟon, and oversight required to support one of the naƟon’s 31 largest civilian mobilizaƟons with speed, accuracy, and confidence, protecƟng the integrity of 32 the data that underpins representaƟon, funding, and planning across the United States and its 33

Territories. All D-X services shall be operaƟonal within a FedRAMP moderate or higher 34 environment at the Ɵme of award, using an authorizaƟon obtained independently without 35 Census Bureau sponsorship. 36

2 Scope 37

2.1 Overview 38

D-X requires the contractor to deliver a comprehensive, scalable, and auditable InformaƟon 39 Technology (IT) and logisƟcs soluƟon that supports all USCB data-collecƟon acƟviƟes for the 40 2028 Census Test and the 2030 Decennial Census. This integrated approach means the 41 contractor must unify IT, logisƟcs, device lifecycle, and field-support acƟviƟes into one 42 coordinated delivery model rather than separate service towers. 43

The contractor shall manage the complete lifecycle of all required devices, equipment, and 44 services. This includes planning, buying, staging, provisioning, shipping, installing, operaƟng, 45 maintaining, supporƟng, tracking, and decommissioning these assets. These lifecycle acƟviƟes 46 must funcƟon as a unified, coordinated process that connects IT, logisƟcs, provisioning, security, 47 inventory management, and reporƟng, rather than as separate operaƟonal tasks. 48

The scope of D-X is performance-based and outcome-oriented. This document establishes the 49 Government’s required outcomes, mandatory requirements, constraints, and minimum 50 capabiliƟes while providing contractors with the flexibility to propose commercially proven 51 service-delivery models and innovaƟve approaches that saƟsfy or exceed the Government’s 52 objecƟves. 53

The D-X scope includes all services, devices, equipment, soŌware licenses, supporƟng 54 processes, integraƟons, security controls, reporƟng capabiliƟes, and operaƟonal support 55 funcƟons necessary to achieve the D-X mission outcomes described in this document and its 56 aƩachments. These items fall enƟrely within the contractor’s responsibility under the D-X 57 program. The scope includes the management, reporƟng, integraƟon, cybersecurity, 58 compliance, and closeout acƟviƟes necessary to sustain operaƟonal readiness and end-to-end 59 lifecycle accountability across the D-X environment. This includes operaƟng within applicable 60 federal security and compliance environments, support for Government system integraƟons, 61 support for asset and inventory accountability, and provision of documentaƟon, reporƟng, and 62 evidenƟary arƟfacts necessary for surveillance, audits, and contract administraƟon. 63

The D-X operaƟng environment is dependent on certain Government-furnished informaƟon, 64 approvals, and condiƟons, including site informaƟon, system interface requirements, policy 65 constraints, and other dependencies idenƟfied in this solicitaƟon. 66

2.2 D-X Service Domains 67

The following service domains define the funcƟonal scope of D-X and establish the 68 organizaƟonal framework for the BPOs described in SecƟon 2.7. 69

Table 1: D-X Service Domains 70 Service Domain In-scope Services

1. Contract, Program, and MSI Service CoordinaƟon

Contract transiƟon-in and transiƟon-out Contract management Contract governance Staffing management Contract risk management CommunicaƟons management Program governance Schedule management Program quality management Program risk management ConƟnuous improvement Data call/audit support OperaƟonal readiness MeeƟngs and reporƟng End-to-end service orchestraƟon across all D-X service domains, Government stakeholders, operaƟonal teams, and suppliers (e.g., subcontractors, contractors, original equipment manufacturers (OEMs), and partners)

MSI governance ExecuƟve decision support ExecuƟve reporƟng Integrated master schedule (IMS) and dependency management CorrecƟve acƟon and service change coordinaƟon Cross-domain engineering escalaƟon coordinaƟon ConƟnuous improvement and lessons learned management

2. Systems Development and Maintenance

IntegraƟon with USCB systems and soluƟons OperaƟonal data integraƟon Data management, data quality and reconciliaƟon Command center and related soŌware licenses Dashboards, reporƟng, predicƟve analyƟcs, and automaƟon SoŌware-as-a-Service (SaaS) SoŌware and licensing management Engineering services

3. Device, Equipment and Asset Lifecycle Management Services

End to end management of all equipment and devices provided as-a-service, to include, but not limited to:

o Provisioning and configuraƟon, quality assurance, zero-touch/bulk device provisioning, repair/replacement, saniƟzaƟon and disposiƟon, reissuing, asset management and inventory to

Service Domain In-scope Services include related soŌware licenses, technical/operaƟonal support, asset recovery/quaranƟne handling, security/OperaƟng System (OS) patching.

o Supply Chain-as-a-Service (SCaaS) o Devices-as-a-Service (DaaS): Smartphones, tablets, laptops o Equipment-as-a-Service (EaaS): Office equipment, peripherals, and related support items; paper data capture (PDC) equipment;

Network/site infrastructure (e.g., access points, servers, networking hardware) o Onsite PDC support o On-site support for break/fix

4. LogisƟcs, Warehousing, Kiƫng, DistribuƟon, Site Deployment and Teardown

LogisƟcs, warehousing, distribuƟon, and reverse logisƟcs to include:

o LogisƟcs-as-a-Service (LaaS) o Secure warehouse capacity o Non-secure warehouse / Government furnished materials (GFM) staging capacity o Receiving and intake o Inventory storage and control o Kiƫng service o GFM handling o Quality assurance (QA)/Packaging verificaƟon service o Outbound shipment service o Residence/alternate delivery coordinaƟon o Remote/island delivery planning service o Device returns/reverse logisƟcs o Scheduled pickup/carrier-agnosƟc return coordinaƟon o Shipping carrier performance and excepƟon management o LogisƟcs management system soŌware licenses o Warehouse management system soŌware licenses o LogisƟcs/site engineering resoluƟon

Site acƟvaƟon and deployment readiness to include:

o Site package coordinaƟon service o Site surveys/site assessments o Site readiness validaƟon o Site installaƟon o Quality Assurance

Site teardown and decommissioning o Teardown and return iniƟaƟon o Data export and portability service o Decommissioning-as-a-Service (DEaaS) o Closeout reporƟng and final reconciliaƟon

5. Mobility, ConnecƟvity, and Unified Endpoint Management (UEM)

Unified endpoint management-as-a-Service (UEMaaS) Mobility as-a-Service (MaaS) Cellular acƟvaƟon service eSIM / profile management service

Service Domain In-scope Services

Coverage validaƟon and remediaƟon service Telecom expense management (TEM) service Standby / suspension / de-surge line management Resilience and conƟnuity Mobility engineering resoluƟon SoŌware licenses

6. Security, Compliance, and ConƟnuous Monitoring

Security operaƟons support Security-as-a-Service (SECaaS) Authority to Operate (ATO) support Incident response support in alignment with USCB (e.g., forensic support, authorizaƟon support) ConƟnuous monitoring service Supply chain / soŌware transparency service Secure data handling and media saniƟzaƟon control Security / authorizaƟon engineering resoluƟon

2.3 D-X Device Requirements 71

D-X device-agnosƟc requirements are defined in BPO AƩachment 3: D-X Device and UEM 72 requirements. The Contractor’s proposed D-X soluƟon shall be scalable and responsive to the D-73 X operaƟonal baseline, which will define expected volumes, deployment profiles, and site types 74 at final release. Device allocaƟon shall reflect user needs as defined in this document and 75 AƩachment 2 – DX 2030 Decennial Fieldwork Personas. 76

2.4 Out of Scope AcƟviƟes 77

The following acƟviƟes are not included within the scope of this acquisiƟon unless specifically 78 idenƟfied elsewhere in the solicitaƟon: 79

HosƟng or operaƟng USCB Enterprise Systems 80 Development or support of Census Data CollecƟon ApplicaƟons 81 Security monitoring for USCB Enterprise Systems 82 Security monitoring for D-X Laptops Enterprise IdenƟty Management 83

The Government reserves the right to clarify, add, or modify scope boundaries through 84 solicitaƟon amendments or contractual modificaƟons. Contractors must explain how they will 85 work with these Government-provided items so that their plans stay on schedule and 86 operaƟons are not disrupted. 87

2.5 D-X OperaƟng Environment 88

The D-X soluƟon shall operate within a complex operaƟng environment characterized by 89 geographically distributed locaƟons, varying operaƟng condiƟons, rapidly changing workload 90 demands, and mulƟple phases of Decennial Census operaƟons. The contractor shall design, 91 implement, and maintain a soluƟon capable of supporƟng the full census lifecycle and all 92 operaƟonal modes while maintaining operaƟonal readiness, accountability, security, real-Ɵme 93 visibility, and service conƟnuity across the integrated D-X ecosystem. Contractor soluƟons must 94 remain effecƟve across these varying condiƟons, including different phases, operaƟng modes, 95 and geographic environments. 96

All contractor acƟviƟes shall be planned and executed in alignment with USCB and Decennial 97 Census Program governing arƟfacts, to include but not limited to: 2030 Census IntegraƟon & 98 ImplementaƟon Plan (IIP), 2030 Census OperaƟonal Delivery Management Plan (ODMP), the 99 2030 Census Test & EvaluaƟon Master Plan (TEMP), 2030 Census IT Defect Management Plan, 100 Decennial Systems Engineering Management Plan (SEMP), and all other applicable Decennial 101 program documents, plans, standards and governance requirements. 102

2.5.1 D-X Program Phases 103

The D-X service environment shall support, at a minimum, the following phases: 104

Contract TransiƟon-in and MobilizaƟon – Startup acƟviƟes required to establish the 105 program management structure, staffing, governance, faciliƟes, systems, and 106 operaƟonal processes necessary to begin contract execuƟon and support early readiness 107 milestones. 108

Design, Development and IntegraƟon – Detailed design, soluƟon configuraƟon, 109 interface development, service integraƟon, planning refinement, and establishment of 110 the operaƟonal and technical foundaƟon needed for downstream validaƟon and 111 execuƟon. 112

OperaƟonal ValidaƟon – Controlled validaƟon acƟviƟes used to test, verify, and refine 113 the integrated D-X environment, including readiness assessments, funcƟonal validaƟon, 114 process verificaƟon, and operaƟonal proofing. 115

2028 Census Test – ExecuƟon of D-X services in support of the 2028 Census Test 116 environment, including deployment, operaƟons, support, reporƟng, performance 117 visibility, and issue resoluƟon under test condiƟons representaƟve of the larger 118 decennial environment. 119

OpƟmizaƟon – Ongoing improvements, correcƟve acƟons, tesƟng and refinement 120 acƟviƟes conducted during development and integraƟon phase and following the 2028 121 Census Test to improve quality, readiness, efficiency, scalability, and mission support 122 prior to full 2030 execuƟon. 123

2030 Decennial Census MobilizaƟon and Peak OperaƟons – Large-scale ramp-up, 124 deployment, and sustained support of field operaƟons at naƟonal scale, including high-125 volume provisioning, distribuƟon, site acƟvaƟon, device readiness, ongoing support, and 126 service conƟnuity during peak demand periods. 127

2030 Decennial Census Close-out (Decommission, Returns, and DisposiƟon) – 128 ExecuƟon of reverse logisƟcs, asset recovery, reconciliaƟon, recycling, saniƟzaƟon, site 129 tear down and related funcƟons. 130

Contract TransiƟon-out – CompleƟon of final turnover, documentaƟon delivery, data 131 export, final reconciliaƟons, and transiƟon support to the Government or successor 132 contractor, as required by the resulƟng contract. 133

These lifecycle phases are not intended to be interpreted as rigidly isolated acƟviƟes. Certain 134 services may begin in one phase and conƟnue into another, and some enabling acƟviƟes, such 135 as governance, reporƟng, integraƟon, security, and asset accountability, may apply across all 136 phases of execuƟon. 137

2.5.2 D-X Contract OperaƟng Modes 138

The Contractor shall support mulƟple OperaƟng Modes under the D-X environment. OperaƟng 139 Modes describe the service-delivery condiƟons or operaƟonal posture under which the 140 Contractor must perform. At a minimum, the D-X soluƟon shall support: 141

Test Mode – Service delivery under controlled, trial, or validation conditions used to 142 confirm functionality, readiness, and operational performance before broader 143 execution. 144

Steady-State Mode – Routine and sustained service delivery under expected demand 145 and normal operating conditions. 146

Surge Mode – Accelerated or elevated service delivery conditions involving increased 147 deployment volume, higher transaction rates, expanded staffing, compressed timelines, 148 or simultaneous large-scale operational activities. 149

Contingency Mode – Service delivery under disrupted or adverse conditions, including 150 continuity operations, failover scenarios, alternate routing, recovery actions, emergency 151 staffing, remote or island-area service degradation, or other unexpected mission-152 impacting circumstances. 153

Disposition / Closeout Mode – Service delivery during shutdown, returns, 154 reconciliation, sanitization, disposition, and transition-out activities, when operational 155 focus shifts from deployment and support to controlled recovery and closeout. 156

OperaƟng modes may occur within the same lifecycle phase or overlap phases. For 157 example, surge mode may occur during 2030 Decennial Census mobilizaƟon and peak 158 operaƟons, while conƟngency mode may arise in any phase where failures, delays, or 159 disrupƟons threaten mission performance. Similarly, closeout mode may begin while some 160 operaƟonal support services remain acƟve for selected Decennial Census sites or user groups. 161

The contractor-developed Performance Work Statement (PWS) shall describe how services, 162 staffing, capacity, governance, reporƟng, logisƟcs, and support capabiliƟes will adjust to 163 accommodate each operaƟng mode. 164

2.5.3 Geographic and OperaƟonal Coverage 165

The service soluƟon shall support operaƟons in urban, suburban, rural, remote, island, and 166 other geographically challenging environments without unacceptable degradaƟon in service 167 performance, security, visibility, or accountability. 168

OperaƟonal coverage includes, at a minimum: 169

Six Regional Census Centers (RCCs) that oversee decennial operaƟons; 170 Decennial Census sites of varying sizes, with a minimum of one established in each state; 171 Island Area Offices (IAOs) in American Samoa, the Commonwealth of the Northern 172

Mariana Islands (CNMI), Guam, and the U.S. Virgin Islands; 173 Puerto Rico Area Office (PRAO); 174 Paper Data Capture Center (PDCC) in Charlestown, Indiana; 175 Census Headquarters in Washington, D.C.; 176 Bowie Computer Center (Bowie, MD); and 177 Any temporary or surge locaƟons required to support operaƟons. 178

Coverage includes, but is not limited to: 179

Census Office Employees 180 Census Field Managers 181 Census Field Supervisors 182 Enumerators / Census Takers 183 Paper Data Capture On-site Employees 184 Paper Data Capture Remote Employees 185 United States Postal Service (USPS) Partners 186 Other authorized users requiring devices, equipment, kits, connecƟvity services, logisƟcs 187 support, or other D-X services. 188

2.5.4 Scale, OperaƟng Environment, and Tempo 189

The D-X soluƟon shall operate at naƟonwide scale and support rapid, high-volume, 190 Ɵme-compressed mobilizaƟon cycles. Contractors must demonstrate the ability to sustain 191 enterprise-level throughput and operaƟonal tempo across the United States and its Territories. 192

The contractor shall maintain the capacity, infrastructure, and operaƟonal readiness to support 193 the following baseline volumes: 194

Opening 25–30 operaƟonal Decennial Census sites per week during peak deployment 195 cycles 196

Provisioning and acƟvaƟng approximately 10,000 mobile devices per day, including 197 enrollment, configuraƟon, and readiness validaƟon 198

Shipping approximately 70,000 equipment kits per week, with full traceability and 199 delivery confirmaƟon 200

ExecuƟng surge operaƟons that exceed baseline throughput during Ɵme-compressed 201 mobilizaƟon periods 202

SupporƟng replacement and break/fix cycles throughout the deployment lifecycle 203 Processing returns and reverse-logisƟcs workflows at high volume during closeout 204 ConducƟng close-out and disposiƟon acƟviƟes in accordance with federal requirements 205

The D-X operaƟng environment encompasses significant logisƟcal, technical, and operaƟonal 206 complexity. Contractors shall maintain the personnel, faciliƟes, systems, inventory capacity, 207 automaƟon, and conƟngency capabiliƟes required to sustain mission performance under both 208 rouƟne and peak condiƟons. This includes: 209

NaƟonwide coverage across the United States and its Territories (to include urban, rural, 210 remote, and island locaƟons) 211

High-volume warehousing and fulfillment operaƟons 212 Integrated technical and mobility environments 213 Secure, compliant, and conƟnuously monitored systems 214 Coordinated cross-domain workflows aligned with the MSI operaƟng model 215

The contractor shall support a sustained operaƟonal tempo that enables conƟnuous 216 deployment, provisioning, logisƟcs movement, and returns processing throughout the D-X 217 lifecycle. This tempo must remain stable and reliable during: 218

RouƟne operaƟons 219 Surge periods 220 ConƟngency condiƟons 221 Time-compressed deployment cycles 222

High-volume closeout and disposiƟon phases 223

Contractors must demonstrate the ability to maintain throughput, accuracy, and operaƟonal 224 control at all tempos while ensuring mission-ready performance and uninterrupted service 225 delivery. 226

2.6 D-X OperaƟonal Baseline 227

The D-X operaƟonal baseline establishes a common planning framework to support proposal 228 development, pricing, capacity planning, and soluƟon design. These baseline assumpƟons 229 ensure proposal comparability but do not limit the contractor’s obligaƟon to deliver sufficient 230 capacity, scalability, resiliency, security, or operaƟonal readiness to meet contractual 231 requirements, including performance under variable, surge, or Ɵme-compressed operaƟonal 232 condiƟons. 233

The Government will provide the D-X operaƟonal baseline as aƩachments at the Ɵme of final 234 solicitaƟon release. The operaƟonal baseline may include the following elements: 235

D-X device and equipment catalog and esƟmated quanƟƟes 236 Kiƫng profiles 237 Site type definiƟons, site profiles, and site locaƟon data 238 Deployment/wave planning data 239 Geographic distribuƟon assumpƟons 240 OperaƟonal volume esƟmates 241 Workforce planning assumpƟons 242

If detailed informaƟon (e.g., site locaƟon data) is not available or releasable at the Ɵme of 243 solicitaƟon, the Government will provide interim planning assumpƟons sufficient to support 244 proposal development and pricing. 245

2.7 BPO Framework 246

The D-X BPO Framework defines the results the contractor must deliver under D-X and the 247 minimum requirements and constraints that apply across all service domains. It focuses on what 248 outcomes are required while allowing the contractor to select how to achieve them using 249 commercially proven, service-based approaches. 250

The BPOs serve as the foundaƟon for proposal development, soluƟon design, and performance 251 management throughout the contract. These requirements establish the baseline operaƟonal, 252 technical, security, logisƟcs, lifecycle management, and governance outcomes necessary to 253 support the 2028 Census Test and the 2030 Decennial Census. 254

For each service domain, the BPO framework consists of: 255

A BPO statement defining the required operaƟonal outcome for the domain 256 Mandatory requirements and operaƟng constraint idenƟfying the required funcƟons, 257 capabiliƟes, limitaƟons, standards, condiƟons, and operaƟng constraints that must be 258 addressed as part of the proposed soluƟon; and 259

Performance Requirements (AƩachment 4) and Service Levels (AƩachment 5) 260

Contractors shall develop a Performance Work Statement (PWS) that maps to each BPO 261 Statement and mandatory requirements and describes how the proposed soluƟon will meet or 262 exceed the baseline outcomes. The PWS shall address processes, tools, controls, service levels, 263 governance, and cross-domain coordinaƟon needed to deliver the required results. 264

The D-X environment operates under a single-integrator model, where one Managed Service 265 Integrator (MSI) is accountable for coordinated delivery across all service domains, unified 266 workflows, authoritaƟve data sources, synchronized dependencies, integrated reporƟng, and 267 consistent execuƟon. 268

Performance Requirements are established in SecƟon 4. Contractors shall incorporate the 269 Government’s performance standards and acceptance evidence into their PWS and proposed 270 Quality Assurance Surveillance Plan (QASP). 271

Except where expressly required, the Government does not prescribe internal contractor 272 organizaƟon, staffing models, or technical methods. The Contractor remains fully responsible 273 for proposing a complete operaƟonal soluƟon capable of achieving all baseline requirements 274 under all operaƟng modes. 275

3 D-X Service Domain Requirements Framework 276

The D-X service domains define the structure for the required capabiliƟes under this acquisiƟon. 277 Each domain specifies the operaƟonal outcomes, mandatory requirements, constraints, and 278 performance standards that the Contractor must saƟsfy to support the 2028 Census Test and 279 the 2030 Decennial Census under a unified Everything-as-a-Service (XaaS) model. 280

The requirements in this secƟon establish the minimum operaƟonal, technical, security, 281 logisƟcs, governance, integraƟon, and lifecycle-management requirements for each domain. 282 Contractors shall design and deliver integrated capabiliƟes that operate as a unified, as-a-283 service environment under the D-X MSI model. Although domains are organized discretely for 284 clarity, they shall funcƟon as coordinated elements of a single integrated operaƟonal 285 environment with shared data structures, synchronized workflows, and cross-domain 286 accountability. Successful performance requires coordinated delivery, unified and authoritaƟve 287 data structures, interoperability across commercial logisƟcs, delivery, mobility, and Government 288 systems, disciplined dependency management, cross-domain governance, security aligned 289 integraƟons, and real-Ɵme operaƟonal visibility through the D-X Command Center. Contractors 290 shall account for these interdependencies when developing their proposed soluƟons and shall 291 not assume that any service domain may be performed independently or in isolaƟon. 292

The Contractor’s PWS shall clearly demonstrate how the proposed soluƟon achieves the 293 required outcomes, saƟsfies all mandatory requirements, and supports cross-domain 294 dependencies, performance standards, acceptance evidence, and operaƟonal readiness. 295 Contractors shall idenƟfy and incorporate any addiƟonal requirements, controls, capabiliƟes, 296 processes, governance mechanisms, service levels, operaƟonal procedures, performance 297 measures, and supporƟng acƟviƟes necessary to deliver a complete, secure, scalable, resilient, 298 and mission-ready soluƟon capable of supporƟng rouƟne operaƟons, surge condiƟons, and 299 Ɵme-compressed deployment cycles. 300

3.1 Service Domain 1 BPO Statement – Contract, Program, and MSI Service 301 CoordinaƟon 302

The contractor shall serve as the single accountable MSI responsible for delivering unified 303 governance, coordinated program management, and end-to-end service orchestraƟon across all 304 D-X service domains. This service domain establishes the enterprise-level management 305 foundaƟon that ensures all providers, subcontractors, vendors, carriers, plaƞorms, and 306 operaƟonal teams deliver services as one integrated, cohesive D-X ecosystem aligned with 307 Census Bureau mission requirements. 308

The MSI shall operate a centralized governance model that provides standardized reporƟng, 309 cross-domain visibility, coordinated execuƟon, and consistent performance oversight across 310 logisƟcs, mobility, cellular services, asset lifecycle management, warehousing, security, and 311 technical integraƟon. The MSI shall ensure that all service areas operate from unified baselines, 312 synchronized workflows, and shared data structures, enabling the Government to assess 313 readiness, validate performance, and maintain unified operaƟonal control throughout all D-X 314 operaƟng modes. The contractor’s PWS should clearly show how these service domains will 315 operate under one integrated plan rather than separate domain-specific workflows. 316

The contractor shall coordinate and maintain enterprise-level integraƟon across commercial 317 logisƟcs, delivery, mobility, and Government systems, ensuring seamless data interoperability, 318 authoritaƟve-source alignment, real-Ɵme operaƟonal visibility, and traceable, high-quality data 319 flows across all plaƞorms. The MSI shall establish and maintain cross-domain dependency 320 management, risk idenƟficaƟon and miƟgaƟon processes, coordinated escalaƟon pathways, and 321 decision-support structures that enable proacƟve operaƟonal management, conƟnuous 322 improvement, and mission conƟnuity. 323

The MSI shall support transparency and iteraƟve communicaƟon with the Government through 324 collaboraƟve forums, clarificaƟon cycles, and Ɵmely delivery of governance informaƟon. The 325 contractor shall ensure that governance funcƟons are fully operaƟonal early in the contract 326 period and provide the documentaƟon, management controls, and operaƟonal support 327 required for the Government to oversee the integrated D-X environment, maintain 328 accountability, and ensure mission-ready performance across all service domains. 329

The MSI shall have formal coordinaƟon authority under the Government-approved DX 330 governance framework to direct cross-provider operaƟonal acƟons, enforce approved standards 331 and workflows, resolve provider conflicts, and ensure unified execuƟon. 332

The MSI is responsible and accountable for the performance of its subcontractors and any 333 designated providers performing under the MSI’s control. 334

3.1.1 Contract and Program Management Mandatory Requirements and 335 Constraints 336

The contractor shall: 337

1. Establish and maintain a governance and management structure sufficient to plan, 338 control, report, and conƟnuously improve performance under the D-X contract. 339

2. Establish and maintain a Program Management Office (PMO) aligned to the latest 340 version of the Project Management InsƟtute (PMI) Project Management Body of 341 Knowledge (PMBOK®) Guide that is fully operaƟonal 60 calendar days aŌer the Program 342 Manager completes USCB onboarding. 343

3. Develop, implement, and maintain an integrated Program and Contract Management 344 Plan that outlines the management framework, governance processes, contract 345 administraƟon, performance management, staffing approach, risk and issue 346 management, subcontractor controls, deliverable management, quality management, 347 communicaƟons, and reporƟng needed to execute all contract requirements. 348

4. Establish and maintain a governance structure that supports rouƟne and recurring 349 Government engagement including but not limited to weekly status reports and 350 meeƟngs, monthly cost and schedule reporƟng, and required governance reviews (e.g., 351 Risk Review Boards, Program Change Request Boards) in accordance with Government 352 reporƟng expectaƟons. 353

5. Establish and maintain a schedule management capability that plans, tracks, and reports 354 all contract deliverables, milestones, dependencies, and criƟcal path acƟviƟes. 355

6. Develop, maintain, and execute a Government-approved D-X operaƟonal schedule that 356 aligns deployment waves, device provisioning, logisƟcs movements, carrier acƟvaƟon, 357 training events, and field readiness milestones. 358

7. Develop and maintain a comprehensive, accurate, and up-to-date contractor 359 organizaƟon chart that visually represents the structure, reporƟng relaƟonships, and key 360 personnel within the D-X program. 361

8. Conduct Program Management Reviews (PMRs) to provide integrated visibility into D-X 362 performance. 363

9. Properly manage all contractor personnel and subcontractors, ensure staff conƟnue to 364 meet required qualificaƟons, background invesƟgaƟon, and training requirements, and 365 that key personnel departures are reported to the Government within 24 hours. 366

10. Maintain visibility into subcontractor roles, performance, and risk posture throughout 367 contract execuƟon and ensure subcontractors performing criƟcal funcƟons meet the 368 same performance, security, and compliance expectaƟons that apply to the prime 369 contractor. 370

11. Track all risks, issues, and dependencies and report all Priority 1 (P1) risks to the 371 Government within 24 hours, with recurring risk and issue reporƟng provided to support 372 Ɵmely decision-making and conƟnuity. 373

12. Achieve full operaƟonal readiness through a structured transiƟon-in plan that includes 374 knowledge capture, process mapping, and joint walkthroughs. 375

13. Submit complete and accurate deliverables and work products by the contractual due 376 dates. 377

14. Support internal and external audits and data calls. 378

15. Submit accurate monthly invoices by the 15th of each month and provide draŌ invoices 379 three business days prior. 380

16. Execute all contractual changes with full adherence to the approved change-381 management process for contractor-managed systems, assets, and workflows. 382

17. Provide complete operaƟonal documentaƟon, data extracts, and training necessary to 383 enable transiƟon to the Government or a successor contractor. 384

18. Maintain pricing structures for services, including surge, special projects, and non-385 standard work, that are clear, itemized, and auditable. 386

19. Follow documented change control processes to include Government review and 387 approval for all contract changes with operaƟonal or cost impact. 388

20. Propose and implement periodic improvements that enhance performance, reduce 389 costs, or increase efficiency. 390

21. Meet priority-based Service Level Agreements (SLAs) (P1/P2/P3) within defined 391 response and resoluƟon targets across service domains and operaƟng modes. 392

22. Develop and maintain a D-X Disaster Recovery (DR) and Business ConƟnuity Framework 393 that integrates and aligns with the USCB’s ConƟnuity of OperaƟons Plans (COOP), 394 InformaƟon System ConƟngency Plans, and Disaster Recovery (DR) Plans to ensure 395 conƟnuity of mission-criƟcal operaƟons during large-scale disrupƟons. This includes 396 disrupƟons requiring alternate faciliƟes, redundant systems, failover capabiliƟes, or 397 affecƟng personnel, faciliƟes, logisƟcs channels, carriers, or service-tower workflows. 398

23. Establish, document, and maintain clearly defined emergency acƟvaƟon roles that 399 support conƟnuity of D-X operaƟons during disrupƟons requiring surge response, rapid 400 escalaƟon, or acƟvaƟon of alternate workflows. These roles must align with D-X 401 operaƟonal domains, including hardware lifecycle, logisƟcs conƟnuity, command center 402 escalaƟon, failure mode recovery, and business conƟnuity, and must specify 403 responsibiliƟes, acƟvaƟon triggers, staffing requirements, and communicaƟon pathways. 404

24. Support the orderly compleƟon of work at the end of this order by ensuring the transfer 405 of knowledge, data, arƟfacts, documentaƟon, and responsibiliƟes back to the 406 Government, and when applicable, to an incoming Contractor, while maintaining 407 conƟnuity of operaƟons, safeguarding Government informaƟon and assets, and closing 408 out all order-related acƟviƟes. 409

25. Align with USCB and Decennial Census Program governing arƟfacts, to include: 2030 410 Census IntegraƟon & ImplementaƟon Plan (IIP), 2030 Census OperaƟonal Delivery 411 Management Plan (ODMP), the 2030 Census Test & EvaluaƟon Master Plan (TEMP), 412 2030 Census IT Defect Management Plan, Decennial Systems Engineering Management 413 Plan (SEMP), and all other applicable Decennial program documents, plans, standards 414 and governance requirements. 415

26. Develop, maintain, and execute a LogisƟcs Support Plan for decennial census employees 416 and site deployments covering kiƫng, storage, shipping, delivery, reverse logisƟcs, and 417 site deployment. 418

27. Develop, maintain and execute a Decommissioning Plan that covers, at a minimum: 419 asset recovery, transfer, reƟrement, saniƟzaƟon, disposal, and disposiƟon of all D-X 420 assets while maintaining asset accountability and operaƟonal readiness. 421

3.1.2 MSI Service CoordinaƟon and Governance Mandatory Requirements and 422 Constraints 423

The contractor shall: 424

1. Implement, maintain, and operate an MSI governance framework that clearly defines 425 cross-domain coordinaƟon responsibiliƟes, decision authoriƟes, required governance 426 forums, escalaƟon pathways, and designated parƟcipants across all D-X service domains. 427

2. IdenƟfy, coordinate, and facilitate resoluƟon of cross-domain issues, service 428 introducƟons, major service changes, and unresolved operaƟonal excepƟons, ensuring 429 that roles, ownership, and required inputs for resoluƟon are clearly assigned across all 430 affected service domains. 431

3. Exercise MSI operaƟonal authority in accordance with the D-X governance framework to 432 direct operaƟonal acƟons, drive coordinated decision making, iniƟate cross-contractor 433 and USCB Enterprise IT escalaƟons, ensure adherence to approved workflows, and 434 maintain service conƟnuity across providers and domain towers. 435

4. IniƟate and manage escalaƟons in accordance with the Government-approved 436 escalaƟon matrix, which specifies the triggers, rouƟng paths, noƟficaƟons, and handoff 437 responsibiliƟes the contractor must follow. 438

5. Provide decision support that uses validated, authoritaƟve operaƟonal data and includes 439 required inputs, analysis, and operaƟonal impacts as defined in the D-X governance 440 framework. 441

6. Document recommendaƟons for operaƟonal decisions meeƟng Government-defined 442 high-impact criteria, including assumpƟons, opƟons considered, and raƟonale. 443

7. Coordinate acƟviƟes across operaƟonal teams, suppliers, and Government stakeholders 444 to maintain synchronized, unified service delivery, ensuring clear handoffs, role clarity, 445 and visibility into cross-domain dependencies. 446

8. IdenƟfy, document, and miƟgate operaƟonal risks using MSI-defined processes aligned 447 to the Government’s risk framework, including required risk categories, inputs, and 448 criteria for escalaƟon or miƟgaƟon planning. 449

9. Monitor, analyze, and report on operaƟonal performance across all managed services 450 using Government-approved Key Performance Indicators (KPIs), data sources, and 451 reporƟng formats, ensuring consistent interpretaƟon of performance outcomes across 452 service domains. 453

10. Maintain full compliance with all USCB governance, security, and operaƟonal policies as 454 they relate to MSI coordinaƟon responsibiliƟes, including cross-domain coordinaƟon, 455 decision support, and escalaƟon processes. 456

11. Lead conƟnuous improvement iniƟaƟves that address cross-domain coordinaƟon 457 effecƟveness, governance processes, and integrated service delivery performance, using 458 Government-approved methods for idenƟfying, evaluaƟng, and implemenƟng 459 improvements. 460

12. Maintain high levels of Government stakeholder saƟsfacƟon through transparent 461 communicaƟon and effecƟve coordinaƟon with Government stakeholders in accordance 462 with the stakeholder engagement approach defined in the D-X governance framework. 463

13. Coordinate cross-domain training readiness, role mapping, training dependencies, 464 training schedules, system access issues, and remediaƟon of training gaps across D-X 465 service domains. 466

3.2 Service Domain 2 BPO Statement – Systems Development and 467 Maintenance 468

The contractor shall deliver a fully integrated D-X technical environment that unifies all required 469 systems, plaƞorms, and data domains, including integraƟon with USCB and Decennial soluƟons, 470 into a secure, interoperable, and operaƟonally cohesive ecosystem. The integrated environment 471 must ensure that every D-X service area: logisƟcs, warehousing, mobility, cellular services, asset 472 lifecycle management, security, and site deployments, operates from consistent, synchronized, 473 and authoritaƟve data sources that support mission-ready performance at naƟonwide scale. 474 The contractor shall deliver integrated technical, data-management, and command center 475 capabiliƟes that provide consistent data quality, end-to-end traceability, secure informaƟon 476 exchange, and real-Ɵme visibility across all service domains, forming the foundaƟon of the D-X 477 operaƟonal picture. 478

The contractor shall provide a Government-facing operaƟonal picture that consolidates cross-479 domain data into a single, role-appropriate interface. This operaƟonal picture must present 480 real-Ɵme visibility into logisƟcs movements, device and asset status, cellular acƟvaƟon and 481 performance, provisioning and deployment readiness, inventory condiƟons, and excepƟon 482 events. It must support operaƟonal awareness, anomaly detecƟon, coordinated response, and 483 decision-making across all D-X operaƟng modes (see secƟon 2.5.2 for details), including rouƟne 484 operaƟons, surge periods, and incident response. 485

The contractor shall deliver integrated technical, data management, and command center 486 capabiliƟes that ensure consistent data quality, end-to-end traceability, secure informaƟon 487 exchange, and Ɵmely visibility into operaƟonal condiƟons across all service domains. The 488 integrated environment must support Government oversight, cross-provider coordinaƟon, 489 predicƟve planning, and operaƟonal response through standardized data structures, controlled 490 integraƟons, unified reporƟng, and cohesive cross-domain workflows. 491

The contractor shall design and operate these capabiliƟes within a governance model that 492 aligns all XaaS providers under a single-integrator construct, ensuring interoperability, 493 accountability, and consistent execuƟon across the D-X ecosystem. The soluƟon must 494 incorporate real-Ɵme monitoring, automated alerƟng, and coordinated workflow rouƟng; apply 495 authoritaƟve source rules; and maintain compliance with federal security and data handling 496 requirements. Together, these capabiliƟes must provide the Census Bureau with a consolidated, 497 decision-ready operaƟonal environment that enables proacƟve management of the 2028 Dress 498 Rehearsal and 2030 Decennial Census. 499

3.2.1 Technical IntegraƟon Mandatory Requirements and Constraints 500

The contractor shall: 501

1. Develop and maintain all required interfaces with USCB systems, including but not 502 limited to USCB Human Resources (HR) and InformaƟon Technology Service 503 Management (ITSM) systems and ensure they are fully operaƟonal to support defined 504 data exchange and operaƟonal requirements. 505

2. Integrate all required ITSM processes with the Census Bureau’s exisƟng ServiceNow 506 instance, including incident management, onboarding, lost/missing/stolen asset 507 reporƟng, and oĪoarding, by the start of performance, demonstrated through 508 measurable Ɵcket-flow accuracy, response and resoluƟon metrics, and complete lifecycle 509 record synchronizaƟon. 510

3. Integrate commercial logisƟcs, delivery, mobility, and Government systems into a unified 511 operaƟonal ecosystem that enables secure and authoritaƟve data exchange, 512 synchronized and traceable status flows, shared and decision-ready reporƟng, 513 coordinated service delivery, and real-Ɵme operaƟonal decision support through the D-X 514 Command Center. 515

4. Integrate the asset management system with USCB enterprise systems in accordance 516 with defined interface and data-exchange requirements. 517

5. Provide an integrated, idenƟty-validated, enƟtlement-based order-management 518 capability that coordinates with required enterprise systems and supports approved 519 device/equipment profiles, lifecycle orders, rouƟng, and full chain-of-custody visibility. 520

6. Deliver an enƟtlement-based fulfillment capability that synchronizes with exisƟng 521 workflows, enforces role-based access, manages lifecycle orders, executes approvals, 522 and maintains real-Ɵme visibility and auditability. 523

7. Provide conƟnuous monitoring of interfaces and generate alerts for failures. Implement 524 and track correcƟve acƟons as needed with manual workarounds limited to 525 Government-approved cases. 526

8. Establish authoritaƟve asset, service, and transacƟon data definiƟons sufficient to 527 reconcile device, equipment, logisƟcs, mobility, site, security, and closeout status across 528 the D-X ecosystem. 529

9. Use automated data feeds where technically feasible and uƟlize manual updates only 530 when automated feeds are unavailable or Government-approved. 531

10. Maintain seamless connecƟvity across all required data sources and plaƞorms. 532

11. Maintain seamless integraƟon with Government-approved systems including but not 533 limited to asset and idenƟty management, HR, and financial systems, ensuring successful 534 data exchanges and daily synchronizaƟon accuracy. 535

12. Update integraƟons as program requirements evolve. 536

13. Handle all data exchanged through these interfaces securely and in compliance with 537

USCB security and privacy policies. 538

14. Maintain interoperability across diverse systems and adherence to open standards. 539

15. Design, implement, and sustain the D-X technical integraƟon architecture and interface 540 control documentaƟon, including Government-approved ApplicaƟon Programming 541 Interfaces (API) and data-feed integraƟons. 542

16. Enable real-Ɵme or near-real-Ɵme data ingesƟon and processing across the integraƟon 543 fabric. 544

17. Conduct funcƟonal, performance, and security tesƟng for all interfaces prior to 545 deployment and aŌer any change, with documented results and Government approval 546 before producƟon release. 547

18. Deliver high-quality integrated data across all pipelines. 548

19. Scale integraƟon workloads dynamically to meet demand without service degradaƟon, 549 and with the ability to handle a 2× surge in data volume. 550

20. AutomaƟcally detect, log, and resolve all integraƟon errors, failed transacƟons, and data 551 mismatches within the Ɵmelines specified by the USCB, with full traceability and without 552 impacƟng operaƟonal schedules. 553

21. IdenƟfy and implement improvements that enhance integraƟon speed, reliability, or 554 data quality, measured by quarterly opƟmizaƟon proposals and documented reducƟons 555 in latency, failures, or data defects. 556

22. Maintain controlled, documented, and Government-approved configuraƟon baselines 557 for all systems and integraƟons. 558

23. Assess, test, and document the operaƟonal impact of all proposed changes prior to 559 implementaƟon. 560

24. Maintain reliable, uninterrupted integraƟon workflows across all D-X service domains 561 and implement automated recovery capabiliƟes that promptly detect and remediate 562 workflow failures to preserve conƟnuous data flow. 563

25. Validate end-to-end PDC readiness by ensuring all project level and program level 564 producƟon tesƟng demonstrates measurable performance, accuracy, throughput, and 565 reliability against Government-defined benchmarks. 566

26. Fully and accurately integrate all PDC equipment with Census systems to achieve reliable 567 workflow, data alignment, and system connecƟvity. 568

27. Implement and sustain the D-X digital twin by maintaining a conƟnuously updated 569 virtual model of key operaƟonal elements, including assets, shipments, site readiness, 570 inventory, support demand, recovery acƟvity, and geographic risk, using common data 571 inputs and synchronized event streams. 572

28. Validate the digital twin accurately mirrors real-world condiƟons through measurable 573 indicators such as data-refresh compliance, event-processing…