Skip to DART content

Overview

Usatii for Emergency Management. Prepare your workforce, staff incidents, and follow each deployment from the first order to the return home.

How DART works

A response team needs to prepare its people before an incident and keep track of them in the field. DART brings both stages into one workspace. A coordinator can follow a responder from training to assignment, then through travel and the return home.

Before sending someone to an incident, staff need to know whether that person is ready. Do they hold the right qualifications? Are they available for the requested dates? Have they had enough rest? DART brings the evidence together and shows the reason for each result.

Each person works within their assigned role. Responders manage their own work. Supervisors review their teams. Coordinators manage incidents and deployment orders. Other staff manage training, equipment, or the records they are allowed to change.

DART was built around FEMA’s survey for a new Deployment Tracking System. The survey is published with FEMA’s public notice on SAM.gov. DART also supports other emergency management teams that need to prepare people and coordinate their response.

A staffing example follows several distinct records. Task evidence and training support a qualification decision. The staffing check then considers availability and conflicts before an order is reviewed and accepted.

Preparation, selection, and field work use separate records. Evidence supports a credential, staffing checks support an order, and acceptance starts the deployment that records actual work.PersonStable IDTasks + trainingVersioned evidenceQualificationdecisionSeparate certifierStaffing needPosition, place, datesReadiness andconflicts pass?Reviewed orderNamed responder replyAccepted deploymentVisits, checks, return
Preparation, selection, and field work use separate records. Evidence supports a credential, staffing checks support an order, and acceptance starts the deployment that records actual work.

Prepare the workforce

Preparation begins with knowing who is on the team and what each person can do. Personnel records give each person a stable ID. The record connects to their employment and position history. Source identifiers show which outside systems supplied the data.

Readiness shows whether a person meets the rules for a position. A Position Task Book records the tasks they must complete. Training and certification records show what they have already earned.

People can work with a mentor and follow a development plan. They can take online lessons or attend a scheduled class. Their transcript keeps the results together. Earlier records stay available when a result changes.

A task-book approval, course award, and outside certificate remain different kinds of evidence. Their versions, dates, and current review states determine how they can support the next decision.

Staff the incident and carry the decision into the field

When an incident needs help, coordinators turn that need into assignments. An incident starts with a need for people. The coordinator defines the positions and dates, then compares responders. The selection view shows who meets the requirements and what might block an assignment.

A deployment order goes to a separate reviewer before it reaches the responder. The responder accepts or declines it. An accepted order starts the deployment record.

During the deployment, DART tracks station visits and daily checks. Supervisors can follow up on missing replies. Equipment stays linked to the person who holds it. Required end steps must be complete before the deployment can finish.

The accepted order revision supplies the deployment dates. Actual arrival opens a station visit; checkout closes it. Return and equipment checks must pass before final completion.

The incident walkthrough follows one team through these steps using real application screens. It keeps the same people, order, deployment, and radio from start to finish.

Selection and approval do not deploy someone. The named responder accepts the issued order; actual visits and completion checks then carry the assignment through the field.Saved selectionCurrent comparisonDifferentapprover?Issued offerDeadline appliesResponderacceptsAccepted revisionsavedActual visitArrival and checkoutEnd checkssettled?CompletedHistory retained
Selection and approval do not deploy someone. The named responder accepts the issued order; actual visits and completion checks then carry the assignment through the field.

Plan, report, and reconstruct

A response plan also needs to account for what might happen next. Surge planning tests whether the workforce can meet several incident needs at once. A coordinator can compare rest policies and see where staffing falls short. Readiness forecasts show gaps that may appear in the coming months.

Decision replay shows the facts used for an earlier staffing choice. Saved reports keep a fixed copy of results. Later changes to the source records do not rewrite that copy.

Evaluation results show how DART has been checked with saved tests and live public data. The evidence includes receipt handling and repeat-safe publication.

A saved result states the source cutoff and rules used. Reviewing that result explains the earlier decision; refreshing current records answers a different question.

Connect data without losing its source

Useful information often starts in systems the organization already uses. Integrations bring outside data into DART. Staff map the fields and check the proposed changes before applying them. The original input stays saved so they can trace a problem to its source.

Integration Studio lets staff build pages and rules around connected data. For example, a water-level reading can appear beside an incident. A rule can create a task when that reading crosses a set limit.

Permissions control who can see or change each record. Record protection adds handling rules for sensitive data. These checks also apply to reports and background jobs.

Capture retains source input. Preview explains the proposed changes, a different reviewer approves the import, and application checks the source versions again. Publishing makes the checked data available for its configured use.

Evaluate DART for your organization

The clearest way to understand DART is to follow a piece of work from start to finish. Start with a real workflow. Follow a qualification request or a training class. Walk through a staffing decision and an accepted order. Inspect the result and the history behind it.

The federal deployment pages explain hosting and security review. The requirements index maps the 61 capabilities in FEMA’s survey to the work DART supports. It also links to the details needed for an agency evaluation.

The evaluation page separates saved service and browser checks from live-source examples. Their dated results are evidence of the cases tested, not a claim about production concurrency or agency authorization.