Skip to DART content

Federal capabilities and deployment

Review DART’s federal capabilities. Understand what is configured and assessed for an agency deployment.

Built for workforce and deployment work

Federal workforce management needs to connect preparation with the response itself. DART was built around FEMA’s workforce and deployment survey. Its requirements index maps all 61 numbered capabilities across the 17 subtask groups.

An agency evaluation can follow those entries into the working application. Staff can inspect the records and decisions for each workflow.

FEMA’s public notice provides the original request. Its survey workbook describes the capabilities used in this guide. The RFI overview gives the program context.

Government-controlled hosting

Government buyers need to know where the system and its information will run. FEMA’s survey asks for a FedRAMP High cloud and a government-owned cloud environment. The delivery team must define the selected hosting boundary.

That boundary states which services are approved and where data flows. It also names the people responsible for operating them.

DART includes GovCloud service adapters. Those adapters do not grant a FedRAMP authorization or Authority to Operate. Authorization applies to the assessed agency system.

The agency deployment boundaryCONTROLLED SYSTEM BOUNDARYAgency identityKnown sign-in identityApplication controlsScope • policy • record versionApproved servicesProtected records • retained eventsAssessment evidenceApproved access
Hosting, identity, data handling, operations, and assessment evidence are defined for the selected agency system.

Access controls and security review

The agency needs to see how an application control works within the wider security plan. DART checks identity and access in its application services. Dated permissions limit where a person may act. Private file checks and independent review protect the related workflows.

The delivery team maps these controls to the agency’s security baseline. The assessment also covers network policy and key handling. Logs and security monitoring must be configured for the environment.

CUI, privacy, and records

An agency’s information rules continue to apply when records are brought into a new system. DART supports protected records and CUI labels. It can restrict exports and block configured data combinations. Retention schedules and holds govern record disposal.

The agency supplies its handling policy. It identifies which sources own each type of fact. Data migration and integrations are tested against those decisions.

Test the agency deployment

The agency must be able to check the delivered system against its agreed requirements. Agency acceptance tests the selected version and environment. The tests cover real role boundaries and operational workflows.

Section 508 review checks accessibility. Load tests examine incident surges and slow connections. Recovery and cutover rehearsals check continuity.

Each result needs a clear expected outcome. The saved evidence shows what was tested and what happened.

Federal delivery and technical engagement

A delivery needs named people who can build the system and support it in use. USATII’s federal delivery plan assigns responsibility for engineering and program management. It also covers security review and ongoing support.

The published DART jobs are anticipated roles. Hiring depends on an award or approved funding. Those postings do not establish an awarded FEMA contract or a fully staffed team.

The engagement defines the named staff and their responsibilities.