DTAM Attachment - Deliverables and Work Products.pdf

Decennial Transformation and Application Modernization

(DTAM)

Deliverables and Work Products

April 17, 2026

U.S. Census Bureau

DTAM Attachment - Deliverables and Work Products

1.0 Deliverables

Deliverable Section C Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

Contract Management Plan (CMP)

3.1.1.1 Procurement Governance

Defines the Contractor’s organizational structure, management controls, and processes used to administer and oversee the order.

Shall include, but is not limited to:

• Contractor team capabilities.

• Contractor team & CPMO organizational structure, roles, and points of contact.

• Staffing Plan that details the required resources, skillsets, onboarding, retention, suitability, training, and staffing strategies throughout the life of the order.

• Subcontractor Management Plan that describes how subcontractors are managed, coordinated, overseen, and integrated into order execution.

• Governance structure and decision-making protocols.

• Project management procedures and controls.

• Schedule management (contract-level).

• Cost management.

• Quality management & continuous improvement.

• Risk and issue management.

• Communication management (contract-administrative).

• Compliance management

• Schedule and scope management

• Governance

• Project management procedures and policies, including a process for project tracking in terms of identified deliverables, working documents, work products and cost.

10 business days after the Program Manager has been cleared, and no more than 3 business days after updates have been made

Electronic upload to Government Repository to

COR/GPMO

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

Monthly Contract Administration Status Report

(MCASR)

3.1.1.2 Staffing

and Subcontractor Management

Summarizes monthly contract performance, updates to management artifacts, task status, risks, issues, and support needs.

Shall include, but is not limited to:

• Any updates made to the CMP, QCP, Risk and Mitigation Plans, Order Communications and Decision Logs, Staffing Plans, and Subcontractor Management Plan.

• Updated Staffing Matrix

• Monthly Internal Use Software (IUS) Monthly Report.

• The identification, summary description, and status of in-progress and newly assigned tasks.

• Progress against agreed-to milestones.

• Risks and issues that may impede progress.

• Request for support required from the Decennial Census Program.

• Identification of delivered work products/working documents/deliverables and pending action items.

Monthly Electronic to COR/GPMO along with the monthly invoice submission

Kick-off meeting

3.1.4.1 Kick-

Off Meeting

Provides initial alignment between the Contractor and the Government by introducing key personnel, reviewing scope and expectations, and establishing the processes and protocols for order execution.

Shall include, but is not limited to:

• An introduction of Contractor key personnel and other significant team members.

• A review of the background, scope, schedule and deliverables.

Within five

(5) business days of contract award

Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• An overview of the activities required to initiate and manage the contract.

• A review of invoice procedures and expectations for contract-level reporting.

• 3Discussion of initial coordination, communication expectations, and operational readiness steps.

Personnel Documentation Records

3.1.1.2 Staffing

and Subcontractor Management

A complete and update-to-date collection of all personnel-related documentation for Contractor and subcontractor staff assigned under this contract to provide to the Government upon request in the format and timeframe specified by the Government.

Shall include, but is not limited to:

• Suitability Records

• Training Completion Records

• Certification Evidence

• Role Assignments

• Onboarding/Exit documentation

As required Electronic upload to Government Repository to

COR/GPMO

PMR Meeting 3.1.4.4 Program Management Review (PMR)

Delivers a comprehensive, data-driven evaluation of program performance, cost, schedule, and projected future outcomes to the

GPMO.

Shall include, but is not limited to:

• Executive summary of program status

• Performance metrics and analysis

• Cost, schedule, and risk status

• Issues, dependencies, and mitigation actions

• Trends, variances, and root-cause analysis

• Forecasted activities and projected program outlook

• Action items with owners and due dates

First submission 60 days after contract start; As defined by the COR thereafter.

Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

Quality Control Plan (QCP)

3.1.2.3 Program Quality Management &

QASP

Performance

Identifies metrics, indicators, and review processes supporting quality control under this order.

Shall include, but is not limited to:

• Alignment of the indicators, indexes and metrics to the Decennial’s stated objectives and measures of success.

• A description of the review/audit process, its documentation, methods of internal review, identification of staff position(s) performing the reviews, and the frequency of the reviews.

• A description of the approach and procedures for communicating with the Government, to include handling corrective actions; identifying and implementing potential improvements to the Decennial Census Program services.

• Identification of with which lesson(s) learned are addressed in each update of the QCP.

Annually Electronic upload to Government Repository to

COR/GPMO

Transition-In Plan (TIP)

3.1.3.1 Transition-In

Defines the Contractor’s approach for onboarding resources obtaining access, transferring knowledge, and achieving Full Operational Capability (FOC) of systems or services.

Shall include, but is not limited to:

• Transition-in risks and mitigation plans

• Transition-in team roles, responsibilities, and communication lines

• Stakeholder mapping for transition-in

• Knowledge and document management processes

• Staffing plan for transition-in

• Background investigation submission schedule and process

• Onboarding process and required training

• GFE/GFI and systems access plans

10 business days after PM is cleared

Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• Document reviews and initial artifact assessments

Transition-Out Plan (TOP)

3.1.3.2 Transition-Out

Describes how the Contractor will wind down activities, transfer knowledge, return assets, and support close-out.

Shall include, but is not limited to:

• Transition-out risks and mitigation plans

• Transition-out team roles, responsibilities, and communication lines

• Stakeholder mapping for transition-out

• Knowledge and document handover processes

• Knowledge transfer and cut-over plans

• Staffing ramp-down plan

• Access revocation and separations process

• GFE/GFI return and asset disposition plan

• Schedule baseline and milestones for transition-out

• Coordination and governance approach

• Close-out activities and final materials

• Documented reviews and final artifact assessments

90 business days before the end of the contract

Electronic upload to Government Repository to

COR/GPMO

Weekly Status Report (WSR) & Meeting

3.1.4.2 Weekly

Status Report and Meeting

Provides weekly updates on progress, risks, issues, staffing, and key events.

Shall include, but is not limited to:

• A summary of the work accomplished in the previous week and work planned for the current and following week.

• Risks and mitigations of risks, to include barriers to completing work, and impacts on quality, schedule and cost and proposed solutions.

• Issues and resolutions to issues.

• Staffing status.

• Any other topics of significance to report.

Weekly Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• Key issues and opportunities and events for the upcoming week.

Monthly Cost and Schedule Report

3.1.4.3 Monthly

Cost and Schedule Report and Meeting

Provides a consolidated, data-driven view of the Contractor’s monthly cost performance and schedule execution.

Shall include, but is not limited to:

• Current and cumulative cost status by CLIN and SLIN

• Labor and non-labor cost breakdowns aligned to the CWBS and DWBS

• Planned vs actual cost and schedule performance, including variances

• Forecasted costs, level of effort, and funding requirements through the period of performance

• Identification and explanation of significant cost or schedule variances and trends

• Schedule status, critical path impacts, and milestone performance

• Funds invoiced to date and reconciliation against obligated funding

• Identification of risks or issues affecting cost or schedule performance

• Supporting data required for invoice validation and performance tracking

Monthly Electronic upload to Government Repository to

COR/GPMO

Internal Use Software (IUS) Monthly Report

3.1.1.2 Staffing

and Subcontractor Management

Contractor’s inputs to a Government drafted report that documents all IUS-related lifecycle events, costs, enhancements, and disclosures for Census financial reporting.

Shall include, but is not limited to:

• Name

• Labor Category

• Hourly Rate

Monthly Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• Number of hours worked per current invoicing period

• Project Phase

• Task

Decennial Census Program Interface Catalog

3.3.1 System

of Systems Architecture and Engineering

End-to-end catalog of all Decennial system interfaces.

Shall include, but is not limited to:

• API names and parameters

• Service Names and parameters

• Signatures

• Data sources/destination parings

• Data/API call frequency and cadence

Ongoing Electronic upload to Government Repository to

COR/GPMO

Knowledge Transfer Strategy & Organizational Change Management Plans

3.2.3 Organizational Change Management

Result in minimal costs, maximum adoption, ongoing service, and long-term adoption for Decennial Census Programs’ transformation and application modernization initiatives that align with enterprise and Decennial objectives.

Shall include, but is not limited to:

• Defining change vision, objectives, and success measures

• Stakeholder analysis and segmentation

• Change impact assessment (Processes, roles, skills)

• Sponsorship and Governance model

• Communication strategy, frequency, feedback loops

• Training and enablement plan

• Adoption and readiness metrics

• Resistance management and escalation approach

• Cutover support and post go-live reinforcement (e.g.

coaching, office hours)

• Integration points with IMS, PI/iteration cadence (if applicable)

TBD Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

Application Rationalization and System Assessment Plan

3.3.1.1 Application Rationalization

Assessment plan defining evaluation criteria, methodology, and improvement recommendations for all applications.

Shall include, but is not limited to:

• Inventory of all applications and systems within scope

• Definitions of assessment criteria (e.g. business value, technical health, cost, security posture)

• Methodology, scoring model, and prioritization approach

• Evaluation of redundancy, utilization, and alignment with enterprise architecture

• Compliance and risk factors

• Recommendations for consolidation, modernization, or retirement in alignment with IT strategy and best practices

• Integration points with IMS

TBD Electronic upload to Government Repository to

COR/GPMO

Cloud Architecture & Engineering Plan

3.3.2 Cloud Architecture and Engineering

Target-state cloud architecture blueprint and associated controls.

Shall include, but is not limited to:

• Definition of the cloud target state and guiding principles

• Reference architectures and landing zone design

• Governance and roles/responsibilities

• Mapping of compliance controls

• Metrics

• Cloud naming standards

• Data tagging strategies

TBD Electronic upload to Government Repository to

COR/GPMO

IT Strategy and Roadmap

3.3.3 Systems Engineering Management

Strategic roadmap outlining current-state assessment and transformation pathways.

Shall include, but is not limited to:

• Current-state assessment of systems, capabilities, and technical constraints

• Target-state vision aligned to mission outcomes, business

TBD Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location priorities, and enterprise architecture principles

• Guiding technical and architectural principles supporting modularity, scalability, security, and interoperability

• Phased roadmap of prioritized initiatives and capabilities, organized into incremental planning horizons (e.g. near, mid, long term)

• Alignment to agile and incremental delivery practices, including dependencies and sequencing assumptions

• Identification of key risks, assumptions, and decision points.

System Defect Management Plan

3.2.5 System Level Testing

Defines a structured, repeatable process for identifying, tracking, and resolving system-level defects to maintain operational stability, compliance, and quality through the lifecycle.

Shall include, but is not limited to:

• Definition of the end-to-end lifecycle process

• Severity/priority and SLAs for response, workaround, and resolution

• Intake channels

• Methods for Root-cause analysis (RCA), corrective/preventative actions, and tracking of recurring issues

• Integration with CI/CD, automated testing, and backlog tools

• Governance roles and responsibilities

• Escalation paths and decision gates for high impact incidents

• Reporting cadence, metrics, and dashboards

• Process for security vulnerabilities and compliance defects

• Data retention, audit, and knowledge base updates to support continuous improvement

Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

Data Dictionaries and Catalogues

3.5.2 Data Management

Authoritative metadata repository for all data assets.

Shall include, but is not limited to:

• Inventory of data assets within scope, including datasets, sources, and ownership

• Standardized definitions for data elements, attributes, and fields

• Metadata describing data structure, format, lineage, and usage context

• Data quality, sensitivity, and classification indicators

• Usage guidance to support discoverability, reuse, and analytics activities

TBD Electronic upload to Government Repository to

COR/GPMO

IT Solutions Requirements Management Plan

3.3.4.1 Requirements Development

Outlines DITDs ownership in the overall requirements management process. It shall align with the overall RMP, but focus on the development, tracking and documentation of the solution requirements upon receipt of the stakeholder requirements.

TBD Electronic upload to Government Repository to

COR/GPMO

Test Strategies and Plans

3.4.3.2 Test Planning

Framework of test principles, scope, plans, and schedules.

Shall include, but is not limited to:

• List of high-level plans and principles that guide the overall software testing process.

TBD Electronic upload to Government Repository to

COR/GPMO

Test Data Strategy and Plan

3.4.3.3 Test Data and Scenario Creation

Defines the approach for creating, securing, and managing test data.

Shall include, but is not limited to:

• How test data will be created, secured, maintained, and refreshed to ensure accurate, repeatable, and compliant testing across all environments.

• Test data sources, types, and required datasets

• Data privacy, security, and compliance controls

• Roles and responsibilities

TBD Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• Test data refresh cycle and maintenance procedures

• Integration with test environments and test execution schedules

Cloud Application Migration Implementation Plan

3.4.6 Cloud Application Migration

End-to-end plan covering migration strategy, sequencing, tools, and validation.

Shall include, but is not limited to:

• CSP assessment and recommendations

• Cost benefit analysis

• Cloud adoption framework

• Governance Framework

• Migration Strategy

• Pre-migration readiness checklist

• Application inventory with dependencies/compliance requirements

• Migration sequencing and cutover approach

• Rollback procedures and downtime windows

• Migration Tools/automation scripts

• Performance validation and security posture checks

• Risk mitigation strategies and contingency plans

• Post-migration validation steps and acceptance criteria

• Integration with IMS

TBD Electronic upload to Government Repository to

COR/GPMO

Cloud Optimization Plan and Roadmap

3.4.6 Cloud Application Migration

Roadmap for FinOps, DevSecOps, and continuous cloud optimization.

Shall include, but is not limited to:

• Cloud optimization objectives and scope applicable across migrated and modernized cloud applications

• FinOps governance and optimization approach, including cost visibility, allocation, monitoring, and optimization practices

TBD Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location

• DevSecOps optimization practices including secure automation, pipeline standardization, and continuous improvement of cloud operations

• Zero-to-mastery enablement approach addressing skills development, knowledge transfer, and adoption maturity

• Optimization roadmap organized into phased improvement periods (near, mid, long term)

• Key assumptions, dependencies, risks, and optimization success metrics.

Data Currency Policies

3.5.2.3 Data Lineage

Shall include, but is not limited to:

• Definition of data currency requirements, including freshness, update frequency, and timeliness expectations

• Identification of authoritative data sources and data refresh points across the data lifecycle

• Policies governing acceptable data latency and expiration thresholds by data type or use case

• Roles and responsibilities for maintaining data currency and addressing outdated or state data

• Alignment of data currency policies with data lineage, data quality, and operational needs

TBD Electronic upload to Government Repository to

COR/GPMO

Data Management Disaster Recovery Plans

3.5.2.4 Data Storage and Retention

Data recovery and restoration strategies aligned with business continuity.

Shall include, but is not limited to:

• Overview of data storage and retention assets within scope and their criticality

• Defined recovery objectives and roadmap for recovering data, including recovery time and recovery point expectations for data assets

• Backup, replication, and data restoration approaches

Annually Electronic upload to Government

Reference

Elements of the Deliverable Due Date / Frequency

Delivery Method /Location supporting continuity of operations, including prototyping and testing processes for storage and recovery to validate that plans will be successful.

• Roles, responsibilities, and escalation procedures for data recovery activities

• Assumptions, dependencies, and constraints affecting data recovery and retention.

Integrated Application Monitoring Plan

3.4.5.2 Application Monitoring

Monitoring framework defining metrics, alerts, and reporting methods.

Shall include, but is not limited to:

• Monitoring approach and toolset

• Key performance metrics

• Alerting and notification procedures

• Roles and responsibilities for monitoring and issue response

• Reporting cadence and dashboard elements

• Integration with incident management processes

TBD Electronic upload to Government

2.0 Work Products

Work Product Section C Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

Change Log 3.1.1.1 Procurement Governance

Tracks all order changes with descriptions, decisions, approvals, and implementation outcomes. May be incorporated into the Communications and Decision Log for consolidated tracking.

Shall include, but is not limited to:

• Description

• Originator

• Date

• Status

• Impact Analysis

• Approvals

• Decisions

• Implementation Outcomes

As required Electronic upload to Government Repository to

COR/GPMO

Communication Plan

3.1.1.4 Communication Management

Describes communication protocols, including communication channels, meeting cadencies, documentation standards, escalation paths, and message coordination.

Shall include, but is not limited to:

• Communication methods and frequency

• Roles and responsibilities

• Meeting cadencies

• Documentation standards

• Escalation paths

• Message coordination

10 business days after PM is cleared, then Annually

Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

Communications and Decision Log

3.1.1.4 Communication Management

Records key communications. Decisions, actions, and order-administrative changes throughout the order.

Shall include, but is not limited to:

• Record of all key order and program changes, communications and decisions.

• Essential discussions, agreements, action items, and rationale behind major decisions made throughout the contract lifecycle.

Ongoing Electronic upload to Government Repository to

COR/GPMO

Contractor Work Breakdown Structure

(CWBS)

3.1.2.2.1.Contractor Work Breakdown Structure (CWBS)

Outlines the hierarchical decomposition of work aligned to the DWBS.

Shall include, but is not limited to:

• Major work scope elements, tasks, and deliverables required order execution

• Updates synchronized with changes to the

DWBS.

Ongoing Electronic upload to Government Repository to

COR/GPMO

CWBS

Dictionary

3.1.2.2.1.Contractor Work Breakdown Structure (CWBS)

Defines each CWBS element.

Shall include, but is not limited to:

• Scope

• Deliverables

• Roles

• Milestones

Ongoing Electronic upload to Government Repository to

COR/GPMO

Contractor Schedule

3.1.2.2.3 Contractor

Schedule

Order-level schedule aligned to CWBS, DWBS, Decennial IMS, deliverables, and the scope of the order.

Shall include, but is not limited to:

• Critical path activities

Ongoing Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Dependencies

• Schedule risks associated with order scope

Lessons Learned Log

3.1.2.7 Lessons

Learned Management

Captures insights, findings, and improvement opportunities derived from all order-administrative activities and observations and recommendations identified through order execution

Shall include, but is not limited to:

• Identification of lessons learned.

• Areas for improvement across the order.

• Impact of each lesson learned.

• Process improvement recommendations for each lesson learned.

After major deliverables, milestones, phase completions, decision gates, reviews, tests, and other significant events

Electronic upload to Government Repository to

COR/GPMO

Meeting Minutes & Action Items List

Task Areas 1 - 5 Shall include, but is not limited to:

• Meeting minutes and action item tracking lists for meetings identified by the COR.

Within three (3) business days after the meeting

Electronic upload to Government Repository to

COR/GPMO

Monthly QASP Performance Response & Meeting

3.1.2.3 Program

Quality Management & QASP Performance

Responds to Government QASP findings with clarifications, corrective actions, and performance updates.

Shall include, but is not limited to:

• A summary of the Government’s monthly QASP findings and the Contractor’s response addressing any Government-identified deficiencies, including clarifications, explanations, and supporting

Submit response of Government’s Monthly QASP findings within 3 business days of receipt.

Conduct Monthly QASP meeting within 5 business days of

Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location data for each identified performance observation.

• Corrective actions and preventative actions.

• Risks and risk mitigations.

• Issues and resolutions.

• Dependences or support needed from the Government.

• Notable accomplishments or process improvements.

receipt of Monthly QASP findings.

Monthly Risk & Issue Report

3.1.4.5 Monthly

Risk and Issue Reporting

Consolidates order risks and program risks into a unified monthly summary for Government review

Shall include, but is not limited to:

• High-level risks and issues across program management, technology, facilities, equipment, staffing, and funding

• Mitigation plans, status updates, and resolutions.

Monthly Electronic upload to Government Repository to

COR/GPMO

Operational Readiness Review & Support Materials

3.1.2.6 Operational

Readiness Reviews

Provides readiness evidence and documented outcomes for each ORR. ORRs are conducted in alignment with the Operational Delivery (OD) Schedules.

Shall include, but is not limited to:

• Summary of readiness status for upcoming operational phase

• Evidence that required capabilities, processes, tools, and resources are prepared

• Status of program-level deliverables relevant to deployment

10 business days prior to ORR.

Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Open items, risks, issues, and mitigation actions tied to readiness

• Data needed to support the Government’s phase-gate approval process

Oversight & Data Call Support Materials

3.1.2.5 Data Call

and Audit Support

Shall include, but is not limited to:

• Data and materials prepared to support responses to Decennial Census program data calls and oversight inquires, to include those from GAO, the Office of Inspector General, and other governing bodies.

As required Electronic upload to Government Repository to

COR/GPMO

Risk Register 3.1.1.3.Order Risk Management

Documents order and program risks in a manner that aligns with the Government risk management process.

Shall include, but is not limited to:

• Risk Description

• Likelihood

• Impact

• Mitigation

• Owner

• Status

Monthly Electronic upload to Government Repository to

COR/GPMO

Meeting Presentations and Briefings

Task Areas 1 - 5 Presentations and briefing materials supporting technical meetings, program reviews, governance boards, and other engagements, as required.

Shall include, but is not limited to:

• Key information

• Decisions

• Progress

• Risks

As required Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

Recommendations

Documentation and Reports

Task Areas 1 - 5 Documents and reports produced in support of IT project management, systems engineering, testing, security, architecture, planning, and operations.

Shall include, but is not limited to:

• Analysis of Alternatives (AoAs)

• Analysis/Evaluations of IT solutions and technologies

• API Standards

• Application Architecture Trade-off Analysis

• Application Security Playbooks

• Business Cases

• Business Continuity and Recovery Plans

• Change and Configuration Control processes, standards, templates

• Change Control Plan

• Data Integrity standards, policies, metrics, and frameworks

• Decennial Census Program Disposition Management Plan

• Defect Management Plan

• DevSecOps Documentation, Procedures, and Policies

• IIP

• Line of Business Architecture Documents

• ODMP

• Program Test Analysis Reports

• Program/Project Charters

• Project Close-out Plans

• Project Plans

As required Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Project post-mortems, after action reviews, retrospectives, and lessons learned

• Readiness Reviews

• Requirements documentation

• Risk Management Documentation

• Schedule Management Plan

• SDLC Documents

• Security Findings Remediation process

• SEMP

• Software Bill of Materials (SBOMs)

• Software Configuration Management documentation

• Software Developer Guide

• Standard Operating Procedures and process documentation

• System-level test cases, test scripts, test scenarios, and test metrics

• Systems Engineering Plan

• Systems Management Plans

• TEMP

• Training Materials

• Wireframe Diagrams

• Workflow Diagrams

• ZTA Gap Analysis and Recommendations

Training Plans & Curriculum

3.2.2 Government

Staff Training

Detailed training program aligned to Government workforce needs.

Shall include, but is not limited to:

• Training goals and objectives in alignment with skills and current state assessment.

• Training schedule

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Training delivery methods (e.g., experiential learning, hands-on workshops, or other best practice modes)

• Performance measurement

Government Staff Training

3.2.2 Government

Staff Training

Training content, as required by Government staff, and in accordance with the training plan.

Training topics must include but are not limited to Change Management (CM) tools and procedures, program management tools, Scaled Agile tools, and public and private cloud.

Shall include, but is not limited to:

• Manuals

• Documentation

• Job Aids

• Hands-on exercises,

• Training tools

• Demonstrations

• Seminars

Systems Architecture & Engineering Gap Analysis

3.3.1 Systems of Systems Architecture and Engineering

Identification of architecture gaps, recommendations, and roadmaps.

Shall include, but is not limited to:

• Gap analysis findings and recommendations

• Implementation roadmap, plans, and schedule

• Engineering footprints, plans, standards

• Future roadmap of on-prem, SaaS, and cloud/multi-cloud architectures, practices, technologies, tools, services, and

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location capabilities

Agile Planning and Execution Artifacts

3.2.1.2 Agile Program Planning and Management Support

Outputs from agile planning cycles documenting objectives, dependencies, and progress.

Shall include, but is not limited to:

• Incremental planning outputs documenting objectives, priorities, and planned work

• Team-level and cross-team coordination artifacts supporting aligned execution

• Visibility into dependencies, risks, and progress across delivery efforts

• Lightweight status and outcome summaries supporting transparency and decision-making

• Retrospective inputs or improvement actions identified during execution cycles

TBD Electronic upload to Government Repository to

COR/GPMO

Agile Program Enablement and Incremental Delivery Roadmap

3.2.1.2 Agile Program Planning and Management Support

Roadmap describing alignment, cadence, and governance across agile teams.

Shall include, but is not limited to:

• Description of the multi-team delivery structure and coordination approach

• Incremental, time-boxed planning cadence and synchronization points

• Identification of key roles, responsibilities, and coordination mechanisms across team, program, and stakeholder levels

• Agile coaching and training approach for teams and leadership

• Incremental planning and execution playbooks (e.g. planning events, reviews, TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location retrospectives)

• Agile performance metrics and reporting approach

• Approach for continuous learning, feedback, and delivery improvement

Application Rationalization Roadmap and Schedule

3.3.1.1 Application Rationalization

Sequenced implementation roadmap for rationalization.

Shall include, but is not limited to:

• Time-phased plan sequencing rationalization activities

• Milestones, decision gates, and dependencies across business units and systems

• Resource plans and cutover windows aligned to operational constraints

• Risk, compliance, and change management checkpoints (e.g. licensing, data privacy, stakeholder readiness)

• Integration with IMS and OCM plan for coordinated execution

• Reporting cadence (Status updates, milestone reviews)

TBD Electronic upload to Government Repository to

COR/GPMO

Cloud Architecture & Engineering Roadmap

3.3.2 Cloud Architecture and Engineering

Phased roadmap outlining required cloud services, capabilities, modernization activities, dependencies, and sequencing to support Decennial cloud adoption.

Shall include, but is not limited to:

• Time-phased milestones

• Sequenced migration waves and

Within 180 days of the contract award

Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location modernization activities

• Identification of dependencies

• Resource planning and up-skilling requirements

• Decision gates and approval check points for each phase

• Alignment with EA standards and security

• Reporting cadence

• Contingency plans

Data Science Documentation

3.5.1 Advanced Data Science

Documentation packages for advanced analytics and data science efforts, including analysis plans, technical reports, models, READMEs, training materials and prototypes.

Shall include, but is not limited to:

• Comprehensive analysis plans

• Technical reports

• Presentations and slides on conducted work.

• User manuals and READMEs for developed code or toolkits.

• Manuscript preparation for conference or journal submissions.

• Coding and documentation templates and compilations of data science best practices.

• Business and technical documents, standard operating procedures, business cases, newsletters, functional descriptions, system specifications, guidelines, special reports, training materials, and other project deliverables to meet the order requirements.

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

Application Architecture Design Patterns

3.4.2.1 Application

Architecture Support

Standardized, reusable architectural patterns guiding application design for interoperability, scalability, security, and consistency across systems.

Shall include, but is not limited to:

• Detailed design patterns for enterprise application architectures.

TBD Electronic upload to Government Repository to

COR/GPMO

Concepts of Operations

3.4.2.1 Application

Architecture Support

Documentation describing how an application or system operates, including user roles, workflows, major interfaces, and operational constraints.

Shall include, but is not limited to:

• Description of how applications support mission and business operations

• Key user roles and high-level operational workflows

• Application interactions and integration points

• Assumptions and constraints affecting application operations

TBD Electronic upload to Government Repository to

COR/GPMO

Reporting Strategy and Plan

3.2.1.6 Reporting Support

Framework for performance reporting, metrics and visualization.

Shall include, but is not limited to:

• Approach for monitoring and reporting progress of achieving security status to include but not limited to: ATOs and penetration testing

• Stakeholder Reports and Visualizations

• Summary Reports with Metrics

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

Architecture & Engineering Runbooks

3.2.4.3 Runbooks

Detailed steps for deployment, rollback, monitoring, and operational readiness.

Shall include, but is not limited to:

• Comprehensive steps detailing system and user interactions

• Deployment, rollback, and change procedures

• Soft launch activities

• System go-live activities

• Post-conduct operations interactions

• Monitoring/altering thresholds and incident response steps

• Patch/update schedule and responsibilities

TBD Electronic upload to Government Repository to

COR/GPMO

Requirements Traceability Matrices

3.3.4.2 Requirements Traceability

Structured matrices mapping requirements across lifecycle stages to ensure traceability from business needs to design, development, and testing.

Shall include, but is not limited to:

• Business to stakeholder level requirements.

• Stakeholder to solution level requirements and specifications.

• Requirements to test cases.

• Test cases to verification methods.

Ongoing Electronic upload to Government Repository to

COR/GPMO

Test Management Approach

3.4.3.3 Test Data and Scenario Creation

Framework supporting requirements traceability, defect injection analysis, test governance, and continuous improvement of the testing lifecycle.

Shall include, but is not limited to:

• Requirements traceability integration

• Defect injection rate tracking & analysis

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Test governance processes

• Testing lifecycle methods & standards

• Metrics, KPIs, and Reporting Cadence

• Test environment & data readiness requirements

Test Analysis Report

3.4.3.5 Test Reporting

Comprehensive summary of test activities, results, defects, insights, and evaluation metrics across test phases.

Shall include, but is not limited to:

• A comprehensive overview of the testing process, including details about what was tested, how it was tested, and the outcomes.

• Results and findings from the testing phase of software development.

• Reporting metrics and data visualizations capturing defects, testing trends, timeframes, and categories

TBD Electronic upload to Government Repository to

COR/GPMO

Plan of Action and Milestones

(POA&M)

3.4.4.4 Authority to Operate (ATO)

Documentation of ATO-related findings, remediation steps, responsible parties, timelines, milestones, and acceptance criteria for unresolved items.

Shall include, but is not limited to:

• Unique identifiers for each finding, description, severity, associated control

• Corrective actions for each item to include responsible parties, resources, and remediation steps

• Target completion dates and interim

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location milestones

• Risk acceptance or mitigation strategies for unresolved items

Research and Development Reports

3.4.7.1 Research and Development

Reports summarizing feasibility studies, research findings, technical evaluations, risks, opportunities, and recommendations related to new technologies or innovations.

Shall include, but is not limited to:

• Description of research or study scope, objectives, and approach

• Summary of data sources, methods, and analytical techniques employed

• Key findings, observations, and results of the research conducted

• Analysis of implications, risks, and opportunities relevant to the program

• Conclusions and recommended considerations or next steps for decision making

• Assumptions, constraints, and limitations of the research

TBD Electronic upload to Government Repository to

COR/GPMO

Analyses of Alternatives (AOAs) Master List

3.4.7.3 Application/ Solution AoA

A consolidated and continuously updated record of all AoAs (planned, outgoing, and completed), including scope assumptions, constraints, and decisions.

Shall include, but is not limited to:

• Description of the scope and decision context for each AoA

• Status of each analysis

TBD Electronic upload to Government

Reference

Work Product Elements Due Date / Frequency

Delivery Method /Location

• Reference to associated documentation, findings, or reports

• Identification of key assumptions, constraints, and decision Dependencies.